Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "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.", "Undo of operations on modifiers is inconsistent when object is in edit mode\nBroken: version: 2.79, 2.82 (sub 1), branch: master, commit date: 2019-11-22 18:14, hash: 373e936e3e\n\n\nwhen a modifier that has been **added in edit mode** to a object and is **deleted in edit mode,** it is not restored when using undo. \nThe operation shows up in the undo history but does nothing.\n\n\n1. go into edit mode\n2. add a modifier\n3. delete the modifier\n4. use undo, notice modifier is not restored.\n\ncreating the modifier in object mode or deleting it in object mode will restore it when using undo. this is a very confusion inconsistency that i noticed with the new undo method.\n", "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", "Restore default value operator removes redo panel\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.0\nWorked: 3.4.1\n\nWith user installed add-ons (sometimes Blenders own operators too) if the user tries to reset a value by RightMouseClick / \"Reset To Default Value\", the redo panel closes.\n\n1) Activate the user installed add-on\n2) Change a value\n3) RMB on the property from redo panel, select \"Reset To Default Value\"\n\nThis will close the panel and end the active add-on (may not happen on first attempt)\n\nYouTube video at the link:\n4woEVTFSrtw\n\n", "Re-render after saving a render result as image with 'Copy' option turned OFF makes blender unresponsive\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: versions 2.79 & 2.81 (sub 16)\nWorked: (optional)\n\nRender with F12, save the rendered image with 'Copy' turned off, and render again. This makes (parts of) Blender unresponsive.\n\n - Render the default cube.\n - Image - Save as, and uncheck Copy in the options.\n - Click Save as image.\n - Re-render the image.\n - Press {key Escape} to close the render window (it doesn't).\n - Press {key F12} to re-render (it doesn't).\n\nStrangely enough some parts of Blender are still responsive. For example {key Shift F12} still switches to the timeline.\n", "Wrong property changing `matrix_world` and destructive undo via RMB.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken:\nversion: 3.6.1\nversion: 4.0.0 Alpha\nWorked: never\n\nReturning to the original state during editing (or canceling) does not give the result that was when editing was started.\n<video src=\"attachment\" title=\"2023-08-16 21-40-53.mp4\" controls></video>\n\n1. Copy script and run\n```python\nimport bpy\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Test Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n col = self.layout.column()\n ob = context.object\n col.prop(ob,'name')\n col.prop(ob,'matrix_world')\n\nif __name__==\"__main__\":\n bpy.utils.register_class(Panel)\n```\n2. Quickly change the scale value for the object matrix.\n3. Press Right mouse button.\n\n", "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.", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "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", "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: 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", "GPencil: Add multiframe support to Move to Layer\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)", "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", "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled" ]

[ "[Poly Build] Cannot use \"shift delete\" for faces when Keymap is set to \"Industry Compatible\"\nOperating system: Win 10 64bit\nGraphics card: GTX 980\n\nBroken: 2.81.16 Release Version\nWorked: (optional)\n\nThe \"shift delete\" short cut of poly build tool is broken for deleting faces when keymap is set to \"industry compatible\"\n1. Open Blender, hit \"General\" for the default box\n2. Open: Edit -> Preferences -> Keymap, Set to \"Industry Compatible\" then close preferences window\n3. Enter Edit Mode and enable poly build tool\n4. press and hold shift while moving the mouse cursor over any faces, the red outline for faces won't show, can only delete points or lines.\n\nBased on the default startup.", "Industry Compatible Shortcuts - Doesn't preview the tool PolyEditTool like blender shortcuts\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n[if you active Industry Compatible ShortCuts or or create your owns, you can not delete face using Shift+Click, only works if you active Blender Shortcuts.]\n\n\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." ]

[ "Artifacts around shadow catcher object\nOperating system: Win 10 PRO 19041.1348\nGraphics card: GTX 1080\n\nBroken: Official 3.0\nWorked: 2.9 lts\n\n{[F12718649](image.png),size = full}\n[头图制作B.blend](头图制作B.blend)\n\nLine is faintly visible at Y=472px height.\n\nThis doesn't happen when Denoise node Prefilter is set to Accurate, but when opening older files, Fast option is used by default.\n", "GPencil: Buffer stroke is only visible in the area that originated the drawing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.1 26.20.15019.1003\n\nBroken: version: 2.90 (sub 0)\n\nWhen creating two viewport, you can't watch the lines drawn at the same time\n\nCreate two viewport and move a little on the screen. Then start drawing. You will notice that the lines are not visible at the right time\n[bandicam 2020-04-21 14-03-29-287.mp4](bandicam_2020-04-21_14-03-29-287.mp4)", "Operators to add to the Outliner\nCurrently the Outliner allows users to fully manage Collections. You can add them, remove them and manage them fully.\n\nHowever, for other data this is very limited currently. Many users would like to be able to use the Outliner to do many more basic management tasks. I think we should add many more basic things here that are related to adding, removing, copying, duplicating and so on.\n\n\n\n\nThese features we can add to the Outliner context menu system:\n\n**Objects:**\nCurrently you can perform these operations in the Outliner for objects.\n - - [x] Delete\n - - [x] Rename\n - - [x] Copy/Paste\n\nIn addition, it would be useful to add these commands too:\n\n - - [ ] Add New (with full list of primitive types)\n - - [ ] Duplicate\n - - [ ] Make Local\n - - [ ] Make Proxy\n - - [ ] Add Constraint\n - - [ ] Add Modifier\n\n\n**Constraints & Modifiers**\nCurrently you can:\n - - [x] Delete\n - - [x] Rename\n - - [x] Toggle visibility, but only in the context menu, strangely\n\nIn addition, we should add:\n - - [ ] Visibility toggles\n - - [ ] Re-ordering (by dragging)\n - - [ ] Transfer modifiers & constraints from one object to another (by dragging)", "Objects with \"In Front\" don't appear when overlays are reenabled until viewport update\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBut works on:\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.91.2\n\nMight be the same as #102199 (Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)) (which was bisected down to 0f95f51361)\n\nWhen an object (specific ones) is set to be displayed in front of everything else, it will not come back immediately when reenabling the overlays. This happens only in solid shading mode as far as I can tell.\n\nThe objects affected by this are first off all objects which have some kind of lines, so camera, lights, the wireframes of meshes, outlines of reference images, empties, ...\nThen there is also the armature which is special in the way that it is rendered solid, but it also vanishes just like the lines.\n\n1. Add an armature\n2. set it to In Front in Armature > Viewport Display\n3. toggle the viewport overlays on and off (that button next to x-ray)\n4. if your rendering was set to solid shading, the armature should be gone now\n5. rotate the view, the armature will reappear\n6. you can do the same with the default camera and light and on the cube if wireframes are enabled (globally or locally on the cube) \n\n", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "Eevee 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", "Viewer node draw depth issue in x-ray mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nViewer node viewport overlay is having some Z-depth drawing issues. Seems to be caused by the X-Ray toggle.\n\n\n\nAdd an object in geometry nodes and view with viewer node\n\n", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Outliner: Linking object hierachies to a collection is buggy\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX Vega ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 2.93.2 Release Candidate\nWorked: Unknown\nLinking objects with parent child relationship has inconsistent display behaviour in outliner\n\nThis bugreport is about linking an object in the outliner to an additional collection. \n\nA linked object can have children. Normally they are displayed in a greyed out state until they are also linked to the same collection as the parent. But there is a bug or at least an inconsistent behaviour if these childs are displayed in a greyed out state or not at all.\n\n\nThe following script adds 3 cubes ,creates a collection and links the cubes to it. \nI deleted everything from the Scene Collection and did run the script. \n\nThis will work: \n\nBut just one more child-level in the tree and it starts to behave inconsistent as can be seen in the outliner shown in the screenshot of some reruns of the same script on a totally empty scene. \n\n\n\n\n\n\n\n\n\n```\n\nimport bpy\n\n# create some cubes\nbpy.ops.mesh.primitive_cube_add(location=(0,0,0))\ncube0= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(5,0,0))\ncube1= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(10,0,0))\ncube2= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(10,0,0))\ncube3= bpy.context.active_object\n\n#create a new coll\ncollection = bpy.data.collections.new(\"Test\")\nbpy.context.scene.collection.children.link(collection)\n\n# establish parent child relationships\n\ncube1.parent = cube0\ncube2.parent = cube1\ncube3.parent = cube2\n\n# link root cube to new coll\ncollection.objects.link(cube0)\n\n\n```\n\n\n", "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.", "Missing Letter V and Black Screen\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.0\n\nWhenever I open Blender, the viewport is black and the letter v is not displayed in any of the menus. Here is a link to a screenshot: VZui9.png \n\nIt simply appears like this on startup.\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", "Missing overlays in the viewport when viewing through transparent shader\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6.1\n\nwhen viewing an LGT-shadow_caster.004 object, all overlays disappear from a certain side of it\n\n\nSee LGT-shadow_caster.004 in blender 3.6 splash screen\n\n", "Metal: selection with GPU depth picking is broken in wireframe mode\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nWhen working in the 3D viewport, when in Wireframe mode and Xray mode is OFF, clicks to select an object are passed through and select objects behind the object. It's very difficult to select the object whose intention it is to select.\nview?usp=sharing\n\nThe video link above demonstrates this.\n\n\n", "Viewport rendering bug : unable to make the render progress (infinite calculation)\nOperating system: Windows 11\nGraphics card: RTX 3090\n\n**3.0.1**\n\nI installed the latest studio drivers for the graphic card (28 january 2022 version), and then :\n\nI encounter a really strange bug when using the viewport rendering (with or without denoising) on some projects. This bug only happens on this new computer, not on my iMac.\n\nDescription : it's like the viewport rendering \"never stops\" and fails to progress. I see the object, but in the \"worst\" rendered version only. It doesn't progress at all and I can hear the graphic card working infinitely, trying to calculate it.\n\nThe bug is present both using CUDA and Optix. Notice that normal rendering works really fine.\n\nUPDATE : The bug is also present with an old version of the studio drivers.\n\nBlend file : [realistic-atom-1.blend](realistic-atom-1.blend)\n\n" ]

[ "Outline Selected is invisible in front of image empty in X-Ray mode\nOperating system: Linux-5.3.0-53-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83 (sub 17)\nWorked: 2.82a\n\nThe \"Outline Selected\" overlay is invisible in X-Ray mode where a selected mesh object is in front of an image empty,\nmaking the overlay useless in that area.\n\nLatest builds of Blender 2.83 and 2.90 are affected.\n\nIn the 3D Viewport:\n - Import an image as an empty (e.g. drag-and-drop in a jpg file)\n - Place a mesh object infront of the image and select it (e.g. the default cube)\n - Activate X-Ray mode (e.g. using Alt+Z)\n\nSee attached .blend file as example:\n[outline-selected-invisible.blend](outline-selected-invisible.blend)\n\n" ]

[ "Geometry Nodes not using `MeshSequenceCache` data while rendering\nOperating system: Linux-5.4.0-153-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.6.2\n\nDuring the rendering, the geometry contained in the `Object Info` node in geometry nodes does not take into account `MeshSequenceCache` modifiers of the corresponding object.\n\nHere is a simple blender file containing a 3D animated sketch made in VR with Quill, and imported through an Alembic file : [bug_mesh_cache_geo_node.blend](attachment). \nThe sketch has 2 keyframes, with each exactly one stroke. \n\nA geometry node is applied to the mesh to add a sphere at the position of the first vertex of the curves.\n\n\n\nA rendering of the second keyframe (frame 10 for example) shows that the geometry node is using the data of the first keyframe of the curve, since the sphere is located at the beginning of the curve in the first keyframe.\n\n\n\n", "Inharitance for `ShaderNodeCustomGroup` is broken\nOperating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nWhen a custom node class is inherited from a base class, it breaks the base clas.\n\n```\nclass MyNodeBase(bpy.types.ShaderNodeCustomGroup):\n ... \n\nclass FooNode(MyNodeBase):\n bl_idname=\"my.foo\"\n bl_label = \"foo\"\n\nclass BarNode(MyNodeBase):\n # this get broken if any derved class exists\n bl_idname=\"my.bar\"\n bl_label = \"bar\"\n\nclass BazNode(BarNode):\n # this works but breakes BarNode\n bl_idname=\"my.baz\"\n bl_label = \"baz\"\n\n```\n\nAttempt of creating `BarNode` results in:\n\n```\nWARN (bpy.rna): /home/sources/buildbot-x86_64-slave/linux_glibc217_x86_64_cmake/blender.git/source/blender/python/intern/bpy_rna.c:8164 bpy_class_call: unable to get Python class for RNA struct 'my.bar'\nTraceback (most recent call last):\n File \"/home/qmax/Heap/3d/test.blend/nodes.py\", line 23, in execute\nRuntimeError: Error: Cannot add node of type my.bar to node tree 'Shader Nodetree'\n```\n\n\n\n - open attached file and execute packed nodes.py\n - call operator 'add bar' in shader editor\n\n[test.blend](test.blend)\n\n**Workaround**\n\nRegister classes in reverse order: derived first, then base.\n\n```\nclasses = (BazNode, BarNode, FooNode)\n\nfor c in classes:\n bpy.utils.register_class(c)\n```\n", "Geometry Nodes fouling up motion blur\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.1.0\nWorked: N/A\n\nGeometry Nodes applied to a spline which affect its shape over time do not blur when Motion Blur is enabled.\n\nLoad attached simple file. Render frame zero. There is no blur at all. Render frame 1, *everything* is blurred, despite only part of the spline is in motion. It would appear the entire spline is blurred according to how the base object is moving, not how the spline is deformed as a result of the applied Geometry Nodes.\n\nNote that same file loaded into 3.3.1 causes Blender to crash (GPU rendering only - it's a stack corruption bug in the nVidia driver, but 3.1 doesn't cause a problem). I previously reported that crash but it was rejected due to possibly being related to the Photographer add-on, which I have uninstalled. It still crashes.[Motion Blur Bug.blend](Motion_Blur_Bug.blend)", "\"Slice String\" field input shows as error, but works (lack of string fields)\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.1\nBroken: version: 4.0.0 Alpha\nWorked: /\n\nA field can be connected to \"Slice String\" node \"Position\" input, and while it shows as red error, it does work. In the attached files, the connection between \"Duplicate Elements\" and \"Slice String\" is shown in red, despite node tree working as expected (tested in Blender 3.5 + current 4.0 daily-build).\n\nAlso note the lack of fields between the \"Slice String\" and string \"Equal\" nodes.\n\nSee attached files.\n\n---\n\nIn the example file, each symbol in a string is an instruction for creating an object at a specified position.\nThe instructions implemented here are \"T(op)\", \"C(enter)\" and \"B(ottom)\".\nI therefore take the input string and create an object for each symbol in the string, then use the geometry index to find the corresponding string symbol to do modifications on the geometry.\n\nFor this to work, \"Slice String\" needs to accept the field input (from \"Duplicate Elements\" field \"Duplicate Index\") so each geometry duplicate gets its own symbol from the input string. This works, but the connection is shown as error in red.\n\nIdeally \"Slice String\" would accept a field for \"Position\" and \"Length\", so arbitrary parts of the string can be extracted for each geometry duplicate. The output of \"Slice String\" should also be a field.\nI'm not sure if there's a way to handle this without an error in the geometry nodes.\n\nOverall, it seems Blender is lacking string-fields, because the \"Equal\" node also defaults to fields for all types except strings. Yet, fields also seem to work here, too?\n\nNot needed here, but the \"String Length\" node also doesn't seem to explicitly support fields.\n\n", "Geometry Nodes \"On Cage\" modifier option does not adjust the editcage to the modifier result (instead, it modifes the result to the original editcage)\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\nGeometry Nodes \"On Cage\" modifier option does not adjust the editcage to the modifier result (instead, it modifes the result to the original editcage)\n\n[GN_OnCage_option.blend](GN_OnCage_option.blend)\n- open .blend\n- we have two modifiers doing the same thing:\n - a GN modifier that just translates 2 along the X axis\n - a \"traditional\" displace modifer doing the same thing (could be achieved differently)\n\n- now toggle the `On Cage` option in the modifier for the GN modifier (it puts the result in the space or the original editcage -- wrong)\n\n- disable the GN modifier, enable the displace modifier, toggle its `On Cage` option (it puts the editcage in the space or the result -- expected)\n\n", "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "Geometry Nodes: Add option to Set Spline Cyclic node to keep shape\n### Problem\n\nAt the moment setting a closed spline to not cyclic, creates a hole between the first and last control point.\n\n### What needs to change\n\n- Add a boolean field input to the node, called `Keep Shape`. \n- The field gets evaluated on the spline domain, just like the other inputs to the node.\n- If the original spline was cyclic, an extra control point is added at the position of the first control point where the field is `true`.", "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", "Nodes to convert between cartesian/spherical coordinates\nThere should be nodes to convert between spherical and cartesian coordinates in a standardized way.\n\nThis point came up when discussing [D12746](D12746) .\n\nThey are multiple design aspects to be figured out:\n- Node layout\n- Naming and Scope\n- Units\n- Value Ranges", "environment pass is occluded by geometry making it unusuable with a shadowcatcher\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 1)\nWorked: unsure if ever\n\nenvironment pass is occluded by geometry making it unusuable with a shadowcatcher\n\n\nopen attached .blend, go to compositing workspace, hit f12, when finished use the split viewer factor to slide between the image and the environment pass. \n\nPerhaps the transparency section needs an additional 'shadow catchers are transparent'.......although that wouldn't make much sense as shadow catchers should always be transparent. Regardless, the environment pass definitely shouldn't contain any geometry information. Is there ever a scenario where you'd want the environment AOV to be jet black where the 3d objects are located?\n\n[environment alpha bug.blend](environment_alpha_bug.blend)", "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", "Search of nodes from multiple strings\nFor the math nodes it would be good to have a way to search \"dot\" and add the attribute vector math in the \"dot\" mode.", "Keymap manager - Missing entries for node tools\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\n\nThe entries for the node tool tool shelf buttons doesn't show in regular view in the keymap manager. They just show when you search for them by node.select\n\n\nThe buttons in the tool shelf have each a own category in the keymap. For the box select tool in the 3d view that's for example four entries in the category 3D View Tool: Select Box.\n\nThe entries for the toolshelf buttons in the node editor does not show. You have to search it, with \"node.select\" for example, then they come up. But they do not show in the regular keymap list in the Node category. And nowhere else, at least from what i can say. I have spent an hour now to expand the whole keymap tree, and couldn't find it. I have modified it to get the restore button that should lead me to the keymap item, and also no luck.\n\n\n\n[2021-01-08 10-12-23.mp4](2021-01-08_10-12-23.mp4)\n\n", "Support geometry node in glTF exporter\nThis should be possible when API will manage it.\nCurrent code used by glTF exporter:\n\n```\ndepsgraph = bpy.context.evaluated_depsgraph_get()\nblender_mesh_owner = blender_object.evaluated_get(depsgraph)\nblender_mesh = blender_mesh_owner.to_mesh(preserve_all_data_layers=True, depsgraph=depsgraph)\n```", "Geometry Nodes: Simulation nodes cache assert\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: version: 4.0.0 Alpha\n\nSee attached stack trace file.\n\nDebug build.\n1. Geometry nodes:\n a. Add Simulation nodes.\n2. Quickly and randomly move time cursor on timeline by hands.\n\n" ]

[ "Geometry Nodes in searching pulls nodes from other node add-ons\nOperating system: Windows 11\n\n\nBroken: 3.4-6f15141f2731\nWorked: 3.2, 3.3\n\nNot bisected but I suspect bdb5754147\n\n\nSearching for a node brings nodes from other node addons.\n\n- Install Sverchok nightly: sverchok#installation\n- Install Blender 3.4 nightly\n- Add an object\n- Add a geonode modifier\n- Search for \"random\" node (see the attached video for the reference)\n\n[blender_vh4ZUevmqh.mp4](blender_vh4ZUevmqh.mp4)", "Custom nodes appear in search results for tree types that don't support them\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0\nWorked: 3.3\n\nCustom nodes created for custom node trees now appear in the search results when adding nodes to the built-in tree types (Shader, Geometry, etc)\n\nExact steps are somewhat complicated since you need to have python script create a custom node tree type along with nodes to go in it and register them... But if you have an add-on or script that creates custom nodes not meant to show up in the Shader node tree and search for them by name while in the Shader node editor they now appear in the search results and can be added to the tree since 3.4. In the previous version they did not appear in search results and could not be added in this way.\n" ]

[ "Particle Edit Breaks After Selecting a Mesh with Cloth Physics\nOperating system: macOS 10.13.6\nGraphics card: NVIDIA GeForce GT 650M 1024 MB\n\nBroken: at least 2.82 up to 2.92 experimental (I suspect it never worked since 2.80)\nWorked: 2.79\n\nParticle edit behaves like object edit mode, but the UI shows \"Particle Edit\" being active.\n- There is no circle typical for the comb tool around the mouse cursor.\n- No additional key points to select or black hair strands are rendered.\n- Instead of e.g. combing you will move the object around once you drag with the mouse.\nBasically everything except for the UI stays in \"Object Mode\".\n\nEffect On (broken):\n\n\nEffect Off (works as expected):\n\n\nBased on the default startup:\n1. Go to \"Particle Properties\"\n2. Add a particle system\n3. Set its type to \"Hair\"\n4. Add a second particle system\n5. Set its type to \"Hair\" too\n6. Add a new mesh e.g. \"Plane\"\n7. Go to \"Physics Properties\"\n8. Add \"Cloth\" physics\n9. Select the original \"Cube\" again\n10. Switch mode to \"Particle Edit\"\n\nWays to reverse the effect (make \"Particle Edit\" work properly again):\n- Either: Make a new file and append both objects of the old file\n- Or: Delete one of the particle systems on the \"Cube\" and undo the operation\n\nEven after reversing it you can restore the effect by selecting the \"Plane\" once.\nAt least two particle systems are required for the effect.\n\nThe effect can even be saved and stays the same after loading from the file again.\nThus I was able to create two files one with the effect and one without.\nThe file without the effect is a little bigger in size.\n\n[EffectOn.blend](EffectOn.blend)\n\n[EffectOff.blend](EffectOff.blend)\n\nIt took me a whole day to find the cause and boil it down so far.\nHope it helps and that it can be fixed with the provided info.", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "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)", "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", "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", "Clicking \"Particle Edit\" mode causes Blender to crash\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.89\n\nBroken: version: 3.5.0\nWorked: I dunno\n\nCan't enter into the Particle Edit mode.\n\nThis issue is probably related to: 106927#issue-96303\n\nIn the sample file, in the Curves Sculpt mode, after converting my Curves (name of the layer: \"my_test_4\") to a particle system, then select the newly converted particle system and enter into the Particle Edit mode, and Blender crashes.\n\n\n\nA sample file is attached. Thank you!\n\n", "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", "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", "Material Preview (EEVEE) can cause access violations when switching to edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.3\nWorked: N/A\n\nSwitching to edit mode with material preview (EEVEE) enabled results in a crash \n(Log from my machine produced with the joined blender file also joined to this report)\n\nusing the file joined in this report:\n- Open the scene\n- Select \"Circle.039\"\n- Switch to material preview\n- Attempt to enter edit mode on \"Circle.039\"\n\n", "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", "Keyboard shortcut doesn't work after switching applicationss\nOperating system: windows 11\nGraphics card: Intel(R) UHD Graphics 630 & NVIDIA GeForce GTX 1060 with Max-Q Design\n\nBroken: Blender 3.1, a solid update to an already outstanding release. Released March 9th, 2022\n\nWhen using different Keyboard shortcut for every window, keyboard shortcut doesn't work when we switch between applications\nCTRL, ALT, Shift, tab are fine, but all of the characters are no response, such as G, E, Shift D, etc.\n\n- Open Windows Settings tab\n- Enable: `Let me use a different input method for each app window` {nav Time & Language > Typing > Advanced Keyboard Settings}\n- Open chrome or any other application and change input method (Chinese for example)\n- Open blender and keep default input method (English for example)\n- Type something in other application window\n- Switch to Blender and use hotkey", "Alpha channel of Textures can't be deactivated in UV Editor\nOperating system: Windows10\nGraphics card:Geforce GTX 970M\n\nBroken: 2.91.0\nWorked: 2.83.0\n\nWhen you load an Image/Texture with an alpha channel in the UV editor, you can't turn the alpha channel off anymore, the image will stay black.\nIt worked in older Versions from 2.80 up to 2.83, there you only have to click on **Color** in **Display Channel** options.\n\nOnly areas that aren't black in the Alphachannel will be visible, in my examples I work with textures that need an all black Alpha channel.\n\njust load any Texture with Alpha channel in UV editor viewport\n\n\n\nHere an Screenshot from Blender 2.83.0 where it worked\n\n\n\n\nand here an screenshot of Blender 2.91.0, the same Texture is used, I also tried different settings under Image, but nothing works\n\n\n", "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)", "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", "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 Crashes When Switching to UV Editing (Mac)\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.90.0 Alpha\nWorked: N/A\n\nBlender crashes when selecting the UV editing workspace. \n\nOpen a new Blender file (Mac Version) and select the \"UV Editing\" workspace. Blender crashes with new or old file. \nAll other \"workspaces\" work as normal.\n\nT78767#976762", "Active workspace UV Editing (segmentation fault)\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 2.90.0 Alpha\nWorked: version: 2.90.0 Alpha\n\nWhen selecting \"UV Editing\" in the active workspace, Blender crashes (segmentation fault).\n\nYou open the default startup and select the cube and then you go into the \"UV editing\" area, it comes on the console:\n\nWriting: /var/folders/kb/tncgngyj6q7_p2ykdcbxkvth0000gn/T/blender.crash.txt\nzsh: segmentation fault [blender.crash.txt](blender.crash.txt)", "Instant crash clicking on \"UV Editing\" tab in 2.90\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.12\n\nBroken: version: 2.90.0 Alpha\n\nInstant crash clicking on \"UV Editing\" tab\n\nOpen Blender 2.90 alpha, click the UV Editing tab leads to crash\n\n", "Crash when entering edit mode with UV Editor open\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M395X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83.0 , caused by afd976a3b4 ?\n\nWhen the view port has both the object modelling window and the UV Editor window open, Blender crashes when entering edit mode. I repeated the crash several times in a row. It would crash when trying to edit several different meshes. Once I closed the UV Editor, the crashing stopped.\n\nSeems similar to T70247 but the problem manifests in 2.90 Alpha and not in 2.83.0. Also, I think it started to manifest around the July 1 build.\n\nSelect a mesh and enter edit mode based on sample .blend file.\n\n\n", "Blender crashes when entering Edit Mode\nOperating system: MacOS 10.15.5\nGraphics card: Radeon Pro 560X 4 GB, Intel UHD Graphics 630 1536 MB\n\nBroken: v2.90 alpha, July 12 (first identified July 11)\nWorked: v2.90 alpha, mid-June build\n\nEntering edit mode on any object causes Blender to crash.\n\nCopying the objects to other files lets them be edited. The original file (and copies of it) still crashes.\nEnter \"shading\" workspace, or open the UV editor. Select a mesh. Enter edit mode. Promptly crash.\n[example.blend](example.blend)\n\nRelated, clicking on the \"UV Editing\" workspace also causes an immediate crash regardless of mode. Likely part of the same issue." ]

[ "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", "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.", "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", "Nodes: Assert and crash: Editing nodes through the material panel and undo.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8729\n\nBroken: 3.4, 3.3, ... 2.8\nWorked: never\n\nWhen I select certain nodes from the materials tab after pressing undo on the last node change, blender crashes. But only if the last click is made with my wired USB mouse. Or even if the cursor was left on the button to switch tabs before clicking with the touchpad.\n\n\n```lines=10\n# Blender 3.4.0, Unknown revision\nbpy.context.space_data.context = 'MATERIAL' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF717820508\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n\n\nStack trace:\nblender.exe :0x00007FF7178203F0 blender::ed::space_node::ui_template_node_link_menu F:\\Blender_build\\first\\blender\\source\\blender\\editors\\space_node\\node_templates.cc:659\nblender.exe :0x00007FF71736AAF0 ui_block_func_POPUP F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_menu_popup.cc:183\nblender.exe :0x00007FF717463480 ui_popup_block_refresh F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_popup.cc:566\nblender.exe :0x00007FF717463050 ui_popup_block_create F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_popup.cc:796\nblender.exe :0x00007FF71736CA60 ui_popup_menu_create F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_menu_popup.cc:358\nblender.exe :0x00007FF717397CC0 ui_block_open_begin F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:4224\nblender.exe :0x00007FF717391810 button_activate_state F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8338\nblender.exe :0x00007FF71739CD50 ui_do_but_BLOCK F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:5982\nblender.exe :0x00007FF7173A7AB0 ui_do_button F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8027\nblender.exe :0x00007FF7173A9D20 ui_handle_button_event F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:9189\nblender.exe :0x00007FF7173BA070 ui_region_handler F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:11275\nblender.exe :0x00007FF7156CFE60 wm_handler_ui_call F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:786\nblender.exe :0x00007FF7156D1CE0 wm_handlers_do_intern F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3217\nblender.exe :0x00007FF7156D01F0 wm_handlers_do F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3334\nblender.exe :0x00007FF7156CB580 wm_event_do_region_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3754\nblender.exe :0x00007FF7156CB440 wm_event_do_handlers_area_regions F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3784\nblender.exe :0x00007FF7156DCD90 wm_event_do_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3979\nblender.exe :0x00007FF7156A5E50 WM_main F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm.c:643\nblender.exe :0x00007FF714C52160 main F:\\Blender_build\\first\\blender\\source\\creator\\creator.c:579\nblender.exe :0x00007FF7186F9260 invoke_main D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7186F9010 __scrt_common_main_seh D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7186F8FF0 __scrt_common_main D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7186F9320 mainCRTStartup D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThreads:\nThread : 00002514\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e60\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002ab8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e20\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000026a0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002404\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002234\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000ddc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000305c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002640\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ec4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002130\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ff0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000002f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000e8c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001b88\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001f10\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000132c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE58561C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFE582EF73C Symbols not available\n\n\nThread : 000000c0\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFEA2020350 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE58597770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE58597770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002298\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE58561C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001e98\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002b4c\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002278\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000014f8\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFE8DD7458B Symbols not available\n\n\nLoaded Modules :\n0x00007FF712C80000 3.4.0.0 blender.exe F:\\Blender_build\\first\\ninja_lite_debug\\source\\creator\\Debug\\blender_private.pdb \n0x00007FFEA4250000 10.0.19041.2130 ntdll.dll \n0x00007FFEA2540000 10.0.19041.1889 KERNEL32.DLL \n0x00007FFEA1FD0000 10.0.19041.2130 KERNELBASE.dll \n0x00007FFEA3550000 10.0.19041.2130 USER32.dll \n0x00007FFEA1B50000 10.0.19041.2130 win32u.dll \n0x00007FFEA2600000 10.0.19041.2130 GDI32.dll \n0x00007FFEA1CC0000 10.0.19041.2130 gdi32full.dll \n0x00007FFEA19B0000 10.0.19041.789 msvcp_win.dll \n0x00007FFEA1A50000 10.0.19041.789 ucrtbase.dll \n0x00007FFEA2630000 10.0.19041.2075 SHELL32.dll \n0x00007FFEA30A0000 10.0.19041.2130 ADVAPI32.dll \n0x00007FFEA34B0000 7.0.19041.546 msvcrt.dll \n0x00007FFEA3790000 10.0.19041.1865 sechost.dll \n0x00007FFEA38B0000 10.0.19041.1806 RPCRT4.dll \n0x00007FFEA2410000 10.0.19041.1202 ole32.dll \n0x00007FFEA39E0000 10.0.19041.2130 combase.dll \n0x00007FFEA22B0000 10.0.19041.2075 SHLWAPI.dll \n0x00007FFEA3270000 10.0.19041.1865 shcore.dll \n0x00007FFE83ED0000 14.32.31332.0 MSVCP140D.dll \n0x00007FFE8C790000 14.32.31332.0 VCRUNTIME140D.dll \n0x00007FFE9CEF0000 14.32.31332.0 VCRUNTIME140_1D.dll \n0x00007FFE7F6C0000 10.0.19041.685 ucrtbased.dll \n0x00007FFE844B0000 6.10.19041.1110 COMCTL32.dll \n0x00007FFE9C5E0000 10.0.19041.546 VERSION.dll \n0x00007FFE9B860000 10.0.19041.867 dbghelp.dll \n0x00007FFE9F730000 10.0.19041.746 dwmapi.dll \n0x00007FFE8C310000 tbb_debug.dll \n0x00007FFE7EC20000 epoxy-0.dll \n0x00007FFE67340000 3.10.8150.1013 python310_d.dll \n0x00007FFEA2F50000 10.0.19041.546 WS2_32.dll \n0x00007FFE98DC0000 14.32.31332.0 VCRUNTIME140.dll \n0x00007FFEA2310000 10.0.19041.546 IMM32.DLL \n0x00007FFE9FA40000 10.0.19041.2130 windows.storage.dll \n0x00007FFEA12E0000 10.0.19041.2075 Wldp.dll \n0x00007FFEA18A0000 10.0.19041.844 profapi.dll \n0x00007FFE9F460000 10.0.19041.2130 uxtheme.dll \n0x00007FFE9F840000 10.0.19041.546 kernel.appcore.dll \n0x00007FFEA1C30000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFE8B530000 tbbmalloc_debug.dll \n0x00007FFEA3150000 10.0.19041.2075 MSCTF.dll \n0x00007FFEA2FC0000 10.0.19041.985 OLEAUT32.dll \n0x00007FFE824C0000 10.0.19041.2075 OPENGL32.DLL \n0x00007FFE8C420000 10.0.19041.2075 GLU32.dll \n0x00007FFEA3400000 2001.12.10941.16384 clbcatq.dll \n0x00007FFE9ADF0000 10.0.19041.2075 AppXDeploymentClient.dll \n0x00007FFE57830000 30.0.14.9649 nvoglv64.dll \n0x00007FFEA3D40000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFEA1960000 10.0.19041.1620 cfgmgr32.dll \n0x00007FFEA1FA0000 10.0.19041.1023 bcrypt.dll \n0x00007FFE9D780000 10.0.19041.546 WTSAPI32.dll \n0x00007FFEA1250000 10.0.19041.546 CRYPTBASE.DLL \n0x00007FFEA1470000 10.0.19041.546 msasn1.dll \n0x00007FFE9C570000 10.0.19041.906 cryptnet.dll \n0x00007FFEA1DD0000 10.0.19041.1889 CRYPT32.dll \n0x00007FFE9AEF0000 10.0.19041.1949 drvstore.dll \n0x00007FFEA1650000 10.0.19041.1620 devobj.dll \n0x00007FFEA1F30000 10.0.19041.2075 WINTRUST.dll \n0x00007FFEA0AA0000 10.0.19041.546 ntmarta.dll \n0x00007FFE93710000 10.0.19041.546 dxcore.dll \n0x00007FFEA17D0000 10.0.19041.546 powrprof.dll \n0x00007FFEA17B0000 UMPDC.dll \n0x00007FFEA1740000 10.0.19041.2075 WINSTA.dll \n0x00007FFE87CC0000 10.0.19041.1387 dataexchange.dll \n0x00007FFE9D990000 10.0.19041.2075 d3d11.dll \n0x00007FFE9E1C0000 10.0.19041.2075 dcomp.dll \n0x00007FFEA0340000 10.0.19041.2075 dxgi.dll \n0x00007FFE94780000 10.0.19041.1865 twinapi.appcore.dll \n0x00007FFE93EB0000 10.0.19041.2075 textinputframework.dll \n0x00007FFE9ED10000 10.0.19041.746 CoreMessaging.dll \n0x00007FFE9EF10000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFE9E060000 10.0.19041.2130 wintypes.dll \n0x00007FFE7E100000 10.0.19041.1949 explorerframe.dll \n0x00007FFE8DD60000 10.0.19041.1566 directmanipulation.dll \n0x00007FFEA1230000 10.0.19041.546 CRYPTSP.dll \n0x00007FFEA0960000 10.0.19041.1052 rsaenh.dll \n\n# Python backtrace\n```\n\n```lines=10\n# Blender 3.4.0, Commit date: 2022-10-20 00:36, Hash 3915f5300ad2\nbpy.context.space_data.context = 'MATERIAL' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF6E6FDF4EA\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x00000000000001A1\n\n\nStack trace:\nblender.exe :0x00007FF6E6FDF4C0 nodeRemLink\nblender.exe :0x00007FF6E80A8DA0 blender::ed::space_node::node_socket_add_replace\nblender.exe :0x00007FF6E80A9980 blender::ed::space_node::ui_node_link\nblender.exe :0x00007FF6E7EBCF50 ui_apply_but_funcs_after\nblender.exe :0x00007FF6E7EC87F0 ui_handler_region_menu\nblender.exe :0x00007FF6E7495810 wm_handlers_do_intern\nblender.exe :0x00007FF6E7494C40 wm_handlers_do\nblender.exe :0x00007FF6E749B1B0 wm_event_do_handlers\nblender.exe :0x00007FF6E7480BC0 WM_main\nblender.exe :0x00007FF6E65512F0 main\nblender.exe :0x00007FF6EC6F4380 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThreads:\nThread : 000032c8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000778\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000015a8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000018f0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000f34\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000265c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000458\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000fdc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000198c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000026e4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001088\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001234\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001aac\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002a14\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002228\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000030f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000c60\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002248\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00003084\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ff0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e60\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002514\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000b84\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000005dc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE4F811C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFE4F59F73C Symbols not available\n\n\nThread : 00002fec\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFEA2020350 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE4F847770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE4F847770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001754\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE4F811C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000e54\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000029ac\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002474\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFE8DD7458B Symbols not available\n\n\nThread : 000007a4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002ed4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022dc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001410\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000154c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002bf4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000f78\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000031e0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF6E63E0000 3.4.0.0 blender.exe F:\\Диск I\\programm\\blenders\\свежак 24-14-9-11\\b \n0x00007FFEA4250000 10.0.19041.2130 ntdll.dll \n0x00007FFEA2540000 10.0.19041.1889 KERNEL32.DLL \n0x00007FFEA1FD0000 10.0.19041.2130 KERNELBASE.dll \n0x00007FFEA2F50000 10.0.19041.546 WS2_32.dll \n0x00007FFEA38B0000 10.0.19041.1806 RPCRT4.dll \n0x00007FFE98DA0000 tbbmalloc.dll \n0x00007FFE988A0000 tbb.dll \n0x00007FFEA3550000 10.0.19041.2130 USER32.dll \n0x00007FFEA1B50000 10.0.19041.2130 win32u.dll \n0x00007FFEA2600000 10.0.19041.2130 GDI32.dll \n0x00007FFEA1CC0000 10.0.19041.2130 gdi32full.dll \n0x00007FFEA19B0000 10.0.19041.789 msvcp_win.dll \n0x00007FFEA1A50000 10.0.19041.789 ucrtbase.dll \n0x00007FFEA30A0000 10.0.19041.2130 ADVAPI32.dll \n0x00007FFE8C700000 14.29.30139.0 MSVCP140.dll \n0x00007FFE999F0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFEA34B0000 7.0.19041.546 msvcrt.dll \n0x00007FFE9A080000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFEA3790000 10.0.19041.1865 sechost.dll \n0x00007FFEA2630000 10.0.19041.2075 SHELL32.dll \n0x00007FFEA22B0000 10.0.19041.2075 SHLWAPI.dll \n0x00007FFEA1960000 10.0.19041.1620 CFGMGR32.dll \n0x00007FFE9B860000 10.0.19041.867 dbghelp.dll \n0x00007FFEA1FA0000 10.0.19041.1023 bcrypt.dll \n0x00007FFE68390000 5.7.0.7 sycl.dll \n0x00007FFEA2410000 10.0.19041.1202 ole32.dll \n0x00007FFEA39E0000 10.0.19041.2130 combase.dll \n0x00007FFEA3780000 10.0.19041.546 PSAPI.DLL \n0x00007FFE81390000 epoxy-0.dll \n0x00007FFEA3270000 10.0.19041.1865 shcore.dll \n0x00007FFE556F0000 cycles_kernel_oneapi.dll \n0x00007FFEA2310000 10.0.19041.546 IMM32.dll \n0x00007FFE53FA0000 9.0.0.0 openvdb.dll \n0x00007FFE67640000 59.16.100.0 avformat-59.dll \n0x00007FFE51AA0000 59.18.100.0 avcodec-59.dll \n0x00007FFE944D0000 59.4.100.0 avdevice-59.dll \n0x00007FFE7EBF0000 57.17.100.0 avutil-57.dll \n0x00007FFEA2FC0000 10.0.19041.985 OLEAUT32.dll \n0x00007FFE8C5C0000 6.4.100.0 swscale-6.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFE83E80000 1.21.1.0 OpenAL32.dll \n0x00007FFE82490000 2.0.20.0 SDL2.dll \n0x00007FFE99D20000 libgmpxx.dll \n0x00007FFEA3D40000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFE67170000 3.10.2150.1013 python310.dll \n0x00007FFE99A30000 tbbmalloc_proxy.dll \n0x00007FFE942E0000 10.0.19041.1 AVIFIL32.dll \n0x00007FFE844B0000 6.10.19041.1110 COMCTL32.dll \n0x00007FFE9C5E0000 10.0.19041.546 VERSION.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFE9F730000 10.0.19041.746 dwmapi.dll \n0x00007FFE92F80000 10.0.19041.546 Secur32.dll \n0x00007FFE8C530000 4.3.100.0 swresample-4.dll \n0x00007FFE98880000 10.0.19041.1 AVICAP32.dll \n0x00007FFE936E0000 10.0.19041.546 WINMM.dll \n0x00007FFE9CED0000 10.0.19041.1 MSACM32.dll \n0x00007FFE8C420000 10.0.19041.1 MSVFW32.dll \n0x00007FFE96EB0000 10.0.19041.1 winmmbase.dll \n0x00007FFEA1820000 10.0.19041.2130 SSPICLI.DLL \n0x00007FFE9F840000 10.0.19041.546 kernel.appcore.dll \n0x00007FFE9FA40000 10.0.19041.2130 windows.storage.dll \n0x00007FFEA12E0000 10.0.19041.2075 Wldp.dll \n0x00007FFE9F460000 10.0.19041.2130 uxtheme.dll \n0x00007FFEA1C30000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFEA18A0000 10.0.19041.844 profapi.dll \n0x00007FFEA3400000 2001.12.10941.16384 clbcatq.dll \n0x00007FFE9CFC0000 10.0.19041.1503 MMDevApi.dll \n0x00007FFEA1650000 10.0.19041.1620 DEVOBJ.dll \n0x00007FFE9D0C0000 10.0.19041.1865 AUDIOSES.DLL \n0x00007FFEA17D0000 10.0.19041.546 powrprof.dll \n0x00007FFEA17B0000 UMPDC.dll \n0x00007FFEA3150000 10.0.19041.2075 MSCTF.dll \n0x00007FFE80380000 10.0.19041.2075 OPENGL32.DLL \n0x00007FFE8B550000 10.0.19041.2075 GLU32.dll \n0x00007FFE9ADF0000 10.0.19041.2075 AppXDeploymentClient.dll \n0x00007FFE4EAE0000 30.0.14.9649 nvoglv64.dll \n0x00007FFE9D780000 10.0.19041.546 WTSAPI32.dll \n0x00007FFEA1250000 10.0.19041.546 CRYPTBASE.DLL \n0x00007FFEA1470000 10.0.19041.546 msasn1.dll \n0x00007FFE9C570000 10.0.19041.906 cryptnet.dll \n0x00007FFEA1DD0000 10.0.19041.1889 CRYPT32.dll \n0x00007FFE9AEF0000 10.0.19041.1949 drvstore.dll \n0x00007FFEA1F30000 10.0.19041.2075 WINTRUST.dll \n0x00007FFEA0AA0000 10.0.19041.546 ntmarta.dll \n0x00007FFE93710000 10.0.19041.546 dxcore.dll \n0x00007FFEA1740000 10.0.19041.2075 WINSTA.dll \n0x00007FFE87CC0000 10.0.19041.1387 dataexchange.dll \n0x00007FFE9D990000 10.0.19041.2075 d3d11.dll \n0x00007FFE9E1C0000 10.0.19041.2075 dcomp.dll \n0x00007FFEA0340000 10.0.19041.2075 dxgi.dll \n0x00007FFE94780000 10.0.19041.1865 twinapi.appcore.dll \n0x00007FFE93EB0000 10.0.19041.2075 textinputframework.dll \n0x00007FFE9EF10000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFE9ED10000 10.0.19041.746 CoreMessaging.dll \n0x00007FFE9E060000 10.0.19041.2130 wintypes.dll \n0x00007FFE7E100000 10.0.19041.1949 explorerframe.dll \n0x00007FFE8DD60000 10.0.19041.1566 directmanipulation.dll \n0x00007FFEA1230000 10.0.19041.546 CRYPTSP.dll \n0x00007FFEA0960000 10.0.19041.1052 rsaenh.dll \n0x00007FFE66EB0000 30.0.14.9649 nvcuda.dll \n0x00007FFE4D460000 30.0.14.9649 nvcuda64.dll \n0x00007FFE788A0000 30.0.14.9649 nvapi64.dll \n\n# Python backtrace\n\n```\n\nBlenders: 3.4, 3.2, 3.0, 2.9, 2.83\n```lines=10\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-14-8-11\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.4\\config\\userpref.blend\nWarning: File written by newer Blender binary (304.3), expect loss of data!\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFE8C723020\nModule : MSVCP140.dll\nThread : 0000207c\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-12-1\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.2\\config\\userpref.blend\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF73481F663\nModule : blender.exe\nThread : 000029c0\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-9-10\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\config\\userpref.blend\nERROR (bke.node): C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\blenkernel\\intern\\node.cc:2222 nodeAddStaticNode: static node type 200 undefined\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7A47ABC94\nModule : blender.exe\nThread : 00000674\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 22-14\\blender.exe\"\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF776C49221\nModule : blender.exe\nThread : 00000cc0\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 20-6\\blender.exe\"\nfound bundled python: F:\\╨Ф╨╕╤Б╨║ I\\programm\\blenders\\╤Б╨▓╨╡╨╢╨░╨║ 20-6\\2.83\\python\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6508070ED\nModule : F:\\─шёъ I\\programm\\blenders\\ётхцръ 20-6\\blender.exe\n```\n\n1: Open blender to the default startup file.\n2: Go to the materials tab.\n3: Click on the button next to \"Surface\" labeled \"Principled BSDF\" and select a different node to switch it out.\n4: Press Ctrl + Z on the keyboard to undo the previous action.\n5: Repeat steps 3 and 4 with various nodes until it crashes.\n(There used to be a more consistent way of replicating this, making a mix shader, putting a glossy bsdf node in the top slot, then pressing undo and selecting an emission node instead, but it stopped crashing with that just before I sent this.\n. . . And it just started crashing with that again. I'm sorry I can't give you something more consistent.)\n\nBased on the default startup file.\n", "Edge quality of uv export\nWindows 10\nGtx 1060\n\nBlender 2.8 - February 28 ( d7d180bd3d8d )\n\ndifference looks huge between blender 2.79 and blender 2.8\n\nPlease note: check image in full view.\n\n\n\n\n\nthanks.", "Realtime Compositor - Crash on Mac when using Map UV node\nOperating system: macOS Ventura 13.3.1\nGraphics card: AMD Radeon Pro 5700 XT 16GB\n\nBroken: 3.6 alpha cef128e68af5 (2023-04-13 16:06)\n\nConnecting a Map UV node in Compositing will crash on macOS\n\nIn Blender's startup scene, enable Compositing by checking \"Use Nodes\".\nConnect a Map UV node between the Render Layers node and the Composite node.\nIn a 3D view, turn on Rendered viewport and set Viewport Compositing to Always.\nThis will crash (100% reproducible).\n\nPlease contact summary if more information is required.\n\n", "Blender 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)", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "Crash when rending animation w/simple physics sim\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: Spinning beach ball in 3.1 Alpha\n\nWhen selecting \"Render Animation\", the Rendering window starts to draw, and then the app crashes.\n\n\nFile attached. Just load and Select Render Animation.[simple-physics-crash.blend](simple-physics-crash.blend)\n\n", "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", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Crash after undo \"Mask slice to new object\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\nWorked: This problem happens to me with 2.92, the pc that I use now I formatted it, unfortunately before I used version 2.82\n\nMy problem is that when I use the option \"mask slice to new object\" and then I use ctrl + Z the blender closes !! I formatted the PC a few weeks ago, unfortunately I didn't use version 2.92 before. What I realized is that when I use the \"mask slice to new object\" option and then go to edit mode, I can use control + Z without any problem, that is, it does not close.]\n\nThis happens to me in any file:\n\n1. Sculpture mode.\n2.Use the \"mask\" or \"box mask\" brushes\n3. I paint the mask.\n4.I go to the \"MASK\" menu.\n5. I click on \"mask slice to new object\".\n6. Press CTRL + Z.\n7. Blender closes.\n", "Crash/Bugs with material's Surface dropdown + undo\nOperating system: Linux-4.15.0-45-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 4)\nAlso confirmed to crash in 2.80.\nWorked: 2.79b does not crash (works as expected)\n\nWhen changing the surface/volume in material properties (the list view of the shader nodetree) and undo, opening the dropdown directly afterwards again can crash Blender.\n\n- Download repro blend file (it's just a Cube with a Principled BSDF) [shaderlistRepro.blend](shaderlistRepro.blend)\n- In Properties Editor, click on Surface (Principled BSDF) and select any option in the dropdown\n- Move your mouse over the Surface dropdown and keep it there!\n- Press CTRL+Z to undo\n- Click on the Surface (Principled BSDF) dropdown again (your mouse may not leave the dropdown box)\n- Blender crashes\n\nThe same happens when done with the Volume dropdown instead.\n\n[2020-02-24 15-09-16.mp4](2020-02-24_15-09-16.mp4)\n\n**Possibly related issue**\nIn another file, doing the exact same steps as above has some other effects:\n- Either it spawns this popup (clicking any of these options crashes Blender) \n- Or it spawns a blank popup \nThis is the reproduction file which caused this: [shaderlistRepro2.blend](shaderlistRepro2.blend)\n\nWhich effect happens is really inconsistent and I am not sure how to reproduce one or the other.", "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)" ]

[ "Blender 2.8 - Crash by Eevee Material Button\nOperating system: Win7 64Bit Pro\nGraphics card: Nvidea Geforce\n\n2.80, b4dfae3df7b9, may 20 - 2019)\n\n\nShort description: Open Blender with Eevee Render Engine. Click Material Button and Blender Crashs.\n\nExact steps: Open Blender with Eevee Render Engine. No further steps are required. Just Click Material-Button and Blender Crashs. No more, no less.\n\nThanks for Blender Dudes!\n\n\nPersonal note: At the moment you get the impression that the team is more concerned with moving menus and buttons than with... (see Outliner Mark button, Visibility, Move Prefencies in the Menus etc.)", "The program being crashed after clicking on the \"Material\" tag\nOperating system: windows 8.1\nGraphics card: NVIDIA Geforce 820M\n\nBroken: 2.80, 9efe117535c6, master, 2019-05-21, as found on the splash screen\nWorked: (optional)\n\nWhen I click on the \"Material\" tag, the program automatically shuts down without showing any notifications\n\nStep 1: Start the program\nStep 2: Click on the \"Material\" tag\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Material tab crash with Intel HD 4x00 on Windows 7/8\nOperating system: Windows 8.1\nGraphics card: Intel(R) HD GraphicsFamily (driver up to date), Visual C++ 2013 Redistributable Package installed\n\nBroken: (2.8, downloaded April 26 from , 513b71c89ad0\nWorked: 2.79, stable version and former versions\n\nI doubleclick blender.exe, it opens okay and when I go to the material tab of the initial cube of the default startup - Blender disappears\n\n\nHow can I run --debug-gpu in the terminal if this could be the solution as mentioned in \n#55787 ?", "Eevee render crash with Intel HD 4400 and Windows 8\nOperating system: Windows 8.1\nGraphics card: Intel HD Graphics\nLaptop: Lenovo Yoga 2 Pro 13 inc\n\nBroken: version: 2.80 (sub 60), branch: blender2.7, commit date: 2019-05-03 21:09, hash: ee0d8426ab6d, type: Release\nbuild date: 03/05/2019, 18:12\nplatform: Windows\n\nWhen I click the render image or render animation, it crashes(It usually crashes when working Evee Render Engine)\n Sometimes while I am working on 3d, it crashes also..\n\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)" ]

[ "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", "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", "Crazy-space support for meshes in geometry nodes\nIn [D15407](D15407) crazy-space support for curves is added to geometry nodes. Currently, meshes use a different system for crazy-space that is not really compatible with nodes as is.\n\nIt should be possible to use the approach implemented for curves for meshes as well, but that needs to be investigated further.", "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", "Ngon with more edge crash blender when using Multires/Subdivision Modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha, 2.93.2, \nWorked: None\n\nPlease check the video, it shows the difference when blender deal will small ngon(edge < 10) and large ngon (~=600).\nI think it should take over aleast 5000 points ngon(for some svg file)\n[2021-08-15 17-50-41.mp4](2021-08-15_17-50-41.mp4)\n\nCreat a ngon with more than 600 points\nextrude it and add Subdivision Modifier\ncrash\n[test.blend](test.blend)\n", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "Blender becomes unstable/crashes after using \"Reload Scripts\" if using any \"ShaderNodeCustomGroup\" nodes.\nOperating system: Windows 10\nGraphics card: NVIDIA\n\nBroken: 2.81\n\nIf you manipulate a \"ShaderNodeCustomGroup\" node after having used the \"Reload Scripts\" operator (F8) Blender will become unstable.\n\nAttached is a small addon that implements a minimal custom node group.\n1. Enable the addon and switch to the shader editor.\n2. Create the custom node (Add->Test Category->TestNodeCustomGroup)\n3. Trigger 'Reload Scripts' (F8 key).\n4. Adjust the color input of the custom node.\n5. Repeat steps 3/4 until you crash (usually crashes on first or second try for me)\n[node_custom_test.py](node_custom_test.py)", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Crash with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "Blender 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", "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", "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", "Regression: Changes in curve normal behavior\nBroken: 3.0\nWorked: 2.92\n\nInstead of a simple arrow, the scene is something very remotely in the neighbourhood of that shape plus random extruded edges. \n\nOpen example file.\n\n", "Outliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.5, 2.90, 2.91 ce0bcd5fb\nWorked: Never (2.79 has the same problem)\n\nOutliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\n\n[T79961_repro.blend](T79961_repro.blend)\n- Open file\n- Cube should be in editmode\n- In the Outliner (should be in Data API mode):\n - navigate to Meshes > Cube > Skin Vertices > expand the dot as well\n - crash" ]

[ "Blender 2.8 crash - convert to curve from mesh under all conditions\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15031.1000\n\n\nBroken: version: 2.80 (sub 73)\nWorked: (optional)\n\n\nBlender 2.8 crash - convert to curve from mesh under all conditions.\n\nToday I created a completely new and clean Blender installation with today's build. If I want to convert a simple mesh (circle, rectangle, ...) to a curve, Blender loads for one to two seconds and crashes, I've tested it under all kinds of conditions. Converting a mesh from a curve is no problem.\n\nWith the installation before (4-5 days old) it was no problem. Of course I deleted all temp and config folders for the new installation - so it is 100% clean.\n\n[curve-from-mesh.blend](curve-from-mesh.blend)\n\nThanks for all your hard work!\n\n\n**One-line way to reproduce the issue**\n$ `./blender -b --python-expr \"import bpy; bpy.ops.mesh.primitive_plane_add();bpy.ops.object.convert(target='CURVE')\"`\n", "Crash on Convert to Curve from Mesh/Text\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 950/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.01\n\n\nBroken: \nversion: 2.80 (sub 73)\nversion: 2.80 (sub 72)\n\n\nCrash on using Convert to Curve from Mesh/Text operator.\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF732C40208\n\n1. Add Bezier Curve to scene\n2. Use \"Curve to Mesh\"\n3. Use \"Curve from Mesh/Text\"\n\n" ]

[ "Crash when adding materials\nOperating system: Linux-5.18.9-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 630 (CFL GT2) Intel 4.6 (Core Profile) Mesa 22.1.3\n\nBroken: version: 3.2.0\n\nBlender crashes when adding a second material (sometimes you need to add some more to crash it)\n\n1. Open the appended .blend file.\n2. Select the object.\n3. Go to material tab.\n4. Try to add a second material.\n\n[crash.blend](crash.blend)", "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 crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "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", "Geo Nodes crash, when updating old node group with new (using user_remap()) \nOperating system: Linux-5.15.21-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.1.0 Beta\nWorked: I think it always crashed\n\nLets say I have two geo nodes: **old_node** group and **new_node** group. I want to update old to new using python:\n\n```\nold_ng.user_remap(new_ng)\n```\n\n\nBlender will crash after running code above, if scene has Cube object with geonodes modifier that uses **old_ng**. Crash happens only if modifiers tab is visible, and you re-select the cube. It wont crash, if new nodegroup does not have additional input.\n\n1. Run script from attached blend file ( it remaps old_ng to new_ng) \n2. re-select 'CubeOld' object. Blender will crash\n\n [gn_update_crash.blend](gn_update_crash.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", "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", "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "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 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", "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)", "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)", "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)", "Error message and unable to edit a skeleton when using a library override armature\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: No idea.\n\nBlender generates an error when you attempt to enter edit mode on a library overriden armature. There's no description of what the error is or if there is some extra step to make it work. Hopefully this isn't one of those, \"works as intended issues,\" because then there's no way to make multiple characters share an updateable base rig.\n\n\n- Add an armature, enter edit mode, extrude out a few bones.\n- Save the file and open a new scene.\n- Link in the armature you just created.\n- Make the armature a library override.\n- Try to enter edit mode. Should get an error.\n\n", "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" ]

[ "If object is reference for 2 shrinkwraps, entering it`s edit mode crashes Blender.\nBisecting points to 0945a79ed1\n\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\nWorked: blender-2.90.0-ab8a6914317f-windows64.zip\n\nCreate a file using the steps shown below or download the .blend file. Select the sphere and enter edit mode and Blender should crash. You may need to enter edit mode a few times for this bug to occur.\n[2020-06-26_05-29-42.mp4](2020-06-26_05-29-42.mp4)\n[untitled1.blend](untitled1.blend)\n\n**Original steps:**\nThere is two shrinkwraps on two fingers. And if both enabled in viewport, I have crash, when I try to enter edit mode for hand.\nYes, tested with factory settings too, the same.\n[untitled.blend](untitled.blend)\n[2020-06-26_05-12-19.mp4](2020-06-26_05-12-19.mp4)" ]

[ "Wrong particle tool properties displayed when using Select or Cursor tools\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 640 Intel Inc. 4.1 INTEL-12.4.7\n\nBroken: version: 2.80 (sub 50)\n\nIn Particle Edit mode, when using the Cursor or Select tools, you can still see particle tool properties for the brushes.\n\n\nOpen this blend file:\n[particle_toolprops_bug.blend](particle_toolprops_bug.blend)\n\nIf you select the Comb tool, you just see the Comb tool properties;\n\n\nBut, if you select the Box Select or Cursor tool, the comb tool properties aren't cleared, and you see settings for both at the same time.\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", "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\n\n", "System Hangs while Interacting with the Viewport\nOperating system: Manjaro KDE Plasma\nGraphics card: Intel HD Graphics (Cherry Trail) Atom X7-Z8700\n\nBroken: 3.5.0, 3.4.0, 3.4.1\nWorked: 3.3.2 (Haven't tried newer versions in the 3.3.x series)\n\nBlender causes the entire system to hang periodically while performing any task. Simply rotating the camera or zooming in or out results in the system freezing for minutes at a time. The mouse cursor responds to mouse and touchpad movement, but the system does not respond to mouse button clicks or keyboard input for long periods of time. Neither Blender nor the desktop respond.\n\nWhen rotating, moving or zooming the camera text overlays in the viewport flicker, sometimes the entire viewport flickers, then the system hangs. There are no errors or warnings printed to the terminal\n\nDoesn't appear to be related to a specific file. The issue is present in all blend files and when starting with the default setup.\n\n", "Region Overlap does not work on VSE editors\nOperating system:\t\tWindows 7\nGPU:\t\t\t\tRadeon Vega 64\nGPU Software Version:\t20.4.2 (2020.0515.1537.28108)\nCPU:\t\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t\t`2.79 (sub 00), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b, type: Release, build date: 2018-03-22, 09:59 AM`\nBroken:\t\t\t\t` 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: Release, build date: 2019-07-29, 09:44 AM`\nBroken:\t\t\t\t` 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42e3, type: Release, build date: 2019-11-20, 16:33:00`\nBroken:\t\t\t\t` 2.82 (sub 07), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd76f, type: Release, build date: 2020-02-13, 01:56:46`\nBroken:\t\t\t\t` 2.83.3 LTS, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd7493e, type: Release, build date: 2020-07-22, 04:04:56`\nBroken:\t\t\t\t` blender-2.90.0-4f59e4bddcb0-windows64` (BF Build Bot)\nBroken:\t\t\t\t` blender-2.91.0-21fec9513969-windows64` (BF Build Bot)\n\n\n|  |  |\n| -- | -- |\n\n\n[No Overlap.blend](No_Overlap.blend)", "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", "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", "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", "Loop Cut at Point\nHere it would be a nice improvement to make it so you can create cuts anywhere along a loop, not just in the center. This would be a tool setting.\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", " 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)", "Unable to select certain vertices (regression from 2.79)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nSome vertices are impossible to select.\n\nAt first I thought it was because the vertices formed a concave area (see first file) but then I hit a second concave case (see second file).\n\n\nWithout rotating or zooming the view try to select one of the marked vertices in both files.\n[Select1.blend](Select1.blend)\n[Select2.blend](Select2.blend)\n\n----\n\n2.79 worked in this case, open this file in 2.79 to test.\n\n[Select1(1)_279.blend](Select1_1__279.blend)", "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", "Applying Skin Modifier to square loop object and in edit mode braking the loop makes prob\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: AMD Radeon HD 8400 / R3 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1065.0\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nSkin modifier disturbs the geometry form one corner on braking the loop form one corner of closed loop (of square shape). Although in this case the angles are 90% but it's will make prob...\n\n\n\n\n", "Show error messages in the info editor\nFollowup task to #83237" ]

[ "loop cut tool\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.0\n\nHaving trouble with adding multiple edges using the loop cut tool\n\nusing ctrl+R to insert loop cut after rotation on the mouse wheel loop cut won't increase instead its zooms in and zooms out. \n\n" ]

[ "Sculpt mode. Switching back to tool with brushes from tool without brushes rolls to next brush.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken 2.83.*, 2.91,\nBroken: version: 2.92.0 Alpha\n\nSculpt mode\nCreate 2 grab brushes 1 and 2, that can be switched with G\nSelect Grab 1\nSwitch to mesh filter.\nPress G.\nNow you switched to Grab2 instead Grab1, that was selected before.\nExpected: return to same brush, that was selected before.\n\nIssue appears with:\nLine project, [Box] mask, Box hide, [Box] faceset, [Box] trim, Mesh/Cloth/Color filters, Mask by color, Edit faceset, all transform tools, annotation.\nAffects all tools, who can have few brushes.\nTested with factory startup too.\n\n[2020-12-10_03-13-39.mp4](2020-12-10_03-13-39.mp4)\n[grabroll.blend](grabroll.blend)", "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", "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)", "Sculpt Mode - Using Mask while Multiress active = Crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.2\n```\n Tried also with\n```\n 2.83LTS\n 2.92beta 77f73a928439\n 2.93.0 ae1e68f5146d\n\nWorked: None\n\nWas working in Sculpt mode, tried to hide the arms and the program crashed.\nI tried with another objects with multires and it doesn't happen\n\nHere the .Blend with the problem\n [Multires prueba.blend](Multires_prueba.blend)\n\nGo to Sculpt Mode -> Try to mask with mask brush, Mask Lasso or Mask Box", "Repeat Last does not work after undo\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0\nWorked: never?\n\nSomething I stumble upon every now and then is that 'Repeat Last' (default hotkey: Shift-R) does not work after an undo call.\nThis is especially annoying if you call undo after 'Repeat Last' - which in turn makes blender forget what the last operation was.\n\nI run into this regularily while doing UV's, so lets say I have called 'align auto' and then select some new uvs - then do 'Repeat Last' and keep doing this for a bit, but at some point I will make a wrong selection and hit shift-r and undo.. now I have to first understand why Shift-R is not working anymore and then search for whatever operation I was doing, this hurts the workflow fluidity quite a bit.\n\nI know the undo area is tricky corner in the blender codebase, so I suspect some technical difficulties will make this not so easy to pull off .. or is the reason why its not working in the first place.\n\nDid a quick search here on phab but could not find an open task for this - let's ignore some tasks from 2011 ;) - so I though I just do a small post about it here.\n\n\n- Open default scene\n- Move the cube\n- {nav Edit -> Repeat last} or `Shift + R` (Works)\n- Undo \n- Perform `Repeat last` again (nothing happens)\n\nAnyways thanks for your time :) \n", "Sculpt Mode: Wrong Transform pivot point when set to 3D Cursor\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nWrong Transform pivot point in sculpt mode.\nIf you set transform pivot point to 3d cursor and perform a rotation after it won't take orientation pivot into account. Only works on the second input. See the videos for details.\n\n - enter sculpt mode\n - enable symmetry\n - set pivot to 3d cursor \n - enable transform tool\n - mask part of the mesh\n - set pivot\n - perform rotation\n - perform second rotation\n[Blender 2023-01-27 12-14-10.mp4](Blender_2023-01-27_12-14-10.mp4)", "Assign Shortcut Missing when Right Clicking Undo History.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.1.2\nWorked: Blender 3.0 Unsure of exact version I had installed but I was not on 3.1.\nChanged in 0e1bb232e6\n\nUnable to assign shortcut to Undo History using Right Click Menu. \n\nRight Click Menu only shows \"Assign to Quick Favorites\"\n\nUsing default startup file, Edit > Right Click Undo History \n\n\nI recently had my OS SSD fail and had to reinstall Windows as well as all my applications fresh. Going through my setup of a new install of Blender 3.1.2 I wanted to reassign my previous shortcut for the Undo History Menu (Ctrl + Alt + Z) but was unable to view the Assign Shortcut option when right clicking. \n\n\n\nUndo History was also missing from the \"Blender\" Keymap when searching. \n\n\n\nTo resolve this, I switched to the Blender 2.7X Keymap which did have the Undo History shortcut, copied the shortcut \"ed.undo_history\" and assigned that manually in the default \"Blender\" Keymap. \n\n\n\n", "Sculpt: Paint tool cavity custom curve crash\nOperating system: Windows 10\nGraphics card: NVDIA RTX 2060 Super\n\nBroken: 3.4, 3.5\n\nSteps to reproduce the issue:\n - Switch to Sculpt Mode or open default sculpting template file\n - Choose the Paint Tool\n - Click on Brush dropdown\n - Enable Cavity by clicking on Advanced >> Cavity in the \"Brush\" dropdown\n # Enable Custom Curve under Advanced >> Cavity in the \"Brush\" dropdown\n\n\n\nResult:\nNo **Custom Curve** is shown as in other Sculpting Tools & after trying to paint with the **Paint** tool setup this way blender instantly crashes.", "Sclupt brush goes back to default (draw) when pressing ctrl+z\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.1\nWorked: 2.90.0\n\nSclupt brush goes back to default (to \"draw brush\") when pressing ctrl+z.\n\n1 - Load default startup.\n2 - Select a cube.\n3 - Go to sculpt mode.\n4 - Pick any brush (I recommend \"grab brush\").\n5 - Manipulate the geometry of the cube a few times.\n6 - Press ctrl+z.\n7 - You will see that the brush jumps back to \"Draw brush\" for no reason.\n", "Its possible to create Built-in attributes with wrong metadata\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: version: 4.0.0 Alpha\n\nSee attached stack trace file.\n\n```\nCode marked as unreachable has been executed. Please report this as a bug.\nError found at C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\blenkernel\\intern\\attribute.cc:486 in BKE_id_attribute_remove.\nSaved session recovery to \"C:\\Users\\rfnei\\AppData\\Local\\Temp\\quit.blend\"\n```\n\n1. Create any attribute on mesh.\n2. Rename it to `material_index`.\n3. In debug: try to delite this.\n\n", "Sculpt: Artifact in Multires when mirror modifier is applied\nOperating system: Linux-4.19.97-x86_64-x86_64-AMD_Athlon-tm-_II_X4_620_Processor-with-gentoo-2.6 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 1)\n\nArtifact in Multires when apply mirror\n\n4xYyu0y.png\n\n1. add multires\n2. subdivide 4-5 times\n3. make sculpt\n4. add mirror\n5. apply mirror\nor \n1. Open attached file\n2. apply the mirror modifier\n[multires_mirror_bug.blend](multires_mirror_bug.blend)", "mask animation is not undoable\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4454\n\n\nBroken: tested 2.79, 2.80\nWorked: non\n\n\nmask animation is not undoable\n\ncreate a mask and make an animation keyframe\npress ctl+Z or edit->undo : nothing happens!\n", "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", "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", "Textures not displayed in sculpt mode due to missing UVs (PBVH rendering, Multires)\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\n\nBroken: version: 2.80 (sub 55)\nWorked: 2.79b\n\n\nModel with Multiresolution modifier doesn't display texture in Sculpt Mode.\nRender engine doesn't matter.\n\n \n\n\nObserved in display modes:\n1. Solid (Lighting: Studio / Color: Texture)\n2. LookDev\n3. Rendered (in Cycles mesh is invisible)\n\n- Open [test.blend](test.blend)\n- Enable \"Display modifier in viewport.\"\n\nOR\n\n- Switch to LookDev mode\n- Apply multiresolution modifier to a mesh with texture\n- Add single subdivision (`Sculpt Base Mesh` OFF)\n" ]

[ "Regression: Sculpt mode undo: Broken when undoing to a Global/memfile undo step after rB4c7b1766a7f1\nOperating system: Win 10\n\nBroken: blender-2.92.0-564f3be20a6f-windows64\nCaused by 4c7b1766a7\n\nIn the sculpting template, the Undo (ctrl+z) function doesn't undo the first stroke.\n\n~~However, if you then click \"Redo\" (shift+ctrl+z), it will actually undo the first stroke...~~ *This is a separated issue, see {#82532}*\n\nSame issue cause a slightly different bug when one switch from Object mode to Sculpt mode, draws a stroke, then undo twice: the object does not go back to Object mode as expected.\n\n- File/New/Sculpting\n- Perform a brush stroke\n# Undo (ctrl+z) - It should undo the brush stroke, but nothing happens.\n~~Redo (shift+ctrl+z) - Now it will undo the brush stroke.~~\n\n*OR*\n\n- Default startup file, switch to sculpt mode.\n- Draw a stroke.\n# Undo twice.\n\n-----------\n\n[2020-11-04_04-03-24.mp4](2020-11-04_04-03-24.mp4)\n\n\nEven **not** using the sculpting template, you can still replicate this erratic behavior in sculpt mode, if you load a texture/perform a brush stroke and try to undo... the undo won't work, but the Redo will undo the brush stroke...\n[2020-11-04_16-25-45.mp4](2020-11-04_16-25-45.mp4)" ]

[ "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", "Sculpt brush Reverts to Default When Undoing\nOperating system: Windows-10-10.0.25336-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\nWorked: 2.79\n\n**Description of error**\n\nWhen using a non-default brush such as clay strips, then undoing, the brush switches to the default one (draw brush). Now this is frustrating to the user because you need constantly switch back to your brush after every ctrl + z. Stupid bug that interrupts the workflow.\n\nNow this bug is not limited to sculpt mode, it happens in vertex painting, weight painting, texture painting and hair sculpt mode.\n\nHowever this bug doesn't happen to most users because for it to happen you need to have two main windows.\n\n* Add a new main window (`Window > New Main Window`) and switch the workspace (say \"shading\")\n* In primary main window: switch to sculpt mode\n* Choose clay strips\n* Press ctrl + z\n* Observe the brush is draw brush and not clay strips 😵‍💫\n\nNote: I think this has to do something with workspace since switching them can fix this bug but also crash blender\n\n[video](https://projects.blender.orgattachment)", "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", "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", "[Sculpt Mode] Remesh - Fix Poles problem.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.82 (sub 1)\nBroken: version: 2.81 (sub 16)\n\n\nIf i apply a remesh to an objecto with \"Fix Poles\" activated, this generate extra vertex's, This happen more with extracted objects with \"Mask Extract\" i think, this is very random and i don't have idea if's normal.\n\n\nAdd an sphere >> Apply a remesh to the sphere for more details >> Create a mask for extract >> Extract mask >> to the new object extracted clear the mask >> Apply another remesh with \"Fix Poles\" On >> select the Smooth brush with the strength 1.000 >> Smooth all. \n\nVideo Example 1: [Fix Poles - ON (Problem)](u3xa8YrCcQo)\nVideo Example 2: [Fix Poles - OFF (No problem)](agZ6T4l92lA)\nVideo Example 3: [Test with an sphere](HPw87j2bews)\n\n", "Fractured object crashes Render\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.10.12\n\nBroken: version: 3.4.1\n\nRendering image crashes Blender\n\nThe attached file is the output of a fractured cube using RBDLabs, nothing else. It's a series of 965 simple static meshes. When displaying rendered shading in viewport, all is well. When doing Render > Render Image, then Blender crashes. Happens on my Mac M1 and Mac Intel, on Blender 3.3.4, 3.4.1, 3.5 and 3.6 alpha. If I delete the 115 last cells or the 134 first ones, then the render will properly happen. Thanks !\n\n", "Multires Displacement Smear brush + Dyntopo Error\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.92.0\n\n[When you want to use the multires displacement smear brush with dynamic topology, blender closes.]\n\n\n1. Open Blender\n2. Enter sculpted mode\n3. Select the Multires Displacement Smear brush\n4. Activate Dynamic Topology dyntopo\n5. Pass the brush through the Bucket\n6. Blender closes\n\n[untitled.blend](untitled.blend)\n\n", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "With enabled Modifier On Cage option crashes on entering Edit Mode if in Render Viewport Shading\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nIn Eevee, in Render Viewport Shading, an object having a Geometry Nodes modifier with enabled On Cage Modifier Result, that affects a UV Attribute which is used in Shader, crashes upon entering Edit Mode.\n\n - Set Viewport Shading Mode to Render\n - Enter Edit Mode ->Crash\n[displace-preview.blend](displace-preview.blend)", "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.", "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)", "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", "Multires design validation\nThe goal of this tasks is to validate the design of Multires as Blender’s main subdivision based sculpting system. \n\nIn order to do that, I’m not focusing on the current state of Multires taking into account its current implementation (bugs, missing features, technical debt), but on the design of Multires itself. The idea here is to ask the question “if Multires was working exactly as intended (no bugs, no TODOs, all possible optimizations...), is that what we want for the sculpting/painting modes?”\n\n## Pros\n\n- **Tangent space sculpting layers**: This is a feature that even specialized software doesn’t support and which is really important for retouching VFX animation. By having multiple ##CD_MDISP## datalayer, it should be possible to tweak the influence of each one of them on the final displacement. As these layers are in tangent space, this supports any transformation on the base mesh without applying the layers displacement in random directions. \n\n- **Supports features that require base + displacement**: Features like displacement eraser or displacement smear rely on having the sculpt geometry stored as a base and a displacement. The current Multires design makes supporting these features straightforward. When Multires is not being used, it is still possible to implement these brushes by creating an operator that generates a base (by smoothing the mesh multiple times) and a displacement. So, this is not a feature that relies on the design of Multires, but it makes it better integrated.\n\n- **Sculpting and rendering different levels**: It is possible to use sculpt mode to deform the limit surface and let the modifier evaluate the displacement of other level. With a delete lower operator and unsubdivide, it should be possible to create a temporally base mesh for any level so it can be sculpted as a limit surface.\n\n- **Easy to integrate with rigs**: For the rest of the animation system, multires is just like having a vector displacement texture on top of a model. Animating models with sculpted displacement does not require any further workflow or features from other modules. \n\n- **Saves a lot of memory**: As it does not store any topology information for the higher levels of the sculpt, it is memory efficient both when sculpt mode is in use and when saving the files.\n\n- **Faster PBVH building times**: as the BVH primitives are the grids, building the tree is faster than building it for the individual triangles of a mesh.\n\n\n\n## Cons\n\n- **No references or indices for edges and loops**: Mesh algorithms that require storing information or topology queries based on edges can’t be implemented. This means like features like fairing, geodesic distances or a better cloth solver can’t be directly available from the ##SculptSession## (I still don’t understand why the current cloth solver works, but its performance is really bad). In order to have those features working, I can only think of workarounds like converting the grids to a mesh or adding some kind of map to store the grids topology as edges and vertex references, which adds extra code that needs to be maintained and misses the point of using grids directly to save memory.\n\n- **Computed and displayed resolution does not match**: When working on level 1 of a quad mesh, all vertices will have 4 duplicates which will be deformed independently when computing the brushes and tools. For the user, this means that performance and vertex count won’t match the sculpt mesh that is being rendered. This makes Multires usually slower on level 1 than on level 5. It also creates unexpected results when adding a single subdivision to a mid/high poly mesh, as the vertex count will increase at a rate users won’t expect.\n\n- **Allows vertices with invalid data state**: This design allows to have a vertex with multiple mask, colors or visibility values. This can be solved with stitching the grids, but this should be something that the design should not allow. It is the cause of constant bugs in all tools that require storing data per vertex. (see #79317)\n\n- **Performance depending on grids dimensions**: In lower levels (on a 2x2 grid), the number of duplicates exposed to the tools is so high that creates performance problems. When the grids are too big, performance decreases because the tool iterations are per grid. This causes that multires optimal performance is only achieved in levels around 5. This is something that users don’t expect. For example, subdividing 4 vert plane 8 times will create a reasonable vertex count for sculpting, but because grids at level 8 are so big, sculpt mode will always update at least a quarter of the plane regardless of the size of the brush.\n\n- **PBVH limited to building per grid**: In order to get the PBVH building speed, grids are used as primitives. This means that the number of nodes can’t never be higher than the number of grids. On higher multires levels, this is a problem as the PBVH can’t have as many nodes as it should for optimal performance. \n\n- **Undefined behavior with undo and shape keys**: The relation between shape keys in the base mesh, sculpt layers and multiple ##CD_MDISP## layers is not clear. We don´t know if shape keys should also contain the info about the displacement of the grids, if they should only deform the base mesh or both. What undo should do with features like propagation and reshaping from sculpt mode is also not clear. \n\n- **Incompatible design with automatic apply base**: With the current Multires design it makes total sense to not apply the deformation to the base mesh automatically. The workflow is more similar to painting a displacement texture than to subdivision based sculpting. As it is exposed in the UI as it was a standard subdivision based sculpting system, this often confuses users. As the main use case for having subdivisions in sculpt mode is to be able to control the surface noise, it does not make much sense that level 0 is not directly available for that.\n\n- **Unpredictable displacement interpolation in edit mode**: (To be checked with @JosephEagar ). It looks like it may not be possible to properly implement grid interpolation in edit mode due to numerical stability problems. \n\n- **No support for other custom data layers**: The only datalayer that is supported in Multires is the mask, which is hard coded. Multires does not have any system in place to support editable datalayers in the grids. Mode info in #80609.\n\n- **Depends on editable limit surface**: As the high poly version of the sculpt is stored as displacement on top of the limit surface, any other Blender tool that changes the limit surface will break it without any warning to the user (for example, changing the crease values in Edit mode). See #81958\n\n- **Extremely hard to develop and maintain**: Blender most advanced sculpting tools don’t rely that much on displacing vertices, but more on topology algorithms for calculating transformations (pose, relax, boundary, expand...). Making and debugging these tools to work on grids usually takes 70% of their development time (I measure it when developing the boundary brush). A feature that may require a slightly different topology query (which is often trivial to implement for ##Mesh##) requires an amount of development for Multires that is usually bigger than the tool itself. \n\n- **No friendly workflow with other softwares**: Having surface detail stored as displacement in Multires is convenient to work inside Blender, but what other software expect is to handle surface detail at render time with UDIMS and vector displacement textures (Blender supports both). If you have an animated scene with multires, for exporting it to other software you need to bake all the displacement at its highest resolution per frame, which is not ideal. Even if Multires displacement data can be stored as a separate file, it can’t be read by any other render engine. \n\n\n\n\n## My opinion\n\nThe main technical limitations are about exposing the grids directly to the sculpting code. Because of this, I think that it makes sense for Multires to be used as a different feature. By design, Multires use case is closer to being an alternative to vector displacement for rendering than to a subdivision based sculpting system. To me, it makes sense for Multires to support features like storing displacement into the grids, baking the deformation of modifiers to the grids, reshaping a base mesh based on a displacement, unsubdividing and storing the grids as separate files (it already does all that). What I don’t see any value is in being able to edit the grids displacement directly with the tools. For users, Multires should be exposed in the UI as something similar to baking a vector displacement texture to use in rendering, or “ptex based displacement”. After the fixes and the features added in 2.90, Multires is completely functional for this use case. \n\nI would rather prefer starting discussing the design of a dedicated subdivision based sculpting system and leave Multires for what it does well instead of keep trying to add workarounds a hacks to make it meet the requirements of something that was not designed for. We need to consider that supporting the existing and planned features (like sculpt vertex colors or layers) in the current Multires will take a lot of development time that can be used for something else. \n\nFor Multires, I imagine the workflow to be like:\n- The user creates a subdivision based sculpt with a dedicated subdivision based sculpting system (not Multires).\n- When done, the user adds a Multires modifier to the high poly version and uses rebuild subdivisions. This will convert the sculpt to a base mesh + displacement. It is the same concept as baking a displacement texture from the high poly mesh into level 0, but slightly more convenient as it does not require UVs and geometry will look exactly the same as the sculpt.\n- After having the new low res based mesh, the user can rig and animate the mesh with displacement. ", "Sculpt: Paint tool cavity custom curve crash\nOperating system: Windows 10\nGraphics card: NVDIA RTX 2060 Super\n\nBroken: 3.4, 3.5\n\nSteps to reproduce the issue:\n - Switch to Sculpt Mode or open default sculpting template file\n - Choose the Paint Tool\n - Click on Brush dropdown\n - Enable Cavity by clicking on Advanced >> Cavity in the \"Brush\" dropdown\n # Enable Custom Curve under Advanced >> Cavity in the \"Brush\" dropdown\n\n\n\nResult:\nNo **Custom Curve** is shown as in other Sculpting Tools & after trying to paint with the **Paint** tool setup this way blender instantly crashes.", "Sculpt: Artifact in Multires when mirror modifier is applied\nOperating system: Linux-4.19.97-x86_64-x86_64-AMD_Athlon-tm-_II_X4_620_Processor-with-gentoo-2.6 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 1)\n\nArtifact in Multires when apply mirror\n\n4xYyu0y.png\n\n1. add multires\n2. subdivide 4-5 times\n3. make sculpt\n4. add mirror\n5. apply mirror\nor \n1. Open attached file\n2. apply the mirror modifier\n[multires_mirror_bug.blend](multires_mirror_bug.blend)" ]

[ "Crash in sculpt mode after adding some multi-resolution modifiers to any object\nOperating system: Linux-5.3.0-29-generic-x86_64-with-Ubuntu-19.10-eoan 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.8\n\n\nBroken: version: 2.80 (sub 75)\n\n\n\nIt crashes when I add a modifier multiresolution to any object 4 or 5 times, and then I go to sculpt mode\nlike I click subdivide four times and go to sculpt-mode and bam a crash. Crash backtrace below.\n\n```\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.modifier_add(type='MULTIRES') # Operator\nbpy.ops.object.multires_subdivide(modifier=\"Multires\") # Operator\nbpy.ops.object.multires_subdivide(modifier=\"Multires\") # Operator\nbpy.ops.object.multires_subdivide(modifier=\"Multires\") # Operator\nbpy.ops.object.multires_subdivide(modifier=\"Multires\") # Operator\nbpy.ops.sculpt.sculptmode_toggle() # Operator\n```\n**Backtrace**\n```\nblender(BLI_system_backtrace+0x37) [0x556df78bc8f7]\nblender(+0x11744ba) [0x556df76744ba]\n/lib/x86_64-linux-gnu/libc.so.6(+0x46470) [0x7fb39ae32470]\nblender(+0x1821f81) [0x556df7d21f81]\nblender(+0x132590c) [0x556df782590c]\nblender(+0x132657b) [0x556df782657b]\nblender(makeDerivedMesh+0xb7) [0x556df7828907]\nblender(BKE_object_handle_data_update+0x378) [0x556df777ecc8]\nblender(BKE_object_eval_uber_data+0x3d) [0x556df777f05d]\nblender(+0x13dd41e) [0x556df78dd41e]\nblender(BLI_task_pool_work_and_wait+0x204) [0x556df78be014]\nblender(_ZN3DEG23deg_evaluate_on_refreshEPNS_9DepsgraphE+0x1a5) [0x556df78dd705]\nblender(+0x12b914a) [0x556df77b914a]\nblender(wm_event_do_depsgraph+0xc3) [0x556df7abde83]\nblender(wm_event_do_refresh_wm_and_depsgraph+0x87) [0x556df7abdfe7]\nblender(wm_event_do_notifiers+0x32a) [0x556df7ac3d9a]\nblender(WM_main+0x28) [0x556df7ab9db8]\nblender(main+0x2b6) [0x556df7638446]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7fb39ae131e3]\nblender(_start+0x2e) [0x556df7670a1e]\n```\n\n" ]

[ "Buffering of nodeGroups is not working correctly\nOperating system: Fedora 31 (5.3.16-300.fc31.x86_64)\nGraphics card: Intel Corporation UHD Graphics 620 (rev 07)\nNVIDIA Corporation GP108M [GeForce MX150] (rev a1)\n\nBroken: 2.81\nWorked: (optional)\n\nIn compositing mode, when connecting output of a Value node to Y input of Translate node, every thing works as expected.\nBut when putting the Value node to a group and enables the `Buffer Groups`, connecting the output of group (which is output of Value node inside it) to Y input of Translate node does not works as expected!\n\n\nOpen:\n[problem.blend](problem.blend)\n* F12 to update.\n* Note that the `Buffer Groups` option is enabled (SideBar).\n* Note that by disabling this option and updating the tree, node group will work again.", "Programmatically creating a link involving a blank group input/output socket causes a UAF\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 3.0.0 Alpha\nAlso occurs in the 2.93.1 debug build\n\nGroup Input and Group Output nodes have blank sockets that can be used to automatically create a new group input or group output by plugging them into something. Trying to do this via `NodeTree.links.new()` causes a use-after-free in a debug build.\n\n1. Open the attached file\n2. Run the script\n3. AddressSanitizer causes a crash\n\n[group-socket-uaf.blend](group-socket-uaf.blend)\n\nAddressSanitizer output: [P2214](P2214.txt)\n\nEverything works as expected in a release build: a new group input or group output is correctly created.\n\nThis also happens if you try to directly create an output or input on the Group Input / Group Output sockets, but it happens in a different place: [P2215](P2215.txt) . I can spin that out into a separate task if needed.\n\nCreating inputs or outputs on the *node group* (which I'm pretty sure is what you're supposed to be doing) works fine.", "Geometry Nodes: Mesh Boolean destroys attributes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\nUsing Mesh Boolean with Geometry Nodes destroys attributes from input meshes. This drastically reduces usability and node network clarity as user is required to surround the Mesh Boolean node with 4 more nodes for every single attribute they want to survive the boolean operation:\n\n\n1. Open the attached file: [BoolDeleteAttributeBug.zip](attachment)\n2. Hold Ctrl+Shift and left click the Geometry output sockets of Group Input and Object Info nodes. Notice the attribute being present.\n3. Hold Ctrl+Shift and left click the Mesh output socket of Mesh Boolean node. Notice the attribute destroyed.\nResult: The attributes are destroyed by Mesh Boolean node.\nExpected: The attributes on the parts of the topology unaffected by Mesh Boolean operation remain preserved.\n\n", "Outliner Floating window Drag & Drop to Geometry Nodes editor not working\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: I don't know if it ever worked\n\nDragging and dropping objects from the outliner to the geometry node editor is not working\n\nFloat outliner to be its own window\ndrag and drop an object from the node editor to the geometry nodes\ndoesn't work.\n\n", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "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", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "linked objects un-parent after save and load.\nwindows 8.1, Geforce 660\n\nBroken: #5ebae1c\nWorked: i couldn't test as how far this existed as old versions won't compile against the current SVN.\n\nlinked objects un-parent after save and load.\n\ni included 3 files:\nfile 1: the parented objects.\nfile 2: the objects linked.\nfile 3: the parent object changed to local, everything is fine till it is saved it will un-parent!\n\n[1.blend](1.blend)\n\n[2.blend](2.blend)\n\n[3.blend](3.blend)", "Geo Nodes crash, when updating old node group with new (using user_remap()) \nOperating system: Linux-5.15.21-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.1.0 Beta\nWorked: I think it always crashed\n\nLets say I have two geo nodes: **old_node** group and **new_node** group. I want to update old to new using python:\n\n```\nold_ng.user_remap(new_ng)\n```\n\n\nBlender will crash after running code above, if scene has Cube object with geonodes modifier that uses **old_ng**. Crash happens only if modifiers tab is visible, and you re-select the cube. It wont crash, if new nodegroup does not have additional input.\n\n1. Run script from attached blend file ( it remaps old_ng to new_ng) \n2. re-select 'CubeOld' object. Blender will crash\n\n [gn_update_crash.blend](gn_update_crash.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", "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)", "Geometry Nodes: Modifier input properties don't cause update for screen statistic\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nModifier input properties of geometry node don't cause update for screen statistic.\n\n1. Create object with geometry nodes.\n2. Add any Mesh Primitive node in modifier node tree.\nPut mesh primitive on group output. Updating the detail of a primitive affects the statistics of the scene.\n3. Put group input dummy socket in detail of a primitive node to create connection.\nChanging the details through the modifier settings is not reflected in the statistics.\n", "Operator to convert input node to new group input socket\nMake an operator to convert input node to new group input socket\n\n\n- >\n\n\n\nBehaviour:\n\n- Create a new input on the current node group.\n\n- Use the input node's...\n... type as the group input socket type\n... value as default value and of the new group input and value of all instances where the group is used\n... label as the new group input's name\n\n- Replace the input node with a group input node and reconnect the new output to all previous connections\n\n- Hide all outputs on the new group input node except the newly create one (same as drag realease search way of adding a new group input socket)", "crash while setting vertices positions using foreach_set\nOperating system: macOS-12.6.6-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 6100 Intel Inc. 4.1 INTEL-18.8.6\n\nBroken: version: 3.6.0\n\ncrash while setting vertices positions using foreach_set\n\nstart blender, run script\n\n```python\nimport bpy\nimport numpy as np\n\nl = 2 ** 28\nme = bpy.data.meshes.new('mesh')\nme.vertices.add(l)\na = np.random.random((l, 3))\nme.vertices.foreach_set('co', a.ravel())\no = bpy.data.objects.new('mesh', me, )\nbpy.context.view_layer.active_layer_collection.collection.objects.link(o)\n```\n\noutput:\n```\nWriting: /tmp/blender.crash.txt\n[1] 13339 segmentation fault /Applications/Blender/blender-3.6.0.app/Contents/MacOS/Blender\n```\n\nin blender 3.4 while using 2**27 length output is this\n```\nError: Array length mismatch (expected -402653184, got 402653184)\nError: Python: Traceback (most recent call last):\n File \"/Text\", line 8, in <module>\nRuntimeError: internal error setting the array\n```\n\ncontents of `/tmp/blender.crash.txt` is just me running script, nothing interesting\n\ninteresting bit from crash report (i can provide in full)\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x10bbaef04 foreach_getset + 1124\n1 Blender \t 0x112f45046 cfunction_call + 134\n2 Blender \t 0x112f01015 _PyObject_MakeTpCall + 373\n3 Blender \t 0x112fdf95b call_function + 971\n4 Blender \t 0x112fdbc41 _PyEval_EvalFrameDefault + 24817\n5 Blender \t 0x112fd5a22 _PyEval_Vector + 146\n6 Blender \t 0x112fd5978 PyEval_EvalCode + 120\n7 Blender \t 0x10bb9cd2a python_script_exec + 506\n8 Blender \t 0x10c6754b0 text_run_script + 64\n9 Blender \t 0x10b600ce6 wm_operator_invoke(bContext*, wmOperatorType*, wmEvent const*, PointerRNA*, ReportList*, bool, bool) + 582\n10 Blender \t 0x10b600a03 wm_operator_call_internal(bContext*, wmOperatorType*, PointerRNA*, ReportList*, wmOperatorCallContext, bool, wmEvent const*) + 515\n11 Blender \t 0x10b602025 WM_operator_name_call_ptr_with_depends_on_cursor + 165\n12 Blender \t 0x10c36bffd ui_apply_but_funcs_after(bContext*) + 285\n13 Blender \t 0x10c366fc2 ui_handler_region_menu(bContext*, wmEvent const*, void*) + 434\n14 Blender \t 0x10b604a4f wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 1007\n15 Blender \t 0x10b604020 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 48\n16 Blender \t 0x10b6033ba wm_event_do_handlers + 2554\n17 Blender \t 0x10b5f91b0 WM_main + 32\n18 Blender \t 0x10adea41e main + 878\n19 dyld \t 0x12788152e start + 462\n```\n\n", "Geometry Node boolean input socket broken when recursive linked file is reloaded in the Outliner\nOperating system: Windows 10 19044.1645\nGraphics card: GeForce RTX 3070\n\nBroken: 3.6.1, 8bda729ef4dc, branch: blender-v3.6-release, 2023-07-17\nWorked: none\n\nGeometry Node with boolean group input socket will show error \"Property type does not match input socket (socket name)\" and the input socket will not get evaluated if the recursively linked source file is reloaded in the Outliner 'Blender File' view mode.\n\nBrief description of the file linking structure\n\"01_source_GN-bool-Input.blend\" is the blend file that contains the source geometry node.\n\n\"02_GN_linked_level1.blend\" linked the \"01_source_GN-bool-Input.blend\" geometry node and using it on a local object.\n\n\"03_GN_linked_level2.blend\" linked \"02_GN_linked_level1.blend\" \"GN Cube\" object.\n\nTested with Integer input socket, works as expected in the above file linking condition.\n\n1. Open the attached blend file \"03_GN_linked_level2.blend\"\n2. In the Outliner 'Blender File' view mode (on the middle right of the UI from file), right click on the file \"//02_GN_linked_level1.blend\" and click \"Reload\"\n3. Noticed that the boolean input 'Switch' checkbox is now showing error \"Property type does not match input socket \"(Switch)\"\"\n\n" ]

[ "Regression: Crash on detaching noddle with click-drag\nBroken: version: 4.0.0 Alpha\nWorked: version: 4.0.0 Alpha\n\nCaused by: 2ce5fc4a3e43ad8564e8e2fa5075465b0711d924\n\nIf change links connected to multi-input socket blender keep crash.\n\n1. Default sceen.\n2. New Geometry Node tree.\n3. Add `Join Geoemtry` node.\n4. Drag link to multi-input socket of `Join Geoemtry` node.\n", "Crash while unpluging noodle from socket.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R9 390 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 23.4.1 31.0.14043.7000\n\nBroken: version: 3.6.0 Beta\nWorked: previous week I think\n\n[When I try to unplug connection marked on screenshot with left mouse button drag blender crashes.]\n\n[-add geometry nodes modifier\n-add set position node\n-add position node and plug it to position socket of the set position node\n-add vector scale node or any other vector math node between those two\n-try to disconnect noodle between position and vector math (marked on screen) with left mouse button drag out\n-blender crashes]\n\n", "Blender Crashes with Geometry Nodes (and probably Displace modifier) with SetPosition, using texture (Voronoi) in the Position and Offset sockets\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.27.07.230424\n\nBroken: version: 4.0.0 Alpha\n\n\nBlender Crashes with Geometry Nodes (and probably Displace modifier) with SetPosition, using texture (Voronoi) in the Position and Offset sockets. After uping the Verts count with Subdivide Mesh.\nTrying to unplug a socket Blender crashes right away.\n\n\n\nUse the default cube.\nCreate new GN. \nAdd a Set Position, Add Voronoi Texture and set Color to Position.\nUse a Color Ramp connected to the Voronoi Texture, Use a multiply node, use a Position node and connect the Multiply to Offset. \nDuplicate above minus the color ramp and connect the duplicated the set position after.\nAdd a Subdivide Mesh before the first Set position. Level 9. \n\nUploading the print of the nodes for better understanding. \nThe video showcase what happens when i try to change a Geometry Socket.\n\n\n\n", "Crash while detaching a noodle curve from a Node Socket inside a Node editor\nOperating system: Linux-6.3.5-arch1-1-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Beta\nWorked: version: 3.6.0 Beta\n\nWhile detaching a noodle curve from a socket, you will experience a crash. The crash isn't dependent on a specific editor.\n\nMain branch also experiences the crash.\n\n1. Open blender with factory startup\n2. Go to Shading Tab\n3. Go down to Shader Editor\n4. Detach the Noodle Curve from the Material Output\n\n" ]

[ "Image Sequence Offset keyframes are randomly skipped during render\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.6.1\n\n\nWhen animating the \"Offset\" parameter of an image sequence, some keyframes are randomly ignored during the render, causing the image offset to be different from what's shown in the graph editor.\n\n\n1. Create a sequence of images, label them `0001.png` to `0004.png` for example\n2. Create a plane and create a shader with an image texture node. Load the first image as the image source.\n3. Set `Frames` to `1`, `Start Frame` to `1`\n4. Insert keyframes for `Offset`, I inserted a new keyframe every 2 frames\n5. Render the animation\n6. **Expected result:** The rendered frames changes every 2 frames. **Actual result:** The rendered frames mostly changes every 2 frames, but occasionally doesn't change at all / gets delayed.\n\n\n\n\n\n\n\n", "Use draw manager for clip editor drawing\nCould be stalled to 2.93 as there isn't an real issue here as far as we are aware of. The compositor issues are more tangable.", "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.", "VSE: Animation operators missing cache invalidation\nOperating system: Linux Mint 19.1\nGraphics card: GTX 980\n\nBroken: blender-3.1.0-alpha+master.c34ea3323a3a-linux.x86_64\n\nRemove created action from NLA editor, this will still animate VSE elements\nSome weird VSE action cache?\n\n- Add any image to VSE strip\n- Set Rotation=0 at first frame and Rotation=220 for some another frame. It's rotating now, right?\n- Go to NLA tab -> push down Scene Action and remove it. Thus, we don't have any actions in our project but the image is still rotating. Why?\nAfter rebooting blender app the magick will gone. Is this a bug?\n\nThis has quite broad reach as all of these (if not more) dont invalidate the cache:\n- clearing keyframes\n- deleting actions\n- removing drivers\n- removing dopsheet channels\n- removing graph editor channels\n- removing nla tracks\n- removing nla strips\n- removing fcurve modifiers\n\n\n", "Library-Override Not able to edit \"Strip time Keyframe\" value in sidebar panel in graph-editor\nOperating system: Windows 10 Pro v.21H2\nGraphics card: NVIDIA GeForce GTX 1060 3GB\n\nBroken: Version:3.3.3, hash:8d94aeb604fa, branch: master, date:2023-01-17\n\nI think is a similar case to this \" blender/blender#81965 \", but more specifically for animated striptime. The striptime key-frame in Graph-Editor is not editable in sidebar and values are grayed out.\n\n\n1. link a collection/character/object\n2. object > relation > make library override\n3. animate\n4. stash action to create NLA track\n5. animate strip time\n6. try to change a keyframe's value in graph-editor's sidebar Fcruve > active keyframe.\nopen the StripTime_KeyLocked.blend file, try to change the selected key's value in graph editor's sidebar\n\n\n\n", "VSE: Find Missing Files Operator 2 little UI issues\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 23.4.3.230420\n\nBroken: version: 3.3.7\n\n1. Issue: The Operator doesn't seem to be generating a processing bar anywhere in the UI; which would be typical to some of those processes in Blender (e.g., when creating Proxy)\n\n2. Issue: Once the Find Missing Files Operator is completed, sequencer preview does not update unless we force the area to update by moving playback. \n\n1. Just be on the VSE.\n2. Add a few Movie Tracks (which contain Sound Track) organizing them in a normal, linear way in the timeline.\n3. Save the Blend File.\n4. Close Blender.\n5. In some file manager, change the location of original video files, so to get them displaced in Blender.\n6. Re-open Blend File, and have that situation where the Video Tracks are missing their paths and not showing in Preview).\n7. Before using the `Find Missing Files` operator, make sure in the 'Current Frame' of the Sequencer is at the time Duration of one of the missing Video Tracks.\n8. Use the Operator to verify both issues.\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", "Application handler not executed when video sequencer contains a strip\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.4\n\nA registered handler for frame_change_post does not get executed while rendering an animation when there is a strip present in the video sequencer.\n\n1. Open the example file and turn on the system console\n2. Execute the example script present in the file\n3. Render an animation, note how you can see the handler getting called before each rendered frame in the console\n4. Add a strip to the video sequencer (for example a solid color)\n5. Render another animation, note how this time the handler doesn't get called per frame anymore\n6. Remove the strip again\n7. Render once more, note how it works again as expected\n\n**Example file**\n[bug_example.blend](bug_example.blend)\n", "GPencil: Add option to jump to scene from Video Sequencer Strip\nNeed a way to jump from the strip to the scene edition directly.\n\nIt's necessary to define in some place what it's the layout to use.", "Sequencer doesn't reflect source range in strip display correctly\nWindows 7\n\nBroken: 2.78 Release\n\nWhen the length of a render source is modified, the display in the strip display doesn't show it. The info 'Original frame range' is correct though.\n\n1. From the default scene, create a 'link object data' copy (although i guess the type doesn't matter)\n2. Go back to scene 'Scene' and set the end frame to 100\n3. Go to scene 'Scene.001', open sequence editor and add scene 'Scene'. It will now show a strip of 100 frames length.\n4. Go back to scene 'Scene' and change the end frame to 50\n5. Go back to scene 'Scene.001' \nThe Sequence Editor will still show a green bar 100 frames long, although the info in the properties panel tells the correct info: Original frame range 1-50 (50).\nMore importantly, you can drag the right grabber of the strip to the right and it will still paint 100 frames green and the rest grey/transparent, although the 100 frames don't have any meaning no more - it was just the length it was created with. You can also unlink the strip from the original scene and relink it again, it will still paint 100 frames green/valid.\n\nMaybe this is a bug, an oversight, maybe even intentional, I don't know. \nI don't think a .blend file is necessary in this case, but I will upload one, if desired. \n", "Compositor workspace: Mouse jumps back to the original position when stereoscopy is enabled\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: 2.83, 4.0\n~~Worked: (3.5)~~\n\nNote: 80444effc62a is the relevant commit here\n\nAfter releasing the mouse after editing a point on the rgb curves nodes, the mouse jumps back to the original position. This makes it much slower to move a point multiple times, and often results in new points being added by accident due to the unexpected change in behaviour.\nHappens only in compositing workspace. Other editors (GN, shader) are unaffected\n\n- Open default scene\n- Select Compositing workspace\n- Add an RGB curves node \n- Add a point in the middle of the curve\n- Enable stereoscopy from output-properties panel\n- click and drag a point down, then release the mouse button. The mouse pointer jumps back to the original position instead of staying where it is.\n- Note: This goes away if you disable `Backdrop`\n\n[Video](https://projects.blender.orgattachment)", "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", "Wrong property changing `matrix_world` and destructive undo via RMB.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken:\nversion: 3.6.1\nversion: 4.0.0 Alpha\nWorked: never\n\nReturning to the original state during editing (or canceling) does not give the result that was when editing was started.\n<video src=\"attachment\" title=\"2023-08-16 21-40-53.mp4\" controls></video>\n\n1. Copy script and run\n```python\nimport bpy\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Test Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n col = self.layout.column()\n ob = context.object\n col.prop(ob,'name')\n col.prop(ob,'matrix_world')\n\nif __name__==\"__main__\":\n bpy.utils.register_class(Panel)\n```\n2. Quickly change the scale value for the object matrix.\n3. Press Right mouse button.\n\n", "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", "Line Art isn't updating active camera\nOperating system: GNU/Linux mint 19\nGraphics card: gforce RTX 2060\n\nBroken: 2.93.4 \n\nLine Art isn't updating active camera when it's changed in a 'Scene' strip (VSE)\n\n\n- Create a scene, a camera and a LineArt object.\n- Now, create a 2nd camera (Cam.001) (not the active one)\n- Create an empty scene in order to be used for video creation.\n- In `Video Sequencer`, add a Scene strip and choose the Cam.001 camera ->it changes ok, but lineart goes dependent on the first one.\n\nTest File:\n[#91971.blend](T91971.blend)" ]

[ "VSE (2.81): Copy-pasted meta strips lose all key frames\nOperating system: Linux-4.19.0-1-amd64-x86_64-with-debian-9.11 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 16)\nI tested this in 2.80 and 2.79 with the same results, which makes me wonder if this is known yet? Couldn't find in a search for \"meta strip keyframes\"\n\nMeta strips appear to be self contained movie clips that can be re-used anywhere and perform exactly the same. But this isn't true for meta strips that have key frames. When you copy and paste a meta strip that contains key frame animation, the copy doesn’t have any of the keyframes, and remains static.\n\n\n - Drag an image into the timeline. And check the \"Offset\" box in it's properties to stop it stretching to fill the screen.\n - Add a \"Transform\" effect strip to it\n - Add some key frames on the X and Y position of the Transform strip to move it around the screen.\n - Select both the image strip and the transform strip and press CTRL+G to make a Meta strip.\n - Select the meta strip, CTRL+C to copy, move the playhead somewhere else, CTRL+V to paste it\n - Notice that the pasted strip does not animate.\n\nI've attached a minimal example that demonstrates the issue.\n[Meta clip animations.zip](Meta_clip_animations.zip)" ]

[ "Python scripts calling bpy.ops.paint.image_paint operates undo steps for \"individual calls\" rather than \"all calls\" during modal operation\n5820K and GTX970\nWindows 10\n\nLatest daily build (but same problem in earlier ones too)\n\nI have a modal operator which uses image_paint function.\nAfter using it, if I do an undo, I would expect all paint operations during modal operation to be undone.\nHowever every call to image_paint adds another item to the undo list which means I have to undo through every mouse move.\nIf I have moved the mouse more than (max undo items) then I can't get back to the position before I started the operator at all (making the undo pointless)\n\nThis doesn't seem to be the consistent with other modal operator. For example, in the docs [bpy.types.Operator.html ](URL) the modal excecution example (with the addition of UNDO added to bl_options) moves a cube. Many changes can be made to the position of the cube during the modal operation. However one undo (correctly in my option) puts the cube back in the original place before the operator is run.\n\nI did try using UNDO_GROUPED in my bl_options as well as UNDO - neither worked.\n\nIf I am doing something wrong or stupid in my code - sorry!\n\nLoad the attached scene. \nPress Run Script\nHover over cube. \nRight click\nPress space\nType in Simple Paint Operator <return> to activate operator\nPress mouse button to stop the operator\nTry Undoing - it undo things one mouse move at a time\n\n[modal_paint.blend1](modal_paint.blend1)", "UI BUG: Icons in the property editor \"flicker\" when you hover them or click on them\nOperating system: Windows 10, 64 bits\nGraphics card: Geforce 1080 8gb, Geforce 1070 8gb\n\nBroken: blender-2.90.0-874af5301cdf-windows64\nWorked: 2.83.0 LTS\n\n\nIcons in the property editor annoyingly flicker, they change border thickness 1-2 pixels upon hovering over or clicking on them.\n\nThin:\n\n\nThen they get thicker:\n\n\nIt's very visible if you use Icon border settings in your theme and many monochrome themes dop use that setting, because not everyone wants to see distracting rainbow colors in their UI.\n\n\nGo to Blender Preference, Themes.\nOpen Icon colors tab and set icon border to 1.\nEssentially use any bright theme as it is very visible when your theme is bright and icons have borders.\n\n\nHover over icons in the property editor, see the flickering.\n\nHere's the video of the bug:\n\n[2020-06-22 01-18-44.mp4](2020-06-22_01-18-44.mp4)\n\n\n", "Crash when updating image pixel data through python API\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.0, 2.90\nWorked: N/A\n\nBlender crashes with apparent memory corruption, when image pixel data and previous are updated frequently with python script.\nStack traces give no obvious answer, i have seen it happen in depsgraph eval, node graph code, imbuf, etc.\n\n*Note: i could not reproduce this issue in debug mode so far, only release or RelWithDebInfo seems to work.*\n\n 1. Open attacehd file\n - Run the script\n - Make sure the scene properties are visible (it seems to only crash when displaying image previews).\n - Grab the default cube and wiggle it around to force depsgraph updates.\n - If it doesn't want to crash, re-open Blender, it seems to be quite random.\n\nI'm using a node group to access image data blocks, so they can be displayed in a panel as pointers. The code generates data to replace the image pixels as well as the preview.\nI have also tried running a timer and deferring pixel updates using a queue as suggested [here ](bpy.app.timers.html#use-a-timer-to-react-to-events-in-another-thread), just in case the depsgraph post update is somehow not safe, but this doesn't change anything substantially. The bug happens in both cases.\n\n[crashtest.blend](crashtest.blend)", "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", "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", "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", "custom brushes icon won't show up is some cases\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\nIn some cases the custom icon of the brushes won't load properly. Even by reassigning it it doesn't work.\n\nOpen the attached file and try to assign the accatech custom icon to the active brush (but anykind of image won't load)\n\nThankyou\n\n\n\n[icon.blend](icon.blend)", "PBVH Pixels should check on center uv coordinate.\nCurrently it checks on bottom left corner, but the painting is half a pixel shifted. By adding an offset of half a pixel this should reduce some artifacts.", "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)", "Edit Dyntopo Detail Size: Add resolution value for visual feedback\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\n## Issue\n\nWhen using the `sculpt.dyntopo_detail_size_edit` on `R` while Dyntopo is set to 'Constant' or 'Manual' Detailing in the dyntopo settings, \nit can easily happen that the overlay doesn't show the wires that indicate the resolution.\nThis happens when the value is much higher than the current brush size, like when working on a very small object.\n\n\n\n## Suggestion\n\nIt would be give better feedback to the user that this is happening by displaying the 'Resolution' value\n- in the header\n- in the viewport itself, like with `object.voxel_size_edit` on the same shortcut.\n\nThe first solution would be the easiest and most consistent with other operators.\nThe second solution is also very welcome but would need the text to be placed outside of the brush cursor (Perhaps even dynamically placed depending on the availible viewport space).\n\n\n\n", "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)", "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", "Add support to full commandline expressions to our 'programm paths' in User Preferences -- Edit Images Externally is unable to launch Gimp 2.10 flatpak\nOperating system and graphics card\n\nLinux Mint 18.3 Cinnammon (64 bit)\nNvidia Geforce GTX 1050 Ti\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\nBlender 2.79b\n\n\nGimp 2.10 has released a flatpak version of its program .\nIn User Preferences/ File/Edit Images Externally = flatpak cannot be launched.\n\nFor this reason a bug with Gimp developers was filed, please read the detailed description here:\n\n[Gimp_Developers](1946)\n\nAlso, before filing the bug with Gimp I posted the issue on Blender Stack Exchange:\n[[ \nedit-images-externally-with-linux-mint?noredirect=1#comment201702_114828 |BlenderStackExchange ]]\n\nTo summarize, Gimp developers believe that, as the flatpak can be launched via terminal, blender should have the option to launch a command line as well.\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\n\nDownload Gimp 2.10 flatpak\nOpen Blender 2.79b \nSet User Preferences/ File/Edit Images Externally/flatpak run org.gimp.GIMP\nUnwrap your model\nUV Map Pane Image/Edit Image Externally\n\nERROR :\n\nImage editor could not be launched, please ensure that the path in User Preferences > File is valid, and Blender has rights to launch it\n\nPlease read the above links to both Gimp Developers and Blender Stack Exchange for further details about the testing done.\n\nThank you!\n\n\n\n\n", "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\n\n", "Film -> Pixel Filter settings are not used when baking textures\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.5.0\n\n\nPixel Filter settings are not used when Baking a Texture, changing them does not effect Baking in any way. The width seems to be fixed at a value of around 0.1\nHad a quick look at the github and I'm guessing they aren't passed to the render when Baking.\n\n\nRender any texture with sub pixel details to a texture, see attached file as example\n\n- Enable viewport render preview\n- Adjust Film->Pixel Filter value, it's effective\n- Bake the texture\n- No matter how you adjust Film->Pixel Filter value, it's not effective on the baked result\n" ]

[ "Drawing single pixels (pixelart) in Image Paint Mode is impossible\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\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nDrawing pixel art in Blender (i.e. unsmoothed single pixels) has become impossible ever since the sub-pixel precision update for the image paint brush.\nThe [\"Option to turn off anti-aliasing\" ]] commit and [[ https:*developer.blender.org/rBa58c1d4497db73b2480bcc31dec0aa1ca98a3880 | \"Fix 2D paint antialiasing offset\" ](https:*developer.blender.org/rBcd827194f7cc771e9947d474ba0e7c4ae2a2aa9a) commit did not fix this.\n@PabloDobarro \nYou're going to want to have a look at this.\n\nCreate a texture of any size. Turn off anti-aliasing in the Brush settings and paint with a brush radius of 1. Neither is it possible to draw single pixels, nor can you draw lines with a width of 1 pixel.\nUsing the \"Constant\" falloff preset, the result is this:\n\nAny of the other non-constant falloffs will produce anti-aliased pixels despite anti-aliasing being turned off:\n\nThis is the expected result you should be getting, regardless of the falloff curve:\n\n\n**Note**\nAlso, apart from this bug, I believe the Falloff options should vanish from the menus completely when brush anti-aliasing is turned off, since they no longer have a purpose. The falloff must always be that of the \"Constant\" preset." ]

[ "Display warning when exporting RGBA using PNG.\nRelated to #81390.\n\nWhen exporting a render to RGBA PNG the alpha isn't correct. The issue is related to the different color spaces and PNG (sRGB) not supporting pure emissive colors. We currently don't show a message to the user explaining that it could result into artifacts.\n\nThis task would be to add a message when user selects this combination. in the export panel. Or when saving an image that isn't sRGB encoded, using these settings.\n\nMessage still needs to be approved:\n`Saving/Exporting non sRGB but transparent images to PNG creates alpha differences.` With a warning icon.", "Shader color affects Shadow Pass in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.1.0\n\nShadow Pass is not working as it should in Cycles. It somhow works much better in EEvEE (altough other problems arise).\n\nEasiest setup is just adding a plane, a sphere and setup cycles as a render engine.\nActivate **Shadow Pass** (not the Shadow Catcher Pass).\nDo an image render and everything works, more or less, as expected. So you get as a result a Black and White image (right side) where black is shadow and white is none:\n\n\nBut, as soon as you texture the objects with any image you get the darkest areas of those images in the Shadow pass (something like if one of the rgb channels is leaking to the final image):\n\n\nI have already tested it in Blender 2.83, 2.93, 3.1, 3.2 and 3.3 alpha and I have got always the same behaviour... so no idea if it ever worked or not as it should do. Right now it is absolutelly useless as you can't compose it without textures afecting the masked shadow.\n\nAs I said I already tested in EEvEE and it works better:\n\nBut another problem arises, tesselation of the objects aren't smoothed, like if it is not using Smooth Shade setting at all.\n\n\nI attach a scene that reproduces the problem: [Shadow_Pass_3.1_Packed.blend](Shadow_Pass_3.1_Packed.blend)\n\nAs a last detailed behaviour, in the scene I'm actually working, I nottice that some Specularity and Diffuse are also \"leaking\" to the Shadow Pass:\n\n\nI hope it can be fixed.\n\nOf course, If I can somehow workaround it let me know as it would be of much help as I didn't found, yet, a way to overpass the trouble other than creating a new scene with untextured materials.\n\nThanks in advance, and cheers!\nIgnasi.\n\n", "Mix Node Modes\nThe new mix node has different options according to data type.\n\nThe idea of this task is to look at adding the mix modes to float and vector data types.\n\nThe color blending modes could be used but a number of these modes assume that the\ndata is in the range of 0-1.\n\n[D16024: Node: Add mix type to Mix Node](D16024) \nThis a patch adds non-color mix types to float and vector data types.\n\nAdditionally, it would be good to look at how different interpolation modes could also be added. ", "Geometry-node object-info rotation&scale outputs values are False if scale is negative \nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0\n\nthe object info rotation & scale values are false if the scale of the sampled object is negative \nsee video, where i compare with simple drivers of the object transforms\n\n[dffdsdfdsfsfd.mp4](dffdsdfdsfsfd.mp4)\n[buggy transforms.blend](buggy_transforms.blend)\n\n", "Cycles: Persistent Data option corrupt geometry nodes instance meshes with changed normals\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.1\n\nThe instance mesh changes if render cycles use persistent data.\n\n1. Open attached file.\n2. Render few frame.\n\n", "Adding texture to particle emission density breaks particle simulation\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 74)\nWorked: (optional)\n\n\nPlease see attached file, after adding cloud texture and enabling Density in Texture influences, the simulated particles either stick to the surface or fly of into infinity as a group. \n\nOpen attached file and play animation, note some particles either sticking or a large group of particles incorrectly flying of.[particle_system_broken.blend](particle_system_broken.blend)\n\n", "New Curves data block\nThis is a follow up task based on discussions we had about #94193.\n\nCurrently, the curve object contains three distinct object types: curves, surfaces and text. We want to split those up into separate types, because there is no real reason for why they are combined into a single type. \nThis task focuses on introducing a new `Curves` data type which we will also need for hair and geometry nodes processing of curves.\n\nInitial steps:\n* - [x] Rename existing (experimental) `Hair` data block to `Curves`. In the ui it will be called `Hair Curves` for now to distinguish it from the old curve type. \n* - [x] Decide on and implement exact data structure used for curves.\n * Should be stored compactly in continuous arrays.\n * Should support arbitrary attributes on points and splines.\n * Ideally, the actual curve data structure is embedded into the `Curves` data block as a separate struct, so that the same struct could e.g. be used for grease pencil.\n* - [x] Refactor geometry nodes to use the `Curves` data block instead of `CurveEval`. (#95443)\n* - [x] Remove the runtime-only `CurveEval` data structure added for geometry nodes.\n* - [ ] Render geometry nodes curves as with the new type in Cycles and Eevee (#96455)\n* - [x] Curves sculpt mode that is mostly focused on hair use cases\n* - [ ] Curves edit mode, similar to existing curve edit mode\n\nFurther in the future:\n* - [ ] Add existing necessary features from the legacy curve object (features like shape keys may add complexity)\n* - [ ] Use versioning to convert legacy curve objects to the new curves object\n* - [ ] Add support for simulations through a generic simulation system involving geometry nodes\n* - [ ] Use versioning to convert hair particle systems to the new curves object\n\n", "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", "vertex paint sample color not working as intended.\nplatform: Windows-10-10.0.19042-SP0\nGraphics card: 1080\n\nBroken: 3.1.0 Alpha\ncommit date: 2021-11-14 00:26 hash: 7e82c840b7a4\nbuild date: 2021-11-15, 00:51:48\n\n**Short description**\nVertex color that is sampled changes.\nChange in sample color after moving mouse over panel\n\n**Steps to Reproduce**\n- Go into Vertex paint mode. (make sure viewport shading mode is set to rendered)\n- Select an object then press s to sample a vertex color and left click the mouse (to add to palette)\n# move the mouse over panel (selected color will be changed)\n\nThis seems to happen when you move the cursor over any part of the U.I.\n\n[Vcol.blend](Vcol.blend)", "User Interface: Float Curve: bug when control points has same X position\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nUser Interface: Float Curve: bug when control points has same X position\n\nIf the points are located on the same X axis, then the result breaks.\n\n| [Set Curve Parameter Bug.mp4](Set_Curve_Parameter_Bug.mp4) | [2022-10-19 15-45-49.mp4](2022-10-19_15-45-49.mp4) |\n| -- | -- |\n\n[simple example float curve.blend](simple_example_float_curve.blend)", "UI Themes: Grid color affecting axis color\n2.81a, 2.82 Beta.\n\n**Description**\nIn 3D View, the grid color overlays the XYZ axis colors, so it's impossible to set the colors I want to the XYZ axis. \nThis even happens if the grid color is set to transparent.\n\n[0020-1556.mp4](0020-1556.mp4)\n\n- Go to preferences -> Themes -> User Interface -> Axis & Gizmo Colors\n- Change X and Y axis color to black RGB(0, 0, 0)\n- Go to preferences -> Themes -> 3d View\n- change Grid color/alpha.\n\nX and Y axis color will be affected", "Font rendered incorrectly with text object\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nThe font is displayed incorrectly when added to 3d text object\n\nFont and blend file in attachment\n[untitled.blend](untitled.blend)\n\n[roadrage.ttf](roadrage.ttf)\n\n", "Cycles: point cloud geometry improvements\n[D9887: Cycles: pointcloud geometry type](D9887)\n\nImprovements:\n- [x] Point Info node with radius, position, random\n- [ ] Backfaces are ignored (like curves), which means e.g. volumes inside points don't work.\n- [ ] Render as normal or ray oriented disc (see [D9887](D9887)#289012, [P2125](P2125.txt))\n- [ ] Baked shadow transparency support like hair? But must be optional since texturing alpha across the sphere/disc is useful.", "Geometry 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).", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should." ]

[ "Creating over 2047 instances overrides object color viewport display\n[pointcloud-object-color.mp4](pointcloud-object-color.mp4)\n\n[#93245 cleaned up.blend](T93245_cleaned_up.blend)\n\n**Steps to Reproduce**\n- Open file\n- Toggle switch node or increase the \"False\" value to 2048\n\nAnother file that demonstrates the issue:\n\n\n### Original Report\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nIt seems that a geometry node scattering system created on one object can somehow change the display color of other point-cloud type objects, see gif \n\nIf we change the density of a scatter system assigned to this blue object, it can somehow change the display color of the other scatter object with a point cloud type\n\n\nIn file below, enable the node \n\n[bug.blend](bug.blend)\n\n\n\n\n" ]

[ "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "Support all attributes in the non-point cloud attribute list\nSee #87827.\n\n* position\n* UVMaps\n* Vertex groups\n(...)\n\nTechnical design discussion: #88460", "EEVEE: Crash if computation is too heavy for the system (TDR issue)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nAny time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[NebulaV2.blend](NebulaV2.blend)", "Texture Node Editor Using nodes causes weird issues in sculpt mode.\nOperating system: Linux-5.15.0-48-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.76\n\nBroken: version: 3.3.1\nWorked: perhaps never? (can redo in 2.83)\n\nAdding an image from the nodes of the texture editor for example, a sculpting brush, causes really weird issues. Disabling nodes and using the texture properties does not have this issue.\n\n- Check the blend file. Try sculpting, you will see weird noise being displaced with the texture.\n- Now disable the nodes and set the texture type from the texture properties to the same image. Sculpting again you see the issue is not happening.\n[bug.blend](bug.blend)\n\n\n\n", "Point Clouds only support one material\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken version: Current main.\nWorked: Never\n\nWhen using the `Join Geometry` node in Geometry nodes to join two points together, their material is reset to default. This only happens when joining two or more \"lone\" points.\n\n1. Recreate the geometry node setup found in the image below\n2. Change the render engine Cycles (necessary to see points with a material)\n3. Render the scene.\n4. Notice that the materials you assigned to the points are not applied.\n\nI have also included a .blend file with steps 1 and 2 done.\n[Missing Material - Join Geometry.blend](attachment)\n\n\n", "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", "bump node ignores height input (with certain inouts used as mapping vectors in the tree, seems to require `SOCKET_OUT_POINT`as opposed to `SOCKET_OUT_NORMAL`)\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.93.0 Alpha\n\n\nbump node does not react to data.\n\n[bump bug.blend](bump_bug.blend)\n\n\n\n\n\n\n\n\nFor Cylces, the following seem to be the working inputs (the ones that trigger the availability of requirements for the bump node):\n- Geometry node\n - Position\n - Parametric\n - all others dont trigger the requirements (derrivatives?)\n- Texture Coordinate node\n - Generated\n - UV\n - Object\n - Camera\n - Window\n - all others dont trigger the requirements (derrivatives?)", "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", "Rendering errors with instanced volumes in cycles geometry nodes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0 Alpha\n\nRendering errors (and extremely slow rendering) occur in Cycles when instancing volumes using geometry nodes \n\nUsing the attached .blend, start rendering (either viewport or F12)\nFrom a startup file, add geometry nodes modifier to the cube, add \"instance on points\" node and \"volume cube\" node, attach input geometry to \"instance on points\"/points and attach Volume cube \"volume\" output to \"instance on points\"/instance.\n\n**More information**\nThis bug was re-creatable on a separate computer (vastly different specs), and does not seem to be localized to just this machine\nThe bug is achievable on both CPU and GPU compute, with both CUDA and OptiX for GPU, I was not able to test with HIP\n\n[volume-instance-bug.blend](volume-instance-bug.blend)\n", "Python API: \"NodeLink\" object in 'insert_link' callback of bpy.types.Node causes crash when reading some properties.\nOperating system: Linux-5.15.65-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0\n\nTrying to dereference the properties of the sockets in the link crashes Blender.\n```\nException thrown: read access violation.\nntree was nullptr.\n```\n```\n>\tblender.exe!nodeFindNode(bNodeTree * ntree, bNodeSocket * sock, bNode * * r_node, int * r_sockindex) Line 2038\tC++\n\n \tblender.exe!rna_NodeSocket_node_get(PointerRNA * ptr) Line 2803\tC\n \tblender.exe!NodeSocket_node_get(PointerRNA * ptr) Line 46896\tC\n \tblender.exe!RNA_property_pointer_get(PointerRNA * ptr, PropertyRNA * prop) Line 3516\tC\n \tblender.exe!pyrna_prop_to_py(PointerRNA * ptr, PropertyRNA * prop) Line 1429\tC\n \tblender.exe!pyrna_struct_getattro(BPy_StructRNA * self, _object * pyname) Line 4287\tC\n \tpython310_d.dll!PyObject_GetAttr(_object * v, _object * name) Line 922\tC\n \tpython310_d.dll!_PyEval_EvalFrameDefault(_ts * tstate, _frame * f, int throwflag) Line 3593\tC\n \t[Inline Frame] python310_d.dll!_PyEval_EvalFrame(_ts *) Line 46\tC\n \tpython310_d.dll!_PyEval_Vector(_ts * tstate, PyFrameConstructor * con, _object * locals, _object * const * args, unsigned __int64 argcount, _object * kwnames) Line 5072\tC\n \tpython310_d.dll!_PyFunction_Vectorcall(_object * func, _object * const * stack, unsigned __int64 nargsf, _object * kwnames) Line 342\tC\n \tpython310_d.dll!PyVectorcall_Call(_object * callable, _object * tuple, _object * kwargs) Line 255\tC\n \tpython310_d.dll!_PyObject_Call(_ts * tstate, _object * callable, _object * args, _object * kwargs) Line 290\tC\n \tpython310_d.dll!PyObject_Call(_object * callable, _object * args, _object * kwargs) Line 318\tC\n \tblender.exe!bpy_class_call(bContext * C, PointerRNA * ptr, FunctionRNA * func, ParameterList * parms) Line 8690\tC\n \tblender.exe!rna_Node_insert_link(bNodeTree * ntree, bNode * node, bNodeLink * link) Line 1751\tC\n \tblender.exe!blender::ed::space_node::node_link_exit(bContext & C, wmOperator & op, const bool apply_links) Line 899\tC++\n \tblender.exe!blender::ed::space_node::node_link_modal(bContext * C, wmOperator * op, const wmEvent * event) Line 1055\tC++\n \tblender.exe!wm_handler_operator_call(bContext * C, ListBase * handlers, wmEventHandler * handler_base, wmEvent * event, PointerRNA * properties, const char * kmi_idname) Line 2380\tC++\n \tblender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3283\tC++\n \tblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3333\tC++\n \tblender.exe!wm_event_do_handlers(bContext * C) Line 3924\tC++\n \tblender.exe!WM_main(bContext * C) Line 643\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 579\tC\n \t[External Code]\t\n\n```\n\n- Open attached .blend file\n- run the script,\n- Create `New` Node Tree\n- add two nodes\n- connect them.\nBlender will crash to desktop.\n[custom_nodes_simple_bug_finder.blend](custom_nodes_simple_bug_finder.blend)\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "Crash When Adding Hair Subdivision upon Viewer node\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\n\n\nAdding hair subdivision will cause crash immediately when you are using viewer node to visualize field values in the viewport.\nNote no crash will occur if the viewer node is inactive.\n\n[Hair Crash.crash.txt](Hair_Crash.crash.txt)\n\n1. select default cube\n2. shift+A to add empty hair\n3. in the node tree add viewer node.\n4. Crash if adding subdivision\n[Hair Crash.blend](Hair_Crash.blend)", "Geometry Nodes: Only re-evaluated log do update available attributes in drop-down menu\nBroken: version: 4.0.0 Alpha\n\nThis is a fairly insignificant UI bug. If the GeoNodes modifier is disabled, the list of available attributes to select in one of the inputs is not updated. For example, when a vertex group is renamed, that won't be reflected in the list, until the modifier is enabled again. Can result in a bit of confusion.\n\n1. Open attached file.\n2. Notice the GeoNode modifier is disabled.\n3. Rename the vertex group.\n4. Try assigning the renamed vertex group as the modifier's Factor input; You can't, because it won't appear in the list.\n5. Enabling the modifier updates the list again, and then all is well.\n\n", "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)", "popup window call operator will crash blender\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0 Beta\n\nThis script is use to check the active material, it can be run correct in the main window, but not popup window(change the pref window to node editor)\n```\nimport bpy\n\nbpy.ops.screen.userpref_show(\"INVOKE_AREA\")\narea = bpy.context.window_manager.windows[-1].screen.areas[0]\n\n\narea.type = 'NODE_EDITOR'\nflip_header = True\narea.ui_type = 'ShaderNodeTree'\narea.spaces[0].node_tree = bpy.data.materials['Material'].node_tree\n\nfor region in area.regions:\n if region.type == 'HEADER':\n with bpy.context.temp_override(area=area, region=region):\n if flip_header: bpy.ops.screen.region_flip('INVOKE_DEFAULT') # this line will not\n\n if region.type == 'WINDOW':\n with bpy.context.temp_override(area=area, region=region):\n bpy.ops.node.view_all(\"INVOKE_AREA\") # this line will report context error\n```\n\n- Open .blend file\n- Execute script\n[#98491.blend](T98491.blend)\n\n\n\n" ]

[ "Point Density texture works wrong\nOperating system: Linux-5.3.0-26-generic-x86_64- Ubuntu 19.10 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 6)\nBroken: version: 2.81 (sub 16)\nWorked: version: 2.80 (sub 75)\n\nPoint Density texture works wrong\nInstead of these reports https:*developer.blender.org/T66915 https:*developer.blender.org/T67718 , I found, that it works correctly in 2.80, but not 2.81a or 2.82 builds. And it also crashes, but only in 2.83\n\n* Open file, switch to rendered mode:\n[point density.blend](point_density.blend)\n* Change resolution or radius value of point density texture.\nThere is 3 different results, depends on resolution or radius value:\n\nWorking ~40% times:\n\nNot working ~60% times:\n\nMesh up, less than 1% times:\n\n\n", "Changing Point Density Radius crashes Blender\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 540 Intel Inc. 4.1 INTEL-10.25.22\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging Point Density Radius crashes Blender\n\n- Default Scene\n- Switch to `cycles` (but it crashes also with EEVEE)\n- Switch viewport shading to `rendered`\n- Add Point Density texture to the default cube material\n- Connect colour output to node wrangler viewer input socket or any diffuse colour (principled or diffuse shader)[bug-point-density.blend](bug-point-density.blend)\n- Change from `particle system` to `object vertices`\n- Select object `Cube`\n- Start playing around with the `radius slider`\n\nAfter few attempts Blender crashes :(\n\nThanks guys for your incredible work!!! \n\nCheers\nAsa\n\n\n", "Point density texture Animation crashes blender\n{[F8197122](flametst2.blend)}Operating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.81 (sub 16)\nWorked: 2.79\n\nblender crashes when trying to render an animation with point density texture no matter what!\nwindows, linux, cpu, gpu they all crash after few frames.\n\n\n1. open attached file which contain a point density texture.\n2. try to render an animation.\n3. blender crashes after few frames.\n\n\n", "Point density texture crashes\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.13558 Core Profile Context 26.20.11015.5009\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nusing point density texture in cycles always crashes while tweaking the settings\n\nopen blender, \nselect cycles as the renderer, \nadd a particle on the cube, \nuse point density in shader nodes, \ntweak some point density settings, \nand it crashes\n\n", "Point Density Node in Vertex Weight mode crashes Blender\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.08\n\nBroken: version: 2.81 (sub 16)\n\nChanging the resolution on the point density node crashes Blender\n\n\nAdd a vertex group to the default cube and add some weights.\nAdd the point density node and [set it to Object Vertices, World Space, Vertex Weights and add the Vertex Group ](point_density.html).\nConnect the density output to your material output or make sure that you can see it.\nMake sure, you're in Cycles.\n\nNow reduce the resolution on the slider and Blender will crash\n\n[point density crash.blend](point_density_crash.blend)\n\nI know that this is just a bug tracker, but a fix for my use case would be to add a vertex weights node similar to the vertex colors node.\n\nThank you for your time!" ]

[ "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", "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", "Can't scrub timeline with alt + pan trackpad gesture\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.105\nMacOS 10.13.6 + Apple Magic Mouse\n\nBroken: version: 2.83 (sub 15)\nWorked: never ?\n\nWhen using a Magic Mouse it's not possible to navigate the timeline using the \"ALT+scroll\" default shortcut.\nCorrect behaviour is seen in **[this ](watch?v=o19U-yPGdyY&feature=youtu.be&t=84)** official Blender video.\n\nThis shortcut is in : User Preferences > Keymap > \"Frame Offset\".\nYou'll see it's actually **two instances** of the same shortcut :\n- one to scroll forward (ALT + Wheel Down) >> `screen.frame_offset = +1`\n- another to rewind (ALT + Wheel Up) >> `screen.frame_offset = -1`\n\nThis is a problem because the Magic Mouse is actually seen as a trackpad, therefore we have to use the \"Mouse/Trackpad Pan\" event.\nUnfortunately if you do that you are only able to scroll one way, because this shorcut entry doesn't \"see\" the scrool as bidirectional.\n\nProposed fix : add a new shortcut entry, like it's been done for \"Zoom View\" and \"Pan View\" for example.\n{[F8515046](MagicMouse_timeline_scroll.jpg), size=full}\n\nOn a Mac, using a Magic Mouse :\nopen Blender, in the viewport try to do ALT+scroll > it doesn't scroll the timeline.\n\n\n", "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", "Mode locked and crash if objects become disabled in viewport while not in object mode\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: didn't crash but showed an error message in 2.91.2\n\nObjects that are in a mode which is not Edit Mode nor Object Mode, will lock the mode setting (so the mode options are greyed out and unusable) if they get disabled in the viewport. Hiding will not cause the this bug, it needs to be disabled in viewport using that display icon in the outliner, not the eye.\n\nThe solution for this is probably to make the disable in viewport action switch the mode to object mode if the active objects gets removed (much like delete from outliner). Another solution would be to still allow the mode switch.\n\nMuch worse though! Blender crashes sometimes when it gets into this state. I can reliably crash blender as described below.\n\nGo into weightpaint mode of the default cube and disable it in the viewport using the outliner (you need to enable the option first). Now you are stuck and have to enable it in the viewport first to be able to edit anything.\n\nNow restart blender etc. and try this:\n1. Go into Vertex Paint Mode of the default cube\n2. Hit Tab to go into Edit Mode\n3. Disable the cube in the viewport using the outliner as above\n4. Hit Tab to switch out of Edit Mode -> Crash", "How to keep asset viewer options and the search field in view?\n\n\nIt's annoying that animators have to scroll up all the time to access these (or down for the search field).", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822", "Particle edit select linked not working from menus\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\n\n\nHi, I noticed that the select linked option in hair \"Particle edit\" mode/Select/ select linked doesn't work\n\nPlease open the file press W then select linked\n\nthankyou\n\n[hair.blend](hair.blend)\n\n\n", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\n\n", "Redo panel does not work for the 3d cursor\nUbuntu 18.04\n\nBroken: 7d38654\n\nRedo panel for moving the 3d cursor does not work as expected.\n\nStart moving the 3d cursor and then change the value in the redo panel.\n\n\n\nMy guess is that this happens because the 3d cursor is not effected by the normal undo.", "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", "Scroll direction Natural doesn't work on node canvas views on macOS\nOperating system: macOS-12.6.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.3.1\n\n**Short description of bug**\nI have scroll direction natural enabled for the my mouse and node views like shader editor, geometry, compositor etc ignore this setting and the direction of scroll is incorrect where scrolling down zoom out but it should be apposite and zoom-in.\n3D viewport behavior is correct and works as expected.\nI also tried to reset factory settings, and clean uninstall this issue still exists.\nThis issue I think is linked to this about invert direction scroll: T89906\n \n\n\n - On macOS make sure Scroll Direction: **Natural** is enabled. (by going to system preferences > mouse/trackpad > scroll & zoom)\n - Scrolling down using Magic mouse or Trackpad on on 3D viewport. and it should zoom-in. (expected behavior)\n # Repeating the step 2 in Shader editor. and it will zoom-out. (incorrect behavior)\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", "Blender 2.7x keymap: Add reroute shortcut (shift right mouse) doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.91\n\nCaused by 58e554a55c\n\nShortcut for add reroute doesn't work in node editor.\n\nTry add reroute between two connected nodes using shortcut (shift + RMB during cross line).\n\n", "\"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" ]

[ "Walk navigation stylus issues in 2.92 - no mouse input until alt tabbing (regression)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0 Alpha\nWorked: version: version: 2.91.0 *\n\nWalk mode seems to be a bit broken in 2.92 alpha (with both mouse and wacom tablet)\n- The issue only happens if Walk mode is entered via keyboard shortcut\n- alt tabbing out and back into the blender seems to fix the mouse lock\n\n\n*Important note:\nI noticed that this issue is a bit less severe in an older 2.92 build !!2.92.0 Alpha!!, there was still an issue where wacom stylus had to be lifted from tablet surface and placed down again in order for blender to start registering mouse movement in walk mode. (The mouse worked fine, this is pen tablet only issue)\n\n**Here's a short video demonstrating issue**\n- Example 1: Blender 2.91 hash: `0f45cab862` - Works as intended\n- Example 2: Blender 2.92 hash: `c1740e9ad0` - Works BUT only if stylus is lifted from screen (note stylus diagnostic screen on right side)\n- Example 3: Blender 2.92 hash: `acbda123ad` - Only works if user alt tabs from the window itself\n[2021-01-13 00-09-24.mp4](2021-01-13_00-09-24.mp4)\n\n\n- Default document\n- 3D Viewport > View > Navigation > Walk Navigation - Assign a keyboard shortcut (eg: Shift + F)\n- Press the previously defined shortcut\n- Walk mode crosshair appears but mouse is locked\n- Alt tab out and back into blender\n- Now walk mode works " ]

[ "Clearing library overrides from the object menu differs from the outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.1 Release Candidate\n\nPlease see the attached movie. Using the \"wrong\" menu will cause the material properties panel to become unresponsive (beginning of movie) with overrides still in place until you use the outliner (end of the movie).\n\n1. Link some objects from a file\n2. Override them down to the materials\n3. Swap out some materials\n4. Use the clear library override from the object menu\n\nResult:\n\nThe material overrides aren't cleared, but you also can't access the properties panel anymore.\n\nExpected:\n\nThe material overrides should be cleared.\n\nWorkaround:\n\nUse the outliner instead.\n\n", "Transfer Mode Operator Do To's\nNOTE: This task should be split up into multiple tasks soon.\n\nThis task is concerned about loose ends for a full working implementation of the \"Transfer Mode\" operator.\n\n---\n\n- [ ] Add the operator to a menu in every mode\n\nRight now this would always be the first menu to the right of \"View\" and \"Select\". \nLike \"Paint\", \"Weights\", \"Grease Pencil\", \"Draw\", etc. Some modes would need a new menu added for this.\n\n- [ ] Add the flash overlay for grease pencil objects\n\nArmature and curve objects are also missing the overlay but there it's less needed since other overlays are already a good indicator.\n\n- [ ] Support the operator between all object types\n\nIt is possible to use the operator on between object types (Meshes, Lattices, Curves, ect) but it doesn't work for GP edit mode, sculpt mode, vertex paint and weight paint modes.\n\n- [ ] (Armature) Edit Mode: The operators still won't run in this mode.\n- [ ] (Metaball) Edit Mode: Doesn't run.\n\n- [ ] (Optional) Also select parented aramtures when using the oeprator in weight paint modes.\n\nWhen using this operator it deselects any other objects, rendering this operator useless for weight paint mode. \n\n- [ ] (Optional) Discuss clarity of the operator name and tooltip. Potentually rename to \"Switch Object\"", "Data Transfer modifier works only for Byte Color & Face Corner color attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.2.0\n\nIf a target color attribute Domain is *Vertex* or it's Data Type is *Color*, the data are not transferred.\n\n[data-transfer-color-attr-bug.blend](data-transfer-color-attr-bug.blend)\nYou can see in the attached .blend that the Data Transfer modifier is set correctly, but the Col attribute isn't updated.\nAfter doing Convert Attribute -> Domain: *Face Corner*, Data Type: *Byte Color*, it starts to work correctly.\n\n\n", "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", "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", "Visibility differences when hiding from layer and object level properties\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.1.0 Alpha\n\nHiding collection/object from outliner with layer level property (eye icon) and object level property (screen icon) in nested releation\ngives inconsistent results\n\n**Steps to Reproduce**\n- Open attached file\n- Hide `Collection A2` with eye icon\n- Now hide `Collection A2` with screen icon\n\nRefer video: r6yA5iDHdn\n[collections_bugs.blend](https://projects.blender.orgattachment)\n\n<details>\n<summary> Original Report </summary>\n\n**Short Description**\nThere are 2 cases where:\n1. Watching viewport in rendering mode give different view in view-port and final render image or video\n\n a ) it's happening due some **not refreshed states from outliner on hide/show object and disable/enabled in render on `vieport`**\n\n b) it's especially observed problem around:\n\n - collections\n\n - moved collection to other\n\n - parent object from other collections\n\n\n2. Watching viewport and animation\n a) user operating object and all looks ok, then ruining animation and blender doing broken whole objects, relations and movements\n\n\n I can't save file that showing this, coz is unpredictable case for me when:\n1. Refresh states not working automatically from outliner in some cases, save/open file again solving problem.\n - also suggestion is to hide all child objects in parent when parent status is changed to hide to not child one per one, or give to hide just this object (eg. contex menu by RMB)\n - this management can solve problems around operation as in point 1,b) issye\n\n2. When refresh states not working on timeline and when just animation refreshing coordination **not when objects are moved,**etc. (just play changing eg. x,y,z on this same frame in case operations as move, scale, rotate not doing this - so backing to main frame when was operation, update etc. not giving effect, just play)\n - for both solution is suggestion to **give option for viewport rendering** as this same like final render, regarding the states and depth levels of parents/child/collections \n\n\nMaybe is know issue, maybe some on meet this and can explain better than me, or some part of code can be checked to see relations for this type issues.\n\n</details>", "Texture Paint: Color Palette operator issues with Undo/Redo -- Vertex Paint is fine though\nOperating system: Darwin-15.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: ATI Radeon HD 5770 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.42.15\n\nBroken: version: 2.83.0\n\n\nIn Texture Paint mode (contrary to vertexpaint mode or gpencil), the palette operators dont work with Undo/Redo\n\nFrom the default startup file:\n- go to vertexpaint mode\n- (a) in the Active Tool tab in the Properties Editor, under Brush Settings > Color Palette, add a palette\n- (b) add a color to the palette\n- (c) Undo --> should be working [color is removed again]\n- so far everything is working\n- go to texture paint and do the same a, b, c --> color is not removed again, Undo is not working\n\nThis is what is probably the cause for the following more specialized original report (but also there the same thing works fine in vertex paint mode)\n\n## original report\n\nWhile in texture mode users press S to activate a color picker (not sure why this isnt the GUI nor the tools palette?)\nWhen its active, we have the options menu (used to be F6 i believe) There is this option \"Add to Palette\".\nThis however always adds colors. When you uncheck it, it will enable itself the next time your use the S key and pick a color.\n\n01. Open the attached scene.\n02. Start texture paint mode\n03. Use S key to enable color picker\n04. Options menu (bottom left) shows \"Add option to palette\" > Deactivate it.\n05. Use S key again > Notice colors are still being added but option is unchecked.\n06. When you let go of the S key, its checked again\n\n\n\n\n[IMport Palette - Blank.blend](IMport_Palette_-_Blank.blend)", "Applying screw modifier doesn't respect hide status of edges from edit mode.\n\n\nUPDATE: If the Unhide hotkey is used, despite no parts actaully being \"unhidden\", the uneditable parts become editable.\n\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.61\n\nBroken: version: 3.5.0\n\n\nApplying a screw modifier with parts of mesh hidden in edit mode will result in those generated mesh from hidden parts to:\n\n1. only show as edges,\n2. be still selectable in edge select mode,\n3. and becoming uneditable.\n\nwhen going back to edit mode.\n\nOriginal description:\n\nIf certain parts of a mesh with a screw modifier are hidden in edit mode (though still visible with the screw modifier, just not selectable), and then the modifier is applied to the mesh in object mode, the previously hidden parts will become uneditable, though still selectable in edit mode.\n\n\n- Add a screw modifier to an object\n- Hide parts of the object in edit mode\n- Apply the screw modifier in object mode\n- Go to edit mode, the parts that's hidden supposedly has edges on display.\n - If use edge select mode, you can actually select those ghost edges, but not editable.\n - If use alt-h, then everything is shown and behaving normal again.\n", "Mistranslated Modifier Option on MacOS using Logitech Mouse\nOperating system: MacOS 12.6\nHardware: Mac Studio M1\nBlender Version: 3.3.0\n\nI use a Logitech M500s corded mouse (FW 53.00.0011) and I programmed the 4th and 5th buttons (on the side) using Logi Options (version 9.70.29) to Modifiers, Shift on one, and either Ctrl or Cmd (I have not settled on which is better) on the other. This has worked fine on all my software until Blender.\n\nAlso, since the Middle button on the mouse is critical in Blender, and since the M500s defaults to side scrolling (which I never use) when you tilt the wheel and these activate way too easily, I re-programmed both the tilts to emulate a Middle mouse button click. I left the normal wheel scrolling untouched. This allows me to click or tilt the wheel to get a Middle mouse click without worrying if I hit it correctly. This has worked great in Blender, both the normal scrolling and middle mouse clicks work as expected.\n\nWhat does not work in Blender is my using buttons 4 and 5 as modifiers when I combine them with other mouse actions. I was getting unexpected results, so I used Keymap to find out what was happening, and discovered the following:\n\nPressing button 4 (or 5) alone works: I see the appropriate \"Ctrl\" (or \"Shift\") appear but it does not map, of course, as I am only providing a modifier. I see the same effect on the status bar when I press the buttons in the editors. I see the guides correctly change for each modifier press.\n\nPressing button 4 (or 5) with a keyboard key works: Blender correctly maps the appropriate modifier (Shift, etc.) with the selected key. Same happens in the editors, e.g. when I use the modified mouse button for \"Shift\" and hit \"A\" on the keyboard, the Add menu pops up correctly.\n\nPressing button 4 (or 5) with mouse Left or Right buttons fails: Blender maps the appropriate modifier (Shift, etc.) but with button 4 (or 5) instead of with the pressed Left or Right button. If Blender is doing this elsewhere, it would explain why I am not getting expected results in the Editors.\n\nPressing button 4 (or 5) with a Middle mouse button (any as programmed) fails: Blender maps the appropriate modifier (Shift, etc.) but with \"Wheel Up\" instead of with the Middle button. Again, this could explain my unexpected results in the Editors.\n\nBy the way, when I press button 4 (or 5) and move the wheel, I get the same map, the appropriate modifier with the appropriate \"Wheel\" direction, although I can get \"Wheel Down\" with the actual wheel.\n\nAlso, when I press a Middle mouse button alone (any three): Blender correctly maps the Middle mouse button as pressed. As it does with any other mouse action except the buttons modified to be Modifiers.\n\nI tested for this problem on my Windows 11 system. Different mouse, G502, and different options software (G Hub vice Logi Options) but same Modifier settings (Shift and Ctrl) for buttons 4 and 5. It worked fine on my Windows system.", "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", "paint.sample_color operator options no longer accessible by default due to undo flag removal\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.0\nWorked: 3.1.2\n\nThe undo flag for `paint.sample_color` was removed in rB511a08585d2934b38e7d3de447752686b5f0e15b, this means that the 'redo toolbar panel' no longer pops up after sampling color with the default keybinding of 'S'. Previously, users could change the default settings through the 'redo toolbar panel', without it, I don't think the \"Sample Merged\" and \"Add to Palette\" options are accessible to users by default any more.\n\nI'm not sure if this should be considered a bug or an API change, but for the latter, I think there should at least be some other way to access these options through the UI or default keybindings without requiring users to create new keybindings with these options specifically enabled/disabled.\n\n'redo toolbar panel': \n\n1. Enter Texture Paint mode\n2. Hit `S` (default keybinding of `paint.sample_color`)\n3. No 'redo toolbar panel' appears to allow for changing operator options\n\n", "Theme > Shader Editor, Sidebar > Alpha value does not work\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A3000 12GB Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.1\n\nIn side of the Shader editor, if you want to change the color works correctly, but if you want to change the Alpha value, is not working.\n\nGo to Preferences > Themes > Node editor > Theme space > Region Background\n\n", "GPencil: Texture Image Alpha pass through grease pencil strokes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.1\n\nContext: Using texture image to make some kind of 2d fur on top of a GPencil Object\n\nThe Image Texture used to make some fur is mostly transparent and the brush used to make the colored part is a texture paint brush with Cloud Mask (it was made entirely in Blender with Blender tools).\n\nWhen on top of the GPencil object, the part of the Image Texture that is only half transparent(between 99%-1% transparent), makes the GPencil color disappear, even when moving the center point behind the one of the fur images.\n\nOn the contrary, when on top of another Image Texture (imported to be used as camera mapping), the Image Texture of the fur doesn't impact the transparency of that one.\nNotice that the Image texture boundary, even from the imported one, has problems with clipping and always makes a white line appear.\n\n- Open attached .blend file\n- Zoom in and out to notice the alpha transparency influencing the GP object\n\nThanks for your help!\n\n\n\n\n\n\n\n[bug_alpha.blend](bug_alpha.blend)", "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. ", " Alpha channel of Tint Modifier don't Work with Fill material but work with stroke material.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nhi, it's been a while i didn't make a report for a bug, :) , well i'm back.\nthe Tint Modifier work well with `Stroke `material for every color channel R,G,B,A , but for Fill material we have problem with Alpha channel that don't work at all.\nthe first video show stroke works well with ALpha channel :\n[2022-10-16 13-12-36.mp4](2022-10-16_13-12-36.mp4)\nthe file\n[aplha color of tint modifier work well with stroke material.blend](aplha_color_of_tint_modifier_work_well_with_stroke_material.blend)\nsecont video show the problem with FILL material and alpha channel:\n[2022-10-16 13-14-27.mp4](2022-10-16_13-14-27.mp4)\nthe file\n[aplha color of tint modifier don't work with fill material.blend](aplha_color_of_tint_modifier_don_t_work_with_fill_material.blend)\nhope to get fixed.thank you for reading it\n\n" ]

[ "Eyedropper is missing in the modifiers editor\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\n\nBroken: version: 3.3.0 Alpha\nWorked: 3.2\n\nthe icon of the eyedroper dissapeared from the modifiers where you can select an object\n\n\n|3.3|3.2|\n| -- | -- |\n|||\n\n" ]

[ "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "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", "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", "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", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "VSE: Cycles displayed as Rendered in Scene strip makes Blender hang - and other Scene strip bugs\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\nThe Render modes of Scene Strips are either missing or broken:\n- When Cycles is set as render and Rendered set as display, it'll make Blender hang.\n- Wireframe and Rendered doesn't work with any Render. \n- The only thing working is Eevee with either solid or Material Preview. \n- Workbench and Cycles settings seems to just use the Eevee render, since these are producing the same results in Solid and Material Preview.\n\n{[F10177251](scenestrip.gif),size=full}\n\nTest file:\nCycles is set up as render in the 3D Footage scene. In the Master Edit scene, switch display mode to Rendered. Blender will hang.\nTry the various other display modes and renders(by changing the render in the 3D Footage scene), to see wireframe and rendered doesn't work with any render. \n[multicam_3d_c.blend](multicam_3d_c.blend)\n\n\n", "Crashing while viewing animation in Cycles\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.4.0\n\nWill crash seconds after playing animation in viewport when Cycles is selected and in render view. Both CPU and GPU crash. Does not crash when removing the Subdivision Surface Modifier so polycount may be a factor? This is a brand new Apple M1 Max computer from BestBuy with nothing else installed. Also tried initializing a render to video file and crashed as well. (Note: This is an error strictly with Apple M1 computers as I have tested it on an Apple intel MacBook Pro and it works just fine.) Thank you and happy holidays!\n\n1. Load file. It is a mesh plane with default cloth and subdivision modifiers acting on a wind force.\n2. Make sure Cycles is selected as Render Engine.\n3. Select Viewport Shading to Rendered (to view cycles render)\n4. Push play. Will crash or freeze seconds after play.\n\n[Cloth_Cycles_Crash.blend](Cloth_Cycles_Crash.blend)\n\n[Blender 3.4 Crash Report 12.13.22.rtf](Blender_3.4_Crash_Report_12.13.22.rtf)\n[Blender 3.5 Crash Report 12.14.22.rtf](Blender_3.5_Crash_Report_12.14.22.rtf)", "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.", "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", "NLA: Animated Influence/Time Property Sliders Unresponsive\nTask: #76549 (NLA Strip influence slider doesn't respond to autokey correctly.)\n\n**Source of Problem**: (anim_sys.c) *nlastrip_evaluate_controls() -> animsys_evaluate_fcurves()*: I believe the issue is due to NLA evaluation, where the animated strip properties are evaluated and flushed at the same time the action strip channels are evaluated. Since autokeying doesn't insert a keyframe as the value changes, that's probably why the slider is unresponsive. \n\n**Solution**: Perhaps we should separate (despgraph-wise) NLA strip animated property evaluation from when we evaluate the NLA system for general animation? Animated strip properties would only be evaluated and flushed on frame change or when the whole frame needs refreshed. Then normal non-NLA animation evaluation will just read the strip properties as is. This would allow the slider be responsive. It also allows the user to change these properties and view their changes without having to keyframe, just like any other Blender animated property. \n\n**Potential Problems with Solution:** What do we do when strip influence is animated and the user changes it (without keying) then inserts keys on character bones. When we remap the keyframes, should we re-evaluate and use the strip's animated influence? Or should the new keys be remapped using the unkeyed strip time?", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "Sculpt undo bug, mixing sculpt brush and multi-res modifier changes.\nWith current master (also 2.83).\n\nThe following steps show and error when redoing sculpt mode undo, when mixing multi-res subdivisions.\n\n- Startup file\n- Add multi-res modifier.\n- Enter sculpt mode.\n- *Repeat this 3-5 times.*\n - Multi-res subdivide.\n - Brush Stroke.\n\n- Now undo until the very beginning.\n- Now redo until the very end.\n\nWhen redoing, there are glitches where the multi-res has tearing/artifacts.\n\nSee video: [sculpt_undo_bug.mp4](sculpt_undo_bug.mp4)", "Blender 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", "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", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) " ]

[ "Placing keyframe outside of NLA Strip frame range while in Tweak Mode no longer possible\n**Update**: The crash described below has already been fixed, but the fix blocks previously working functionality.\n\nOperating system: Windows 7 x64\nGraphics card: NVIDIA GeForce GTX 580\n\nBroken: 2.80 e2102e991764\nWorked: 2.79\n\nPlacing a keyframe outside of the range of an NLA Strip while in Tweak Mode crashes Blender entirely. System console reports: \"Attempt to free NULL pointer\"\n\nOpen attached .blend, enter Tweak Mode on the NLA strip, move to a frame outside the NLA strip's frame range, translate the Cube and insert a keyframe.\n\n[tweak_bug.blend](tweak_bug.blend)\n\n\nAnother mutation of this issue has been reported in #75804\n\n> In #75804#911738, @Rosalie wrote:\n> An other odd behavior is that if one of the end key frames are moved to lengthen the animation, you will also get the error if you try to add an animation in what used to be out of the range of the animation before you started editing. If you stop editing the stashed animation and start again, you will be able to add frames now. \n> \n> > 1- Default Startup.\n> 2- Select Cube, create new Action and add keys at 0 and 10 frame in position, rotation or scale.\n> 3- Go to the NLA editor, add the New Action to the NLATrack\n> 4- Click the ActionClip and right click (or shift-tab) \"Start editing stashed action\".\n> 5- In the Dope Sheet, Graph or Action editor, Move the keyframe that is at frame 10 to frame 20 \n> 6- Add key frame after frame 15 using Insert Key frame shortcut (i).\n> \n> The expected behavior is that I should be able to add a key frame anywhere on my timeline without having to get out of Editing Stashed Action mode. ", "Could not insert key frame due to zero NLA influence or base value\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen editing a stashed action and trying to add keys outside of the original length of my action, I get this error : **Could not insert key frame due to zero NLA influence or base value** \n\n\n1- Default Startup. \n2- Select Cube\n3- Go to pose mode\n4- In the Action Editor, Create new Action and add keys at 0 and 10 frame in position, rotation or scale.\n5- Go to the NLA editor, add the New Action to the NLATrack\n4- Click the Action Clip and right click (or shift-tab) \"Start editing stashed action\". \n6- In the Action editor, Graph editor or Dope Sheet, Add a key frame after frame 11 using Insert Keyframe shortcut (i). \n\n\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", "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", "Object drivers driven by outliner visibility not updating automatically\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb\n\nBroken: 2.90.0-874af5301cdf (June 20)\n\n\nDrivers on object modifiers that are driven by outliner settings (Hide in viewport, hide in render, etc.) won't work when toggling said outliner settings and has to be forced manually with Update Dependencies.\n\n\n\n\n\n\n - Have 2 cubes in a scene, Cube 1 and Cube 2.\n - Add a modifier on Cube 2 (In my case, a mask, in which Cube 2 is subdivided twice and has a vertex group)\n - Add a driver on the Realtime button on said mask modifier.\n - Have it be driven by Cube 1's \"Disable in Viewports\" button with the following settings:\n\n\nSingle Property\nProperty: Object Cube 1\nPath: hide_viewport\n\n\n\n 6. Disabling Cube_1 from the viewport in the Outliner will not enable the driver on Cube_2's mask modifier.\n 7. Updating Dependencies in the driver editor will correct this.\n\n\n\nAfter updating dependency, enabling Cube_1 will disable the mask in the viewport, although the mask is still enabled in the modifier tab. Clicking once in the viewport will correct this.\n\nExample .Blend File \n[BrokenDriverTest.blend](BrokenDriverTest.blend)", "Objects with volume material is included in render even when it's inside HOLDOUT collection\nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2070 Super\n\nBroken: 2.91\nWorked: (Nothing since collection system was presented)\n\nObjects with volume material is included in render even when it's inside HOLDOUT collection.\n\nApart from the question whether volume material should mask the other collections, it should not be rendered like it normally would. It should at least be excluded from the render.\n(Volume material object inside INDIRECT ONLY collection works fine)\n\nIt's very simple. Based on the default new file...\n\n1. Make a new collection and enable holdout.\n2. Make a new icosphere object inside the new collection.\n3. Give the icoshpere a volume material(Simple principled volume is fine).\n4. Move the icosphere in front of the camera, making the default cube go behind the icosphere inside the camera view.\n5. Render the image. You'll see that the holdout is not working properly for volume material objects.\n\n[volume_holdout.blend](volume_holdout.blend)", "Shadow catcher causes artifacts in PNG exports with denoising\nOperating system: Manjaro Linux\nGraphics card: AMD Radeon 535\n\nBroken: 3.1.0\n\n\nIn Cycles, rendering a scene with transparent world background and shadow being projected into a shadow catcher causes a ring of pixels with very little opacity to be created around the render's edges when exporting it as a PNG. These artifacts go away when re-rendering the scene with the shadow catcher turned back into a normal plane.\n\nI'm aware of #93865 (Artifacts around shadow catcher object) but created this one because it wasn't clear to me if this was the same issue, as that one seems to be considered a property of the 'Fast' denoiser. These artifacts were recorded on the 'Accurate' one.\n\n- In Cycles, make the world background transparent\n- Move the default cube slightly up and add a plane, scale it up a bit. \n- Point the camera so that your render captures the cube projecting a shadow into the plane, but still has the transparent world background showing around the edges\n- Turn the plane into a shadow catcher and render the scene with denoising on. Export it as a PNG; color depth and compression don't affect this issue.\n- Save the render and open it in Krita (other image editing applications may have the following feature too)\n- On the Select menu, use Select Opaque to highlight all pixels with some opacity. You will notice pixels very close to the image border all around the edges. These are normally invisible, being of very low alpha, but if you stack many renders produced like this they will be revealed as being grayscale.\n- Now, change nothing else, but turn the shadow catcher into a normal plane. Render the scene again, save it with the same settings. The ring of noise around the image edges will have disappeared.\n\nScreenshot of Krita showing the opaque pixels on a normal render:\n\n\n\nOpaque pixels on the same scene rendered with the plane made into a shadow catcher and denoising set to Accurate. Note the barely visible artifacts selected around the plane and image edge. These can be observed no matter what shape the render output takes.\n\n\n\nAnd now the same scene, denoising turned off. No ring around the edges.\n\n\n\nBlender file used for the renders above: [democatcherbug.blend](democatcherbug.blend)", "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)", "Hair Dynamics: Reduced animation frame count leads to loss of Hair Particles on Collection visibility updates\nOperating system: Windows 10 Home 64\nProcessor: AMD Ryzen 5 4600H with Radeon Graphics, 3.00 GHz\nRAM: 16.0 GB (15.4 GB usable)\nGraphics card: NVIDIA GeForce GTX 1650 Ti\n\n\nBroken: 3.4.1, 3.3.5\nWorked: 3.3.x (before 3.3.5)\n\n\nWhen applying Hair Dynamics with a reduced simulation frame count, the Hair Particles \"disappear\" on updating the visibility of any Collection in the Outliner after successfully baking.\n\n\nBased on the file hairbaketest_72frames_notOK.blend (attached).\n\n* Add hair to default cube\n* Enable hair dynamics\n* Set cache end frame to 10\n* Bake\n* Hide and unhide collection\n\n**Expected Behaviour**\nThe Hair Particles are still visible, the simulation can be played. After closing and re-opening the file, the current saved frame will show the Hair Particles at that frame as in the bake. \n\n\n**Actual Behaviour**\nThe Hair Particles are \"gone\", not visible anymore. After closing and re-opening no Hair Particles are shown. \n\n\n**Additional Information**\nThe file hairbaketest_250frames_OK.blend (attached) shows the successful workflow, it saved the baked state successfully and I could toggle the visibility of Collections in the Outliner without any effect on the Hair Particles. The workflow described in the steps is as it worked for me for a long time. I tried to break down the issue and the reduced frame count seems to make the difference for all I can tell.\n\n\n**Windows Update**\n* Last time I used Hair Dynamics workflow successfully: 3/5/2023 (March 5th) with Blender v3.3.x\n* First time I wanted to use it again but the bug occured: 3/25/2023 (March 25th) with Blender v3.3.5\n\nBetween these dates a Windows Update was made. See attached Screenshot of my Windows Update history. The reason I think it's worth mentioning, is that I did a lot of testing and as I have to use Hair Dynamics for a project and it's not possible, I tried and installed older versions of Blender that definitely worked without any issues (back to 2.93) but even the older versions now have this behavior when I try to make new files with Hair Dynamics.", "FADE INNACTIVE GEOMETRY MODE doesn't work properly with COLLECTION INSTANCES\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\n\nI really like this mode, but it feels likeit not completely done. It's not work with collection instances at all.\nHere is was my expectations and what it looks like currently: \n\nAnd even instances from other scenes ignore this mode too. Will be cool if it(instances) will work in stream ideology of this mode\n\n\nOpen this file [FADE INNACTIVE GEOMETRY DOESN'T WORK PROPERLY WITH INSTANCES.blend](FADE_INNACTIVE_GEOMETRY_DOESN_T_WORK_PROPERLY_WITH_INSTANCES.blend) and select (one by one) buttom figures (cone/torus/cube) and after selecting each one - press Tab.\nYou will see that instances ignores this mode\n\n", "Outliner: display of children that are not themselves part of a collection is arbitrary\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 472.12\n\nBroken: version: 3.2.2\n\nI have a children who paranted to parent from another collection. And children of childrens not all in main parent hierarchy.\n\n\nCreate 4 objects named \"1, 1.001...\" And parent them to object \"2\". Then copy this hierarchy \"2\" 3-4 times. Plase them to collection \"a\".Then create object \"3\" and place this object to collection \"b\". Parent objects \"2. 2.001. 2.002, 2.003\" to object \"3\". And you'll see that hierarchy \"3\" is not full...\n\n[#100393.blend](T100393.blend)\n{[F13387137](image.png) size=full}\n\n", "Add smart behavior (linking/instanciation) when pasting a collection in the Outliner or the 3DView\nOperating system: Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26\n\nBroken: version: 2.81 (sub 4)\nWorked: Never\n\nCopied Collection does not paste correctly in the Outliner \n\nCopy a Collection from the Outliner and Past it in the Outliner - Collection doesn't shown in the 'View Layer' but in 'Orphan Data'\n", "Blender 3.0 Denoising on Transparency Creates Artifacting (Blend included)\nOperating system: Win 10 (latest update)\nGraphics card: RTX 3090\n\nBroken: (3.0.0 and 3.0.1 dc2d18018171 Branch: Master)\nWorked: (2.9.0)\n\nWhen enabling transparency under \"Film\" settings, artifacts occurs in the transparency channel\n\nOpen attached .blend in 2.9.0 and 3.0.0 and hit render to see. I've set-up a compositor node setup to highlight and visualize the artificating found in 3.0.0. Try rendering with both Denoising methods to see variations in artifacts.\n\n**Other notes**\nI've played with as many render settings as possible and found that the denoiser is responsible. OptiX is worst, OpenImage is not as bad in artifacting.\n\n[alpha-transparency-denoising-issue-sample.blend](alpha-transparency-denoising-issue-sample.blend)\n\nNotice the clean colors in the greys (background composited in Compositor to help see issue)\n\n\nNotice the vertical and horizontal line noise\n\n\n[system-info.txt](system-info.txt)", "Reopening file with cleared LibOverrides restores override state\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\n`Library Override > Clear > Selected` or `Selected & Content` can set overridden hierarchies to a linked state, where collection is overridden, but contained object isn't. On reopening of .blend file, the object is overridden again.\n\n- Download both attached blend files, open linking.blend\n- In the outliner, right click on the object named 'Parent' and select `Library Override > Clear > Selected & Content`\n- Notice how the object and its children revert to a state of purely linked with no library override defined\n\n- Save and reopen .blend file\n\nThe Parent object is overridden again.\n", "Asset Browser: Instance option shifts objects from the nested collection to the world origin\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\n\nBroken: 3.5\nWorked: unsure\n\nIf we have a collection as a asset which contains nester collection, after spawning such collection with instance unchecked will keep \nobjects from nested collection at world origin\n\n- Download zip\n- Open default scene add set this as asset library path; `Example/Asset Browser`\n- Open asset browser -> select `User Library`\n- Drag & drop `Example_Object`\n- Uncheck `Instance` from redo panel. \nNotice collider objects shifts to World origin\nFound this issue by @JelSadones while discussing #103216 (Linked objects only count once towards the triangle count)\n- - - \n**Additional Info**\n- Open Prop_Example.blend\n- Remove `BoundingBox` and `CustomColliders` collection and move all objects under single collection (i.e. `Example_Object`)\n- Save file then open a default file.\n- Now drag & drop this asset and uncheck Instance option (all objects will be at the instanced position)\n\n[Example.zip](Example.zip)", "EEVEE is ghosting with viewport denoising enabled.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHere's a viewport render:\n[EEVEE ghosting0001-0090.mp4](EEVEE_ghosting0001-0090.mp4)\n\nHere's what it looks like during playback if viewport denoising is enabled:\n[2021-10-23 17-07-44.mp4](2021-10-23_17-07-44.mp4)", "Unable to add drivers to bone collections visibility\nOperating system: Windows 11\nGraphics card: RTX 4060ti\n\nBroken: 4.0.0 Alpha 2023-09-06\nWorked: Before bone collections were merged\n\nThis kinda leans into feature requests, but it is a regression nonetheless. Drivers also weren't acknowledged from what i could see.\nBefore bone collections were recently introduced, you could add a driver to each layer to influence it's visibility, and i know many people liked to use that in order to influence the visibility of a group of bones. Currently you cannot influence the visibility of a bone collection through drivers, the only option to do it now being controling the visibility of individual bones.\n\nN/A\n\n" ]

[ "Outliner: “Hide in Viewport” state reset by the “Exclude from View Layer” check box for a collection\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\nOutliner: “Hide in Viewport” state reset by the “Exclude from View Layer” check box for a collection.\n\n\n* You can use the “CollectionVisibilityExcludeFromViewLayerBug.blend” project in attachment as a starting point.\n* Go to the Outliner.\n* Ensure that the states of the objects “Cube” are all disabled.\n* In the Outliner, uncheck the visibility check box (“Exclude from View Layer”) for the collection “Collection Test”.\n* Re-enable the visibility for the collection.\n* Notice that the state “Hide in Viewport” has been re-enabled for all the objects in the collection.\n\nThe “Hide in Viewport” also mentions “Temporarily hide in viewport”. It does not seem so temporary.\n\nAs a consequence, if I decide to modify the visibility of different collections for view layer, I lose the temporary visibility state for my object when I re-enable the collection visibility.\n\nA common scenario where I frequently encountered the problem was when I was trying to isolate specific objects by disabling other collections. For example, I wanted to hide other collections to better see specific objects in a particular collection or I wanted to hide a collection because of performance issues. When I decided to re-enable the hidden collection, all the “Hide in Viewport” states were reset to the default visible value.\n\nBefore disabling “Exclude from View Layer” check box.\n\n\n\nAfter re-enabling “Exclude from View Layer” check box.\n\n\n\n[CollectionVisibilityExcludeFromViewLayerBug.blend](CollectionVisibilityExcludeFromViewLayerBug.blend)\n\n", "Toggling Collection Viewlayer visibility messes up the visibility of children objects\nOperating system: Windows 10\n\n\n**Blender Version** \nBroken: e7ae9f493aaa\n\nIt seems like toggling a collection's visibility also messes up the viewport visibility of the children objects. This might sound reasonable when all the objects under a collection have the same visibility status, but in a real use case this seems to just messes up the visibility of all the children. \n\nThe user can already make all the children visible or invisible in the viewport port by shift clicking on a parent or on the parent collection. The viewlayer visibility of a collection should not mess up the child object's viewport visibility.\n\n[ZNC62U4FmM.mp4](ZNC62U4FmM.mp4)\n\n\nOpen the attach .blend file\nDisable the viewport visibility of the cube objects\nToggle the Viewlayer visibility of the collection\nThe cubes are enabled back.\n\n[viewlayer_30112021_1542_07.blend](viewlayer_30112021_1542_07.blend)", "Objects do not retain View State when turning Collections Off then back On\nOperating system: Linux-5.8.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0\n\nIf an object has been hidden within a collection, after turning the collection off and then back on the object becomes visible again. It's \"hidden\" state is not retained.\n\n\n- Drag the cube into a new collection\n- Disable `Hide in viewport (eye button)` option for cube\n- Disable `Exclude from view layer option (checkbox)` for collection.\n- Enable checkbox, now cube is visible (it should not)\n\nResult = the cube is visible, it should remain hidden.\n\nN.B. This does not affect whether the cube is hidden from renders - the render view state is retained.\n\n" ]

[ "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "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)", "Material rendered as black with motion blur and intersecting geometry (was:motion blur bug in geometry nodes)\nOperating system: Linux-5.13.0-23-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.2\n\nBroken: version: 3.0.0\n\nwhen i turned on motion blur seems that exactly when a instance intersects another instance is rendered as black\n\nwhen motion blur is turned on and two instances instect each other its rendered as black\nif frame 27 is rendered u are able to see the bug\n\n[domino line.blend](domino_line.blend)\n\nedit (Martijn) : Renamed to make the problem slightly clearer. \nIt doesn't happen every time, when rendering with Optix I can reasonably reliably reproduce it.\n", "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.", "Displacement map, wrong normals and shadows on triangle geometry\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.69\n\nBroken: version: 2.92.0\nWorked: ?\n\nExperimental Cycles displacement introduces rendering artifacts on some geometries made of triangles. The problem seem to disappear on quad geometry.\n\nOpen the attached \"displace-problem.blend\" file.\nRender an image, or enable Cycles preview in viewport.\nThe left object is made of triangles, and appears with problems.\nThe right object is made of 1 quad, and appears fine.\n\n[displace-problem.blend](displace-problem.blend)\n", "Stroke overlay when erasing\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070 Ti\n\nBroken: (example: 2.80, 66684bdff30f, master, 2019-07-05)\n\n\nThe new alpha overlap stops working, when you erase somethin of that stroke.\n\n \nOpen a new project create a blank stroke object draw something try to erase it", "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", "Cycles fully transparent shader is brighter when a Clear Coat shader is behind it\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0 Alpha\nWorked: Never Worked\n\nWhen doing Decals, we often use alpha channel to define transparent area. However, I found when the Object's base color is above hsl(h,s,0.01), who's under the Decal, then the decal's transparent area will affect the underneath object's shading.\nMy test configuration is that 2048 viewport samples alongwith light bounces param all been set to 64.\nThe BUG is easier to notice when the background object is light grey, and the light is quite dimmed(or just turn down the exposure in colormangement to observe.)\n\n\n\n\n\nPlease open the attached Blend file to test.\n[Transparent shading BUG.blend](Transparent_shading_BUG.blend)\n\n", "Keyed Particle Physics Incorrectly Rendered Under Eevee and Cycles, but Correctly Rendered in Viewport Render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nCreate two objects. Attach a normal particle system to the first one. Attach a keyed particle system to the second one, with the two relations \"first object\" then \"second object\". Therefore, particles should move from the first object to the second object. If the starting velocities are non-trivial and the keyed particles are generated over three or more frames (e.g., start time 10, end time at least 12) then the particles of the keyed system are correctly rendered in the viewport (rendered mode) but appear in different positions when actually rendering (pressing F12).\n\nI first discovered this with a more complicated example, and the same behaviour occurred under both 2.90 and 2.83 (normal releases). Googling did not turn up anything relevant. (Motion blur is off.)\n\nI have been able to recreate it with a simple .blend file attached. Included are two screenshots at frame 20, one of the viewport, one of the rendered image. While the difference is just one particle here (a red particle is over the left square in the viewport but off the square in the rendered image), vastly different behaviour can be achieved by increasing the difference between start and end times. \n\nIn the more complicated example, not included here, a particle would appear at the top of the screen and move towards its final destination. When rendered though, it would appear in the correct place on that frame but then immediately jump to a very different location on the next frame.\n\nNote: This bug might depend on the first object's particles having a short lifetime - the original motivation is having one object explode then morph into another object. The rendered animation looked very different (and incorrect) from the viewport animation.\n\n[system-info.txt](system-info.txt)\n\n\n\n\n\n\n[Debug 2.blend](Debug_2.blend)\n1) Open it.\n2) Set viewport to Rendered mode.\n3) Move playhead to frame 20.\n4) Observe the locations of the 4 red particles near Plane.001. (They form a loose \"T\" shape and none are touching Plane.001.)\n5) Press F12.\n6) Observe the locations of the 4 red particles near Plane.001 are very different. (Two are touching Plane.001 and the other two are in line ready to arrive at Plane.001.)\n\n", "Cycles Volume Anisotropy artifacts with intersecting volumes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.23.01 30.0.13023.1012\n(CPU rendering)\n\nBroken: version: 3.0.0\nAlso tested in 3.1\nWorked: maybe never?\n\nI have a scene in which I have a smoking volcano, clouds, and an atmosphere, which was giving me trouble for a while.\n\nAs you can see, there's a horizontal line running through the smoke column.\nBy trial and error, I found out that it wasn't there when the atmosphere, which is a cube with a volume shader on it, was disabled.\n\nI tried to recreate the setting to figure out the cause of the issue, and I **boiled it down to this**:\n*If there are two volumes intersecting with different anisotropy values, things get a little weird.*\nTake a look:\n\n| | Column 0 | Column 0.1 |\n| -- | -- | -- |\n| Atm. 0 |  | \n| Atm. 0.1 | |  |\n\nNotice the horizontal line running across the smoke column when the two anisotropy values don't match.\nThis seems to happen at a specific density where the height fallof of the atmosphere crosses a certain threshold.\n\nThings I have found that have no effect:\n- *Volume step rate*\n- *Volume max steps*\n- *Clipping planes*\n- Disabling *ray visibility* (on both the atmosphere and the smoke column) to everything but *Camera*\n\n[BrokenAnisotropyCycles.blend](BrokenAnisotropyCycles.blend)\n\n\n\nPerhaps this is worth a look?", "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", "Exact Boolean (Union & Self Intersections -- to remove inside geometry) bad performance/memory footprint\nOperating system: Linux-5.15.0-67-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.6\n\nBroken: version: 3.5.0 Beta\n\nI have a group of nodes that gets rid of internal geometry by creating a \"mold\" of an object.\n\nBut it crashes on some meshes and not on other meshes and the crash doesn't give any real information why.\n\nIs there a work around for this?\nNodes works with certain meshes and crashes with others.\n\nWorking mesh and blend file.\n\n**Left side shows internal / overlapping geometry and Right side is free of this after using node network.**\n\n\n\n[doesn't crash.blend](attachment)\n\n\nCashes when I **click the switch node to enable it** (**see red arrow**).\nCrashes in 3.4.1 and 3.5.\n\n\n\n\n\n[this one crashes.blend](attachment)\n\nCrash text files attached below\n\n\nIs there a work around for this?\n\n", "Freestyle wireframe-only rendering is broken with Ztrans faces (lines disappear when Ztrans alpha and Ztrans spec are set to zero / lines behind transparent faces are not rendered / marked edges are not sometimes rendered when faces overlap)\nOSX 10.11.2 / Macbook Pro Retina 15\" Mid 2014 / GeForce GT 750M\n\nBroken: 2.76b (also broken in 2.76)\n\nRendering wireframes with controllable wire thickness requires using Freestyle but Freestyle requires filled faces even when rendering only edges. To only render edges and make the faces invisible one must set Ztrans alpha to zero.\n- When other line objects are behind line-only objects their lines are culled (however ordinary objects are rendered properly)\n- When both Ztrans alpha and spec are set to zero no lines are rendered\n- When faces overlap only some marked edges are rendered (even when faces are set to be transparent)\n\nObserve and render the attached .blend file.\n[freestyle-lineclipping.blend](freestyle-lineclipping.blend)", "Retopology: Active Object Geometry gets Occluded by Semi-Transparent Reference Object in Edit Mode\nOperating system: Linux Ubuntu 16.04\nGraphics card: Nvidia GeForce MX130\n\nBroken: 2.83.0\nWorked: 2.82.a\n\nActive mesh is occluded by high poly or another reference mesh in Edit mode. This is: I want to edit mesh A. I need mesh B to get a reference. So I make B to have a semi-transparent material for Viewport view. I select A and go to Edit mode to edit it. However, its edges and vertexes are occluded by B. We can see a comparison of 2.83.0 (first image) with 2.82a (second image): version: 2.83.0 does not show active object geometry so that we can not edit it. On the other hand 2.82a does show required geometry.\n\n \n\n1. Open Blender 2.83.0\n2. Create a Sphere mesh in the world origin so that it fits inside the default cube.\n3. Assign a semi-transparent viewport display material to the Cube so that we can see the Sphere inside. Change color also to have a better view.\n4. Select Sphere and go to Edit mode.\n5. Press A to select all vertexes.\n6. We can see that Edges and Vertexes are occluded by the Cube so that we can not edit the Sphere properly.\n\n\n[bug-report.blend](bug-report.blend)\n", "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" ]

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

[ "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!", "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related.", "Linked Mesh Editing Doesn't Work As Expected When Using Data Transfer Modifier\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.81 (sub 16)\n\nObject instances doesn't work as in blender 2.81\n\n\nIn blender 2.81, after entering the edit mode, all instances become active. You can see changes in real time.\nScreen below:\n\n\nIn Blender 2.82 it work ok till some time. I couldn't determine at what moment it breaks...\n\n\nChanges appears only after You enter to object mode.\n\n\n\nHere is blend file to test\n[instances_issue.blend](instances_issue.blend)\n\n\n", "How to handle edit-mode face/edge select-modes without any face/edges.\nBased on this report #41562,\n\n----\n\nSimple example of the problem:\n\n- Add a Circle\n- Enter EditMode\n- Select Face Mode\n- Select All (AKey)\n- Grab *(Nothing happens)*\n\n----\n\nIf you have a mesh without faces in edit-mode and use face-select for example,\nQuite a lot of tools don't work usefully.\n*(same for edge select-mode on a mesh containing only vertices, but for purpose of discussion - just talking about faces for now).*\n\nLists of tools which fail when edges/vertices are selected but no faces exist.\n\n- Transform Grab/Rotate/Scale does nothing.\n- Extrude does nothing.\n- Inconsistent de-select-all verts and edges (AKey) - *(but border/circle/mouse select dont work).*\n- *...Likely others exist, off hand these are the ones I can find...*\n\nThere are some possible solutions.\n\n- Automatically switch out of face mode *(when entering edit-mode - doesn't solve problem completely since you can remove all faces while editing)*\n- Make tools support this configuration *(need to check how to support for each tool).*\n# Make tools report a warning when its not supported (or add support when it makes sense), *otherwise - assume users know what they're doing and not attempt to second-guess their actions.*\n\nFor this design issue, Id like to come to some agreement on a good way to handle this case.\n\n----\n\nSome things to consider regarding automatic select-mode switching:\n\n- Users may temporarily remove all faces, so changing select-modes automatic for the users could disrupt their workflow.\n- Switching modes automatically could break scripts (and generally give unpredictable behavior).\n- Checking if the mesh has faces isn't really reliable since you may have hidden faces which is like having no faces from the users POV.", "Undo of operations on modifiers is inconsistent when object is in edit mode\nBroken: version: 2.79, 2.82 (sub 1), branch: master, commit date: 2019-11-22 18:14, hash: 373e936e3e\n\n\nwhen a modifier that has been **added in edit mode** to a object and is **deleted in edit mode,** it is not restored when using undo. \nThe operation shows up in the undo history but does nothing.\n\n\n1. go into edit mode\n2. add a modifier\n3. delete the modifier\n4. use undo, notice modifier is not restored.\n\ncreating the modifier in object mode or deleting it in object mode will restore it when using undo. this is a very confusion inconsistency that i noticed with the new undo method.\n", "Persistent Base of Layer brush resets when selecting another object\nOperating system: gentoo ~amd64\nGraphics card: 1060\n\nBroken: all\nWorked: none\n\nPersistent Base resets in local mode\n1 select default cube\n2 subdivide it (Edit mode > W> Subdivide to 100 > Object mode)\n3 go to sculpt mode\n4 select layer brush\n5 select \"Persistent\" chbox\n6 Push Set Persistent Base\n7 Draw\n8 Draw with CTRL (it now worked like undo brush)\nNow all good works, and i can change anu brush - super useful\nbut\n9a select any other object/collection\n9b go to other mode ant went tot sculpt mode\n9c go to local mode (hotkey /) and went back\n10 Draw with CTRL (now it don't work right - it draw without Persistent Base)\n\nPlease see my screencast\n[2020-05-26 09-58-50.mp4](2020-05-26_09-58-50.mp4)\nIn global mode all works perfect\nIn local mode Persistent Base was gone\nThank you for great opensource sculpt tool!\n\nUpdate\n[2020-05-26 10-09-57.mp4](2020-05-26_10-09-57.mp4)\nBug happend If object has been selected agane too", "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)", "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 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", "Switching Curve Shapekeys in Edit Mode go haywire if relative to one another\nOperating system:\nLinux\n\nBroken in 2.79 onwards\nWorked in 2.78\n\nPossibly caused by\n6f1493f68f\n5e1d4714fe\n\nShapekeys on curves do not reset properly when switching between them in edit mode, and one shapekey is relative to another.\n\nSelect the circle and enter edit mode. Repeatedly switch between shapekeys 'Key 1' and 'Key 2' while staying in edit mode. 'Key 2' will change over time from just this.\n[bug_report_shapekeys_curve.blend](bug_report_shapekeys_curve.blend)\n\n**How to reproduce the scene**\nCreate a Curve object. Add Basis, Key 1, Key 2 shapekeys. Set 'Key 2' relative to 'Key 1'. Select 'Key 1' and translate/scale it. ", "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)", "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)", "Switching collections does not work in Local mode.\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 5)\nWorked: 2.81\n\nIn Local mode, switching collections with hotkeys (1, 2, 3 ...) does not work.\n\nWhen I select several objects from different collections, and go into local mode, switching collections through hot keys (1, 2, 3, etc.) stops working.\n\n", "Remeshing object with subdivision modifier hangs Blender\nOperating system: macOS 10.14.6\nGraphics card:\n\nBroken: All versions of Blender but tested on Version 2.93.0 (2.93.0 2021-02-25) & Version 2.92.0 (2.92.0 2021-02-25)\nWorked: ?\n\nRemeshing object with subdivision modifier hangs Blender\n1 Add a subdivision modifier to the default cube, set it to 2 or more.\n2 Jump into Sculpt mode and remesh with default voxel settings, it should work fine.\n3 Undo the last remesh and now change the voxel size to 0.002 m and remesh again, it hangs.\n\n\nDo step 1 again, this time apply subdivision modifier and then try to remesh with voxel size of 0.002 m, it should work\n\n\n\n", "GPencil: Curve Editing - curve data desync issues\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0 Beta\nWorked: (feature was added in 2.92)\n\nThe curve data can be desynced from the stroke points. This happens when the stroke points were edited directly (like in sculpt mode), but the curve received no update. This task describes one way of generating the desync, but there may be more.\n\n\nThis can usually be fixed by toggling Curve Editing off and on again.\n\n\n - Start Blender with the 2D Animation template.\n - Draw a stroke.\n - Switch to Edit Mode.\n - Select the stroke and turn on Curve Editing to generate the curve.\n - Turn Curve Editing off.\n - Switch to Sculpt Mode.\n - Turn stroke selection on then deselect all ({key Alt}+{key S}) and turn stroke selection back off.\n - Use the grab brush and move the stroke around (to see the desync later on).\n - Go to Edit Mode.\n - Turn on Curve Editing. The data should be desynced now.\n\nor\n\n - Open attached `.blend` file in 2.92.0 Beta.\n - Turn on Curve Editing. The curve should be desynced. Toggle Curve Editing to fix it.\n\n[curve_data_desync.blend](curve_data_desync.blend)\n" ]

[ "Experimental Features: Some features still (partially) available (hotkeys, menu entries) even if feature is disabled (e.g. sculpting hotkey \"D\" to switch meshes)\nBroken: version: 2.91.0 Alpha\n\nthe \"d\" hotkey to swap sculpting meshes does not work.\n\nOpen blender\nduplicate the default cube twice into different positions\nenter sculpt mode\ntry to swap to another mesh by pressing \"d\"\nnothing happens\n" ]

[ "Regression: Crash on deleting shape key from Blender File view.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0, 3.2\nWorked: 3.1\n\nCaused by a71a513def202b119328035dbd68e86c2c47f7ac\n\nOutliner on Blender File when delete cause crash guide.\n\n- Open attached file\n- Add shape key\n- Switch outliner to Blender file display mode\n- Expand Shape key\n- select `key` then delete it from context menu\n\nr2jrCca\n\nYoutube:\nOlegeJrBbmE\n\nMy Dropbox file:\nLola%20Bunny.zip?dl=0\n\n- - -\nFirst create new ticket I unable to paste picture this here.\nI did drag there 250MB and (Remove) cause appear <html><head></head><body></body><html> please fix without <html> k5RFuuy\n\n", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\n\n", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)", "Blender 2.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)", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "Crash while using the Cloth Filter brush with collisions enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14739 Core Profile Context 21.6.1 27.20.22001.14011\n\nBroken: version: 3.0.0 Alpha\n\nUsing the cloth filter brush with collisions enabled on *both* the deforming object and the non-deforming object causes Blender to crash.\n\n- Open the attached .blend file with a minimal scene where this error can be observed. Everything has been already set up.\n- With the pre-selected *Cloth Filter* brush set to *Gravity* and both *Use Collisions* and *Use Face Sets* enabled, `LMB` on the \"Skirt\" mesh, and start dragging to the left of the screen, causing the \"Skirt\" mesh to start flying upwards.\n- After a brief while, release `LMB` and repeat the above operation by dragging to the right. Note how the direction of the cloth filter brush was not reversed this time.\n- Almost as soon as this new sculpting operation is initiated, typically Blender crashes. Occasionally it might take a few more attempts.\n\n[facesets-crasher.blend](facesets-crasher.blend)\n\n**Additional notes**\nIf extensive changes are performed to the \"Collisions\" mesh, the bug will not be able to be reproduced anymore.", "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)", "Fractured object crashes Render\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.10.12\n\nBroken: version: 3.4.1\n\nRendering image crashes Blender\n\nThe attached file is the output of a fractured cube using RBDLabs, nothing else. It's a series of 965 simple static meshes. When displaying rendered shading in viewport, all is well. When doing Render > Render Image, then Blender crashes. Happens on my Mac M1 and Mac Intel, on Blender 3.3.4, 3.4.1, 3.5 and 3.6 alpha. If I delete the 115 last cells or the 134 first ones, then the render will properly happen. Thanks !\n\n", "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n", "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "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", "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", "Asset Browser don't show my asset's and crash Blender\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: 3.4, 3.5.0\nWorked: \n\n\nI created my asset browser and at first it worked well. But after it's worked strange. Then i opened asset browser i don't see my assets, but after refreshing Blender was crashed. I tried to re-specify the path to the library, but was changed nothing. I tryed to install new Blender (3.5) and it take change but don't fix it. I can't see assets in asset browser, but then a refresh it, Blender don't crash.\n\n\n- Download and extract the attached .zip file\n- In Preferences -> File Paths -> Asset Libraries, add the directory of the unzipped file\n- Go to Asset Browser an look for the assets in the added library - You cannot find then\n- Refresh - crash", "Application templates crashes if the startup.blend of the application template contains scene named \"Asset\"\nOperating system: Windows-10-10.0.22621-SP0'\nGraphics card: NVIDIA GeForce RTX 2070 Super with Max-Q Design/PCIe/SSE2\n\nBroken: 3.5.1 2023-04-24 18:00 e1ccd9d4a1d3\nWorked: Never\n\nApplication templates that contain certain pattern in startup.blend lead to Blender to crash.\nApparently occurs when the scene is created with the name \"Asset\" and used as a application template.\n\n- Download attached [MCE.zip](attachment) file\n- Install the attached application template file (`Blender` menu > `Install Application Template...`).\n- Load it (choose the new \"MCE\" option in `File` > `New`).\n\nBlender crashes.\n\nAttached also the `blender.crash.txt` and another template.\n\n[MCE.zip](attachment)", "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 @ Startup\nOperating system: macOS-12.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.4, branch: master, commit date: 2022-10-13`\nWorked: (3.31)\n\nWon't open Crashes during open sequence\n\nOpen blender\nBased on the default startup \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", "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. ", "Crash while using the Cloth Filter brush with collisions enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14739 Core Profile Context 21.6.1 27.20.22001.14011\n\nBroken: version: 3.0.0 Alpha\n\nUsing the cloth filter brush with collisions enabled on *both* the deforming object and the non-deforming object causes Blender to crash.\n\n- Open the attached .blend file with a minimal scene where this error can be observed. Everything has been already set up.\n- With the pre-selected *Cloth Filter* brush set to *Gravity* and both *Use Collisions* and *Use Face Sets* enabled, `LMB` on the \"Skirt\" mesh, and start dragging to the left of the screen, causing the \"Skirt\" mesh to start flying upwards.\n- After a brief while, release `LMB` and repeat the above operation by dragging to the right. Note how the direction of the cloth filter brush was not reversed this time.\n- Almost as soon as this new sculpting operation is initiated, typically Blender crashes. Occasionally it might take a few more attempts.\n\n[facesets-crasher.blend](facesets-crasher.blend)\n\n**Additional notes**\nIf extensive changes are performed to the \"Collisions\" mesh, the bug will not be able to be reproduced anymore.", "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", "Crash choice asset library\nOperating system: Win 10\nGraphics card: RX460 2gb\n\nBroken: (3.2)\nWorked: (3.0)\n\n[Tests.zip](Tests.zip)\n\n- Extract archive and add `...\\Tests\\Test Asset\\` path to asset libraries\n- Open Asset library blend file\n- Open New file\n- Change any editor to Asset Browser\n# List contents of `Test Asset` library\n\nIt should crash.\nSometimes, omitting step 2 would prevent crash, but no assets would be shown.\nAlso omitting `tests` folder somehow prevented the crash, \n\nCrash log:\n[P3143: (An Untitled Masterwork)](P3143.txt)\n```\n# Blender 3.4.0, Commit date: 2022-08-14 18:40, Hash 659b63751d63\nbpy.context.space_data.params.asset_library_ref = 'Test Asset' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : UNKNOWN EXCEPTION\nException Address : 0x00007FFF3F66D759\nException Module : KERNELBASE.dll\nException Flags : 0x00000001\nException Parameters : 0x4\n\tParameters- [x] : 0x0000000019930520\n\tParameters- [x] : 0x000000FB7C5FD460\n\tParameters- [x] : 0x00007FF678278398\n\tParameters- [x] : 0x00007FF66CA80000\n\n\nStack trace:\nKERNELBASE.dll :0x00007FFF3F66D6F0 RaiseException\nVCRUNTIME140.dll :0x00007FFF283E63F0 CxxThrowException\nblender.exe :0x00007FF672BC42D0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC36C0 nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_string<char,std::char_traits<char\nblender.exe :0x00007FF672BC82B0 blender::io::serialize::JsonFormatter::serialize\nblender.exe :0x00007FF66E27B970 blender::ed::asset::index::AssetIndexFile::write_contents\nblender.exe :0x00007FF66E277D40 blender::ed::asset::index::update_index\nblender.exe :0x00007FF66E653B90 filelist_readjob_list_lib\nblender.exe :0x00007FF66E654370 filelist_readjob_recursive_dir_add_items\nblender.exe :0x00007FF66E653710 filelist_readjob_asset_library\nblender.exe :0x00007FF66DB341A0 do_job_thread\nblender.exe :0x00007FF672E5A810 _ptw32_threadStart\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThreads:\nThread : 00000448\nntdll.dll :0x00007FFF41D2C620 ZwDelayExecution\nblender.exe :0x00007FF672B3A220 BLI_thread_is_main\n\n\nThread : 000069ac\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003130\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069cc\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000054bc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000026c0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008788\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000aa4c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000608c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009c7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008d78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029c4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009918\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000162c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001478\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000040b4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000036d0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003468\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007444\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005208\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000059e4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a018\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000085a8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b1ac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000921c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005544\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad94\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067e0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000401c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b360\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008b38\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005884\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003334\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008c60\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a2e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nnvoglv64.dll :0x00007FFE819D057C Symbols not available\n\n\nThread : 00009be0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFF3F690C30 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003f9c\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007978\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ace0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ada4\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFF3012457B Symbols not available\n\n\nThread : 00009dbc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005f9c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009dac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000405c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000834c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000099e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00006284\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005ec8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a8fc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003240\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00000a10\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000082dc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000196c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004374\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007dec\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004294\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000559c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a90\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004cc8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000055f8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069a4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005c40\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001a80\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004308\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000081c8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b0d4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004bc0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009d28\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008010\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF66CA80000 3.4.0.0 blender.exe C:\\Users\\John\\Desktop\\blender-3.4.0-alpha+master.659b63751d63-windows.amd64-release\\blender.pdb \n0x00007FFF41C90000 10.0.19041.662 ntdll.dll \n0x00007FFF40620000 10.0.19041.662 KERNEL32.DLL \n0x00007FFF3F640000 10.0.19041.662 KERNELBASE.dll \n0x00007FFF40C70000 10.0.19041.546 WS2_32.dll \n0x00007FFF41310000 10.0.19041.662 RPCRT4.dll \n0x00007FFF41170000 10.0.19041.685 USER32.dll \n0x00007FFF1D640000 tbb.dll \n0x00007FFF3FCC0000 10.0.19041.662 win32u.dll \n0x00007FFF41940000 10.0.19041.685 GDI32.dll \n0x00007FFF1D600000 tbbmalloc.dll \n0x00007FFF3FAB0000 10.0.19041.685 gdi32full.dll \n0x00007FFF3FA10000 10.0.19041.546 msvcp_win.dll \n0x00007FFF3F910000 10.0.19041.546 ucrtbase.dll \n0x00007FFF417D0000 10.0.19041.610 ADVAPI32.dll \n0x00007FFF406E0000 7.0.19041.546 msvcrt.dll \n0x00007FFF41980000 10.0.19041.662 sechost.dll \n0x00007FFF3FED0000 10.0.19041.662 SHELL32.dll \n0x00007FFF283E0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFF3AE70000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFF40F00000 10.0.19041.546 SHLWAPI.dll \n0x00007FFEC90D0000 14.29.30139.0 MSVCP140.dll \n0x00007FFF3FC70000 10.0.19041.546 CFGMGR32.dll \n0x00007FFF36DA0000 10.0.19041.488 dbghelp.dll \n0x00007FFF3FBC0000 10.0.19041.662 bcrypt.dll \n0x00007FFF40CE0000 10.0.19041.546 ole32.dll \n0x00007FFF41470000 10.0.19041.662 combase.dll \n0x00007FFEC8180000 10.0.19041.546 OPENGL32.dll \n0x00007FFF41440000 10.0.19041.546 PSAPI.DLL \n0x00007FFF41A20000 10.0.19041.662 shcore.dll \n0x00007FFF3FEA0000 10.0.19041.546 IMM32.dll \n0x00007FFEB74B0000 9.0.0.0 openvdb.dll \n0x00007FFEC5BE0000 59.16.100.0 avformat-59.dll \n0x00007FFEB4FB0000 59.18.100.0 avcodec-59.dll \n0x00007FFF1D5D0000 59.4.100.0 avdevice-59.dll \n0x00007FFF40FC0000 10.0.19041.546 OLEAUT32.dll \n0x00007FFEC9030000 6.4.100.0 swscale-6.dll \n0x00007FFEC5A00000 57.17.100.0 avutil-57.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFEC5190000 1.21.1.0 OpenAL32.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFEC29E0000 2.0.20.0 SDL2.dll \n0x00007FFF39630000 libgmpxx.dll \n0x00007FFEC0D70000 3.10.2150.1013 python310.dll \n0x00007FFF40780000 10.0.19041.546 SETUPAPI.dll \n0x00007FFF300E0000 tbbmalloc_proxy.dll \n0x00007FFF31280000 6.10.19041.488 COMCTL32.dll \n0x00007FFF1C490000 10.0.19041.1 AVIFIL32.dll \n0x00007FFF39120000 10.0.19041.546 VERSION.dll \n0x00007FFF3D210000 10.0.19041.546 dwmapi.dll \n0x00007FFF1C460000 10.0.19041.546 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFF27EE0000 10.0.19041.546 Secur32.dll \n0x00007FFECB6B0000 4.3.100.0 swresample-4.dll \n0x00007FFECBF00000 10.0.19041.1 AVICAP32.dll \n0x00007FFF2EBF0000 10.0.19041.546 WINMM.dll \n0x00007FFF20660000 10.0.19041.1 MSACM32.dll \n0x00007FFECB5D0000 10.0.19041.1 MSVFW32.dll \n0x00007FFF24F20000 10.0.19041.1 winmmbase.dll \n0x00007FFF3F280000 10.0.19041.662 SSPICLI.DLL \n0x00007FFF3D240000 10.0.19041.546 kernel.appcore.dll \n0x00007FFF3D520000 10.0.19041.662 windows.storage.dll \n0x00007FFF3EE40000 10.0.19041.662 Wldp.dll \n0x00007FFF3CE80000 10.0.19041.610 uxtheme.dll \n0x0000022043090000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFF3F300000 10.0.19041.546 profapi.dll \n0x00007FFF41880000 2001.12.10941.16384 clbcatq.dll \n0x00007FFF38BE0000 10.0.19041.546 MMDevApi.dll \n0x00007FFF3F180000 10.0.19041.546 DEVOBJ.dll \n0x00007FFF38EF0000 10.0.19041.662 AUDIOSES.DLL \n0x00007FFF3E980000 10.0.19041.546 powrprof.dll \n0x00007FFF3E840000 UMPDC.dll \n0x00007FFF41AD0000 10.0.19041.662 MSCTF.dll \n0x00007FFF39850000 10.0.19041.662 AppXDeploymentClient.dll \n0x00007FFE80E80000 31.0.15.1640 nvoglv64.dll \n0x00007FFF3AE30000 10.0.19041.546 \n```\n\n\n - The conditions have been changed, but the error is still present. -----------------------------------------------------------", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Crash on toggle bone layer\nOperating system: OpenSUSE Linux, kernel 5.10.7\nGraphics card: intel \n\nBroken: blender-2.92.0-a5637756491c-linux64\n\nBlender crashes when I'm trying to enable bone layer visibility.\n\n1) Open example file: \n[rig-bug3.blend](rig-bug3.blend)\n2) Click on the *second* rig bone layer: \n\nResult: blender crashes with backtrace:\n\n```\n# Blender 2.92.0, Commit date: 2021-02-05 15:23, Hash a5637756491c\nbpy.ops.outliner.item_activate(extend=False, deselect_all=True) # Operator\nbpy.ops.outliner.item_rename() # Operator\nbpy.ops.outliner.orphans_purge(num_deleted=40) # Operator\nDeleted 40 data-block(s) # Info\nbpy.ops.outliner.orphans_purge(num_deleted=10) # Operator\nDeleted 10 data-block(s) # Info\nbpy.ops.outliner.orphans_purge(num_deleted=1) # Operator\nDeleted 1 data-block(s) # Info\nNo orphaned data-blocks to purge # Info\nSaved \"rig-bug3.blend\" # Info\nbpy.context.space_data.context = 'DATA' # Property\nSaved \"rig-bug3.blend\" # Info\n\n# backtrace\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(BLI_system_backtrace+0x20) [0x865fd90]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0xeb3a2a]\n/lib64/libc.so.6(+0x3d6c0) [0x7ff5377926c0]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_displist_vertbuf_create_pos_and_nor+0x5e) [0x13d443e]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_curve_batch_cache_create_requested+0x4ea) [0x13d24ea]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0x85bf76b]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(BLI_ghash_free+0x4e) [0x85c00ee]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0x13840e7]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_draw_render_loop_ex+0x1ac) [0x138649c]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(view3d_main_region_draw+0x8f) [0x1c0442f]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(ED_region_do_draw+0x7e1) [0x17ab221]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(wm_draw_update+0x52e) [0x123c70e]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(WM_main+0x30) [0x123a5a0]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(main+0x31e) [0xdeb30e]\n/lib64/libc.so.6(__libc_start_main+0xea) [0x7ff53777ce0a]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0xeb03c3]\n\n```", "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", "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "Crash 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)", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Crash 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", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\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 pressing Ctrl+S twice and then click \"Cancel\" in the save window\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1\n\nBlender crashes when pressing Ctrl+S twice and then click \"Cancel\" in the save window.\n\n- Open Blender\n- Press Ctrl+S\n- \"Save\" window appears\n- Press Ctrl+S again\n- Click \"Cancel\" (or \"Save\", this then also doesn't create a \"untitled.blend\" file)\n- Blender closes\n\nI also tried to reproduce it with the menu buttons that seems to work.\n", "Regression: Crash when saving after pressing ctrl+S twice.\nOperating system: Linux-5.12.3-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD Radeon RX 5700 (NAVI10, DRM 3.40.0, 5.12.3-arch1-1, LLVM 11.1.0) AMD 4.6 (Core Profile) Mesa 21.1.0\n\nBroken: version: 2.92, 2.93.0 Beta (1a69d491e5), 3.0 Alpha (067587e329).\nWorked: 2.83\n\nCaused by 796412dca0 \n\nBlender crashes when I click on save in the file browser after pressing ctrl+S twice.\n\n1. Open default scene.\n2. Press ctrl+S to open the save file dialog.\n3. When it opened, press ctrl+S again.\n4. Click on \"Save Blender File\".\n5. Crash.\n\n```\n_BLI_assert_abort() (/home/jacques/blender-git/blender/source/blender/blenlib/intern/BLI_assert.c:56)\nwm_handler_fileselect_do(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, int val) (/home/jacques/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2316)\nwm_handler_fileselect_call(bContext * C, ListBase * handlers, wmEventHandler_Op * handler, const wmEvent * event) (/home/jacques/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2462)\nwm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) (/home/jacques/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2906)\nwm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) (/home/jacques/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2958)\nwm_event_do_handlers(bContext * C) (/home/jacques/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3378)\nWM_main(bContext * C) (/home/jacques/blender-git/blender/source/blender/windowmanager/intern/wm.c:647)\nmain(int argc, const char ** argv) (/home/jacques/blender-git/blender/source/creator/creator.c:520)\n```\n", "Press \"Ctrl + S\" twice and then \"Cancel\", Blender quit abruptly\n**\nOperating system:Win10\nGraphics card:GTX1050Ti\n\n\nBroken: (2.93.1)\nWorked: (2.83.12)\n\n\nI accidentally pressed \"Ctrl + S\" twice when trying to open the pie menu \"Shift+S\".\nAfter that, when I pressed \"Cancel\", Blender quit abruptly and data was lost.\n\n\n 1. Open Blender.\n 2. File > New > General (project that has never been saved)\n 3. Ctrl + S > Release your hand from keyboard. (Do not save)\n 4. Ctrl + S > Release your hand from keyboard. (Do not save)\n 5. After doing these, press the \"Cancel\".\n 6. The blender quit abruptly.\n\nBlender 2.92 is Same phenomenon.\nBlender 2.91.2 is Same phenomenon.\n\nBlender 2.83.12 is No problem.\n" ]

[ "Startup File Viewport view is tilted by around 0.8 degrees since 2009 (Blender 2.5)\nNow, before you click away, I know what you're thinking, how can the default 3D View be tilted? This guy must have messed something with his camera, or activate the trackball views settings by mistake right?\nWell believe it or not, the default 3D view (as in, the view of the default 3D viewport in the blender startup file) is tilted by around 0.8 degrees.\n\nHere is a quick proof I just threw together, I believe it's important for you to watch it until the end, as the main proof really comes around 0:40.\n\n[tiltedview.mp4](tiltedview.mp4)\n\nAs you can see, when trying to align your view with the cube, it doesn't lined up, this can be seen by the jagged selection edges, and of course with the Camera aligned to view.\nYou can also see at 0:35 that when switching to the Front Orthographic viewpoint the view gizmo itself is rotating on the X axis a little bit.\nAnd of course, when switching back to the normal Perspective view, the viewport view is realigned, enhance why the Camera that's been re-aligned with the view is now sitting properly on the X axis. (see 1:10)\n\n**Now, why is this happening?**\n\nAfter a bit of investigating, I discovered that the issue as been around since **Blender 2.5**, which is now more than **10 years ago**\nBlender 2.5 was the first version to have the default startup file view not lined up with one of the orthographic axes. But it also had the Trackball orbiting style as default instead of Turntable. This might explain why, 10 years ago, a blender dev might have tried to get the view somewhat lined up in trackball mode, and got it almost right.\nHere's a quick demo of the same problem on 2.5 Alpha 0:\n\n[tilted25.mp4](tilted25.mp4)\n\nNow, while this isn't a top priority issue, this as been around for quite some time now, so this is not really an inquiry for an immediate fix, but more of a way too long report I did since I couldn't find anything on it online, and it drove me crazy for a few hours when I first discovered it.\n\nBroken: 2.5 Alpha0 and beyond\nWorked: 2.49b, where the view was orthographic by default\n\nStart Blender, use the viewport (Will disappear if snapping to an Orthographic axis)", "Pixar USD export does not follow API spec for camera units of attributes like focalLength\nBroken: blender-2.93.5-candidate+v293.ae1a57a05eed-windows.amd64-release\n\nPixar USD export for camera units does not follow API specification\nclass_usd_geom_camera.html#a911505cf224b975546bc2ea5505a041e\n\nOpen blender\nFile->Export as Universal Scene Description \nSave as test.usda\nopen text.usda in text editor and view camera definition\n\nIn Camera prim, note that prim attributes focalLength, horizontalAperture, horizontalApertureOffset, verticalAperture, verticalAperture are written out in mm units. As per the API class_usd_geom_camera.html#a911505cf224b975546bc2ea5505a041e the units should 1/10 of the world unit therefore focalLength should be 0.50 (aka decimetre or 0.1m units) when metersPerUnit=1\n\n```\n def Camera \"Camera\"\n {\n float2 clippingRange = (0.1, 100)\n float focalLength = 50\n float horizontalAperture = 36\n float horizontalApertureOffset = 0\n token projection = \"perspective\"\n float verticalAperture = 20.25\n float verticalApertureOffset = 0\n }\n```\n\n\nHere is an example from Houdini's USD export for a 35mm focal length\n```\n def Camera \"camera1\"\n {\n float2 clippingRange = (1, 1000000)\n float focalLength = 0.35\n float focusDistance = 4.4\n float fStop = 2.4\n float horizontalAperture = 0.20955\n float horizontalApertureOffset = 0\n token projection = \"perspective\"\n double shutter:close = 0.25\n double shutter:open = -0.25\n float verticalAperture = 0.1571625\n float verticalApertureOffset = 0\n }", "Blender 3.6's window has 1/4 content area, 3/4 transparent area under Linux\nOperating system: Arch-based Linux, kernel 6.3.7-arch1-1\nGraphics card: Intel Arc A779\n\nBroken: blender-3.6.0-beta+v36.2ef27684c56c-linux.x86_64-release, but has happened with all 3.6 daily builds so far.\nWorked: 3.5.1, the latest version.\n\nThe content area is 1/4 of the window size when the window is first open. 3/4 of the window is transparent.\nGnome 44.2, Wayland, fractional scaling enabled (100%, 175%), dual monitors (1920x1200, 4K).\n\n\n\n\nRun Blender 3.6\n\n", "VSE: Splitting Speed effect strip break movie continuity\nOperating system: Linux-5.11.0-41-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: this seems to be broken for years\n\nWhen splitting a strip that has a Speed effect applied, there's a break in continuity of the video: last frame before the split does not match the first frame after the split. As a user, I expect that a split operation keeps continuity.\n\n1. Add a movie/image sequence strip\n2. Apply a Speed Effect sequence over it, then set Speed Control to Multiply and set it to 10 (any value should work, but higher ones should make the problem easier to spot)\n3. Move the playhead to the middle of the strip and hit K to split it\n4. Check that there's a break in continuity at the split\n", "Export filеs in DAE the animation plays from the last frame\nHello!\nFrom Version 2.8 to this day, the problem has not been resolved: when exporting animation to the DAE extension, the animation is played in the Blender browser and stops at the last frame. Thus, when starting the animation in the employer's program, the animation plays from the last frame and jumps sharply to the first frame.\nExample: animation has 10 frames.\nThe animation starts from in the following sequence: 10, 1, 2, ... 10.\nIt is necessary that it was: 1, 2, ... 10.\nIn versions earlier than 2.8, there is no such problem. I have to keep Blender 2.79b and save the animation. Therefore, in this version, the animation is not played in the browser upon saving and does not stop at the last frame.\n\nP.S.\nwhen exporting to DAE in versions 2.8+, you will see that the animation will play in the browser window and stop at the last frame. in 2.79b - there is no such thing.", "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", "Mantaflow replay length change doesn't take into account effectors.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83 (sub 15)\n\nWhen you run a mantaflow simulation with replay, then increase the length of the simulation, collision effectors fail\n\nOpen file, Shift + right arrow to go to initial frame and make folder. play to bake till frame 20. (it'll be quick)\nPause, change frame end for baking to something bigger: 50. \nShift + right arrow to go to first frame. Play. After 20th frame, see effector being ignored & fluid rushing in.\n[#76075.blend](T76075.blend)", "VSE video strips with audio get packed into the .blend file when auto-packing enabled, leading to crashes with large amounts of videos\nOperating system: Windows 8.1\n\nBroken: 2.80, 2019-04-09\nWorked: 2.79\n\nBlender will try to pack all video/audio files in the vse into the .blend file if \"File>External Data>Automatically Pack Into .blend\" is enabled. This is terrible default behavior since it can very easily lead to blender attempting to save huge multi-gb files.\nIn addition to this, if you have more gb of files than you have ram, blender will crash when you enable auto-pack... really easy to do since a single video can easily be over 32gb.\n\nSome notes:\nBlender seems to only decide to do this for video files that have an audio track, even if the audio track is no longer loaded into the timeline.\nThere are no options to pack/unpack a video track. If the audio track is removed, the file will still attempt to be packed, but it cannot be unpacked.\n\nCreate a new 'Video Editing' file.\nLoad several gb of videos with audio into the vse timeline.\nSelect \"File>External Data>Automatically Pack Into .blend\"\nSave the file...\n", "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", "adding a movie strip to the video sequence editor changes the scene frame rate, this breaks all alembic currrently in use by the scene if they have a different framerate\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nadding a movie strip to the video sequence editor changes the scene frame rate, this breaks all alembic files currrently in use by the scene if they have a different framerate\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", "Volumes look much much different in master compared to 2.79b\nWindows 10 pro x64\nGTX 970\nThread Ripper 1950x\n\n\n\nBasic volume shader with noise texture from build bot today doesnt look the same as 2.79b\n\n\n\n[untitled.blend](untitled.blend)\n", "Edge quality of uv export\nWindows 10\nGtx 1060\n\nBlender 2.8 - February 28 ( d7d180bd3d8d )\n\ndifference looks huge between blender 2.79 and blender 2.8\n\nPlease note: check image in full view.\n\n\n\n\n\nthanks.", "Video Editing: Strip Offset Start/End not consistent with adjusting the strip handles\nOperating system: Win 10, 64bit\nGraphics card: no (CPU)\n\nBroken: (v 2.82a) and also (v 2.83 Alpha, Date 2020-03-18 17:16, Hash c9c08dc7c873)\n\nFrom the Manual:\nstrip.html\nStrip Offset Start/End [...] This is the same as adjusting the strip handles.\n\n\nHowever currently it is NOT really the same, which adds a lot of confusion to the already complicated concept that includes several offsets:\n\n\n\n**Detailed description of error**\n- Good: Extend the Strip using Handles: The Strip gets a helpful color code. The \"animated\" part is colored. The extended \"NOT animated / last frame repeated\" part is transparent.\n- Bug: Extend the Strip using Strip Offset: \"Animated\" and extended parts of the Strip get the same color.\n\n- Good: Shorten the Strip using Handles: Strip Offset is correctly calculated.\n- Bug: Extend the Strip using the Handles (or Extend *Keyboard E* or Slide *Keyboard S*): Strip Offset is incorrectly reset to 0.\n\n- Good: Handles: The Strip can not be shortened past the last \"animated\" frame.\n- Bug: Strip Offset: The Strip can be shortened, until no \"animated\" frame is left, and even further until the Duration becomes negative.\n- Bug: Using Slide *Keyboard S*, the \"animated\" frames can be moved completely outside the Strip. At least one \"animated\" frame should remain inside the Strip.\n\n**To further improve clarity, I would**\n- rename **Hold Offset Start/End** to **Trim Source Start/End**\n- change **Hold Offset Start/End tooltip** to \"Shortens the Strip by skipping frames at the start/end of the source\"\n- add **Strip Offset Start/End tooltip** to \"Extends the trimmed strip by repeating it's first/last frame or shortens it further\"\n- make **End** editable (it should do the same, as moving the right strip handle)\n- add **End tooltip** \"X position where the strip ends\"\n- change **Duration tooltip** \"The length of this strip after applying Trim and Strip Offset\"\n\n**If you feel very courageous**\n- change **Start** so that it points to the start of the Strip (currently it points to the first \"animated\" frame)\nI think, Blender heavily depends on **Start**, while it happily ignores Strip Offset Start and Strip Offset End. So, changing the internal meaning of **Start** likely makes a huge mess. However, maybe you can introduce and display a new variable \"display start\" or \"strip start\" instead, that does the trick, without messing too much with the internals.\n\nHappy Coding!", "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" ]

[ "Incorrect Framerate for videos imported from OBS (2.79+)\nWindows 7, 8GB RAM, GeForce 1060 with 6GB VRAM\n\nBroken: All versions above 2.79, including 2.79 and 2.8 test builds\nWorked: 2.78 and any previous version I've used for video editing, as far back as 2.5.\n\nVideos which are correctly interpreted as being 30fps in 2.78 are being loaded in as 1000fps in 2.79. Somehow, the video playback is still fine, but the number of frames is incorrect and zoom in the vse panel is limited. A 2 minute video has over 120,000 frames. Altering the framerate in the rendering panel only alters the duration of the audio. mp4 files files produced by ffmpeg/blender seem to be fine, but mp4/mkv containers produced by OBS induce the issue.\n\nLaunch blender or reload startup file. Open VSE. Add attached video file to VSE by any method. Check the render properties panel. Blender has set framerate to \"Custom (1000.0)\" with some other unfamiliar variables defined below. Repeat process in 2.78 and notice that the correct framerate (30) is automatically detected, meaning this is a recent change in how blender handles frame rate detection.\n\nAttached is a video that demonstrates the issue for testing purposes.\n\n[2018-01-22 15-30-49.mkv](2018-01-22_15-30-49.mkv)\n" ]

[ "Principled BSDF Anisotropy black faces\nWin10, 1080Ti\n\nBroken: 2.79\n\nIt seems that using anisotropy produces black odd artifacts under certain mesh circumstances. I don't think this happens often as it seems the actual mesh caused it, possibly by being a little bit too symmetrical? \n\nI suppose often it goes unnoticed so I thought it might be good for someone to investigate upon if there isn't some inconsistency.\n\nRotating the object by the tiniest bit helps (probably helps by something being non 0 ^__^).\n\nMoving random vertices randomly produces different results that are often completely correct or at least 50% correct. Good to try that in Rendered mode.\n\nScreenshot: \n\nBlend: [Anisotropy_Bug.blend](Anisotropy_Bug.blend)", "Cycles freeze on render and texture baking (with packed textures)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.83\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nBlender freezes on render\nBlender also freezes on texture bake and rendered viewport\nTried on 3 different PCs, all the same\n\nIf textures are unpacked, rendering is fine.\n\nSimply open attached .blend file and hit F12\n\n[render_test2b_delmesh3_simplified.blend](render_test2b_delmesh3_simplified.blend)", "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.", "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", "Cycles misses intersections when objects are too close\nBroken: 2.79b\n\nWhen two objects are too close, Cycles can miss intersections.\nIn the attached file, there are two intersecting semitransparent planes (at the center).\nIf the color is green or pink it indicates that the ray only intersected one plane.\n\n- Open the attached .blend file and render.\nNote how the line where the planes intersect has a coloured border.\n[transparent_planes.blend](transparent_planes.blend)", "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", "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", "EEVEE Volume draw distance broken with emission shader\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.4\nWorked: none\n\nWhen using an Emission shader as Volume shader in EEVEE, draw distances smaller than 100 produce unecpected behaviour.\nUsing Principled Volume works fine as long as Density is not 0, if it is 0 the behavior breaks in the same way.\n\n- Open attached blend (Cube with emission shader as Volume)\n- Change Volumetrics End distance to 70m\n- Zoom in and out in EEVEE viewport, the cube does disappear at a distance range inbetween the set clipping range\n[eevee_volume_drawdistance_bug.mp4](eevee_volume_drawdistance_bug.mp4)\n[eevee_volume_drawdistance_bug.blend](eevee_volume_drawdistance_bug.blend)\n\n", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "UI: Color picker lightness/value changes Hue and Saturation (only in Preferences > Themes?)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.6\n\nThe color jumps erratically by adjusting the lightness value, worse the closer to black\nSeems to converge towards specific colors (see video).\nDoesn't seem like node colors are affected.\n\n1. Open a theme setting.\n2. Adjust the lightness value.\n[ZVj8uWcUpy.mp4](ZVj8uWcUpy.mp4)\n", "Adding texture to particle emission density breaks particle simulation\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 74)\nWorked: (optional)\n\n\nPlease see attached file, after adding cloud texture and enabling Density in Texture influences, the simulated particles either stick to the surface or fly of into infinity as a group. \n\nOpen attached file and play animation, note some particles either sticking or a large group of particles incorrectly flying of.[particle_system_broken.blend](particle_system_broken.blend)\n\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)", "Reflection plane significantly reduces intensity of normal maps on affected surfaces\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU\n\nBroken: Currenct main.\nWorked: Never.\n\nWhen a reflection plane capture is added to any scene in EEVEE, the resulting reflections on surfaces affected by said capture will be significantly less affected by shader-based normal maps.\n\nComparison:\n| Without a Reflection Plane | With a Reflection Plane |\n| -- | -- |\n|  |  |\n\nThis is unexpected behavior, and although I do not fully know the intricacies of how the reflection plane capture functions, it would ideally not affect surfaces in this way.\n\nOpen the included demo file and switch to rendered view.", "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)", "Optix Viewport Denoiser Makes Objects Glow When Using High Exposure Even When There is no Light in the Scene\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nThe latest build added the feature to let non-RTX GPUs use the denoiser, so I tested it on my scene right away. However, the objects in the scene start glowing when the denoiser starts working. The scene was lit using the Physical Lights feature that the Photographer 3 addon has provided, which offers units like Lumen and Candela, etc. And since physically correct light values can sometimes be very dim (like a candle = 1 candela), sometimes be very bright (like the Sun at noon 111,000 lux), Photographer offers real life camera's settings for modifying the exposure in the color management in the render settings to adjust the overall brightness. And in my scene, I used a candle, which is very dim. Therefore the exposure has been set very high. It has been fine until the denoiser came. \n\nBased on the default startup\n1. Delete the default point light\n2. Turn the World Background Strength to 0\n3. Turn the Exposure in the Render Settings under Color Management to 10\n4. Change the render engine to Cycles\n5. Turn on render view, you should see nothing but complete darkness\n6. Turn on the Optix Viewport denoiser\n7. Wait for a while and see the default cube glowing\n\nI don't know if this is a bug or not, if it is not, please at least get some work around. Like making the denoiser refresh when the exposure changes or something?\n\n" ]

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

[ "Particle system, Hair, unwanted recalculations\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.83.9\n\nObject with hair system rotates slowly when it is not instanced. So I suppose, that something racalculates again and again with each movement.\n\n[2021-02-02_04-04-17.mp4](2021-02-02_04-04-17.mp4)\n\n- Open attached file\n- Unhide any of the collections\n- Compare the speed to rotate the object with the instance.\nThe greater the number of child particles, the more evident the problem\n [ddd.blend](ddd.blend)\n", "Cycles can not render parent particle hair, while Eevee can.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duno\n\n\nIn Eevee, parent particles are successfully rendered both in viewport and final render.\n\n\nHowever, Cycles fail to render the parent particles both in viewport and final render.\n\nA sample Blender file has been attached below.\n\n", "Duplicating hair particles from one file to another is not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0\nWorked: I don't know. And at least, v3.2.1 is also affected.\n\nFor Eevee rendering, duplicating the hair particles within the same file is working as expected, because the duplication and the original hair look exactly the same. \nHowever, duplicating the hair particles from one file to another is not working for Eevee rendering, because they do not look identical. \nMoreover, under the Eevee rendering, the duplicated hair can no longer be controlled by the particle system. (In comparison, Cycles rendering is not affected by this problem.)\n\nThe video to reproduce the error:\n[Duplicate hair under Eevee.mkv](Duplicate_hair_under_Eevee.mkv)\n\n**Steps to reproduce**\n[eevee hair test3.blend](eevee_hair_test3.blend)\n\n- Open file\n- Copy objects `LLonglash` and `LLonglash.001`\n- Open new file\n- Paste objects\n# Inspect hair shape\n\n", "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", "Selection to Active doesn't work when the selected object is a child of the active object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0 Beta\n\n\nSelection to Active operator doesn't work when the selected object is a child of the active object.\n\n\n1. Add 2 cube.\n2. Parent one of the cubes to the other.\n3. Select both cubes such that the parent is active. \n4. Use the Selection to Active operator.\n5. The operator has no effect.\n\n", "Non Uniform Scaling possible when Camera is parented\nOperating system: Win 10\nGraphics card: Geforce 2070\n\nBroken: 2.82-3.2\n\n\nIf you parent a Camera to an Object and scale the parent non uniformly, the Camera View gets scaled and distorted too.\n\n\nCreate an Empty, parent the Camera to an Empty, scale the Empty. The Camera View gets distorted.\n\n[blender_camera_scaling_bug.blend](blender_camera_scaling_bug.blend)", "Double transform of grease pencil with lattice modifier\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.1\n\nWhen GP layer is parented to bone and then deformed with Lattice modifier, the deformation occurs in incorrect place.\nIn sample file, deformation is simplified to moving all vertices.\n\nHere is original file, where actual deformation occurs, but I think relationships could be optimized a bit:\n[simple eye lattice in gp.blend](simple_eye_lattice_in_gp.blend)\n\n\n[#89943.blend](T89943.blend)\n\n- Open file\n- Move \"handle\" bone - works as expected\n- Move \"base\" bone - not as expected", "Asset Browser: Instance option shifts objects from the nested collection to the world origin\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\n\nBroken: 3.5\nWorked: unsure\n\nIf we have a collection as a asset which contains nester collection, after spawning such collection with instance unchecked will keep \nobjects from nested collection at world origin\n\n- Download zip\n- Open default scene add set this as asset library path; `Example/Asset Browser`\n- Open asset browser -> select `User Library`\n- Drag & drop `Example_Object`\n- Uncheck `Instance` from redo panel. \nNotice collider objects shifts to World origin\nFound this issue by @JelSadones while discussing #103216 (Linked objects only count once towards the triangle count)\n- - - \n**Additional Info**\n- Open Prop_Example.blend\n- Remove `BoundingBox` and `CustomColliders` collection and move all objects under single collection (i.e. `Example_Object`)\n- Save file then open a default file.\n- Now drag & drop this asset and uncheck Instance option (all objects will be at the instanced position)\n\n[Example.zip](Example.zip)", "ID Management: Sanitize and clarify our ID creation/copy tags\nSome of our ID creation/copying code and flags are currently still fuzzy and not really correct, especially when changes proposed in #88555 (ID Management: Sanitize and clarify our ID tags) become real. This concerns 'out of `G_MAIN`' IDs mostly.\n\nIMPORTANT: This task is a sister of #88555 (ID Management: Sanitize and clarify our ID tags), both will be worked on together.\n\n## `LIB_ID_CREATE_LOCALIZE`\nThis ID creation flag is only used in two places, and its name is extremely confusing since it actually sets `NO_MAIN` flag, not `LOCALIZED` one. It should simply be removed.\n\n## `LIB_ID_COPY_LOCALIZE`\nShould be updated to set `LOCALIZED` flag instead of `NO_MAIN` one: `LIB_ID_CREATE_LOCAL | LIB_ID_CREATE_NO_USER_REFCOUNT | LIB_ID_CREATE_NO_DEG_TAG | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_NO_LIB_OVERRIDE`\n\nA new `LIB_ID_COPY_NO_MAIN` set of flags should be added with default behavior to create a `NO_MAIN` ID, probably `LIB_ID_CREATE_NO_MAIN | LIB_ID_CREATE_NO_DEG_TAG | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_CACHES | LIB_ID_COPY_NO_LIB_OVERRIDE` (would leave `NO_REF_COUNT` out of the default set of flags).\n\n## `ntreeLocalize`\nThis special function needs to be removed, this specific behavior should be strictly handled through calls to generic `BKE_id_copy_ex` and dedicated code in `ntree_copy_data` IDType callback.\n\nNot sure where the recursive copying of sub-trees should be handled though, either in `BKE_id_copy_ex` or `BKE_libblock_copy_ex`, in a similar way to how we deal with animation data currently, or from `ntree_copy_data`, as done e.g. for shapekeys for meshes and other obdata?\n*Would rather keep this 'localize' behavior in the `ntree_copy_data` i think, at least for now. We need a full rethink of how we handle recursive 'deep' copying of IDs anyway, current code is dodgy at best here, and often fully broken (ref. #72659 (Making 'singleuser' for a group with too smart NodeCustomGroup breaks user counters of both source and target nodes) and similar).*", "Visual glitches With adaptive domain enabled when object is duplicated or transformed\nOperating system: windows 10\nGraphics card: 3080ti\n\n**Blender Version** 3.3 lts\n\nVisual glitches With adaptive domain enabled when object is duplicated or transformed\n\n- Open default scene\n- Add quick smoke on cube\n- enable `adaptive domain`\n- play animation\n- move domain around or duplicate it (snaps back to original place)\n- play animation again (will move to transformed position)", "GTLF always imports objects into root Scene Collection instead of active collection\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.1\n\nWhen importing objects using GLTF, the objects are always imported into root Scene Collection, instead of active collection. This is inconsistent with other importers, such as FBX.\n\n1. In a new Blender file, created some nested collection under Scene Collection\n2. Make the collection active by clicking on it\n3. Import any objects using GLTF\nResult: The imported objects are placed in the root Scene Collection\nExpected: The imported objects are placed in the active collection, consistently with other format importers.\n\n", "Cryptomatte: Are instanced objects handled correctly.\nIt is unclear what the current logic is and if it is desired. This task is there to investigate and propose a solution and implement it.", "CTRL+C does not copy ruler value like it says in documentation\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 24.20.100.6194\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nOfficial documentation claims that pressing CTRL+C will copy a ruler's value.\nI was unable to reproduce this result.\n\n\nFailure 1 (Edit mode):\n\nCreate any mesh object.\ntype `t` to open the tools.\nSelect measuring tape tool.\nclick close to a vertex to snap the measuring tape's first point to it.\nhold `CTRL` and click near another vertex to measure the distance between them.\nYou get measurement.\nPress `CTRL+C`.\nAttempt to paste this value in a field. It will fail regardless of what mode you are in.\n\nFailure 2 (Object mode):\n\nVerify that this fails in object mode as well by measuring any space in object mode and as soon as you see the measurement, press `CTRL+C`. Attempt to paste this value in a field. It will fail.", "\"Object Custom Properties\" Drivers don't work while Object Custom Properties are created with simple script.\n\n\n\n\n\n\n\n\n\n\n\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Beta\n\n\"Object Custom Properties\" Drivers don't work while Object Custom Properties are created with simple script.\n\n1. Open Blender.\n2. Select the Default Cube.\n3. Run this code via Text Editor (it creates one Object Custom Property to Cube, and one Object Custom Property to Camera):\n\n\n```\nimport bpy\n\nob = bpy.context.active_object\n\nprop_name1 = ob.name + \"_Property\"\nob[prop_name1] = 0.0\nob.id_properties_ensure() # Make sure the manager is updated\nproperty_manager = ob.id_properties_ui(prop_name1)\nproperty_manager.update(min=0.0, max=1.0, soft_min=0.0, soft_max=1.0)\n\ncamera = bpy.context.scene.objects['Camera']\n\nprop_name2 = ob.name + \"_Property\"\ncamera[prop_name2] = 0.0\ncamera.id_properties_ensure() # Make sure the manager is updated\nproperty_manager = camera.id_properties_ui(prop_name2)\nproperty_manager.update(min=0.0, max=1.0, soft_min=0.0, soft_max=1.0)\n```\n4. Select Camera.\n5. Right Click on created Camera's Object Property \"Cube_Property\" and Left Click on \"Copy as New Driver\".\n6. Select Cube.\n7. Right Click on created Cube's Object Property \"Cube_Property\" and Left Click on \"Paste Driver\".\n8. Value is not drivered / updated. Unless you edit driver, click in Data Path Textbox or Name Textbox, click Enter - now everything works great, but... i didn't change anything there.\n\n", "Datablocks can't be duplicated everywhere, because trick with fake user no longer works\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4454\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional) 2.79b\n\n\nThe MCE or tracker, should allow you to duplicate the clip asset so that you can attach other tracker bundles. In 2.8 it does not allow you to create more instances.\n\nHowever I was able to make a duplicate of a Movie Clip which is reflected in its datablock. I opened a legacy tracking project from 2.79b. It had some duplicated clips already. Once this function (multiple instances) is activated I am able to duplicate them more by using the counter buton next to the Clip name in the MCE.\n\n[Please describe the exact steps needed to reproduce the issue] Make a project in 2.79 with multiple instances of a Movie Clip then open it in 2.8. The number indicator appears. Otherwise opening a movie clip in 2.8 it does not.\n[Based on the default startup or an attached .blend file (as simple as possible)] Find the .blend of a project with extra Movie Clip instances attached{[F7091277](broken_MCE_clip_users.blend)}\n\n" ]

[ "[Duplicate Objects] 2.90.0 Duplicating parented objects have a bug\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\nIntroduced in ad6cccf058\n\nDuplicating parenting objects worked in wrong way. If we make parent objects one to each other in simple hierarchy and duplicate they it broke hierarchy in a crazy way. Same thing happen if we have objects with mirror modifier which use \"mirror object\" as axis and those objects parented to another object or Empty. \nWatch the video below, please!\n\nVersion 2.83.1 doesn't have any of these issues\n\n\n\n\n - make some cubes, maybe 4-5\n - parent them to each other \n - try select them all and duplicate\n\n\n - also you may make some objects with mirror modifier which use \"mirror object\" as axis\n - parent them to another object\n - select them all and duplicate\n\n\n\n[Duplicate_BUG.blend](Duplicate_BUG.blend)\n[Duplicate_Parent_BUG.mp4](Duplicate_Parent_BUG.mp4)\n\n", "Boolean and Parenting Inconsistencies\nSystem Information: Intel i5, 8 GB RAM\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1050\n\nBlender Version: 2.90.0 alpha, a3e6b7c2ce06 from June 30\n\nWorked in version: 2.83.1\n\nWhen I duplicate an object which has children and also boolean modifiers, the duplicates are parented to the first object instead of the duplicate parent. Also, some of the booleans are gone, because they are referenced to the cutout objects of the first setup, not those of the duplicate setup.\n\nExact steps:\nOpen file [202006bugscene1.blend](202006bugscene1.blend) and duplicate the three cube setup.\nOne of the booleans is gone, since it is referenced to the original instead of the duplicated cutout object.\nThe entire duplicate is parented to the first solid cube instead of the second one." ]

[ "Segfault after F12 render with multi-GPU Intel ARC A770 and experimental oneAPI packages on Debian\nOperating system: Linux-6.4.0-1-amd64-x86_64-with-glibc2.37 (Debian sid)\nGraphics card: two identical Intel ARC A770 Limited Edition 16GB\n\nBroken: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-25 19:23, hash: aebc743bf1c7\nWorked: 3.4, 3.4.1, 3.5.1\n\nSegfault when rendering Victor benchmark scene with F12 with second Intel ARC A770. This happens only when the second GPU is chosen as rendering device in Cycles. If both GPUs are selected first one seems to work correctly, but the second one causes a crash/error.\nEmbree on GPU does not seems to matter.\n\nBoth F12 and viewport renders with the second GPU give:\n`oneAPI kernel \"shader_eval_curve_shadow_transparency\" execution error: got runtime exception \"Native API failed. Native API returns: -50 (PI_ERROR_INVALID_ARG_VALUE) -50 (PI_ERROR_INVALID_ARG_VALUE)\"`\n\nRelevant info:\nI'm using following packages from experimental sources (I'm impatient I know :) ), so this crash might be very well caused by their incompatibility with Debian sid:\n`libigc1` - 1.0.13822.1-1\n`libigdfcl1` - 1.0.13822.1-1\n`intel-opencl-icd` - 23.13.26032.7-1\nRest of the packages, including all dependencies are from Debian sid.\n\nFull backtrace:\n\n```\n(gdb) backtrace full\n#0 0x0000000001cfee77 in ?? ()\nNo symbol table info available.\n#1 0x0000000001cffab9 in ?? ()\nNo symbol table info available.\n#2 0x0000000001b0fa9c in ?? ()\nNo symbol table info available.\n#3 0x0000000000f376a3 in ?? ()\nNo symbol table info available.\n#4 0x00007fffebaa63ec in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444\n ret = <optimized out>\n pd = <optimized out>\n out = <optimized out>\n unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737147199792, -8317621660586406251, -286296, 11, 140737488344416, 140734520795136, 8317937541230038677, 8317594907036290709}, mask_was_saved = 0}}, priv = {\n pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}\n not_first_call = <optimized out>\n#5 0x00007fffebb26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\nNo locals.\n(gdb)\n```\n\n1. On Debian sid install experimental packages mentioned above.\n2. Set second ARC GPU as a rendering device in Blender. \n3. Open Victor benchmark scene.\n4. Hit F12 and wait for the crash.", "ALT + H\nOperating system: Windows-11 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.34\n\nBroken: version: 3.6.2\n\nALT + H not working. I verified languages installed on my computer and also engaged an informatician to verify if theres no conflicts with shortcuts with another program or so. Also i am not sure if its me, but i cant change the keymapping. in preferrences\n\njust ALT + H not working. I doubt if there is other shortcuts with Alt+ that are not working... Please forgive my english i am french as first language and i live in canada. So the language installed is Canada(fr)\n\n", "Favorites menu does not take into account language change\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\n1. Set the display language to Chinese. \n2. Add some functions from the menu to the favorite menu. \n3. Switch the display language back to English\n\n", "Error when custom socket type is drawn in node tree inputs list.\nOperating system: Linux-5.11.0-36-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 620 (KBL GT2) Intel 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: version: 3.0.0 Alpha\n\nHaving a custom node socket in the side panel creates an exception when drawing the input list:\n\n* Load script [P2427: Example of socket interface](P2427.txt)\n```python\nimport bpy\nimport nodeitems_utils\n\nclass CSTree(bpy.types.NodeTree):\n bl_idname = 'CSTree'\n bl_label = \"CS Node Editor\"\n bl_icon = 'NODETREE'\n \n\nclass CSSocket(bpy.types.NodeSocket):\n bl_idname = 'CSSocket'\n bl_label = \"CS Socket\"\n\n def draw(self, context, layout, node, text):\n layout.label(text=text)\n\n def draw_color(self, context, node):\n return (1.0, 0.8, 0.4, 1.0)\n\n\nclass CSSocketInterface(bpy.types.NodeSocketInterface):\n bl_idname = \"CSSocketInterface\"\n bl_socket_idname = \"CSSocket\"\n bl_label = \"CS Socket\"\n\n def draw_color(self, context):\n return (1.0, 0.8, 0.4, 1.0)\n\n def draw(self, context, layout):\n pass\n\n\nclass CSNode(bpy.types.Node):\n bl_idname = 'CSNode'\n bl_label = \"Node\"\n\n def init(self, context):\n self.inputs.new('CSSocket', name='Input1')\n\n\nclass CSNodeGroup(bpy.types.NodeCustomGroup):\n bl_idname = 'CSNodeGroup'\n bl_label = 'Node Group'\n bl_icon = 'OUTLINER_OB_EMPTY'\n\n def init(self, context):\n self.node_tree = bpy.data.node_groups.new('CSNodeGroup', 'CSTree')\n nodes = self.node_tree.nodes\n inputnode = nodes.new('NodeGroupInput')\n\n\ndef make_group(context):\n space_data = context.space_data\n node_tree = space_data.node_tree\n selected_nodes = context.selected_nodes\n node_group = node_tree.nodes.new(\"CSNodeGroup\")\n node_group_tree = node_group.node_tree\n input_group = node_group_tree.nodes['Group Input']\n \n new_node = node_group_tree.nodes.new(\"CSNode\")\n\n to_socket = new_node.inputs[0]\n from_socket = input_group.outputs.new(to_socket.bl_idname, to_socket.name)\n node_group_tree.links.new(input=from_socket, output=to_socket)\n \n\nclass CSMakeNodeGroupOperator(bpy.types.Operator):\n bl_idname = \"crowd.cs_make_group\"\n bl_label = \"CS Make Group\"\n \n @classmethod\n def poll(cls, context):\n space_data = context.space_data\n\n if not (space_data.type == 'NODE_EDITOR'\n and space_data.tree_type == 'CSTree'\n and space_data.node_tree is not None):\n return False\n\n return True\n \n def execute(self, context):\n node_group = make_group(context)\n return {'FINISHED'}\n\n\ndef register():\n bpy.utils.register_class(CSTree)\n bpy.utils.register_class(CSSocket)\n bpy.utils.register_class(CSNode)\n bpy.utils.register_class(CSNodeGroup)\n bpy.utils.register_class(CSMakeNodeGroupOperator)\n\ndef unregister():\n bpy.utils.unregister_class(CSTree)\n bpy.utils.unregister_class(CSSocket)\n bpy.utils.unregister_class(CSNode)\n bpy.utils.unregister_class(CSNodeGroup)\n bpy.utils.unregister_class(CSMakeNodeGroupOperator)\n\nif __name__ ==\"__main__\":\n register()\n\n```\n\n* execute script\n* open CS Node Editor\n* create new node tree\n* Search for \"CS Make Group\" operator\n* Select to \"CSNodeGroup\" tree\n* Open side panel (N), Group tab\n* Add new input socket of `CS Socket type`\n* Check console for stack trace\n\nHaving a custom node socket in the side panel also creates an exception when drawing the input list:\n```\nPython: Traceback (most recent call last):\n File \"/home/jeroen/blender-git/build_linux/bin/3.0/scripts/startup/bl_ui/space_node.py\", line 772, in draw\n self.draw_socket_list(context, \"IN\", \"inputs\", \"active_input\")\n File \"/home/jeroen/blender-git/build_linux/bin/3.0/scripts/startup/bl_ui/space_node.py\", line 757, in draw_socket_list\n active_socket.draw(context, layout)\nAttributeError: 'NodeSocketInterface' object has no attribute 'draw'\n```", "Blender crashes with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n", "Sculpt: mask cut and fill can`t hold tubes\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\nBug or limitation/flaw?\n[untitled.blend](untitled.blend)\n[2020-01-17_19-12-26.mp4](2020-01-17_19-12-26.mp4)", "Request for Telugu Translation of Blender \nI want to translate blender into my native language. Telugu. Can anybody help in this regard. I can translate the words but somebody has to tell me what to translate and how it works. Kindly somebody guide me or tell the developers.. ", "Hitting 'Escape' while editing a shortcut enters that key on Windows, while on linux it cancels edition\nWindows 7 64bits, nvidia gt540m CUDA 2GB, Intel i7 2GHz, 8GB ram\n\nBroken: 2.75 c6b042b\n\n\nWhen i do a search of a shortcut, and then if i want to assign a new value and then cancel, the tab disappear.\n\nBlender User Preferences > Input > Search by key-binding \"Ctrl Tab\" > Show key map and property of any tab > Clic on \"type of event\" to change the value > Press Esc to cancel > the tab disappear.\n", "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", "2 out of 6 bytes produced by BLI_rng_get_char_n() are predictable\nOperating system: Kubuntu Linux 20.04 LTS\n\nBroken: current master @ 9fe6854a93\nWorked: didn't check with older versions\n\n`BLI_rng_get_char_n()` seems to produce predictable bytes, regardless of the seed used.\n\nRun this program a few times, and take note of the fact that the seed changes on every run, but the magenta columns stay the same between runs.\n[P2390: (An Untitled Masterwork)](P2390.txt)\n```c\n\n#include \"BLI_rand.h\"\n\n#include <stdio.h>\n#include <stdlib.h>\n#include <string.h>\n#include <time.h>\n\nstatic struct RNG *rng = NULL;\nstatic inline void maybe_initialise_rng(void);\nstatic void free_rng(void);\nvoid generate_random(void);\n\nint main(void)\n{\n for (int i = 0; i < 10; ++i) {\n generate_random();\n }\n return 0;\n}\n\nvoid generate_random()\n{\n maybe_initialise_rng();\n\n uint8_t buffer[36];\n BLI_rng_get_char_n(rng, (char *)buffer, sizeof(buffer));\n for (int index = 0; index < (int)sizeof(buffer); index++) {\n if (index % 6 == 0) {\n printf(\"\\033[95m\");\n }\n printf(\"%02x \", buffer[index]);\n if ((index - 1) % 6 == 0) {\n printf(\"\\033[0m\");\n }\n }\n printf(\"\\n\");\n}\n\nstatic void free_rng()\n{\n BLI_rng_free(rng);\n rng = NULL;\n}\n\nstatic inline void maybe_initialise_rng()\n{\n if (rng != NULL) {\n return;\n }\n\n struct timespec ts;\n\n timespec_get(&ts, TIME_UTC);\n unsigned int seed = (ts.tv_nsec >> 32) ^ (ts.tv_nsec & 0xFFFFFFFF);\n rng = BLI_rng_new_srandom(seed);\n srand(seed);\n fprintf(stderr, \"%s: RNG allocating, seeding with %u\\n\", __func__, seed);\n atexit(free_rng);\n}\n```\n\n\nI compiled this with `g++ -Wall -std=c++17 -o rng_test rng_test.cc -I ./source/blender/blenlib/ ../build_linux/lib/{libbf_blenlib.a,libbf_intern_guardedalloc.a}`, but I've seen the same behaviour using it to generate random bytes for generating UUIDs within Blender, so this shouldn't be caused by my simplified compilation options.\n\nThis is a screenshot of the output I get on my machine (screenshotted so that the highlighted colums are maintained)\n\n\n\n-------------------\n\n# Proposed Solution\n\nFixing this issue would break a lot of things in existing files (e.g. layout of particles or hair, or patterns of procedural textures, etc.). Since there is no versioning possible here, this issue could be fixed in two steps:\n\n- Rename current broken API e.g. with a `_deprecated` prefix, but keep using it everywhere it is currently used in code.\n- Add a new API with proper behavior.\n- Use the new API everywhere it is possible without breaking compatibility, and also for new code.\n- Wait for the next compatibility-breaking release (Blender 4.0) to switch the whole existing code to the new API. ", "Text Object -> Edit Mode, Many Short-cuts Showing Here & There, But Not Working \nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: AMD Radeon HD 8400 / R3 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1065.0\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (Probably Never)\n\n\nFor Text Object -> Many Short-cuts are showing in e.g. menus but not working. e.g. T (Tool Shelf), N (Numeric Pane) e.t.c\n\n\n\n\n*Wait:* I am checking a list the all short-cuts which are not working...", "Tests: fix script_load_keymap hierarchy test\nOperating system: verified Win32/Win64/Linux64/Mac didn't test Linux32\nGraphics card: N/A\n\nBroken: 2f77175fecc7\nWorked: \n\n\n`script_load_keymap` is passing on all platforms, however looking a little closer at the output, it really should not have passed by the looks of it.\n\nWindows\n```\n[HANDLER_OUTPUT] \n Start 38: script_load_keymap\n\n[HANDLER_VERBOSE_OUTPUT] \n\n38: Test command: D:\\a\\1\\build_windows_Release_x64_vc15_Release\\bin\\Release\\blender.exe \"--background\" \"-noaudio\" \"--factory-startup\" \"--python\" \"D:/a/1/s/tests/python/bl_keymap_completeness.py\"\n\n38: Test timeout computed to be: 10000000\n38: Blender 2.80 (sub 74) (hash d30f72dfd8ac built Wed 06/19/2019 10:55 PM)\n38: Unable to create directory C:\\Users\\VssAdministrator/.thumbnails/large/\n38: Unable to create directory C:\\Users\\VssAdministrator/.thumbnails/fail/blender/\n38: found bundled python: D:\\a\\1\\build_windows_Release_x64_vc15_Release\\bin\\Release\\2.80\\python\n38: Traceback (most recent call last):\n38: File \"<string>\", line 1, in <module>\n38: File \"D:/a/1/s/tests/python/bl_keymap_completeness.py\", line 90, in <module>\n38: main()\n38: File \"D:/a/1/s/tests/python/bl_keymap_completeness.py\", line 80, in main\n38: err = check_maps()\n38: File \"D:/a/1/s/tests/python/bl_keymap_completeness.py\", line 52, in check_maps\n38: for km_id in sorted(test):\n38: TypeError: '<' not supported between instances of 'function' and 'function'\n38: Keymaps that are in 'bl_keymap_utils.keymap_hierarchy' but not blender\n38: \n38: Blender quit\n[HANDLER_OUTPUT] \n 38/103 Test #38: script_load_keymap ..................\n Passed 1.15 sec```\n\nMac\n```\n2019-06-19T23:14:58.8907830Z Start 38: script_load_keymap\n2019-06-19T23:14:58.8909090Z \n2019-06-19T23:14:58.8909990Z 38: Test command: /Users/vsts/agent/2.153.2/work/1/s/build/bin/blender.app/Contents/MacOS/blender \"--background\" \"-noaudio\" \"--factory-startup\" \"--python\" \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\"\n2019-06-19T23:14:58.8910100Z 38: Test timeout computed to be: 10000000\n2019-06-19T23:14:58.9466020Z 38: Blender 2.80 (sub 74) (hash d30f72dfd8ac built 2019-06-19 23:13:34)\n2019-06-19T23:14:59.0865090Z 38: found bundled python: /Users/vsts/agent/2.153.2/work/1/s/build/bin/blender.app/Contents/Resources/2.80/python\n2019-06-19T23:14:59.7974200Z 38: Traceback (most recent call last):\n2019-06-19T23:14:59.7974580Z 38: File \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\", line 90, in <module>\n2019-06-19T23:14:59.7974830Z 38: main()\n2019-06-19T23:14:59.7975000Z 38: File \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\", line 80, in main\n2019-06-19T23:14:59.7975190Z 38: err = check_maps()\n2019-06-19T23:14:59.7975270Z 38: File \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\", line 52, in check_maps\n2019-06-19T23:14:59.7975320Z 38: for km_id in sorted(test):\n2019-06-19T23:14:59.7976280Z 38: TypeError: '<' not supported between instances of 'function' and 'str'\n2019-06-19T23:14:59.7976740Z 38: Keymaps that are in 'bl_keymap_utils.keymap_hierarchy' but not blender\n2019-06-19T23:14:59.8211820Z 38: \n2019-06-19T23:14:59.8212080Z 38: Blender quit\n2019-06-19T23:14:59.8264730Z 38/103 Test #38: script_load_keymap .................. Passed 0.94 sec\n```\n\nLinux\n```\n2019-06-19T22:40:21.3651709Z Start 38: script_load_keymap\n2019-06-19T22:40:21.3651763Z \n2019-06-19T22:40:21.3652247Z 38: Test command: /home/vsts/work/1/build/bin/blender \"--background\" \"-noaudio\" \"--factory-startup\" \"--python\" \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\"\n2019-06-19T22:40:21.3652639Z 38: Test timeout computed to be: 10000000\n2019-06-19T22:40:21.3853468Z 38: Blender 2.80 (sub 74) (hash d30f72dfd8ac built 2019-06-19 22:31:01)\n2019-06-19T22:40:21.4068327Z 38: found bundled python: /home/vsts/work/1/build/bin/2.80/python\n2019-06-19T22:40:22.0448958Z 38: Traceback (most recent call last):\n2019-06-19T22:40:22.0449067Z 38: File \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\", line 90, in <module>\n2019-06-19T22:40:22.0449108Z 38: main()\n2019-06-19T22:40:22.0449150Z 38: File \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\", line 80, in main\n2019-06-19T22:40:22.0449213Z 38: err = check_maps()\n2019-06-19T22:40:22.0449255Z 38: File \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\", line 52, in check_maps\n2019-06-19T22:40:22.0449294Z 38: for km_id in sorted(test):\n2019-06-19T22:40:22.0450043Z 38: TypeError: '<' not supported between instances of 'function' and 'function'\n2019-06-19T22:40:22.0450290Z 38: Keymaps that are in 'bl_keymap_utils.keymap_hierarchy' but not blender\n2019-06-19T22:40:22.0677065Z 38: \n2019-06-19T22:40:22.0677122Z 38: Blender quit\n2019-06-19T22:40:22.0718362Z 38/103 Test #38: script_load_keymap .................. Passed 0.71 sec\n2019-06-19T22:40:22.0720194Z test 39\n```\n\nbonus weirdness:\n \nWin64 and Linux report \n> TypeError: '<' not supported between instances of 'function' and 'function'\n\n\nwhile Mac and win32 report \n> TypeError: '<' not supported between instances of 'function' and 'str'\n\n\ngiven all builds are of the identical commit and use identical versions of all deps, it's \"kinda weird\" \n\n\nrun the `script_load_keymap` test", "USD import: investigate texture color space conversion issue\n\n@brurpo Reported the following issue:\n\n> When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb.\n> Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space.\n> Is there a workaround for this, or is this planned?\n\n\nI'll be looking into this.\n\n\n", "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!", "Crash creating \"position\" attribute with the wrong type while in Edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: 3.5.0 and 3.6.0 Alpha\nWorked:\n\nWhile in Edit mode, attempting to create an attribute called `\"position\"` that has type not set to `\"FLOAT_VECTOR\"` will crash Blender.\n\nI couldn't get any other attributes to crash when added while in Edit mode.\nCreating the `\"position\"` attribute with the correct type, but incorrect domain does not cause a crash either.\n\nI can't imagine a use case for users wanting to do this, but it came up while I was determining the extent of 107228 and isn't really the same issue.\n\n1. Select a mesh object\n1. Enter Edit Mode\n1. Either:\n 1. Run `bpy.context.object.data.attributes.new(\"position\", \"FLOAT\", \"POINT\")` from the Python Console\n 1. Create a new attribute called \"position\" using the `bpy.ops.geometry.attribute_add` operator and set the `Data Type` to anything other than `Vector`: " ]

[ "can't type Chinese in\nOperating system: Linux-5.13.13-hardened1-1-hardened-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01\n\nBroken: version: 3.0.0 Alpha\nWorked: seems none on Arch Linux. other IME, Linux distribution and Windows may be working\n\nOS: Arch Linux\nIME: [RIME ]() with `fcitx-rime`\n- `fcitx version: 4.2.9.7`\nsimilar: #91103, #55998, #87578\nwhen typed, an error appears in terminal:\n```\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x6acb3716bd80 0x6acb67436d00\n```\nand nothing inputs in\n\n- select a Chinese IME, and type in a text box\n\n", "Cannot enter any characters in Ubuntu 20.04\nOperating system: Linux-5.11.0-37-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 2.93.4\n\n\n\n\n\nError message in terminal : \n\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fbd2e6c6a80 0x7fbd52bffbc0\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fbd2e6c6a80 0x7fbd52bffbc0\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fbd2e6c6a80 0x7fbd52bffbc0\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fbd2e6c6a80 0x7fbd52bffbc0\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fbd2e6c6a80 0x7fbd52bffbc0\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n\n\n\nI tried version 2.83.18, which can be entered in the input box, but can't use shortcut keys.\n\n\n\n\n\n", "Cannot use Chinese input or Japanese input\nOperating system: Linux-5.4.0-70-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Beta\nWorked: 2.92 ([#issuecomment-224988](87578#issuecomment-224988), [#issuecomment-225000](87578#issuecomment-225000))\n\nCannot use Chinese input or Japanese input\n\nWhen I use Chinese or Japanese input, I get a warning like this on the console \n\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fca129c0900 0x7fca36c513c0\n\n" ]

[ "Two Shader to RGB nodes fed from the same BSDF : one produces black result\nOperating system: OSX 10.15.7 / Windows 10\nGraphics card: Geforce GT650M / Geforce 2060\n\n3.6.0\n\nThis should be a white cube:\n\n\n\nOpen the blender file...\n\nHere a additional screenshot, see that If I use two Principled BSDF's instead of one (with the same settings...), then the problem is 'fixed'.\n\n\n\n", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)", "Add option to re-use or duplicate data for the Current File asset library\nAgreed on this alternative to [D12752: Asset Browser: Hide Import Types menu for \"Current File\" asset library](D12752). Currently dragging in data from the *Current File* asset library always reuses the existing ID. The option to duplicate the data could be quite useful and make it explicit what dragging in the asset will do.", "Random vertices light up as if they were selected (but they're not) when I select one vertice at a time\nOperating system: Linux-5.4.0-7634-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83.0\n\n\n- See the GIF above (sorry my mouse cursor didn't get recorded :(\n- so, in short, when I select one vertex and then select another, random vertices light up as if they're selected but they're not. Really annoying.\n- this happened to me in 2.82a as well (but only in Linux, not in Windows)\n\n- load factory settings\n- subdivide the default cube 10 times, add subsurf modifier (CTRL+2), shade smooth\n- in EDIT mode, duplicate the mesh 6 or so times\n- select one vertex, select another vertex, the glitch seems to happen (like in the GIF above)\n\n**BLEND**\n[mesh_glitches_bugreport.blend](mesh_glitches_bugreport.blend)\n\n", "Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.5.0\n\nif I change the offset (or start frame) of the sequence in the shader editor, I would expect it to also change in the image editor or wherever I am using the same image sequence, otherwise it causes discrepancies and buggy viewport display (since we dont know which offset is displayed in the viewport). \n\nJust change the offset of 1 of the 3 displayed image sequence settings displayed... the other 2 won't follow.\n\nCycles does this fine btw.", "Incorrect shading on Intel HD 6000\nOperating system: Mac OS Catalina 10.15.3 (latest as of 13/02/2020), Windows 10 1909 (Bootcamp)\nGraphics card: Intel HD 6000\nCPU: Intel Core i5-5350U\nHardware: MacBook Air 2017\n\nBroken: 2.81a, 2.82\n\nProblems with shader of Auto-Eye add-on on Intel HD 6000, although on creator's machine works fine (I emailed him and he suggested it's a blender bug).\nBUT it's not only Mac OS problem! Also tested on Windows (via bootcamp) -- it crashed (on Mac OS it continue working at least).\n\nCreator's machine specs (where it works fine):\nIntel Core i7-4790 CPU @ 3.60GHz × 4\nGeForce GTX 1060 6GB\n\nJust open .blend file, make sure it's EEVEE render/look dev mode, test it with Mac OS or Windows and Intel HD card.\n\nAttaching file for testing and screenshots -- first two is how shaders looks broken, and third how it should approximately look, but with shader (right now it's only color output or flat texture output)\nBroken 1\n\nBroken 2\n\nHow it should like like(with shader enabled (BUT right now it's only color/flat texture output)\n\n\n[iris_only.blend](iris_only.blend)", "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.", "`bpy.context.space_data.overlay.grid_scale` returns inconsistent view3D grid scale in multi-view\nOperating system: win 10\nGraphics card: RTX 3090\n\nBroken: This was observed in 3.5 alpha but I don't think that is relevant \nWorked: N/A\n\n`bpy.context.space_data.overlay.grid_scale` does not apply to multi-view functionally, and any interaction with the 3D navigation sphere only effects the main window portion of multi-view.\n\nSee attached video for a demonstration of some of the odd behavior.\nSee attached blend to reproduce the error.\n\nEnter multi-grid view: **ctrl+alt+q** (mismatched transform grid) The main window is top right.\nClick any axis sphere in any 3D view that isn't the top right quadrant, only the main window transforms.\nYou will also notice that the main window also inherits the grid scale of the multi-view windows.\n\nPlaces to look maybe? [A](overlay_grid.cc#L86) [B](space_view3d)\n\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "Eevee: 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.", "Fix big LIghtCache restriction\nAs reported in #78529 saving big lightcache is impossible due to blocksize restriction.\n\nFor now we restrict the lightcache size that can be written to disk but it would be better to slice the huge textures to avoid such limitation.\n\nHowever this needs some refactors in GPUTextures namely the need of a properly exposed `glTexSubImage2D` and `glTexSubImage3D`.", "Blender 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", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "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.", "Regression: When making a collection real, curves with depth in the collection are instantiated twice\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.2.0\nBroken: 3.0\nWorked: 2.93\n\nCaused by b9febb54a4\n\nwhen making a collection real, curves where geometry/bevel/depth is not zero are created twice.\ncurves that do not have this property set are only created once.\n\n- open the attached file\n[curves_file.blend](curves_file.blend)\n- select the collection instance\n- object -> apply -> make instances real\n\n**What should happen**\n- every object of the collection appears once\n\n**What happens**\n- the \"BezierCurveWithDepth\" appears twice in the hierachy\n\n\nthis also is the case, when exporting the instanced collection, without making it real\n" ]

[ "Duplicated previews for Matcaps and HDRI's if config folder is present\nWindows 10 x64, AMD Radeon R9 390\n\nBroken: Every 2.8 version\nWorked: (optional)\n\nWhen the user creates a config folder in the root folder containing Blender 2.8 all of the matcap and world preview images show up as duplicates.\n\n\nExtract Blender 2.8 (any version) to a folder on your computer -> Create a \"config\" folder inside the \"2.80\" folder as you would when creating a portable version of Blender -> Start Blender and open up the shading window in the 3D view and select a matcap/studio \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.", "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", "popup window call operator will crash blender\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0 Beta\n\nThis script is use to check the active material, it can be run correct in the main window, but not popup window(change the pref window to node editor)\n```\nimport bpy\n\nbpy.ops.screen.userpref_show(\"INVOKE_AREA\")\narea = bpy.context.window_manager.windows[-1].screen.areas[0]\n\n\narea.type = 'NODE_EDITOR'\nflip_header = True\narea.ui_type = 'ShaderNodeTree'\narea.spaces[0].node_tree = bpy.data.materials['Material'].node_tree\n\nfor region in area.regions:\n if region.type == 'HEADER':\n with bpy.context.temp_override(area=area, region=region):\n if flip_header: bpy.ops.screen.region_flip('INVOKE_DEFAULT') # this line will not\n\n if region.type == 'WINDOW':\n with bpy.context.temp_override(area=area, region=region):\n bpy.ops.node.view_all(\"INVOKE_AREA\") # this line will report context error\n```\n\n- Open .blend file\n- Execute script\n[#98491.blend](T98491.blend)\n\n\n\n", "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", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Crash when rendering animation\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.1\n\nBlender crash when rendering an animation\n\nIn an attempt to simplify my rendering of multiple scenes, I added an additional scene to a blend file with no objects itself. Its purpose is to be a place to put multiple *Render Layer* nodes in its compositor for all the other scenes in the file. In other words I hit \"Render\" when on that special scene and all other scenes are rendered in one go. Running this render as a single image works fine. Running render animation crashes after one frame.\n\nMy actual file has 7 scenes to be rendered. But to help demonstrate and reproduce this, I have simplified the file to just two scenes:-\n\"*Scene 1*\" is a simple scene containing a cube and a camera. Rendering this scene directly, works fine as still image or animation.\n\"*Render all*\" is a second scene that has no objects of its own (just a camera because my render farm seems to insist upon that). This scene is set to not be rendered (\"*Use for Rendering*\" unticked). However it's compositor has a *Render Layers* object which looks at *Scene 1* and which is connected to a *File output* node.\n\n\n[crash-test3.blend](crash-test3.blend)\n\nOpen file and render animation.", "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", "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", "Cycles HIP device crash on rendering on latest AMD Adrenaline Driver\nOperating system: Windows 11 Pro for Workstation\nGraphics card: AMD Radeon RX 6750XT (Driver: AMD Adrenaline 23.7.1, 23.7.2 23.8.1 23.9.1)\n\nBroken: 3.6.1 LTS (On latest driver)\nWorked: 3.6.1 LTS (On old driver: AMD Adrenaline 23.5.2)\n\nAfter synchronizing objects, Blender crash\nBut render the default cube scene Blender works well even using 23.7.1 driver\n\nBased on the default startup or an attached .blend file (as simple as possible).\nScene is from Blender official demo file: \nbarbershop_interior/\nCrash log file: \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)", "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.", "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.", "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" ]

[ "Regression: World shader setup crashes Blender in rendered view\nOperating system: macOS-12.6-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.3\n\nBroken: version: 3.4.0 Alpha\nWorked: N/A\nFirst bad commit 697b447c20\n\nWhen in rendered view, a particular material setup in the world shader will crash Blender immediately.\n\n1. With Blender in factory settings, switch to the shading tab\n2. Switch to rendered view in the viewport\n3. Switch to 'World' in the shader editor\n4. Add the following setup to the world shader:\n5. Connect 'result' from the Mix node to 'surface' on the world output node\n6. Blender immediately crashes\n\n[crash.blend](crash.blend)" ]

[ "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", "The tools panel suddenly disappears in engraving mode.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro K620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\n\nBroken: version: 2.93.0\n\n\n\n\nIn the engraving mode, use the blank key to call the tools panel may suddenly disappear.\n\nMy native language text↓↓↓↓\n\n在雕刻模式，使用空白鍵呼叫　tools 面板會有突然消失的可能。\n\n\n\n\n\n1. Set KeyMap>Spacebar Action>Tools\n2. Select any object and enter sculpt mode.\n3. Press the blank key to call the tools panel. At this time, the panel will suddenly disappear. (Error generation)\n4. Move the mouse arbitrarily\n5. Press the space button again to call the tools panel. At this time, the panel will suddenly disappear. (Error occurs again)\n\nOther additional tests:\n\n1. The panel disappears (when an error occurs), do not move the mouse, press the blank key again, and it will appear normally\n\n2. When it appears normally, as long as you move the mouse and press the blank key, an error will occur, but there is one exception, which is simply moving the mouse horizontally so that the panel appears in the second position, the selected brush and slide The overlapping position of the mouse is exactly the same as the last time, the error will not occur (image)\n\n3. In the object mode, everything is normal, I think it should be operated like the object mode.\n\nMy native language text↓↓↓↓\n\n1.設定 KeyMap >Spacebar Action>Tools\n2.選擇任意物體，進入sculpt模式。\n3.按空白鍵呼叫tools面板。這時候面板會突然消失。(錯誤產生)\n4.任意移動滑鼠\n5.再次按空白鍵呼叫tools面板。這時候面板會突然消失。(再次錯誤產生)\n\n其他額外測試 :\n\n1.面板消失(錯誤產生時)，滑鼠不要動，再按一次空白鍵，就可以正常出現\n\n2.當正常出現後，只要有移動滑鼠，再按空白鍵就會發生錯誤，但有一個時候例外，就是單純水平移動滑鼠，讓第二個位置出現面板時，選取的筆刷與滑鼠重疊的位置和上一次一模一樣，錯誤就不會發生 (圖片)\n\n3.在物體模式，一切正常，我認為應該操作起來要像物體模式這樣。\n\n\n\n", "Issues with Fluid sim INSIDE objects\nOperating system: Win 10\nGraphics card: Twin GTX 1070\n\nBroken: 2.92\nWorked: 2.91\n\n**Fluid sim inside properly meshed objects does not work at all**\n- Create a tube with a curb or a Cylinder,\n- add a solidify modifier and apply it,\n- put a icosphere and downscale it to fit inside the tube,\n- keep icosphere selected and go to Object -> Quick Effects -> Quick Liquid.\n- scale the domain to fit everything inside.\n- Use tube as effector (planar or not does not work either way)\n- Try to bake a sim.\nAll settings that used to work in 2.93 and 2.91 do not work AT ALL in 2.92. Looks like it considers the mesh as a closed object.\n\nThanks in advance", "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", "Eevee 'Principled Normal' connected to 'Normal Map' node is disabling 'Displacement'\nOperating system: Win 10\nGraphics card: 2x1080Ti\n\nBroken: blender-2.91.2-windows64, blender-2.93.0-420f538fadfd-windows64\nNever worked as long as I remember\n\nBasically connecting normal map to principled shader is disabling any displacement map connected to the output. Just unplugging normal from principled turning it on. I don't know if its a bug or is it intentional \n\nNormal and displacement plugged in - displacement not working\n\nNormal unplugged - displacement working\n\n\n- Open attached file\n- Compare the result in Eevee with Cycles\n[bump_test2.blend](bump_test2.blend)", "GHOST/Wayland Support\nGHOST/Wayland support has been committed to master and is enabled for daily builds, this task is an overview of the remaining TODO's. \n\nNote that these could be expanded into their own tasks, listing here for now.\n\n**Library Linking**\n\n- [x] dynamically load libwayland (e58e023e1a)\n\n**Integration**\n\n- [ ] Support display server reconnecting (new feature, not yet supported by main-line MESA), see [KWIN/Restarting](Restarting)\n- [ ] IME (text input) support (see: [text-input-unstable-v3](text-input-unstable-v3)), See: [D17030: [WIP] initial GHOST/Wayland IME support](D17030)\n- [x] Primary clipboard support b0eff51fb7\n\n\n**Input Devices**\n\n* [x] #104272 Touch-pad support for detecting inverted (natural) scroll events 98272e5bb24b865380ad580ce0354ccacb0fa52d (depends on Wayland v1.22 release).\n- [x] Tablet support (pressure sensitivity, angle), 97f894881c\n- [x] NDOF (3D mouse) support 8841bd9660 \n- [x] Detectable key repeat events (`GHOST_TEventKeyData.is_repeat`).\n- [x] #98793 (Wayland clamps cursor movement failes with gnome-shell (fixed up-stream)), up-stream bug in gnome-shell, worked around in Blender.\n- [x] #76429 (GHOST/Wayland event's don't correspond to physical keys)\n- [x] #77311 (Mouse cursor stays in-place with Ghost/Wayland for operators that grab cursor input)\n- [x] High resolution track-pad scroll events 30d9a6245f\n- [x] Touch-pad gesture support (zoom, swipe, rotate.. etc). *lower priority, not supported by Blender under X11.* 8bb211a771\n\n\n**Display**\n\n- [x] Support for DPI detection (`GHOST_GetDPIHint`) 2770010224\n- [x] Support fractional scaling (`fractional-scale-v1`) cde99075e87032d99d986182e98d9c367b22d417\n\n**Windowing**\n\n- [x] Support activating windows 3071ec486bffd0fef180f221a85f0b15f07b7950\n- [x] Support dialog windows (so they're always in-front `GHOST_CreateDialogWindow`, respecting parent windows).\n- [x] #98612 (Window Decorations Not Present on GNOME - Wayland) 29755e1df8\n\n**OpenGL**\n\n- [x] Switch from GLEW to libepoxy, to support dynamic loading of either `libOpenGL.so` or `libGL.so`, patch: [D15291](D15291) (see [D12034](D12034)#312834).\n- [x] #98462 (Save Screenshot (glReadPixels) fails under Wayland)\n- [ ] Enable EGL by default for X11 (This is trivial at this point. Just remove the `USE_EGL` ifdefs in `GHOST_SystemX11.cpp` and `GHOST_WindowX11.cpp`)\n- [ ] Support `libOpenGL.so` and EGL in OpenSubdiv and USD `glLoader`\n\n\n----\n\n**Limitations**\n\nWayland has constraints that might not be practical to work around.\n\n- [ ] #102985 (Wayland: Unable to lower windows)\n- [ ] #98928 (Wayland: Unable to access window position, finding the window under the cursor doesn't work)\n- [ ] #100276 (Wayland: Windows reset when reloaded on a multi-monitor configuration)\n- [ ] Window decorations look out of place (libdecor) see, #101176 and this [merge-request ](43).\n\n**Bugs**\n\n- [x] #100855 (GHOST/Wayland: Terminal Ctrl-C closes the window while Python is running) *Low priority, needs further investigation.*\n- [ ] #103059 (GHOST/Wayland: Huge cursor when using a graphics tablet in KDE) *Low priority, needs further investigation.*\n- [ ] #102999 ([Wayland] Incorrect UI scaling on high-resolution screen under GNOME 42.5 w/ fractional scaling) *Fixed in GNOME 43, not clear how Blender would workaround the bug.*\n\n**Bugs with LibDecor**\n\n- [ ] #109194 Window decoration size doesn't match Blender window size.\n- [ ] #108308 Crash on startup with LibDecor on Wayland.\n- [ ] #107797 Resizing window causes crash on Wayland.\n\n**Bugs with GPU Drivers**\n\n- NVidia\n\n - #110327 Only 3D View-port region is transparent on Wayland (NVidia + Nouveau)\n\n**Bugs with Other Components**\n\nHere are issues that are noticeable with Blender.\n\n- [ ] Gnome-shell doesn't scale custom cursors with Hi-DPI displays: 1215\n- [ ] Gnome-shell doesn't receive tablet input for new windows #107778 2658\n- [ ] #98927 (Cursor input \"low resolution\" with Hi-DPI in gnome-shell), reported to mutter: 2311", "Grease pencil eraser settings not loaded on startup when using ctrl+LMB with the Draw tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 2.90.0\n\nWhen first opening a blend file, your eraser settings are set to default when using ctrl+LMB with the draw tool, and only update after switching to the eraser tool and using it.\n\n\n- Open attached file (the Stroke object is selected and the Draw tool activated in Draw mode).\n- Draw a line\n- Erase part of the line using the same tool but with Ctrl selected. Notice how it behaves as if the `\"Eraser Soft\"` brush is used. \n- Switch to the Eraser tool, erase part of the line. Notice how it behaves according to the specified Brush: `\"Eraser Point\"`. \n- Switch back to Draw tool, and hold down ctrl to erase another part of the line, it should now start behaving like the `\"Eraser Point\"` brush.\n\n[eraser bug.blend](eraser_bug.blend)\n\n", "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "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.", "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.", "The SHIFT key, mapped on my graphic tablet is not working in Blender 2.80\nOperating system: Windows 10\nGraphics card: NVidia GeForce GTX 1070\n\nBroken: 2.80 25-12-2018\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nI own a Huion NEW 1060 PLUS 8192 graphics tablet. One of my keys is mapped as SHIFT, but Blender doesn't recognize it at all. As one of the pen keys is mapped as the Middle Mouse Button.\nAnother key on the tablet is mapped as CTRL, another as ALT etc. and they all work with the MMB on the pen, but the SHIFT key is not recognizable to Blender. I can zoom, I can rotate, I can change views but i cannot pan nor select multiple objects. Basically, everything that is connected to the SHIFT key is dead.\nBlender recognizes the keyboard SHIFT key, as well as a mapped SHIFT shortcut on the mouse, but not on the tablet.\nAll around the OS and in Rhino, Photoshop, Illustrator, the Shift key from my tablet is working perfectly, but inside Blender no.\n\nOh, and this is the first time I'm trying 2.8. \nEverything works fine in 2.79.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "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", "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", "Texturing with anchored type stroke\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.51.06\n\nBroken: version: 2.91.0 Alpha\n\nTexture paint with stroke set to anchored while using texture significantly slows down blender up to non responsive state and crash while paint texture is larger than 2k.\n\n[Texture pain stroke ty[e anchored.blend](Texture_pain_stroke_ty_e_anchored.blend)\n", "Particle hair simulation not working\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.93.4\nWorked: unknown\n\nI modeled particle-hair and try to make it dynamic, for whatever reason I cannot make it to work and sometimes Blender crashes.\n\n[Test.blend](Test.blend)\n\n[Test.crash.txt](Test.crash.txt) \n\nIf I try another simple particle-hair system on the-same object it does work. \n\nTry to get the hair in attached file to simulate." ]

[ "Huion Windows Ink no presure\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.35\n\nBroken: version: \n- 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0d7\n- 2.91.0 Beta, branch: master, commit date: 2020-11-13 00:36, hash: 2e08500d047e\n- 2.92.0 Alpha, branch: master, commit date: 2020-11-14 08:44, hash: a3ce05d00e\n\n**Description of error**\n- Pen pressure doesn't work with Windows Ink.\nIn Krita pen pressure works fine, the problem is only in Blender\n- Win tab works fine for version 2.90.1 and 2.91, for 2.92 pen buttons don't work\n- Pen tablet: Huion Inspiroy Ink H320M\n\n**Attach**\n[WmPWxaAnRK.mp4](WmPWxaAnRK.mp4)\n\n\n\nKrita with Win Ink\n\n" ]

[ "GN: Delete Geometry node hides edges in some cases\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.2.0 Alpha\n\nHard to describe this one more abstract..\n\nI start with a mesh line primitive (0,0,0) (0,1,0) and extrude it **n** times along **x** to get a grid.\nNow I try to delete all points with a distance from the **y** axis greater than **d** \nWhenever **d** lies between the first and the last extrusion, the edges of the starting primitive are not displayed.\nIt shows up in the spreadsheet however and reappears if I apply the modifier and tab into edit mode and back \n\n[2022-02-05 19-27-50.mp4](2022-02-05_19-27-50.mp4)\n[del_geo_node.blend](del_geo_node.blend)\n\n", "Imported SVG dimensions are incorrect after scaling and undo\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2070\n\nBroken: 2.93.1\nWorked: 2.80 also has this issue, the older versions are not working on my computer.\n\nImported SVG dimensions are incorrect after scaling and undo. After toggling edit mode this issue can't be reproduced anymore.\n\nSeems to be caused by `BKE_nurb_minmax` because `use_radius` is true\n\n\n\n- Import svg file (as curve, not GP)\n- Open side panel > Item tab, note initial dimensions\n- Scale imported object\n- Undo scale\nDimensions are incorrect.", "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", "Edit Dyntopo Detail Size operator is not working with all methods.\nOperating system: Ubuntu 18.04\nGraphics card:\n\nBroken: master #e7dc3c91ad82\nWorked: 2.90\n\nEdit Dyntopo Detail Size operator was recently replaced to have a better gizmo.\nThat only works with Constant Detailing method.\n\nShift D is doing nothing when Relative or Brush detailing method are used.\nThat is a regression. It is pertinent to change the size for those methods, too.\n\nProbably, gizmo should work differently for a Brush Method. But, at least, shortcut should allow to change Detail Size like in 2.90. \n\n\n\nIssue in Master :\nEnter into Sculpt Mode.\nEnable Dyntopo mode.\nPress Shift D. Nothing happens.\nChange Detail Method from Relative to Constant. \nPress Shift D. New Gizmo is available.\nChange Detail Method from Constant to Brush.\nPress Shift D. Nothing happens. \n\nRepeat same steps In 2.90 :\nCircle gizmo is adapted to used method.\nRelative method is relative to screen. So, circle does not go above a certain limit.\nConstant/Manual method is relative to World Space. Size of Circle is not limited.\nBrush Method is relative brush size. Gizmo is showing a percentage.\n", "Cannot set the Color attribute to display an object through Geometry Nodes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: version: 3.4.1\n\nbehavior changed in 6514bb05ea\n\nUsing the \"Store Named Attribute\" node setting the Attribute \"Col\" in geometry nodes, no longer sets the Vertexcolor of an object procedurally. When the Curve is converted to mesh and then the created \"Col\" Vertexcolor attribute is clicked, the colors show up.\n\nIn 3.4 and below this would override the vertexcolor attribute in \"realtime\" without converting the curve to mesh.\n\nOn a Curve Object, add a geometry node\n- create \"Store Named Attribute\"\n- set the \"Name\" to \"Col\"\n- change the color\n- Set the Viewport shading to color \"Attribute\" (seeattached Images) to view the result\n\nAttached file with example setup that used to overwrite the vertexcolor in 3.4.1, but no longer does in 3.5.1\n\n", "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", "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.", "Geometry Nodes does not work with Rigid Body correctly\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.5.1\n\nI have seen that Geometry Nodes does not work with Rigid Body correctly.\n\nI join you and example with two flags and two dominoes pieces.\n[Bug Gemoetry Nodes and Rigid Body 1.blend](attachment)\n\nA flag traditionally rotates on the \"Z\" axis and pushes the domino piece.\nThe other flag uses the geometry nodes to rotate and instead of pushing the domino, it through it.\n\n\nThe Geometry Nodes only did a 'Transform Geometry' to rotate the flag.\n\nI opened the issue on https://blender.stackexchange.com/ and no one could did it work. \nI don't know if is a bug or that it still not deployed.\n\nI hope this is helpful and that you can fix it.\n\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", "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "Metaball particles are handled inconsistently in Geometry Nodes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725\n\nBroken: version: 3.4.0 Alpha\nWorked: (n/a)\n\nMetaball rendered via particles are handled inconsistently in Geometry Nodes. It seems only mesh related nodes are generally working well with them.\n\nI wasn't sure about reporting this as a bug, because I assume that compatibility with the particle system is probably not intended use case. I guess ability to access metaball particles at all is an unintended bonus from eaa87101cd5a? I'd argue that if this can be easily \"fixed\" it will open up some interesting use cases before actual simulation/physics nodes arrive, but this is a borderline feature request and I guess developers will decide if this is worth to look at at this point.\n\n\n[MetaballParticles.blend](MetaballParticles.blend)\n[MetaballParticles.mp4](MetaballParticles.mp4)", "Multi-type sockets (int, float, ...) for compact nodes\nNeed a solution for how to:\n* Automatically change socket type based on what is dragged.\n* How to change a socket that supports multiple input types.\n\nA good example is the Switch node\n\nNote: This doesn't account for nodes where we need to switch between attribute and value.\n", "Nodes to convert between cartesian/spherical coordinates\nThere should be nodes to convert between spherical and cartesian coordinates in a standardized way.\n\nThis point came up when discussing [D12746](D12746) .\n\nThey are multiple design aspects to be figured out:\n- Node layout\n- Naming and Scope\n- Units\n- Value Ranges", "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", "GPencil: Screen-space stroke size incorrect\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTS 450/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.92.0 Alpha\nWorked: none found\n\n**Description**\n\nWhen drawing a stroke with a defined pixel size and stroke-thickness-space is set to screen space, the radius of the drawn stroke should measure the set pixel size. This is not the case. The strokes radius measures half the size.\n\n**Steps to reproduce**\n\n - Create a grease pencil object\n - Set the stroke-thickness-space to screen space in objects grease pencil settings\n - Set the brush size to 100px\n - Draw a single dot.\n - Print the screen\n - Measure the dot size in any image editing app.\n # You will see that the radius of measures 50px and the diameter measures 100px. Instead of 100px and 200px respectively.\n\nThis issue can be further seen by trying to change the brush size using the `f` key. The brush size cursor is drawn at the correct size but is double the size of the stroke.\n\n**Investigations**\n\nThis relates to my original report #82707 wherein I thought the cursor size was incorrect. I have now had time to review the code enough to understand how the cursor is drawn; and how the brush size is defined and passed to the rendering engine.\n\nI have confirmed that the brush size takes the following path.\n\nBrush.size user setting: RADIUS → bGPDstroke.thickness: RADIUS → gpencil_vert.glsl thickness: RADIUS\n\n*Simplified for explanation purposes. Path steps missing.*\n\nI originally thought thickness was defined as a diameter but this is not the case.\n\nI also thought this would be a noticeable fix but I haven’t found where the issue lie yet so I thought I would report again. \n\nNote: When drawing a stroke with stroke-thickness-space set to world space the stroke is mapped to the users screen correctly. When world space is used a stroke with a brush size of 2000px is drawn with a radius of 1m in world space as defined internally. \n\n[Bug-GPencil-Screen-Space-Stroke-Size-Incorrect-Report-VID.mp4](Bug-GPencil-Screen-Space-Stroke-Size-Incorrect-Report-VID.mp4)\n" ]

[ "Node values for sizing remains in metric even with imperial selected\nOperating system: Win 10\nGraphics card: 3080\n\n3.0.0\n\nI’m trying to create a grid at a specific size with a specific number of divisions in each direction.\n\nHowever, I’m not sure how Blender is calculating sizes, since what I thought would work as numeric inputs (values, to allow fractional input) is translating to a setting of 1/3 of what it should be.\n\nIn the picture below, the cube in the center is 1’. I thought I could use 1.0 in the value input and arrive at the same size, but it’s… weird.\n\n\n\n\nFWIW it appears the input remains in Blender default metric units. Here is a view with a setting of “1” which appears to be 1 meter (39.4 inches)\n\n\n\nIf the input is removed, the units are correct:\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Geometry Nodes Integer not same as World scale units\nOperating system: Win10 Pro\nGraphics card: ROG RTX 2080ti\n\n3.1\nBroken: Geometry Nodes Integer Node coded at 1m, will not use Imperial units even when Imperial units selected in World Properties\nWorked: Never that I know of.\n\nWhen using Imperial units and resizing a Geometry Nodes Mesh Primitive Size field using the Integer Node, 1 is equal to 1 meter, not 1 foot.\n\nAdd cube, add Geometry Nodes tree, add Grid (or any) Mesh Primitive, insert Grid Mesh Primitive output to Group Output, add Integer Node and insert output into input of Size field for Grid Mesh Primitive, change to 1, observe size in Properties (N) Panel and size is 3' 3.4\" (1m) and not 1'.\n\nThank you.", "Blender Unit System counter-intuition in Geometry nodes and Displacement Modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.2.0 Alpha\nWorked: Never worked.\n\nWhen the length unit been set to \"millimeter\" in scene unit, every node that generates a value/vector output defaults to take the user input as \"meters\".\nTake a example: when using a set position node to lift up vertexs 1mm, it's intuitive for human to type in 1 when the scene unit been set to \"millimeter\".\nThis problem also happends to the displacement modifer's \"strength\" value.\n\n\nTry the blend file attached.\n[blender unit counter intuition.blend](blender_unit_counter_intuition.blend)" ]

[ "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)", "Vertex flickering on high grid density mesh \n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen a relatively high grid density is reached the vertices flicker\n2.81 does not have such problems\nThe method of creating a dense grid does not make a difference\nlrehEGrTkCXMvQ\n\n\nOn default cube, tab. (edit mode)\nright click on cube, subdivide. \nadjust last operation, cuts = 20. shake mouse to see glitches.\n {[F8414482](Скриншот_16-03-2020_133135.png), layout = inline}{[F8414484](Скриншот_16-03-2020_133204.png), layout = inline}\nvideo: [F8414488](Видео_14-03-2020_23_11_01.mp4)", "Vertex Paint Viewport Overlays stencil mask not working\nplatform: Windows-10-10.0.19042-SP0\nGraphics card: 1080\n\nBroken: 3.1.0 Alpha \n```\n commit date: 2021-11-14 00:26 hash: 7e82c840b7a4\n build date: 2021-11-15, 00:51:48\n```\n\nWorked: Has'nt worked for ages\n\nGo to vertex paint mode, select some polys on a model.\nGo to overlay options/vertexpaint/stencil mask opacity the slider does nothing to unselected polys overlay.\n\n\n\n\n", "Alembic export animated vertex color exports only first frame vertex color\nDebian, Nvidia GTX 1080ti\n\nBroken: 2.78-58a0c275464 and the newest ones\n\nWhen you create an animated vertex color on a mesh with dynamic paint for example, you expect it to be written into alembic while exporting it with vertex colors checked, but instead you have only first frame vertex color baked in it.\n\n1. Open attached blend file\n2. Bake dynamic paint\n3. Export abc with vertex colors checked\n4. Import that abc file and have no animated vertex color\n\nI'm also attaching that abc file.\nDon't know if it's a bug or a thing to do, sorry.\n[alembic_anim_vertex_color.blend](alembic_anim_vertex_color.blend)\n[alembic_anim_vertex_color.abc](alembic_anim_vertex_color.abc)", "Viewport shading solid mode not displaying geometry nodes color attributes correctly\nOperating system: Win10\nGraphics card: 960m\n\nBroken: 3.5\nWorked: never\n\n\nWhen using geometry nodes to add color attributes, there are several situations where the viewport solid mode attribute option does not display the color attributes correctly.\n\nAs can be seen by this example. The first image shows a cube with a color attribute added. The geometry nodes setup adds a red color to the \"Color\" attribute. This all works as expected as can be seen in the viewport and the spreadsheet. \n\n\n\nIf a GN cube is added instead of the standard mesh cube (which has been bypassed by the switch node) then the color attribute is added as expected. This can be seen in the spreadsheet as to be the same as the previous screenshot for the color attribute. However, it is not being displayed in the viewport.\n\n\n\nThis is a problem seen with any procedural geometry made with just nodes. As a workaround, you can have a single vertex as the only \"real\" geometry and use a join node to join with any nodal procedural geometry. Strangely though, this has to be the first connection in the join node, and won't work if it is second. This can be seen by the next 2 images:\n\n\n\n\n\nA similar related case is that some mesh nodes will also make the viewport lose the displayed attribute. For instance, if you create a cube, add a GN modifier and add a dual mesh node to the chain, the color attribute is still there, but no longer displayed in the viewport. This happens with some nodes (like mesh to volume and back to mesh) but not others (like subdivide or extrude).\n\n\n\nThere is also a related issue that when exporting to obj or gltf the color attributes are not exported if they are not displayed in the viewport. If apply the GN modfier, you have to actually click on the color attribute in the properties panel to see it in the viewport or to be able to export it. \n\nOddly, the fbx exporter seems fine without applying the modifier. It also doesn't matter if the color attribute is on the vertices, or face corners, or if the color is float or byte color. The same issues happen regardless.\n\n", "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", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Geometry Attributes panel in Edit Mode (design pending)\nThis task is going to adding a unified panel for editing attributes of the selected element by value in edit mode. It makes users able to pass arbitrary per-element data to geometry nodes, opening up more possibilities for procedural modeling.\n\nAll data types (int, color etc.) should be supported. \nDomain supports should match selection modes in edit mode (eg. no face corner support for meshes). \n\n## Basic\nAttributes on the active element is listed in the side panel. \nItems are grouped by domain.\n\n\n## Multiple Selection\nfor float types (float, vector, 2d vector): \n* Show a mean value computed from all selected elements. \n* Button offsets values of all selected elements.\nfor other types: \n* If an active element with a matching domain exists, show the value of it.\n* Button only affects the value of the active element.\nFill operators are provided for batch editing. It fills current button value into all selected elements.\n\n", "Weight Paint Vertex Selection Display issue\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: never really, more on that below\n\nWhen in weight paint mode with\n* vertex selection enabled\n* show wire enabled\n\nedges will not be drawn within the selection\n\n\n**The odd part**\nClicking in an empty space will get the wires to show again, but keep the vertices selected. \nThat's a behaviour that has changed from 3.1.2 to 3.2.2\nPreviously it deselected the vertices but didn't draw the edges\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n* Open the attached blender file\n* you can see that edges are not drawn between selected vertices\n* click in an empty space (important to click, not click drag)\n* vertices stay selected but wires are drawn\n\n", "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!", "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 ", "Intersecting Meshes are not marked as overlapping anymore when selected\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.90.1\nWorked: 2.83.x\n\nIn blender 2.83.x Solid View intersecting objects had, if selected, the otherwise hidden parts shown in a more muted color when overlapping. with 2.90.x this is no longer the case. \nI hope this did not get removed intentional but is a missing feature.\n\nDuplicate the default Cube, move it a bit so that is still intersects with the first cube and confirm movement. \nWatch the outline in Solid View be the same color and thickness all around the mesh. \nin 2.83 while moving the white outline turned light grey when intersecting and the selected object outline turned a darker orange. This is very helpful for positioning elements.\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)", "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", "SpaceView3D.draw_handler_add with PRE_VIEW draw type does not result in visible draws\nOperating system: MacOS 11.6.3, Ubuntu 18.04 LTS (issue exists in both)\nGraphics card: Intel UHD 630, Nvidia Quadro RTX 400 (issue exists in both)\n\nBroken: 2.93 LTS, latest master (b626edd751d64b269da12ef8e774ced2836c3c9e)\nBroken: 2.83.0\nWorked: 2.82\n\nBroke between good 189e96ba68 and bad d95e9c7cf8\n\n1. Startup Blender\n2. Go to scripting tab and create a new script\n3. Copy \"Triangle with custom shader\" code from: gpu.html\n4. Change draw_type param in draw_handler_add from\n```\n'POST_VIEW'\n```\nto\n\n```\n'PRE_VIEW'\n```\n5. Run script.\n\nExpected behavior:\nThe drawn triangle is visible.\n\nActual behavior:\nThe drawn triangle is not visible.\n" ]

[ "UV Editor does not draw pinned selected UVs as pinned\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\nBroken: version: 2.91\nWorked: 2.90.1\nCaused by 4212b6528a\n\n\n\ndoes not display pin vertexes in UV when selected\nblender 2.91 blender 2.92\n\nselect\n\nblender 2.90.1\n\n\n" ]

[ "VSE Linked external scene with audio with input Sequencer only works if the scene is NOT also linked with input Camera\nOperating system: Linux-4.9.0-9-amd64-x86_64-with-debian-9.9 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 13.0.6\n\nBroken: version: 2.81 (sub 3)\nWorked: Haven't yet tried other versions.\n\nVSE: Linking external scene with audio with input Sequencer only works if the scene is NOT also linked with input Camera.\n\n1. Create file A with Scene-A and add audio to it on the VSE.\n2. Create file B\n3. From the VSE in file B, link the Scene-A from file A. Set it's input to \"Sequencer\". On file B, playing the strip will correctly play the sound from Scene-A.\n3. Duplicate (or re-instance) Scene-A on the VSE sequencer. If the Input is still \"Sequencer\", both clips will play the audio, as expected.\n4. Switch one of the Scene-A instances to use the Camera as input. \n\nExpected behaviour: \n\nWe should be able to both see the Camera strip and hear the Sequence strip for Scene-A\n\nActual behaviour:\n\nFor all the strips of Scene-A that are set to Input \"Sequencer\", the audio will stop playing.\n\nNote: I've determined that it is not that the audio crashes: other clips with sound on the sequencer keep playing normally.\n\nNote: If I delete the strip with Input Camera and leave only the input Sequencer strips, the problem will not go away, unless I save the file like this and \"revert\" to it.\n\nI cannot find a suitable work-around. In the video that I'm producing I need to edit local sound effects on the shot sequence, and incorporate it on the larger edit.\nI cannot, therefore, both see and hear my sequence on the host sequencer.\n\n\nIf a workaround is possible (that is not reconstruct and re-import the sounds on the original scene) I'd be a happy man :-)\nThanks!\n\n\n", "With FPS change, VSE does not change clip start frame\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\nAlso problem in 2.92, 3.3.2, 3.5 alpha\n\nWith a FPS change, VSE changes the duration of an audio clip but not the start frame and the clips become misaligned.\n\nBest seen with two clips starting at different frames. See images. In my example the audio clips are mono at 11025 Hz. (Seems video clips act the same way.)\n\n{[F14133157](24.png),size=full}\n{[F14133163](6.png),size=full}\n\nI know there are several somewhat related reports re: VSE and FPS. Hope not a duplicate.\n\nThanks!!! (for all the great work!)\n\n", "VSE: Frame Rate Base Rounding Leads To Vid / Audio Strips Out Of Sync by 1 Frame\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: since 3.0 until now in 3.6.1 hash 8bda729ef4dc\nWorked: 2.93.18\n\nIt looks like the same bug #21138 is reappearing in the 3.x series and since the bug report is 14 years old, I created a new one.\nOld bug report: 21138\n\nMy description:\nI have a lot of projects with 29.97fps (30000/1001) and those work correctly with Blender 2.9x but since Blender 3.0 all video clips are 1 frame shorter and my projects are a mess, because the frames in all clips are also shifted 1 frame !!\nIf I set the base to 1.0009 instead of 1.001 its all fine in the Timeline, but if I set 29.97 from the drop-down menu, all clips are 1 frame shorter and shifted.\nI have this also tested with videos without any audio and that makes no difference.\nThe audio length btw is alway correct.\nI also noticed that the trick with 1.0009 is not good, because this value is then transferred to the exported video and thats wrong!\n\nI think the problems in the following posts also have the same cause?\n[audio-is-1-frame-off](https://blender.stackexchange.com/questions/51650/audio-is-1-frame-off)\n[blender-3-0-vse-audio-and-video-out-of-sync-bug](https://blender.stackexchange.com/questions/250718/blender-3-0-vse-audio-and-video-out-of-sync-bug)\n\n", "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)", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "Crash when updating image pixel data through python API\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.0, 2.90\nWorked: N/A\n\nBlender crashes with apparent memory corruption, when image pixel data and previous are updated frequently with python script.\nStack traces give no obvious answer, i have seen it happen in depsgraph eval, node graph code, imbuf, etc.\n\n*Note: i could not reproduce this issue in debug mode so far, only release or RelWithDebInfo seems to work.*\n\n 1. Open attacehd file\n - Run the script\n - Make sure the scene properties are visible (it seems to only crash when displaying image previews).\n - Grab the default cube and wiggle it around to force depsgraph updates.\n - If it doesn't want to crash, re-open Blender, it seems to be quite random.\n\nI'm using a node group to access image data blocks, so they can be displayed in a panel as pointers. The code generates data to replace the image pixels as well as the preview.\nI have also tried running a timer and deferring pixel updates using a queue as suggested [here ](bpy.app.timers.html#use-a-timer-to-react-to-events-in-another-thread), just in case the depsgraph post update is somehow not safe, but this doesn't change anything substantially. The bug happens in both cases.\n\n[crashtest.blend](crashtest.blend)", "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.", "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", "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)", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Crash 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)", "Crashing and freezing when working on files with assets\nOperating system: macOS-12.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 580 1.2\n\nBroken: version: 3.5.0\n\nCrashing and freezing when working on files with assets\n\nif I open the demo file cube_diorama.blend the whole system freezes and either crashes or logs out needing to login again.\nevery blender crash a WindowsServer log is created.\n\n cube_diorama.blend never crashed in previous versions of blender for me.\n\n", "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", "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" ]

[ "VSE copy-pasting strip 2nd usage in a row with crashes Blender (and other clipboard/undo actions)\nOperating system: Windows 10 64-bit 1909 build 18363.778\nGraphics card: Nvidia GTX 1060 6GB & AMD Radeon 5700 flashed to XT firmware\n\nBroken: 2.83\nWorked: eaee2b411935^ (caused by eaee2b4119)\n\nControl-V Paste 2nd usage in a row with object selected crashes Blender to desktop\n\nPressing Control+C to copy a strip object in video editor. Then paste to a new copy. Then paste a second copy. Don't unselect pasted items. Results in crashed Blender. \n\nI've had this same issue occur when doing 2 undos in a row as well. \n\nHad it occur again after initial report submission but this time I had copied, pasted, copied initial object, pasted a second time successfully. But then pressing \"space\" to continue playback caused crash. \n\nWas able to complete and export the render as long as I was very careful to save before any possible affected actions (with 3 more crashes during editing). \n\nNotes: \n* Link to unlisted Youtube of crash session: Vsz5yQpni7U\n* Googled a few times trying to find replication but only found older (2018) reports with either no fix or stating fixed. \n* Attached: system-info.txt & .blend file\n* The blender window is on the monitor driven by the 5700 card. 1060 card is used for encoding and driving 2 side monitors. System-info.txt should show this detail but I have OpenCL disabled (was the first thing I tried to do when the crash happened, so it also occurs when OpenCL is also enabled). \n* This is a new download + install of Blender, just giving it a try as a free video editor, haven't been using Blender much since the 2.79 days and this PC didn't exist then\n\n[system-info.txt](system-info.txt)\n\n[test1.blend](test1.blend)\n" ]

[ "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", "Geometry Node Crash\nOperating system: macOS-11.6-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon HD - FirePro D500 1.2\n\nBroken: version: 3.6.2\n\nGeometry Node crash when I try to add a node to the default Cube.\n| Node Setup: | Crash Log: |\n| --- | --- |\n|||\n\n- open blender\n- open the geometry node workspace\n- With the default cube selected, add a new Geo Node setup\n- add a node using the menu or Shift A\n\nBlender crashes.\n\nIf I delete the cube, add a plane, and add the geo node to the plane, blender does not crash.\n\n", "Subdivision Surface Performance Degrades Markedly With Non-Quad Meshes\nOperating system: Windows 7 Pro X64\nGraphics card: Nvidia Geforce GTX 980 Ti\n\n\nBroken: Date: 2019-01-21\n```\n Hash: dd3f5186260e\n Branch: Blender 2.7 (although it's supposed to be a 2.80 Beta)\n```\n\n[OpenSubDiv_PerformanceBug.zip](OpenSubDiv_PerformanceBug.zip)\n\nSubdivision surfaces are fast and responsive in Edit mode *with all-quad meshes*, but very slow (~ 10x slower) with meshes comprised of triangles and quads.\n\n\nOpen the attached blend file and select **Cube.001**\n\nGo into Edit mode. Turn on Proportional Editing. Grab a point and move it - observe how responsive the viewport is with the all-quad mesh.\n\nGo back to Object Mode. Select **Cube**. Go back into Edit Mode. Grab a point and move it (with proportional editing still turned on) Observe how slow it is.\n\n", "Blender crashes instantly when trying to render with Cycles (HIP)\nOperating system: Windows 11\nGraphics card: AMD RX 6600 / Adrenalin 23.9.1\n\nBroken: Blender 3.4.x / 3.5.X / 3.6.2 / 4.0 Alpha\nWorked: 3.3.X\n\nBlender instantly crashes when trying to render with Cycles using HIP. Apparently only happens with files that have high number of polygons. New Project with cube doesn't crash. Using CPU doesn't crash.\nAlso, System preferences shows that I have 2 GPU units, but I have only one. It disables both when trying to disable a single one (idk if this is normal)\n\n", "Crash 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", "Regression: GPU subdivision - Mesh does not immediately count viewport statistics\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\n\nBroken: version: 3.3.0 Alpha\nWorked: blender-3.3.0-alpha+daily.`d095fcd6b417`\n\nI didn't do rigorous bisecting but I suspected this is caused by 163f6a17e4 so I tested with a daily build before it was committed.\n\nMesh does not immediately count in viewport statistics with GPU subdivision enabled.\n\n\n\n- Open startup file.\n- Add Subdivision Surface modifier to the cube\n- See the mesh is not counted towards viewport stats\n- Deselect the cube (or do some other action related to viewport display, for example, ticking viewport display options), and see now it is counted towards viewport stats\n", "Mesh related crash in add-on\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 780 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\n\nUsing an the operation connect spread in an addon is causing an EXCEPTION_ACCESS_VIOLATION. \n\n[blender.crash.txt](blender.crash.txt)\n\n```\nStack trace:\nblender.exe :0x00007FF7A109EC60 blender::deg::deg_graph_flush_updates\nblender.exe :0x00007FF7A1084AA0 DEG_evaluate_on_refresh\nblender.exe :0x00007FF79C983790 scene_graph_update_tagged\nblender.exe :0x00007FF79CB61510 wm_event_do_notifiers\nblender.exe :0x00007FF79CB4B550 WM_main\nblender.exe :0x00007FF79C7E2ED0 main\nblender.exe :0x00007FF7A16421A8 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEEB937020 BaseThreadInitThunk\nntdll.dll :0x00007FFEECA62630 RtlUserThreadStart\n```\n\nDownload [Forgotten Tools ](forgotten_tools_0_5_0.zip) use Connect spread on 2+ edges go to operation popup menu increase the cuts.\n\n[2021-06-20_00-26-23.mp4](2021-06-20_00-26-23.mp4)\n\n", "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "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)", "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", "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", "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```", "GPU subdivision: Wrong object's size when using subdivision surface modifier with GPU subdivision\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia Geforce GTX 660\n\nBroken: 3.1\nWorked: 3.0\n\nWhen GPU subdivision is activated, the object with subdivision surface doesn't show the correct size on the dimension section of the properties' sidebar.\n\nSelect the default cube.\nAdd Subdivision surface modifier\nOpen the properties' sidebar with N, the dimensions should be 1,68m (for X, Y and Z) but it shows 2,0m for all the axes. By deactivating the \"GPU subdivision\" the panel shows the correct dimensions.\n", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "Blender crashes when I try to subdivide my model\nOperating system: Windows 11 Pro 64-bit, 12th Gen Intel(R) Core(TM) i9-12900KF (24 CPUs), ~3.2GHz\nGraphics card: NIVIDIA GeForce RTX 3070 Ti\n\nBroken: 3.6, latest version\n\n\n\n- Open Blender, Open File\n- Go to Preferences, Turns off GPU Subdivision\n- Change to CUDA and tick Graphics Card Box\n- Goes to Modifier, Click Subdivision Surface, Processing, Crashes\n\nTo give a bit more context, my current model only has 160000 vertices which I think is quite little? But still it cannot subdivide and crashes whenever I click the subdivide option in modifiers.\n\n" ]

[ "Blender 3.2beta version adds Subdivision Surface, which crashes directly\nOperating system:Deepin 20.5 x86_64 Kernel: 5.17.3-amd64-desktop\nGraphics card:AMD Radeon RX 6600 XT \n\nBroken: version: 3.2.0 Beta（blender-3.2.0-beta+v32.f11dba88923f-linux）, branch: Daily, Commit date: 2022-05-04 19:23, Hash f11dba88923f\n\n\nBlender 3.2beta version adds Subdivision Surface, which crashes directly。[blender.crash.txt](blender.crash.txt)\n\n", "GPU Subdivision: Crash after opening particular files\nOperating system: Linux-5.15.0-27-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-27-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.2.0 Alpha\nWorked: 3.1\n\nCrash occurs when trying to open a file with GPU subdivision enabled\nCrash probably started to happen after library updates\n> In #97702#1349274, @DFair wrote:\n> So this was one of the more painful bisects, but it's related to a bump in dependencies for 3.2.x here T95206\n\n\n- Open blender (default scene)\n- Enable GPU subdivision\n- Load attached file\n\nHere is the output of `blender --debug-all `:\n[debug.txt](debug.txt)\n[3D-101-INSTALLATIONS.crash.txt](3D-101-INSTALLATIONS.crash.txt)\n[3D-101-BUILDING-MATERIALS.crash.txt](3D-101-BUILDING-MATERIALS.crash.txt)\n\nSample blend file that does not open\n[3D-101-BUILDING-MATERIALS.blend](3D-101-BUILDING-MATERIALS.blend)\n\nScreencast of the problem (GPU Subdivision)\n[Screencast from 2022-05-01 08:04:44 PM.webm](Screencast_from_2022-05-01_08_04_44_PM.webm)\n", "Blender 3.2.0 beta linux crashes with subdivision surface modifier\nOperating system: Linux-5.13.0-40-lowlatency-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 6800 XT (sienna_cichlid, LLVM 13.0.1, DRM 3.41, 5.13.0-40-lowlatency) AMD 4.6 (Core Profile) Mesa 22.0.0-devel\n\nBroken: version: 3.2.0 Beta\n\nBlender shuts down when using subdivision surface modifier (no issue with that on alpha version)\n\nJust apply subdivision surface modifier on any mesh (default cube for instance).\n\n" ]

[ "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Undo doesn't consider changes in nodetree when object is in edit and texture paint mode\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.79-3.4\n\nFor reference: this is due to this commit 4a08b974f4\nFrom the commit message:\n\"don't store undo steps for property changes in paint & edit modes.\"\n\nWhen in edit and texture paint mode, I can't undo changes, that I made in the shader editor. \n\n\n - Open .blend\n - Move some verts.\n - Change a shader node setting.\n - Press {key Ctrl Z}.\n # The verts move back, but the node setting remains.\n[#71895-undo-not-undoing-shader-nodes.blend](T71895-undo-not-undoing-shader-nodes.blend)", "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", "Properties don't update focus when copy/paste an object\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1, 3.1.2\nWorked: I don't know\n\nIf you **Copy/Paste** object with **Ctrl+C**, **Ctrl+V** the Property window will still have focus on the old object (although a new one is selected).\nIn this case, the **Duplicate** operation works correctly, the focus is on the new object (the one that is selected).\nReproduce on **Scene objects** and on **Nodes** in node editor. I think there are many more places.\n\n[filename700.mp4](filename700.mp4)\n[filename704.mp4](filename704.mp4)\n\nIn node editor\n1) Select any node.\n2) Copy and paste node with Ctrl+C/Ctrl+V.\n3) Change any properties, you can see that you are changing the previous object, although a new one is selected.\n\n", "Outliner Sorting and Dragdrop\nCurrently, the way you sort items in the Outliner is rather unclear.\n\nWe include this option in the Filter popover:\n\n\nBut when you disable this, you cannot re-order objects manually - instead they are displayed in the order of creation. \n\nAdditionally, this toggle only affects objects, not Collections, which are always manually sorted.\n\nWe can make this a lot clearer and more consistent, like so.\n\n - Replace the Sort Alphabetically toggle with an enum for with different sorting methods:\n\n - Make it apply to everything: Objects, Bones & Collections.\n - When set to Free, you can then freely re-organize both Collections and objects manually. \n\n---\n\nDragdrop is also closely related to sorting once we add custom sorting. We draw small black bars between items to indicate a sort dragdrop, and we shade the line dark when dropping into an item. We could improve on this.\n\nAlso, it would be good to allow object parenting without the shift modifier key.", "Outliner displays non existing Screens.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.3 26.20.13001.18009\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nOutliner displays non existing Screens.\n\nThey exist in default blender workspace, however opening any editor in separate window with Shift and closing that window will create same thing, they wont be removed after saving and reopening file either.\n\n\n", "Bevel gizmo is hidden when disabling Active Object gizmos\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.91.0 Alpha\nWorked: N/A\n\nThe bevel gizmo is hidden when disabling Active Object gizmos, even though the bevel gizmo is an *active tool* gizmo\n\n\n - Enter Edit Mode\n - Switch to the Bevel tool by clicking on the Bevel icon in the toolbar\n - Go to the Gizmos popover and disable Active Object gizmos\n - The Bevel gizmo disappears\n\n\n\n\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", "Sliders not being seamless overlap by sliders UI\nBroken: 3.3.0 from 2.8\nWorked: 2.79 All visibility icons hide behind sliders\n\nIf `bpy.context.space_data.show_sliders = True` and left panel is reduced, visibility eye icon hides under the slider each three rows .\n\n\n- Have more than two keyframes visible in Curves editor (it starts at index 1 and then it repeats its 4 loop).\n- Enable Show Sliders in {nav Graph Editor > View > - [ ] Show Sliders} (`bpy.context.space_data.show_sliders = True`)\n- Decrease the space of the the Source List Panel (Left Panel)\n\n[Sliders_Overlay_Visibility_Icon_Curves_Editor.blend](Sliders_Overlay_Visibility_Icon_Curves_Editor.blend)\n", "AutoDepth ignores texture transparency\nOperating system: Win 10 64-bit\nGraphics card: 980 Ti\n\nBroken: 2.93.4 LTS, 3.0 alpha (including current latest build)\nWorked: 2.79\n\nWhen navigating using mouse with auto-depth enabled, the full-transparent parts of textures should be ignored when picking the depth.\nThis worked correctly in 2.79, but 2.93 and the latest 3.0 alpha seem to ignore this.\n\n\nEnable Auto-Depth, create an object, assign it a material with some full-transparent texture, then try to zoom / pan using mouse with the cursor on it.\n[autodepth-transparent-issue.blend](autodepth-transparent-issue.blend)", "Blender 3.5 - Python - Excluding Collections that have child collections is not consistant\nOperating system: Linux-5.4.0-131-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.5.0 Alpha\nBroken : 3.2.1\n\nWe have a custom render manager which enables / disables collections on demand.\nIf you have a collection, that gets excluded via script, then included. all child collections get excluded and not re-included\n\n1. Open Attached blend file \n2. Toggle Collection on and off and Collection 2 on and off\n3. Notice how when Collection is toggled, Collection 2's exclusion is remembered, whether it is excluded or not\n4. Make sure Collection 2 is not excluded, and Collection 1 is excluded.\n5. Run Example script\n6. Notice how Collection 2 is now excluded\n\nThe expected behaviour, is that Collection 2 should remember what its previous state was, whether it was excluded or not. This is causing issues at render time when we are toggling collections on / off and objects are not rendering because of it.\n\n[bug.blend](bug.blend)\n\n", "Properties Editor Popover\nWith properties search and outliner to properties tab switching we need a place in the properties editor for various settings. These options may include:\n* Outliner Tab Switch. There isn't an automatic solution that works well enough, so an explicit toggle is needed. [Auto, Enabled, Disabled]. Auto will keep the current behavior of only switching tabs on shared borders\n* Property search: Full tooltip text search would be useful, but could make performance suffer so a toggle would be useful\n* Tab hiding. Some workspaces don't need to display certain tabs and they can be hidden by default", "Asset Browser - Current File doesn't place objects in active collection\nOperating system: Windows 11\nGraphics card: RTX 4070ti\n\nBroken: 3.5.0\nWorked: Supposedly never (tested 3.0-3.6)\n\nWhen adding an object into the scene from the Current File category in the Asset Browser, objects are placed into the same collection as the assets they originate from instead of the collection you are currently working in.\n\n- Move default cube into a new collection\n- Mark as asset\n- Ensure the scene collection is active, not the cube collection\n- Drag cube asset from Asset Browser Current File category into the scene\n- It will appear in the same collection as the asset reference object\n", "Dopesheet Display Hidden doesn't work property combined with Only Selected.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: Version 2.79b\n\n\nIn version 2.79 with the \"Selection Only\" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations.\n\nFrame 1:\nTurn off the object then Animate Disable in viewport,\nFrame 2:\nTurn on the object and animate Disable in viewport.\nOpen dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear.\n\n[Dopesheet_280.blend](Dopesheet_280.blend)\n[Dopesheet_279b.blend](Dopesheet_279b.blend)\n\n\n", "Copying scene unhides hidden collections\nWindows-10-10.0.16299 64 Bits\nGeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBlender 2.80 (sub 53)\n\n[hidden_collections_copy_scene_bug.blend](hidden_collections_copy_scene_bug.blend)\n\nOpen attached file. There are two hidden collections.\nMake a copy of the scene using either \"Link Object Data\" or \"Full Copy\".\nCollections in the newly created scene will be set to visible." ]

[ "Hidden Objects \"Unhide\" after making changes to Adjust Last Operation\nOperating system: Ubuntu Mate 20.04\nGraphics card: Nvidia GeForce GTX 850M\n\nBroken: 2.80-2.82- 2.90\nWorked: (optional)\n\nThe adjust last operation window un-hides any object hidden while it's open.\n\n\nOn default cube, hit {key S} scale it. \nThe Resize menu comes up, hide the cube in outliner.\nExpand the resize menu & change some setting.\nCube is unhidden. " ]

[ "Shrink/Fatten \"Offset Even\" can not be used as default\nThe \"Offset Even\" option is turned on by default for the Shrink/Fatten (Alt-S) tool. You can see this by opening user preferences, selecting the input tab and opening the Shrink/Fatten menu under the Mesh menu. However, if you use the tool, you'll see checking or unchecking this default option makes no difference. The tool always defaults to off.\n\nIt doesn't seem currently possible, even with custom coding, to have this option on by default. I disabled all transform modal map keys just to be sure they weren't interfering. They are not. I also tried changing the default key to something else (Ctrl-K). It seems nothing can be done to have this tool use \"Offset Even\" (i.e. even thickness) by default. ", "Gizmo shifting to different value after release with tablet input.\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\nWorked: 2.79 (haven't tested this extensively)\n\nWhen using a tablet to manipulate objects, the gizmo will often pop to a different location. A similar thing happens in the dopesheet when moving the playhead, it will pop to a different (usually very close) frame. I assume this is due to how the tablet input is being interpreted but after exploring and changing every setting I can find, the problem still persists to a certain degree. \n\nBasically, just select an object, choose the rotate tool (not the r shortcut) and use a tablet to rotate on an axis. I've attempted to record this issue in the attached video. [tablet issue.mp4](tablet_issue.mp4)\n\n", "VSE's selection not centred to images\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.1.0 Alpha\nWorked: Never\n\nWhen zooming in enough to a selected image's corner, it can be seen that the selection box (white rectangle) reaches outside the image itself. It also happens with a scaled down \"color\" strip.\n\n- Open a \"Video Editing\" workspace and add a \"Color\" strip\n- Scale it down and zoom to a corner\n- To better notice the issue, play with the resolution of the Preview (in Properties)\n\n\nNotes & thoughts:\n- The selection box (white box) is unresponsive to \"aspect ratio\" changes (in Properties)\n- The drifting of the image is somewhat annoying, and sticking the selection box to the image wouldn't fix this.\nSince I don't know how pixel alignment works in the preview, I'm not sure about this, but it may work to instead drift the canvas, leaving the image put like the selection box currently does. So sticking the image TO the selection box.", "Video Editing: Strip Offset Start/End not consistent with adjusting the strip handles\nOperating system: Win 10, 64bit\nGraphics card: no (CPU)\n\nBroken: (v 2.82a) and also (v 2.83 Alpha, Date 2020-03-18 17:16, Hash c9c08dc7c873)\n\nFrom the Manual:\nstrip.html\nStrip Offset Start/End [...] This is the same as adjusting the strip handles.\n\n\nHowever currently it is NOT really the same, which adds a lot of confusion to the already complicated concept that includes several offsets:\n\n\n\n**Detailed description of error**\n- Good: Extend the Strip using Handles: The Strip gets a helpful color code. The \"animated\" part is colored. The extended \"NOT animated / last frame repeated\" part is transparent.\n- Bug: Extend the Strip using Strip Offset: \"Animated\" and extended parts of the Strip get the same color.\n\n- Good: Shorten the Strip using Handles: Strip Offset is correctly calculated.\n- Bug: Extend the Strip using the Handles (or Extend *Keyboard E* or Slide *Keyboard S*): Strip Offset is incorrectly reset to 0.\n\n- Good: Handles: The Strip can not be shortened past the last \"animated\" frame.\n- Bug: Strip Offset: The Strip can be shortened, until no \"animated\" frame is left, and even further until the Duration becomes negative.\n- Bug: Using Slide *Keyboard S*, the \"animated\" frames can be moved completely outside the Strip. At least one \"animated\" frame should remain inside the Strip.\n\n**To further improve clarity, I would**\n- rename **Hold Offset Start/End** to **Trim Source Start/End**\n- change **Hold Offset Start/End tooltip** to \"Shortens the Strip by skipping frames at the start/end of the source\"\n- add **Strip Offset Start/End tooltip** to \"Extends the trimmed strip by repeating it's first/last frame or shortens it further\"\n- make **End** editable (it should do the same, as moving the right strip handle)\n- add **End tooltip** \"X position where the strip ends\"\n- change **Duration tooltip** \"The length of this strip after applying Trim and Strip Offset\"\n\n**If you feel very courageous**\n- change **Start** so that it points to the start of the Strip (currently it points to the first \"animated\" frame)\nI think, Blender heavily depends on **Start**, while it happily ignores Strip Offset Start and Strip Offset End. So, changing the internal meaning of **Start** likely makes a huge mess. However, maybe you can introduce and display a new variable \"display start\" or \"strip start\" instead, that does the trick, without messing too much with the internals.\n\nHappy Coding!", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "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", "Multi-Button Drag: not working properly for Object Dimensions\nWindows 7\n\nBroken: 2014-02-11\n\nMulti-Button Drag - D270 - doesn't work properly in N panel for Dimensions\n\nIf you drag over all 3, only X and Z change, Y remains unchanged. As mouse button is released, the first selected property will reset, only the last hovered is kept (and scale changed)", "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", "Constrained [on an axis] transform of an object far out of view can result in insanely high numbers\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\nWorked: never\n\nConstrained [on an axis] transform of an object far out of view can result in insanely high numbers\n\nThis file just contains a single cube 250m away from the origin:\n[#94105.blend](T94105.blend)\n- open file\n- hit {key G Y}\n- start moving the mouse\n- see values of 1000000000 m in the header\n\n**Original report**\n\nYour camera has to be close enough as in the attached video. Press G+Y and do a little move. The Cube starts to ignore modifiers and drastically increase Y-axis numeric value.\n[bug_10.mkv](bug_10.mkv)\n[bug_10.blend](bug_10.blend)", "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", "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", "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", "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", "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", "Geometry Nodes: HSV color circle has incorrect position\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\n*Input > Constant > Color* shows incorrect position compared to numerical edit or shader editor.\n\nOpen file, compare node representation of a color with position, when you numerically edit input color\n\n" ]

[ "Blender 2.8 - Pie menus are inaccurate\nSystem Information\nOperating system: Ubuntu 17.10\nGraphics card: GTX 1080\n\nBlender Version\nBroken: 168a6a4bfc13cbe5c2fb510607b9565de3eb9472\n\nPie menus are inaccurate\n\n1. Open Blender2.8\n2. go into edit mode\n3. tap .\n4. Try hovering over the 'Active Element Icon'\n" ]

[ "Sporadic boolean issues\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.2.0\nWorked: 3.0\n\nMeshes using the boolean modifier sporadically break in Blender 3.2.0, while they still worked in 3.0.\nThis would result in meshes that lack faces or even crash Blender\n\n\nUnfortunately I wasn't able to isolate the cause of the issue, as it seems to occur sporadically and randomly. What I have noticed is that sometimes meshes that were fine suddenly break once you enter exit edit mode.\n\n", "Running multiple instances of Cycles HIP ends in segfault\nOperating system: Windows 10\nGraphics card: 2x Radeon W6800 32GB\n\nBroken: 3.0.0, 3788003cdaeb, master, 2021-11-30\nWorked: Never\n\nWhen I have 2 instances of Cycles rendering using HIP at the same time on a particular production scene, one instance will crash with the following error: \n\n\n```\n...\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.57 | Mem:1469.81M, Peak:1469.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Furniture_Roughness.png\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.70 | Mem:1533.81M, Peak:1533.81M | Scene, View Layer | Updating Images | Loading Metal02_nrm.jpg\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.73 | Mem:1569.81M, Peak:1569.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Objects_normal.png\nFra:441 Mem:9030.99M (Peak 9030.99M) | Time:00:21.73 | Mem:1570.69M, Peak:1570.69M | Scene, View Layer | Updating Images | Loading Tires_rough.png\nMalloc returns null: len=37748736 in Cycles Aligned Alloc, total 1149156740\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFED98C853D\nModule : amdhip64.dll\nThread : 00000734\n\n```\nI was unable to reproduce it in a simple scene or any commonly available demo scenes such as classroom or Barbarshop. And unfortunately I cannot share the particular scene that's causing the issue. But the scale of the scene that's crashing should easily fit onto the GPU vram three times.\n\nI've attached the crash report. If more info is needed I will try to create a dummy scene that show the same behavior.\n\n[Anim-A-Garage.crash.txt](Anim-A-Garage.crash.txt)", "Knife Tool when faces are exactly aligned (zero screen-space-area), get cut diagonally\nWindows 7 SP1\nGtx 770\n\nBroken: : Started at 2.72 until now 2.73a\nWorked: 2.71\n\n\nWhen > Knife Tool > Cut through > it will create a tri on other planes that is not projected ex. orthographic view + top\n\n\n\n\nVideo ( please download for High quality Drop Box )\n\n2.73a Version ( Heavy Plugin and Shortcut Keys )\n2.73_Modified.mp4?dl=1\n\n\n2.73a Restore Factory ( Deleted >Appdata > Blender foundation )\n[restored.mp4](restored.mp4)\n\n2.71\nknife is working as intended\n2.71.mp4?dl=0\n\n[TEST.blend](TEST.blend)\n\n\nQ> Hi i would like to ask if i should mind because it is normal function and a new feature of 2.72 and not a bug ?", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "Crash 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)", "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", "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "How to handle edit-mode face/edge select-modes without any face/edges.\nBased on this report #41562,\n\n----\n\nSimple example of the problem:\n\n- Add a Circle\n- Enter EditMode\n- Select Face Mode\n- Select All (AKey)\n- Grab *(Nothing happens)*\n\n----\n\nIf you have a mesh without faces in edit-mode and use face-select for example,\nQuite a lot of tools don't work usefully.\n*(same for edge select-mode on a mesh containing only vertices, but for purpose of discussion - just talking about faces for now).*\n\nLists of tools which fail when edges/vertices are selected but no faces exist.\n\n- Transform Grab/Rotate/Scale does nothing.\n- Extrude does nothing.\n- Inconsistent de-select-all verts and edges (AKey) - *(but border/circle/mouse select dont work).*\n- *...Likely others exist, off hand these are the ones I can find...*\n\nThere are some possible solutions.\n\n- Automatically switch out of face mode *(when entering edit-mode - doesn't solve problem completely since you can remove all faces while editing)*\n- Make tools support this configuration *(need to check how to support for each tool).*\n# Make tools report a warning when its not supported (or add support when it makes sense), *otherwise - assume users know what they're doing and not attempt to second-guess their actions.*\n\nFor this design issue, Id like to come to some agreement on a good way to handle this case.\n\n----\n\nSome things to consider regarding automatic select-mode switching:\n\n- Users may temporarily remove all faces, so changing select-modes automatic for the users could disrupt their workflow.\n- Switching modes automatically could break scripts (and generally give unpredictable behavior).\n- Checking if the mesh has faces isn't really reliable since you may have hidden faces which is like having no faces from the users POV.", "blender crash itself while importing a dae (collide) file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nBroken: version: 2.82 and all versions in between then and now\nWorked: n/a\n\nHi, I'm using blender version 3.3 on a windows 10 downloaded on steam.\n\nwhen i try to import dae files, blender crashes itself and shuts down\n(this only happens with some dae files, not all and the ones who crash are not to big ).\n\nI tried to search with powershell to find the problem and I got this:\n\nError: EXCEPTION_ACCESS_VIOLATION\n[bgr_darryls_ship_ground.dae](bgr_darryls_ship_ground.dae)\n\n```\nThe gh->hashfp function pointer is NULL (hasn't been initialized yet)\n\nblender.exe!ghash_keyhash(const GHash * gh, const void * key) Line 133\tC\nblender.exe!ghash_lookup_entry(const GHash * gh, const void * key) Line 411\tC\nblender.exe!BLI_ghash_lookup(const GHash * gh, const void * key) Line 736\tC\nblender.exe!BKE_armature_find_bone_name(bArmature * arm, const unsigned char * name) Line 601\tC\nblender.exe!ArmatureImporter::create_armature_bones(Main * bmain, std::vector<Object *,std::allocator<Object *>> & arm_objs) Line 478\tC++\nblender.exe!ArmatureImporter::make_armatures(bContext * C, std::vector<Object *,std::allocator<Object *>> & objects_to_scale) Line 826\tC++\nblender.exe!DocumentImporter::finish() Line 228\tC++\n[External Code]\t\nblender.exe!DocumentImporter::import() Line 127\tC++\n```\n", "Access violation in `vk_icdNegotiateLoaderICDInterfaceVersion` when putting computer to sleep.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.3 Release Candidate\nWorked: (3.6.2)\n\naccess violation when putting computer to sleep. crash log is created immediately after clicking sleep.\n\n\n1. launch blender.\n2. open a file\n3. save it\n4. put the computer to sleep\n\nEdited steps because it just happened when blender was launched normally. Wasn't saved this time, and was a different blend file.", "Blender crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "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", "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" ]

[ "Intersect Knife: Segmentation fault or incorrect behavior\nOperating system: win10\nGraphics card: gtx1060\n\nBroken: 2.79, master; 2.80, master\n\nSegmentation fault or incorrect behavior\n\n\n```\nNew plane\nOne vertical loop cut\nIndividual insert faces\n ```\n \n\n```\nSelect one inner rectangle\nShift + D\nRotate 90 degrees\nHorizontally scaled slightly\n``` \n\n\n```\nTwo inner rectangle added to selection\nShift + H\nCtrl + F\nSelect: Intersect (Knife)\n```\n\n\n\n**.blend file**\n[untitled.blend](untitled.blend)" ]

[ "Particle system behaves inconsistently in viewport and render when instance object visibility is disabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro [P2200](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.91.0 Beta\nWorked: The behavior was different in 2.80\n\nWhen the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.\n\n1. Open the default scene.\n2. Create another object (B).\n3. Create a particle system modifier on the default cube (A).\n4. Set Particle Settings to Hair (A).\n5. Set Render -> Render As to \"Object\" (A)\n6. Set the Instance Object to the other object (B).\n7. Disable the object (B) in viewport and render\n8. Render the scene, observe that the object has particles rendered\n[particle_visibility_bug.blend](particle_visibility_bug.blend)\n", "EEVEE macOS: visual glitching when using Tangent shader input on hair\nOperating system: macOS Big Sur 11.2.3\nGraphics card: AMD Radeon Pro 5500M 8 GB, Intel UHD Graphics 630 1536 MB\n\nBroken: 3.0.0 Alpha, e81533b25e6b, master, 2021-09-28\nWorked: Unknown\n\nAttempting to use the \"Tangent\" shader input on hair with EEVEE results in visual glitching and smearing in the viewport:\n[EEVEE Hair Tangent Bug example.mov](EEVEE_Hair_Tangent_Bug_example.mov)\n\nFurthermore, if the tangent input is used in a node tree with any BSDF nodes, the hair will fail to render at all, appearing checkered as if it were using holdout instead:\n\n\n\nI've tested on both Windows and macOS; **only macOS is affected**.\n\nA similar bug occurs with the Parametric input, however it's slightly different so I will open another report for that one.\n\n\nPart one: \n1. Add a particle system to the default cube, or any mesh\n2. In the particle settings set the type to Hair\n3. To visualise the hair more clearly: under Hair Shape, increase diameter scale to 0.1. Also, under Render Properties -> Hair, set the Hair Shape Type to \"Strip\"\n4. Add a material to the mesh if it doesn't already have one\n5. In the shader editor add a Geometry node\n6. Connect the \"Tangent\" input to the Surface port on the material output node\n7. Enter EEVEE Material Preview or Rendered mode and orbit the 3dview to see smearing and glitching\nPart two:\n8. Add a diffuse BSDF (or any BSDF) node\n9. Connect the tangent input to any port on the BSDF node.\n10. Render with F12. In the rendered image any hair strips appear checkered as if they were masked with holdout\n\nExample blend file below. Note: if the hair doesn't show up, toggle \"Regrow\" or any other option in the particle settings.\n[EEVEE Hair Tangent Bug.blend](EEVEE_Hair_Tangent_Bug.blend)", "Crash when sculpting with a texture, deleting the image of the texture and exiting sculpt mode\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: version: 3.4, 3.5, 3.6\nBroken: version: 3.3.3\nBroken: 3.1.0\nWorked: 3.0.1\nWorked: 2.93 LTS\n\nCaused by 9111ea78ac\n\nBlender crashes when a texture image is deleted and you exit sculpt mode.\n\nYou can test it inside the attached blend file. I basically just attached an image to a sculpting brush.\n\n1. Open the blend file below\n2. draw on the surface of the sphere\n3. delete the image inside the outliner\n4. exit sculpt mode\n\nCrash occurs because `item->image->runtime.cache_mutex` is null inside `BKE_image_pool_free`\n```\nStack trace:\nblender.exe :0x00007FF713D04C10 pthread_mutex_lock\nblender.exe :0x00007FF70E6EE880 BKE_image_pool_free\nblender.exe :0x00007FF70E6B5CF0 BKE_sculptsession_free\nblender.exe :0x00007FF70F1B67A0 ED_object_sculptmode_exit_ex\nblender.exe :0x00007FF70F1B85F0 sculpt_mode_toggle_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\nblender.exe :0x00007FF70E9528D0 wm_operator_call_internal\nblender.exe :0x00007FF70E955880 WM_operator_name_call_ptr\nblender.exe :0x00007FF70F171800 ED_object_mode_set_ex\nblender.exe :0x00007FF70F148710 object_mode_set_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\n```", "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 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.", "Cycles: tapering hair transparency fails in '3D Curves' mode [regression] (probably caused by embree)\nOperating system: Ubuntu 20 LTS and MacOS Mojave\nGraphics card: Quadro p2000\n\nBroken: 2.92 and latest 2.93.0 alpha 5f1f233dc97de34f6be0f51edd3cbf2d8247fbda\nWorked: 2.82a and 2.83.4\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nSetting a transparent BSDF shader to hair in 3D curves mode yields a visible error where parts of the hair are black.\nThis issue is visible in the viewport and at render time. It affects both CPU and GPU rendering.\n\nIn ribbons mode, transparency works almost as expected. I noticed that when hair strands overlap and they have transparency, they are not transparent but they take the background opaque color instead, so the hair strands below are \"covered\" with background color.\n\nembree\n\nbefore embree\n\n\n[#86500.blend](T86500.blend)\nOpen file and switch to rendered view\n\n---\n\nOriginal report:\n\nInitial setup in viewport: a cube with 20 hair strands:\n\n\nRender in version 2.83.4:\n\n\nRender in version 2.92+\n\n\n\nAttached is a .blend file example (so that you don't need to reproduce the steps below). [transparent_hair_curves_issue.blend](transparent_hair_curves_issue.blend)\nIf you run it on Blender 2.82a, rendering should show only a cube. Blender 2.92+ will show the issue.\n\nSteps:\n- Open a new default blender scene with a cube\n- Choose Cycles renderer\n- Under Render Properties > Hair, select 3D Curves\n- Add a hair particle system to it\n- Lower particle count to 10\n- Set segments to 5\n- Enable Hair Dynamics, play the timeline for a while until hair bends\n- Go to simulated frame 30 (just an example)\n- Scroll down in psys panel to Render, enable b-spline with steps 2\n- In Timing, set start to 0.361 (just for testing purpose)\n- In Hair Shape, set Diameter Root 0.5, Tip 1, Radius Scale 1.00\n- Render in viewport or to an image (same result)", "Hair from 2.79 messed up in 2.8 (modifiers prior to PSys and partially broken without 'Use Modifer Stack')\nOperating system:\nGraphics card:\n\nBroken: blender-2.80.0-git.dd3f5186260e-windows64\nWorked: 2.79b release\n\nHair particles made in blender 2.79 get messed up, when opend in 2.8. The hairs are pulled in direction of objects origin:\n\n\n[hairbug.blend](hairbug.blend)\n\nopen attached file in 2.80 (and in 2.79, to compare)\n\n---\nIt is maybe is related to T59587 .. i am not sure.", "Adding texture to particle emission density breaks particle simulation\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 74)\nWorked: (optional)\n\n\nPlease see attached file, after adding cloud texture and enabling Density in Texture influences, the simulated particles either stick to the surface or fly of into infinity as a group. \n\nOpen attached file and play animation, note some particles either sticking or a large group of particles incorrectly flying of.[particle_system_broken.blend](particle_system_broken.blend)\n\n", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "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", "Attribute Edit Mode\nThis is an extract from the now archived Vertex Color/Attribute Edit Design (#71947).\nThe design needs further investigation an discussion with the #geometry_nodes module.\n\n## Attribute Edit Mode\n\n\n\nAttribute Edit is intended to be a mode to modify and visualize any kind of data stored in mesh elements. Some use cases for it could be:\n\n- Editing IDs on face corners to modulate materials in a shader\n- Painting velocity vectors on vertices to guide a particle system\n- Editing the weights of a rig\n- Editing per face colors for low poly models without using textures\n- Setting custom values on edges for a motion graphics animation\n- Modifying mesh values for procedural modeling\n\nSome of these task could use a brush, but they don’t need a brush with artistic painting functionality. It does not make sense to edit the weights of a rig with a brush with wet paint and density noise.\n\nFurthermore, these task could take advantage of a mode with more control and precision tools than an artistic painting mode, like precise elements selection and data editing, controlled value interpolation…\n\nThe plan is to use the current Vertex Paint mode as a base implementation for this mode and start adding all necessary features during multiple releases. It already has quite some work done because most users were using it with these use cases in mind.\n\nThis task is not as detailed as the Sculpt/Paint mode, but it should be enough to have an idea of its purpose, use cases and design goal.\n\n### Tools\n\n**Simple brush tools**\n\nThe current Blender brush functionality is enough to support this kind of painting, if we consider painting changing the values of elements that are inside the cursor radius. We can reuse the current brush code for that.\n\n**Value interpolation tool**\n\nThis tool could produce controllable interpolations of an attribute between two mesh elements following the mesh topology. For example:\n - Select the base of a cone and assign the value of one \n- Select the top vertex of the cone and assign 0 \n- Let the tool generate the rest of the values across the cone surface\n\n**Mesh elements selection**\n\nAttribute paint should provide tools for selecting mesh elements and assign values directly to them. This provides much more control than a brush. This could be useful when working with low poly models, where you want to assign values like armature weights in a precise way.\n\n**Mesh element masking**\n\nWe can support a basic masking functionality for the brush that supports all mesh elements (not only vertices like the Sculpt/Paint mask). This can make easier some painting task.\n\n### Features\n\n**Data conversion operators**\n\nAttribute edit mode should provide a set of conversion tools to convert data between elements and other Blender data layers when possible. For example:\n\n- Convert a per vertex attribute to a per face corner attribute\n- Convert a per edge attribute to a vertex attribute averaging the\n```\n values\n```\n- Generate material slots from an ID attribute stored on faces\n- Generate an editable 2D vector attribute from an UV layer\n\n**Per face corner color data to sculpt/vertex color data**\n\nThis is a specific case of a conversion operator. Other conversion operators can be added in the future as we support more attribute types.\n\n**Internal attribute conversion**\n\nWe need to identify what element/attribute type conversion combinations are more frequent and design how they can work (usually averaging the values). For example\n\n- Converting an attribute from face corners to faces by averaging the\n```\n values of all the face corners in the face\n```\n- Converting from vertex to edges by averaging the value of the two\n```\n vertices of the edge\n```\n- Converting from vertex to face corners assigning the same vale of\n```\n the vertex to all the face corners that use that vertex\n```\n\n**Topology symmetry**\n\nWe could support editing operations with symmetry based on the mesh topology instead of mirroring the XYZ axis.\n\n**Attribute data type selection**\n\nThe use should be able to choose what kind of data he/she wants to edit and in which mesh element that data should be stored. For example\n\n- A float factor stored on faces\n- A vector stored on vertices\n- A color stored on face corners (Current supported MLoopCol)\n\nAll tools should be aware of the data type of the layer and behave accordingly.\n\n**Import/Export**\n\nIt should be possible to import and export meshes with different attributes in mesh elements. We need to check format compatibility.\n\n### Rendering\n\n**Attribute edit overlay**\n\nAs we can make assumptions that the attributes are colors, we need to render a configurable overlay to display the data in an appropriate way.\n\n**Attribute rendering mode selector**\n\nThe attribute rendering overlay should provide and UI to choose which rendering mode the user wants to render the data. This should include tools like a gradient editor, rendering two attributes at the same time, render vectors and randomly generated ID maps.\n\n**EEVEE/Cycles attribute node**\n\nThe current attribute nodes exposes MLoopCol and UVs to the render, which are both loop attributes. We need to investigate how to expose face, vertex and edge values.", "Particle system bug with texture influence\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: N/A.\n\nParticle system caching issue. \n\n1. Make a particle system with collider that kills particle. Add a cloud texture to influence it's density.\n2. Now bake.\n3. Now later when you increase or decrease size of the particle. the cache breaks. \n4. Some particle is starting to stay on collide serve instead of killing . And some particle floats around.", "Hair object - design proposal\n\nIMPORTANT: Please note that this document is subject to change and will most likely not represent the final product of the new hair object in Blender\n\n---\n\n**Reference links**\n\nHair object - project description\n#68981 (New curves object type)\nHair object - node design\n#78515 (Hair object - Node types design)\n\n---\n## Hair object design\n\n**Guide curves**\nThis is a list of guides in the hair object. \"myGuides\" in image example. On the same hair object there can be multiple guide curves (\"eyebrows\", \"hair\", \"eyelashes\" etc). Guide curves are the curves are what the user grooms with the particle brush. The guide curves are sourced into the node tree graph via an input node.\n\n**Growth mesh**\nThis is the mesh that the guide curves are attached to.\n\n**Node tree**\nThis is a slot that referers to the node tree containing the nodes for creating and deforming the instanced hair curves. See design task #78515 (Hair object - Node types design) for more info regarding hair object node design\n\n**Hair simulation properties**\nI don’t currently have a strong opinion about where to place simulation related controls/UI. Perhaps this could be integrated somehow with particle nodes? See example of **simulation influence node** in #78515 (Hair object - Node types design). We should check with @JacquesLucke, since he is working on particle nodes and physics.\n\n|||\n| -- | -- |\n\n\n\n---\n## Alembic cache\n\nReading curves from alembic file as hair is supposed to be implemented as noted in the project description #68981 . I've been going back and forth regarding if I think alembic settings should be placed in the Hair object UI or in the Input node in the node network. I ended up with the conclusion that alembic settings should be placed in the hair object node networks **input node**.\n\n\n{[F8664085](image.png), height = 400}\n\n\n---\n**Notes on guide curves geometry data**\n\nThis is likely relatable to \nT76659\n\nDeformed instances\nImagine the blue poly strip on the image to the left is a deformed instance along a guide curve. The goal is to have it conform to the normal of the surface of the growth mesh (head geometry). This type of workflow is important for creating hair for real time rendering (e.g games) or feathers for offline rendering\n\n{[F8664030](image.png), height = 400}\n\n\n\nSometimes the sampled normals from the surface is too noisy (ear area) and needs to be averaged based on neighboring guide curve vertex normals. The smoothing should propably be done with an operator that is triggered by the user.\n\n{[F8664033](image.png), height = 400}\n\n\n**Normal per guide curve vertex**\nTransfer normal vector from growth mesh surface (CYAN) to guide curve vertices. This normal vector is not used for shading, but for aligning tilt/twist of instances to the growth mesh surface. This is very important for creating hair cards for real time graphics/games.\n\nGuide curve vertices that does not get a ray hit from growth mesh surface can inherit normal vector from the closest guide curve vertex that got a ray hit (YELLOW). We could also use this normal vector to displace the guide curves along the normal of the growth mesh surface with the deform node that is described in the Hair object node design T78515\n\nIf transferring normal vectors from the growth mesh is slow, perhaps it’s a good idea to transfer normals with an operator that is run by the user when desired. I guess it’s important to note that we would not want normal transfer to happen post simulation\n\nIt seems likely that this task is related to storing custom data on hair vertices: #76659 (Geometry Attributes Design)\n\n\n\n---\n**Direction per guide curve vertex**\nAnother important vector to use would be the direction of the guide curve. The direction of the last guide curve vertex will need to be inherited from its closest neighbor. The direction could be used by the tilt for deformed instances and also, the deform node that is described here: #78515 (Hair object - Node types design)\n\n\n\n\n---\n## Tangent per guide curve vertex\n\nThe cross product of the transferred surface normal and guide curve direction would result in a tangent. One potential problem is that the transferred surface normal and guide curve direction could sometimes be almost aligned (eg when hair is pointing along the surface normal). I’m not sure how big of a problem that could be. In case the tangent is zero, perhaps it should just get some arbitrary vector? Perhaps pointing along the X-axis?\n\nThe tangent can be used by the deform node that is described here: #78515 (Hair object - Node types design)\n\n\n\n---\n\n## Operators\n\nIMPORTANT: Nodes are to be developed first, so operators will not be a first priority\n\n**select random**\nexisting operator that is extremely useful while grooming. Selects random hair/points \n\n\n**transfer normals from growth mesh**\nTransfer growth mesh normals to guide curves. Vertecies that does not get a ray hit to growth mesh should inherit from closest guide curve vertex on same guide curve. Normals on guide curves can be useful for aligning instanced mesh. Very important for real time hair (eg hair cards) or feathers in off line rendering\n\n\n\n\n\n**smooth guide curve normals**\nsometimes growth mesh normals might be pointing in a lot of different directions (close to an ear for example). Then smoothing out normals can be useful. This is very simililair to **smooth curve tilt** for curves\n\n{[F8664672](image.png), height = 150}\n\n\n\n**create guide curves from curves**\nUseful for interoperability between other softwares. I think it would be useful to rearrange vertex order per guide curve so that vertex index 0 is closest to growth mesh surface. Only the two ends of the curve needs to be sampled to determine which is closer to the growth mesh. This would be very useful for converting hair using old hair system to the new hair system\n\n{[F8664681](image.png), height = 400}\n\n**resample guide curves**\nBased on current selection. Change number of vertices per guide curve. Vertices should always be equally spaced. When going from a low amount of vertices to a higher amount, it might be needed to \"change curvature\" in order to avoid linear interpolation between each new vertex. The current operator **Rekey** does a very good job, but doesn't solve issues where hair vertices that is not evenly spaced per hair.\n\n{[F8664686](image.png), height = 200}\n\n**Create curves from hair nodes**\nConvert current hair node setup to curves. Useful for interoperability with other softwares. Current operator hides in the **particle system modifier**\n\n{[F8664691](image.png), height= 300}}\n\n\n**Tilt normal**\nTilt normal on selected guide curve vertices. Very similair to tilt operator for curves\n\n{[F8664702](image.png), height= 200}\n\n**select by length**\nusable for deleting/pruning very small hairs. Small hairs can sometimes be accidentally too short by using the \"cut brush\"\n\n{[F8664699](image.png), height= 200}\n\n\n**smooth length**\nsmooth length on selected guide curves by sampling surrounding guide curves. This is useful for making sure there are no guide curves that are shorter or longer than they should be\n\n{[F8664705](image.png), height = 200}\n", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n" ]

[ "Crash entering edit mode with particle system\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 399.07\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nhave a scene with a carpet (a plane with hair particle system). in rendered view (another window) entering in edit mode for that carpet blender crashes.\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)" ]

[ "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", "Asset spawns at Camera origin when in camera view\nOperating system: Microsoft Windows 10 Home\nGraphics card: GeForce RTX 2060\n\nBroken: (3.0.0, f1cca3055776, master, 2021-12-02 18:35 )\nWorked: N/A\n\n----------------------------------------------------\n\nCreate and mark asset. \nAdd camera move camera along Y axis away from world center. \nOpen asset browser and find your marked asset. \nGo into camera view, drag asset to viewport. \nAsset will lock to camera origin. \n\n--------------------------------------------------\n\nGo to front view, drag asset in, works as expected.\n\n----------------------------------------------------\n\n2D artist will want to work from the camera view for standardize production. In this example I used a grease pencil object but it can be replicated with 3D objects also. Thanks for looking at this. \n\n[2022-01-17 11-40-38.mp4](2022-01-17_11-40-38.mp4)\n", "Outline Selected is invisible in front of image empty in X-Ray mode\nOperating system: Linux-5.3.0-53-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83 (sub 17)\nWorked: 2.82a\n\nThe \"Outline Selected\" overlay is invisible in X-Ray mode where a selected mesh object is in front of an image empty,\nmaking the overlay useless in that area.\n\nLatest builds of Blender 2.83 and 2.90 are affected.\n\nIn the 3D Viewport:\n - Import an image as an empty (e.g. drag-and-drop in a jpg file)\n - Place a mesh object infront of the image and select it (e.g. the default cube)\n - Activate X-Ray mode (e.g. using Alt+Z)\n\nSee attached .blend file as example:\n[outline-selected-invisible.blend](outline-selected-invisible.blend)\n\n", "Using View Navigation in Camera View Causes Viewport View to Focus on World Origin\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: Never (2.79+)\n\nUsing view navigation (Shift+\") in camera view (Numpad 0) causes to lose the previous viewport view (Numpad 0 again) and it focuses world origin. \n\n1- Launch default Blender.\n2- Change your view to anywhere (For example zoom in to a vertex of the cube).\n3- Go in camera view (Numpad 0), use view navigation (Shift+\") and right click to cancel it (you can change view with left click as well, it doesn't matter).\n4- Go in viewport view (hit Numpad 0 again), notice that your previous view changed (it now focuses world origin)\n\nBelow gif demonstrates the issue:\n\nView navigation that I used:\n\n\n", "Crash when rendering animation\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.1\n\nBlender crash when rendering an animation\n\nIn an attempt to simplify my rendering of multiple scenes, I added an additional scene to a blend file with no objects itself. Its purpose is to be a place to put multiple *Render Layer* nodes in its compositor for all the other scenes in the file. In other words I hit \"Render\" when on that special scene and all other scenes are rendered in one go. Running this render as a single image works fine. Running render animation crashes after one frame.\n\nMy actual file has 7 scenes to be rendered. But to help demonstrate and reproduce this, I have simplified the file to just two scenes:-\n\"*Scene 1*\" is a simple scene containing a cube and a camera. Rendering this scene directly, works fine as still image or animation.\n\"*Render all*\" is a second scene that has no objects of its own (just a camera because my render farm seems to insist upon that). This scene is set to not be rendered (\"*Use for Rendering*\" unticked). However it's compositor has a *Render Layers* object which looks at *Scene 1* and which is connected to a *File output* node.\n\n\n[crash-test3.blend](crash-test3.blend)\n\nOpen file and render animation.", "Sequencer doesn't reflect source range in strip display correctly\nWindows 7\n\nBroken: 2.78 Release\n\nWhen the length of a render source is modified, the display in the strip display doesn't show it. The info 'Original frame range' is correct though.\n\n1. From the default scene, create a 'link object data' copy (although i guess the type doesn't matter)\n2. Go back to scene 'Scene' and set the end frame to 100\n3. Go to scene 'Scene.001', open sequence editor and add scene 'Scene'. It will now show a strip of 100 frames length.\n4. Go back to scene 'Scene' and change the end frame to 50\n5. Go back to scene 'Scene.001' \nThe Sequence Editor will still show a green bar 100 frames long, although the info in the properties panel tells the correct info: Original frame range 1-50 (50).\nMore importantly, you can drag the right grabber of the strip to the right and it will still paint 100 frames green and the rest grey/transparent, although the 100 frames don't have any meaning no more - it was just the length it was created with. You can also unlink the strip from the original scene and relink it again, it will still paint 100 frames green/valid.\n\nMaybe this is a bug, an oversight, maybe even intentional, I don't know. \nI don't think a .blend file is necessary in this case, but I will upload one, if desired. \n", "Image Editor in Mask mode: Toolbar broken \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nImage Editor in Mask mode: Toolbar broken \n\n- Open the Image Editor\n- Change the UI mode to Mask.\n- Add a new mask.\n- Toggle Toolbar(T).\nNotice that the Adjust Last Operation pop up i moving but no Toolbar becomes visible.\n{[F11089235](mask.gif),size=full}\n\n\n", "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", "Blender 2.8 Defaults\nThis is a list of things we should change about Blender's default settings and behaviour.\n\nThe list will grow and change over time.\n\n\nCommits:\n\n- 4d5b7696cb - prefs\n- bcf6cc1f6b - startup\n- Update: default preferences are now maintained in: `./release/datafiles/userdef/userdef_default.c`\n\n## Preferences\n\n- - [x] Python tooltips OFF\n- - [x] Auto Perspective ON ***\n- - [x] Navigation Manipulator ON ***\n- - [x] Region Overlap ON (Could be removed completely, now that it's optimized) ***\n - To make transparent toolbars work better, we would like to:\n - Make the toolbar region height be limited to the contents.\n - Make the toolbar region a separate theme\n\n## Default Settings\n\n- - [x] Default Shader should be set to Principled BSDF\n- - [x] Default Lamp increased strength (10x stronger)\n- - [ ] Playback set to AV Sync (reverted, breaks physics caching)\n- - [x] 3D View Lens = 50mm\n- - [x] Camera film size = 36x24mm Full Frame\n- - [x] Camera Focal Length = 50mm\n- - [x] Render Size Percentage = 100%\n- - [x] Render Display = New Window\n- - [x] Scene Units = Metric\n- - [x] Color Management View = Filmic\n- - [x] Workbench Object Overlap = ON\n- - [x] Absolute Shape Keys Interpolation = Linear\n- - [x] Curve Fill Mode = Full\n\n## Default Renderer\n\n- - [x] Viewport = Workbench + Studio Lighting\n\n\n## Layout\n- - [x] Headers on top for all editors, except the Timeline at the bottom\n- - [x] Default Properties tab = Object Properties\n\n## New Objects\n- - [x] Generate UV's = ON\n\n## Default Theme\n\n- - [x] Flat\n- - [x] Dark UI Chrome\n- - [ ] Universal widget radius\n- - [x] Transparent header in 3D View\n- - [x] Transparent toolbar area in 3D View\n\n## Tools\nVertex Slide:\n- - [x] Correct UV's = ON\n\nExtrude Along Normals:\n- - [x] Even Thickness = ON\n\nLaplacian Smooth:\n- - [x] Lambda Factor = 1.000\n\n## UV/Image Editor\n- - [x] Normalized Coordinates\n\n## Weight Painting\n- - [ ] Auto-Normalize = ON\n\n\n## Cycles\n- - [x] Dithering = 1\n- - [x] Image Sequence Auto Refresh = ON\n\n\n## New Objects\n- - [ ] SubdivisionSurfaces = ON (via OpenSubdiv)\n- - [ ] Shade Smooth = ON (Wait till we have OpenSubdiv)\n\n## Preferences\n - - [ ] Compute Devices ON (Postpone until we can detect crappy GPU's)\n - - [x] Release Confirms Transform\n\n## Text Editor\n - - [x] Line Numbers ON\n\n## Addons\n - - [ ] All exporters should be set to Only Selected by default", "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.", "Problem with stop animation when View Viewport Render Animation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.17\n\nBroken: version: 3.5.0\n\nThere is big gap and Problem with **stop** animation when View -> Viewport Render Animation is started in blender, eg. when it's selected accidentally and as alternative to View -> Viewport Render Image.\n\nTry to stop this animation. By me when I made this mistake not found solution other by kill blender process, cos stop button not was available or \"x\" btn like render (in case render view updating each image on Evee rendering process).\nNo imagine some big project and situation that user must waiting to finish, and he is not sure about saved file and blender is hanged due this process.\n\n", "Support Dragging Assets Into the Outliner\n- - [ ] Objects\n - - [ ] Drag into empty space in *View Layer* or *Scenes* display mode instantiates the object at the 3D cursor (TBD: Active collection or scene collection?). Linking places it at the location from the source file.\n - - [ ] Drag onto/into collection does the same, but assigns it to given collection. Rather not support modifier keys like {key Shift} to parent at first, better keep asset dragging simple and let users decide which collection the object should live in first. They can do the parenting then.\n - - [ ] Drag into the *Blender File* display mode only adds the object to the file, doesn't instantiate it? \n - - [ ] Dragging onto/into a collection there could still instantiate.\n- - [ ] Other Datablocks\n - - [ ] Other data-blocks only get added to the file by default\n - - [ ] Dragging materials or meshes onto objects could reassign. (Probably should consider where it's dragged to exactly, e.g. a material dropped onto another material could replace it, or add a new material slot if dropped in-between two existing ones.)\n\nMore type dependent behavior could be considered/investigated. E.g. maybe it's nice to have an image empty created when dragging an image to the Outliner.", "Delayed update of outliner ui on change of active collection\nBlender 3.6\n\nWhen you change active collection outliner UI updates only after you leave the outliner.\nAttached short demo gif.\n\nWay to reproduce the issue:\n1) Start default blender scene.\n2) Add new collection \"Example\"\n3) Run the script below in the text editor.\n4) Note that above the outliner you can see currently active collection, by default it's \"Collection\"\n5) Try to select \"Example\" instead of \"Collection\" - it won't update in the ui above.\n6) If you leave the outliner it will update the active collection.\n7) You can also try to choose some other collection and run operator to `.tag_redraw()` - F3 - Update Outliner. Note that info message that says that active collection didn't changed, it's just that outliner area wasn't updated.\n\nWhat expected - outliner ui to update as you change active collection.\n\n```python\nimport bpy\n\ndef get_outliner_area(context):\n screen = context.screen\n for area in screen.areas:\n if area.type == \"OUTLINER\":\n return area\n\nclass EXAMPLE_OT_custom_collection_new(bpy.types.Operator):\n bl_idname = \"example.redraw_outliner\"\n bl_label = \"Update outliner\"\n def execute(self, context):\n before = context.collection.name\n area = get_outliner_area(context)\n area.tag_redraw()\n self.report({\"INFO\"}, f\"{before} -> {context.collection.name}\")\n\n return {'FINISHED'}\n\ndef context_draw_outliner_foobar_buttons(self, context):\n layout = self.layout\n layout.label(text=context.collection.name)\n layout.label(text=context.view_layer.active_layer_collection.name)\n layout.operator(\"example.redraw_outliner\")\n\ndef register():\n bpy.utils.register_class(EXAMPLE_OT_custom_collection_new)\n bpy.types.OUTLINER_HT_header.append(context_draw_outliner_foobar_buttons)\n\ndef unregister():\n bpy.utils.unregister_class(EXAMPLE_OT_custom_collection_new)\n bpy.types.OUTLINER_HT_header.remove(context_draw_outliner_foobar_buttons)\n\nif __name__ == \"__main__\":\n register()\n```\n\n", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Allow user to change the shading parameters of the asset preview generation scene\nUsers should be able to have some control over the render settings of generated asset preview icons.\n\nPersonally, I want to be able to turn off the specular lighting because it makes my assets look ugly in the previews (note the big shiny surfaces on these bushes).\n\n" ]

[ "Outliner: any action triggers expansion of all ViewLayers\nOperating system: Linux-6.0.5-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro RTX 4000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: I don't think it ever worked\n\nAs seen on the attached video, when the `All View Layers` filter is enabled, performing any action (such as clicking on a ViewLayer name) triggers the expansion of all the View Layers.\n\nI think the behavior should follow that of other items, such as Collections, so clicking on the View Layer name only selects it, doesn't expand it.\n\nThe video also shows a different bug I noticed (around 0:10), but I made a separate report for that: #102357.\n\n\n* Create multiple View Layers\n* In the Outliner, enable the filter `All View Layers`\n* Collapse all view layers\n* Select one view layer\n[#102317.blend](T102317.blend)\n{[F13862779](sr-2022-11-07_01.07.31.mp4), size=full}" ]

[ "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!", "Support Alembic export/import of curve objects\nI created this issue as requested [here ](T51195#430327).\n\nWhile the export of animated mesh objects works quite well, exporting and importing curve objects does not work as expected at the moment.\n\nWhen exporting curves there are two main options:\n- Export as curve\n- Export as mesh\n\nBoth of these are very useful. Depending on the specific setup it might not be useful to export a curve as curve but rather as mesh. Being able to export as mesh should always be an option.\n\nI created a little test file that includes a curve object with multiple animated properties and modifiers: [curve_export_test.blend](curve_export_test.blend)\nSome modifiers implicitly convert the curve into a mesh, so when the user wants to export as a curve, it should (if possible) evaluate all modifiers until the curve is converted. If it is not possible to apply only some modifiers, it should still be possible to only export the curve before any modifier is applied (next to the option to export the whole thing as a mesh).\n\nAlso, keep in mind:\n- Curves can consist of multiple splines.\n- The amount of splines per curve object can change over time.\n- The amount of points in a spline can change over time.\n- Curves and spline points have quite properties have quite a few attributes that need to be considered when exporting as curve (bevel radius, ...).\n\nIf I had to choose what to develop first, mesh or curve export of curve objects, I'd vote for mesh, as it allows for more flexibility. Additionally I imagine it to be easier to develop.", "Optix fails when geometry nodes instance has animated translation and scale 0 and motion blur is on\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.4.1\n\nRendering will not start. It stops at \"Building OptiX acceleration structure\"\n\n\n\nThe culprit seems to be a combination of animated Translation and Scale 0 together with animated Rotation of the object and motion blur.\n\n\n\nDoesn't work in OptiX. Cuda and CPU both work.\n\nOpen the .blend file and render the frame.\n\n", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "Cycles: Pointiness has artefacts on extremely small mesh size\nOperating system:\nGraphics card:\n\nBroken: version: 3.6.0 Alpha\nWorked: Never\n\nPointiness has artefacts on extremely small mesh size. \n\n| Normal size | Small size | Smaller size |\n| -- | -- | -- |\n|  |  |  |\n\n1. Create cube with beveling edges. Create small copies on vertices (as on example pictures).\n2. Set shader to cube. Shader with:\n a. Inputs: Geometry -> Pointiness.\n b. Map range: From Min: 0.5, From Max: 0.54.\n c. Material Output.\n3. Render that cube with applied different sizes.", "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.", "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.", "Intermittent: Control + MMB to zoom non responsive or sluggish vs mouse speed\nOperating system: MacOS Ventura 13.4.1\nGraphics card: M1\n\nBroken: 3.5.1, Hash: e1ccd9d4a1d3, Branch: blender-v3.5-release\n\nZoom via Control + MMB becomes very sluggish to the point where excessive movement of the mouse is required. Does not match the mouse pointer speed for the rest of the application. \n\nAny model in perspective mode. Attempt to zoom view to the object.\n\n", "Current frame indicator has misaligned and inconsistent pixel positioning\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060 TI\n\nBroken: 3.1.2\nWorked: Probably never\n\nThe current frame indicator is aligned inconsistently against the keyframes depending on where the current frame indicator is within the 2D viewport.\n\n[framewiggle.mp4](framewiggle.mp4)\n\nThere is an additional issue that is probably contributing to this as well. The frame indicator is 4 pixels wide (shadow included). Note that this is an *even* number. Because the background grids, keyframes etc. all have *odd* widths, it is mathematically impossible for the frame indicator to ever be properly centred over any of them. The current frame indicator should be made to be 3 pixels wide, or perhaps 5 pixels wide so that it can actually be centred with other elements in the UI.\n\n\n\n1. Make a bunch of keyframes on an action.\n2. Position the current frame at a frame that has keyframes.\n3. Pan the 2D viewport of the action editor.", "Gpencil: Delay & Frames field values in Build Modifier should be integers only\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\nIn the Grease Pencil Build modifier, when using the mouse or the arrows to change Start Delay or Frames, the value goes through decimals instead of going directly to the next frame value.\n\nLoad a Grease Pencil Build modifier,\nIn the Start Delay or Frames field, use the arrows or the mouse left button to change the value, or type a number with decimals.\n", "alt brush doesn't work in image editor -> paint\ni think this should be fairly easy to reproduce so i wont bother sharing system info. i was able to reproduce this on 3.3.0 and 3.3.1.\n\nalt brush doesn't work in image editor -> paint\n\ni have a different colour on my brush but when i press ctrl and try to paint the primary colour is painted onto the canvas", "Translation of UI into Catalan\nDear colleagues,\n\nI would like to be included as member of the #translations team(s) to work on the Catalan version of the UI.\n\nI apollogize in advance if I post this in the wrong place. The instructions say that I should create a task and ask for this; but it seems that I can only access the \"create task\" functionality here. It seems that other members can create tasks elsewhere; but presently not me.\n\nBest wishes,\n\nJoan Pujolar\n", "Python API: TRANSFORM_OT_resize unrecognized in bpy.ops.mesh.extrude_region_move (macros can change their operators during execution)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.76\n\nBroken: version: 2.91.0\nWorked: (newest version of Blender that worked as expected): don't know\n\nError displayed in the system console: \"Converting py args to operator properties: : keyword \"TRANSFORM_OT_resize\" unrecognized\n\nIn a blank view \n- add a circle (with 'bpy.ops.mesh.primitive_circle_add(radius=1, enter_editmode=True, align='WORLD', location=(0, 0, 0), scale=(1, 1, 1))' in the Python console)\n- then extrude it toward the center by typing {key E}, then {key S} to create an annulus. \n- The command shown in the Info window is: \n\n```\nbpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={\"use_normal_flip\":False, \"use_dissolve_ortho_edges\":False, \"mirror\":False}, TRANSFORM_OT_resize={\"value\":(0.560534, 0.560534, 0.560534), ...etc\n```\n\nSo `TRANSFORM_OT_translate` (in a \"normal\" extrude_region), became `TRANSFORM_OT_resize` (by hitting {key S})\n\nThis same command pasted into the Python Console or in the text editor gives the error shown above.\n\n\n", "Generic Rigid Body Constraint Bug\nOperating system: Windows 10\nGraphics card: Radeon RX 470\n\nBroken: 2.83.0\nWorked: Unknown if it ever worked\n\nAngle limit not only doesn't work but causes weird neverending twitching back and forth\nUPDATE:\nTwitching happens for both cases when both rigid bodies are active and when one of them is passive.\n[M0DJ38oWQo.mp4](M0DJ38oWQo.mp4)\n\n1. Add 2 rigid bodies, 1 active, 1 passive animated\n2. Position them active on top, passive on the bottom\n3. Add an empty in between them, add a rigid body constraint to it, select the 2 rigid bodies in its settings, uncheck disable collisions.\n4. Change the joint type to Generic, limit location to 0-0 on each axis.\n5. Play. Now it works, once you select the passive RB and move it it should behave normal.\n6. Undo. Check angle limit on Z and choose some angle range (I had it set to -30 to 30).\n7. Play. Move the passive RB and watch it breaking.\n", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). " ]

[ "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", "Alembic Imported Camera - misses Focal Length Animation & Depth of Field Animation\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1070\n\nBroken: All Blender versions\nWorked: None\n\nWhen Alembic camera with \"focal length animation\" is imported into blender - there is no animation for focal lens - it stays same as first frame focal length mm\nSame goes for Focus Distance (Depth of Field)\n\n**Temporal solution**\nThe solution is to use Side program like Maya:\n1) Import alembic with camera into maya; \n2) Export camera as FBX from Maya; \n3) Import Camera FBX into Blender;\n4) Copy Animation of Focal Length and Focus Distance from FBX Camera to Alembic Camera. \n\n \nA great solution would be if whyle importing Alembics - there would be an option to import it Localized, and also with desired framerate to chose." ]

[ "Missing progress indicator for 'Render Audio'\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.83.4\n\nWhen we use the 'Render Audio' option from Render menu, after the rendering starts, there is no indicator about the rendering progress, how much time is left.\n\nIn any scene with audio in the Sequence editor, try using Render>Render audio command. There is no progress indicator. It is very vital specially for long length tracks.\n", "Tool Menu does not wait in Sculpt mode unless the cursor is hovering on the previously selected tool.\nOperating system: Windows 10\nGraphics card:\n\nBroken: 2.90.3 alpha Date: 2020-05-25 19:50 Hash : 5254ffa17bf0 Branch: master\n\nTools menu does not wait even for a second Shift + Spacebar in Sculpt mode. Tricky thing is : unless the mouse cursor is on the previously selected tool in the menu.\n\n- Go to Sculpt Mode\n- Press Shift + Spacebar.\n\nOnly when you PRESS TWICE the \"Shift Spacebar\" key combination TOOL MENU STAYS. i.e., Only if cursor hovering on the previously selected tool menu stays otherwise it disappears. ", "Property Search Improvements\n**Ctrl-Tab Improvement**\nCurrently ctrl-tab doesn't know about which tabs have search results. It should change a little bit:\n* If used while the text field is in focus, keep that focus.\n* Only cycle through tabs with results.\n\n**Fuzzy Search**\n[D9145](D9145) *Needs to be altered to not use per-word comparison, instead compare the entire text block at once.*\n\n**Performance**\nIt's not yet known if search will be a bottleneck for anyone on lower end hardware. At least some efforts should be made to identify any performance issues, and possibly address them. I did some initial profiling. Although I didn't find any major bottleneck, it's possible some things could be looked at.\n\nI tested by maximizing the property editor in a relatively complex file and ctrl-scrolling up and down very quickly, so it should be redrawing as quickly as it can.\n\n\nHere are some interesting items from the \"Bottom up\" results:\n* `__strcmp_avx2`: 5.52%\n** `buttons_context`: 1.15%\n* `UI_panel_begin`: 0.85%\n* `BLI_strcasestr`: 0.617% -- *called from property search only*\n* `panel_add_check`: 0.61%\n* `uiItemFullR`: 0.582%\n\nI think the first thing I would consider is using GHash for `buttons_context.c`, similar to the recent changes in `screen_context`.\n", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Dead Keys failing (accented letters, double strokes)\nOperating system: Windows 10 X64 Enterprise\nGraphics card: Nvidia RTX 2070 MaxQ\n\nBroken: 2.73, 2.91.0\nWorked: Never\n\nIn a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).\nIf I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?\nActually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.\n\n- In the text editor, press and hold the dead key\n- without releasing the dead key, press the key to be transformed. (this will fail)\n\nIf you release the dead key before pressing the key to be changed, it will work normally.", "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", "Shader Editor has a significant delay after opening Translation.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nShader Editor has a significant delay after opening Translation.\n[bandicam 2019-05-28 07-48-44-136.mp4](bandicam_2019-05-28_07-48-44-136.mp4)", "Brushes: Smooth algorith is not consistent.\nCurrent smooth algotithem overwrites input data that can then be used during the same iteration. Meaning that the smooth operation is not consistent.\nDuring usage this is not that noticeable as smoothing is done per brush evaluation step. But it could be improved.\n\nThe memory could be allocated per thread and not per work item to reduce the overhead introduced.", "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!", "Old todos (to be checked)\nNOTE: this is a direct dump of Install-OS (without cherrypicking the valid items)\n\n- [ ] Add code to detect drives to change (usb connected, disconnected)\n- [ ] RNA library needlessly rebuilds every time in visual studio.\n- [ ] Blender doesn't recognize .lnk shortcuts or hidden files.\n- [ ] Symbolic links are not supported #37619.\n- [ ] NTFS junctions are not supported #52080.", "Sculpt Trim tools are very slow\nOperating system: macOS Mojave 10.14.6 \nGraphics card:\n\nBroken: Version 2.91.0 (2.91.0 2020-11-25) & Version 2.92.0 (2.92.0 2020-12-27)\nWorked: n/a\n\n\nUsing Box Trim is very slow. If you use the tool and then switch to another program like a web browser before the task is done, Blender becomes unresponsive and you have to force quit it.\n\nSee video of the slowness.\n\n[boxtrim.mov](boxtrim.mov)", "No responding open .blend file reuse mesh many times\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: blender-3.0.0-alpha+master.32cc9ff03746-windows.amd64-release (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: None (newest version of Blender that worked as expected)\n\n.blend file can download here\n21082\n\nI use bpy build a scene reuse some mesh many times. reuse around 64 times can work smoothly, only 0.4 second to build and open immediately. 128 times build 0.9 seconds and open will take a while. 256 times build 3.17 seconds and cannot open(no responding, not error). \n\n```\n collection = bpy.data.collections.new('matrices')\n bpy.data.collections['meshes'].children.link(collection)\n count = 0\n for mat in self.matrices:\n obj = bpy.data.objects.new(mesh.name, mesh)\n collection.objects.link(obj)\n mat_bpy = matrix_translate_to_bpy(mat)\n obj.matrix_world = mathutils.Matrix([mat_bpy[:4], mat_bpy[4:8], mat_bpy[8:12], mat_bpy[12:16]])\n obj.data.materials.append(materials[get_material_key(self.material)])\n count += 1\n if count > 256:break\n```\n\n", "UV Editor lacks Annotation 'Placement' option\nBroken: 2.80rc1\nWorked: 2.79b\n\nIn Blender 2.79, you had the 'View' and 'Cursor' Stroke Placement option in the left panel, under 'Grease Pencil'.\nIn 2.8 this is meant to be in the Top Bar or 'Active Tool and Workspace Settings', as it is for the 3d Viewport's Annotate tool, but this is missing for the UV Editor, meaning all annotation defaults to 'View'.\n\n - Open the blender and choose the `UV Editing` workspace\n - Compare the 3d View Annotate Tool with that of the UV Editor\n - Notice the lack of Placement options", "Refactor AssetCatalogservice\nAfter Blender 3.0 has been released, the `blender::bke::AssetCatalogService` class needs some refactoring. It has too many responsibilities in this single class:\n\n- Finding catalogs (by ID, by path)\n- CRUD operations on catalogs\n- Writing to & loading from disk\n- Undo/redo system\n- ... by the time you read this, likely more.\n\nOnce Blender has been released (or at least after the release branch has been created), there should be a better view on the necessary functionality, and a refactor of the code should be fairly straight-forward.\n", "Depsgraph deferred evaluation design\nFor heavy modifiers, evaluation will take a lot of time, while the UI is locked, which affects user experience. Deferred (background) evaluation will allow:\n\n1. UI to be responsive while calculation is happening in the background.\n2. Showing progress in the UI.\n3. Other interactive stuff (?)\n\nThis function will eventually be needed anyway so I set up a task here while I poke around the code to find a doable design.\n" ]

[ "Strange behavior during blend file save\nWindows 7 x64\nI7 860 16gb ram\n2x Geforce GTX 670 4 gb vram\n\nBroken: Blender 2.73 Hash : b4d8fb5\nWorked: (optional)\n\nDuring saving, 3 times on 5 save commands, Blender takes 3-4 time the time, sometime more, to save the blend like a freeze (a 2.30 mb file). At start, I thank was my Qnap but same behavior on my SSD. No problem with my Octane render Blender version Blender 2.72 last version. The previous version of the 2.73 RC not had this problem, not saw it.\n\n\nJust save a file... can know how to found an other way to reproduce this. If you want, I can run Blender in a specific mode to output more informations or using a program under windows to debug it.\n\nBest Regards,\n\nMatt\n" ]

[ "Cycles does not respect the texture alpha mode\nOperating system: Gentoo Linux \nGraphics card: AMD 290x\n\nBroken:\n2.79b\n2.80 f15205b93f56e454b76d5a222fdb9a9665b99907 2018-01-02\n\nEevee respect the alpha mode in the texture settings, however cycles does not.\n\n[alpha_test_pack.blend](alpha_test_pack.blend)\n\n1. Load the attached .blend file\n2. Change the texture settings for the `Alpha:` setting for the image texture node (with use alpha on).\n3. Notice that in cycles the `Alpha:` setting has not effect, the texture alpha is always premultilied.", "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)", "In eevee, shading disappears when SSS is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: -\n\nShading disappears in Eevee if one object is located on another object and both have Subsurface enabled\n\nWhen an object has no shading, it looks unrealistic and wrong.\nTo get around this bug, I render two images and connect them in the compositor.\n\nMaybe it is possible to somehow enable these shading without a second render?\nSSS is needed for both objects.\n\nBall Subsurface On (0.02)\n\nBall Subsurface Off (0.0)\n\n\n.Blend file\n[bugshafowsubsurface.blend](bugshafowsubsurface.blend)\n", "Eevee: Occasional render glitches when using attribute node\nOperating system: Linux, specifically KUbuntu with X11\nGraphics card: RTX 3080 (Driver Version: 530.30.02, CUDA Version: 12.1)\n\nBroken: 2.93 - 4.0.0 Alpha, 2023-06-29, f47eed749eaf\nWorked: 2.92 (as available on Steam)\n\nUsing an attribute in an Eevee material causes occasional but severe render glitches. This does not happen consistently on any particular frame. It does not happen when rendering from the command line with `--background`.\n\nTo reproduce, render an animation with the attached Blender file. One in every 50 frames or so are corrupted. Occasionally it gets most of the way through the animation before ever producing a bad frame.\n\nThis file is basically the startup file with two changes:\n1. An attribute node with the name set to \"Color\" is plugged into the base color on the default material.\n2. The sample count is lowered to one. (The issue persists without this, but with a higher sample count, some samples glitch and others do not. The final image is a mix of the glitched and regular samples.)\n\nI have ensured that this is not a problem with my particular Blender settings by deleting everything in `~/.config/blender/4.0/config` and selecting \"Save New Settings\" in the splash screen before opening and rendering the file in the 4.0.0 alpha.\n\nNormal frame:\n\n\nCorrupted frame (as rendered in 2.93, some other versions simply display a transparent hole where the cube was without affecting the background):\n\n\n", "Cannot disable shadows if an object is set to holdout.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: Confirmed on Version 3.4 to version: 3.5.0\nWorked: Never (Goes as far as 3.0, since the addition of the \"Object Properties -> Visibility -> Holdout\"option)\n\nCannot control an objects shadow visibility if the object is set to holdout. Having a shadow on a holdout object does not work as expected, especially when trying to use the holdout object as a 3d mask.\n\n\n- Set scene renderer to Eevee.\n- Create an object, set \"Shadow Mode\" to none in the material shader of said object.\n- The object will no longer have a shadow, as expected. \n- Set the object to holdout via \"Object Properties -> Visibility -> Holdout\" option, and the shadow reappears. Can not turn off shadow as long as this option is on.\n - However, if use Holdout shader in the nodes and connect it directly to the Surface output, no shadow will appear (this matches expectation).\n\nAdded a file that directly shows the issue.", "Compiling shaders for Eevee locks up the viewport until the process is complete (MacOS)\nOperating system: macOS-11.2.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.0.7\n\nBroken: version: 2.93.0 Beta\nWorked: I don't believe this has ever been good on the Mac platform\n\nWhen working in a heavy scene (the spring or barbershop demo, for example), the UI will \"beach ball\" or lock up while blender calculates Eevee shaders. On a pc, these calculations don't appear to lock up the interface the way it does on Mac. The expected behavior would be that the UI remains responsive at all times.\n\nOpen the Spring or Barbershop demos. Switch the viewport to full Eevee interactive rendering. The UI will lock up while Blender calculates the shaders. Once this process is complete, the viewport will return to normal behavior.\n\n", "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", "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", "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)", "Geometry Node in World Shaderworkspace does not output the same coordinates in Eevee like in Cycles.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\nWorked: None same in 2.83\n\nGeometry Node works differently for Cycles and Eevee in the World Shader Tab, The Coordinates are distorted with Eevee. Im not sure if this is as expected.\n\n1 Goto Shading Workspace\n2 Enable Viewport Shading and enable World Background\n3 Add Geometry Node.\n4 Connect either Position, Normal, True Normal or Incoming to Background Shader.\n5 Switch between Eevee and Cycles to see the difference.\n\nOn the other hand, the Normal output of the Texture Coordinate Node is exactly the same in both render engines.[Geometry Shader in World Bug.blend](Geometry_Shader_in_World_Bug.blend)", "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", "Add interference effects to glossy and glass shaders\nAs a response to patch [D2003](D2003) and my own work in OSL ([interference script](showthread.php?403299-UPDATE-v1-6-Cycles-PBR-thin-film-interference-and-metals)), I suggest to add the option of interference effects to the glossy and glass shaders natively in cycles. Please note that I'm not familiar with the source code of Cycles, so this task description is based on cursory glancing through the code.\n\nThe OSL script suffers from the limitation that the effect of roughness on the surface normal does not influence the reflectance and transmittance factors calculated with the generalized Fresnel equations. Only the macroscale normal is used for the reflectance and transmittance. Patch [D2003](D2003) handles this in a more appropriate way for metals by applying the correct reflectance to each sample from a distribution of angles in case of rough surfaces. \n\nI propose to build on top of patch [D2003](D2003), which I expect to have pretty much laid out all the ground work, and to extend it to include one or two additional layers of an arbitrary material that can be described with a complex refractive index. \n\nThings to discuss:\n\n - Implementation: multiple glossy shaders, or a single shader that can handle substrate-only, substrate+1 layer, substrate+2 layers?\n - The phase of the reflectance is required for physically-correct behavior (no approximation). I implemented a complex math library in OSL just for this. Is it acceptable to do the same for cycles?\n - If for substrate-only the approximate Fresnel reflectances are used, then for 1 or two layers with zero thickness a small color change can occur as in that case the exact solution is used. Is that acceptable? (disregarding a check for zero thickness of course)\n - What to show the user? My OSL script has 3 n,k pairs (RGB) for each material (substrate, layer 1, layer 2). Then two thicknesses, one for each layer. I think this is the minimum. I optionally have the wavelengths of the RGB triplet and the refractive index of the outside medium as input via conditional compilation. The latter is perhaps the least useful, but the wavelengths determine the spacing between the interference fringes and therefore have an artistic value.\n\nThere are probably more things that I didn't think of, but this is a start. I am familiar with the physics and the equations that calculate such a feature and have experience with coding in C++. I would volunteer to implement interference effects in cycles and am thinking along the lines of co-development with a more senior Cycles developer.\n\n\n\n\n\n", "EEVEE: Volumetric simulation show ghosting in playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: ALL versions up to and including version: 2.91.0 Alpha\n\n\n\nHere's the video of the problem, as can be seen, I have to stop playback to clear the viewport vdb data from the previous frames. Left is EEVEE viewport, right is solid mode (so you can see what the eevee viewport should be displaying:\n\nIt isn't related to EEVEE volume optimisation as I have tried reducing the number of voxels displayed and also reducing the volume samples, viewport samples, and turning off the denoiser. \n\nlatest gpu driver and blender version, resetting blender to factory defaults doesn't help.\n\n[2020-08-20 04-22-55.mp4](2020-08-20_04-22-55.mp4)\n\nHere's the blend file:\n\n[vdb playback bug.rar](vdb_playback_bug.rar)\n```\n\n```\nP.S, the fps is Extremely slow compared to other 3d apps I've tested this sim in (with shading). Is this due to all of the surplus vdb data not being cleared? Perhaps there needs to be an option to cache to RAM if reading from disk is the cause?\n", "Shader to RGB node is ignoring shading and just using color socket data directly\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.4\n\n\nIf you have a Shader that is converted with the Shader to RGB node, and then the resulting Color is plugged into another shader node and rendered, the output of Eevee's Color pass for that shader shows color plugged to socket of shader that is converted to RGB. In example file it is pure white, when you would expect to see the converted shader to RGB.\n\nProblem exists with Diffuse, Glossy, and Emission shaders and passes with the exception that an Emission converted to RGB going into another Emission will show up properly in the emission pass.\n\nSee Node graph in attached image, or attached file.\n\n\n[shader_to_rgb_eevee_pass.blend](shader_to_rgb_eevee_pass.blend)", "2.93 EEVEE ScreenSpace Reflections - Trace Precision Factor - Faded Reflections (Reflections Not Fully Reaching The Upper Surface of Objects ''\nOperating system: Windows-10\nGraphics card: GeForce GTX 960M\nBroken: version: 2.93.0 Beta\n\n\n\n\n\n\n\n\n\n\n\n\nThe new 2.93 screenspace reflection implementation' s trace precision is not enough to put reflections on all the surface of object (especially near the top parts of surface near upper edge) compared to the screenspace reflections with same or less trace precision in old 2.92 implementation. Its like reflection always fades to top and increasing trace precision doest fix it.\nNormally trace precision allows for reflections go all the way up on (for example cube surface) to make its surface fully reflected, but new 2.93 Trace precision 1 doesnt allow for fully making surface reflective and give darker less reflective areas near upper side edges or upper corners\n\nFor instance, in most cases: 2.92' SSR with trace precision 0.25 is almost = (almost equal to ) = 2.93 SSR with trace precision 1 (maxed)\n\n(Even though camera is further away enough to get all the reflections from screenspace , new SSRI 2.93 trace precision is inadequate and kind of gives the effect of ''as if'' we make zoom in so screenspace doesnt see all objects and the top part of cube didnt get any reflections and get darker and faded into weak reflections) \n\nMoreover, when its compared with cycles, with trace precision of 1 ob both , 2.92 one looks closer to cycles while 2.93 has faded reflection on upper pars of surface (maybe even though new reflection implementation uses cycles implementation, new implementations inadequate trace precision might be making it differerent from cycles)\n\n\n1. Create a plane scale by 5 and move -1 (down)\n2. Edit the material of default cube and previously created plane by using same material and give it a red color FF0000 with max saturation 1 \n3. Optional step: make base color saturation of material lower to see faded darkening effect more Plus Make it metallic if you want to see the result more with metallic or just leave it as it is\n4. Ensure viewport shading settings do not use scene world but use the forest HDRI and maximize world opacity and remove blur\n5. In properties rendering tab, Enable screenspace reflections and make edge fading zero. Also uncheck half-res trace\n6. Go camera view and dont zoom too much on viewport so screenspace reflection can see everything around\n7. !!Do same processes in 2.92 and 2.93 releases to compare \n8. Then, set 2.92 and 2.93 have trace precision to 0.25 - and observe\n- In 2.93 U will notice the reflected surface of the cube as u approach top edges/as u go up, have darker/unsaturated or ''Faded'' screenspace reflections caused by the trace preciison is not enough to reach there\n- however in 2.92, the reflection reaches better to all the surface and it has almost no faded or darker look\n9. Make 2.93 SSR trace precision 1 while 2.92 SSR is still 0.25 and observe:\n- then u will notice, ''the result of 2.93 SSR Trace precision 1 '' is more similar to ''2.92 SSR with trace precision of 0.25 ''\n10. When 2.93 SSR Trace precision is 1, make 2.92 SSR trace precision 1 and observe agan\n- Then u will notice 2.92 SSR Trace precision is the ideal to fully trace all reflection to surface perfectly without having any faded area with less reflection. On the other hand, 2.93 Trace precision 1 is still not adequate to put reflection to upper parts of cubes surface near top edges with full power and precision\n\n'!! Compare these on both 2.93 and older 2.92 version with old SSR implementation\n\nIn summary in 2.92 when we increase trace precision from 0 to 1, the tracing or visibility of reflections go all the way up to top edge of cubes surface making it fully reflected as trace precision maxed\nOn the other hand, in 2.93 if we increase trace precision from 0 to 1, the reflections still cannot reach all the way up to cubes surface near top edge which gives a faded and partially traced upper surface area.\n\nMaybe, To solve this maybe, the screenspace trace precision factor can be multiplied by 4-6 or maybe the it should be square cubed so the 2.93 trace precision of 2.92.\n\n[2.93&92 SSR-TRACE PRECISION 1 - CAMERA VIEW .blend](2.93_92_SSR-TRACE_PRECISION_1__-_CAMERA_VIEW_.blend)\n\n[2.93&92 SSR-TRACE PRECISION 0.25 - VIEWPORT VIEW POSITIONED .blend](2.93_92_SSR-TRACE_PRECISION_0.25_-_VIEWPORT_VIEW_POSITIONED_.blend)\n\n[2.93&92 SSR-TRACE PRECISION 1 - VIEWPORT VIEW POSITIONED .blend](2.93_92_SSR-TRACE_PRECISION_1_-_VIEWPORT_VIEW_POSITIONED_.blend)\n\n[2.93&92 SSR-TRACE PRECISION 0.25 - CAMERA VIEW.blend](2.93_92_SSR-TRACE_PRECISION_0.25__-_CAMERA_VIEW.blend)" ]

[ "EEVEE: Specular BSDF incompatible with Shader to RGB when SSR is active.\nPassing Specular BSDF through Shader->RGB when SSR is enabled causes shading other than ambient world lighting to be removed, not just the SSR reflections. The same happens with Glossy, Principled etc. \n\n2.93:\n\n\n2.92:\n\n\nAfter bisecting, this was found to be caused by rB7f7e6830991 but it's a large commit so I didn't dig in and find exactly what was responsible. \n\n(If I've already found the commit/cause should it still be opened as \"Needs Triage\"? Would marking it as \"Confirmed\" be presumptuous?)", " Shader node: Convert to RGB does not draw Specular\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 2.93.2 Release Candidate\nWorked: Blender 2.83.15\n\nThe \"Shader to RGB\" node is omitting the high light values ​​in the Specular when \"Screen Space Reflaction\" is activated in Eevee,\nit happens in version 2.93.0 but not in 2.83 series\n\n1- Create any primitive and add a new material\n2- In this material Add a \"Shader to RGB\" node after the shader and connect it to the Surface of the Material Output\n3- Add any Light\n4- In Render Properties activate \"Screen Space Reflaction\"\n\n\n\n\n[Shader_RGB_Error_2_93.blend](Shader_RGB_Error_2_93.blend)\n\n[Eevee_Error_Roughness_2_93.blend](Eevee_Error_Roughness_2_93.blend)\n" ]

[ "Missing UV Islands / Image Editor / Some generative modifiers (bevel, skin, triangulate, wireframe)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro M2200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIf geometry has the Bevel Modifier applied and the Realtime Display is on, the UV islands do no display in the Image Editor.\nIf you turn off the Realtime display (Display in Viewport) and then adjust the view in the Image Editor, the UV Islands will appear.\nIf you turn On the Realtime display and then adjust the view in the Image Editor, the UV Islands will vanish.\nYou can still paint in the Texture paint on the geometry and it will appear in the Image Editor.\n\nCreate a Cube\nAssign a Bevel Modifier - turn Realtime display ON (for me it is on by default)\nSet interface to Texture Paint mode.\nThere will by no UV Islands displayed in the Image editor\n\n[UV_Island_Bevel.blend](UV_Island_Bevel.blend)\n\n\n\n", "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)", "Mask invisible on object with modifiers when entering sculpt mode\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: unkown\n\nWhen selecting a previously unselected object with a modifier and a sculpt mask, the mask is invisible at first when entering sculpt mode.\nPainting the mask reveals it.\n\n- Create an object with a modifier (e.g. mirror or array) and paint a sculpt mask on it. Or use the file attached.\n- Outside the sculpt mode first make sure the object is unselected, then select it and enter sculpt mode.\n- The object appears with no mask visible, still you can not sculpt the masked parts.\n- Painting the mask reveals it.\n\n[mask.blend](mask.blend)\n\n[mask.mp4](mask.mp4)", "Can't see wireframe (vertex, selected components) through semi-transparent object\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 10)\nWorked: c26f470cfeea is last I have by hand\n\nIn the viewport, you can't see wireframe (vertex, selected components) through a semi-transparent object\n\n[75106.blend](75106.blend)\n1 - Create 2 objects one behind the other \n2 - Make front object semi-transparent (via Object properties > Viewport Display > Color > Alpha\n3 - Select the second object in Edit mode\n\n", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "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", "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", "Dopesheet Display Hidden doesn't work property combined with Only Selected.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: Version 2.79b\n\n\nIn version 2.79 with the \"Selection Only\" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations.\n\nFrame 1:\nTurn off the object then Animate Disable in viewport,\nFrame 2:\nTurn on the object and animate Disable in viewport.\nOpen dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear.\n\n[Dopesheet_280.blend](Dopesheet_280.blend)\n[Dopesheet_279b.blend](Dopesheet_279b.blend)\n\n\n", "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", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "Bevel gizmo is hidden when disabling Active Object gizmos\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.91.0 Alpha\nWorked: N/A\n\nThe bevel gizmo is hidden when disabling Active Object gizmos, even though the bevel gizmo is an *active tool* gizmo\n\n\n - Enter Edit Mode\n - Switch to the Bevel tool by clicking on the Bevel icon in the toolbar\n - Go to the Gizmos popover and disable Active Object gizmos\n - The Bevel gizmo disappears\n\n\n\n\n\n", "Mesh to Volume modifier is recalculated even if the volume object is disabled/hidden\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nI'm disabling the volume object in the viewport to move the origin mesh, but the viewport is lagging until I turn off the \"Mesh to Volume\" modifier.\nMaybe it is better to not compute the \"Mesh to Volume\" modifier while the volume object is hidden/disabled?\n\n- Open attached file\n- hide the volume object\n- move the origin mesh\n[H.blend](H.blend)\n\n", "Retopology: Active Object Geometry gets Occluded by Semi-Transparent Reference Object in Edit Mode\nOperating system: Linux Ubuntu 16.04\nGraphics card: Nvidia GeForce MX130\n\nBroken: 2.83.0\nWorked: 2.82.a\n\nActive mesh is occluded by high poly or another reference mesh in Edit mode. This is: I want to edit mesh A. I need mesh B to get a reference. So I make B to have a semi-transparent material for Viewport view. I select A and go to Edit mode to edit it. However, its edges and vertexes are occluded by B. We can see a comparison of 2.83.0 (first image) with 2.82a (second image): version: 2.83.0 does not show active object geometry so that we can not edit it. On the other hand 2.82a does show required geometry.\n\n \n\n1. Open Blender 2.83.0\n2. Create a Sphere mesh in the world origin so that it fits inside the default cube.\n3. Assign a semi-transparent viewport display material to the Cube so that we can see the Sphere inside. Change color also to have a better view.\n4. Select Sphere and go to Edit mode.\n5. Press A to select all vertexes.\n6. We can see that Edges and Vertexes are occluded by the Cube so that we can not edit the Sphere properly.\n\n\n[bug-report.blend](bug-report.blend)\n", "Subdivision surface settings part of the Mesh\n**Description**\n\nWe want to make subdivision surfaces a property of the Mesh datablock. The modifier would remain, but would likely be used less.\n\nThere are a few reasons for this:\n* OpenSubdiv GPU acceleration in the viewport and adaptive subdivision in Cycles need the modifier to be last in the stack. The available settings, behavior and implementation would be more clear if this was controlled outside of the modifier stack.\n* When we add modifier nodes support, the concept of a last modifier in the stack becomes fuzzy. Being able to pass along a subdivision surface Mesh to another node without actually subdividing is important for performance and to leave subdivision to the renderer.\n* For best performance with GPU acceleration, we don't want Blender to also subdivide the mesh on the CPU at all. But operations like hair positioning, particle emission and snapping still need to take into account the subdivision surface. If the Mesh datablock contains all the subdivision surface information, these could potentially work on the limit surface without subdividing the mesh on the CPU.\n* Simpler smooth normals handling, see #68893 (Smooth shading usabilty).\n* File formats like USD have native subdivision surface primitives. By making it part of the mesh, we are more compatible with such file formats. \n\n\n**TODOs**\n\n- Modeling\n - [ ] conjugate the presence of a subdivision surface modifier with the mesh settings if it is the last in the stack\n - [ ] ensure creases survive the modifier stack (unless consumed by a subsurf modifier)\n - [x] (follow up to [D10145: Subdivision: add support for vertex creasing](D10145)) move edge crease to a custom data layer\n\n- Cycles/EEVEE\n - [x] detect subdivision using the mesh settings instead of the modifier\n\n- Normals (work on some aspects of #68893 (Smooth shading usabilty))\n - [ ] remove autosmooth and custom normals options if the mesh is a subdivision surface\n - [ ] always render with smooth normals (flat areas can also be defined trough creasing)\n\n- Alembic/USD\n - [ ] set mesh settings during imports\n - [ ] export as SubD Object when subdivision is used\n\n- Workflow\n - [ ] option to set the subdivision settings when creating a mesh, or add a sub-menu with meshes with subdivision enabled\n - [ ] shortcuts to subdivide (?)\n - [ ] script/addon to update old files to replace last subdivision modifier in the stack with mesh settings (doing this in version code might have undesirable side effects)\n\n- Other\n - [ ] Update test files", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)" ]

[ "GPU subdivision: Hiding verts/edges and faces is not working with GPU subdiv \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 511.65\n\nBroken: version: 3.1.0 Beta\n\nHiding faces, edges and verts are not hiding the mesh (only the lines from the subdiv modifier). This happens only when the mesh has a subdiv modifier.\n\n1. Open 3.1 and add a subsurf to the default cube.\n2. test it by selecting a vert/edge/face and press H in edit mode. \n3. Delete the subsurf and test the feature again.\n\nIt works when you disable the gpu subdiv in the prefs.\n\nI think a file is not needed here. \nI wont ping any devs but because its the subsurf modifier its probably related to the recent work on it on the gpu part. \n\n**Temporary Workaround**\nDisable GPU subdivision in the preferences: `Edit ⯈ Preferences... ⯈ Viewport ⯈ Subdivision ⯈ GPU Subdivision`" ]

[ "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "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.", "Snap Increment with \"Absolute Grid Snap\" not working correctly in XY plane\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.Q3.230719\n\nBroken: version: 3.6.2\n\nDescription of error\nWhen moving an object by using Increment Snapping with \"Absolute Grid Snap\" enabled and constraining the plane the object no longer moves with the mouse cursor. It is best demonstrated in the video I have captured.\n\nTo repeat follow these steps:\n1. Make a new default blender scene with an object to move.\n2. Enable Snapping, set to Increment.\n3. Select the object and then \"G\" to move it.\n4. Constrain movement to XY plane and move the object around the 3D space.\n5. Next cancel the transform and Enable in the Snapping Setting, \"Absolute Grid Snap\".\n6. Press \"G\" to move the object once again and contrain its movement to the same plane as before and move the object around.\n7. The object will no longer follow the cursors movement.\n\nAdditionally, this is a recent bug as of this version as tested both 3.4.1 and 3.5 version of blender and they both work as expected, with no Discrepancy.\n", "Geometry Nodes: Mesh Boolean-Union node anamoly when boolean does not alter input mesh\nBroken: Current main.\nWorked: Never.\n\nI was trying to see if the simulation node group would get rid of internal geometry by incrementally using the **Mesh Boolean-Union** node in the **Simulation node group** but it **seems to delete some outer geometry instead.** \n\n## Without Simulation Nodes:\n| Operating as expected without Mesh Boolean Union node enabled (**creates internal geometry see red arrow**) | Operating as expected with Mesh Boolean Union node enabled (**no internal geometry**) |\n| -- | -- |\n|  |  |\n\n## With Simulation Nodes:\n\n| Description | Show |\n| -- | -- |\n| Operating as expected without Mesh Boolean Union node enabled (creates internal geometry see red arrow) |  |\n| Not Operating as expected with Mesh Boolean Union node enabled (no internal geometry but missing outer geometry) |  |\n| It should look something like this (no internal geometry but it should have \"external\" geometry also see red arrow |  |\n\nThe reason I'm trying to use the boolean mesh-union node within the simulation node group is because on some large meshes the boolean mesh-union node will fail or crash blender. \n105652#issuecomment-931240\n\nMy logic is if you have to finish an entire pie in one sitting (think of a pie eating contest) it's easier to cut them up into little pieces and eat them one at a time. **So I'm incrementally running the boolean mesh-union node on smaller pieces in the simulation node group to get rid of internal geometry therefore it's less likely to crash / fail like it does trying to do this all at once on larger meshes.**\n\nSee attached blend file: [cube repeat.blend](https://projects.blender.orgattachment)", "Custom Normals: some operations that alter topology (bisect, loopcut, subdivide, knife, triangulate modifier) destroy them while other operations (e.g. Connect Vertex Path, triangulate operator) preserve them\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2\nWorked: unknown\n\nMesh bisect generates incorrect normals when applied to a face generated using bevel with \"harden normals\" applied\n\n1. Start with the default cube\n2. In the cube properties, enable auto smooth normals (Object Data -> Normals -> Auto Smooth)\n3. Enter edit mode\n4. Select one edge and bevel it\n5. In the operator panel, ensure that \"harden normals\" is enabled\n6. Select the whole model\n7. Bisect the cube so the bevelled edge is split in half\n\nThe bad normals should now be visible. You can enable normal indicators in Overlays -> Normals -> Split face normals (the second option of the three icons). You can also go to object mode to remove the wireframe and make the bad shading more obvious.\n\n[bevel and bisect.mp4](bevel_and_bisect.mp4)\n\nNote that traditionally, topology altering operations were not expected to preserve custom normals, see for example \n- #69290 (Loop cut and knife tools makes wrong shading on the mesh)\n- #53763 (Operations that alter topology (e.g. Mirror modifier AND mirror operator, loopcut, subdivide, knife) destroy custom normals)\n\nThen there has been 93c8955a72 which was a nice improvement for some operators (but was missing others afaict).\n(check usages of `BM_custom_loop_normals_to_vector_layer`)\n\nSo this now leaves us in the situation which feels puzzling/inconsistent:\nOn the reported geometry for example `Connect Vertex Path` works as expected, whereas `Knife` doesnt:\n[#97698.webm](T97698.webm)", "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", "Mesh Mirror Node\n{[F9914997](mirror.png) size=500}\n\n**Changes and simplifications in comparison to the modifier:**\n\n1. It reflects on an arbitrary plane which is defined by position and rotation.\n\n2. It shows a gizmo that visualizes the reflection plane.\n\n3. Merge by distance operation can be done by a separate node.\n\n**Open Questions:**\n\n1. Will we handle UV data in this node or a separate one?\n\n2. How to handle the Bisect option. Having Bisect as separate node makes sense, but to use it in combination with the mirror node would require to some effort to get them lined up correctly e.g. using at least the same plane for both nodes.", "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)", "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)", "Intersect Knife: options 'self interesect' + 'cut' result in too many loose parts\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.6912\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[2 intersected objects should do an intersection on each one but keep 2 objects not 4 ]\n\n[[2 intersected objects>ctrl+J>'EDIT'>select all verts>intersect (knife)>options self intersected and cut] [which should be equivalent to 1 object selected>interect (knife)>options select/unsel and cut >>given 1 intersection but still 2 initial objetcs]]\n\n", "Threshold of the 'Select Similar' operator (Shift G) is very limited at large scales.\nHi,\nsince I'm working on a project in Unreal Engine it needs to be actually done in centimeters (meaning in mesh-terms it's 100 bigger than meter mesh).\n\nHere is the blend file: [ShiftG_SelectSimilarArea_CantPutInMoreThan1.000.blend](ShiftG_SelectSimilarArea_CantPutInMoreThan1.000.blend)\nTry to select a face and Shift+G -> Select Similar (not sure if the shortcut stayed that way)\n\n\nI'm running into an issue here and there where some functions expect the mesh to be in meters and work worse in centimeters (or not at all)\n\nFor example here I was using Shift+G and Area to get the faces with the same area. Because the areas in the centimeters model are so big number-wise it doesn't find any match. So either I think the amount needs to be unlimited (I would put in 100 and that would probably have the same results as when the mesh is 100x smaller) or this needs to be addressed from the unit scale side of things.\n\nThis is in Meters (scaled the mesh 0.01), we get a good window selection because they are mostly the same:\n\nAnd in Centimeters nothing more than the one face is selected.\n\n\nMaybe the scale in Units should be used in these operators to make the mesh smaller?\n\n\nThanks for looking into this.", "Exact boolean removes custom split normals\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0\nWorked: -\n\nCustom normals get removed with \"exact\" boolean modifier option, but not \"fast\".\n\n1. Open attached example\n2. Toggle boolean modifier on and off or toggle the boolean modifier option between fast and exact\n\n[exact boolean ruins custom normals.blend](exact_boolean_ruins_custom_normals.blend)\n\nComments:\n\nIf Blender wants more bug reports with attached example files, perhaps they should allow you to export a selection to a .blend? I removed all packed files, but still a bit unsure why the file is so large.\n\nSomeone may question why the attached objects require custom normals at all, but let me just say that custom normals are always present and extremely important to any imported objects from CAD, which these and 90% of all of the objects I work with are.\n\nAlso, I did see #95915 and #95913.", "No Vector Displacement On Instances\nWindows 10 x64\n\n2.79.4\n\nVector displacement doesnt work with instances, It mirrors the displacement on the first object, Im sure this is working as intended but there are many cases where you need to displace actual instances as well.\n\nHaving a checkbox somewhere to enable instance displacement would be amazing\n\n\n\n\n\n[instances.blend](instances.blend)\n", "Curve to Mesh node causes other objects to edge split when not shaded smooth\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nWhen using a Curve to Mesh node, it causes other objects joined to it to be read with each face as a separate mesh island by Cycles (using the Random per Island socket of the Geometry node in shaders). This only happens while using Flat shading AND the Curve to Mesh is plugging into the first position of the Join Geometry node. In any other order it will not happen.\nAlso happens with more mesh objects as long as the Curve to Mesh object is the first on in the Join node.\n\nThe edges aren't actually split, it just seems to be Cycles that thinks they're individual mesh islands.\n\nAdd a grid node and join it to a curve going through a Curve to Mesh node.\nEnsure the Curve to Mesh is the first connection into the Join Geo node.\nAssign a material to the grid and in the shader, view the Random Per Island output of the Geometry node.\n\n[2021-11-06 18-08-29.mp4](2021-11-06_18-08-29.mp4)\n\n[Mesh Island Bug.blend](Mesh_Island_Bug.blend)", "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" ]

[ "Boolean Redesign\n# Problem Description\n\nThis design task is about making the Boolean modifier and intersect tool handle special cases and be more robust, so that users can depend on it and not complain about things Carve could do that the BMesh boolean cannot.\n\nA number of bug reports about Boolean have been captured in #47030. They can be mostly grouped into these kinds of problems:\n\n* Not handling cases where there is coinciding or nearly coinciding geometry (typically edges and faces that intersect other edges and faces at more than one point, or vertices that intersect the middle of a face or edge). By design the current BMesh Boolean code does not handle these cases, putting it on the user to move the geometry around some so that the desired effect can be gotten without these special cases. But this annoys users, who regard it as a bug, and also sometimes misses the point of what they are trying to do (e.g., bring in a bunch of \"roads\" in a plane and intersect them).\n\n* Not dealing with precision problems (e.g., near-zero area faces). I suspect but am not positive that when the intersection objects have very small faces, say the result of sculpting on a high-res mesh, that the precision problems start to become abundant.\n\n* (For Boolean only) Not dealing with non-hermetically sealed intersection objects. Again this is by design in the current code, but some users miss the behavior of Carve, which would sometimes do useful things in such cases. Also, by requiring hermetically sealed objects, we miss the opportunity to use Boolean for cleaning up objects that have self-intersection.\n\n* Performance issues, usually when there are a very large number of intersections in a single face. E.g., #52471\n\n# Proposed Design\n\nSome design decisions to make:\n1. What algorithm(s) should be used?\n2. What kind of arithmetic to use? Possibilities are: floats, doubles, or exact arithmetic (would likely involve porting some exact arithmetic library to Blender).\n3. Should this be done by evolving / modifying current BMesh code, or starting from scratch? If the latter, do we try to follow the lead of the current code in trying to do the work as much as possible in BMesh structures themselves, and reusing BMesh elements wherever possible, or do the calculations in some different structure and then rebuild all affected BMesh geometry?\n\n## Algorithms\nI surveyed a number of papers on how to do Booleans. Two of the most promising papers, in my opinion, are:\n\n[[mesh-arrangements-for-solid-geometry-siggraph-2016-zhou-et-al.pdf |\n\"Mesh Arrangements for Solid Geometry\", by Zhou, Grinspun, Zorin, Jacobson. Siggraph 2016. ]]\n* Handles coplanar, self-intersections, non-manifold edges (but not ‘flaps’ nor open volumes; uses exact arithmetic; requires closed volumes, but mentions generalized winding number concept (which could fix the requirement about no-open-volumes but looks a bit messy to incorporate).\n\n[[S092577210700018 |\n\"Boolean operations on 3D selective Nef complexes: Data structure, algorithms, optimized implementation and experiments\", by HachenBerger, Kettner, and Melhorn. Computational Geometry 38 (2007).]]\n* Handles everything in closure of boolean ops on half-spaces - so, non-manifold edges, topological singularities, etc. Uses exact arithmetic. Basic idea is to represent 3d topology by “Sphere Maps” which show which volumes are in/out around vertices. They have a representation called “Selective Nef Complex” (SNC) which is a lot like BMesh but with sphere maps at the vertices instead of just vertices. There’s an algorithm that creates SNC’s from just sphere maps. And another algorithm that does boolean operations by first doing all intersections, then getting sphere maps at each intersection point according to boolean operation and in/out labels, and finally synthesizing resulting SNC. This is what CGAL implements now.\n\nThe Zhou et al. paper pays more attention to things like coplanar faces, and looks easier to implement, so I have a preference for that approach.\n\nAn important subproblem that comes up as soon as we want to handle arbitrary intersections of faces, edges, and vertices in a single plane, is how to do that. The current Blender code uses the BM_face_split_edgenet function to do the work of remaking faces when there are edges intersecting it. So one approach is to generalize the triangle-triangle intersection code in Blenlib to handle all the results of coplanar intersections, and use that to figure out what edges to feed BM_face_split_edgenet. The latter would need to be slightly generalized to handle isolated vertices in a face too; treating them as zero-length edges will work (I tried this). One issue with this approach is that it only deals with intersections with one given face: if the things being intersected with the face intersect with each other, then the code doesn't work, and needs considerable development in order to make it work.\n\nAnother approach to the planar intersection problem is to use [Constrained Delaunay Triangulation]], with an algorithm that will discover all the intersections, coincident vertices, and overlapping edges, as a by-product of doing that triangulation. Afterwards, most of the triangulation edges can be removed, leaving only enough that valid BMesh faces can be formed out of what remains. A promising paper for doing CDT, paying close attention to overlaps etc., and keeping track of how the output relates to the input, is [[http:*citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.14.6477&rep=rep1&type=pdf | \"Fully Dynamic Constrained Delaunay Triangulations”, by Kallmann, Bieri, and Thalmann](https:*en.wikipedia.org/wiki/Constrained_Delaunay_triangulation). I have this implemented now and plan to soon propose putting it in Blenlib, as I believe it can be useful for other things, including Python API users.\n\n**Update (June 15, 2020)**\n\nThough I had the whole thing mostly working in May 2020, I hit a kind of brick wall when intersecting very dense meshes. My approach to using doubles with epsilons was just proving too hard to make work in such cases. More details of my journey are in this [devtalk thread](72).\n\nThe new approach I am taking is to make a fairly faithful implementation of the Mesh Arrangements Zhou et al paper cited above. For the CDT, I switched to using the Guibas-Stolfi algorithm described in [\"Primitives for the Manipulation of General Subdivisions and the Computation of Voronoi Diagrams\", by Guibas and Stolfi]], though still using the plane subdivision data structure from the Kallmann et al. paper. For triangle-triangle intersection, I am using the algorithm of [[https:*hal.inria.fr/inria-00072100/document|\"Faster Triangle-Triangle Intersection Tests\", by Devillers and Guigue](https:*dl.acm.org/doi/10.1145/282918.282923). This is all mostly implemented now in the *newboolean* branch.\n\n## Arithmetic\n\nWe had some discussion of arithmetic in general, and somewhat about Boolean in particular, in [this devtalk thread](6). A general consensus was that using double arithmetic internally to Boolean would likely be helpful. But what about exact arithmetic? Many of the papers on Boolean and other intersection problems have reached the conclusion: just use exact arithmetic and many problems go away; it is a lot slower, but can be sped up some by tricks that use floating point in many cases an only resorting to the more expensive techniques sometimes. I see three main problems with this approach: (1) the code to implement exact arithmetic is complex; there are libraries that we could import into Blender (maybe -- have to check licensing) but do we need to do that? (2) I'm pretty sure our users don't actually want the result of doing exact arithmetic: in many cases where faces are almost coplanar, they would not appreciate have two separate planes joined by extremely long and skinny triangles. (3) Do we really want the performance hit? For all of these reasons, I think we should use doubles (with careful epsilon tests) instead of exact arithmetic.\n\n**Update (June 15, 2020)**\n\nGoing along with the algorithm changes update, above, I have decided to bite the bullet and use exact arithmetic. I have decided to use the rational type from [GMP multiprecision library](https:*gmplib.org/), which is a reasonably small additional library dependency for Blender, and has a suitable license. In order to solve the other downsides I mention above: maybe add post-processing to remove very small triangles; and use floating point filtering to try to limit the cases where full rational arithmetic is needed for doing orientation tests. The basic support for this is now in the*newboolean// branch, though not yet with floating point filters. There is a new rational type vector called `mpq2` and `mpq3` in the C++ blenlib.\n\n## Development approach\n\nI have tried for a number of months to use the \"evolve the current code\" approach. It is kind of working and I'll continue to do that for a while. But the code needed to deal with merged vertices and edges has gotten increasingly complex and hard to do correctly, so I hit a kind of wall. I think switching from trying to use BM_face_split_edgenet to the CDT approach may unblock me, so I will continue down this path for now. But there are attractions to the approach of building the geometry up separately from existing BMesh, and then putting it back into BMesh at the end. That's the approach I took for Bevel, and I do not regret that decision. So if the code starts to look too hairy, I might try to switch to that approach.\n\n**Update (June 15, 2020)**\n\nFor the reboot started in May, I decided to use C++ for the implementation. There is a template-ized version of the CDT routine (capable of doing either double arithmetic, with exact-arithmetic predicates; or an `mpq2` version using exact rational arithmetic. For now I am only doing an `mpq3` version of the Mesh Intersection and Boolean functions, since the attempt to do it with doubles and epsilon tweaking mostly failed, so there doesn't seem to be much point in template-izing these algorithms with double, at least for now.\n\nMost of the heavy algorithm lifting operates on a separate, simple, mesh representation that uses `mpq3` coordinates and integer vertex indices for triangles and faces. The reasons for not doing this in BMesh were (1) We need separate coordinate representation for the `mpq3` values (though I could have solved this problem by having and maintaining a parallel map of BMVert -> exact coords); and (2) I thought the algorithm may have to go through some states where the mesh is not representable in BMesh; (3) it was not clear that maintaining the topological relations in all generality, as BMesh does, was going to be necessary; (4) it is easier to debug algorithms with integers instead of pointers everywhere, and also hash tables based on integers can lead to algorithms with consistent results across runs and architectures, while hash tables based on pointers usually do not have those properties; and (5) there is no C++ interface for BMesh (yet, anyway).\n\n**Status as of June 15, 2020**: The *newboolean* branch does basic booleans using the new approach in the Boolean tool (with an `Exact` option, so the user can choose between the current BMesh boolean and the new one). However, I have yet to code the part that removes the triangulation edges after doing the boolean, and yet to code the part that preserves the BMVert, BMEdge, BMLoop, and BMFace attributes and data. And no performance tuning has been done yet, so it is still very slow. I expect that getting the whole thing done to the state where users will want to use it will take another two to three months.\n\n**Status as of July 14, 2020**: Now the code to remove triangulation edges after doing the boolean is done. Also, coplanar intersections work. I also did a fairly big refactor to reduce copying of vertex and face data, and to prepare for using floating-point filtering of exact arithmetic predicates (to improve performance). Also did the very first step of performance improvement: using bounding boxes and BVH trees to greatly reduce the number of triangle-triangle intersections tried. The performance is still very far from what I want it to be (currently about 100 times slower than the BMesh boolean on test that intersects two 8k face spheres; and 10 times slower on two 250 face spheres). But I still have a lot of things to do that I know will improve performance.\n\nIn terms of functionality, still to do: using original mesh attributes on created new ones (though plumbing is there to make this easy now); hooking up the boolean modifier to this code; doing proper post-operator selection; handling the proper final cutting in the Boolean Knife intersect mode; some handling of non-manifold inputs.\n\n**Status as of Aug 4, 2020**: It is mostly all implemented now: the modifier is hooked up, the Boolean Knife mode works, the original edge and face attributes are preserved. The performance is much better (within a factor of 5 of the BMesh code); there is still more headroom for performance improvement, so will likely to get even closer to the old BMesh performance in the near future. It still needs work to do something reasonable if the inputs are non-manifold. Now the GMP libraries are in SVN (thanks to the platform maintainers!), so buildbot can build the branch, as well as anyone else who can compile blender,\n\n**Status as of Aug 17, 2020**: The implementation is complete. There is a known performance problem, which will be fixed soon, and other opportunities for performance improvement still. Most bugs found by initial testers have been fix, though one is still outstanding. This code seems in reasonable shape (to me) to include in 2.91. But still need a review and agreement from the rest of the Modeling Module before this is certain.\n\n## Update (Aug 28, 2020)\nThe newboolean branch has now been merged into master, and should be in the 2.91 release, barring any big problems discovered during testing." ]

[ "Segfault with gdb debugger in PointsToVolume node\nOperating system: Linux-6.4.3-gentoo-x86_64-AMD_Ryzen_9_7950X_16-Core_Processor-with-glibc2.37 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.3-gentoo) AMD 4.6 (Core Profile) Mesa 23.1.3\n\nBroken: version: 4.0.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `Unknown`\n\nGCC builds with a gdb debugger attached crash in the Points-to-Volume node.\nThis does not happen if no debugger is attached, or when using msbuild.\n\nUse a GCC Debug build, run Blender with a GDB debugger attached.\nCreate a point cloud and convert it to a volume.\n\n\nOpenVDB will throw a lot of warnings about missing RTTI on the [`ParticlesToLevelSet::Raster`](ParticlesToLevelSet.h#L468) class.\n```\nRTTI symbol not found for class 'tbb::interface9::internal::finish_reduce<openvdb::v10_0::tools::ParticlesToLevelSet<openvdb::v10_0::Grid<openvdb::v10_0::tree::Tree<openvdb::v10_0::tree::RootNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::LeafNode<float, 3u>, 4u>, 5u> > > >, void, openvdb::v10_0::util::NullInterrupter>::Raster<blender::geometry::OpenVDBParticleList, openvdb::v10_0::Grid<openvdb::v10_0::tree::Tree<openvdb::v10_0::tree::RootNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::LeafNode<float, 3u>, 4u>, 5u> > > > > >'\n```\n\n~~This appears to be a long-standing gcc bug:\nshow_bug.cgi?id=81932\nThe nested `Raster` class is virtual due to its destructor, which seems to be the condition triggering this problem.~~\nEDIT: The same problem occurs with the _Volume Cube_ node, the gdb warning might be a red herring. Removing the `virtual` keyword from the `Raster` class also silences the warning, not sure if this class really must be virtual at all.\n\nThe effect is that debugging any file containing a Points-to-Volume node with gdb becomes impossible. I'm not sure if there is anything we can do on the Blender side to work around the problem.\n\n", "Depsgraph - Dependency Cycle - concurrency issue leading to memory after use errors.\nDisclaimer: This is a very elusive 'bug'. I stumbled on it after making changes in a completely unrelated area (liboverrides diffing code in fcddb7cda7). Artificially raising the amount of threads seems to make it more easily reproducible though.\n\nReproducible fairly consistently on my machine with Sprites production file `110_0010_A.anim.blend` version `r2747`. This file contains dependency loops, which as far as I understand makes depsgraph fail to fully handle dependencies between updates, leading to some data being freed while/before it is used from another ID.\n\nNot sure how much we support these dependency loops cases, but think crashes at least should not be accepted here?\n\n--------------------------------\n\nHere is a small patch I used to debug:\n\n```\ndiff --git a/source/blender/blenkernel/intern/object_update.cc b/source/blender/blenkernel/intern/object_update.cc\nindex 625aa666023..7f1f4a1b4d2 100644\n--- a/source/blender/blenkernel/intern/object_update.cc\n+++ b/source/blender/blenkernel/intern/object_update.cc\n@@ -376,6 +376,20 @@ void BKE_object_select_update(Depsgraph *depsgraph, Object *object)\n if (object->type == OB_MESH && !object->runtime.is_data_eval_owned) {\n Mesh *mesh_input = (Mesh *)object->runtime.data_orig;\n std::lock_guard lock{mesh_input->runtime->eval_mutex};\n+\n+ BLI_assert(mesh_input->runtime->mesh_eval != nullptr);\n+ BLI_assert(mesh_input->runtime->mesh_eval == static_cast<Mesh *>(object->data));\n+ if (mesh_input->runtime->mesh_eval != static_cast<Mesh *>(object->data)) {\n+ printf(\n+ \"%s: mesh_input->runtime->mesh_eval (%p) of %s does not match object->data (%p) of \"\n+ \"%s\\n \",\n+ __func__,\n+ mesh_input->runtime->mesh_eval,\n+ mesh_input->id.name,\n+ object->data,\n+ object->id.name);\n+ }\n+\n BKE_object_data_select_update(depsgraph, static_cast<ID *>(object->data));\n }\n else {\n```\n\nThe interesting part of the error log with an ASAN build:\n\n```lines=10\nDependency cycle detected:\n OBGEO-log_moss/MODIFIER(GeometryNodes) depends on\n GRfallen_log/GEOMETRY_EVAL_DONE() via 'Nodes Modifier'\n OBGEO-log_moss/GEOMETRY_EVAL() via 'Collection Geometry'\n OBGEO-log_moss/MODIFIER(GeometryNodes) via 'modifier stack order'\nDependency cycle detected:\n OBGEO-oak_slingshot-moss/GEOMETRY_EVAL() depends on\n OBGEO-oak_slingshot-moss/MODIFIER(GeometryNodes) via 'modifier stack order'\n GRPR-slingshot_tree/GEOMETRY_EVAL_DONE() via 'Nodes Modifier'\n OBGEO-oak_slingshot-moss/GEOMETRY_EVAL() via 'Collection Geometry'\nDetected 2 dependency cycles\n\nBLI_assert failed: source/blender/blenkernel/intern/object_update.cc:380, BKE_object_select_update(), at 'mesh_input->runtime->mesh_eval != nullptr'\nBLI_assert failed: source/blender/blenkernel/intern/object_update.cc:381, BKE_object_select_update(), at 'mesh_input->runtime->mesh_eval == static_cast<Mesh *>(object->data)'\nBKE_object_select_update: mesh_input->runtime->mesh_eval ((nil)) of MEPlane.029 does not match object->data (0x61c000286888) of OBGEO-oak_slingshot-moss\n\n =================================================================\n==404553==ERROR: AddressSanitizer: heap-use-after-free on address 0x61c0002868b0 at pc 0x000013bb005c bp 0x7f394ec88070 sp 0x7f394ec88068\nREAD of size 2 at 0x61c0002868b0 thread T137\n - 0 0x13bb005b in BKE_object_data_select_update /home/bastien/blender/src/source/blender/blenkernel/intern/object_update.cc:357\n - 1 0x13bb0a4d in BKE_object_select_update /home/bastien/blender/src/source/blender/blenkernel/intern/object_update.cc:393\n - 2 0x168103db in operator() /home/bastien/blender/src/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1532\n - 3 0x1684125a in __invoke_impl<void, blender::deg::DepsgraphNodeBuilder::build_object_data_geometry(Object*)::<lambda(Depsgraph*)>&, Depsgraph*> /usr/include/c++/12/bits/invoke.h:61\n - 4 0x1683a429 in __invoke_r<void, blender::deg::DepsgraphNodeBuilder::build_object_data_geometry(Object*)::<lambda(Depsgraph*)>&, Depsgraph*> /usr/include/c++/12/bits/invoke.h:111\n - 5 0x1683289f in _M_invoke /usr/include/c++/12/bits/std_function.h:290\n - 6 0x1696ceb0 in std::function<void (Depsgraph*)>::operator()(Depsgraph*) const /usr/include/c++/12/bits/std_function.h:591\n - 7 0x1696787c in evaluate_node /home/bastien/blender/src/source/blender/depsgraph/intern/eval/deg_eval.cc:101\n - 8 0x16967caf in deg_task_run_func /home/bastien/blender/src/source/blender/depsgraph/intern/eval/deg_eval.cc:119\n - 9 0x2f3f586c in Task::operator()() const /home/bastien/blender/src/source/blender/blenlib/intern/task_pool.cc:164\n - 10 0x2f3f9022 in tbb::internal::function_task<Task>::execute() /opt/lib/tbb/include/tbb/task.h:1059\n - 11 0x7f39bce4cff4 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) (/opt/lib/tbb/lib/libtbb.so+0x2cff4)\n - 12 0x7f39bce4d382 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) (/opt/lib/tbb/lib/libtbb.so+0x2d382)\n - 13 0x7f39bce32fb6 in tbb::internal::arena::process(tbb::internal::generic_scheduler&) (/opt/lib/tbb/lib/libtbb.so+0x12fb6)\n - 14 0x7f39bce4206f in tbb::internal::market::process(rml::job&) (/opt/lib/tbb/lib/libtbb.so+0x2206f)\n - 15 0x7f39bce4605b in tbb::internal::rml::private_worker::run() (/opt/lib/tbb/lib/libtbb.so+0x2605b)\n - 16 0x7f39bce46298 in tbb::internal::rml::private_worker::thread_routine(void*) (/opt/lib/tbb/lib/libtbb.so+0x26298)\n - 17 0x7f39ab0a7fd3 in start_thread nptl/pthread_create.c:442\n #18 0x7f39ab12866b in clone3 ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\n\n0x61c0002868b0 is located 48 bytes inside of 1704-byte region [0x61c000286880,0x61c000286f28)\nfreed by thread T137 here:\n - 0 0x7f39bc6b76a8 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:52\n - 1 0x2f43bbfa in MEM_lockfree_freeN /home/bastien/blender/src/intern/guardedalloc/intern/mallocn_lockfree_impl.c:117\n - 2 0x134f9b18 in BKE_id_free_ex /home/bastien/blender/src/source/blender/blenkernel/intern/lib_id_delete.c:168\n - 3 0x134f9b49 in BKE_id_free /home/bastien/blender/src/source/blender/blenkernel/intern/lib_id_delete.c:174\n - 4 0x1364372f in BKE_mesh_eval_geometry /home/bastien/blender/src/source/blender/blenkernel/intern/mesh.cc:1876\n - 5 0x1681190d in operator() /home/bastien/blender/src/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1561\n - 6 0x16841442 in __invoke_impl<void, blender::deg::DepsgraphNodeBuilder::build_object_data_geometry_datablock(ID*)::<lambda(Depsgraph*)>&, Depsgraph*> /usr/include/c++/12/bits/invoke.h:61\n - 7 0x1683a7bb in __invoke_r<void, blender::deg::DepsgraphNodeBuilder::build_object_data_geometry_datablock(ID*)::<lambda(Depsgraph*)>&, Depsgraph*> /usr/include/c++/12/bits/invoke.h:111\n - 8 0x16832ad5 in _M_invoke /usr/include/c++/12/bits/std_function.h:290\n - 9 0x1696ceb0 in std::function<void (Depsgraph*)>::operator()(Depsgraph*) const /usr/include/c++/12/bits/std_function.h:591\n - 10 0x1696787c in evaluate_node /home/bastien/blender/src/source/blender/depsgraph/intern/eval/deg_eval.cc:101\n - 11 0x16967caf in deg_task_run_func /home/bastien/blender/src/source/blender/depsgraph/intern/eval/deg_eval.cc:119\n - 12 0x2f3f586c in Task::operator()() const /home/bastien/blender/src/source/blender/blenlib/intern/task_pool.cc:164\n - 13 0x2f3f9022 in tbb::internal::function_task<Task>::execute() /opt/lib/tbb/include/tbb/task.h:1059\n #14 0x7f39bce4cff4 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) (/opt/lib/tbb/lib/libtbb.so+0x2cff4)\n\npreviously allocated by thread T0 here:\n - 0 0x7f39bc6b83b7 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:77\n - 1 0x2f43c32f in MEM_lockfree_callocN /home/bastien/blender/src/intern/guardedalloc/intern/mallocn_lockfree_impl.c:223\n - 2 0x134ede74 in BKE_libblock_alloc_notest /home/bastien/blender/src/source/blender/blenkernel/intern/lib_id.c:1101\n - 3 0x134edfdc in BKE_libblock_alloc /home/bastien/blender/src/source/blender/blenkernel/intern/lib_id.c:1113\n - 4 0x134ef71d in BKE_libblock_copy_ex /home/bastien/blender/src/source/blender/blenkernel/intern/lib_id.c:1274\n - 5 0x134e9788 in BKE_id_copy_ex /home/bastien/blender/src/source/blender/blenkernel/intern/lib_id.c:637\n - 6 0x13632b83 in BKE_mesh_copy_for_eval /home/bastien/blender/src/source/blender/blenkernel/intern/mesh.cc:1109\n - 7 0x122b0c00 in operator() /home/bastien/blender/src/source/blender/blenkernel/intern/DerivedMesh.cc:1130\n - 8 0x122c264c in operator() /opt/lib/tbb/include/tbb/task_arena.h:96\n - 9 0x7f39bce332b4 in tbb::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long) (/opt/lib/tbb/lib/libtbb.so+0x132b4)\n #10 0x7fff66c6047f ([stack]+0x4b47f)\n```\n\nThis trace makes it pretty clear that `BKE_object_select_update` from object evaluation code accesses data that has been freed by Mesh evaluation code (`BKE_mesh_eval_geometry`).\n\nNote that skipping (returning) here does not help, since code will crash in another place then (like inside the `BKE_library_foreach_ID_link` call in `deg_validate_copy_on_write_datablock`).\n\n----------------------------\n\nPS: Also seems weird to me that freeing runtime `mesh_eval` in `BKE_mesh_eval_geometry` is not protected by a lock on `mesh->runtime->eval_mutex`?\n", "GPU Codegen parser warning\nI'm working on a patch for Gabor Noise: 110802\n\n@OmarEmaraDev suggested opening a bug report.\n\nThe function below has to be written with a return type rather than void.\n\nUsing `void` generates the following gpu_codegen parser warning. `Unknown parameter type \"GaborParams\"`\n\n```\nvoid gabor_sample(\n GaborParams gp, float orand, float orand2, float prand, out vec3 omega, out float phi)\n```\n\nAs a workaround I have written the function with a return type of `GaborParams` which solves the issue.\n\n`GaborParams` is a struct of floats.\n\n```\nGaborParams gabor_sample(\n GaborParams gp, float orand, float orand2, float prand, out vec3 omega, out float phi)\n{\n float pvar = mix(0.0, prand * 2.0 - 1.0, gp.phase_variance);\n phi = M_2PI * pvar + gp.phase;\n\n /* Anisotropic direction. */\n if (gp.anisotropic == 1) {\n omega = gp.direction;\n }\n else { /* Isotropic. */\n float ovar = M_PI * (orand * 2.0 - 1.0);\n float omega_t = ovar * gp.rot_variance - gp.rotation;\n float cos_omega_p = 1.0 - 2.0 * orand2;\n float sin_omega_p = sqrt(1.0 - cos_omega_p * cos_omega_p);\n float sin_omega_t = sin(omega_t);\n float cos_omega_t = cos(omega_t);\n omega = normalize(vec3(cos_omega_t * sin_omega_p, sin_omega_t * sin_omega_p, cos_omega_p));\n }\n /* Return GaborParams to workaround gpu_codegen parser warning when return type is set to void :\n * Unknown parameter type \"GaborParams\". */\n return gp;\n}\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", "Memory Leak in Blender 3.1.2 Metal CPU + GPU\nOperating system: macOS 64 Bits (12.3.1?)\nGraphics card: AMD RX 6900 XT x 2\nCPU: i9 10859K\nRam: 64Gigs (2x32)\n\nBroken: version: 3.1.2\nWorked: -\n\nI've been encountering a consistent Memory Leak using the new 3.1.2 Version, rendering in Cycles \"Metal\", on both GPUs and the CPU.\nAll rendering settings are default - the output Render samples are set to 1200 cycles.\nAll export settings are default - Resolution is set to 1920x1080 at 100%\n\nThere is no difference when Cycles Render Rate or Resolution Output is changed - I always end up with a memory leak in that I can render around 440 Frames before the memory has become full enough to suddenly increase render time. The system eventually reaches about 60.64Gigs of usage and stays there:\n|||\n| -- | -- | -- |\n\n**Workaround:** Render only 400 frames. Close Blender, restart and start the next render at Frame 401, etc.\n\n- \n\n---\nStill new to Version 3.1.2, quite different from 2.7 But I begin to really like the new layout and system - big shout out to all developers!\nJens", "Blender continuosly freezes when transforming an object\nOperating system: Ubuntu 20.04.4 LTS\nGraphics card: ntel Corporation Skylake GT2 [HD Graphics 520] (rev 07)\n\nBroken: 3.1.2\n\n\nBlender continuosly freezes when transforming an object.\n\nCreate a General project (With the default cube). Scale the cube in every direction. Continue doing this and it the app will freeze. The debug log is filled with the following message:\n\n\n> INFO (gpu.debug): Notification : memory mapping a busy \"miptree\" BO stalled and took 0.039 ms.\n\n\n\n\n", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "No space mouse support in --debug mode\nOperating system: macOS 12.6.7\nGraphics card: Apple M1 Max GPU\n\nBroken: 3.6.1\n\nConnexion Space Mouse does not work if Blender is launched with --debug.\nNormal launch works.\nIs this related to #93170 ?\n\nLaunch Blender with --debug\nTry to use Space Mouse\n\n", "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", "Eevee Light Limitation testcase T91611 crashes on Win11 Intel Arc GPU \nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) Arc(TM) A770 Graphics Intel 4.5.0 - Build 31.0.101.4090\n(note: also tested on driver .4032 latest stable, which also crashes)\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 3.3.2, 3.4.1\n\n \n\nWhile tracking down another bug (direct lights not appearing in Eevee), I found that the test case for #91611 hard crashes blender.\n\nAnalyzing the code, the crash happens because the GPU module cannot create a 3D texture with dimensions `4096x4096x576`. The result is `nulltptr`\n```\nif (!success) {\n delete tex;\n return nullptr;\n}\n```\n\nbacktrace:\n\n```\n>\tblender.exe!blender::gpu::Texture::attachment_type(int slot) Line 257\tC++\n\n \tblender.exe!GPU_framebuffer_texture_attach_ex(GPUFrameBuffer * gpu_fb, GPUAttachment attachment, int slot) Line 316\tC++\n \tblender.exe!GPU_framebuffer_texture_layer_attach(GPUFrameBuffer * fb, GPUTexture * tex, int slot, int layer, int mip) Line 331\tC++\n \tblender.exe!EEVEE_shadows_draw_cubemap(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata, int cube_index) Line 203\tC\n \tblender.exe!EEVEE_shadows_draw(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata, DRWView * view) Line 316\tC\n \tblender.exe!eevee_draw_scene(void * vedata) Line 247\tC\n \tblender.exe!drw_engines_draw_scene() Line 1111\tC\n \tblender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1767\tC\n \tblender.exe!DRW_draw_view(const bContext * C) Line 1637\tC\n \tblender.exe!view3d_draw_view(const bContext * C, ARegion * region) Line 1552\tC++\n \tblender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1587\tC++\n \tblender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 551\tC\n \tblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 960\tC\n \tblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 1127\tC\n \tblender.exe!wm_draw_update(bContext * C) Line 1385\tC\n \tblender.exe!WM_main(bContext * C) Line 648\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 589\tC\n \t[External Code]\t\n\n```\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n- Download and open any of the test cases bellow\n- Click Render Preview in viewport\n\n[Light ViewportRender ERror.blend](Light_ViewportRender_ERror.blend)\n[lighttest2.blend](lighttest2.blend)", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "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", "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", "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", "[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" ]

[ "Blender crashes on startup\nBlender crashes when I try to run it on my computer with CentOS 8 and Nouveau. On my other computer with CentOS 8 and an Intel graphics card everything works without problems.\n\nOperating system: Linux-4.18.0-147.8.1.el8_1.x86_64-x86_64-with-centos-8.1.1911-Core 64 Bits\nGraphics card: NVE4 nouveau 4.3 (Core Profile) Mesa 19.1.4\n\nBroken: version 2.83 (sub 15) build date: 2020-05-08\nBroken: version 2.90 (sub 0) build date: 2020-05-08\nWorked: version: 2.82 (sub 7)\n\n```\n$ cd blender-2.83-ce76e17584ee-linux64/\n$ ./blender\nfound bundled python: /home/user/Downloads/blender-2.83-ce76e17584ee-linux64/2.83/python\n/usr/include/c++/8/bits/stl_deque.h:1385: std::deque<_Tp, _Alloc>::reference std::deque<_Tp, _Alloc>::operator[](std::deque<_Tp, _Alloc>::size_type) [with _Tp = nv50_ir::ValueRef; _Alloc = std::allocator<nv50_ir::ValueRef>; std::deque<_Tp, _Alloc>::reference = nv50_ir::ValueRef&; std::deque<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.\nAborted (core dumped)\n```\n\n```\n$ cd blender-2.90-6f985574b775-linux64/\n$ ./blender\nfound bundled python: /home/user/Downloads/blender-2.90-6f985574b775-linux64/2.90/python\n/usr/include/c++/8/bits/stl_deque.h:1385: std::deque<_Tp, _Alloc>::reference std::deque<_Tp, _Alloc>::operator[](std::deque<_Tp, _Alloc>::size_type) [with _Tp = nv50_ir::ValueRef; _Alloc = std::allocator<nv50_ir::ValueRef>; std::deque<_Tp, _Alloc>::reference = nv50_ir::ValueRef&; std::deque<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.\nAborted (core dumped)\n```\n\n" ]

[ "Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.5.0\n\nif I change the offset (or start frame) of the sequence in the shader editor, I would expect it to also change in the image editor or wherever I am using the same image sequence, otherwise it causes discrepancies and buggy viewport display (since we dont know which offset is displayed in the viewport). \n\nJust change the offset of 1 of the 3 displayed image sequence settings displayed... the other 2 won't follow.\n\nCycles does this fine btw.", "Wrong SubSurf modifier results with inconsistent normals\nOperating system: Windows 10 Enterprise Version 1803\nGraphics card: 2 x GTX1080 ti\n\nBroken:\nblender2.8, 2018-12-05\n\nFrom latest builds subsurf modifier make a wrong subdivision of geometry as displayed in the attached files.\nBefore 18/20 November the behaviour of subsurf modifier was ok.\nI am sure because I did an animation on that date and the subdivided vase was ok.\n\nBest regards,\n\nUmberto\n\n\n\n\n\n[ceramic.blend](ceramic.blend)", "Shader Image Mapping Issue\nOperating system: Mac OSX High Sierra\nGraphics card: NVIDiA GeForce\n\nBroken: (example: 2.92 Master 02948a2cab44\nWorked: N/A\n\nIt seems the mapped image is not applying to an object that's linked by Object Data\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[repro2.blend](repro2.blend)\n\nIn this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):\n\n\n\n\n\n\n---\nOriginal report:\n[modular.blend](modular.blend)\n\nLook at the image reference in the shader for the second to last vehicle. All other vehicles with similar bodies are linked and are following the map except the second to last object. After linking the body of that vehicle, the object appears to follow the map until you render the image. ", "Curve extrude offset default value is 1 (instead of 0)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500M ATI Technologies Inc. 4.5.13587 Core Profile Context 19.40.30.02 26.20.14030.2002\n\nBroken: version: 2.93.0\nWorked: -\n\nCurve > Object Data Properties > Geometry > Offset\nIf you reset the \"Offset\" value with right click+*Reset to Default value* or by pressing backspace the value is set to 1\n\n - Open blender\n - Create a curve\n - Extrude it\n - Reset the offset to the default value\n - Offset is set to 1 instead of 0\n\n**Expected behaviour**\nThe default value for this should be 0. If a curve is created the value is 0 without any changes\n\n[curve reset offset.blend](curve_reset_offset.blend)\n", "Cycles box mapping not working with rotated texture coordinates\nubuntu 14.04, 630GT, 4930k\n\nBroken: 2.74\n\n\nbox mapping doesn't work with object mapping (object) if the object is rotated (only 1 side is properly projected)\n\n\n1. open the blend file\n2. copy \"Cube\" and rotate it (90 degress)\n3. render\n\n\n\n\n\n\n\n\n", "Pinning data (mesh, curve, grease pencil, lattice, particle system) makes certain tabs/options disappear (vertex groups, shapekeys facemaps)\nOperating system: Microsoft 10\nGraphics card:GeForce GTX 10606GB\n\nBroken: 2.93\nWorked: don't know\n\n**in the properties editor, in object data properties, the pin toggle hides vertex groups and shapekeys**\n\n- select default cube\n- go to properties editor\n- press object data properties tab\n- press the pin button\n", "Resize a incoming fluid cause fluid to stop flowing in\nOperating system: windows 11\nGraphics card: RTX\n\nBlender 3.6.1\n\n\nGood morning\n\nFirst thank you for the work done on Blender.\n\nI think I found a bug. In fluid simulations when we resize an incoming flow, it often happens that the flow is no longer able to generate a fluid.\nI have seen this with eco-spheres\n\nThanks in advance .\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "When you clear measurements through View > Annotations, they don't vanish immediately\nOperating system: Windows\nGraphics card: GTX-2080\n\nBroken: 3.4.1\n\n\nDeleting measurement annotations appears to be broken because the UI is not refreshed until you change tool.\n\n\n1. Create some measurements\n2. Open View settings Tab\n3. Remove ruler Annotations\n\nExpected behavior: Measurements are removed and action can be undone.\n\nCurrent behavior: The Annotation is no longer visible in the annotation list, but still shown in edit view.\n\nHere is a screen recording: 185530\n\n", "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", "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", "Texture Mapping issues on large brush radius\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\n\nWhen a large brush radius for textured brushes in sculpt mode, the outer-most affected geometry doesn't apply the texture fully. This is especially noticeble on the Clay Strips and Paint brushes when the stroke method is set to anchored.\n\n\n\n\n\nBlend file = [bug.blend](attachment)\n\n- Open the File\n- Use the provided paint brush and clay strips brush on a subdivided cube or suzanne head like shown\n- Notice how the outer edges of the falloff is not updating the geoemtry fully\n\n", "Add option to automatically adjust UV based on curve length per span\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nGenerated UV's from curves are always normalized in UV space (circumference and length are always 0-1). This results in UV stretching as the vertices of the curve are changed. I suggest adding an option to automatically adjust the generated UV's of the curve so that the UV's position in the X axis are adjusted per length of each span.\n\nIn some cases it's really handy to keep UV's completely normalized, so let's add this as an option and not a behaviour that cannot be turned off. I'm all for keeping it as a default behaviour though.\n\nHere is a screengrab mockup that hopefully makes this suggestion easy to understand.\n\n [curve uv correction.mp4](curve_uv_correction.mp4)\n\n---\n\nSuggested UI mockup in object data properties\n\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)", "Particles reset their position when using time stretching\nMinimal reproduction steps:\n- Add a particle system to the default cube and make it renderable.\n- Set the old time stretching setting to 20 and leave the new at 100.\n- Play the animation until frame 90 and render.\n- Find that the particles are sticking on the object as opposed to their correct position in the viewport.\n- Render again. They now have their correct position.\n- Play another 5 frames.\n- Render again, they are now sticking to the object again.\n\n[timeStretchingBadRender.blend](timeStretchingBadRender.blend)\n\n**Original Report**\n\nHello,\n\ni am using blender-3.1.0-linux-x64 and working on particles with time stretching but the viewport display is correct.\n\nattached is the blend file. [experiment with text.blend](experiment_with_text.blend) \n\nproblem seen in cpu/gpu/cycles/evee.\n\nregards,\nYaju", "Simulation nodes: Automatic cache reset behavior\n# Terminology\nTo make discussion of inputs and outputs easier, the following naming convention is be used:\n* Input sockets of the “Simulation Input” node are *simulation inputs*\n* Output sockets of the “Simulation Input” node are *iteration inputs*\n* Input sockets of the “Simulation Output” node are *iteration outputs*\n* Output sockets of the “Simulation Output” node are *simulation outputs*\n\n\n# Stepping\nSome node evaluations don’t involve a time step (e.g. loading a file). In those cases the simulation inputs are used unmodified as simulation outputs.\n\n\nIf an iteration is computed during node evaluation then the simulation outputs are defined as follows:\n1. When cached data is available for the exact current frame the outputs simply expose the cached data.\n Simulation inputs are ignored.\n \n\n2. When cached data for the current frame is not available, but exists for an earlier frame, an iteration is performed with the necessary time step.\n Simulation inputs are ignored.\n Iteration inputs are cached data.\n \n\n3. When previous data is unavailable or invalid, then the current simulation inputs are used and piped straight to iteration inputs.\n This is only correct for the start frame (to keep results deterministic), so on other frames a warning should be shown if no cached input is available.\n \n\n# Invalidating Caches\nA cache becomes invalid if the scene data is changed such that the output for the current frame will be different. This could be because\n1. The simulation input on the start frame is different.\n2. Scene data used during the iteration (e.g. an Object Info node) changed.\n\nIn practice it will be difficult to determine precisely when changes do or do not affect the simulation. False positives have to be expected, that is: invalidating the cache when it wouldn’t have to be. This is because we have to rely on coarse depsgraph dependencies. It is preferable to invalidate the cache unnecessarily than to keep cached results and miss potential changes. Over time the dependencies affecting nodes may be refined for more stable caching.\n\n## Reset\nThe term \"reset\" describes the point when a simulation reverts to the initial scene data, typically when animation jumps back to the start frame (Point 3 in [Stepping](#stepping)).\n\nConditions that can cause a reset (only when cache is invalid!)\n* Jump to start frame\n* Jump to other frame, with a warning\n* Start frame is changed (might invalidate cache)\n\nA reset should not happen just because the cache got invalidated. For example: A particle simulation might use an object as emitter. The user moves this object manually during simulation, which constantly invalidates the cache. However, the particle simulation should not *reset*: all the current particles remain in the simulation.\n\nThe last valid simulation state is always retained even if the rest of the cache is invalidated. That way simulations can be tested dynamically.\n\n# Baking\nBaked caches are never invalidated automatically.\n\nIf a baked cache exists then the simulation input should never be used and no further iterations should happen. The simulation output is always read from the cache.\n\nA baked cache must be freed explicitly, at which point it reverts back to a dynamic cache.\n\n# Notes\n* “Memory cache” vs “disk cache” distinction should not be relevant to most of the examples below.\n* Undo is effectively a file load operation too.\n" ]

[ "Out of edit mode, Texture Space is behaving like BoundBox\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.1 26.20.13001.9005\n\n\nBroken: version: 2.80 (sub 74), 2019-07-10\nWorked: before 15dd289992\n\n\nWhen a mesh has modifiers, they affect the Texture Space.\nOriginally the Texture Space depended only on Mesh in Edit Mode.\n\nOpen the attached file and compare the Texture Space in and out of edit mode.\n\n[TexSpaceBug.blend](TexSpaceBug.blend)\n\n" ]

[ "USD Alab v2 import errors\nWhen loading the latest version of the Alab scene (v2), materials don't render correctly. I've narrowed the problem down to the following issues:\n\n - Some of the UV primvars in the Alab scene are of type `Float2Array` which is unusual. The Blender USD importer expects UV primvars to be of type `TexCoord` (e.g., `TexCoord2fArray`). Hence, some of the Alab UV maps are not getting imported, resulting in the wrong UVs getting applied in the Blender scene. The importer logic should be extended to import `Float2Array` primvars as texture coordinates as well.\n - The USD importer is attempting to read the `varname` input of the `UsdPrimvarReader_float2` shader as a `TfToken`, which conforms to the original `UsdPreviewSurface` specification. However, in the latest specification, `varname` is a string. This type mismatch when reading the input can result in an empty map name in the `UV Map` node in Blender and the wrong texture coordinates getting applies. \n - For materials that have an authored opacity value, the importer sets the material `Blend Mode` to `Alpha Blend`. In the Alab scene this causes artifacts due to object sorting issues. Setting the `Blend Mode` to `Alpha Hashed` provides improved results.\n\nTo reproduce the issue, the Alab USD can be downloaded here:\n\nalab/\n\nI created branch `tmp-usd-alab-v2-#100452` with work in progress on fixes so far.", "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", "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", "UI: Excessive cut-off while searching in keymap preferences\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 2.50alpha1 (searchbox for input first appeared)\nWorked: never\n\nWhen searching in keymap text name of a category will be cut too much.\nIt does not happen with add-ons or properties editor search.\n\n1. Open Keymap in preferences.\n2. Resize window. Notice that category name will be cut off only when it really doesn't have any spare space.\n3. Start searching for anything, for example `grease pencil`.\n4. Resize window. Now category name will be cut off way too easily, having spare space several times largen than it's full text.\n[Excessive cutoff2022-01-19 12-55-36.mp4](Excessive_cutoff2022-01-19_12-55-36.mp4)", "Duplicated volumes act like they are linked\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.93.1\n\n\nDuplicating a volume object creakes linked volume objects\n\n\n\n\n- Add an empty volume object\n\n- Shift-D to duplicate it\n\n- Change the density to 0.5\n\n- You can see the density is also set to 0.5 for both\n\n- Open the attached VDB from thee OpenVdb file path\n\n- You can now see that the VDB is assigned to the both.\n\n[torus.zip](torus.zip)\n\n\n\n\n\n", "Cycles - Viewport render preview stucked on the first sample - in a scene a DupliVerts objet parenting instances owned by more than one Groups\nBlender 2.78 (2.78 2016-10-24, Blender Foundation)\nMac Book Pro Retina 2013\n2.6 Ghz Intel Core i7 - 16GO 1600 MHz DDR3\nOSX 10.9.2\n\nUsing Cycles\n\nIn my scene with a parent DupliVerts object (Properties /Object / Duplication / Verts), with inside of if instances of Group.\nWhen those childs instances are from one group, that's ok.\nBut when they are from several groups, the 3D viewport render preview is stucked to the sample 1, rendered without ending !\n\nGood for heating the room ;)\n\nTo test, simply [Shift] - [x] in 3d the viewport in my blend to see this issue\nHope this help, keep the good work !\n[DupliVerts_and_Groups_BUG_with_Render_ViewPort_Cycles.blend](DupliVerts_and_Groups_BUG_with_Render_ViewPort_Cycles.blend)", "Import and Export options look identical in contexts besides the File menu, such as QuickFavorites. (Low priority)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 2.93.0\n\n**Short description of error:**\nThe *import* and *export* buttons for the same file types are identical, and indistinguishable if these buttons are found in some other contexts, for example the QuickFavorites menu.\n... I understand that it's easier to see than to communicate. \n\n - Start from any template\n - Right-click the button for File > Import > STL, add to QuickFavorites\n - Do the same for Import\n - Open QuickFavorites now (Q)\n - Notice that you cannot tell which one is import and which is export without the tooltips.\n\n\n\n\n\n", "Simplify duplication options in user preferences.\nCurrently we have one duplicate option for each and every object data type (in user preferences, 'Editing' section, 'Duplicate Data' panel).\n\nTopic of this task is whether we should keep things like that, or if we should rather simplify options by defining 'categories' instead.\n\nCategories could be:\n* Geometry *(meshes, curves, surfaces, fonts, mballs, lattices, armatures, gpencil)*\n* Physics *(hair, pointcloud, volume, particles)*\n* Lights *(lamp, lightprobe)*\n* Actions *(actions)*\n* Shading *(materials)*\n* Camera *(cameras)*\n* Speaker *(speakers)*\n\nThis could also include better handling of 'new' things, e.g. duplicating (deep copy) of geometry nodes when 'Geometry' is enabled, duplicating (deep copy) of shading nodes when 'shading' is enabled, and so on.\n\nNOTE: this was triggered by #90638 (Inconsistent object data behavior when link-duplicating collections.) and its fix 65dbeb1d81, which required adding three new options there to fully cover all current object types...", "Multiple pop-ups overlayed with same functioning on Right Clicking `Online Manual` button\nOperating system: Windows 10 Pro\nGraphics card: GeForce GTX 1650\n\nBroken: version: 3.5.0 Alpha, branch: master, commit date: 2022-12-31, hash: 614704f90c, type: release\n\nRight Click on any operation/property on interface until `Online Manual` button is available and keep right clicking on `Online Manual` to get prompted again to right on `Online Manual` and keep going to create an infinite error pop-ups type screen. \n\n- Keep right clicking on `Online Manual` option in context menu\n", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "Python: Large memory leak if an operator modifies certain properties during the \"load_post\" handler\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.3.3\nBroken: version: 3.4.x through 3.6 as well\nWorked: n/a\n\nThere's a large memory leak if an Operator modifies certain properties during the `load_post` handler\n\n\n- Install the provided `leak.py` addon\n- Enable it and save preferences\n- Quit Blender\n- From the command line execute `blender --debug-memory`\n- Once loaded, quit blender again\n- Notice the large amount of leaks\n\n`Error: Not freed memory blocks: 543, total unfreed memory 0.040207 MB`\n\nThe property being modified -- see the 2 \"NOTE\" comments in provided addon for clues:\n```python\n def execute(self, context):\n \n # NOTE: This statement causes a large leak\n context.space_data.show_region_tool_header = False\n```\n\nThe leaks looks like:\n```\nError: Not freed memory blocks: 552, total unfreed memory 0.040894 MB\nWM_event_add_keymap_handler len: 80 000002128B026558\nWM_event_add_dropbox_handler len: 40 00000212EF01CE58\nWM_event_add_ui_handler len: 80 000002128B0264B8\nWM_event_add_keymap_handler len: 80 000002128B026418\nWM_event_add_keymap_handler len: 80 000002128B026378\nWM_event_add_keymap_handler len: 80 000002128B0262D8\nWM_event_add_keymap_handler len: 80 000002128B026238\nWM_gizmomap_add_handlers len: 40 00000212EF01CDE8\nWM_event_add_keymap_handler_dynamic len: 80 000002128B025AB8\n...\n...\n```\n\n", "Tests: fix script_load_keymap hierarchy test\nOperating system: verified Win32/Win64/Linux64/Mac didn't test Linux32\nGraphics card: N/A\n\nBroken: 2f77175fecc7\nWorked: \n\n\n`script_load_keymap` is passing on all platforms, however looking a little closer at the output, it really should not have passed by the looks of it.\n\nWindows\n```\n[HANDLER_OUTPUT] \n Start 38: script_load_keymap\n\n[HANDLER_VERBOSE_OUTPUT] \n\n38: Test command: D:\\a\\1\\build_windows_Release_x64_vc15_Release\\bin\\Release\\blender.exe \"--background\" \"-noaudio\" \"--factory-startup\" \"--python\" \"D:/a/1/s/tests/python/bl_keymap_completeness.py\"\n\n38: Test timeout computed to be: 10000000\n38: Blender 2.80 (sub 74) (hash d30f72dfd8ac built Wed 06/19/2019 10:55 PM)\n38: Unable to create directory C:\\Users\\VssAdministrator/.thumbnails/large/\n38: Unable to create directory C:\\Users\\VssAdministrator/.thumbnails/fail/blender/\n38: found bundled python: D:\\a\\1\\build_windows_Release_x64_vc15_Release\\bin\\Release\\2.80\\python\n38: Traceback (most recent call last):\n38: File \"<string>\", line 1, in <module>\n38: File \"D:/a/1/s/tests/python/bl_keymap_completeness.py\", line 90, in <module>\n38: main()\n38: File \"D:/a/1/s/tests/python/bl_keymap_completeness.py\", line 80, in main\n38: err = check_maps()\n38: File \"D:/a/1/s/tests/python/bl_keymap_completeness.py\", line 52, in check_maps\n38: for km_id in sorted(test):\n38: TypeError: '<' not supported between instances of 'function' and 'function'\n38: Keymaps that are in 'bl_keymap_utils.keymap_hierarchy' but not blender\n38: \n38: Blender quit\n[HANDLER_OUTPUT] \n 38/103 Test #38: script_load_keymap ..................\n Passed 1.15 sec```\n\nMac\n```\n2019-06-19T23:14:58.8907830Z Start 38: script_load_keymap\n2019-06-19T23:14:58.8909090Z \n2019-06-19T23:14:58.8909990Z 38: Test command: /Users/vsts/agent/2.153.2/work/1/s/build/bin/blender.app/Contents/MacOS/blender \"--background\" \"-noaudio\" \"--factory-startup\" \"--python\" \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\"\n2019-06-19T23:14:58.8910100Z 38: Test timeout computed to be: 10000000\n2019-06-19T23:14:58.9466020Z 38: Blender 2.80 (sub 74) (hash d30f72dfd8ac built 2019-06-19 23:13:34)\n2019-06-19T23:14:59.0865090Z 38: found bundled python: /Users/vsts/agent/2.153.2/work/1/s/build/bin/blender.app/Contents/Resources/2.80/python\n2019-06-19T23:14:59.7974200Z 38: Traceback (most recent call last):\n2019-06-19T23:14:59.7974580Z 38: File \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\", line 90, in <module>\n2019-06-19T23:14:59.7974830Z 38: main()\n2019-06-19T23:14:59.7975000Z 38: File \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\", line 80, in main\n2019-06-19T23:14:59.7975190Z 38: err = check_maps()\n2019-06-19T23:14:59.7975270Z 38: File \"/Users/vsts/agent/2.153.2/work/1/s/tests/python/bl_keymap_completeness.py\", line 52, in check_maps\n2019-06-19T23:14:59.7975320Z 38: for km_id in sorted(test):\n2019-06-19T23:14:59.7976280Z 38: TypeError: '<' not supported between instances of 'function' and 'str'\n2019-06-19T23:14:59.7976740Z 38: Keymaps that are in 'bl_keymap_utils.keymap_hierarchy' but not blender\n2019-06-19T23:14:59.8211820Z 38: \n2019-06-19T23:14:59.8212080Z 38: Blender quit\n2019-06-19T23:14:59.8264730Z 38/103 Test #38: script_load_keymap .................. Passed 0.94 sec\n```\n\nLinux\n```\n2019-06-19T22:40:21.3651709Z Start 38: script_load_keymap\n2019-06-19T22:40:21.3651763Z \n2019-06-19T22:40:21.3652247Z 38: Test command: /home/vsts/work/1/build/bin/blender \"--background\" \"-noaudio\" \"--factory-startup\" \"--python\" \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\"\n2019-06-19T22:40:21.3652639Z 38: Test timeout computed to be: 10000000\n2019-06-19T22:40:21.3853468Z 38: Blender 2.80 (sub 74) (hash d30f72dfd8ac built 2019-06-19 22:31:01)\n2019-06-19T22:40:21.4068327Z 38: found bundled python: /home/vsts/work/1/build/bin/2.80/python\n2019-06-19T22:40:22.0448958Z 38: Traceback (most recent call last):\n2019-06-19T22:40:22.0449067Z 38: File \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\", line 90, in <module>\n2019-06-19T22:40:22.0449108Z 38: main()\n2019-06-19T22:40:22.0449150Z 38: File \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\", line 80, in main\n2019-06-19T22:40:22.0449213Z 38: err = check_maps()\n2019-06-19T22:40:22.0449255Z 38: File \"/home/vsts/work/1/s/tests/python/bl_keymap_completeness.py\", line 52, in check_maps\n2019-06-19T22:40:22.0449294Z 38: for km_id in sorted(test):\n2019-06-19T22:40:22.0450043Z 38: TypeError: '<' not supported between instances of 'function' and 'function'\n2019-06-19T22:40:22.0450290Z 38: Keymaps that are in 'bl_keymap_utils.keymap_hierarchy' but not blender\n2019-06-19T22:40:22.0677065Z 38: \n2019-06-19T22:40:22.0677122Z 38: Blender quit\n2019-06-19T22:40:22.0718362Z 38/103 Test #38: script_load_keymap .................. Passed 0.71 sec\n2019-06-19T22:40:22.0720194Z test 39\n```\n\nbonus weirdness:\n \nWin64 and Linux report \n> TypeError: '<' not supported between instances of 'function' and 'function'\n\n\nwhile Mac and win32 report \n> TypeError: '<' not supported between instances of 'function' and 'str'\n\n\ngiven all builds are of the identical commit and use identical versions of all deps, it's \"kinda weird\" \n\n\nrun the `script_load_keymap` test", "Workspace duplicate resets my tweak tool back to default select box\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 11)\nWorked: ???\n\nAnd EACH time I create new workspace I forced to change it back to tweak, because i prefer it.\nIt is a pain in the … code.\n\nWhy do I think it is a bug? Because scale cage or annotation are saved.\n[2020-04-02_16-44-41.mp4](2020-04-02_16-44-41.mp4)\n\n", "Auto keyframing causes Duplicate Linked object to change location \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.1.0\nWorked: Never (2.8+)\n\n- Open new general animation template,\n- Turn on auto keyframing\n- Add a mesh object\n- Alt+D create few Duplicate Linked objects,\n# Change frame\n\nDuplicate Linked objects will change location.\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)" ]

[ "Keymap Duplicates on import\nWindows 10 64 bit\nBlender 2.92/3\n\nImporting a previously exported keymap will append on top of old keymaps creating duplicates, bloating file size the of the saved keymap file.\n\nReproduce by exporting keymap and reimporting a few times then doing a search by name of a keymap. Should see the duplicate entry." ]

[ "Export and import collada = distorted mesh.\nOperating system: Linux Debian.\nGraphics card:\n\n3.1.2\n\nWhen doing a roundtrip (export then import) in collada from a mixamo animation, the model is completely distorted at the reimport stage.\n\nDownload any character in mixamo, save it in Collada from the service, import it in Blender, export it as dae, then reimport it. \nEven with all the extras options activated, Blender fails to reimport it properly. Which means that either the export or the import stage is breaking something.\n\nThe same thing doesn't occur when exporting to Gltf\n\nPlease try with the attached blend: [ex.blend](ex.blend).\n\nbefore\n\n\nafter\n", "alembic exporter is changing material names.\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\nopen file:\n[alembic duplicate material after import.blend](alembic_duplicate_material_after_import.blend)\n\nselect cube (not that it's material is named material.003\nexport cube as alembic with the following options:\n\nhide the cube\nre-import the alembic\nnote the material on the new cube is called material_003 and therefore a new material is created instead of using the correct material (material.003)\n\nThis is extremely problematic considering blender automatically adds '.###' to the end of all duplicates.", "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", "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)", "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", "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", "Report statistics for all on-screen geometry\nThis task proposes to ignore instancing when reporting statistics.\n\nCurrently statistics ignores instanced duplicates.\n\nI'm not sure if this is desirable behavior, because for many use cases\nthe final poly-count is significant:\n\n- Rendering\n- Polygon budgets for 3rd party engines.\n- General performance, since instances add overhead.\n\nThe down-side is that there _are_ cases where you might not need to\nbe aware of the extra geometry created by instancing - for file-size,\nor in cases the instances end up not being duplicated in memory.\n\n----\n\nPosting this since there is a patch to show geometry for selection\nthat doesn't make much sense with the current behavior - see: [D5762: Show the number of verts & faces for selected objects in object mode](D5762)\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", "Add resync tagging to BKE_main_collection_sync_remap\nAdd a different tag to collection cache resyncing.\nThis should be a different tag then the view layer caches.\n\nBKE_main_collection_sync_remap frees existing hashes. It also reconstructs the hashes to ensure that the remapping that was done didn't create duplicates. This can happen in the situation where you replace an object with a different object that already exists in the same view layer.\nDoing de-duplication in this can be triggered many times and result to a process what isn't expected.\n\n1. Deduplication should not be the responsibility of a function that only clears and tags.\n2. Creation function should only create, not remove inconsistency\n\nA possible (still dirty) solution would be to not recreate during remap, but do the deduplication during first usage.\nTemporarly the de-duplication spends most time in resizing the hash_map. By giving a size hint resizing could be eliminated fo rmost cases.\n\nBest solution would be to move the responsibility to the actual functionality that could make these incorrect states. \n\n## Experiment\n\nWith this experiment we postpone the de-duplication check; all access to the object_bases_hash is guarded with a NULL check and is already recreated when needed. So not necessary to recreate during remap. De-duplication is performed during view layer syncing. It is unclear to me in what situation postponing the de-duplication would lead to different results/wouldn't work.\n\nNot added as a patch as this doesn't solve the responsibility issue, it just moves it to another time.\nPS this of course improves performance and many code paths can be cleaned up.\n\n```\ndiff --git a/source/blender/blenkernel/intern/layer.c b/source/blender/blenkernel/intern/layer.c\nindex 5b54f16661c..1a9457cae79 100644\n--- a/source/blender/blenkernel/intern/layer.c\n+++ b/source/blender/blenkernel/intern/layer.c\n@@ -384,7 +384,7 @@ Base *BKE_view_layer_base_find(ViewLayer *view_layer, Object *ob)\n BLI_assert_msg((view_layer->flag & VIEW_LAYER_OUT_OF_SYNC) == 0,\n \"View layer out of sync, invoke BKE_view_layer_synced_ensure.\");\n if (!view_layer->object_bases_hash) {\n- view_layer_bases_hash_create(view_layer, false);\n+ view_layer_bases_hash_create(view_layer, true);\n }\n \n return BLI_ghash_lookup(view_layer->object_bases_hash, ob);\n@@ -1308,7 +1308,7 @@ void BKE_layer_collection_sync(const Scene *scene, ViewLayer *view_layer)\n \n /* Create object to base hash if it does not exist yet. */\n if (!view_layer->object_bases_hash) {\n- view_layer_bases_hash_create(view_layer, false);\n+ view_layer_bases_hash_create(view_layer, true);\n }\n \n /* Clear visible and selectable flags to be reset. */\n@@ -1426,7 +1426,7 @@ void BKE_main_collection_sync_remap(const Main *bmain)\n /* Directly re-create the mapping here, so that we can also deal with duplicates in\n * `view_layer->object_bases` list of bases properly. This is the only place where such\n * duplicates should be fixed, and not considered as a critical error. */\n- view_layer_bases_hash_create(view_layer, true);\n+ //view_layer_bases_hash_create(view_layer, true);\n }\n \n BKE_collection_object_cache_free(scene->master_collection);\n```", "Library Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nLibrary Overrides: Making an override (for a linked object in the scene collection) creates a duplicate object\n\n- open `main.blend`\n- (there is a linked object in the scene collection)\n- `Object` > `Library Override` > `Make`\n- A separate (overridden) Cube object is created in the scene collection (along with the linked object still there)\n\nNOTE: doing the same from the Outliner (RMB > `Library Override` > `Make` > `Selected`) seems to work as expected\n\nas a comparison:\n- open `main_with collection.blend`\n- (there is a linked object in a collection [not the scene collection])\n- `Object` > `Library Override` > `Make`\n- The overriden Cube object is just there without the linked object Cube being present\n\n", "Quick favorites: Add previously removed behavior causes duplication\nOperating system: windows 10\nGraphics card: RTX 3090\n\nBroken: Current main.\nWorked: N/A.\n\nIf you remove one item from Quick favorites, the next time you will be able to add it again.\nThis cause duplication:\n\n\n1. Add some items to Quick Favorites.\n2. Remove some items.\n3. Sometimes you will able to add previously existing items back to the list again. (see attached video examples)", "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", "Scene pre/post handlers are called for each main loop iteration\nTitle says it pretty much everything. just execute this in py console:\n\n```\ndef cb(sce): print(\"foo\")\n\nbpy.app.handlers.scene_update_post.append(cb)\n```\n\n…and you'll get endless 'foo' lines in your console, even when Blender is hidden and all.\n\nIssue is, main loop calls (through `wm_event_do_notifiers()`) `BKE_scene_update_tagged()`, which unconditionally fires those pre/post scene update handlers.\n\nNot quite sure what's to be done here really, not familiar at all with this area of the code.", "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", "Freeze on typing in name field of Named Attribute node\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 472.12\n\nBroken: version: 3.4.0 Alpha\n\nBlender freezes when I typing in name field of named attribute node\n\n- Open .blend file\n- select named attribute node and type {key C} twice\n\n[Bug_GM_big_attribute.blend](Bug_GM_big_attribute.blend)" ]

[ "Keymap Export with \"All Keymaps\" -> Import resulting in duplicated keys for some addons\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.0.0 Alpha\n(problem exists in Blender 2.93.1 as well)\n\nExporting Keymaps with \"All Keymaps\" option enabled causes some addons to get duplicated hotkeys. This doesn't happen with the \"All Keymaps\" options turned off.\nI've seen hotkeys for both [Machin3Tools ]] and [[ https:*armoredcolony.gumroad.com/l/xvVPd | Curve Basher ]] experience this duplication error but not all addons ([[ kekit_blender | kekit ](https:*machin3.gumroad.com/l/MACHIN3tools) for example is unaffected)\n\n\nWith a clean Blender install:\n\n # Download [Machin3Tools ](MACHIN3tools) (free)\n\n # Enable \"Filebrowser Tools\" \n\n # Export Keymap (with \"All Keymaps\" enabled)\n\n # Import the exported Keymap\n\n - Hotkeys are now duplicated " ]

[ "EEVEE: Mixing between a fully transparent and holdout shader yields a half transparent result\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.2.0 Release Candidate\nWorked: I thinck the issue is for \"all\" versions of blender\n\nHoldout shader having issue with alpha (semi transparency).\n\nPut a image plane with exr image that contain alpha. When using a holdout shader mixed with another shader (transparency shader for exemple) the alpha of the image sequence is used for the mix of the 2 shaders. It should have a complete transparent image with the holdout of other object in the scene. The issue is that there is a dark outline for the semi transparent. Holdout have issue dealing with semi tranparency ? or maybe something else.\nSee the attached image to understand the issue.\n\n\n", "Selected object color is weird in wireframe mode if the object color isn't single.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0 Alpha\n\nOutline overlay seems to be drawn under wireframe.\n\n[#91619.blend](T91619.blend)\n\nImmediately visible in provided file.", "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", "Mantaflow emitter sometimes creates smoke of wrong color (blue and green channels swapped)\nOperating system: Arch Linux, kernel 6.0.2, but this also reproduced on Win 10\nGraphics card: [AMD/ATI] Hawaii PRO [Radeon R9 290/390] (according to lspci)\n\nBroken: 3.2.0, 3.3.1, 3.4.0\nWorked: not tested yet\n\nThis bug involves mantaflow smoke simulations with an animated emitter color.\nUnder some conditions, the emitted smoke has the wrong color. This manifests in the \"solid\" viewport shading as well as in the shader when the color is read from the Volume Info node.\n\nSpecifically, in the attached blend, when baking the fluid simulation with a domain resolution of 128, the colors are wrong. When baking with a resolution of only 64, the colors appear correct.\nWhen the colors are wrong, it seems that the blue and green channels are swapped.\n\nHere is a screenshot: The emitter color changes every 50 frames, in the order red, green, blue.\nAt the current frame, the correct emitter color would be blue, as shown in the Properties Panel, while the actual emitted smoke color is green.\nNote how the emitter plane itself is covered in smoke of the correct color.\n\n\n\nAlthough this can be worked around in the shader, it seems especially problematic that the bug depends on the domain resolutions (and possibly other factors).\n\n\n - Open the attached blend file and bake the fluid simulation without changing the resolution.\n - Observe how the smoke colors are wrong: blue and green channels are swapped\n - Free bake, change domain resolution to 64 and bake again.\n - Observe how the colors are correct now.\n\n[mantaflow_rgb_bug.blend](mantaflow_rgb_bug.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)", "\"Reset to Default Value\" sets alpha incorrectly in [Material Properties > Viewport Display > Color]\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.5.0\n\nRight-clicking \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] sets both the color's \"value\" and \"alpha\" bars to 0.8, when the alpha one specifically should reset to 1. Alpha resets incorrectly.\n\nRight-click \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] on any material.\n\n", "EEVEE motion blur in cryptomatte\nI have tested this in 2.93.3 and even blender-3.0.0-beta+v30.bd734cc4419a to check if it got added there. \nThe issue is simple to explain: cryptomattes in eevee don't include motionblur. In Cycles they do include the motion blur. Is this a known thing, will it be addressed in the next updates?\nI suppose it could also be an undiscovered bug as the blender manual describes it as following \"[...] mattes will be anti-aliased and take into account effects like motion blur and transparency.\" cryptomatte.html - well in eevee it doesn't take motion blur into account", "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", "EEVEE Material Preview works significantly slower than before. \nOperating system: MacOS Mojave 10.14.6 (18G9323)\nGraphics card: Intel Iris Graphics 550 1536 MB\nMemory: 16 GB 2133 MHz LPDDR3\nProcessor: 3,3 GHz Intel Core i7\n\nBroken: (example: 3.0.1, 2.93.8 edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: 2.83.19 \n\nSwitching to \"Material Preview\" view mode (or Rendered) and any manipulation of a material (like adding new node) takes significantly longer than in previous version. \n\n1. Open attached file\n2. Click \"Material Preview\" view mode\n3. Wait until material is fully visible in the viewport\n\nI know my machine is not a great performance beast and my OS is pretty outdated (but I can't upgrade because of other apps that I use), but you can clearly tell that 3.0.1 works much slower. I tried also 2.93.8 version (LTS tab on blender.org) and the result is the same. Only 2.83.19 worked faster. I attached a video, it's realtime screen recording (the only editing within the video is blurring the mess on my desktop). Also you can find a blend file that was use to perform the test. [performance-test.blend](performance-test.blend)\n\n[blender_performance.mp4](blender_performance.mp4)", "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", "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)", "Reversing frames on video sequencer don't play them backwards\nOperating system: Windows 10\nGraphics card: Nividia GEFORCE 940MX\n\nBroken: ( 2.82a, 2020-3-12, as found on the splash screen)\n\n\nReversing frames do not play the frames backward as expected to when the strip is split.\n```\n\n```\n\nvideo sequencer -> Add an image strip -> cut the stip into 2 or three parts -> select the middle stip ->check the reverse frame checkbox.[Reverse.blend](Reverse.blend)\n", "EEVEE: Alpha Blend + Show Backface material is out of focus.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIn EEVEE when the DOF is on, and the focus is on the glass object, it is blurred.\nOnly when you set the focus on an object that can be seen through the glass, it becomes sharp.\n\nI set up a simple animation in the blender file, where the camera's DOF is fixed on the glass ball, and the background moves forward and backward.\nFocus is only caught when the background overlaps with the ball.\n\n- Open Attached File\n- disable and enable`Show Backface`\n[focus bug.blend](focus_bug.blend)\n\n", "VSE: Alpha Over + Convert to float changes the color of the top layer\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8853\n\nBroken: version: 2.92.0 Alpha\n\nAdd two color strips - not black, and change compositing of the top strip to Alpha Over. Toggle 'Convert to float' under color while pressing arrow left/right to update the preview. The top layver will now change color, it's a regression and a bug. \n\n", "Eevee Volume Artifacting\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.3.1\n\nI'm rendering some nebulae in Eevee and despite having 256 render samples, 256 volumetric samples and 128 volumetric shadow samples with 0.9 distribution and 2px tile size with proper start and end clipping distance both in camera and volume settings I'm getting really ugly flickering where the whole volume just artifacts which is really irritating. I'd love it if you could fix this issue in the upcoming blender release because even though I have a good computer it still takes 30 minutes to render the exact same scene in Cycles (where the issue is absent). watch?v=8ImqpM4zOEU\n\n[#101826.blend](T101826.blend)\n\n- Open file \n- Render animation\n\nIssue is visible after rendering ~10 frames when animation is inspected.\n\n" ]

[ "Video Sequencer UI Rendering Error\nOperating system: macOS-12.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon `R9 M370X` OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.101\n\nBroken: version: 3.1.0 Alpha\nWorked: 3.0.0 Release\n\nThe video sequencer UI appears to be extremely broken. Sometimes it's all neon green, sometimes it's retains the 3d viewport's image, sometimes both!\n  \n\nLaunch Blender\nThen either open a new video sequencer editor or go to a video editor tab\n", "Sequencer Window background is shows green\nOperating system: macOS-11.6.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.21\n\nBroken: version: 3.1.0 Alpha\nWorked: Blender 3.0.1 Release candidate\n\n- Start a new Blender\n- Add a Video Editor Layout or Tempate\n\nThe sequencer window is green. Seems like a graphics bug?\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", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)", "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", "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", "Crash when modifing materials after using BMesh in Depsgraph-Pre event\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\n\nBroken: version: 3.0.0\nBroken: version: 3.0.1 Release Candidate\nBroken: version: 3.1.0 Alpha\n\nI wrote a script with a function that copies a mesh via BMesh to another object and then changes it's materials. When I want to export the scene as an alembic, Blender crashes when the function gets called via the Depsgraph_Pre event. Depsgraph_Post and Frame_changed_Pre & Post all work fine.\n\n\n- Open the attached Depsgraph_Pre_Crash.blend file in Blender\n- Run the script\n- (Optional) Scroll on the timeline between frames 1 & 2 to check that the script works\n- Set the active frame on the timeline to 1\n- Export as alembic with default settings\n- Blender crashes\n[Depsgraph_Pre_Crash.blend](Depsgraph_Pre_Crash.blend)\n\n[Depsgraph_Pre_Crash.crash.txt](Depsgraph_Pre_Crash.crash.txt)\n\nHere is the callback registered in `depsgraph_update_pre`:\n```lines=10,lang=python\ndef updateFrame(scene): \n```\n emptyObject = bpy.data.objects[\"EmptyObj\"]\n firstOBJ = bpy.data.objects[\"Frame1\"]\n secondOBJ = bpy.data.objects[\"Frame2\"]\n```\n\n```\n if(scene.frame_current == 1):\n bmNew = bmesh.new()\n bmNew.from_mesh(firstOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n```\n\n #Doing anything with the materials crashes blender on alembic export\n```\n emptyObject.data.materials.clear()\n```\n\n```\n if(scene.frame_current == 2):\n bmNew = bmesh.new()\n bmNew.from_mesh(secondOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n \n emptyObject.data.materials.clear()\n```\n", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n", "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", "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)", "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", "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "Subdiv of certain model causes huge memory consumption and crash (regression bug)\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\n2 guys from 3d-chat also checked it too and caught the same memory leak and crash.\n\nBroken: version: 2.82 (sub 1)\nand 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e\n\nWorked: 2.79 (sub 0), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b\n\nBlender 2.80+ consume a lot of memory and crashes (before memory filled), when I try to subdivide this certain model. \n[2019-11-18_17-17-06.mp4](2019-11-18_17-17-06.mp4)\n\nOpen file with 2.80+, press Ctrl+1 to subdivide.\n[killsubdivdragon.7z](killsubdivdragon.7z)\n", "Crashes when trying to mirror particles\nOperating system: Windows 11\nGraphics card: Nvidia RTX 2060\n\nBroken: 3.6.1\n\nWhen I try to mirror hair particles Blender crashes. I've tried it multiple times and it happens every single time. Ive tried applying the mirror modifier I have on the character but it still crashes.\n\nI have a retopologized character. I make a particle system for eyebrows. I try to mirror the eyebrows by selecting all the particles, going to particles and selecting mirror and blender crashes.\n\n", "Blender 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)" ]

[ "Subsurface modifier is broken\nWin 7x64, GTX 580\n\nBroken: 2.75 f6e0262\nWorked: 2.75 c86a519\n\nAdding subsurface modifier distorts object or crashing blender.\n\n1. Add any mesh\n2. Add Subsurface modifier\n3. Mesh disappears/distorts or crashes blender" ]

[ "Frequent crashes when performing minor adjustments with rigid body constraints\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel Inc. 4.1 INTEL-16.5.2\n\nBroken: version: 3.0.0 Alpha\n\nWith a simple rigid body setup (see attached file), there are frequent crashes when doing simple adjustments such as moving the constraint around, rotating it, starting/stopping the animation, undoing some steps. There is not a single scenario leading to a crash, but performing a combination of these actions in succesion consistently leads to a crash (segmentation fault) within about 30-60s.\n\n[Rigid body crash.blend](Rigid_body_crash.blend)\n[Rigid body crash.txt](Rigid_body_crash.txt)\n\nI closed #91025 because I thought it was fixed, but it turns out the crashes still occur. I have found one reproducible way to get the crash:\n- With factory preferences, open attached blend file.\n- Press spacebar to start the animation\n- Press command-Z to undo and then shift + left arrow to restart at the first frame\n- Repeat the last step (command + z and then shift + left arrow) a few times\n- Blender will crash usually after repeating 2-3 times, sometimes a few more.\n", "Regression: Crash when Sculpting on a mesh from a GP Lineart Modifier\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (W11)\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.2, 4.0.0 Alpha\nWorked: 3.1\n\n\nWhen trying to sculpt a mesh in an assigned collection that a grease pencil lineart modifier references and the layer it is drawing to contains Grease Pencil strokes - it will instantly crash Blender. \n\n\n1. Download and extract zip to get the test blend file\n2. Load attached file with Load UI off\n3. Select the bust, it is in a GP lineart modifier collection \n4. Go to sculpt mode\n5. Try sculpt\n6. Crash\n\nAlternative steps:\n1. Create new scene\n2. Create a sphere\n3. Create a Grease Pencil object\n4. Add sphere to a new collection\n5. Select the GP object and add a lineart modifier\n6. Reference the sphere collection in the modifier\n7. Assign layer and material to the modifier\n8. Draw in the same layer in Draw mode of the GP\n9. switch to sculpt mode\n10. Try sculpt over sphere surface\n11. Instant crash\n\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Blender 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.", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\n\n", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "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)", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "System UI Freeze and blender UI blinks\nOperating system: Linux-6.4.12-zen1-1-zen-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) HD Graphics 630 (KBL GT2) Intel 4.6 (Core Profile) Mesa 23.1.6-arch1.4\n\nBroken: version: 3.6.2\n\nblender often freezes (with the entire UI of the System), sometimes blender comes back to control, but, there are times when doesn't, the blender UI blinks to come entirely black and unresponsive.\n\nThis happens when I was using a graphic tablet to sculpt something.\nJust opened blender and started to sculpt, eventually the situation occur.\n\n", "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", "Error baking particles in OSX\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.135\n\nBroken: version: 2.83.1\n\nI have two particle emisor and when I try to bake it crash.\nI try it in Linux and work perfectly!\n[TEST_ERROR.crash.txt](TEST_ERROR.crash.txt)\n\n[TEST_ERROR1.blend](TEST_ERROR1.blend)\n\n- Open file\n- Bake particles\n\n" ]

[ "Crash switching to Modeling then Sculpting Workspace\nWindows 10 Nvidia 1060\n\n2.80 current commit.\n\nBlender crashes when switching to Modeling then Sculpting Workspace.\n\n\nOpen Blender, dismiss splash, click /Modeling\\ workspace tab, click /Sculpting\\ tab, crash:\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6DA6C2B5D\nModule : G:\\bdev\\build_windows_Release_x64_vc15_Release\\bin\\release\\blender.exe", "change OM in EM and after OM in workspace causes the crash\nwin 7 pro ,\n 2047 MBNVIDIA GeForce GTX 980 Ti (MSI)\t\n3071 MBNVIDIA GeForce GTX 780 (ZOTAC International)\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\n2.80.34 \n\n\nchanging the mode OM \\ EM \\ OM in sculpting workspace creates error\n\nopen blender\nselect the default cube\nchange in workspace sculpting\nchange in edit mode using TAb key\nchange in object mode using TAb key\nchange in edit mode using TAb key -> crash\n\nif I use the pie menu with ctrl + tab the error does not happen\n\n" ]

[ "TexBlendNode Python property tooltip incorrect\nBlender 2.8 \n\nI can not change the Progression or the Flip Axis for the Tex Blend Node with python. \n\nIt returns with an error that says \" no attribute use_flip_axis\". I thought this was my fault so I reached out for help on the Stack Exchange> [here ](how-do-i-change-the-blend-node-to-vertical?)\n\nThey think this is a bug or missing API?.. I checked online but could not see this bug reported so I thought I would let you guys know.\n\nI have used a rotate node to work around the problem but I am sure you guys would be able to fix this issue with ease.\n\n[#69973.blend](T69973.blend)", "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", "Automatic Weights not working if part of mesh has negative scale\nOperating system: Windows 10 Pro\nGraphics card: NVIDIA GTX 960\n\nBroken: 3.1.0\nWorked: Never (2.8+)\n\n\nWhen part of a character mesh is given a negative scale in Edit mode, parenting to an armature with Automatic Weights no longer seems to work correctly. Applying scales does not help either as the scaling is done in Edit mode.\n\nI realise there are other ways to mirror part of a mesh rather than negative scale, however myself and one of my students have now both lost hours to this issue before I finally found out what seemed to be causing it.\n\n**How to recreate the bug**\n1. Open the file \"Block Man Example.blend\".\n2. Select the Cube mesh.\n3. Go into Edit mode.\n4. Select an entire arm or leg (I used Select Linked).\n5. Set the scale to -1 on the x-axis. (S, X,-1).\n6. Return to Object mode.\n7. Select the Cube mesh, then holding shift, select the Armature as well.\n8. Press Ctrl+P to parent, choosing With Automatic Weights.\n9. Select the Armature and go into pose mode.\n10. Try rotating the bones around the arm or leg which had been scaled.\n11. You see the mesh does not follow the bone as you would expect.\n\nFile: [Block Man Example.blend](Block_Man_Example.blend)", "Add error message feedback on constraints, similar to what already exists for modifiers.\nCurrently de-activated constraints only show their status through a small red icon. It would be better for users to also show an error message explaining what is the issue, similar to what modifiers already do.\n\nSee e.g. the invalid settings for the IK constraint of the first bone in this file from #100128: [lib.blend](lib.blend)", "Very slow interaction with Armature, if GPU Subdiv is enabled\nOperating system: Ubuntu 20.04\nGraphics card: Gefore MX230\n\nBroken: 3.3, 3.2.2\n\nwith the enabled GPU Subdivision, interactions with the armature are much slower than with the disabled\n\n[2022-10-23 13-29-00.mp4](2022-10-23_13-29-00.mp4)\n\nmove the bones with GPU Subdivision on and off\n[kira_lite.blend](kira_lite.blend)", "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", "Pinning Bones/Constraint Tabs in Properties Editor doesn't work\nBroken: 2.76 - master (1283c66)\nWorked: Unknown\n\nThe context pinning functionality in the Properties Editor doesn't work for Bones and Constraints. There may be a few others too that I haven't noticed yet, but these are the biggest ones.\n", "Cycles: negative BSDF mixtures weights\nOperating system: Ubuntu 21.10\nGraphics card: Nvidia 2060\n\nmaster branch\n\nWhen adding some sanity checks into the Cycles code I realized that the BSDF mixture weights can become negative.\nI am not sure if this is the desired behavior since it is not physically correct and has the potential to cause problems when there is the assumption\nthat BSDF evals always return positive values.\n\n\nNegative BSDF mixture weights occur in the Barbershop scene and can be matched by adding an assert \nto the `svm_node_closure_weight` function in `intern/cycles/kernel/svm/closures.h`:\n\n```\nccl_device void svm_node_closure_weight(ccl_private ShaderData *sd,\n ccl_private float *stack,\n uint weight_offset)\n{\n float3 weight = stack_load_float3(stack, weight_offset);\n assert(weight.x >= 0.f && weight.y >= 0.f && weight.z >= 0.f);\n svm_node_closure_store_weight(sd, weight);\n}'\n```", "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)", "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}", "Cannot Apply Multi Objects\nOperating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10\n\nBroken: version: 2.92.0\n\nWhen I try to apply scaling, rotation or location to a linked object (Alt+D) I get this error message:\n\"Cannot apply to a multi user: Object \"Cube.001\", Mesh \"Cube\", aborting\"\n \n- Scale the cube \n- Link it with Alt+D,\n- Apply scaling, location or rotation to one of the two cubes.\n\n[Blender 2021-05-30 00-10-18.mp4](Blender_2021-05-30_00-10-18.mp4)", "World Cavity Not Scale-Agnostic\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92, 2.7, 2.8\nWorked: Never, I think.\n\n\nBlender's viewport AO behaves differently depending on scene scale, to the effect of significantly limiting its usability at larger or smaller scales than 1BU.\n\nA scene that has been scaled up does not have the same AO patterns as the original scale, even if you also increase the \"Distance\" and/or \"Valley\" factors proportionally.\n\nThe noise behaviour is also significantly degraded at larger scales.\n\nDefault scene scale and world cavity settings:\n\n\n\nScene scaled up 100X, cavity still defaults:\n\n\n\nScene scaled up 100X, cavity distance also increased 100X:\n\n\n\nScene scaled up 100X, cavity distance and strength also increased 100X. Notice the noise:\n\n\n\nThis might seem like a feature request for a new AO algorithm, but I think it crosses over into being a bug report because the current behaviour means that the usefulness of world cavity rendering is significantly degraded for any feature sizes that are much larger or much smaller than 1BU. I.E. It's not that a totally new algorithm is necessarily required; the issue is that the current system is effectively broken outside a very narrow range of settings. Outside that range of settings, its best performance is either too weak or too noisy to be useful.\n\n\nSet up two geometrically similar scenes at different scales, then try to find world cavity settings that produce equivalent results for them. Set \"Lighting\" to \"Flat\" to make it easier to see.\n\nOr: Set up a scene where the average feature size is much larger than 1BU, and then try to find useful world cavity settings for it.\n\nOr: Open the below file that has two differently sized Suzannes in two viewports, and play around with world cavity settings.\n\n[WorldCavityFailure.blend](WorldCavityFailure.blend)", "Weighted normals modifier produces different results on objects of different scales\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.0\n\n\nWeighted normals modifier is not consistant on small objects \n\nOpen Blender\nCreate a cube 1mmx1mmx1mm, scale applied, \nadd bevel and weighted normals modifiers\nYou can notice the différence by doing the same process on a 1mx1mx1m cube\n\nI can do a work around by modifying the unit scale parameter but I think it should work on 1mm objects, like a lot of watch pieces. \n\n[weightednormals_defect.blend](weightednormals_defect.blend)\n", "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", "Bone's Transformation constraint numbers won't be symmetrized correctly.\nOperating system:Windows 10\nGraphics card:RTX 2070\n\nBroken: 3.3.1\n\n[Use this file](https://projects.blender.orgattachment)\n\nThis will break:\n\n- open the blend file\n- delete the selected Left bone\n- select Right bone and symmetrize it\n- check both Right and Left bones' Transformation constraint setting. Numbers on the Left one will be messed up.\n\nBut this works:\n\n- delete the selected Left bone\n- go to pose mode\n- select the Right bone\n- go to edit mode again and symmetrize it\n- Transformation numbers are both fine. \n\n------\n\nOriginal description:\n\nWhen Bones have Transformation constraint and are symmetrized in edit mode, its numbers are symmetrized correctly too.(Map from numbers like Location X min , Location X max and Map to numbers like Location min max etc) but if Transformation constraint's Target and Owner space are set as not Local those numbers are totally messed up and broken.\n\n" ]

[ "Negative values defy \"Limit Scale\" constraint limit, Parent Empty\nOperating system and graphics card\n\nBroken: 2.71 RC2 (a19c1be)\n\nWhen defining all limits in \"Limit Scale\" to 1, it is possible to scale to -1 and flip the mesh.\n\n1. With startup settings, add a cube. In edit mode, scale the top side to .5\n2. Add an empty beside the cube. Make sure it is outside the cube.\n3. Parent the cube to the empty.\n4. In the empty's constraints menu, add a \"Limit Scale\" constraint. Activate and set all of its minimum and maximum values to 1.\n5. Select the empty, and scale it down until you see a change, or just type \"-1\" to do it automatically.\n\nI haven't tested this with the other constraints. The blend file is here:\n[test.blend](test.blend)", "Copy Scale constraint ignores negative values\nWindows 7 64, HD 5770\n\nBroken:\nHash 19e627c (2.70 release)\nHash b5982f7\n\nAn object or bone using Copy Scale (Constraint) dont copy negative values of X Y Z.\nInstead, negative values are converted to positive values.\n\nExample:\nTarget X-1.0 = Constraint X+1.0 (wrong)\nTarget Y-1.0 = Constraint Y+1.0 (wrong)\nTarget Z+1.0 = Constraint Z+1.0\n\n[CopyScaleBug.blend](CopyScaleBug.blend)\n\n1. Add 2 monkey objects.\n2. Set Copy Scale constraint for one monkey, and choose the other one as target.\n3. Scale the target monkey negative.\n\nProblem: Constraint monkey dont follow into negative.\n\n-------\nSry if this report is a copy of the mentioned Todos in the Transform list.\nI was not sure, if this problem is included.", "Limit Scale ignores negative numbers\nGNU/Linux 64 bit (fedora 20) Intel CPU, Nvidia GPU\n\nBroken: bbab2ec 2014-01-10\nWorked: (optional)\n\nLimit Scale seems to use absolute values for limiting, allowing objects and bones to have negative scale values even if limit is >= 0\n\nCreate a Cube\nAdd a limit scale on e.g. X, lower value 0 upper value 1 (for example again)\nClick 'For Transform' in the constraint just to see it quickly\nScale the Cube down on X: note it skips past 0 to negative values, all the way to negative 1\n\nalternative just load the linked file and scale the cube.[limitscale.blend](limitscale.blend)\n", "Limit Scale does not Limit Scale on the Minimum Value\nOperating system and graphics card\nOS X 10.8.5\nGraphics AMD Radeon HD 6490M 256 MB\n\n\nBroken: Blender 2.69\n\nThe Limit Scale constraint fails with a minimum value of 0.0. The user is able to bypass the minimum and scale all the way \"down\" to the negative maximum value. It is easiest to bypass the minimum value at 0.0. It is also possible at values close to zero such as 0.2 or 0.4, but the user must move the mouse rather quickly to jump over the minimum value into the negative side.\n\nThis is reproducible with the default blend or with the attached.\n[limit_scale_bug.blend](limit_scale_bug.blend)\n" ]

[ "Subdivide smooth is not symmetric\nWindows 8\nGeforce GTX 665 M\n\nBroken: Blender 2.96.0 r60995\n\n\nOn a 3 vertex line with the center vertex with greater y like that :\n\n\nIf I use subdividee smooth the result is not symmetric, I haven't set any random property.\n \n\n1./ Use subdivide smooth on the attached blend file, I have put the result that I get and the original\n[subdivide_smooth_bug.blend](subdivide_smooth_bug.blend)", "Copypasting material is broken for `NodeCustomGroup` nodes\nOperating system: Linux-5.0.0-37-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nWhen copying+pasting material:\n\n - method `copy` is called twice, which produce undesireble results. \n```\n when copying for 'copy' operation it is called on unlinked nodetree inside buffer\n```\n - user counter of trees of containing nodes are messed up: source node get decremented counter\n\nAsan use after free [T72579_asan_use_after_free.txt](T72579_asan_use_after_free.txt)\n\n - load attached file and execute embedded script\n - it registers 2 custom nodes and adds them to first material\n```\n node trees created: 'foo' (1 user), 'bar' (1 user) \n```\n - select first slot in material list and call 'copy' from specials menu\n - select second slot and call `paste`\n\nThis expected to produce: \n - 'foo' (2 users, both materials)\n - 'bar' (1 user, material1) detached from pasted node in `copy` api call\n - 'bar.dup' (1 user, material2), created from inside `copy` api call\n\nInstead: \n - 'foo' (1 user, used in both materials), copypasting did not increment users (or incremented and then decremented)\n - 'bar' (0 users, used in material1), copypasting decremented source users\n - 'bar.dup' (0 users), created in first api `copy` call\n - 'bar.dup.001' (1 user, used in material2), created in second api `copy` call\n\n[test_mat_copypaste.blend](test_mat_copypaste.blend)\n\nThis case is covered by autotests submitted: D6420\nThe issue with api calls is fixed by D6450 \nBut the counter issue remains.", "Segfault pasting stale driver.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\nDrives copied and pasted with significant change in file data in between can trigger segfaults. \n\n```\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nblender(BLI_system_backtrace+0x34) [0x55dfd70fd084]\nblender(+0xe151bd) [0x55dfd4bd41bd]\n/usr/lib/libc.so.6(+0x3cf80) [0x7f9b26870f80]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder26build_object_data_geometryEP6Objectb+0x170) [0x55dfd7000380]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder17build_object_dataEP6Objectb+0x54) [0x55dfd6ffb4b4]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x1d3) [0x55dfd6ffe2c3]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder22build_driver_variablesEP2IDP6FCurve+0x77) [0x55dfd6ffad87]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder14build_animdataEP2ID+0x1f9) [0x55dfd6ffe8b9]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x228) [0x55dfd6ffe318]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder16build_view_layerEP5SceneP9ViewLayerNS0_26eDepsNode_LinkedState_TypeE+0xb2) [0x55dfd7003892]\nblender(_ZN7blender3deg23AbstractBuilderPipeline16build_step_nodesEv+0x76) [0x55dfd6fea296]\nblender(_ZN7blender3deg23AbstractBuilderPipeline5buildEv+0x42) [0x55dfd6fea4b2]\nblender(DEG_graph_build_from_view_layer+0x33) [0x55dfd6fd24e3]\nblender(+0xef501a) [0x55dfd4cb401a]\nblender(wm_event_do_depsgraph+0xc5) [0x55dfd4f59245]\nblender(wm_event_do_refresh_wm_and_depsgraph+0x92) [0x55dfd4f593b2]\nblender(wm_event_do_notifiers+0x36a) [0x55dfd4f6055a]\nblender(WM_main+0x2b) [0x55dfd4f5532b]\nblender(main+0x367) [0x55dfd4b9da67]\n/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f9b2685bb25]\nblender(_start+0x2e) [0x55dfd4bd056e]\n\n# Python backtrace\n```\n\n\n* Add a custom property to the Scene.\n\n* Right click on its value field, and run \"Copy as New Driver\".\n\n* Run `CTRL`+`N` or \"File\" —> \"New\" —> \"General\".\n\n* Right click on any value field, and run \"Paste Driver\".", "Perstistant data causes point cloud objects to move\nOperating system: WIndows 10\nGraphics card: RTX 3070Ti\n\nBroken: Latest 3.4 Alpha of time of writing\nWorked: Tested back to 3.0 where the domain size node doesn't exist.\nCorrect location, no persistent data: \nRandom location, using persistent data \nA combination of animating the point cloud count and Persistent data causes the point cloud to move from its set location. \nBased on the default startup or an attached .blend file (as simple as possible).\nRender with and without persistant data.\n[Bug_test.blend](Bug_test.blend)", "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.", "Bone Transformation - Make Individual Origins work with groups of linked bones\n**Short description**\nWhen the pivot point is set to Individual Origins, and multiple edit bones are selected, when rotating they are expected that each group of linked bones has its own rotation pivot.\nBut instead these bones pivot from the head of their parent, which seems unintentional, considering this works as I would expect in pose mode.\n\n[UncommonGlaringGilamonster.webm](UncommonGlaringGilamonster.webm)\n\nIn the video, is expected Individual Origins to behave the same way as Active Element, since in the case of a single selected(therefore the active) element, those two do the same thing in other cases in Blender.", "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", "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", "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", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "Principled BSDF Anisotropy black faces\nWin10, 1080Ti\n\nBroken: 2.79\n\nIt seems that using anisotropy produces black odd artifacts under certain mesh circumstances. I don't think this happens often as it seems the actual mesh caused it, possibly by being a little bit too symmetrical? \n\nI suppose often it goes unnoticed so I thought it might be good for someone to investigate upon if there isn't some inconsistency.\n\nRotating the object by the tiniest bit helps (probably helps by something being non 0 ^__^).\n\nMoving random vertices randomly produces different results that are often completely correct or at least 50% correct. Good to try that in Rendered mode.\n\nScreenshot: \n\nBlend: [Anisotropy_Bug.blend](Anisotropy_Bug.blend)", "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", "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)", "\"Paste Objects\" doesn't copy source objects' collection heirarchy\nStarting to switch over to Blender 2.8 / 2.9, copy pasting still isnt working as intended. Please see #58190 as a reference of the previous bug.\n\nSystem Information\nOperating system: Ubuntu 17.10\nGraphics card: GTX 1080\n\nBlender Version\nBroken: blender2.9 55a2682348\nWorked: master Oct 2018 786870e26f\n\nShort description of error\nCopy pasting between blend files, it does not honor the collection hierarchy, Previously with blender 2.7 we could disable 'Active Layer' and the objects would go to their correct respective layers from the original blend file. Now with Blender 2.8 the only option is to have the copy paste on to the active collection, ruining any sort of collection hierarchy that was previously setup.\n\nExact steps for others to reproduce the error\n\n - Open Blender 2.8\n - create a new collection called 'test'\n - move the cube into this the collection 'test'\n - copy collection 'test'\n - create new blend file\n - delete everything apart from the default collection 'Collection'\n - create new collection 'test'\n - make the active collection the default collection 'Collection'\n - Paste\n - in the 'Paste Selection from Buffer' dialogue box, disable active collection\n - notice how the cube just created a new collection altogether, rather than creating the correct collection name / merging into it.", "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" ]

[ "Recording of Group instances is incorrect\n**Category**: Animation\n\n\n%%%Recording of Group instances is incorrect\n****\nScene:\n - one cube part of GroupCube Group\n - one floor\n - 6 empties being instances of the GroupCube\n```\n \n```\nHow to check:\n 1.Press P to see the instanced objects\n```\n collide\n```\n 2.press ESC to stop the animation\n```\n \n```\n 3.Check Game --> Record Animation\n 4.Press P again to record the animation\n 5.Press ESC to stop the recording\n 6.navigate the Timeline to see the recording as being incorrect\n\nResult: when trying to record the animation\nthe instanced objects are displaced; when not\nrecording they behave normally\n\nRegards,\nAlbert%%%" ]

[ "Dissolve can create duplicate faces\nOperating system:\nGraphics card:\n\nBroken: 2.81 R970d7ed all the way back to 2.70a\nWorked: likely never\n\nUsing the dissolve tool it's possible to create faces sharing the same boundary edges.\n\n\n**Exact steps for others to reproduce the error (using *Dissolve Vertices*):**\n\n1. In the default scene, edit the cube.\n2. In **vertex** selection mode, select one face (4 vertices).\n3. Still in vertex mode, dissolve using {key Ctrl X}.\n\nYou should be left with a \"plane\" that has 4 vertices, 4 edges, and **2** faces. None of the options for the Dissolve Selection (the ctrl+x) tool seem to help against it. I don't think that any of the built-in clean up helpers can detect these either, at least directly. Select Non-Manifold can be of some small help, if there's some adjacent geometry, but if there isn't (as in this example), it won't select anything.\n\n**Exact steps for others to reproduce the error (using *Limited Dissolve*):**\n\n1. Create a plane and go into Edit Mode\n2. Select a triangular part by selecting 3 vertices and pressing `F`\n3. Select the opposite triangle part by selecting another 3 vertices on the opposite side\n4. Press `A` and `X` *> Limited Dissolve*\n5. Notice that you have 2 faces now.\n6. Repeat this procedure and you can have as many faces as you like all sharing exactly the same 4 vertices\n \n\n\n\n\nThen try to dissolve one vertex with `X` *> Dissolve Vertex*. One face gets deleted.\n", "Pinching effect when using bevel and bevel 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 bevel in editing mode or bevel modifier sometimes a pinching effect happens at the beveled corners.\n\nWhen using bevel in editing mode or bevel modifier sometimes a pinching effect happens at the beveled corners.\nThis is particularly visible when using many segments.\n\nTest file:\n[Bevel_test_file.blend](Bevel_test_file.blend)\n\nAt first I thought, that this was some kind of limitation of the bevel operation/modifier, however after observing the top part of the test file mesh i'm very sure that this is a bug, because the left part of the topmost face of the test file mesh has a correctly beveled corner, whileas on the other side there is a clearly visible pinching effect despite the local topology of both sides of the topmost face being indentical.\n\nThank you and have a nice day!", "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)", "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", "Bevel not correct adding bevel weight/crease in new edges\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.90.0 Beta\n\non mesh(Bevel_Weight_Bug) have 2 bevels:\n1- bevel with vertex group(for more nice view its be seam)\n2- bevel on weight edges\n\nsome of the new edges(after bevel 1) have information of bevel weight(green annotation), some not(red annotation)\n\n\non mesh(Cube) we have bevel 2 edges and subdivision\n\nnew edge after bevel don't have crease but all 3 connected edges at the base are with crease=1\n[Bevel_Bug_Report.blend](Bevel_Bug_Report.blend)\n\n\n\n", "Incorrect Fresnel layer weight shading on backfacing geometry\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\n\nFresnel layer weight creates a sharp boundary instead of a smooth falloff when viewed on backfacing geometry.\nIn this example there are 2 hemispheres with the same material, but the left one has inverted face normals.\n\n\n[fresnel bug.blend](fresnel_bug.blend)\n", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Edges generated by Bevel Modifier do not inherit correct crease values\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nThe Bevel Modifier ignores the crease values of connected edges, producing unexpected/undesired results.\n\nExample image of the bug in production asset (the rear of a flatbed car):\n\nPlease observe how the top is rounded toward the center of the car, despite the vertical corner crease and the horizontal beveling. This roundness goes against the artist's intention.\n\n\nOpen this file: [#70587-bevel-edges-bug.blend](T70587-bevel-edges-bug.blend)\n\nThat file was created by following these steps:\n\n1. Create a cube\n2. Set Edge Crease of vertical edges to 1.0\n3. Set Edge Bevel Weight of top horizontal edges to 1.0\n4. Add Bevel Modifier in Weight Mode\n5. Add Subdivision Modifier\n\nThis produces undesired result 1:\n\nPlease observe how the top of the cube becomes circular because the creasing on the vertical edges does not extend to the newly generated loop of faces.\n\nThis can be seen in image 2:\n\n\nOnly after manually adding the crease value to the new edges do we get the expected result, image 3:\n\n", "Hair with material using a non-existing attribute looks different between Eevee and Cycles\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.00.20.220516\n\nBroken: version: 3.4.0 Alpha\nWorked: -\n\nHair can be affected by materials that use attributes such as mesh.\nThe color of the mesh at the root position of the strand usually defines the color.\nBut that's not the case in Eevee if an attribute doesn't exist.\n\n\nThe actual color can be kind of undefined, but there should be a convention between the renders.\n\n- Open attached .blend file\n- Compare Cycles and Eevee\n[hair_material_with_non-existing_attribute__bug.blend](hair_material_with_non-existing_attribute__bug.blend)\n\n", "Random Per Island working incorrectly with sharp edges and volumes\nOperating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50\n\nBroken: version: 2.82 (sub 4)\nWorked: (optional)\n\nRandom Per Island not working correctly with sharp edges or volumes.\n\n\nSharp Edges:\n\n- Create Cube\n- Add Bevel Modifier with Harden Normals\n- Set Smooth Shading\n- Set Auto Smooth\n- Random Per Island is affected incorrectly by sharp edges, even after applying Bevel modifier\n\nVolumes:\n\n- Create cube (or array of objects)\n- Create volume shader\n- Assign Random Per Island to volume shader\n- No random colors\n\n[random_per_island.blend](random_per_island.blend)", "Intersecting Meshes are not marked as overlapping anymore when selected\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.90.1\nWorked: 2.83.x\n\nIn blender 2.83.x Solid View intersecting objects had, if selected, the otherwise hidden parts shown in a more muted color when overlapping. with 2.90.x this is no longer the case. \nI hope this did not get removed intentional but is a missing feature.\n\nDuplicate the default Cube, move it a bit so that is still intersects with the first cube and confirm movement. \nWatch the outline in Solid View be the same color and thickness all around the mesh. \nin 2.83 while moving the white outline turned light grey when intersecting and the selected object outline turned a darker orange. This is very helpful for positioning elements.\n\n", "Connect failed in certain case\nWin8 64bit | GTX680 \n\nBroken: 2.71.6 a0b3604\n\nWhen select two vertices and press J to connect, it fails to add vertices to edges in between.\n\nPlease see the attached case for example. Thanks for checking.\n\n\n\n[vertex_connect.blend](vertex_connect.blend)", "Bevel amount less than 1 mm and profile at 1 doesn't give expected result\nBroken: version: **2.91.0** Alpha, **2.79**\n\nWhen the bevel amount is smaller than 1mm., the bevel profile shape at 1 doesn't give the expected result.\nThe 'Depth' width type starts having the issue from 0.65 mm and below. All other width types suffer from 0.9 mm and below.\n\n\n[Bevel Profile Problem.blend](Bevel_Profile_Problem.blend)\nTry changing the bevel amount and the width type in the above file.", "Solidify Modifier wrong solidification normals in some cases\nOperating system: Windows 11\nGraphics card: ATX4000\n\nBroken: 3.5.0\n\nIn some corner cases, the Solidify modifier uses wrong solidification normals.\n\nWith the \"Faces linked only by one vertex.obj\" object, where some faces are sharing only one vertex and no edge, the solidification behaves as if ignoring that shared vertex.\n\nWith the \"Triangulated mesh wrong solidification.obj\" object the vertex in coordinates (-1, 1, -1) does not solidify properly, while the exact same mesh, but not triangulated (\"Triangulated mesh right solidification.obj\" object) solidifies right.\n\n", "Backface culling setting applies in Material Preview shading and affects selectability\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90 (sub 3)\nBroken: version: 2.83 (sub 17)\nWorked only if face orientation on in 2.82a release\n\nBackface culling setting applies in Material Preview shading and affects selectability.\nExpected: if it is visible and selectable, I should be able to select it.\n[2020-05-26_00-02-02.mp4](2020-05-26_00-02-02.mp4)\n\n**Steps to reproduce**\n[nonselectable.blend](nonselectable.blend)\n\n- Open file\n- Try to select octagon" ]

[ "Bevel Modifier: Inconsistent vertex colors with odd-numbered segment counts\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\n\nWhen using the bevel modifier with a vertex-colored object, using odd-numbered segment counts creates unusable results.\n\nImage 0: Base mesh\n\n\nImage 1: One-segment bevel, with broken color regions\n\n\nImage 2: Two-segment bevel, clean regions\n\n\nImage 3: Three-segment bevel, broken regions\n\n\nProvided blend file illustrates the issue. Simply adjust the segment count on the simple cylinder that has some vertex colors and bevel weights.\n\n[bevelcolors_bug.blend](bevelcolors_bug.blend)\n\nPreferred result would be for color regions to remain clean with odd-numbered segment counts. \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", "Grease Pencil mask error\nOperating system:windows10\nGraphics card:GTX1060ti\n\nBroken: 2.83&2.9\nWorked:greasepencil-Mask error\n1.When 2.83 or later, creates two objects, the masks collide, causing a strange phenomenon, and in 2.82 there are no errors.\n2.And creating two masks under the same object can cause problems too。\niJlqkf556sA\n[GP剪贴测试.blend](GP剪贴测试.blend)", "Proportional Editing in Mask mode only works with \"G\", not with slide_marker\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.93.0 Alpha\nWorked: never\n\nCould be that this is more a design issue, but it feels very inconsitent to me and I cannot find a good reason for it.\nWhen proportional editing is enabled in Mask mode, it only works when you use \"g\" or the move tool to actually grab the mask control point and move it, but when you use the left mouse button (= \"slide_marker\") it only moves the current CV, without proportional editing. I am not sure there should be a difference between \"grab and move\" and \"slide_marker\" when it comes to proportional editing.\nWith keymap set to right click select this is maybe less of an issue because you can right click and drag to tweak the curve (and thereby using proportional editing), but with the default of left click select there is only slide_marker available as a tweaking option, and that does not use proportional editing. \nI suggest to have proportional editing during slide_marker as well. \n@SeanKennedy what do you think about this?\n\nOpen this file:\n[mask_drawing.blend](mask_drawing.blend)\nUse use left mouse button to slide any of the mask points. No falloff is in use.\nNow try the same with \"g\". Proportional editing is in use.", "No Vector Displacement On Instances\nWindows 10 x64\n\n2.79.4\n\nVector displacement doesnt work with instances, It mirrors the displacement on the first object, Im sure this is working as intended but there are many cases where you need to displace actual instances as well.\n\nHaving a checkbox somewhere to enable instance displacement would be amazing\n\n\n\n\n\n[instances.blend](instances.blend)\n", "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.", "Keyed particles work on viewport but not in render, also they are not affected by force fields\nOperating system: Linux-4.15.0-20-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Desktop Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.2.8\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen making a particle system with keyed physics, it works in viewport but the particles do not show properly in the final render. They reappear from the world center when all the previous particles die. Also the particles of the keyed particle system are not affected by force fields.\n\nSee the link for screen recording and the sample file.\n\nThe problem shows in blender 2.80 and 2.81 but not in 2.79.\n\nI think this might be a bug in blender 2.8 but I hope you can help me to solve it.\n\nscreencast\n\nview?usp=sharing\n\n**Steps to reproduce:**\n[#69238.blend](T69238.blend)\n\n- Open file\n- Render animation\n- Compare output to viewport\n\n\n\n\n\n", "Shape keys for surface not working - no active option\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.17\n\nBroken: version: 3.5.0\nBroken: version: 3.6.0\nWorked: don't know any version where this working, but last time no option for use this doing hard work\n\nShape keys for surface not working - no active option. \n\nThis not working like expected as typical object have verts. See screen.\n\n", "When double clicking to selecting text the first characters aren't selected\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.2\n\nWhen you double click on any text field with the intention to select all of the text when you start dragging to select the other words the first characters dont stay selected\n\ndouble click on a word and then drag your mouse to select the next or previous words. Some of the characters will always become unselected when you drag the mouse as seen in the attached video\n\n\n\nusually when double clicking a word the entire word stays selected regardless of where the initial mouse location was when double clicked but in blender the characters before or after the mouse location when double clicked don't remain selected when you drag to select more words", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "Issues with Fluid sim INSIDE objects\nOperating system: Win 10\nGraphics card: Twin GTX 1070\n\nBroken: 2.92\nWorked: 2.91\n\n**Fluid sim inside properly meshed objects does not work at all**\n- Create a tube with a curb or a Cylinder,\n- add a solidify modifier and apply it,\n- put a icosphere and downscale it to fit inside the tube,\n- keep icosphere selected and go to Object -> Quick Effects -> Quick Liquid.\n- scale the domain to fit everything inside.\n- Use tube as effector (planar or not does not work either way)\n- Try to bake a sim.\nAll settings that used to work in 2.93 and 2.91 do not work AT ALL in 2.92. Looks like it considers the mesh as a closed object.\n\nThanks in advance", "Transfer shape key is only working for meshes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: Never\n\nTransfering shape keys is option in panel menu, but it only works for meshes. This is not mentioned in documentation and only evident after running the operator.\n\n\nDuplicate object in provided file and try to transfer shape keys.\n", "View Pan not working for smaller clip start value\nOperating system: win 10 pro\nGraphics card: rtx 2060\n\nBroken: 3.5, 2.83\nWorked: never?\n\nFor smaller `clip start` value when we zoom out, `View pan` does not work\n\n- Open .blend file\n- Pan around by any method\nIncrease `clip start` value, this will fix panning problem\n[Sand_003.blend](Sand_003.blend)", "Cursor jumping to edge of screen when lifting pen from tablet area (wintab)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93\n\nTablet model: Huion h950p\nTablet api: Wintab\n\nWhen lifting the pen away from the tablet area, the cursor occasionally jumps to the edge of the screen, causing unexpected camera jumps or preventing hotkeys from being used in the 3d view.\n\nThe problem only happens with the Wintab api.\n\n\n - Set the tablet api to Wintab\n\n - Start creasing some edges and repeatedly lift and return the pen to the tablet area\n\n[cursorjump.mp4](cursorjump.mp4)\n\n", "No fluid particles created when switching from gas to liquid\nOperating system: Linux-5.4.0-40-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.90.0 Alpha\nWorked:2.83 sometimes shows the same behaviour, and sometimes it works (???) however in 2.90.0 I can consistently reproduce this.[logs.zip](logs.zip)\n\nWhen 'manually' creating a fluid sim, no particles are created, while when using 'quick liquid' it does work as expected.\nChanging the cache to an empty directory correctly initializes the particles.\n\n- default startup\n- switch to wireframe view\n- duplicate startup cube\n- scale duplicate x 2\n- select original cube. go to physics properties. check liquid.\n- choose 'type = flow' in fluid panel\n- choose 'flow type = liquid' in the fluid settings panel, leave the rest of the settings as is.\n- select larger cube\n- go to physics properties, check fluid\n- check 'type = domain'\n- check 'domain type = fluid'\n\nNo particles are created inside the small cube. \n\nGoing to the cache settings and selecting a different (empty!) cache folder solves it makes it create particles.\n\nWhen I set MANTA::with_debug to 1 and I compare a run between 'quick fluid' and 'manual fluid' the first obvious difference is that has_data is 1 in the 'manual' fluid run.\n\nCould it be that erasing the cache for the unused gas cachedata fails somehow?\n\nAttached are two console outputs , one from quick fluid and one using the manual steps above (except that I used a different scale factor for the domain in these runs) \n\n\n(edit: removed embedded text files and added them as a zip)\n(edit2: cleared up some mixup with the bugreport I originally wrote for 2.83)\n(edit fix small typo)", "After duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\n\nBroken: `master` branch\nWorked: Don't know if it ever worked\n\nAfter duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\n\n**Steps to Reproduce**\n\nIn a new blender project, add a new collection. Add a cube to the collection. Add a rigidbody to the cube. Verify that playing the simulation causes the object to fall under gravity.\n\nCopy and paste the cube to create a new cube inside the collection. Move the new cube so both are visible. Verify that playing the simulation causes both cubes to fall under gravity.\n\nIn the outliner right-click on the collection and select \"Duplicate Collection\". Move the two new cubes so all four cubes are visible. Run the simulation.\n- The two cubes in the original collection will fall under gravity.\n- The two cubes in the duplicate collection do not move and are not affected by the simulation.\n\n \n\nIt appears the two cubes in the duplicated collection are not added to the RigidBodyWorld collection.\n\n" ]

[ "Tablet pressure sensitivity only working in original main window.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\nGraphis Tablet: Huion Kamvas Pro 20 (Window's Ink)\n\nBroken: version: 2.81 (sub 15) AND 2.8 release \nWorked: (didn't work in any version I tried)\n\nAfter creating a new window, main or otherwise, tablet pressure sensitivity doesn't work in that window but remains working in the original window.\n\nCreate new window, add object to sculpt on, try to sculpt with pen with pressure sensitivity on.\n\n", "Tablet Pressure in new window not working\nOperating system: Windows 7\nGraphics card: Nvidia gtx 760 // Huion Kanvas pro 13\n\nBroken: (example: 2.80, 8b2b79c2108b, master, 2019-06-06, as found on the splash screen)\nWorked: (optional)\n\n\nWhen you Duplicate \"Area into New window\", and work in the graphic tablet, pressure sensitivity for strength / size / autosmooth, don't work.\nYes it works in original windows. \n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Freestyle > \"Render Animation\" uses only the widest keyframed focal length for all the frames\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 16)\nBroken in the most current 2.83, date: 2020-02-17 00:09:39, hash: `819af2094b21\nWorked: 2.8\n\n\nWhen the focal length of the camera is keyframed to different values over several frames, Freestyle takes only the widest focal length and uses it for all keyframes\n\n[Freestyle_Test.blend](Freestyle_Test.blend)\n1. Open the attached blend file\n2. Set the Output location for the rendered images\n3. Select \"Render Animation\" and check the finished frames\n\nThanks so much for your help! Highly appreciated\n\n", "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", "Missing red border for render border in Image Editor\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\nIn the 3D view you have a red border around an active render border. In the Image editor not.\n\nThis can lead to hours of lost render times since you cannot see if a render border is active or not. And is inconsistent. Two equal functionalities should work equal.\n\nOpen Blender, activate Render border in the 3D view and render a portion with viewport shading rendered.\nNow render the image, and render a portion of the image with enabled render border. You will notice that in the 3D view you have a red rectangle that indicates that the render border is active and what area to render. \n\nBut in the image editor you just see that just a portion is rendered. The next render can be with or without render border. There is no visual hint if the tool is active or not. And no hint if you have selected the correct area for preview rendering.\n\n\n\n\n\n\n", "Freestyle wireframe-only rendering is broken with Ztrans faces (lines disappear when Ztrans alpha and Ztrans spec are set to zero / lines behind transparent faces are not rendered / marked edges are not sometimes rendered when faces overlap)\nOSX 10.11.2 / Macbook Pro Retina 15\" Mid 2014 / GeForce GT 750M\n\nBroken: 2.76b (also broken in 2.76)\n\nRendering wireframes with controllable wire thickness requires using Freestyle but Freestyle requires filled faces even when rendering only edges. To only render edges and make the faces invisible one must set Ztrans alpha to zero.\n- When other line objects are behind line-only objects their lines are culled (however ordinary objects are rendered properly)\n- When both Ztrans alpha and spec are set to zero no lines are rendered\n- When faces overlap only some marked edges are rendered (even when faces are set to be transparent)\n\nObserve and render the attached .blend file.\n[freestyle-lineclipping.blend](freestyle-lineclipping.blend)", "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", "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", "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", "Motion blur artifacts on complex object animation (reproducable)\nOperating system: win10\nGraphics card: 2070super\n\nBroken: (example: 2.83.4, 2.92.0alpha)\n\n\n**motion blur gives strange artifacts in some frames.**\n\n[bug_motion_blur.blend](bug_motion_blur.blend)\n\n\nIn the attached file, this happens on frames 9 and 20. Bug reproducable", "Line Art isn't updating active camera\nOperating system: GNU/Linux mint 19\nGraphics card: gforce RTX 2060\n\nBroken: 2.93.4 \n\nLine Art isn't updating active camera when it's changed in a 'Scene' strip (VSE)\n\n\n- Create a scene, a camera and a LineArt object.\n- Now, create a 2nd camera (Cam.001) (not the active one)\n- Create an empty scene in order to be used for video creation.\n- In `Video Sequencer`, add a Scene strip and choose the Cam.001 camera ->it changes ok, but lineart goes dependent on the first one.\n\nTest File:\n[#91971.blend](T91971.blend)", "GizmoAPI: Lines appear between triangles using \"DEPTH_3D\" option.\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.56\n\nBroken: version: 3.1.0 Alpha\n\nWhether using the built-in `draw_preset_facemap()` to draw face maps or the `draw_custom_shape()` function to draw based on a list of arbitrary vectors, as long as the GizmoGroup has the \"DEPTH_3D\" option to enable depth culling, see-through lines appear between the drawn triangles:\n\n\nThis doesn't seem to be affected by the widget's alpha color, and doesn't seem to be related to z-fighting, because it still happens when using a second mesh that has a Displace modifier and is hidden. But, it is purely cosmetic.\n\n- Prototype addon: [bone-gizmos.zip](bone-gizmos.zip)\n- Minimal test file: [ellie_mesh_gizmos.rigging_minimal.blend](ellie_mesh_gizmos.rigging_minimal.blend)\n- Mouse hover on the jacket sleeve\n\nCC @ideasman42 ", "Edge-slide seems to highlight an edge now (visually noisy and inconsistent)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\nWorked: not sure, maybe early july?\n\nEdge-slide seems to highlight a split edge now which seems a bit visually noisy and inconsistent. It's visually noisy since it's not adding much for the user (it's not an indication of snapping target for instance) and represents another visual color change that distracts the user from the primary operation. Inconsistent because it's based on the location of your mouse when invoking the operation which leads to really weird cases like the following.\n\nA hidden edge being highlighted on this cube:\n\n\nOr different edges depending on slight differences in mouse position between edge-slide attepts:\n\n\n\n\n\n- Go into edit mode on default cube in default scene\n- Add an edge loop and attempt to slide it\n\n", "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", "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", "Cursor jumping to edge of screen when lifting pen from tablet area (wintab)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93\n\nTablet model: Huion h950p\nTablet api: Wintab\n\nWhen lifting the pen away from the tablet area, the cursor occasionally jumps to the edge of the screen, causing unexpected camera jumps or preventing hotkeys from being used in the 3d view.\n\nThe problem only happens with the Wintab api.\n\n\n - Set the tablet api to Wintab\n\n - Start creasing some edges and repeatedly lift and return the pen to the tablet area\n\n[cursorjump.mp4](cursorjump.mp4)\n\n", "Cycles: Motion blur artifacts\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.88\n\nBroken: version: 3.2.2\n\n\n**description of error**\nWhen rendering an animated rigged model on cycle **with motion blur** ; if the model has **auto smooth enable AND a subdivision modifier**, then it is possible that strange artefact will appear during the render. (doesn't happen in the viewport) \n- This bug do not happen if auto smooth is disable or doesn't have a subdivision modifier. \n- The bug also only appear during some specfic poses. So this is mainly noticiable when rendering an animation.\n- Those artefact often appear near sharp edge.\n- Only happen on Cycle, Eevee render seem fine.\n- [Edit] changing the shutter values of the blur will sometime remove the bug on some frames OR make the bug appear on frame that was fine before.\n\nHere 2 Render exemple with and without autosmooth , both has motion blur enabled :\n \nAnd here an animation where you can notice the bug.\n[Animated0035-0318.mp4](Animated0035-0318.mp4)\n\n\n[MotionBlurCycleArtefact.blend](MotionBlurCycleArtefact.blend)\nIn this blender file, rendering the frame 302 will make the bug happen. \n- If you disable auto smooth on the model (the main body and not the cloth) then the render will be fine.\n- If you disable the subdivision modifier on the model then the render will be fine.\n- If you disable the subdivision modifier AND the auto smooth on the model then the render will be fine.\n\nThank\n" ]

[ "Blender Freestyle LineSet Visibility problem at Render\nWindows 10 64 bit Home\n\n2.77a\n\nCoincident planes with FreeStyle lines don't detect or render properly\nvia the Visibility condition for animation or image render.\nThis can occur via Freestyle Edges or Freestyle Faces.\nThis seems to be an issue inside Blender, irrespective\nof the render engine.\n\n\nHave one smaller plane precisely located on another larger one.\nBoth have the identical material reference to prevent z-fighting.\nThere are no textures or images on the planes.\nIt isn't always possible to have 1 smallest unit offset between planes,\nif for example one wants to do an origami simulation\nwith all paper folds accumulating to a virtual, zero thickness.\n\nThis issue can also prevent itself when animating\nbetween various such states using Key Frames,\nmaybe involving the AnimAll plugin.\n\nExamples include frames 400, 670, 560-580.\n\n[file.blend ](attachment.php?attachmentid=448546&d=1470892940)" ]

[ "Quick Favorites: add support for operator/prop enums (e.g. \"Set origin\")\nOperating system: Windows 10\nGraphics card: Nvidia GTX1080\n\nBroken: 2.80, 16fc62e15f0, blender2.8, 2018-12-12\nWorked: 3d92afca7eb\n\nThe Set origin menu is not possible to put into quic favourites.\n\n3dView -> Object menu -> Right click on \"Set origin...\" -> empty menu.", "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).", "Geometry Nodes: Disabled from viewport object is not visible as instance\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: Current main.\nWorked: Never.\n\nDisabled from viewport object is not visible as instance.\n\nOpen attached file and check/uncheck `As Instance` option of _Object Info_ node.\n\n", "3D View Selection Occlusion (Select Through) \nCreating this design task as there are unresolved issues with [D6322: Mesh: Select through](D6322) which are more design issues.\n\nThis is a place holder, some topics to address:\n\n- Where this option is stored, accessed?\n- Which selection tools/operators should use this?\n- Which modes this should be supported in (edit, pose, grease pencil... etc)\n- How to display this option when in wire-frame display (when the user will always select-through)\n- How to access this from both active-tools & key-bindings?\n- How to make it obvious selecting-trough is enabled *(draw style, cursor - this might help avoid confusion)*.\n- Should this be supported in object mode too?(the reverse since objects already select-through), IIRC we discussed having this option for box select too.\n\n\n### Related Topics\n\nNote that there are topics being raised which relate to select-through, but might be best treated as separate topics since we could change behavior here with or without select-through.\n\n- Current behavior of X-ray.\n- Current usability toggling X-ray (Z-drag or Alt-Z).\n- Selecting faces by their centers.\n- Lasso select using object centers #64281 (Option to lasso-select using geometry instead of object centers.).\n", "Proposed Size Preference for Color Picker\nI had fixed a bug that allows the [eyedropper to work in popups](105387). That led to other fixes, like [problems with positioning](106122) and that it can't currently work [outside Blender windows](105324).\n\nBut this work prompted some users on BlenderArtists to mention that it is [too small](589).\n\nWhile playing with the idea of making it user configurable, I came to agree that it is easier to use at a larger size that we have it now. This becomes especially important when users have very large monitors that are then used at a relatively small scale. This can give you a very large working area but a very small color picker.\n\nThe following capture was taken at 1.0 scale and shows it at the current size, a size that I liked much better, and then even larger:\n\n\n\nThere is a PR that can allow testing this: 106135\n\n", "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)", "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", "GPencil: W shortcut in Draw mode not working and displays error\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.1\n\nThe W shortcut used to display the Context menu, the same summoned with RMB, but it's not working & displaying this error message:\n```\nTool 'builtin.select_box' not found for space 'VIEW_3D'\n```\nOpen a new 2D Animation file and press W.\n\n", "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.", "Armature Object's \"Display As\" does nothing\nOperating system: Linux-5.3.0-26-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 6)\nWorked: version: 2.79 release.\n\nWhen I add an armature and change the Viewport Display Mode, nothing happens.\n\n\nOpen the blender;\nDelete the default objects;\nAdd an Armature, single bone;\nIn the Properties Panel, Object Properties, Viewport Display:\nChange 'Display As' to anything, it doesn't work.\n\n\n\n", "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", "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", "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", "Texture Paint - Clone tool not working when clone source area out of viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nTexture Paint - Clone tool not working when clone source area out of viewport\n\nImport image as plane- select part of image to clone in bottom part of image. Scroll up to the top part of image so the bottom is not visible = clone tool doesnt draw anything.\n\n\n\n", "Python API : OBJECT_OT_convert can't be fully abstracted from context with override\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 2.93.5\nIt didn't work in latest Beta build either.\nWorked: I don't think it ever worked otherwise ?\n\nOverriding the context of an operator with a dictionary enables us to call them from pretty much anywhere in the code without having to make sure the context is correct (selected objects, active object, called from a particular editor, etc.)\n\nHowever the `OBJECT_OT_convert` called with `bpy.ops.object.convert` operator still requires an active object to be selected to function with an override, which defeats the purpose of using an override.\n\nIt is explained quite thoroughly in this BSE Q&A 86891\n\nScript to reproduce in an empty file :\n\n```\nimport bpy\n\nbpy.ops.curve.primitive_bezier_curve_add()\n\n# Commenting these 2 lines removes the RuntimeError (context incorrect) on last line\nbpy.context.active_object.select_set(False)\nbpy.context.view_layer.objects.active = None\n\nbpy.ops.object.convert({\"selected_objects\": bpy.data.objects}, target=\"MESH\")\n```\n\n" ]

[ "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related.", "put a driver on the scale of an object\nOperating system: windows 10\nGraphics card: GIGABYTE NVIDIA GeForce RTX 2070\n\n\nWorked: 2.90.0\n\nBlender crashes every time I put a driver that copy the x scale (or y or z) of an object to another one.\n\n\n++I cannot attach my file it's too big++\n\nI select the object, add the driver on the scale (x, y or z). The quick driver window appears, but an error message appears the next second 'invalid python expression', even though I didn't do anything yet.\nThen I try to click on the pipette to select an object but nothing happens / it looks buggy.\nThen I go to the driver editor, the pipette works there, but after clicking the pipette, if I try to input an expression Blender crashes.\n(The same happens in the quick driver window)\n\nMy workaround is to fill the input variable, copy it, delete it, not fill the expression.\nThen re-edit the driver paste the variable, then edit the expression.\n\nI tried to redo the same thing with the location and the rotation, even though the pipette was still buggy, I couldn't reproduce the bug\n\nLet me know if I can help more", "Driver property cannot be picked in popup-driver editor, when applied on numeric value\nOperating system: Windows 10 x64 (20H2)\nGraphics card: Nvidia RTX 2070S\n\nBroken: 2.91.0\nWorked: ?\n\nIf a driver is added on a numeric value, the picker widget (e.g. to pick the object of the traget property) cannot be used. Instead of a normal cursor (arrow), the cursor for value selection (horizontal double-arrow) remains.\nWhen trying to pick an object, the popup-driver editor closes immediately. The same applies when the driver is edited, using the context menu.\n\nEdit: The picker seems not to work at all in the popup window, regardless of the value type of the applied field\n\nPicking only works in the \"Drivers\" Editor (Shift F6)\n\nSee attached animation\n\n\n\n1. Select an object\n2. Hover over a numeric field (e.g. Location X)\n3. Right-Click\n4. Select \"Add Driver\" in the context menu\n - The popup window to edit the driver opens\n5. Click on \"Add Input Variable\"\n6. Try to use the object picker on \"Prop:\"\n - The picker cannot be used", "Object picker not working in driver pop up menu\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce 940M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.93.0 Alpha\nWorked: not sure, has been broken for some time\n\nwhen adding a driver via context menu, the picker tool in the pop up doesn't work. This is also true for the floating driver window.\n\n\n", "Eye dropper in driver edit pop-over window does not work.\n**System Information:**\nOperating system: Linux-5.8.0-3-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060 SUPER 450.80.02\n\n**Blender Version:**\nBroken version: 2.92.0 Alpha, 2.90, 2.83, 2.82\nWorked: Unsure\n\n**Short description of error:**\nThe eye dropped in the driver editor pop-over window does not appear to work. \n\n**Exact steps for others to reproduce the error:**\n1. In any file, give a property a driver by `Right clicking` on it and selecting `Add Driver`.\n2. Right click the property again and select `Edit Driver`. A window should pop up.\n3. In the default driver, there is `Object Data Block` selector field with an eye dropper (see image below). Select the eye dropper and try to select an object. This will not work.\n\nNote: The eye dropper works in the side bar of the driver editor, just not in this pop-over.\n\n", "\"Edit Driver\" window, can't select object with the eyedropper.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro #1000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.66\n\nBroken: version: 3.5.0 Alpha\nBroken: version: 3.3.1\n\nI can't select an object with the eyedropper in the small window of the \"Add/Edit Driver\".\n(In the Blender Drivers Editor window, it worked as it should)\n\n\n1. Right-click on some input (X Location for example)\n2. Select \"Add Driver\" or \"Edit Driver\" from the menu.\n3. Try to click on the eyedropper - > unclickable.\n\nAttached is the screenshot of the \"Edit Driver\" window with the problem and the Blender Drivers Editor window.\n\n\n", "Can't use the object picker from 'Edit Driver' popup\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nWorks fine from the Drive Editor.\n\n\n1. Add a driver in the location of the default cube\n2. Now, right click in the field and choose 'Edit Driver'\n3. Try to choose the object picker.\n\n", "Object Picker in Driver Editor doesn't work because moving the mouse away closes the driver editor popup\nOperating system: Linux-5.4.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: AMD Radeon VII\n\nBroken: version: 2.91.0\n\n\nDuplicate default cube, move it away somewhat.\nSelect either cube, go into object properties, right click and add driver to a transform channel.\nSet the driver variable to \"transform channel\".\nAttempt to use the eyedropper in the \"Object\" field of the variable to select the other cube.\n\nIt doesn't work, as moving the mouse out of the driver editor closes the driver editor.\n\nIn my opinion, the driver editor should have a close button that must be clicked. It should not close on \"mouse-out\", as you might be using the eyedroppers or moving through other parts of the UI (or even other applications) to get values to copy-paste into the fields. It should be (somewhat) more of a first-class window then it is.", "Driver Editor object picker problem\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90.0 Alpha\nWorked: Never (2.8+)\n\nObject picker in Floating Driver Editor does not work.\n\n1. Open Blender\n2. Right-click on a property (like the cube's location x), Add Driver, and click the eyedropper in the floating driver editor.\nThe eyedropper disappears without any effect." ]

[ "The alpha channel set in Viewport Display settings for an object's material appears as if it's set to 0 when a background image is behind it\nOperating system: Linux x64 (Debian-based)\nGraphics card: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a)\nNvidia drivers, version: 440.31\nKernel: 4.19.0-6-amd64\n\nBroken: v2.81a and v2.80, downloaded from blender.org as a tar.gz\n\nWhen you change the Viewport Display color for an object to have an alpha channel < 1.0 but > 0.0, then manipulate the scene so that there's a reference or background image behind that geometry, the overlapping area will appear completely transparent (alpha 0.0).\n\n\n1. New scene\n2. Add a cube: Shift a -> Mesh -> Cube\n3. Add an image: Shift a -> Image -> Reference (or background)\n4. Select an image\n5. Position the image behind the cube in the viewport. Select the cube.\n6. In the properties panel, select Material Properties\n7. In the Material Properties panel, select Viewport Display\n8. Change the Color to have an alpha between 0.0 and 1.0, exclusive\n\n**Observed behavior**\nLike the screenshots, the overlapping area allows the background image to completely shine through.\n\nQQxLCpv\n\n**Expected behavior**\nThe object will become uniformly translucent and allow the background/reference image to be partially visible, not make the image fully transparent in the overlap.\n\n", "Default Value for Viewport Display Color's Alpha Wrong.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.92.0 Alpha\nAlso tested on 2.83.8 and same problem.\nWorked: It do not think this has ever worked\n\nWhen reverting to the Default Value for Viewport Display Color the alpha gets down to 0.8 making the object semi transparent.\n\nOpen up a new scene.\nSelect the cube.\nGo to the materials tab.\nScroll down to \"Viewport Display\"\nRight Click on \"Color\"\n\"Reset to Default Value\"\nResult: RGB values go back to the default, but Alpha goes to 0.8\n\n\nThank you so much !", "Dynamic Indirect light cache\nThe idea would be to have a multiple level cache that stores a voxelized version of the scene to render the irradiance points.\n\nEach voxel would be linked to a set of surfel (surface elements) that stores color and normal of the surface.\nEach time the lights in the scene changes, the voxelized version is updated and propagates the change to the irradiance points.\n\nThis means having a list of surfel per voxel (say 6, 8) and a list of voxel per irradiance points.\nThis would be a mix of The Division dynamic indirect lighting [link]] and Mc Guire raytraced irradiance probes [[http:*jcgt.org/published/0008/02/01/|link](https:*www.gdcvault.com/play/1023273/Global-Illumination-in-Tom-Clancy).\nThis feature might be limited to hardware that supports compute shaders.\nThis is not a trivial feature and needs a lot of R&D.\n\nEstimate : 4 weeks\n", "Exchanging a color in Grease pencil from a color attribute is bugged\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 3.4.1\n\n**Short Description**\nExchanging a color in Grease pencil from a color attribute is bugged\n\n- Go into 2D animation\n- Draw a shape with a fill color using a color attribute\n- Change color attribute and draw another fill stroke\n- In materials tab create a new fill color\n- Assign that color in edit-mode to the shape to replace color attribute. \nIt doesn't look like it got applied. Go into viewport shading with material view and the assigned color is there. Pressing F12 shows the color that is supposed to be overwritten.[Color error.blend](Color_error.blend)", "Grease Pencil: draw pixels don't scale to pixels.\nCurrently grease pencil uses pixels in a very confusing way, since it doesn't actually relate to pixels.\n\nEither:\n\n- The size of a brush should use the current zoom level and use pixels as we do for all other draw tools.\n- We should use blender units for grease pencil brushes.", "Grease Pencil - drawing preview ignores canvas settings\nOperating system: Windows 10 Pro 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nBroken: 2.83 and 3.5 latest\n\nWhen previewing grease pencil (before pen release), the Stroke Placement settings do not render properly. It looks like the preview is stuck on \"View\" but renders correctly on pen release. In my GIF you can see the strokes clipping, but appear correct after pen release. Can this be fixed? It's easily repro'd and consistent in multiple versions\n\n1. Create basic Mesh.\n2. Create Grease Pencil object above Mesh.\n3. Set Stroke Placement to \"3D Cursor\" or \"Origin\" and set Drawing Plane to anything but View.", "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!", "Shadows stop working properly when changing render pass in viewport.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1404\n\nBroken: version: 3.5.1\n\nWhen doing a certain shading setup and changing render pass, the shadows break.\n\n- Create a new project, keeping the render engine to eevee\n- Make a new material and apply on default cube\n- Connect any image texture into the color input of principled bsdf\n- Connect any image texture into the normal input of principled bsdf while setting its color space to non-color\n- Switch viewport shading to rendered\n- Switch render pass to shadow and then back to combined\n- The lights will now not produce any light unless their shadow setting is turned off\n\nAny other nodes added before or in-between the image texture node do not seem to affect the result.\nThe shadows will stay like this until blender is closed and reopened again.\n\n", "2.83lts Regression: Viewport render image ignores colormanagement, and appears to be hardcoded to use sRGB.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBisect points to 190fd795a9\nBroken: version: 2.83.0\nWorked: 2.82a\n\n`Viewport Render Image` ignores color management. The image produced is clamped to 1.0 according to the color sampler. It appears to be hard coded to sRGB.\n\nCreate a Scene that has scene linear color values above 1.0. Render with Filmic. Then do `viewport render image` and see how it produces an image with blown out highlights.\n\n2.82a:\n\n\n2.83:\n\n\n\n[test.blend](test.blend)\n\n", "User defined default color for images\n**The Default Color**\n\n_**If you map a texture in such a way that the image doesn't cover the entire model, the default color should show up.**_\n\nInterestingly Blender does have a default color and as far as I know the only way to see it is to set an image texture extension mode to _Clip_. In that case, any UVs mapped outside of the image space get the color black (0.0, 0.0, 0.0). However this default color can not be currently defined by the user.\n\n\n\n**The Panic Color**\n\nThe panic color for images AKA the bright magenta (1.0, 0.0, 1.0) appears when an image file has not been loaded correctly. It's meant as a visible warning for **missing images**.\n\n\n\n**The Problem With UDIMs**\n\nExternal texturing tools are able to _skip_ UDIM tiles that do not contain any valuable information apart from the base color value.\n\nBlender doesn't correctly support variable size UDIM sets and expects all UDIM sets to be of equal size.\n\nThe panic color currently shows up when dealing with **variable size UDIM sets** (color, normal, roughness, etc).\n\nAs a way of an extremely simplified example I've created the following file featuring a material with 2 UDIM sets, one for the Color and one for the Normal.\n\n\n\nThe problem appears because the 2 UDIMs are not conformed by the same number of tiles (images).\n\nThe Color UDIM with 3 tiles:\n\n\n\nThe Normal UDIM with 2 tiles:\n\n\n\nThe Normal UDIM delivers the panic color (magenta) in the non existing 1003 UDIM tile.\n\nThis is incorrect behavior since no image is really missing (there can not be a missing image if the tile does not exist in the first place).\n\n\n\n**The proposal**\n\nAllow for the default color to be user definable.\n\nIn the case of single image textures with extend mode set to clip, this color is applied to any UVs that exist outside of the (0.0, 0.0) - (1.0, 1.0) space.\n\nDefault color set to (0.28, 0.25, 0.2):\n\n\n\nIn the case of UDIMs this color is applied to any UVs that exist outside any tile.\n\n\n\nDefault color set to (0.5, 0.5, 1.0) AKA the bluish normal base color:\n\n\n\nFor existing tiles that have failed to load their image (missing images). The pink panic color is **still expected**.\n\n\n\nPanic color to be expected since the tile **exists** but it's image was not found.\n\n", "VSE: Transform settings doesn't get copied across scenes\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\nTransform settings doesn't get copied across scenes\n\nCopy a strip, which doesn't match the render resolution, across scenes:\n{[F10121941](copy_missing_transform.gif),size=full}\n\n", "Data changes in pre and post scene evaluation handlers not recognised by Cycles, plus occasional ACCESS VIOLATION and inconsistent scene properties.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.4.0 Alpha\nWorked: (Unsure)\n\nCycles is not using the evaluated scene following scene modifications via handlers that fire before scene evaluation, and some data refers to the previous frame whilst other data refers to the frame currently being rendered..\n\n\nHi, we're trying to get Blender fully integrated into our studio, but we're running into quite a lot of issues with handlers. It seems that Cycles is only partially recognising changes made to the scene in the pre_render, pre_frame, and post_frame handlers. \n\nIn the below zip file there are 3 directories, each containing a blend file with a simple script to demonstrate the issue. The script changes the file output node's base path, and it also changes blender own render.filepath in the output properties panel. The new file name includes the scene camera name (which changes on frame 1 and 3 using markers) and the frame number when the handler updated the filepath/base_path properties, followed by the __0001 added by Blender. For example frame one should read: left cam_updated_path_on_frame_1__0001.png\n\n**Steps to reproduce problem**\n\n\n\n - Unzip [cycles handler bug.zip](cycles_handler_bug.zip)\n - open each of the blend files in place (use 'load UI' as I've set up the workspace for the easiest testing)\n - notice that the blender output is set to 'not set yet', as is the file output node in the compositor.\n - choose to render the animation\n # In the folder where the current blend file resides there will now be two additional folders, one for blender's output, and another for the file output node's results.\n\n\n**Results**\n\n**pre_render handler**\n\nAs expected the camera is incorrect because the pre_render handler happens before the scene has been evaluated. Although strangely some of the information is for the unevaluated frame that the playhead has just moved to (the frame number) and some is for the frame the playhead was on prior to beginning rendering (the camera name which was active on frame 4 before the playhead moved to the beginning of the animation ready for rendering in this example).\n\nBlender's own image sequence output does use the new path which was assigned whilst in the first frames pre_render handler, but on the first frame, the camera name is incorrect and the frame number is correct:\n\n\nThe file output node images however show that cycles didn't recognise that the base_path property had been updated until the next frame. We can see here that the file ending in __002.exr was updated on frame 1, but not used until frame 2, and this continues all the way through.\n\n\n\n**pre_frame handler**\n\nStrangely, although this handler also fires prior to the scene being evaluated (directly after the pre_render handler), this time Blender's own output shows the camera name is now correct, but again, the updated file output node is still not being used until the following frame:\n\nblenders output:\n\n\nfile output node's output:\n\n\n\n**post_frame handler**\n \nBlender's output again is correct, but the file output node's new path is not being recognised:\n\nBlender's output:\n\nFile output node's output:\n\n\n\nThe above can be worked around with code by grabbing the camera from the marker list instead of the active scene camera, but one really major issue for us is that even when locking the viewport prior to rendering, if we update the file output node's base_path, we start experiencing occasional Access Violations and instant crashes, this happens even if the file output node's path is not visible to UI. (perhaps this is related to the reason why the base path isn't being recognised until the next frame?)\n\n\n", "Bump map texture painting in 3d viewport applies gamma correction to 32-bit float noncolor image data. \nOperating system: **NA** (Windows-10-10.0.18362-SP0 64 Bits, Darwin)\nGraphics card: **NA** (GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35, AMD Radeon HD 6970M 4.1 ATI-1.68.25)\n\nBroken: version: 2.90.1, 2.92.0 Alpha\n\nWhen texture painting a float non color image, the `3D viewport` uses a different `mix` algorithm than the one used on byte images in the 3D viewport, and floats and bytes in the `Image Editor`.\n\n\n\n| **Mix additive ?** | Byte | Float |\n| -- | -- | -- |\n| Image Editor | Yes | Yes |\n| 3d Viewport | Yes | No |\n\n\n\n\n\n\n\nProblem with texture painting bump maps. The image above shows two drawn curves. The left curve was drawn in the image editor, the right curve was drawn in the 3D viewport. Brush color is set to (r,g,b)=(0.6,0.6,0.6). The image texture used for the bump map was generated by the brush tool which creates a noncolor image set to 0.5. The problem occurs when specifying a 32-bit float for that image. \n\nYou can open the 2 following .blend files, and try painting a stroke in both the 3D viewport and the Image editor.\n\n\n\n[T82818_texturepaint_mix_byte.blend](T82818_texturepaint_mix_byte.blend)\n\n\n\n\n\n[T82818_texturepaint_mix_float.blend](T82818_texturepaint_mix_float.blend)\n\n---\n[system-info.txt](system-info.txt)", "Same pattern looks different for Cycles and Eevee\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.1\n\nThis is the difference\n\n\n\n\nsimplified file\n[pixels tiled1.blend](pixels_tiled1.blend)\n\n\nold file \n[pixels tiled.blend](pixels_tiled.blend)\n\nI suppose the difference in Color Ramp or Noise node.\n", "Filter color bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.1\n\n\nHue color and color bar doesn't sinchronize\n\n1) change object in sculpt mode\n2) use colore filter\n3) option fill\n4) try to change hue color\n\n" ]

[ "\"Disable hard coded Color Space texture setting\" checkbox\nOperating system: Windows 7 SP1, 64-bit, i5-4670K\nGraphics card: NVIDIA GeForce GTX 1070\n\nblender-2.80 branch\n\nColor Space setting under the Texture Tab is ignored under certain circumstances, which seem to be filename dependant (-diffuse, -normal) but also format dependent regardless of OCIO configuration.\n\n**Possible Solution**\nCreate documentation on the hard coded color spaces and keep the behavior for newcomers but allow a checkbox to disable hard code settings to rely completely on OCIO configuration." ]

[ "Outliner: Double click on icon to select contents/hierachy\n**Motivation**\n\nUsers often want to select all objects in a collection, or all (direct or indirect) children of an object to transform them together, or apply different operations. For this, the Outliner context menu already provides *Select Objects* when right-clicking on a collection, and *Select Hierarchy* when right-clicking on an object. Since these are such common/useful operations, faster access would be a good quality of life improvement.\n\n**Design**\n\n- Double clicking on the icon of a collection should select all contained objects, even those contained in nested collections. I.e. execute the *Select Objects* logic. The collection itself does not need to be selected (although it might be fine to do it).\n- Double clicking on the icon of an object should select the hierarchy including the clicked on parent object. Ie. execute the *Select Hierarchy* logic.\n- The collapsed or opened state of tree elements should be ignored. So the children should be selected when double clicking on an object for example, even if the object element is collapsed and thus doesn't show its children in the Outliner.\n\nNote that both cases are an operation acting on the entire hierarchy, so they are recursive. With the difference that the first doesn't keep the clicked on element selected, while the second does. Other than that these are consistent operations.\n\n**Corner Cases to Consider**\n\n- If an object has a child that is not in the same collection as the parent, double clicking the collection icon should not select that child object. Only the objects actually contained in that collection (directly or indirectly) should be selected.\n- Ideally: When objects or collections are linked into multiple collections, only the hierarchy that was clicked on should be selected in the Outliner, not the other occurrence of it. This is better explained visually: [outliner_select_multi_link-2022-06-29_17.42.42.mp4](outliner_select_multi_link-2022-06-29_17.42.42.mp4) Note how even though the Suzanne object gets selected properly (orange font), only the clicked on Outliner element gets selected (blue element highlight). Note that the existing *Select Objects* and *Select Hierarchy* don't behave this way, they select all occurrences in the Outliner. Therefore this is more of a nice-to-have feature.\n\n**Implementation Notes**\n\n- An new operator can be added that is invoked with a double-click in the Outliner, checks if the cursor is over a relevant icon, and executes the logic then.\n- The last corner case mentioned above (with the video explanation) can be done by selecting the tree element and updating the object selection from this with `ED_outliner_select_sync_from_outliner()`. If done the other way around (object is selected and outliner tree is synced from that), all occurrences would be selected in the Outliner. This is what the existing *Select Objects* and *Select Hierachy* do, and it's a bit tricky to correct that.", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "After opening File explorer with export shortcut the window doesn't ignore the first click from selecting something behind 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 445.87\n\nBroken: version: 2.90 (sub 0)\nBroken: version: 2.82 (sub 7)\n\n\nAfter you open the file explorer and the first click you do will select an object behind the window if there is any. Annoying if you use selected objects to export. Seems to only happen if you use a shortcut to export to any file type. Couldn't reproduce with selecting file -> export -> any file type.\nEdit: If there is no objects behind where you click you will deselect everything.\n\nWith default scene. Short cut some export file type. File -> export -> filetype -> assign shortcut. hit the shortcut and if you click in the file explorer window where the default cube is you will select it.\n\n", "Selection Options\nDesign for expansion of selection and adjacent features.\n\n**Introduction**\nI made a build for 3.60 that is mostly about selection, check out the source if you want #109150\n\n[Here's a video about my build that I will reference throughout.](watch?v=HVrFCOa7RO8)\n\nI will be updating my build and it's individual features to 3.6 over the next week or two, then I'll update them to main after that. I'll link to the pull requests of each individual feature, they don't have much in the way of description and are behind the main build I made, but I will be updating them. \n\n**Edges and Faces**\nAt 0:42 in the video above. \n#109309\n\nGive some options in the keymap for more control over how user can box/circle/lasso select edges and faces. \n\nA dropdown for Edge Select with up to 3 options:\nDefault does Blender does, and Circle doesn't have this option\nTouch will select anything the selection area touches\nEnclose will select edges that have both ends inside the selection area\n\nAll 3 tools have 4 options for selecting Faces:\nDefault does what Blender does\nTouch will select anything the selection area touches\nEnclose will select a face if all their verts are inside\nCenter will select a face if you touch their center\n\n**X-Ray**\nAt 2:38 in the video above.\n#109318\n#109319\n\nBlender doesn't select unseen mesh. You select what you can see. If user wants to box/circle/lasso select something on the other side of a mesh, they'd either turn on X-Ray or move the camera until it's visible. With objects Blender always selects through, and it can't be turned off. Give user control over this, and provide some convenience features. \n\nMake a popover for the X-Ray button. Move the X-Ray settings here from the Shading Popover. Give them new names so it's more clear that wireframe and solid have separate X-Ray properties.\n\nIf user wants to box/circle/lasso select unseen mesh without X-Ray, they can use Select Through. They can decide which tools and modes will use it. \n\nIf they don't want to change how X-Ray affects box/circle/lasso selection, they can use Automatic X-Ray. When they start to drag select it will turn X-Ray on, and when the selection is done X-Ray will turn off. They can decide which tools and modes will use it. \n\nInclude some operators. User can show any combination of them in the Header. If everything necessary for the tool and mode is enabled, the button for the operator will be lit up. It's modular, so there are many ways for the user to setup their shortcuts. Make new icons for Auto X-Ray and Select Through, the ones in my build were made by Alexey Adamitsky.\n\n**Viewport Facing Select**\nAt 4:17 in the video above.\n#109357\n\nBlender _does_ select unseen Mesh, and not in a good way like Select Through. If user can see some verts of an edge or face, they're potentially selectable regardless of their visibility. If it isn't truly random which unseen edges and faces this applies to, it may as well be. The 3 drag selection tools select the same wrong things, but if the viewport camera is moved or rotated, this will usually mean that different unseen edges and faces are now selectable.\n\nThe opposite is also a problem, where user cannot select visible mesh. If user zooms out, has a complex mesh, or a shallow angle on it, selection bitmap will only capture some of the mesh and give a patchy bit of what the user wanted. Long term, need to increase resolution of selection bitmap, whatever that would mean. Maybe Vulkan affects this in a positive way, maybe it has nothing to do with it. \n\nFor now I made Viewport-Facing Select to deal with this. Put it in Toolsettings. It works in near select, X-Ray, or both. When user drag selects with box/circle/lasso, it compares mesh normals to the viewport. If they aren't facing each other within the threshold, they won't be selected. Has a range from +/- 0.999999. Greater or equal to 0 means the mesh normal is pointed in the direction user has it set to. The higher they set the threshold, the more the mesh needs to be facing in that direction. A value of 1 should mean the viewport and mesh are aligned, but was only working from the front perspective (numpad 1) and from nowhere else regardless of ortho. Max threshold of 0.999999 is functionally the same as having it at 1 except it works from any angle. Negative values can select unseen mesh.\n\nAll Verts setting saves performance without compromise, because Blender doesn't select unseen verts. They're dimensionless, and since there's only one position for them to be drawn in, they shouldn't be in the selection bitmap unless they're visible.\n\nFront Verts will select verts based on their normals,. Some of the verts at the edge of a mesh are excluded. Verts of Front Face will fix that, it selects verts if they're part of a face with a viewport facing normal. There's also rear facing counterparts to these, they do the opposite where they'll select stuff pointed away from the viewport. Not sure if they're useful but it's easy to include.\n\nThe settings for edges work the same as verts. Using edge normals will exclude things the user probably wants to select, and Edges of Front Face will correct that. Same goes for face settings, except Front Faces are what give accurate selection. Faces of Front Vert will select faces that have at least one vert with a viewport facing normal. This means it can select unseen faces, which is what I'm trying to avoid, but maybe it's useful for something.\n\nSometimes user will be able to see a face even though it has a rear-facing normal, and VFS won't select it. Usually this is because they are dealing with two triangles that have no business sharing the same quad, but that's going to happen from time to time, and they'll need a way to select them. Besides turning this feature off temporarily, triangulating or otherwise fixing the mesh, single-clicking, or rotating the camera, they can drop the VFS threshold into the negative. How negative they go depends on what they're willing to live with, and it gets worse the lower they go. I keep it at zero, because at least I have a chance of noticing things I didn't select. Hard to keep track of random selections that you can't see. It's not perfect, but it's predicable, and should work with most geometry.\n\n**Object Origin**\nAt 7:35 in the video above.\n#109373\n\nMy implementation of this feature is incomplete, but functional. Circle and lasso are forced to select objects by their origin, while box cannot do this. Put a checkbox in the Keymap so user can control this. Call it Select Object Origin. With my build box origin seems ok, but circle is a little off and lasso has enough problems with non-origin that I left it out. There's an addon that does this fine though from what I've been told. I looked at it but I couldn't figure out how to give object mode access to vert info, just kept getting errors so I left it at that for now. Addon is called [X-Ray Selection Tools](DaLdj)\n\n**Unsolved Mesh Select Issues**\nAt 8:32 in the video above\n\nIntersect doesn't work with Touch or Enclose face in X-Ray and Select Through. Don't know why, looked at it a few times, doesn't make sense to me. With my build it will fallback to a Center select instead. Figured it's better to do something close to what is expected rather than nothing.\n\nEnclose face works in near select, but it's hard to use if user can't see all the verts of a face. If there is a visible face, but some of it's verts that would otherwise be on screen are behind something else, the selection bitmap thinks they don't exist. This means that it also thinks that part of these faces are outside the selection area, even though they aren't, and they get excluded from selection. One thing user can try is avoiding the selection bitmap entirely. Turn on Select Through, and set Viewport Facing Select to work in X-Ray, Verts of Front Face, Edges of Front Face, and Front Faces. Threshold at zero is best in my opinion. Now they get a decent result, but have to deal with the baggage that comes with Select Through and VFS. They don't always get everything they can see, at least when encountering some weird faces that have triangles pointing in very different directions. Also, they're going to select like X-Ray so if there's something that is facing the viewport, but they don't have line of sight, they're going to select it without actually seeing it.\n\n**Drag Direction**\nAt 9:56 in the video above.\n#109726\n\nBlender let's you assign a direction to click-drag in the Keymap. There are 8 of them, which is nice, but it's confusing and inaccurate if all you need are 2. Provide some alternatives in Preferences->Input->Mouse. I'd like to put them at the top of the keymap in that preferences area, but I noticed how that thing will disappear if you load a keymap or use one other than the default. Didn't look into it yet. \n\nKeymap Drag Direction has 3 options. Eight, which is what Blender does, Left Right, and Up Down. The tradeoff for the new ones is that they're exclusive. If you use Left Right, the only Keymap items Blender will match with are Any, Left, and Right. Unless something has been manually set to a direction, there shouldn't be anything besides View Axis, the ones where you hold ALT and Middlemouse while dragging in the direction that corresponds to the view you want.\n\nWith Blender's way, try to set Box select to Extend when dragging left aka West, and Subtract when dragging right aka East. If user doesn't initiate a mouse drag within 45 degrees of left or right, they get a Tweak Event instead of what they expected. There's a way to make this work better using the keymap alone. They can set Extend to Any, and Subtract to East, Northeast, and Southeast. The Keymap item set to Any needs to be after the other 3 or they'll be undetectable. Not intuitive, and I didn't figure out this was possible until after making this feature.\n\nWith the new ways I made there's 3 operators that will set drag direction. If a Keymap item is undetectable, it will warn the user about it. Not ideal, but nothing bad will happen, it's just telling them that this Keymap item won't do anything because Blender can't see it anymore.\n\nDrag detection has some perpindicular bias. If the user is on the Left Right setting, and they drag up or down far enough before moving to the right, they're going to get the Left Keymap item instead of the Right Keymap item that they intended. If they're on Up Down, and move horizontally before going up, they would get the Down Keymap. With Blender's Eight way, assuming they set it like I described, the dominant Keymap item is the one that is set to the Any direction. The Left Right and Up down options are a lot more precise so it's hard for this to happen. The Eight way calculation rounds to the nearest int, so it treats every mouse drag within 45 degrees of a cardinal direction like it went straight vertical or horizontal. This problem can be mitigated by increasing drag theshold in Userprefs->Input->Mouse.\n\n**Selection Radius**\nAt 12:48 in the video above.\n#109729\n\nSingle-click an edge, vertex, or facedot and there's a pretty big area the user can grab it from. Faces in near select have zero radius, so the cursor needs to be right on top of them. Make this adjustable and consistent. Preferences->Editing->Miscellaneous-> Adjustable Click Select is where I put it, but that is not a good spot. It makes faces act the same as the others, and the user can change the size of the selection radius. Blender gives unselected mesh a slight bias, this can be turned off. Very minor detail that would not likely be noticed.\n\n**Conclusion**\n Nothing is really done all the way, but it is closing some gaps. Lot's of things can be moved, renamed, tweaked. That's what I'd like to do, and maybe some of it can make it into real Blender.\n\n", "Very slow interaction with Armature, if GPU Subdiv is enabled\nOperating system: Ubuntu 20.04\nGraphics card: Gefore MX230\n\nBroken: 3.3, 3.2.2\n\nwith the enabled GPU Subdivision, interactions with the armature are much slower than with the disabled\n\n[2022-10-23 13-29-00.mp4](2022-10-23_13-29-00.mp4)\n\nmove the bones with GPU Subdivision on and off\n[kira_lite.blend](kira_lite.blend)", "Show small preview image even in non-Thumbnail Display Modes\nAs mentioned in #89729 (Add toggle for Vertical and Horizontal Display Mode) we should support the Vertical and Horizontal List Display Modes as well. But rather than showing the data-block type icon there (which is rather useless), show the preview, which is much more important typically.\n\nThis may actually be nice for the regular File Browsing as well, but there it may be more important to have an icon to quickly differentiate the different file types.", "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", "Viewport display: in front should be listed under visibility as it also affects final render\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nUnder object properties, viewport display: in front affects both the visibility in the viewport and in the final render, and as such should probably be listed under visibility rather than viewport display.\n\n-", "Operator: Play Rendered Animation no frame_preview_start for images\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.83 (sub 11)\n\nTopbar >> Render >> View Animation \n`bpy.ops.render.play_rendered_anim()`\n\nWhen using the View Animation operator it runs as intended with videos, however if you're using images as your render output, and using a preview range,\nthe operator will output from the Render Frame Start, rather than the Preview Frame Start. \n\nSo, unless your preview range included the first scene frame, the player will fail to start. \n\n\n**Steps to Reproduce**\nStep 1:\nEnable Preview Range in the timeline (click clock next to the Start/End numbers)\nChange the Start Frame (this is currently the Preview Start, not the Render/Scene Start)\n\n```\n Step 2: Option 1:\n in python window (or text editor) run:\n print(bpy.context.scene.render.frame_path(preview=False)) # Outputs Render Range\n print(bpy.context.scene.render.frame_path(preview=True)) # Outputs Preview Range\n```\n\n```\n Step 2: Option 2:\n Render the animation (3D Viewport Header >> View >> Viewport Render Animation)\n Topbar >> Render >> View Animation \n```\n\n\nRepeat Step 2, twice. \nOnce with your Render Output format set to any video format (AVI / FFMpeg)\nOnce with your Render Output format set to any image format (PNG / BMP / JPEG / etc)\n\n\n**Details**\n`\\2.83\\scripts\\startup\\bl_operators\\screen_play_rendered_anim.py` `line #117`\n`file = rd.frame_path(frame=scene.frame_start, preview=scene.use_preview_range)`\n\nThe function `bpy.context.scene.render.frame_path()` isn't doing anything with the `preview` variable, when the output is an image, so it just always return `scene.frame_start`\n\n`\\blender\\makesrna\\intern\\rna_scene_api.c` >> ` void RNA_api_scene_render` >> `static void rna_SceneRender_get_frame_path`\n\nThis function does one check for movies and different one for images. \nif it's image, it doesn't use the `preview` bool variable, and just use the scene's frame\n\n", "5700 xt not working with HIP cycles\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.27.09.230330\n\nBroken: version: 3.6.2\n\nI am trying to render my donut, but I can only do so with CPU. Whenever I try to render with GPU compute HIP with my 5700 xt enabled, the screen freezes; it becomes unresponsive and I have to manually close the program. My hardware doesn´t seem to be the problem, afterburner is detecting everything and it seems fine. Drivers updated, latest Windows 11 version\n\n1. Hit render with cycles active, GPU compute and the 5700 xt activated in HIP/system/preferences tab.\n\n", "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "FaceMaps Phase 1: bone selection & bone display\nThe first phase of integrating the FaceMaps feature, is to make it work as an alternative way of displaying and selecting bones. \n\nThe user sets it up this way:\n\n\n - For each bone, we will have a display option called 'Face Map'. The user can enable it for all the bones he/she wants to use it\n - When enabled, it looks for Face Maps with the same name as the bone.\n\nThat's it. Users can then manipulate their rigs just like today, but bones will look as if you are selecting and manipulating the mesh itself.\n", "Click-and-Drag the Cursor with Snapping enabled and an Active Object selected missplaces the Cursor\nOperating system: Linux-5.2.9-125.current-x86_64-with-glibc2.9 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\nWorked: None so far\n\n\nDragging the cursor and snapping it to a Vertex while having the Target set to Active makes the cursor snap to a point in space that is directly related to where you start your *click-and-drag* instruction in reference to the selected object's origin. \n\n1) Change snapping to Vertex, Edge or Face\n2) Change snapping target to Active\n3) Set active tool to Cursor\n4) Activate snapping during transform\n5) Select default cube\n6) Drag Cursor over cube\n\n**Important notes**\n\n- If you deselect everything it works, but while there's an object selected the snapping won't work.\n\n- The problem also happens in Edit Mode, but only if there's an object selected in Object Mode. If you deselect everything in Object Mode and then go back to Edit Mode it works as intended.\n\n- As far as I can tell the _offset_ of the snapping is directly related to where you start your click-and-drag in regards to the Objects Origin.\n\n- There's a BlenderArtist Topic in which some have tested the behavior in Blender 2.81: 1177897\n\n- I recorded a video showing the problem: [blender_bug_report_complete.mkv](blender_bug_report_complete.mkv)\n\n- I also uploaded the blend file I used to record the video: [bug_report_cursor_snapping.blend](bug_report_cursor_snapping.blend)", "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)", "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" ]

[ "Bone selection malfunction in Pose mode with X-Ray + In Front display\nOperating system: Ubuntu 19.10\nGraphics card: GeForce GTX 460\n\nBroken: 2.83 (sub 0), branch: master, commit date: 2020-01-17 19:09, hash: 1f92e9903fb7, type: Release\nbuild date: 2020-01-18, 00:02:53\n\nWhen both X-Ray and Armature \"In Front¨ display are enabled in Pose mode, bones cannot be selected by Right clicking on them or by using Select Box. \nThey can only be selected with Select Circle or Select Lasso. \n\nDefault startup \n\n1. Add an Armature\n2. Enable X-Ray\n3. Switch to Pose mode\n4. Enable \"In Front\" in Object Data Properties > Viewport Display\n5. Disable X-Ray\n6. The bone cannot be selected\n(*) X-Ray button does not change visual state when switching X-Ray state, and it is still enabled when you exit Pose mode.\n\n*Another sequence*:\n\n2. Enable In Front in Armature \n3. Switch to Pose mode\n4. Enable X-Ray\n5. The bone cannot be selected\n\n*Pre-selecting a bone*:\n\n2. Enable In Front\n3. Switch to Pose mode\n4. Select the bone\n5. Enable X-Ray (The bone is still active and can be transformed)\n6. Deselect the bone with ALT A or click anywhere else but the bone (Notice Right clicking on the bone, which would normally keep it selected, deselects it now)\n7. The bone cannot be selected\n(*) Please also note when you exit Pose mode, X-Ray view has not been enabled.\n\nIf both X-ray and In-Front are selected before switching to Pose mode, the bones can be selected, but as soon as you disable X-ray they become unresponsive.\n\nThank you", "Unable to select bones in pose mode when 'Fade Geometry' used with 'In Front'\nOperating system: Kubuntu Linux 18.04-5.0.0-37-generic 64 Bits\nGraphics card: AMD Radeon R9 290 4.5.13581 Core Profile Context 19.50\n\nBroken: 2.82 (sub 7)\nWorked: 2.81\n\nWhen 'Fade Geometry' overlay is used (flag is set, any fade value) and Viewport Display -> 'In front' also checked for armature then selecting bones with mouse clicks stops working. You still can use 'Select all' and Circle Select, but not Box Select and mouse clicks.\n\nOpen attached .blend file. It has default cube and armature with two bones. You shouldn't be able to select them. Uncheck 'Fade Geometry' or 'In Front' and now you are able to select bones with mouse clicks.\n[test-select-bones.blend](test-select-bones.blend)\n\n" ]

[ "Line Art errors when rendering small details\nOperating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.0.1\nBroken: version: 3.1.0 Beta\nBroken: version: 3.2.0 Alpha\n\nWorked: version: 2.93.8\n\nLine art when rendering fine edge mark details now produces errors that were not present in 2.93.\n\n**Example of Error**\n{[F12864446](3.0_World_Space.png)}\n\n**Expected Results**\n{[F12864444](2.93_Screen_Space.png)}\n\n\nEXAMPLE BEND FILE: [Line Art Fine Detail Error.zip](Line_Art_Fine_Detail_Error.zip)\n1. Open Example File \n2. Ensure Line Art is enabled\n3. Render Image\n\n", "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", "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", "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", "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.", "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.4 Random Crashing Since GPU Replacement\nOperating System: Windows-10-10.0.19044-SP0\nGPU: NVIDIA GeForce RTX 3060/PCIe/SSE2 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0, branch: blender-v3.4-release\n\n**Short Description**\nI have replaced my RX580 with an RTX3060 earlier and ever since that replacement, I have been having constant crashes whenever I attempt to use Blender, do note that I've been in edit/object mode during these crashes as I'm working on a subd model, I have tried a handful of fixes such as upping TDR values but it didn't seem to fix the issue.\n\nRyzen 5 2600, RTX3060, 16gb RAM, no temperature exceeds 60 degrees Celsius and nothing is active besides Blender 3.4 along with addons I have installed.\n\nHere are the logs I get when I run Blender via the gpu debug cmd: \n\nEdit: I did try disabling UV Packmaster as per the error logs, but that didn't stop the crashing.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[gunflipped.crash.txt](gunflipped.crash.txt)", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "Crash Guide during render complete 2 December 9, 2022\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.4.0\n\nCrash Guide during render 2\n\nSame crash guide during render before and today.\nSee youtube: ZeCA2p5wISY\n\nHistory previous.\nT100691\n\n\n\n\n[Blender-2022-12-09-161546.ips](Blender-2022-12-09-161546.ips)\n\n[Horizontal Video.zip](Horizontal_Video.zip)", "Holdout material no export in PDF\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.57\n\nBroken: version: 2.93.0\nWorked: (newest version of Blender that worked as expected)[story bug.blend](story_bug.blend)\n\n\n\n", "Old todos (to be checked)\nNOTE: this is a direct dump of Install-OS (without cherrypicking the valid items)\n\n- [ ] Add code to detect drives to change (usb connected, disconnected)\n- [ ] RNA library needlessly rebuilds every time in visual studio.\n- [ ] Blender doesn't recognize .lnk shortcuts or hidden files.\n- [ ] Symbolic links are not supported #37619.\n- [ ] NTFS junctions are not supported #52080.", "Chromebook file manager fails to properly extract Blender's tar.xz archive\nOperating system: Debian bullseye \nLinux penguin 5.10.147-20159-g06a9a2b12b31 #1 SMP PREEMPT Thu Dec 15 19:14:41 PST 2022 x86_64 GNU/Linux\nGraphics card: Intel integrated\n\nblender-3.4.1-linux-x64\n\n./blender: error while loading shared libraries: libsycl.so.6: cannot open shared object file: No such file or directory\nsudo apt-cache search libsycl [produces nothing]\n\nexecute blender", "Can't bind shortcut Alt+Numbers 0-9\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\nKeyboard: UK ISO (tenlesskey) w/ UK Layout\n\nBroken: version: 2.93.4\nBroken: version: 3.0.0 Alpha\nWorked: None (tried 1.8, 2.28, 2.34, 2.58, 2.66, 2.79, 2.80, 2.82)\n\nUnable to use Alt modifier with Numbers 0-9\n\nTry to rebind something (e.g Hide Collections to Alt+Number key).\nThe binds will fail to execute.\n\n{[F10604609](210926_blender_10b48.png), size=full}\n\nBroken:\n• Alt+Numbers 0-9\n• Alt+Numpad Numbers 0-9\n• Using 'Left Alt' as a custom modifier key in the keymap plus Numbers 0-9\n\nWorks:\nAlt+F Keys 1-24 work (unfortunately Alt+F4 is hardcoded to exit blender.exe)\nAlt+Qwerty/Punctuation keys work.. just seems like its Alt+Numbers that fail\n\nThank you for your time and consideration :3", "Library Override broken for Snow character rig\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: 3.0 to 4.0\nWorked: never?\n\nI tried to use the Snow character, following the guidelines. But every time I use the Libary Override, the character's eyebrows and neck get stretched and distorted. When the bug does not happen at the time, when saving and reopening the file it appears\n\n- Link the CH-snow collection\n- Object -> Relations -> Make Library Override\n- Save file then reopen it\n", "Opening of a new/recent file interrupted with saving current file\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\n1. create new file, make changes\n2. try to open recent file\n3. agree to save current file with new name\nfile saved but new one not opened.\n\n[2021-04-24_07-58-40.mp4](2021-04-24_07-58-40.mp4)\n\n" ]

[ "Regression: Unwrap angle based fails with seams.\nOperating system: Linux-5.19.0-50-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 525.125.06\n\nBroken: version: 4.0.0 Alpha\nLikely broken by a35ad5899fca168e9457af98b7ff11a7c4000ac9\n\nIf you try to make an unwrap on the Monkey (it is only an example) blender gives you an error \"Unwrap failed to solve....\"\nConformal works fine, the problem is on Angled Based.\n\nOpen file [110729](https://projects.blender.orgattachment)\nPress U to unwrap\n\n" ]

[ "Crash on accessing Bone Driver in Python\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nAccessing Bone Driver via Python:\n\n```\nbpy.context.active_object.animation_data.drivers['pose.bones[\"Bone.001\"].bbone_curveinz']\n```\ncauses crash.\n\n[python.blend](python.blend)\n - Press enter in console.", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "bpy.props.IntProperty fails to register if given float values\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 496.76\n\nBroken: version: 3.1.0 Alpha\n\nWhen an addon tries to register an IntProperty, whilst not giving one of the numerical values an explicit int value, the property will return an error during registration.\n\n```\nprop = bpy.props.IntProperty(default=1.0) # prop is created okay\nbpy.types.Object.intprop = prop\nTypeError: integer argument expected, got float\nTraceback (most recent call last):\n File \"<blender_console>\", line 1, in <module>\nValueError: bpy_struct \"Object\" registration error: 'intprop' IntProperty could not register (see previous error)\n```\n", "inconsistancy in runing script console vs editor, pose mode bones transformations.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.2\n\nthere is difference when running script from blender editor vs blender python console \n\n\n1. the example suppose to place bones from one armature (B) on another (A) while in pose mode.\n\n2. when running the script in editor mode the result is unpredictable and you can click few times and get different results.\n\n3. when copying the whole script and run it in the blender console its seem to work just fine. \n\n4. keep up the great work.\n\nTest File:\n{[F10327076](bone_to_bone_test03.zip)}[tests02_no_try.zip](https://archive.blender.org/developer/F10325225/tests02_no_try.zip)", "bpy.ops.object.transform_apply no working after physics simulation\nOperating system: Windows 10 Pro\nGraphics card: 2x Nvidia 1080 GTX\n\nBroken: 2.8, b46245470f79, 2018-04-18\nWorked: 2.7x\n\nWhen running a rigid body simulation, it is not currently possible to apply transformation to freeze a specific frame. If you start scrubbing in the timeline, the object either goes back to original position or jumps to random position that was generated during the simulation.\n\n - add a plane and add a passive rigid body\n - add a suzanne and add an active rigid body\n - run the simulation\n - choose a frame\n - select the suzanne object\n - apply transformation/apply visual transformation\n # scrub in the timeline\n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "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'", "internal error: modal gizmo-map handler has invalid area\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\n\nWhen rendering to the Image Editor and toggling \"maximize area\" while rendering, an error is displayed in the console\n\n\n\n**Step to Reproduce**\n- open `test.blend`\n- make sure `Preferences` > `Interface` > `Editors` > `Temporary Editors` > `Render In` is set to `Image Editor`\n- render {key Ctrl F12}\n- Hit {key Ctrl + Space} when rendering\n\n```\ninternal error: modal gizmo-map handler has invalid area\n```\n\n[test.blend](test.blend)\n[userpref.blend](userpref.blend)", "PyAPI: template_modifiers doesn't work in the viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nThis was working outside the context of the Properties Editor prior to 9b099c8612 -- when it was still template_modifier(md).\n\nDisplaying the dafault modifier layout doesn't work in the viewport (in the sidebar or in a popup). template_modifiers() gives errors:\nPanel type 'MOD_PT_Array' not found.\nPanel type 'MOD_PT_Bevel' not found.\nPanel type 'MOD_PT_SimpleDeform' not found.\n... \n(interface_panel.c, line 292)\n\nBased on the attached file:\n1. Run the script in the text editor to create a panel in the sidebar called \"Modifiers\"\n2. Verify that the modifiers don't show up and there are errors in the console\n3. Click the \"Modifier Popup\" button\n4. Same thing should happen with the popup\n\n[template_modifiers_bug.blend](template_modifiers_bug.blend)\n", "input() raises error in python console\nWindows 7 64bits / ASUS EAH6670\n\nOfficial 2.70a 64bits\n\nThe input function doesnt work in the python console.\n\n```\nimport bpy\nfrom bpy import data as D\nfrom bpy import context as C\nfrom mathutils import *\nfrom math import *\n\n```\n - ~ PYTHON INTERACTIVE CONSOLE 3.3.0 (default, Nov 26 2012, 15:38:36) [MSC v.1500 64 bit (AMD64)]\n - ~ \n - ~ Command History: Up/Down Arrow\n - ~ Cursor: Left/Right Home/End\n - ~ Remove: Backspace/Delete\n - ~ Execute: Enter\n - ~ Autocomplete: Ctrl-Space\n - ~ Zoom: Ctrl +/-, Ctrl-Wheel\n - ~ Builtin Modules: bpy, bpy.data, bpy.ops, bpy.props, bpy.types, bpy.context, bpy.utils, bgl, blf, mathutils\n - ~ Convenience Imports: from mathutils import *; from math import *\n - ~ Convenience Variables: C = bpy.context, D = bpy.data\n - ~ \n```\ninput()\n```\n - ! Traceback (most recent call last):\n - ! File \"<blender_console>\", line 1, in <module>\n - ! RuntimeError: input(): lost sys.stdin\n - ! \n\n\n\n\nIn python console, type\n\n```\ninput()\n```\n\n", "bake hair dynamics issues\nOperating system: wind 10\nGraphics card: gtx 1070\n\nBroken: blender-2.80-79f67acccb36-win64\nWorked: idk\n\nunable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.\n\n", "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", "Bake fluid domain simulation crashes when using a depsgraph poll\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.92.0\n\nWhen using bpy.context.evaluated_depsgraph_get() in a poll and then baking a fluid blender crashes\n\n1. use the provided file with a fluid prepared to bake data or create a fluid domain and a fluid source\n[mantaflow.blend](mantaflow.blend)\n\n2. make sure the chace type is set to modular\n\n\n3. run the simple operator script (should come with the blend file)\n[operator_simple.py](operator_simple.py)\n\n4. press the bake Data in the Fluid domain settings and blender should crash\n\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)", "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" ]

[ "Overriding context in rigidbody operations [override not passed along in startup/bl_operators that themselves call bpy.ops]\nOperating system: Ubuntu 16.04 \nGraphics card: MSI 1080Ti\n\nBroken: 2019-03-26, 337eb8c1de4c\n\nContext override information in bpy.ops.rigidbody.bake_to_keyframes() not shared with bpy.ops.anim.keyframe_insert() causing poll() error.\n\n- Open default file\n- Give cube active rigid body\n- In the python editor:\n```\nobj = bpy.data.object['Cube']\nobj.select_set(True)\nbpy.context.view_layer.objects.active = obj\n\nfor area in bpy.context.window.screen.areas:\n if area.type == 'VIEW_3D':\n for region in area.regions:\n if region.type == 'WINDOW':\n override = bpy.context.copy()\n override['area'] = area\n override['region'] = region\n override['scene'] = bpy.context.scene\n override['point_cache'] = bpy.context.scene.rigidbody_world.point_cache\n bpy.ops.rigidbody.bake_to_keyframes(override)\n```\n\nReturns:\n```\nRuntimeError: Operator bpy.ops.anim.keyframe_insert.poll() failed, context is incorrect\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", "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", "VSE snapping defaults\nSnapping status is stored in tool settings, but it is independent of global scene snapping status. Further snapping parameters are stored in `SequencerToolSettings`, since it is intended to be best suited for VSE workflow. \nCurrent snapping implementation is important also for new transform mode outlined in [D11805](D11805), which is still not finished tohugh. this is also VSE/NLE specific mode.\n\nSnapping was enabled by default because visually aids in strip positioning, while still allowing usual workflow. I have no strong opinion about default status here.\nScrubbing snapping - [D11745](D11745) should be subset of VSE snapping settings, and off by default, because it complicates usual workflow in that user can't smoothly scrub through entire timeline.\n", "Sample texture color dialog isn't dismissed after use\nOperating system: W10\nGraphics card: GTX 970\n\n2.82a\n\nAfter use of the pipette in the Image Texture Editor, the 'F9' dialog box is not dismissed until an UNDO operation is performed.\n\n\nSample file included; Launch file. Switch to Texture Paint. In the Texture Image Editor, invoke the sample function with the S hotkey. Observe the dialog.[Sample Dialog Dismiss.blend](Sample_Dialog_Dismiss.blend)", "Improve communication of auto-save behavior by adding dialog box to \"Load Factory Preferences/Settings\"\n*Adding this task based on a discussion about improving usability to auto-save preferences when loading factory settings.*\n\nCurrently when loading factory settings, the preferences don't auto-save, even though loading the factory settings enables the auto-save option.\n\nThe rationale here is that we want to allow users to temporarily load factory settings without it overwriting their own preferences.\n\nIn this case explicitly saving needs to be done to overwrite their preferences.\n\nThis task is not to re-open the design discussion, for some context on the topic see other discussions.\n\nFor reference, discussion on this topic:\n- [D4863](D4863) - Preferences UI patch for Save/Revert/Reset\n- [D5236](D5236) - Remove option for disabling the override when factory settings are loaded\n- #66675 - Tooltip urgently needed for Preferences editor button to avoid user data loss with factory-defaults.\n- 4a5e046c92 UI: remove button to enable auto-save after load factory preferences\n\n----\n\nBased on discussion with @JulienKaspar, @dr.sybren & @WilliamReynish - we agree the current logic isn't well communicated to the user,\nsince loading factory settings puts Blender in a state where auto-save is checked but ignored.\n\nThis could be mitigated using a dialog which lets the user know what happens when loading factory settings.\n\nSuggested text:\n\n> Loading factory preferences won't automatically save your preferences on exit.\n> To overwrite your current preferences you must manually save the preferences. \n\n\n\n", "Crash when rendering animations (GPU Subdivision ON, OFF is fine)\nSystem Information\nOperating system: WIndows 11 22H2\nGraphics card: Nvidia GeForce RTX 4080\n\nBlender Version\nBroken: 3.4.1, 3.5, 3.6\n\nForce closes when rendering animation after a number of frames and when opening larger blend files. Happens with all files. All drivers up to date and tested memory with no issues. Worked without issue for 6 months, crashing started 1 week ago.\n\nRendering animation with GPU Subdivision unchecked did not trigger a crash", "File Browser: Can't Select/Delete Favorites Bookmark When File Path Is Missing\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCan't select/delete an existing Favorites Bookmark in the Blender File Browser if the path no longer exists on your OS. You have to recreate the path to enable select/delete again.\n\n1. Create a Favorites Bookmark in the Blender File Browser that links to a folder on your OS.\n2. Close the Blender File Browser.\n3. Delete the folder in your OS the Bookmark links to.\n4. Open the Blender File Browser.\n5. The Bookmark is now gray and can't be selected/deleted. (Hovering over the link does show the original path.)\nTo reverse this:\n1. Close the Blender File Browser.\n2. Recreate the original path in your OS the bookmark originally linked to (see 5 above).\n3. Open the Blender File Browser.\n4. The Bookmark can now be selected/deleted.\n\nNOTE: A limited workaround was added some years ago (the 'Cleanup' option that will remove all invalid entries)", "Modifying keymap won't tag prefs dirty\nWindows 7 Professional 64-bit service pack 1\nIntel Core i7-2600\n8GB RAM\nNVIDIA GTX 1060 6GB\n\nBroken: blender-2.80.0-git.aa003c73245f-windows64\n\n\"Save Preferences\" button, shown when \"Auto-Save Preferences\" is turned off, stays unavailable after modifying keymap.\n\n1. Make sure \"Auto-Save Preference\" is turned off. If it isn't, turn off this and press \"Save Preferences\" button.\n2. Modify keymap, editing the settings used to activate an operator (example: search for `Clear Rotation` operator, changing the `Clear Delta` option will not tag prefs dirty).", "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled", "Cannot keyframe particle count property\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Quadro 2000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 377.83\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\n clicking keyframe button next to particle count responds with *Failed to resolve path to property, try manually specifying this using a Keying Set instead*\nsee screenshot attached\n\nClick on animate property next to particle count\n", "Drivers of sub-ID properties do not get removed along with the sub-ID\nBy \"Sub-ID\" I mean things like Modifiers, Constraints (bone & object), custom properties, shape keys, bones, VSE strips, etc. Not sure how to get a complete list of these types of things.\n\nWhen one of these things, such as a modifier, is removed, drivers on its driven properties are not removed. This makes it easy to leave behind broken drivers that now target nothing. These can be cleared up in the Driver Editor UI fairly easily, but the fact that we must do so is annoying. Experienced users end up learning that you can't just remove a modifier or constraint without removing its drivers first - Just to save you a trip to the Driver Editor.\n\nForgetfulness in this habit results in console warnings, which in a production environment trickle down from assets to shot files, and contribute to the users' sense of \"console warnings aren't important, I will ignore them\".\n\nI always thought this was a known issue but @Sergey told me it's fixable and that I should make a report. Here ya go! \n\nThis would be a really, really welcome improvement for the studio and probably the whole world.\n\n", "No Exit Temp file created when accidentally exiting steam.\nDon't think this is related in any way but i have\n8GB ram\n850m\n1tb hdd\ni7 4770\nMSI GE70 apache\n\nblender 2.77\n\nCreate a scene in blender exit steam and no exit file created, exit blender and exit file created.\n\nCreate a scene in blender exit steam and no exit file created, exit blender and exit file created.\n", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "How to keep asset viewer options and the search field in view?\n\n\nIt's annoying that animators have to scroll up all the time to access these (or down for the search field).", "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" ]

[ "User Perferenses Crash\nWindows 7 Ultimate Edition, Mobile Intel(R) 965 Express Chipset Family\n\nBlender work\n\n\nWhen I open the User preferences, then Blender crashes. And this in all Blender versions\n", "opening user preferences crashes blender\n%%%--- Operating System, Graphics card ---\nWindows 7 Home premium, Intel (im sure this is the problem)\n\n - Blender version with error, and version that worked ---\n2.63, 2.64 \n\n - Short description of error ---\nwhen I go to file-> user preferences and click, blender stops responding. I am well aware that there is a problem with intel, and it appears that I need to use\nblender-softwaregl script, and furthermore I have seen the download directory. I still cannot find this script though. was it included in the Blender download and in one of the created files for installation? Was it somewhere on the official download directory page that I missed?\n\n - note ---\nmany others have had this error. Some said that switching to an Aero theme would work, but it did not for me.\nit is a problem that I have read all about, and seen many issues which relate to it, but I mearly cannot find the script that I need to run.\n\nI would greatly appreciate any help I could get with this issue. \n%%%", "Blender 2.69 crashes if you \"File / User Preferences\".\nWindows 7 Home Premium, (6.1) [Build: 7601]\nAcer Aspire 5732Z with the latest and greatest (2009) drivers from both Acer (manufacturer) and Intel (chipset).\n( But I've seen this other Windows 7 machines I've tried it on. The laptop is my main machine. )\n( PS: \"Help / System Info\" appears to save to a file, but that file can't be found on my system anywhere. Hmm. )\n\nBroken: 2.69.0 r60995\n( invoked via PortableApps 11.2 )\n\nBlender crashes if I try to enter \"User Preferences\" via the \"File\" menu, but not from other routes.\n\n**Exact steps for others to *reproduce* the error**\n- Start Blender (get past the splash screen)\n- click the \"File\" menu in the main toolbar\n- click the \"User Preferences\" command\n- Crash! Bang! Boom!\n\n**Exact steps for others to *avoid* the error**\n- Start Blender\n- click the \"Editor Type\" button in the 3D view area toolbar\n- click the \"User Preferences\" command\n- everything is copacetic.\n\nI realize this crash has been reported many times before, and eventually closed as \"it is in their driver, not in our blender\", but if there is one code path in Blender that triggers the crash and another code path that does not trigger the crash, then there _is_ a blender bug that _should_ be addressed.\n\n- Jesse\n", "User Preferences Crash\nDeveloper note: *this is a known bug in Intel drivers, merge duplicate reports here.*\n\n----\n\nWin 7 64- Intel HD Graphics\n\nBroken: 2.70a f93bc76\n\n\nWhen selecting User Preferences, either by mouse or by keyboard, the program closes. \n\nFile>User Preferences or CTRL+ALT+U\n", "Blender crash wen getting out of User Prefrences\ni5 4690k\nGTX 980\n8 GB RAM\n\nWindows 8.1\n\nBroken: 2.72b\nWorked: 2.7\n\n\nWhen I go into the user prefrences, and then close the window, blender crashes.\n\n>open blender\n>open User Prefrences\n>close User Prefrences\n>everything dies\n", "User Preferences ( BUG )\n - System Information --\n\nOperating System - 32-Bit\nGraphics Card - None\nManufacturer - TOSHIBA\nComputer Edition - Windows 7 Home Premium\nComputer SP - Service Pack 1\n\n - Blender Version --\n\nVersion - 2.72b\nDate Release - 2014-10-21 11:38\nHash - 9e963ae\n\n - Bug Description --\n\nBug - User Preference Crash\nNotes - When ever i attempt to open user preferences under file it closes the program. this type of bug is bad for me because i am a user of blender without a mouse so its a must to make hot keys to maneuver and observe my model is my case. Please help.\n\n - Re-Create The Error --\n\nStep 1 - Open Blender ( v.2.72b )\nStep 2 - Go To File\nStep 3 - Select User Preferences\nComment - In my case Blender closes every time i attempt to open user preferences.\n", "Blender crash when trying to open user preferences\nOperating system and graphics card\nWin 7 premium\nIntel family 4 onboard\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\nLatest\nClicked on user preferences and crashed to desktop.\nSome say it is a problem with Intel graphics. Latest update installed.\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Outliner displays non existing Screens.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.3 26.20.13001.18009\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nOutliner displays non existing Screens.\n\nThey exist in default blender workspace, however opening any editor in separate window with Shift and closing that window will create same thing, they wont be removed after saving and reopening file either.\n\n\n", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Operators for visibility on active face set missing from menus\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 3.0.0 Alpha\nWorked: Never\n\nThe default hotkey to show or hide the active face set does not appear in the menus.\n\n\n- Open Blender\n- Switch to Sculpt Mode\n- Use the Draw Face Set brush to create some face sets\n- Use the shortcut `H` and `Shift H` to control the visibility of the active face set\n- Search for the mneu entires of these shortcuts", "Gradients not working on Grease pencil masks\n\nOperating system: windows 10\nGraphics card: GEForce RTX 2080 super\n\n**Blender Version** 2.9\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nGradient layers not working properly with Grease Pencil if you open the example file 5c30cf5f637c8d7750c8aa6c you will see that applying the mask to the gradient layer does not work as in the preview from the old version of blender, the layer is not \"multiplying\" to give a sense of shadow on the lower layers of Grease pencil it just looks like a dirty overlay, also radial gradients do not work or are not visible.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Eyedropper picker Afected by retopology overlay\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: \n\nBroken: version: 4.0.0 Alpha\n\n\nUsing the Eyedropper Data-Block wouldn't pick visible objects if edit mode and retopology overlay are active\n\n1. Enter edit mode with the default cube.\n2. Activate retopology overlay\n3. Enter in the view tab in the n-panel\n4. Use the Eyedropper Data-Block and you won't be able to pick the object, only if you are at the origin of the object.\n\n", "Retopology Overlay Color Location\nA user noted that the overlay can be difficult to see when using random object colors: 15\n\nOne solution would be to move the color from the theme to the workspace, and expose it in the overlays popover.\nI think that just exposing the color isn't enough, because editing a preference outside of the preferences window does not autosave.\nMeaning that if you change the color in the popover, save your project, and restart Blender, the color would be back to default.", " LineArt: (Collection) Issue for Cameras in Orthographic View\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nChecked in Blender version 3.4.0 Apha, commit date: 2022-10-08 02:26 - same issue\n\nFor orthographic Camera without any shifts - Line art modifier (for a Collection) showing lines for objects behind other objects - which otherwise should not be visible. And some lines are not visible which should be.\nHappens with contours option in the Line Art modifier. Slight rotation on z axis solves the issue.\n\nNoticed issue with some specific frames on my complete blend file.\n\nOpen attached blend file and go to front orthographic view.\n\n[BugReport01.blend](BugReport01.blend)\n\n", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "The viewport grid is visible over the curves hair \nOperating system: Linux-5.15.14-1-lts-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46\n\nBroken: version: 3.3.0 Beta\n\nThe viewport grid is visible over the curves hair with cycles render engine.\n\nWith cycles > Press render preview on the viewport.\n[grid_cycles_and_hair_bug.blend](grid_cycles_and_hair_bug.blend)\n\n{[F13429852](image.png) size=full}", "Missing UV Islands / Image Editor / Some generative modifiers (bevel, skin, triangulate, wireframe)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro M2200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIf geometry has the Bevel Modifier applied and the Realtime Display is on, the UV islands do no display in the Image Editor.\nIf you turn off the Realtime display (Display in Viewport) and then adjust the view in the Image Editor, the UV Islands will appear.\nIf you turn On the Realtime display and then adjust the view in the Image Editor, the UV Islands will vanish.\nYou can still paint in the Texture paint on the geometry and it will appear in the Image Editor.\n\nCreate a Cube\nAssign a Bevel Modifier - turn Realtime display ON (for me it is on by default)\nSet interface to Texture Paint mode.\nThere will by no UV Islands displayed in the Image editor\n\n[UV_Island_Bevel.blend](UV_Island_Bevel.blend)\n\n\n\n", "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", "HDRI Preview Spheres appear in surface reflections\n\n\nBroken: version: 2.82 (sub 7)\nMaster\n\nWhen using material shading and overlays in the viewport, the gizmo at the bottom-left corner (sphere displaying the environment map used for preview) is reflected by shiny surfaces in the 3D world, despite technically being a part of the UI. Using the icon to show / hide overlays affects this, the reflection also disappears when overlays are hidden.\n\nShould work in any setup, if there are issues replicating this let me know and I'll extract the relevant part from my project's blend file. Just add a plane, lower its material roughness so it's shiny, move the view upward so the overlays appear under it, and you should see the strange reflection.\n\n\n\n[HDRI_reflected_in_viewport.blend](HDRI_reflected_in_viewport.blend)", "Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.0\nWorked: --\n\nLow resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to \"closest\" in the material shader.\n\nfeature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.\n\nplace object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. \n\ntextures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from \"linear\"(or whichever is set to default) to \"closest\"\n\nWe have 4 materials each having individual Image Texture nodes (but all using the same image).\n\nIf you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.\n\n", "Geometry 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.", "Objects with \"In Front\" don't appear when overlays are reenabled until viewport update\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBut works on:\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.91.2\n\nMight be the same as #102199 (Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)) (which was bisected down to 0f95f51361)\n\nWhen an object (specific ones) is set to be displayed in front of everything else, it will not come back immediately when reenabling the overlays. This happens only in solid shading mode as far as I can tell.\n\nThe objects affected by this are first off all objects which have some kind of lines, so camera, lights, the wireframes of meshes, outlines of reference images, empties, ...\nThen there is also the armature which is special in the way that it is rendered solid, but it also vanishes just like the lines.\n\n1. Add an armature\n2. set it to In Front in Armature > Viewport Display\n3. toggle the viewport overlays on and off (that button next to x-ray)\n4. if your rendering was set to solid shading, the armature should be gone now\n5. rotate the view, the armature will reappear\n6. you can do the same with the default camera and light and on the cube if wireframes are enabled (globally or locally on the cube) \n\n" ]

[ "Orthograpic 3dview clipping messed up in recent builds.\nWindows 10 64-bit, Nvidia 1060\n\nCurrent 2.80, not sure how long it has been broken.\n\nView clipping messed up in Orthographic mode. Grid not visible, scene clipped.\n\n\nStart Blender with the default scene.\nHit numpad f5 to enter orthographic mode. Grid disappears, cube gets clipped in half.\nHit N, change Near Clip to 100m and the grid and the rest of the cube shows up.\nHit numpad f5 to leave orthographic mode and everything disappears due to the now proper interpretation of the near-clip value.\n\n\n", "Unusual camera clipping behavior in orthographic view\nOperating system: Windows 10 Pro\nGraphics card: GTX 1080 Ti\n\nBroken: 2.80, 319b9d6501f2, 2019-02-17\n\nIn orthographic view, all near objects are clipped by the camera. The background grid also fades out oddly. Changing the Clipping Start value has the opposite of expected result. The attached gif demonstrates this behavior.\n\n\n\n1. Open Blender.\n2. Switch to orthographic view.", "Clip Start value in orthographic view\nOperating system: Windows 10, version 1809\nGraphics card: GTX 1060 6GB, version 418.81\n\nBroken: 2.80, 0d86259fc8a3, blender2.7, 2019-02-16 14:45\n\nClip Start value is changing both perspective and orthographic view.\n\nDefault start up:\n1. Create UV Sphere\n2. Enter in any orthographic view\n3. Play with Clip Start value\n\n" ]

[ "Visual geometry to Mesh does not duplicate a linked object\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.2.0 Alpha\n\nWhen applied to a linked object, Visual geometry to Mesh does it on the shared mesh.\n\nApply the subdiv modifier to the original cube. Link copy it. Use Visual geometry to Mesh on the linked object. Now select the original object and go into edit mode. You should see that the the subdiv modifier has been applied.\n\nThere is also a side issue to this. If you put a Decimate modifier (something visible like planar 20 degrees) on the original object, selected the linked one and go into edit mode, you'll see that in the viewport the modifiers on the original object don't show their effect.", "Cloth physics cache gets reset by changing object materials\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.83 (sub 11)\nWorked: unknown\n\nWhen using a cloth physics simulation, if you add or remove a material from an object, the cloth system cache is reset (\"cache is outdated\"). I don't think the material affects the cloth physics in any way (as it seems you can change any parameter within the material without the cache resetting), and therefore this should probably not happen. Please correct me if I am wrong and the material does affect the physics somehow.\n\nIn the default scene, enable cloth physics for the cube. Let the playback run for a few frames, building up the cache. Add a material to the cube; now the cache gets reset.\n\n", "Fade Inactive Geometry: Objects with the same object data are faded\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 3.0.0 Alpha\n\nThe \"Fade Inactive\" Geometry\" overlay is supposed to fade out any object that is not affected by the currently active object in any mode that is not object mode.\nBut if any other object has the same object data linked (same geometry) it will be faded out anyway.\n\n In this example the quad-sphere in the center is active in edit mode. The one to the right has the same linked object data, which is why it also shows the edit mode overlays as it is the same geometry.\nBut since it is another object it is greyed out.\n\nThis is related to #87704 since the overlay seems to prioritise objects that are in the same mode instead of objects that share the same geometry.\n\n- Duplicate an object multiple times to have more than 2\n- Duplicate one of them with Alt + D to have their object data linked\n- Enter Edit Mode on one of those objects\n\n", "Geometry Nodes: Support materials in simulation state.\nCurrently, the simulation state in geometry nodes cannot contain materials. The main reason is that those separate IDs which are not serialized as part of simulation baking. Ideally, baking materials would just work, at least in the most common circumstances.\n\nWhile this task is about materials, the same thoughts also apply to other referenced IDs like object/collection instances.\n\nThere are two main possible solutions:\n1. Serialize materials as part of the simulation state.\n2. Only store a reference to the material in the simulation state.\n\n### 1. Serializing Materials\n\nSerializing materials has the benefit that it could just work. We'd have to store all the materials for every geometry in the simulation state in cached frame. Though, it's possible to deduplicate this to some degree of course. Serializing materials would also involve serializing the node graph and potentially even more referenced data like images. At some point we most likely want things to stay referenced, so the problem is just moved to a different place. Another problem is that the materials are essentially recreated on every frame. Blender does not really have the ability to work with materials that are not in `Main` currently.\n\n### 2. Storing References\n\nStoring a reference to the material mainly means storing a material name and an optional library name in the simulation state. Then, when loading the simulation state, the materials available in the .blend file are mapped to the loaded geometry. Conceptually, this is also very straight forward. Materials can still be edited like they always have been. A potential problem is that if materials are renamed or removed, they can not be linked correctly anymore. However, that is somewhat expected with linking already. While this approach is easy design wise, there are some technical difficulties: The main problem is that we only know which materials are used by the baked data, once the data is loaded. And, to make matters more difficult, we might only know which baked data to load once depsgraph evaluation has started. That can happen when e.g. the file path to the data on disk is dynamically build/choosen during evaluation (this is not supported right now, but likely will be at some point).\n\nThe problem with knowing which materials will be used by the geometry is that materials are part of the dependency graph. As such, all materials we wish to use for rendering have to be added to the dependency graph *before* evaluation starts. As of right now, it's not possible to lazily add materials to the depsgraph once it becomes known that it is required.\n\nThere are a couple different possible solutions with different trade-offs:\n* A. Always add all materials to the depsgraph. This would be a simple solution, but it's obviously not scalable. Even less so if we wish to use the same solution for other kinds of referenced data like objects.\n* B. Only support linking baked data with materials that are referenced by material slots on the object or original geometry. This means that if the simulation state happens to contain materials used by e.g. other imported objects, those will not be linked correctly.\n* C. Detect all materials \"reachable\" from an object and always add those to the depsgraph. This might have noticeable overhead when potentially large parts of `Main` have to by scanned by many objects. It also wouldn't work in all cases. For example, if the simulation has been baked, and then the .blend file changes in ways that the material is not reachable from the object anymore. Then the material would not be linked correctly.\n* D. Store a name-to-material mapping on the modifier. This mapping could be created/updated automatically when baking or at other points in time. Only materials in this mapping can be linked when loading simulation state. If the simulation state contains a material name that is not in the list, we could show a warning and automatically add it to the list with the press of a button in many cases. With this approach, the user also has the ability to replace a material after baking easily. The mapping could also have per simulation zone overrides for more control.\n\n-----\n\nCurrently, my preferred solution is referencing the materials by name in the simulation state and use option D to do the linking at evaluation time.\n\n", "Subdivision modifier breaking custom normals.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.6.0 Core Profile Context 23.7.2.230718\n\nBroken: version: 4.0.0 Alpha (Also tested in v3.5.0 & v3.6.1)\nWorked: N/A\n\nIdentical normals are slightly messed up when a subdivision surface modifier is enabled, breaking cell shaders.\n\n1. Download the attached .blend file\n2. Change Viewport Shading to \"Rendered\"\n3. Enable/Disable the subdivision surface modifier.\n4. You might need to rotate the light slightly on the x-axis.\n\n\nSome notes:\n- All mesh normals were copied and pasted via \"Mesh/Normals/Copy Vector\" and \"Mesh/Normals/Paste Vector\".\n- \"Subdivision modifier/Use Custom Normals\" property is enabled.\n- Changing \"Render/Performance/High Quality Normals\" or \"Subdivision modifier/Use Limit Surface\" changes alters where the issues appear on Suzanne. (Sphere is unaffected.)\n- Issue doesn't occur on flat meshes.\n- Even after applying the modifier, repasting normals still leaves some artifacts.", "Solidify (Complex, Constraints) - very rare glitch\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.1\nWorked: 3.1.2\n\nbehavior changed in c2e8e68b6517b91eb14270707d7182c1727861c4\n\nSolidify modifier creates a weird glitch at a specific vertex.\n\nI have a model with about 40000 verticies that I wanted to solidify. Everything works fine, except the surroundings of a single vertex. The topology does not seem any particular there. The model is made out of triangles, but the glitch also appears if I convert it to quads. I copied the vertex and the surrounding faces to a sperarate blender file and recorded how the glitch appears depending on moving one of the verticies:\n\n(the glitch looks exactly the same when the vertex is part of the larger object)\n\nSolidify Modifier Settings:\nMode: Complex\nThickness Mode: Constraints\n(other settings does not affect the glitch)\n\n", "Multi-Object-Mode: EditMesh Tools\nNote, while these follow menus, duplicates have been removed.\n\n## Remaining\n\n- MESH_OT_select_similar_region ([D3672](D3672))\n- MESH_OT_knife_project (leave aside for now, too complex - see [D3637](D3637))\n- MESH_OT_knife_tool (leave aside for now, too complex - see [D3637](D3637))\n\n\n## Mesh Menu:\n\n- ~~MESH_OT_duplicate_move~~ 1ade071052\n- ~~MESH_OT_extrude_edges_indiv~~ d8f70a26fd\n- ~~MESH_OT_extrude_faces_indiv~~ 07774d4860\n- ~~MESH_OT_extrude_verts_indiv~~ 7c415e6fd7\n- ~~MESH_OT_extrude_edges_move~~ 1d7bdbd273\n- ~~MESH_OT_extrude_vertices_move~~ 1d7bdbd273\n- ~~MESH_OT_delete_loose~~ bfc9d426bb\n- ~~MESH_OT_decimate~~ 5b45d32f3a\n- ~~MESH_OT_dissolve_degenerate~~ (initial comsmit) bfc9d426bb\n- ~~MESH_OT_dissolve_limited~~ 09e14cb5bc\n- ~~MESH_OT_face_make_planar~~ 0e5a4f927a\n- ~~MESH_OT_vert_connect_nonplanar~~ b942106c73\n- ~~MESH_OT_vert_connect_concave~~4043e4b820\n- ~~MESH_OT_fill_holes~~ 69b95b45f4\n- ~~MESH_OT_symmetrize~~ 03a916e5b5\n- ~~MESH_OT_symmetry_snap~~ 7f9768cb80\n- ~~MESH_OT_bisect~~ f9eb2f29fe\n- ~~MESH_OT_sort_elements~~ ffb424c85f\n\n## Snap Menu:\n\n\n- ~~VIEW3D_OT_snap_selected_to_grid~~ 016ba0f38b\n- ~~VIEW3D_OT_snap_selected_to_cursor~~ ec3357e03a\n- ~~VIEW3D_OT_snap_selected_to_active~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_selected~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_center~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_grid~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_active~~ (no change required)\n\n\n## Vertex Menu:\n\n- ~~MESH_OT_merge~~ b73c7381cc\n- ~~MESH_OT_remove_doubles~~ 22b2bab702\n- ~~MESH_OT_rip~~ 9d0d7c375e\n- ~~MESH_OT_rip_edge~~ 6539c1fc41\n- ~~MESH_OT_split~~ fc8d903000\n- ~~MESH_OT_separate~~ 5e915baec4\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_vertices_smooth~~ d915aa57f8\n- ~~MESH_OT_vertices_smooth_laplacian~~ 1f30232aa7\n- ~~MESH_OT_blend_from_shape~~ 6ae09dfcad\n- ~~OBJECT_OT_vertex_group_smooth~~ 3dee8b4a12\n- ~~MESH_OT_shape_propagate_to_all~~ 3a43528274\n\n## Edge Menu:\n\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_subdivide~~ (initial patch)\n- ~~MESH_OT_subdivide_edgering~~ 853e55b043\n- ~~MESH_OT_unsubdivide~~ e245f7c09c\n- ~~TRANSFORM_OT_edge_crease~~ (initial patch)\n- ~~MESH_OT_mark_seam~~ 61f0608b4a\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_edge_rotate~~ 66ffbf9b7d\n- ~~MESH_OT_edge_split~~ 207b549d40\n- ~~MESH_OT_bridge_edge_loops~~ eb2226dde2\n- ~~TRANSFORM_OT_edge_slide~~ (wrapper to other operator, working)\n- ~~MESH_OT_loop_multi_select~~ df49155cfb\n- ~~MESH_OT_loop_to_region~~ 8b41999ea0\n- ~~MESH_OT_region_to_loop~~ 56d65719b3\n\n\n## Face Menu:\n\n- ~~MESH_OT_flip_normals~~ 4704f2687a\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_fill~~ b726ff4fc4\n- ~~MESH_OT_beautify_fill~~ e42b8c32ab\n- ~~MESH_OT_inset~~ 570455fb83\n- ~~MESH_OT_bevel~~ d9e04cb594\n- ~~MESH_OT_solidify~~ f309c34cfe\n- ~~MESH_OT_intersect~~ dffd37877d\n- ~~MESH_OT_intersect_boolean~~ 46aec45b2a\n- ~~MESH_OT_wireframe~~ a0a78f6da4\n- ~~MESH_OT_poke~~ 3a9669bfff\n- ~~MESH_OT_quads_convert_to_tris~~ (initial patch bfc9d426bb\n- ~~MESH_OT_tris_convert_to_quads~~ (initial patch bfc9d426bb\n- ~~MESH_OT_face_split_by_edges~~ b6a822d726\n- ~~MESH_OT_faces_shade_smooth~~ e4c4e8566f\n- ~~MESH_OT_faces_shade_flat~~ 9fc0c0c3de\n- ~~MESH_OT_uvs_reverse~~ 63951bc987\n- ~~MESH_OT_uvs_rotate~~ faaffc4011\n- ~~MESH_OT_colors_rotate~~ 42c5c20e54\n- ~~MESH_OT_colors_reverse~~ 753be0a2a5\n\n## Mesh Toolbar: (should be added to menu)\n\n- ~~MESH_OT_loopcut~~ e87dd9aa00\n- ~~MESH_OT_convex_hull~~ e1cee0ac71\n- ~~MESH_OT_delete~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_delete_edgeloop~~ 49be803ad6\n- ~~MESH_OT_dissolve_edges~~ 7f5c469716\n- ~~MESH_OT_dissolve_faces~~ 848d9cda0e\n- ~~MESH_OT_dissolve_mode~~ (wrapper of vert/edge/face dissolve)\n- ~~MESH_OT_dissolve_verts~~ 5f59a8bb11\n- ~~MESH_OT_drop_named_image~~ b4d23818c8\n- ~~MESH_OT_dupli_extrude_cursor~~ 68a719f1ea\n- ~~MESH_OT_duplicate~~ 1ade071052\n- ~~MESH_OT_edge_collapse~~ 2349b9777a\n- ~~MESH_OT_edgering_select~~ 7fa77cd31d\n- ~~MESH_OT_edges_select_sharp~~ dd93c80747\n- ~~MESH_OT_extrude_region~~ 1d7bdbd273\n- ~~MESH_OT_extrude_repeat~~ 9a125ca5fe\n- ~~MESH_OT_faces_select_linked_flat~~ 1bb9ccf887\n- ~~MESH_OT_fill_grid~~ 1cbe3b6e03\n- ~~MESH_OT_hide~~ 5d8937e8ba\n- ~~MESH_OT_loop_select~~ 7fa77cd31d\n- ~~MESH_OT_normals_make_consistent~~ 266638d783\n- ~~MESH_OT_offset_edge_loops~~ efd843b51c\n- ~~MESH_OT_reveal~~ f4c1685a16\n- ~~MESH_OT_screw~~ badd88ca02\n- ~~MESH_OT_select_all~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_axis~~ c899f21800\n- ~~MESH_OT_select_face_by_sides~~ 90c9458b2f\n- ~~MESH_OT_select_interior_faces~~ e161c51e7f\n- ~~MESH_OT_select_less~~ b6a7fa1880\n- ~~MESH_OT_select_linked~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_linked_pick~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_loose~~ eacb2eb423\n- ~~MESH_OT_select_mirror~~ 3ebe389605\n- ~~MESH_OT_select_mode~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_more~~ 2309131b4d\n- ~~MESH_OT_select_non_manifold~~ 4da2aec2bb\n- ~~MESH_OT_select_nth~~ 63c2397171\n- ~~MESH_OT_select_random~~ 847f028b71\n- ~~MESH_OT_select_similar~~ 75b2091d42\n- ~~MESH_OT_select_ungrouped~~ 1d8e6c5cd0\n- ~~MESH_OT_shortest_path_pick~~ c32cc3e43e\n- ~~MESH_OT_shortest_path_select~~ 5a431be629\n- ~~MESH_OT_spin~~ ab8dded330\n- ~~MESH_OT_vert_connect~~ 944054fbb6\n- ~~MESH_OT_vert_connect_path~~ fc7316fb54\n", "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", "Joining meshes or realizing instances in geometry nodes removes custom normals data\nOperating system: macOS Big Sur 11.5.2\nGraphics card: Apple M1\n\nBroken: 2.93 and 3.0 Alpha\n\n\nUsing the collection info node in geometry nodes destroys custom normals data when the geometry node modifier is applied (or when the project is exported).\n\n\nApply the geometry node modifier on the \"Dummy\" object in the attached blender project. I've also included a video that shows the issue.[collection_info_test.blend](collection_info_test.blend)\n\n[collection_info_bug.mov](collection_info_bug.mov)", "Meshes that are generated with the screw modifier cant use the box projection type\nOperating system:\nGraphics card:\n\nBroken: 83f9218801d4\n\nThe meshes that are modified or extended by the screw modifier can't use the box projection of an image map. All the objects in the screenshot use the same material and the texture projection. As you can see the box and the plane has no problem with the projection type.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLoad the attached .blend\n\nEnable the material preview and check the object named \"Screw\"\n\nCtrl-A -> \"visual geometry to mesh\" to see that the texture would normally work on the mesh, except ehwn the modifier is enabled.\n\n[_23012023_1655_00.zip](_23012023_1655_00.zip)", "Erratic behaviour of materials/material slots for text objects\nOperating system: Linux-5.19.0-45-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.6.0\n\nMaterial assignment for text objects doesn't behave as expected. Removing an unused material slot will cause changes to the materials used by the object. The same happens if you rearrange the material slots.\n\n1. Add a new text object. Leave the default string \"Text\".\n2. Add 3 new material slots with different materials to the object. Use different viewport display colors to be able to see changes.\n(You will now have Material.001, Material.002 and Material.003)\n3. In edit mode, select the last two letters and assign Material.002.\n(You should now have \"Te\" using Material.001 and \"xt\" using Material.002)\n4. In object mode, remove the last material slot containing Material.003.\n(This material was not assigned to any character, and removing it should not cause any change.)\n5. All 4 letters are now using Material.001. \"xt\" should still be using Material.002.\n\nAlternatively, execute step 1-3 above and then.\n4. Move the last material slot up to the first place.\n(This should not cause any change. Normally in blender, the materials used by the geometry will not change if you rearrange the material slots.)\n5. You will now have \"Te\" using Material.004 and \"xt\" using Material.002. \"Te\" should still be using Material.001.\n\nI have attached a blend file where you just need to remove the last (unused) material slot to see the problem, or move the last material slot up to first position.\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", "Material slots undo is inconsistent in non-Object modes\nBroken: 3.0\nMaterial slots undo is inconsistent. Sometimes multiple slots are added/removed in one undo, and sometimes undo won't change back mode.\n\n\ntab to edit mode \nadd a material slot\nundo twice\nadd another material slot\nundo\nboth material slots will be undone. Also undo won't go back into edit mode.\nif you redo both material slots are redone at the same time.\n", "Library overrides get reset when the linked file changes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.1 Release Candidate\n\n\n1. Link a collection from a different file\n2. Override everything (selection & content & data etc down to the materials, so that materials have an O in front of them)\n3. Replace a few materials on some objects with new materials\n4. Go into the originally linked different file and make some changes to a mesh (and perhaps move some meshes to a different collection that's not linked)\n5. Open the files with the link in it\n\nResult:\n\nAll material changes have now been reset\n\nExpected:\n\nThe overriden materials should of course stay the same!\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)" ]

[ "Material Slot Bug\nWindows 7 64, HD 5770\n\nBroken: 9337574 (2.71 release) + 35bc266\n\nMaterials that are used by more than one object, but in different material slots:\n(MeshA RedMaterial Slot1 + MeshB RedMaterial Slot 2)\ndisappear if they have any generate modifier assigned on its object.\n\nThere also seems to be a dependency if the faces are assigned to only one material or more than one.\nI havent fully discovered the cause, but its easy to reproduce - please take a look in the file.\n\n[MaterialDisappearsBug.blend](MaterialDisappearsBug.blend)\n\n- Add a Cube\n - Give it a Array modifier.\n - Give it 2 Materials (use 2 different colors - more visible).\n - Assign some faces or whole mesh to Material 2.\n- Duplicate the Cube\n - Delete Slot 1 Material on Cube 2.\n\nYou now have Material2 in different slots:\nCube 1 = Slot 2\nCube 2 = Slot 1\n\n- Press P to start the Game Engine\n\n**Problem:** Material 2 on Cube 1 doesnt show up.\n\n---\n\nThe bug exists very long, i think over 3 years - finally i have found something.\nWould be great if you can fix that.", "Modifiers make materials disappear in BGE\n**Category**: Rendering\n\n\n%%%Two objects use the same material, which is the 2nd material slot for the first object created.\n\nThe first object has (any?) modifier except Armature. eg. Subsurf works.\n\nResult:\nOn one object the shared material does not show in BGE, the faces are invisible.\n\nThe material index isn't reset to zero for the modified mesh probably, this has happened before. But it only happens if the material is the same.\n\nWindows Vista 64, NVidia GeForce GT 240, Blender 2.55 official, VBO off.\n\n--------\nThe tracker is down to 3 pages - awesome job everyone!\n\nDave Heinemann%%%" ]

[ "Cycles render artifacts relating scene scale\nOperating system: Windows 10\nGraphics card: tested multiple graphics cards with same issue\n\nBroken: 2.83.6 (file originally made in 2.79 and had the same issue)\n\nThere exists in the blend file data only two objects - the camera and a simple plane. Yet when rendering, the result does not match the viewport and there seems to be another ghost object appearing in the scene.\n\nBased on the following startup file: [strange-error.blend](strange-error.blend)\n\n1. Switch to rendered view in the viewport. This is how things should look.\n2. Now render the current frame at frame 97. Notice the strange ghosting effect in the center of the frame.", " Startup File: Header Collapse Menu not restored after restarting blender\nOperating system: windows 10 64bit\nGraphics card: Nvidia gtx m860\n\nBroken:\nversion: 2.80 (sub 37), branch: blender2.8, commit date: 2018-12-16 00:27, hash: 4488056f3d9, type: Release\n\nWorked: (optional)\n2.79b\n\nwhen using Collapse Menu on the header and restarting blender the setting is ignored and the header menu is expanded again.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. open blender 2.8\n2. collapse the header menu\n \n3. save startup file so we save the header configuration\n\n4. restart blender\n5.the Header menu is expanded again after a restart, other headers like the editor menu stay collapsed after a restart.\n\n", "Render: Option to use fullscreen depthbuffer for tracing\nAdd an option to allow the use of a more precise depth buffer when doing screen space effects.\n\nThat may solve some issue regarding noise or self intersection.", "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)", "Topbar glitch when the Status Bar is hidden due to the process bar display\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: 2.81a, 2.82a, 2.83.0, 2.90, 2.93.3, 3.1.0\nWorked: not found\n\nIf the Status Bar is hidden, when you invoke a process that displays a progress bar, it causes a glitch.\n\nThis has something to do with the fact that the *arena* is divided into *regions*, so for example,\nthis works fine when `template_running_jobs()` is moved from `draw_right()` to `draw_left()`.\n\n\n- Hide the Status Bar\n- Press F12\n\n{[F8577145](topbar-glitch.png), size=full}\n\n[topbar-glitch.mov](topbar-glitch.mov)\n\n\n- Hide the Status Bar\n- Invoke the File Browser with File > Import or Add > Image > Background.\n\n{[F10340167](bug.mp4), layout=link}", "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", "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", "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "Blender 2.8. In edit mode when you have hard scene (slow down processing) all your actions will applyes not at right moment (not at click but at moment when blender finn. caclucations)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 53)\nWorked: (optional)\n\n\nI have scene where I put a lot boolean(and not only) modificators on one objects and when I enter into edit mode all processing erally slow (each action: movement, extrusion, etc..) And problem here in next: when you doing any action (and it took time to process it) and then press mouse button to apply action affect, but! it will not memorize position of the mouse when you pressed, and still continue doing (move to the cursor) And this really anoing because you need repeat all twice or more time. Or just seating and waiting with no mouse movement at all, when it will apply action effect. \nSo core problem is that: in edit mode any affect will applyes not at moment when you decide but by moment when CPU will finished calculetion of movement/action and will change your action to position where is going be mouse positioned at the moment of the end calculation... something like that. \n\nCreate some worcload/heavy scene. For example by a lot subdivisions and booleans at object. When each your action will be like \"under water gravity\" slowed down. And then try to change(extrude/move vertext / anything) boolean part that will be used as cut area in the edit mode. \n\n[2019-04-01 17-39-35.mov](2019-04-01_17-39-35.mov)", "AutoDepth ignores texture transparency\nOperating system: Win 10 64-bit\nGraphics card: 980 Ti\n\nBroken: 2.93.4 LTS, 3.0 alpha (including current latest build)\nWorked: 2.79\n\nWhen navigating using mouse with auto-depth enabled, the full-transparent parts of textures should be ignored when picking the depth.\nThis worked correctly in 2.79, but 2.93 and the latest 3.0 alpha seem to ignore this.\n\n\nEnable Auto-Depth, create an object, assign it a material with some full-transparent texture, then try to zoom / pan using mouse with the cursor on it.\n[autodepth-transparent-issue.blend](autodepth-transparent-issue.blend)", "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", "Viewport display: in front should be listed under visibility as it also affects final render\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nUnder object properties, viewport display: in front affects both the visibility in the viewport and in the final render, and as such should probably be listed under visibility rather than viewport display.\n\n-", "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", "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", "GPencil: Layers used as mask and with viewlayer filter applied are rendered in all passes. \nOperating system: Linux-5.4.43-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.90.0 Alpha\n\n\nLayers, used by other layers as masks, are always rendered when they have a viewlayer filter applied in all render passes.\nI feel a layer used as a mask for other layers and with viewlayer filtering it should work as a mask even when it is not rendered in a pass.\nI don't know if this is intentional, a time limitation, or a complex implementation.\nAssess whether this squares as a bug or feature recuest. Thank you very much for your wonderful work.\n\n- Download the blend file.\n- Note that the layer called \"masc\" is used as a mask for the other two and all layers are filtered in viewlayer filter.\n- Render and note that the mask appears in both passes.\n[GP bugreport viewlayerfilter and layers mask.blend](GP_bugreport_viewlayerfilter_and_layers_mask.blend)\n" ]

[ "Preferences window opening behind main window when in fullscreen mode\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 1070\n\nBroken: version: 2.80 (sub 39), branch: master, commit date: 2018-12-22 09:56, hash: 4c5e76025d83, type: Release\n\nWhen in fullscreen mode, the preferences window opens behind the main window (but still gets input focus).\n\nLaunch Blender,\nclick \"Toggle window fullscreen\" in the \"Window\" menu to make the main window occupy the entire screen,\nclick \"Preferences...\" in the \"Edit\" menu.\n\nExpected result: The preferences window should open in front of the main window and receive input focus.\n\nObserved result: The preferences window opens behind the main window but receives input focus anyway, making parts of the main window temporarily unresponsive to mouse clicks. Alt-Tab (on Windows) reveals the preferences window.\n" ]

[ "Overlapping objects of different sizes with volumetric materials render incorrectly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.83.4\nWorked: 2.82a\n\n\nTwo cubes, both principled volume, one large one small, smaller cube inside larger cube. \n\nThe area inside the smaller cube from the view perspective renders differently than outside with a hard edge where the mesh ends, the effect is much easier to see with a texture controlling the volume density of the large cube. Looks to me like an issue with blender using different step sizes for different objects. Definitely not an issue with not enough transparency/volume light bounces, already tried that.\n\nOnly happens with cycles\n\nOpen blend file\nSwitch to rendered view\nToggle visibility of big volume and/or small volume in outliner to see difference\nExtra notes in shader nodes for big volume and small volume's materials\n\n[overlapping volumes hard edge bug.blend](overlapping_volumes_hard_edge_bug.blend)", "Drivers not updating correctly when multiple drivers are relying on single property value change (viewport issue only)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\nBroken: version: 2.81 (sub 10)\nAlso tested on 2.80 release version. Happened for me there for the first time so I've downloaded newest build to check if issue still occurs.\n\nWhen multiple drivers are linked into the same property, changing value of that property is not always propagated to all drivers. It looks like some sort of race condition, although I don't think it's caused by switching property back and forth and threads overlapping in that scenario, because even when doing this slowly, issue occurs. Issue also occurs when clicking arrows on a property instead of dragging left/right. \n\nSeems to be related to viewport displaying only. As presented at the end of linked video, rendering scene in such broken state is working correctly.\n\n1. Open provided blend file\n2. Select small cube at the bottom of the screen\n3. Cube has a property on it. Switch its value back and forth.\n4. When property is set to 0, only vertical bars should be visible. When property is set to 1, only horizontal bars should be visible.\n5. Not every time, but occasionally bar is visible when it shouldn't or the other way around.\n\nVideo of bug occurrence:\n\nwatch?v=5wrGXl3KnrQ&feature=youtu.be\n\n[bug-drivers.blend](bug-drivers.blend)", "Having a Collection with volume shaders set to Indirect Only doesn't work with Transmission rays\nOperating system: Windows\nGraphics card: GeForce RTX 2080 Ti\n\nBroken: 2.82\n\nThe Indirect Only setting on a Collection doesn't seem to apply when viewing Volume shaders through shaders with Transmission enabled.\n\nSee the attached blendfile. Enabling or disabling the VOLUMETRICS collection (which is set to Indirect Only) doesn't affect what is seen through the glass.\n[comp_test_render_scene.blend](comp_test_render_scene.blend)", "Particles reset their position when using time stretching\nMinimal reproduction steps:\n- Add a particle system to the default cube and make it renderable.\n- Set the old time stretching setting to 20 and leave the new at 100.\n- Play the animation until frame 90 and render.\n- Find that the particles are sticking on the object as opposed to their correct position in the viewport.\n- Render again. They now have their correct position.\n- Play another 5 frames.\n- Render again, they are now sticking to the object again.\n\n[timeStretchingBadRender.blend](timeStretchingBadRender.blend)\n\n**Original Report**\n\nHello,\n\ni am using blender-3.1.0-linux-x64 and working on particles with time stretching but the viewport display is correct.\n\nattached is the blend file. [experiment with text.blend](experiment_with_text.blend) \n\nproblem seen in cpu/gpu/cycles/evee.\n\nregards,\nYaju", "Stereoscopy not working properly with time remapping and motion blur\nOperating system: Windows 7\nGraphics card: GTX 1070\n\nBroken: Blender Version: 2.83 LTS\nWorked: Never\n\nI encountered two weird issues when using stereoscopy, time remapping and motion blur at the same time.\n\nThe first issue is easy to reproduce because it happens every time stereoscopy and time remapping are enabled.\nFor example if we set time remapping to be Old: 100 and New: 200 and try to render the frame 100 there is no issue while rendering the left camera, but the right camera reports it as the frame 50 (but it does actually render the correct frame - 100). Also the playhead gets set to the frame 50 after rendering. If we were to render again, it would render the frame 50 and set the playhead to 25 and so on and so on.\n\nThe second issue I have not been able to reproduce in a fresh scene, but I have a .blend file where it is present. \nSo again when rendering some frame with time remapping enabled, the left eye is fine, but the right eye renders some objects with motion blur that should not be there.\nI believe these two things are related and possibly the result of a single bug, so I'm not splitting these into two bug reports.\n\nThis is a stripped down version of my scene - it was a complete animation with a character.\nThe motion blur wasn't present on the character's body, but it was present on the character's eyes and teeth (both parented to a specific bone through Object Properties > Relations), and that sphere parented (with a 'child of' constraint) to the root bone.\n\n[stereoscopy bug.blend](stereoscopy_bug.blend)\n\n- Open file\n- Render\n\nOne eye have motion blur, another one does not.\n\n", "Scene statistics not updating depending on geometry node behaviour\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: Never.\n\nIt seems that the scene statistics (both in the viewport and in the status bar) are not updating to reflect the number of vertices after a deleting operation through geometry nodes.\nHowever it does update if I move to another frame in the timeline.\nIt may be a design choice to limit the computation needed but I thought useful to report\n\nIn the attached blender file go to the modifiers tab and change the LOD value in the geometry nodes setup, you'll see no change in the scene statistics despite the mesh displayed has a different amount of objects. If you move to any other frame it will update accordingly\n\n", "Measurements don't refresh when changing 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.3.0 Alpha\nWorked: Never\n\nWhen doing measurements with the Measure tool and changing to another scene, this measurements are preserved when they shouldn't.\nThey refresh correctly when changing tool to another (ex. Cursor) and then going back to Measure.\n\n- Draw a measurement with Measure tool\n- Create a new, empty scene\n- Notice the measurement is still there\n- Change the tool to Cursor and then back to Measure. Not there anymore.\n\nYou can also make a measurement, change Scene without refreshing and edit this measurement. That will create a new measurement in the Scene that that happened.\n\nA more destructive behavior happens when there are already measurements in the Scene you're going. If you delete a measurement without refreshing, all the previous measurements in the Scene are also deleted.\n", "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", "(Shrinkwrap) Modifiers and constraints targeting a mesh wont update during that meshes sculpting session (unless an additional mirror modifier is in play)\n2.8x - 3.0 (may exist in older versions)\n\nAppearently I cannot modify the shape of the target mesh in sculpt mode since the shrinkwrap on the main mesh does not update unless I click somewhere else and not use the sculpt tools. It does update in edit mode tho.\nI remember someone saying its supposed to happen in order to keep performance running smooth or something like that, but I hardly believe it.\n\nThe only way to be able to update shrinkwrap is to add a mirror modifier to the target mesh and then you can now use sculpt mode with no issues. I've done this a few times now and I barely noticed any performance impact.\n\n1) Add a mesh, any mesh\n2) Give it a shrinkwrap modifier\n3) Add another mesh that will be used as the target\n4) Go to sculpt mode and shape up the target mesh\n\nNo update on shrinkwrap unless I click something else around the UI\n\nTo fix this:\nif the model has one mesh and I wanna edit it symmetrically, I cut it in half and add a mirror modifier to it\nShrinkwrap now updates all the time when I sculpt the target mesh without needing to click somewhere\n\nFrom there on I can do whatever I want with the target mesh in sculpt mode", "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", "Attribute Node Doesn't Function Under World Shader Context\nOperating system: Windows 10 19044.1826 64-bit, Linux 5.18.14.arch1-1\nGraphics card: NVIDIA GeForce GTX 1080 Ti\n\nBroken: 3.2.1\nWorked: never\n\nThe `Attribute` node (both in Cycles or Eevee) doesn't work under World materials.\nAlso the `Geometry` and `Instancer` types in the node are irrelevant in the Word context and should be hidden.\nMaybe the `Object` type should be renamed to 'World', but it currently doesn't seem to be able to pass world properties as uniforms.\nThis essentially means that:\n - There are redundant elements in the World shader node editor that currently serve no purpose\n - There is no way to pass custom uniform attributes to World shader nodes, although they should be available (similarly to how it is done for objects)\n\n\n\n- Open attached .blend file\n- Note that the \"test_color\" attribute of the World is not read by the material.\n[AttributeWorldShader.blend](AttributeWorldShader.blend)", "Rigidbody cache is not invalidated when constraints are adjusted.\nOperating system: Ubuntu 20.04 x64\nGraphics card: RTX 2080\n\nBroken: 3.2\nWorked: Unknown\n\n\nWhen working with motor and slider constraints, adjusting them does not (always?) invalidate the existing rigidbody cache, causing the previously cached behavior to be retained.\nThis behavior does not persist on file reload (eg, saving and reloading the file with modified constraints corrects the issue), and anything else that will invalidate the cache also \"corrects\" the problem (ie, adjusting a simulated object).\n\nStarting with the included blend file.\n[repro.blend](repro.blend)\n 1. Press play on the timeline. Observe that the cube moves towards the +X axis.\n 2. Rotate the empty hosting the slider constraint (select from the outliner, or select the empty in the -Y quadrant) so that the local X axis points in another direction; for example, rotate 90d around the Z axis so it points in the +Y direction.\n 3. Rotate the empty hosting the motor constraint (select from the outliner, or select the empty in the +Y quadrant) so that the local X axis matches the direction of the slider constraint.\n 4. Press play on the timeline. Observe that the cube still moves towards the +X axis.\n\n[vokoscreenNG-2022-06-28_13-37-49.webm](vokoscreenNG-2022-06-28_13-37-49.webm)", "Irradiance volume visibility collection not working properly\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.5\nWorked: Unknown\n\nThe irradiance volume visibility collection is not working as intended. File is included.\n\nDownload [this example. ](view?usp=sharing)\nWhen you open the file you'll notice immediately that the IV is already set to Collection, which means in theory it should NOT be affecting anything in \"Collection 2\". Even if you delete the light cache and rebake it, no matter what happens, it affects everything outside \"Collection\" regardless. The way I see it, visibility collection is meant to affect whom it collects lights from and meshes to light up, but so far it only seems to care about gathering lights alone.\n\nThis ALSO affects rendering it out. For that, just change the view layer to V1, and turn on Collection 2 to replicate.\n\nWorse still, disabling the visibility/renders of the irradance volume still lights up other objects no matter what. This, in my opinion, is a huge issue. It means I have to delete the light cache whenever I need it off, and rebake it, wasting a TON of time just to render it and only have it affect a singular object.", "Linked Mesh Editing Doesn't Work As Expected When Using Data Transfer Modifier\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.81 (sub 16)\n\nObject instances doesn't work as in blender 2.81\n\n\nIn blender 2.81, after entering the edit mode, all instances become active. You can see changes in real time.\nScreen below:\n\n\nIn Blender 2.82 it work ok till some time. I couldn't determine at what moment it breaks...\n\n\nChanges appears only after You enter to object mode.\n\n\n\nHere is blend file to test\n[instances_issue.blend](instances_issue.blend)\n\n\n", "Mesh to Volume intersection artifacts\nOperating system: Ubuntu18x64, Ubuntu20x64, Win8x64.\nGraphics card: Mesa DRI Intel(R) HD Graphics (BYT) Intel Open Source Technology Center 4.2 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0, 3.1\n\nIntersecting Mesh to Volume produces artifacts (on CPU. GPU not tested).\n\n[volume-intersection.blend](volume-intersection.blend)\n - Open,\n - Run viewport Render Preview on the left side." ]

[ "volumetric broken, not refresh\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nvolumetric broken, not refresh, it is necessary to enter and exit in local mode to update the parameters\n\nonly on these gpus, I tried on the intel HD and they work well.\n\nsee the gif\n\n\n\n\n\n" ]

[ "Multi-User Action keeps moving object after deleting all keyframes until reloading file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nDeleting keys from action with several users doesn't update correctly.\nActions without any keyframes keep changing the object until you revert the file.\n\n1. Add two keyframes to the default cube. (Scale it up and move it to the side)\n2. ALT+D to create a linked copy.\n3. On the linked copy, go to the dopesheet (e.g. action editor)\n4. Delete the keys. Because the action has two users, the keys should be deleted for all users.\n5. Play the animation. You'll see the original copy still moves according to the original keys.\n\n[#88208.blend](T88208.blend)\n\nThank you for taking a look at this! :)\nSeems like a bug to me.\n", "UI: activate_init doesn't work with Int and Float type properties\nOperating system: Windows & Linux\n\nBroken: 3.2\nWorked: Unknown\n\nUsing activate_init to allow users to directly edit a property doesn't seem to work when the property is of type IntProperty or FloatProperty.\n\n1. Open the attached script in blenders text editor\n2. Run the script\n3. Go to the 3d viewport\n4. Ensure an object is selected/active\n5. Run the simple operator, either through the menu or operator search\n6. Notice that the property in the popup is not directly editable\n\n[test_activate_init.py](test_activate_init.py)", "Toggling edit mode messes with active attribute\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 3.6.0 Alpha\n\nToggling edit mode does not properly preserve the active attribute.\n\n\n\nFrom default startup:\n- go to attribute panel\n- select UVMap as active\n- go to edit mode\n- nothing is active\n\n", "Shortcut changes are applied to all keymaps globally instead of individual keymap\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.34\n\nBroken: version: 2.92.0\nWorked: Unknown - I tested as far back as 2.79b\n\nAfter creating a new, custom keymap in Blender, any shortcut changes are applied globally for all keymaps instead of only locally to the new, custom keymap. Therefore, switching between keymaps does not make a difference, since any shortcut changes made to one keymap are applied to the rest of the keymaps globally.\n\n\n1) Launch Blender\n2) Go to Edit > Preferences > Click \"Keymap\" from the list on the left\n3) Click the \"+\" next to the keymap dropdown (default says \"Blender\")\n4) Enter a name and click \"OK\"\n5) Change a shortcut\n6) Switch back to the default \"Blender\" keymap\n7) The shortcut change is applied (copied) to the default keymap plus all other keymaps in the drop down.\n\n**Conclusion:** Creating different keymaps has no purpose since the shortcut changes are copied to all keymaps globally.\n\n**Workaround:** \n\n1) Launch Blender\n2) Go to Edit > Preferences > Click \"Preferences\" in the menu bar and uncheck \"Auto-Save Preferences\"\n3) Click \"Keymap\" from the list on the left\n4) Make all shortcut changes **before** creating a keymap\n5) Add a new keymap and give it a name\n6) Click \"Preferences\" in the menu bar and click \"Revert to Saved Preferences\"\n7) Keymaps should now be different and show their own individual shortcuts when switching back and forth\n\n\n\n - Any further changes to the new keymap will be applied globally. To update your new keymap with further changes:\n\n\n\n8) Update the shortcuts \n9) Delete the custom keymap (or add a new keymap with the same name and skip the next step)\n10) Add a new keymap and give it a name\n11) Click restore above the shortcut updates\n\n\n", "Reordering menu or modifier in Properties Panel spams modal events until Blender restart.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.1\nWorked: I'm not sure the newest but tested 2.90 and it worked correctly there.\n\nIf you run *bpy.app.debug_events=True* from the Py Console, then click to move a menu or modifier in the Properties Panel, that is, drag to reorder it, you'll note that Blender goes from reporting event input data in the System Console to non-stop spamming of event.type as \"TIMER\" and event.value as \"NOTHING\" and it won't quit until you restart Blender. This can be seen by running bpy.app.debug_events, as well as in any additional addon or script that prints event.type and event.value during its modal function while running after clicking to reorder a menu or modifier in the Properties Panel.\n\nThis spamming can cause unexpected behavior in addons or scripts the user is running. For another example, if you click a menu or modifier to reorder it in the Properties Panel and then run the template code that comes with Blender \"operator_modal.py\" and paste this line within the modal function *print(event.type,event.value)* you'll see the spamming. This also happens in the latest builds of 3.1 and 3.2. \n\n\n\n\n\n\n - Open a vanilla install of Blender.\n - Go to the Scripting Workspace.\n - Enter this line into the Py Console \n\n\n```\nbpy.app.debug_events=True\n```\n\n\n - Press Enter.\n - Go to Window and press Toggle System Console.\n - Note the normal behaivor of debug_events\n - Now click and drag to reorder a menu or modifier in the Properties Panel.\n - System Console gets spammed with event.type \"TIMER\" event.value \"NOTHING\" until restart.\n - Event data of addons or scripts running modals also get spammed until restarting Blender.\n\n\n\n\n\n\n", "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.", "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", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "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", "Clearing library overrides from the object menu differs from the outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.1 Release Candidate\n\nPlease see the attached movie. Using the \"wrong\" menu will cause the material properties panel to become unresponsive (beginning of movie) with overrides still in place until you use the outliner (end of the movie).\n\n1. Link some objects from a file\n2. Override them down to the materials\n3. Swap out some materials\n4. Use the clear library override from the object menu\n\nResult:\n\nThe material overrides aren't cleared, but you also can't access the properties panel anymore.\n\nExpected:\n\nThe material overrides should be cleared.\n\nWorkaround:\n\nUse the outliner instead.\n\n", "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*", "Cancel gizmo is still working, even it is deactivated\n2.80\n\nCancel Generic Gizmo Tweak is still working even you delete this event or deactivate it.\n\n\n\nBtw. I can not even found \"Generic Gizmo *\" in the hotkey list. Just with search function. Is it listed?\n\n", "GPencil: Shortcuts in Draw Mode are hardcoded\nMultiple keys in the `gpencil_draw_modal` function are hardcoded and (some) don't show up in the info bar. This makes it impossible for the user to know what certain keys do as well as impossible to change them in the keymap. All of those keys should be in the keymap with the default keys set as they are now.\n\nHere is a list of these (hardcoded) shortcuts:\n\n - {key Enter}, {key Pad_Enter}, {key Esc}, {key Space}, {key Ctrl Z} (?): Confirm\n - {key Mousewheel_Up}, {key Pad_Plus}: Increase size of eraser\n - {key Mousewheel_Down}, {key Pad_Minus}: Decrease size of eraser\n - {key O}: Set center of guide\n - {key V}: Turn off speed guide\n - {key M}: Alternate or flip guide direction\n - {key L}: Turn on line guide; {key Ctrl L}: Turn on line guide with angle = 0; {key Alt L}: Turn on line guide with last angle\n - {key C}: Turn on circular guide\n - {key K}: Turn line guide clockwise\n - {key J}: Turn line guide anti-clockwise\n", "Change autokey preferences \"Only insert needed\" to \"Only insert keyframes on properties that have changed.\"\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\n\nThe auto key preference descriptions can be confusing. Without an understanding of what \"Needed\" means, it's unclear what this preference does. We can be more descriptive and make it clear to users that this option will only insert keyframes on properties that have changed.\n\n", "Menu Editor for Quick Favorites\nCurrently users can only manage menu items in the quick-favorites menu by adding/removing items.\n\nThis task proposes to: \n\n- Create a generic menu editor in the user preferences.\n\n - Add/remove menu items\n - Re-ordering menu items.\n - Operators options should be able to be changed or unset - as we have with the keymap editor.\n\n**Implementation**\n\n- This could share UI code with the keymap editor for adjusting operator settings, since internally they are very similar.\n- We may support multiple kinds of menus, besides \"Quick Favorites\", internally there is support for this. Even if this isn't exposed to users initially.\n\n```\nThis would be useful for declaring user defined toolbars for example.\n```\n\n**User Interface**\nHere's how the UI could be organized: \n\n{[F8282863](Screenshot_2020-01-17_at_11.08.58.png), size=full}" ]

[ "Unable to remove added keying set from context menu\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GT 440/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.0.0\nWorked: (NONE i tried all 2.9 versions):\n\n\nadding something to the \"keying set menu\" removes the default keying set and you can't remove anything you added and it does not even give a menu to choose the thing you wanna animate\n\nalso when you try to animate the stuff you added to the keying set menu it keys everything you added even if the object is not selected or something else is selected and it keys multiple opjects\n\n- Open default scene\n- Add anything to the keying set menu (from object properties tab -> RMB on scale -> Add all/single to keying set)\n- And then try to remove it (RMB -> Remove from keying set)\n\n" ]

[ "Mesh calc_smooth_groups(use_bitflags=True) issue\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2070S\n\nBroken: 3.0.0\nWorked: \n\nIf use_bitflags is True calc_smooth_groups returns only 1 smoothing group for opposingly facing faces when they share a vertex, see attachment. \n[flip.blend](flip.blend)\nIf use_bitflags is False calc_smooth_groups returns 2 smoothing groups in this case which is fine.\nIf use_bitflags is True and the 2 faces share an edge it returns 2 smoothing groups which is also fine.\n\nbpy.data.collections- [x].objects- [x].to_mesh().calc_smooth_groups(use_bitflags=True)\nreturns ((1, 1), 1) instead of ((1,2), 2)", "Geometry Nodes + Shader Editor + Asset Browser bug\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5 `7bf75231e8c5` , 3.4.1 `55485cb379`\nWorked: (latest 3.3.2 for Mac Intel)\n\nGeometry Nodes Editor + Shader Editor loads in all marked, related assets from Asset Browser causing crash and memory overload\n\n- Extract Asset.zip\n- Open default blender scene and assign asser library path as shown in the image\n- Open node editor\n- SHIFT+A action cause immediate memory overload from Asset Browser\n\n\n\n[Assets.zip](Assets.zip)\n\n[asset-library-indices.zip](asset-library-indices.zip)", "Blender crashed in edit mode with material index creazy and strange normal\nOperating system: Linux pop-os 5.17.5-76051705-generic\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.1.0 / blender-3.2.0-stable+v32.e05e1e369187-linux.x86_64-release\n\nAn object imported from I don't know where, with crazy material_index : (-30086) in spreadsheet editor, and with strange normal, makes blender sik.\n\nIn edit mode, if I try to move the concerned geometry blender crashes systematically.\n\n[2022-06-16_bug-normal.crash.txt](2022-06-16_bug-normal.crash.txt)\n\n[2022-06-16_bug_system-info.txt](2022-06-16_bug_system-info.txt)\n\n[2022-06-16_bug-normal.blend](2022-06-16_bug-normal.blend)\n\nthank you,\n - Thomas", "sharp_edge attribute doesn't work for GN-created geometry in 4.0\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nBlender 4.0 is expected to finally expose normal smoothing capabilities to geometry nodes, and while the sharp_face attribute seems to somewhat work on the geometry generated inside GN, instead of inherited from the parent object, sharp_edge attribute just won't work on GN-created geometry no matter what.\n\n\n1. Open the attached file: [sharpbug.blend](attachment)\n2. Move the B value of Great Than node\nResult: sharp_edge attribute modifications don't have any effect on the mesh shading.\nExpected: sharp_edge attribute modifications affect the mesh shading.\n\n", "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 2.92.0 crashes when baking steam simulation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\nCPU: Intel Core i7-8700K\nMemory: 32 GB\n\nBroken: version: 2.92.0\nWorked: I have not tried any other version than 2.92.0 (sorry)\n\nI tried to make a simple steam simulation following the steps described here: watch?v=_K0XsHht6pg. It crashed while baking, and tried to simplify the setup with a minimal set of objects, and it still crashes after baking about 30-50% of the 300 frames.\n\nFollow the steps as described in the video watch?v=_K0XsHht6pg\n\nAttached is .blend file that I tried to make as simple as possible: [steam.blend](steam.blend)\n\n - Open the attached file\n - Press \"Bake Data\" for Physics Properties for the cube\n - Blender crashes after 30%-50% of baking\n\nI have not tried a newer experimental release or an older release.\n\nI was able to reproduce the issue with the default 32 Resolution Divisions (which is way faster to reproduce than the 160 in the included file). I then tried experimenting which exact setting caused the crash. I got it to crash with Adaptive Domain disabled, and Gas Heat 1.5 and Dissolve Time 30, but now I'm not able to reproduce anymore with any setting (at least with 32 Resolution Divisions).\n\nAfter some more experimenting, it seems it randomly crashes and sometimes works. It is definitely reproducible with 32 Resolution Divisions. I kept all settings as I had before, which had worked successfully, but then changed the Time Scale to 0.8, and then it crashed again when baking. However, it had previously crashed at least once with the exact same settings with which I had also successfully baked (and the Time Scale at the default 1.0), so it is not the Time Scale that is causing the issue.", "Support all attributes in the non-point cloud attribute list\nSee #87827.\n\n* position\n* UVMaps\n* Vertex groups\n(...)\n\nTechnical design discussion: #88460", "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 ", "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)", "Assert in debug for dyntopo sculpt\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: Today main.\n\nSee attached stack trace file.\n\nIn debug:\n1. Sculp mode.\n2. Enable Dyntopo option.\n3. Do something.\nSee the crash.\n\n", "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", "Geometry Nodes: Rendered glitch with Image Texture and Scene Time\nOperating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.0\nWorked: Never\n\n**Short description**\nGeometry nodes that use single images or image sequences are rendered inconsistently but usually look normal in the viewport.\nHigh-res images seem to be more unstable.\nHaving a connected/unconnected scene time node in the geo node group while using an image sequence with any number of frames also makes the rendered image/animation more unstable.\n\n|Expected render|Occasional render glitch|\n|--------------------------|--------------------------------------|\n|| |\n\n\n**Reproduction steps**\nThis is the most unstable setup:\n\n1. Create new project\n2. in the image editor window add a new image with resolution of around 1080x1080 pixels and set the source an image sequence \n3. add geometry nodes modifier to the default cube\n4. follow this node setup; in the image texture node use the created image sequence \n5. Render animation\n6. some of the rendered images will be glitched\n\nI've also tested this approach with face extrusion or instance selection instead of deleting faces. The resulting renders were also glitched. \n\nInside of this zip file is a blender project with a similar setup along with some sample images:\n[geo node groups that use images are rendered inconsistently.zip](attachment)\n\nThis reddit post seems to be describing a similar issue:\ngeometry_nodes_rendering_glitch_info_in_comments/\n\nThe workaround with disabling geo nodes modifier in the viewport mentioned there seems to be working in a simple setup. In the above project from the .zip file it is less effective.\n\n", "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", "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", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)" ]

[ "Geo_Node Crash on Undo when there are group inputs other than 'geometry'\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\nWorked: I think the build from yesterday..\n\nExactly as the title says\n\n1. Open a new scene\n2. Add a nodetree in the default cube\n3. Add a new input in the Group Input node\n4. Do something and undo and then crash\n\n\n", "Geometry nodes undo crash with legacy nodes\nOperating system: Linux-5.14.7-2-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.14.7-2-MANJARO, LLVM 12.0.1) AMD 4.5 (Core Profile) Mesa 21.2.2\n\nBroken: version: 3.0.0 Alpha\n\nThe official geometry nodes demo file will crash if Ctrl-Z is used after moving a node/connecting or disconnecting a wire/selecting an object/deleting a node/editing an attribute field of a node.\nIn this file, changing any value of the nodes/hiding objects with the eye icon in the outliner does not get pushed to the undo stack: the asterisk indicating an unsaved change will not show up. After such a change, pressing undo is \"save\" and will not crash blender, but it will also not undo the action.\n\n- download the file https:*download.blender.org/demo/geometry-nodes/pebble_scattering.blend (from https:*www.blender.org/download/demo-files/) \n- move a node/connect or disconnect a wire/select an object/delete a node/edit an attribute field of a node\n- Ctrl-Z\n- crash\n\n\nSegmentation fault (core dumped)\n\nbacktrace\n../build_linux/bin/blender(BLI_system_backtrace+0x33) [0x7dd8b03]\n../build_linux/bin/blender() [0xf62d1b]\n/usr/lib/libc.so.6(+0x3cda0) [0x7f32cecceda0]\n../build_linux/bin/blender() [0x15b0a15]\n../build_linux/bin/blender() [0x124295e]\n../build_linux/bin/blender() [0x12456c7]\n../build_linux/bin/blender() [0x12461d2]\n../build_linux/bin/blender(makeDerivedMesh+0xaf) [0x12463bf]\n../build_linux/bin/blender(BKE_object_handle_data_update+0x3f0) [0x100e490]\n../build_linux/bin/blender(BKE_object_eval_uber_data+0x2f) [0x100e84f]\n../build_linux/bin/blender() [0x14cee71]\n../build_linux/bin/blender() [0x14ceec2]\n../build_linux/bin/blender() [0x7ddc83d]\n../build_linux/bin/blender() [0x134eac5]\n../build_linux/bin/blender() [0x134ed7b]\n../build_linux/bin/blender(BLI_task_pool_work_and_wait+0xe8) [0x7ddc5e8]\n../build_linux/bin/blender(_ZN7blender3deg23deg_evaluate_on_refreshEPNS0_9DepsgraphE+0x235) [0x14cf195]\n../build_linux/bin/blender() [0x104d241]\n../build_linux/bin/blender(wm_event_do_depsgraph+0xbb) [0x13585bb]\n../build_linux/bin/blender(wm_event_do_refresh_wm_and_depsgraph+0x87) [0x1358707]\n../build_linux/bin/blender(wm_event_do_notifiers+0x5d9) [0x135ff29]\n../build_linux/bin/blender(WM_main+0x28) [0x1354178]\n../build_linux/bin/blender(main+0x336) [0xeda3a6]\n/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f32cecb9b25]\n../build_linux/bin/blender(_start+0x2e) [0xf5f3ee]", "Geometry Nodes: Crash when hitting Undo\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nWhen I'm adjusting the Radius in the Geometry Nodes Modifier of the Procedural Donut scene, if I hit undo afterwards Blender crashes.\n\n[geometry_donut_fields1.blend](geometry_donut_fields1.blend)\nOpen the file, select the Donut object and in the modifiers, adjust the radius.\nThen hit Undo, and blender will crash.\n\nThanks :)", "Geometry nodes (Fields) Assertion failed at input_has_attribute_toggle()\nOperating system: Linux Ubuntu 20.04\nGraphics card: Nvidia RTX 3090\n\nBroken: master 4cf4bb2664ebe145dac9715bbbfcc2b96f5ff175 (2021-09-28)\n\nBlender crashes because hitting an assertion:\n\n```\nBLI_assert failed: source/blender/modifiers/intern/MOD_nodes.cc:320, input_has_attribute_toggle(), at 'node_tree.field_inferencing_interface != nullptr'\n```\n\n1. Start blender\n2. Enter geometry nodes workspace\n3. Click New to create a new GN modifier\n3. Add a new Math node\n4. Connect a new output socket from Group Input into the first socket of the Math node\n5. Click on empty space to deselect nodes\n6. Hit Ctrl+Z\n7. Crash\n\nStack trace:\n\n```\n- 0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50\n- 1 0x00007ffff6dd2859 in __GI_abort () at abort.c:79\n- 2 0x000000001aff98ae in _BLI_assert_abort () at /mnt/data/Devel/blender-git/blender/source/blender/blenlib/intern/BLI_assert.c:61\n- 3 0x000000000631e3f2 in input_has_attribute_toggle(bNodeTree const&, int) (node_tree=..., socket_index=1)\n at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:320\n#4 0x0000000006325d2b in initialize_group_input(NodesModifierData&, blender::nodes::OutputSocketRef const&, void*)\n (nmd=..., socket=..., r_value=0x60e000097498) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:693\n#5 0x000000000632b95d in compute_geometry(blender::nodes::DerivedNodeTree const&, blender::Span<blender::nodes::NodeRef const*>, blender::nodes::NodeRef const&, GeometrySet, NodesModifierData*, ModifierEvalContext const*)\n (tree=..., group_input_nodes=..., output_node=..., input_geometry_set=..., nmd=0x60f000191cb8, ctx=0x7fffbc7a0bd0)\n at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:934\n#6 0x000000000632de20 in modifyGeometry(ModifierData*, ModifierEvalContext const*, GeometrySet&)\n (md=0x60f000191cb8, ctx=0x7fffbc7a0bd0, geometry_set=...)\n at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:1066\n#7 0x000000000632e768 in modifyGeometrySet(ModifierData*, ModifierEvalContext const*, GeometrySet*)\n (md=0x60f000191cb8, ctx=0x7fffbc7a0bd0, geometry_set=0x7fffbc7a0ed0)\n at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:1093\n#8 0x0000000004902d86 in modifier_modify_mesh_and_geometry_set(ModifierData*, ModifierEvalContext const&, Mesh*, GeometrySet&)\n (md=0x60f000191cb8, mectx=..., input_mesh=0x61c00011f088, geometry_set=...)\n at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:953\n#9 0x00000000049067df in mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)\n (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, use_deform=true, need_mapping=false, dataMask=0x7fffbc7a15a0, index=-1, use_cache=true, allow_shared_mesh=true, r_deform=0x7fffbc7a14a0, r_final=0x7fffbc7a1480, r_geometry_set=0x7fffbc7a14c0)\n at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:1291\n#10 0x000000000490da2b in mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool)\n (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, dataMask=0x7fffbc7a15a0, need_mapping=false)\n at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:1914\n#11 0x000000000490f684 in makeDerivedMesh(Depsgraph*, Scene*, Object*, BMEditMesh*, CustomData_MeshMasks const*)\n (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, em=0x0, dataMask=0x7fffbc7a16c0)\n at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:2061\n#12 0x00000000037cee65 in BKE_object_handle_data_update (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088)\n at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/object_update.c:202\n#13 0x00000000037d196b in BKE_object_eval_uber_data (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088)\n--Type <RET> for more, q to quit, c to continue without paging--\n lender-git/blender/source/blender/blenkernel/intern/object_update.c:395\n#14 0x0000000005d09b4d in blender::deg::DepsgraphNodeBuilder::<lambda(Depsgraph*)>::operator()(Depsgraph *) const\n (__closure=0x6110016da248, depsgraph=0x61a00010aa88)\n at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1485\n#15 0x0000000005d2dabd in std::_Function_handler<void(Depsgraph*), blender::deg::DepsgraphNodeBuilder::build_object_data_geometry(Object*, bool)::<lambda(Depsgraph*)> >::_M_invoke(const std::_Any_data &, Depsgraph *&&) (__functor=..., __args#0=@0x7fffbc7a1830: 0x61a00010aa88)\n at /usr/include/c++/9/bits/std_function.h:300\n#16 0x0000000005c666c9 in std::function<void (Depsgraph*)>::operator()(Depsgraph*) const (this=0x6110016da248, __args#0=0x7fffbc7a18a0)\n at /usr/include/c++/9/bits/std_function.h:688\n#17 0x0000000005c61ab2 in blender::deg::(anonymous namespace)::evaluate_node(blender::deg::(anonymous namespace)::DepsgraphEvalState const*, blender::deg::OperationNode*) (state=0x7fffffffd880, operation_node=0x6110016da188)\n at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/eval/deg_eval.cc:118\n#18 0x0000000005c61b01 in blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*)\n (pool=0x61300062b2c8, taskdata=0x6110016da188)\n at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/eval/deg_eval.cc:129\n#19 0x000000001b53b7c0 in Task::operator()() const (this=0x613000210ac8)\n at /mnt/data/Devel/blender-git/blender/source/blender/blenlib/intern/task_pool.cc:178\n#20 0x000000001b53eeda in tbb::internal::function_task<Task>::execute() (this=0x613000210ac0)\n at /mnt/data/Devel/blender-git/lib/linux_centos7_x86_64/tbb/include/tbb/task.h:1059\n- 21 0x0000000005135475 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) ()\n- 22 0x000000000513572b in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*)\n ()\n- 23 0x0000000005124327 in tbb::internal::arena::process(tbb::internal::generic_scheduler&) ()\n- 24 0x000000000512f160 in tbb::internal::market::process(rml::job&) ()\n- 25 0x000000000513119c in tbb::internal::rml::private_worker::run() ()\n- 26 0x0000000005131399 in tbb::internal::rml::private_worker::thread_routine(void*) ()\n- 27 0x00007ffff7546609 in start_thread (arg=<optimized out>) at pthread_create.c:477\n- 28 0x00007ffff6ecf293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95\n```", "Geometry Nodes crashes undoing a change to an input node value \nOperating system: Mac and Windows\nGraphics card: Various{[F10741660](Undo_Crash.jpg)}\n\nBroken: 3.0.0 Alpha -- October 3rd build\nWorked: Unknown \n\nBlender crashes after undoing a changed geometry node's input value (please see picture)\n\n -- please reference picture\n1. Add a mesh\n2. Setup geometry nodes like the picture. Could be any node. I used Distribute Points on Faces in this example.\n3. Connect one of the inout fields back to the Group Input node to expose this input.\n4. Find this value in the modifier inspector window. \n\nIf you change this value and select undo, blender crashes. \n(fyi - Blender doesn't crash if you undo without changing the value)\n\nSeems to happens with any node, any geometry as long as the node has an input you can connect to the group input block and change the default value and press undo. \n\nAlso it may be helpful to note the behavior in the picture below. Multiple input nodes can be made by plugging and unplugging values into the Group input node. And they can be rearranged without the node names updating. Pressing undo here with crash blender even without changing values.\n", "GN: Crash on undo whenever a Group Input is present.\nOperating system: Linux-5.14.8-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.74\n\nBroken: version: 3.0.0 Alpha\n\nBlender crashes whenever undo is executed and a Group Input is present in Geometry Nodes.\n\n1. Open attached blendfile.\n2. Make a change (any change) in the GN tree and try to undo it.\n3. Should crash immediately.\n\nNote that it also crashes when you move the cube and then try to undo that action.[GN_Crash.blend](GN_Crash.blend)" ]

[ "Support Viewport roll - around the cursor position\nCurrently view orbit supports zoom-to-mouse-position as a way to rotate and zoom around the cursor position.\n\nView roll however always uses the view center.\n\nWhile low priority, this would be nice to support. See: #70761 (Roll View ignores Auto Depth)", "Regression: View jump randomly when zoom in and out with AutoDepth\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.93 0f7becece7\nWorked: 2.93 1a69d491e5 \n\nView jump randomly when zoom in and out with AutoDepth\n\n- Open Blender.\n- In Preferences->navigation->check \"Auto Depth\"\n- You should also enable Zoom to mouse position\n- Then in view port press num7 to go TopView. \n- Navigate mouse arrow to corner (for example) of default cube \n- Zoom in and zoom out.\n\nView will jump randomly\n\n", "Cycles: Normal Edit modifier after displace modifier does not with motion blur (Eevee seems fine)\nTried on multiple systems\n\nBlender 3.0 (And the previous beta builds)\n\nThe normal edit mode will not work with motion blur enabled\n\nSee attached file - Using a NormalEdit modifier looks correct in viewport then fails at render time if motion blur is used in combination with the attached Geometry Nodes tree that is displacing the main geometry over time. \nWith the node tree disabled the NormalEdit modifier works even with motion blur.\n\n**Viewport Result:**\n\n\n**Rendered Result:**\n\n\n\n**Demo file:**\n[Bug (1).blend](Bug__1_.blend)\n[#93700 Cycles Normals Motion Blur Displace.blend](T93700_Cycles_Normals_Motion_Blur_Displace.blend)", "'Frame selected' with 'Lock To 3D Cursor' sets weird focus\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0 Alpha\nand 3.1\n\nIf you select something and do 'view3d.view_selected' while View Lock is set to 'To 3D Cursor', the view will focus on the cursor instead of the selected object and if you pan and do 'Frame selected' again, you will get somewhere near the cursor instead of the selected object.\n\nAlso, calling 'view3d.view_center_cursor' won't do anything while 'To 3D Cursor is active'.\n\n1. activate 'Lock': 'To 3D Cursor'\n2. select an object\n3. View -> 'Frame Selected'\n[Video.mp4](Video.mp4)\n\n\n", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "Cursor Warped on Scale Cage Cancel Transform\nOperating system: Windows 11, Linux Zorin\nGraphics card: GTX 1060 MSI OC 3GB\n\nBroken: 3.3.x - 3.6.2 (Latest)\n\nCursor warp when i cancel resize operator using Scale Cage tool.\n\n1. Open Blender\n2. Activate Scale Cage tool from the toolbar\n3. scale anything, but cancel operation with RMB\n\n", "Addon: 3d Viewport Pie Menus. Press-move-release behaviour inconsistency\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\n\n\nBroken: version: 2.92.0 Alpha\n\nName: 3D Viewport Pie Menus (1, 2, 9)\nAuthor: meta-androcto\n\nIn pie-menus Option, who have additional menus do not react to fast action P-M-R or local hotkeys\n[2020-12-16_20-50-47.mp4](2020-12-16_20-50-47.mp4)\n\n- In sculp mode press W and then 2 or M\n", "Support dragging to change tabs in the side-bar\nNote, this was reported as a bug however it's a TODO (wasn't supported in 2.7x).\n\n----\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.39\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (version before the click transparent passthrought)\n\n\nCannot drag on the tabs to select other tab like normal tab behavior on Blender.\n\n- Factory defaults\n- Press 'N' on the 3D View.\n- Try to drag on the tabs on the \"WM_OT_context\", the result is the box selection.\n\nSee attached gif (ignore the mouse cursor offset, that is due to 4k display with only 125% scale applied.)\n\n\n\n\n", "Auto perspective desn't work in \"align to active\"\nOperating system: Linux-6.3.8-arch1-1-x86_64-with-glibc2.37 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.5.1\n\nAuto perspective behavior diverges between global and active view alignment.\n\n1. Start blender with default cube scene.\n2. Turn on \"auto perspective\".\n3. Press '7' on numpad to activate the orographic view from the top.\n4. Orbit the object to get back to the perspective view (auto perspective works fine).\n5. Select the cube and press \"shift+7\" to activate the orthographic view for the top of the active object.\n6. Orbit the object but the view doesn't change to perspective (auto perspective doesn't work here).", "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.", "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", "3D Cursor tool todo\nIn Blender 2.80, we now have a special tool for transforming the 3D Cursor. The issue is that it's not easy to move it visually, using gizmos, to set a certain pivot point for transforms. We can support this via a toggle in the tool settings, enabled by default for the 3D Cursor toolL\n\n\n\nThis makes it so you can reposition and rotate the 3D Cursor using gizmos, like so:\n\n\n\n---\n\n * - [ ] {icon circle color=green} Add button in the Tool Settings to reset the Cursor position to 0,0,0\n * - [ ] {icon circle color=green} Add XYZ controls for 3D Cursor next to it\n * - [x] {icon circle color=yellow} Add Rotation XYZ controls for 3D Cursor in the Sidebar, next to location.\n\n", "Transform cursor (patch included)\nRecently LMB-Drag was made to move the cursor *(edit, this has since been reverted)*.\n\nHowever this just moves the cursor under the mouse,\n\nit _could_ be useful to use transform here, it allows.\n\n- Drag, XKey to lock to an axis\n- ... Shift+Y to constrain to a plane.\n- ... Hold Ctrl to snap (snap to verts for example is handy)\n- ... Shift for more precise placement...\n... most other transform keys.\n\n\nOne reservation I have about this, is that you probably would often want to be able to snap to vertices and edges, and not have to depend on the current snap options in the 3d view header.\n\nSo we could override the snap options that transform uses.... but this seems a bit crappy too, since you may want to snap to faces in some cases, or even snap to grid.\n\nAs an alternative, we could just not bother attempting to integrate this with transform, and add snapping to the current modal operator (similar to how we have with the Ruler operator, which shares low level code with transform snapping)\nBut in that case we miss the axis constraints which seem like they would be nice to support.\n\n\nHere is a test patch to show how it works: [P87](P87.txt)\nNote, it crashes if you try to scale and its hard coded to LMB for cursor place, so its mostly a proof of concept.", "Blender 3.5: Cursor warping usable on windows remote desktop (RDP)\nOperating system: Windows 10 21H1 19043.2130\nGraphics card: GTX1650 4GB\n\nBroken: 3.5.0 Alpha, hash: 508fd044b44a\nWorked: 3.4.1, hash: ef9ca44dee7f\n\nI'm using Blender through Windows Remote Desktop (RDP) for quite a long time.\nNow in the new alpha 3.5 the Blender UI acts weird and non controllable anymore when using mouse middle click to pan viewport or left clicking into number fields to drag values up or down.\n\nAt this point for me Version 3.5 alpha is not usable anymore through an RDP connection - which is quite important for me! - while at least in Blender Version 3.4.1 everything worked fine!\n\n- Open blender from a Windows computer on another Windows computer via remote session\n- use {key MMB} to pan viewport or {key LMB} into number fields to drag values up or down.\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" ]

[ "3D Cursor is not in the right place after Shift + C (Center Cursor and Frame All)\nOperating system: macOS-11.6.1-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-16.5.4\n\nBroken: version: 3.0.0\nWorked: 2.93\nCaused by bda9e4238a\n\nPressing Shift+C resets the position of the 3D cursor and centers the view on the origin. However, if the camera doesn't get moved, the viewport doesn't update, so the 3D cursor appears to be in the wrong position.\n\n1. Hit Shift+C to center the camera and cursor\n2. Move the 3D cursor somewhere other than the origin\n3. Hit Shift+C again\n4. The 3D cursor doesn't visibly move.\n5. Move the camera\n6. The 3D cursor appears in the right place" ]

[ "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "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).", "Wireframe not visible with X-ray in weight paint mode.\nOperating system: Win10\nGraphics card: GTX 1070\n\nBroken: 3.0.0\nWorked: 2.93.6\n\nWireframe on other side of mesh can't be seen through faces when x-ray is enabled.\n\n[#94704.blend](T94704.blend)", "Sculpt mode: Pose brush with Face sets FK mode do not work with Multiresolution\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: 3.0 fresh alpha, 2.93.0\n\nAs title says. It produces weird results even with simpliest model.\n\n[face set FK multires.blend](face_set_FK_multires.blend)\n[2021-06-09_13-32-46.mp4](2021-06-09_13-32-46.mp4)\n\n", "Hair Curves: Posed hair curves get stuck onto a wrong pose upon entering and exiting Sculpt, Vertex Paint or Weight Paint mode on the surface object\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060 Super\n\nBroken: 3.6.1\nWorked: n/a\n\nOn posed hair when using the 'deform curves on surface' node, if you enter and exit Sculpt, Vertex Paint or Weight Paint mode on the surface object, the posed hair will get stuck on a wrong pose, see attached images for comparison. You don't have to edit anything for the bug to occur. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open the file and select the \"Surface\" object\n2. Enter and exit Sculpt, Vertex Paint or Weight Paint mode\n3. The hair curves object should now have deformed onto a wrong pose and can't be fixed until you reload the file\n\nThis bug still appears in the final render and can only be fixed by reloading the save file.\n\n", "Some Bones get slightly offset from Binding/Edit pose in Pose/Object mode\nOperating system: Linux-5.8.0-59-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 2.93.1\n\nAs per usual procedure of chasing out rigged character twitches (rest pose differences from edit pose), I've stumbled upon one that seems to have nothing but bone configuration as the source.\nChain of Bones in particular coordinates produces an offset at the last bone tail when switching to/from edit mode (constraints/animation erased).\nIt was a longer bone chain but those not affecting the result were deleted.\nRecreating bones from scratch in identical coordinates/rolls produced the same offset but in another direction.\nCalculation precision insufficiency?\n\n[stretch1.blend](stretch1.blend)\n - Open,\n - Switch to/from Edit/Pose or Edit/Object modes.\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", "\"Shape Key Edit Mode\" toggle for correct mesh deformations\nWhen using the toggle \"Shape Key Edit Mode\" it gives me a representation of all shapekeys mixed together but it's only a visual preview. \n\n\n\nIt doesn't affect the result of rotating or scaling the mesh since you still only work on the shapekey that is selected instead of the mixed representation that is shown. \nAnd since it's all just based on vertex location the results can be pretty odd, especially when using the 3D cursor as a pivot point. \n\n[2019-07-15 11-23-25.mp4](2019-07-15_11-23-25.mp4)\n\nSince working with multiple shapekeys is a great way to work non-destructively it would be a big improvement if the mixed shapekey representation would also be used for any deformations made.\nThis could be by default or as an additional toggle.", "As a user I would like the option *add* to my existing pose with the Pose Library instead of *replacing* it.\nCurrently with the pose library, I can select some controls and then blend to a new pose. This is very handy for many cases, but sometimes you may want to use a pose in an additive method.\n\nTwo example use cases.\n\n1. I have a frame where I've posed my hand to look like a loose fist and now I just want to squeeze the fingers together a bit more. I have a pose in the library called \"finger squeeze\" where each finger finger is just brought together in a single axis. With the current library, if I drag on the finger squeeze pose it would **blend to** that finger squeeze pose.. removing the loose fist. If we add the ability to **add** to the pose instead of replace, then I could keep my fingers in this loose fist, but additively squeeze them together. \n2. I've posed my character's face in a worried expression and now I want to slightly lift the brows higher. With an **additive** mode to using the pose library, I can go to the \"brow raise\" pose and raise the brows w/out them loosing the worried shape. ", "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 In Front/Visible option to lasso and box mask tools\nCurrently Box Mask and Lasso Mask create the mask through the object, which is not useful in some cases. There should be an in front option to change this behavior. \n\nImplementing this by checking the vertex normal and view direction is trivial, but it won't work as expected on models with occluded vertices facing toward the view. We should evaluate if it is possible to implement vertex occlusion test in sculpt mode. If it is not, then we can use the vertex normal implementation. ", "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", "Active pose bone override not taken into account in bpy.ops.constraint.move_up()\n`bpy.ops.constraint.move_up(ctx, constraint=\"FOOBAR\", owner='BONE')` returns cancelled if the Pose Bone is not the active bone, despite all related context members are overriden:\n\n```Py\n ctx = bpy.context.copy()\n ctx['constraint'] = con\n ctx['active_bone'] = bone\n ctx['active_pose_bone'] = pbone\n ctx['selected_bones'] = [bone]\n ctx['selected_pose_bones'] = [pbone]\n ctx['selected_editable_bones'] = [pbone]\n```\n\nIt only works if the corresponding bone is really made active using `ob.data.bones.active`\n\n\nSample setup: [bug_active_pose_bone_override.blend](bug_active_pose_bone_override.blend)", " LineArt: (Collection) Issue for Cameras in Orthographic View\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nChecked in Blender version 3.4.0 Apha, commit date: 2022-10-08 02:26 - same issue\n\nFor orthographic Camera without any shifts - Line art modifier (for a Collection) showing lines for objects behind other objects - which otherwise should not be visible. And some lines are not visible which should be.\nHappens with contours option in the Line Art modifier. Slight rotation on z axis solves the issue.\n\nNoticed issue with some specific frames on my complete blend file.\n\nOpen attached blend file and go to front orthographic view.\n\n[BugReport01.blend](BugReport01.blend)\n\n", "Bone Override Transform affects bone local axis display.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nWhen a bone gets assigned a display transform override, it's viewport display axis gets transformed, which probably shouldn't happen as its purpose is to display the Bone's not it's Shape's local axes.\n\n[override-transform.blend](override-transform.blend)\n - Remove Override Transform from Bone's Viewport Display's Custom Shape -> Displayed Bone's axes change location." ]

[ "Difficult selection of bones with custom shape from Empty\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.2.1\nWorked: 3.1.x\n\nIt is now more difficult to select a bone that has a custom shape from an Empty.\nThis was not happening in Blender 3.1.\n\nOpen the file with Blender 3.2, and try to select the circle bone in the middle without changing the camera angle.\nIn fact, it seems you can select the bone only when it has on a certain camera angle.\nDo the same in Blender 3.1, and you'll find that you can easily select the bone.\n\nBlender 3.2\n\n\nBlender 3.1\n\n\n[empty_selection_bug.blend](empty_selection_bug.blend)\n", "Regression: Bones using Empties as Custom Shapes cannot be selected properly\nOperating system: Win 10 Home 64 bit\nGraphics card: Nvidia Geforce 1050 Ti\n\nBroken: 3.2\nWorked: 3.1.2\n\nCaused by 3267c91b4d\n\n\nIf you use an **Empty** instead of a **Mesh** (with the same shape) as the **Custom Shape** for a Bone, as of version 3.2 (and still in 3.3 alpha) the bone cannot be selected properly in Pose Mode.\n\nIts selection hitbox seems to only cover the original shape of the bone instead of the shape of the Custom Object as you would expect, ie if you set a Cube empty as the custom shape you still have to click where the actual bone is to select it, instead of clicking on the edges of the Cube shape. If you use a Cube mesh instead of an Empty as the Custom Shape it behaves normally and you can select by clicking on the visible custom shape. In 3.1.2 it did not matter whether you used an Empty or a Mesh for the Custom Shape.\n\n**Steps to reproduce**\n- open .blend file\n- Try selecting bones where empties are used as custom shape\n[empty_vs_mesh_customshapes.blend](empty_vs_mesh_customshapes.blend)\n[emptyshape_bone_selection_01.mp4](emptyshape_bone_selection_01.mp4)" ]

[ "Texture Node Editor defaults to empty value\nOperating system: Linux-4.19.33_1-x86_64-with-glibc2.9 64 Bits\nGraphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\n\nBroken: version: 2.80 (sub 54)\nWorked: (optional)\n\n\nWhen switching to the texture node editor, it defaults to an empty texture type.\nAdditionally, the \"World\" texture type is missing the texture selection list at the top, so no texture can be manipulated or created.\n\n- Switch window to Texture Node Editor > No Type is selected\n- Switch to \"World\" Texture type, texture selection and creation is missing in the header\n", "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)", "Geometry Nodes: Mismatching data types connections work differently from other node editors\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\nFloat math node overrides color data, even though it is muted. Same setup works in shader editor without problems.\n\nOpen file and activate *Viewer* in GN. Expected result: colored output (judging by shader area behavior)\n\n", "GPencil: Missing functionality in Vertex Paint mode Selection tool (left-click-select)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nWhen Points select is enabled in Vertex Paint mode, the Selection tool doesn’t behave like in Edit mode:\n- it cannot select a single vertex,\n- a left click away from points doesn’t deselect them.\n\nAdditionally there is no color picker when this tool is selected, so if you select some points to use the Set Color Attribute operator on them, you can’t see the current color or choose a different color, unless you switch to a different tool.\n\nMake sure you use Left Click Select in Preferences > Keymap\nAs shown in video, open any stroke in Vertex Paint mode, enable Points select and select the Selection tool.\n- You can box select points but can’t left click on a point to select it and you can’t click away to deselect points.\n- There is no color picker.\n<video src=\"attachment\" title=\"Selection Bug-1.mp4\" controls></video>\n\n", "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", "Color attributes difference between vertexpaint and sculpt modes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Beta\n\nColor attributes difference between vertexpaint and sculpt modes\n\n[vertex_paint_geo_nodes.blend](vertex_paint_geo_nodes.blend)\n\n- open the included blend file and try to remove the instance objects from the geo nodes (The objects are linked to a color attribute. Using white color to add the objects and black to remove them)\n- when using vertexpaint mode, several pure black strokes are required\n- when using sculptmode paint tool, trees vanish on the first black stroke stroke- when i open blender 3.1 it works fine. \n\n\n\n", "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", "Texture paint in viewport is not using the color space of the image.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nIf you paint a noncolor texture like a normal map, painting it directly in the 2D image correcly uses the non-color space, but painting in the viewport doesn't.\n\n\n- With any non-color texture, try to paint both in viewport and in the 2D image\n[2022-02-15 10-34-07.mp4](2022-02-15_10-34-07.mp4)\n\nAditional note: This seems to happens when you sample from the 2D image. By contrast, if you sample the color from the 3D view, you can correctly paint on it, BUT in the 2D viewer the color becomes brighter.", "\"Regression\" : Using normal or bump maps in cycles produces flat washed-out shading (caused by terminator softening)\nOperating system: Windows 10 x64\nGraphics card: GeForce GTX 1660 Dual OC\n\nBroken: 2.81, 2.82, 2.83 from 2020-03-06 22:46\nWorked: 2.80\n\nCaused by c3be14e151\n\nUsing normal or bump maps in cycles produces flat washed-out results comparing to EEVEE.\nThe bug also appears in the latest 2.83 build, it affects both Diffuse and Principled Shader but not Glossy.\nNormal Map and Bump nodes seem to produce identical results with the 2.80 version, so the problem lies with the Shader node itself.\n\n\n[bug_report.blend](bug_report.blend)\n1. Open file\n2. Switch to Rendered viewport shading", "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", "Image Editor don't change to active texture if there is one texture node in material \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.4.0 Alpha\n\nWhen there are two texture nodes in Shader Editor Texture Editor switches to the active texture when you clicks on any Image texture node. But when there is only one texture node Image Editor ignores selecting that node. It makes it inconsistent and may confuse user with showing him the wrong texture\n\n\nCreate two materials. In one of them create one image texture node and a texture. In second one create two or more image nodes with textures. Try to switch between materials and texture nodes.\nOr open blend file.\n[texture-pick_bug.blend](texture-pick_bug.blend)", "Not possible to add keyframes to HSV values.\nOperating system: Linux-5.15.76-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: Mesa Intel(R) Graphics (ADL GT2) Intel 4.6 (Core Profile) Mesa 22.2.1 & NVIDIA GeForce RTX 3050Ti Laptop GPU 520.56.06\n\nBroken: version: 3.3.1\n\nIt is not possible to add keyframes to the HSV values of any color picker.\n\nOpen a new file. Go to the material tab of the default cube. Right-click in any of the HSV values of the Base Color picker tool.\n\n", "After setting a shortcut for the \"Auto Keyframe\" button, there is an exception in the status display.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\nWorked: none\n\nSee below\n\nUse right click->assign shortcut key\nCreate a shortcut for the auto keyframe button e.g. ctrl+alt+n\nThen test the shortcut in a different viewport and you will see that it looks like nothing is happening.\nBut,**The auto keyframe state is actually changed**, but the button display is not refreshed, and the button dispaly state is changed only when the mouse moves to the timeline window.\n\n", "Diffuse Light pass not working as expected in 3.2 Eevee with 'shader to RGB'\nOperating system: macOS-12.4-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.2.1\nWorked: 3.1\nAffected by 80859a6cb2\n\nDiffuse light pass does not work on shaders using 'shader to rgb' node and just comes back blank. it will severely limit the use of compositor with simple NPR style shaders if so. Unless there is a new approach to this node setup I'm not aware of. Other NPR shaders with a colour component also get lost when going between passes.\n\nAttached blend file has simple toon shader. When going from 'combined' pass to the 'diffuse light' pass all information is lost. Not able to isolate the passes that makes up the 'combined' pass for compositing etc.\n\n[3.2shadertest.blend](3.2shadertest.blend)\n\n\n\n\n\n\n\n", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n" ]

[ "Material animations not update during animation playback.\n**Windows 8, 64bits. Nvidia gtx 460 se**\n\n**2.72 eb464ee**\n\n**In blender Cycles engine, Material Viewport, Blender not update the color animation or any other animations made in Nodes material.\nAfter press Alt+A and stop animation the color is not changing at all.\nBut would be very helpful if the color is updating during animations. Is very hard to make animations colors without to see in real time.\nThank you.**I put a blend file.**In Cycles engine, Create new material and over color press right click and \"Insert Keyframe\" then go other frame and chose other color and \"Insert Keyframe\". Then play animation with Alt+A and the colors not update during the animation **\n" ]

[ "When using mask modifier, particles get also generated from the origin\nOperating system: macOS-10.14.4-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.23 355.11.10.50.10.103\n\nBroken: version: 3.0.0\n\nI'm emiting particles from an object. I use the mask modifier so that the particles are generated only in some areas. Particles will be generated from the origin, even if there's no geometry there.\n\nPlay the animation from the attached file. You will see a column of particles coming from the origin. \n\n[Bug.blend](Bug.blend)\n", "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>", "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)", "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", "Retopology: Active Object Geometry gets Occluded by Semi-Transparent Reference Object in Edit Mode\nOperating system: Linux Ubuntu 16.04\nGraphics card: Nvidia GeForce MX130\n\nBroken: 2.83.0\nWorked: 2.82.a\n\nActive mesh is occluded by high poly or another reference mesh in Edit mode. This is: I want to edit mesh A. I need mesh B to get a reference. So I make B to have a semi-transparent material for Viewport view. I select A and go to Edit mode to edit it. However, its edges and vertexes are occluded by B. We can see a comparison of 2.83.0 (first image) with 2.82a (second image): version: 2.83.0 does not show active object geometry so that we can not edit it. On the other hand 2.82a does show required geometry.\n\n \n\n1. Open Blender 2.83.0\n2. Create a Sphere mesh in the world origin so that it fits inside the default cube.\n3. Assign a semi-transparent viewport display material to the Cube so that we can see the Sphere inside. Change color also to have a better view.\n4. Select Sphere and go to Edit mode.\n5. Press A to select all vertexes.\n6. We can see that Edges and Vertexes are occluded by the Cube so that we can not edit the Sphere properly.\n\n\n[bug-report.blend](bug-report.blend)\n", "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", "Geometry node don't expose materials to the solidify modifier\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060\n\nBroken: blender-3.1.0-beta+v31.93cc89247010\nWorked: 3.0.1\n\n\nWhen using a geometry node to generate a mesh, and then applying a solidify modifier to it, the materials are not properly exposed and not or wrongly assigned to the final mesh\n\n- create a plane\n- go in edit mode and delete all the mesh data\n- back in object mode, add geometry node modifier\n- add a Cylinder mesh primitive, and set its fill type to None\n- add a Join Geometry node and plug the Group Input Geometry socket and the Cylinder node Mesh socket into the Join node\n- plug the join node into the output\n- add 3 materials to the object and set different colors\n- add a solidify modifier and set material for offset and rim to indices 1 and 2\n\nThe resulting tube doesn't show any of the materials.\n\n- go in edit mode and add at least one vertex to the mesh\n\nNow the resulting tube displays the last material of the list on some parts, but this is still not it.\n\n- Instead of creating a cylinder in the geometry node tree, plug a Mesh circle primitive\nThen add a screw modifier to extrude it, after the geometry node modifier and before the solidify modifier\nSet its angle to 0° and Screw value to 1\n\nNow the resulting tube is only displaying the first material\n\n- Go in edit mode and add at least one vertex to the mesh\n\nNow the resulting tube displays all the materials properly.\n\nNote : it is not obvious, but it is mandatory to join the original geometry into the end result to get the materials correctly propagated to the output.\nMaybe this could be more clearly explained or simplified somehow.\n\nSample file here reproducing all cases mentionned above :\n[solidify_material_bug.zip](solidify_material_bug.zip)", "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?", "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", "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 ", "Boolean modifier - Intersect option - not working / artifacts while doing 3D Sectioning\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0 Beta\nWorked: in Blender 2.92\n\nStrange artifacts using 3D sectioning using Boolean modifier - Intersect (see sectioning animation issues below)\n\nExpected behavior:\n3D slice working correctly in Blender 2.92 (to view internal section of object)\n```\n-Create Mesh Plane (larger than object)\n-Select Plane - Add Boolean Modifier \n\tOptions - Intersect\n\tObject - STL or Object\n\tSolver - Exact\n\n```\n\n\nActual behavior:\n3D slice issues using Blender 2.93 beta (to view internal section of object)\n1) Not showing object as a 3D section like in 2.92 (see animation above)\n2) Artifacts Showing up when moving cutting plane back and forth (see animation below) \n\n\n\n\nIn the blend file, move the `Plane_xy` along the z axis, or move the `Plane_xz` along the y axis.\n[section.blend](section.blend)\n\n", "Applying Subdivision/Multires Modifier De-merges UV's\n### Update\n\nThe issue of custom-data (UV's specifically) becoming detached remains, this problem existed before b88dd3b8e7, it was just less obvious since selection connected near-by UV's. Now UV's are merged by default at a very low threshold when applying modifiers to mitigate the problem. Keeping this report open as it would be good if subdivision-surface didn't separate UV's, replies to this report contain some notes that could lead to a solution. In practice users should not experience problems caused by this behavior, so marking low priority. ~ @campbellbarton.\n\n----\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha \nWorked: working in 2.90 \n\nCaused by b88dd3b8e7\n\nWhen applying a subdivision modifier, certain UV's points disconnect from their neighbors. This does not seem to occur with the F3 menu subdivide operation.\n\n- Open default blender scene.\n- Subdivide cube - 1 level and apply it. Do this step 4x\n- In the UV editor use \"Alt select\" to select face loops at random.\n- Alt click around until a face loop is not fully completed, this will reveal unmerged vertices.\n- Check area that did not complete by moving faces, vertices, edges etc to confirm unmerged UV's.\nThis does not seem to be an issue with the newly added 9a52b30cc0 in my eyes, rather an issue with subdividing.\n[UV Disconnect.blend](UV_Disconnect.blend)\n\n", "Modifiers after physics ones shouldn't invalidate cache\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\n\nIn current Blender, any change on modifiers invalidates.\nModifiers *after* physics modifiers won't affect the result of physical simulation, therefore they shouldn't invalidate the cache. \n\n\n1. Create a plane\n2. Give it Cloth and Subdivision modifiers, in this order\n3. Set the end frame to 10\n4. Play animation until the end\n5. Stop animation\n\nNow the simulation is cached.\n\n6. Change the viewport division level on Subdivision modifier\n\nNow the cache is invalidated.\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", "Viewport display: in front should be listed under visibility as it also affects final render\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nUnder object properties, viewport display: in front affects both the visibility in the viewport and in the final render, and as such should probably be listed under visibility rather than viewport display.\n\n-" ]

[ "Sub-division modifier is not displaying anything\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14830 Core Profile Context 21.10.02 27.20.21002.112\n\nBroken: version: 3.4.1\n\nSub-division modifier is not displaying anything when previewing, it only displays subdivision after applying.!(https://)\n\nadd subdivision modifiet to anything\n\n", "Object with Subdiv Modifier turns into a line in the viewport.\nSystem Information\nOperating system: Microsoft Windows 10\nGraphics card: AMD Radeon RX 550\n\nBroken: 3.1.0\nWorked: 3.0.0\n\nBug description:\nWhen Subdiv Modifiers are applied to objects, they turn into a line in the viewport. (However, this is not the case in rendered mode.)\nInstead, of course, it needs to add more polygons to make the object smoother.\n\n\nSteps to replicate:\n\n- Start a new scene, or open one of your own. It matters not.\n\n- Apply a Subdiv Modifier to the default cube or any 3D object in your scene.", "A disaperring trick\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) RX Vega 10 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.44.05 27.20.11044.5003\n\nBroken: version: 3.1.2\n\nSo while i was on blender following a tutorial I activated the subdivision modifier and when I clicked the computer icon on it to see the change from adding the modifier, The torus disapeared.\n\nFirst create the torus shape at 1m scale and other doughnut like shaping, then add the subdivision modifier and when it loads have the computer icon lit up blue and the shape disappears\n", "Problem with Subdivision Surface in Blender 3.3\nOperating system: Windows 10\nGraphics card: AMD R9380X\n\nBroken: 3.3\nWorked: 3.2\n\nAs soon as I updated to Blender 3.3, I noticed some objects that were were gone. After some searching I understood that only those that had Subdivision Surface modifier were gone. And if I turned the modifier off in viewport, they would appear again. \n\nSubdivision visibility in viewport turned off.\n\n\nSubdivision visibility in viewport turned on.\n\n\nAlso after I applied the modifier, the objects would behave normally.", "error en Subdivision Surface\nOperating system: Windows-10-10.0.15063-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R9 360 ATI Technologies Inc. 4.5.13476 Core Profile Context 22.19.172.769\n\nBroken: version: 3.1.2\n\n\nCuando aplico el modificador **Subdivision Surface** solo se ve una linea en el viewport.\n\n\n\n\n", "The surface subdivision modifier does not work\nOperating system: Windows 10\nGraphics card: Radeon RX550/550 Series\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nBlender Version 3.4\n\nI create a model, apply a surface subdivision modifier to it, and everything disappears for me\nCreate a cube and try to apply the surface subdivision modifier\nBased on the default startup or an attached .blend file (as simple as possible).\n \n\n", "Surface Subdivision problem\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 3 Graphics ATI Technologies Inc. 4.5.148201 Core Profile Context 20.50.02.08 27.20.15002.8001\n\nBroken: version: 3.2.1\n\nWhen I try to apply the modifier Surface Subdivision to an object, the object just disappears.\n\n", "Subdivision Surface\nOperating system: windows 10\nGraphics card: vga 2gb\n\nBroken: when I create a cube object and then give the effect of \"subdivision surface\" the object immediately disappears. can appear after pressing apply, even though it shouldn't be pressed apply can be seen\nWorked: (newest version of Blender that worked as expected) 3.1.2\n", "Subdivision modifier is broken in this AMD card\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.13476 Core Profile Context 22.19.171.1024\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 2022-03-20 12:59, hash: b9123b806f\nWorked: (newest version of Blender that worked as expected) Blender 3.1.0 Alpha\n\nSubdivision modifier is broken in this AMD card, may be in some other AMD card as well?\n\n\n- Check the video below\n- I have tried this with Nvidia card but it is working correctly.\n- I have the latest drivers as well.\n\n[subdivision modifier_broken_10001-0349.mp4](subdivision_modifier_broken_10001-0349.mp4)", " Subdivision modifier doesn't work right on 3.2\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009\n\nBroken: version: 3.2.0\nWorked: 3.0\n\nSubdivision modifier doesn't work right on 3.2. (Same problem on 3.1 as well).\nWhen I add the subdivision modifier to any object, instead of subdivide it, it just makes the object appear invisible in the viewport.\n\nAdd any object and just add a subdivision modifier to it.\n[Subdivision_test.blend](Subdivision_test.blend)\n\n", "Subdivide will mess up the mesh\nOperating system: Windows 11\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nWhen i click subdivide on ANY model or shape, it will become invisible and if you see the mesh it looks like it was all collected in a diagonal line.\nBased on the default startup or an attached .blend file (as simple as possible).[untitled.blend](untitled.blend)", "GPU subdivision doesn't work on Radeon(TM) RX 460\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon(TM) RX 460 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.1.0\nWorked: version 2.9.3\n\nSubdivided model doesn't look correct in object/edit mode. When applied subdivision modifier work as expected. Haven't used blender for a while, so I don't know if GPU subdivision is new feature, so take \"Worked: version 2.9.3.\" with a grain of salt.\n\n17434c2c06fbccf1883c7ccff5099a8a\n\n\n1. Open default startup file\n2. Add subdivision modifier to Cube\n\n\n", "Subdivision surfave modificator bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 21.5.2 27.20.14540.4003\n\nBroken: version: 3.1.0\n\n[object transforms to one line in every preview expect render prev and render]\n\n[when using subdiv odject transforms into one line when is not selected. In render it is visible]\n\n", "Regression: Mesh geometry is broken with GPU subdivision\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: master, 3.1.0\nCaused by 118a219e9d\n\nMesh geometry collapses with subdivision surface modifier.\nIssue only appears when GPU subdivision is enabled\nWorked on Integrated Intel GPU: `Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7323`\n\n- Open .blend file\n- Enable GPU subdivision\n[gpu-subdiv.blend](gpu-subdiv.blend)\n\n| Solid Mode | Wireframe |\n| -- | -- |\n|  |  |", "Using the \"surface subdivision\" modifier the object disappears\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) RX Vega 10 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.36 27.20.11036.3\n\nBroken: version: 3.1.0\n\n[Applying surface subdivision over any chosen object is not applied correctly, only a diagonal segment will be displayed within the object]\n\n[I add a monkey, from the properties of the modified I insert subdivision of the surface and set vision of level 1-2.\nThe object disappears and only one segment is created within the object.]\n[Baco.blend](Baco.blend)\n\n\n\n\n\n\n\n\n\n\n\n", "Error modificador de subdivision\nProcesador Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz 3.GHz\nMemoria Instalable (RAM): 32,0 GB (31.7 GB utilizable)\nSitema Operativo de 64 bits, Pocesador x64\n\nOperating system: Windows 10 Enbterprise\n\nBroken: (3.1.2 ultima versión descargable en blender org )\n\n\nCuando le pongo un modificador de subdivisión a cualquier geometría, toda la maya se comprime en una línea diagonal en el caso de un cubo por ejemplo \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nSimplemente abro un archivo desde cero y le coloco modificador de subdivisión al cubo que aparece por defecto", "Since Blender 3.0 when I use the subdivision modifier the mesh disappears from the screen.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.13560 Core Profile Context 26.20.11030.22001\n\nBroken: version: 3.5.0 Alpha\n\n[Since Blender 3.0 when I use the subdivision modifier the mesh disappears from the screen. I have to use the Geometry nodes to be able to visualize the mesh. {[F14233741](0001-0883.mp4)}]\n\n[When I use the subdivision modifier.]\n\n", "error subdivide surface\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 3 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12036.1\n\nBroken: version: 3.1.2\nWorked: (version: 2.93.2)\n\n[when applying subdivide surface to an object it disappears]\n\n\n", "Subdivision Modifier Broken\nOperating system: Windows10\nGraphics card: Radeon R9 390 (X2)\n\nBroken: 3.2.0 Alpha AC3F4DB71945 2022-02-25 22:47\nWorked: 3.2.0 Alpha 7D7DD66BA78F 2022-2-24 21:51\n\nSubsurf modifier seems to be collapsing vertices?\n\nJust add a Subsurf modifier to the default cube and it seems to disappear, but if you go into edit mode and enable the transformed cage on the modifier tab the vertices appear to have collapse in a weird way.\n\nI've also deleted my blender build folder and rebuilt but the issue remains\n", "Subdivision Modifier and visibility of Objects\nDevice name\tDESKTOP-UT256NR\nProcessor\tAMD Ryzen 3 3200U with Radeon Vega Mobile Gfx 2.60 GHz\nInstalled RAM\t8.00 GB (5.92 GB usable)\nDevice ID\t6A18E30F-412F-4DA1-A501-C3A7446ABFB0\nProduct ID\t00325-81651-00692-AAOEM\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen and touch support with 10 touch points\n\nBroken: version: 3.1.0\n\n\nBlender 3D\n\nI have uploaded the latest version of Blender 3.1.\n\nWhen I opened Blender 3.1 and loaded the last file I created using Blender 3.0.1 the following happened: \nSeveral objects of the Scene did not display although all the Scene information was intact. (see Fig 1)\n\nAfter a few experiments I discovered that the missing objects re-appeared when the Subdivision Modifier was applied to the Object or the 'Display Modifier in viewport' was toggled OFF (Fig 2 ).\n\nThe object remained invisible in Render until the Subdivision Modifier was actually applied to the object or the button 'use modifier in Render' was toggled OFF (Fig 3).\n\nI believe that previous versions of Blender did not require the actual application of the Subdivision Modifiers to the object for Viewport or Render.\n\nThis leads me to ask: “Is there an Order and Timing when one should Apply the Modifiers to the Object?”\n```\n\n```\nAnother issue that I ran into was that the Background of the Render is red meaning it is missing something or needs some adjustment. I never encountered this in the older versions, I still have not found what I must do to correct this.\n\nHas anyone else experienced these situations? Was it something the Blender team intended for Blender 3.1?\n\nSeveral .png screen prints are included to present the situation of my encounter.\nComments and suggestions will be appreciated.\n\n\nFig 1 – file originally created using Blender 3.0.1 opened in Blender 3.1\n\n\n\nFig 2 – Realtime 'Display Modifier in viewport' toggled OFF\n\n\n\nFig 3 – Render with 'use modifier in Render' button ON\n\n\n \nFig 4 - Render with 'use modifier in Render' button OFF\n\n", "Subdivision it's not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800M ATI Technologies Inc. 4.5.14739 Core Profile Context 21.20.01.24 27.20.22001.24003\n\nBroken: version: 3.1.0\n\nsubdivision it's not working\n\n\nI create an object and then I click in [modifier properties-Add modifier-subdivision surface] and they delete the object\n\n\n", "Subdivision surface modifier hides/removes the mesh from view\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon R5 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.2.1\n\nsubdivision surface modifier hides the mesh\n\nopen blender \nadd subdivision surface modifier to the cube or any mesh for that matter \nmesh disappears\n\n\n", "Subdivision delete my figures\n\nOperating system: Windows 10\nGraphics card: 2gb envidia\nNombre del dispositivo\tLAPTOP-CHFB493Q\nProcesador\tIntel(R) Core(TM) i5-10210U CPU @ 1.60GHz 2.11 GHz\nRAM instalada\t8,00 GB (7,83 GB utilizable)\nTipo de sistema\tSistema operativo de 64 bits, procesador x64\n\nBroken: 3.1.2\n\nwhen a put the modifier subdivision to my figures that is deleted.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n", "when i add a subdivision modifier in an obeject it disappears \nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R7 200 Series Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.09.08.04 27.20.14540.4003\n\nBroken: version: 3.2.1\n\nwhen i add a subdivision modifier to an object, the object just disappears from the solid mode. but i can still see it in render mode and edit mode.\n\nopen blender, add any object and add a subdivision modifier\n\n", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "Subdivide surface modifier does not work\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 20.45.44 27.20.14544.6\n\nBroken: version: 3.1.2\n\n[I open Blender, apply the subdivide surface modifier to the cube that comes by default and it doesn't work]\n\n\n\n", "objects become invisible with subdivision modifier before it is applied\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nCPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz 3.60 GHz\nGraphics card: AMD Radeon (TM) R9 200 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n(my GPU is not recognised by blender and therefore does not work for blender)\n\nBroken: version: 3.3.0 Alpha\n\nwhen adding a subdivision surface modifier to a primative object, it will remove the object from view port however the object is still there. then looking at the object through the rendered viewport it shows up in its subdivied state. \nhowever, in edit mode, if the modifier is applyed then the object shows up again. \n\n\nopen blender\nadd cube (or any primative object)\ngo to modifier stack and add \"subdivision surface\" modifier\n(at this point the object disapears)\nthen apply modifier and it shows agian\n\n[subdivied_issue.blend](subdivied_issue.blend)\n\n{[F13251345](image.png), size=full}\n\nthanks!", "When using Subdivision Surface Modifier, the object in question disappears\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon R5 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.1.0\n\n It worked fine on 3.0.1\n\n\n\n\n[When using Subdivision Surface Modifier, the object in question disappears, and I tried to restart, but not worked either. In fact, just starting Blender, the first thing I try to do was use the modifier on the default cube, but dont work. \n\nWhen I use the previous version, the modifier work fine, has always. ]\n\n\n[Just use the Subdivision Surface modifier on the default cube of Blender 3.1]\n[It happen on the start of Blender, and on any files I have]\n\n", "Subdivision surface\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 3 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.3.1\n\nWhen I add the subdivision modifier my mesh disappears. \n\nPut the mentioned modifier on a mesh.\n\n", "bug in subdivide surface modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.13560 Core Profile Context 26.20.11028.0\n\nBroken: version: 3.3.0\n\n[when using the \"subdivide surface\" modifier the selected object that I am working with disappears and makes it impossible for me to continue working on it]\n\n[1-add object\n2-add modifier\n3-subdivision surface\n\n" ]

[ "\"New Image\" UI improvement\nNOTE: This design is still under discussion and is incomplete.\n\n# Current Issue\n\nThe UI for image creation in Blender doesn't make it very easy to pick an optimal resolution and could be improved for usability.\n\n\nExperienced Blender users might know that you can:\n- Drag over both fields to edit both at the same time\n- Type `*` or `/` to multiply or divide the resolutions to keep standard resolutions\n\n# Proposal\n\nWe need to make these options more obvious and readily available:\n- Add a dropdown for common resolutions (128,256,512,1024,2048,...)\n- Add a toggle to either keep image square. When disabled choose resolution for both dimensions.\n- Add an option to type in a custom resolution\n\nThis still needs mockups and further discussion.", "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)", "AutoDepth ignores texture transparency\nOperating system: Win 10 64-bit\nGraphics card: 980 Ti\n\nBroken: 2.93.4 LTS, 3.0 alpha (including current latest build)\nWorked: 2.79\n\nWhen navigating using mouse with auto-depth enabled, the full-transparent parts of textures should be ignored when picking the depth.\nThis worked correctly in 2.79, but 2.93 and the latest 3.0 alpha seem to ignore this.\n\n\nEnable Auto-Depth, create an object, assign it a material with some full-transparent texture, then try to zoom / pan using mouse with the cursor on it.\n[autodepth-transparent-issue.blend](autodepth-transparent-issue.blend)", "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", "Viewport display: in front should be listed under visibility as it also affects final render\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nUnder object properties, viewport display: in front affects both the visibility in the viewport and in the final render, and as such should probably be listed under visibility rather than viewport display.\n\n-", "Custom Properties Improved UI\nCurrent UI:\n\n\n\n- [ ] Allow reordering of custom properties in ways that make the most sense to an artist\n- [ ] Allow editing from the sidebar\n- [ ] Decrease the space between properties\n- [ ] Using an 'X' icon to delete\n- [ ] User and edit icon instead of \"Edit\"\n- [ ] Better location of icons\n- [ ] Group properties by the selected object/bone (see image)\n- [ ] Add a drop-down to select the data type\n- [ ] Allow the use of checkboxes to represent booleans\n\n", "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", "SpaceView3D.draw_handler_add with PRE_VIEW draw type does not result in visible draws\nOperating system: MacOS 11.6.3, Ubuntu 18.04 LTS (issue exists in both)\nGraphics card: Intel UHD 630, Nvidia Quadro RTX 400 (issue exists in both)\n\nBroken: 2.93 LTS, latest master (b626edd751d64b269da12ef8e774ced2836c3c9e)\nBroken: 2.83.0\nWorked: 2.82\n\nBroke between good 189e96ba68 and bad d95e9c7cf8\n\n1. Startup Blender\n2. Go to scripting tab and create a new script\n3. Copy \"Triangle with custom shader\" code from: gpu.html\n4. Change draw_type param in draw_handler_add from\n```\n'POST_VIEW'\n```\nto\n\n```\n'PRE_VIEW'\n```\n5. Run script.\n\nExpected behavior:\nThe drawn triangle is visible.\n\nActual behavior:\nThe drawn triangle is not visible.\n", "4090 has problem with texture in render preview\nOperating system: Windows 11\nGraphics card: Nvidia Geforce 4090\n\nBroken: (3.4 and 3.5.1)\nWorked: none.\n\n**Short description of error** \nThis only started recently, has been fine up till today. My preferences are set to use both the CPU (AMD Threadripper 32) and the GPU (geforce 4090) in OptiX (or CUDA, doesnt seem to matter). Once the file opens, material preview works fine. (refer to \"materialpreview.png\") but when i click render preview (refer to renderprevier.png) all i see is my rig. Anything with a texture is a similar dark grey as the default blender background. I can move the camera around fine, but no textures are visible. If i click material preview again to switch back, blender freezes and must \"end task\" in task manager. If i turn off the GPU assistance and only have the CPU enabled, everything works as it should. \n\nYesterday i updated to latest windows 11 update. I also updated my gameready drivers for my 4090. When the issue started, i thought it might have something to do with gameready drivers so switched to Studio drivers. This did not fix it. \nAssuming that these updates may have broken my file, i rolled back windows 11 drivers to most recent previous version, and did the same with the nvidia studio drivers (uninstalled 5.35.... installed 5.31). This fixed nothing.\n\nI would love to know why my GPU can't be used with Blender suddenly. Games work fine. Furmark 3d app works fine, no issues. Heat is fine. Very frustrating to have such expensive gear suddenly stop working.\n\n", "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", "Color attributes in sculpt mode not showing in instance objects\nOperating system: Linux-5.15.0-47-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.226.00\n\nBroken: version: 3.4.0 Alpha\n\nWhen sculpting an object its instance reflect the changes after the stroke, but not with color attributes, you have to go out of sculpt mode to see the color attributes.\n\n1. Open a new sculpt file.\n2. Make and instance in object mode with Alt D\n3. Enter sculpt mode of the original object.\n4. Paint some color attributes\n5. Sculpt with clay brush to see the expected behavior.\n\n[Grabación de pantalla desde 17-09-22 16:08:53.webm](Grabación_de_pantalla_desde_17-09-22_16_08_53.webm)\n\n\nOne funny thing is that if you give the original object a mirror modifier, the changes to the instance are in real-time, not after the stroke, both for sculpt and for paint. But not when you sculpt or paint in the one without the modifier.\n\n\n[Grabación de pantalla desde 17-09-22 16:22:16.webm](Grabación_de_pantalla_desde_17-09-22_16_22_16.webm)\n\n", "LookDev: Add option to set the background color\nTheme, World, Viewport.\n", "Image Sequence data disappears after certain properties are set\nOperating system:\nGraphics card:\n\nBroken: 2.83.6 (and all previous 2.8x versions)\n\n\nCannot access image sequence pixel data from 'Image Sequence' editor after certain properties are set.\n\nBased on the following startup file and bundled image sequence:\n\n\n1. Open the 'image_sequence_issue.blend' file from the following zip folder:\n[image_sequence_issue.zip](image_sequence_issue.zip)\n2. Run the active script in the text editor area\n3. Notice that an error is thrown - the image sequence has no data.\n4. Now comment out lines 8 & 9 (or line 12), and re-run the script. Notice that no error is thrown and the image has data.\n\nFor reference; the script bundled in the above file is copied below:\n\n```\nimport bpy\n\n# get the image editor space in the current screen\nviewer_area = next(area for area in bpy.context.screen.areas if area.type == \"IMAGE_EDITOR\")\nviewer_space = next(space for space in viewer_area.spaces if space.type == \"IMAGE_EDITOR\")\n\n# set properties on the image user\nviewer_space.image_user.frame_offset = 1\nviewer_space.image_user.use_cyclic = True\n\n# set the display channels to 'color'\nviewer_space.display_channels = \"COLOR\"\n\n# viewer_space.image.reload() # this line does not fix the issue\nprint(\"Before update:\", viewer_space.image.has_data)\nviewer_space.image.update()\nprint(\"After update: \", viewer_space.image.has_data)\n```", "Materials animation doesnt show up in animation actions editor\nOperating system: Linux-5.8.18-300.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.92.0 Alpha\nWorked: never\n\nMaterials animation doesnt show up in animation actions editor\n\n[#82522.blend](T82522.blend)\n- Open blend\n- keyframes for nodetree actions will be visible in the Graph Editor\n- keyframes for nodetree actions will be visible in the DopeSheet\n- keyframes for nodetree actions will be visible in the NLA Editor\n- keyframes for nodetree actions will **not** be visible in the Action Editor and appropriate Action cannot be selected from the dropdown\n\njust make a base color of material animated and then see that its not in action editor\n\n", "Weird artefacts from emission surface\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M (but this occurs also on CPU)\n\nBroken: 3.6.2\nWorked: don't know\n\n\nIn the attached .blend file I have set up an emission shader to emit light from one end of a long thin surface. The screenshot illustrates the problem: a bunch of weird artefacts appear.\n\nIf I change it to emit from the other end of the surface, by swapping the 'Map Range' node in the screenshot for the disconnected one, the problem goes away.\n\n\n\n\nLoad the attached .blend file and switch the view to rendered.\n\n" ]

[ "Missing some texture input option in yellow color socket node in material properties\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\nCPU: intel 2328m \n\nBroken: version: 3.0.0 Alpha\nWorked: 3.0 hash: `18959c502d`\nCaused by 0cd3d46246\n\nmissing some option in texture category (see image).\n\nit seem only in yellow socket is missing, i haven't check other socket but if you add search image node in shader editor it still apear in texture category.\n\n\n\njust use default scene and click the yellow socket in material properties.\n\n" ]

[ "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Blender crashes when I try to subdivide my model\nOperating system: Windows 11 Pro 64-bit, 12th Gen Intel(R) Core(TM) i9-12900KF (24 CPUs), ~3.2GHz\nGraphics card: NIVIDIA GeForce RTX 3070 Ti\n\nBroken: 3.6, latest version\n\n\n\n- Open Blender, Open File\n- Go to Preferences, Turns off GPU Subdivision\n- Change to CUDA and tick Graphics Card Box\n- Goes to Modifier, Click Subdivision Surface, Processing, Crashes\n\nTo give a bit more context, my current model only has 160000 vertices which I think is quite little? But still it cannot subdivide and crashes whenever I click the subdivide option in modifiers.\n\n", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "Solidify (Complex, Constraints) - very rare glitch\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.1\nWorked: 3.1.2\n\nbehavior changed in c2e8e68b6517b91eb14270707d7182c1727861c4\n\nSolidify modifier creates a weird glitch at a specific vertex.\n\nI have a model with about 40000 verticies that I wanted to solidify. Everything works fine, except the surroundings of a single vertex. The topology does not seem any particular there. The model is made out of triangles, but the glitch also appears if I convert it to quads. I copied the vertex and the surrounding faces to a sperarate blender file and recorded how the glitch appears depending on moving one of the verticies:\n\n(the glitch looks exactly the same when the vertex is part of the larger object)\n\nSolidify Modifier Settings:\nMode: Complex\nThickness Mode: Constraints\n(other settings does not affect the glitch)\n\n", "Texture Mapping issues on large brush radius\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\n\nWhen a large brush radius for textured brushes in sculpt mode, the outer-most affected geometry doesn't apply the texture fully. This is especially noticeble on the Clay Strips and Paint brushes when the stroke method is set to anchored.\n\n\n\n\n\nBlend file = [bug.blend](attachment)\n\n- Open the File\n- Use the provided paint brush and clay strips brush on a subdivided cube or suzanne head like shown\n- Notice how the outer edges of the falloff is not updating the geoemtry fully\n\n", "GPU Subdivision slows down in Sculpt mode, Weight paint mode.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.1\n\nGPU Subdivision slows down the work in Sculpt mode and Weight paint mode\n\n1. Turn on the GPU Subdivision.\n2. Enable the subdivision surface modifier on the model.\n3. Try to do something in Sculpt mode, Weight paint mode.\n4. Turn off the GPU Subdivision and follow step 3.\n\nWith GPU Subdivision enabled, the Sculpt mode and Weight paint mode tabs work much slower.\nIf it can't be fixed, then it would be logical for GPU Subdivision not to be enabled on these tabs.\n\nAt the same time, the GPU Subdivision works correctly in Object mode.\n", "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)", "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", "Subdivision Surface Performance Degrades Markedly With Non-Quad Meshes\nOperating system: Windows 7 Pro X64\nGraphics card: Nvidia Geforce GTX 980 Ti\n\n\nBroken: Date: 2019-01-21\n```\n Hash: dd3f5186260e\n Branch: Blender 2.7 (although it's supposed to be a 2.80 Beta)\n```\n\n[OpenSubDiv_PerformanceBug.zip](OpenSubDiv_PerformanceBug.zip)\n\nSubdivision surfaces are fast and responsive in Edit mode *with all-quad meshes*, but very slow (~ 10x slower) with meshes comprised of triangles and quads.\n\n\nOpen the attached blend file and select **Cube.001**\n\nGo into Edit mode. Turn on Proportional Editing. Grab a point and move it - observe how responsive the viewport is with the all-quad mesh.\n\nGo back to Object Mode. Select **Cube**. Go back into Edit Mode. Grab a point and move it (with proportional editing still turned on) Observe how slow it is.\n\n", "“Surface Deform”-modifier is overwriting the whole modifier stack\nOperating system and graphics card\nFedora 27 / GeForce GT 740\n(OS-independent issue)\n\n2.79a - offical release - 8928d99270f\n\nUnlike the “Mesh Deform”-modifier, which is applying the changes in a relative fashion, the “Surface Deform”-modifier just overwrites the previous modifier/s with the absolute values of the transform.\n\n[bug_report_surface_deform_modifier.blend](bug_report_surface_deform_modifier.blend)\n\nPlease look into the attached blend-file to follow the examples:\n\nExample1: adding two times the same “Surface Deform”-modifier on top of each other yields the same result as just one or in fact any number of copies of this modifier, thus rendering the nature of the modifier-stack here somewhat useless. In contrast e.g. the “Mesh Deform”-modifier would apply each copy of itself as a relative transform, thus building upon the previous modifiers in stack and changing the output-mesh with every copy of itself.\n\nExample2: Using the “Multi Modifier”-option of the “Armature”-modifier usually takes the same data as the previous modifier as input. The results of the previous modifier and the “Armature”-modifiers are then mixed together, using the weights of the Vertex Group as “mixing guides”. But in the case of the “Surface Deform”-modifier being the previous modifier this seems not to apply and the “Multi Modifier”-option takes no effect at all.\n\nExample3: Adding the “Surface Deform”-modifier on top of “Armature”-modifier overwrites the effect of the “Armature”-modifier (and all other modifiers prior to the “Surface Deform”-modifier.\n\n( An additional oddity seems to me that there is no option to control the overall influence of the “Surface Deform”-modifier with a vertex group, as is usually the case with all other deform modifiers. This though is not part of the bug report and rather a small feature request – but if someone is already looking into the above issue, I figured it wouldn't hurt to mention it here as it is probably just a matter of copy and paste from any modifier that already has this implemented - I might be wrong here though of course - please forgive my ignorance.)\n\nThank you for taking your time to look into that issue.\n\n\n", "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", "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", "Surface Deform modifier always updates when selecting objects\nOperating system: Windows 10\nGraphics card: NVidia GTX1080\n\n2.93.1, 2.93.3\n\nSurface Deform modifier causes click lag even if object or/and the modifier is disabled in viewport. It doesn't affect camera panning or rotation.\nWhile I'm at it, it also seems to keep unnecessary data in saved file. I wanted to provide an example file, but it turned out to be over 1 GB. I don't see why it keeps the deformed mesh in the file rather than recalculating it when we enable it or open the file.\nIt seemed to me to be the best way of making a chainmail, but I can't work with the lag.\n\n1. Subdivide the default cube with 7-10 cuts (7 enough for my PC, if in the end it doesn't lag, try more divisions).\n2. Duplicate the cube.\n3. Add subdivision modifier (level=6) to 2nd Cube, then add Surface Deform, set the source to 1st Cube, bind.\n4. Disable both objects in viewport, you can even disable the modifiers.\n5. Add a new Cube to the scene. Try selecting and deselecting in in the viewport. There's a lag. Camera panning and rotation works fine. The only way to fix the lag is to apply or remove the Surface Deform modifier.\n6. Save the file. Our file is just 396 faces with modifiers applied. It's over 1GB in size.\n\nVideo: hEQnVVvPEGU\n\nor\n- Open .blend file\n- Bind mesh to the target\n- Try to select the Cube.001 in viewport\n[#90985.blend](T90985.blend)\n", "DepsGraph: Disabled objects referenced by other disabled object still get evaluated\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.56\n\nBroken: version: 3.0.0 Alpha\n\nIn the below setup, although all mesh objects are disabled, the viewport is still extremely slow because the objects (which have expensive modifiers like Remesh and Boolean) are still evaluated.\n\nThey stop being evaluated only when their grandparent collection (\"coll Root\") is also hidden from the viewport(or deleted).\n\nNote that there are no drivers involved.\n\nFile: [disabled_objects.blend](disabled_objects.blend)\n- Try moving the cube, should see bad performance even though all meshes are disabled. If your PC is too powerful to notice, put a subsurf modifier on the object named \"expensive mesh\", that should make it a lot more expensive.\n- Disable or remove the \"coll Root\" collection, and performance goes back to normal.\n\n[depsgraph_bug-2021-07-02_13.10.41.mp4](depsgraph_bug-2021-07-02_13.10.41.mp4)", "Cycles freeze on render and texture baking (with packed textures)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.83\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nBlender freezes on render\nBlender also freezes on texture bake and rendered viewport\nTried on 3 different PCs, all the same\n\nIf textures are unpacked, rendering is fine.\n\nSimply open attached .blend file and hit F12\n\n[render_test2b_delmesh3_simplified.blend](render_test2b_delmesh3_simplified.blend)" ]

[ "Subdivision Surface modifier doesn't works proper in 2.80\nOperating system: Windows 10 Pro 64bit\nGraphics card: AMD Radeon RX 560\n\nBroken: 2.80 dd3f5186260e\nWorked: 2.79b\n\nWhen I use the Subdivision Surface modifier the object because very slow....... like a have an old PC and have frame drops. The other objects that don't have the Subdivision Surface modifier works just fine! \n\nJust add the Subdivision Surface modifier in an object.", "Error with subdivide\nOperating system:\nGraphics card: Nvidia GTX 1050 ti\n\nBroken: 2.80 and 2.81\n\n\nAfter using the subdivide modifier on the model, the blender hangs for 2 minutes + -\nWith quality 3 or higher\nThis hang occurs in this model because of the dense mesh around - 192 vertexes, with 32 vertexes everything is fine, it was also checked in 2.7 with 192 vertexes it does not freeze\nПосле использования модификатора сабдивайд на модели, блендер зависает на минуты 2+-\nПри качестве 3 или выше\nЭто подвисание происходит у этой модели из за плотной сетки вокруг - 192 вертекса, при 32-х вертексов все нормально, так же проверено было в 2.7 при 192 вертексов не зависает\n\nSelect a model and press ctrl + 1\nВыбрать модель и нажать сочетание клавиш ctrl + 1\n[Test.blend](Test.blend)", "strange slowness in subsurf + armature deform (blender 2.80)\nI attached a simple example scene. \n\ntry to move the bone, and notice how slooooowly the cube follows.\nit's because of the subsurf modifier. even in level 1.\n\nbut, thing is, same kind of setup works just fine in 2.79, even with higher subsurf levels.. \nalso, this used to work fast in 2.80 too.. because I've done couple of scenes that use the same type of technique...but opening those blends now crawl to a halt if I try to pose the characters.\n\n[slowness.blend](slowness.blend)\n\n\n.b", "switch between edit and object mode is very slow when subsurface modifier is active.\nOperating system: win7 64\nGraphics card: gtx1070\n\nBroken: git.bf9904ec8018\nWorked: 2.79\n\nSubsurface modifier make switch between \"object mode\" and \"edit mode\" very slow, even with low poly meshes.\nSetting the subsurface modifier UV settings to sharp give a little boost, but still very slow.\nHere is 2 identical files, one for 2.79 and the same for 2.80 to check the difference in performance.\nThis is probably a well known issue, but may those files, that I'm actually using in production can be helpful to make some tests.\n\nThank you\n\n[switch279.blend](switch279.blend)\n\n[switch280.blend](switch280.blend)\n\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)", "Subdivision surface lag\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.8.2 26.20.13001.40003\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nLag with subsurface\n\nSelect the model\nGo to the modifiers tab and enable sub-surf(you should experience some lag after doing this action)\nGo into edit mode on the model and try moving stuff around, it lags like CRAZY!\n\n\n", "Specific File with Dynamic paint hangs on render (but renders on deleting dynamic paint canvas object)\nOperating system: GNU/Linux (Fedora 30)\nGraphics card: nvidia 1050 (mobile on Dell xps 15)\n\nBroken: 2.80, 85322737baec, blender2.80 beta, 2019-05-22, from buildbot)\nWorked: unkown\n\nOn this file, starting a render or a bake results in blender hanging at 0% either using cycles or eevee. Cancelling render hangs at 'cancelling' though the file can be saved in this state.\n\n1- load the attached .blend\n2- press render\n\nThere is an object in the file named 'water' that is a dynamic paint canvas. deleting this object results in the file rendering fine. I suspect this is a depsgraph issue and not cycles/eevee since it happens in both engines.[bug.blend](bug.blend)", "Subdivision modifier makes editing complicated mesh Laggy, despite the area of effect being really small\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\n\nA complicated mesh will be laggy when editing the vertices, despite the affected area being really small\n\nDrag the cheeks of the complicated mesh. Notice it being more intensive to handle.\nDrag the cheeks of the head only mesh. Notice it being much smoother. In both cases it's a very tiny area that's being changed by the subdivision modifier, but one is far more laggy\n\nIf there was a thing in place to only change the actually changed part of the subdivided mesh, it could speed up work I bet\n[subdivision lag.blend](subdivision_lag.blend)\n\n", "2.8 bevel + subdivision = lag\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[When I use the bevel and the subdivision surface modifiers in the same object I have lag when move the faces/verts/edges (this doesn´t happen in 2.79)]\n\n[Create a monkey and add a bevel (angle method) and a subsurf modifier, then try to move a face/edge/vert]\n\nexample video here UFIR13EPtV0\n\n", "Subsurf Modifier slows vertex tweaking\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro K3100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n**Subsurf Modifier slows vertex tweaking**\n[Applying the Subdivision Modifier to Object results to lagging while tweaking vertex. \nIn fact tweaking with the Subsurf Modifier on is counterproductive for Polygonal Modeling at this time. \nIt makes no difference even if the Viewport setting is set to 1.\nTested same procedure with daily build blender-2.83-a24f52c51cff-windows64 (29/03/20)\nand got the same result.]\n\n[Loaded model made of verts 36.570 - Faces 36.540 - Tri: 73.080\nAdded Subsurf Modifier. \nSettings: Display Modifier in Viewport - Display Modifier in Edit mode.\nRender 2 - Viewport 1 - Quality 2.\nSelected the Tweak Tool then selected one vertex to move.\nIt takes about 4 seconds or more to move a single vertex..]\n\n\n", "Subsurf modificator long time to add on mesh\nOperating system: Win 7 64bit\nGraphics card: GTX1070\n\nBroken: 2.83.5(release build) , 2.90.1(release build) \nWorked: 2.79b\n\n\n1 select mesh\n2 add subsurf modificator \n3 and wait -about 1 min 25 sek for (2.83.5) and (2.90.1) or 1-2 sek for 2.79b\n\n[MeshtoSubsurf.blend](MeshtoSubsurf.blend)\n", "Very slow playback with Subdivision modifier 2.81, 2.82, 2.83\nPlayback of an animated mesh with shape or bones is very slow with the subdivision modifier (2.8, 2.81, 2.82.7, 2.83) It is a very serious problem for characters and creatures animation, open subdivisions should use the GPU.\nI attach 3 videos.\nThe problem had been resolved in older versions of Blender (2.7) as you can see in this video where Sharybin shows a dragon flapping its wings (2014):\ndzIl_S-qHIQ\n\nTest: 200 x 200 sphere (shape animation):\n\nBlender 2.82.7\nSubdivision level 1\nFrame rate: 3 fps\n\nBlender 2.79b\nSubdivision level 2\nFrame rate: 59 fps\n\nMaya 2018\nSubdivision level 2\nFrame rate: 160 fps\n\ncsYeyNDWyxE\nCnLUnFdQ38s\nhiX8bCpOwzE", "Blender 2.80 Beta Subsurface Modifier Lag\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GeForce 750 Ti\n\nBroken: Blender 2.80, 4c31bed6b46, blender2.8, 2018-11-30\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen I add a Subsurface Modifier and then adding Loop Cuts it starts lagging until I place the Loop Cut.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Modifier Subdivision Surface Lag\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nIf modifier Subdivison Surface is active, the edit mode is slow in any model with 8k vertex or more.\n\n\n- Add modifier Subdivison Surface in any model(With 8k vertex or more).\n- Enter in Edit Mode\n- Try move, scale or rotate\n\n[Example ](view?usp=sharing)\n\n" ]

[ "Crash on render\n**System Information** MSI BRAVO 15\nOperating system: WINDOW 11\nGraphics card: RX 6600\n\n**Blender Version**3.6\n\nWhen attempting to render a scene in Blender, the software consistently crashes, causing frustration and hindrance to the rendering process. This issue is hindering users from efficiently creating their projects and requires immediate attention to maintain a stable and reliable rendering environment.\n\n[debug-log](https://projects.blender.orgattachment)\n[system info](https://projects.blender.orgattachment)", "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "Blender 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", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "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", "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)", "Material Library VX causes permanent freeze with EEVEE rendering\nOperating system: Windows 10, 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.81\n\nUsing materials from Material Library VX addon, particularly Floor Wood and Rusty Metal, causes EEVEE to freeze all of Blender. They work fine with Cycles, so it's not the addon. Not even the partial \"developer view\" render can take the materials.\n\nOpen default blend file.\nEnable Material Library VX addon.\nApply \"Floor Wood\" to the cube.\nSwitch to \"render view\" without changing the engine off of EEVEE. Blender 2.81 will freeze.\n\nNote: If you try to view the material preview and EEVEE is the render engine even *that* will freeze Blender 2.81.", "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", "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```", "Quick Smoke crash guide February 3, 2023\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.5.0 Alpha\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\n[image.png](image.png)\n[image.png](image.png)\n[Blender-2023-02-03-113746.ips](Blender-2023-02-03-113746.ips)\nTest File: [3.5.zip](3.5.zip)\n```\nCall Stack: Main thread\n__psynch_cvwait\n_pthread_cond_wait\ntake_gil\nPyEval_RestoreThread\nPyGILState_Ensure\npy_timer_execute\nBLI_timer_execute\nwm_event_do_notifiers\nWM_main\nmain\nstart```", "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", "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", "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", "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", "Material Properties Button\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6700 XT ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.18.220726\n\nBroken: version: 3.5.0\n\nevery time i click on the materials properties button on the right, blender shut down.\n\nit happens when you start or anytime what you are doing. Just start program, click materials properties button.\n\n" ]

[ "Blender crashed when clicking \"Material\" icon\nOperating system: Windows 7 32-Bit\nGraphics card: GT 730\n\nBroken: (example: 2.80, b331515d2e47, master, 2019-05-02, as found on the splash screen)\nWorked: (optional)\n\n\nWhen in Eevee, clicking \"Material\" Icon. System will crashed.\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "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", "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.", "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", "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", "Blender 2.90.1 crashes after rendering the first few frames of animation.\n**System Information** \nOperating system: windows 10 64 bit\nGraphics card: Nvidia GeForce GTX 1650\n\nBroken: (2.90.1 3e85bb34d0d7; master)\nWorked(didn't): (only tried on 2.8.3 and did not work at all)\n\nWhen I try to render the animation, after about 50 or so frames(varies randomly), blender crashes with no alerts or anything that tells me what the error is, it simply closes.\nI've rendered another project, and that did indeed render, so I'm left confused why this short animation would cause a crash.\n\nEdit: I disabled motion blur, and it rendered fine. However, I would really like to know why blender won't render if motion blur is enabled. The renderer is Eevee and while my laptop isn't a super computer, it should be able to handle it. Thank you all in advance!\n\n- Open attached file\n- render the animation\n[cube-loop-tut-V1.0.blend](cube-loop-tut-V1.0.blend)", "Crash when 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 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 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>", "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", "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 ", "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "Crash 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", "Crash when multiple materials are assigned to a mesh\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.1 Release Candidate\nWorked: unknown (I haven't opened the .blend file in versions older than 3.2. It is broken in 3.2)\n\nWhen two materials are assigned to the mesh, random faces disappear and reappear when switching between Object and Edit modes. After switching back and forth several times, Blender crashes. In some instances it took significantly more switches from Edit mode to Object mode and back before Blender crashed. In some of these instances, Blender appeared to create new faces with one or more vertices at the object's origin.\n\nWhen transforming any vertex, edge, or face, Blender quickly generates new faces with at least one vertex at the object origin and crashed shortly thereafter.\n\nI posted a 30-second video of the issue (including two crashes) here: strange_face_artifacts_causing_crashes/\n\nThankfully, I have not reproduced this issue in any other .blend file.\n\n1) Open the attached file, \"Crash - random faces.blend\" and you will see the mesh has a number of holes in it.\n2) Press tab and the missing faces will reappear but other faces will disappear. Pressing tab additional times eventually results in Blender crashing.\n3) Select any vertex, edge, or face and transform the selected element using G, S, or R and new faces will appear. Blender will quickly crash.\n4) Reducing the number of material slots to one appears to fix the problem (all faces are visible as normal) but it reappears as soon as a material is assigned to the second slot.\n\nThank you very much for your time.\n\n[Crash - random face orientation.blend](Crash_-_random_face_orientation.blend)\n", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "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)" ]

[ "Material crash in 2.8\nOperating system: Windows 7 64-bit SP1\nGraphics card: Nividia GeForce GT 730\n\nBroken: From the 29th of april version to the latest\nWorked: Till 28th of april\n\nThe material tab crashes the software\n\nI don't really know if it happens to others, but here is how it happens:\n1) create a new object with no material on it, or a pre-existing 3D model you made\n2) go to the material tab and create a new material.\n3) now wait 2 seconds until the software will crash.\n\nThe other way is when the object already has a material being setup. Just click the material tab, and the software will crash instantly.\n\nThe crash type is silent, so I don't really know what causes it to happen." ]

[ "VSE (Video Sequence Editor) scene strips have very slow playback in both Material preview and Rendered mode.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\n\nAdding the 3d scenes to the VSE and turning Material Preview or Rendered mode are making the playback very slow.\n\n1. With the default scene opened create a second scene.\n2. Switch to the Video sequencer.\n3. Add a first scene to the timeline.\n4. Switch \"Scene strip display\" to Material preview or Rendered.\n\nThank you.", "Eevee slower than cycles when using a lot of particles or collection instances\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 17)\n\nWhen using a lot of collection instances with particles in them, or with a lot of objects, Eevee seems to be very slow in evaluating the scene. \neevee: 2min and 2sek \ncycles (gpu): 9sek\n\nopen the file switch to cycles - hit render\nswitch to eevee hit render\n", "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", "\"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)", "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)", "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)", "Speed of update geometry in viewport down when nodes/modifiers have boolean with empty collection\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\n\nI'm trying to create an addon similar in functionality to mop-boolean modo, where there is a ready-made modifier tree and you only need to transfer objects to the desired collection.\nIf there is an empty collection in nodes/modifiers, the whole process starts to slow down(until u add objects to collections)\n\n1- open file\n2- try move Cube.006 in [D1](D1) collection\n3- delete Cube.013 , Cube.014 , Cube.015 from U2 , [D2](D2) , U3 collections\n4- try move Cube.006 again\n\nif I do this I see how speed dropped by 2 or more times\n\n[Slow_Boolean.blend](Slow_Boolean.blend)\n\n\n\n\n", "Can not undo Node Editor operators in Edit Mode\nOperating system: Linux-5.4.0-125-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.5.0\n\nIf Edit Mode is active (for Curves or Meshes), Undo on Node linking/moving etc. gets ignored.\nIf there is a reason for that, Undo history probably should reflect that, for example by not allowing iterating to steps in Edit Mode that won't match reality.\n\n[undo.blend](attachment)\n - In GN or Shader Editor create a new Node Link.\n - Undo.\n -> Undo History shows a step back, but nothing actually happens.\n\n", "Regression: Global Viewport Visibility no longer readable when object is appended from another file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.0.0 Alpha\nWorked: version: 3.0.0 Alpha\n\nGlobally disable in viewports Bug. I just upgraded from version 2.9 to version 3.X I downloaded version 3.5.1 and noticed this problem, then I downloaded some other versions of 3.X and noticed the same problem, the same problem as in version 2. X I didn't have it.\n\nWhen I create an object and then I disable the globally disable viewport option, and then I save the file, when I open another blender file and append to that object, it appears in the scene with globally disable viewport ON even if I saved it with this option to OFF. I know I can disable it, but this is very annoying when I append a rig and have to check that box 100 times on different meshes\n\nHere is a video to understand better : AecByo8PYQw \nI did that on 3.6.2 and 2.9.1 to see the differences. \n\n1. Open any 3.X version of blender. \n2. Delete the camera and the sun, keep the cube.\n3. Then disable the globally disable viewport option. \n4. Save the file somewhere. Then close blender.\n5. Open blender again (not the file you just saved) .\nThen append the cube you just saved and you will see that it appears with globally disable in viewport ON, even if you saved it with off.", "Viewport display broken for fire- solid and rendered mode (Cycles & Eevee)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\n[Fire seems to get 'stuck' in the viewport (as in it does not disappear), it does however behave correctly when F12 rendered.\nThis happens in 2.83Alpha and 2.82Beta (both downloaded as of today, approx 16:00 Sydney time 15 Jan 2020)]\n\n[Bake the attached and observe.\nhere's what it looks like-\n[ViewportFire_2-82+2-83.mp4](ViewportFire_2-82_2-83.mp4)\n\nIt works Ok when F12 rendered as seen here-\n[Fire26Nov20190001-0050.mp4](Fire26Nov20190001-0050.mp4)\nI couldn't be bothered to render out the clip in Cycles but stills show the error is only in the viewport-\n\n\nHere's the .blend-\n[Fire2.83A.blend](Fire2.83A.blend)\n\nThis works properly in the 26November2019 build, here's what that looks like-\n{[F8279386](ViewportFireMantaflow_26-11-19Build.mp4)}]\n\n", "Slow reaction when assigning a new material\nOperating system: Linux-6.1.0-9-amd64-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD ARUBA (DRM 2.50.0 / 6.1.0-9-amd64, LLVM 15.0.6) X.Org 4.5 (Core Profile) Mesa 22.3.6\n\nBroken: version: 3.6.0 Alpha\n\n\n\n\nhello,\neverything in blender is working very good except for one problem which is (( assigning a new material ))\nit's doing it but it's taking too much time for each choice in material picker or color picker, i opened blender in terminal and it's doing a lot of things, i copied some of the long list lines and attach it in a normal text file.\nit is doing the same in:\nblender 3.3 - 3.4 - 3.5 and 3.6 on linux debian 11 mate with x.org x11 and gnome with wayland.\nblender 3.3 - 3.4 - 3.5 and 3.6 on linux debian 12 mate with x.org x11 and gnome with wayland.\nblender 3.3 - 3.4 - 3.5 and 3.6 on linux fedora 37 mate with x.org x11 and gnome with wayland.\nblender 3.3 - 3.4 - 3.5 and 3.6 on linux fedora 38 mate with x.org x11 and gnome with wayland.\nblender 3.3 - 3.4 - 3.5 and 3.6 on linux manjaro 22.0 mate with x.org x11 and gnome with wayland.\n\n", "Cycles: Changing certain settings with `Persistent Data` enabled can lead to extremely long initialization times on re-render\nOperating system: Linux-5.15.0-1-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken version: 3.1.0 Alpha\nBroken version: 2.93.6\nWorked: Unsure\n\nWhen changing certain settings on some objects while having `Persistent Data` on in Cycles, can lead to extremely long initialization times on re-renders. For example I may have a particle count set to `10,000,000` and I render the scene for the first time. It takes roughly 2 minutes. Re-rendering the scene only takes 10 seconds because of the `Persistent Data` option. However, if I then **decrease** the particle count to `1,000,000`, the render takes a really long time to start (I waited 15 minutes before giving up)\n\n1. Change the render engine to Cycles.\n2. Change render settings such that the render is quick (lower sample count, turn off denoising, reduce the resolution).\n3. Enable `Persistent Data` in the `Render Properties -> Performance` section of the `Properties editor`\n4. Create a hair particle system with lots of objects. I did this by creating a plane, giving it a hair particle system set to count `10,000,000` and set it to \"render as\" a Suzanne object\n5. Render the scene. Take note of roughly how long it takes for the render to initialize. Roughly 2 minutes for me.\n6. Render the scene again. (I'm not sure why but this steps seems to be necessary)\n7. Reduce the particle count on the plane. I reduced it to `1,000,000`.\n8. Render the scene again. Notice how the render takes a really long time to start. (I gave up after waiting 15 minutes.)\n\nHere is a file that does step 1-4 for you:\n[Persistent Data Long Intialization Time.blend](Persistent_Data_Long_Intialization_Time.blend)\n\n**NOTE:** This is not an out of memory issue, at least from what I can tell. Blender gets nowhere close to using the entirety of my RAM (64GB) or VRAM (24GB) during tests using CPU or GPU for testing.", "DrawManager: Threading for ibo.fdots_nor/hq\nCurrently done in finish with comment that it is faster.\nWe should benchmark when it is faster and document this with the code.\nOr change it to use threading.\n\nIt could be faster, but can stall other batches.\n\nThe comment was written before the previous optimization that supports better batching. I don't see why the current structure would be faster than implementing it with poly looping.\nFile: `draw_cache_extract_mesh.c` section `Extract Facedots Normal and edit flag`.\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)", "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" ]

[ "Having Global Undo enabled causes freezes while editing objects in huge files\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\n\nA well known issue with Blender is the slow undo on complex files, I am aware that the developers know about this issue. However, it seems that even **having global undo enabled causes Blender to freeze while doing very basic adjustments in complex files**. I have made a video which shows the issue most clearly: \nwatch?v=m1VsIQYlWzg&feature=youtu.be\nAs you can see in the video, the performance is so slow that it makes working on files like this very frustrating. I assume this freezing is caused by Blender saving the full file every time I make a simple adjustment. (One thing that I cannot explain is why the first selection after switching off Global Undo is still slow, everything after is much faster)\n\nThis means that, to have workable complex ArchViz files, one has to turn off Global Undo (which is of course by far a perfect solution, since a lot of things cannot be undone then anymore)\n\nSome useful information:\n1) The file is 2.8GB big, it contains a large amount (ca. 1 million) grass particles which are disabled in the viewport\n2) I have 32GB of RAM, Blender is not even close to using it all\n3) This is an extreme scenario, usually, the freeze takes about 2-5 seconds depending on how complex the moved object is\n4) I tested this on another complex file, and it also showed a speed boost after turning off global undo (the freezing was less extreme in this file, so the difference in speed was smaller)\n\n1) Have a file that is very complex and large (e.g. multiple Gigabytes big)\n2) Select a reasonably complex object (the oven used as example is a 50k tris object)\n3) Duplicate or move it\n4) Blender freezes for a couple of seconds\n\n\n\n" ]

[ "Bezier Splines: Support different interpolation options\nBezier splines have the option of different interpolation methods between control points.\nTo achieve feature parity with the old curve implementation, these should be supported\nfor geometry nodes curves as well.\n\n{[F11838239](image.png) size=full}\n\nBecause of the generalized way attributes are handled in geometry nodes, supporting\na different interpolation method for the `tilt` and `radius` is much more complicated,\nand would require special cases in many areas of the code. I propose merging the two\noptions, so a spline can only have one interpolation method that applies to all attributes.\nIf one wants to interpolate tilt and radius differently, it would always be possible by changing\nthe interpolation mode procedurally and capturing the result as an anonymous attribute.\n\nMeeting notes: 21733", "Node group assets in add menu do not work with quick favorites\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nNode groups assets in the add menu was introduced in 3.4.\n\nRight click on node group assets in the add menu brings up `Add to Quick Favorites` operator but they don't work with quick favorites.\n\nIf you register a submenu it just shows an empty box in quick favorites. If it's a node group asset, it does not add the asset.\n\nAlso all of the group assets and menus try to use the same quick favorite slot.\n\n- In Geometry Nodes editor's add menu, right click on Hair menu or the assets under it\n- Add to Quick Favorites\n- Bring up Quick Favorites, and try to use the item just registered\n\n", "Delete Geometry node face mode behaves unexpectedly when used after Join Geometry\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.2.1\nWorked: N/A (problem exists on 3.1.2)\n\n\nNot sure if this is by design, but I find that the following behaviour unexpected:\n\n- By itself, a Mesh Line output connected to Delete Geometry + Geometry Proximity node using Face mode won't delete anything.\n- However, when such a Mesh Line is joined with a Grid primitive, then Delete Geometry + Geometry Proximity in Face mode will cause all of Mesh Line to be deleted, regardless of distances.\n\n\n\n\n\n\n\n\n- Download the blend and observe Mesh Line is preserved.\n- Unmute Grid node link to Join Geometry, and observe Mesh Line is now gone.\n\n[line-deletion.blend](line-deletion.blend)\n", "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", "Metaball names with digits in the end are invisible (also issue with renaming/duplicating metaballs)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIf you will try to use names like MetaballFamily2, Family will disappear. \nNames like Aaaa1aa and 1aaaaa — checked too, causes no problem\n[2019-07-11_19-49-29.mp4](2019-07-11_19-49-29.mp4)\n[untitled.blend](untitled.blend)\n\n\nMake metaball, add 1 to the family name\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", "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.", "Create geometry nodes modifier when selecting an existing one in the editor\nSelecting an already existing geometry nodes tree in the editor on an object without a modifier should automatically create a nodes modifier. This is in parallel to the behaviour of selecting a material without a material slot.\n", "Geometry Nodes Baking\nAs mentioned on the [blog]() the goal is to support the following features:\n* Editing procedurally generated geometry destructively in the viewport.\n* Prepare and manage simulations for the render farm which shouldn't need to run the simulation itself.\n* Explicitly cache parts of the node tree to avoid recomputing them after every change.\n* Re-time animated geometries, i.e. access geometry generated on one frame in another frame.\n\nAt a high level these goals are achieved by allowing the user to bake still or animated geometry at arbitrary positions in a geometry nodes tree using a new Bake node. The baked data can then be used without having to recompute the inputs of the Bake node. It can be edited destructively using Blender's existing edit modes. Furthermore, the baked data can be imported at specific frames.\n\nImplementing all of these features in one go would be too big of an undertaking, so below are smaller releasable milestones that can be worked on one after another.\n\n## Milestone 1: Bake Node\n\nAfter this milestone users will be able to bake still or animated geometries at arbitrary positions in the node tree. The main use cases are:\n* Prepare simulations (with optional post-processing) for a renderfarm.\n* Speedup working with very heavy node trees (e.g. static landscape generation) by explicitly caching the generated data.\n\nThere are a few requirements for this milestone:\n* New Bake node with a dynamic number of sockets for geometries and their attributes.\n* Baking works by pressing on a bake button in the node itself.\n * For baking the user has to choose between still or animated geometry and optionally a frame range.\n * A bake directory on disk has to be choosen.\n* Deleting the baked data should be possible from the node as well.\n* Potential settings and the baked data are stored per Bake node instance. A Bake node that is in a reused node group is counted as multiple Bake node instances. The actual data per Bake is stored in the geometry nodes modifier on the object.\n\nIt may be enough to keep UI changes local to the new Bake node.\n\n## Milestone 2: Manage Bakes\n\nIn production files, there are typically many simulations and other heavy effects that require baking. The goal of this milestone is to give the user tools to manage many bakes.\n\nThere are multiple parts to this which could potentially be split up into somewhat independent tasks, but I keep them together until further discussion happened:\n* Support naming Bake node instances.\n * While working with just Bake nodes in the node tree, this is less important, because the location of the Bake node in the tree \"identifies\" it to the use. When dealing with many Bake node instances at once, one can't rely on their location but needs to use names.\n * Just using node names does not work well for this, because a node only has one name but might be reused many times.\n* Support tagging Bake node instances.\n * As we've seen in the intro, not all baking happens for the same reasons. Therefore it is important that tools that work with multiple bakes can filter what bakes to work on.\n * Supporting custom tags can help the user organize baked data.\n* UI for dealing with all bakes in a scene or file.\n * There should be some kind of UI list that shows all the Bake node instances.\n * It should show which data is currently baked and which not.\n * Filtering can happen using tags and object selection.\n * Various new operators can work on multiple bakes at the same time: bake, delete bake, set bake directory.\n* Python API for dealing with baked data.\n * While the UI we provide for managing baked data should be good enough for most use cases, it seems unrealistic that we can provide all the tools that a larger production needs out of the box. Therefore, it is necessary to make it easy to manage bakes from addons as well.\n\n## Milestone 3: Import Bake\n\nThe Bake node does two things implicitly, it indicates where in the node group the baking happens and it also imports the baked data. Having both of these in the same node is desirable for most use cases, but sometimes it's benefitial to split both tasks. For example:\n* Baking an animated geometry and the loading it at different frames for re-timing.\n* Load multiple baked frames of the same Bake within the same frame.\n* Baking a geometry in one .blend file and then loading it as a cache in another.\n\nAll of these use-cases turn our baking format into a more general purpose interchange format like Alembic that is Blender specific. Baking into other formats will be possible eventually as well, but it not part of this project. Using a custom format allows us to optimize it for our needs and avoids the problem that Blenders data does not always map 1 to 1 to how data is stored in common formats. Also see [this](105251) task.\n\nThe import can be done with a new Import Bake node which takes a (file) path and a frame as input and outputs the geometry. There are some problems that need to be overcome:\n* The Import Bake node ideally has the same sockets as the corresponding Bake node, but this can't be guaranteed when they are in separate .blend files.\n* While not supported yet, it will be possible to pack baked data into the .blend file. Therefore, the path input is sometimes a path on disk and sometimes some internal identifier.\n* It should be possible to use the combination of a Bake node with one or more Import Bake nodes within a node group without having to hard code the file path for all of these nodes. Therefore, it seems reasonable that the Bake node also outputs where the baked data is stored. Also see [this](29266) older proposal.\n\n## Milestone 4: Editing Baked Data\n\nThe idea is that the user can just go into edit, sculpt or other modes on the baked data and edit it in place. For animated geometries, every frame can be destructively edited separately. The goal here is not to record all manual edits the user did. After baking again, the edits will generally be gone.\n\nWhile this might seem like a small feature, if done right, it can have huge impacts on the way people work with geometry in Blender in the long-term. That is because it could theoretically allow us to get rid of the idea of \"original geometry\" in Blender (e.g. the mesh referenced by `object->data`). To give a glimpse into what could become possible: Adding a cube object could just add an \"empty\" object with Cube node in geometry nodes. This allows the primitive mesh to remain procedural. Going into edit mode could implicitly (or explicitly) add a Bake node and bake the cube so that it can be edited destructively.\n\nAs for this milestone, the target use cases are more minor and mostly revolve around fixing up \"bad\" data in animated geometry. For example, in a particle simulation, a single particle got too close to the camera and blocks the entire view. It should be possible to just delete it manually. \n\n## Parallel Track 1: UI for Unused Nodes\n\nThere are various situations in which nodes in a node group are unused:\n* Nodes not connected to the output.\n* Nodes that would compute the unused input of a Switch node.\n* Nodes that were used to compute a simulation that is now cached.\n* Nodes that compute the inputs to the Bake node which is now baked.\n\nCurrently, there is no obvious way for the user to determine which nodes have been evaluated by the last evaluation. However, this information would be very useful because it allows seeing at a glance when data is cached/baked.\n\nLogging the set of nodes that has been evaluated is relatively [straight forward](107780). However, we still need the a good UI for these nodes. The obvious solution is to just gray out these nodes. While that can work, it's not ideal because the nodes can and should still be editable and graying out usually indicates that the user is not expected to edit them.\n\n## Parallel Track 2: Store Baked Data in .blend File\n\nWe already support packing external files into .blend files. That system just needs to be enhanced to also support baking entire folders full with baked data. Ideally, it is possible to load the baked data lazily when loading a .blend file, but that's probably quite a bit more challenging. It remains to be seen how much of a performance hit loading all frames at once has.\n\n", "Geometry Nodes: Disabled from viewport object is not visible as instance\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: Current main.\nWorked: Never.\n\nDisabled from viewport object is not visible as instance.\n\nOpen attached file and check/uncheck `As Instance` option of _Object Info_ node.\n\n", "Support for USD PointInstancer\nOperating system: Win10\nGraphics card: GTX 1660 Ti\n\nBroken: 3.1\n\nAfter loading a USD file with type particleInstancer attached with spheres as child, Blender failed to draw the points as spheres. Instead, the displayed object in the layout window is just a singular point at the origin. Example file attached.[example_sim_granular.zip](example_sim_granular.zip)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Cycles: point cloud geometry improvements\n[D9887: Cycles: pointcloud geometry type](D9887)\n\nImprovements:\n- [x] Point Info node with radius, position, random\n- [ ] Backfaces are ignored (like curves), which means e.g. volumes inside points don't work.\n- [ ] Render as normal or ray oriented disc (see [D9887](D9887)#289012, [P2125](P2125.txt))\n- [ ] Baked shadow transparency support like hair? But must be optional since texturing alpha across the sphere/disc is useful.", "Geometry Nodes Object Group input does not remove dependencies\n[system-info.txt](system-info.txt)\n\nBroken:version: 3.4.0 Alpha, branch: master, commit date: 2022-10-04 22:45, hash: f9a10e7ed039, type: release\n...been already around for a while\n\nIt seems that Blender does not correctly remove the dependency from the formerly connected object from the Geometry Nodes Object Group input.\nEven when deleting all the default values.\n\n- Append the object `Cube` from the attached .blend file\nit will also append Suzanne even though all former links in the setup have been removed.\nThe only thing that helps to get rid of the dependency is to delete the input and recreate it together with all the links. \n[dependency_bug.blend](dependency_bug.blend)\n...and do not get me wrong i really like Suzanne! But if she appears all the time even when she is not invited it gets a bit annoying.\n", "Cannot set the Color attribute to display an object through Geometry Nodes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: version: 3.4.1\n\nbehavior changed in 6514bb05ea\n\nUsing the \"Store Named Attribute\" node setting the Attribute \"Col\" in geometry nodes, no longer sets the Vertexcolor of an object procedurally. When the Curve is converted to mesh and then the created \"Col\" Vertexcolor attribute is clicked, the colors show up.\n\nIn 3.4 and below this would override the vertexcolor attribute in \"realtime\" without converting the curve to mesh.\n\nOn a Curve Object, add a geometry node\n- create \"Store Named Attribute\"\n- set the \"Name\" to \"Col\"\n- change the color\n- Set the Viewport shading to color \"Attribute\" (seeattached Images) to view the result\n\nAttached file with example setup that used to overwrite the vertexcolor in 3.4.1, but no longer does in 3.5.1\n\n", "Geometry Nodes: Viewer overlay disappears when enabling In Front\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nWhen enabling \"In Front\" in the Viewport Display options of an object, which currently has a geometry nodes viewer overlay, that overlay disappears.\n\n| Viewer object: `In Front`: OFF | Viewer object: `In Front`: ON |\n| -- | -- |\n|  |  |\n\n1. Open the attached file in 3.4 or newer versions.\n2. Make sure the viewer node is enabled in the geometry nodes of `Plane.001`.\n3. Under Viewport Display, toggle `In Front` for `Plane.001`.\n\n[bug_report.blend](bug_report.blend)\n" ]

[ "Geometry Nodes: Metaball instances disappear on update or have delayed updating\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.79\n\nBroken: version: 3.2.1\nWorked: 3.1.2\n\nInstanced metaballs using geometry nodes disappear when changing exposed values in the modifier itself or when you move the object that has the node tree, but seem to update to previous operation when changing values inside the node tree.\n\n- Start a new file\n- Add **Metaball**\n- Shift select the default **Cube** and parent the **Mball** to it {key SHIFT LMB} > {key CTRL P}\n- For **Cube** switch *Instancing* from **None** to **Vertices** in object properties\n- Add new geometry nodes to **Cube**\n- Put **Instance on Points** node between input and output\n- Add **Object Info** node, pick Mball, check **As Instance** and connect it to the Instance socket of the Instance on Points node (at this point, everything works in 3.1.2)\n- Uncheck **As Instance**, the metaballs appear instanced on points now\n- Try moving the Cube or do any change in the geometry node tree: metaballs disappear\n\nMetaballs show up, but update to previous operation:\n- Check **As Instance**\n- Change X scale on the Instance on Points node by clicking and dragging to something like 10, metaballs show up and update as expected\n- Change X scale again, but by typing in 1 manually, metaballs update in an unexpected way\n- Change X scale by typing again to 2, metaballs update to the previous value of 1\n\n[gn_metaball.blend](gn_metaball.blend)", "Metaballs geometry nodes instancing bug+workaround\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Beta\n\nWhen I use geometry nodes and try to instance let's say a sphere on the verts of a cube with object info it works normally. However metaballs become invisible. There is however a workaround. I have to make the metaballs a child of the cube and then on the cube turn on instancing on verts. Suddenly I can control the position of the metaballs and where they should be instanced normally from inside geometry nodes. While the sphere object works always.\n\n\nNow turned instancing off (to the right)\n\nSphere object works always even when not a child of in this case the cube and instancing set to vert\n\n\n\n", "Point Instance node doesn't instance meta objects.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\nBroken: version: 2.93.0 Alpha\n\nFor Geo Nodes, Point Instance node doesn't work (doesn't copy) meta objects (like metaball). \n\nI used a very basic setup. The original input and output nodes plus one point instance node. I selected the object to be a meatball. Nothing happens! I selected any other object (non-meta). The object is instanced. Geo nodes were added to the default cube. \n" ]

[ "Hair Dynamics does not work for all strands when hair has been cut\nSystem 1:\nOperating system: Linux Mint 18.3 Cinnamon 64-bit\nCinnamon version: 3.6.7\nLinux Kernel: 4.13.0-39-generic\nProcessor: Intel Core i5-4430 CPU @ 3.00GHz (4 cores)\nMemory: 23.2GiB\nGraphics card: NVIDIA GTX 1070 + NVIDIA GTX 760\n\nTested and verified on secondary PC with Linux Mint 18 Cinnamon + Intel Core M-5Y10c CPU (duo core) as well.\n\nBroken:\n - 2.79 (official),\n - 2.79.6 (build hash: e50a3dd4c4e),\n - 2.79.6 (build hash: 5c10c92b23c),\n - 2.76b (official),\n - 2.80 Alpha 2 (build hash: ee7236859df),\n - possibly more.\n\nSimulating hair dynamics using the hair dynamics option (standard settings) does not work for all hair particles when the hair has been cut in particle edit mode. In particular, hair simulation only works for some strands, the others remain stationary throughout the simulation. The affected particles are seemingly random depending on the cut shape, although shorter strands seem to have a larger likelihood of remaining stationary. The affected strands do not change over time, they only change depending on the cut.\n\nSee attached .blend file for the finished result.\n[hair_dynamics_bug.blend](hair_dynamics_bug.blend)\n\nSimplest way to reproduce:\n1. Add a particle system to the default cube. (Rotate the cube 45 degrees to prevent vertical hairs - this is to allow gravity to work on all hairs.)\n2. Change particle system type to 'Hair'. Do not change any of the other settings.\n3. Go to particle edit mode with the cube selected. Using either the 'cut' tool, shrink tool or shape cut, cut the hair to some arbitrary shape (preferably with both long and short strands).\n4. Enable 'Hair Dynamics' in the particle settings tab. Do not change the settings there (although changing any does not resolve the error to my knowledge).\n5. Perform the simulation by pressing the 'play' button in the timeline. If the bug has been reproduced, you should see some of the hair particles fall down normally, whereas some of them will remain stationary. If not, try a different cut.\n\nWhen performing all steps above, except for the particle edit, the bug does not occur. Therefore, the culprit seems to be in the length of individual guide hairs.\n\nThe bug seems to occur using more complex geometry as well.\n\nAnother note: using a hair length texture does not produce the bug - because the guide hairs still have uniform length.", "\"Long Hair\" children pulled to world origin when using Texture (2.93.4 regression)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.4\nWorked: 2.93.3\n\nMy particle hair system works as expected in 2.91+ up to 2.93.3:\n\n\nIn 2.93.4, the children are pulled towards world (not object) origin:\n\n\nThis appears to only happen IF a texture is used to affect Density AND \"Long Hair\" is checked.\n\n\n\n1. Move default cube away from origin\n2. Add particle system\n3. Enable interpolated children\n4. Check \"Long Hair\"\n5. Add a Texture (even a cloud texture works)\n6. Enable Density influence\n\n\n\nBlend file with error:\n\n[Bug3.blend](Bug3.blend)\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.", "Hair particles: cannot delete hair particles in particle edit mode until you comb it\nOperating system: Linux-3.10.0-957.10.1.el7.x86_64-x86_64-with-centos-7.6.1810-Core 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.81 (sub 4)\nWorked: 2.79\n\nYou cannot delete all (hit a) hair particles until you comb them. Even more, if you select one hair or several and hit delete, they disappear, but if you then select all the rest and hit delete, all the particles deleted come back.\n\n\n- Open this blend file: [#69487-hair-delete-279.blend](T69487-hair-delete-279.blend)\n- Press {key X} and choose Particles\n\nIn current Blender (2.82 alpha @ 756b9acaf5) hairs get deselected but are not deleted. In 2.79b the hairs are deleted.\n\n**Original steps to reproduce:**\n\nCreate a new hair particle system\nGo into particle edit mode\nSelect all, hit X delete particles -> nothing happens\nDeselect all\nSelect a couple, hit X -> the selected hairs will disappear\nSelect all, hit X -> all the hairs come back visible again\n\nThere's a hair particle system newly created in the attached file.\n[hair_particles_delete_bug.blend](hair_particles_delete_bug.blend)", "Affects only origins does not work for Point Cloud, Curves, Text objects\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nAffects only origins does not work for Point Cloud, (new hair) Curves and Text objects.\n\n- Add Point Cloud (experimental), Curves or Text object\n- Set Affect Only: Origins\n- Try to move\n\n[AffectOnlyOrigin.mp4](AffectOnlyOrigin.mp4)", "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.", "Particles on Faces/Volumes with grid does not respect zero gravity\nSystem Information\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 1650\n\nBlender Version\nBroken: 3.0.0 Release candidate, 2.93.4\nWorked: Not sure\n\nParticles on Faces/Volumes with grid does not respect zero gravity\n\n1. Open a default scene and remove the default cube\n2. Add a plane\n3. Add a particle system and change the emission to Faces or Volumes and Distribution to Grid\n4. Change the Gravity to 0 in Field Weights\n\nExpected result: The particles generated needs to move up\nObtained result: The particles generated sticks to the plane\n\n", "Cycles can not render parent particle hair, while Eevee can.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duno\n\n\nIn Eevee, parent particles are successfully rendered both in viewport and final render.\n\n\nHowever, Cycles fail to render the parent particles both in viewport and final render.\n\nA sample Blender file has been attached below.\n\n", "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", "Some particles do not appear in the render when the 'Vector' pass is enabled\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: 3.2.2 - 3.3.1\nWorked: 2.79\n\nParticles in Render don't match particles in viewport. Some particles do not appear. When they move very fast the issue is more visible.\nIt happens when we enable the pass `Vector`\n\n- Open attached file or:\n - In the default scene (with the Cube), add a Plane\n - Add a ParticleSettings toe the plane\n - In {nav Particle Properties > Render} set `Render As` to `Object`\n - For the `Instance Object` choose the Cube\n - In {nav Particle Properties > Field Weights} set `Gravity` to `0.0`\n - Optionally bake for cache\n - Set `Render Engine` to `Cycles`\n - In {nav View Layer Properties > Passes > Data} enable `Vector`\n - Move Cube out of camera view\n- Choose a frame in the middle and render\nNote that the particles closest to the plane disappear\n\n[particles displaced.blend](particles_displaced.blend)\n\n", "Default Particle System colourization in Particle Edit Mode (Hair) doesn't follow theme wire/verts settings\nArch Linux + GTX 780ti\n\n\nAll versions since 2.5alpha. Currently using Blender v2.79 8ef39d5c882\n\n\n * Choose a dark Blender UI theme (Dark 3Dview background)\n * Working in `Particle Edit Mode` with different different particle systems (PS) the currently selected hair PS wire/verts colours are set to *black* instead. This is ok with light `3DView` (opengl) backgrounds. With black or dark themes or blender scenes the user can't see particle paths.\n * Adding more than one PS shows all unselected PS colours just fine using their set material colour. That is not what this bug report is about. Here the focus is on wire/vertices default colourization for the **currently selected** PS.\n * It looks like selecting the first PS uses black as default wire/verts colour. While selecting all other PS they use theme wire colour somehow, but changing `User settings -> Themes -> 3D View -> Wire/Wire Edit` colour has no impact?!\n\n\n**Side effects**\n * Switching `Particles->Render->Emitter` brings viewport PS colourization \"back\" somehow. Broken, but unselected PS are showing their material colour. randomly (?)\n * Working with three hair PS and playing with Emitter influences only some unselected PS (random)?\n\n\n**Current Workaround**\nWhile editing (Particle Edit mode) the current PS just *select all* and then use the brush to edit them. \n\n\n * Use the attacked blend file [PS.blend](PS.blend)\n * and play around while switching between `PS Red/Green` in `Particle Edit Mode` and randomly switch `Emitter` on/off.\n\n\n**Suggested Result**\nThe currently selected hair PS follows theme wire/verts colourization. All unselected PS are using their material diffuse/base colour.\n\n**PS**\nI added a cloned PS, too. Which was cloned from the Red one `ParticleSystem Green (cloned Red)`. Switching its visibility brings all PS material back.\n\n**Possibly Related Sources**\n* Blender Artists: [How Do I Change Hair Colour In Particle Edit Mode?](showthread.php?320868-How-Do-I-Change-Hair-Colour-In-Particle-Edit-Mode)\n", "Particles reset their position when using time stretching\nMinimal reproduction steps:\n- Add a particle system to the default cube and make it renderable.\n- Set the old time stretching setting to 20 and leave the new at 100.\n- Play the animation until frame 90 and render.\n- Find that the particles are sticking on the object as opposed to their correct position in the viewport.\n- Render again. They now have their correct position.\n- Play another 5 frames.\n- Render again, they are now sticking to the object again.\n\n[timeStretchingBadRender.blend](timeStretchingBadRender.blend)\n\n**Original Report**\n\nHello,\n\ni am using blender-3.1.0-linux-x64 and working on particles with time stretching but the viewport display is correct.\n\nattached is the blend file. [experiment with text.blend](experiment_with_text.blend) \n\nproblem seen in cpu/gpu/cycles/evee.\n\nregards,\nYaju", "When hair emitter's \"Curve Guide\" Field Weight lies between 0 and 1, strands float toward origin.\nOperating system: macOS Mojave 10.14.6 \nBug occurs both in 2.8 and 2.81 beta\n\nWhen a hair emitter's \"Curve Guide\" Field Weight lies between 0 and 1, strands float inexplicably toward origin. This renders the \"Curve Guide\" styling method incompatible with \"Hair Dynamics.\" \n\nThe attached .blend was made with these steps: \n1. enable \"Hair\" particle system on default cube.\n2. add a bezier curve and enable \"Curve Guide\" Force Field physics. \n3. stretch bezier curve into a wide arc emerging from the cube. \n4. parent the curve to the cube.\n5. translate the cube far from the origin.\n6. In the Particle Settings' \"Field Weights\" tab, set Curve Guide to 0.5. \n7. **Hair particles float inexplicably toward origin.**\n(Optional)\n8. set Curve Guide back to 1.0\n9. in the curve's Physics tab, under Settings, set \"Falloff Power\" to nonzero. Encounter the same bug.\n\nThanks for your time! \n[curve-guided hair with field weights bug.blend](curve-guided_hair_with_field_weights_bug.blend)\n", "Force field + hair dynamics not working in (linked) instanced collections\nOperating system: Windows 10 64 bit\nGraphics card: GeForce GTX 1070\n\nBroken: 2.80 3d8cbb534f82 (2019-01-25)\nWorked: 2.79b release\n\nA surface force field does not affect hair dynamics when it is part of a collection that is linked into another file.\n\nSteps to reproduce:\n1. Create a hair particle system, with hairs along x axis. \n2. Enable hair dynamics on hair\n3. Create a surface force field underneath it.\n4. Press play button to verify hair is affected by force field.\n5. Save file\n6. Link the collection from the first file into another file. (I have 'Instance Collections' turned on)\n7. Press play. hair will fall and not be affected by the force field.\n\nExample blend file attached.\n[hair_force_test.blend](hair_force_test.blend)\n", "Normal orientation for complex selection work unpredictable\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\nHere is simple example with cylinder. Same surface with same normals changes it's normal orientation and scale-cage orientation after rotation.\nIt is unexpected and unpredictable.\n\n[2020-11-21_14-27-41.mp4](2020-11-21_14-27-41.mp4)\n\nIt work as expected only if I deselect one of opposite faces\n[2020-11-21_14-31-14.mp4](2020-11-21_14-31-14.mp4)\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)" ]

[ "Delta Time not used in Rigid Body Physics and strange behavior\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 4.0.0 Alpha\nWorked: ?\n\n**Explanation**\nI was working in GN on some particle physics and wanted to see what gravity was actually supposed to look like, so I added a rigid body physics to another object. I saw that something wasn't adding up, so I tested further. I changed the frame rate and observed that the rigid body was getting faster and slower, depending on the frame rate, as well as exhibiting strange behavior (speeding up then slowing down). \n\nrigid body physics exhibiting different behaviors depending on frame rate, as well as speeding up and slowing down (this might be a bake issue or the delta time only taking effect later 🤷‍♂️)\n\n- set up a rigid body physics\n- see the speed of the gravity\n- change the frame rate\n- see that there is now a different gravity speed\n- (there may also me some strange behavior, that the speed gets faster then slower, this could also happen when switching frame rates back to what was normal before)\n\n<video src=\"attachment\" title=\"2023-07-16 00-22-27.mp4\" controls></video>\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)", "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", "weird viewport visual glitch\nOperating system: Windows 11 64 bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti Gaming X Trio\n\nBroken: version: 3.3.1\nWorked: cant bother sorry\n\nits like the position of the viewport has an offset relative to the orientation of the camera, and the viewport has a set size and cant change.\n\nfirst go to the layout workspace and have an animation playing (must have an animation playing for the bug to happen), then create a new viewport by sliding it like im doing in the video. then change the viewport into rendering mode like im doing in the video and when you resize the viewport, it has a set size and cant be changed and the position of all parts have an offset according to the position and orientation of the camera.\n\n", "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", "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", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "'Flipped' in Graph Editor Redo Panel for Paste Keyframes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\nWorked: N/A\n\nWhen copying and pasting keyframes in the Graph Editor, the Redo panel has an option called 'Paste Flipped.' This is a highly-specific and confusing option.\n\n - Create an F-Curve with keyframes\n - Graph Editor Key Menu > Copy Keyframes\n - Graph Editor Key Menu > Paste Keyframes\n - Open Redo Panel\n # Enable and disable 'Flipped'\n\n**More Info**\nThe 'Flipped' option's description says that it pastes keyframes from mirrored bones if they exist. That is not at all my initial expectation of 'Flipped' in this context. I would expect the F-Curves to either be flipped on the X-axis or Y-axis in the Graph Editor. I would also expect 'Flipped' to work with all pasted keyframes: not just those of mirrored bones.\n\n\n\nFix: D14328", "`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", "Incorrect rotation using driver or constraint\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n2.79, 2.80, 2.81, 2.82, 2.83\n\n\nBone \"target\" is animated on y-axis.\n\"Target\" turned close to gimbal lock gives the wrong result for Transformation constraint, Copy Rotation constraint, Driver.\nUsing the driver, you can see how the radian (degrees) value jumps and does not match the value of the target object.\nOnly using the driver via copy data path creates the correct result.\n\n[rotation.blend](rotation.blend)\n\n[rotation_.mp4](rotation_.mp4)\n", "Particle 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.", "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)", "Armature animation glitch when using collection instances across scenes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\nWorked: Probably never (2.90 is buggy still)\n\nWhen an armature is included in a collection, and that collection is instanced in another scene, selecting a bone or moving in the timeline creates a seemingly random time-jump in the posing/animation, until the bone is moved, at which point the whole armature snaps back into its real position.\n\nThis issue only occurs when an armature is included in a collection that is instanced in another scene. If the armature is not in a collection or is not instanced, the animation plays back as expected. The meshes under the armature does the same, if one mesh stays in the collection, the bug still happens, everything needs to be removed for the bug not to happen.\n\nWorkaround:\nMoving the bone causes the entire armature to snap back into its correct position, so this can be used as a workaround to keep the animation accurate. Alternatively, the armature can be removed from the collection and into the main scene hierarchy.\n\nThank you for looking into this issue.\n\n* Open attached file\n* Click on any bone\n\nThe pose will change. Change frame and pose will jump unexpectedly again.\n\nSome info that may be helpful: This issue seems to happen when persistent data is enabled and frame is rendered. Armature will then \"remembers\" last rendered frame. The cause may be linked to usage of Autorig pro addon.\n", "Fix Animation Channel Selection Sync\nThere are several issues with the selection synchronisation mechanism between pose bones (and shader nodes) and animation channels (in the dope sheet etc.). This task aims to provide an improved implementation of this sync to address these reports:\n\n* #48145 (All bone drivers selected when reselecting bone)\n* studio/blender-studio#58718 (Clicking on Dope Sheet deselects all bones)\n* #62463 (Skeleton rig with keyframes prevents selection of Shader Nodetree channels in Dope Sheet and Graph Editor)\n* #71615 (Select key in dopesheet deselect bone in the viewport)\n* #73215 (Blender autokeying deselects objects channels but not Armatures.)\n\n@Hjalti mentioned that it's probably better to synchronise less, that is, have the selections more separate. I'll talk with him, @PabloFournier, and @Mets in the Blender studio to come up with an initial proposal, which can then be fine-tuned here.\n\nFor me the trigger to start working on this was #62463 (Skeleton rig with keyframes prevents selection of Shader Nodetree channels in Dope Sheet and Graph Editor); in that situation it's really impossible to select certain channels.", "Menus & Context Menus: What to do if operators aren't valid\nThis is a design doc to clarify how we should handle cases where operators aren't applicable. \n\nCurrently, we deal with this poorly:\n\n - In the context menus, we often show properties that won't work (such as when nothing is selected)\n - In regular menus, sometimes operators don't work in certain criteria, but it isn't communicated\n\nHere's how I think we should solve it:\n\n## Context menus\nRule: Only ever show operators here that actually work in the current context.\nThis means that, if nothing is selected, we should not show operators to act on the selection, since this will fail.\nIn general the context menus are always meant to show the user relevant items for the current situation, so this fits with that concept.\n\n**When nothing is selected**\nFor the case where nothing is selected, there often won't be very many applicable operators. In that case, we should add operators to add new items (objects, meshes, strips etc).\n\n## Regular menus\nThese we should keep constant, and not hide or show items, since it breaks muscle memory. Instead, we should use greying out. Preferably we should improve operator polling so that operators get greyed out when not applicable. When nothing is selected, or the wrong kind of item is selected, operatoers that don't do anything then should become greyed out." ]

[ "Regression: Action actuator with playback type \"Flipper\" does not reverse correctly after action reaches end frame\nBroken: Version 2.71 official\nWorked: Version 2.70a official\n\nHow to reproduce:\n - Open the attached file in the latest version of Blender, inspect the cube's logic bricks, and press P to start the game.\n - Left click to lift the cube, and release to put it back down.\n # Notice that if you hold LMB for long enough, allowing the cube to reach the end of its action, the cube will not go back down gently when you release. Instead, it snaps back down.\n\nExpected behaviour:\n\n - Open and play the same game in version 2.70a.\n - Notice now that you can hold the cube at the top, and releasing the left mouse button always plays the action in reverse, putting the cube down smoothly, regardless of how long you've held it up there.\n\nThe Flipper playback type should behave as it did in 2.70; playing the action forward when given a positive signal, then reversing when negative. The current behaviour of \"snapping\" back to frame 0 is a regression and it negates the usefulness of the feature." ]

[ "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "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", "Toggle to Edit Mode call error when the Blender use linked a object data from another file\nOperating system: Linux 5.10.2\nGraphics card: Intel Haswel (4-th Gen ) HD Graphics 4600\n\nBroken: 2.92\n\n\nToggle to Edit Mode call error when the Blender use linked a object data from another file\n\n\n1) Create any object in a scene and save this file \n2) Create a new blend file and link the object from previous saved a file with `File` → `Link..` and then select this object.\n3) Then convert linked object to local object with `Object` → `Relations` → `Make Local...` → `Selected Objects`\n4) Select the object and press Tab that go to Edit Mode. \n5) Error - Unable to execute 'Toggle Editmode', error changing modes\n\nor download both files and then open linked.blend:\n\n[source.blend](source.blend)\n[linked.blend](linked.blend)\n\n", "EEVEE: Blender Crashes when rendering specific File\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.93.0\nWorked: (N/A)\n\nBlender crashes when rendering specific file. It only seems to happen with this file - when I render other (even larger) files with the same inputs it works fine, but with this one it crashes every time. The error message is EXCEPTION_ACCESS_VIOLATION, but I received the data from an open source website and it is placed in a folder on my computer that I have full access to. Debug report: [blender_debug_output.txt](blender_debug_output.txt)\n\nSave NZ_Compressed40pc.jpg to desktop \nOpen Dev.blend\nIn the shader editor for the plane, ensure the image texture has NZ_Compressed40pc.jpg linked as input.\nRender>render image\n\nTest File:\n[Dev.blend](Dev.blend)\n", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "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)", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\n\n", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "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", "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "Crash 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", "Render crash when using Python API to modify object Attribute data in frame_change_pre handler\nOperating system: Windows 10 Home\nGraphics card: GTX 1070 8GB\n\nBroken: Blender 2.93.0 84da05a8b806 (2021-06-02 11:21)\nWorked: n/a\n\n\nThis issue was discovered during development of an addon that generates procedural meshes in a `frame_change_pre` handler. When adding attributes to these meshes in the `frame_change_pre` handler, Blender can crash during render on random frames.\n\nThe `Render → Lock Interface` option is enabled as per the note in the [handlers documentation ](bpy.app.handlers.html#note-on-altering-data).\n\nI have created a simplified script that reproduces this crash during render, typically within a minute of starting the render. This script randomly generates triangles and attribute values in a frame change handler:\n\n```lines=5\nimport bpy, random\n\n\ndef frame_change_pre(scene):\n n_triangles = 10000 # number of triangles to generate\n n_attributes = 10 # number of attribute 'layers' to generate\n \n tsize = 0.1\n vertices = []\n triangles = []\n for i in range(n_triangles):\n xshift, yshift, zshift = random.uniform(-3, 3), random.uniform(-3, 3), random.uniform(-3, 3)\n vertices.append((-tsize + xshift, -tsize + yshift, zshift))\n vertices.append((tsize + xshift, -tsize + yshift, zshift))\n vertices.append((0 + xshift, tsize + yshift, zshift))\n triangles.append((3 * i, 3 * i + 1, 3 * i + 2))\n\n object = bpy.data.objects[\"Cube\"]\n object.data.clear_geometry()\n object.data.from_pydata(vertices, [], triangles)\n \n for i in range(n_attributes):\n attribute_name = str(i)\n try:\n object.data.attributes.remove(object.data.attributes.get(attribute_name))\n except:\n pass\n \n attribute = object.data.attributes.new(attribute_name, \"FLOAT\", \"POINT\")\n for value in attribute.data:\n value.value = random.uniform(0, 1)\n \n \nbpy.app.handlers.frame_change_pre.append(frame_change_pre)\n```\n\nIncreasing the number of triangles and/or number of attribute layers seems to increase the frequency of crashes. The crashes do not seem to occur when rendering from the command line.\n\nThis is the error reported after the crash:\n\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7736C6490\nModule : blender.exe\nThread : 00000814\n```\n\nAttached is the crash log: [attribute_crash_example.crash.txt](attribute_crash_example.crash.txt)\n\n\nAttached is a .blend file including the script that reproduces this issue.\n\n1. Open the .blend file\n2. Press 'Run Script'\n3. Begin rendering the animation (Blender > Render > Render Animation)\n\n[attribute_crash_example.blend](attribute_crash_example.blend)\n\n-----\nSeems easier to reproduce on a debug build since it hits an assert (although i'm not sure who is at fault there, could be the script, could be blender, @HooglyBoogly will likely know since he worked in this area recently) \n\n1) Make a debug build\n2) Load up the .blend above\n3) Hit the Play button on the Python script\n4) Rather than render, just his play on the timeline\n5) Boom!\n\n```lines=10\nBLI_assert failed: K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361, BKE_mesh_vertex_normals_ensure(), at 'CustomData_has_layer(&mesh->vdata, CD_NORMAL) || mesh->totvert == 0'\n\nStack trace:\nblender.exe :0x00007FF783355EA0 bli_windows_system_backtrace_stack_thread K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:233\nblender.exe :0x00007FF783354F30 BLI_windows_system_backtrace_stack K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:320\nblender.exe :0x00007FF783354900 BLI_system_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:386\nblender.exe :0x00007FF783359730 _BLI_assert_print_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c:50\nblender.exe :0x00007FF777848300 BKE_mesh_vertex_normals_ensure K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361\nblender.exe :0x00007FF7778467E0 BKE_mesh_calc_normals K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:475\nblender.exe :0x00007FF77951DC80 ED_mesh_update K:\\BlenderGit\\blender\\source\\blender\\editors\\mesh\\mesh_data.c:1106\nblender.exe :0x00007FF77885B520 Mesh_update_call K:\\BlenderGit\\2022_full_with_tests\\source\\blender\\makesrna\\intern\\rna_mesh_gen.c:7350\nblender.exe :0x00007FF778528720 RNA_function_call K:\\BlenderGit\\blender\\source\\blender\\makesrna\\intern\\rna_access.c:7336\nblender.exe :0x00007FF778A024F0 pyrna_func_call K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_rna.c:6304\npython310_d.dll :0x00007FFA32E09B40 _PyObject_MakeTpCall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:215\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:112\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4232\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E0EAC0 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:114\npython310_d.dll :0x00007FFA32E0ED10 method_vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\classobject.c:53\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:115\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4183\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E07FD0 PyVectorcall_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:255\npython310_d.dll :0x00007FFA32E086F0 _PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:290\npython310_d.dll :0x00007FFA32E07680 PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:318\nblender.exe :0x00007FF778A12F20 bpy_app_generic_callback K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_app_handlers.c:354\nblender.exe :0x00007FF776ECF220 BKE_callback_exec K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:51\nblender.exe :0x00007FF776ECF400 BKE_callback_exec_id K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:67\nblender.exe :0x00007FF7776D5C60 BKE_scene_graph_update_for_newframe_ex K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2648\nblender.exe :0x00007FF7776D5C10 BKE_scene_graph_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2712\nblender.exe :0x00007FF778A46A10 ED_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_edit.c:1729\nblender.exe :0x00007FF778A70B30 screen_animation_step_invoke K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_ops.c:4754\nblender.exe :0x00007FF777D74A30 wm_operator_invoke K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:1339\nblender.exe :0x00007FF777D6FE10 wm_handler_operator_call K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2340\nblender.exe :0x00007FF777D72F10 wm_handlers_do_keymap_with_keymap_handler K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2693\nblender.exe :0x00007FF777D720D0 wm_handlers_do_intern K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3020\nblender.exe :0x00007FF777D70B70 wm_handlers_do K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3161\nblender.exe :0x00007FF777D6A440 wm_event_do_handlers K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3775\nblender.exe :0x00007FF777D3EB60 WM_main K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm.c:642\nblender.exe :0x00007FF776EB2C60 main K:\\BlenderGit\\blender\\source\\creator\\creator.c:564\nblender.exe :0x00007FF7837A1B00 invoke_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7837A18B0 __scrt_common_main_seh d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7837A1890 __scrt_common_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7837A1BC0 mainCRTStartup d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFAE8F27020 BaseThreadInitThunk\nntdll.dll :0x00007FFAE9062630 RtlUserThreadStart\n\n```\n\n", "Cycle crash\n[System Information](https://projects.blender.orgattachment)\n\nBlender version: 3.4.1\n\nCrash when switching from Material Preview to Rendered in Viewport Shading and GPU Compute was set for Cycles. In CPU mode it's OK.\n\n\nOpen project.\nSelect CPU in Cycles settings.\nSwitch from Material preview to Rendered in Viewport shading.\nNow it works.\nChange to GPU Compute in Cycles settings.\nCrash...\n\n" ]

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

[ "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)", "Right-click reroute node opens \"Edit Source\" menu\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 3.0.0\nWorked: version: 2.93.3\n\nUsing right-click select, with Developer Extras enabled, makes it so you can't reliably select a reroute node (Geometry Nodes editor) without the \"Edit Source\" menu opening.\nSimilarly, in left-click select, you can not open the node context menu in this situation.\n[bug_rightclick_reroute.blend](bug_rightclick_reroute.blend)\nThis does NOT happen in shading nodes!", "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", "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", "Weird behavior with the set spline type node selection\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1\n\nThe selection on the *set spline type* isn't working right for bezier and NURBS modes.\nAlso adding another node before the *set spline type* node will manipulate the weird behavior, even though the node doesn't do anything or is muted etc.\n\n- add a GN setup\n- add more that one curve\n- add a *set spline type* \n- try adding a selection that doesn't select all splines\n- see the weirdness.\n(it is more perceivable if the splines have more than two points, though the bug is still there)\n\nFile:\n\n[GN_set_spline_type_test.blend](attachment)\n\nVideo:\n\n<video src=\"attachment\" title=\"2023-07-31 21-15-45.mp4\" controls></video>\n\n", "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", "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", "Weight Paint Vertex Selection Display issue\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: never really, more on that below\n\nWhen in weight paint mode with\n* vertex selection enabled\n* show wire enabled\n\nedges will not be drawn within the selection\n\n\n**The odd part**\nClicking in an empty space will get the wires to show again, but keep the vertices selected. \nThat's a behaviour that has changed from 3.1.2 to 3.2.2\nPreviously it deselected the vertices but didn't draw the edges\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n* Open the attached blender file\n* you can see that edges are not drawn between selected vertices\n* click in an empty space (important to click, not click drag)\n* vertices stay selected but wires are drawn\n\n", "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", "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)", "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", "Snap vertices with \"Closest\" is not acting as expected\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.3\nWorked: 2.82a at least. Didn't check any 2.83 releases. \n\nSnapping to vertex when moving with \"Closest\" works as if \"Center\" is chosen when moving several vertices at once.[cubicle.blend](cubicle.blend)\n\n- In the attached file, go to edit mode with the selected cubic shape.\n- 3 vertices already selected, try to move them down on Z axis with snap to vertices, \"Closest\".\n- The expected behavior is that the vertex at the bottom among the 3 selected vertices, should be at the same position of the vertex I'm snapping to.\n\n#46892 (Snapping closest vertex with Pivot point set to Individual Origins)\n\n", "Improve Interior Face Selection Method #2\nOperating system: Win 10 Pro\nGraphics card: nVidia GeForce GTX 1070ti\n\nBroken: tested in 2.80 stable and 2.81-dcad1eb03ccc\n\n\nIn Edit Mode Select -> Select all by Trait -> Interior Faces does not select all expected Faces.\n\n\nIn the attached blend file try to select the interior faces by trait and nothing happens. The object was created by moving a default cyclinder and UV sphere into each other and merging the vertices at the spheres equator by distance. After the merge the top face of the cylinder is selected by trait as expected while the lower faces of the sphere are not.\n\n[interior_faces_bug.blend](interior_faces_bug.blend)", "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)", "3D Cursor tool todo\nIn Blender 2.80, we now have a special tool for transforming the 3D Cursor. The issue is that it's not easy to move it visually, using gizmos, to set a certain pivot point for transforms. We can support this via a toggle in the tool settings, enabled by default for the 3D Cursor toolL\n\n\n\nThis makes it so you can reposition and rotate the 3D Cursor using gizmos, like so:\n\n\n\n---\n\n * - [ ] {icon circle color=green} Add button in the Tool Settings to reset the Cursor position to 0,0,0\n * - [ ] {icon circle color=green} Add XYZ controls for 3D Cursor next to it\n * - [x] {icon circle color=yellow} Add Rotation XYZ controls for 3D Cursor in the Sidebar, next to location.\n\n" ]

[ "snap cursor to selected ignores geometry position with modifiers\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\nsnap cursor to selected ignores vertex geometry position with modifiers\n\n(p.s. it would be useful if in the case as in the video with a mirror modifier, the snap function takes into account the intermediate snap between the vertices)\n\n\n1) Open .blend file\n2) Find selected vertex or select one that isn't on XY plane\n3) Press F3 and run `Snap Cursor to Selected` or {key shift s} -> `Cursor to Selected`\n4) Note cursor not snapping to selected vertex\n\n[testsfile.blend](testsfile.blend)\n\n[cursor _to _elected.mp4](cursor__to__elected.mp4)\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", "Scene statistics not updating depending on geometry node behaviour\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: Never.\n\nIt seems that the scene statistics (both in the viewport and in the status bar) are not updating to reflect the number of vertices after a deleting operation through geometry nodes.\nHowever it does update if I move to another frame in the timeline.\nIt may be a design choice to limit the computation needed but I thought useful to report\n\nIn the attached blender file go to the modifiers tab and change the LOD value in the geometry nodes setup, you'll see no change in the scene statistics despite the mesh displayed has a different amount of objects. If you move to any other frame it will update accordingly\n\n", "File thumbnails don't always show rendered result\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\nBlender doesn't save previews that look as the eevee (or cycles) render when using a camera.\n\nUse a file with a camera, save while rendered mode is on, and it will look like workbench mode.\nDelete the camera, it will save as the mode is displayed and will do as rendered if that's what you have.", "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", "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", "Shader Image Mapping Issue\nOperating system: Mac OSX High Sierra\nGraphics card: NVIDiA GeForce\n\nBroken: (example: 2.92 Master 02948a2cab44\nWorked: N/A\n\nIt seems the mapped image is not applying to an object that's linked by Object Data\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[repro2.blend](repro2.blend)\n\nIn this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):\n\n\n\n\n\n\n---\nOriginal report:\n[modular.blend](modular.blend)\n\nLook at the image reference in the shader for the second to last vehicle. All other vehicles with similar bodies are linked and are following the map except the second to last object. After linking the body of that vehicle, the object appears to follow the map until you render the image. ", "Switching image color space doesn't work on grayscale images in Cycles\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1060\n\nBroken: 3.0 release, 3.1 daily build (e6ca0b33e920)\n\nSwitching image's color space doesn't work on grayscale images in Cycles. Eevee and image editor displays image correctly, RGB images are also displayed correctly.\n(Tested on current 3.0 release build and today's 3.1 daily build, haven't checked older blender versions)\n\n[Test.zip](Test.zip)\n1) Open the attached file, go into rendered view\n2) Compare rendered image to the one opened in the image editor\n3) Switch to Eevee, image now displays as it should\n4a) Interesting thing, if you pack the image into the blend file using External data>Pack resources and switch to solid view and back to rendered, image updates and displays correctly", "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)", "Performance issues when moving bones of an armature when the Outliner is set to Blender file\nBroken: 2.93\n\nThis happens on heavy scenes and with many linked files, if you have an Outliner opened and set to \"Blender file\".\nThe fps drops dramatically only when trying to move a bone of an armature. It doesn't matter the complexity of said armature.\nThe problem stops happening after closing the Blender file Outliner.\nCould it be related to this other fix? T87842", "Animated alembic curves dont update on render\nOperating system: Xubuntu 18.04\nGraphics card: Titan X (Pascal)\n\nBroken: 2.80 63ac7c799c8\n\nImported alembic objects with animated hair strands render incorrectly.\nThe cache doesn't get read properly and no updates happen in between frames when rendering, resulting in a render where the animation is stuck on the first frame of the cache.\nProblem persists between Eevee and Cycles. Regular mesh based caches work fine, this only seems to affect imported hair/curves.\nTried animating the frame parameter too, as well as adding a driver, but it doesn't help. Every render is static on the first frame of the cache.\n\n- Create hair system\n- Animate said hair system (dynamics / forces)\n- Export Hair to Alembic\n- Import Alembic with hair animation\n- Hair animation doesn't update on render\n\n[alembic-render.zip](alembic-render.zip)", "Viewport rendering bug : unable to make the render progress (infinite calculation)\nOperating system: Windows 11\nGraphics card: RTX 3090\n\n**3.0.1**\n\nI installed the latest studio drivers for the graphic card (28 january 2022 version), and then :\n\nI encounter a really strange bug when using the viewport rendering (with or without denoising) on some projects. This bug only happens on this new computer, not on my iMac.\n\nDescription : it's like the viewport rendering \"never stops\" and fails to progress. I see the object, but in the \"worst\" rendered version only. It doesn't progress at all and I can hear the graphic card working infinitely, trying to calculate it.\n\nThe bug is present both using CUDA and Optix. Notice that normal rendering works really fine.\n\nUPDATE : The bug is also present with an old version of the studio drivers.\n\nBlend file : [realistic-atom-1.blend](realistic-atom-1.blend)\n\n", "Image Sequence Offset keyframes are randomly skipped during render\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.6.1\n\n\nWhen animating the \"Offset\" parameter of an image sequence, some keyframes are randomly ignored during the render, causing the image offset to be different from what's shown in the graph editor.\n\n\n1. Create a sequence of images, label them `0001.png` to `0004.png` for example\n2. Create a plane and create a shader with an image texture node. Load the first image as the image source.\n3. Set `Frames` to `1`, `Start Frame` to `1`\n4. Insert keyframes for `Offset`, I inserted a new keyframe every 2 frames\n5. Render the animation\n6. **Expected result:** The rendered frames changes every 2 frames. **Actual result:** The rendered frames mostly changes every 2 frames, but occasionally doesn't change at all / gets delayed.\n\n\n\n\n\n\n\n", "Blender continuosly freezes when transforming an object\nOperating system: Ubuntu 20.04.4 LTS\nGraphics card: ntel Corporation Skylake GT2 [HD Graphics 520] (rev 07)\n\nBroken: 3.1.2\n\n\nBlender continuosly freezes when transforming an object.\n\nCreate a General project (With the default cube). Scale the cube in every direction. Continue doing this and it the app will freeze. The debug log is filled with the following message:\n\n\n> INFO (gpu.debug): Notification : memory mapping a busy \"miptree\" BO stalled and took 0.039 ms.\n\n\n\n\n", "Cycles does not generate the exact same images when a scene is rendered twice\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia 2070 Super\n\nBroken: master\nWorked:\n\n\nThe results generated by Cycles are not 100% deterministic.\nAs a consequence path guiding ( #92571 ) can not be implemented deterministically.\n\n\n1. Start Blender and open a scene like `monster`\n2. Render the scene with 64spp and store the result as exr image (e.g., monster-run-0.exr).\n3. Repeat 1. and 2. and save the result as exr again (e.g., monster-run-1.exr).\n\n4. Use an image comparison tool such as tev (tev) and compute the difference. \n\nYou will see that, even if both renderings were performed on the same machine, the resulting images have minor differences.\nNote: It might be necessary to scale the diff-images to see the errors.\n\nRun 0:\n\nRun 1:\n\nDiff:\n\n\n\n\n\n\n \n\n\n \n\n \n\nBased on the default startup or an attached .blend file (as simple as possible).", "Artifact with cycles (interaction with moving spotlight and motion blur)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nI wouldnt describe it as a error, more as a artifact in cycles, basically when you parent a light to an object with motion blur, it doesnt behave as expected, it clips into objects and deforms due to the motion blur, there is no easy way to explain this, its better to show it, keep in mind that the spot light in these examples is completely Static! its just parented to the empty that also is parented to the camera, what is moving is the empty, light in real life doesn't behave this way!\n\ni first noticed this in a render i did for my animation \nrender: view\nproject file: view?usp=sharing\n\nso i did a test render and the problem pressists\nrender: view?usp=sharing\nproject file: view?usp=sharing\n\n\n\nAll the best! If this report is invalid please inform me why, because i cant find a work around this issue and there is no information online regarding this problem. Thank you.\n\n\n\n" ]

[ "Video textures not updating in Cycles renders when using persistent data\nOperating system: Linux-5.13.0-7620-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha\n\nVideo textures do not update correct frame in render time in cycles when using Persistent Data\n\nExtract the following\n[Video Texture.zip](Video_Texture.zip)\nSet viewport shading to *Rendered*\nSee how the video clip updates\nNow render an animation (it will render out really fast)\nCheck the generated test.mp4 video file\nThe video is not shown in the polygon\nDisable persistent data in the render settings for it to work correctly\n\nNote: clip is creative commons from the Minutephysics Youtube channel\n\n" ]

[ "Allow View Navigation within Modal Operators\nExcept when there's a good reason to block navigation (such as modal transforms) all modal operators should allow user to navigate the viewport. This includes panning, rotating, zooming, and changing to direct view (top, front, side, etc).\n\nFor example, neither Box Select or Circle Select allow viewport navigation. This severely limits the tools use, often requiring the user to activate the operator multiple times from different angles. \n\n**Operators that need navigation events passed through**:\n - Circle Select\n - Box Select\n - Mesh Bisect\n - Mesh Loopcut and Slide\n", "panormic camera inverts the vector pass when rendering with Cycles.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.3.0 Alpha\n\n\nOpen below blend file and go to the compositor. For convenience I've included the rendered exr vector sequence, but you can recreate by rendering the animation with the pano cam and then the standard cam if you like. The panoramic/fisheye cycles render has inverted the vector pass data, whilst the standard/perspective cam is correct. \n\n[fisheye vector pass bug.zip](fisheye_vector_pass_bug.zip)\n\n", "Cursor warping not supported on Remote Session\nOperating system: Linux-3.10.0-1160.59.1.el7.x86_64-x86_64-with-glibc2.17 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.2\nNever worked on previous Blender Version as far as I am aware\n\nMouse wrapping (seem in `Walk Navigation` for example) in Remote Sessions is unusable.\nAs Unreal had a similar issue that was fixed, I was wondering if that was something that could be fixed for Blender as well.\nIt happens both on Linux and Windows.\n\nInfo from the Remote tech used and possible issue:\nrelative_mouse_support/\nInfo on Unreal Problem and Solution:\n141157\n\n- Under a Remote session, go to View > Navigation > Walk Navigation to activate the tool.\n- panning and tilting around,\nthe camera will lag a lot and get out of control by over-panning/tilting\n\nThanks a lot :)\n\n", "Can't scrub timeline with alt + pan trackpad gesture\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.105\nMacOS 10.13.6 + Apple Magic Mouse\n\nBroken: version: 2.83 (sub 15)\nWorked: never ?\n\nWhen using a Magic Mouse it's not possible to navigate the timeline using the \"ALT+scroll\" default shortcut.\nCorrect behaviour is seen in **[this ](watch?v=o19U-yPGdyY&feature=youtu.be&t=84)** official Blender video.\n\nThis shortcut is in : User Preferences > Keymap > \"Frame Offset\".\nYou'll see it's actually **two instances** of the same shortcut :\n- one to scroll forward (ALT + Wheel Down) >> `screen.frame_offset = +1`\n- another to rewind (ALT + Wheel Up) >> `screen.frame_offset = -1`\n\nThis is a problem because the Magic Mouse is actually seen as a trackpad, therefore we have to use the \"Mouse/Trackpad Pan\" event.\nUnfortunately if you do that you are only able to scroll one way, because this shorcut entry doesn't \"see\" the scrool as bidirectional.\n\nProposed fix : add a new shortcut entry, like it's been done for \"Zoom View\" and \"Pan View\" for example.\n{[F8515046](MagicMouse_timeline_scroll.jpg), size=full}\n\nOn a Mac, using a Magic Mouse :\nopen Blender, in the viewport try to do ALT+scroll > it doesn't scroll the timeline.\n\n\n", "Normal orientation for complex selection work unpredictable\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\nHere is simple example with cylinder. Same surface with same normals changes it's normal orientation and scale-cage orientation after rotation.\nIt is unexpected and unpredictable.\n\n[2020-11-21_14-27-41.mp4](2020-11-21_14-27-41.mp4)\n\nIt work as expected only if I deselect one of opposite faces\n[2020-11-21_14-31-14.mp4](2020-11-21_14-31-14.mp4)\n", "Continuous Grab occasionally fails\nOperating system: Linux 5.9.10-arch1-1 (KDE Plasma desktop)\nGraphics card: NVIDIA GTX 980Ti (455.45.01)\n\nBroken: 2.80 - 2.92 master\nWorked: N/A\n\n\nMouse wrapping sometimes fails to transition screen edges, requiring at least a pixel of backpedaling with the mouse. This seems to affect all mouse-wrapping operators. Initially this report was written in terms of Shear, with which I've discovered this behavior.\n\nMesh edit mode Shear operator sometimes gets stuck on the toolbar side of window, showing the system mouse pointer (perhaps due to mouse passing over the toolbar?), needing at least one pixel of motion to the right to untangle it.\n\n[Video ](PeSL2fzKfT4).\n\nThis does not seem to occur if:\n- viewport is not touching window edge\n- window is made fullscreen\n\n\n- Make sure your window is not made fullscreen and that the 3D viewport is bordering window edges\n- Enter edit mode, select all and invoke Shear operator. Move the mouse continuously to the left, until it eventually gets stuck.", "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", "Material slots undo is inconsistent in non-Object modes\nBroken: 3.0\nMaterial slots undo is inconsistent. Sometimes multiple slots are added/removed in one undo, and sometimes undo won't change back mode.\n\n\ntab to edit mode \nadd a material slot\nundo twice\nadd another material slot\nundo\nboth material slots will be undone. Also undo won't go back into edit mode.\nif you redo both material slots are redone at the same time.\n", "Changing Hotkey for Perspective/Orthographic isn't working after being changed\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nWhen changing the hotkey for the Perspective/Orthographic Toggle to 'Ctrl + 5' or 'Shift + Ctrl + 5' the hotkey stops working (I cannot test whether it works with the default hotkey as I have no numpad).\n\n1. Start up Blender.\n2. Open preferences.\n3. Go to keymap tab.\n4. Go to 'View Persp/Ortho' hotkey. (Can be searched by typing 'ortho' into search tab)\n5. Change Hotkey to 'Ctrl 5'.\n6. Unset the 'Subdivision Set' hotkey.\n7. Test hotkey.\n\n", "Accessed thru Parsec software, with left hand mouse, some operations need a right click instead of a left click to confirm\nOperating system: ?\nGraphics card: ?\n\nBroken: version: 3.6.1 Release Candidate, branch: blender-v3.6-release, commit date: 2023-07-16 02:43, hash: edc1a09966a7, type: release\nbuild date: 2023-07-16, 23:35:12\n\n\n\nI m using parsec to acces to my workstation, but through parsec I have issues,\n\nI m left hand so my left click is a right one. I notice some operations needs a right click instead of a left click to confirm. For validating a scale I need to right click, for validating a rotation too.\nfor grab it's ok.\n\n\n- Access Blender through Parsec\n- I'mm a left hand guy I set my mouse with the master click as the right button instead of the left one, \nso everything should work with a right click instead of a left one...\n- Select an object with right click and grab, and can confirm grabbing with right click.\n- Repeat for Rotate/Scale, but have to confirm with left click.\n\n", "Support Undo for tweaking Gizmos\nSupport Undo for tweak gizmos, such as the Spin gizmo. Currently, the user may have performed many adjustments using adjustment gizmos, but if the user performs one undo, everything is lost.\n", "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", "Front view Y axis keybinding is reversed\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: Never?\n\nFront view key binding should give us +Y view, now it gives us -Y view. The negative Y axis is now key binded for the front view instead of the back view.\n\n- Press numpad 1, viewport switched to -Y view. (Should be +Y)\n- Press cntrl + numpad 1, viewport switched to +Y view. (Should be -Y)\n\n", "Regression: Mouse cursor jumps to the left when keep clicking on the colour circle under Windows\nOperating system: Windows 10, 21H2\nGraphics card: Intel A770\n\nBroken: 3.4, 3.6.0\nWorked: 3.3\n\nIf I keep clicking random place in the colour circle, the mouse pointer randomly jumps to the left edge of the circle. This seems to be happening only under Windows, not under Linux. \nI have only one Windows installation, so I am not sure if this would happen on other computers. Please check for it.\n\n- Just keep clicking random places on the color circle for about 10 seconds. (See the attached screen recording.)\n\nNot necessary: ~~I was using a 4K monitor with 200% scaling and Blender interface scaling was 1.0.~~", "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" ]

[ "Orbit inverted on Mac with Magic Mouse\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.24 355.11.10.50.10.103\n\nBroken: version: 2.92.0\nWorked: 2.91.0\n\nIn 2.91, when i moved my fingers on the touch-sensitive Magic Mouse to orbit, it would move in the opposite direction, which is what i, and most likely most Magic Mouse users are used to; however in 2.92.0, the orbit is the same as using a regular scroll wheel. Very disorienting, and there are no settings to invert this navigation, as far as i am aware.\n\nDefault Startup > Orbit with Apple Magic Mouse, touch sensitive surface.\n\n", "invert rotation view when use magic mouse swipe, mac\nmacos 10.15.7\nMac (Retina 5K, 27-inch, 2017)\n3,4 GHz 4‑core Intel Core i5\n16 ГБ 2400 MHz DDR4\nRadeon Pro 570 4 GB\n\nIn this and earlier version 2.91.2 (2.91.2 2021-01-19) everything is cool. Same as it was on all previous versions.\n\nIn this version 2.92.0 (2.92.0 2021-02-25) swipe on apple \"[magic mouse ](magic-mouse-2-space-gray?fnode=833f02efe5a126290577980e13bd01091065729645e3be8797a2bcdffaab2cf402f128bf0d37bb58a2496132bcc6b5558bc8bd251bbe04b36b4b6021ba1475fdd7f952c882ab343ac1295a7515da9572564513094d2f44c44dca1dffbf927302{F9881592})\" - rotate in reverse order. Top - bottom, left - right.\nIn the new version, rotation more faster. I don't change any preferences, set by default.\n\nI recorded a video. Show the difference in direction of rotation. and increased rotation speed.\n\nwatch?v=mjMZZqNXyaY\n\n[IMG_6214.MOV](IMG_6214.MOV)\n\nsteps to reproduce: download last version 2.92.0 (2.92.0 2021-02-25), run blender, rotate view. It is all time.\n\nT86346" ]

[ "EEVEE/Cycles discrepancy in how image texture node's alpha is managed.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.2.0 Alpha\nWorked: ?\n\nWorkbench and EEVEE perform an unpremultipy calculation when premultiplied alpha mode is selected and the image texture node's alpha socket has a connection.\nWorkbench and EEVEE ignore the image alpha when straight alpha mode is selected and the image texture node's alpha socket has a connection.\nSee: [node_shader_tex_image cc](node_shader_tex_image.cc$125-153)\n\nIn Cycles, there is no apparent difference between the straight and premultiplied alpha modes and the alpha socket's connection status does not change how the alpha is managed.\nSee:\n[shader_nodes cpp](shader_nodes.cpp$200-250)\n[image cpp](image.cpp$471-566)\n[image_oiio cpp](image_oiio.cpp$154-204)\n\nExample:\n\nExample 2:\n\n\n**Test File**\n[Alpha_Image_Test_3.1.0.blend](Alpha_Image_Test_3.1.0.blend)\n", "`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)", "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.", "Material slots undo is inconsistent in non-Object modes\nBroken: 3.0\nMaterial slots undo is inconsistent. Sometimes multiple slots are added/removed in one undo, and sometimes undo won't change back mode.\n\n\ntab to edit mode \nadd a material slot\nundo twice\nadd another material slot\nundo\nboth material slots will be undone. Also undo won't go back into edit mode.\nif you redo both material slots are redone at the same time.\n", "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: 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", "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", "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: GPU Subdivision causes noticeable shading differences\n**System Information: System 1**\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) Arc(TM) A770 Graphics Intel 4.5.0 - Build 31.0.101.4369\n\n**System Information: System 2**\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nThis object does not appear shinier/with brighter highlights when rendered on Eevee and GPU subdivision is turned OFF.\n\nI noticed this when using both PCs to render an animation faster, this particular material flickered at random and it was because one PC was outputting slightly different results than the other.\n\n- Open .blend file\n- select EEVEE engine and start viewport render\n- toggle GPU subdivision to notice the difference\n", "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.", "Different padding between eevee and cycle properties\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.0.0 Beta\nWorked: ???\n\ndifferent padding see image below:\n\n\n\ni dont know is this because new ui design or not.\n\n\n", "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", "Crash without warning when opening material properties panel.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon RX 540 Series, ATI Technologies Inc., OpenGL, 4.5.0 Core Profile Context 22.20.16.03.220829\n\nBroken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379f7\nBroken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3\nWorked: no newer version works.\n\nWe get a hard crash without warning when opening the material properties panel in the \"Layout\" workspace right after startup (i.e. with a clean \"General\" new file). Opening the material properties panel in other workspaces causes the same crash.\n\nI suspect that this is an EEVEE problem since opening other properties panels (which do not have the material preview) works fine and opening the material properties panel after having selected the Cycles engine in the \"Render properties\" panel also works fine. Somehow, it feels like being a hardware problem, but I cannot explain why. Interestingly, the device for rendering in the [Preferences][System] is set to \"\"None\" and no GPU's are available in the Cuda, OptiX, HIP, and oneAPI sections.\n\nWhen switching the viewport in the \"Layout\" workspace to \"Viewport Shading\" (i.e. rendered by EEVEE), Blender crashes. When Cycles is selected as rendering engine, then \"Viewport Shading\" works fine.\n\nThe crash happens on my colleague's computer in India to which I have no direct access. Updating graphics drivers is not easily possible due to company constraints. My colleague now uses the Cycles rendering engine by default. Some current file of her was saved with the default EEVEE setting, so she cannot load the file without crashing Blender; I have now modified the file on my computer by switching it to Cycles rendering which bypasses that problem for now.\n\n\n[Based on the default startup]:\n- Open Blender.\n- Select \"General\" new file\n- Open the \"Material properties\" panel in the \"Layout\" workspace.\n- Blender crashes.\n\n[Based on the default startup]:\n- Open Blender.\n- Select \"General\" new file\n- Select \"Viewport Shading\" in the \"Layout\" workspace.\n- Blender Crashes.\n\n[Based on the default startup]:\n- Open Blender.\n- Load a previously stored blend file with EEVEE set as the renderer (and I suspect showing the \"Materials properties panel\" or the viewport in \"Viewport Shading\" mode).\n- Blender Crashes.\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", "Boolean modifier assigns wrong material\nOperating system: win10\nGraphics card: 1050 ti\n\nBroken: 3.4 alpha\nWorked: 3.3.2\n\nMaterial transferred during boolean operation is not the one assigned to target geometry.\n\n[boolean_material_update_problem.blend](boolean_material_update_problem.blend)\nOpen attached file or:\n\n - Create some boolean difference situation with modifier\n - Add two materials to target, assign first to geometry and put it on second slot -> modifier owner slice has wrong material\n\n\n" ]

[ "Eevee: Only one material is displayed before enter in Edit mode when mesh has multiple materials\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.81 (sub 4)\n\nIf blend file is saved with \"Color\" set to \"Object\", \"Single\" or \"Random\" in the viewport shading settings\n\n\nand mesh has two different materials applied\n\n\nafter switching to \"rendered\" mode in Eevee, only one material is displayed.\n\n[multiple_materials_eevee_bug.blend](multiple_materials_eevee_bug.blend)\n - Open file.\n - Switch to rendered mode. Only one material is visible.\n\n - Switch to edit mode and back. Now it's displayed properly.\n" ]

[ "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Mask invisible on object with modifiers when entering sculpt mode\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: unkown\n\nWhen selecting a previously unselected object with a modifier and a sculpt mask, the mask is invisible at first when entering sculpt mode.\nPainting the mask reveals it.\n\n- Create an object with a modifier (e.g. mirror or array) and paint a sculpt mask on it. Or use the file attached.\n- Outside the sculpt mode first make sure the object is unselected, then select it and enter sculpt mode.\n- The object appears with no mask visible, still you can not sculpt the masked parts.\n- Painting the mask reveals it.\n\n[mask.blend](mask.blend)\n\n[mask.mp4](mask.mp4)", "Select similar face regions doesn't work across objects in multi-object edit mode\nOperating system: Windows 10\nGraphics card: GTX 1070\n\nBroken:\n3.0.0 alpha, 3.1.0 alpha\n\nSimilar face regions don't get selected across objects in multi-object edit mode.\n\n\nBased on the attached .blend file.\n\nI made a scene with a cube and bevelled its edges. I then copied the cube, selected both objects, entered edit mode and selected 3 faces of the active cube object where bevelled edges meet.\nThen I went to Select Similar > Face Regions and Blender selected 7 analogous face regions, but only on the active cube, not on the other object.\nIn comparison, if I add materials to these objects and try selecting faces by similar materials, both objects' faces will be selected. Any other trait among \"Select Similar\" will select faces across multiple objects.\n\n\n\n[similar face regions don't get selected across objects in multi-object edit.blend](similar_face_regions_don_t_get_selected_across_objects_in_multi-object_edit.blend)", "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", "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "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.", "Alpha textures do not work with holdout collection in Eevee\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Beta\nWorked: None\n\nWhen setting a collection to holdout in Eevee, objects with an alpha texture will display as the entire object being held out, but the expected behaviour is possible using a Holdout shader. This can be very inconvenient as then you have to duplicate and remove all models using alpha textures from the collection and create unique materials for them.\n\nThe collection set to holdout.\n\n\nThe expected behaviour using a material with alpha blend to hold out the object.\n\n - Create an object using an alpha texture (blend mode doesn't seem to matter) in Eevee\n - Set the collection containing it to holdout\n\n\n[HoldoutAlpha.blend](HoldoutAlpha.blend)\n", "Hairs not rendered in cycles when edit mode or particle edit mode is active\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nWith the attached file, when you render with F12 while edit mode or particle edit mode is active in the viewport, the hairs are not rendered. In Eevee this does not occur.\n\nOpen attached file, select the bezier curve\nPress f12 to render while in object mode -> hairs are rendered\nSwitch to edit mode or particle edit mode and press F12 -> hairs are not rendered\n\n[Feather hair bug.blend](Feather_hair_bug.blend)\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.", "Backface culling setting applies in Material Preview shading and affects selectability\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90 (sub 3)\nBroken: version: 2.83 (sub 17)\nWorked only if face orientation on in 2.82a release\n\nBackface culling setting applies in Material Preview shading and affects selectability.\nExpected: if it is visible and selectable, I should be able to select it.\n[2020-05-26_00-02-02.mp4](2020-05-26_00-02-02.mp4)\n\n**Steps to reproduce**\n[nonselectable.blend](nonselectable.blend)\n\n- Open file\n- Try to select octagon", "Eevee: Occasional render glitches when using attribute node\nOperating system: Linux, specifically KUbuntu with X11\nGraphics card: RTX 3080 (Driver Version: 530.30.02, CUDA Version: 12.1)\n\nBroken: 2.93 - 4.0.0 Alpha, 2023-06-29, f47eed749eaf\nWorked: 2.92 (as available on Steam)\n\nUsing an attribute in an Eevee material causes occasional but severe render glitches. This does not happen consistently on any particular frame. It does not happen when rendering from the command line with `--background`.\n\nTo reproduce, render an animation with the attached Blender file. One in every 50 frames or so are corrupted. Occasionally it gets most of the way through the animation before ever producing a bad frame.\n\nThis file is basically the startup file with two changes:\n1. An attribute node with the name set to \"Color\" is plugged into the base color on the default material.\n2. The sample count is lowered to one. (The issue persists without this, but with a higher sample count, some samples glitch and others do not. The final image is a mix of the glitched and regular samples.)\n\nI have ensured that this is not a problem with my particular Blender settings by deleting everything in `~/.config/blender/4.0/config` and selecting \"Save New Settings\" in the splash screen before opening and rendering the file in the 4.0.0 alpha.\n\nNormal frame:\n\n\nCorrupted frame (as rendered in 2.93, some other versions simply display a transparent hole where the cube was without affecting the background):\n\n\n", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Partial UV selection working incorrectly with Metal backend\nOperating system: macOS-13.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0 Beta\n\nUsing hide unselected in the UV editor seems to randomly 'explode' the UVs around the map.\n\nOpen [file](https://projects.blender.orgattachment), go to edit mode.\n\nUV is very messy, but when everything is selected, it's OK. Works fine with OpenGL backend\n", "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." ]

[ "EEVEE displays wrong material\nOperating system: Linux-4.15.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 11)\nWorked: 2.80\n\nSometimes, if mesh object have several materials, EEVEE can display whole object just in one of them. \nIf you switch to edit mode, it fixes, but only on selected object. But if you reset materials in this way many times, blender may crash (not very often)\n\n\n\n* Open file:\n[materials-test.blend](materials-test.blend)\n* Swich to rendered mode - whole object is black:\n\n* Switch to edit mode and back - now only handle is black:\n\n\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.", "2.83.2 and 2.9.0 problem with bone selection inside another bone\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: AMD Radeon HD 6670 ATI Technologies Inc. 4.5.13417 Core Profile Context 15.301.1901.0\n\nBroken: version: 2.83.2\nWorked: (in blender 2.80 worked as expected)\n\nBone selection problem, inside another bone\n\n\nBlender 2.83.2 and the latest version 2.90 currently have a problem with bone selection in both Edit mode and Pose mode.\n\n1. If you create a bone and then copy it and scale down. In Edit mode with the OpenGL Depth Picking enabled and xray-mode on, you can only select bone tail inside another bone. If select the bone itself, the outer bone is highlighted. \nI tested this with both, my settings and Factory Defaults, the problem occurs in both cases.\nVideo demonstration: NksQCnU6kjs\n\n2. If you create a bone and then copy it and scale down. In Pose mode with the OpenGL Depth Picking enabled and xray-mode on, you can't select bone tail and bone inside another bone. \nI tested this with both, my settings and Factory Defaults, the problem occurs in both cases\n\n3. If you create a bone and then copy it and scale down. In Pose mode with the OpenGL Depth Picking disabled and xray-mode on, you can select bone tail inside another bone, but you cannot select a bone along its edge inside another bone.\nI tested this with both, my settings and Factory Defaults, the problem occurs in both cases.\nVideo demonstration: Su6GZJg_-Ak\n\nversion 2.8 does not have this problem\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", "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.", "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", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "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", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "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", "\"Whole Character\" keying set not working properly with autokey enabled\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 2.93.4\n\nUsing the keying set \"Whole character\" with autokey enabled creates a keyframe only for the selected bone and not for all bones and properties.\n\n- Open attached file or create a new armature with more than one bone, add a few bone properties to each bone.\n- Enable autokey and set \"Whole Character\" as the keying set.\n- Move one bone and you can see that only the transform values are keyed.\n- If you enable \"Only active keying set\" in the autokey options and move the bone, a keyframe for the custom properties of the selected bones, at least, will be created, but other bones and properties will be unaffected.\n[bugreport.blend](bugreport.blend)\n", "Bone selection icon could be added next to Face and Vertex Selection in Weight Paint mode\nHello. I want to suggest to add a Bone Selection icon in weight paint mode by side the face and vertex selection modes. It intents to be a better feedback on what selection mode the artist is using. Now it is like having only face and edge selection icons for mesh editing but not vertex because it is the \"default\" tool. I know the bone selection is not a mask tool like the face and vertex selection, but, at the end, all 3 are just selection modes for the artist workflow.\n\nCheerios\n\n", "Painting across different resolution UDIM tiles in image editor crash.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\n\nIf you have UDIMs of different resolutions, and you paint in the Image editor window across the tiles, you get a crash.\nIf you do the same thing in the 3D viewport, there is no problem.[CrashFile.7z](CrashFile.7z)\n\n\nCreate a UDIM texture, with at least two tiles, of different texture resolutions. \nIn the image editor in paint mode, draw a line across the tiles and it will crash. Sometimes I need to draw two lines crossing the tiles for it to crash.\n\nThat's all, you don't need to apply the textures to a model or anything else.\n\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```", "Unexpected viewport bone limit\nOperating system: Ubuntu 22.04.1 LTS\nGraphics card: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate]\n\nBroken: 3.3.5\n\nSelecting the 8192th bone in an armature with 10.000 bones will select bone 0.\nWith to many bones in one armature viewport selection fails.\n\n1. Open a fresh blender instance\n2. Create an Armature and add 10.000 bones\n3. Select the 8192th bone.\n-> The 0th bone will be selected instead\n\nSelecting the bone via the outliner works as expected.\n\n", "Action Editor: Animations no longer work after renaming bones.\n**Information & Blender version**\nWindows 10, 64 bit, CPU integrated/no graphics card [doubt it's relevant but: AMD A8-7600 Radeon R7]\nBroken Blender Version: 3.3.0, master, 2022-09-06, hash: 0759f671ce1f\nNo idea if it worked in a previous Blender version.\n\n**Description**\nThis happens while using Action Editor and creating several actions to store different animations.\nIf at some point you rename bones, the action that is currently active will automatically update it's paths and continue to work, but any previous actions will not update their path and the animation will no longer play. \n\nFixing it requires either:\n1) manually changing the name of each affected path through the graph editor.\n2) Select the bone, select the affected channel under the action summary, temporarily change the name back to what it used to be, then change it again to the new name. This way the path gets updated.\n\n\n**Reproduce Error & File**\nYou'll need to create at least 1 bone first.\nCreate an action [dope sheet/action editor] and make an animation.\nCreate a new action, make a new animation, and change the name of the bone. The action that is currently active continues to work, but any previous actions now have a broken path and no longer work.\n\nIn this file I made 2 actions with different animations, I had \"Action 1\" active while I renamed the bone form \"Box\" to \"Bone\". Now \"Action 1\" continues to work, while \"Action 2\" no longer plays.\n\nFor this test I changed the name of the bone while in pose mode through Bone Properties.\n\n**Important note: This seems to not happen all the time, I'm not sure why.**\nWhile making this file to recreate the issue, I first created both actions actions and animations, and I had \"Action 2\" active when I changed the bone's name from \"Bone\" to \"Box\". This seemed to create the error for a moment, but when I changed from \"Action 2\" to \"Action 1\" and back to \"Action 2\" it resolved itself and I was able to see both animations.\nI then had \"Action 1\" active while I changed the name of the bone from \"Box\" to \"Bone\", and now the error persisted. [even after closing and reopening the file]\n\nI made the test again with a new file [not attached] and the error persisted, I saved the file, closed it, and after re-opening the file the error was gone.\nSo it seems sometimes the paths get updated automatically and other times they don't.\n\n[BrokenActionTest.blend](BrokenActionTest.blend)" ]

[ "Clicking the edge of a Bone in Edit mode Crashes Blender in 2.9 Alpha\nAMD Ryzen 7 3700x\n\nOperating system: Windows 10 Pro 64 Bit\nGraphics card: ASUS ROG Strix GeForce GTX 1070 Ti 8GB GDDR5 Advanced Edition\n\nBroken: (2.90.0-b74cc23dc478 alpha, ) \n\nThere are no errors, the program just self terminates.\n\n\n\n4 Steps\n\n1.Create a bone.\n2.go into edit mode.\n3.left click on the edge of said bone. \n4.Profit\n\nThis happens in a brand new blender scene file.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nVideo for further proof.\nlzzOqzG" ]

[ "Undo in Armature Edit Mode does not undo Custom Properties\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.5 Beta\n\nUndo in Armature Edit Mode does not undo changes to Armature Custom Properties\n\n- [optionally] In default scene delete all objects\n- Add an \"Armature\" object\n- Go to `Edit Mode`\n- In `Object Data Properties` add a `Custom Property`\n- Change the value of the property (to for example `0.0`) in order to add an Undo step\n- Try undo (`Ctrl+Z`)\n\nThe step is not undone in edit mode.\nInterestingly, changes to the Custom Properties of Bones are correctly undone in Edit mode.\nThis makes it seem that changes to Armature Custom Properties were perhaps missed in the Armature Edit Mode Undo Context.\n\n---\n**Original Report**\n[Video](3RZNWd5tRQI)\nNote when changing the **head size** in the redo panel, you can observe how the number of elements in in the Collection Property `bones_for_delete` grows.\n\n1. Execute the script generate_rig.py from the file, if you do not have automatic script execution enabled\n2. After execution, the Generate Rig panel will appear in the Rig category\n3. Select Empty.021 first, then Armature.001. Switch to armature editing mode, and click Generate Rig on the panel\n4. The bones will appear, and also the text on the panel will notify that there are elements in bones_for_delete. After that, you can scroll the **head size** on the redo panel, or simply undo the operator. the label in the panel will notify you that the number of items will not change\n\n", "Pose Mode X-Axis Mirror is not working properly with IK when skeleton is moved\nIntel Core i7, 16 Gb RAM, NVidia GeForce 2070 RTX\nWindows 10 x64\n\nBroken: 2.83 cfdb5d9a8b07 from 2020-02-19\nWorked: 2.83 5df494d75c9a from 2020-01-27 although it seems that this feature was introduced recently so technically it wasn't working before because symmetry didn't work with IK at all.\n\nPose Mode X-Axis Mirror is not working properly with IK when skeleton is moved or rotated from zero in Pose Mode.\n\n1. Open provided test file and try moving selected bone - opposite side will twitch weirdly instead of moving symmetrically.\n2. Now reset the skeleton to its default position and move the same bone - symmetry will work properly.\n3. Rotate first bone and try again - weird twitching again.\n[IK_Symmetry_Error.blend](IK_Symmetry_Error.blend)", "Startup File Viewport view is tilted by around 0.8 degrees since 2009 (Blender 2.5)\nNow, before you click away, I know what you're thinking, how can the default 3D View be tilted? This guy must have messed something with his camera, or activate the trackball views settings by mistake right?\nWell believe it or not, the default 3D view (as in, the view of the default 3D viewport in the blender startup file) is tilted by around 0.8 degrees.\n\nHere is a quick proof I just threw together, I believe it's important for you to watch it until the end, as the main proof really comes around 0:40.\n\n[tiltedview.mp4](tiltedview.mp4)\n\nAs you can see, when trying to align your view with the cube, it doesn't lined up, this can be seen by the jagged selection edges, and of course with the Camera aligned to view.\nYou can also see at 0:35 that when switching to the Front Orthographic viewpoint the view gizmo itself is rotating on the X axis a little bit.\nAnd of course, when switching back to the normal Perspective view, the viewport view is realigned, enhance why the Camera that's been re-aligned with the view is now sitting properly on the X axis. (see 1:10)\n\n**Now, why is this happening?**\n\nAfter a bit of investigating, I discovered that the issue as been around since **Blender 2.5**, which is now more than **10 years ago**\nBlender 2.5 was the first version to have the default startup file view not lined up with one of the orthographic axes. But it also had the Trackball orbiting style as default instead of Turntable. This might explain why, 10 years ago, a blender dev might have tried to get the view somewhat lined up in trackball mode, and got it almost right.\nHere's a quick demo of the same problem on 2.5 Alpha 0:\n\n[tilted25.mp4](tilted25.mp4)\n\nNow, while this isn't a top priority issue, this as been around for quite some time now, so this is not really an inquiry for an immediate fix, but more of a way too long report I did since I couldn't find anything on it online, and it drove me crazy for a few hours when I first discovered it.\n\nBroken: 2.5 Alpha0 and beyond\nWorked: 2.49b, where the view was orthographic by default\n\nStart Blender, use the viewport (Will disappear if snapping to an Orthographic axis)", "Add object redo: exits local view if there are no other objects in local view\nBroken: 2.80 to 2.92 master\nWorked: 2.79b\n\n\nIf you're in local view and there are no objects, add an object and attempt to adjust any property in the redo panel, Blender drops out of local view. However, if you don't touch the redo panel and instead e.g. transform the object, local view is retained.\n\n\nIn the default scene with cube selected:\n\n- enter local view\n- delete the cube\n- add a new object\n- attempt to adjust any property in the redo panel", "Dynamic Paint With UNDO [Control Z] Crash Blender\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen Press Control Z While In Weight Paint (EDIT MODE), Blender Crash\n\nBased on the default startup or an attached .blend file (as simple as possible).\n[weight-paint-v1.blend](weight-paint-v1.blend)\n1. Open the provided .blend file\n2. Start playback and enter Weight Paint mode\n3. Paint and then undo (Control + Z)\n4. Blender crashes after a while,\n\nHere is video to show case KUUbxSnwmbE", "UV: Add 3D Gizmos for UV projections, Cube, Cylinder and Sphere projection\nThe \"Unwrap > Projection\" operators are powerful, but would be even better with artist control over exact placement in 3D space.\n\nPropose to add gizmos in the 3D viewport to allow precise artistic control over the cube, sphere and cylinder.\n\nConsider adding Planar Projection as well.\n\nThanks @BlenderBob for the suggestion!\n\n", "Missing undo push for Paint Mask and Vertex Selection in weight paint\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.0 Alpha\n\nEnabling or disabling of the Paint Mask and Vertex Selection modes is missing an undo push\n\n\n\n[Weight.blend](Weight.blend)\nEnable Paint Mask\n\nPaint on the model\nUndo\nResult: Both the paint and the paint mask mode are undone", "Collection usability\n- [ ] Viewport UI\n- [ ] Shortcuts to toggle visibility?\n[ ] . . .\n\nNeed a clear design on what to do.", "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", "inconsistancy in runing script console vs editor, pose mode bones transformations.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.2\n\nthere is difference when running script from blender editor vs blender python console \n\n\n1. the example suppose to place bones from one armature (B) on another (A) while in pose mode.\n\n2. when running the script in editor mode the result is unpredictable and you can click few times and get different results.\n\n3. when copying the whole script and run it in the blender console its seem to work just fine. \n\n4. keep up the great work.\n\nTest File:\n{[F10327076](bone_to_bone_test03.zip)}[tests02_no_try.zip](https://archive.blender.org/developer/F10325225/tests02_no_try.zip)", "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)", "Bone Heat weighting: failed (due to none of the vertices in an island being visible to any bones)\n**Win 10 64. gtx 970**\n\n**Blender 2.75a Hash c27589e**\n\n**Bone Heat weighting: failed to find solution for one or more bones**\n\nI attach the blend file and two prints..\n\nAlso the same broblems apper when i try to \"assign automatic from bones\" by individual bones in Weight Paint. Like one by one. Please see print2.\n\n\n\n\n\n[cat.blend](cat.blend)\n", "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", "Annotation tool: wrong undo order and different in different modes\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: 2.93.2\nBroken: 3.0.0 Alpha, `c1f5ac7cfe`, 2021-07-25 18:36\nBroken: 2.83.17\nWorked: never\n\n\n| Object mode | works correct, as expected. Each undo action undoes 1 stroke |\n| -- | -- |\n| Weight paint | works properly |\n| Vertex paint | works properly most of the time, sometimes as Texture paint |\n| Texture paint | do not undoes each stroke but after number of {key Ctrl+Z} (n=strokes) undoes all strokes simultaneously or disables em at n=strokes+1 and undo previous action (mode switch in my case) |\n| Edit mode | same as Texture paint |\n| Sculpt mode | Undoes strokes one by one, but on the last stroke it do not react to {key Ctrl+Z} once, and then on the secon disables stroke and previous action (mode change) |\n\n**Steps to Reproduce**\n- Open default scene\n- Switch to Edit or texture paint mode\n- Draw 4 strokes with annotation tool\n- Undo 4 times (nothing happens to any stroke)\n- Undo again: Clears all strokes\n[2021-08-15_15-46-27.mp4](2021-08-15_15-46-27.mp4)\n\n", "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\n\n" ]

[ "Object Mode: XRay Draw Option\nNote: There are many draw options and it's likely we won't bring them all back, adding this one since its often used for pose-mode drawing." ]

[ "EEVEE: Slow Shader compilation when editing Vector Transform Node values\nOperating system: Windows 11\nGraphics card: GTX 1060\n\nBroken: 3.0, 3.6\nWorked: \n\n**Short Description**\nThe Vector Transform Node output doesn't update when changing input value used for unconnected socket. \nIt updates normally if a Combine XYZ is used instead. It also updates normally in Cycles Renderer.\n\n**Steps to Reproduce**\n- Open .blend file\n- Change `vector` socket value with mouse-drag (shaders are compiling until mouse is steady/released)\n- Now Connect `combine XYZ` to `vector transform node`\n- Edit socket values of `Combine XYZ` node\n\n", "Attribute Node Doesn't Function Under World Shader Context\nOperating system: Windows 10 19044.1826 64-bit, Linux 5.18.14.arch1-1\nGraphics card: NVIDIA GeForce GTX 1080 Ti\n\nBroken: 3.2.1\nWorked: never\n\nThe `Attribute` node (both in Cycles or Eevee) doesn't work under World materials.\nAlso the `Geometry` and `Instancer` types in the node are irrelevant in the Word context and should be hidden.\nMaybe the `Object` type should be renamed to 'World', but it currently doesn't seem to be able to pass world properties as uniforms.\nThis essentially means that:\n - There are redundant elements in the World shader node editor that currently serve no purpose\n - There is no way to pass custom uniform attributes to World shader nodes, although they should be available (similarly to how it is done for objects)\n\n\n\n- Open attached .blend file\n- Note that the \"test_color\" attribute of the World is not read by the material.\n[AttributeWorldShader.blend](AttributeWorldShader.blend)", "Alpha textures do not work with holdout collection in Eevee\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Beta\nWorked: None\n\nWhen setting a collection to holdout in Eevee, objects with an alpha texture will display as the entire object being held out, but the expected behaviour is possible using a Holdout shader. This can be very inconvenient as then you have to duplicate and remove all models using alpha textures from the collection and create unique materials for them.\n\nThe collection set to holdout.\n\n\nThe expected behaviour using a material with alpha blend to hold out the object.\n\n - Create an object using an alpha texture (blend mode doesn't seem to matter) in Eevee\n - Set the collection containing it to holdout\n\n\n[HoldoutAlpha.blend](HoldoutAlpha.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)", "Material rendered as black with motion blur and intersecting geometry (was:motion blur bug in geometry nodes)\nOperating system: Linux-5.13.0-23-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.2\n\nBroken: version: 3.0.0\n\nwhen i turned on motion blur seems that exactly when a instance intersects another instance is rendered as black\n\nwhen motion blur is turned on and two instances instect each other its rendered as black\nif frame 27 is rendered u are able to see the bug\n\n[domino line.blend](domino_line.blend)\n\nedit (Martijn) : Renamed to make the problem slightly clearer. \nIt doesn't happen every time, when rendering with Optix I can reasonably reliably reproduce it.\n", "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.", "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", "Artifacts appear in texture bakes [stripe pattern]\nOperating system: Windows 10 Pro 64-bit\nCPU: i7 4790\nGraphics card: GTX 1050\n\nBroken: Every Blender Build on this PC, Baking.\nWorked: never\n\nWeird artifacts appear in bakes, especially visible in the AO bakes (see attached images)\n\n\n\n\n\n[AOArtifacts_Test.blend](AOArtifacts_Test.blend)\n- Open blend\n- hit `Bake`", "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", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "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)", "Eevee preview nodes with drivers performance drop Round 2\n[NodesPerformanceDropRound2.blend](NodesPerformanceDropRound2.blend) this is extend of previos task #71214\nSystem Information\nOperating system:Windows 10\nGraphics card: GeForce GTX 1060\n\nBlender Version\nBroken: Blender 2.81 Beta aff6446e064f and 2.82 Beta 092deb88b074\nWorked: 2.8\n\nShort description of error\nComplex shader with large amount of math nodes and with drivers slow down performance\nin 2.8 60 fps\nin 2.82 30 fps\n\nExact steps for others to reproduce the error\nCreate material with 30 node groups contains 30 math nodes, add driver to shader. Set viewport to material preview and watch performance droping", "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", "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: Texture Coordinate Node in world shader render artifacts (AMD)\nOperating system: Windows-10-10.0.17758 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.2 26.20.13003.1007\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\nstable 2.80\n\nViewport shading glitches bad when using any HDRI, it doesn't show up in reflections, also using in-build textures like (noise, magic, voronoi etc) produces serious performance drops set to anything other then 2D mode.\n\nsee screenshot attached \n" ]

[ "Crash after undo \"Mask slice to new object\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\nWorked: This problem happens to me with 2.92, the pc that I use now I formatted it, unfortunately before I used version 2.82\n\nMy problem is that when I use the option \"mask slice to new object\" and then I use ctrl + Z the blender closes !! I formatted the PC a few weeks ago, unfortunately I didn't use version 2.92 before. What I realized is that when I use the \"mask slice to new object\" option and then go to edit mode, I can use control + Z without any problem, that is, it does not close.]\n\nThis happens to me in any file:\n\n1. Sculpture mode.\n2.Use the \"mask\" or \"box mask\" brushes\n3. I paint the mask.\n4.I go to the \"MASK\" menu.\n5. I click on \"mask slice to new object\".\n6. Press CTRL + Z.\n7. Blender closes.\n", "Redo panel does not work for the 3d cursor\nUbuntu 18.04\n\nBroken: 7d38654\n\nRedo panel for moving the 3d cursor does not work as expected.\n\nStart moving the 3d cursor and then change the value in the redo panel.\n\n\n\nMy guess is that this happens because the 3d cursor is not effected by the normal undo.", "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", "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 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)", "2.91 - Undo in Sculpt Mode switches tool to inflate brush (specific to attached file)\nOperating system: Win 10 64-bit\nGraphics card: Nvidia GFX 1060 6GB\n\nBroken: \n - 2.90.1\n - 2.91.0, from steam, seems *file specific*\n - 2.92.0\nWorked: 2.91.0, same version, fresh file\n\nWith attached file: In sculpt mode calling undo changes the tool to \"Inflate\" besides undoing.\n\nAdditionally, when undo is called via menu, the undo operation happens only when undoing so far back sculpt mode was entered. On reentering Sculpt Mode, tool is set to \"Inflate\". \n\nThis issues seems to be tied to this specific file, as it's not reproducible in a fresh file. The file was created with blender 2.91.0. I sculpted multiple objects using both Dynamesh and Remesh in Sculpt Mode. I deleted the sculpts to keep the file size small and since the same behavior persisted with newly created geometry (in this case a cube). I don't know how to debug this any further, any hints appreciated. As a workaround I will try to reimport the geometry into a new file.\n\nBased on the attached .blend file [SculptModeBug.blend](SculptModeBug.blend)\n\nUndoing with shortcut:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - hit ctrl + z\n - tool switched to \"Inflate\"\n\nUndoing via menu:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - modify mesh with tool\n - call \"undo\" from menu \"edit/undo\" - this has no effect\n - call \"undo\" from menu \"edit/undo\" until the point object goes back to Object Mode - changes get undone\n - On entering Sculpt Mode again, the active tool has switched to \"Inflate\"\n", "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", "Creating a new image texture in shader editor does not appear among the texture slots\nWindows 10 Pro 64bit, AMD Ryzen 5 2600, 16Gb RAM\nNVidia GTX 1060 6Gb\n\nWindows 10 Pro 64bit, AMD Ryzen 5 1600, 8Gb RAM\nNVidia GTX 1050Ti 4 Gb\n\nBlender 2.8 Beta 91a155833e59\n\nIf you are texture painting in one window and you modify the shader by adding/removing an image texture to it in another, it won't appear/disappear from the texture slot list until you change to edit mode (or anything else) and back. Another issue is that this way you can paint onto an image texture that is no more connected to the shader and it doesn't disappear even if you do the \"edit mode and back\" (TAB x2) trick.\n\nSteps: Add an image texture to the shader in the attached file, connect to the roughness for example, create a new texture for. It won't be in the texture slots list. Now TAB x2 in the 3D view, slot appears. Paint on it, delete the node from the shader. It is still in the list. TAB x2. It is no more in the list, but the 3D view still shows the texture.\n\n[test1.zip](test1.zip)", "Cycles takes very long to cancel a render\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: 2.93\n\nEver since Cycles was upgraded to Cycles X whenever I render a scene with a high Max sample count and cancel the render mid-render it always takes very long (up to a few minutes) until the render actually stops.\nThe time it takes to until the render stops seems to be proportional to both scene complexity and Max sample count.\nAt the start of rendering the samples first go up at small increments and later go up at greater increments. The greater the increments between sample count updates the longer it takes to stop the render.\nChecking Task manager shows that after hitting `cancel render` it does keep using the GPU, therefore keep rendering, until it finally stops.\nDuring the time between hitting `cancel render` and Cycles actually stopping the render the entirety of Blender becomes completely unresponsive.\n\nThis is only a problem when actually rendering the scene. Viewport render doesn't seem have this issue.\n\nTest file:\n[untitled.blend](untitled.blend)\n\nHit render and wait a little until the rate samples go up slows down. The hit `cancel render`.\n\nThank you and have a great day!", "Video Editing: Undo kills Rebuilding Proxy when it wasn't the last command\nOperating system: Windows 10\nGraphics card: GTX 960\n\nBroken: 2.92\n\nVideo Editing: Undo kills Rebuilding Proxy when it wasn't the last command:\n1. add the video file to the timeline\n2. click Rebuild Proxy and Timecode Indices\n3. rebuilding proxy process should start\n4. split the strip\n5. click Undo\n6. the rebuilding proxy process breaks", "Apply Base (Multiresolution Modifier) on mesh with shape keys distorts the mesh\nBroken: version: 2.83 (sub 8)\nWorked: Doesn't Work even in Blender 2.79b official release. I haven't tested versions earlier than that.\n\nPressing Apply base using the multires modifier on a mesh with a stored Basis shape key causes artifacting and mesh corruption. Undo still works though.\n\n1. Delete Default Cube\n2. Add Plane mesh (Shift+A > Mesh > Plane)\n3. Add Basis Shape Key.\n4. Add Multiresolution modifier\n5. Subdivide multiple times. (Either Catmull-Clark or Simple type)\n6. (optional) Apply brush strokes in Sculpting mode. \n7. Press Apply Base in Modifier Properties.\n\nor\n\n1. Open attached file\n2. Press Apply Base in the Modifier Properties.\n\n[Shape key Multires Bug.blend](Shape_key_Multires_Bug.blend)\n\n", "Color picker undo adds step when cursor exist\nRun blender, logging undo events:\n\n```\n blender --log \"bke.undosys.*\" --log-level -1 --log-show-basename\n```\n\n\n\nClick on the object color swatch and move pointer away from the popup.\n\nEven though no changes have been made, an undo step is added.\n\n----\n\nIsn't high priority, reporting so it's not forgotten.", "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.", "Erratic behaviour of materials/material slots for text objects\nOperating system: Linux-5.19.0-45-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.6.0\n\nMaterial assignment for text objects doesn't behave as expected. Removing an unused material slot will cause changes to the materials used by the object. The same happens if you rearrange the material slots.\n\n1. Add a new text object. Leave the default string \"Text\".\n2. Add 3 new material slots with different materials to the object. Use different viewport display colors to be able to see changes.\n(You will now have Material.001, Material.002 and Material.003)\n3. In edit mode, select the last two letters and assign Material.002.\n(You should now have \"Te\" using Material.001 and \"xt\" using Material.002)\n4. In object mode, remove the last material slot containing Material.003.\n(This material was not assigned to any character, and removing it should not cause any change.)\n5. All 4 letters are now using Material.001. \"xt\" should still be using Material.002.\n\nAlternatively, execute step 1-3 above and then.\n4. Move the last material slot up to the first place.\n(This should not cause any change. Normally in blender, the materials used by the geometry will not change if you rearrange the material slots.)\n5. You will now have \"Te\" using Material.004 and \"xt\" using Material.002. \"Te\" should still be using Material.001.\n\nI have attached a blend file where you just need to remove the last (unused) material slot to see the problem, or move the last material slot up to first position.\n\n", "Linking/Moving collection to another scene messes with the object visibility.\nOperating system: Windows 11\nGraphics card:\n\n**Blender Version** \nBroken: 9719fd696488\n\n\n\nThere is no reason the object visibility should not be carried over when the collection is moved or linked to another scene.\n\n\n[blender_HRo7zHHvN3.mp4](blender_HRo7zHHvN3.mp4)\n\nload the attached .blend\n\nselect the TEST collection in scene.A\n\nleft click drag onto scene.B while holding ctrl to link the collection instead of moving it. Moving the collection has the same affect\n\nopen scene.B and check the visibility\n\n\n\n[tests_06122022_1933_13.zip](tests_06122022_1933_13.zip)\n" ]

[ "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots." ]

[ "Cycles Render: Volume (Before Baked Simulation Starts) still trying to be rendered\nOperating system:windows 11\nGraphics card:nvidia geforce rtx 2060\n\nBroken: 3.4.1\n\nThe cycles render tries to use the volume cache to render if the frame is less than the start of the simulation. See video example.\n\n1. Default cube: Add Quick Smoke.\n2. Cache settings:\n a. Type: All.\n3. Start frame: 50, end: 100.\n4. Bake.\n5. Start render on 30~ frames.\nExpected: Simulation chunks will appear in different parts of the domain.", "Problems due to leftover Nvidia drivers\nOperating system: Windows 11 Home\nGraphics card: Intel Arc a770 16gb Limited Edition (latest drivers)\n\nBroken: (Blender 3.3, 3.5 and 4.0) Trying to work out if it is just my GPU that is the issues\n\n\nBlender 3.5.1 will not allow me to access editor preferences, and won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 3.3 allows me to access editor preferences, but still won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 4.0 allows for editor preferences, same issue with Cycles. Eevee works fine.\n\nBy not allowing me to access editor preferences or Cycles I mean it crashes.\n\nI have tried to converse with Intel engineers with a video of the crashes but they seem incompetent with knowing how to enable GPU rendering in their own tests.\n\n", "Discrepancy between CPU and GPU rendering/material behaviour\nOperating system: macOS 13\nGraphics card: AMD W6800X Duo MPX module\n\nBroken: 3.3.1 (latest full release)\n\nI bought some assets which render with weird artefacts with the GPU, but work fine with CPU.\n\nThe assets are made by Bproduction (Florian Benedetto) on Blender Market. They are trees and vegetation models, which can be used individually or with Scatter 5.3. Simply put: they render properly with the CPU (Mac Pro, 24-core Intel), but render with horrible artefacts using the dual GPU. This doesn't happen with any other assets or materials I have.\n\nThe images below show the issue. I believe it's something to do with the material setup, but in any case it should render properly under both systems. Maybe it's an issue with macOS drivers?\n\n\n\n", "Regression: Tiled rendering is not applied to texture baking in 3.x onwards, causing crash on large bakes\nOperating system: Win10\nGraphics card: AMD Radeon R9 280x\nSystem RAM: 32gb\n\nBroken: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: bcfdb14560e7, type: release\n(also tested Daily 3.2.2 and beta 3.3)\n\nWorked: 2.8x, 2.9x, 2.9 LTS\n\nPreviously tile based rendering was applied when using the bake to texture feature, allowing baking to very large canvases. As of version 3.x tiled rendering no longer applies when baking textures and crashes on large canvases. In my case I can no longer bake to a texture larger than 2^14 (16384x16384).\n\n- Open attached file or\n - From a new blend file, delete default cube,\n - switch renderer to Cycles (CPU).\n - Create a plane,\n - switch to UV and create a very large texture (in my case anything larger than 16384x16384, my previously and still working in 2.9x size is 19310x) with float precision and no alpha.\n - Create a new material,\n - remove the principled Shader,\n - connect the color output of a noise texture to the material output Surface,\n - add an Image Texture node and select the previously created canvas. In my case I disable bounces (set all to zero) and set samples to 1, Filtering to Box filtering. \n - Switch bake type to Emit.\n- Hit bake and blender crashes trying to allocate the memory for the render target canvas. Setting Tiled rendering to other sizes does not work either.\n\nNotes:\nI'm prebaking complex noise channels as it dramatically reduces render time on the final texture bake.\nYou may need to create an excessively large target canvas if you have a lot of ram.\nWhen stopping a bake half way through on 2.9x and lower version you can see tile based rendering has taken effect and the sizes declared are used.\nWhen stopping a texture bake on 3.x versions you can see that it is filling the entire canvas at once and not using tile based rendering, no matter what the tile size is set to.\n[bake_crash.blend](bake_crash.blend)\n", "Bake All Dynamics doesn't include all when Lifetime of particle system gets animated\nOperating system: Windows 10\nGraphics card: Quattro\n\nBroken: 2.91.0\nWorked: \n\nWhen the lifetime setting of a particle system gets changed during an animation of the emitter and the animation gets baked, the number of frames are not aligned to the changed lifetime. \n\nInitial lifetime of 100 will be changed during the animation to 500. Number of frames after bake is the frame end setting of the particle system plus the initial life time setting - in this case 100.\n\n- Open attached file or (Based on the default startup):\n - Set number of frames to 1.000\n - Create a sphere - size .1\n - Enter keyframe on frame 0 for location x,y,z\n - Move sphere on x-axis to +10\n - Enter keyframe on frame 250 for location x,y,z\n - Add particle system to the sphere, 1.000 pieces, start frame 1, end frame 250, lifetime 100\n - Add keyframe for lifetime on frame 1 and frame 49 with lifetime value 100\n - Add keyframe for lifetime on frame 50 with a lifetime value of 500\n\n- Bake all Dynamics\nYou will see 351 frames in memory and not 751 as expected\nAlthough the error is the same, rendering of animation does still work in Blender 2.83.5 but not in Blender 2.91.0 anymore\n **WORKAROUND:** Set keyframe for lifetime on frame 0 with lifetime value 500 \n[LiveTimeTest_002.blend](LiveTimeTest_002.blend)\n\n\n\n", "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```", "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.", "High poly meshes perform poorly with planer decimate\nOperating system: Windows 10\nGraphics card: AMD Asus Vega RX64\n\nBroken: blender-2.81-92736a7b7592-windows64 (plus previous few builds - atleast)\nWorked: 2.8\n\nMy PC is decent, and I have had no problem decimating millions of vertices (albeit some few seconds of lag) usually. Right now, I'm trying to decimate a simple model with about 45k vertices only. The decimate modifier is working fine on default settings i.e., on 'Collapse' setting .. but as soon as I switch to 'Planer' .. Blender becomes unresponsive for several minutes at least (and also indefinitely in some cases). \n\nI noticed that in my task manager, the Blender is only using 29% of CPU.. and regarding RAM .. on one side it shows 61% usage, while the actual usage is only 289MB in the value column (see screenshot). Could this be a memory related overflow/underflow? This definitely does look like a bug to me. \n\n\n\n\n\n", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)", "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)", "Baked cache files should not depend on blend file name\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: 4.0.0 Alpha\n\nBaking eg. Dynamic Paint will create a folder with .bphys files. When I save the scene under a new name and reload the scene the baked files will be ignored. I need to delete the cache and Bake All Dynamics again.\n\nThe baked result should be independent of the scene filename.\n\nMaking the baked files internally independent of the scene filename is important for our render management with CGRU because CGRU will save a specific filename for the clients. Then the clients can't render the baked result.\n\nWorkaround in my case:\n\n- Submitting job\n- Stopping job\n- Loading scene\n- Delete All Bakes\n- Bake All Dynamics\n- Save scene\n- Restart the job\n\nBake something with Dynamic Paint. Save a new scene, reload and check if the baked result will be rendered.\n\n", "Cycles GPU Compute 5000 x 5000 pixels render F12 crashes\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0 Alpha\n\nCycles GPU Compute 5000 x 5000 pixels render F12 crashes\n\nMacOS 13.5\nSee youtube about Blender crash guide during 5000 x 5000 pixels.\n\nNot matter both same crash Blender 3.6.3 and 4.0\n\n", "EEVEE Cryptomatte Processing Performance\nCurrent implementation uses a single core. During implementation it was always kept in mind that we should do the processing in a threaded way. It should also be possible to render the next sample during the integration of the previous sample in the accumulation buffer.\n\nAnother solution would be to do the sorting on the GPU using compute shaders. [D10913: GPU: Compute Pipeline.](D10913)", "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" ]

[ "Slow GPU bake and blown out baking cycles render\nCard name: AMD Radeon (TM) R9 Fury Series\nCard name: AMD FirePro W8100 (FireGL V)\nOperating System: Windows Embedded 8.1 Industry Pro 64-bit (6.3, Build 9600) (9600.winblue_ltsb.150715-0840)\nProcessor: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz (12 CPUs), ~3.3GHz\nMemory: 32768MB RAM\n\nBroken: 2.7.6rc1 and 2.7.5.4\n\nWhen baking in GPU compute am receiving blown out Ambient Occlusion and Normal maps. Works fine in CPU. \nwhen baked with CPU: BlvA7.jpg\nwhen baked with GPU: SsJI3.jpg\n\nSwitch mode to cycles render. Add Suzanne smart uv unwrap her. Add image texture in node editor, and create and use a texture. Switch device to GPU compute in render properties. Switch Bake type to Ambient Occlusion or Normals. \n" ]

[ "Cannot disable shadows if an object is set to holdout.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: Confirmed on Version 3.4 to version: 3.5.0\nWorked: Never (Goes as far as 3.0, since the addition of the \"Object Properties -> Visibility -> Holdout\"option)\n\nCannot control an objects shadow visibility if the object is set to holdout. Having a shadow on a holdout object does not work as expected, especially when trying to use the holdout object as a 3d mask.\n\n\n- Set scene renderer to Eevee.\n- Create an object, set \"Shadow Mode\" to none in the material shader of said object.\n- The object will no longer have a shadow, as expected. \n- Set the object to holdout via \"Object Properties -> Visibility -> Holdout\" option, and the shadow reappears. Can not turn off shadow as long as this option is on.\n - However, if use Holdout shader in the nodes and connect it directly to the Surface output, no shadow will appear (this matches expectation).\n\nAdded a file that directly shows the issue.", "GP: Time offset and Armature modifier causes glitches\nOperating system:WINDOWS10\nGraphics card:GTX1060\n\nBroken: 2.93LTS\n\n\n[#89433.blend](T89433.blend)\n\n- Open file\n- Move selected bone to left until it hits constraint, and then a bit randomly\n\nGP object will keep rotating in one direction and can be reset only by changing frame.\nSame happens when scrubbing in negative frame range.\n", "Metaballs particles with drag force disapearing\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.33.01\n\nBroken: version: 2.83.2\nWorked: Never (2.8+)\n\nHi Guys,\n\nas you could see in the atachment file, the metaballs instances particles disapears on certains frames ...\nThere is no problem when Drag Force is not applied\n\nThanks in advance for your help !\nYour Software is amazing !! We love it !\n\n[MetaballsParticlesBug.blend](MetaballsParticlesBug.blend)\n\n- Open file\n- Play animation", "After duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\n\nBroken: `master` branch\nWorked: Don't know if it ever worked\n\nAfter duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\n\n**Steps to Reproduce**\n\nIn a new blender project, add a new collection. Add a cube to the collection. Add a rigidbody to the cube. Verify that playing the simulation causes the object to fall under gravity.\n\nCopy and paste the cube to create a new cube inside the collection. Move the new cube so both are visible. Verify that playing the simulation causes both cubes to fall under gravity.\n\nIn the outliner right-click on the collection and select \"Duplicate Collection\". Move the two new cubes so all four cubes are visible. Run the simulation.\n- The two cubes in the original collection will fall under gravity.\n- The two cubes in the duplicate collection do not move and are not affected by the simulation.\n\n \n\nIt appears the two cubes in the duplicated collection are not added to the RigidBodyWorld collection.\n\n", "Connected child bone's nominal location values affected when transformed about 3D cursor\nBroken: 2.79, 2.90.1\nWorked: N/a\n\nAs expected, when moving a single connected child bone, its location is not affected, only the rotation.\nBut it is still possible to affect them accidentally if transforming about the 3D cursor.\nThis is a minor bug, but it's a definite inconsistency.\n\n - Open attached file.\n - Move/Rotate/Scale the child bone about the 3D cursor.\nNote the bone's nominal location values in the side panel.\n\n[Connected Bone Pose Bug.blend](Connected_Bone_Pose_Bug.blend)", "Particles appear above where they should not appear (with rigid bodies)\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 780M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 2.92.0\nWorked: 2.79\n\nI have a cube that is an active rigid body that falls on a floor (another cube) that is a passive rigid body. The falling cube has a particle system. I tell the particles to start in the frame that coincides with the impact of the cube with the floor and to finish emitting one frame behind. The problem is that at the moment of impact this particle appears in the air, I attach an image of when it appears and then when it disappears everything continues normally. Particles only appear above when it coincides with the same frame in which there is a collision in the rigid body. In 2.79 this does not happen. In 2.92 and 2.93 if it happens. Greetings, I attach an example scene made with 2.92 stable.\n\n1 add cube an scale (this is the ground) \n2 add pasive rigid body to ground\n3 create a cube an put an raise it up a little\n4 add rigid body active to the cube above\n5 add particles to the cube above\n6 in the same frame as when the top cube collides with the ground and to finish broadcasting one frame later\n7 Now we play and we see that at the moment of impact, particles appear above where they should not appear.\n\n\n\n\n[particles_bug_when_collide_rigid_body.blend](particles_bug_when_collide_rigid_body.blend)", "Blender 2.8. In edit mode when you have hard scene (slow down processing) all your actions will applyes not at right moment (not at click but at moment when blender finn. caclucations)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 53)\nWorked: (optional)\n\n\nI have scene where I put a lot boolean(and not only) modificators on one objects and when I enter into edit mode all processing erally slow (each action: movement, extrusion, etc..) And problem here in next: when you doing any action (and it took time to process it) and then press mouse button to apply action affect, but! it will not memorize position of the mouse when you pressed, and still continue doing (move to the cursor) And this really anoing because you need repeat all twice or more time. Or just seating and waiting with no mouse movement at all, when it will apply action effect. \nSo core problem is that: in edit mode any affect will applyes not at moment when you decide but by moment when CPU will finished calculetion of movement/action and will change your action to position where is going be mouse positioned at the moment of the end calculation... something like that. \n\nCreate some worcload/heavy scene. For example by a lot subdivisions and booleans at object. When each your action will be like \"under water gravity\" slowed down. And then try to change(extrude/move vertext / anything) boolean part that will be used as cut area in the edit mode. \n\n[2019-04-01 17-39-35.mov](2019-04-01_17-39-35.mov)", "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", "Overriding context in rigidbody operations [override not passed along in startup/bl_operators that themselves call bpy.ops]\nOperating system: Ubuntu 16.04 \nGraphics card: MSI 1080Ti\n\nBroken: 2019-03-26, 337eb8c1de4c\n\nContext override information in bpy.ops.rigidbody.bake_to_keyframes() not shared with bpy.ops.anim.keyframe_insert() causing poll() error.\n\n- Open default file\n- Give cube active rigid body\n- In the python editor:\n```\nobj = bpy.data.object['Cube']\nobj.select_set(True)\nbpy.context.view_layer.objects.active = obj\n\nfor area in bpy.context.window.screen.areas:\n if area.type == 'VIEW_3D':\n for region in area.regions:\n if region.type == 'WINDOW':\n override = bpy.context.copy()\n override['area'] = area\n override['region'] = region\n override['scene'] = bpy.context.scene\n override['point_cache'] = bpy.context.scene.rigidbody_world.point_cache\n bpy.ops.rigidbody.bake_to_keyframes(override)\n```\n\nReturns:\n```\nRuntimeError: Operator bpy.ops.anim.keyframe_insert.poll() failed, context is incorrect\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", "\"Whole Character\" keying set not working properly with autokey enabled\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 2.93.4\n\nUsing the keying set \"Whole character\" with autokey enabled creates a keyframe only for the selected bone and not for all bones and properties.\n\n- Open attached file or create a new armature with more than one bone, add a few bone properties to each bone.\n- Enable autokey and set \"Whole Character\" as the keying set.\n- Move one bone and you can see that only the transform values are keyed.\n- If you enable \"Only active keying set\" in the autokey options and move the bone, a keyframe for the custom properties of the selected bones, at least, will be created, but other bones and properties will be unaffected.\n[bugreport.blend](bugreport.blend)\n", "Dependency cycle detected even when the constraint is inactive\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 527.56\n\nBroken: version: 3.3.0\nWorked: Never\n\nBlender complains on inactive (disabled) dependency cycles each time when I bake animation.\nUnfortunately it affects the baking process (the keys are baked with the delay in one frame). \nI know it might not be considered as the bug, but it is a problem:\n For instance: I'd use empties to fix feet sliding the ground during the complex character root motion movements. \n To make it work first I constraint empties to feets, bake the animation, delete the constraints, then clean up the empties animation so they keep stable toward the surface and finaly constraint the feets to the empties to bake fixed animation. \n Defenetly I would not want to create and delete the constraints over and over again: it is much easier to turn them on and off during the work. Same goes with objects that can guide a character or be guided by one during the same scene. We might just want to choose when the object is constrained to the character and when the character should be constrained to the object. \n \n So when the constraint is disabled it should not be considered as the dependency cycles. (It should not be considered in general)\n1. Create some bone and an empty\n2. Add a Copy Transforms constraint to the bone. Choose the empty as the target.\n3. Add a Copy Transforms constraint to the empty. Choose the bone as the target and **disable the constraint to break the loop.**\n4. Animate empty and try to bake this animation to the bone in a pose mode.\nOnce you press Bake Action (with Visual Keying On) you'll have a warning: Dependency cycle detected like if you have both constraints enabled. \nThe animation will be baked with the delay in one frame.\n\n", "Generic Rigid Body Constraint Bug\nOperating system: Windows 10\nGraphics card: Radeon RX 470\n\nBroken: 2.83.0\nWorked: Unknown if it ever worked\n\nAngle limit not only doesn't work but causes weird neverending twitching back and forth\nUPDATE:\nTwitching happens for both cases when both rigid bodies are active and when one of them is passive.\n[M0DJ38oWQo.mp4](M0DJ38oWQo.mp4)\n\n1. Add 2 rigid bodies, 1 active, 1 passive animated\n2. Position them active on top, passive on the bottom\n3. Add an empty in between them, add a rigid body constraint to it, select the 2 rigid bodies in its settings, uncheck disable collisions.\n4. Change the joint type to Generic, limit location to 0-0 on each axis.\n5. Play. Now it works, once you select the passive RB and move it it should behave normal.\n6. Undo. Check angle limit on Z and choose some angle range (I had it set to -30 to 30).\n7. Play. Move the passive RB and watch it breaking.\n", "Performance issues when moving bones of an armature when the Outliner is set to Blender file\nBroken: 2.93\n\nThis happens on heavy scenes and with many linked files, if you have an Outliner opened and set to \"Blender file\".\nThe fps drops dramatically only when trying to move a bone of an armature. It doesn't matter the complexity of said armature.\nThe problem stops happening after closing the Blender file Outliner.\nCould it be related to this other fix? T87842", "pan gesture behaves randomly\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.4.1\n\nHi,\n\nOn external monitor, two fingered pan gesture on a Mac touchpad behaves randomly between orbit and zoom\n\nThis happens when you use the default Orbit & Pan navigation settings. Most of the time it works correctly: You make a two fingered pan gesture and the camera view orbits. But once a while a two fingered pan gesture will zoom the camera view (instead of obiting). As if you are making a pinch gesture (which you are not). I have disabled the pinch gesture on the system level to rule out the possibility that the pinch gesture interferes with the pan gesture. It is not a pinch gesture conflict.\n\nTo me it looks like following is happening. It seems like that although you have multi-touch gestures enabled, the two fingered pan gesture is sometimes handled as if multi-touch gestures is disabled. (When you go to Input > Touchpad preferences and disable Multi-touch Gestures then the camera view always zooms when you make a two fingered pan gesture.) \n\nThis happens about once every minute, and sometimes even a couple times a minute. It's random. When it happens and you don't end the gesture (you keep your fingers down on the touchpad) then you can continue to zoom in and out by moving two fingers left and right. So once the pan gesture handler chooses to zoom instead of to orbit then it is locked in this zoom behaviour until you end the pan gesture.\n\n\nWorkaround: 103973#issuecomment-79513\n\n" ]

[ "Rigid body dynamics: Initially deactivated objects are not activated on collision, but on bounding box intersection\nMacOS 10.12.3\n\nBroken: 2.78 2017-02-23\n\nWhen setting the rigid body dynamics of an object so that \"Enable Deactivation\" and \"Start Deactivated\" are both enabled, the expected result is that the object is \"activated on collision with other objects\" (quote from the manual). Instead, the object is already activated when its bounding box and another active and dynamic rigid body object's bounding box intersect, even if the two objects never collide.\n\nOpen the attached .blend, then start the animation (Alt-A or click on play) and watch closely at what point the capital T is activated (it starts falling down).\nAlternatively, there are two small spheres behind the text. The top sphere is deactivated, but the bottom one immediately activates it even though they don't collide.\n\n[rigid body activation threshold test.blend](rigid_body_activation_threshold_test.blend)" ]

[ "Sculpting/Painting on invisible objects\nOperating system: Linux-6.5.2-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.2-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-b492f73f87)\n\nBroken: version: 4.0.0 Alpha\nWorked: ---\n\nThis is an inconsistency that I noticed when toggling between collections of objects while working on an asset. It's most likely not a regression.\n\nIn edit mode it's impossible to operate on the selection if the object is currently hidden. This is very helpful to prevent mistakes and as feedback that you might be editing the wrong object atm.\n\nWhile in sculpt mode or any of the painting modes this is not the case. If the object is currently hidden while in sculpt or weight paint mode, it is possible to use the brushes on the geometry.\n\nIdeally any operation should be prevented if the object is hidden.\n\n1. Enter edit mode.\n2. Select everything.\n3. Hide the object or collection in the outliner.\n4. Try to move or otherwise edit the selected geometry.\n5. Show the object again (No edits should have happened).\n6. Enter sculpt mode and hid the object/collection again.\n7. Use a brush on the hidden object.\n8. Show the object/collection (See the edits that have been done).\n\n", "Sculpt Mode: Occlusion blurring steps\nFor View and Area auto-masking we implemented Limit and Falloff sliders for controlling the extend and softness of the mask.\nThese are disabled when \"Occlusion\" is used.\n\n\n\nWe need to implement a setting to blur the edge of the Occlusion mask.\nThe easiest solution would be to add additional \"Blur\" steps, similar to the Cavity masking.", "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", "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.", "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", "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", "It is not possible to set a hotkey to Transfer Sculpt Mode\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nIt is not possible to set a hotkey to Transfer Sculpt Mode. Neither using the right-click menu nor via the Settings (including using the Python command)\n\n- Open default scene\n- Switch to Sculpt mode\n- {nav Sculpt > Transfer Sculpt Mode > Right click > Remove Shortcut}\n- Now try to assign shortcut\n\nThe shortcut wasn't saved.", "Auto smooth smooths triangulated faces despite faces beeing set to flat shading/EEVEE smooths faces when it shouldn't\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.0\n\nWhen using cycles after enabling auto smooth it smooths the faces after triangulation despite setting faces to flat shading, meaning that a quad will still have flat shading compared to it's neighbors but instead of showing 2 flat tris it will show 1 smoothed quad.\nWhen using EEVEE it always smooths the faces after triangulation despite setting faces to flat shading even if auto smooth is turned off, so depending on whether or not this is intentional behvior, the title might also be \"triaglulated faces not smoothed correctly in cycles when auto smooth disabled.\"\n\nTest file:\n[Test.blend](Test.blend)\n\n2 almost identical Suzannes. Both are set to shade flat, but the left one has auto smooth enabled while the right one does not.\nNote that the triangulation is not visible for the left suzanne.\nSwitching to EEVEE shows that the triangulation is not visible for either of them.\n\nThank you and have a great day!", "Multires Unsubdivide freezes Blender with hidden geoemtry\nOperating system: Linux-5.15.0-41-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.3.0 Alpha\n\nIn the Multiresolution modifier the buttons \"Unsubdivide\" and \"Rebuild Subdivisions\" do a similar operation.\nWhen having any faces in edit/sculpt mode hidden though, using any of these operators will freeze Blender.\n\n- Subdivide Cube a couple times\n- Apply modifier\n- In edit mode, hide some faces\n- Add multires modifier (Don't add any more subdivisions)\n- Use \"Unsubdivide\" or \"Rebuild Subdivisions\" \n\n[#99887.blend](T99887.blend)", "Material glitches at joints when using Bevel modifier\nOperating system: Ubuntu 20.04.3 LTS\nGraphics card: GeForce RTX 2060\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked:\n\n\nI know people experience no end of unexpected Bevel behavior due to issues with their geometry. But I think this is a genuine bug - as do people who responded to my Blender SE question: 124535\n\nRobin Betts commented there that \"it looks like a bug. But at least a consistent, and therefore traceable bug. It seems to be in the 'Automatic' (-1) material offset setting, which should split the bevel down the middle at material boundaries. It's getting the boundary 1-off at the end of a patch/arc spread of faces.\"\n\nAt joints where two materials meet, the Bevel modifier seems to miscalculate which faces of the bevel should contain one material and which the other, as shown here:\n\n\n\nIf I apply the modifier, I can then correct the issue by hand.\n\nThe above picture is from Blender 3.1.2. The problem seems to have been there for a long time, things look different but are still incorrect in 2.93.7:\n\n\n\nThe complete mesh is fairly simple (I cut it out of a larger object for this bug report) and I've confirmed there are no overlapping vertices etc.:\n\n\n\nI actually started with a much simpler mesh but converted to triangles to ensure the issue wasn't somehow n-gon related (it isn't):\n\n\n\n\nCreate a simple shape like the one shown in the last image above and use two different materials for your object, e.g. above, I've applied one material to the darker colored faces and the other to the lighter colored faces.\n\nThen apply a *Bevel* modifier and then look at the object in a *Viewport Shading* mode that shows materials, e.g. *Material Preview* or *Rendered* (you can even see the issue with *Solid* viewport shading if you set the *Viewport Display* for one of the materials to be a different color to the default grey).\n\nHere are two small `.blend` files - the first created in Blender 3.1.2 and the second in Blender 2.93.7:\n\n[bevel-3.1.2.blend](bevel-3.1.2.blend)\n\n[bevel-2.93.7.blend](bevel-2.93.7.blend)\n\nYou can find a larger `.blend` file containing the original full mesh in my Blender SE question: 124535", "Speedup request for switching to objects with multires in sculptmode \nMy name is Daniel Bystedt and I'm currently working with @PabloDobarro as commissioner for #81180 (Sculpt Mode Performance). After testing sculpting in Blender in general I wanted to give some feedback on the Multires modifier after discussing this with Pablo. It's a general request about being able to switch objects and switch from sculpt to object mode faster. I hope this can be useful. \n\nvideo example details:\n**Raw geo:**\n582 480 vertices\n\n**Multires :**\nhas 2 sculpt levels.\nbase level is 36 405 vertices\nsculpt level 582 480 vertices\n\n\n**Switching objects in sculpt mode**\nSwitching between objects in sculpt mode feels a bit slow when the object that you are switching to has a multires modifier. Switching between objects when sculpting is something I do quite frequently, so it would be fantastic if it would be possible to speed it up a bit.\nswitching to raw geo (no multires) = 0 sec 903 ms\nswitching to object with multires = 1 sec 767 ms\n\n\n[sculpt switch object.mp4](sculpt_switch_object.mp4)\n\n**From sculpt to object mode delay**\nThere is a slight delay when switching from sculpt mode to object mode. Switching between these modes is not done super frequent, so it's not a high priority issue but I thought I'd mention it.\nswitching to raw geo (no multires) = 435 ms\nswitching to object with multires = 969 ms\n\n[sculpt to object mode.mp4](sculpt_to_object_mode.mp4)\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", "Inconsistent naming for modes in the undo history menu\nBroken: 3.4 alpha\n\nIn the undo history panel, the \"Object mode\" entry is registered with the name of previous modes. Switch from sculpt mode to Object mode will create an undo step with \"Sculpt Mode\" name\n\nAs for the other modes entries, they have no naming standard. Some entries have \"Toggle\" written before, some have \"Toggle\" after, some don't have \"Toggle\". Also they all have \"Mode\" written except for texture paint. \nThe entries are as follows:\n\n\"Texture Paint Toggle\"\n\"Weight Paint Mode\"\n\"Vertex Paint Mode\"\n\"Toggle Edit Mode\"\n\"Sculpt Mode\"\n\nBased on the default startup;\nChange modes; \nCheck \"Edit -> Undo History\" menu.\n", "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", "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" ]

[ "Regression: Smooth shading issues with multiresolution\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 Alpha\nWorked: 3.2\n\nCaused by 285a68b7bb\n\n9 levels of multiresolution on the cube, full smooth shading.\nWhen I enter sculpt mode, i have flat shading and smooth only appears partially around the pointm where I touched surface with brush\n\n[2022-06-14_17-03-09.mp4](2022-06-14_17-03-09.mp4)\n\n[brushes.blend](brushes.blend)\n\n" ]

[ "Wireframe not visible with X-ray in weight paint mode.\nOperating system: Win10\nGraphics card: GTX 1070\n\nBroken: 3.0.0\nWorked: 2.93.6\n\nWireframe on other side of mesh can't be seen through faces when x-ray is enabled.\n\n[#94704.blend](T94704.blend)", "Particle systems on a moving emitter with particle settings start/end outside the animation frame range showing up in wrong place intermittently\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nBroken: 3.0.1\nWorked: xx\n\n[Desktop 2022.02.10 - 14.44.35.08.mp4](Desktop_2022.02.10_-_14.44.35.08.mp4)\n\nRepro steps with particle_bug.blend (attached)\n[particle_bug.blend](particle_bug.blend)\n1. Press play, observe:\n - on the initial frame of the animation, a cubic volume of particles spawn at the initial position of the cube\n - when the animation loops, the trail of particles disappears\n**This is the behavior I believe is a bug.**\n\n2. Change the animation start frame from 40 to 0, and let the animation play through at least one full loop.\n3. Change the animation start frame back to 40, and observe:\n - on the start frame of the animation, no cube of particles appears at the initial position of the cube\n - when the animation loops, the trail persists with each particle seeming to remain in its existing location.\n**This is the behavior I believe is intended when using duplicate particle systems with non-overlapping timespans to create the illusion of looping particles.**\n\n4. In the particle properties tab on the right, select the 'during' particle system (instead of the currently selected 'pre' particle system), and observe:\n - the behavior from step 1 immediately resumes: the particle trail disappears and the cube of particles appears at the initial position of the cube on the first frame of the animation.\n**This is the easiest way that the bug can be reproduced predictably.**", "Source Collection visbility will affect the final render of the links object(geo nodes) in eevee/cycles\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nWhen collection is used in GN tree and it is disabled for final render (camera icon in outliner). Then the new object is not visible in final render\nWhich is not the case when object is used instead of collection in GN tree\n\n1. create a simple object\n2. move it to a new collection\n3. turn off the collection's visibility\n4. new object with geo mod, use the collection as output\n5. render, the new object didn't show in the final render(but viewport)\n\nor \n- Open test file\n- Do final render i.e. F12 (object is not visible in final render)\n- Now connect `object info` node to group output and render (object is visible)\nTest File\n[#97535.blend](T97535.blend)\n[2022-04-22 12-55-10.mp4](2022-04-22_12-55-10.mp4)", "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", "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)", "Wire objects that are being displayed on front only updates visibility after interaction\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nThis problem is similar to the one found in #84717, but in this case it is only affecting objects that are marked as in front and wired mode. I noticed it happening in a rig, but It can be applied at anything that is wire.\n\n\n- Using Any object go to viewport display and mark in front and set it to wire in the display as. (you can also use a rig with custom shapes, e.g. the one in rigify.)\n```\n{F12895660}\n```\n- Disable and then Enable Overlays\n[2022-03-03 11-21-26.mp4](2022-03-03_11-21-26.mp4)", "Search Filter, when used, vanishes collapsed modifiers headers texts.\nOperating system: Linux-6.4.6-76060406-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05\n\nBroken: version: 3.6.2\n\nSearch Filter, when used, vanishes collapsed modifiers headers texts.\n\n\n\n<video src=\"attachment\" title=\"Peek 2023-08-23 15-53.mp4\" controls></video>\n\nType any text in the search filter for some object with a bunch of modifiers collapsed and the texts on the box are gone. They are only displayed if modifiers are expanded.\n\n", "Eeevee SSS Artifacts with Subsurface Translucency on\nOperating system: MacOS 10.15.2\nGraphics card: AMD Radeon Pro 5500M 8 GB\nBut it's worth noting I've also seen this on Windows machines with Nvidia cards.\n\n\nBroken:2.81a (release), also broken in 2.82 latest alpha (December 25)\n2.80 seems to have a similar problem, but it looks a little different and maybe not as extreme (though I haven't tested in all lighting situations)\n\nWhen working with high contrast lighting setups, materials with SSS and subsurface translucency turned on generate artifacts that look a little like banding. This can be reduced to some degree by raising the shadow cube size, but I've yet to see it disappear entirely. This is especially frustrating since these are the exact kinds of lighting conditions that can make SSS really shine. \n\nYou can get this by setting up a material with SSS, scaling down the SSS scale, turning on subsurface translucency, turning off or lowering the environment lighting, then lighting the object with the material from the size. It can be finicky to get it to occur sometimes depending on your model and settings, but I've encountered it in a number of ordinary situations\n\nProbably the easiest way to reproduce it is to just load up the attached blender file and hit render or turn on the viewport\n\n\n[mnkysss.blend](mnkysss.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Regression: Curve wire line not displayed in wireframe display mode when it has evaluated mesh/point/volume\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.2.0 Alpha\nWorked: 2.93\n\nCaused by b9febb54a4\n\nThe original curve line for curves is not displayed in wireframe display mode.\nThis change only applies when the curve is changed during evaluation, for example, when it is replaced by an evaluated \"tube\" mesh, or points, or a volume, etc.\nThis is very similar to #96138 (Regression: Curve wire line not displayed in edit mode when it has evaluated mesh/point/volume), but for objectmode.\n\n- create a curve\n- in the curve properties, give it a bit of extrude\n- enable viewport shading wireframe OR\n- enable object Viewport Display properties > Wireframe\n\n3.0+\n\n2.93\n\n\n", "Applying Subdivision/Multires Modifier De-merges UV's\n### Update\n\nThe issue of custom-data (UV's specifically) becoming detached remains, this problem existed before b88dd3b8e7, it was just less obvious since selection connected near-by UV's. Now UV's are merged by default at a very low threshold when applying modifiers to mitigate the problem. Keeping this report open as it would be good if subdivision-surface didn't separate UV's, replies to this report contain some notes that could lead to a solution. In practice users should not experience problems caused by this behavior, so marking low priority. ~ @campbellbarton.\n\n----\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha \nWorked: working in 2.90 \n\nCaused by b88dd3b8e7\n\nWhen applying a subdivision modifier, certain UV's points disconnect from their neighbors. This does not seem to occur with the F3 menu subdivide operation.\n\n- Open default blender scene.\n- Subdivide cube - 1 level and apply it. Do this step 4x\n- In the UV editor use \"Alt select\" to select face loops at random.\n- Alt click around until a face loop is not fully completed, this will reveal unmerged vertices.\n- Check area that did not complete by moving faces, vertices, edges etc to confirm unmerged UV's.\nThis does not seem to be an issue with the newly added 9a52b30cc0 in my eyes, rather an issue with subdividing.\n[UV Disconnect.blend](UV_Disconnect.blend)\n\n", "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.", "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", "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 ", "Dopesheet Display Hidden doesn't work property combined with Only Selected.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: Version 2.79b\n\n\nIn version 2.79 with the \"Selection Only\" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations.\n\nFrame 1:\nTurn off the object then Animate Disable in viewport,\nFrame 2:\nTurn on the object and animate Disable in viewport.\nOpen dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear.\n\n[Dopesheet_280.blend](Dopesheet_280.blend)\n[Dopesheet_279b.blend](Dopesheet_279b.blend)\n\n\n", "Edges created by a bevel modifier are visible even for hidden items in edit mode (in wireframe display)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I did not follow it back to n previous versions.\nThe Problem is also reproducable in the latest nightly e362a2f0d41f\n\n\nIn mesh editting mode, if you hide an edge that is affected by a bevel modifier, the edges created by the bevel modifier are still visible. I expect them not to be visible because the edge is hidden.\n\n\n1. Open the attached file.\n2. There is one mesh in edit mode. One of the edges is affected by a bevel modifier.\n3. One face is already selected. Press Shift+H to hide all unselected items, including the aformentioned edge.\n4. You still see the result of the bevel modifier even if the edge is hidden. I expect it not to be visible. \n\nIn practice, this caused many confusing \"ghost\" lines of invisible items.\n\n" ]

[ "Round objects with too many subdivisions become invisible in wireframe mode\nOperating system: Windows 7 64bit\nGraphics card: nVidia GeForce GTX 660\n\nBroken:\n2.8, 1df6a98b176f, 2019-03-05 00:32\n\nAdd a default cube or a sphere. Turn on wireframe mode. Ctrl+5 to add a subdivision modifier. Deselect the object. Object is invisible and unselectable (can be selected only by clicking on the origin point). " ]

[ "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled", "linked objects un-parent after save and load.\nwindows 8.1, Geforce 660\n\nBroken: #5ebae1c\nWorked: i couldn't test as how far this existed as old versions won't compile against the current SVN.\n\nlinked objects un-parent after save and load.\n\ni included 3 files:\nfile 1: the parented objects.\nfile 2: the objects linked.\nfile 3: the parent object changed to local, everything is fine till it is saved it will un-parent!\n\n[1.blend](1.blend)\n\n[2.blend](2.blend)\n\n[3.blend](3.blend)", "Bone IK constraint - add lockable axis properties for stretching\n*Adding task after e-mail conversation with Sybren 2020-12-17*\n\nThe bone IK constraint can activate stretching on the constrained bones if constrained bones has \n\n**Properties / Bone properties / Inverse Kinematics / IK Stretch > 0**\n\nexample:\n```\nbpy.context.object.pose.bones[\"Bone.005\"].ik_stretch = 0.01\n\n```\n\nThe problem is that the constrained bones stretch in all axes and not only in the +Y axis of the bone, which results in unwanted \"scaling\" of each bone. \n\n---\nHere is a video showing the issue:\n\n[ik stretch.mp4](ik_stretch.mp4)\n\n---\nMy suggestion is to fix this by adding properties to each bone that show the resulting IK stretching per axis on each bone. These properties should be readable (for drivers) but not possible for the user to change, since the stretching is generated. The property should be lockable by the user in order to fix any unwanted scaling on a specific axis.\n\nAnother solution is to add properties that is a factor (multiplier) to the scaling/stretching per axis. The upside is that the user can change the values, but the downside is that the user does not have a property to read the generated IK stretch values. \n\nI leave it up to you to decide what is the most \"blender way\" in regards to implementation.\n\n\n", "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", "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", "Unique generic attribute names can break armature binding process\nOperating system: N/A\nGraphics card: N/A\n\nBroken: Current main (48950ff934de4)\nWorked: 3.6 (before extending unique names to vgroup as 'virtual' part of generic attributes)\n\nRelated to/caused by !109910.\n\nParenting (binding) a mesh to an armature is broken if other existing generic attributes are already using some of the bones' names.\n\nSee also 31073\n\nStarting with default cube from default startup file:\n\n1. Add (or rename) a generic attribute to `Bone` (e.g. a UVMap).\n2. Create a default, one bone armature.\n3. Parent the cube to the armature, with one of the vgroup creation options (e.g. automatic weights).\n4. The newly created vgroup is named `Bone.001`, and the bone does not deform the cube object at all.\n\nFinal result: [armature_bones_generic_attributes_name_collision.blend](attachment)\n\n--------------------\n\nNote: this is a very dumb, but also very good example of the kind of issues that name uniqueness is going to cause in existing code and workflows.\n\n", "Set parent to > Keep transform without inverse. - Don't work with animation.\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 536.23\n\nBroken: version: 3.6.2\n\nSet parent to > Object ( Keep transform without inverse. ). Doesnt keep transform with animation\nThe child jump to another positions like the \"keep transform\" of the operation didn't worked.\n\n\nYou can watch the video below.\n<video src=\"attachment\" title=\"Blender 2023-09-13 08-53-20_edit.mp4\" controls></video>\n\nExact steps needed to reproduce the issue. Based on the default startup .blend file.\n1. open blender 3.6.2 lts\n2. select the cube. press g. move the cube. \n3. maj + a. add mesh > torus. \n4. select the torus. frame 1. object propertie. press i to create keyframe at xyz position\n5. move to frame 40. press G. move torus. press i to create keyframe at xyz position\n6. select the torus and the cube. The cube must be the active object. press Ctrl + P > parent without inverse and keep transform.\n7. move the timeline cursor. The position of the torus jump to another location\n\n", "Accessibility: Rigging bone text cannot be resized independently \nOperating system: Darwin-20.0.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.0.33\n\nBroken: version: 2.91.0 Alpha\n\nLet me show you an example of Rigging on bone text.\nThe text in viewport here is too small.\n\nSo I try to increase Theme > Text style > widget > points.\n\n\n\nBut it also creates overlapping blocks in the rest of the interface. This is problematic when they cannot be resized by command + two finger scroll (MMB), like in top bar menus.\n\n\n----\n\nChanging resolution doesn't work since the menus eat up a lot of space on the screen. \n\n\n\nSee previous link T79059\n\nEnable armature names in Object data properties. \nAttempt to resize the name of the bone.\n", "Hair particles rendered as an object do not follow parent object when the parent object is falling under gravity as a rigid body when animating\nOperating system: Microsoft Windows 10 Home, Version 10.0.18362 Build 18362\nGraphics card: GeForce GTX 1080\n\nversion: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4caf4, type: Release\nbuild date: 2020-03-12, 15:41:08\nplatform: Windows\n\nI have an issue where i have a cube mesh, I create hair particles, and set the hair to render as an object, say a cylinder. I then enable rigid body physics for the cube. I also have a passive plane below the cube. When I run an animation, the cube falls as if under gravity and stops at the plane, but the cylinder particles remain in their original position?\n\nIf I add soft body physics to the cube and order the soft body physics before the particle settings, then the cylinders fall, but lag behind the cube. The cube falls through the plane below, but the cylinders are stopped by the plane?\n\nWith soft body added (to top of stack). Particles do fall but have a lower acceleration rate, and the cube no longer detects the floor and passes through the plane?!\n\nThanks!!\n\nSee attached blend file [StackExchangeParticleProblem-001.blend](StackExchangeParticleProblem-001.blend)", "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", "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", " 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)", "Custom property of armature object not up-date visual value with pose bone transorm value\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nArmature object custom property which driven by the armature bone transform value,not change value as visual untill select the property in properties objcet panel\n\n\nWhen I move mouse curser on the property area, it suddenly change value. but when I rotate bone along with X , it not up-date value.\n\n\nThough value seems up-date correctly (internal) , but when use bone driver to control many property,\nlike driven propA drive other propB, propB drive shape keys ,, etc,,current behavor make really difficult to check pose bone driver working or not. \n\n- Open attched file\n- In the 3D View Sidebar, change the bone rotation X value. (This value drive the custom property float value label as \"prop\". The driver expression only use one variable var = transform channel bone X rotation value).\n it not up-date visual value in object property panell >>custom properties prop value. , until select the prop value area. \nBut In driver editor view prop value actually up-date (change with bone X rotation value)\n\n[bonedriver.zip](bonedriver.zip)\n\n\n \n\n", "Copying in edit-mode copies the entire object, not the selection\nthere is an issue occurs when a part of (mesh) is copyed in the edit mode \nwhat happens when copying one part of a (mesh) and pasting it\nyou suppose to get this part only pasted ,but instead you get the whole (mesh) pasted\n\nfor examble if you have a cube model with a single face selected in the edit mode \nif you copyed then pasted it the result is the whole cube modele is pasted rather than the single face \n \n \n\n", "Mesh Deform modifier doesn't deform after binding\nBlender 3.3.0 (hash: 0759f671ce1f)\n\nMesh Deform modifier simply doesn't work. The cage mesh doesn't deform the effected mesh.\n\nI modeled my base mesh (a simple array of duplicated rectangles). Then i added a cube, as a separate object, entered Edit Mode, adjusted the size to fit my base mesh, added some loop cuts, exited Edit Mode. Selected my base mesh, added the Mesh Deform modifier, chose the object to deform with, clicked on Bind. \n\n[mesh deform.blend](mesh_deform.blend)\nThe deformation mesh is a solid geometry. I just changed the Viewport Display option to Wire. " ]

[ "Make parent --> Bone : Weird behaviour\nOperating system: Mint 19\nGraphics card: Nvidia 860M\n\nBroken: 2.80 build of feb 21rst\nWorked: Blender 2.79\n\n\nMake parent --> Bone : Weird behaviour\n\n* Keep default cube\n* Add an armature\n* Select Cube, then Armature, change to pose mode, and select your bone\n* Make Bone parent (Ctrl + P --> Bone)\n* Cube moved where it shouldn't\n* Weird : In \"Make parent\" panel (where you can change parameters of just exec operator), checks \"keep transform\" --> Cube back to original location, but when you uncheck, keeps the default location \n\nMore weird things:\n* On a new file, after making bone parent (where cube moved):\n* Clear parent (Alt+P)\n* Make Bone parent again (the cube don't move)", "Parenting an Object ot a bone messes the position of the object up\nOperating system: Windows 10 64bit\nGraphics card: Nvidia 1060 6gb\n\nBroken: blender-2.80.0-git.552b2287db86-windows64\nWorked: 2.79\n\nUsing Ctrl+P >\"Bone\" or \"Bone relative\" to parent an object to a bone, shifts the position of the object, as opposed to how it worked in 2.79 or parenting an object to another object.\n\nIf you unparent to restore the object to the original position, and parent again to the same bone, it doesn't happen a second time, unless you parent the object to a different bone and the bug happens once again\n\nUse this 2.79 file to test parenting the cube to the bones. And try the same in 2.8 to test the difference\n[bug10.blend](bug10.blend)\n[bug.mp4](bug.mp4)", "Parenting to bone offsets object\nOperating system: Win10\nGraphics card: 2x 1080 Ti\n\nBroken: 2.80 Beta, 54ffc4e19dc4\nWorked: 2.79\n\nAs the title says: Parenting to a bone offsets the mesh. The mesh doesn't have any tranformation or any other offset-creating effect/animation applied. \nOne thing which helped: checking the Relative Parenting checkbox positions the object back to the starting position. \n\n\nStart a new Blender file, 3D cursor should be at the world origin, create a mesh (doesn't matter which one), create an armature (automatically you get one bone). Parent the mesh to the bone, see how the mesh get transformed.\n\n\n[offset_parenting.blend](offset_parenting.blend)", "Parenting objects to bones causes offset\nOperating system: MacOS 10.14.2\nGraphics card: AMD Radeon R9 M395X 4096 MB\n\nBroken: Blender 2.80 beta Jan 18\nWorked: Blender 2.79\n\nWhen parenting an object to a bone, the object is wrongly offset from it's previous position. This was not the case in 2.79.\n\nThis scene is nothing special, just a normal bone and a normal cube. No special settings or anything out of the ordinary. In any case, it serves as a very simple test case for this issue. \n\nOpen this Blend:\n[Object_parent_bone_bug.blend](Object_parent_bone_bug.blend)\n\n - Select the cube, then the bone\n - enter pose mode and make sure the bone is selected\n # Press Ctrl-P and select 'Bone'\n\nYou'll see the cube fly away to a different position. It should stay put and just become a child without moving. This worked correctly in 2.79.\n\n**2.8 beta:**\n\nBefore Parenting:\n\n\nAfter Parenting:\n\n\nThis offset should not happen.\n\n**2.79:**\n\nBefore Parenting:\n\n\nAfter Parenting:\n\n\nHere the object stays correctly put.", "\"set parent to vertex or bone\" causes displacement in the child.\nOperating system: Windows.\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2.\n\nversion: 2.80 (sub 44), branch: master, commit date: 2019-02-14 07:01, hash: c6cbcf83d015, type: Release build date: 13/02/2019, 23:22\n\nWhen an object is parented directly to a vertex or a bone, it jumps.\n\nCreate a cube.\nCreate Empty.\nSelect the Empty.\nAdd cube selection.\nEnter edit mode.\nSelect a vertex.\nParent with Ctrl + p (set parent to vertex).\nReturn to object mode.\n\nThe same happends if the Empty is parented to a bone in pose mode." ]

[ "Blender 2.8. In edit mode when you have hard scene (slow down processing) all your actions will applyes not at right moment (not at click but at moment when blender finn. caclucations)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 53)\nWorked: (optional)\n\n\nI have scene where I put a lot boolean(and not only) modificators on one objects and when I enter into edit mode all processing erally slow (each action: movement, extrusion, etc..) And problem here in next: when you doing any action (and it took time to process it) and then press mouse button to apply action affect, but! it will not memorize position of the mouse when you pressed, and still continue doing (move to the cursor) And this really anoing because you need repeat all twice or more time. Or just seating and waiting with no mouse movement at all, when it will apply action effect. \nSo core problem is that: in edit mode any affect will applyes not at moment when you decide but by moment when CPU will finished calculetion of movement/action and will change your action to position where is going be mouse positioned at the moment of the end calculation... something like that. \n\nCreate some worcload/heavy scene. For example by a lot subdivisions and booleans at object. When each your action will be like \"under water gravity\" slowed down. And then try to change(extrude/move vertext / anything) boolean part that will be used as cut area in the edit mode. \n\n[2019-04-01 17-39-35.mov](2019-04-01_17-39-35.mov)", "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.", "Nodes: Different mouse drag effect for float properties\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.5.0 Alpha\n\nDrag step inconsistent of float data type that between of geometry nodes in modifier and editor.\nAnd float of vector also.\nThis caused the mouse to drag far to reach the maximum value when going from 0-100.\n\n\n[drag_step.blend](drag_step.blend)\n\n", "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.", "Node link drag search in shader editor doesn't filter by render engine compatibility\nOperating system: macOS-11.6.2-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-16.5.7\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't think ever. The feature was introduced in 3.1: 11be151d58\n\nOther than the default node search menu ( {nav Add > Search...} ) the link drag search doesn't filter out nodes that are not compatible with the current render engine.\n\n[node-link-drag-search-bug.mp4](node-link-drag-search-bug.mp4)\n\nAs shown in the video:\n- open the default blend scene with factory settings\n- switch to the shader editor\n- add a *Value* or *RGB* node\n- drag from the node's output and release the link on the canvas to activate the link drag search\n- look for the \"Toon BSDF\"\nResult: inputs from the node appear in the search despite the node not being supported by Eevee.\n\nHere's the simple setup from the video.\n[node-drag-link-search-bug.blend](node-drag-link-search-bug.blend)\n\n", "Multi-Button Drag: not working properly for Object Dimensions\nWindows 7\n\nBroken: 2014-02-11\n\nMulti-Button Drag - D270 - doesn't work properly in N panel for Dimensions\n\nIf you drag over all 3, only X and Z change, Y remains unchanged. As mouse button is released, the first selected property will reset, only the last hovered is kept (and scale changed)", "Continuous Grab occasionally fails\nOperating system: Linux 5.9.10-arch1-1 (KDE Plasma desktop)\nGraphics card: NVIDIA GTX 980Ti (455.45.01)\n\nBroken: 2.80 - 2.92 master\nWorked: N/A\n\n\nMouse wrapping sometimes fails to transition screen edges, requiring at least a pixel of backpedaling with the mouse. This seems to affect all mouse-wrapping operators. Initially this report was written in terms of Shear, with which I've discovered this behavior.\n\nMesh edit mode Shear operator sometimes gets stuck on the toolbar side of window, showing the system mouse pointer (perhaps due to mouse passing over the toolbar?), needing at least one pixel of motion to the right to untangle it.\n\n[Video ](PeSL2fzKfT4).\n\nThis does not seem to occur if:\n- viewport is not touching window edge\n- window is made fullscreen\n\n\n- Make sure your window is not made fullscreen and that the 3D viewport is bordering window edges\n- Enter edit mode, select all and invoke Shear operator. Move the mouse continuously to the left, until it eventually gets stuck.", "Dragging a folder in file view has an incorrect offset, when pressing the \"B\" key\nOperating system: Darwin-15.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-10.14.73\n\n\nBroken: version: 2.80 (sub 54) (self-built)\nWorked: (optional)\n\n\nDragging a folder in the file browser view and then pressing the \"B\" key leads to an unexpected offset of the dragged item.\n\n(This works in all display modes for the file list. Video has been done with the \"Thumbnails\" mode)\n1. Open the file browser.\n2. Drag a folder.\n3. While still dragging, press the \"B\" key.\n4. Notice, that the dragged folder is now offset.\n\n\n[filebrowser_drag_offset_bug.mp4](filebrowser_drag_offset_bug.mp4)", "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", "Data-block Selector Design Changes (latest iteration)\nNOTE: This task does **not** cover the search menu of the data-block selector. There were ideas for this in the past, but they are not covered here.\n\n## Motivation\n\nThis initially was motivated by the addition of library overrides. Data-block selectors need a way to show library override operations.\n\nThere are a few other issues the following proposal addresses:\n* **Scalability**: The current solution of adding little icon buttons next to the data-block name field doesn't scale well. It only works if there's a small number of operations. We need to be able to place more items for better data-block management. Especially with the introduction of library overrides.\n* **Discoverability**: It's not obvious what some of the icons do. They appear and disappear, but it's not clear why some are available at times and others not.\n* **Unclear Status**: Currently their library status (linked, indirectly linked, broken link, library override) isn't really clear.\n* **Unusual behavior**: Some of the icon buttons allow Shift or Ctrl clicking to invoke alternative behaviors. This is not a usual pattern in Blender.\n* **Misleading/incorrect terms and icons**: The current design mixes \"Duplicate\" and \"New\", as well as \"Delete\" and \"Unlink\". So it's unclear what a click on the duplicate-icon does for example.\n\nThere is a conflict here: Many of the data-block selectors have little space, but users want to see many things at once: Fake user status, user count, name with sufficient space for long ones, often used operations (duplicate, unlink), etc. And there needs to be access to a data-block search box and advanced operations.\n\n## Proposal\n\n[TODO properly explain this]   \n\n**Operations Menu**\n\n**Necessary Changes**\n\n**Remaining Issues**\n\n* Space is still an issue. The proposed design may be an improvement in some regards, but only slightly reduces needed space.\n* For now, this design won't display the library status icon (linked, indirectly linked, broken link, overridden, is-asset). There is just too little space for this. What other ways could we communicate this?\n\n## Higher Level Issues\n\nThere are at least two higher level issues, which are not addressed in this proposal, but can be addressed in a more or less orthogonal way:\n* Fake user is an ancient concept that should probably go (see #61209). Once that is done we don't need to show the fake user status icon. Maybe we can show the library status icon instead then.\n* Data-block selector is \"abused\" for general data-block management, because there is no proper place for that. E.g. the data-block could visualize the data-block relations (e.g. see <2.5 OOPS schematic) and provide better tools for managing them. A data-block selector should really just be used for managing a simple data-block user.", "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", "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", "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}", "Custom Node Trees: Selected node tree is lost when editor is switched to other node editors\n1. Run the official Custom Nodes Python template\n2. Switch to the newly registered Custom Node Tree editor\n3. Create a node tree\n4. Switch to another node editor (Shader Editor for example)\n5. Switch back to the custom node tree editor\n6. The selected node tree was switched back to None", "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" ]

[ "Regression: Node editor: Tweak is broken and requires click, then click again to drag\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.2.0 Alpha\nWorked: 3.1\n\nCaused by 4d0f846b93\n\nAs title said. Node drag requires click (selection) before dragging. Here is comparison:\n\n**Steps to Reproduce**\n- Open default scene and switch to Any node editor\n- Deselect nodes\n- Switch to tweak option from toolbar\n- Hover over the node which is not selected\n- Hold left click and try to drag the node\n[2022-03-16_15-35-12.mp4](2022-03-16_15-35-12.mp4)\n" ]

[ "White Noise Glitch using Value Attribute of Particle Instances\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\nWorked: (?)\n\nThe White Noise Texture (in 1D) does not display as expected using the Value Attribute of Particle Instances in both EEVEE and Cycles. Instead of showing a single random value or color on the surface of an instance there's a fuzzy mess of different values similar to the look of overlapping faces:\n\nThe issue also appears on non flat geometry not only on planes. The using the Index attribute shows the same result. It's the same on the current stable release (that being 2.91.2) and previous releases. I tried the same setup with a Noise Texture and it seems to work just fine:\n\n- Choose any object as the emitter of a particle hair system.\n- Adjust the settings of the particle system to display the desired quantity of hairs\n- Add another object and add a Particle Instance Modifier to it\n - under 'Object' set the emitter object\n - check 'Create Along Paths'\n - in the object data properties under vertex color create a new vertex color\n - choose the same vertex color as the 'Value' data of the particle instance modifier under 'Layers'\n- use the created data as the name in the Attribute Node\n- connect any output of the Attribute Node to a White Noise Node set to '1D'\n- display the results\n(same last 5 steps for Index Attribute)\n[ParticleInstanc_ValueAttributeBug.blend](ParticleInstanc_ValueAttributeBug.blend)\n\nThank you so much for looking into it! And keep up the great work.", "Hair particles: Entering sculpt mode [dyntopo] changes hair particle distribution without warning\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: Don't know\n\nEntering Sculpt Mode can mess up particle settings without warning. See the attached gif. \n\n\nIn the attached blend file, notice hair in the \"x\" pattern on the cube. Switch to Sculpt Mode, then back to the Particle Edit mode. Notice the hair pattern has changed. \n\n[sculpt_hair_test.blend](sculpt_hair_test.blend)\n\nTo reproduce the issue from scratch, follow these steps: \n- Modify a mesh using sculpting tools with Dyntopo enabled. \n- Make sure the mesh has no vertex data that would cause Dyntopo to turn off when you switch away from and back to sculpting mode.\n- Make sure Dyntopo is on and switch away from sculpting mode.\n- Add a hair particle system to the mesh. Use the particle editor to add a recognizable shape to the hair.\n- Switch to sculpting mode.\n- Switch back to the particle editor and see the shape of the hair.", "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", "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.", "Particle system behaves inconsistently in viewport and render when instance object visibility is disabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro [P2200](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.91.0 Beta\nWorked: The behavior was different in 2.80\n\nWhen the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.\n\n1. Open the default scene.\n2. Create another object (B).\n3. Create a particle system modifier on the default cube (A).\n4. Set Particle Settings to Hair (A).\n5. Set Render -> Render As to \"Object\" (A)\n6. Set the Instance Object to the other object (B).\n7. Disable the object (B) in viewport and render\n8. Render the scene, observe that the object has particles rendered\n[particle_visibility_bug.blend](particle_visibility_bug.blend)\n", "Motion Pasths: \"Clear Motion Paths\" default to \"only selected\"\nProblem: \nAs with \"calculating\" motion paths you expect the clear motion paths function to default to the one selected, In the same way you create Keyframe the selected objects. The default deletes all motion paths in scene and wanting to clear one motion path is more common than wanting to clear them all.\n\nSolution:\nChanging the default of clear motion paths to \"clear motion path\" and turn \"Only Selected\" to default.", "User Interface: Float Curve: bug when control points has same X position\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nUser Interface: Float Curve: bug when control points has same X position\n\nIf the points are located on the same X axis, then the result breaks.\n\n| [Set Curve Parameter Bug.mp4](Set_Curve_Parameter_Bug.mp4) | [2022-10-19 15-45-49.mp4](2022-10-19_15-45-49.mp4) |\n| -- | -- |\n\n[simple example float curve.blend](simple_example_float_curve.blend)", "Hair particle distribution changes randomly\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.41\n\nBroken: version: 3.5.0\n\nHair particle distribution changes without the user changing parameters.\n\nOpen the attached Blender file.\n\nIn the particle settings of the active object, click on the Emission -> Number field to edit it, and then without actually changing it, press enter.\n\nNotice that even though no parameter was changed, the distribution pattern on the emitter changes. \n\nThis keeps happening for 5 repeats of the previous step, until it seems to reach an equilibrium. \nBut you can start it again, by clicking onto the Emission -> Seed field, and hitting enter without changing it. This will allow you to click on the Number field again and cause changes.\n\nFor this to function, we seem to need both Interpolated Children to be active, and a texture to drive the distribution.\n\nAs a side note here, I'm not sure if this should be a separate bug report, but the texture is set to influence Density, but also influences the size of the scattered objects. Whereas if you try to have it influence the Size field, nothing changes.\n\n", "Cycles GPU/CPU render difference with more than 64 transparent bounces and coplanar faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\n\n\nWhen using particle plane with transparency ( to fake volume scatter ), we have a color mismatch between CPU and GPU rendering. \n\n\n see attach file\n\n\n\n[cpu_gpu_issue.blend](cpu_gpu_issue.blend)\n \n", "\"Reset to Default Value\" sets alpha incorrectly in [Material Properties > Viewport Display > Color]\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.5.0\n\nRight-clicking \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] sets both the color's \"value\" and \"alpha\" bars to 0.8, when the alpha one specifically should reset to 1. Alpha resets incorrectly.\n\nRight-click \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] on any material.\n\n", "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)", "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.", "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", "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", "Parented Rigid Body offsets on transform if the parent has been moved\nWin8.1, 3x gtx580\n\n2.79\n\nIf a rigid body is parented to something (like an empty for group animation before beginning of the simulation etc.), if the parent was moved or animated, when attempting to transform the rigid body, it begins transformation with the offset of the parent (makes it impossible to fine tune simulation starting locations).\nThis happens when animation frame is within simulation range +1.\n\n[wt2.blend](wt2.blend)\n - Press G (grab transform) or use transform widget on the selected plane.\nIf the rigid body gets re-parented, the offset disappears until the parent is moved.\n" ]

[ "Particle refresh issue when emit start and end time are the same\nWindows XP/32bits Sp3\n\nBroken: 2.73a , 2.71\nWorked: unknown\n\nDistribution setting of Particles is ignored\n\nI set distribution of Particles of Particle Setting in Grid, and distribution setting is ignored when I change a rendering method of Particle.\nBut it occurs only at the time of the first change.\n\n" ]

[ "Render glitches on cycles when 'Motion Blur' and 'Use Limit Surface' are turned on. \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\nAlso broken in: 2.93.0 Alpha, branch: master, commit date: 2021-03-20 21:00, hash: 9ca67c47a152, type: Release\nbuild date: 2021-03-20, 23:00:48\nWorked: unknown. This file was created within 2.92\n\nWhen rendering this file I get (for me) random glitches in the render, when Motion Blur is active in Cycles.\nIn the attached file you can see this in for example frames 13,46,77 and 153 (amongst others) for the figure on the left and in frames 57,65 and 82 for the figure on the right.\nTurning off motion blur makes the glitches go away. It happens - for me - both with CPU only and with GPU renders.\n\nThe only objects - as far as I can tell - that produce these glitches are the two 'jasjes' with the material called 'overhemd'. (changing 'overhemd' to a different color also changes the glitches to that same color) Apart from the very obvious triangular glitches, you can also see some sort of wrinkly render errors near the ties on the shirt that only appear when the glitch is visible.\n\nFrame (13) with a glitch: \nFrame (14) without a glitch: \n\nThe objects started out as duplicates of each other.\n\n- Open attached file\n- Render frame 153 (or any of these: 13, 46, 77)\n\nI'm sorry the file is as large as it is, but I haven't had this happen in other renders/files yet, so I couldn't reproduce with another file.\nPlease let me know if you prefer to get Dropbox links instead of an actual upload.\n\n[Statler_en_Waldorf_animatie_013.blend](Statler_en_Waldorf_animatie_013.blend)", "\"Setup Tracking scene\" not alligned when using vertical Videos \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\nWorked: not sure\nNoticed that all vertical videos(horizontal video with frames extracted with -90 offset) I tracked using the smartphone and dslr source were not alligned with the tracking marker empties when \"Setup Tracking scene\" was done\n\n\nwhen used horizontally it works perfect but difficult to interact with blender sideways\n\nrendered video rotated on export: 1447977113303220226?s=20\n\n- Use any vertical video\n- track and solve\n- do \" setup tracking scene\"\n- the tracking empties should be misaligned with the video in the 3d scene\n", "Eevee renders full frame and cut it instead region rendering\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\nI tested with same settings and I have the same time for whole frame and region.\n\n\n\nIt makes problem, when I want to render small part zoomed. Now the workaround — is making new camera with smaller angle and render from it.\nIf it is limitation, may be render should create temporary camera that cuts region.\n\nRender same scene with Eevee through {key F12} and it`s region and compare render time.", "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!", "Freestyle > \"Render Animation\" uses only the widest keyframed focal length for all the frames\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 16)\nBroken in the most current 2.83, date: 2020-02-17 00:09:39, hash: `819af2094b21\nWorked: 2.8\n\n\nWhen the focal length of the camera is keyframed to different values over several frames, Freestyle takes only the widest focal length and uses it for all keyframes\n\n[Freestyle_Test.blend](Freestyle_Test.blend)\n1. Open the attached blend file\n2. Set the Output location for the rendered images\n3. Select \"Render Animation\" and check the finished frames\n\nThanks so much for your help! Highly appreciated\n\n", "Adjust last operation fails to align new objects\nOperating system: Linux-5.11.0-31-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 620 (KBL GT2) Intel 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: version: 3.0.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Unknown\n\nWhen trying to add new objects, changing the alignment via Adust Last Operation does not work.\n\n- Enter Camera View\n- Add Object\n- Deselect Object\n- Open Adjust Last Operation (Edit --> Adjust Last Operation)\n# Change `Align` to `View`\n\n", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "Eevee slower than cycles when using a lot of particles or collection instances\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 17)\n\nWhen using a lot of collection instances with particles in them, or with a lot of objects, Eevee seems to be very slow in evaluating the scene. \neevee: 2min and 2sek \ncycles (gpu): 9sek\n\nopen the file switch to cycles - hit render\nswitch to eevee hit render\n", "Motion Blur glitches, the further an object is placed from the world origin (even with no motion)\nMac Os 10.14.5\nRadeon Rx580 \n\nBlender 2.8 & 2.81 Beta (5/11/19 build)\n\nObjects are seriously corrupted when the motion blur checkbox is ticked, even when there is no camera or object motion.\n\nI have attached a simple project with only a Cube, Camera & light... & placed it 500,000m from the world origin on the Y-axis.\n\nThe image is distorted in rendered camera view...moving the cube backwards towards the world origin fixes the issue at around 50,000m\n\nMoving the object further away (try adding a zero to push the cube 1,000,000 from the world origin) distort the object more.\n\nSwitching off motion blur on the (static!) camera restores the image quality.\n\nI'm doing a space animation with some large distances involved, & this bug has just bitten me. I'd appreciated if others could confirm.\n[Motion Blur Draw Distance Test.blend](Motion_Blur_Draw_Distance_Test.blend)\n\n\n\n", "Surface Deform modifier always updates when selecting objects\nOperating system: Windows 10\nGraphics card: NVidia GTX1080\n\n2.93.1, 2.93.3\n\nSurface Deform modifier causes click lag even if object or/and the modifier is disabled in viewport. It doesn't affect camera panning or rotation.\nWhile I'm at it, it also seems to keep unnecessary data in saved file. I wanted to provide an example file, but it turned out to be over 1 GB. I don't see why it keeps the deformed mesh in the file rather than recalculating it when we enable it or open the file.\nIt seemed to me to be the best way of making a chainmail, but I can't work with the lag.\n\n1. Subdivide the default cube with 7-10 cuts (7 enough for my PC, if in the end it doesn't lag, try more divisions).\n2. Duplicate the cube.\n3. Add subdivision modifier (level=6) to 2nd Cube, then add Surface Deform, set the source to 1st Cube, bind.\n4. Disable both objects in viewport, you can even disable the modifiers.\n5. Add a new Cube to the scene. Try selecting and deselecting in in the viewport. There's a lag. Camera panning and rotation works fine. The only way to fix the lag is to apply or remove the Surface Deform modifier.\n6. Save the file. Our file is just 396 faces with modifiers applied. It's over 1GB in size.\n\nVideo: hEQnVVvPEGU\n\nor\n- Open .blend file\n- Bind mesh to the target\n- Try to select the Cube.001 in viewport\n[#90985.blend](T90985.blend)\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "Shader Image Mapping Issue\nOperating system: Mac OSX High Sierra\nGraphics card: NVIDiA GeForce\n\nBroken: (example: 2.92 Master 02948a2cab44\nWorked: N/A\n\nIt seems the mapped image is not applying to an object that's linked by Object Data\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[repro2.blend](repro2.blend)\n\nIn this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):\n\n\n\n\n\n\n---\nOriginal report:\n[modular.blend](modular.blend)\n\nLook at the image reference in the shader for the second to last vehicle. All other vehicles with similar bodies are linked and are following the map except the second to last object. After linking the body of that vehicle, the object appears to follow the map until you render the image. ", "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\n\n", "Lineart in viewport inconsistent with bound cameras\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\nWhen I'm using lineart with bound cameras on the timeline and View Lock, Camera to view is True, sometimes the lineart updates dynamically, sometimes I have to click the Clear Baked Line Art button to force an update in the viewport.\n\n1. Open the attached file.\n2. Clear the baked line art. Do *not* try to bake.\n3. Keep \"Camera to View\" set on. (Note that in frame 1, lineart is updated as you navigate through the view)\n4. Step through each of the 3 frames, and rotate the view with middle-mouse-drag.\n\nOnly one of the frame/camera will properly update the lineart. As the viewport moves to the rear of the cube in the other two, the lines are missing. I haven't found an obvious reason why one frame is working, or why that frame. The working one has been 1 or 2 just while I wrote this report.\n\nClicking Clear Baked Line Art again will update the cureent viewport so it is correct, but rotating the view will again show one camera binding working, the other two not. It does not seem to matter which frame is active when the Clear Baked Line Art is clicked.\n\n", "Metal Viewport flickering on interaction\nOperating system: Mac OS Monterey, Version 12.6.2\nGraphics card: Apple M1 Max, Mac Book Pro 16 inch 64 GB, LG Ultra Fine Display as secondary monitor\n\nBroken: 3.5.1 release candidate\nWorked: 3.4 with Open GL does not have these issues\n\n\nWhen interacting in the viewport say moving a camera the viewport flickers. Also when adjusting shaders in a cycles window the viewport also flickers depending on the speed of the interaction. Evee viewport does not have this issue, but solid render does\n\nBased on supplied file Look through camera and split the viewport in two. Left side has cycles rendering turned on. Change the default renderer from Eevee to Cycles and change to GPU compute. Rotate camera with the empty and cycles view on left flickers. Next select cube and change the shader colour from pink to any other colour you like. Again viewport flickers like crazy.\n\n" ]

[ "Video Editor Scene Strips and scene camera binds are out of sync (most of the time)\nBroken: blender-2.80.0-git.03bd024c077d-windows64\n\nThis is a re-do of another other bug report I filed earlier this month (#63304), now that I understand it a lot better I'm filing it again with a more accurate description and demo file.\n\nIn the video editor, if you one or many scene strips, on updating the frame the camera bind that the playhead falls under will most likely not be applied until the following frame.\nSo, when you place the playhead in a region that uses a different camera bind, it usually does not update unless you update once more in that same region.\nThis is also the case in rendering animations using the video editor.\n\nI've created a demo file that perfectly illustrates this problem below.\nThis bug urgently needs fixing.\n\n**Exact steps for others to reproduce the error**[sequence camera bind bug.blend](sequence_camera_bind_bug.blend)\nInstructions for demo:\n\nIf the playhead is in the BOX region, it should show a box, if it is in the SPHERE region, it should show a sphere. I estimate about 80-90% of the time it doesn't update correctly. Why there is an element of chance I cannot work out.\n\nTry moving the playhead around between markers (which indicate a camera bind in the strip's scene) and notice how the bind almost always fails to apply.\n\nNow try jumping from region to region and notice how the camera bind is almost always 1 step behind, so it is never applied, place the playhead within the current region and it updates without fail." ]

[ "Regression: Tiled rendering is not applied to texture baking in 3.x onwards, causing crash on large bakes\nOperating system: Win10\nGraphics card: AMD Radeon R9 280x\nSystem RAM: 32gb\n\nBroken: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: bcfdb14560e7, type: release\n(also tested Daily 3.2.2 and beta 3.3)\n\nWorked: 2.8x, 2.9x, 2.9 LTS\n\nPreviously tile based rendering was applied when using the bake to texture feature, allowing baking to very large canvases. As of version 3.x tiled rendering no longer applies when baking textures and crashes on large canvases. In my case I can no longer bake to a texture larger than 2^14 (16384x16384).\n\n- Open attached file or\n - From a new blend file, delete default cube,\n - switch renderer to Cycles (CPU).\n - Create a plane,\n - switch to UV and create a very large texture (in my case anything larger than 16384x16384, my previously and still working in 2.9x size is 19310x) with float precision and no alpha.\n - Create a new material,\n - remove the principled Shader,\n - connect the color output of a noise texture to the material output Surface,\n - add an Image Texture node and select the previously created canvas. In my case I disable bounces (set all to zero) and set samples to 1, Filtering to Box filtering. \n - Switch bake type to Emit.\n- Hit bake and blender crashes trying to allocate the memory for the render target canvas. Setting Tiled rendering to other sizes does not work either.\n\nNotes:\nI'm prebaking complex noise channels as it dramatically reduces render time on the final texture bake.\nYou may need to create an excessively large target canvas if you have a lot of ram.\nWhen stopping a bake half way through on 2.9x and lower version you can see tile based rendering has taken effect and the sizes declared are used.\nWhen stopping a texture bake on 3.x versions you can see that it is filling the entire canvas at once and not using tile based rendering, no matter what the tile size is set to.\n[bake_crash.blend](bake_crash.blend)\n", "Multiple Smoke Flow Colors Rendering Black when Flow Behavior is set to Geometry\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.83.1\nWorked: 2.81 -- N/A, newer versions use fluid settings, but the old smoke sim worked as it should\n\nBaking a smoke domain multiple smoke flow objects with flow set to \"geometry\" and each set to a color results in all of the smoke rendering black.\n\nCreate a smoke domain on any object and place two smoke flow objects inside the domain. Set the smoke color of the smoke flow objects to any color, and the flow behavior to \"geometry\" vs \"inflow\" or \"outflow\". Change the material on the domain object to a material without a surface bsdf but with a volume bsdf whose color is set to the color output of an attribute node with the Name property set to \"color\". Bake the sim and render, and you should observe that all smoke is black, as opposed to the colors set on the flow objects. This works correctly when the flow behavior is set to inflow (except on the first frame), so I'm guessing this has something to do with the initialization of the smoke.\n\n[smoke_multi_color_bug.blend](smoke_multi_color_bug.blend)", "Quick smoke vorticity is broken.\nOperating system: Windows 10.\nGraphics card: NVIDIA GeForce RTX 2080 Super\n\nBroken: (version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29c0, type: Release \nThe same is on experimental 2.91\n[system-info.txt](system-info.txt)\n\nI'm not sure, but in video tutorial of Blender 2.7 is working correctly. Link to vid: watch?v=BhjK-6t9Gqs&t=2m10s\n\nWhen you add vorticity to smoke sim it does something crazy,video with 0 vorticity:\n[smoke_novorticity.wmv](smoke_novorticity.wmv)\n\n\nWith vorticity value of 3 here is what happens:\n[smoke_vorticity.wmv](smoke_vorticity.wmv)\nIt happens a bit differently on different strength but once you add any vorticity it goes wrongly.\n\nThe file is simple - adding icosphere, make couple keyframes to animate it. Add quick smoke, adjust domain. For emitter make temp.diff -1, enable initial velocity. For smoke domain set vorticity to 3.\n[smoke_voticity.blend](smoke_voticity.blend)", "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", "MantaFlow Smoke simulation \"breaks\" after 110 frames\nOperating system: Windows 10 \nGraphics card: NVidia RTX 2080 Ti\n\nBroken: (example: 2.83 Beta, d8133b3eb99a, 2020-05-04)\nWorked: Not that I know of\n\nWhen baking the Smoke Simulation of the attached File, the smoke 'explodes' at frame 110. It looks as if an 'Explosion Force Field' was placed in the middle of the domain that applies its forces at frame 110.\n\nTo Reproduce: Download attached file, Bake the simutaltion and look at frame 110+.\n\nBlendFile: [Blender_ [D__03_personal_MartinFroehlich_florianDubois_Laminar_7.blend] 2020-05-06 17-17-04.mp4](Blender___D__03_personal_MartinFroehlich_florianDubois_Laminar_7.blend__2020-05-06_17-17-04.mp4)\nVideo: [Laminar_7.zip](Laminar_7.zip)", "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", "bpy.ops.object.transform_apply no working after physics simulation\nOperating system: Windows 10 Pro\nGraphics card: 2x Nvidia 1080 GTX\n\nBroken: 2.8, b46245470f79, 2018-04-18\nWorked: 2.7x\n\nWhen running a rigid body simulation, it is not currently possible to apply transformation to freeze a specific frame. If you start scrubbing in the timeline, the object either goes back to original position or jumps to random position that was generated during the simulation.\n\n - add a plane and add a passive rigid body\n - add a suzanne and add an active rigid body\n - run the simulation\n - choose a frame\n - select the suzanne object\n - apply transformation/apply visual transformation\n # scrub in the timeline\n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Particle simulations dont generate valid disk caches\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 2.93.1\n\nand I tried on the blender-2.83 LTS and it has the same issue.\n\nBlender stops simulating particle systems. if I'm baking them it just puts noting in the bake if I'm rendering without baking first if doesn't do anything except make my fans run full blast.\n\ncreate a bunch of particle sims. Use I used the script in the blend to do it.\nrun bake all dynamics. Only the first few of them actually generate anything.\n\nOf don't bake and just try to render. It freeze.\n\n[bugReportFireworks.blend](bugReportFireworks.blend)", "Blender crashing while baking Smoke Domain\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 511.65\n\nBroken: version: 3.0.0 & 3.2.0 Alpha\nWorked: NA\n\n\nBlender Crashes while baking smoke domain\n\n- open Project \n- Select smooth domain from outliner\n- {nav Physic properties > Bake All} (crash between frame 60 & 70)\n\n\n\n\n", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "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)", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "Baking API: remove non-working baking to external image, also cleanup misleading error messages\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\n\nWhen baking for example an AO map, on a mesh, with no materials. You'll get an error stating you can bake to an external file [which was never implemented fully]\nSo that means the API would need to be cleaned up [non-working external save_mode removed, warning-/error messages adjusted]\n\nLoad new file,\ngo to bake tab\nselect ambient occlusion\nHit bake.\nNotice error, It suggests to save to an external file. But there is no option to select an external file.\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)", "Smoke simulation silently fails in Sync to Audio or Frame Dropping playback\nSmoke simulation silently fails in Sync to Audio or Frame Dropping playback\n\n---\n\n**Original Report:**\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 3.1.2\nWorked: Never (tried 2.93, 2.83)\n\nThe smoke simulation does not simulate beyond the first frame in this particular file. Any smoke simulation added or appended from other files stops working as well.\n\nHowever, everything works fine in new files on the same system & hardware.\n\n[smoke simulation issue.blend](smoke_simulation_issue.blend). \n\nOpen the blend file, move the smoke domain to clear the old cache.\nHit play and the smoke is not moving. Other physics (rigid body, particles) are working fine.\n\nDelete everything, add a cube, add the quick smoke effect, and the same happens.\n\n" ]

[ "Smoke simulation dont show up after baking Noise\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.91\n\nAfter baking \"Noise\" in Smoke simulation, smoke doesn't appear.\n\n- Setup \"Quick Smoke\" to some Mesh\n- Bake smoke sim\n- Enable and bake Noise\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", "Autosaves not written anymore, writting crash files instead\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\nOn crashes, I realize autosave files are not being wriiten to disk, instead there is crash.txt files\n\nNo idea what might have started causing it, potentially an addon, but the crashes are just usual random stuff, not connected to anything new. I have autosaves ste to 1 minute and using them a lot/everyday, so it's quite traumatic to suddenly start losing work again like if it was Maya 2009.\nHere is examples of crash files.\nThanks a lot for any help/clues about what is going on.\n\n", "Clicking on empty space in editors creates undo step\nBroken: version: 3.0.0\nBroken: version: 2.80\nWorked: 2.79b\n\nWhen clicking in certain Editors (doesn't matter if it's not selecting/doing anything) undo step is created. It does make sense to do in certain cases when selecting objects (for example, when selecting objects via outliner undo to previous selection is logical) but definitely not when there are nothing to select.\nAffected Editors/modes:\n- [x] Outliner (3775615aea)\n- [x] Video Sequencer Editor: `Sequencer` and `Sequencer & Preview` modes (clicking on image) (5d30c3994e)\n- [ ] Dope Sheet: `Dope Sheet`, `Grease Pencil`, `Mask`, `Cache File`\n- [ ] Timeline\n- [ ] Graph Editor\n- [ ] Drivers: only when clicking on left area, \n- [ ] Nonlinear Animation\n\nWhere to click:\n\n\n- Open default scene\n- open any editor listed above\n- Click on area of an editor several times (See above image).\n- Notice undo step is created for selection (in reality, we've selected nothing)", "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", "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", "Cloth simulation presets only save some of the settings\nOperating system: Windows\nGraphics card: RTX 2080\n\n**Blender Version** \nBroken: 3.4.1\nWorked: never?\n\nCloth simulation presets only store the first few sections of settings not internal springs, pressure, shape, collisions, or field weights\n\n- Create a cloth simulation with specific variables.\n- Save as preset.\n# make new object and apply preset\nonly the above mentions sections are applied from the preset, others are untouched.", "'Reset to Default Value' sets any property on a node to 0\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nIn shader editor gamma default is 1 when I do the hover over setting and press backspace to reset the default it goes to 0.0\nSame with hue/saturation/value.. and probably more.\nThe one with hue is pretty annoying as it has specific default settings .\nSame deal with groups - I set the defaults, it doesn't default .. goes to 0\n\n- in any node editor hover over any setting and press backspace to reset to default value.\nIt defaults to 0 instead of 1 or whatever it's default was in shader editor..\n\n", "Calling operator from handler that saves bmesh freezes blender forever\nBlender version: 3.5.1\n\nI setup some shader to run on top of blender viewport and connected it’s update to `SpaceView3D.draw_handler_add`. The idea was that shader will only work in EDIT mode and if user exists it then it will automatically trigger some operator.\nLine that freezes Blender is `bm.to_mesh(context.object.data)` although it doens’t freeze right away.\n\nWhat I’ve found that if I call operator that edits mesh from bmesh then it freezes Blender entirely.\nCurrently as a workaround I moved operator’s code to some function and call it instead of because `bm.to_mesh(context.object.data)` doesn’t seem to freeze Blender when it’s called from handler without operator.\n\n\nEasy way to reproduce (create default scene, make sure cube is selected, run the script):\n\n```python\nimport bpy\nfrom bpy.types import SpaceView3D\nimport bmesh\n\nclass TestHandler:\n installed = None\n\n @classmethod\n def install(cls, context):\n handler = cls()\n cls.installed = SpaceView3D.draw_handler_add(\n handler, (context, ), \"WINDOW\", \"POST_VIEW\"\n )\n\n @classmethod\n def uninstall(cls):\n try:\n SpaceView3D.draw_handler_remove(cls.installed, \"WINDOW\")\n except ValueError:\n pass\n cls.installed = None\n\n def __call__(self, context):\n obj = context.object\n if obj.mode != \"EDIT\":\n TestHandler.uninstall()\n bpy.ops.test.test()\n print('HANDLER CALL FINISHED') # never printed\n return\n \n print('HANDLER FINISHED')\n\nclass TestOperator(bpy.types.Operator):\n bl_idname = \"test.test\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST OPERATOR CALLED')\n bm = bmesh.new()\n\n # WITHOUT THIS LINE IT DOESN'T FREEZE\n bm.to_mesh(context.object.data)\n\n # still printed\n print('TEST OPERATOR FINISHED')\n return {\"FINISHED\"}\n \nclass TestSetupOperator(bpy.types.Operator):\n bl_idname = \"test.test_setup\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST SETUP OPERATOR CALLED')\n TestHandler.install(context)\n return {\"FINISHED\"}\n\n\nbpy.utils.register_class(TestOperator)\nbpy.utils.register_class(TestSetupOperator)\nbpy.ops.object.mode_set(mode=\"EDIT\")\nbpy.ops.test.test_setup()\n# freezes on the next step\nbpy.ops.object.mode_set(mode=\"OBJECT\")\n```\n\n", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", " 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)", "addon preferences changed by code (not by user in UI) are not saved\nOperating system: Ubuntu\nGraphics card: RTX\n\nBroken: master\nWorked: ?\n\naddon preferences changed by code (not by user in UI) are not saved at Blender close.\n\n- Open Blender. Load Factory Settings, close Blender. \n- Open Blender\n- In console, change an addon preferences. For example, change device of Cycles : bpy.context.preferences.addons['cycles'].preferences['compute_device_type'] = 1 (this change to CUDA)\n- Close Blender. No log saying preferences are saved.\n- Open Blender again, check that device is still None. pref save is KO\n- Change preferences to \"CUDA\" by clicking with your mouse\n- Close Blender\n- See that a log saying preferences are saved\n- Open again, you can see that preferences are set to CUDA, pref save was OK", "Linked Mesh Editing Doesn't Work As Expected When Using Data Transfer Modifier\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.81 (sub 16)\n\nObject instances doesn't work as in blender 2.81\n\n\nIn blender 2.81, after entering the edit mode, all instances become active. You can see changes in real time.\nScreen below:\n\n\nIn Blender 2.82 it work ok till some time. I couldn't determine at what moment it breaks...\n\n\nChanges appears only after You enter to object mode.\n\n\n\nHere is blend file to test\n[instances_issue.blend](instances_issue.blend)\n\n\n", "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", "Make saving of `quit.blend` on exit optional\n### Description & Scope of Problem\n\nEvery time Blender quits, when it has something on the undo stack, it will write the current \"undo file\" to `${TEMPDIR}/quit.blend` ([manual](open_save.html#last-session)).\n\nSaving `quit.blend` can take a while when the file is large. While the file is being written, Blender's UI is gray and unresponsive.\n\nThe problem is not pressing, as usually it takes considerably longer to load the files in the first place. I've asked some artists at the Blender Studio and they didn't really consider the delay when quitting Blender a practical issue. Still, it gets somewhat in the way of quickly testing things with various production blend files, so it could be seen as an issue for developers more than for artists.\n\n### Possible Solutions & Impact\n\n**Simplest solution:**\n\nAs a solution we could introduce a user preference \"Save Recovery File\" that is enabled by default. Disabling this option would:\n- Avoid writing `quit.blend`.\n- Remove the \"File ‣ Recover ‣ Last Session\" menu item.\n- Remove the \"Recover Last Session\" button from the splash screen.\n\n**Alternative solution:**\n\nThe \"Recover Last Session\" operator does not poll the filesystem from its poll function. This means that the operator is available even when the file `${TEMPDIR}/quit.blend` does not exist. Changing this, such that the operator is disabled when `quit.blend` does not exists, means that the above solution would not have to remove the recovery operators when \"Save Recovery File\" is disabled. The operators would auto-detect whether a recovery file is available at all.\n\nThe upside of this solution is that it makes the \"Recover Last Session\" operator appear more reliable, as it refuses to work when it knows it cannot do its job. This would be an improvement regardless of the \"Save Recovery File\" status.\n\nThe downside is that an old `quit.blend` might be lingering around after \"Save Recovery File\" has been disabled. This means that it could appear as if you could still recover, but it would load an older file. This could be avoided by removing `quit.blend` when disabling \"Save Recovery File\", but I'm not a big fan of Blender explicitly removing files that are meant to recover from human error.\n\n### Discussion Topics\n\nThis task is meant to discuss the following:\n\n- Do we want to make it possible to quit without writing `quit.blend` at all?\n- If so, which of the solutions is preferred? Or is there another way to deal with this that's even better?\n- Do we want this as a general option, or something that's enabled only when \"Developer Extras\" are enabled?\n", "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." ]

[ "Blender doesn't quit.\nOperating system: Win64\nGraphics card: N/A\n\nBroken: 2f77175fecc7\nWorked: (optional)\n\nBlender does not quit when there is unsaved data.\n\nWith the default cube scene.\n\n1) Delete the cube\n2) Quit blender, by either using the menu item or the X in the upper right corner of the window\n3) This file has not been saved yet! save? Sure. why not.\n4) Enter filename, save\n5) Blender returns to the 3d view\n6) click X again.\n7) ahhh now we quit...\n\nmentioned this informally to @Harley on chat but unsure if he's working on a fix or not. " ]