Datasets:

mano-wii

/

blender_duplicates

like 0

[ "Quad View Exiting Behavior\nUsers coming from other software expect Quad View to behave a certain way. Since d71db08f6d, when exiting Quad View we always toggle to the *User Perspective* (top right) view, rather than the one the mouse currently hovers. That differs from what users probably expect (see #43523, #42462, #42368, #43452, #69717).\nIt should not be hard to get the (presumably) expected behavior to work again while addressing the reasons it was removed.\n\nQuick proposal:\n* Maximize the hovered view when exiting Quad View\n* Keep rotation of that view locked if it wasn't the *User Perspective* one\n* Keep the view transform of the *User Perspective* stored so when going back to Quad View, it shows that in the top right.\n\nFor more details, see d71db08f6d.", "Blender 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\n", "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", "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", "Clearing followed by setting a listbox created by UILayout.prop_search while keeping the mouse on the listbox crashes Blender\nOS: Ubuntu 16.04 x86_64\nGfx: Intel HD Graphics 530 (Skylake GT2) (driver: GL 4.5 (Core Profile) Mesa 17.3.0-devel)\n\nBroken:\n- 2.79-42a562496b5-linux-glibc219-x86_64 (latest build)\n- 2.79-5bd8ac9abfa-linux-glibc219-x86_64\n- 2.76b\n\nClearing followed by setting a listbox created by UILayout.prop_search while keeping the mouse on the listbox either crashes Blender or leads to unexpected behaviour.\n\nConsistently reproducible.\n1. Open the default startup blender file\n2. Open a textblock and paste and run the code provided in Appendix A\n3. In the 3D viewport, press SPACE and type \"Crashable\", then select \"Crashable Operator\" => at the right an operator panel will be drawn\n4. In the operator panel, click on the field next to \"Obj:\" and select e.g., \"Camera\" from the list\n5. Click the X sign right to \"Camera\" while keeping the mouse pointer pointed at the field\n6. Click again on the field\n\n**Expected behaviour of step 6.**\nStep 6 should be able to behave as step 4, i.e., one should be able to again select something from a non-empty list\n\n**Observed behaviour after step 6**\nOne of following, probably depending on how Blender's memory was allocated:\n - Crash\n - The list is empty\n\n**Appendix A**\n\n```\nimport bpy\n\n\nclass CrashableOperator(bpy.types.Operator):\n bl_idname = \"object.crashable_operator\"\n bl_label = \"Crashable Operator\"\n bl_options = {'REGISTER', 'UNDO'}\n\n obj = bpy.props.StringProperty(name=\"Obj\")\n\n def draw(self, context):\n self.layout.prop_search(self, \"obj\", context.scene, \"objects\")\n\n def execute(self, context):\n return {'FINISHED'}\n\n\ndef register():\n bpy.utils.register_class(CrashableOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(CrashableOperator)\n\n\nif __name__ == \"__main__\":\n register()\n```\n\n**Terminal output upon crash**\n\n```\n$ blender\nRead new prefs: /home/elias/.config/blender/2.76/config/userpref.blend\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n**Contents of \"blender.crash.txt\"**\n\n\n```\n# Blender 2.76 (sub 0), Commit date: 1970-01-01 00:00, Hash unknown\nbpy.context.area.type = 'TEXT_EDITOR' # Property\nbpy.ops.text.run_script() # Operator\nbpy.ops.object.crashable_operator() # Operator\nbpy.ops.object.crashable_operator(obj=\"Camera\") # Operator\nbpy.ops.object.crashable_operator(obj=\"\") # Operator\nbpy.ops.object.crashable_operator(obj=\"\") # Operator\n\n# backtrace\nblender(BLI_system_backtrace+0x30) [0x1361b10]\nblender() [0x97a98e]\n/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f242a7894b0]\nblender(rna_ID_refine+0x4) [0x11bac84]\nblender(rna_pointer_inherit_refine+0x66) [0x11a9af6]\nblender() [0x1273ae2]\nblender(RNA_property_collection_begin+0x15c) [0x11b161c]\nblender() [0xb654ae]\nblender(ui_searchbox_update+0x6a) [0xb7514a]\nblender() [0xb57089]\nblender() [0xb59f6d]\nblender() [0xb5a027]\nblender() [0xb5d7ad]\nblender() [0xb5ebe6]\nblender() [0xb5f433]\nblender() [0x985e81]\nblender() [0x986251]\nblender(wm_event_do_handlers+0x5f6) [0x9868e6]\nblender(WM_main+0x18) [0x97cfd8]\nblender(main+0xef4) [0x95ce04]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f242a774830]\nblender(_start+0x29) [0x97a2b9]\n```", "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", "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", "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)", "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", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "Subpanels flicker when expanding panel that has moved\nOperating system: Windows-10-10.0.20161-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\nWorked: Persistent issue throughout 2.8x.\n\nCertain combinations of minimizing and maximizing the physics properties panels (described below) will cause the element to flash near the bottom of the screen for a frame.\n\n1. With any object selected, enable two (or more) physics properties for the object.\n2. Minimize the *final* panel, and then the first.\n3. Maximize the final panel.\n\n**Observations**\nThe differences previously mentioned are simply due to a lack of subpanels or panel length.\nA second jump appears to sometimes happen when maximizing the final panel after changing the panel type, though I cannot reproduce this reliably.\n\nIf the formatting of this video is as terrible as it seems, please let me know how to fix it. \n[ezgif.com-crop.mp4](ezgif.com-crop.mp4)\n\n", "Trembling when selected cube in edit mode\nOperating system: MacOS Sierra - Versione 10.12.6\nGraphics card: NVIDIA GeForce GTX 680MX 2048 MB\n\nBroken: 2.83.0 (2020-06-03), 2.90 (2020-06-12)\nWorked: 2.82a\n\nA strange flicker happens when I select the faces of the cube.\n\nI select the cube.\nI change the visualization in Edit Mode.\nI set select mode to Face.\nI select the faces of the cube but they do not remain selected instead, a strange flicker of the object occurs. Here a video example:\n\n[blender_283_bug.mp4](blender_283_bug.mp4)", "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", "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", "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" ]

[ "Blender 2.8 close with a default cube, and material is clicked\nOS: Win 10 Home\nGraphics card: Intel HD Graphics 630 NVIDA GeForce GTX 1050\n\n2.80 beta win 64bit feb 08 01:08:35 3d16a268ee68\n\nOpen Blender, do not delete the default cube\nGo right to the properties view and select material icon \nBlender close by itself immediately\n\nIf we add and select cylinder, then select material. Blender wont close, but it will close as soon as cube is selected.\n", "blender crash when open material tab\nOperating system: win7 64\nGraphics card: gtx 1070\n\nBroken: blender-2.80.0-git.3d16a268ee68-windows64\n\nTry to open the material tab makes blender crash\nAn example file here.\n\nthanks\n\n[crash.blend](crash.blend)\n" ]

[ "Geometry instances cannot mix with other instancing\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\nWorked: 3.0 alpha\n\n\n\n[cant scatter.blend](cant_scatter.blend)\n[2021-11-02 19-08-07.mp4](2021-11-02_19-08-07.mp4)\n\n", "Batch Rendering Crashes if EEVEE set in scene\nOperating system: Windows 10\nGraphics card: Any or None\n\n2,83, 2,90, 2.92\n\nEEVEE is set as renderer in the scene file.\nThe scene is send to the render farm. \nOpenGL is not available as render farm is running as background service OR blades machines do not have any GPU at all.\nBlender in Commandline Crashes.\n\n(Side Note: Cycles works fine as CUDA is available within background service)\n\n\n**Expected Behavior**\nReport an error \"EEVEE requires OpenGL. Unable to find/initialize openGL32.dll\"\n\nTo reproduce the issue, you either need some helper service that starts Blender in commandline mode (I can provide one) OR you can use any machine that does not have a GPU installed.\nCreate a new scene with EEVEE as renderer.\nTry to commandline-render the scene.\n\nCommandline that we used:\n\"C:\\renderer_exe\\blender\\win_x64\\Blender_2.90\\blender.exe\" -b \"\\\\isilonai\\woodspeople\\Boar (With fur).blend\" -o \"\\\\isilonai\\woodspeople\\Boar (With fur)\\Brawler####\" -F PNG -x 1 -s 10 -e 10 -j 1 -t 24 -a -y\n\n\nCommandline output:\nR 6| >\"C:\\RR_localdata\\renderer_exe\\blender\\win_x64\\Blender_2.92\\blender.exe\" -b \"C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\" -o \"C:\\RR_localdata\\renderout\\A\\3D\\Blender\\render\\myOut####\" -F PNG -x 1 -s 2 -e 3 -j 1 -t 24 -a -y \nR 7| Blender 2.92.0 Alpha (hash 719bea0d6d06 built 2021-01-12 23:10:47)\nR 8| Read blend: C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\nR 9| Writing: C:\\RR_localdata\\temp\\A\\cube.crash.txt\nR 10| StdErr: Warning! Using result of ChoosePixelFormat.\nR 11| StdErr: Warning! Using result of ChoosePixelFormat.\nR 12| StdErr: Warning! Using result of ChoosePixelFormat.\nR 13| StdErr: Warning! Using result of ChoosePixelFormat.\nR 14| StdErr: Warning! Using result of ChoosePixelFormat.\nR 15| StdErr: Warning! Using result of ChoosePixelFormat.\nR 16| StdErr: Warning! Using result of ChoosePixelFormat.\nR 17| StdErr: Warning! Using result of ChoosePixelFormat.\nR 18| StdErr: Warning! Using result of ChoosePixelFormat.\nR 19| StdErr: Warning! Using result of ChoosePixelFormat.\nR 20| StdErr: Warning! Using result of ChoosePixelFormat.\nR 21| StdErr: Warning! Using result of ChoosePixelFormat.\nR 22| StdErr: Warning! Using result of ChoosePixelFormat.\nR 23| StdErr: Warning! Using result of ChoosePixelFormat.\nR 24| StdErr: Win32 Error# (127): The specified procedure could not be found.\nR 25| StdErr: Error : EXCEPTION_ACCESS_VIOLATION\nR 26| StdErr: Address : 0x00007FFF8DBA1C81\nR 27| StdErr: Module : VCRUNTIME140.dll\nR 28| StdErr: Thread : 00001c94\n[Boar.crash.txt](Boar.crash.txt)\n\n\n", "macOS todo list\nNOTE: this is a direct dump of Install-OS\n\n- [ ] Users have to manually change macOS defaults:\n * Map middle mouse to regular \"Mouse button 2\"\n * Make the Function keys use modifiers (so Blender sees these)\n * Change the Shift+NumPad options to not use Shift (change spaces)\n * The latter two could become part of a new standard macOS compliant map in the future?\n- [ ] ~~Finder aliases or~~(1f223b9a1f afb1a64ccb) hidden files are not being recognized by Blender\n- [ ] macOS swallows some key events, like e.g. emulated numpad - on Norvegian keyboard (see #38273).\n- [ ] Blender prevents macOS from sleep #38702", "Ideas about missing vocabulary in language\nHello,\n\nI have spent a couple of hours localizing Blender for farsi/persian. I have noticed that farsi misses a lot of widely used technical vocabulary.\n\nThere are 3 ideas I can think of right now:\n- There are ways to translate the words into really less common words and phrases in farsi, but they wouldn't be intuitive to the user who reads them as they're using the program. And from what I've seen, it annoys the users in many cases.\n- To use the english word but write it with farsi letters, so it's pronounced like the english word, but it's written in farsi.\n- To use the english letters and not localize them.\n\nI wanted to ask others opinions too. I think english is the richest language regarding the technical vocabulary, I'm sure other languages have faced this problem too. ", "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", "PyGPU: Deprecate shader creation through direct GLSL code input\nWith new backends implemented (Metal, Vulkan), an alternative for creating shaders that is compatible with them was required.\n\nFor this we have [gpu.shader.create_from_info](gpu.shader.html#gpu.shader.create_from_info) and [gpu.types.GPUShaderCreateInfo](gpu.types.html#gpu.types.GPUShaderCreateInfo).\n\nBut we need to make this clear to users. So it's important:\n- [ ] a deprecate message\n- [ ] a better documentation\n\nRefs:\ngpu.html#examples\n#106304\n#107332\n\n", "Blender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb (Idk if this is very relevant lol)\n\nBroken: 2.82 BETA, 689a873029b9, master, 2020-01-15 21:07\nWorked: -\n\nBlender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\n\nAdd a stroke, hover it with your mouse and press your \"Set 3D cursor\" hotkey combination (by default Shift RMB).\n\n**Expected result**\nWhen doing just this, but when hovering your cursor/mouse over a mesh object instead, the 3D cursor will be set on the surface of the mesh object right where the cursor/mouse is hovering over that mesh/object. As the grease pencil is rather new, Im guessing making this react with the grease pencil strokes were just something that was forgotten when implementing it.", "Add support for more gettext flags to UI translation tools\nAs reported in 101830#issuecomment-1023470 , Weblate `C-format` is not very smart, and generates a lot of false-positives.\n\nThe solution is likely to not enforce these checks over the whole messages, but selectively enable them for messages that actually need it (e.g. (almost?) all RNA-extracted message will not have such formatting).\n\nThis will require updates in the python modules and add-on code generating these translation files.\n\n----------------\n\nParent task: infrastructure/blender-projects-platform#65", "Hindi font displayed wrongly\nOperating system: Windows/Linux\nGraphics card:\n\nBroken: 3.2.0 e05e1e369187\n\nDevanagari (the alphabet of the Hindi language) gets displayed wrongly. As a text object it displays `करिष्यामि` with the Font \"Mangal\" as this:\n\n\n\nNotice the difference in the upper part of the letters.\nI'm aware that this might as well be an issue with the font. I checked the font with two font viewers one of which displayed it like blender does, the other one displayed it correctly.\n\nI've also been told that the display of hindi in the UI is not without issues, although that might be a different issue:\n\n\nI am reporting this on behalf of another user and can only relay questions to them, not answer any about hindi language myself. I've attached a blend file and the font they sent me below.\n\n[bug report.zip](bug_report.zip)\n\n\nCreate a text object\nAs font select the one provided in the folder or, if you happen to have it installed, choose Mangal Regular\nChange the text to `करिष्यामि`", "Mantaflow not caching if path contains characters with accent\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.1.0\n\nIf the cache folder path for Manta FLow contains \"french\" accent character, no sim data is computed.\n\n\n- Create a simple blen file in a folder named \"d:\\Données\\Blender\\2 - Projets Blender\\MyFluidSim\\fluidSim.blend\"\n- Create a simple sphere\n- Choose Object/Quick effect/Quick fluid to create a simple domain\n- Set the cache directory to a subfolder of the .blend file\n# Move forward to the fluid sim... No simulation data create\n\nTo fix it :\n- Just rename \"d:\\**Données**\\Blender\\2 - Projets Blender\\MyFluidSim\\fluidSim.blend\" to \"d:\\**Workspace**\\Blender\\2 - Projets Blender\\MyFluidSim\\fluidSim.blend\"\n- Re-open the same file\n# It works\n\nIf cache folder is relative to .blend file or absolute, it doesn't create data if the path contains any character with accent.\n\nThank you for the great job you are doing\nHave a nice day\n\nDidier\n\n\n\n\n", "Blender freezes when using Texture paint or Weight Paint\nOperating system: Windows 10 Insider build19592\nGraphics card: GTX 1660Ti Max Q 6GB\nProcessor: i7-9750H\nRAM: 32GB DDR4-2666Mhz\n\nBroken: version: 2.83 (sub 11)\nWorked: Never (2.79, 2.8+)\n\nBlender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue.\nMoreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting. \n\nAssigned GPU in Preferences>System>CUDA, but the GPU is been barely used.\n\n[Blender.rar](Blender.rar)", "Upload settings from previous version breaks language settings\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\n\nIn previous version I have Russian language only for tooltips.\nAfter uploading in newer version all checkboxes checked.\nSame issue, if i switch to English and back.\n\n**Steps to Reproduce**\n- `Edit -> Preferences -> Interface -> Translation`\n- Change the language (eg. Dutch)\n- Change the checks present below it\n- Switch to some different language and return again to `Dutch`\n- State of the checks is lost\n[2021-03-11_01-56-09.mp4](2021-03-11_01-56-09.mp4)\n\n", "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", "Huge memory usage when trying to paint on UVs far ouside the 0-1 range\nBroken: version: 2.82a (sub 7)\nWorked: Never\n\nBlender freezes when I attempt to use the paint options, after adding an image to Texture Paint. Memory will skyrocket from 150MB to 13GB and does not un-freeze.\nYoutube tutorial I'm following trying to learn to paint textures, bug happens after adding the image at 2:35, and I attempt to paint the model: watch?v=lmbAs9jE1vI\nI am very new to Blender, but pretty sure it shouldn't be doing that when attempting to use the Paint tools.\n\n\n\n- Open attached file\n- Try to paint the mesh\n\n[texture_paint_huge_memory_usage.blend](texture_paint_huge_memory_usage.blend)\n\n", "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" ]

[ "Graphic accents position is wrong when using hebrew text.\nOperating system: Win 10\nGraphics card: RTX 2070\n\n2.83.3\n\n\nGraphic accents position is wrong when using hebrew text.\nOriginal text in word:\n\nI had to reverse the text online(blender does not support RTL text:\n\nafter pasting it into blender:\n\n\nGraphic accents seem to work fine with latin words, but it looks displaced with hebrew characters.\n\nBlend file: [text wiggle reverse.blend](text_wiggle_reverse.blend)\n\nRTL text: `אִישׁ עַל מַחֲנֵהוּ וְאִישׁ עַל דִּגְלוֹ`\nReversed text: `וֹלגְדִּ לעַ שׁיאִוְ וּהנֵחֲמַ לעַ שׁיאִ`", "ERROR - Arabic letters \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.4\n\n[the Arabic language it is full or good supported in blender]\n\n[the Arabic language it is full or good supported in blender, the problem is i can't write Arabic in blender and i can't add Arabic (TEXT) in blender, i need other programs to add like (ILLUSTRATOR) to upload it in blender as (SVG), other problem is i can't write in (outliner) to organize my work]\n\n{[F11600972](blender_2.jpg), size=full}", "Text rendering: Add full support for complex scripts layout (like devanagari, thai, etc.)\nThere has been a (low-level) stream of reports since years now, about users wanting to write in Blender in their own language, which requires [complex script layout](Complex_text_layout).\n\nThis is currently not possible in Blender, we only have a very basic/simple layout code. Some scripts (like Arabic one) can partially work around the situation by using (pasting) some kind of 'pre-processed' strings using pre-layed-out unicode points instead of the 'raw' ones, but this means people cannot directly type in Blender in those languages either. And this is not available for other scripts, like many from South-East Asia (India, Cambodia…).\n\nMost obvious solution currently would seem to be to replace out current layout code with [HarffBuzz](http:*harfbuzz.org/), probably together with [fribidi](https:*github.com/fribidi/fribidi).\n\nThis is not a terrific amount of work, but likely not a very simple one either, and though most of it should be limited to the BLF area of the code, it could require some changes elsewhere too. First step would be to try a quick proof-of-concept, to see how well that could be going…\n\nSee also [D1809: Complex Text Layout](D1809), an old patch adding support to complex scripts." ]

[ "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.", "simply moving the render window is terribly slow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nwith more complex scenes (such as for example blenderman file 57e5084f0fcf294119c5055c) once you render an image and you have eevee in render preview mode, moving the render window becomes very slow, probably because eevee returns to refreshing the previw render without needing it.\n\nsee the video\n\n[GRAbwindow.mp4](GRAbwindow.mp4)\n", "Clicking on image nodes is very slow when Cycles render preview is enabled\nOperating system: Win 10\nGraphics card: RTX 2070\n\nBroken: 3.0 a3e2cc0bb7fe \n\n\nIt seems like clicking on and activating the image nodes in the shader network view is very slow when Cycles render preview is enabled in the viewport. This issue can be seen in relatively dense poly scenes. So this has to be tested in heavy scenes. There should be no reason for such delay when clicking on an image node given no settings is changed. \n\nOne thing I see is that clicking on nodes in general gets slower and slower as the scenes get more complicated, this is also true for the compositor nodes. Not sure why scene complexity might have direct effect on the compositor given no real-time rendering is enabled.\n\nOpen the attached .blend \nEnable Cycles render preview in the left top viewport\nStart clicking on the image nodes in the shader network below.\n\nNow disable the render preview and start clicking on the image nodes. The speed of activating is much faster although still not super fast.\n\n\n\n[slow_nodes.zip](slow_nodes.zip)", "PBVH image texture painting technical design\nWe want to support painting 16K textures on high resolution meshes, 3D rather than just projection painting, and more features matching sculpt mode. For this we are re-implementating texture painting similar to #73935 (Texture Displacement Sculpting design).\n\nThat task sets out a rough direction, this is a more detailed technical design.\n\n### Current Implementation\n\n* Before painting starts:\n**Divide screen into buckets (tiles)** Loop over triangles and add to buckets they fit in\n** Detect if each triangle edge is a seam\n* For paint operation, multithreaded over buckets: \n**Init bucket if not done yet, caching list of pixels with world/image space coordinate, accumulated mask, color pointer, etc.*** Rasterize each triangle in the bucket into pixels\n***Add additional pixels around triangle for seam bleeding** Loop over cached pixels to perform paint operation\n* Blur and clone\n**To lookup a color at an arbitrary position, intersect mesh and read color from image at corresponding UV coordinate** Intersection is accelerated through using triangles cached in buckets and working in screen space\n\n**Seam Bleeding**\nThe current algorithm works by effectively extending the UV coordinates of a triangle and rasterizing additional pixels. The algorithm for has some logic to avoid overlaps with other triangles, however in general there are still some limitations with it:\n* UV islands extended this way may end up overlapping with other islands, and incorrectly bleed into them or not evenly fill in the space between islands.\n* Extending UV coordinates like this does not necessarily give the least discontinuities across seams, since what is baked across the seam may be different due to mapping distortion or different resolution.\n\n**GPU Texture Updates**\nCurrently there is a mechanism for tagging tiles of an image as modified, and only uploading those to the GPUs. However some profiling revealed this to be a bottleneck, so potentially this is not fully working correctly.\n\nWith an incoherent UV map, for example a light map packing individual triangles, this system may also not help since many tiles might be affected even with a small brush radius.\n\nAnother performance issue may be updating of mipmaps. In old Blender versions mipmap updates were disabled in texture paint mode, but it’s not clear this is still working.\n\n### Proposed Implementation\nIn order to support 3D brushes and integration with sculpt features, it seems logical to go with a design proposed in #73935 (Texture Displacement Sculpting design). The basic idea is to reuse the PBVH and iterators over it, so that you can iterate over pixels the same as you do over vertices.\n\nOne important consideration is memory usage. With a 16K texture, just storing 1 byte per pixel is already 256 MB. And multiple 16K textures might be painted on at the same time (either multiple channels or UDIMs). So any additional precomputed data, masks and other utility data structures should not be too large.\n\n**Basic Algorithm**\n\n* Compute a PBVH over the mesh, organizing triangles in spatially coherent nodes\n* For brush operations, find overlapping nodes:\n**If needed, lazily init an array of cached pixels, by rasterizing triangles in image texture space, and storing a pixel index + barycentric coordinate.** Loop over cached pixels to perform paint operations\n\nIn terms of what is actually cached, there are multiple options and the right performance/memory trade-off would have to be found empirically.\n* Don’t store any cached pixels, re-rasterize every time\n* Store only a pixel index, and compute barycentric and then 3D coordinates from that (32 bit)\n* Store pixel index and barycentric coordinate (64 bit, 2x 16 bit for pixel index and 2x 16 bit float for barycentric).\n* Store pixel index and 3D coordinate (128 bit)\n\nHere can also be some coherence from store pixel of the same triangles consecutively in the array, so that memory access is more coherent and certain per-triangle computations can be done once for all pixels in the triangle.\n\n**Seam Bleeding**\nA possible solution for better seam bleeding would be to work more in texture pixel space, similar to how baking works. The new texture margin algorithm in baking extends island pixels outward with a Dijkstra shortest distance algorithm. Then to fill in the pixel it reads pixels from other islands across the seam. This addresses two of the limitations of the existing algorithm mentioned above.\n\nAn interesting aspect of such a method is that it can run as a post processing step, potentially after finishing a stroke or at lower frequency, though ideally it would be fast enough to do it every step. It can also be re-run with a larger margin as post-processing. Or it could run on the GPU even if painting happens on the CPU.\n\nHowever there is the question of how to make this efficient both in performance and memory usage. Some information could be precomputed per texture. For example the image could be split into tiles, and then storing a map of which pixels to copy to which other pixels. Tiles could be lazily initialized in some way, which may require building a 2D BVH of triangles in UV space or some other type of efficient culling.\n\nOne potential other issue is when islands are so small they don’t even cover any pixel. In such extending UVs would have at least written something, whereas this post processing method might leave gaps.\n\n**GPU Texture Updates**\nThe implementation should only changed tiles are updated, and probably (temporarily) disabling mipmaps for images while they are being painted on. Or at least delaying that until the end of the stroke. These optimizations existed in 2.7x, but seem to be broken now and should be restored.\n\nTwo potential optimizations that could be done in addition to that:\n* When the number of changed pixels is a small subset of the entire texture, an array of change pixel indices + values could be constructed and sent to the GPU. Then a compute shader could be used to update the actual texture.\n* Mipmaps could be partially recomputed somehow based on the changed tiles. Currently we use the native GPU implementation, we’d have to write a custom compute shader that can efficiently do this.\n\n**Clone and Blur/Filter Tools**\nThe best approach here is unclear, but some options are:\n\n* Perform ray intersection with the mesh to find neighboring points, accelerated with BVH suitable for efficient ray-tracing. This is quite expensive.\n* Rasterize the mesh from the normal direction into an image, and then sample from that. Quality/performance depends on the image resolution, and some heuristic would need to be found to pick a good resolution.\n* Use mesh adjacency information to find neighboring pixels on the surface. Extend the UV coordinate, and if within the same triangle just use that location. If not then jump to other triangles across the edge, which may or may not be a seam.\n\nFor the clone tool, the normal that we are cloning from could be considered fixed. For blurring the normal direction could also potentially be ignored entirely, and always blur across the surface shape or in 3D space. So there is potential here for caching neighboring pixel locations, though this is memory intensive. \n\n**GPU Implementation**\nImplementing algorithms on the GPU in compute shaders would be another potential speedup. This would significantly increase code complexity and in practical terms is more like a future project than something we expect to start with. However some notes regarding this:\n\n* Storing a pixel list and instead rasterizing could be redone every time. Note however that we can’t simply rasterize to a 16K frame buffer, both because hardware has limits here, and because it may be inefficient. There may be other ways to do this in compute shaders that lets us touch just the pixels we need.\n* For textured brushes we’d need texture nodes evaluation on the GPU, which could become possible if we unify texture nodes so brushes and Eevee share the same nodes.\n* No need to copy pixels to the GPU would avoid some overhead. We’d need to copy the pixels back from the GPU to the CPU at the end of a stroke.\n* PBVH already has GPU buffers per node with vertex coordinates, so these could be reused.\n\n**Sculpt Unification**\nThis design naturally helps integration with sculpt tools, in that the same PBVH and even some tools can be reused.\n\nFor masking, an easy first step would be to reuse the masking tools that work at the vertex level from sculpt, and simply interpolate the mask for pixels. However support for masks at the image resolution (or a lower resolution) is likely useful also.\n\nThe PBVH iterations should be refactored, so it becomes easier to add the pixel case. Likely porting to C++ rather than using a long macro.", "Poor hair editing performance\n{[F5901764](FurBall.blend)}Operating system: Windows 10 64-bit 1809\nGraphics card: NVidia GTX1080Ti\n\nBroken: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-08 17:06, hash: e79bb957fc3, type: Release\nWorked: 2.79b\n\nPoor performance when editing hair system using particle edit mode.\n\n1. Open FurBall.blend (attached) using Blender 2.80.\n2. Switch to Particle edit mode.\n3. Use any editing operation (e.g. Combing). Observe how slow and unresponsive it is.\n4. For comparison, repeat steps 1-3 using Blender 2.79b. The performance should be several times better.", "Mask modifier slow when one of its properties is animated/driven\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\nBroken: version: 2.81 (sub 1)\n\nWhen one of mask properties is animated/driven, it drops performance excessively, the less it hides. \n\n[2019-08-16 10-23-30.mp4](2019-08-16_10-23-30.mp4)\n\n1. Open attached file;\n2. Play animation to see the fps;\n3. Add a keyframe (I key) to the `Display modifier in viewport`.\n\n[maskman.blend](maskman.blend)", "Slow initialization in the rendered viewport after the default normal map added\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.0\n\n\n[slow initialization time in viewport rendering.mp4](slow_initialization_time_in_viewport_rendering.mp4)\nThe slow initialization in the rendered viewport occurs after the default normal map node was added in the Skin shader. (The Skin shader is very simple - it contains just a Principled BSDF and Material Output.) I have tried both CUDA and Optix, and the slow initialization exists in both cases after the default normal map node added. \n\n\n[Sample to test slow initialization in viewport rendering.blend](Sample_to_test_slow_initialization_in_viewport_rendering.blend)\n\nSteps to reproduce the bug:\n\n1, Download the sample file and open Blender; \n\n2, Select the mesh, and go to the Sculpting mode, and then under the \"Remesh\" tab change the Voxel Size from 0.4 m to 0.004 m, or even smaller value if your computer can handle. Click \"Remesh\".\n\n3, Then click the rendered preview. You will find that the higher the poly-count, the slower initialization speed. \n\n4, Go to the Shading mode, and remove the Normal Map, and click the rendered preview. Your initialization speed returns to normal, even if the poly-count is high. \n\n", "Some GUI Pannel takes forever to load\nHello,\nOperating system: windows 10\nGraphics card: NVDIA RTX a2000 with latest driver\nIntel I7 with desactivated integrated gpu\n\nBroken: 3.5, 3.6\n\nBlender starting up is very slow\nmore importantly GUI is unresponding ( often around 25 sec ) when accessing to:\n>\"shading\" panel\n>Window explorer ( loading an image texture for example)\n>Material preview mode\n>Display render preview\n>Accessing preferences\n>Rendering window\n\nNo problem for modeling rendering etc. loading theses GUI parts seems to be the only lag itself.\n\nWhat i've tried:\n>Disable all addons\n>Factory user prefs\n>Deleted user pref app data folder\n>Updating driver to the latest version\n\ntried on 3.5. > Still the same\n\nThe lag is present even with the most basic file available\nIt has always been like so since i installed my pc.\n\nThanks\n\n", "Dynamic Paint doesn't update to original values on start frame\nOperating system: win10 64\n\nBroken: 2.81\n\nAdd *Dynamic Paint (Canvas)* to any mesh and try to set 0 as a start frame of simulation.\n\n1. Open file and see how Displace modifer doesn't affect mesh\n2. Run animation -> bake current cache\n3. First problem: see how weight is empty at the mesh origin (Displace modifier works except begining of animation)\n4. Second problem: return to frame 0 -> weight doesn't updated to original values (Displace modifier still active on vertex group)\n\n[dyn_paint.blend](dyn_paint.blend)", "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", "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)", "Proposal: Improving Brush Workflow in Blender\nThis is an ongoing design-topic about improving the way we handle brushes in Blender. This applies to Grease Pencil Draw Mode, Texture Paint Mode, Vertex Paint Mode, Sculpt Mode and so on. \n\n## Terminology\n\n\n**Tool**\nA tool a something that can perform a type of operation. Extrude, paint, erase, line etc are tools.\n\n**Brush**\nA brush is essentially a preset for tools. As an example, the draw tool has a bunch of options for stroke width, textures, curves, spacing and so on. A brush acts as a preset to set these various settings which can be combined to create infinite combinations of settings. Brushes act as a way to save and reuse these tool presets.\n\n\n## Problems\nThe way we handle brushes in Blender is has some issues:\n\nIn the toolbar, we directly select brushes, rather than the tools they belong to. This means we mix up brush icons and tool icons in confusing ways. In fact, the brush icons currently can’t update to reflect changes in brush settings, making the icons go out of sync if you make changes to the brushes. It also makes it so the list of tools in the toolbar becomes very long, because we mix both tools and brushes, and there’s a toolbar entry for every brush variation. So if you use Sculpt Mode, and want to make three brushes for the Smooth tool, the Smooth tool now has three copies in the toolbar, all with the same Smooth icon. That is not great.\n\nEven worse, sometimes we don't even put tools inside the toolbar, because of this clash. Case in point: In the Grease Pencil Draw Mode, the Line, Oval & Rectangle tools are placed in the header, not the toolbar, which has the brushes instead. The distinction between tools and brushes is unclear and often swapped around in inscrutable ways. \n\n## Proposal\nWe can make this much more straight forward to use, and much more powerful, like so:\n\n*In the toolbar, we only show the tools.*\n\nThe brushes then become a property of the tool, and can be selected in the tool settings/top bar. This means we can make nice generic icons that represent the tool, and then dynamic brush icons in the brush popover that updates to reflect the changes in settings, like this:\n\n\n\n*Here you can see the list of tools on the left, and the brushes popover in the top bar.*\n\nHere's a more visually complete version:\n\n\n\n\nThis is using Grease Pencil Draw mode as an example. With this change, we can now properly put the Line, Oval and Rectangle tools inside the toolbar and make the brushes separate, so they can apply to any of the tools used. \n\nIn the Tool Settings, we can display an expanded version of the Brushes popover to quickly switch between brushes:\n\n\n\nThe brush icons update dynamically to reflect the changed settings, making brushes much more useful. Users can still name brushes and share them, just as before.\n\nHere are specific examples of how the tools and brushes in the various paint modes in Blender:\n\n### Grease Pencil Draw Mode\nHere we should add the Line, Rectangle & Circle tools to the toolbar, and then expose the brushes for the corresponding tools.\n\n\n\n### Texture Paint Mode\n\n\n\n### Vertex Paint Mode\nBlending Modes should become brush settings, not separate entries in the toolbar\n\n\n### Weight Paint Mode\nBlending Modes should become brush settings, not separate entries in the toolbar\n\n\n\n### Sculpt Mode\n\n\n\n\n## Quick Access\nWith this proposal, users can change the active brush using the top bar. To make switching faster, they can also directly select the active brush in the Tool Settings tab in Properties. However, when the Properties isn't visible, we could still have other quick ways to access brushes.\n\nOne idea, is to use a shortcut to bring up the same brush panel with previews, and users can select brushes from here. We could even enable shortcut keys here, so that typing any number on the keyboard would enable a given brush.\n\nThe exact shortcut can be defined as part of the keymap, and can be decided separately. \n\n\n### Switching Brushes\nIn order to make switching brushes in Blender fast and fluid, we should provide an expanded list UI, so that users can directly click on any desired brush directly, without having to open up a popup to do so every time. The *dynamically generated* **brush previews** help the user to know what the brush will look like.\n\n\n\nNow that all the tools in our paint modes are expanded and directly available in the toolbar, we can add an affordance so that users can hold down on the tool to get a fly-out popover to set the brush, like so:\n\n\n\nHere's an example of the same thing in Sculpt Mode:\n\n\n\n\nBy default, we only show brushes that are relevant to the active tool. When switching brushes, you don't expect the tool to change, only the brush, and this approach makes it easier to categorise brushes. \n\nHowever, there are some situations where it can be useful to quickly jump between specific brushes across several tools. We can support this by having a toggle to enable viewing all the brushes in the current mode:\n\n\n\nWith this enabled, we can still display the tool that the brush will activate when you enable it, using the tool icon here:\n\n\n\nSomething we can do to aid in switching and organising brushes, is the ability to group them by category. If a user has, say 200 brushes, keeping them all in one list is not tenable. Therefore, we can support a way to give each brush a category tag name. At the top of the brush selector, users can then switch between these categories:\n\n\n\nAnother thing we can do here, is add a way that users can favourite certain brushes they may use a lot, even if they are in different categories. By clicking the heart symbol, the brush is added to the favourite brushes category:\n\n\n", "Selection not transfering to paint mask (vertexpaint, weightpaint, texturepaint) when a triangulate modifier is present\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.81\n\nBroken: version: 2.92.0\nWorked: -\n\nIf you face select on edit mode, it will carry your selection to weight paint face select or texture paint face select or etc.\nBut if you have triangulate modifier on it will not carry it over.\n\nI did not know this and there was not error message about this anywhere on blender.\n\nLoad this file: [faceselect001.blend](faceselect001.blend)\nyou see some faces selected with triangulate modifier on.\ngo to weight paint or texture paint and you see none.\n\nI know this might not be a bug but how software works BUT for a common artist, at least adding a message that it will not carry over selection would have been nice, or disabling triangulate on view automatically when you go to those modes.\n\n", "No \"affect alpha\" in brush settings in the Image Editor\nOperating system: Linux-5.3.0-40-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 7)\n(as well as the latest alpha: version: 2.83 (sub 5))\nWorked: 2.80 (Checkbox existed in Image Editor brush settings, but had NO effect on brush behavior)\n\nIn the 3D Viewport as well as the Properties Editor while in Texture Paint mode, all brushes offer the \"affect alpha\" option in the \"Advanced\" section of the Brush Settings. In the Image Editor that option is missing from the \"Advanced\" section for no apparent reason.\n\n\nOpen Blender with factory settings. Switch to \"Texture Paint\" tab. Compare the \"Advanced\" section of the active brush's tool settings in the Image Editor to that in the 3D Viewport or Properties Editor.\n\nSurely this has to be a well-known issue and exists only due to technical limitations of some kind.\nWhat should I tell my students why this inconvenience exists and when it will be addressed?", "Polishing the Painting Experience\nThere are a few tasks that would enhance the texture painting pipeline that could be prioritized before advanced features like layered textures is even considered.\n\n## Existing Painting System\n\n### Small Tasks (e.g., bug fixing)\n- [ ] Graphics Tablet Lag when in Texture Paint mode in Blender 3.0 #93796\n- [ ] Undo bugs\n - [ ] Undo eliminates brush texture #88592\n - [ ] Texture paint undo can changes texture slot #62520\n - [ ] Texture Paint mode tools swap when exiting maximized area #98014\n- [ ] Color space support for texture painting #95797\n- [ ] Sync Image Sequence options (Frames, Start Frame, Offset, Cyclic, Auto Refresh) #109769\n- [ ] Texture paint: Bleedind around thin cuts do not fill texture #106066\n- [ ] Add support for \"Channels\" to the Images & Color Attributes #108404\n- [ ] 8/16 bit textures have different strength behavior (premultiplied problems) #101436\n- [ ] UDIM bugs [need report]\n- [ ] 3D mirroring in Image Editor\n- [ ] Other bugs (by Daniel Bystedt) [need report]\n\n### Bigger Tasks (e.g., re-designs) - need design\n- [ ] Image syncing between Editors via active image canvas #103636\n- [ ] Multi-object painting\n- [ ] Multi-object uv editing\n- [ ] Support \"viewport\" face sets in Image Editor\n- [ ] Square brush\n\n## 3D Brush\n\nRelated to #96225\n\n### 3D brush vital\n- [ ] Color sampling\n- [ ] Erase blend mode\n- [ ] Affect only visible (Show/Hide)\n- [ ] Affect Alpha option\n- [ ] Masking\n- [ ] (2D) Fill operation\n\n### 3D brush additional\n- [ ] Feature parity\n - [ ] Blur & Smear brushes\n - [ ] Clone brush\n - [ ] Sync masks and edit mode selection\n - [ ] Paint modified geometry instead of base mesh\n - [ ] Missing brush settings\n - [ ] Stencil masking\n- [ ] Image editor syncing\n- [ ] Dedicated paint mode\n- [ ] Performance\n\n" ]

[ "Vertex Color/Attribute Edit Design\nThis task lists and details all tasks related to the design of a Sculpt/Vertex painting mode and a attribute edit mode.\n[2019-11-20 23-59-09.mp4](2019-11-20_23-59-09.mp4)\n\n# Vertex Colors Project Description\n\n\n\n## Sculpt/Paint Mode\n\n\n\nBy adding the MVertCol datalayer we can reuse the sculpt mode code to support painting functionality inside Blender.\n\nThis painting mode is intended to be an artistic painting mode with support for all tools and workflows designed for this task. Texturing, illustration and concept art uses cases fall into this category. This does not mean that other modes with other uses cases should not have brush tools or painting functionality.\n\nThis functionality is accesible inside the current Sculpt Mode to support features and workflows that could take advantage of sculpting and painting at the same time, as well as sharing common features instead of implementing a painting and a sculpting version of the same thing.\n\n### Tools\n\n**Paint Brush**\n\nImplementation of Blender´s main painting brush in Sculpt/Vertex paint\nmode.\n\nThe behavior of this brush is most likely going to be used as a reference to implement 2D and 3D painting. The goal should be to support the same brush presets in all paint modes, so the implementation in the different paint modes should match.\n\n**Brush paint properties**\n\n[Vertex Colores Test 1.mp4](Vertex_Colores_Test_1.mp4)\n\n**Density noise**\n\nDensity is a factor that controls how many elements inside the brush radius are going to be painted. This adds extra detail to the stroke without needing to add a texture. Useful for simulating pencils or organic mix brushes.\n\nThis works by hashing the pseudorandom values before applying the paint to each element (in this case, hashing the vertex index + brush position). Some other painting apps have the density seed fixed per stroke instead of per sample. We can add an option to support both.\n\n**Opacity/Flow**\n\nOpacity controls the alpha of the painting color (it is currently called strength in the UI, so it should be renamed for painting modes).\n\nFlow controls how many brush samples are needed to reach the opacity alpha value. This is often explained as “how much paint the brush applies”.\n\nTo support that, the PBVH needs extra compositing buffers to mix the paint from the current stroke on top of the original colors.\n\n**Wet Mix/Persistence**\n\nThis controls how much paint is picked from the surface and added to the brush color while painting. This is essential to support proper brush color blending while painting.\n\n**Falloff hardness**\n\nHardness should be the main property to control the brush fall off. The current Falloff panel should be hidden in the UI as an advanced brush option as changing that curve breaks the intended behavior of the brushes.\n\nFurthermore,Hardness is a linear property and it can be mapped to pressure or tilt, which is a basic behavior of any painting software.\n\nAs it is implemented now, hardness shifts the falloff interval towards the edges of the brush.\n\nSome features in the sculpt and paint modes are already coded with a hard coded hardness value, so we need to replace it with the brush property.\n\n**Procedural tip shape**\n\nThe functionality of this feature is implemented in brush_test_cube and it is shared with the sculpt Clay Strips brush. It allows to change the brush tip shape between a square and a circle.\n\n**Tip shape rotation**\n\nThe paint brush should support tip rake rotation. The implementation is identical to the clay strip brush.\n\nWe can also support locking the initial rotation in screen space. This is useful for creating inking and lineart brushes with non uniform scaled tip shapes. The initial rotation can be controlled by another brush property.\n\nThis feature is more important in 2D paint than in 3D paint, so I need to investigate a correct way to implement it.\n\n**Tip shape scale**\n\nThis is achieved by scaling the brush local space matrix. Exposing one axis as a brush property is enough as you should be able to set the rotation.\n\nWe can also look at using the brush tip scale to adjust the brush spacing accordingly, but it is not absolutely necessary.\n\n**Default brush presets**\n\nAs the new brush with all the new painting properties is flexible enough to create brushes for different purposes, we may want to ship Blender with a small set of default brushes (like Grease Pencil).\n\nWe may need feedback from texture artist and illustrators to design a set that fits most users needs.\n\n**Brush input curves**\n\nUntil we have the functions branch merged and the new brush input system in master, all brushes should come with a default input curve hard coded to get the correct behavior (this is something that was done during the 2.82 development in the sculpt brushes).\n\nAs part of this task, it may be needed to add extra flags to map pressure to some of the new attributes, similar to how we are now enabling pressure/size and pressure/strength. This flags won’t let users modify the curves.\n\nAfter adding the new node based brush input system, all these attributes should be exposed to the node network and users would be able to choose how they want to map them to the pen pressure/tilt\n\n**Color Mix Modes**\n\nAdd all the color mix modes available in Blender to the paint brush. The implementation is straightforward.\n\n**Paint Brush UI**\n\nWe need to decide were to add the new brush properties in the UI. Properties like hardness should be easily accesible, both for sculpting and painting.\n\nWe may need to reconsider how the top bar is organized in Sculpt Mode, as currently it does not make much sense. Often the most important properties of the brush are hidden under a popover.\n\n**Color smooth brush**\n\nSimple color smoothing function, similar to the current mask smooth. It can be included as part of the main paint brush when pressing shift or as a separate tool.\n\n**Liquify tool**\n\nThis brush tool should move the vertex colors without displacing the geometry. I need to check how to implement it, but it could be similar to the Slide/Relax brush.\n\n**Color filter**\n\n[P2N6BZfTCgcLiz3s.mp4](P2N6BZfTCgcLiz3s.mp4)\n\nThe color filter is a tool that modifies all colors in the sculpt at once taking the sculpt mask into account. The implementation is exactly the same as the current mesh filter, so all extra modifications needed to support this are already in Blender (FilterCache, filter fully masked nodes)\n\n**Color fill**\n\nWe may consider adding the color fill functionality to the color filter instead of adding a separate fill color operator. The main advantage is that users will be able to control the intensity of the fill in real time, because in sculpt mode the redo panel is not available. We need to add a color property to Sculpt to support this (similar to the Texture or Gravity Object datablock)\n\n**Texture color filter**\n\nExact same implementation than the Mesh texture filter but for colors instead of for displacement. This needs a texture datablock to be in Sculpt, similar to the gravity object.\n\nWe may want to consider this later as it uses the old Texture datablock and nodes, which is currently deprecated.\n\n**Color editing filters**\n\nThis is the standard set of color editing operations on colors, also available in Cycles/EEVEE and in the compositor. Most of these operators are already coded for MLoopCol and can be easily ported to the color filter.\n\n**Gradient tool**\n\n[MS_Hf5pqrpjSTNf_.mp4](MS_Hf5pqrpjSTNf_.mp4)\n\nThe gradient tool is almost identical to the color filter. The main differences are the input code (this tool needs the direction of the cursor movement) and the functions that are used to modify the colors.\n\nIt includes the basic types of gradients that are supported in most graphic editing software.\n\nIt also supports snapping to 90 degree angles and it takes the sculpt mask into account.\n\n**Top bar color ramp UI design**\n\nIf we render the current color ramp template in the top bar in a single row it does not look nice (it usually needs 3 rows). We may want to improve this, but it does not affect the functionality of the feature.\n\n**Gradient types**\n\nAll gradient types work the same, they just use a different geometry operation to determine the gradient (Distance to plane, distance, angle…)\n\n**Radial gradient**\n\nGradient based on the distance to the initial position\n\n**Linear gradient**\n\nGradient based in the distance to a plane\n\n**Circular gradient**\n\nGradient based on the angle difference between the mouse drag vector and the initial position - vertex position vector.\n\n**Active vertex color picker**\n\nThe painting sample_color operator should pick the color of the active vertex and assign in to the brush (or to the UnifiedPaintSettings color)instead of picking the shaded color from the viewport.\n\n### Features\n\n**Brush management**\n\nThis task needs the asset manager in master in order to start.\n\n**Brush engine preview generator**\n\nThis needs the new input system on top of the asset manager in order to start. The idea is to generate brush previews based on the parameters of the new brush engine and use them in the asset manager.\n\n**Asset manager global brush palette**\n\nAfter merging the asset manager, all brushes should be accesible from a single place, changing the tool automatically when you select a brush preset.\n\n**Import/export brushes**\n\nWe need to decide how are we going to store, export and import brushes. This is an asset manager related task.\n\n**Import/export**\n\nImport/Export support for the vertex colors layers. We need to check which formats and use cases support this.\n\nIn the meanwhile we can use the vertex colors/attributes conversion operators to get the colors in an out or Blender\n\n**Sculpt mode integration**\n\nThis describes different task that can be done to create new tools and workflows that can be done after supporting sculpting and painting in the same mode.\n\n**Sculpt + Paint at the same time**\n\nThis feature is useful when creating concept art. As all the painting functionality shares the same code as sculpt mode, this is easy to support.\n\n**Paint capability**\n\nWe need to add an extra paint capability to the brushes to enable only the sculpt brushes that make sense for painting (for example, it does not make sense that the pose brush applies paint).\n\n**Undo support**\n\nWe need to add a SCULP\\_UNDO\\_COORD\\_COLOR flag to support storing the undo data for coordinates and colors at the same time. Internally, this is just calling both coord and color store functions in the same node undo push.\n\n**Sculpt mask integration**\n\nWhen painting, the sculpt mask and all the tools to edit it (mask filter, mask expand, box and lasso selections) can provide the same functionality as selections in other painting software, so we don’t need to code another selection system for painting.\n\n**Mask by color operator**\n\nSimple operator that mask all similar colors to the active vertex color.\n\n**Mask expand by color**\n\nThe current mask expand supports two modes (topology and curvature). We can turn this operator property into an enum and add a mask expand color mode that calculates the mask expand factors based on the color differences. After this change, this operator should provide the same functionality of the “magic wand” or “smart selection” in other painting softwares.\n\n**Automask by color**\n\nThe automasking code supports enabling multiple automasking operations. We can create another automasking modes that assigns mask values automatically based on the color difference of the active vertex when the stroke started. This can be useful when sculpting across painted ¨materials¨.\n\n**Remesh support**\n\nOne of the main features of this paint mode is that you can sculpt on models with colors without using UV. This allows to keep the topology dynamic using the remeshers.\n\n**Voxel remesh Reprojection**\n\nThis will add the “Preserver paint colors” option to the Voxel remesher. All vertex colors layers are recreated and colors are transferred using the nearest vertex color from the previous mesh. This is also how the “preserve sculpt mask” option works.\n\nThis function can be also added to Quadriflow, but it does not make much sense as Quadriflow is supposed to be used with Multires.\n\n**Quadrilfow reprojection to multires**\n\nQuadriflow remesh should produces a base mesh with the sculpt detail projected to the appropriate Multires level. This is currently not implemented as the current Multires modifier is not enabled for sculpting.\n\nAfter enabling Multires and implementing this feature, it should also support vertex color reprojection.\n\n**Multires support**\n\nWe need to check the status and roadmap of Multires before tackling these tasks. If sculpting multires is not fully functional, it does not make sense to add color features to it.\n\n**Multires color data layer**\n\nA datalayer needs to be added to support vertex colors in Multires, similar to how the Sculpt Mask works.\n\nThis also needs all necessary updates to Multires to support vertex colors in the grids.\n\n**Multires level propagation**\n\nColor values need to be propagated across levels without creating artifacts.\n\n**Multires texture baking**\n\nAfter finishing these task, Sculpt/Vertex paint mode will be a more advance painting more than Texture paint and some users will want to use it as the main painting mode. Until we design and update texture paint to support all these painting features it would be nice to have some baking functionality to be able to work on texture colors by converting them to vertex colors. Sculpt mode can easily work with 17M vertices + duplicates on Multires, so supporting painting a baked 4K texture on vertex colors seems like a reasonable use case.\n\n\n### Rendering\n\n**Workbench vertex color rendering**\n\n**PBVH Rendering**\n\nSculpt PBVH rendering support for regular meshes (PBVH\\_FACES). We also need to add support for PBVH\\_GRIDS if we want to support Multires.\n\n**Object Mode rendering**\n\nRegular workbench vertex color rendering for the rest of the modes. This should be enabled when enabling the vertex color mode in the Shading popover\n\n**EEVEE/Cycles vertex color node**\n\nVertex Colors layers should be accesible with the Vertex Color node to render in Cycles/EEVEE.\n\n### Color management\n\nVertex colors are stored as floats in scene linear color soace as defined by the OpenColorIO configuration. By default this would be a linear color space with sRGB chromaticities. This is the same color space as for example material colors. That means these colors can be used as is for rendering without any color space transformation.\n\nNote that by convention old vertex colors are stored in scene linear color space with the sRGB transform used for compressing them to bytes. This transform should be considered purely a compression and has no semantic meaning.\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.\n\n\n# Development Plan\n\nI recommend that the main priority for merging and reviewing the patches should be getting the full version of the paint brush to master as soon as possible, even with a temporally incomplete painting workflow. The design decisions on parameters, default values and behavior are really hard to get right, it would me nice to have as much artist feedback as possible. We will continue making changes to the brush during the release cycle to ship Blender with a proper implementation, defaults and presets.\n\n## Datalayers and Paint Brush\n\nAs it is possible that the design of the brush will be reused for texture painting, this is a critical task. In order to achieve this, these are the task that the first patch should contain:\n\n- MVertCol datalayer and PBVH undo support to implement the brush.\n- Paint brush (with all paint properties)\n- Workbench vertex color rendering: PBVH color rendering\n- Active vertex color picker\n\nIn order to create small test projects to test the brush more extensively, it would be also recommended to include:\n\n- Remesh reprojection support\n- Workbench object mode rendering: Object mode rendering\n- Cycles/EEVEE vertex color node\n\nWith that set of features merged, we should be in a good place to start creating vertex paint projects.\n\nNote that the naming (Sculpt vertex colors vs vertex colors) won´t be final when merging this patch. This is to avoid duplicating the length of the patch with a huge name of line changes that won’t make any difference on what we should be doing at that stage.\n\n\n## Renaming\n\nAfter merging the first patch, we can create another patch that includes only the renaming of the current code functions and UI. By doing this, we reduce the amount of lines changed in the first patch and we will have more time to decide the final naming of the datalayer to make it less confusing for the users.\n\n- Sculpt Vertex Colors -> Vertex Colors\n- Vertex Colors -> Attributes\n\nAlternative:\n\n- Sculpt Vertex Colors -> Sculpt Colors\n- Vertex Colors -> Attributes\n\nAfter this patch, we should have stablished the difference between Painting and Attribute editing described in this patch. Vertex Paint/Vertex colors will became Attribute Edit and it will have the exact same functionality, with is a subset of the Attribute Edit mode.\n\n## Tools\n\nAfter merging the two initial patches, we can start merging the rest of the tools, in no particular order. \n\n### Gradient and Mesh Filter\n\nThe Gradient tool and the mesh filter code is almost identical, so it should be easier to review them at the same time. Also, both share some common code (color data in the filter cache)\n\n### Color Smooth Brush\n\nThis is just a copy of the regular smooth/mask smooth brush but that works on color data. Should be easy to review and merge.\n\n\n\n\n\n\n\n" ]

[ "Tool cursors are too small in HD mode on WIN32\nOperating system: MS Windows 10\nGraphics card: AMD Radeon Vega Pro Duo 32GB (Polaris)\n\nBroken: 2.8 RC3\nWorked: (optional)\n\n\nI am using the high resolution mode of MS Windows 10; I am big sized 4k monitor\nAnd blender 2.8 supports it so I am able to see the beautiful HD UI in blender. All the UI element sized doubled and nicely anti-aliased.\nHowever, any tool cursors stays in normal size. So it kinda looks awkward and also I can't actually see the cursor; it's too small. \n\nbtw, I couldn't have captured the image related because Windows basic capture function didn't allow me to capture any tool cursor in blender.\n\n\n1. Run Blender 2.8 RC3 in High Resolution Mode of MS Windows 10.\n2. Select the box placed in the center of the screen.\n3. Change the mode to vertex edit\n4. Select knife tool on the left side \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).", "When search is active in keymap section of preferences, top level text truncated for no reason.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen search is active in keymap section of preferences, top level text truncated for no reason.\n\n\nGo to Edit > Preferences > keymap.\nIn the search box type \"eye\".\nSee the useless truncated text, and all the unused space.\n\n", "UsdPreviewSurface import is missing UV transformations\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 512.59\n\nBroken: version: 3.1.2\n\nWhen importing USD files, UV transformations (offset, scale, rotation) are missing in the imported material graphs when UsdPreview import is enabled.\nUsdTransform2d spec here: spec_usdpreviewsurface.html#transform2d\n\n- Download and unzip [TextureWrapModes.usdz](TextureWrapModes.usdz)\n- Import \"FBXTextureWrapModes.usdc\" with UsdPreviewSurface enabled\n\n- enable texture preview\n\n**Expected:**\n\n\n**Actual:**\n", "Compositor: Viewport issues when zoomed in\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera is not fully in view.\n\n\n* Open this file: [zoomed_in.blend](attachment)\n* Notice that in the viewport the view is zoomed in inside the camera view.\n\nCurrent buggy result:\n\n\nThe mask only matches when the entire camera is in view:\n\n\n", "VSE: Ensure all operators in the Strip menu are working on the selected and not only on active strip (+unselected) \nAs it is confusing and inconsistent to have functions in the Strip menu which only works on properties of the active strip even if it is unselected, this design list is for ensuring all functions in the strip menu to work on selection. \n\n- - [x] Swap Strip: #91191 Fix: [D12441](D12441)\n- - [x] Effect menu. Fix: [D12451](D12451)\n- - [x] Movie(Set Render Size + Deinterlace) and Image(Set Render Size + Separate Images) menu entries should be moved into the source sidebar with +alt for selection. Fix: [D12464](D12464)\n- - [ ] Add Modifier in the menu needs to work on selection and is missing +alt for selected, when executed in the sidebar.\n- - [ ] Inputs menu: Swap data should go into the swap menu and the rest into Strip Source sidebar with +alt for selected. Bug report: #91350\n- - [ ] Toggle Meta and UnMeta should go into the strip sidebar, as they are only working on the active strip. Old patch: #74130\n(A checked checkbox means a fix has been submitted, but not necessarily been committed)\n\n", "Addon custom categories/tabs are broken (are gone after a session)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\nBroken: 2.80\nWorked: 2.79\n\nChanging the category (in add-on preferences) on add-ons that allow you to change the category does not retain placement after restart.\n\nTested using \"Align Tools\" add-on as example.\nRelevant reference:\nT48459\n\n- Open default scene\n- Go to \"Align Tools\" (Prefs > add-ons)\n- Enable add-on and change `Tab category` string to something else (say \"AB\")\n- Save preferences\n- restart blender.\n- Now the label of tab remains same (AB) in preferences but it does not reflect in UI (sidebar)", "Edit mode: Fill region operator wrong behavior.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: since 2.79 till now. \nTested with 2.79b, 2.83.9, 2.92, 2.93 3ea1779365b5\n\n\nFill region operator fails with this geometry. Test my file.\n{[F9906012](9540941.png) size = full}\n[untitled.blend](untitled.blend)\n[2021-03-23_23-38-13.mp4](2021-03-23_23-38-13.mp4)\n", "Blender 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", "GHOST:: m_windows not clearing list of fullscreen windows \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 8)\n\nI just wanted to warn you about a potential bug in GHOST when we close a fullscreen window. The problem is that I don't know how to reproduce it in blender official.\nThen this is just if someone is interested...\n\nWhen we close a fullscreen window, GHOST::m_windows list doesn't erase the fullscreen window. Then m_windows list size increases.\nWhen I erase the fullscreen window from m_windows list, it is fixing a crash with our fork of blender (upbge)\n\nI describe the steps to reproduce the bug here: 4fc32990010d5765ba1abd523d57b252be73a657\n\nThis needs to compile restart_hacks branch from upbge github: upbge\n\nThere's a link to the testfile in the commit in mentionned.\n\nJust in case:\n\n[ledi.blend](ledi.blend)\n\n", "Eyedropper for props does not work in dialog boxes\nBlender 2.81, 71f2229b0d82\nfor example, in Texture Paint Context Menu\nI wanted to implement something using Operator and context.window_manager.invoke_props_dialog()\nThis is not a bug, but why not do it at the dialog level.\n", "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", "Outliner: Data API view can expand non expandable properties\nThe Data API view in the outliner let you click on the (invisble) expand arrow on non expandable properties.\n\nThis result in the property value to become invisible. You can click to bring it back, so I think it's only a display issue.\nNot all properties seems to be affected.\n\nBefore:\n\nAfter:\n", "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. ", "Wireframes aren't displayed in Edit Mode when Overlays are off. \nBroken: 2.82a, 2.83, 2.90 alpha\nWorked: 2.81a\n\nWireframes aren't displayed in Edit Mode if Overlays are turned off, but they're only shown in object mode, or if there's a modifier with \"display in edit mode\" option. \n\nOpen default file.\nChange to wireframe mode.\nturn off overlays.\nchange to edit mode. Wireframe won't be shown.\n" ]

[ "Broken file browser in render window\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 71)\nWorked: (optional)\n\n\nWhen i try to render in 4000x4000 resolution and render window is on second monitor (in full screen mode. Double click on titlebar.) After render when i press shift+s to save image, file browser opens but without top buttons and possibility to write filename and save. I must drag titlebar and then file browser is ok.\n\nexample:\n\nWM8KBm0bp6E\n\n\n\nsystem Info:\n\n5Pa2AVtf\n" ]

[ "Byte vertex colors are sometimes interpolated in sRGB, sometimes linear\nOperating system: Linux\nGraphics card: Intel Integrated\n\nBroken: 2.93.0, 3.0.0 Alpha at 8c21667\nWorked: \n\nA Data Type: Byte Color color attribute is interpolated in sRGB space when subdividing or using the knife, but in linear space when interpolating across a tri in the viewport. I expect it to be consistent.\n\nThis is different than Data Type: Color (FLOAT_COLOR) attributes, which are always interpolated in linear, and vertex colors in pre-2.8 versions, which are always interpolated sRGB.\n\nAdd a plane, paint one corner white, the others, black. Add a Subdivision/Simple modifier and turn up the levels. Look at the result.\n\n\n\nI expect it to approach the ideal bilinear result in linear space, but it's clearly approaching the ideal bilinear result in sRGB space. Same thing for manually subdividing with the knife.\n\n**Addition after 3.2**\nIMO since there is a new way to get linear vertex colors, it would be nice if FLOAT_COLOR attributes always interpolated in linear space and BYTE_COLOR attributes always interpolated in sRGB. 2.8 removed the ability to get sRGB interpolation and it would be nice to have both options (pre-2.8 files would also be viewable with the intended interpolation).", "Baking Procedural Wave Textures\nOperating system: Win10\nGraphics card: Nvid 2080ti / 3090 \n\n3.4 (and others)\n\nCannot bake these textures correctly. \n\nCreate an object. \nAdd a wave texture, set it to uv, and scale it to show many even lines. \nAdd a color ramp to tighten those lines, setting it to constant. \nPlug this into the bump/normal to make raised lines. \nNow bake this. \n\nThe lines will be a broken mess most of the time. I have tried almost every trick I can find/think of, and nothing makes this better. \n\nI am not sure it's a bug, but it is certainly a problem.\n\n", "Alt-Drag (multi-editing) fails for HSV color buttons\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.83 (sub 1)\nSeems to be a long-lasting issue, as even Blender 2.81a shows the same behaviour.\n\nPretty much the title. \nTrying to assign an object color through the Object Properties tab (Viewport Display > Color) to multiple Objects doesn't work, neither by picking the Color on the Color Wheel, nor by moving the HSV sliders, while Alt-Clicking. Only the last selected Object will update.\nHowever:\n\n\n - If sliders are set to RGB, editing them will correctly affect all selected Objects.\n - The Alpha slider, which is shared between all three Color Wheel modes, works as intended and affects all selected Objects.\n\n\nFrom the Info console I've noticed a tuple is set everytime a Color is picked from the Color Wheel, but doesn't show anything when using the HSV Sliders.\nMoving the the RGB and Alpha sliders correctly sets each Object's property to the selected value.\n\n\n\n\n - Open Blender, default startup file\n\n - Add>Mesh - Select any kind of Mesh Object (have at least 2 items in the scene, or more)\n\n - Go to the Shading Panel in the top right and Select \"Object\" down the Color section, to see Object Colors in the viewport\n\n - Press A to select All Objects, or alternatively, select them one by one by Shift+Right Click\n\n - Go to Object Properties > Viewport Display > Color\n\n - Hold ALT either while clicking on the Color Wheel or while moving the HSV Sliders. Only the last selected Object will update.\n\n\n\n\n - While holding ALT, try moving the Alpha slider. All selected Object will update.\n\n - In the Color Wheel, select the RGB tab. While holding ALT, try moving the R, G or B slider. All selected Object will update.\n\n\n\n\nHere's a quick demonstration:\n\n[2020-01-20_22-01-14.mp4](2020-01-20_22-01-14.mp4)\n\nAnd the Info panel readings:\n[2020-01-20_22-02-46.mp4](2020-01-20_22-02-46.mp4)\n", "Cycles Bake Selected to Active with transparency gives undesirable results\nSystem Information:\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GT 635M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\nBroken: version: 2.81 (sub 16)\n\n\nBug or unintended behavior:\nBaking using \"Selected to Active\" does not take into account transparency \n\nHow to reproduce:\nCreate two objects with materials and textures assigned to each;\n```\n One texture to be baked to\n One texture with an alpha channel (optionally a normal map)\n```\n\nIn the shader editor, modify the material of the object with a transparency channel\n```\n Join the transparent textures' alpha into the alpha of the shader that is being used\n (optionally join the color of a normal map)\n```\n\nIn render properties, enable Selected to Active and use an appropriate ray distance\n```\n Finally bake.\n```\n\nResult:\nWhen baking combined or most channels, the transparent areas will assume the color as if it were completely opaque,\nWhen baking normals with transparency, the transparent areas will mix with the normal of the geometry that is being baked to the active selection.\nBoth outcomes are unfavorable when working with transparent cards/ribbons.\n\n[bugreport.blend](bugreport.blend)\n\nI packed the textures edited the project to make the issues that I am having more clear.\n\n{[F8286028](image.png), size=full}\nThere are now 3 overlapping objects with transparency.\nAfter baking normals or color, none of the colors or normals behind the transparent objects appear because the object appears to draw over top without transparency.\nThis example also shows that with full normal transparency, the normal will then be the geometry normal of the object rather than a flat normal or anything that is below the object.", "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", "Transfer data - vertex position by sampling UV\nAs we discussed on blender.chat, Blender would benefit from being able to transfer vertex positions from one object to another by sampling the UV's. Both the operator and the modifier\n\nHere is a mockup that might clarify what I mean\n\n\n\n", "Selected Objects render state (hidden in renders) causes baking of black images (also these are visible in renders after baking, setting is not as it was before)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0\nWorked: Cannot find any - tested back to 2.81\n\nIf rendering of the selected object is not enabled, then the baking will fail with a black image created.\nStrangely the rendering icon for this object will be automatically turned-on in the outliner - if you hover your mouse over.\nBaking will still fail - even though the icon now shows that rendering is enabled.\nTurning off render, then turning it back on again will fix the problem so that baking will now work.\n\nLoad the blend file attached (or use your own scene set-up for baking).\n[Bake selected to active has black image.blend](Bake_selected_to_active_has_black_image.blend)\nClick on Bake to confirm that the baking is successful.\n\nDisable render for the Selected object.\n\nClick on Bake again, and a black image will be created.\n\nNote that the Selected object still has rendering disabled.. Move your mouse into the Outliner above the render icon, and observe that rendering for the Selected object automatically becomes enabled.\n\nClick on Bake again and observe a black image is still created.\nDisable rendering for the Selected object, then enable it again.\nClick on Bake again and the baking will be successful.\n\n\nObservations:\n1) If rendering is disabled for the active object, then this error is shown.\n\n2) The bake duration is the same whether the rendering is enabled for the selected object or not. (Mine was taking a 2.5 minutes, and it took a long time to figure out what the problem was.)\n3) Saving the blend file and reloading fixes the problem - the state is persisted as render==enabled.", "Mesh modeling performance regressions\nList of performance issues that we would like to fix or investigate for 2.80:\n\n* Transforming vertices in edit mode on high poly meshes is slow, due to overhead of depsgraph, mesh updates and and batch creation. Verify if there is anything unexpected happening here.\n* BMesh to mesh conversion was happening all the time at some point, is this still the case? See check_rendered_viewport_visible, it now always happens when a 3D viewport is visible, and could be quite problematic for edit mode performance.\n* Verify if custom data is only being preserved through modifier stack when needed (vertex colors, vertex groups, UVs)\n* Manipulate modal callback performance may be problematic: #55458\n", "Smart Bake option for \"Bake Action\"\nProblem: \nCurrently we only support baking every Nth frame. Which sometimes results in more keys than desired, but \"cleaning curves\" doesn't do the job since most of the time you'd want your original key frames to be returned as a result not a \"cleaned up version\" of the curves.\n\nSolution: \nAdd an option to \"bake action\" named \"Smart Bake\", which will bake and only return key frames where the user has key framed already.\nIf the object baked has a constraint target to an other object. The constrain result should be considered in the same fashion it is done now, but only the keyframes that the user inputs in the object baked should be gotten as output.\n\n\nThis will retain the user's original poses or keys in place but depending how sparse the keyframes he originally has are, it will possibly break the interpolation between keys which is expected but should be stated in the tooltip.\n", "Vertex Selection Clipping Through Model\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.1\n\nWhen selecting vertices on an object, it will select the vertices on the face of the object and intermittently select all others behind as if in xray mode. \n\nGrab or scale icing vertices and pull.\n\n", "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).", "Bake artifacts with multimaterial in object\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nThen i try bake Ambient Occlusion in object with 2 or more assigned materials, Ambient Occlusiun bakes grey or black squares\n\n\n- Open attached file and bake ambient occlusion.\n[Bake_Test.blend](Bake_Test.blend)\n\n", "Shader Mix RGB node color burn and color dodge operations clamp incorrectly.\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\nShader Mix RGB node clamps the output color when using color burn and color dodge blending mode when it shouldn't\n\n\nWhen using the mix rgb node in the shader editor the color burn and color dodge blending modes both clamp the output of the node. Color burn clamps it to a 0 to 1 range while color dodge clamps it to a -infinity to 1 range, despite the factor being 0.\nColor dodge doesn't match EEVEE, which clamps the lower bound to 0 instead of -infinity.\n\nTest file:\n[Color_blend_test_file_HDR_input.blend](Color_blend_test_file_HDR_input.blend)\n\nThank you and have a great day!", "Cycles vertex baking seams\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 560 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.1.0\n\nThere are seams between the vertices when I try to bake lighting into vertex colors using Cycles, even when the vertices are merged.\n\nHere's my .blend file:\n[baking test.blend](baking_test.blend)", "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)" ]

[ "Baking time on diffuse - color only is highly impacted by vertex count on other objects\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0\n\nWhen trying to bake the diffuse only of an object, with color only (as to get an albedo map), the render time is very dependent on the surrounding geometry, even though it is not supposed to impact performances.\n\nThe scene is made of two rocks, the one called \"ToBake\", is to be baked, the other one has a lot of subdivision surfaces (turned down to 0 in viewport for ease of use, turned up to 5 in render for exemple).\nThe baking process takes a very long time with this highly subdivided rock (Usually ends up crashing if I press cancel by the way). If you disable it from render and viewport, the bake is almost instantaneous.\nThis looks like a possible optimization for albedo only baking in large scenes. [Volcanic Bake.blend](Volcanic_Bake.blend)\n\n\n" ]

[ "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "Move the transform info away from the header, into the viewport.\nCurrently, when you transform any item in Blender, we take over the header while the transform is happening:\n\n\n\nThis makes for a vey flashing/blinking UI, where both the header and the viewport gizmo disappears and re-appears in a jarring way. \n\nInstead, the header and viewport gizmos should stay untouched, and the transform info can be moved to the viewport along the bottom.", "Rigid body Bounciness parameter not functioning\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: 2.92 and version: 3.0.0 Alpha\nWorked: 2.83.13\n\nIn recent Blender versions the bounciness parameter of rigid bodies does nothing.\n\nOpen attached file, press space to start animation.\nOlder versions: ball bounces\nRecent versions: ball falls and immediately comes to an halt when it hits the surface of the cube.\n\n[Bounciness bug.blend](Bounciness_bug.blend)", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\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```", "Render issues when two VBD overlap if rendered with motion blur\nBroken: 3.2, 3.6\nWorked: 3.1\n\nRender issues when two VBD overlap if rendered with motion blur\n\nRender the attached file with and without motion blur. If you render them separatly they both render OK. Only when together it doesn't work.\n\n", "NLA: Action Track Hold Forward Inconsistency\nBug Report: #66946 (NLA strip unexpectedly auto-switching from Hold to Hold Forward)\n\n**Problem:** For the Action Track (non pushed action), extrapolation `None` and `Hold` is respected but `Hold_Forward` is not. It's a source of confusion. \n\n**Solution:** [Originally proposed by angavrilov]]. We treat extrapolation `Hold_Forward` as bounded on the left and infinite on the right.*FModifiers note:*It's important to note that the Action Track does not evaluate the same as normal strips which is [[https:*developer.blender.org/T66946#723602 |intentional](https:*developer.blender.org/T66946#724251). FModifiers will affect the track's boundaries so keyframes don't necessarily define the Action Track's evaluation bounds. So adding a default cyclic modifier to channels effectively makes the Action Track's evaluation bounds infinite. Even extrapolation `None` in this case appears to not work properly. This behavior is still intentional even though it appears broken. The user-side solution is to restrict the modifier's frame range. ", "Particle Texture influence broken when using two particle system on the same object\nOperating system: Ubuntu 18.04\nGraphics card: GeForce 970GTX\n\nBroken: 2.90.1\nWorked: Never (2.8+)\n\n\nWhen using two particles system on the same object with an influencing texture, one particle system has a wrong influence (e.g. Particle System shrink to quickly)\n\nBlend File: [particle_texture_bug.blend](particle_texture_bug.blend)\n\n0. Set the animation start and end to 100 - 200\n1. Create an Emitter and a Particle Object\n2. Add a Particle System to the Emitter and use the Particle Object for rendering\n3. Set the Start and End to 100 - 200\n4. Give the Particle System a Blend Texture that influences the size with \"Strand/Particle\" as Coordinates\n5. Add another System and Duplicate the previous one to get the exact same setting\n6. Change the Start and End of the new System to 0 - 100\n7. Bake all Dynamics\n8. Render Frame 199 and compare to rendering of 101. The particles in 199 are tiny in comparison (or invisible). They should look near identical\n\nOptional: \n9. Remove the 0-100 Particle and Redo Baking\n10. Frame 199 now has normal sized particles\n", "Hidden Particle paths draw solid [2.79 draws them half transparent]\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 15)\nWorked: (optional)\n\nComparison of particle hiding Blender 2.81 beta and 2.79. I wrote earlier that the particles are not hiding, and this is so fixed?\n\n", "Bug in particle system - missing particles representations\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.90.1\nWorked: potentially never, does also not work with 2.80\n\nWhen creating a particle system with `instance objects` and using more than ~15.000 particles, not all particles are represented with the instance object. The more particles the particle system contains, the more instance objects are missing. \nThe following images illustrate the problem.\n\nExample with 120 x 120 = 14.400 particles. All particles are represented with the instance object (in this case a cube) - except for the first particle at the top left corner. This particle is always missing - even for small particle systems. \n\n\n\nFor slightly bigger particle systems (e.g. 150 x 150 = 22500 particles), a few particles at random positions in the particle system do not contain an instance object (see the black dots)\n\n\n\nFor way bigger particle systems (e.g. 200 x 200 = 40000 particles) the last particles (i.e. the particles at the bottom right with the biggest indices are missing)\n\n\n\nThe presence of particles without instance objects also affects other particles when using specific nodes. For example, when using the `index` output of the `Particle Info Node` to compute a texture coordinate for each particle used to compute individual colors for the particles produced strange results.\n\nHere a working example for 120 x 120 particles (as reference)\n\n\n\nAnd here a non-working example for 200 x 200 particles (zoomed on the bottom-right corner)\n\n\n\nSide note: In all the examples, the particles are there, but the instance object representation is missing.\n\n\nExecute the following Python script within Blender's text editor. Or, when using Jacques Lucke's VSCode Plugin: execute the script (again) when Blender is already opened (since it does not work with a restricted context)\n\n[particle_sys.py](particle_sys.py)\n\nBlend file with the an incorrect particle system\n\n[particle_sys.blend](particle_sys.blend)\n", "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.", "Rigid-Bodies Colliding Improperly\n[Basic Setup with bug 2.blend](Basic_Setup_with_bug_2.blend)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.81 (sub 13)\n\nSome of the Rigid-Body objects in the included .blend go flying when animation is played, as though they were intersecting each other, but they are not.\n\nOpen the included .blend.\nPlay animation. The two objects named \"Suspension.FL will go flying off in opposite directions.", "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", "Show Emitter toggle still hides object after Particle System has been deleted.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.92.0 Alpha\nWorked: version: \n- 2.92.0 Alpha\n- 2.91.0 Release\n\nWhen you delete a particle system with show emitter unchecked under Viewport Display the object stays hidden. You have to re-add the particle system and check Show Emitter.\n\n- Add Particle System to default cube.\n- Uncheck Show Emitter under Viewport Display\n- Delete Particle System. \n\n", "Rigid Body Constraints break when copying its empty object\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nCopying a rigid body constraint via CTRL+C / CTRL+V breaks it permanently (you have to remove and re-add the constraint to make it work again).\n\n- Create a simple rigid body constraint setup. You can use this file to start: [bug_rigidbodyconstraints_copy.blend](bug_rigidbodyconstraints_copy.blend)\n- Select all objects\n- CTRL+C to copy\n- CTRL+V to paste\n- Move the new objects a bit to avoid clipping, and play the animation - the active object just falls down\n- Fixed by removing and manually re-creating the constraint on the Empty.001 object\n\nThis does not happen when using SHIFT+D to duplicate.\n\n---\n\nSeems like the dependency graph loses the connections between the constraint and the rigid body objects after copying.\n\nWorking (before copy): \n\nBroken (after copy): " ]

[ "found work around for compound assembly issues,\nwhen assembling a compound body inside a function the objects physics bound was incorrect, also the objects physics bound (child) was left where the object was when assembled,\n\na work around was to do\n\n(calculations for assembling)\n\nassembling function (center of mass etc)\n\nfunction(create mesh libNew and parent children and assign mass of \"centroid\")\n\nfor all parts in assembly\nremoveParent()\ndisableRigidBody()\nsuspendPhysics()\nsetParent(centroid libNew host)\n\nhowever after doing this, once the object is removed from the assembly with \"removeParent\" it still had the complex compound shape bounds in physics,\n\nso\n\nfor removed objects:\nadd new copy of object\nset properties\nend old object\n\nworks around all issues.", "GE objects set as compound parents leave collision hull behind after child obejct ended\n**Category**: Physics\n\n\n%%%Child objects in a compound object group (parent set to compound) will leave their collision hull behind when the object has been 'ended' either via logic or Python. The attached picture shows when an object is created in space- when the child object is 'ended' it leaves its collision hull. Subsequent spawns of the child object interact with the 'orphaned' collison hull.\n\nThere exists re-instancing the collision hull but this is not for compound objects.\n\nIn the test file, T spawns the parent, G spawns a box below into a compound group. By pressing G multiple times you will see a build up of (child) collision hulls.\n\nNon-compound parent/ child groups do not have this problem.\n\nMany thanks for your time\n\nPaul\n\nOS:Win 7\nBlender: 2.58, 2.59, 2.60a\nGFX: GeForce 460 GTX%%%" ]

[ "Error in Message of Linked data is Missing\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6 beta\n\nThe message about the lost linked data mentions Proxies that have been removed since 3.0. Perhaps it should be replaced with \"Library Overrides\"? The error is not only in the pop-up window, but also in the Info editor\n\n\n\nOpen this file\n[bandit_anim_2.blend](attachment)\n\n", "Blender 3.5.1 + Mac + Metal + Crash\nOperating system: MONTEREY 12.6.3\nGraphics card: AMD Radeon Pro 5500 XT 8 GB\n\nBroken: Blender 3.5.1\nWorked: Blender 3.4.1\n\nBlender 3.4.1 will render a given scene with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" in 1 min 58 sec\n\nBlender 3.5 and 3.5.1 will crash on the same scene set on \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" - \nIt has to be run with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"CP\" and now takes 5 min 53 sec.\n\nI have lost computing power with the latest versions.\n\nJust run the file with GPU BACKEND turned on and \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\"\n\nI could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send\n\n", "NLA: Support for Merge Strips\n**Preface:**\nI know this isn't the place for feature requests. However I plan on implementing this myself soon. This is more of a heads up and acts a way to get feedback before or while I'm working on it. Maybe I'm overlooking something or maybe the idea can be developed further. People can discuss problems and improvements here instead of within the patch comments itself. That way the important discussion can remain here for easier reference.\n\nEdit: Diff: [D8867: Feature: NLA Merge Strips](D8867)\n\n**Problem:**\nFor the animation layer workflow, the only way to combine strips into a single strip is to use the Bake Operator. However, it will always bake all active NLA strips to a single full replace strip. Effectively, this is a \"Merge All\" operator. There is no way to merge a selected set of strips. \n", "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```", "OpenGL error in console\nOperating system: Windows 10, 11\nGraphics card: 6700 XT, 6800 XT, driver 23.7.2 \n\nBroken: 4.0.0, ecb3262bf04, main, 08.08.2023\nWorked: no information.\n\nFirst of all it's better to run Blender with USD built with this fix 2550 since it fixes a lot of other OpenGL errors in console.\n\nThere is an error in console `Runtime Error: in HgiGLPostPendingGLErrors at line 91 of C:\\GPUOpen\\RPRHydraRenderBlenderAddon\\USD\\pxr\\imaging\\hgiGL\\diagnostic.cpp -- GL error: invalid framebuffer operation, reported from __cdecl pxrInternal_v0_23__pxrReserved__::HgiGLBuffer::~HgiGLBuffer(void)` If you select `Render Engine = Hydra Storm` and run Viewport Shading and stop it.\n\nBut if you start Blender with `--debug-gpu` flag you will an error in console `ERROR (gpu.debug): : GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9` and above error with `HgiGLBuffer::~HgiGLBuffer` won't appear anymore.\n\nI put some `debug::check_gl_error` in `detect_mip_render_workaround` and one of them returns `GL_INVALID_FRAMEBUFFER_OPERATION` right after `glClear(GL_COLOR_BUFFER_BIT);` and one more error `GL_INVALID_VALUE` after `glGetTexImage`.\n\nAlso `glCheckFramebufferStatus(GL_FRAMEBUFFER)` returns `GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT`.\n\nI tried to get rid of `HgiGLBuffer::~HgiGLBuffer` error via calling `glGetError`. There are only 2 places worked for me: \n1. ViewportEngine::~ViewportEngine;\n2. End of the `detect_mip_render_workaround`.\n\nDefault startup. \nFirst:\n1. Select `Render Engine = Hydra Storm`\n2. Start Viewport Shading\n3. Stop Viewport Shading\n4. Look in the console\n\nSecond:\n1. Start Blender with `--debug-gpu` flag\n2. Look in the console\n\n", "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\n\n", "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)", "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", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "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. ", "Curve \"solidify\" modifier glitch\nOperating system: Windows 7\nGraphics card: GT750M\n\nBroken: 2.80, 2019-02-28\nWorked:\n\nWhen applying a \"Solidify\" modifier to a bezier curve shape (or imported SVG), it creates random height vector points, creating strange triangles. This can be fixed by simply selecting the errored vector point then selecting one of the transform value (in my case it was Y) in the panel and either pushing enter (keeping the same value) or unselecting the vector point.\n\n\nAttached blend file with imported SVG.\n\n", "UI: Gizmo's tooltips appear after pressing\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 2.92.0 Alpha, branch: master\nWorked: none\n\nClicking on button, or pressing and holding - prevents the tooltips from appearing.\nBut it doesn't work that way for gizmos. This leads to an annoying flickering of tooltips.\n\nSo, you hover and press on the gizmo - a tooltip appears;\nyou move, stop and release - tooltip appears again.\n[#83589.mp4](T83589.mp4)", "Adjusting multiple properties at the same time doesn't work for all property types\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.90.1\n\nMost properties in blender can be changed for all selected objects by holding ALT while changing it. However, this doesn't work for all properties. For instance, the 'Rig Type' property in the Rigify add-on doesn't work. We can make it work by right click and selecting 'Copy to selected' but it should be possible with the ALT shortcut for consistency.\n\n**Steps to reproduce**\nWhile in Pose Mode select multiple bones\ngo into Bone Properties -> Rigify Type -> Rig type\ntry to change the Rig Type for all of them by holding ALT", "Remove BKE_layer_collection_resync_forbid and BKE_layer_collection_resync_allow\nThese can be removed after each area has been checked and optimized to use the new structure (synced_ensure)\n\nRecently ceb0e7fcea was done and added a use for resync_forbid. This makes this ticket perhaps irrelevant?", "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```" ]

[ "macOS: addons fail to import due to Python 3.9 libraries linking against libz.dylib\nOperating system: MacOs 11.2\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: MacOs 2.93\nWorked: 2.92 and Win10 2.93\n\nAddon Rigify won't load with 2.93 MacOs version.\nRun `import binascii` in Blender.\n\nOr\n```\nPython: Traceback (most recent call last):\n File \"/Applications/Blender.app/Contents/Resources/2.93/scripts/startup/bl_operators/userpref.py\", line 609, in execute\n import zipfile\n File \"/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/zipfile.py\", line 6, in <module>\n import binascii\nImportError: dlopen(/Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so, 2): Library not loaded: libz.1.dylib\n Referenced from: /Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n Reason: unsafe use of relative rpath libz.1.dylib in /Applications/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so with restricted binary\n````\nWin10 version works fine.\nThanks!\n\nPiotr\n", "Animation Nodes ; macOS Big Sur ; python 3.9.0\nHi \nI have a MacBook Pro with macOS Big Sur 11.2.1 \nI have installed Python 3.9.0\nI have installed the Blender Alpha 2.93 and when I try to install this add-on Animation Nodes+Extra Nodes for Blender 2.93 - Mac OS appears this window:\n```\nTraceback (most recent call last):\nFile Applications Blender.app/Contents/Respurces/2.93/scripts/modules/addon_utils.py line 351 in enable mod = import _module _name\n File Applications Blender.app/Contents/Respurces/2.93/scripts/addons/animation_nodes/init_py line 90 in <m raise Exception message\nException:\nThe animation nodes add-on depends on the numpy library.\nUnfortunately the blender built you are using does not have this library.\nYou can either install bumpy manually or use another Blender version that comes with lumpy (eg the newest official blender release)\n```\nPlease; How can I solve this problem? Thanks" ]

[ "\"Make Default\" option not registering file explorer Thumbnails on Microsoft Store Blender\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.63\n\nBroken: version: 3.5.1\n\nWhen installing Blender 3.5 from the official Microsoft Store, attempting to \"Make Default\" installation to get Thumbnails to show on file explorer does not work, even after restarting the OS and refreshing file explorer.\n\n\n1. Download Blender 3.5 from the Microsoft Store\n2. Load Blender > Settings > System > \"Make Default\"\n3. Open any .blend with a camera and save it\n3. Open Windows File Explorer > go to the .blend path > Right Click > View > Large Icons\nOR press Ctrl + Shift + 1\n4. Click F5 to Refresh directory view\n\n", "Importing a keymap with a default name makes a non deletable copy\nBroken: version: 3.2.1\n\nAfter importing a keymap configuration with the name \"Blender\" it created a copy of the default setting that is impossible to remove from the UI at least.\n\n\n\n\n\nImport a keymap setting with a default name\n\n\n**Fix**\nDelete keymap configuration from the user folder directly \n\n> \\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\scripts\\presets\\keyconfig\n\n\n", "There is no undo on linked data for the very few editable properties of linked data-blocks\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nWhen you __link an armature from other file__, then go to pose mode and __hide a bone__ and __undo the hide operation__, nothing happens.\n\n1) Create __a file with a simple armature__ (at least one bone).\n2) Open another project and __link the armature from before__.\n3) __Enter pose mode__.\n4) __Hide__ a bone.\n5) __Undo__ the hide operation. -> **nothing happens**\n\nI have added two files to reproduce the bug:\n(in the example I linked a whole collection and created a proxy to enter the __pose mode__ **but nothing changes if you link just the armature**)\n- `main.blend` - contains a proxy of the armature from __bone.blend__\n- `bone.blend` - contains just an armature used by __main.blend__\n\n[hide undo bug.zip](hide_undo_bug.zip)", "\"Repeat History\" unavailable after \"Undo\"\nCurrently undo clears the operator history,\nideally this should instead keep these actions in sync with the undo history.\n", "Asset System: Remove asset handle\n`AssetHandle` is temporary design. It was used to abstract away the fact that all asset data is just stored in a file entry (`FileDirEntry`). It was also used as a type that could populate an RNA collection for the asset-view template. Asset handle was also a volatile type, that was tied to the file browser caching and could be freed by it at any time (although not asynchronously at least).\nMeanwhile, `AssetRepresentation` was introduced, to hold all asset information, managed by the asset system storage. See Back_End#Asset_Representation.\n\nNote that loading asset representations still uses the file browser backend (either directly in the Asset Browser or via the `AssetList` API).\n\n### TODOs\n\n- [ ] Store previews in `AssetRepresentation`\n- [ ] Store preview icon-id in `AssetRepresentation`\n- [ ] Remove `ED_asset_handle` API\n- [ ] Replace all context setting asset handles with asset representations\n- [x] Remove `CTX_wm_asset_handle()`\n- [ ] Use asset representations for populating the asset-view RNA collections, or remove the asset view template entirely (to be replaced by asset shelves? #104831)\n- [x] Add `AssetRepresentation` RNA type\n- [x] Switch UI scripts to use asset representations (asset browser + ?)\n- [x] Switch Pose Library to use asset representations\n- [ ] Remove `AssetHandle` RNA\n- [ ] Communicate 4.0 API breakage\n\n", "Outliner selection not working correctly after undoing object deletion\nOperating system: Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (LLVM 13.0.1, DRM 2.50, 5.17.15-1-MANJARO) AMD 4.5 (Core Profile) Mesa 22.1.2\n\nBroken: 2.91.2, 3.2.0, version: 3.3.0 Alpha\nWorked: prior to b077de086e\n\nAn object that is linked in another collection can usually be removed from just that collection by using unlink, while using delete removes it from both collections. But if you delete the object and undo, unlink does delete the object in both collections. \nRenaming the cube or creating a new object \"breaks\" the cubes apart so they can be selected/unlinked individually again.\n\nIn the default scene,\n- create a new collection\n- in the outliner, ctrl-drag the default cube object to that collection to link it\n- delete the cube\n- undo\n- in the outliner, it is now impossible to select the cube in the new collection separately and using unlink will delete both cubes", "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", "Python API - Modal operator losing context.area after focus is stolen\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77\n\n\nBroken: version: 2.80 (sub 58)\nWorked: (optional)\n\n\nWhen focus is stolen (for example, when the user uses Ctrl+S and the file browser dialog pops up), a running modal operator will lose the context.area and it never returns even after the dialog has been closed.\n\nRun the attached modal operator from a VIEW_3D area, without pressing RMB or Escape (which will cancel the operator), bring up the Save File dialog. Watch the console output- it will change from VIEW_3D to \"no context area\" because the dialog has focus and the area is no longer valid, but when you Cancel the file save operation, you would expect the context.area to return but it never does. You must cancel the operator and restart it.[modal_area_focus_bug.py](modal_area_focus_bug.py)\n\n", "UI Lists Filtering can have non-visible items active (e.g. after deletion) which lets you act on non-visible items\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83 (sub 17)\n\nWhen using any UI list filtering, if you press the \"-\" several times, at some point you'll jump out of the list and start deleting things from the list without seeing them:\n\na short video to show more in detail\n[2020-05-15 08-44-35.mov](2020-05-15_08-44-35.mov)\n\nUse any list, that has more than a few elements,\nfilter it, \nstart deleting, \nthe active highlighting disappears at some point, \nkeep deleting\nfind out that you deleted things outside of the list that was filtered.\n\nOR\n[#76853.blend](T76853.blend)\n- Open File\n- Cube has 2 vertex groups [\"apples\" and \"oranges\"]\n- \"oranges\" is selected/active\n- \"oranges\" is not visible though because a filter for \"app\" is applied on the list\n- \"thus only \"apples\" is visible\n- hit the {key -} button\n- \"oranges\" will be deleted [without user knowing]\n", "VSE unkeyed transforms in preview persist in cache\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 3.3.0 Alpha\nWorked: never\n\nVSE unkeyed transforms in preview persist in cache.\nIf transforms occur on a property that has an fcurve already (but no keyframe is actually created on that frame), this transform will remain in the cache for that frame.\nThis does not get invalidated on timeline scrubbing / frame change.\n\n(this report was split from #98015 (VSE strip transforms do not animate correctly and persist after clearing the animation) since multiple issues came up in that report)\n\n[VSE_keyframing.blend](VSE_keyframing.blend)\n\n- open .blend\n- create a keyframes for rotation on frame 1\n- go to frame 10\n- rotate in the `Preview` again and confirm the rotation (but dont create a keyframe)\n- scrub the timeline\n- since this change on frame 10 was not keyed, it should vanish, but it doesnt, it remains in the cache\n- note: when the strip in the `Sequencer` view gets moved, the issue goes away (assume the whole cache gets invalidated then)\n\n\n", "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", "Textfield disables input permanently if hidden while editing\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: <2.80\n\nIf a textbox that is currently being used is hidden, then all input gets permanently disabled, staying in typing mode of a non existing textbox. There is also a memory leak of a few bytes reported in the console when I close blender in this state.\nThis bug can lead to data loss since there is no way to recover, so it's basically like a crash.\n\n1. Make the blender window maximized.\n2. Open the right panel in the viewport and drag it open until it covers as much of the window as possible.\n3. go into text editing of the x location of the default cube\n4. use Meta+Right Arrow or some similar shortcut which resizes the window.\n5. now if the window is small enough the panel with the textbox is hidden, but the mouse is still a textcursor and all input is blocked.", "Pie Menus initiated by tweak events will disable the mouse button used in the tweak event. Works fine for regular menus, operators.\nWindows 10\ngeForce GTXTitan\n\nBroken: blender-2.77.0-git.94e18c5-AMD64\nWorked: (optional)\n\nI've set up some UI shortcuts that use 'tweak' events (or directional gestures) for various pie menus, regular menus, and operators. This work fine for regular menus and operators. After calling a pie, however, the tweak button defined in the input editor (left, right, middle, action) becomes unusable. \n\n1) Open User Prefs, select the add-ons tab, and enable Official Pie menu addon\n2) Select the 'Input' tab in User Prefs, and in the keymap filter (set to name), type the the word 'pie' without quotes\n3) The first filtered pie is 'Frames'. change the hotkey as follows: \nClick the event mapping dropdown (its set to keyboard by default), and change to Tweak. two new options appear next to it: 'Left', and 'Any'.\nChange the type of event, or leave it as 'Left' \nChange 'Any' to a direction.\nSelect a modifier key such as Shift\n\n4) go to the 3d view and execute the new shortcut you set up. The playback options should appear in the pie menu but are not selectable. Hitting the escape key will get out of the pie, but the defined tweak button is not usable.\n\nNOTE: If you use the default right click select, you can still place the cursor, but can't trigger the shortcut again. If left click select is set, then normal tweak events like moving selected objects are also not possible.\n\nNOTE: Toggling Object/Edit mode will make the button usable again.", "Window title shows unsaved indicator while loading\nOperating system: Linux-4.15.0-45-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: May 18 2021, hash: `1f9eb7e2c6`\n\nWhile Blender loads a file, the window title shows the unsaved indicator: `Blender* [/path/to/blend]`.\n\n- Create a .blend file which takes long to load. A simple example involves creating huge amounts of geometry with Array modifier, then applying the modifier.\n- Open the startup file (ctrl+N) so the window title is cleared (makes it easier to see what changes, but not required).\n- Open the .blend you created earlier, you will see the unsaved indicator in the title until loading finished.\n\n", "Sculpting: Ctrl+S reverts recent progress. \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0,\nBroken too: b67423f806\n\nWhen saving with ctrl+S the last changes applied to sculpt with \"grab\" brush gets reverted. This should be observed by reopening the file. \n\n- Have a sculpt with dynamic topology. Disable dynamic topology for the next step.\n- Move a part of the mesh with the grab brush.\n- Save your last progress. \n- Reopen the file using file browser. All changes done with the grab brush will be undone.\n\n\n\n[face sculpt broken.blend](face_sculpt_broken.blend)\n\nThanks, have a great day and stay healthy!" ]

[ "Blender File View looses buttons and input field\nOperating system:Windows\nGraphics card:\n\nBroken: 2.82a\n\n\nUI breaks on export if name is being edited in outliner\n\nIn the startup file:\n1. Open Blender File View (e.g. `File` > `Save As`)\n2. Move your mouse away from the new window, start editing name of anything in outliner [previous window], dont confirm it though\n3. Move you mouse back to the Blender File View, press `Save As` --> button and input file-input-field will be gone...\n\n" ]

[ "Subdivided surface preserves mesh UVs and vertex colors when not needed\nThis code causes UVs and vertex colors to always be preserved through the modifier stack.\n\n```\n /* this wasn't in 2.63 and is disabled for 2.64 because it gives problems with\n * weight paint mode when there are modifiers applied, needs further investigation,\n * see replies to r50969, Campbell */\n#if 0\n CustomData_set_only_copy(&dm->loopData, mask->lmask);\n CustomData_set_only_copy(&dm->polyData, mask->pmask);\n#endif\n```\n\nFor simple solid shading these are not needed, and `ED_view3d_datamask` should take care of requesting them when needed, taking up memory and CPU time.\n\nHowever, there is currently an issue where switching shading modes does not reevaluate the dependency graph to add these data layers, so just re-enabling this code is not enough to fix this. See also #63595 (Generated texture coordinates missing when switching from solid to rendered mode).", "Causing other objects to be named .001 doesn't immediately update the Viewport Name Display\nI found this in 3.0.0 but happens the same in 3.1.0.\n\nWhen you turn on Viewport Name Display:\n\n\nAnd then you rename a new object the same as object that was already in the scene:\n\n\nThe name of the original doesn't update until you somehow \"touch\" the object by moving it, entering Edit Mode etc.\n\nIt doesn't get fixed by simply affecting something else.\n\nIn the .blend you need to select the object with name \"Plane.001\" and rename it to \"Plane\" then the object on the left stays named as Plane until you somehow affect it.\n[Bug-ViewportDisplayName.blend](Bug-ViewportDisplayName.blend)", "Overlay: Edit-Mode: Anti-Alliasing not working with constructive modifiers\n```\nOperating system: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce 610M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n```\n\nthe bug is really intresting so... when you add mirror modifier to object.. and u enter edit mode and u select face or edges etc... the AA goes crazy it is so pixelised like even worse than tottaly without AA.\n\n\n\n\n\n\n\n", "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)", "Mirror modifier with mirror object updates slowly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.83 (sub 15)\nWorked: Never (2.79+)\n\nAdding a Mirror Modifier and using an empty or another object to mirror across, causes slow viewport performance.\n\n[#76102.blend](T76102.blend)\n\n- Open file\n- Move Suzanne - Notice performance\n- Remove Mirror Object from mirror modifier\n- Move Suzanne - Performance much better\n\nYou can apply subdiv modifier, it shouldn't have an effect.", "Unable to get object to stay hidden while new mesh tool is active.\nWindows 10, 1060\n\nBroken: 2.80 master (also reproduced in a month-old daily build, so not new behavior).\n\nIf you have an active tool like Add Cylinder going, and you hide another object using the eye icon in the outliner, then as soon as you touch the cylinder parameters, the hidden object becomes unhidden.\n\n1) From the default scene, Add a Cylinder to the scene and expand the tool properties in the lower left of the 3dview.\n2) Because the cylinder is hidden inside the cube, we can't easily see the effect of changing the tool parameters, so go to the outliner and click the eyeball icon associated with the cube to hide it in the viewport.\n3) Change any parameter in the cylinder tool properties pop-up in the 3dview. The cube reappears and the eyeball indicates it is no longer hidden.\n\nBasically any changes made to the Outliner visibility icons gets reverted as soon as you change any active tool property, (at least for the Cylinder tool). This at least unexpected behavior.", "CMD terminal stays open after opening blender\nOperating system: Windows-10-10.0.25247-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\n\nI'm not sure why it';s happening but it's not happening for 3.3 version\n\n\n\n", "Adding new hook while in Edit mode breaks when trying to undo/redo the operator\nWin7 (32bit)\n\nBroken: 2.78a\n\n\n- Add Path from Curve menu, add new Armature\n- Assign Bone to control point as Hook\n- Blank Hook modifier appears along with real one\n\nScreencast: [screencast0001-0250.mp4](screencast0001-0250.mp4)\n", "PyAPI: Unregistering DATA_PT_modifiers causes wrong panels (such as contraints) to appear in modifier UI\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.83\n\nUnregistering DATA_PT_modifiers causes wrong panels to appear in the modifier UI. \n\nProblem 1: Constraints appear in the modifier UI.\nProblem 2: Grease pencil modifiers appear on other object types. To be more specific, only the main panels appear, not subpanels. \n\nThese problems didn't occur with the old modifier stack. I use this in my Modifier List addon.\n\nRelated: T77541\n\n1. Open the attached file\n2. Run the simple script to unregister DATA_PT_modifiers\n3. Select the grease pencil object\n4. Select the mesh object\n5. Grease pencil modifiers should appear on the mesh\n6. Add some constraints to the mesh\n7. Switch to modifiers tab\n8. The modifiers should appear there (however, now the grease pencil modifiers should no longer be there)\n\n[unregister DATA_PT_modifiers grease pencil bug.blend](unregister_DATA_PT_modifiers_grease_pencil_bug.blend)", "Renaming Vertex Group Breaks Modifier's Vertex Group Reference\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: Never (2.79+)\n\nChanging name of the vertex group breaks modifier's vertex group reference.\nSame issue has been reported 6 years ago: [#41876](T41876). If it's still a \"known limitation\" or \"to do\", it might be a good idea to tag it with new/proper labels.\n\n1- Launch default Blender.\n2- Create a vertex group to the cube and assign a face.\n3- Create a modifier with vertex group option (Mask modifier for example) and select the vertex group that we just created.\n4- Rename the vertex group and notice that breaks the modifier referencing to that vertex group.\n\n[#74726.blend](T74726.blend)\n", "\"Add Modifier\" menu gets cut off inside narrow windows\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nWhen the properties window is floated the modifier selection menu gets cut off\n\nShift click-drag the corner of an area type to float the properties area. \nGo to modifiers select a modifier menu is cut off.\n\n", "Mesh cache Modifier cant unselect Flip axis once selected \nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nin Mesh cache Modifier i cant unselect X,Y,Z Flip axis once selected ..it can only be interchanged\n\n\n\n", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "Make the “redo” panel also appear in the tool settings tab\nWe should make the 'redo' panel also appear in the Tool Settings tab in Properties:\n\n", "Hook modifier after Vertex Weight Mix modifier pulls incorrect vertices\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: \n3.5.0 Alpha\n3.4.0\n3.2.0\n2.93.8\n2.83.20\n(all version of blender, so far as I tried)\n\nWorked: None\n\nHook modifier after Vertex Weight Mix modifier pulls incorrect vertices.[HookAfterVWM.blend](HookAfterVWM.blend)\nIn other words, Vertex Weight Mix modifier breaks vertex index for Hook modifier.\n\n- Add a plane mesh and subdivide\n- Select some of vertices and \"Hook to new object\"\n- (At this time, an empty and a hook pull vertices correctly)\n- Add empty vertex group \"Group\" to plane\n- Add a VertexWeightMix modifier *before* the Hook modifier and set \"Group\" to Vertex Group A\n- The hook pulls incorrect vertices\n\n" ]

[ "Drivers applied to modifier values don't get deleted when the modifier is applied or deleted\nOperating system: Mac OS\n\nBroken: 2.80, 1c5860407068, master, 2019-05-05\n\nWhen using a driver to drive a modifier value, deleting the modifier or applying it doesn't delete the driver.\nSo issues start occurring after this when you add the same modifier to the object and it automatically has this driver.\nOr you duplicate the object and the driver is also duplicated, which means adding the same modifier to the duplicate also automatically has a driver.\nThis also leads to an issue with appending objects to other blend files. Since, when the driver is driven by other objects, appending this object will also append the objects the driver is linked to. Causing many more objects to be appended, without any real idea of how they are linked since the modifier that connects them was deleted.\n\n[ModifiersAndDriversBug.blend](ModifiersAndDriversBug.blend)\nGrab the empty and move it, it should drive the thickness value of the solidify modifier.\nDelete the solidify modifier on the plane.\nGrab the empty again and move it (the plane shouldn't change, which is expected).\nDuplicate this plane.\nAdd a solidify modifier back to the duplicated plane (it's thickness value will automatically have a driver attached).\nGrab the empty again and move it (Nothing should happen as the drivers dependencies need to be updated for it to work).\nUpdate the driver dependencies (It should work like before).\nDelete the duplicate and save the file.\nOpen a new blender file and append the plane object from the saved file (the empty will also be appended, as it is linked to the driver)." ]

[ "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)", "Texture nodes CPU evaluation design\nFor #54656, we need CPU evaluation of a subset of shader nodes that form the texture nodes.\n\nPrototype under development in [D15160](D15160).\n\n**Overview**\n\nThe plan is to make this a subset of geometry nodes that can be evaluated using the same mechanisms. Texture nodes can be though of as a geometry nodes field, and when evaluated in the context of geometry nodes they are.\n\nHowever they can also be evaluated outside of a geometry node tree. In particular, they can be evaluated on:\n* Geometry domains vertex, edge, face, corner, for geometry nodes and baking of textures to attributes. Possibly also sculpting and vertex color painting.\n* Geometry surface, for image texture baking and painting.\n* 2D or 3D space not attached to any geometry. For brushes, 2D image painting, physics effectors.\n\nTo support the last two cases in the geometry nodes infrastructure (but not the geometry node evaluation itself), a new field context named `TextureFieldContext` is added. This represents a continuous texture space, that may be mapped to a geometry surface or not. It has one domain, `ATTR_DOMAIN_TEXTURE`.\n\n**Compilation and Execution**\n\nThe texture nodes compilaton and evaluation mechanism uses much of the same infrastructure as geometry nodes, but is separate to be usable in different contexts. It's meant to be possible to execute texture nodes efficiently many times, for example paint brushes are multi-threaded and each thread may execute the nodes multiple times. This is unlike geometry nodes where multiple threads may cooperate to execute nodes once.\n\nThe current compilation mechanism is as follows:\n* Multi-function nodes are compiled into a `MFProcedure`, which bundles multiple multi-functions into one for execution. Geometry nodes do not currently use this mechanism, but it is designed for this type of evaluation. This is rather inefficient currently for individual points, but should get more efficient when evaluated in big batches.\n* Remaining nodes are input nodes, and execute `geometry_node_execute` as part of compilation, which then outputs fields and values. The execution context for these nodes is limited, unlike geometry nodes there is no geometry, object or depsgraph.\n* For evaluation, fields are converted into `GVArray` using the provided geometry.\n\nWe could consider making geometry available and to the compilation and caching the compilation per geometry, though it's not clear there will be nodes that need this. Alternatively we may cache just the `GVArray` per geometry.\n\n**Fields**\n\nInput nodes return fields, which are then turned into `GVArray` for evaluation. For the texture domain, this is a virtual array that interpolates attributes. There may be some possibility here to share code with data transfer field nodes, or nodes that distribute points and curves on surfaces and inherit attributes.\n\nShader nodes need additional fields that are not currently in geometry nodes:\n* Generated / Rest Position / Orco\n* Normal, taking into account face smooth flag and custom normals\n* UV maps (planned to become available as float2 attributes)\n* Active render UV map and color layer\n* Tangent\n* Pointiness (Cavity)\n* Random Per Island\n\nIt's unclear to me what the best way to specify these as fields is, if we should add additional builtin atttribute names or `GeometryFieldInput`. Some of these like Pointiness would also make sense to cache as attributes, and make available to external renderers.\n\nOne constraint is that it must be efficient to evaluate only a small subset of the domain. For many field inputs and operations this works, but there are some that will compute a data array for the entire domain. This can be enforced by just not making such nodes available as texture nodes, or caching the data array on the geometry.\n\nFor sculpt and paint modes, there is a question if and how we can make all these attributes available. The challenge is that it has different mesh data structures (bmesh and multires grids), which are not supported by geometry nodes. Additionally, recomputing for example tangents and pointiness as the geometry changes during a brush stroke would be inefficient, especially if it's for the entire mesh and not just the edited subset.\n\n**Batched Processing**\n\nFields and multi-functions are not optimized for evaluating one point at a time, there is too much overhead. That means we want to process texture evaluations in batches, and all (non-legacy) code that uses textures should be refactored.\n\nFor geometry nodes, modifiers and 2D brushes this is most likely straightforward. However for 3D brushes, particles and effectors it will be more complicated.\n\nThere is currently a mechanism to single evaluations possible while code is being converted. However this is rather inefficient, with quite a bit of overhead in `MFProcedure` execution. It may be possible to do some optimizations there for legacy code that we may not be able to easily convert to batches.\n\n**Node Graph Transforms**\n\nTo support sockets like Image datablocks, and to automatically insert Texture Coordinate or UV Map nodes for textures coordinate sockets, we need to transform the node graph. The texture node layering will also need to do significant node graph transformations. In order to share code with Cycles and other external engines, it may be best to do this as part of node tree localization.\n\n**Relation to Other Node Systems**\n\nThere are many node evaluation systems in Blender, and the question is if we can somehow share this implementation with anything else. I don't think the CPU evaluation can be directly shared, but will make the old texture nodes evaluation obsolete at least. The GPU implementation can probably be largely shared with shader nodes, and that implementation could be refactored to use DerivedNodeTree for consistency and to simplify that code.", "bevel node is making entire material appear rough even when roughness == 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Alpha\n\nbevel node is making entire material appear rough even when roughness == 0\n\n[bevel breaks roughness.blend](bevel_breaks_roughness.blend)\n\nroughness == 0, bevel node attached\n\n\nroughness== 0, bevel node not attached.\n\n\nroughness ==0, bevel node attached but samples turned up crazy high\n\n\n", "Node Group Texture slot problem\nOperating system: Windows 10\nGraphics card: gtx1060\n\nBroken: 2.9\nWorked: N/A\n\nIn the Texture Paint mode, when all textures are inside a node group, if you change brush radius it jumps to the top texture slot every time.\n\n- Open attached file\n- In the property editor, select `test` texure slot\n- Change brush radius.\nThe top texture slot (`test`) was selected automatically\n[Node Group Texture Slot Problem.blend](Node_Group_Texture_Slot_Problem.blend)", "Texture stencil \"Reset Transform\" doesn't work properly\n**System information**\nLinux Mint 17.3 (x86_64)\nLinux Mint 18 (x86_64)\nWindows 8.1 64bit\n\nNvidia Geforce GT640\nNvidia Geforce 820M\n\nBroken: 2.78, 2.77a\n\nIn texture paint mode (wether in 3D or 2D), the \"Reset Transform\" under \"Texture\" doesn't work once you clicked on the \"Reset Transform\" under \"Texture Mask\".\n\n\n\n - Open this .blend file [stencil Reset transform bug.blend](stencil_Reset_transform_bug.blend)\n\n - Click on the upper \"Reset transform\"\n\n - it works.\n\n - revert file\n\n - click on the lower reset transform, then on the upper one\n\n - it doesn't work.", "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?)", "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", "Texture Paint: Wrong active Texture Slot\nOperating system:win10\nGraphics card:GTX 740m\n\nBroken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, build date: 2021-02-25, 09:31:14, hash: 02948a2cab\n\nVpqy7BmMKaA\n\n- Open attached file or:\n - Go to \"texture painting mode\" (in default workspace)･\n - Create 2 base color textures\n - Open Shader Editor\n- In the Shader Editor, select non -active texture (\"Material Base Color 2\")\n- in the View 3D, paint texture\n- Nothing happen in visual.\n- The other texture slot is changed instead of current active texture.\n[tex_slot_problem.blend](tex_slot_problem.blend)\n\n", "Bump node results are affected by camera angle in Cycles\nOperating system: Linux-5.6.10-3-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GT 525M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.132\n\nBroken: version: 2.83 (sub 17)\nWorked: Never (2.80+)\n\nBump node result is affected by camera angle in Cycles, seems to work well in Eevee\n\nOpen Blender\nGo to Shader Editor\nCreate a Bump Node and connect its normal output to the normal input of Principled Shader(or any shader)\n[BumpBug.blend](BumpBug.blend)\n\n", "Viewer Node from Compositor is not updated in Camera's Background Image\nOperating system: Arch Linux\n\nBroken: 3.2.2\nWorked: never\n\nThe viewer node result from compositor is not propagated in the 3D viewport as a camera background image when selected. This might be really useful in many cases. I often use compositor to edit input videos and I want to adjust the 3D scene according to the video. Especially with the grease pencil, there might be a case when the animator wants to draw an animation over an existing one. It is really strange that the option to use the node is there but it's unusable, related to #73188.\n\n**Possible problems**\nRecursion mentioned in #73182. Might be resolved by overriding the order when the node is used in the camera or letting the user change the order somewhere.\n\n**Workaround**\nExport the composited result in a video and then use as a background image or hit F12 after every frame and use the render result in the background image.\n\n1. Create a setup in compositor that changes over time\n2. Connect the result to Viewer node\n3. Use Viewer node as camera background image in the 3D scene\n4. Move to another frame - no change in the background image\n\nIncluded the project file with simple texture animation and two workspaces. One with split screen where both compositor and 3D view are visible. When the compositor is hidden, the background image is not changed at all. When it's visible, it's updated but from the previous frame or state. It seems like the camera first takes the compositor result as the background and then the new compositing takes place. Yes, I understand that it's the design of these stages but this is still a trick to somehow make it work, the image does not update at all without the compositor window being active as shown in the second workspace.\n\n[viewerNodeInCamera.blend](viewerNodeInCamera.blend)", "World aov output nodes dont work unless background node's colour is >= 0.0001\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.3 Release Candidate\nWorked: Unknown\n\nWorld aov output nodes dont work unless background node's colour is >= 0.0001\n\n\n1. Open attached file\n2. go to the compositor of 'scene' and render still image\n3. the custom world aov is blank\n4. go to scene.001 and render\n5. the world aov now outputs correctly\n\nBoth scene's are identical, the only difference is scene.001's world background node's colour is set to 0.0001. The custom AOV is of type Value rather than colour. This is problematic because it breaks compositor setups that check for values > 0 etc.\n\n", "Generic Input in a Group Node displays as Grayscale, when it is in fact neutral.\nSolution: \n\n\n\nIn the example above, the only change would be that the socket next to the Input would be empty instead of gray. This would fix the wrong impression that it's a Grayscale input - it's not, it's neutral as Sergey stated.", "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", "Image syncing between Editors via active image canvas \nThis is related to [D16811](D16811) and similar improvements.\n\n## Issue\n\nThe purpose of this design is to avoid unintended syncing of images between the image editor, 3D viewport and shader editor.\nThe syncing is currently tied to the last active image texture node in the material. But since this is triggered with selection it leads to many accidents.\nThis has lead users to avoid using the syncing all together by pinning images and not using the \"Material\" texture selection in the 3D viewport.\n\n## Solution\n\nThe goal is to make the syncing an explicit action by\n- Using the active texture paint slot/canvas, instead of the last active image texture node\n- Indicating the active image canvas on any image texture node that uses it with an icon (Eye icon for example)\n- Changing the active image canvas in the node editor via an explicit action (Clicking the icon)\n- For faster use, add a shortcut (like double clicking on an image texture node) to make the image canvas active\n- For reference, add a context menu entry with the used shortcut\n\n\n\nThis also affects other areas where currently the active image texture node is being used:\n\n- General Image editor display\n- 3D viewport solid shading with color set to Texture\n- Baking target texture\n- UV editing image aspect ratio\n\nThis wouldn't contradict current cases of icons in the top-right corner.\n\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" ]

[ "Using viewernode as an image texture causes shader or compositor to fail intermittently\nOperating system: Linux-5.8.0-38-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.91.2\n\nSet up a scene with compositor tree and a viewer node connected to the scene input. Add a material to the default cube, connect an image texture node to the surface output. Select \"Viewer Node\" as the image texture. Press render. Result will probably be a purple cube. This is perfectly understandable, however what's *not* understandable (or at least not desireable) is that this will often still happen even if the viewer node currently contains a valid image. Say you just rendered something into the compositor and you want to preview it as a texture on an object. You can do this with the viewer node, and then tweak masks or compositor settings and see the texture update on the model in realtime. However, if you press render again, *even if the viewernode textured model is offscreen*, this stops working. In fact, it even breaks the viewer node itself, such that trying to view the viewer node contents in the image editor shows solid purple.\n\nExpected behaviour: contents of viewer node (and probably \"render result\" as well) should be cached before rendering so blender can use them during the shading process without getting confused. Would allow better editing of objects textured by renders. This already seems to kind of work intermittently, so I don't really consider this a feature request.\n", "Geometry Nodes: Image Texture nodes do not support Render Result\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.14\n\nBroken: version: 3.5.1.\nWorked: Never.\n\nSee Screen\n\n\n1. Open *.blend file.\n2. Press key F12 (render Image).\n3. See in GN nodes what whis image unavailable.\n\n" ]

[ "Support socket icons in the Group Sockets Input/Output type enum\n{[F10225900](image.png), size=full} (crude mockup)\n\nThe issue is that the socket colors are not icons, but maybe they should/could.", "Principled shader clearcoat roughness inconsistent change from 0.0177 to 0.0178.\nCPU: AMD 860K\nRAM: 8GB\nGFX: nVidia 960 GTX, 4 GB\nOS: Xubuntu 16.04\nDrivers: 375.82 from nvidia-375 (open source), installed from \"Additional Drivers\" section of settings window.\nBlender: 2.79 2017-09-11 10:43, Hash = 5bd8ac9abfa\n\nOn the left, the plane has a principled shader. It only has a clear coat on it. No SSS, diffuse is RGB 0,0,0, no sheen, and no normal/bump mapping. The \"Clearcoat Roughness\" setting is at 0.0177 (and of course displays it at 0.018 unless you click on it).\n\n\nHowever, the right plane is exactly the same, except the \"Clearcoat Roughness\" setting is at 0.0178, 0.0001 more. As you can see in the above picture, it's completely different, not just slightly different.\n\nHere is the blend file:\n[cleacoat_rough_bug.blend](cleacoat_rough_bug.blend)\n\nAny questions, I'll respond as quickly as I can.", "Eevee: math wrap and floor, AMD Driver precision issues\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.1 27.20.21003.1028\n\nBroken: version: 2.92.0\nBlender 2.83 LTS has same problem\n\nMath and Vector Wrap give different results for Eevee and Cycles, also doesn't swap min max, when max is less than min\n\n\n**More info**\nThis is important for an upcoming Shader Nodes patch that relies on wrap operation\nalso for shader setups that rely on this\n\nother people tested this, the problem seems to appear only on AMD Windows\n\n\nWhen Using -3 as Min for wrap, and 3 as max, some values give different results in Eevee than in Cycles\nFloor operation is probably the cause of this\nthis node setup \n\n\nCycles\n\n\nEevee\n\n\n[eevee_math_wrap_different_from_cycles.blend](eevee_math_wrap_different_from_cycles.blend)\n\n", "Vertex Paint ➔ Paint menu ➔ Smooth Vertex Colors could be improved\nOperating system: Windows 10 Pro 64-bit\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nTested: Blender 2.81 Alpha, September 18, 14:29:45 - b962aca8003d\nWorked: never\n\nVertex Paint ➔ Paint menu ➔ Smooth Vertex Colors tool does not smooth other than direct loop neighbors.\n\n1. Divide the default cube a few times (apply if subdivision is done with modifier).\n2. Enter Vertex Paint mode.\n3. Paint an area with black.\n4. Apply Paint menu ➔ Smooth Vertex Colors.\n5. The vertex paint is not smoothed other than direct loop neighbors.\n\n\nHere is some clarification as the descriptions above are not very clear (I work with vertex colors very regularly and still came out confused by reading this post).\n\n- The Smooth Vertex Colors command will have visible results *if* it is run on vertex colors that have been applied per-face (by first selecting the desired faces in Edit mode, and then filling them with colors in Vertex color mode with the face filter enabled). Think of these as \"harsh\" vertex colors. When such vcols exist, then the smooth operation will indeed smooth out the vcol data so that the harsh separation between painted faces will be smoothed out, blending it with the surrounding faces.\n- But if the command is run on vcol data that has been painted on using the paint brush or on vcol generated by the \"dirty vertex colors\" command then nothing will happen as the vcols will already be point-based.\n\nTherefore there is no bug here, just some very confusing naming of the command and a lack of clarity when the command is run but nothing happens. For any user working with painted-on vertex colors, it will indeed seem like nothing is happening at all since one would expect some sort of global smoothing to be applied.\n\nPart of the confusion is also coming from the fact that this command sits just below \"Dirty Vertex Colors\" in the menu, which generates smooth, per-vertex vcol data. Meaning that for a user exploring vcol mode by trying one feature after the next, \"smooth vertex colors\" will almost always feel like it is doing nothing at all (unless the user first applied some vcol using face masking, which is extremely unlikely).\n\nIf anything the tooltip and/or the menu entry could be changed for clarity :\n\n- The menu item name could be renamed from \"Smooth vertex colors\" to \"Smooth harsh per-face vertex colors\"\n- The tooltip could be changed from \"Smooth colors across vertices\" to \"Smooth colors across vertices. Only operates on harsh, per-face vertex colors\".\n\nAnd then of course it would be great to have a new feature altogether to blur vcols globally, similarly to what the blur brush does.", "Add overlay to visualize full weight values in weight paint mode\nTake the following case in which some vertices are weighted in full 1.0 (RED), some have a weight of 0.0 (Blue) and some are weighted very close to full (0.9) and some are weighted very close to zero (0.1)\n\n\nIn this case it is very hard to visualize which vertices are weighted 0.0 or 1.0 or which are just very close but might have a different influence.\n\nFor that reason we have a **Zero Weights** overlay that uses black to indicate 0.0 weights\n\n\nWith this overlay enabled it is quite easy to distinguish between 0.0 or just very close to 0.0\n\n\nWhat's missing is the same logic but for values of 1.0 where an overlay would show the **Full Weights** in white, 0.0 in black and the rest in the typical colors\n\n\n*Note: The above screenshot assumes the implementation of another [related task ](https:*developer.blender.org/T93147)//", "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.", "Instanced objects get their viewport display color ignored (by design)\nBroken: 022ad416702d\nWorked: 022ad416702d~\n\nInstanced objects get their viewport display color ignored.\n\nThis is by design, as you can see in 022ad41670:\n```\nDRW: use object color from instancer\n\nOtherwise it's impossible to set the color of instanced library objects.\nFollows convention of instancer controlling draw options.\n```\n\n[viewport-display.blend](viewport-display.blend)\n\n**My issues with the design**\nThe original commit seems like a workaround for the fact that the override system is not implemented yet.\nI find this too arbitrary and I would favour the flexibility of having a per-object granular viewport display object color instead (i.e., revert the mentioned commit).", "Color Picker 'Square (SV + H)' changes Hue while editing SV\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.4.0\n\nWhile using one of the theme color widgets, if change the saturation, the hue will change\n[blender_FLKonKBXBK.mp4](blender_FLKonKBXBK.mp4)\n\n- In {nav Blender Preferences > Interface > Editors} change `Color Picker type` to `Square (SV + H)`\n- In {nav Blender Preferences > Theme} click any color widget\n- Choose a `Hue` between blue and cyan\n- Change SV values in the square interface", "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", "Color management look contrasts apply the wrong gamma when the display device is set to None\nOperating system: window 11\nGraphics card: RTX 2060s\n\nBroken: 3.1 stable, 3.0 stable\n\nWhen the display device is set to None, applying a look contrast results in what looks like a double gamma correction. This doesn't happen when the Display device is set to XYZ.\n \n1. set the display device to None\n2. set the look contrast to any other setting than None or Medium", "UI: Show invalid cache as stripped lines\nAt the moment we use a faded color to indicate that a cache is invalid. The difference is a too subtle at times, even when users customize their theme colors.\n\nThe proposal here is to draw the invalid caches with a darker stripped diagonal line (see image). In this case I used the original color with a 50% value.\n\nIn this mockup you see the Simulation cache (pink) as invalid, and the Cloth cache (blue) as valid.\n\n\n\n_Design done with [Pablo Vazquez](pablovazquez)._", "Color picker value not working as expected\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha, 2.92 doesn't work either.\nWorked: 2.91 official release\n\nWhen I enter 0, 0 , 0. 5 in the HSV-values expecting a 50% grey ,but the grey I get is way too bright. It's more like 70% grey. The value slider also indicate this brighter value and not half way the black and white gradient as you'd expect it.\nThe saturation value exhibits the same kind of problem a 0, 0.5, 0.5 HSV-value is not as saturated as one would expect.\n\nfirst noticed this in the 2.92 official release and and checked, as advised, the latest version (the above mentioned 2.93 alpha) to see if it was resolved. The last time the color picker worked as expected was in 2.91.\n\nMakes inputing specific colors values pretty much a nightmare.\n\nopen blender, change color pretty much anywhere you can change color. \n\nattached screenshots:\n\n\n\n\n\n\nThanks, have a nice day. (Pablo made me say it! 'cause apparently humans are checking XD)\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.", "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.", "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!" ]

[ "SV + H color picker doesn't keep hue constant\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: 2.90.0 Beta\n\nColor picker automaticaly change Hue\n\n- Change color picker type to SV + H\n- In shader editor click on base color (could be different color property)\n- Set hue to number that is not period of 1/6\n- Swipe with mouse through color field\nHue will change (it may be just a little bit)\n\n\n[GgRWXrlPZW.mp4](GgRWXrlPZW.mp4)", "Manipulating saturation of colors (e.g via HSV or RGB curves, but also within color picker) shifts HUE\nOperating system: Linux-4.15.0-58-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\nBroken: version: 2.81 (sub 8)\n\nTo desaturate a color you plug a HSV or RGB curves node. But the more you light up the color the more hue shifts. I've tested it with eyedropper in blender and gimp. Dragging the right side control of the RGB curves node (making darker) doesn't shift hue.\nIf i'm doing something wrong, then what's a correct way to desaturate a color without hue shifting?\n\nOpen up the attached file\nFire the render\nFrom the Picker node pick the color from the render view\nCompare the hues on both nodes\n\n\n[color_hue_shift_bug.blend](color_hue_shift_bug.blend)", "Changing value affects hue & saturation in 3D view gradient color sliders\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.90 (sub 0)\nAlso Broken on 2.82 official release\n\n\nValue Slider on the Right of the Color Wheel (or on the HSL) is affecting the hue and saturation with weird behavior.\nWhen I slide the 'value' of white to black on the right of the color wheel or on the 'value' for the HSL it begins affecting the Hue and Saturation while the user only changes the Value by sliding it up and down (do it over and over again to really see it get weird).\n\n- Navigate to Blender Preferences - Themes Menu - 3D View - Theme Space - Gradient Colors - Gradient High/Off & Gradient Low \n- Select a color on the wheel.\n- Play with the 'Value' sliders on the right side of Color Wheel and on the HSL. The more you slide up and down the more the hue and saturation seem to change.\n\nLet me know if I can help with any more info.\n\nThanks and Best Regards,\n\nblanchsb" ]

[ "Gesture selection does not deselect on nothing if collection is hidden\nOperating system: Linux-6.4.8-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.8-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-57b0db63e1)\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nThis is an inconsistency in the selection behavior.\nIf you select on nothing, it will deselect all objects in the viewport and the outliner. This is the case for click selection and selection tools/operators.\n\nBut if selected objects are hidden, they are not affected by this with selection tools (gesture selections such as box & lasso). Selected objects and collections stay selected in the outliner.\nThe expected behavior is that gesture selection and single click selection have the same effect on hidden objects and collections.\n\n1. Create two collections each with an object in it\n2. Select a collection and its object in the outlliner\n3. Select on empty space (Notice how the object and collection are deselected)\n4. Repeat 1 & 2\n5. Do a lasso/box selection on empty space (Notice how the outliner selection isn't cleared)\n\n", "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)", "Selection problem on new 'add modifier' menu\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nin new 'add modifier menu' which introduced in Blender 4.0 if you hover your mouse over a main menu items like 'edit' to open edit's submenu then move your mouse diagonally from top right to bottom left on main menu, other main menu items not highlighting or selecting.\nI attach a video take look at it, in this video I move my mouse from edit(while it's open) to physics , non of menus open, not even physics which I stop mouse there no matter how much time my mouse stay there it will not open.\nalso I moved my mouse from edit to generate and also menu did not open.\n\n", "Semitransparent grease pencil covers wireframe. Bug or limitation?\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nit looks like this \n\n[untitled3.blend](untitled3.blend)\nAnd it is difficuilt sometimes to work with wireframe and GP-sketch when I don`t see vertices\n", "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", "Outliner doesnt preserve selected or active state when clicking mesh twice (objectmode -> editmode -> objectmode)\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 3)\nWorked: (optional)\n\nExport selected object export empty file if object have only mesh selected in outliner.\n\nProbably this is more UX bug than exporters problem.\nCreate default object: Cube or Suzanne.\nExpand Object tree and select mesh in outliner. Blender will switch to mesh edit mode.\nClick one more time to mesh in outliner. BLender will switch to Object editing mode.\nViusually Object still looks selected because mesh still highligted but in 3D viewport object is unselected.\nNow try export as OBJ, enable Export Selected only.\nBlender correctly will export empty OBJ file because there is no any object actually selected.\n\n\n\nThis UX bug quite confusing, and i catch it almost every time i need export files.\n", "Workbench: Cull before batch creation during viewport animation rendering\n\n## Current Situation\n\nWhen drawing an object (eg sending draw calls to the GPU) the object boundary sphere is tested against the active view). When the test fails the object isn't send to the GPU. Before this happens the GPUBatches were already generated.\n\nWhen doing animation playback this could lead to the situation that the GPU Batches are calculated, but not used.\n\n## Target Situation\n\nWhen using the Overlay engine/Workbench engine we could test the objects to the default view (e.g viewport). When this fails we could skip this object at all. This feature would be disabled when the shadows are turned on and only enabled when doing an image/animation render.\n\nA consistent framerate is more important to animators then having some frames faster.\n", "Can't Animate Texture Mapping Offset For Particle Hair\nWindow 7 64bit 8gb\nnvidia 660\n\nBroken: 2.72 RC\nWorked: I thought this was possible all the way back into the 2.4 series.\n\nAdd a single keyframe to particle texture mapping coordinates.\nMove to another frame and type a new number in the *Offset* mapping field and it will jump back to the number of the first keyframe.\nIn this state there is no way to animate the*Offset*. Even if I insert the same value at the new time location and edit the value in the graph editor the system still refuses to use the *Offset*information for the particle system hair density.\n\nOpen the Attached BLEND file and type a new number in the *X Offset* field.\nThe system refuses to accept the input and resets to the keyframe value.\n\nNOTE: This seems to only be a problem in the *Offset* and *Size* properties for Mapping. You will also see in the BLEND file that I have successfully keyframed the R value of the RGB without experiencing the same problem.\n\n[27_sequin_star_curtain_1a.blend](27_sequin_star_curtain_1a.blend)\n", "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n", "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", "Alt-Drag (multi-editing) fails for HSV color buttons\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.83 (sub 1)\nSeems to be a long-lasting issue, as even Blender 2.81a shows the same behaviour.\n\nPretty much the title. \nTrying to assign an object color through the Object Properties tab (Viewport Display > Color) to multiple Objects doesn't work, neither by picking the Color on the Color Wheel, nor by moving the HSV sliders, while Alt-Clicking. Only the last selected Object will update.\nHowever:\n\n\n - If sliders are set to RGB, editing them will correctly affect all selected Objects.\n - The Alpha slider, which is shared between all three Color Wheel modes, works as intended and affects all selected Objects.\n\n\nFrom the Info console I've noticed a tuple is set everytime a Color is picked from the Color Wheel, but doesn't show anything when using the HSV Sliders.\nMoving the the RGB and Alpha sliders correctly sets each Object's property to the selected value.\n\n\n\n\n - Open Blender, default startup file\n\n - Add>Mesh - Select any kind of Mesh Object (have at least 2 items in the scene, or more)\n\n - Go to the Shading Panel in the top right and Select \"Object\" down the Color section, to see Object Colors in the viewport\n\n - Press A to select All Objects, or alternatively, select them one by one by Shift+Right Click\n\n - Go to Object Properties > Viewport Display > Color\n\n - Hold ALT either while clicking on the Color Wheel or while moving the HSV Sliders. Only the last selected Object will update.\n\n\n\n\n - While holding ALT, try moving the Alpha slider. All selected Object will update.\n\n - In the Color Wheel, select the RGB tab. While holding ALT, try moving the R, G or B slider. All selected Object will update.\n\n\n\n\nHere's a quick demonstration:\n\n[2020-01-20_22-01-14.mp4](2020-01-20_22-01-14.mp4)\n\nAnd the Info panel readings:\n[2020-01-20_22-02-46.mp4](2020-01-20_22-02-46.mp4)\n", "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", "Regression - depth buffer drawing go bonkers when selecting object on second collection\nOperating system: Linux-5.8.18-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0\nWorked: 2.90\n\nAfter drawing simple 3d lines with python script - depth buffer is drawn incorrectly when deselecting object that is placed on **second collection**. \nScript itself is very generic - from blender gpu docs examples. It worked ok in all previous blender versions.\n\n[Linde_draw_depth_bug.mp4](Linde_draw_depth_bug.mp4)\n\n- run script - it will draw 2 lines in 3d view for 8 seconds\n- if you select/deselect box which is placed on second layer/collection you will see those lines are drawn incorrectly on object deselect.\n\n[3d_view_lines_bug.blend](3d_view_lines_bug.blend)\n\n\n\n", "Grease Pencil keyframes not updating after GPencilFrames.copy()\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\n\nCopied keyframes do not update with Grease Pencil Layer\n\n- Create a new document with the 2D Animation template\n- Draw a shape \n- (Note by @iss) It may be necessary to make new keyframe at later frame, see video\n- Run the below script in the Text Editor\n# Run the \"Grease Pencil Test Script\" command from the Draw Menu\n\nThe Grease Pencil data isn't updating in the Viewport unless the playhead is going backwards, a keyframe is deleted, or if the keyframes are added to a new `GPencil` object. I believe the issue is because the keyframes generated with `GPencilFrames.copy` are missing the layer update for some reason. If I use `GPencilFrames.new()` and copy every attribute manually, this issue does not happen. In the below code, I am updating all of the data I know to be possible.\n\n```\nimport bpy\n\ndef main(context):\n active_layer = context.active_gpencil_layer\n frames = active_layer.frames\n start_frame = frames[0]\n frame_numbers = [frame.frame_number for frame in frames]\n\n for frame in range(start_frame.frame_number, context.scene.frame_end+1):\n if frame in frame_numbers:\n continue\n new_frame = frames.copy(start_frame)\n for i,start_stroke in enumerate(start_frame.strokes):\n new_stroke = new_frame.strokes[i]\n for p,start_pt in enumerate(start_stroke.points):\n new_pt = new_stroke.points[p]\n new_pt.co[0] = start_pt.co[0]+(frame*0.5)\n new_frame.frame_number = frame\n\n gpencil = context.object\n gpencil.data.layers.update()\n for l in gpencil.data.layers:\n l.frames.update()\n for f in l.frames:\n f.strokes.update()\n for s in f.strokes:\n s.points.update()\n\n gpencil.data.update_tag()\n context.view_layer.depsgraph.update()\n context.view_layer.update()\n bpy.ops.gpencil.recalc_geometry()\n\nclass GPENCIL_OT_simple_operator(bpy.types.Operator):\n bl_idname = \"gpencil.simple_operator\"\n bl_label = \"Grease Pencil Test Script\"\n\n def execute(self, context):\n main(context)\n return {'FINISHED'}\n\ndef draw(self, context):\n self.layout.operator(GPENCIL_OT_simple_operator.bl_idname)\n\ndef register():\n bpy.utils.register_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.append(draw)\n\ndef unregister():\n bpy.utils.unregister_class(GPENCIL_OT_simple_operator)\n bpy.types.VIEW3D_MT_draw_gpencil.remove(draw)\n\nif __name__ == \"__main__\":\n register()\n```\n\nPlease disregard the step where I put the GP Object into Edit mode & create a new keyframe. This step is not necessary to seeing the `GPencilFrames.copy` bug.\n[duplicated_frame.mp4](duplicated_frame.mp4)\n\nNot sure if the bug will show consistently, but here is the scene file:\n[Grease_Pencil_Data_Bug.blend](Grease_Pencil_Data_Bug.blend)", "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" ]

[ "Selection problem with grease pencil\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nSelection problem with a grease pencil in edit mode and sculpt mode\n\n\n[New Poses.blend](New_Poses.blend)\n\n- Open file\n- Select one of circles in GP layers\n- Go to edit mode\n- Select all points\n- Move to frame 10\n\nCircle points doesn't change position, only shape - displayed incorrectly\n\n- Go to object mode\n- Go to edit mode\n\nCircle points has changed position and shape\n\nIn 30 seconds you will see that I go from pose mode to sculpt mode and you can see the problem that happens [https:*youtu.be/LKXkCtKRDOA?t=932 ](https:*youtu.be/LKXkCtKRDOA?t=932)\n\nSill image explaining the problem.\n\n\nGif demonstrating the problem.\n\n\nThis was tested in the official release and in 2.82 and the 2.83 the hour of this report.\n[system-info.txt](system-info.txt)\n\nThe next 15 seconds shows the problem with selections as well [https:*youtu.be/AhZGuuLzV1k?t=316 ](https:*youtu.be/AhZGuuLzV1k?t=316)\n\nIf you have the patience to watch from the above link till 7:51 I will tell you why this workflow is good and how the sculpting selection/ ghosting issue is a problem.\n\nPlease again if there is a problem with what I've explained I will do my best to try and clarify just ask.\n\nThanks again \n\nAd\n\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", "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)", "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", "crash freeze with ellie_animation.blend file\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.23\n\nBroken: version: 3.2.0\nv3.0.1 also broken for this file\n\nwhen opening the demo file ellie_animation.blend the Blender crash freezes with spinning beachball.\n\nopen the demo file ellie_animation.blend \nBlender has spinning beachball\nmacOS Activity Monitor built-in utility shows Blender (Not responding). \nI have to force quit blender.\n\nother blender files I have work ok. other blender demo files work ok.", "Blender 3.5.1 + Mac + Metal + Crash\nOperating system: MONTEREY 12.6.3\nGraphics card: AMD Radeon Pro 5500 XT 8 GB\n\nBroken: Blender 3.5.1\nWorked: Blender 3.4.1\n\nBlender 3.4.1 will render a given scene with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" in 1 min 58 sec\n\nBlender 3.5 and 3.5.1 will crash on the same scene set on \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" - \nIt has to be run with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"CP\" and now takes 5 min 53 sec.\n\nI have lost computing power with the latest versions.\n\nJust run the file with GPU BACKEND turned on and \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\"\n\nI could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send\n\n", "Crash while baking the Line Art modifier\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: 7c2dc5183d03\n\n\n\nI get regular crashes when baking Line Art modifier in relatively complicated geometries. \n\nI can't provide my project file. I am hoping that the crash log will give insight into this bug.\n\n", "Crash 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 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", "Serious problems with visibility when linking a character\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3\n\n\nwhen linking a collection containing a character model, rig, etc., oddities occur with the visibility of the armature: when the overlays are turned off/ on, the armature is not displayed until some event occurs (this bug applies to the file where the model is located). undo ignores hiding bones (scene with linked and override character) for clarity, two animation files will be attached. in both, sometimes both of these bugs occur, while it is absolutely unpredictable\n[2022-09-16 02-20-35.mp4](2022-09-16_02-20-35.mp4)\n\n[broken_7.zip](broken_7.zip)\n\nfile with character in broken_7/stalker/\nfiles with animation in broken_7/3d_projects/tests/animation/\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "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", "Crash while switching to edit mode with EEVEE + Geometry Nodes\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.0.0\n\nWhen switching to edit mode in while the viewport's set to render it crashes (see attached video)\n[blender crash 2021-12-17 21-54-00.mp4](blender_crash_2021-12-17_21-54-00.mp4)\n\n1 load the attached file\n2 switch to rendered view in the viewport\n3 switch to edit vertex mode\n4 that's a crash!\n\n[transitions_001_blender3.blend](transitions_001_blender3.blend)", "Crash after executing the script\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1 Release Candidate\n\nApplication crashes when clicking on the script run button\n\n1/ launch Blender\n2/ click on \"Scripting\" tab; click \"New\"\n3/ paste the following chatgpt generated script and run it: \n```\nimport bpy\nfrom math import sqrt, sin, cos\n\n# Define the vertices of the tetrahedrons\nvertices1 = [\n (1, 1, 1),\n (-1, -1, 1),\n (-1, 1, -1),\n (1, -1, -1)\n]\n\nvertices2 = [\n (1, -1, -1),\n (-1, 1, -1),\n (-1, -1, 1),\n (1, 1, 1)\n]\n\n# Define the faces of the tetrahedrons\nfaces1 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\nfaces2 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\n# Create new meshes and objects\nmesh1 = bpy.data.meshes.new(\"Tetrahedron1\")\nobj1 = bpy.data.objects.new(\"Tetrahedron1\", mesh1)\n\nmesh2 = bpy.data.meshes.new(\"Tetrahedron2\")\nobj2 = bpy.data.objects.new(\"Tetrahedron2\", mesh2)\n\n# Set the object locations and scene context\nobj1.location = (-2, 0, 0)\nbpy.context.scene.collection.objects.link(obj1)\n\nobj2.location = (2, 0, 0)\nbpy.context.scene.collection.objects.link(obj2)\n\n# Create the vertices and faces of the meshes\nmesh1.from_pydata(vertices1, [], faces1)\nmesh1.update(calc_edges=True)\n\nmesh2.from_pydata(vertices2, [], faces2)\nmesh2.update(calc_edges=True)\n\n# Hinge the tetrahedrons together by one edge\nedge1 = mesh1.edges[0]\nedge2 = mesh2.edges[2]\n\nbpy.ops.object.select_all(action='DESELECT')\nobj1.select_set(True)\nobj2.select_set(True)\n\nbpy.context.view_layer.objects.active = obj2\nbpy.ops.object.mode_set(mode='EDIT')\nbpy.ops.mesh.select_all(action='DESELECT')\nedge2.select = True\nbpy.ops.mesh.edge_face_add()\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Add an armature to the tetrahedrons\nbpy.ops.object.armature_add()\narmature = bpy.context.object\narmature.name = \"HingeArmature\"\narmature.location = (0, 0, 0)\n\n# Add bones to the armature\nbpy.ops.object.mode_set(mode='EDIT')\nbone1 = armature.data.edit_bones.new('Bone1')\nbone1.head = (0, 0, 0)\nbone1.tail = (-2, 0, 0)\nbone1.use_deform = False\n\nbone2 = armature.data.edit_bones.new('Bone2')\nbone2.head = (0, 0, 0)\nbone2.tail = (2, 0, 0)\nbone2.use_deform = False\n\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Parent the tetrahedrons to the armature\nobj1.parent = armature\nobj1.parent_type = 'BONE'\nobj1.parent_bone = 'Bone1'\n\nobj2.parent = armature\nobj2.parent_type = 'BONE'\nobj2.parent_bone = 'Bone2'\n\n# Animate the hinge\nframes = 30\n\nfor frame in range(frames):\n bpy.context.scene.frame_set(frame)\n\n angle = frame / frames * 2 * 3.14159265\n\n bone1.tail = (-2 * cos(angle), 0, -2 * sin(angle))\n bone2.tail = (2 * cos(angle), 0, 2 * sin(angle))\n\n bone1.keyframe_insert(data_path='tail')\n bone2.keyframe_insert(data_path='tail')\n```", "QuadriFlow Remesh Crash\nOperating system:iMac (Retina 5K, 27-inch, 2020)\nGraphics card:AMD Radeon Pro 5700 8 GB\nRam: 96 GB 2133 MHz DDR4\n\nBroken: 3.6.0, 3.5.0 Beta and 3.2.1\nWorked: N/A\n\n\nDear all\n\nI found that the QuadriFlow Remesh will crash when i try to remesh (40K) from also most 900K faces. I tested on 30K and so on. The only sucessful try is down to 500 faces.\n\n\nHere is the model for your reference which is modified after 3D print addon (cannot QuadriFlow if not) from the orignal question below and i also record a 1:30min video for reference as well ( YR6oPpNbKis )\n\nModel file: view?usp=share_link\n\nPlease check. Many thanks\n\nOrignal Question: mesh-doesnt-follow-the-armature", "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" ]

[ "Triangle mesh BGE character mode crash\nMS Windows 7 Home Premium 64-bit SP1\nNVIDIA GeForce GT 555M\n\n\nBroken: 2.71 Release Candidate 2 a19c1be\n\nAlthough it's been broken since at least 2.67.1 r57348\n\nWhen object's collision bounds is set to triangle mesh and physics mode is set to character, blender will crash when object hits another.\n\nChange object collision bounds to triangle mesh\nStart game engine\n\n[local_add_move_bug.blend](local_add_move_bug.blend)\n(File is from another bug)" ]

[ "Killed particle's position is reset to the initial position when rendered\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nI am encountering a strange particle behavior.\nWhen a particle collides with a plane where collision is enabled and \"kill particles\" is checked, the particle position seems to be reset to its initial position. This can not be observed in the viewport. This unexpected position reset is observed only when rendering the images.\nAs shown in this video:\n[0001-0050.mp4](0001-0050.mp4)\n\n[debug.blend](debug.blend)\nBake particle simulation and render images. You will get the same video as shown above.\n", "Animation (e.g. driver) jumps to another socket, when i move input socket in the node group.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.3.0\n\nOpen file, try to move Scale input socket upper. Driver will jump to Scale socket\n[driver jumps.blend](driver_jumps.blend)\n\n[2022-09-24_22-56-08.mp4](2022-09-24_22-56-08.mp4)\n", "Cycles: Cycles Alpha Representation is incorrect on some PNG files when loaded from disk compared to packed in the file\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple `M1` Pro Apple 4.1 Metal - 83\n\nBroken versions: \n3.3\n3.4\n3.5.0 Alpha\nWorked: 3.2\n\nA certain mix node setup that I found in the Spring demo file results in extremely bright outputs. I could only reproduce the issue in Blender 3.3 and higher. The issue isn't there in Blender 3.2 or lower. I could also only reproduce this issue in Cycles.\n\n\n\n1. Download the attached .zip file, extract it, and open it. It's an extremely simplified version of the `Spring` demo file from the Blender foundation.\n2. Enter Cycles rendered viewport. Notice how the hand is really bright. This is caused by the output of the `mix node` found in the material `MAT_spring.hands` on the hands.\n3. Test the EEVEE rendered viewport. Notice the issue isn't there. Test Blender 3.2 or older and notice the issue isn't there.\n\n[Spring Bright Hand Issue.zip](Spring_Bright_Hand_Issue.zip)\n\nExtra note: If the image texture that's causing the issue is packed into the .blend file, and the file is re-opened, then the issue goes away.", "Render artefacts with GPU / motion blur\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.80.02\n\nBroken: version: 2.91.0 Alpha + official releases and master from build bot.\nWorked: none that I tried so far\n\nI get weird rendering artefacts where some buckets render different than others. This only seems to happen when:\nRendering with motion blur AND rendering with GPU AND rendering under a Linux OS AND the shutter position is set to \"start\" or \"center on frame\". \"end of frame\" renders fine.\nIt's completely weird as it doesn't happen under Win10 (at least in my case). I completely reduced a production scene to the point where some basic geometry and particles with a sky shader show the problem.\n\n- Open the attached blend file:\n[SHOT060_MPS_v33.blend](SHOT060_MPS_v33.blend)\n- Press F12 to render\n- If you're under Windows (and maybe Mac) or render with CPU you should be fine. Otherwise you should get something like this:\n\n- Switch the motion blur position from \"center on frame\" to \"end on frame\" and render again:\n\nEverything fine\n- Now switch back to \"center on frame\" and switch the render engine to CPU and render again:\n\nFine again.\n\nSo it only affects Linux, \"start or center on frame\" and GPU rendering.\n\nP.S.: Might be somehow related to T76792 although I can't reproduce his problems. But the description sounds similar and he's on Linux, too.\n\n", "simply moving the render window is terribly slow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nwith more complex scenes (such as for example blenderman file 57e5084f0fcf294119c5055c) once you render an image and you have eevee in render preview mode, moving the render window becomes very slow, probably because eevee returns to refreshing the previw render without needing it.\n\nsee the video\n\n[GRAbwindow.mp4](GRAbwindow.mp4)\n", "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", "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", "Child Of vertex group fails when controled by Particle System\nWin10 64bit\n\nBroken: 2.79\n\nChild Of constraint fails on rotation from PS\n\nOpen file, play animation on every layer\n\nFirst layer: *Empty* with *Child Of* constraint is controled by Plane's transform animation -> works OK\nSecond layer: *Empties* with *Child Of* are controled by Plane's *Particle System* (via *Explode*) -> Location is maintained, but **rotation is non-synchronized**\nThird layer (example of how previous case is expected to work): Empties parented to *3 vertices* are controled by same PS - OK\n[Child_Of_test.blend](Child_Of_test.blend)\n", "Motion blur artifacts on certain frames EEVEE\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nMotion blur on error appears on same certain frames.\n\nblend attached Error appears on frames : 49 , 60, 85, 95, 103, 119,130\n\n[blur test.blend](blur_test.blend)\nnormal frame \n\nerror frame \n\nvideo with error frames [0001-0300.mp4](0001-0300.mp4)\n\n", "EEVEE 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", "Optix: Motion Blur seems to glitch out while rendering\n\nOperating system: Windows 11 Pro 22H2 22621.525\n\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\n\nBroken: version: 3.3.2 LTS / 3.5.0 Alpha (Broken in both)\n\n\nHaving motion blur on while rendering with Optix seems to not work as expected in this scene. It renders out with artifacts (Alpha / black squares). Things work fine **when you turn off motion blur or switch to Cuda**.\n\n \n\n**Steps to reproduce the bug:**\nOpen the attached fine and render frame #82 with Optix enabled.\n\n[Keyframe remove 1_010.blend](Keyframe_remove_1_010.blend)\n", "Stereoscopic - right side has incorrect render (Eevee)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.93.4\nWorked: unknown\n\nStereoscopic creates an incorrect image for the rendered Right side (Eevee).\nThe right side seems to be a mix of the correct render and a render with low samples (1?). This is clear on the soft shadows and AO.\n \nIt can only be resolved by enabling Screen Space Reflections, which isn't always desirable obviously. \n\nOpen attached blend file and render. \nCompare left and right render.\n\n[stereoscopic_rightSide_difference.blend](stereoscopic_rightSide_difference.blend)\n", "depsgraph.view_layer.name driver expression doesn't work correctly\nOperating system: Windows 11\nGraphics card: Geforce RTX 3090\n\nBroken: 3.3.5 LTS\nBroken: 3.5\n\nI use a driver expression to control modifiers visibility or shader values depending on a view layer name. If the needed view layer is active, then values change. All works well when switching viewlayers manually inside the viewport of my scene. But as soon as I render the scene, the expression is ignored and nothing happen.\n\n* Open attached file\n* Change view layer few times\n\nDriver will change only once. This also doesn't work when rendering.\n\n", "EEVEE viewport error when using volume and lights (with animation)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25\n\n\nTested with the following two versions:\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\n\nWhen enabling a Volume Scatter shader in the World Settings with anisotropy set to 1.0, a simple point light is emitting a streak of light when the camera is animated. This does not show when the animation is rendered.\n\n\n\n[eevee_volumetric.blend](eevee_volumetric.blend)\n\nWith the attached .blend file:\n - Open the attached .blend file\n - Switch to rendered view (renderer should be Eevee)\n # Play the animation\n\nTo reproduce from scratch (just for info on what I did)\n\n - Default scene, delete cube, renderer should be Eevee \n - set intensity of point light to high intensity (1000W or so should be enough to see the effect)\n - add Volume Scatter BSDF to Volume output of the world shader with low intensity (0.010) and Anisotropy set to 1.0\n - Place the light so that it can be seen in camera view somewhere on the right side and animate two keyframes for the camera so that the light moves from right to left. (Test file anmiates for 40 frames)\n # switch to Rendered view and play animation\n\n\n**Note 1**\nHas been reported as second issue in #58023 with the system info below, so reporting it separately here to be able to close #58023 as the primary issue there is solved.\n\nSystem Information\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\nBlender Version\nBroken: version: 2.81 (sub 11)\n\n**Note 2**\nI wasn't sure if #53588 could be same underlying cause, feel free to de-duplicate this report if it is.\n\n**Note 3**\nI checked that it also happens when using scene lights and world in 'Material Preview' (LookDev) mode\n\n\n\n", "Rolling the viewport causes unpredictable behavior when orbiting using turntable method.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\nWorked: Never\n\nWhen using the turntable there is a fixed axis around which the viewport always orbits (the Z axis when the viewport hasn't been rolled).\nWhat happens is that Blender rolls this fixed axis with the viewport, so that when you orbit up/ down it does that using the new rolled fixed axis.\nHowever it does not roll the left/right orbiting directions (whatever you call them) with the viewport, meaning that, in my example, it creates an issue akin to gimbal lock where orbiting up/down will cause the same rotation of the viewport effectively making it lose one degree of freedom.\n\nI don't know the reason why Blender seems to behave in an unpredictable manner when orbiting with the mouse, but when orbiting with the numpad keys it confirms that we do indeed lose one degree of freedom as both Numpad {key 4} and {key 8} both cause an upward rotation of the viewport and both Numpad {key 2} and {key 6} cause a downward rotation of the viewport.\n\nSo to fix the issue all that needs to be done is to roll the left/right orbiting directions with the viewport and fixed axis.\n\n**Edit:**\nIt seems my original report focuses to much on the special case where the viewport has been rotated by exactly 90 degrees, causing it to lose one degree of freedom.\nHowever this is just a special case, the main issue is that whenever the viewport is rolled only the fixed axis is rolled, while the left/right orbiting axis(whatever you call them) is not.\nWhat you normally would expect when orbiting left/right that it orbits perpendicular to when you orbit up/down.\nBut since the left/right orbiting axis is not rolled, it meets the fixed axis at an angle other than 90 degrees, causing very unintuitive viewport behavior.\nOf course unless the viewport is rolled by exactly 90 degrees it is still technically possible to axis any viewing direction, however trying to do so will pose quite a challenge to the user.\n\n\n**For loss of one degree of freedom:**\n\n- Open new Blender file (Make sure to use turntable orbit method).\n- Roll the viewport by e.g. 90 degrees using {key shift 4} or {key shift 6}\n- Try orbiting the viewport with the mouse or the Numpad {key 2} {key 4} {key 6} {key 8} keys.\n\n**To see the unintuitive behavior:**\n\n- Open new Blender file (Make sure to use turntable orbit method).\n- Roll the viewport by any number of degrees using {key shift 4} or {key shift 6}\n- Try orbiting the viewport with the mouse or the Numpad {key 2} {key 4} {key 6} {key 8} keys.\n" ]

[ "Weird motion blur occuring when using drivers\n[mblur_drivers.blend](mblur_drivers.blend)\n*Operating system*: Windows 10 64bit\n*Graphics card*: Nvidia 1060 6gb\n\n*Broken*: 2.81\n\nObjects driven by drivers have weird motion blur. In 60 frame animation (24fps) the motion blur \"resetted\" twice, 2nd just before the end so it could be every second (24 frames)\n\nAnimate object going from on position to other. Set the driver for rotation axis of your choice so the objects rotates as it moves (I've used this for rolling wheel). Enable motion blur (default settings in my case) and render animation. When rendering single frames nothing happened (occured when rendering animation on .png and .avi jpeg). I have rendered 3 scenarios, 1st is my case, moving object and his rotation driven by driver (motion blur is wrong), 2nd is position and rotation manually keyframed, no drivers used, just keyframes (mblur worked), 3rd is case is, which I hoped would work, emptys location being animated, rotation driven by driver. Object then parented onto the empty. Didn't work. Rendering on CPU didn't help also.\n1) watch?v=XKMTGqFQte8\n2) watch?v=e2cbqpYZN90\n3) watch?v=CSwcuDPjw1s", "Drivers are not applied properly when transformation is aborted\nOperating system: macOS 10.14.5\nGraphics card: GeForce 650M\n\nBroken: 2.8 (2019-07-11\nWorked: (optional)\n\nDriven properties are not reset if `esc` is pressed during transform operation\n\n1. Open attached file\n2. Select the cube\n3. g-x to move the cube along the x-axis\n\n```\nThe scale is driven by x / 4, so the cube will be invisible when it's at the origin and will get bigger as you drag it along the x-axis\n```\n\n4. Press escape\n\nNote that the cube returns to the origin, but the scale does not get reset to 0\n\n5. Press g and the drivers will be applied (the cube will disappear)\n\n[driver-bug.blend](driver-bug.blend)", "Position in Render does not match viewport. (Driver properties)\nOperating system:Windows7\nGraphics card: gtx1050ti\n\nBug:2.80 (release)\n\nInformation about the position of objects is obtained in a different way for the viewport and render when working with drivers\n\nThe position of the dummy in the viewport is taken from its past state. When rendering from the frame on which the viewport was standing.\n\n1.create a cube\n2.create a dummy (or another cube)\n3. Set for dummy driver in the X position\n4. Script expression: (bX + aX) /2\nVariables:\n[bX is the position of the dummy on the x axis]\n[aX is the position of the cube on the x axis]\n5. create an animation on x axis for target cube\n6. play in vievport\n7. play in render\n\np.s. Rendered animation 1HdPOXR1qCs (sound driver's work's right but render isn't) planks on sides must indicate acceleration (in vievport its right) indicators on front sides must indicate drift.\np.p.s I offer 2 solutions: 1. take the position of objects for drivers from their position in the last frame. 2. add the parameters \"speed\"(local and world space) and \"acceleration\"(same) to the properties of object's in drivers tab.", "Drivers are not updated when relative to itself while rendering with cycles or eevee\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nI have a z rotation that is driven by the z translation of the same object, when rendering the rotation is not updated by the renderer.\n\n\n- Select the default cube and go to the object properties \n\n- Right click on the Z rotation and Add driver\nIn the driver tab put : \n```\n Object: chose the same cube\n Type: Z location\n Space: Local space\n```\n\n- Now when Moving the Z location the cube should rotate, animate the Z location value and render it, the rotation will not appear \n\n[Cycles_bug.blend](Cycles_bug.blend)\n\n" ]

[ "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.**", "Depsgraph integration of physics\n- [ ] Rigid body\n- [ ] Fluids\n[ ] ...", "Blender development todo list -- Import/Export\nNOTE: this is a direct dump of Import_Export (without cherrypicking the [still] valid items)\n\n## Blender files and Library linking\n\n- [ ] Mixing \"direct\" and \"indirect\" data not well supported #26706\n- [ ] Making local data which is still used in libraries, causes problems #44321\n\n## All Formats\n\nCurrently negative scales will flip faces for formats which don't store object transformations (obj, ply, stl ... etc). #35892\n\n## FBX\nSee [[Extensions:2.6/Py/Scripts/Import-Export/Autodesk_FBX]].\n\n## Alembic\n- [ ] While Alembic exports particles as points and supports ParticleInstance modifiers it could also support particle duplication (dupliobjects etc.), see #54703\n", "Add cube\" wrong representation of Z-extrusion (Not a bug Just little correction)\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.93.0\n\n\"Add cube\" wrong representation of Z-axis direction\n\nNot an error but an incorrect representation of object depth creation while using \"Add cube\" function.\n\n\n\n", "Alembic Exports Particles Wrong?\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\n\nAlembic Exports Particles Wrong\n\nThe image shows the problem. Green is the source that generates the white alembic. They should be the same.\n\n\nIt looks like all the particles are presented on frame #1, then simulated to fall as a clump, instead being born over time and falling one by one. Also, the export does not take into account the *Show Emitter* flag for the particle system. Most users won't want the emitter surface exported, and I can't find anyway to remove it using Blender.\n\n\n1.) Download the file and export the simulation as an Alembic.\n2.) Import result to observe the failure.\n\n[alembic_particle_failure.zip](alembic_particle_failure.zip)\n\n", "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)", "Particle System missing on right eye when renderd via terminal\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\nBroken: version: 2.81 (sub 12)\nI tested also 2.8 and it's also broken.\n\nIf you render a stereo image via terminal and use particle system emitter/hair the particle are only visible on one eye (left).\n\n- Add a second cube and make it smaller\n- Add a Particle System to the first cube, as hair, set \"render as\" to object and choose second cube.\n- In output properties enable stereoscopy. Set Outputfilename.\n- Save blendfile and start rendering via terminal, like this on windows:\nC:\\Users\\simeo\\Desktop\\blender2.8_nightly\\blender.exe -b C:\\Users\\simeo\\Desktop\\bugreports\\stereo_terminal_bug.blend -f 1\nHere's my blendfile:\n[stereo_terminal_bug.blend](stereo_terminal_bug.blend)\n\nHere's a comparison between rendered with and without terminal:\n\n\n", "Unable to get object to stay hidden while new mesh tool is active.\nWindows 10, 1060\n\nBroken: 2.80 master (also reproduced in a month-old daily build, so not new behavior).\n\nIf you have an active tool like Add Cylinder going, and you hide another object using the eye icon in the outliner, then as soon as you touch the cylinder parameters, the hidden object becomes unhidden.\n\n1) From the default scene, Add a Cylinder to the scene and expand the tool properties in the lower left of the 3dview.\n2) Because the cylinder is hidden inside the cube, we can't easily see the effect of changing the tool parameters, so go to the outliner and click the eyeball icon associated with the cube to hide it in the viewport.\n3) Change any parameter in the cylinder tool properties pop-up in the 3dview. The cube reappears and the eyeball indicates it is no longer hidden.\n\nBasically any changes made to the Outliner visibility icons gets reverted as soon as you change any active tool property, (at least for the Cylinder tool). This at least unexpected behavior.", "Kill Particles does not make them really dead\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 2.93.6\nWorked: -\n\nIf you give a mesh a physics property of collision and check the \"Kill Particles\" Checkbox, they are not becoming dead, they just stop moving. If you add a Particle Instance to another object and only show dead, the dead objects show correctly in viewport but not in render (eevee/cycles).\n\nI created a plane, put it about 10m higher and turned it 180° on x axis. Then i added a particle system to that plane with default settings. I added another plane and scaled it up a few times and applied all transforms. I then added a collision physics property with \"Kill Particles\" enabled to that plan. Now i added an Icosphere, scaled it down, applied all transforms and added the Particle Instance modifier. As Object i chose the first created plane and only left show dead active. After baking the Particle system, you see in viewport the Icosphere as soon as the particles hit the Plane with the collison physics property. But if you then want to render the image they are gone.\n\nWith the attached .blend file you just have to click bake in the particle system properties of the ParticleEmitter object and you should see the dead ParticleInstance object at Frame 40. But if you render the image then they are gone.[ParticlesNotDead.blend](ParticlesNotDead.blend)", "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", "Volumetric object not taking into account by cycles depth/mist pass\nOperating system: Linux-4.15.0-52-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 410.104\n\n\nBroken: version: 2.80 (sub 75)\n\n\nNo matter what \"Alpha Threshold\" is set to, cycles depth pass does not include volumes.\n\n**Expected behavior**\nIn the same way that Alpha Threshold is compared with the alpha transparency of each object, it (or another parameter like Density Threshold) should be compared with the density of each volume in the scene (for the purposes of inclusion in depth passes)\n\n[depth-pass.blend](depth-pass.blend)\nRendering this file yields a (normalized) depth pass that is missing the cube with the volume shader (but it does include the cube with the 0 alpha principled BSDF)\n\n\n", "Missing Freestyle Lines\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon(TM) Vega 10 Graphics (RAVEN, DRM 3.35.0, 5.4.0-91-generic, LLVM 12.0.0) AMD 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: 3.0.0, 3.2.0\nWorked: 2.83\n\nThere are missing Freestyle Lines when Rendering with Cycles. The results are better in eevee but the Problem is not gone. \nI use a similar file to create floorplans at work. \n\n- Open attached file or:\n - Create an orthographic camera,\n - create a huge amount of planes and text objects,\n - enable Freestyle, \n- render via Eevee or Cycles.\n[fs.blend](fs.blend)\n", "Fluid domain renders as the original object when particle mesh is momentarily disappear\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0\n\nIf there is no mesh generated from active particles within the domain, the frame will render with the domain as its original surface.\n\nI have an emitter object that periodically (cycles) emits fluid into the domain. At times when there is no mesh generated from particles in the domain the rendering is correct -- the fluid mesh:\n\n\n\nAt some point when there is no mesh generated particles inside the domain, the render is incorrect -- the surface coloring on the domain boundary:\n\n\n\nIn the attached file, I would know when I might start to include the Fluid Domain in the rendering, but it would be rather difficult to tell when there are no more particles if velocities or emissions are complicated with noise.\n\nHere is the [StackExchange ](fluid-simulation-gives-a-obscured-render-when-active-fluid-particles-are-absent) discussion and an example blend file.[fluid render problem.blend](fluid_render_problem.blend)\n\n\n\n", "Appending packed libraries is treated as if they weren't packed\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\nWorked: I believe never, at least it also seems broken in 2.83.\n\n- This file has packed resources as well as libraries: [ellie.blend](ellie.blend)\n- Everything was packed without any shennanigans, just File->External Data->Pack Resources, Pack Linked Libraries.\n- File works fine on its own.\n\n- Append the CH-ellie collection into an empty file.\n\n\n- It's looking for the packed libraries outside of the file, as if they were not packed.", "Alembic animation import missing dynamically spawned objects\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 531.79\n\nBroken: version: 3.3.1\nWorked: ?\n\n\nHi ! :) I'm trying to import a rigid body sim from houdini, where smalls spheres are spawning during time by wave, the first wave appear in the viewport but the other no. BUT blender still recognize them because i can see the other objects in the Object Path in MeshSequenceCache. The video i attached explain the probleme well. Someone know how to make the other object appearing ? Thanks :D\n\n?\n\n" ]

[ "Default cube UVs are incorrectly arranged.\nBroken: 2.80.75, 76dfbee423e8b, master, 2010-07-25 \n\nThe UV map of the default cube are aligned in a way that some vertices make contact with each other in UV space but don't actually make contact with each other in 3D space. Cubes added manually are not affected.\n\n* Default Cube \n* Manually added Cube \n\nTo fix this the default startup.blend file would have to be updated. All other meshes, that can be added manually, do have properly arranged UVs by default. As a side note the \"Quad Sphere\" in the sculpting startup.blend does not have UVs, and is to my knowledge the only way to end up with a mesh without UVs.\n\n- Create an Image\n- Create a Material\n- Set Base Color as Image Texture with image\n- Set Cube material to Material\n- Paint edges in Vertex Painting" ]

[ "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", "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", "Vertex Painting with data type \"Color\": Painting pure Red or Green creating non Zero in Blue Channel\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.63\n\nBroken: version: 3.5.0 Alpha\n\n**Short description of error** \nIn Geometry Nodes, I've tried scattering objects with vertex painting (data type \"Color\") using pure red (1,0,0), green (0,1,0) and blue (0,0,1). With a math node set to \"Greater than\", the different color channels are tested whether their values are bigger than 0. However, I discovered that I needed actually a \"Threshold\" value slightly bigger than 0 (I used 0.0001, just below the \"Spreadsheet's\" precision) because my objects for the blue painted areas got also displayed in red and green areas with a \"Threshold\" value of exactly 0 for testing the blue color channel. The red and green channels could be tested with a threshold of exactly 0. \n\nWith vertex painting using the data type \"Byte\", I could also set the blue channel's testing threshold to exactly 0.\n\n**Steps to Reproduce**\n- Open attached file\n- Set Threshold value exact to 0 for blue color channel\n[Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend](Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend)\n\n", "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", "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", "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", "Render crash\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon RX 560X ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.1.220810\n+ AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx\n\nBroken: version: 3.3.0 Beta\nWorked: 3.2.2\n\nBlender every time crash when switch to render mode in viewport.\nRender set to Cycles with GPU Compute.\nVega 8 selected as device in preferences.\nIf I select RX 560X in preferences, GPU Compute is greyed in Render preferences (also interesting why).\n\nAny project with simple cube crashed.[test11.crash.txt](test11.crash.txt)\n", "MacOS Crease Problem Back end Metal\nOperating system: Macbook Pro 14\nGraphics card: Apple M2 Pro\n\n3.6.2\n\n\nWhen the backend setting of macos is set to metal, the color change of the edge when applying blender's vertex crease. When edge crease is used, magenta color does not come out and it is processed as black color.\n\nrecording video\n\nview?usp=sharing\n\nview?usp=sharing\n\n", "Grease Pencil Shear Tool Todo\n## Grease Pencil Shear Tool Todo\n * - [x] {icon circle color=red} The tool should execute on release, so when you click and drag, it stops. Currently you need to click an extra time, which is inconsistent and annoying.\n * - [ ] {icon circle color=green} Add Tool Setting to switch between horizontal and vertical shearing\n * - [ ] {icon circle color=green} Shear should have a manipulator to shear in any direction, the orientation on which is controlled by the Orientation setting, just like the Transform manipulators. Dragging any of the handles shears in that direction.", "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", "ops.paint.image_paint() crashes blender with brush texture\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.1\nWorked: unknown\n\n\nWhen using bpy.ops.paint.image_paint() in a addon and use a brush texture, blender crashes on the first stroke with a EXCEPTION_ACCESS_VIOLATION\n\n\n\n1. load the paintstroke addon \n```\n {F10253953}\n```\n\n2. load the blend file\n[paint_crash.blend](paint_crash.blend) \n3. go into texture paint mode\n3. make sure the brush texture is assigned\n\n4. paint on the object with (LEFTMOUSE)\n5. crash\n\n\n**addon code:**\n\n```\nbl_info = {\n 'name': 'paintstroke',\n 'description': 'Paint Material image channels at once',\n 'author': 'Daniel Grauer',\n 'version': (2, 0, 0),\n 'blender': (2, 92, 0),\n 'location': \"View3D > Sidebar > Edit Tab\",\n 'category': 'Image Paint',\n 'wiki_url': 'blender_Material_Brush',\n}\n\nimport bpy\nfrom bpy.utils import register_class, unregister_class\nfrom bpy.types import Operator, Brush\n\n \nclass PaintStroke(Operator):\n '''paintstroke'''\n bl_idname = \"paint.paintstroke\"\n bl_label = \"paintstroke\"\n bl_options = {'REGISTER', 'UNDO'}\n \n \n @classmethod\n def poll(cls, context):\n return bpy.ops.paint.image_paint.poll()\n \n def modal(self, context, event): \n #print(\"MB keybinding test modal\")\n if event.type in {'MOUSEMOVE'}: \n brushstroke = {\n \"name\": \"defaultStroke\",\n \"pen_flip\": False,\n \"is_start\": False,\n \"location\": (0,0,0),\n \"mouse\": (event.mouse_region_x, event.mouse_region_y),\n \"pressure\": 1,\n \"size\": bpy.context.tool_settings.unified_paint_settings.size,\n \"time\": 0,\n \"mouse_event\": (0.0, 0.0),\n \"x_tilt\": 0,\n \"y_tilt\": 0,\n }\n stroke = [brushstroke] \n bpy.ops.paint.image_paint(stroke=stroke, mode='NORMAL') \n\n elif event.value in {'RELEASE'} or event.type in {'ESC'}:\n return {'FINISHED'} \n return {'PASS_THROUGH'}\n \n\n def invoke(self, context, event):\n if event.type in {'LEFTMOUSE'}: \n #self.paint(event) \n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n \n\nclasses = (\n PaintStroke, \n )\n\n\naddon_keymaps = []\n\ndef register(): \n [register_class(c) for c in classes]\n \n # Keymapping\n kc = bpy.context.window_manager.keyconfigs.addon\n km = kc.keymaps.new(name=\"Image Paint\", space_type='EMPTY', modal=False)\n kmi = km.keymap_items.new(\"paint.paintstroke\", type='LEFTMOUSE', value='PRESS', shift=False, ctrl=False , alt=False)\n kmi.active = True\n addon_keymaps.append((km, kmi))\n \n\ndef unregister(): \n # remove keymaps\n for km, kmi in addon_keymaps:\n km.keymap_items.remove(kmi)\n addon_keymaps.clear() \n \n [unregister_class(c) for c in classes]\n \n\nif __name__ == \"__main__\":\n register() \n```\n", "GPencil: Selecting textured brushes will crash Blender\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92.0\n\nWhen appending the textured brushes from the [Blender Cloud](5ccfe64353b85e279cf72acd) into a file, Blender will crash when trying to preview the brushes in the tool settings.\n\n\n - Open Blender 2.93 and select the \"2D Animation\" template.\n - Go to *File*>*Append* and browse to the `pepeland_GP_brush_pack_V1.blend` file. Go into the *Brush* folder and append the brushes `GBrush_001` through `GBrush_010`.\n # Click the brush icon in the tool settings. Blender crashes.\n\n\n\n", "Eevee clamping color values when viewport rendering and using viewport HDRI\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.0.0 Alpha\nWorked: (never)\n\nWhen doing a viewport render, color values are being clamped. In 2.92 a workaround for this was introduced - if you disable overlays, color is being processed as it should.\nHowever, if you use a viewport HDRI, even with the overlays turned off, values are still clamped.\nAs these two are often used together to get some quick snaps, it is a little inconvenient\n\n\n\n[#88288.blend](T88288.blend)\n\n- Open file\n- Switch to rendered view\n# Viewport render image\n\nColors are clamped even though overlays are disabled\n", "project turning purple automatically after closing and opening later+zoom in/out buttons not working properly.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.79\n\nBroken: version: 3.6.2\n\n\n\n", "Workbench: Random object color disables transparency in solid view\nOperating system: Windows 10 64bit\nGraphics card: Nvidia RTX 2080ti\n\nBroken: 2.83.1 official\n\n\n\n\nWhen setting the color of the material in the viewport to be semitransparent (Alpha value = 0.1) it works if the color of the viewport objects is set to \"Material\" it works, while if the color is set to \"Random\" the object is not semitransparent anymore.\n\nBlend file to test:\n[bug.blend](bug.blend)" ]

[ "ColorRamp Keyframes crash Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: In any version the feature is integrated in. e.g. since version 2.90\nWorked: None\n\nCreating a keyframe of ColorRamp's position value crashes blender.\n\nThis works in any file, with every mesh and every material. Example: [Bug Report.blend](Bug_Report.blend)\n1. Open Blender and select General under \"New File\". \n2. Select the default cube and Open the Shader Editor\n3. Create a \"ColorRamp\" node and connect its \"Color\" output to the \"Base Color\" input of the Principled BSDF.\n4. Go to Material Properties -> Surface and expand Base Color [ColorRamp] \n5. Create a keyframe of \"Pos\" at any value by clicking the dot to the right.\n\n", "Blender Crash When Adding Keyframe to ColorRamp Position\nHello, I am experiencing a crash in Blender 3.3.0.\n\nI am on a Mac Studio with 32GB of RAM, M1 Max, running MacOS 12.6.\n\nBlender crashes when I add a second keyframe to a ColorRamp in a shader. I'm trying to animate the ColorRamp position. Upon clicking the \"insert keyframe\" button to add a second keyframe, Blender will crash.\n\nI have attached a .blend file. To reproduce:\n\nOpen the shader settings. Scroll down to the normal settings and find the color ramp I have placed. Increase the white colorramp arrow to any value higher than what it is set to and then try to insert a keyframe by clicking the keyframe button next to the Pos slider. Blender will immediately crash.\n\n[test.blend](test.blend)\n\n\n\n```lines=18\n-------------------------------------\nTranslated Report (Full Report Below)\n-------------------------------------\n\nProcess: Blender [13202]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.3.0 (3.3.0 2022-09-07)\nCode Type: ARM-64 (Native)\nParent Process: launchd [1]\nUser ID: 502\n\nDate/Time: 2022-10-07 14:57:41.0172 -0500\nOS Version: macOS 12.6 (21G115)\nReport Version: 12\nAnonymous UUID: 29C7B32C-3B4A-D471-1090-A7D185BB6260\n\n\nTime Awake Since Boot: 11000 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000010\nException Codes: 0x0000000000000001, 0x0000000000000010\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11\nTerminating Process: exc handler [13202]\n\nVM Region Info: 0x10 is not in any region. Bytes before following region: 68719476720\n REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n commpage (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL ...(unallocated)\n\nKernel Triage:\nVM - pmap_enter failed with resource shortage\nVM - pmap_enter failed with resource shortage\nVM - pmap_enter failed with resource shortage\nVM - pmap_enter failed with resource shortage\nVM - pmap_enter failed with resource shortage\n\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x100eee9ec rna_property_update + 24\n1 Blender \t 0x1016b706c ui_apply_but_funcs_after + 324\n2 Blender \t 0x1016b706c ui_apply_but_funcs_after + 324\n3 Blender \t 0x1016c1fc0 ui_region_handler + 448\n4 Blender \t 0x100c6fcc4 wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 2256\n5 Blender \t 0x100c6ee58 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 72\n6 Blender \t 0x100c6e87c wm_event_do_handlers + 2864\n7 Blender \t 0x100c65b78 WM_main + 36\n8 Blender \t 0x1006e7a20 main + 872\n9 dyld \t 0x11376108c start + 520\n\nThread 1:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 2:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 3:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 4:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 5:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 6:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 7:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 8:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 9:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 libdispatch.dylib \t 0x185b30750 _dispatch_sema4_wait + 28\n2 libdispatch.dylib \t 0x185b30df8 _dispatch_semaphore_wait_slow + 132\n3 Blender \t 0x108d7bf94 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 64\n4 Blender \t 0x108d7abe0 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 64\n5 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n6 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 10:\n0 libsystem_pthread.dylib \t 0x185cef078 start_wqthread + 0\n\nThread 11:\n0 libsystem_pthread.dylib \t 0x185cef078 start_wqthread + 0\n\nThread 12:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 caulk \t 0x18e769a2c caulk::mach::semaphore::wait_or_error() + 28\n2 caulk \t 0x18e74d7ac caulk::concurrent::details::worker_thread::run() + 56\n3 caulk \t 0x18e74d3cc void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 96\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 13:\n0 libsystem_pthread.dylib \t 0x185cef078 start_wqthread + 0\n\nThread 14:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t 0x185cb68b0 mach_msg_trap + 8\n1 libsystem_kernel.dylib \t 0x185cb6d20 mach_msg + 76\n2 CoreAudio \t 0x187a066a0 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 104\n3 CoreAudio \t 0x187893bb0 HALC_ProxyIOContext::IOWorkLoop() + 3336\n4 CoreAudio \t 0x1878928b0 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 100\n5 CoreAudio \t 0x187a5eab0 HALB_IOThread::Entry(void*) + 88\n6 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n7 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 15:\n0 libsystem_pthread.dylib \t 0x185cef078 start_wqthread + 0\n\nThread 16:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 17:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 18:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 19:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 20:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 21:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 22:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 23:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 24:\n0 libsystem_kernel.dylib \t 0x185cb68ec semaphore_wait_trap + 8\n1 Blender \t 0x100c5bc30 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) + 64\n2 Blender \t 0x100c5b7e8 tbb::internal::rml::private_worker::run() + 420\n3 Blender \t 0x100c5b638 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n4 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n5 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 25:\n0 libsystem_kernel.dylib \t 0x185cbee84 __accept + 8\n1 _socket.cpython-310-darwin.so \t 0x13aede3dc sock_accept_impl + 32\n2 _socket.cpython-310-darwin.so \t 0x13aede7ec sock_call_ex + 492\n3 _socket.cpython-310-darwin.so \t 0x13aedc3e8 sock_accept + 120\n4 Blender \t 0x108dcab48 method_vectorcall_NOARGS + 160\n5 Blender \t 0x108e9a500 call_function + 428\n6 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n7 Blender \t 0x108e91860 _PyEval_Vector + 148\n8 Blender \t 0x108e9a500 call_function + 428\n9 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n10 Blender \t 0x108e91860 _PyEval_Vector + 148\n11 Blender \t 0x108e9a500 call_function + 428\n12 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n13 Blender \t 0x108e91860 _PyEval_Vector + 148\n14 Blender \t 0x108e9a500 call_function + 428\n15 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n16 Blender \t 0x108e91860 _PyEval_Vector + 148\n17 Blender \t 0x108dc3e14 method_vectorcall + 284\n18 Blender \t 0x108f35b78 thread_run + 72\n19 Blender \t 0x108eea7b4 pythread_wrapper + 28\n20 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n21 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 26:\n0 libsystem_kernel.dylib \t 0x185cc1598 __select + 8\n1 Blender \t 0x108f33ea0 time_sleep + 144\n2 Blender \t 0x108e0651c cfunction_vectorcall_O + 292\n3 Blender \t 0x108e9a500 call_function + 428\n4 Blender \t 0x108e97b38 _PyEval_EvalFrameDefault + 25052\n5 Blender \t 0x108e91860 _PyEval_Vector + 148\n6 Blender \t 0x108e9a500 call_function + 428\n7 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n8 Blender \t 0x108e91860 _PyEval_Vector + 148\n9 Blender \t 0x108e9a500 call_function + 428\n10 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n11 Blender \t 0x108e91860 _PyEval_Vector + 148\n12 Blender \t 0x108dc3e14 method_vectorcall + 284\n13 Blender \t 0x108f35b78 thread_run + 72\n14 Blender \t 0x108eea7b4 pythread_wrapper + 28\n15 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n16 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 27:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t 0x185cb68b0 mach_msg_trap + 8\n1 libsystem_kernel.dylib \t 0x185cb6d20 mach_msg + 76\n2 CoreFoundation \t 0x185dc1210 __CFRunLoopServiceMachPort + 372\n3 CoreFoundation \t 0x185dbf6c0 __CFRunLoopRun + 1180\n4 CoreFoundation \t 0x185dbea84 CFRunLoopRunSpecific + 600\n5 AppKit \t 0x188a93100 _NSEventThread + 196\n6 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n7 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 28:\n0 libsystem_kernel.dylib \t 0x185cc1598 __select + 8\n1 Blender \t 0x108f33ea0 time_sleep + 144\n2 Blender \t 0x108e0651c cfunction_vectorcall_O + 292\n3 Blender \t 0x108e9a500 call_function + 428\n4 Blender \t 0x108e97b38 _PyEval_EvalFrameDefault + 25052\n5 Blender \t 0x108e91860 _PyEval_Vector + 148\n6 Blender \t 0x108e9a500 call_function + 428\n7 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n8 Blender \t 0x108e91860 _PyEval_Vector + 148\n9 Blender \t 0x108e9a500 call_function + 428\n10 Blender \t 0x108e97b08 _PyEval_EvalFrameDefault + 25004\n11 Blender \t 0x108e91860 _PyEval_Vector + 148\n12 Blender \t 0x108dc3e14 method_vectorcall + 284\n13 Blender \t 0x108f35b78 thread_run + 72\n14 Blender \t 0x108eea7b4 pythread_wrapper + 28\n15 libsystem_pthread.dylib \t 0x185cf426c _pthread_start + 148\n16 libsystem_pthread.dylib \t 0x185cef08c thread_start + 8\n\nThread 29:\n0 libsystem_pthread.dylib \t 0x185cef078 start_wqthread + 0\n\nThread 30:\n0 libsystem_pthread.dylib \t 0x185cef078 start_wqthread + 0\n\n\nThread 0 crashed with ARM Thread State (64-bit):\n x0: 0x000000012300a808 x1: 0x000000013b5bae08 x2: 0x000000013b5de808 x3: 0x000000016f84b100\n x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000030 x7: 0x0000000000000120\n x8: 0x000000016f84afa0 x9: 0x000000016f84afa0 x10: 0x0000000000000074 x11: 0x00000000000ce850\n x12: 0x0000000156a00000 x13: 0x0000000000000000 x14: 0x00000000518bd31e x15: 0x0000000000206867\n x16: 0x0000000185d08530 x17: 0x00000001137d4580 x18: 0x0000000000000000 x19: 0x000000016f84b100\n x20: 0x000000016f84b1a0 x21: 0x000000013b5bae08 x22: 0x000000016f84b160 x23: 0x0000000156af2a18\n x24: 0x0000000000000000 x25: 0x000000010e4ec088 x26: 0x000000016f84b030 x27: 0x000000010e6f1e20\n x28: 0x000000010e532df0 fp: 0x000000016f84b020 lr: 0x00000001016b706c\n sp: 0x000000016f84b000 pc: 0x0000000100eee9ec cpsr: 0x60001000\n far: 0x0000000000000010 esr: 0x92000006 (Data Abort) byte read Translation fault\n\nBinary Images:\n 0x1005b4000 - 0x10da97fff org.blenderfoundation.blender (3.3.0) <938c577c-1fe9-340d-ad93-925c633a74d5> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11375c000 - 0x1137bbfff dyld (*) <38ee9fe9-b66d-3066-8c5c-6ddf0d6944c6> /usr/lib/dyld\n 0x185cb5000 - 0x185cecfff libsystem_kernel.dylib (*) <a9d87740-9c1d-3468-bf60-720a8d713cba> /usr/lib/system/libsystem_kernel.dylib\n 0x185b2c000 - 0x185b72fff libdispatch.dylib (*) <b3c7a004-1069-3171-b630-2c386a8b399c> /usr/lib/system/libdispatch.dylib\n 0x185ced000 - 0x185cf9fff libsystem_pthread.dylib (*) <63c4eef9-69a5-38b1-996e-8d31b66a051d> /usr/lib/system/libsystem_pthread.dylib\n 0x18e74b000 - 0x18e771fff com.apple.audio.caulk (1.0) <fbaaa1ec-abbe-3c0d-a491-0dc66ee9d8ce> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x1876d2000 - 0x187df5fff com.apple.audio.CoreAudio (5.0) <01e2a2bb-2115-3015-9744-c0dc512bb554> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x13aed8000 - 0x13aee7fff _socket.cpython-310-darwin.so (*) <7a01f822-84f3-3b38-8db3-1fcd04db2915> /Applications/Blender.app/Contents/Resources/3.3/python/lib/python3.10/lib-dynload/_socket.cpython-310-darwin.so\n 0x185d3c000 - 0x186282fff com.apple.CoreFoundation (6.9) <fc3c193d-0cdb-3569-9f0e-bd2507ca1dbb> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x1888e5000 - 0x18979dfff com.apple.AppKit (6.9) <5e432f87-5b58-391a-a542-fa2d909dd210> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\nWritable regions: Total=761.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=761.9M(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 128K 1 \nActivity Tracing 256K 1 \nCG backing stores 2880K 4 \nCG image 128K 6 \nColorSync 208K 7 \nCoreAnimation 176K 8 \nCoreGraphics 32K 2 \nCoreImage 16K 1 \nCoreUI image data 1088K 7 \nDispatch continuations 80.0M 1 \nFoundation 16K 1 \nKernel Alloc Once 32K 1 \nMALLOC 403.3M 114 \nMALLOC guard page 192K 10 \nMALLOC_MEDIUM (reserved) 64.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 496K 31 \nStack 95.5M 32 \nStack Guard 16K 1 \nVM_ALLOCATE 102.6M 202 \nVM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)\n__AUTH 2052K 215 \n__AUTH_CONST 13.1M 387 \n__CTF 756 1 \n__DATA 29.9M 448 \n__DATA_CONST 21.2M 457 \n__DATA_DIRTY 1016K 137 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 653.9M 71 \n__OBJC_CONST 2158K 186 \n__OBJC_RO 83.0M 1 \n__OBJC_RW 3168K 1 \n__TEXT 550.2M 473 \n__UNICODE 592K 1 \ndyld private memory 1024K 1 \nmapped file 223.5M 27 \nshared memory 896K 14 \n=========== ======= ======= \nTOTAL 2.3G 2857 \nTOTAL, minus reserved VM space 2.2G 2857 \n\n\n\n-----------\nFull Report\n-----------\n\n{\"app_name\":\"Blender\",\"timestamp\":\"2022-10-07 14:57:41.00 -0500\",\"app_version\":\"3.3.0\",\"slice_uuid\":\"938c577c-1fe9-340d-ad93-925c633a74d5\",\"build_version\":\"3.3.0 2022-09-07\",\"platform\":1,\"bundleID\":\"org.blenderfoundation.blender\",\"share_with_app_devs\":0,\"is_first_party\":0,\"bug_type\":\"309\",\"os_version\":\"macOS 12.6 (21G115)\",\"incident_id\":\"D72CEB85-E68E-4B37-AF3A-16781B5E8CFE\",\"name\":\"Blender\"}\n{\n \"uptime\" : 11000,\n \"procLaunch\" : \"2022-10-07 14:57:29.0947 -0500\",\n \"procRole\" : \"Foreground\",\n \"version\" : 2,\n \"userID\" : 502,\n \"deployVersion\" : 210,\n \"modelCode\" : \"Mac13,1\",\n \"procStartAbsTime\" : 281163181492,\n \"coalitionID\" : 1596,\n \"osVersion\" : {\n \"train\" : \"macOS 12.6\",\n \"build\" : \"21G115\",\n \"releaseType\" : \"User\"\n },\n \"captureTime\" : \"2022-10-07 14:57:41.0172 -0500\",\n \"incident\" : \"D72CEB85-E68E-4B37-AF3A-16781B5E8CFE\",\n \"bug_type\" : \"309\",\n \"pid\" : 13202,\n \"procExitAbsTime\" : 281448444934,\n \"translated\" : false,\n \"cpuType\" : \"ARM-64\",\n \"procName\" : \"Blender\",\n \"procPath\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"bundleInfo\" : {\"CFBundleShortVersionString\":\"3.3.0\",\"CFBundleVersion\":\"3.3.0 2022-09-07\",\"CFBundleIdentifier\":\"org.blenderfoundation.blender\"},\n \"storeInfo\" : {\"deviceIdentifierForVendor\":\"50BA26D6-7E14-5258-AC79-1B633F07AB3B\",\"thirdParty\":true},\n \"parentProc\" : \"launchd\",\n \"parentPid\" : 1,\n \"coalitionName\" : \"org.blenderfoundation.blender\",\n \"crashReporterKey\" : \"29C7B32C-3B4A-D471-1090-A7D185BB6260\",\n \"sip\" : \"enabled\",\n \"vmRegionInfo\" : \"0x10 is not in any region. Bytes before following region: 68719476720\\n REGION TYPE START - END [ VSIZE] PRT\\/MAX SHRMOD REGION DETAIL\\n UNUSED SPACE AT START\\n---> \\n commpage (reserved) 1000000000-7000000000 [384.0G] ---\\/--- SM=NUL ...(unallocated)\",\n \"isCorpse\" : 1,\n \"exception\" : {\"codes\":\"0x0000000000000001, 0x0000000000000010\",\"rawCodes\":[1,16],\"type\":\"EXC_BAD_ACCESS\",\"signal\":\"SIGSEGV\",\"subtype\":\"KERN_INVALID_ADDRESS at 0x0000000000000010\"},\n \"termination\" : {\"flags\":0,\"code\":11,\"namespace\":\"SIGNAL\",\"indicator\":\"Segmentation fault: 11\",\"byProc\":\"exc handler\",\"byPid\":13202},\n \"ktriageinfo\" : \"VM - pmap_enter failed with resource shortage\\nVM - pmap_enter failed with resource shortage\\nVM - pmap_enter failed with resource shortage\\nVM - pmap_enter failed with resource shortage\\nVM - pmap_enter failed with resource shortage\\n\",\n \"vmregioninfo\" : \"0x10 is not in any region. Bytes before following region: 68719476720\\n REGION TYPE START - END [ VSIZE] PRT\\/MAX SHRMOD REGION DETAIL\\n UNUSED SPACE AT START\\n---> \\n commpage (reserved) 1000000000-7000000000 [384.0G] ---\\/--- SM=NUL ...(unallocated)\",\n \"extMods\" : {\"caller\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"system\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"targeted\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"warnings\":0},\n \"faultingThread\" : 0,\n \"threads\" : [{\"triggered\":true,\"id\":122577,\"threadState\":{\"x\":[{\"value\":4882212872},{\"value\":5290831368},{\"value\":5290977288},{\"value\":6165934336},{\"value\":0},{\"value\":0},{\"value\":48},{\"value\":288},{\"value\":6165933984},{\"value\":6165933984},{\"value\":116},{\"value\":845904},{\"value\":5748293632},{\"value\":0},{\"value\":1368118046},{\"value\":2123879},{\"value\":6540002608,\"symbolLocation\":0,\"symbol\":\"_platform_strcmp\"},{\"value\":4621944192,\"symbolLocation\":0,\"symbol\":\"_main_thread\"},{\"value\":0},{\"value\":6165934336},{\"value\":6165934496},{\"value\":5290831368},{\"value\":6165934432},{\"value\":5749287448},{\"value\":0},{\"value\":4535009416,\"symbolLocation\":0,\"symbol\":\"RNA_UserAssetLibrary\"},{\"value\":6165934128},{\"value\":4537130528,\"symbolLocation\":0,\"symbol\":\"MEM_freeN\"},{\"value\":4535299568,\"symbolLocation\":0,\"symbol\":\"RNA_KeyMapItem\"}],\"flavor\":\"ARM_THREAD_STATE64\",\"lr\":{\"value\":4318785644},\"cpsr\":{\"value\":1610616832},\"fp\":{\"value\":6165934112},\"sp\":{\"value\":6165934080},\"esr\":{\"value\":2449473542,\"description\":\"(Data Abort) byte read Translation fault\"},\"pc\":{\"value\":4310624748,\"matchesCrashFrame\":1},\"far\":{\"value\":16}},\"queue\":\"com.apple.main-thread\",\"frames\":[{\"imageOffset\":9677292,\"symbol\":\"rna_property_update\",\"symbolLocation\":24,\"imageIndex\":0},{\"imageOffset\":17838188,\"symbol\":\"ui_apply_but_funcs_after\",\"symbolLocation\":324,\"imageIndex\":0},{\"imageOffset\":17838188,\"symbol\":\"ui_apply_but_funcs_after\",\"symbolLocation\":324,\"imageIndex\":0},{\"imageOffset\":17883072,\"symbol\":\"ui_region_handler\",\"symbolLocation\":448,\"imageIndex\":0},{\"imageOffset\":7060676,\"symbol\":\"wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*)\",\"symbolLocation\":2256,\"imageIndex\":0},{\"imageOffset\":7056984,\"symbol\":\"wm_handlers_do(bContext*, wmEvent*, ListBase*)\",\"symbolLocation\":72,\"imageIndex\":0},{\"imageOffset\":7055484,\"symbol\":\"wm_event_do_handlers\",\"symbolLocation\":2864,\"imageIndex\":0},{\"imageOffset\":7019384,\"symbol\":\"WM_main\",\"symbolLocation\":36,\"imageIndex\":0},{\"imageOffset\":1260064,\"symbol\":\"main\",\"symbolLocation\":872,\"imageIndex\":0},{\"imageOffset\":20620,\"symbol\":\"start\",\"symbolLocation\":520,\"imageIndex\":1}]},{\"id\":122589,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122590,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122591,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122592,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122593,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122594,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122595,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122596,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122597,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":18256,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":28,\"imageIndex\":3},{\"imageOffset\":19960,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":132,\"imageIndex\":3},{\"imageOffset\":142376852,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":142371808,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122609,\"frames\":[{\"imageOffset\":8312,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":122610,\"frames\":[{\"imageOffset\":8312,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":122614,\"name\":\"AMCP Logging Spool\",\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":125484,\"symbol\":\"caulk::mach::semaphore::wait_or_error()\",\"symbolLocation\":28,\"imageIndex\":5},{\"imageOffset\":10156,\"symbol\":\"caulk::concurrent::details::worker_thread::run()\",\"symbolLocation\":56,\"imageIndex\":5},{\"imageOffset\":9164,\"symbol\":\"void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)\",\"symbolLocation\":96,\"imageIndex\":5},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122673,\"frames\":[{\"imageOffset\":8312,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":122689,\"name\":\"com.apple.audio.IOThread.client\",\"frames\":[{\"imageOffset\":6320,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":7456,\"symbol\":\"mach_msg\",\"symbolLocation\":76,\"imageIndex\":2},{\"imageOffset\":3360416,\"symbol\":\"HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int)\",\"symbolLocation\":104,\"imageIndex\":6},{\"imageOffset\":1842096,\"symbol\":\"HALC_ProxyIOContext::IOWorkLoop()\",\"symbolLocation\":3336,\"imageIndex\":6},{\"imageOffset\":1837232,\"symbol\":\"invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)\",\"symbolLocation\":100,\"imageIndex\":6},{\"imageOffset\":3721904,\"symbol\":\"HALB_IOThread::Entry(void*)\",\"symbolLocation\":88,\"imageIndex\":6},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122719,\"frames\":[{\"imageOffset\":8312,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":122762,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122763,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122764,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122765,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122766,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122767,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122768,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122769,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122770,\"frames\":[{\"imageOffset\":6380,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":6978608,\"symbol\":\"rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&)\",\"symbolLocation\":64,\"imageIndex\":0},{\"imageOffset\":6977512,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":420,\"imageIndex\":0},{\"imageOffset\":6977080,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":12,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122772,\"frames\":[{\"imageOffset\":40580,\"symbol\":\"__accept\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":25564,\"symbol\":\"sock_accept_impl\",\"symbolLocation\":32,\"imageIndex\":7},{\"imageOffset\":26604,\"symbol\":\"sock_call_ex\",\"symbolLocation\":492,\"imageIndex\":7},{\"imageOffset\":17384,\"symbol\":\"sock_accept\",\"symbolLocation\":120,\"imageIndex\":7},{\"imageOffset\":142699336,\"symbol\":\"method_vectorcall_NOARGS\",\"symbolLocation\":160,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":142671380,\"symbol\":\"method_vectorcall\",\"symbolLocation\":284,\"imageIndex\":0},{\"imageOffset\":144186232,\"symbol\":\"thread_run\",\"symbolLocation\":72,\"imageIndex\":0},{\"imageOffset\":143878068,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":28,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122773,\"frames\":[{\"imageOffset\":50584,\"symbol\":\"__select\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":144178848,\"symbol\":\"time_sleep\",\"symbolLocation\":144,\"imageIndex\":0},{\"imageOffset\":142943516,\"symbol\":\"cfunction_vectorcall_O\",\"symbolLocation\":292,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143539000,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25052,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":142671380,\"symbol\":\"method_vectorcall\",\"symbolLocation\":284,\"imageIndex\":0},{\"imageOffset\":144186232,\"symbol\":\"thread_run\",\"symbolLocation\":72,\"imageIndex\":0},{\"imageOffset\":143878068,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":28,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122808,\"name\":\"com.apple.NSEventThread\",\"frames\":[{\"imageOffset\":6320,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":7456,\"symbol\":\"mach_msg\",\"symbolLocation\":76,\"imageIndex\":2},{\"imageOffset\":545296,\"symbol\":\"__CFRunLoopServiceMachPort\",\"symbolLocation\":372,\"imageIndex\":8},{\"imageOffset\":538304,\"symbol\":\"__CFRunLoopRun\",\"symbolLocation\":1180,\"imageIndex\":8},{\"imageOffset\":535172,\"symbol\":\"CFRunLoopRunSpecific\",\"symbolLocation\":600,\"imageIndex\":8},{\"imageOffset\":1761536,\"symbol\":\"_NSEventThread\",\"symbolLocation\":196,\"imageIndex\":9},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122820,\"frames\":[{\"imageOffset\":50584,\"symbol\":\"__select\",\"symbolLocation\":8,\"imageIndex\":2},{\"imageOffset\":144178848,\"symbol\":\"time_sleep\",\"symbolLocation\":144,\"imageIndex\":0},{\"imageOffset\":142943516,\"symbol\":\"cfunction_vectorcall_O\",\"symbolLocation\":292,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143539000,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25052,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":143549696,\"symbol\":\"call_function\",\"symbolLocation\":428,\"imageIndex\":0},{\"imageOffset\":143538952,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":25004,\"imageIndex\":0},{\"imageOffset\":143513696,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":148,\"imageIndex\":0},{\"imageOffset\":142671380,\"symbol\":\"method_vectorcall\",\"symbolLocation\":284,\"imageIndex\":0},{\"imageOffset\":144186232,\"symbol\":\"thread_run\",\"symbolLocation\":72,\"imageIndex\":0},{\"imageOffset\":143878068,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":28,\"imageIndex\":0},{\"imageOffset\":29292,\"symbol\":\"_pthread_start\",\"symbolLocation\":148,\"imageIndex\":4},{\"imageOffset\":8332,\"symbol\":\"thread_start\",\"symbolLocation\":8,\"imageIndex\":4}]},{\"id\":122824,\"frames\":[{\"imageOffset\":8312,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":122825,\"frames\":[{\"imageOffset\":8312,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]}],\n \"usedImages\" : [\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64\",\n \"base\" : 4300947456,\n \"CFBundleShortVersionString\" : \"3.3.0\",\n \"CFBundleIdentifier\" : \"org.blenderfoundation.blender\",\n \"size\" : 223232000,\n \"uuid\" : \"938c577c-1fe9-340d-ad93-925c633a74d5\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"name\" : \"Blender\",\n \"CFBundleVersion\" : \"3.3.0 2022-09-07\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 4621451264,\n \"size\" : 393216,\n \"uuid\" : \"38ee9fe9-b66d-3066-8c5c-6ddf0d6944c6\",\n \"path\" : \"\\/usr\\/lib\\/dyld\",\n \"name\" : \"dyld\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6539661312,\n \"size\" : 229376,\n \"uuid\" : \"a9d87740-9c1d-3468-bf60-720a8d713cba\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_kernel.dylib\",\n \"name\" : \"libsystem_kernel.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6538051584,\n \"size\" : 290816,\n \"uuid\" : \"b3c7a004-1069-3171-b630-2c386a8b399c\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libdispatch.dylib\",\n \"name\" : \"libdispatch.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6539890688,\n \"size\" : 53248,\n \"uuid\" : \"63c4eef9-69a5-38b1-996e-8d31b66a051d\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_pthread.dylib\",\n \"name\" : \"libsystem_pthread.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6684979200,\n \"CFBundleShortVersionString\" : \"1.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.caulk\",\n \"size\" : 159744,\n \"uuid\" : \"fbaaa1ec-abbe-3c0d-a491-0dc66ee9d8ce\",\n \"path\" : \"\\/System\\/Library\\/PrivateFrameworks\\/caulk.framework\\/Versions\\/A\\/caulk\",\n \"name\" : \"caulk\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6567043072,\n \"CFBundleShortVersionString\" : \"5.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.CoreAudio\",\n \"size\" : 7487488,\n \"uuid\" : \"01e2a2bb-2115-3015-9744-c0dc512bb554\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreAudio.framework\\/Versions\\/A\\/CoreAudio\",\n \"name\" : \"CoreAudio\",\n \"CFBundleVersion\" : \"5.0\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64\",\n \"base\" : 5283610624,\n \"size\" : 65536,\n \"uuid\" : \"7a01f822-84f3-3b38-8db3-1fcd04db2915\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/Resources\\/3.3\\/python\\/lib\\/python3.10\\/lib-dynload\\/_socket.cpython-310-darwin.so\",\n \"name\" : \"_socket.cpython-310-darwin.so\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6540214272,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.CoreFoundation\",\n \"size\" : 5533696,\n \"uuid\" : \"fc3c193d-0cdb-3569-9f0e-bd2507ca1dbb\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreFoundation.framework\\/Versions\\/A\\/CoreFoundation\",\n \"name\" : \"CoreFoundation\",\n \"CFBundleVersion\" : \"1866\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"arm64e\",\n \"base\" : 6585995264,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.AppKit\",\n \"size\" : 15437824,\n \"uuid\" : \"5e432f87-5b58-391a-a542-fa2d909dd210\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/AppKit.framework\\/Versions\\/C\\/AppKit\",\n \"name\" : \"AppKit\",\n \"CFBundleVersion\" : \"2113.60.148\"\n },\n {\n \"size\" : 0,\n \"source\" : \"A\",\n \"base\" : 0,\n \"uuid\" : \"00000000-0000-0000-0000-000000000000\"\n }\n],\n \"sharedCache\" : {\n \"base\" : 6536593408,\n \"size\" : 3144744960,\n \"uuid\" : \"049b583e-d4dc-3b2b-88da-e52d6e18313d\"\n},\n \"vmSummary\" : \"ReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\\nWritable regions: Total=761.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=761.9M(100%)\\n\\n VIRTUAL REGION \\nREGION TYPE SIZE COUNT (non-coalesced) \\n=========== ======= ======= \\nAccelerate framework 128K 1 \\nActivity Tracing 256K 1 \\nCG backing stores 2880K 4 \\nCG image 128K 6 \\nColorSync 208K 7 \\nCoreAnimation 176K 8 \\nCoreGraphics 32K 2 \\nCoreImage 16K 1 \\nCoreUI image data 1088K 7 \\nDispatch continuations 80.0M 1 \\nFoundation 16K 1 \\nKernel Alloc Once 32K 1 \\nMALLOC 403.3M 114 \\nMALLOC guard page 192K 10 \\nMALLOC_MEDIUM (reserved) 64.0M 1 reserved VM address space (unallocated)\\nOpenGL GLSL 256K 3 \\nSTACK GUARD 496K 31 \\nStack 95.5M 32 \\nStack Guard 16K 1 \\nVM_ALLOCATE 102.6M 202 \\nVM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)\\n__AUTH 2052K 215 \\n__AUTH_CONST 13.1M 387 \\n__CTF 756 1 \\n__DATA 29.9M 448 \\n__DATA_CONST 21.2M 457 \\n__DATA_DIRTY 1016K 137 \\n__FONT_DATA 4K 1 \\n__GLSLBUILTINS 5176K 1 \\n__LINKEDIT 653.9M 71 \\n__OBJC_CONST 2158K 186 \\n__OBJC_RO 83.0M 1 \\n__OBJC_RW 3168K 1 \\n__TEXT 550.2M 473 \\n__UNICODE 592K 1 \\ndyld private memory 1024K 1 \\nmapped file 223.5M 27 \\nshared memory 896K 14 \\n=========== ======= ======= \\nTOTAL 2.3G 2857 \\nTOTAL, minus reserved VM space 2.2G 2857 \\n\",\n \"legacyInfo\" : {\n \"threadTriggered\" : {\n \"queue\" : \"com.apple.main-thread\"\n }\n},\n \"trialInfo\" : {\n \"rollouts\" : [\n {\n \"rolloutId\" : \"607844aa04477260f58a8077\",\n \"factorPackIds\" : {\n \"SIRI_MORPHUN_ASSETS\" : \"6103050cbfe6dc472e1c982a\"\n },\n \"deploymentId\" : 240000066\n },\n {\n \"rolloutId\" : \"60186475825c62000ccf5450\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000026\n }\n ],\n \"experiments\" : [\n {\n \"treatmentId\" : \"5b729754-3882-4560-826f-9c0bc27d77c6\",\n \"experimentId\" : \"6192fb082171a2330e561df0\",\n \"deploymentId\" : 400000034\n }\n ]\n}\n}\n\nModel: Mac13,1, BootROM 7459.141.1, proc 10:8:2 processors, 32 GB, SMC \nGraphics: Apple M1 Max, Apple M1 Max, Built-In\nDisplay: LG HDR 4K, 3840 x 2160 (2160p/4K UHD 1 - Ultra High Definition), Main, MirrorOff, Online\nMemory Module: LPDDR5\nAirPort: Wi-Fi, wl0: Apr 6 2022 06:12:09 version 20.90.45.0.8.7.118 FWID 01-13a89935\nBluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports\nNetwork Service: USB 10/100/1000 LAN, Ethernet, en6\nPCI Card: pci8086,15f0, USB eXtensible Host Controller, Thunderbolt@3,0,0\nUSB Device: USB31Bus\nUSB Device: USB31Bus\nUSB Device: USB31Bus\nUSB Device: USB31Bus\nUSB Device: 4-Port USB 2.0 Hub\nUSB Device: USB Controls\nUSB Device: USB31Bus\nUSB Device: USB2 Hub\nUSB Device: USB3 Gen2 Hub\nUSB Device: PSSD T7 Shield\nUSB Device: USB31Bus\nUSB Device: Dell dock\nUSB Device: USB 10/100/1000 LAN\nUSB Device: Dell dock\nUSB Device: Dell dock\nUSB Device: Dell dock\nUSB Device: Dell dock\nUSB Device: Dell dock\nUSB Device: USB Audio\nUSB Device: USB Receiver\nThunderbolt Bus: Mac Studio, Apple Inc.\nThunderbolt Bus: Mac Studio, Apple Inc.\nThunderbolt Device: WD19TB Thunderbolt Dock, Dell, 1, 43.43\nThunderbolt Bus: Mac Studio, Apple Inc.\nThunderbolt Bus: Mac Studio, Apple Inc.\n```\n", "Crash when clicking on a decorator to key a ColorRamp Node's color stop in the material properties menu.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.4\n3.0.0 Alpha\n\n\nI want to animate the position parameter in the Color Ramp (shader node) using the decorator in the material properties menu, when the key is set, the program crashes.\n`PropertyRNA *prop` is a nullptr\n [blender_crash.mp4](blender_crash.mp4)" ]

[ "Particle systems cannot read curve modifiers and geometry nodes ..\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.1\n\nCan particle systems not use curves with modifiers added, or can particle systems only support fixed curves? This seems to lose a lot of creativity\n\n", "'Signed Angle' of node 'Edge Angle' does not clearly define what is convex or concave\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.2\n\nAccording to the [manual](edge_angle.html):\n> The signed angle in radians between two faces where they meet at an edge. Flat edges and Non-manifold edges have an angle of zero. Concave angles are positive and convex angles are negative.\n\nBut for some geometries, the choice of whether an edge is concave or convex seems to be random.\n\n- Open attached .blend file (It has two very similar geometries)\n- Enable the `Viewer Node` for each of the geometries.\n\nOne of them the edge will have negative value (convex)\nIn the other, the edge will have a positive value (concave)\n\n", "Regression: 2D Curve -> 3D Curve keeps 2D Curve fill\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: since 3.0.0\nWorked: 2.93.3\n\nCurves have the 2D mode, where points all points are on the same plane and fills are done similar to a 2D vector program like Inkscape and the 3D mode, where the fills are placed along the curve.\nBy switching a Curve to 2D and then undoing, you can (temporarily) get the 2D fill behavior in 3D.\n\n1. Add a Curve like the circle\n2. Go into edit mode and select a single point\n3. In the properties, switch the Curve type from 3D to 2D\n4. Change the Curve fill type so that the Curve has a fill\n5. Switch the Curve back into 3D\n6. Switch the Curve back into 2D\n7. Undo\n8. The Curve will now be 3D, but still have its 2D fill. You can now move your selected point around and see the fill persisting.\n\n[blender_2022-07-18_18-58-12.mp4](blender_2022-07-18_18-58-12.mp4)", "Circle select does not select all vertices within the same pixel\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.90.1\n\nSelecting closely-arranged vertices with circle select tool doesn't consistently select all vertices.\n\nCreate plane geometry with three vertices located close together (e.g., the end of a sword or a blade of grass). Type 'C' to use the circle select tool and select the vertices. Zoom in to verify that all vertices have been selected. De-select vertices. Change zoom level. Repeat selection. Repeat verification. See animated GIF, attached, using simple .blend file, attached.\n\n\n\n[C3DE_Ch4_L12a.blend](C3DE_Ch4_L12a.blend)\n\n", "Bevel Modifier: Odd amount of segments causes UV propagation issues at seams\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 2.83, 3.4.0 Alpha\nWorked: unknown\n\nAny odd number of bevel segments greater than 1 fails to preserve seams in the propagated UV data on intersections. Instead UV data is interpolated, which can for example cause nasty artefacts when baking.\n[bug_bevel_uv_seams_interpolation-2022-09-01_15.26.11.mp4](bug_bevel_uv_seams_interpolation-2022-09-01_15.26.11.mp4)\n\nFile:\n[baking_artefacts.blend](baking_artefacts.blend)\n\n", "Multi-segment bevel doesn't follow edgeloop below certain width.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Beta\nWorked: NA (repro in 2.80)\n\n\nWhen using a multi-segmented bevel below a certain width the existing edgeloop flow is not respected. It will 'snap' to follow the existing edgeloop once you reach a certain width. \n\nChanging the unit scale does not affect the issue. However, scaling up the object and applying scale will avoid the issue as the bevel width with the issue is so insignificant.\n\n\n\n[bevel_issue.blend](bevel_issue.blend)\n\n\n - Load bevel_issue.blend\n - Enter the Right Orthographic (X+) preset viewpoint\n - In outliner select bevel object from the scene collection and enter edit mode (edge)\n - Select the two edges marked sharp\n - Use the bevel tool and set segments to 4\n - Observe that a bevel width < 1.6mm results in a slight upwards bowing of the mid-ring loops inside the bevel, whereas a larger bevel follows the existing orientation of the edgeloop.", "Operator to convert from New to Old curve object type\nAdd the ability to convert from the new `Curves` object to the old `Curve` object, in the `Object > Convert` menu.\nSimilar to #96559.\nThere should probably be an info message when custom attributes are lost with the conversion.", "Simulation Nodes: Store baked geometries in .blend file\nFor simulation nodes in geometry nodes we want to be able to store the baked geometry data directly in .blend files. This is similar to how we are able to store a baked particle simulation using the old particle system. \n\nWhat makes the problem more complex now than it used to be is that geometry nodes deals with geometry much more generically. Not only can a mesh change its topology over time, but it's also possible that there are multiple geometries (e.g. a mesh and a point cloud) or the geometry type changes between frames. Also, instances have to be supported, but it may be ok to add that support later.\n\nThe main difficulty is to store many arbitrary geometries in the .blend file efficiently. I identified a couple possibilities to deal with this which are explained below.\n\n## Option A: Store geometries directly in `Main`\n\nIn this option every baked mesh/pointcloud/curves geometry is stored as a separate data block in `Main`.\n\nPros:\n* Code infrastructure exists already.\n* In theory, the baked geometries can easily be edited individually without much futher effort. This is something we want to support eventually anyway.\n\nCons:\n* Results in potentially lots of additional IDs in `Main` which can cause significant slowdowns (for example one mesh per baked frame).\n* Probably needs some new behavior in the depsgraph because we likely don't want a depsgraph node per cached geometry data-block.\n* Harder to implement data sharing across multiple data blocks in .blend files than it is within a single ID (both should be possible in theory though).\n* Might need special cases in ui code because we probably don't want to show all these data blocks in the data block dropdowns.\n* The way we store baked geometries wouldn't be an implementation detail, which makes it harder to change later.\n* Instances can't be stored natively in DNA yet.\n\n## Option B: Store geometries as no-main data-blocks.\n\nInstead of storing e.g. a baked `Mesh` in `Main` (which comes with user counting, unique names, etc.), the mesh could be owned by something else like a node or modifier. From the perspective of the .blend file, the mesh would just be normal data and not an ID data-block. To make that work, there need to be functions like `BKE_mesh_blend_write_nomain`. I did a small test for this and so far it worked as expected.\n\nPros:\n* Can reuse existing code to serialize/deserialize geometries (except for instances and volumes).\n* No additional IDs in `Main`.\n* Implementing data sharing between multiple geometries is more straight forward than with separate data-blocks.\n\nCons:\n* Need to make sure that versioning code for geometries also runs on those that are not in `Main`. This likely means iterating over all objects/nodes to version meshes.\n* No-main IDs are often more difficult to deal with by generic id handling code.\n* All these non-main IDs seem to be some new kind of embedded IDs which might need special handling in various places.\n\n## Option C: Store geometries as no-main no-id data.\n\nThe idea is to introduce a new struct like `BakedMesh` that is very similar to `Mesh` but skips a few data members that are not required. Same thing for other geometry types.\n\nPros:\n* No new complexity in ID management code.\n* Instances behave more like other geometries (one would have to add a `BakedInstances` struct).\n* More control over which data is (not) stored for baked data.\n* Independent versioning code for baked data.\n\nCons:\n* Leads to some more code duplication because a new way to serialize geometries has to be added.\n* Can reuse less existing code.\n\n## Option D: Use external file format and embedd that in the .blend file.\n\nWe also want to be able to store baked geometries outside of the .blend file. For that it's probably best to come up with a new file format that exactly suits our needs (also see #105251). This could potentially be implemented first. Then to store the baked geometries in the .blend file, we could just dump the external files into the .blend file (similar to how image files can be packed).\n\nPros:\n* Would solve storing baked geometries in the .blend file and outside in one go.\n* Does not add complexity to existing ID management, versioning and .blend IO code.\n* Feature parity between storing baked geometries externally or in the .blend file by default.\n\nCons:\n* Likely needs more new code than all the other options.\n\n-----\n\nI'm still undecided on which approach would work best in the short and long term. Feedback would be welcome.\n\n", "Exact Boolean with Incorrect Result - multiprecision/float round trips not exact\nOperating system: Windows 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.91.0 Beta dca36a8ec922\n\nAnother case, where the exact boolean does not work as expected. (Sorry @howardt, I had to break it. I have to admit, that I have not run into this problem in a real scene.)\nAgain, this manifests after applying the same difference operation several times.\n\n[boolean_rotated_box3.blend](boolean_rotated_box3.blend)\nLook at the scene.\nThe first run of the modifier works as expected, the second creates overlapping faces, the third removes most of the mesh.\nThis \"bug\" is very erratic, and if the transform of the objects is slightly changed, it does not occur.\n\nThis is what I see:\n\n\nThe expected behavior is that the second and third modifier do nothing.", "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", "Cycles: improve subsurface scattering for some meshes shapes\nIn cycles-x, the Christensen-Burley dipole approximation was fully replaced by random walk.\n\nHowever for some mesh shapes results are not as good, or could be improved regardless.\n* Self-intersection meshes give dark borders. Counting back/front facing intersections could help determine inside/outside better to avoid such artifacts.\n* Sharp corners \"glow\", which may be physically correct but is not necessarily desired. It may be possible to add user control with an option somehow, using some minimum throughput\n\nIf these can't be solved, we may consider adding back the dipole approximation, but since path splitting and the memory usage is a difficult fit for the new kernels we'd really like to avoid it.", "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`.", "boolean node in geometry nodes seems to work wrong\nOperating system: macOS-11.2.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15\n\nBroken: version: 3.0.0 Alpha\n\n\n\nI have made this node tree in geometry nodes and i am getting this result, which - for me - looks like a bug.\n\n", "Subdivision surface with circle curve issue. \nOperating system: Windows 11 Pro\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0\nWorked: (on 2.9 was working fine)\n\nCreating a mesh ring with curve circle and applying sub division serface, the modifier fails at two vertecies on the mesh. \n\nAdd curve -> circle -? edit mode -> select verticies -> E to extrude and S to apply size -> E to extrude on Z direction -> done\nObject Mode -> add modifier -> subdivision serface -> issue.\n[Issue with subdivision serface .blend](Issue_with_subdivision_serface_.blend)\n\n\n", "Regression: Bevel issue when its percent/absolute mode is operated on edge loop along sharp angle\nBroken: 2.91~4.0\nWorked: 2.90.2\n\nCaused by 48c484a22e0d105ed21a4f18b0cb455af6aac661\n\nIf bevel's percent and absolute modes are operated on an edge loop along sharp angle, the sharp angle part does not get beveled.\n\nTest file: [bevel_sharp.blend](https://projects.blender.orgattachment) ~~[bevel_issue_2.blend](attachment)~~\n\n### Test mesh\nEdge loop at the center has bevel weight of 1.0 and runs along a sharp angle.\n\n\n\nI'm using bevel modifier here for convenience but this also happens with edit mode bevel operator.\n\n| | 2.83.20 | 2.93.16 | 4.0 alpha 2023-06-26 `82d9eb09dbbe` |\n|--|--|--|--|\n| Percent mode |  |  |  |\n| Absolute mode | - | - |  |\n\nEdit: Reproduce:\n\n- Open the updated [bevel_sharp.blend](https://projects.blender.orgattachment)\n- Bevel\n- Select to Absolute/Percent mode and adjust depth\n- observe two cubes behaves differently \n" ]

[ "Account for curvature in curve to mesh node\nOperating system: Darwin-18.5.0-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: 2.90.0\n\nI used a curve as a bevel profile on another one with 90 degree angles but the result is not 90 degrees on the result\n\nplease see attached file\n[badBevel.blend](badBevel.blend)" ]

[ "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```", "Segfault on unregistering operator/menu with open props dialog.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92, 2.93\n\n\nWhen an operator currently has a `wm.props_dialog_(self)` open, unregistering it will cause a segfault.\n\nThis only seems to happen reliably when the module it's from has at least one `bpy.types.Menu` subclass that's also been registered.\n\nThe displayed values of property fields in the dialog will sometimes flicker and switch values with each other for a split second before the segfault.\n\n\n[InvokeSegfault.blend](InvokeSegfault.blend)\n\n1. Open the attached file.\n\n2. Invoke the operator from the 3DView toolbar.\n\n3. Use a system hotkey (E.G. `ALT`+`TAB`) to switch to the window with the text editor space while leaving the props dialog open.\n\n4. Run the script again from the text editor window.", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\n\n", "Blender Crash by doing 2d animations\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 500 Intel 4.5.0 - Build 31.0.101.2111\n\nBroken: version: 3.6.0\n\nWhenever I draw with a line, circle, arc, curve, interpolate, and box tool, my drawings disappear and reappear and then it suddenly crash.\n- 2D animation Draw Mode\n[\nPlease describe the exact steps needed to reproduce the issue]\n\n", "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", "Crash when sculpting with a texture, deleting the image of the texture and exiting sculpt mode\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: version: 3.4, 3.5, 3.6\nBroken: version: 3.3.3\nBroken: 3.1.0\nWorked: 3.0.1\nWorked: 2.93 LTS\n\nCaused by 9111ea78ac\n\nBlender crashes when a texture image is deleted and you exit sculpt mode.\n\nYou can test it inside the attached blend file. I basically just attached an image to a sculpting brush.\n\n1. Open the blend file below\n2. draw on the surface of the sphere\n3. delete the image inside the outliner\n4. exit sculpt mode\n\nCrash occurs because `item->image->runtime.cache_mutex` is null inside `BKE_image_pool_free`\n```\nStack trace:\nblender.exe :0x00007FF713D04C10 pthread_mutex_lock\nblender.exe :0x00007FF70E6EE880 BKE_image_pool_free\nblender.exe :0x00007FF70E6B5CF0 BKE_sculptsession_free\nblender.exe :0x00007FF70F1B67A0 ED_object_sculptmode_exit_ex\nblender.exe :0x00007FF70F1B85F0 sculpt_mode_toggle_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\nblender.exe :0x00007FF70E9528D0 wm_operator_call_internal\nblender.exe :0x00007FF70E955880 WM_operator_name_call_ptr\nblender.exe :0x00007FF70F171800 ED_object_mode_set_ex\nblender.exe :0x00007FF70F148710 object_mode_set_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\n```", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "Blender full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "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", "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", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "Rigidbody crash undoing while animation plays (which was started at frame 1 or below)\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[animation_john2.blend](animation_john2.blend)\n\nOperating system: Windows 10\nGraphics card: Nvidia 2070 Super\n\nWorked: -\n\nBlender crashes when object is rotated to a steep vertical angle and animation player is run.\n\nFor animation_john2.blend\n- Play Animation\n- Select a bone (could be any other operator as well I think)\n- Undo (this will also jump back to frame 0 -- where we started -- which is the important part, starting animation at frame 2 or higher does not result in the crash)\n- Redo\n\nRepeat until crash. Occurs between 2-5 repeats.\n\nAlso occurs at other similar high angles.", "Text editor undo system, undo step grouping behavior\nThis design task is to resolve how to handle undo steps in the text editor (and possible text fields in the future).\n\nPossible options:\n\n- Keep current behavior - each key is a single unto step.\n- Group by character type / action.\n- Group using a timer, so characters typed in quick succession are put into a single undo step.\n\n```\nThe timer can be a preference, so users who type slowly or prefer to have the current behavior can either increase the timer or set it to zero.\n```\n\n\nNote:\n\n- Using a timer may be unpredictable especially when the users typing speed hovers around the limit - undo groupings may seem unpredictable.\n- Using whole words may have the disadvantage that large blocks get undone (not fine grained enough).\n- Having grouped undo makes it difficult to test undo/redo *(developer detail, even so - noting it here).*\n\n----\n\n\n**Proposal**\n\n- Undo grouping will only be done for single character insertion/removal.\n- Undo wont group edits separated by cursor motion.\n- Word level grouping has the same delimiters as pressing Ctrl-Left/Right,\n```\nthis means whitespace/punctuation & alpha-numeric characters will be undone/redone in blocks.\n```\n\n- Have a preference for the text editor to group undo by words or characters.\n *(this allows undo testing code to behave predictably).*\n\n----\n\nMaybe there are other options, @WilliamReynish we discussed this a while ago.\n\nCreating because [D6283: Add undo grouped to Insert and Delete text operator](D6283) was submitted which.", "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)" ]

[ "Segmentation fault in `ED_info_stats_string` during redo\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.0\nWorked: N/A\n\nI'm experiencing consistent crashes when redoing rapidly, i.e. when holding down Command + Shift + Z. This is on macOS 10.15.5 with Blender 2.83. Attached is the crash log from the most recent crash. It might be worth mentioning that I've increased the undo buffer size in the preferences from the default of 32 actions to 128 actions.[blender_2_83_redo_crash.txt](blender_2_83_redo_crash.txt)\n\n- Open Blender\n- holding down Command + Shift + Z\n", "Duplicate Object, then Linked Duplicate Object, then Repeat Last Tool causes crash\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.20\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83.0\n\nCrash when redoing Duplicate Linked several times in a row\n[ShiftD AltD Crash.mkv](ShiftD_AltD_Crash.mkv)\n\n- On a new scene, with default cube, Shift D (move and confirm),\n- then Alt D (move and confirm)\n- then Shift R R R R ... repeatedly until it crashes\n\n\n" ]

[ "Color attributes difference between vertexpaint and sculpt modes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Beta\n\nColor attributes difference between vertexpaint and sculpt modes\n\n[vertex_paint_geo_nodes.blend](vertex_paint_geo_nodes.blend)\n\n- open the included blend file and try to remove the instance objects from the geo nodes (The objects are linked to a color attribute. Using white color to add the objects and black to remove them)\n- when using vertexpaint mode, several pure black strokes are required\n- when using sculptmode paint tool, trees vanish on the first black stroke stroke- when i open blender 3.1 it works fine. \n\n\n\n", "Serious problems with visibility when linking a character\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3\n\n\nwhen linking a collection containing a character model, rig, etc., oddities occur with the visibility of the armature: when the overlays are turned off/ on, the armature is not displayed until some event occurs (this bug applies to the file where the model is located). undo ignores hiding bones (scene with linked and override character) for clarity, two animation files will be attached. in both, sometimes both of these bugs occur, while it is absolutely unpredictable\n[2022-09-16 02-20-35.mp4](2022-09-16_02-20-35.mp4)\n\n[broken_7.zip](broken_7.zip)\n\nfile with character in broken_7/stalker/\nfiles with animation in broken_7/3d_projects/tests/animation/\n", "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.", "LOAD UI - Checkbox Status Ignored\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked: (Unknown)\n\n\nWhen opening a file with a UI that does not match the default UI, the file's internal UI is loaded regardless of the LOAD UI checkbox being marked \"OFF\". More specifically, the MODE of a workspace is not respected and uses what ever mode is used within the file.\n\nIE, the default is \"Object\", while a scene can override it to something else - in this example, Texture Paint.\n\nAs the mode is part of the workspace setting, it should not be overriding when the scene is opened.\n\n\n\n\nSee screenshots.", "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", "Weight painting with Zero Weights overlay method Active, once painted vertices remains blue\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.33\n\nBroken: version: 3.5.0 Alpha\n\nI don't think it has ever worked.\n\n\nWhen you choose the Zero Weights overlay method Active, then vertices with a weight of 0 are displayed as black. But once painted vertices remains blue when you paint with a value of 0 across it. You cannot paint them to zero again. Not without lots of tries. I managed to get it back to black once after five minutes permanently painting across it.\n\n\n- Switch to weight paint\n- In the Viewport Overlay settings change the Zero Weights behaviour to Active.\n- Paint a vertice \n- Now change the value back to zero and try to paint it back to zero again. So that it displays black like the other vertices with a weight of zero.\n\nSometimes, in very rare cases, i really managed to paint it back to black again. And i can misuse the Gradient tool here, which is a bit more reliable. But also this method needs lots of tries. Which made me report this as a bug then. I would expect that i can paint it to zero with a few strokes like i can paint it to 1.\n\n\n\n[2022-11-18 18-43-59.mp4](2022-11-18_18-43-59.mp4)\n\n\n", "Texture Paint tools lead to incorrect colors on bright HDR textures in 3D\nOperating system: Linux-5.12.0-19.1-liquorix-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 5700 (NAVI10, DRM 3.40.0, 5.12.0-19.1-liquorix-amd64, LLVM 11.0.0) AMD 4.6 (Core Profile) Mesa 21.0.1\n\nBroken: version: 2.93.0\nBroken: version: 3.0.0 Alpha\nWorked: N/A\n\nI am trying to touch up an HDR lightmap using the Texture Paint mode.\nAttempting to soften, smear or clone HDR images in 3D view in Texture Paint mode will lead to pixel values being clamped up to 1.0, unexpectedly removing bright spots. 2D view is not affected and the tools behave as expected. See video:\n[blendertexpaint.mp4](blendertexpaint.mp4)\n\nI have found that this line is responsible for this issue. Commenting it out fixes the problem.\nimageprocess.c#l219\nLine 219: `clamp_v4(outF, 0.0f, 1.0f);`\n\nI am unsure about the purpose of this line, or any unintended consequences of removing it. Someone else needs to take a look.\n\n1. Assign an HDR texture to an object's material.\n2. Enter Texture Paint mode\n3. Attempt to use the Soften, Smear or Clone tools to edit the texture in 3D view, in spots where the value of a pixel's R, G or B component is greater than 1.0\n4. The bright spots will unexpectedly become dark as they are touched by the tools.\n[Sample.blend](Sample.blend)\n\n", "Mirror painting error\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "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 !", "3D Cursor & Origin overlays should be grayed out if hidden by current mode/tool\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\nThe 3D Cursor and Origins are not displayed in painting modes as well as sculpt mode. \nThe overlay popover does not give feedback on this though.\n\n\nThe overlays should be grayed out in the modes and tools where it is hidden. \nIdeally there should be exceptions to this rule, like while the 3D Cursor is transformed (already implemented) and when the current Tool is using it (Annotation Tools).", "Sound stops playing after undo\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.9.22\n\nLinux has this issue as well, no problem on windows.\n\nBroken: 2.92.0 Alpha\n\nSound stops playing after undoing all actions back to original file state.\n\n[#84052.blend](T84052.blend)\n\n- Open file\n- Select strip\n- Undo selection, so file is in original state\n- Play animation\n\nThere will be no sound.\n", "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "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.", "Cycles: sRGB texture compression happens after interpolation \nBroken: 2.81\n\nCycles does sRGB->linear texture conversion after texture interpolation instead of before. This leads to incorrect results.\n\nExample scene is attached. Two squares with a fine checkerboard texture, one with linear interpolation, the other with closest interpolation.\n\nExpected result: Both textures should render to an identical shade of gray. When switching the texture color space to \"linear\" instead of \"sRGB\", the result should not change as the texture contains only pure black and white pixels.\nActual result: The textures show different shades of gray. Switching the color space changes the result.\n[checkerboard.blend](checkerboard.blend)\n\n", "Incorrect order in undo stack when switching between Object Mode and Edit Mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83 (sub 10)\nWorked: I don't know, I am a new user\n\n**Expected Behavior**\nWhen you undo, you expect to undo the last thing you did (FIFO).\n\nCurrently, if I am in Edit Mode and I change the scale of an object in the \"Transform\" panel on the right, and then undo immediately, it will undo all changes I did in Edit Mode and only then, undo the scale change even though I just did the scale change.\nIn other words, for some reason the undo stack in blender prioritizes things you didn't do in the transform panel when you are in Edit Mode even if these other changes aren't the most recent ones.\n\nFile > New > General\nA cube should appear in the center\nUse Tab to go into edit mode\n(1) Do some changes like moving vertices\n(2) Now change the scale of the object in the transform panel on the right\nNow hit Ctrl+Z to undo the last change\n\nIt will likely undo (1) the \"Edit Mode\" change instead of (2) the \"Transform Panel\" change.\nIf you keep doing Ctrl + Z it will eventually undo the transform panel change after undoing all the \"Edit Mode\" changes." ]

[ "Eevee Shading Error- Object's go completely black if they have a normal map.\nOperating system:Wn10\nGraphics card:gtx970\n\n2.8 2019-02-22\n\n\n**Objects shading breaks if duplicated in wireframe mode(must have a normal map node)**\n\n**Add a material to an object, set shader to 'Principled BSDF', Set normal to 'Normal Map', press shift+z, select object, alt+d to duplicate, press shift+z. the object should now be black. To fix, switch shading mode in the top right and then switch back to eevee.**\n\nYou don't need to actually use a normal map, just setting up the material like so suffices.\n\n " ]

[ "Eevee: Unknown bug when just create first shader \nStep to reproduce an issue (or bug?):\n1. Run latest Blender v3.4alpha (Experimental build) with Eevee Next integrated.\n2. Create scene with just one Cube.\n3. Go to Properties > Material panel > Create New material.\n4. Boom! Blender shut down imidetily.", "Crash when loading a geometry nodes asset into itself\nOperating system: Win 11\nGraphics card: 2070\n\nBroken: 3.4, 4.0\nWorked: none\n\nWhen working on an geometry nodes asset in an asset library - if you search for the name and adding it to the graph it causes a crash. \n\nDrag n drop from the asset browser behaves correctly here - so I think its just the node search code which is missing the check for self referencing.\n\n1. Download the blend file.\n2. Put into a folder.\n3. Add folder as asset library in prefs -> file paths -> asset libraries.\n4. Open the blend file from that folder.\n5. Go to the geometry node graph (should be open already).\n6. `Shift` + `A` to add new nodes.\n6. Search \"noop\" and press enter.\n\n", "Math with Nodes\nCurrently, there are two main math nodes: \"[Float] Math\" and \"Vector Math\". The current workflow for using these is that first the correct math node has to be inserted, and then the correct operation has to be selected. This approach has two problems:\n- It forces the user to do two steps for an operation that should only take a single step (e.g. \"insert multiply node\").\n- \"Math\" is a very generic term. When more operations are added, it becomes more and more unclear which should be added to the math node and which belong to another node. And the user has to remember that.\n\nA more scalable approach is to remove the \"Math\" node entirely and create individual nodes for different operations. For example, there will be an \"Add\", a \"Subtract\" and a \"Dot Product\" node. These new nodes can adapt to the data types that are connected to them.\n\nThis is not a change we have to do in the short term, but in the long run it is the better solution in my opinion. Especially as we get more types and operations.", "Crash with lineArt modifier and Armature\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nExperienced with 2.93.2\n\nHaving a line art object in the scene applied to an object 'A' when there is an armature on object 'B' makes blender very unstable. A simple scroll in the timeline will crash instantly.\n\n\nIn the attached file, what I did : \n- Create a cube, subdivided along Y, add a simple armature, keyframe it with a simple motion.\n- Duplicate the cube, apply the armature.\n- Select the second cube, shift-a -> Object Line Art\nFrom there : \n- Scroll the timeline... Crash.\n\nIf I delete the animated cube, scrolling works fine. Disabling it in viewport as well.\n\n\nI also tried adding a simple cube, instead of duplicating the initial \"armatured\" cube, and adding the Object Line Art to it, but the same crash occurs.\n\n[LineArtCrash.blend](LineArtCrash.blend)\n\n", "Shader node float precision issue cause different results on CPU and GPU\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\nCPU: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz\n\nBroken: version: 2.80rc2 (2.80 (sub 74))\n\nWhen rendering a mandelbulb volumetric thing on cycles using CPU and GPU, the two have very different ideas on how the scene should look like, making the individual tiles clearly visible. \n\n**Render**\n \n(most tiles are GPU-rendered, note the stray red CPU-rendered tile to the left)\n\n**Blend**\n[mandelbrot.blend](mandelbrot.blend)\n\n**Potentially useful information**\n* #50193 may be the same bug; I opened a new one because that bug doesn't report differences within a single frame, and is from 2016.\n* Since most of this object is endless math nodes, it may be some sort of floating-point thing that works differently on CPUs and GPUs. \n* I was following this tutorial: watch?v=WSQFt1Nruns\n* I noticed that some operations for which I expected single inputs (namely the sines) had two inputs. In the tutorial, the dude said the second input doesn't do anything, but then, that's from the alpha. Maybe taking a 0.5th sine of a value does something strange?", "Correct link is shown as invalid\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIn the composer, after some actions, the link is displayed as incorrect, although there is no reason for this.\n\n**Exact steps for others to reproduce the error** \n\n0. Factory settings file (optional).\n1. Switch render engine to Cycles.\n2. Enable any `Scene > ViewLayer > Passes`. For example, this would be `... > Data > UV`.\n3. Enable the compositing nodes and connect the new socket to the \"Composite\" node.\n4. Switch render engine to Eevee.\n5. Make a Render.\n6. Switch render engine to Cycles.\n\n\n\n", "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", "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", "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", "Regression: Crash with boolean modifier\nOperating system: Fedora Linux 36 (Workstation Edition)\nGraphics card: Nvidia Geforce RTX 3080\n\nBroken: 3.2.1, 3.3 alpha\nWorked: 3.1\n\nCrash with boolean modifier\n\n- Open .blend file\n- In boolean modifier tab -> select `dot cutter` for boolean operation\n[yin_yang-v1.blend](yin_yang-v1.blend)\noriginal file: [F13292564](yin_yang.blend)", "Realtime compositor: Texture node output textures with artifacts\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nTexture node support was introduced in 151a53110c\n\nIn realtime compositor, Texture node outputs textures with artifacts.\n\n\n\nIt happens with most procedural textures I tested. This does not happen when a custom image is used, or when Blend texture is connected from the Value output (instead of the Color output) of the node. (With other textures it happens with both outputs.)\n\nThis does not happen when running Blender with a single thread (`blender -t 1`)\n\nFile for quick test: [TextureNodeTest.blend](attachment)\n\n", "Design: Shading: Extend Clamp and Map Range nodes to work with Vectors\nI'd like to make these nodes work with vector inputs and outputs.\n\nIt's unclear to me as the the best way of doing this. \n\n\n\nSome options:\n\n - **Separate Nodes** : Create separate versions of these nodes with Vector sockets.\n\n - **Dynamic** : Use a dynamic socket. This is better from a UX perspective but how do we show this? For these two nodes, they are pretty pointless without a value input so the edit control could be hidden. The node then operates accordingly depending on the input link. \n\n\n\n- **Mode Switch** : Add vector input and output sockets and add a mode switch to hide the unwanted input socket. \n\n- **Double Sockets** : Add vector input and output sockets and depending what is connected. For vector only input, `Vector` > `Float & Vector`. For float only input, `Float` > `Float & Vector`. If both inputs are connected do `Float` > `Float` and `Vector` > `Vector`.\n\nFor the combined cases, the node would output and show both Value and Vector.\n\n\n\n\n\n\n\n", "Behavior for mathutils.Vector.rotation_difference when vectors are aligned\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001\n\nBroken: version: 2.93.0 Alpha\nWorked: Never? (tested on 2.79)\n\n```\nimport bpy\nfrom mathutils import Vector\n\nvector_a = Vector((0.0,-1.0,0.0))\nvector_b = Vector((0.0, 1.01,0.0))\nquat = vector_a.rotation_difference(vector_b)\n\nobj = bpy.context.object\nobj.rotation_quaternion = quat\n```\nIn the `rotation_difference` method shown in the script above, when the angle between two vectors is 180° or close, the resulting Quaternion, although pointing in the correct direction, also rotates on another axis.\n\n- Open attached file\n- Run script\nNote that the object did not rotate exactly 180° on one axis\n[rotation_difference_bug.blend](rotation_difference_bug.blend)\n\n", "Eevee: math wrap and floor, AMD Driver precision issues\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.1 27.20.21003.1028\n\nBroken: version: 2.92.0\nBlender 2.83 LTS has same problem\n\nMath and Vector Wrap give different results for Eevee and Cycles, also doesn't swap min max, when max is less than min\n\n\n**More info**\nThis is important for an upcoming Shader Nodes patch that relies on wrap operation\nalso for shader setups that rely on this\n\nother people tested this, the problem seems to appear only on AMD Windows\n\n\nWhen Using -3 as Min for wrap, and 3 as max, some values give different results in Eevee than in Cycles\nFloor operation is probably the cause of this\nthis node setup \n\n\nCycles\n\n\nEevee\n\n\n[eevee_math_wrap_different_from_cycles.blend](eevee_math_wrap_different_from_cycles.blend)\n\n", "Generated Texture Coordinate Node In Shader Creates Broken Pattern Upon Applying Subdivision After Armature Modifier \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.1\nWorked: Blender 3.2\n\nWhen I use the Generated value of a Texture Coordinate node, and have a modifier stack with an Armature above and a Subdivision below, it creates a really weird result [broke.blend](broke.blend)\n\n\n - Check the .blend file and simply activate the Subdivision modifier on the model\n\n\n\n\n" ]

[ "Texture Coordinates Node output crash in blender 2.8 in Lookdev Mode even with Cycles renderer.\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 780 OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.113\n\n\nBroken: version: 2.80 (sub 55)\nWorked: (optional)\n\n\nTexture Coordinates Node output crashes blender 2.8 in Lookdev Mode even with Cycles renderer.\nForced to use cycles render preview and never swap back to lookdev, making the texture coordinates node unusable.\n\n- Select Cycles renderer and cycles preview mode\n- Keep default cube\n- Edit cube shading\n- Add Image Texture, Ctrl+T, select object in the Object dropdown on the Texture Coordinates node.\n- Switch to Lookdev or Eevee rendering mode\n- > Crash " ]

[ "Line Art doesn't exclude object's instanced by geo node\nOperating system: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.3.1\nBroken: version: 3.5.0 Alpha\n\nCollection Line Art includes instances that are distribute my geometry nodes, even if that object is not within the Line Art target collection.\n\n\n[Line_art_Geo_Nodes_instance_bug.blend](Line_art_Geo_Nodes_instance_bug.blend)\n**Exact steps for others to reproduce with example file**\n1. Open Attached File \n2. Observe Line Art is on objects outside target collection\n\n**Exact steps for others to reproduce the error from Startup**\n1. Distribute Objects from a collection with Geo-Nodes\n2. Create a second collection with a Line Art Target Object only\n3. Add Collection Line Art and target collection from step 2\n4. Line Art will be drawn on Geo-Nodes instanced objects\n\n\n\n", "Frame counter while rendering does not respect blender's DPI setting\n4K screen, Windows 10, GEFORCE 960M\n\nBroken: bac1279\n\nThe cursor frame counter that displays while rendering is minuscule on a 4K screen, regardless of the DPI setting in Blender", "Rotate drawing canvas (viewport)\nThis is a requested feature for all 2D artists, texture painters and sculptors.\nWe need a way of rotating the full viewport as other softwares do, because sometimes is easier draw from left to right instead of drawing vertical, especially for lines.\n\nThere are some add-ons already for that, but these are partiall solutions and only works in some situations. We need a more general solution.\n\nThis is general problem for any mode that need to use a pen for drawing.", "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", "Constrain axis always draws on top [covers mesh in unfavorable ways]\nThe mesh outline is not visible when extruding or moving along the axes. The axes overlap the faces of the mesh themselves, and because of this, it is not convenient to precisely position the extruded faces.\nIt exists on all versions of the 2.8x blender.\n\nTo repeat the problem, you can select an edge in the editing mode and simply drag along the y axis. In this case, the contour will not be visible by how much it is moved from its actual position.\n\n\n\nWith the same action in 2.79, I see black the contours of the mesh as far as it changes when moving.\nBring it back as it was in 2.79", "GPencil: Stroke not working with Holdout\nOperating system: Windows 10\nGraphics card: GeForce GTX 970\n\nBroken: 2.82a, as found on the splash screen\nWorked: Never\n\nSetting a collection as holdout in view layer options in cycles works as expected on grease pencil objects in the viewport render preview, but does not work on grease pencil objects when rendering. The entire grease pencil object is visible in the renders, whereas in the viewport render preview the parts of the grease pencil obscured by foreground objects set to holdout is alpha. \n\nCreate a grease pencil empty behind the startup cube. \nDraw some stuff. \nPut the startup cube in a collection and set the engine to cycles. \nFrom the view layers options for the new collection containing the startup cube, set it to holdout. \nTurn on render preview from the viewport shading options. Notice that the cube is invisible, along with the parts of the grease pencil that had been obscured by the cube.\nPress F12\nNotice in the rendered image that all of the grease pencil is visible, even the parts we had expected to be alpha masked from the startup cube holdout.\n\nSee the attached blend file.\n[HoldoutTrouble.blend](HoldoutTrouble.blend)\n", "Cursor's icon doesn't update correctly when going from panel to scene\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.2.0 Alpha\nWorked: Never (introduced/discovered with new design for 2.8 series)\n\nThe cursor icon doesn't update properly when returning it to the scene fast enough after tweaking in panels, and on it's way passing over text panels.\n\n- Go edit mode and select a vertice/edge/face to activate the transform panel\n- Place the cursor in the panel where its icon displays the OS default one\n- Move the cursor fast enough onto the scene. On its way pass over text panels.\n- The cursor icon is the default's one, not the cross as it should.\nSee the .gif for visual explanation:\n", "Python 4.0 delayed annotation evaluation (from __future__ import annotations )\n\n\nAdding\n`from __future__ import annotations`\nat the top of a python file makes the properties annotations of operators non-existent.\n\nThis will be enabled by default in Python 4.0, see: pep-0563\n\nCreate and enable this simple demo addon:\n\n```\nfrom __future__ import annotations # this line makes the line 30 throw an error, because the property some_prop of BUGANNOTATIONS_OT_some_op will no longer exist\n\nbl_info = {\n\t'name': 'Bug annotations with __future__',\n\t'author': 'Arnold, Arnaud Couturier, piiichan ([email protected])',\n\t'version': (1, 0, 0),\n\t'blender': (2, 80, 0),\n\t'location': 'scene options',\n\t'category': 'Scene',\n}\n\nimport bpy\n\n\nclass BUGANNOTATIONS_OT_some_op(bpy.types.Operator):\n\tbl_idname = 'scene.hey'\n\tbl_label = 'An operator'\n\tsome_prop: bpy.props.StringProperty(name='Hello', default='Default value')\n\n\nclass BUGANNOTATIONS_PT_some_panel(bpy.types.Panel):\n\tbl_region_type = 'WINDOW'\n\tbl_space_type = 'PROPERTIES'\n\tbl_context = 'scene'\n\tbl_options = {'DEFAULT_CLOSED'}\n\tbl_label = 'Bug annotations'\n\n\tdef draw(self, context):\n\t\top = self.layout.operator(BUGANNOTATIONS_OT_some_op.bl_idname)\n\t\tprint(op.some_prop)\n\n\ndef register():\n\tbpy.utils.register_class(BUGANNOTATIONS_OT_some_op)\n\tbpy.utils.register_class(BUGANNOTATIONS_PT_some_panel)\n\n\ndef unregister():\n\tbpy.utils.unregister_class(BUGANNOTATIONS_PT_some_panel)\n\tbpy.utils.unregister_class(BUGANNOTATIONS_OT_some_op)\n```\n\nthen go in the scene settings, a new panel appears. Show the button inside, and look into the console, you'll see that some_prop from the operator doesn't exist if __future__ is imported.\n\n", "Mesh selection in viewport broken with scenes using a high number of models\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.0 Alpha\nWorked: Never (2.8+)\nWe are working on a commercial project with imported SketchUp scenes using 55K+ models and running more and more into broken scenes with selection issues in the viewport.\n\n`What we figured out so far:`\n- Selection in the outliner works\n- Some models can be selected by a point and click\n- Other models can't be selected by a point and click\n- Models at a different location will be selected by a point and click and not at the mouse pointer location\n- Box select is messed up and doesn't work overall (selects just parts of the model or fails completely)\n- Lasso select seems to work as intended\n- Circle select seems to work as intended (but can freeze Blender)\n- Some random models can cause a hard crash of Blender when selecting them by a point and click\n**When we delete all my other scenes in the Blender file and purge the data the selection modes work again.**\n\n\n\n\n[T104008_Selection_Bug_350_v006_CUBES_REPORT.blend](T104008_Selection_Bug_350_v006_CUBES_REPORT.blend)\n\nTry to select cubes.\n\n", "Texture painting with mirroring and viewport clipping does not mirror\nOperating system: Linux-5.8.4-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: never, 2.79 also did not do this\n\nTexture painting with mirroring and viewport clipping does not mirror\n\n[texturepaint_mirror_clipping.blend](texturepaint_mirror_clipping.blend)\n- Open .blend\n- Do a stroke on the right side --> updates on the left as well because x-mirroring is turned ON\n- (Undo)\n- {key Alt B} a clipping region in the viewport\n- Do a stroke again on the right side --> updates on the right side\n- {key Alt B} to clear the clipping region in the viewport, see no updates have taken place on the clipped left side\n\nExpected: stroke should update the clipped area as well [as we do for vertexpaint, weightpaint and sculpting], everything else would be inconsistent\n\n", "Viewport: Texture limit size generates artifacts during painting\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nWhen limit size is lesser than the actual image size, this will result in artifacts at paint region.\n\n- Open attached file\n- Change Texture limit size to 2k or less (`Edit > Preferences > Viewport > Textures > Limit size`\n- Paint the plane.\n", "Drawing of pose markers does not take NLA time mapping into account\nOperating system: Linux-5.11.0-49-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.2.0 Alpha, branch: `master`, hash: `d6e7241237`\nWorked: don't think it ever workerd\n\nShifting an Action on the NLA, then going into tweak mode to edit it, shows the keyframes shifted in the animation editors. The action's pose markers are still in their absolute position.\n\n\n\nThe pose markers should align with the 2nd, 3rd, and 4th keyframe.\n\n- Open the attached file, look at the pose markers.\n- Drag the action in the NLA editor, and see the keys moving while the pose markers stay put.\n\n[[D14176](D14176)-select-markers.blend](https://archive.blender.org/developer/F13001132/D14176-select-markers.blend)\n\n**Context & Relevance**\n\nThese \"pose\" markers originated from the old, now obsolete, pose library. However, regardless of the status of that library, I've heard the desire to have Action-scoped markers (so independent of scene time), and the pose markers would fit that need quite well. The only thing that has to be done to make this a reality is a rename (from \"pose marker\" to \"action marker\") and some UI cleanup. Fixing this bug is a good start.\n\nMarked as low-prio because the new purpose for pose markers isn't that official yet.\n\n**Note:** Be sure to test the `marker.select_leftright` operator as well (f1ae6952a8) after addressing this issue.\n", "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", "Projected falloff in sculpt mode displaces vertices in wrong direction\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nThe stroke is incorrectly applied for some vertices when using projected falloff\n\n[bug.blend](bug.blend)\n\nUse a projected falloff and make a stroke using a line stroke type or a curve type\n\n\n\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)" ]

[ "Grease Pencils Strokes and Annotations are Broken/Invisible\nOperating system: Windows-7, 10, Linux\nGraphics card: NVIDIA, Intel\n\nBroken: version: 2.83 (sub 2)\n\nGrease Pencils / Annotations are in the file but are invisible as though you have them hidden/disabled from viewport/overlays.\nThe points can be seen in Edit/Sculpt/Weight Paint, but the actual strokes are only visible on Annotations, while you're drawing them.\n\nI got this bug where sometimes the annotation will flip out and be visible and stick to the viewport but otherwise, nothing.\n[2020-02-11 22-03-17.mp4](2020-02-11_22-03-17.mp4)\n" ]

[ "Crash when deleting one rigidbody from constraint during simulation\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\nBroken: master branch\nWorked: Don't know if it ever worked\n\nDeleting one rigidbody that is part of a constraint during simulation causes a crash.\n\n**Steps to Reproduce**\n- Add two cubes to a scene. Add a rigidbody to both cubes.\n- Add an empty object to the scene. Add a fixed rigidbody constraint to the cube. Set the cubes as the first and second object in the constraint.\n- Play the simulation for a few frames and then pause the simulation.\n- Delete either cube, then continue playing the simulation.\n- Crash", "Smoke and Fire simulation bug\nOperating system: Mac osx 10.15.6\nGraphics card: AMD Radeon Pro 5500M 8 GB\nIntel UHD Graphics 630 1536 MB\n\nBroken: 2.90.0 (202-08-31)\n\n\nBlender crashes while trying to bake a fire + smoke simulation in 128 resolution divisions... Sometimes it works. Mostly it doesn't.\n\nAttaching the file.\n\n[Blender Bug copy.rtf](Blender_Bug_copy.rtf)\n\n[fire.blend](fire.blend)", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "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", "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", "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)", "Segfault in CustomData_blend_read\nOperating system: Debian Linux, Stable\nGraphics card: GTX970\n\nBroken: 3.6.0 Alpha, branch: main (modified), commit date: 2023-04-05 18:55, hash: 92c9c1d4003e, type: Release\nWorked: Unsure. Old blend I loaded and worked on for a while. Errors on open now.\n\nSegfault on load.\n\n1. Load blend, or open blender and load blend\n\n(No idea what the gvfs error is.)\n```\nFailed to open dir (No such file or directory): /run/user/6001/gvfs/\n[New Thread 0x7fffe3ae9700 (LWP 2310937)]\n...\n[New Thread 0x7fffdb9fe700 (LWP 2310945)]\nRead blend: \"/tmp/segfault.blend\"\n\nThread 1 \"blender\" received signal SIGSEGV, Segmentation fault.\n0x0000000001009af9 in CustomData_blend_read (reader=0x7fffffffd498, data=0x7fffd9c471f0, \n count=5002)\n at /opt/src/blender-git/blender/source/blender/blenkernel/intern/customdata.cc:5194\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n(gdb) l\n5189\n5190 int i = 0;\n5191 while (i < data->totlayer) {\n5192 CustomDataLayer *layer = &data->layers[i];\n5193\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n5195 layer->flag &= ~CD_FLAG_IN_MEMORY;\n5196 }\n5197\n5198 layer->flag &= ~CD_FLAG_NOFREE;\n(gdb)\n```\n\n", "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", "Blender 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\n", "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)", "[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", "Particle Edit mode for non hair particles - 2 Crashes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n\nParticle Edit: 2 Crashes\n\nParticle Edit: 2 Crashes\n\n- Open the blender file and click on the buttons \"Particle select and display point\"\n- Crash 1 (Screenshot)\n\n- Open the blender file and click on the tool \"Weight\" and click into the particles\n- Crash 2 (Screenshot)\n\n- Also had a crash with \"Puff\" \n- file not included\n\n- There are some tools that do nothing while others work\n- User gets no feedback / error message but give no feedback\n\n\n\n[2019-05-19-particle-edit-crash.blend](2019-05-19-particle-edit-crash.blend)\n\n", "Intermittent Segfault When Programmatically Creating Node Group\nThere have been intermittent crashes plaguing some of my addons. I think I have narrowed it down to creating node groups using the Python API. Specifically, to connecting something to a new node output.\n\nEnclosed [ldo_node_crash.py](ldo_node_crash.py) is a simple script that seems to reliably reproduce the problem for me; I hope it does for you, too. Open it in, or paste it into, Blender’s text editor, and run with ALT-P. I set the loop to run for 10 iterations, but for me, so far, it has always crashed before that.\n\nI am currently normally running Blender 2.82 on Debian Unstable AMD64; I tried a Blender build from the latest master branch, and the crash happens there, too. The backtrace looks like this:\n\n```\nblender-build-latest-debug/bin/blender(BLI_system_backtrace+0x26) [0x8257e79]\nblender-build-latest-debug/bin/blender() [0x2a09cfc]\nblender-build-latest-debug/bin/blender() [0x2a09efc]\n/lib/x86_64-linux-gnu/libc.so.6(+0x3b7e0) [0x7f5c97ff07e0]\nblender-build-latest-debug/bin/blender() [0x3919d1c]\nblender-build-latest-debug/bin/blender() [0x3919e13]\nblender-build-latest-debug/bin/blender(node_connected_to_output+0xf6) [0x391a0a6]\nblender-build-latest-debug/bin/blender(ED_node_tag_update_nodetree+0x41) [0x390df93]\nblender-build-latest-debug/bin/blender() [0x321f7c6]\nblender-build-latest-debug/bin/blender(NodeLinks_new_call+0x98) [0x323b5c9]\nblender-build-latest-debug/bin/blender(RNA_function_call+0x47) [0x3159a88]\nblender-build-latest-debug/bin/blender() [0x334374e]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyObject_FastCallKeywords+0xd7) [0x7f5c9890c887]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(+0x6dfc3) [0x7f5c9871bfc3]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x68a2) [0x7f5c98722c42]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x92d) [0x7f5c988443dd]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(PyEval_EvalCodeEx+0x3e) [0x7f5c9884465e]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(PyEval_EvalCode+0x1b) [0x7f5c98844e8b]\nblender-build-latest-debug/bin/blender() [0x333463c]\nblender-build-latest-debug/bin/blender(BPY_execute_text+0x39) [0x33348cc]\nblender-build-latest-debug/bin/blender() [0x3969d26]\nblender-build-latest-debug/bin/blender() [0x3969dfb]\nblender-build-latest-debug/bin/blender() [0x2ce7313]\n```", "Crash 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)", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n" ]

[ "Crash on STL import. Python library not found\nOperating system: Fedora 33\nGraphics card: NVIDIA Geforce 1030\n\nBroken: (Blender 2.90.1, )\nWorked: (Blender 2.80 )\n\nImport of an STL file crashes blender.\n\nError reported;\n\n> # Blender 2.90.1, Commit date: 1970-01-01 00:00, Hash unknown\n> bpy.ops.object.delete(use_global=False, confirm=False) # Operator\n> Deleted 1 object(s) # Info\n> bpy.context.space_data.bookmarks_active = 0 # Property\n> bpy.context.space_data.bookmarks_active = 1 # Property\n> \n> # backtrace\n> blender(BLI_system_backtrace+0x33) [0x55c02df3f1a3]\n> blender(+0xcef6c3) [0x55c02c0e86c3]\n> /lib64/libc.so.6(+0x3dc50) [0x7fedd80cac50]\n> /lib64/libpython3.9.so.1.0(PyEval_ReleaseLock+0x15) [0x7fedd88ccfc9]\n> blender(+0x127a90d) [0x55c02c67390d]\n> blender(+0x13c4def) [0x55c02c7bddef]\n> /lib64/libpython3.9.so.1.0(_PyObject_MakeTpCall+0x7f) [0x7fedd891a8df]\n> /lib64/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x583f) [0x7fedd891760f]\n> /lib64/libpython3.9.so.1.0(+0x1154bb) [0x7fedd891f4bb]\n> /lib64/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x4efe) [0x7fedd8916cce]\n> /lib64/libpython3.9.so.1.0(+0x106e81) [0x7fedd8910e81]\n> /lib64/libpython3.9.so.1.0(_PyFunction_Vectorcall+0xe6) [0x7fedd891f206]\n> /lib64/libpython3.9.so.1.0(_PyObject_FastCallDictTstate+0xd2) [0x7fedd891a462]\n> /lib64/libpython3.9.so.1.0(_PyObject_Call_Prepend+0x68) [0x7fedd8926b48]\n> /lib64/libpython3.9.so.1.0(+0x1b99ba) [0x7fedd89c39ba]\n> /lib64/libpython3.9.so.1.0(_PyObject_MakeTpCall+0x16b) [0x7fedd891a9cb]\n> /lib64/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x5e5f) [0x7fedd8917c2f]\n> /lib64/libpython3.9.so.1.0(+0x107439) [0x7fedd8911439]\n> /lib64/libpython3.9.so.1.0(_PyFunction_Vectorcall+0xe6) [0x7fedd891f206]\n> blender(+0x13dcdf2) [0x55c02c7d5df2]\n> blender(+0x13b0bb8) [0x55c02c7a9bb8]\n> blender(+0xfcb583) [0x55c02c3c4583]\n> blender(+0xfcf75a) [0x55c02c3c875a]\n> blender(+0xfcfb6c) [0x55c02c3c8b6c]\n> blender(wm_event_do_handlers+0x5fe) [0x55c02c3c954e]\n> blender(WM_main+0x20) [0x55c02c3cb280]\n> blender(main+0x31e) [0x55c02c0883de]\n> /lib64/libc.so.6(__libc_start_main+0xf2) [0x7fedd80b51a2]\n> blender(_start+0x2e) [0x55c02c0c6a7e]\n> \n> # Python backtrace\n> File \"/usr/share/blender/2.90/scripts/modules/bpy/ops.py\", line 159 in _view_layer_update\n> File \"/usr/share/blender/2.90/scripts/modules/bpy/ops.py\", line 195 in __call__\n> File \"/usr/share/blender/2.90/scripts/addons/io_mesh_stl/__init__.py\", line 139 in execute\n\n\n" ]

[ "Cycles regression testing for GPU devices\n**Background**\n\nThe Cycles automated regression tests so far only ran on the CPU.\n\nWith some environment flags it was possible to execute a script that runs them on other devices, but this is cumbersome. The goal of this task is to add a CMake option to enable running the regression tests on GPU devices in addition to CPU devices.\n\nThe reference images are currently only valid for CPU rendering. Keeping differeing reference images updated will have to wait until we have CI infrastructure for testing GPU rendering. For now we can do a few things:\n* Do nothing and manually check when tests fail\n* Increase difference thresholds for tests that only differ a little\n* Disable failing tests for GPU testing\n\n**Status**\n\n- [x] CYCLES_TEST_DEVICES option to specify devices to test\n- [x] Blacklist failing CUDA tests\n- [x] Blacklist failing OPTIX tests\n- [ ] Verify HIP tests are working\n- [ ] Enable GPU testing on the buildbot", "flow simulation element viewport size indicator strange after applying resize\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83 (sub 17)\nWorked: not known\n\nElement size preview in viewport behaves unexpected.\n\n1) Open Blender\n2) Apply Quick Smoke to cube\n3) scale up Smoke Domain by 20 in x and y direction while keep z scale unchanged (S+Shift Z+20). Notice that preview of element size in corner of Smoke Domain gets resized and becomes more flat. Maybe that is bug because I would have expected that fluid elements are always cubic. But maybe that is intended?\n4) Apply All transforms to Smoke Domain\n5) I would now expect that viewport showed a resized preview of element size for Smoke Domain that was cubic. Instead size preview completely disappears from Smoke Domain. Instead a preview element is shown in the Cube. See . \n\nWhy does a flow object, that is not a domain object, need a element size preview? I think this is a bug.\nAlso, why doesn't the Smoke Domain get a updated cubic element preview when the Smoke Domain object changes size? I think this is also a bug.\n\n\n\n", "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)", "Points not rendered when indices are higher than 67.5 million(roughly)\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 516.94\n\nBroken: version: 3.6.0 Beta\n\n\nI encountered this issue when importing huge point clouds(~100 million points).\n\n\nI prepared a simple file to reproduce the issue, it seems that points stop rendering roughly around index 67.5 million, see the gap between points and 3D cursor.\n\nRepro:\n- unhide Plane object in Outliner, you should see gap between points and 3D cursor, that means some points didn't render\n- change integer from 67.500.000 to say 40.000.000, see that all points along the X axis up to 10(3D cursor) got rendered\n\nEdit: when you unmute Points to Vertices node you can see vertices along whole 0-10 range", "Freestyle doesn't render hair\nOperating system: Win10 64bit\nGraphics card: gtx1050ti\n\nBroken: 2.8-155c62b070a9\nWorked: 2.79b\n\nRender file with Cycles in 2.79b and 2.8. In 2.8 only mesh is outlined.\n[free.blend](free.blend)", "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)", "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", "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", "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", "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", "ShowNavigationGuide refresh Problem\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nno Updating the Viewport when setting the the Navigation Guide on/off\n\n \ninside Blender -Preferences -Input -Show Navigation Guide \nno refresh when checking the Show Navigation Guide on off .\norbit in the 3d-view will refresh and Update these changes.\n\n\n\n\n", "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)", "FLuid Manta Flow Bug\nOperating system: Windows 10\nGraphics card: RTX 3070\n\nBroken: 2.9.1 / 2.9.2 / 2.9.3\nWorked: (newest version of Blender that worked as expected) 2.8.3 / 2.9.0\n\nCaused by 55fd7f55bd\n\n\nUnable to make fluid work properly inside a containiser let say a sphere. I need to make fluid to fill completely the sphere but i am unable to do that. On version 2.9.0 and 2.8.3 it works perfectly... on version 2.9.1 and beyond it does not work....\n\nToo much step to describe but to resume :\n\n1 spehere is fluid > flow\n1 sphere is fluid > colision\n1 cube is fluid > domain\n\nI refresh the cache multiple times, i invert normals on the sphere and so on but liquid don't go inside the sphere or pass through but if i put the fluid source inside the sphere no fluid goes inside...\n\n[fluide.blend](fluide.blend)", "Cycles HIP binaries disabled due to compiler bugs\n### Tasks\n\n- [x] Enable on Windows (#107098)\n- [x] Enable on Linux (#107662)\n- [ ] Enable Radeon VII (gfx906)\n\n### Background\n\nThere are known bugs in HIP compiler that are causing random build failures when making changes to the Cycles kernel. This is preventing developers from efficiently making improvements to Cycles.\n\nCycles AMD GPU rendering were disabled in Blender 3.6 alpha, so that ongoing work like Principled v2 is not blocked. Additionally light tree sampling is not available for HIP in Blender 3.5. We hope this can be resolved later on in the 3.6 release cycle.\n\nRelevant FIXME's in LLVM amdgpu backend (in fact I suspect we hit the same ones back when we were using OpenCL).\nSIRegisterInfo.cpp#L221\nSIRegisterInfo.cpp#L296\n\nMost recent issues:\n#104085 (#104720 )\n#104669\n#104097\nD16714", "dual monitor will sometimes cause blender to freeze\nOperating system:win10\nGraphics card:2080s\n\nBroken: 3.4.1\nWorked: \n\ni have two monitors (4k and 2k) scrolling timeline or doing anything on one monitor and displaying cycles render viewport on the other monitor will sometimes cause blender to freeze forever\n\nit is not specific to this scene it will freeze on all kinds of scenes, might be related to the muti-monitor bug i have been reporting T96248\nhere is a screenshot of what it looks like when freezing \n\nmake some animation\nhave 2 monitors and use cycles rendered view on one monitor and scrolling timeline on the other monitor" ]

[ "Blender 2.91 (and 2.92) cycles viewport rendering issue\nOperating system: Windows 10\nGraphics card: Nvidia Quadro 4000 (y2010)\n\nBroken: (2.91, 2.92)\nWorked: (2.83, 2.90 (different issue))\n\nWith viewport render disabled for a simple fire simulation, cycles repeatedly renders the first sample over and over again in the viewport render mode.\n\n1. Open Blender (2.91 or 2.92)\n2. Create a simple Mantaflow fire simulation with at least one input and one domain.\n3. Give the domain a simple volumetric material for the fire.\n4. Set the render engine to Cycles.\n5. Disable viewport rendering for the fire domain.\n6. Click on viewport rendered view.\n7. Watch Cycles try to repeatedly render the first sample over and over.\n8. If you enable viewport denoising and set the denoise to start at one sample, the problem goes away, but is verrrry slow." ]

[ "Automatic cache change in dynamic hair\nOperating system: Linux-5.10.0-8-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.0.0 Alpha\n\n**Short description of error**\nI can assign a key to the index of the hair cache. But it doesn't work as animation.\n\nOpen dynamic hair. Create hair cache with the same name. More than one. Make the framerate different. bake the disk. Create an empty cache layer with the same name. Key to the cache in frame range taken according to the index number. Switch to other index number. Start the animation.\n\n[blendcache_hair_test.zip](blendcache_hair_test.zip)\n\n[hair_test.blend](hair_test.blend)\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)", "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", "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)", "Interpolated hair curves sharp turns\nWindows 10\nGeforce 970\n32 Gigabytes ram\n\n2.79\n[system-info.txt](system-info.txt)\n\n\nAs shown in the screenshot below, some of the hairs seemingly at random have their curves restart mid stroke, leading to a perfectly straight line connecting from one side of the wave to the other where it continues as a curve.\n\nThis happens on hair systems using interpolated children and either braid or spiral kink. \n\n\nAdd Hair system, Up the number of steps to 7\nDisplay 7 steps\nSet children to Interpolated\nSet Kink to Braid\nAmplitude 0.663 \nFrequency 1.507\n\nThe error occurs at any Amplitude/Frequency\n\n[HairSystemError.blend](HairSystemError.blend)\n", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "Hair (Particles): Cannot animate the property hair_lenght\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14739 Core Profile Context 21.6.1 27.20.22001.14011\n\nBroken: version: 2.93.5\n\nI can't animate the hair_lenght property in hair (particles)\n\n1. Select an object (mesh) and add hair (particles) to it.\n2. Add an animation key in the Hair Lenght property (4m by default).\n3. Change to another frame, modify the Hair Lenght property (put 0m for example) and add a new animation key.\n\n", "Hair Dynamics Strange Behaviour\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0\n\nI have not seen hair behave this way before. For this example file, I have simply used the default hair dynamics settings. I have a bake in the file attached, and you can try bake yourself to replicate the issue. The hair will fly all over the place, it is not colliding with anything and I cannot figure out what is causing the issue. It was recommended by a developer that I post the issue here for others to have a look, many thanks.\n[HairProb.blend](HairProb.blend)\n\n", "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!", "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", "Initial stroke delay - clay strips\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1\n\nWhen you start a stroke in sculpt mode with the clay strips brush, it takes some movement for it to start registering. Previous versions of Blender didn't have this problem. See video to understand better (sorry for the low audio volume, if you can, wear headphones or raise the volume).\n\nJust start a stroke with clay strips, it will take a drag to appear. It can be reproduced in default room.\n\n", "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", "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. ", "Hair particles missing viewport update after \"Rekey\"\nOperating system: Linux-5.19.6-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha\nWorked: 2.79b\n\nHair particles missing update after \"Rekey\"\n\n[particle_hair_rekey_mssing_vieport_update.blend](particle_hair_rekey_mssing_vieport_update.blend)\n- open .blend (in particle editmode, 1 hair particle is selected)\n- run `Particle` > `Rekey` > `Number of Keys` : 50 > {key enter}\n- particle is not updated with 50 points\n- select an existing point\n- now particle shows with 50 keys\n\naware the old particle system is EOL, just posting bugs as a reference because I am looking into new curves editmode (where rekeying/resampling should also be implemented)", "Interpolated hair curves clipping into meshes with subdivision modifiers unapplied\nOperating system: Windows 10\nGraphics card: RTX 2080 Super Max-Q\n\nBroken: 3.51\nWorked: N/A\n\nInterpolated hair curves clip into meshes with unapplied subdivision modifiers. Will stop clipping once subdivision is applied.\n\n1. Create a mesh (i.e. suzanne) and add a subdivision modifier with any amount of subdivision. \n2. Add 'fur' hair curves and do a basic groom\n3. Notice (hopefully) that there a bald spots. No amount of extra guide curves will remove these bald spots\n4. Applying the subdivision modifier should remove these bald spots.\n\n" ]

[ "Poor particle edit performance with subsurf modifier\n[ParticleEdit.blend](ParticleEdit.blend)\n\nOperating system: Wintows 10 Home 64Bit\nGraphics card: GTX1080Ti\n\nBroken: (2.80)\nWorked: (2.79b)\n\nParticle edit performance (with a subsurf) is a lot worse in 2.80 than before. In 2.79 you can edit the hair without lag if you go slowly, but in 2.80 it's going to lag no matter what. And the lag is generally a lot worse.\n\n1. Open ParticleEdit.blend in 2.79\n2. Switch to particle edit mode and try any editing tools on both of the monkeys. Especially the one on the right.\n3. Do the same thing in 2.80", "Poor hair editing performance\n{[F5901764](FurBall.blend)}Operating system: Windows 10 64-bit 1809\nGraphics card: NVidia GTX1080Ti\n\nBroken: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-08 17:06, hash: e79bb957fc3, type: Release\nWorked: 2.79b\n\nPoor performance when editing hair system using particle edit mode.\n\n1. Open FurBall.blend (attached) using Blender 2.80.\n2. Switch to Particle edit mode.\n3. Use any editing operation (e.g. Combing). Observe how slow and unresponsive it is.\n4. For comparison, repeat steps 1-3 using Blender 2.79b. The performance should be several times better.", "Editing particles in high poly objects is extremely slow\nOperating system:win10 1903\nGraphics card:gtx1060\n\nblender-2.80.0-git.676543d91f5c-windows64\nWorked: (optional)\n\nWhen attempting to edit particles on any high poly object, extreme slowness is observed.\n\n1. Open the attached file;\n2. On the particle edit mode, try combing the hair;\n3. See slowness.\n\n(To compare, disable the Subdivision Surface modifier).\n\n[slow.blend](slow.blend)", "Slow Particle/Hair Editing in Blender 2.80 Release Candidate\nHello,\n\nhere is my report:\n\n\nOperating system: Windwos 10 Pro 64bit Build 17763\nGraphics card: 8GB Nvidia Quadro RTX 4000\nProcessor: AMD Ryzen Threadripper 2950X\nRAM: 64GB DDR4 2900MHZ\n\nBlender 2.80 Release Candidate\n\nThe performance for editing Hairs in Blender decreased from Version 2.79b to 2.80 Release Candidate:\nI first found out about this problem when I tried out one of my created characters inside one of the Blender 2.80 beta versions: While the viewport performance for showing Hair increased, the performance for editing Hair was significantly slower (too slow to work with). \n\nI now created two files in Blender 2.79b and the Release Canditate of Blender 2.80 with the same settings:\n- Standard-scene with a 1.5m radius sphere; \n- Segments and rings to 64; \n- Default prinzipaled shader; \n- 3000 Hair with 0.2m length and interpolated Children with a Display Amount of 50\n\nIf the Scenes are opened one can directly begin to comb the hair. At my PC-Sytem the performance for Blender 2.79b is faster during the editing.\n\nGreetings,\nKeks0943\n\n\n[2019_07_13 - DemoHairGroomingPerformance - Blender 2_8 Release Candidate.blend](2019_07_13_-_DemoHairGroomingPerformance_-_Blender_2_8_Release_Candidate.blend)\n[2019_07_13 - DemoHairGroomingPerformance - Blender 2_79b.blend](2019_07_13_-_DemoHairGroomingPerformance_-_Blender_2_79b.blend)", "Using Particle Edit is much slower on 2.80 than 2.79\nOperating system: Operating system: Windows 10\nGraphics card: Nvidia gtx 1080 ti\nCPU: AMD Ryzen Threadripper 1950X\n\nBroken: 2.80 rc2 (sub 74), branch: master, 2019-07-18 14:52\nWorked: 2.79\n\nUsing Particle Edit mode is much slower on 2.80 compared to 2.79 (example: creating hairstyle to a rigged character)\n\nAdd cube; subdivide 30 times; Add Modifier: Subdivision;\nAdd Particle System slot, Particle type: Hair, Emission/ Number: 1\nEnter Particle Edit mode and compare 2.80 editing speed to 2.79\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", "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", "Geometry Node: Viewer output for instance domain ignore if value nearest to 0.01\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4, 3.5\n\nGeometry Node: Viewer output for instance domain ignore if value nearest to 0.01\n\nIf you explicitly specify the instance domain, then with a value nearest to 0.01, the viewer will ignore the value input\n\n[2022-11-11 23-41-29.mp4](2022-11-11_23-41-29.mp4)\n\n\n- Put some intance to Viewer\n- Connect Float Value to Viewer set to instance domain\n- Test various floats (0.01 and 0.3)\n\nOr in attached file switch between couple of Viewer nodes\n[gn_viewer_value.blend](gn_viewer_value.blend)", "Glitches with Curve Fill Node\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked version: never\n\nIf you instance circles or other curves on a curve and you will realize those instances, and you will use the curve fill node on them. There are some glitches or inconsistencies.\nIf you change the scale, the fill node will also randomly decide what should be filled.\n\n\n\n\nTest File:\n[#95518.blend](T95518.blend)\n", "Geometry Nodes: Color mix nodes don't effect the alpha\nOperating system:\nGraphics card:\n\nBroken: 3.4.1\n\nwhenever I try doing any math with colors, the alpha isn't affected when I use the color mix node in any blend mode. \n\n1. Open blender geometry nodes.\n2. Add 2 combine color, color or whatever node with different different values for the alpha's.\n3. Use a mix color node with any operation like add, subtract etc.\n4. See that the alpha didn't change (use the spreadsheet or the hover over).", "Geometry 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", "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", "Changing UI resolution scale messes up nodes snapping\nOperating system: Windows-10-10.0.25393-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: Never AFAIK\n\nWhen you have a node tree all snapped to grid and is perfectly organized, you move it and it all moves in an organized manner. But say you change your UI resoltuion scale, or line width; the perfectly organized node tree is not organized anymore 🥲. Now it may seem that this bug is really rare, but it's really infuriating when you open someone's file and you mess up the node tree in seconds by just moving.\n\nI created a small video that demonstrates the bug, but basically the steps are.\n1. Create a well-organized node tree that is snapped to grid.\n2. Change the UI resolution.\n3. Observe your node tree not snapped to grid anymore.", "Wrong tangent space when using GPU subdivisions\nOperating system: Linux-5.18.0-1-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.08\n\nBroken: version: 3.3.0 Alpha\nWorked: N/A\n\n\nThe tangent space is calculated wrongly when using GPU subdivisions: it appears as if it is calculated for the base mesh instead of being calculated at the limit surface.\n\n\nOpen the attache file, and toggle \"GPU subdivisions\" in the preferences.\n\n|CPU subdivisions|GPU subdivisions|\n| -- | -- |\n||\n\n[gpu_subdiv_tangent.blend](gpu_subdiv_tangent.blend)\n", "Geometry Node: Changing modifier input values with python no cause update\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0 Alpha\n\n\nChanging modifier input values with python no cause update.\nBy code:\n\n```\nbpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_1\"][0] = 13.8\n```\n\nValue in modifier property was changed. User interface no updated before modifiers panel are not redrawn. Result of modifier didn't updated.\n\n\n\n- Open attached file\n- Run the code `bpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_7\"] = 1.0` in the python console\nThe modifier UI may change, but the Viewport does not.\n[geom_node_py_bug.blend](geom_node_py_bug.blend)\n\n", "Wrong initial size in the operator panel if Cylinder object is added through left side tool panel gizmo.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.1.2\n\nI was told to post a bug report in the comments of my question so without further consideration I have done so.\n\nWhen creating a cylinder from the tool menu on the left-hand side of the screen, the dimensions present in the window do not match what was created and manually inputting new dimensions will not result in the correct size, instead seeming to multiply by the existing shape's dimensions.\n\nadd-mesh-cylinder-radius-confusion\n\n\n1. Click create cylinder on left-hand tool menu\n2. Click and drag to create cylinder of any size and depth\n3. The \"Add Cylinder\" panel will always show a radius of 1m and the depth of 2m, and adjusting the values will scale the geometry accordingly as if the gizmo-created cylinder size is the 1m/2m base size.\n\n", "Geometry Node: New Sample Curve\nAdding support for a random attribute to the sampling node exposed the problem of attribute evaluation ignoring the calculated curve. This design variant is intended to treat the sampling of values from calculated curves as a new attribute-based сontext.\n| [2022-08-01 14-00-56 (video-converter.com).mp4](2022-08-01_14-00-56__video-converter.com_.mp4) |    |\n| -- | -- |\nThe crux of the problem is that a random attribute, when sampled, must be able to have a position behavior. Other behaviors are not covered yet, but may be added later.\nSampling attributes do not belong to the curve and have their own size. Their interpolation may not be linear, but based on the type of curve, which increases the speed for large objects.\n\nExample: sampling a random vector from curve points. You want the vector to keep its length. But even the original implementation of normals kept the length just because of the normalization. Nonlinear interpolation in spline space for a vector has the ability to rotate it without loss of length and incorrect deformations.\n\nOr you want to sample a color. You can set the color for the breakpoints and... Whoa, those are just linear transitions! Handles cannot be used. They are not a domain and this design does not violate that. Simply by sampling an attribute, you can sample it not only from breakpoints, but from handles!\n\nAlso, in addition to entering an attribute as the domain of the sampled curve, a segment data node is offered. This low-level node is for primary access to cache data. The sampled attribute input node uses this as its signature. But it can also be useful for the user to be able to use this data, for example, to visualize the operation of a bezier curve.\n\nWhen sampling, 3 types of values must be present in the scope of the context:\n - Curve data obtained from the visible version of the curve\n - Curve data sampled from its points and handles\n - Sampling destination data. To keep things simple, if multiple post-sampling values are going to be used with geometry definitions, it's best to do this before the sampling node to keep the output of the node to a minimum.\n\nAlso sampling features:\n1. The option of sampling a vector in normal/target space + sample position can be used as a variant of the curve mesh deformation\n2. Sampling at an arbitrary point creates freedom to obtain information about the curvature of the surface.\n\n---\nCurve Input:\n - Spline type (Select current type curves / index of type)\n - Select Spline By Type (By type index)\n\n---\nChanged Nodes:\n - Sample Curve\n - Input:\n - Curve\n - Factor / Length\n - Curve (Index)\n - Attribute (Random type) (use SampleCurveContext)\n - Output:\n - Value (Random type)\n```\n\n```\n - Position:\n - In SampleCurveContext return evaluated_positions\n - Normal:\n - Same Position\n - Curve Tangent:\n - Move TangentFieldInput to Fields Input and add it in SampleCurveContext same position\n - Index:\n - Same position. Index in sampling input index of current curve\n - ID:\n - Same Index. ID is index of current sample. Sampling no has order ad id make sence only for random and same things\n - Spline Length, Parameter, Resolution, Cyclic:\n - Data of spline same changed. Data of point internolated by sampling\n\n- Context Add:\n - Sample Signature Input:\n - Curve Index\n - Curve Type\n - First Point\n - First Factor\n\n---\nAdd Nodes (Valid only in SampleCurveContext):\n - Sample Attribute on Curve:\n - Input:\n - Attribute (Random type)\n - Hadles type ? left/right position : Weight\n - Output:\n - Value (Random type)\n - Sampling Attribute:'\n - Input:\n - Attribute (Random type)\n - Output:\n - Value (Random type)\n - Sample Segment:\n - Output:\n - Previous Point of original curve\n - Factor for interpolatin in current segment\n\nFirst test version: P3114", "Wrong 'Vector Math' position in 'Add Node' menu\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\nWorked: not sure, but sure not in blender 2.91a :c\n\nIn Node Add Menu (Shift + A) Vector Math Node (Vector Node) is in Converter submenu/category\n\n1. Add some material to edit\n2. Go to Shader Editor (Shift + F3 or Shading Workspace)\n3. Try to find Vector Math node in Add Node Vector submenu (Shift + A; should be there)\n4. Find it in Converter submenu (but it's not converter, even blender uses Vector Color for this node)\n\n---------------\n - Photos\n - Here Vector Math is:\n\n\n### Here Vector Math should be:\n\n\n### ...and how it looks in blender over all:\n", "Incorrect and Confusing Units for String to Curves Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\n\nIncorrect and Confusing Units for String to Curves Node, depending on Scene / Units\n\nIf Scene / Units is set to Metric this node looks like this:\n\n{[F13984816](image.png),width=100%}\nCharacter spacing is shown in meters, and that is so odd that it might as well be shown in \"number of chickens\". Our current Character Spacing is already done strangely enough. This value is divided by 2 then 0.5f is subtracted from it. That value is a portion of the font's em square that is added to each character. So a value of **1 means no change** to character spacing. 0 means that 0.5 of an em is subtracted from each one. That \"1\" means default is bad enough, but much worse to show it as one meter. \n\nAt minimum we should show this as unitless. Better would be to not do the division and shifting and therefore show \"0\" as default and add \"em\" as unit. This would match with CSS letter-spacing.\n\nWord spacing is similar, but is a factor multiplied against each character's advance. So again, \"1\" means normal, 0 means that a space has no width, a 2 means a space is twice as wide. No relation to grid size. So showing \"1 meter\" is pretty bad.\n\nThis also should be unitless. Ideal would be to change it from a factor to a absolute value added to the width of space characters. That way it can also be \"0\" by default and show \"em\" as units. This would match with CSS word-spacing.\n\nFor even more oddness, this what it looks like in Imperial\n\n{[F13984832](image.png),width=100%}\n\nAs in normal and default character width and normal word spacing are shown as \"3.28 inches\"?\n\n", "Node editor: zoom is affected by DPI\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.2.2\nSame on 3.3.0 beta and 3.4.0 alpha\n\nGeometry nodes panel does not re-scale when Blender window is moved to a display with a different DPI (e.g. retina to non-retina display, in Apple's parlance). Everything else in the GUI gets re-scaled correctly.\n\nSee attached screen-shots.\n\nHave 2 displays - one with a higher DPI.\nOpen Geometry Nodes panel.\nMove Blender window from one display to another.\n\n" ]

[ "Default Values Don't Reset Properly in Custom Node Groups\n# Default Values Don't Reset Properly in Custom Node Groups\n\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.2.0, hash: `e05ele369187`\nBroken: version: 3.3.0 Alpha\nWorked: N/A\n\nWhen I set the default value for any input in a custom node group, I would expect to be able to easily reset that input to its default value by clicking \"Reset to Default Value,\" but it always just resets to \"0.000,\" \"false,\" etc. (depending on input type), as though I hadn't set a default.\n\n- Create a custom node group with one or more inputs\n- Set a default value for an input (other than 0)\n- Exit the node group\n- Right-click the value and select \"Reset to Default Value\"\n- Value will reset to \"0.000\"\n\n [Blender 3.3 Alpha - Node Group Default Value Always 000.mp4](Blender_3.3_Alpha_-_Node_Group_Default_Value_Always_000.mp4)", "Material node input fields always reset to 0 by Reset to Default Value operation even when it's not the default value.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.2.2\n\nPretty much all numerical inputs of material nodes reset to 0 when Reset to Default Value operation is performed by hovering mouse over input fields and pressing backspace even when the default value is not 0.\n\nFor example Invert node's factor resets to 0, Vector Mapping node's scale resets to 0,0,0, Emission Shader's strength resets to 0, all inputs of Hue Saturation Value value reset to 0 and so on. If the node is reset entirely when selected and not hovering over particular input field they reset correctly. \n\n* make any object with a material\n* in the shader editor create any of the nodes mentioned\n* hover over some input field that has non zero default value when created and hit backspace.\n", "Node group input value resetting to default value does not respect group input settings\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.27\n\nBroken: version: 3.3.0\nWorked: never\n\nWhen resetting a node group's input value to default, by either rightclicking and choosing that option, or by hovering the mouse and hitting backspace on the keyboard, It does not respect the value set as default value in the group's input settings in the properties panel.\n\n\n\n\n\n1. Create node group\n2. Add input value\n3. Set default value to anything but 0.0\n4. Exit node group\n5. Change value\n6. Reset to default by either method described above.\n\n", "'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", "\"Reset to Default Value (Backspace)\" does not work for NodeGroups\nOperating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.0.0\n\nWhen trying to reset a property value from a created NodeGroup using the hover mouse + backspace it will set it to 0 (zero) instead the defined value previously in the Group Input properties panel.\n\n\n\n\n1. Set a default property value in the Group Input of an arbitrary NodeGroup\n2. Tab out, hover your mouse and press backspace\n3. The value will reset always to 0 instead of the defined value previously.\n\nOnly adding the NodeGroup from scratch will bring the defined values which is not ideal.", "Geometry nodes: Transform node - scale is reset to 0 (instead of 1)\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\n\nThe scale in the transform node (Geometry nodes -> Shift + A -> Geometry -> Transform) is changed 0 if the value if reset.\nSame for point scale (Geometry nodes -> Shift + A -> Point -> Point Scale).\n\n - Create a transform node\n - Reset the scale value\n\n**What I would expect to happen**\nIn the 3D viewport or Properties tab the scale is reset to 1. I would expect blender to do the same here\n\n**Files**\nThe issue as image\n\n\n[blender 2.93 reset scale.blend](blender_2.93_reset_scale.blend)" ]

[ "Face orientation - no colors in X-Ray\nOperating system: windows 10\nGraphics card: NVIDIA GeForce GTX 1070 \nsame issue on different pc Samsung NP900X3C\n\nBroken: 2.83.2 and 2.90.0-f319eec88186 (latest 2020 jul 14)\nWorked: 2.80 ~ 2.82\n\n**Face orientation in X-Ray view does not show transparent colors(blue and red)**\n\n1) turn on face orientations ; \n2) turn on toggle X-Ray\n\n![2020-07-14 21-26-43.mkv_snapshot_01.48_[2020.07.14_21.57.56].png](2020-07-14_21-26-43.mkv_snapshot_01.48__2020.07.14_21.57.56_.png)\nhere how it works in 2.83.2 & 2.90.0 [2020-07-14 22-43-43.mkv](2020-07-14_22-43-43.mkv)\nand how it should like in 2.80 ~ 2.82 [2020-07-14 22-49-24.mkv](2020-07-14_22-49-24.mkv)", "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.", "Default theme: Data types corresponding with modes\nFor the release of Blender 2.83, we have removed the use of the crosshair cursor for Edit Mode, because it was conflicting with tool cursors. \n\nInstead, we can use other things to help clarify to users which mode is active. \n\n{[F8383208](Screenshot_2020-03-02_at_11.07.10.png), size=full}\n\nCurrently, selection in all modes is orange. But, as you can see above, we already color code different kinds of data in Blender. Object data (mesh, curve etc) is set to green, so we could use that as the edit mode selection color.\n\n\n## Examples:\n\nVertex:\n{[F8383329](theme_vertex.png), size=full}\n\nEdge:\n{[F8383332](theme_edge.png), size=full}\n\nFace:\n{[F8383334](theme_face.png), size=full}", "Unbaked Dynamic Paint Not Displayed in Rendered Output but Shows in Viewport\nOperating system: Manjaro 18.0.1 Illyria / x86_64 Linux 4.14.90-1-MANJARO\nGraphics card: Nvidia 1080 Ti\n\nBroken: 2.80 (sub 39), Commit date: 2018-12-29 18:10, Hash 266b1e2cdbc1\nWorked: 2.79 (sub 6), Commit date: 2018-10-22 16:17, Hash 86dbbd156fa\n\nUnless baked, dynamic paint does not affect the final rendered image but is properly displayed in viewport.\nThe default and expected behavior is to be able to render the effect regardless if baked or not. This is how 2.7x operated in the past.\nMoreover this problem, which I assume has something to do with vertex colors [has caused other issues ]] with different [[ https:*github.com/hsab/tensionmap | addons ](https:*github.com/JacquesLucke/animation_nodes/issues/989) that depend on similar workflows of modifying the vertex color using the python API (eg. proximity, stress mapping etc.) \nNot sure if #51214 is related since it's from April 2017. If so please close as a duplicate.\n\nTwo blend files attached, one for 2.8 and one for 2.79.\n2.79 file works as expected.\n2.8 file is broken unless baked.\n\n2.79.6 Render:\n\n\n2.80.0 render:\n\n\n[dynamicpaint2.8.blend](dynamicpaint2.8.blend)\n[dynamicpaint2.79.blend](dynamicpaint2.79.blend)", "Insert key dropdown on keymap doesn't show keying sets anymore\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.2 Release Candidate\nWorked: 2.92\n\nwhen trying to assign a default keying set to the insert key menu, it doesnt show the list anymore just a dropdown that says default\n\n2.92\n\n\n\n2.93+\n\n\nopen blender, go to settings > keymap\nsearch for \"insert keyframe\"\nexpand the \"insert keyframe menu\" under pose mode\nclick the keyingset dropdown... all you get is default.\n", "GPencil: Low hardness values always draws yellow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nGrease Pencil creates yellow transparency with lower hardness values on brush.\n\n - Open in 2D Animation mode\n - Set to a \"Dots\" brush (eg. Dots Brush) its most noticeably shown there. It happens for the other ones too but this one is most noticeable\n - Set the Radius to something largish so we can see whats happening (eg 2000px), or zoom in \n - Draw a circle and you'll be able to see it\n\nIt looks like there's a faint yellow tinge transparency which builds up when putting the grease pencil strokes on top of each other.\nWhat it looks like:\n\n\nExample blend\n[yellowtransparency.blend](yellowtransparency.blend)\n\nBasic repro gif\n\n\nMe shading a ball\n\n\n\n\n\n", "Support Face color attributes for painting\nFace color attributes should be supported for sculpt painting and vertex paint mode.\n\nThey should also be listed under the Color Attributes UI List.\n\n", "Design: Graph Editor Curve Display\nThere are a few issues with the display of curves in the Graph Editor mentioned in the Paper Cuts devtalk thread. However while technically simple to change the drawing, it needs to stay consistent and clear, which is why this Design task exists.\n\n**Issues**\n* Locked Curve keyframes look like they are active\n* Curves are drawn in the same thickness even outside the range they can be edited in ?sorting=hot#\n* Location/Rotation/Scale curves are not distuingishable at first glance 27?u=christophlendenfeld\n\n## Current State\n\nNormal\n\n\nDisabled\n\n\nLocked\n\n\n## Proposed Solution\n\n* Locked curves have crosses instead of keyframes to indicate that they can't be selected. [#106052](106052)\n* Locked curves are always drawn as if they were unselected since you can do nothing with them even though they are selected.[#106052](106052)\n* Increase the dash length and spacing to reduce visual noise [#106052](106052)\n* Add preferences to modify the colors of FCurves based on their type. Will default to the current standard to not confuse existing users.\n", "UI: Show invalid cache as stripped lines\nAt the moment we use a faded color to indicate that a cache is invalid. The difference is a too subtle at times, even when users customize their theme colors.\n\nThe proposal here is to draw the invalid caches with a darker stripped diagonal line (see image). In this case I used the original color with a 50% value.\n\nIn this mockup you see the Simulation cache (pink) as invalid, and the Cloth cache (blue) as valid.\n\n\n\n_Design done with [Pablo Vazquez](pablovazquez)._", "Graph Editor: Automatic Colours can be confusing\nProblem: when there are many curves, the mapping from X/Y/Z/W to colour is inconsistent. For example, the same hue can be used for X in one bone and Y in another.\n\n**Proposal**: No concrete proposal yet, apart from the desire to have consistent X/Y/Z/W colours. The colour generator code could be altered to always produce the same hue for the same RNA `array_index`, for example, or use `array_index/array_length`.\n", "OBJECT_OT_shape_key_clear ignores slider_min and slider_max\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 2.79, 3.5.1, 4.0.0 Alpha\nWorked:\n\nThe OBJECT_OT_shape_key_clear operator clears the `.value` of each Shape Key, setting it back to zero, but Shape Keys have `.slider_min` and `.slider_max` attributes which specify the minimum and maximum values for `.value`. OBJECT_OT_shape_key_clear does not respect the `.slider_min/max` values when it clears the `.value` of each Shape Key, setting `.value` to an otherwise impossible value when either `.slider_min` is greater than zero or `.slider_max` is less than zero.\n\nAttached is a .blend (authored in 4.0.0a) with steps 1-4 already set up.\n1) Create two non-'Basis' shape keys on a default cube\n1) On the first shape key, set its `.slider_min` to 0.5\n1) On the second shape key, set its `.slider_min` to -1.0\n1) On the second shape key, set its `.slider_max` to -0.5\n1) Click the button in the UI to Clear Shape Keys, or run `bpy.ops.object.shape_key_clear()`\n\n1) Observe that the `.value` of each shape key is now set to 0.0\n\n", "Regression: Themes: Highlight color in the text menus\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6.2\n\nThe highlight color is not longer adjustable by the Selected color in the User Interface / Menu Item panel. But changes with the Inner color. This breaks theming.\n\n\n- Enter Preferences. \n- Navigage to Themes tab, User Interface, Menu Item panel.\n- Play around with the Selected and Inner color\n\n", "Animation: Circle & Lasso select does not work correctly on bones with custom shapes\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.1\nWorked: Unknown\n\n\nUsing circle or lasso select to select bones with custom shapes does not work correctly. It seems to pick against the actual bone shape instead of the custom bone shape. It's interesting to note that box select seems to work fine here.\n\n[circleselectcustombones.mp4](circleselectcustombones.mp4)", "\"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", "Text Object: D key is used for the Annotate Tool\nOperating system: Linux-5.4.0-104-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.0 Alpha\n\nIn the keymap preferences there is an option to use the Active Tools for shortcuts instead of the modal operation.\nIt's called \"Tool Keys -> Immediate / Active Tools\".\n\nIf this preference is used and you go into edit mode of a text object, you are unable to type in the letter `D`.\nIt will always make the Annotate Tool active instead.\n\n- Enable the \"Active Tool\" keymap preference\n- Add a text obejct\n- Enter Edit Mode\n- Type in a word with the letter `D` in it like \"Addon\" " ]

[ "Driven or keyed states no longer visible on shapekey sliders\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.92.0 Alpha\nCaused by 600fb28b62\n\nWHen keying the current value of a shapekey or addign a driver the color is only dispalyed on the value below but not on the list of the shapekeys.\n\n\n\n" ]

[ "Cycles GPU rendering is broken on Apple M1/macOS Ventura\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.3.0 Release Candidate\nWorked: 3.2.2\n\nCycles GPU rendering is broken, CPU rendering works as expected.\n\nCycles - CPU:\n\n\nCycles - GPU Compute:\n\n\n1. Create any scene\n2. Switch Cycles to GPU Compute\n[simple_test.blend](simple_test.blend)\n", "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", "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)", "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", "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", "3D Texturing: Fix seam bleeding non-manifold meshes\n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "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", "Cycle gpu rendering crashes randomly\nOperating system: Win11\nGraphics card: Nvidia RTX 3070 Ti\n\nbroken: all 3.0 versions\n\nRenders keep crashing randomly when I’m using my gpu with cycles, I updated my drivers, my memory use is okay, I tried to not use denoiser, lower my samples, resolution etc but nothing works, sometimes it render 10 frames sometimes 100 but it can't render my whole animation without crashing (also for animations with low poly count and small textures tiles) \nDon't know how to read the crash log file.\n\n", "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", "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 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", "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", "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", "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)" ]

[ "Alembic Hair Won't Render Correct Frame.\n[system-info.txt](system-info.txt)\n\nBroken: 2.90 alpha (6f985574b7)\n\nI can scrub the timeline and see my Alembic hair update, but Blender always render frame #1.\n\nOpen the attached file, move to somewhere along the timeline and press F12.\n\nOn my system Blender always renders frame #1.\n[alembic_hair_issue.zip](alembic_hair_issue.zip)", "Alembic curve animation stuck not update\nOperating system: win10 20H2\nGraphics card: 2060 super\n\nBroken: 2.83 , 2.92 , 2.93.0-9ca67c47a152-windows64\nWorked: no\n\ncurve animation with modifier always return to frame 1. \nrender not update\n\n[b3d_bug_20210321_A.zip](b3d_bug_20210321_A.zip)\njust move timeline render, render result is at frame 1", "alembic results in hair with \"random position per frame\" in render time\nOperating system: windows 10\nGraphics card:GTX 1080\n\nBroken: 2.80, 2019-01-26, 25772c9e1d2d, branch: blender2.7\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[hairNoise.rar](hairNoise.rar)\nWhen using rendering hair and using alembic as mesh cache (Mesh Sequence Cache modifier) I get unique root positions of each hair strand per frame. This bug can only be seen in rendertime. When looking at the fur in the viewport, everything looks fine.\n\nWhen using MDD as cache format, this issue can not be seen. Only alembic cache seems to be affected.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. create a sphere\n2 add a displacment modifier with cloud texture and animate the displacement. Any deform modifier will do\n3. Export the sphere as alembic \n4. Duplicate the sphere \n5. add a Mesh Sequence Cache modifier and connect it to the exported alembic. \n6. add fur. Use few hairs so it's easier to spot the random hair poisition per frame.\n7. scrub the timeline. Notice that the hair looks fine in the viewport\n8. render the image sequence. Look at the rendered images and see that the fur looks really noisy/jittery per frame\n", "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)", "Cycles / Eevee not rendering curves, although perfectly rendering in viewport.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nThis does not apply to simple curves, but ones imported via abc or other format.\n\n\nextract attached blend file, please check .abc mesh sequence for correct load. If you render the curves in viewport you will see them (with bevel or extrude), in proper render with F12 there will be nothing.[BUG_Curves.zip](BUG_Curves.zip)\n" ]

[ "Insert keyframe wrong with cycle-aware keying after deleting end frame\nOperating system: Linux-6.4.6-arch1-1-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05\n\nBroken: version: 3.6.0\n\nI have an action with manual frame range, 1 to 11, with cyclic animation checked. I have cycle-aware keying on.\n\nI'm not sure exactly when the bug starts, but eventually adding a frame at time 9 creates the keyframe at frame 4 again.\n\n\nI'm not sure exactly when the issue started, but roughly\n1. Cube\n2. Insert frame at time 1\n3. Turn overlay action into layer (stack?) action with the down icon button\n4. Set up manual frame range 1-11, cyclic\n5. Turn on cycle-aware keying\n6. Insert another frame at time 6, blender automagically adds a frame at time 11 to match the frame at time 1\n7. Delete the frame at time 11\n8. Move to time 9 and insert frame\n\n7 seems to be the key. Additionally, it's impossible to add a new frame at time 11. The issue persists after closing and re-opening. \n The issue disappears when cycle-aware keying is off, but comes back if I turn it back on.\n\nI didn't try a daily build, but I searched issues to see if anything similar was reported and found nothing.\n\n", "Importing a keymap with a default name makes a non deletable copy\nBroken: version: 3.2.1\n\nAfter importing a keymap configuration with the name \"Blender\" it created a copy of the default setting that is impossible to remove from the UI at least.\n\n\n\n\n\nImport a keymap setting with a default name\n\n\n**Fix**\nDelete keymap configuration from the user folder directly \n\n> \\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\scripts\\presets\\keyconfig\n\n\n", "Editing redo panel properties of torus in edit mode reverts some steps\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.24 355.11.10.50.10.103\n\nBroken: version: 3.4.1\nWorked: (never worked as expected)\n\nAdding and then adjusting a Torus or any Add Mesh add-on in edit mode reverts edits made to nodes, video sequencer, and more, since entering edit mode on the mesh object.\n\n1. Go to the Geometry Nodes workspace\n2. Select the default cube\n3. Click the New button to add the Geometry Nodes modifier and create and assign a new node group\n4. In the 3D Viewport switch to Edit mode\n5. In the Node Editor, pour your heart and soul into crafting an elaborate node tree (lol, jk 👀💔)\n6. In the 3D Viewport add a Torus\n7. Tweak any setting in the Adjust Last Operation panel\n8. Observe Geometry Nodes edits reverted (all edits since entering edit mode in the 3D Viewport)\n\nNo other built-in mesh primitives (nor even primatives!) have this effect, but the Add Mesh add-ons all do.\n\nI have checked some of the editors to see what data is reverted and what is preserved. This is not yet an exhaustive review.\nThe following data is reverted:\n- Video Sequencer\n- Properties\n- every Node editor\n- Timeline\n\nThe following data is preserved:\n- Preferences\n- Text Editor\n- Python Console\n- Movie Clip Editor\n- UV Editor\n\nThe Outliner has mixed results:\n- Hierarchy expansion reverts in Blender File, Data API, and Orphan Data but not in Scenes nor View Layer.\n\nSome editors have special behavior:\n- Image editor\n - Paint mode\n - {Add torus, paint image, tweak torus} reverts the paint\n - {Paint, add, tweak} kicks out of Edit mode into Object mode\n - Switching Image Editor modes does not close the ALO panel. The following sequence of steps produces a Python error:\n - Add torus\n - Switch Image Editor modes\n - Adjust torus\n (If this merits its own tracker issue, tell me and I will write one up. This all seems so tied to one root culprit that it is not my initial inclination to do so)\n\n", "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)", "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.", "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", "Undo/Redo shortcut still active in the Blender File View window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Beta\n\nUndo/Redo shortcut still active in the Blender File View window\n\n* Open Blender with the default cube.\n* Move the cube a few times.\n* Open the “Preferences” window in the menu “Edit | Preferences...”\n* Then do Ctrl + Z to undo. The undo shortcut still works. It is the same for the redo shortcut.\n\nThe undo/redo is also active from any other windows of the “File” menu like “Open”, “Link”, “Save”, “Append”, etc. All links showing the “Blender File View”.\n\nIn the “Blender File View” window, I noticed that the buttons at the bottom disappear when doing the undo shortcut.\n\nI tried a few other shortcuts like Tab to go to edit mode and G to move the cube. They do not seem to be active when the focus is on the “Preferences” or “Blender File View” window.\n\nThe undo/redo is also active when the “Blender Render” has the focus.\n\nAs a consequence, someone accidentally hitting the undo shortcut will get his work being modified behind the window and probably will not notice.\n\n\n{[F9111517](BlenderFileView_Open.jpg) size=full}\n\n{[F9111519](BlenderFileView_AfterShortcut.jpg) size=full}", "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", "Lost hotkey with save preset\n2.80\n\n\nI finally can replicate problem from 2.7x and it is still problem in 2.80. When you change some combination of hotkeys and save it to the preset. You lose some of them. On my GIF example Numpad 1 dissapear.\n\nSometimes it come back after restart Blender, but sometimes it is just gone.\n\n\n\n", "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 moving to Shading workspace\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.17.5 355.10.05.45f01\n\n|Broken:|version: 2.83.0, commit date: 2020-06-03,|hash: `211b6c29f7`\n| -- | -- | -- |\n||version: 2.90, commit date: June 08,|hash: `9f7d84b656`\n|Worked:|version: 2.82|-\n\nWhen I open Blender, without changing anything in the default scene, if I move to the 'Shading' workspace my system freezes for a few seconds and crashes (it closes).\n\n- Default startup scene\n- click on 'Shading' workspace from the top bar\n", "\"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.", "Local view mode is not exited correctly when closing New Windows\nOperating system: Mac OS*\nGraphics card: Macbook pro M1 MAX, 64G ram\n\n**Blender Version** 3.41 (same issues found in 3.2)\nBroken: Local view doesn't work(/)\nWorked: \n\nit's hard to say when it will happened, I used MacBook with two monitors, (one is Mac Studio, an other one is iPad Pro), when I duplicate a new windows to my second screen, like to iPad for sculpting, some times, local view function(hot key\"/\") doesn't work and show 'no more than 16 local views\" error. I met this error 3times from version 3.2 to 3.41\n\n\n\n\n- Repeat the following 16 times\n - Open a new `Window`->`New Window`\n - Go into Local view in the new 3d viewport that appears\n - Close the window while still inside local view\n- Attempt to go into local view 1 more time\n- Observe failure\n\nThe issue is that local view mode is not exited when those temporary New windows are closed. Blender continues to think that those local views are still in use and runs out of available space for any new ones.\n\n[test.blend](test.blend)\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", "Render window don't close from Windows taskbar thumbnail\nWindows 10x64 Home Ru Version 1607 Build 14393.639\nNVIDIA GeForce GTX 970 with 378.66 NVIDIA drivers\nIntel Core i7-4790K\n[system-info-2.78c.txt](system-info-2.78c.txt)\n\nBroken:\n2.78c x64 e92f235283\n2.79 testbuild2 x64 248bba81e7a\n2.79 daily build x64 66383ea\n2.26\nWorked: (optional)\n2.04\n\nWhen rendering to separate window, this windows won't close by clicking on \"close\" button in the Windows taskbar thumbnail (If blender main window or render window is active, close button may sometimes work).\nBut after that render window will close automaticaly when blender window is activated (on mouseover, atl-tab etc.)\nWith blender 2.04 button is work, but it close blender instead render window.\n\n1. Switch render display to \"New Window\"\n2. Render by F12\n3. Click somewhere outside to deactivate blender.\n4. Try to close render widow from Windows taskbar thumbnail - close button is not work.\n5. Move mouse over blender - render window will close automatically.\n\n" ]

[ "Preferences GUI tree-collapse, undesired operation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: TITAN V/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\n\nWhen adding a new value or editing some values, in the keymap settings. The entire tree setup collapses after every change of any value. Not just the tree you are in, but all trees. (I have not tried other areas.)\n\nEnter the [preferences] window.\nGo to the [keymap] section.\nNavigate to the [3D view] area and expand that tree.\n- Expand any tree-view items, then continue below...\n- Expand the [3D view (Global)] area.\n- - Expand the [Rotate view] area.\n- - - Expand the [View 3D Rotate Modal] area.\n- - - Select {+ Add New} and adjust the settings.\n\nIt is at this point that any open trees will all collapse and return to closed-state, as well as the view scrolling back to some other location from where you were. Which now requires you to scroll back to the area you were, open all the levels of the tree view again, and continue editing that new area more. (Assuming that you did not finish editing the settings. As it continues to close the tree after every change to any setting.)\n\nExpected operation...\n\nThe tree remains open after altering or setting a value and the list does not scroll away from the area you are editing. Including any other areas you may have open, which may be open for a reference of duplicating those settings.", "Key Map Editor entry \"un-expand upon change(Resets entry list display to its original expand/fold state)\" behavior\nIrrelevant\n\n2.8 release\n\nKey Map Editor entry \"un-expand upon change\" behavior\n\nUpdate: A better description may be \"Resets entry list display to its original expand/fold state\"\n\nWill be tricky to reproduce.\n\n1. Get to keymap editor, find \"Box Select\" under view3d.\n\n2. Expand its setting, see the sub-category \"Gesture Box\"\n\n3. Enable/Disable entries under \"Gesture Box\"\n\n4. Notice the whole entry for \"Box Select\" folds up.\n\n5. If nothing un-expands and things seem to be normal, repeat from step 1 on something else.\n\nUpdate: A weird fix for this trouble is to toggle enable for the \"Box Select\" entry when it is expanded. Don't know why it fixes the issue. If toggled again when it is folded, the problem comes back." ]

[ "Rigid body baked cache not invalidated\nOperating system: Windows 10 Pro 64-bit\nGraphics card: 4095MB NVIDIA GeForce GTX 1080 (NVIDIA)\n\nblender-2.80rc1-windows64\nWorked: (optional)\n\nSimple physics object is trapped in previous (deleted) animated properties.\n\nI have included a blend file which consist of just a cube with physics properties added.\nIt is supposed to fall but it moves to the origin and stays there.\nThe file is a working file from which everything has been deleted and a cube added.\nRun the animation and the cube will behave oddly.\nIf the cube is deleted and a different mesh added, say a sphere and moved and basic physics assigned. It will do the same.\nThis is likely to be a problem with my file from which everything has been deleted??\n[physics-problem.blend](physics-problem.blend)", "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)", "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", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Cycles shading glitch\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.4.1\nWorked: ?\n\nCycles shows incorrect shading, also different from Eevee. (The file is very simplified just to showcase the problem)\nI'm thinking it is a variation of T99933 bug but not sure so tell if that's the case\n\n[bug.blend](bug.blend)\n1) Open the file, switch to rendered view. Normals should look like this\n\n2) In the material disconnect the alpha socket, now it should look different.\n\nIs alpha supposed to affect normals at all?\n3) Repeat the same in Eevee, results look consistent", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "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!", "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", "Crash when trying to show a Workspace using a deleted Screen.\nIf a Screen ID is deleted, and one then try to show a Worspace using it, Blender will crash.\n\nSetting to low prio since deleting a Screen ID is not easy to do for end user currently (you'll have to use py console, e.g. `bpy.data.batch_remove(ids=(bpy.data.screens- [x],))`), but still, this is violating general design and expected sane behavior of ID handling.\n\nThink solution should be either:\n* Deleting Screens IDs should be forbidden (not ideal, since it kind of breaks general ID design, but should be doable).\n* Deleting Screens IDs should also delete matching Workspace (not ideal either, there should not be that kind of relationships between IDs, but we already have similar things between objects and obdata...).\n* Or (probably the sanest thing to do) a Workspace should handle gracefully the case where it has no assigned Screen.", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "blender 3.0 cannot render this file with audio\nProcessor\tIntel(R) Core(TM) i7-10750H CPU @ 2.60GHz 2.59 GHz\nInstalled RAM\t16.0 GB (15.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\n\nEdition\tWindows 11 Home\n\nGraphics Card: NVIDIA GeForce RTX 2060 \n\nThis problem happens only with these files, It works fine with other files.\n\nI think that I have setup rendering props ok, Using mp3 for audio output.\nThis file will render video only. It will also render audio audio only from the render tab. \nI have tried any number of combinations of audio and video output (mp4, mp3, etc).\n\nI have tried for weeks to solve this, with no success. Please help. \n\nThank you for your attention,\n\nRoberto Collins Lazo\n\nKept trying different starting and ending points for the video. Rendering only audio crashes with more than a short starting and ending points.\n\n\n**Steps to reproduce**\n[#94586.blend](T94586.blend)\n\nOpen file and render animation. No sound is rendered.", "Unbaked Dynamic Paint Not Displayed in Rendered Output but Shows in Viewport\nOperating system: Manjaro 18.0.1 Illyria / x86_64 Linux 4.14.90-1-MANJARO\nGraphics card: Nvidia 1080 Ti\n\nBroken: 2.80 (sub 39), Commit date: 2018-12-29 18:10, Hash 266b1e2cdbc1\nWorked: 2.79 (sub 6), Commit date: 2018-10-22 16:17, Hash 86dbbd156fa\n\nUnless baked, dynamic paint does not affect the final rendered image but is properly displayed in viewport.\nThe default and expected behavior is to be able to render the effect regardless if baked or not. This is how 2.7x operated in the past.\nMoreover this problem, which I assume has something to do with vertex colors [has caused other issues ]] with different [[ https:*github.com/hsab/tensionmap | addons ](https:*github.com/JacquesLucke/animation_nodes/issues/989) that depend on similar workflows of modifying the vertex color using the python API (eg. proximity, stress mapping etc.) \nNot sure if #51214 is related since it's from April 2017. If so please close as a duplicate.\n\nTwo blend files attached, one for 2.8 and one for 2.79.\n2.79 file works as expected.\n2.8 file is broken unless baked.\n\n2.79.6 Render:\n\n\n2.80.0 render:\n\n\n[dynamicpaint2.8.blend](dynamicpaint2.8.blend)\n[dynamicpaint2.79.blend](dynamicpaint2.79.blend)", "blender 4.0 shutdown immediately after launching\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nblender 4.0 latest build shutdown immediately after launching . and i think its cant overwrite the file showing in the image .when i deleted that file and try to launch blender its work just fine . after doing some stuff blender got crashed 🙃 and the same thing happen again (can`t launch) and so i have to do the same method to get it to work again 🙂👌\n\n----\n\n", "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", "Error: Illegal address in CUDA queue copy_from_device\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\n\nWhen rendering in GPU mode, Render crashes.\n\nAttached Blend File\nAny frame after 1150 crashes on render with the title error for us.\nTry rendering frame 1160 - This one crashes for me all the time.\n\n" ]

[ "Blender 2.80 intel hd selecting bug\nOperating system: Windows 8.1 64 bit\nGraphics card: intel hd 4400\nComputer: Lenovo yoga 2 pro 13'\n\nBroken: (blender-2.80.0-git.03672e77836d-windows64)\n\n**Edit mode selecting problem**\n\n**When I want to select edges, faces, vertexes, it doesnt seems. You can see the video which I uploaded.**\n[blenderissue.mp4](blenderissue.mp4)", "Crash in Edit Mode!\nOperating system: Windows 7-6.1.7601 64 Bits\nGraphics card: Intel(R) HD Graphics 4600\n\nBroken: (example: 2.80, git.e78770039397 commit date: 2019-05-22 09:41\nWorked: blender 2.79\n\n\n\nWhen I use Blender in edit mode, I can not use it because the vertex is broken into one side.\nNow I'm using it on my school computer and it only worked well on my Blender 2.79 version.\nSee the image for details.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. In Blender 2.79 version, the edit mode that was in operation does not work and vertex is fixed to the right.\n2. This error is fixed even when the screen is turned.\n3. It's so embarrassing to see this screen at the stage of learning Blender.\n", "Edit Mode - Intel HD 4x00 display glitch on Windows 7/8\nOperating system: Windows-7-6.1.7601-SP1 32 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.4414\n\n\nBroken: version: 2.80 (sub 61)\nWorked: (optional)\n\n\nWhen I switch to edit mode, the cube has messy display.\nI still can edit that, but all vertices always on the right screen.\nThis is happen when i try blender 2.8 beta compiled 2019-05-10.\nEdit mode works fine in previous build.\nScreenshots available below:\n\n\n\n\n\n\n\n\n" ]

[ "After updating the video card drivers to 20.11.2, interface artifacts appeared.\n{[F9329300](Снимок_экрана_2020-11-19_212921.png)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 590 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.83.9\n\nMultiple artifacts can appear [see merged reports and see below]\n\n\n|  |||\n| -- | -- | -- |\n\nAfter updating the video card drivers to 20.11.2, interface artifacts appeared\nPossible workaround: downgrade GPU driver\n\nWe had more user state that enabling Render Properties > Performance > High Quality Normals avoids the drawing issues with Eevee.", "Very strong aliasing in 3.2\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2\nWorked: 3.0\n\nin 3.2, there is a very strong aliasing in edit mode. In 3.0 it is not so strong\n3.2:\n\n\n3.0:\n\n\nboth versions have the same settings. There are 16 samples everywhere and smoothing in edit mode\n[jupiter.fbx](jupiter.fbx)", "Black render artifact with CPU+GPU rendering in viewport\nWindows 7 Pro\nNvidia Quadro P6000\nIntel Xeon E5-2690 v4\n\nBroken: daily builds 2.79 since at least 25.10.2017.\nWorked: -\n\nIf I enable combined CPU+GPU rendering, a black rectangle shows up on one of my objects. It shows up in viewport rendering, and also in the final render. This seems to be independent of the material used. I have provided a stripped down version of the scene where it is still visible. This time only in the viewport, the final render works for this simplified scene. \n\nThe artifact seems to be \"locked in space\", I can move or rotate the object away, so that it disappears. In some rotation angles it is not a black rectangle, but dense black lines. \nWhat is also interesting is that the surface of the object in not only black, but partly transparent. I have put a lamp and a cube inside the object in the demo scene, these should not be visible from outside, but they are.\n\n- Open file. In the render settings GPU compute should be turned on, and in the user preferences CUDA should have both the CPU and GPU selected.\n- Turn on viewport rendering. --> black box visible.\n- Then switch to CPU rendering. No more black box.\n\n[black_artifact_bug3.blend](black_artifact_bug3.blend)\n\n", "Improved way to display weight painting colors\nWeight group colors in vertices blend between their neighbors by going through the entire range of values between the 2 points\n\n\nFor example if a vertex has a 1.0 (red) value and one of it's neighbors has a 0.0 (blue) value, the face will show a rainbow interpolation going trough orange, yellow, green, cyan and finally blue\n\n\nIn certain situations where each of the vertices of a face have different values (like 1.0, 0.5, 0.75, 0.0) it will create weird intersections in the middle that look like there is a vertex there that doesn't exist\n\n\nThe problem is even worst when the wireframe is not displayed and we only see gradients of colors indicating vertex values that do not exist\n\n\nThe solution is to fix the color blending mode to simply **mix** between the 2 neighboring colors. This way it is very clear that vertices have values of 1.0, 0.75 and 0.5 and nothing in between.\n", "Multiscatter GGX is bugged\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.5\n\nOn a glossy Multiscatter GGX material, highlight on reflection seem to look dark and kinda like a donut at around 0.02 roughness.\nIt also seems to change depending on focal length and only happens when using the environment to light the scene\n> | rough 0.03 | rough 0.02 |\n> |---|---|\n> |  |  |\n\n\n- Add an HDRI to the scene\n- On an object (preferably flat) set a Glossy BRDF material with Multiscatter GGX\nThe HDRi used in the image is this one: autoshop_01\n[multiscatter_bug.blend](multiscatter_bug.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)", "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", "Strange background grid pattern appears on the compositor panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9079\n\nBroken: version: 2.93.5\nWorked: 2.91.2\n\nStrange grid pattern appears on the compositor background when zooming in (when backdrop is on).\n\nThis is what it should looks like:\n\n\nThis is what it actually looks like:\n\n\nAnd this only happens when I zoom in. At a very far-away view the background gradually becomes normal:\n\n\n\n\nThis does not happen on my other devices, so I think it might be a hardware compatibility problem. Also, I had the latest graphic driver installed and the graphic card supports OpenGL 4.6:\n\n\n- Open blender\n- Switch to the compositor workspace,\n- Enable backdrop\n- zoom in.\n\n", "Generic Input in a Group Node displays as Grayscale, when it is in fact neutral.\nSolution: \n\n\n\nIn the example above, the only change would be that the socket next to the Input would be empty instead of gray. This would fix the wrong impression that it's a Grayscale input - it's not, it's neutral as Sergey stated.", "Compositor DropOuts: Vertical Green Lines\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\nBroken: version: 3.10 Beta, 3.20 Alpha\nWorked: 2.93.6\n\nThe compositor will render randomly vertical green lines.\n\n- Unzip archive\n- Check the movies in folder \"Combine\" for the described dropouts\n- Load the attached scene\n- Render > Render Animation\n\n[RB220206_Blender_301_Comp_DropOuts.zip](RB220206_Blender_301_Comp_DropOuts.zip)", "Cycles render artifacts relating scene scale\nOperating system: Windows 10\nGraphics card: tested multiple graphics cards with same issue\n\nBroken: 2.83.6 (file originally made in 2.79 and had the same issue)\n\nThere exists in the blend file data only two objects - the camera and a simple plane. Yet when rendering, the result does not match the viewport and there seems to be another ghost object appearing in the scene.\n\nBased on the following startup file: [strange-error.blend](strange-error.blend)\n\n1. Switch to rendered view in the viewport. This is how things should look.\n2. Now render the current frame at frame 97. Notice the strange ghosting effect in the center of the frame.", "Cycles noise texture with high distortion differences between CPU and CUDA\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Quadro M4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.82 (sub 3)\nWorked: (optional)\n\nCycles appear to produce different random values for CUDA tiles and CPU tiles.\n\nOpen [TileBug_CUDA+CPU.blend](TileBug_CUDA_CPU.blend) and compare rendered view with rendered output.\nImages of the bug in isolation.\nCPU Only - Fine:\n\nCUDA Only - Fine:\n\nCPU + CUDA - Bugs out:\n\n\nIn addition, I had some even more strange artefacts in a real render.\nThe random effect is more subtle here, but it's there. But the other ones I can't really reproduce, not sure what is going on with that:\n\n\nI can't update drivers, due to other software requiring certain certified drivers. Windows 10 is up to date.", "CPU + GPU render precision differences for small, far away area light\nOperating system: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\nBroken: version: 2.81 (sub 8)\nWorked: (optional)\n\nThis was recently reported in this thread : \n2\n\n I can at least say, that when using small area lights below a size of 1 (e.g. meter), and it’s getting darker (the light source is far away from the object) you can clearly see this problem: CPU renders the tiles darker than the CUDA GPU.\n\n\n\nCreate a new scene with the cube, remove the default light, create an area light, resize it to lets say 10% (or 1%… the smaller the bigger the effect) and rotate it that it lights the default cube.\nHere is a .blend that reproduce the issue :\n[TileProblem.blend.blend](TileProblem.blend.blend)\n\n", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Black and white pixels appearing in render and viewport when rendering with HIP in Cycles (Blender 3.1.2)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 21.Q4 30.0.14011.2006\n\nBroken: version: 3.1.2\n\n\nViewport and render displayed Black and white pixels in places that should not be black or white when rendering using HIP. On the attached image, the mushroom shows it best and is a hotspot for these broken pixels. Switching to CPU rendering fixed the issue. \n\n*Open attached blend file\n*Set rendering to 'HIP' in preferences, switch to GPU compute for rendering\n*In rendered view in the viewport, there will be black + white error pixels. The more samples are used, the more of these pixels are visible.\n*Rendering the image has the same result. \n[TheWetland.blend](TheWetland.blend)\n\n\n\n" ]

[ "video sequencer having random colourful dots \nOperating system: Windows10\nGraphics card: intel irisXe{not activated}\n\nBroken: (stable 3.2.0)\nWorked: ( )\n\n**video sequencer having random colourful dots when opened 2nd time**\n\n**open blender as normal go to pre-setup's video editing\nsometimes the error is already present or \ngo to file-new- video editing if not seeing click \"N\" and not came yet move the window around \n\n\n\n\n\n{interesting to know it shows up in ordinary file if the window was changed(in video sequencer )\n and it does not effect any thing other than the visuals and \nit kinda looks like a image that was recently used somewhere if observed close}\n**\nit is less likely to happen in the first file you open\n\nBased on the default startup or an attached .blend file ().the file-\n[error.blend](error.blend)\nGood luck" ]

[ "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. Mesh/color filters. RMB do not cancel operation immediately\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.6.0 Alpha\n\nIf i press and drag with left mouse button, right click do not cancel operation and revert it immediately. It is a bug and inconsistency with grab/rotate/scale for example. RMB works with GRS awesome, as it should!\n\n", "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)", "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", "Segfault on unregistering operator/menu with open props dialog.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92, 2.93\n\n\nWhen an operator currently has a `wm.props_dialog_(self)` open, unregistering it will cause a segfault.\n\nThis only seems to happen reliably when the module it's from has at least one `bpy.types.Menu` subclass that's also been registered.\n\nThe displayed values of property fields in the dialog will sometimes flicker and switch values with each other for a split second before the segfault.\n\n\n[InvokeSegfault.blend](InvokeSegfault.blend)\n\n1. Open the attached file.\n\n2. Invoke the operator from the 3DView toolbar.\n\n3. Use a system hotkey (E.G. `ALT`+`TAB`) to switch to the window with the text editor space while leaving the props dialog open.\n\n4. Run the script again from the text editor window.", "Error: Illegal address in CUDA queue copy_from_device\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\n\nWhen rendering in GPU mode, Render crashes.\n\nAttached Blend File\nAny frame after 1150 crashes on render with the title error for us.\nTry rendering frame 1160 - This one crashes for me all the time.\n\n", "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", "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", "Indices order is inconsistent with duplicate operation\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.2.0\n\nIndices on copied geometry (in edit mode) are sometimes reversed (verts) or misplaced (edges). Not sure when it happens exactly, but it can happen, if you duplicate and delete new geo couple times.\n\n\n\n\n - Enable *indices* overlay to see results\n - Create clockwise mesh loop (for example draw it in *Edit mode* from single vert via *ctrl + mouse click*)\n - Select mesh and press *shift + D* and *Enter*\n - Check verts indices order, it should match initial clockwise direction\n # Delete copied geometry and repeat steps 3 & 4 -> indices should be reversed. (Interesting thing that if you change *Mode* option in operation's menu from 1 to 0 it preserves original order)\n\nOr in attached file perform steps from 3 to 5\n\n[indices_order.blend](indices_order.blend)\n\n", "Modifying keymap produces unreliable results when duplicate entries exists\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: 2.83-3.0\n\nModifying keymap produces unreliable results when duplicate entries exists.\n\n**Steps to reproduce**\n1. To create duplicate keymaps apply patch \n[P2817: (An Untitled Masterwork)](P2817.txt)\n```\ndiff --git a/release/scripts/presets/keyconfig/keymap_data/blender_default.py b/release/scripts/presets/keyconfig/keymap_data/blender_default.py\nindex 5fb0f052154..ad335883afa 100644\n--- a/release/scripts/presets/keyconfig/keymap_data/blender_default.py\n+++ b/release/scripts/presets/keyconfig/keymap_data/blender_default.py\n@@ -2758,20 +2758,28 @@ def km_sequencercommon(params):\n def km_sequencer(params):\n items = []\n keymap = (\n \"Sequencer\",\n {\"space_type\": 'SEQUENCE_EDITOR', \"region_type\": 'WINDOW'},\n {\"items\": items},\n )\n\n items.extend([\n *_template_items_select_actions(params, \"sequencer.select_all\"),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n+ {\"properties\": [(\"type\", 'SOFT')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n+ {\"properties\": [(\"type\", 'HARD')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n+ {\"properties\": [(\"type\", 'SOFT')]}),\n+ (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n+ {\"properties\": [(\"type\", 'HARD')]}),\n (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS'},\n {\"properties\": [(\"type\", 'SOFT')]}),\n (\"sequencer.split\", {\"type\": 'K', \"value\": 'PRESS', \"shift\": True},\n {\"properties\": [(\"type\", 'HARD')]}),\n (\"sequencer.mute\", {\"type\": 'H', \"value\": 'PRESS'},\n {\"properties\": [(\"unselected\", False)]}),\n (\"sequencer.mute\", {\"type\": 'H', \"value\": 'PRESS', \"shift\": True},\n {\"properties\": [(\"unselected\", True)]}),\n (\"sequencer.unmute\", {\"type\": 'H', \"value\": 'PRESS', \"alt\": True},\n {\"properties\": [(\"unselected\", False)]}),\n\n```\n \n\n2. Remove shift modifier key from all `sequencer.split` keymap entries\n - First time this works, after that entries will be removed\n3. Try to set Shift modifier key for last `sequencer.split` keymap entry.\n - This sets Shift modifier key on first `sequencer.split` keymap entry.\n4. Try to set Shift modifier key for second `sequencer.split` keymap entry. (Type is Hard)\n - This entry will jump to bottom and it is last entry now.\n", "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", "Creating Lattice object with script with {\"REGISTER\", \"UNDO\"} if parameters was changed in Undo window and mesh was in Edit mode - undo last changes to the mesh or last action\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.1\n\n{\"REGISTER\", \"UNDO\"} also undo last action if parameters was changed in \"Adjust last action\" pannel and mesh was in Edit mode.\n\n[Register_Undo_Issue.mp4](Register_Undo_Issue.mp4)\n\n[REGISTER_UNDO_in_EDIT_Mode.blend](REGISTER_UNDO_in_EDIT_Mode.blend)\n\n", "Adjusting spotlight blend using gizmo does not register undo\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nThe gizmo control is introduced in 3c8c0f1094.\n\nAdjusting spotlight blend using gizmo does not register undo\n\n[SpotlightBlendGizmoBrokenUndo.mp4](SpotlightBlendGizmoBrokenUndo.mp4)\n", "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", "OpenGL error in console\nOperating system: Windows 10, 11\nGraphics card: 6700 XT, 6800 XT, driver 23.7.2 \n\nBroken: 4.0.0, ecb3262bf04, main, 08.08.2023\nWorked: no information.\n\nFirst of all it's better to run Blender with USD built with this fix 2550 since it fixes a lot of other OpenGL errors in console.\n\nThere is an error in console `Runtime Error: in HgiGLPostPendingGLErrors at line 91 of C:\\GPUOpen\\RPRHydraRenderBlenderAddon\\USD\\pxr\\imaging\\hgiGL\\diagnostic.cpp -- GL error: invalid framebuffer operation, reported from __cdecl pxrInternal_v0_23__pxrReserved__::HgiGLBuffer::~HgiGLBuffer(void)` If you select `Render Engine = Hydra Storm` and run Viewport Shading and stop it.\n\nBut if you start Blender with `--debug-gpu` flag you will an error in console `ERROR (gpu.debug): : GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9` and above error with `HgiGLBuffer::~HgiGLBuffer` won't appear anymore.\n\nI put some `debug::check_gl_error` in `detect_mip_render_workaround` and one of them returns `GL_INVALID_FRAMEBUFFER_OPERATION` right after `glClear(GL_COLOR_BUFFER_BIT);` and one more error `GL_INVALID_VALUE` after `glGetTexImage`.\n\nAlso `glCheckFramebufferStatus(GL_FRAMEBUFFER)` returns `GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT`.\n\nI tried to get rid of `HgiGLBuffer::~HgiGLBuffer` error via calling `glGetError`. There are only 2 places worked for me: \n1. ViewportEngine::~ViewportEngine;\n2. End of the `detect_mip_render_workaround`.\n\nDefault startup. \nFirst:\n1. Select `Render Engine = Hydra Storm`\n2. Start Viewport Shading\n3. Stop Viewport Shading\n4. Look in the console\n\nSecond:\n1. Start Blender with `--debug-gpu` flag\n2. Look in the console\n\n" ]

[ "Resetting multi-button value does not work when active button value is the same\nOperating system: Linux-5.12.15-300.fc34.x86_64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31\n\nBroken: version: 3.0.0 Alpha, branch: latest master\nWorked: Caused by eb06ccc324\n\n[multi-button-reset.mp4](multi-button-reset.mp4)\n\n1. Find a vector exposed in the UI\n2. Set the first value to 0\n3. Set the second value to 1\n4. Drag down from the first button to edit all three values\n5. Type in 0\n6. Press enter\n7. Observe the bug\n" ]

[ "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\n\n", "closest_point_on_mesh() freezes Blender when called from a driver\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: 2.79\n\nCalling closest_point_on_mesh() from within a driver causes Blender to freeze.\n\n[test2.blend](test2.blend)\nOpen the file allowing scripts -> Freeze", "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", "File Browser: Blender freezes for half a minute when opening File Browser\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: 3.5, 3.6, 4.0\n\nIn Blender when I access a file that has a shortcut to my private cloud storage, which contains an IP address (\\192.168..*), Blender freezes.\nThe cloud storage is not running most of the time, so it could be that Blender is trying to read the folder but fails, because the storage doesn't respond (because it's turned off).\nGeneric Windows File Explorer does the same thing when I open the folder (but doesn't freeze ofc, just trying to load it until timeout).\n\n<video src=\"attachment\" controls></video>\n\nYou will need a shortcut-file that points to some address on the network that takes a long time to load.\nOne way I found to create a shortcut like this is by:\n- On a local network, access a file from a computer on the network and create a shortcut to that file\n- Shut down the network or the computer being accessed.\n\nNow that we have this shortcut-file, in Blender, just do this:\n- Open File Browser in any way (loading file, or texture, or click on File > Import > Wavefront (.obj).)\n- Go to the directory with the shortcut-file\n\nAfter some time, the files may finally appear and the delay disappears when accessed again.\nTo replicate the delay again, close and reopen Blender.\n\n", "Fluid inside Effector / Fluid Inside Closed Object not Working\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\nWorked: 2.83 (#104938)\n\nFluid simulation stops flowing while inside effector whether the effector its one mesh or separate mesh.\nThis also works, when I created a holes in the mesh, but I really need to close it completely for my actual project.\n\n\n[Fluid Inside Effector.mp4](Fluid_Inside_Effector.mp4)\n\n\n\n[Fluid Inside Effector.blend](Fluid_Inside_Effector.blend)\n", "(Linux; AMD Radeon GPU) Rendering a complex scene with eevee crashes desktop environment / causes rendering and viewport artifacts\n```\nOperating system: EndeavourOS Linux / Fedora Linux (Same issue on both distros)\nGPU: AMD Radeon RX 6800 XT (16 GB VRAM)\nCPU: AMD Ryzen 5 3600\n```\n\n```\nrenderer:\t'AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64)'\nvendor:\t\t'AMD'\nversion:\t'4.6 (Core Profile) Mesa 22.3.7'\ndevice type:\t'AMD'\nbackend type:\t'OPENGL'\n```\n\nBroken: 3.4.1, 55485cb379f7, blender-v3.4-release; 3.5.0 Release Candidate, d5d8246441a5, blender-v3.5-release (both version exhibit the issue)\n\nWhen rendering complex scenes in Eevee (Scenes with many different objects), one of the following occurs:\n\n 1. On **X11**: Computer freezes for about 5 seconds before all monitors cut to black. After about 5 seconds on a black screen, the login screen appears and I can log in as normal, as if I logged out. All of the applications have closed.\n 2. On **Wayland**: Render finishes rendering, but many of the objects appear broken; they are semi transparent or appear as if they were using the holdout shader. Returning to the viewport causes all objects with transparency to flicker randomly and appear distorted. Occasionally, the desktop of the computer itself will become broken and artifacted, only logging out or restarting fixes it. This usually isn't possible, however, as after a short while everything all displays cut to a black screen. Unlike X11, however, the only way to recover from this is to restart the PC by holding down the power button.\n\nThis issue **only occurs on linux and does not occur on my Windows 10 partition**, even with the exact same settings and scene. It also only occurs when actually trying to render the scene. In the viewport everything works just fine, even on rendered view where everything looks the same as it should in the render.\n\nThis issue seems to occur regardless of the GPU Usage; even when I limit the GPU clock and power draw significantly it still happens.\n\nThe attached .blend file is an example of a simple scene which triggers the bug. It seems to occur no matter what the render settings are set to.\n\n", "Scene update bug\nSystem Information\nwindows7 64\nASUS ATI Radeon HD6870\n\nBlender Version\nBroken: (All)\nWorked: (None)\n\n\n\n\n\n\n\n\nopen this file, select plane and try to select for this plane any mesh - all this meshes don't have users, but was saved, try to select material - materials was saved, but don't have users, \nwe can revert, close and open again many times - materails and meshes will be saved.\ntry to add gruop instance - we will have all this groups is empty.", "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", "Local view mode is not exited correctly when closing New Windows\nOperating system: Mac OS*\nGraphics card: Macbook pro M1 MAX, 64G ram\n\n**Blender Version** 3.41 (same issues found in 3.2)\nBroken: Local view doesn't work(/)\nWorked: \n\nit's hard to say when it will happened, I used MacBook with two monitors, (one is Mac Studio, an other one is iPad Pro), when I duplicate a new windows to my second screen, like to iPad for sculpting, some times, local view function(hot key\"/\") doesn't work and show 'no more than 16 local views\" error. I met this error 3times from version 3.2 to 3.41\n\n\n\n\n- Repeat the following 16 times\n - Open a new `Window`->`New Window`\n - Go into Local view in the new 3d viewport that appears\n - Close the window while still inside local view\n- Attempt to go into local view 1 more time\n- Observe failure\n\nThe issue is that local view mode is not exited when those temporary New windows are closed. Blender continues to think that those local views are still in use and runs out of available space for any new ones.\n\n[test.blend](test.blend)\n\n", "Blender Selection Lag\nOperating system: Windows 8.1 64bit\nGraphics card: Intel(R) HD Graphics 4400\n\nBroken: \nblender-2.83-39aa122a0e6d-windows64\nblender-2.90-4f622c9a080b-windows64\nblender-2.90-5254ffa17bf0-windows64\nWorked: \nblender-2.79b-windows64\nblender-2.80-windows64\nblender-2.81a-windows64\nblender-2.82a-windows64\n\n\nBlender's selection tool started to lag noticeably behind the mouse. \n\nSteps to reproduce:\n1. Open Blender 2.83 / 2.90 Beta and Alpha\n2. Select Circle select or Box select\n3. Move around the mouse to see the lag\n\nNot sure if this is intended or a new known issue.[SelectionLag.avi](SelectionLag.avi)", "Blender 3.5.1 keeps crashing on occasion\nOperating system: Mac OS Ventura 13.3.1 (a) (22E772610a)\nGraphics card: Apple M1 Ultra (64-Core GPU)\n\nBroken: Version 3.5.1 (3.5.1 2023-04-25)\nWorked: N/A\n\nBlender occasionally crashes on my new Mac Studio (I used to work on a Windows PC beforehand and never had that problem). I'm guessing it is a saving error.\n\n- Download and open the demo-file `Blender 3.4 – “Charge” Open Movie` from demo-files/\n- Change the engine from Eevee to Cycles GPU\n- Set \"Viewport Shading\" to \"Rendered\" - nothing happens\n- Go back to Solid View - blender freezes\n\nAttached is is a video demonstrating what is happening, but in a few words:\n\nThe same happens with some of my heavy(ish) project in 3.6.0 beta\n\nIn 3.5.1 the same project responds in render view as it should be.\n\nWhen I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached)\nI manage to reopen the project after a few crashes.\n\nI hope it helps! \n\n\n", "Blender freezes when deleting or unparenting nurbs path (hangs in particle collision detection)\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.25\n\nBroken: version: 2.93.1\n\nBlender will hang if attempting to delete or unparent empty controlling this model that is parented to the curbs path.\n\n\n1. Open attached blend file.\n\n2. Delete nurbs path\n\nResult = Blender will hang.\n\n3. Attempt to remove parenting to nurbs path by selecting object properties of the Empty \"Nautilus Empty v2\".\n\nResult = Blender will hang.\n\nN.B. - The file is simplified as much as possible. The collection \"Nautilus\" was appended into a brand new Blend file.\n\n[Blender Hangs Deleting Nurbs Path.blend.zip](Blender_Hangs_Deleting_Nurbs_Path.blend.zip)\n\n\n\n", "project turning purple automatically after closing and opening later+zoom in/out buttons not working properly.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.79\n\nBroken: version: 3.6.2\n\n\n\n", "Trackpad stops working for a while\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M\n\nBroken: 3.6.2\nWorked: don't know\n\n\nSometimes, Blender stops responding to trackpad gestures such as two-finger scroll or pinch zoom. This is not just in the viewport but everywhere - I can't scroll menus or the node view, for example.\n\nThe UI is otherwise responsive when this happens - I can scroll menus by dragging the slider at the edge, just not with a two-finger scroll.\n\nIf I go and do something else in another app for a few minutes, it usually fixes itself.\n\nThis happens sporadically and I don't have a reliable way to reproduce it, but it seems to happen often after I render an image - after the image has rendered, I try to use pinch-zoom to look more closely and find I can't. I am not sure if it happens in other situations as well - if it does I will update this report.\n\n\nI'm afraid that I can't reproduce this reliably - it just happens every now and then, in any .blend file. I am happy to take any advice on how to look for a way to reproduce it.\n\n", "stack_overflow exception while rendering with viewport render on\nOperating system: win10\nGraphics card: 2070super\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 2.83.4, 2.91 6fe609d4c3\n\n\nwhen pressing f12 in render mode, blender crashes,\nwhen pressing render in solid mode, blender doesnt crash\n\n[blender_debug_output.txt](blender_debug_output.txt)\n```\nError : EXCEPTION_STACK_OVERFLOW\nAddress : 0x00007FFF42963FDB\nModule : C:\\Windows\\system32\\DriverStore\\FileRepository\\nv_dispsi.inf_amd64_6af46268c19e4980\\nvcuda64.dll\n```\n[2.blend](2.blend) \n1. switch to render mode\n2. press f12 & watch task manager.\n3. blender will close" ]

[ "Blender 2.83beta crashes right after closing Preferences dialog on Fedora 32\nOperating system: Linux-5.6.7-300.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.6.7-300.fc32.x86_64, LLVM 10.0.0) X.Org 3.3 (Core Profile) Mesa 20.0.5\n\nBroken: version: 2.83 (sub 15)\n\nBlender 2.83 (sub 15) crashes right after closing Preferences dialog on Fedora 32.\n\nDownload the Blender 2.83 (sub 15) from the buildbot environment, launch it directly or from the Terminal using \n\n/opt/blender/blender --debug\n\nUnder the \"File\"-menu select \"Defaults\" and then \"Load Factory Settings\" to begin fresh. Now go to the \"Edit\"-menu and select \"Preferences\". It doesn't matter if chanes are made there or not, click \"Save Preferences\" and close the Preferences-window. Now it will take a few seconds in which the mouse can be moved and such, after which clicking the mouse will not be registered anymore and Blender itself crashes. The Terminal then contains the following lines:\n\n\n```\n[machinename@macpro ~]$ /opt/blender/blender --debug\nSwitching to fully guarded memory allocator.\nBlender 2.83 (sub 15)\nBuild: 2020-04-29 08:47:09 Linux Release\nargv[0] = /opt/blender/blender\nargv[1] = --debug\nRead prefs: /home/machinename/.config/blender/2.83/config/userpref.blend\nread file /home/machinename/.config/blender/2.83/config/startup.blend\n Version 283 sub 15 date 2020-04-29 08:26 hash 839fe335d2d6\nfound bundled python: /opt/blender/2.83/python\nread file \n Version 280 sub 39 date unknown hash unknown\nWriting userprefs: '/home/machinename/.config/blender/2.83/config/userpref.blend' ok\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n[machinename@macpro ~]$ \n\n```\nAnd the /tmp/blender.crash.txt file contains the following lines:\n\n\n```\n# Blender 2.83 (sub 15), Commit date: 2020-04-29 08:26, Hash 839fe335d2d6\n\n# backtrace\n/opt/blender/blender(BLI_system_backtrace+0x1d) [0x69841ad]\n/opt/blender/blender() [0xc14bb2]\n/lib64/libc.so.6(+0x3cab0) [0x7f42923cdab0]\n/usr/lib64/dri/r600_dri.so(+0x5b4d6e) [0x7f4265a88d6e]\n/usr/lib64/dri/r600_dri.so(+0x6ddc63) [0x7f4265bb1c63]\n/usr/lib64/dri/r600_dri.so(+0x125f5e) [0x7f42655f9f5e]\n/usr/lib64/dri/r600_dri.so(+0x128213) [0x7f42655fc213]\n/usr/lib64/dri/r600_dri.so(+0x133794) [0x7f4265607794]\n/usr/lib64/dri/r600_dri.so(+0x13078e) [0x7f426560478e]\n/usr/lib64/dri/r600_dri.so(+0x122b62) [0x7f42655f6b62]\n/usr/lib64/dri/r600_dri.so(+0x357b4d) [0x7f426582bb4d]\n/usr/lib64/dri/r600_dri.so(+0x357c05) [0x7f426582bc05]\n/opt/blender/blender(immEnd+0x2f9) [0x5690a49]\n/opt/blender/blender(ED_region_do_draw+0xbaa) [0x121f44a]\n/opt/blender/blender(wm_draw_update+0x52d) [0xec287d]\n/opt/blender/blender(WM_main+0x30) [0xec0820]\n/opt/blender/blender(main+0x321) [0xb4b7d1]\n/lib64/libc.so.6(__libc_start_main+0xf2) [0x7f42923b8042]\n/opt/blender/blender() [0xc113dc]\n\n\n```\n\n", "Save File : Saving new file causes Blender to freeze and crash\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: AMD Radeon HD 5700 Series ATI Technologies Inc. 4.5.13417 Core Profile Context 15.301.1901.0\n\nBroken: version: 2.90 (sub 0)\nWorked: 2.82\n\nAs the title says: On my system, saving a new file crashes Blender, ever since the last version of 2.83 I tried.\nThe file still saves properly, it can be loaded after re-starting Blender and will save without crashing on every subsequent save. \n\n1) Create a new blender file\n2) Save file anywhere under any name\n3) Blender should freeze and crash once the file is saved\n\n" ]

[ "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", "Point lamp power value hard to change with unit scale (button step is calculated for Watts, but applied to milliWatts)\nOperating system: Windows 10 Home 1909\nGraphics card: NVIDIA RTX 2080 Ti\n\nversion: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f771, type: Release\nWorked: 2.82a\n\nIf I insert a point lamp to the scene and I alter the power value of the lamp sliding left and right it works. If I click then in the power field and type a value (e.g. 10W) and confirm with enter it takes the new value, but afterwards I'm not able to change the power value sliding right and left or using the arrows left and right of the field. I have to click again in the field and enter a value.\n\nCreate a point lamp\nEnter the power value in the field (e.g. 10W) and confirm with enter\nSlide the power field slider left and right, the value is not changing.\nClick on the left/right arrow of the power slider, the value is not changing.\nClick in the power field and enter a new value, confirm with enter. The new value will be accepted.", "Cycles not really excluding lights from volume MIS calculation\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nI noticed that cycles, when using volume lights, if we exclude lights from the volume contribution it still affects the sampling of the visible volume lights.[Volumeissue.blend](Volumeissue.blend)\n\nIve included the blend file and also described the issue visually in this thread:\n10982\n\nTo check the issue just turn on and off the Volume Scatter ray visibility and compare the result by hiding the lights instead.\n\nI think this is a serious performance issue in scenes with multiple lights, with some lights contributing to volume while others not, which forces the user to unnecessarily throw a lot of volume samples to get rid of the noise.\n\n\n", "Shader Nodetree Error: Invalid implicit socket conversion: Shader -> Color\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.33\n\nBroken: version: 3.3.1\nWorked: I don't know but the problem is also present in the version 3.0.0\n\n\n```lang=glsl\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.3\\config\\userpref.blend\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n\n 7164 | invert(float_from_Closure(tmp34), node_tree.u36, tmp37);\n |\n | Error: C1503: undefined variable \"float_from_Closure\"\n\n\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n\n 7164 | invert(node_tree.u35, vec4_from_Closure(tmp34), tmp37);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n\nShader Nodetree Error: Invalid implicit socket conversion\nShader Nodetree Error: Invalid implicit socket conversion\n```\n\n\n1. EEVEE render\n2. Shader editor: put some shader socket to color socket\n3. Check the console", "Volumetrics: Add Light Grid support\nVolumetrics are currently not affected by lightgrids. FIX THAT.", "Working sliders are faded in the overlays panel\nBroken: 3.0\n\n**Short description of error** \nthe wireframe and wireframe opacity sliders are faded in the overlays panel even when they're working.\n\nFor better visibility, delete the cube, add a suzanne, press ctrl+3 to subdivide it, then apply the modifier.\nIn the Object Properties, under viewport display, turn on \"show edges\" OR set the object to \"Display As: Wire\".\nIn the viewport's Overlays panel, drag the wireframe threshold and wireframe opacity sliders. Make sure that you are in solid shading and the wireframe option is off in the overlays panel. \nThe sliders are faded even though they are working.", "Interpolated children on object rendered particles not working\nOperating system: Manjaro Linux\nGraphics card: AMD Radeon rx570\n\nBroken: 2.60, 2.79, 2.80, 2.81, 2.82, 2.82a, 2.83, 2.90Alpha\nWorking: Couldn't find any\n\nCan't see any particles when there set to render as an object with an object selected and interpolated children\n\n\n1. Open this file: [particle_child_interp_bug_2_79.blend](particle_child_interp_bug_2_79.blend)\n2. Play animation\n3. In the particle children settings, set Interpolate \nor \n1. Create a particle system on a uv sphere,\n2. set the render type to object,\n3. select a 2nd uv sphere as the render object\n4. set the children to interpolated\n[Daily Challenge 80(particles galore).blend](Daily_Challenge_80_particles_galore_.blend)", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)", "Area Light Leave light border traces on surfaces (less noticable on CPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0 Beta\nBroken: 3.1, 3.0\nWorked: never?\n\nArea light leaves visible trailing light on wide surfaces\n\n\n[Area light trails_render.blend](Area_light_trails_render.blend)\n\n 1.open Blender\n 2.add a plane scale it by 30\n 3.change point light to area light\n\n\n", "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", "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)", "Error de progama\nno me aparece el modo vèrtice\n\n", "Color picker value not working as expected\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha, 2.92 doesn't work either.\nWorked: 2.91 official release\n\nWhen I enter 0, 0 , 0. 5 in the HSV-values expecting a 50% grey ,but the grey I get is way too bright. It's more like 70% grey. The value slider also indicate this brighter value and not half way the black and white gradient as you'd expect it.\nThe saturation value exhibits the same kind of problem a 0, 0.5, 0.5 HSV-value is not as saturated as one would expect.\n\nfirst noticed this in the 2.92 official release and and checked, as advised, the latest version (the above mentioned 2.93 alpha) to see if it was resolved. The last time the color picker worked as expected was in 2.91.\n\nMakes inputing specific colors values pretty much a nightmare.\n\nopen blender, change color pretty much anywhere you can change color. \n\nattached screenshots:\n\n\n\n\n\n\nThanks, have a nice day. (Pablo made me say it! 'cause apparently humans are checking XD)\n", "Diffuse Direct, Indirect Bake to Vertex Color Artefacts\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nWorked: This has never worked properly (At least in my experience)\n\nWhen baking Diffuse light to vertex color, black triangles and random dark spots appear in vertex color. This effect is more apparent with:\n- Area lights.\n- Emissive surfaces.\n- Lights with very high power.\n\n1. Create geometry and give each a byte_color vertex color channel.\n2. Place area lights in scene with high power.\n3. Bake diffuse direct and indirect to color attribute.\n\nSee .blend of my project attached. In the file i've already baked the emissive light to vertex color where you can see the artefacts. Switch to cycles live render view to see the correct output. I think the tiled texture may have something to do with it. I've added a tiled texture and packed it in the example.\n\n", "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" ]

[ "help plz\nOperating system: Windows 10 20H2 19042.685\nGraphics card: RX560\n\nBroken: 2.91.0\n\nidk how to explain it xD\n\n**Bug screenshot**\n\n\n", "Eevee broken since graphics card update\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14758 Core Profile Context 21.1.1 27.20.14527.2002\n\nBroken: version: 2.91.2\nWorked: (same version before AMD graphics update)\n\n[It doesnt render anything as it should and makes everything transparent heres a screen shot:\n\n\n]\n\nHave this graphics card with the latest drivers and use any part that uses eevee. \nOccurs in both material preview and eevee rendered views in the view port as well as eevee renders.\n[Based on the default startup)]\n\n", "Objects not showing in viewport on Solid view\n{[F9532799](Capture.JPG)}[name ](URL)Operating system: windows 10\nGraphics card: Radeon\nRX 570\n\nBroken: blender-2.82a\nWorked: blender-2.91.0\n\nObjects not showing in viewport on Solid view\n" ]

[ "Cycles HIP rendered viewport crashes system/GPU on Linux with RDNA2 GPU\n Operating system: Fedora Linux Release 36 - Linux-5.18.16-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 6900 XT (sienna_cichlid, LLVM 14.0.0, DRM 3.46, 5.18.16-200.fc36.x86_64) AMD 4.6 (Core Profile) Mesa 22.1.5\nROCm Version: rocm-5.2.0\n\nBroken: version: 3.2.2\nWorked: never\n\nWhen using HIP on AMD GPU together with Cycles GPU Rendering my entire system freezes when using the rendered viewport, and I have to hard-reset the PC. I think it's the GPU /GPU-driver that crashes. \nKernel messages from journalctl suggest amdgpu (kernel module?) crashing (see attached) [journalctl.txt](journalctl.txt)\n\nThe crash is not always immediate and might instead only happen after using the rendered viewport for a while or switching back and forth between textured and rendered a few times.\n\nRendering with F12 works fine and I have observed no other crashes as long as I don't use the rendered viewport.\n\nI have only started using blender a few days ago creating procedural textures in the node editor and using the rendered viewport all the time and the crash didn't happen once.\nNow that I started working with image-texture-based assets like in the attached .blend file this problem started happening.\nMaybe it's related with this issue: T97591\n\nCan I somehow get more detailed debug output from blender? The \"-d\" switch didn't generate much more relevant output.\n\nI could reliably reproduce the issue by following these steps [test.blend](test.blend)\n1) Open up two Blender instances with the attached .blend File loaded and have the viewport running in rendered mode\n2) move the viewport in the first instance to get it to \"refresh\"/re-render\n3) while the first instance is still working - move the viewport in the second instance - for me the System/GPU freeze/crash happens right there. \n\n--\nlet me know what info I can provide to help.\n\nThank you!", "Blender 3.5.0 Win11 RTX3090 Fatal Crash on activating Cycles\n@deadpin thanks for replying.\n\nDriver Version: 31.0.15.3161 (NVIDA 528.24) DCH Win1164 installed\n\nCycles now working without issue thank u.\n\n_Originally posted by @Jaymi-McManus in /blender/blender/issues/106953#issuecomment-923094_\n\n>>>>>\n\nUpdate: \n\n1. Closed the ticket too soon, after adding some simple color, specular, metallic, changes in BSDF and then navigating between layout and other tabs, fatal crash occurs again\n\n2. Updated NVIDIA drivers to 31.0.15.3161 (NVIDIA 531.61) DHC / Win11 64 the issue still persists\n\nUpdate logs attached.", "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", "gpu module in CustomRenderEngine causes segfault\nOperating system: Linux-5.4.2-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.7\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nUsing gpu module in CustomRenderEngine render function causes segfault\n\n- Open attached blendfile\n- Run the python script from text editor\n - it is based on the example bpy.types.RenderEngine.html\n - only difference is, importing gpu module and doing a gpu.matrix.push_pop() in the render function\n - also added faulthandler to see where it crashes\n- change render engine to custom\n- hit f12 (blender crashes)\n\nIs the GPU module not suited for use in CustomRenderEngine ?\nAlso testet drawing a gpu.types.GPUBatch to a framebuffer object without doing matrix.push_pop(), it also caused a segfault. The matrix thing is just the simplest case to reproduce.\n\n[CustomRenderBug.blend](CustomRenderBug.blend)\n\n", "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", "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)", "Crash to login screen on macOS Ventura when enabling caustics and smooth shading.\nOperating system: macOS 13.1\nProcessor: 2.6GHz Intel Core i7\nGraphics card: AMD Radeon Pro 5500M 8 GB\nMemory: 16GB 2667MHz DDR4\n\nBroken: 3.4.1\n\nBlender/macOS crashes to login screen when enabling smooth shading on an object with \"Cast Shadow Caustics\" enabled.\n\nCreate a scene with:\n\n - A light with \"Shadow Caustics\" enabled\n - An object with \"Cast Shadow Caustics\" enabled and a transmissive material applied\n - An object with \"Receive Shadow Caustics\" enabled\n\nSet render engine to Cycles and device to GPU compute (crash does not occur with CPU compute).\nSwitch viewport mode to Rendered.\nSelect the cast shadow caustics object and enable smooth shading.\n\nmacOS will hang before crashing to a login screen.\n\nsystem.log reports:\n\nsessionlogoutd[4795]: DEAD_PROCESS: 3681 console\n\nConsole.app also lists a crash report for WindowServer (example crash report is attached).\n\n[Caustics-Crash-on-Shade-Smooth.blend](Caustics-Crash-on-Shade-Smooth.blend) [WindowServer-2023-01-19-171731.ips](WindowServer-2023-01-19-171731.ips)", "Regression: Pixels in render result appear blurry during rendering\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.4.1\n\nPixels in the render result can appear to be stretched into 1x2, 2x1 or 2x2 pixels depending on window resolution. \nThis is only the case while the render is still going; when it finishes the pixels appear as they should.\n\n\n1. Start rendering any scene, most noticeable in scenes with easily visible noise like this one: \n[noisebox.blend](noisebox.blend)\n2. Resize the window while the render is running\n3. Observe pixels changing size\n[blender_2023-02-07_04-11-02.mp4](blender_2023-02-07_04-11-02.mp4)\n", "Object rotation increases render time more than 10 times.\nTested with windows 7 64bit and windows 10 64bit.\nCPU ryzen 5 1600\nGPU GTX 780\nRAM 8GB GDDR4\n(bug appears on other computers too)\n\ntested with 2.79 and 2.8\nWorked: (optional)\n\nIf I rotate object for about 45 degrees around Z axis render time increases more than 10 times.\nBut in preview mode there is no difference in render time before and after rotation.[test.blend](test.blend)\njust rotate the object on attached blend file around Z axis about 45 degrees and compare render times before and after.\n10seconds for 2000 samples before rotation and about 10 minutes after.\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n", "Rendering animation freezes with particle system\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.91.2\nWorked: 2.83LTS (not sure, this is said in most of the comments)\n\nI am trying to render out an animation based on the CGBoost Blender Launchpad Tutorial. Every time I try to render, it will render around 50-400 frames and then it will just stop rendering new frames. My CPU usage goes straight up to 100% when that happens and my GPU usage drops down to 0%. The Blender UI is still responsive, it is just that the render seems to get stuck on a frame. If I cancel the render, then Blender becomes totally unresponsive and I have to force quit via the Task Manager.\n\nIssue happens in both EEVEE and Cycles\n\n**Workarounds (picked up from comments)**\n- Render animation from command line\n- Check lock interface: {nav Render > Lock interface}\n\n1. Open attached Blend file \n2. Press Ctrl-F12 to render out animation.\n3. Wait for render to freeze on a frame. This can happen within the first few frames or after 400-500 frames. It seems random.\n4. Examine CPU and GPU usage.\n\n[Blender Launchpad.blend](Blender_Launchpad.blend)\n[ING BG.blend](ING_BG.blend) (File provided by @Megaseppl: #85267#1122053)", "Very slow rendering on RTX 3080!\nOperating system: windows 11\nGraphics card: RXT 3080 (Gainward RTX 3080 Chasing Wind)\n\nBroken: 3.4.1; 3.4; 3.3.1\nWorked: Works on the vega 11 video card built into the processor, also works stably on the CPU. Works on RTX 3080 graphics card with driver 497.29 on all blender versions\n\nAt times while working in the blender program, I encounter absurdly long render times for one frame: oB4BJ5L.png (shreenshot).\n\nI ran render tests on different driver versions (527.56, 522.30, 526.86, 497.29). In all versions of the drivers, after some time, performance dropped hundreds of times, except for driver 497.29. It works stably. Also tests were carried out on blender versions 3.3, 3.4, 3.4.1.\n\nIt would seem that the problem is solved, you can simply install the 497.29 driver and work stably on it, but this is not so. Only blender works on this driver version, other programs crash and require drivers of at least 520. Regardless of the driver version, the video card is always loaded at 100%\n\nI've done some testing and may have found what's wrong. I made a scene with several cubes, a volume and a strong light source, and also set a large sample size.\nResults:\n497.29 driver - 4 minutes 12 seconds (806 MB of video memory used)\n527.56 driver - 3 minutes 45 seconds (806 MB of video memory used)\nAt the same time, the viewport works quickly and responsively in the cycles render mode. Just like I planned\nI also ran a test with a complex scene and then everything got much worse:\n497.29 driver - 22 minutes 51 seconds (8775 MB VRAM used)\n527.56 driver - 35 minutes 37 seconds (8775 MB of video memory used)\nThe viewport is quite buggy and poorly responsive in both versions of the drivers (but this is logical since the scene is complex). In the viewport, the view mode in cycles on the 497.29 driver works as expected - it gradually develops the picture. On the 527.56 driver, cycles almost doesn't work in the cycles view mode (more precisely, it works, but it's even slower than my four-core processor).\nIn render mode 527.56 the driver is unstable. I had to wait 11 minutes for the first sample to load. And I'm still lucky. Sometimes the render time can be 44 hours for a single frame (oB4BJ5L.png)\n\nAs a result, we can come to the conclusion that with the new drivers, the blender is unstable when the video memory is almost completely loaded.\n\nI recorded the workflow of all tests on video in an accelerated version: 1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link . I advise you to download the video to your computer so that it does not compress when viewed through Google Drive ...\n\n1. Make a complex scene with lots of textures, lots of geometry and use the latest Nvidia drivers.\n2. Engage in scene editing often switching between working scenes\n3. Start rendering the scene at a high resolution and a lot of sampling\nI made a screen recording of the editing process: 1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link\n.blend: 1MY37OWlYleiusnEbxDuTwIx63F_eQIVK?usp=share_link\n", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "Cycles GPU crash when switching to Rendered 3DViewport --MacOS 13.1--\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.5.0 Alpha (works fine)\n\nInstant crash of blender when switching to rendered 3DView.\n\nCompile latest 3.5 version as of 2022-12-18 20:06, hash: `50c7eb14f4`\nopen empty scene provided below and switch to rendered 3DView.\n[gpu.blend](gpu.blend)\n\n\nxcode 14.1\nlatest brew updates\n(cycles-cache & build-darwin folders deleted before compiling )\n\nPS: When switching to CPU there is no crash. Only GPU !", "Blender 3.2 crash when extracting mesh draw cache\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\nWorked: 3.1\n\nBlender 3.2 constantly crash on heavy load.\n\nI have loaded my scene that has a lot of particles. tried to playback the timeline. after maximum 3 frames, Blender just closes without any error messages.\n[HourglassBuildUp-JUNE30.blend](HourglassBuildUp-JUNE30.blend)\n\n", "Blender freezes when using Texture paint or Weight Paint\nOperating system: Windows 10 Insider build19592\nGraphics card: GTX 1660Ti Max Q 6GB\nProcessor: i7-9750H\nRAM: 32GB DDR4-2666Mhz\n\nBroken: version: 2.83 (sub 11)\nWorked: Never (2.79, 2.8+)\n\nBlender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue.\nMoreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting. \n\nAssigned GPU in Preferences>System>CUDA, but the GPU is been barely used.\n\n[Blender.rar](Blender.rar)" ]

[ "Cycles crash \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.2 27.20.2001.16003\nCPU: Ryzen 9 3900X \nMotherboard: MSI MPG X570 Gaming Edge Wifi\n\nBroken: version: 2.83.5\n\nBlender crashes after selecting GPU compute in Cycles. Message on screen says \"Loading render kernels (may take a few minutes the first time)\" and then blender program shuts down. Does not crash while using the CPU to render in Cycles.\n\n\n", "Cycles viewport rendering stuck at Path Tracing Sample 1/32 with high GPU usage\nOperating system: Ubuntu Mate 18.04.4 LTS and Windows 10 (1909) x64\nGraphics card: AMD Radeon RX 570 4GB\n\nBroken: 2.82a, 2.83.2 LTS, 2.83.3 LTS, 2.90.0-b8601b64c7cb, 2.91.0-a51048a5d335, 2.90.0 Stable\n\nViewport GPU rendering on Cycles stuck at Path tracing sample 1/32 with high GPU usage when applying Volume Absorption properties in a Material over any Object\n\nNewer Blender versions (2.90+) or versions previous to 2.83 throws an error \"Split kernel error: failed to load kernel_path_init\"\n\n1) Load attached .blend file in 2.83.2 LTS, 2.90.0 or the latest beta\n[cube_with_water.blend](cube_with_water.blend)\n2) If not set, set the rendering engine to Cycles and select GPU Compute\n3) Select the \"Cube_Content\" object\n4) Go to materials tab, and in Volume section, select \"Volume Absorption\"\n5) Change to Viewport rendering\n\n**Additional Notes**\n- This is only happening on Viewport rendering only, in the final render (when hitting F12) it works fine\n- CPU Rendering in viewport works fine\n- Viewport shading works fine\n- Seems like every other Volume type is affected by this (Volume Scattering, Velvet BSDF, Emission, etc)\n- Trying to apply any BSDF Volume, freezes the computer\n- Some versions like 2.82a and latest alpha at this edition date makes high CPU and RAM usage freezing the computer.\n- 2.90.0 causes high CPU usage only.\n\nMy system-info.txt in Linux (2.83.2 LTS):\n[system-info.txt](system-info.txt)\n\nMy system-info.txt in Windows (2.83.3 LTS):\n[system-info-win.txt](system-info-win.txt)" ]

[ "Cycles viewport unneccessary update calls\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia MX150\n\nBroken: 2.83.17, 8a8c61190b06, Beta and 2.90.2, 8f21f867e715, Alpha\nWorked: 2.82a official\n\n[#76970.blend](T76970.blend)\n\n* set scene renderer to Cycles\n* configure two viewports and a shader editor in a single screen\n* set one viewport to cycles preview render\n* set second viewport to workbench texture color\n* add two image texture nodes and load them with different textures\n* by clicking on the texture node both viewports are redrawn.", "Edit-Mesh \"Select Next Active\" doesn't handle a wire edge loop (vertex mode)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nIt works with loop ,that surrounden by others, but can`t deal with single circle, when I am trying to select one per one.\nPlease watch video:\n[2020-01-17_19-06-34.mp4](2020-01-17_19-06-34.mp4)\n\n[untitled.blend](untitled.blend)", "Keep Alt Key not work in the F-Curve properties\nwin10 64bit, gtx1060\n\nBroken: 2.79a 8928d99270f\nWorked: (optional)\n\nKeep alt key for multiple objects not work in F-curve property ( N panel )\n\nOpen my .blend file, when I select multiple curves and keep alt key to twice the Interpolation or Easing option, it's just worked in one cure,not for all selected, if this is bug, please fix, it very useful for lots curves, else I must one by one to change those, thanks.\n\n\n\n[bug.blend](bug.blend)", "Selection problem on new 'add modifier' menu\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nin new 'add modifier menu' which introduced in Blender 4.0 if you hover your mouse over a main menu items like 'edit' to open edit's submenu then move your mouse diagonally from top right to bottom left on main menu, other main menu items not highlighting or selecting.\nI attach a video take look at it, in this video I move my mouse from edit(while it's open) to physics , non of menus open, not even physics which I stop mouse there no matter how much time my mouse stay there it will not open.\nalso I moved my mouse from edit to generate and also menu did not open.\n\n", "Gpencil: dopesheet selection issues [clicking in summary deselects corresponding ID channel, e.g. breaking \"Jump to keyframe\"]\nBroken: version: 2.92.0 Alpha\nWorked: n/a, tested with 2.91 and didn't work\n\nJump to keyframe command & shortcut doesn't work anymore when you duplicate a keyframe.\nDoesn't matter what amount of layers there are.\n\n1) Draw a keyframe\n2) Draw a nother keyframe at another time = works\n\nDuplicate 1) keyframe = doesn't work, please see the video\n\n\n[gp_duplicate_keyframe_jump.mp4](gp_duplicate_keyframe_jump.mp4)\n\nReason why this happens: clicking in the summary will deselect the corresponding greasepencil ID channel [on which the \"Jump to keyframe\" operator relies]\nClicking in the summary should not deselect every channel there is, but keep the channel representing the selected greasepencil object selected as well [same as for other object types such as meshes].\nThis goes hand in hand with selecting a grease pencil object in the 3DView or Outliner not selecting the corresponding ID channel [this should also be the case (same as for other object types such as meshes)]", "Animation workspace: Switching between tabs causes viewport to change\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0\nWorked: Not sure\n\nChanging between the Texture Paint tab and Animation tab causes the Animation viewport to take on properties of the Texture Paint viewport. If this is working as expected it's not ideal.\n\nOpen a new General 3D project. (Or use attached blend)\nSelect the Animation tab. The viewport should look normal.\nNow go to the Texture Paint tab.\nGo back to the Animation tab.\nThe viewport has taken on the properties of the Texture Paint tab.\n\n(A similar issue with the UV editor and Animation tab also occurs.)\n\n[TexPaintToAnimationTab.blend](TexPaintToAnimationTab.blend)\n\n\n", "Opening the Preferences/Render window replaces the current opened window with the other interface\nBroken: version: 2.83 (sub 13) \nWorked: Never\n\nOpening the Preferences/Render window replaces the current opened window with the other interface.\n\n\nMethod 1:\n* Open a new scene/or an existing scene.\n* Press F11 to render the scene.\n* Once rendered, go to the menu “Edit | Preferences...”\n* The preferences interface replaces the render interface in the same window.\n\nMethod 2:\n* Open a new scene/or an existing scene.\n* Go to the menu “Edit | Preferences...”\n* Press F11 to render the scene.\n* The render interface replaces the preferences interface in the same window.\n\nThere is no reason to replace a window/interface by an interface of different functionalities or with a different purpose.", "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)", "3DConnexion Mouse not working in new Blender instance\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon VII OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 5)\nWorked: (optional)\n\n3dconnexion mouse works only in one instance of Blender\n\nIf I open 2nd instance of Blender 3d mouse does not work in it, only in the original file. This behaviour is same in official 2.8. I have tested this in Rhino for Mac. There Mouse works in both instances, which ever is active of course.\n", "Move some parameters to Blender's DNA\nThese parameters are supported (or going to be) by EEVEE-Next, and we should avoid duplicating the settings for each engine:\n- Motion blur curve\n- Panoramic camera settings\n- View Layer material override\n\nThis is a big change and 4.0 should be the right time to do this.\n\n", "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", "Panorama selection support in viewport\nMouse selection needs to be abstracted so we can remap mouse position to 3d world direction/position. We may be able to do it as a hack, but since we may change mouse selection API in the future - #68989 - we may find an elegant solution in the end.", "Needs two clicks with Ctrl or Shift key to deselect an item from a list of selected items\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0\n\nNeeds two clicks with Ctrl or Shift key to deselect an item from a list of selected items.\n\n\n* Open the project file “OutlinerSelectItemWithCtrl.blend” in attachment as a starting point.\n\nThe same problem happens in different views with different details.\n\nOutliner:\n* Select the entire collection of objects from the collection “Item List”. You can click the “Cone” object, hold the Shift key and then click the “Torus” object to select the entire list.\n* Then hold the Ctrl key and click the Cylinder object to deselect.\n* The item’s color get a lighter color, but it is still not excluded from the whole selection.\n* Clicking a second time on the object really deselects the object.\n* If clicking the first item of the selection (which is the Cone is this example), it is deselected properly.\n\n3D View:\nThe Shift key is used to select/deselect objects individually. It is pretty much the same issue. It requires two clicks on the same object to really deselect the object, whatever the order of the object in the selection. However, if one object has already been selected before deselecting everything, then the same object gets selected with an additional highlight from the new selection (dragging the mouse cursor in the viewport).\n\nShading view:\nPretty similar to the 3D view.\nIf I deselect all the nodes (Alt + A for example) and I drag the mouse cursor to select all nodes, the last selected node is highlighted in white. If I click the node highlighted in white while holding the Shift key, the node is deselected. However, if I do the same thing for the other nodes, it selects the node with a white highlight and I have to click a second time on the same node to really deselect it. The behavior of the last selected item is also present in the 3D View, but not for the Outliner.\n\nThe Compositing view has the same problem and I suspect that the Geometry Node view has the same too (I haven’t tested the last one).\n\nIn general, it requires two clicks to deselect an object with the normal behavior.\n\nThe first click behaves as an “add to selection” click unless the object already had a selection before completely creating a new selection.\n\nIn all cases, there is an issue with deselecting (or excluding) and single object from a selection of objects in different views. As a reference how it should behave correctly, the Windows Explorer in Windows is able to deselect a single item on the first time it is clicked.\n\n[OutlinerSelectItemWithCtrl.blend](OutlinerSelectItemWithCtrl.blend)\n\n[Deselect_Issue.mp4](Deselect_Issue.mp4)", "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", "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)" ]

[ "Secondary Window Behaviors\nWe want users to be able to use multiple windows on multiple monitors, have them behave in ways that are as consistent as possible between platforms, conform to expected per-platform norms, and offer maximum flexibility for different workflows.\n\nWindows should be created and restored at the **size** they are requested and saved, even when the scale and/or dpi differs between monitors.\n - - [x] Windows - This all seems correct now\n - - [ ] Mac - Some windows are created at incorrect size on high-dpi (Retina) displays\n - - [ ] Linux - Unknown status\n\nWindows should be restored at the same **position** where they were saved, regardless of monitor arrangement.\n - - [x] Windows - This all seems correct now\n - - [ ] Mac - Probably does not restore some windows correctly with multiple monitors in *vertical* arrangement.\n - - [ ] Linux - Unknown status\n\nSecondary and temporary windows should appear above other Blender windows, but not on top of all the windows of all other apps\n - - [x] Windows - Platform variation: Child windows are above parents, but parent siblings have no on-top behavior\n - - [x] Mac - Considered to be working as users prefer\n - - [ ] Linux - Unknown status\n\nBring all Blender windows to the front when the main Blender window is activated. \n - - [x] Windows - Platform variation: Each main window will bring children to front when activated, but not other main windows.\n - - [ ] Mac - Unknown status\n - - [ ] Linux - Unknown status\n\nTemporary windows should be created at a last-used size, and not reset to the default size every time they are opened. \n - - [ ] All Platforms\n\nTemporary windows should not steal each other’s windows \n - - [x] All Platforms - These windows are only now reused if the titles are identical.\n\nAll Windows should have informative titles to help differentiate them.\n - - [ ] All Platforms - This might (eventually) do the trick: [D12365: UI: Improved Window Titles](D12365)\n\nBetter activation behavior as the mouse moves back and forth between the windows (don't require a click to activate another blender window so shortcuts can be pressed)\n - - [ ] Windows - If desired on platform, this might work: [D13951: Win32: Auto-Raise and -Focus Windows on Hover](D13951)\n - - [ ] Mac - N/A\n - - [ ] Linux - Unknown status\n\nDon't let secondary windows appear in the task bar (main windows of course should still appear here)\n - - [x] Windows - All windows of app instance are bundled together on Task Bar.\n - - [ ] Mac - N/A\n - - [ ] Linux - Unknown status\n\nSecondary windows *could* use a slimmer title bar, to make them visually different from the main Blender window. \n - - [ ] Windows - Platform does not currently have such a style as would decrease the mouse hit size.\n - - [ ] Mac - Unknown status\n - - [ ] Linux - Unknown status\n\nTemporary windows (open/save dialogs) *could* block the underlying windows until they have been closed or dismissed. Although breaks our non-blocking paradigm.\n - - [x] Windows - Not currently desired on this platform. Behavior could be implemented if we ever have very small and simple dialogs.\n - - [x] Mac - Considered working as users prefer\n - - [ ] Linux - Unknown status\n" ]

[ "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\n\n", "Blender hangs due to deadlock caused by two registered draw handlers\nOperating system: Only happens on Linux (Ubuntu 22.04)\n\nBroken: 3.2.2\nWorked: unknown\n\n\nWhen my addon is used together with the addon [\"node minimap\" ](1366781), Blender hangs/freezes completely under certain conditions (details below).\nTo close Blender in this state, not even Ctrl+C is enough, it is necessary to close the parent terminal from which Blender was started.\n\n\n[addons.zip](addons.zip)\n\n[test.blend](test.blend)\n\n- Install the two addons \"node minimap\" and \"test addon\" from the attached zip file.\n- Enable both addons (search for \"node\" in the addon list to find both).\n- Open the blend file.\n- Convert the editor on the lower left to a Shader Editor.\n# Blender will immediately hang.\n\n\n", "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", "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", "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", "GPencil: Strokes with texture & round caps have distorted extremities\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Alpha\n\nStrokes with a material of line type 'Line', a texture & round caps have distorted extremities.\n\n\n- Open file and see how the start & end of the drawn strokes are distorted.\n[round caps bug.blend](round_caps_bug.blend)\n\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Flickering macOS Blender 2.83\nOperating system: macOS 10.15.4\nGraphics card: XFX Radeon RX 580 8 GB\n\nBroken: 2.83\nWorked: 2.82\n\nFlickering occurs sometimes, as seen on this capture:\n[Screen Recording 2020-06-16 at 09.11.21.mov](Screen_Recording_2020-06-16_at_09.11.21.mov)\n\nI don't know exactly. I think it happens when I use Blender, then I switch to other applications and then return to Blender.\nIf I go to full screen mode, it's back to normal.\n\nThanks.", "Blender Freezes and Crashes on AMD Laptops with White and Black boxes\nOperating system: Windows 10 & 11\nGraphics card: Radeon RX 6600M ATI Technologies Inc. 4.5.14800 Core Profile Context 22.4.2 30.0.15021.7000\n\nI've been using Blender with many versions. From 2.8, to 3.1 and the laptops have issues with all of them.\n\nBlender will freeze, white and black boxes will appear, and then Blender will crash and Windows will close it.\n\nI don't have exact steps, because it happens infrequently. It can happen as quickly as opening Blender, or take an hour of work.\n\nI am a teacher using HP Omen laptops with AMD CPU's and graphics cards. I have 21 laptops, and about 5-7 of them have issues with Blender. I have done a clean install of the graphics drivers, updated Blender to the most recent version, and tried everything I can think of. My personal laptop rarely ever crashes, so it's hard for me to replicate the issue.\n\nI have attached log files from crashes from multiple laptops. Half the laptops have been upgraded to Windows 11, and that doesn't seem to make it more or less likely to crash. My hope is these logs can pinpoint what's happening so I can fix it. I\n\nLog files created with `blender_debug_gpu_glitchworkaround.cmd`\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\nLog files created with `blender_debug_gpu.cmd`\n\n[blender_debug_output (1).txt](blender_debug_output__1_.txt)\n\n[blender_system_info (1).txt](blender_system_info__1_.txt)\n\nWarning and errors:\n```lines=10\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_multi_rect_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_multi_rect_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_text VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_text FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_uniform_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_uniform_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_INST_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_INST_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_rect_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_rect_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_flat_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_flat_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_LINE_DASHED_UNIFORM_COLOR_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_LINE_DASHED_UNIFORM_COLOR_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_3D_uniform_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_3D_uniform_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_desaturate_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_desaturate_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_composite_studio VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_composite_studio FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_merge_infront VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_merge_infront FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transparent_resolve VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transparent_resolve FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_effect_outline VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_effect_outline FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_taa VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_taa FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_1 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_1 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_2 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_2 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_antialiasing_263 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_antialiasing_263 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_414 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_414 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_449 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_449 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_401 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_401 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 GeomShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n | \n 6 | #define DFDY_SIGN 1.0\n | ^\n | (#310) Inputs that are integers should be qualified with the interpolation qualifier \"flat\"\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_wire_469 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_wire_469 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_wire_538 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_wire_538 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_solid_559 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_solid_559 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_stick_518 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_stick_518 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_499 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_499 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_489 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_489 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_wire_579 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_wire_579 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_background_276 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_background_276 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_uniform_color_1465 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_uniform_color_1465 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_grid_905 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_grid_905 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_885 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_885 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_groundline_924 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_groundline_924 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_loose_point_983 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_loose_point_983 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_point_1004 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_point_1004 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_facing_1022 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_facing_1022 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_grid_1055 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_grid_1055 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 GeomShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_vert_1170 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_vert_1170 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_1204 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_1204 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_pointcloud_1257 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_pointcloud_1257 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_gpencil_1230 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_gpencil_1230 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_detect_1272 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_detect_1272 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_dot_1410 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_dot_1410 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_shape_1429 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_shape_1429 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_wireframe_1589 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_wireframe_1589 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nERROR (gpu.debug): : GL_INVALID_VALUE : generated before glGenTextures\n```\n\nStack trace:\n```lines=10\nblender.exe :0x00007FF6F22F7D90 bli_windows_system_backtrace_stack_thread\nblender.exe :0x00007FF6F22F7010 BLI_system_backtrace\nblender.exe :0x00007FF6F228C530 blender::gpu::debug::debug_callback\nblender.exe :0x00007FF6F228C3F0 blender::gpu::debug::check_gl_error\nblender.exe :0x00007FF6F220EE50 blender::gpu::GLTexture::GLTexture\nblender.exe :0x00007FF6F21F8420 blender::gpu::GLBackend::texture_alloc\nblender.exe :0x00007FF6F21F2E20 GPU_texture_create_2d\nblender.exe :0x00007FF6ED267400 DRW_texture_create_2d\nblender.exe :0x00007FF6ED267810 DRW_texture_ensure_fullscreen_2d\nblender.exe :0x00007FF6ED2A4F90 workbench_cache_finish\nblender.exe :0x00007FF6ED25E4D0 DRW_draw_render_loop_ex\nblender.exe :0x00007FF6ED25F5A0 DRW_draw_view\nblender.exe :0x00007FF6EDBC7820 view3d_main_region_draw\nblender.exe :0x00007FF6ED56D940 ED_region_do_draw\nblender.exe :0x00007FF6ED1660C0 wm_draw_window_offscreen\nblender.exe :0x00007FF6ED165F10 wm_draw_window\nblender.exe :0x00007FF6ED165A10 wm_draw_update\nblender.exe :0x00007FF6ED1488F0 ghost_event_proc\nblender.exe :0x00007FF6EDCB1E10 GHOST_CallbackEventConsumer::processEvent\nblender.exe :0x00007FF6EDCFD680 GHOST_EventManager::dispatchEvents\nblender.exe :0x00007FF6EDCFE2E0 GHOST_System::dispatchEvents\nblender.exe :0x00007FF6ED14A980 wm_window_process_events\nblender.exe :0x00007FF6ED140110 WM_main\nblender.exe :0x00007FF6ECDA03C0 main\nblender.exe :0x00007FF6F246FE74 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFF7DCC7020 BaseThreadInitThunk\nntdll.dll :0x00007FFF7E582630 RtlUserThreadStart\n```\n\n----\n\n[blender_system_info_1.txt](blender_system_info_1.txt)\n\n[blender_system_info_2.txt](blender_system_info_2.txt)\n\n[blender_system_info_3.txt](blender_system_info_3.txt)\n\n[blender_debug_output_2.txt](blender_debug_output_2.txt)\n\n[blender_debug_output_1.txt](blender_debug_output_1.txt)\n\n[blender_debug_output_3.txt](blender_debug_output_3.txt)", "Blender 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", "Unusable display with AMD driver errors.\nOperating system: Ubuntu 22.04.2 LTS/Kernel version 5.15.0.75/FOSS amdgpu driver(default)\nGraphics card:MSI Radeon RX580 8GB\n\nBroken: 3.5.1, 3.1.0\nWorked: 3.1.0(Did not experience this until recently)\n\nWhen editing UV GPU gets reset after errors, the compositor does not recover. Garbled image on the screen with displays unusable. Log data attached.\n\nThis happens when pressing .(dot) on the keypad, selecting or moving a UV.\n\n", "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", "The version over 3.5 (3.6 and 3.6.2) crashes for me after using control of view.\nOperating system: Linux-6.2.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics 650 (Kaby Lake GT3e) (KBL GT3) Intel 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: 3.6 and 3.6.2\nWorked: version: 3.5.0\n\n\nI have quite simple scene: 1 table, 1 chair. I change selection from chair to table f.x., then deselection or I make zoom out, the screen freezes, Blender proposes me to closing because not responding\n\n", "Eevee RGB Curves node inaccurate compared to Cycles\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\n[eevee_rgb_curve.mp4](eevee_rgb_curve.mp4)\nThe transformation that the RGB curves node applies to a color differs slightly between Eevee and Cycles, even if the curve is left as default.\nNot sure if this is a bug or just a known limitation, but it breaks compatibility between Eevee and Cycles in edge cases.\n\n[eevee_rgb_curve.blend](eevee_rgb_curve.blend)\n\n", "Vertex paint + x-ray + polygon selection mode = weird shading\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\n\nFor me it looks like this\n\n\n\n[vertex paint x-ray strange shading.blend](vertex_paint_x-ray_strange_shading.blend)" ]

[ "camera and light looks weird when i open new file\nOperating system: Linux-6.2.9-060209-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 22.2.5\n\nBroken: version: 3.5.1\n\nthe camera and the in the scene looks that has some issues in shaping\n\nby opening a new file\n\n", "Viewport symbols for lights and cameras are rendered incorrectly\nOperating system: Linux-6.0.11-300.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nDistribution: Fedora Workstation 37 64-bit\nGraphics card: Mesa Intel(R) HD Graphics 4400 (HSW GT2) Intel 4.6 (Core Profile) Mesa 22.2.3\n\nBroken: version: 3.4.0\nWorked: version: 3.3.1\n\nIn Blender release 3.4, symbols for cameras and lights have weird rendering artifacts\n\n\nLaunch Blender 3.4 and observe how lights and cameras are incorrectly rendered in the viewport\nBased on default startup file\n" ]

[ "Asset Browser preview generation not updating untill hovering over Preview menu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\n\nWhen trying to generate an asset preview using `Render Active Object` the preview **won't display** until hovering over the `Preview` menu.\n\nOpen `Blender` -> Open `Asset Browser` -> Mark any **object** as asset -> Open `Asset Details` -> In the `Preview` Menu you will find `Render Active Object Button`\n\n[2022-12-08 21-59-59.mp4](2022-12-08_21-59-59.mp4)", "Shadow catcher issue with Cycles Standalone\nOperating system: Win10\nGraphics card: 2070 super\n\nN/A Cycles standalone\n\nShadow catcher is not working properly\n\nI've modified the XML parser of Cycles standalone to read shadow_catcher tag as well as create a new sample, derived from scene_monkey.xml, that uses a plane with shadow catcher enabled.\n\nNotice that the shadow is not visible on the output (you can use something like in the commandline \"scene_monkey_shadow.xml --samples 128 -output Temp.png --background\" \n\n[shadow_catcher_issue.zip](shadow_catcher_issue.zip)", "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)", "Eevee Depth of field creates white outline\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 2.93.2 Release Candidate\n\nwhite outlines appear on out of focus objects\n\n\n- open attached file and turn to rendered mode\n\n[dof bug recovered.blend](dof_bug_recovered.blend)\n", "Bisect Tool Todo\n## Bisect\n * - [ ] {icon circle color=yellow} We should add an updated Gizmo here \n\n *Comment: should this gizmo's plane be an outline (design looks opaque), also, it's quite different to the previous design, see: #54661 ~ ideasman42*\n\n *Answer: This design is more similar to what we have now, but makes it easier to rotate and move the bisect plane along specific axes. The blue plane here should be transparent, not opaque. ~ billreynish*\n\n * - [x] {icon circle color=yellow} We should add these options to the tool settings: Fill, Clear Outer, Clear Inner. Otherwise, users have to keep setting these settings for every bisect operation.\n * - [ ] {icon circle color=yellow} We should add an option called 'Only Selected' just like the Knife tool. Currently it always only applies to selected elements, but that makes many successive bisects annoying because you constantly have to select all. \n", "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", "New geometry nodes viewer overlay makes mesh edit mode overlays invisible\nOperating system: Linux-5.19.10-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha, current master\n\n\n| {[F13588717](image.png) size=full} | {[F13588720](image.png) size=full} |\n| -- | -- |\n", "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", "Bend Tool Todo\n## Bend Tool Todo\n * - [ ] {icon circle color=green} We should add the Bend tool to the toolbar\n * - [ ] {icon circle color=green} Should work with drag-release paradigm, similar to other tools in the toolbar\n * - [ ] {icon circle color=green} We should introduce an interactive Gizmo for this tool, such as this:\n * - [ ] {icon circle color=yellow} Just like the transform gizmos, the manipulator should be visible immediately, not only *after* the initial bend operation.\n\n", "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", "Grease pencil stroke partially invisible until mouse-up\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nWhile drawing in the attached scene the stroke is only partially visible. The full line becomes visible only on mouse-up\n\n* open the attached .blend\n* draw over the area with the 3d geometry behind it, only part of the line will show until you end the stroke (see video below)\n\nScreen recording of the problem: Jehz9YAXmE0\n\nBlend file: [gpdrawbug.blend](gpdrawbug.blend)\n\n", "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", "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", "API: Drawing artifact when drawing inside Gizmo and blend mode is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0 Release Candidate\n\nDrawing artifact when drawing inside Gizmo.draw and blend mode is enabled.\nLook at the line across each graphic/rectangle.\n\n\n[GizmoDrawingIssueBlendAlpha.blend](GizmoDrawingIssueBlendAlpha.blend)\n1. Open the provided .blend file.\n2. Run the script\n3. Look at the simple rectangle and the transparent line across the rectangle\n4. Now try again but remove both 'gpu.state.blend_set' lines\n5. Rectangle is ok\n\nNote: the same drawing code from a [draw callback ](bpy.types.Space.html?highlight=draw_handler#bpy.types.Space.draw_handler_add) works fine without artifact.\n", "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." ]

[ "Grease pencil object outline shader fails to compile on radeonsi\nOperating system: arch linux\nGraphics card: RX 460 (radeonsi)\nllvm 11.0.0-4, and master compiled today\nmesa 20.2.3-1, and master compiled today\n\nBroken: 2.83.9, 2.91.0, 2.92 daily build\nWorked: 2.80\n\nselecting a grease pencil object tanks performance and the outline fails to render.\nI assume it's the grease pencil outline shader, as it does not render, and other object selection outlines seem to render fine with no slowdown.\nI don't know for sure if it's an issue with blender, could also be an LLVM/mesa bug.\n\nblender 2.80 downloaded from blender.org does not have the issue, I'm assuming it's bundled with it's own older LLVM.\n\nthese are the relevant lines from startup:\n\n```\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr1 = V_CNDMASK_B32_e32 32768, killed $vgpr2, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nradeonsi: can't compile a main shader part\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nradeonsi: can't compile a main shader part\n```\n\nand then this prints at least once per frame with a grease pencil object selected in object mode:\n\n```\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\n```\n\n1) start blender (e.g. git-master) in a termimal\n\n$ blender-tip\n```lines\nRead prefs: ... .config/blender/2.92/config/userpref.blend\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr1 = V_CNDMASK_B32_e32 32768, killed $vgpr2, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nradeonsi: can't compile a main shader part\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nradeonsi: can't compile a main shader part\n```\n\n2) delete cube\n3) add grease pencil → monkey\n\n```lines\nInfo: Deleted 1 object(s)\n\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\nLLVM failed to compile shader\nLLVM triggered Diagnostic Handler: Illegal instruction detected: VOP* instruction violates constant bus restriction\nrenamable $vgpr3 = V_CNDMASK_B32_e32 32768, killed $vgpr3, implicit killed $vcc, implicit $exec\n....\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", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "Grid unwrap uv\nMake rectangular uv layout of selected uv’s. If non rectangular/quad topology is selected, it is adjusted to the rectangular/quad topology. \n\n- Filter out continuous areas with gridlike topology\n- Filter out the grid area with the largest area\n- Align the grid area with largest area to a grid like uv layout\n- store current pinning\n- pin grid area with largest area and unselected vertices\n- unwrap the rest of the selected vertices\n- restore pinning\n\n**Starting point**\n\nSelected UV island shoud be automatically aligned to a to U and V as much as possible for the topology which is built in a grid like fashion\n\n\n\n\n**Desired result**\n\nThe topology that is built in a grid like fashion (selected/orange) is aligned to the U and V axis.\n\nThe topology that is not built in a grid like fashion (selected/green), or is not part of the contineous grid like topology with largest area, will be adjusted to fit nicely to the rectified UV’s.\n\nThe dominant grid is the continuous grid with the largest area. Supporting multiple grid areas are not important at the first implementation of the operator\n\n\n\n", "Line art modifier clips with object on (MBP 16\")\nOperating system: macOS Big Sur\nGraphics card: 5500M \n\nBroken: 2.93.0 LTS\nWorked: -\n\nLine art modifier (grease pencil) seems to clip into / z-fighting the object. \n\n\nJust add a new line art modifier, possibly a mac problem?\n\nTest File:\n[line_sample.blend](line_sample.blend)", "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)", "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)", "Wireframe overlay opacity does not work correctly with viewer node\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.1.230305\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nAlso confirmed in 3.4 (which introduced the Viewer Node).\n\nWireframe overlay opacity does not work correctly if Geometry Nodes viewer node is activated and it's showing attribute.\n\nIt looks as if there's extra wireframe overlay under the usual overlay. Remaining wireframe does not respect smooth wires option from the preferences.\n\n- From the startup file, add Geometry Nodes to the cube\n- From Geometry Nodes editor, add a node that outputs attribute (Random Value node for example)\n- Connect Group Input and the attribute node to Viewer node\n- From viewport overlay option, enable wireframe. Try opacity slider\n\nVideo:\n<video src=\"attachment\" controls></video>\n\nFile for quick test:\n[ViewerNodeWireframe.blend](attachment)\n\n", "Node muting connects mismatching sockets\nBroken: 3.2.0 beta\n\n\n - Add *Float Curve* node in any editor (*Shader, Geometry Nodes*) and connect output to anything else\n - Plug *Value* nodes into input sockets (both factor and value)\n - Mute *Float Curve* -> inner noodle connects Factor to Value\n\nOr in provided file mute *Float Curve*\n\n[wrong_mute.blend](wrong_mute.blend)\n", "Cycles/Eevee texture nodes for modifiers, painting and more\nWith Blender Internal being removed, we have an opportunity to support the same set of textures for Cycles, Eevee, modifiers, particles, painting, compositing, etc. So we plan to port the relevant Cycles / Eevee shader nodes to Blender C code, and make those the new texture nodes that can be used throughout Blender. Blender Internal textures can be removed then, and we can extend the Cycles / Eevee shader nodes to add any important missing features from them.\n\n* Some nodes like color ramps, RGB curves, and similar utilities are already there.\n* Texture nodes like image, noise, voronoi need to be ported.\n* Geometry, attribute and similar nodes as well. These are the most complicated since they access the mesh geometry.\n* Some nodes like BSDF, Mix Shader, Bevel, .. would not be supported.\n\nFurther we need a good UI for this in the texture properties.", "Knife Tool: incorrect interaction with Array modifier when the Merge \"First Last\" option is set\nOperating system: Win10\nGraphics card: nVidia 1070\n\nBroken: 2.80 (sub 44), branch: master, commit date: 2019-02-14 04:22, hash: caa8e7ff2894\nWorked: not sure\n\nWhen the Merge First Last option is set for an Array modifier, it seems like hidden, virtual geometry is picked up while using the knife tool to cut across the surface of the primary shape.\n\nThis results in an improper cut.\n\nBad in-progress cut:\n\n\nBad confirmed cut: \n\n\nGood cut -- with the First Last option turned off:\n\n\n[array-bug.blend](array-bug.blend)\n- Create a simple shape and array it in a radial fashion so that the first/last vertices of the shape are eligible for merge\n - Or just load the attached .blend\n\n- Attempt to make a cut across the main shape with the Merge First Last option set\n- Notice that the cut line is picking up some hidden edges somehow -- perhaps due to triangulation?\n- Confirm the cut and notice it's still incorrect and pretty weird", "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", "Unable to create manual curve to mesh UV with spline parameter\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\nBelow file is creating uv's from the curve length and profile and then outputting as a custom_UV attribute. There seems to be squashing happening at the beginning and end.\n\n[spline parameter fac bug.blend](spline_parameter_fac_bug.blend)\n\n\n\n", "Grease pencil over geometry occlussion problems\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5\nBroken: version: 3.0.0 Alpha\n\nGP lines get incorrect occlussion in the render while looking fine in the viewport\n\nThe problem displays differently in the following 2 scenarios:\n\nThis file has a grease pencil stroke close over (but not really touching at all) a piece of geometry\n[GP Aliasing.blend](GP_Aliasing.blend)\nViewport Rendering\n\nRender\n*The line looks jagged in the render*\n\n\nThis file has a grease pencil drawing far behind a piece of geometry\n[Occlussion.blend](Occlussion.blend)\nViewport\n\nRender\n*The drawing that should be occluded is completely visible*\n\n", "Geometry Nodes: viewer node and output geometries are shown together in Cycles render preview\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.5.1 30.0.15021.11005\n\nBroken: version: 3.4.0 Alpha\nWorked: n/a\n\n\n\nThe output geometry should not be shown when viewport preview in Geometry Nodes is active. But it's shown in Cycles render preview.\n\n[ViewportPrivewCycles.blend](ViewportPrivewCycles.blend)\n", "boolean node in geometry nodes seems to work wrong\nOperating system: macOS-11.2.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15\n\nBroken: version: 3.0.0 Alpha\n\n\n\nI have made this node tree in geometry nodes and i am getting this result, which - for me - looks like a bug.\n\n" ]

[ "Geometry nodes fails to maintain links to vertex colours when converted to regular geometry.\nOperating system: win10\nGraphics card: 2080ti\n\nBroken: 2.93.1 & blender-3.0.0-alpha+master.fb87d236edb7-windows.amd64-release\nWorked: Never\n\nWhen using geometry nodes its possible to use vertex colours. You can see the vertex colour in the the Spreadsheet and in the viewport.\nWhen converting the output of this geometry node mesh to a standard mesh, either by applying the GN modifier or placing another modifier after the GN (such as decimate) the vertex colours are no longer viewable.\nOn the objects with the geometry node modifier applied, looking at the spreadsheet the vertex colours still exist, but there is no vertex colour group under object data properties.\n\nHere is a blend file with some examples\n[Geometry Nodes Test.blend](Geometry_Nodes_Test.blend)" ]

[ "simply moving the render window is terribly slow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nwith more complex scenes (such as for example blenderman file 57e5084f0fcf294119c5055c) once you render an image and you have eevee in render preview mode, moving the render window becomes very slow, probably because eevee returns to refreshing the previw render without needing it.\n\nsee the video\n\n[GRAbwindow.mp4](GRAbwindow.mp4)\n", "Undo/Redo shortcut still active in the Blender File View window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Beta\n\nUndo/Redo shortcut still active in the Blender File View window\n\n* Open Blender with the default cube.\n* Move the cube a few times.\n* Open the “Preferences” window in the menu “Edit | Preferences...”\n* Then do Ctrl + Z to undo. The undo shortcut still works. It is the same for the redo shortcut.\n\nThe undo/redo is also active from any other windows of the “File” menu like “Open”, “Link”, “Save”, “Append”, etc. All links showing the “Blender File View”.\n\nIn the “Blender File View” window, I noticed that the buttons at the bottom disappear when doing the undo shortcut.\n\nI tried a few other shortcuts like Tab to go to edit mode and G to move the cube. They do not seem to be active when the focus is on the “Preferences” or “Blender File View” window.\n\nThe undo/redo is also active when the “Blender Render” has the focus.\n\nAs a consequence, someone accidentally hitting the undo shortcut will get his work being modified behind the window and probably will not notice.\n\n\n{[F9111517](BlenderFileView_Open.jpg) size=full}\n\n{[F9111519](BlenderFileView_AfterShortcut.jpg) size=full}", "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.", "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```", "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", "Show Emitter toggle still hides object after Particle System has been deleted.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.92.0 Alpha\nWorked: version: \n- 2.92.0 Alpha\n- 2.91.0 Release\n\nWhen you delete a particle system with show emitter unchecked under Viewport Display the object stays hidden. You have to re-add the particle system and check Show Emitter.\n\n- Add Particle System to default cube.\n- Uncheck Show Emitter under Viewport Display\n- Delete Particle System. \n\n", "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", "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", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Inconsistent behavior of knife tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.13540 Core Profile Context 25.20.14002.1\n\nBroken: version: 2.93.0 Alpha, branch: `master` , commit date: `2021-03-24`, hash: `26b45448abf`\n\n\nAfter confirming the cut ( hit `space` ) , sometimes one or more drawn knife edges disappear ( problem seen with edges . verts does not disappear )\n\n - Select default cube ( any mesh ) \n - Move to edit mode \n - Select knife tool \n - draw cuts with knife tool . Issue is more predictable when initial and final verts of a cut are closer and end vertices near the center of face\n```\n ( not necessary though ) \n```\nVideo :\n( Unpredicted behavior is visible from 13th sec )\n\n [Blender 2021-03-25 14-52-57.mp4](Blender_2021-03-25_14-52-57.mp4)\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)", "Frame counter while rendering does not respect blender's DPI setting\n4K screen, Windows 10, GEFORCE 960M\n\nBroken: bac1279\n\nThe cursor frame counter that displays while rendering is minuscule on a 4K screen, regardless of the DPI setting in Blender", "Undo in Sculpt Mode\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.90.1\n\nWhen I apply undo in sculpt mode it applies to my previous settings as well (symmetry activation, some of brush settings and any settings in sculpt mode). \nThis is so annoying moment please help with it?\n\n", "Contradictory labels in UI. Naming of boolean properties sometimes positive, sometimes negative.\nOperating system: Any\nGraphics card: Any\n\nBroken:\nBlender 2.80.74 aka rc2\n\nInconsistency in naming leads to contradictory info.\n\n- Open Blender\n- Select an object on the scene (add one if you have nothing...)\n- Go to Object properties panel\n- Scroll down to Visibility\n- Hover \"Show in Renders\"\n- A pop-up info label reads \"Globally disable in renders\", so now you're not sure what happens if you check the box\n- Check the box\n- Open the Info Editor, the last line will read \"bpy.context.object.hide_render = True\"\n\nSo now we have three different nomenclatures for the same thing. Two that are contradictory within the UI and one that is the opposite naming of what's in the UI.\n\nInstead of having properties named \"show_name\" and some others \"hide_viewport\", all such boolean properties could be named \"show_function\" or \"enable_function\" so that you don't have to negate the negation as in hide_viewport = False\n\nSince Blender 2.8 is a breaking release, it is the time when you can implement coherent naming. After that, it's going to be much more difficult.\n\nOf course that's by far not a priority since it doesn't break Blender.", "Collection visibility animated\nI need to recap with @brecht and @Sergey why we didn't push for this in 2.80. If it is doable and doesn't break our design, we should support this.\nBasically only the datablock settings (global viewport visibility, and renderability)." ]

[ "Opening the Preferences/Render window replaces the current opened window with the other interface\nBroken: version: 2.83 (sub 13) \nWorked: Never\n\nOpening the Preferences/Render window replaces the current opened window with the other interface.\n\n\nMethod 1:\n* Open a new scene/or an existing scene.\n* Press F11 to render the scene.\n* Once rendered, go to the menu “Edit | Preferences...”\n* The preferences interface replaces the render interface in the same window.\n\nMethod 2:\n* Open a new scene/or an existing scene.\n* Go to the menu “Edit | Preferences...”\n* Press F11 to render the scene.\n* The render interface replaces the preferences interface in the same window.\n\nThere is no reason to replace a window/interface by an interface of different functionalities or with a different purpose." ]

[ "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "Sculpting laggy and weak from some directions.\nOperating system: Windows 10\nGraphics card: Nvidia GTX 970\n\nBroken: 3.6.1\nWorked:Never(2.80+)\n\nWhen i try to sculpt from from below, using radius unit: scene, sculptings get laggy and the stroke is weak.\n\nI'm trying to sculpt stones for a wall in place.\nThe sculpting works fine if i first move the stone i'm working on to the scene origin. This adds a lot of work as i want to for example put bevels on all objects first, then go on with cracks and other features!\n\nTo reproduce:\nOpen file, sculpt from top and bottom\n\nFile is default sculpt template with sphere moved up by 5 and using scene radius.\n\n", "Migrate Texture To Texture mask for existing brushes\nTexture painting brush uses two textures:\n* Texture that overrides the color of the brush (`brush.mtex`)\n* Texture Mask that acts as a masking reducing the effect of the brush. (`brush.mask_mtex`)\n\nSculpt/Vertex painting only supports a single mask.\n* Texture that acts as a masking to reduce the effect of the brush. (`brush.mtex`)\n\nThis is confusing when we combine the texture painting and vertex painting in the same mode.\n\nCleanups to be done:\n* `BKE_brush_sample_tex_3d` currently only uses mtex, perhaps a reason why sculpt is using mtex as mask_tex. masktex only has a 2d variant.\n\n\n## Approach\n\nAfter doing some prototypes and detecting the different viewpoints about mtex by different developers, I was researching a solution that could sanitize this issue. Sanitation is required due to:\n* Sculpt mode uses `mtex` for masking. Newly created brushes that could benefit from color masks are hard to implement in a maintainable fashion.\n* Sculpt mode uses a concept of primary and secondairy mask texture.\nMain idea is that all functions that access mtex/mask_mtex would access it via a wrapper.\n```\nstruct MTexAccessor {\n MTex *color;\n MTex *mask;\n};\n```\nDifferent tools/modes would then be responsible to create and fill this struct.\nSpecific implementations would only access the mask via the wrapper that is suitable for the functionality.\nFor example `SCULPT_brush_strength_factor` should pass `MTextAccessor::mask` to the `BKE_brush_sample_tex_3d`.\n\nAfter this is done we could migrate per mode/tool to the actual brush mtex attribute that is designed for it.\n\n", "Point density texture rendering differently from command line\nOperating system: Windows, Linux\nGraphics card: Not relevant, works the same on CPU / GPU\n\nBroken: All, including the last 3.1 alpha c34ea3323a3a\nWorked: None, as far as I can tell\n\nWhen rendering via command line, a texture with point density and emission renders completely different from rendering via full Blender. The attached file contains a simple example. I also attached sample renders for both command line and full interface.\n\n1. Open blend file in full Blender, render it.\n2. Render the same file via command line\n\n[pointdensity-cmd-bug.blend](pointdensity-cmd-bug.blend) \n\n", "EXR output color options do not work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nWhen choosing OpenEXR or OpenEXR Multilayer output format we have options for BW | RGB | RGBA\n\n\n\nHowever EXR files are always written as RGBA no matter what, meaning there is not way to save a 3 channel RGB image without alpha or a single channel BW grayscale image.\n\nAnother related issue is the inconsistency in output options.\n\nAs mentioned above the render output does show BW | RGB | RGBA options:\n\n\nBut saving an image from the image editor only shows RGB | RGBA options\n\n\nThe same is true for the options available in the compositor File Output node\n\n\n\n", "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", "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)", "Find solution to unify color picking methods with options for sample space\nReopened as, though the initial issue is invalid, the current solution, as it is, is problematic.\nThe sample_color paint operator {key S} has a problem with discoverability and is separate from both the general UI color picker and the sample tool. This needs a better design solution.\n\n**Old Description** (resolved by sample_color operator)\n\nRight now all color picking is using the display space, which usually makes it (almost) impossible to accurately pick colors from an image that is not sRGB for texture painting.\nSimilarly, for texture painting in the 3D viewport the picked color is that after shading and display transformation. This can be useful, but it should be optional. In a lot of cases the user wants to pick and draw a color from within the same image texture, without any additional color space conversion.\n\nThe View mode of the image editor already has a sample tool, which has the functionality to show the color data in image space without additional color management. So simply using this tool in paint mode for picking color with the option to select the color space would already be a huge benefit.\n\nFurther, having a similar tool for 3D texture painting would be even better, but I assume that this might have more difficult implications for the implementation. Tackling this for the image editor first using the Sample tool, might me a good trade-off for investing a small amount of work for maximum impact.\n\n[color_picker_behaviour-2021-03-02_15.50.34.mp4](color_picker_behaviour-2021-03-02_15.50.34.mp4)\n[non-color_picker.blend](non-color_picker.blend)", "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 !", "Fade Inactive Geometry: Objects with the same stored mode are not 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\nIt is possible to keep objects in a certain mode even if they are not active. \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.\nUnfortunately if any object in the scene is also in the same mode, even if it is not active or affected by the currently active object, it will not be greyed out.\n\n In this example image 2 quad-spheres are not greyed out. The left one is active and can be sculpted on. The right one is not active or selected but is also currently in sculpt mode. \n\n- Disable \"Lock Object Modes\" in Topbar -> Edit\n- Duplicate an object multiple times to have more than 1\n- Select one and switch to (for example) vertex paint mode\n- Select another object in the 3D viewport or via the outliner without exiting the mode of the active object\n- Switch into the vertex paint mode\n- The other object is not greyed out \n\n", "Color Picker in texture mode sampling incorrect values (sample merged OFF, sampling from another object)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.92.0\nWorked: ?\n\nThe color picker in \"Texture Painting\" mode seems to only sample the correct color when the look is set to **None**under the **ColorManagement->Look->\"None\"** and if the Viewport **Shading->RenderPass** is set to **DiffuseColor**.\nOtherwise, the color values are simply wrong, they are either too bright or too dark.\n*In the provided scene the issue is quite clear, but in more complex scenes with more complex lighting and post-processing the sampling becomes **completely** broken giving values that aren't even close to what is shown on screen.*\n\n**Expected Behaviour**\nThe way I would expect the color picker to work is that it either samples the color as **I** as a user see it on my viewport.\nOr that it samples the source texture at the pixel I am sampling without any extra lighting applied to it. *( This should be easily toggleable behavior but that is more of a feature request )*[ColorPicker_WrongSampling.blend](ColorPicker_WrongSampling.blend)\nRight now it seems to do neither.\n\n\n - Open attached .blend file.\n - Select the black cube and enter Texture Paint Mode.\n # Sample the color from the other cube *( I recommend sampling the green since the meshes are close to each other making it easy to see the color difference )*.\n\n\n", "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. ", "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", "Can't get vertex color in index layer of \"Particle Instance\" modifier\nOperating system: Mac OS ventura 13.1 \nGraphics card: Apple M1\n\n\nBroken: version: 3.5.1. 3.6.1\nWorked: 2.80.75\n\n\nI define a vertex color named \"test color\" in \"Object data properties\"-\"color attributes\"-\"+\"-\"domain: vertex\"-\"data type: color\" for a general plane mesh. Then I add a \"Particle Instance\" modifier for the mesh. In the \"layers\" section of the modifier, I want to assign the previous \"test color\" to the \"index\" field. However, I get an empty list prompted when tapping the field area. And I can't enter the name manually either.\n\n1. build a plane mesh\n2. Create a vertex color. \"Object data properties\"-\"color attributes\"-\"+\"-\"domain: vertex\"-\"data type: color\" for the plane\n3. Add a \"Particle Instance\" modifier for the plane\n4. Go to \"index\" field in \"layers\" section of the modifier.\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" ]

[ "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", "Bug on Multiresolution modifier UV Map when in Sculpt Mode\nOperating system: Windows 10 Pro 64-bit (10.0, Build 18362)\nGraphics card: NVIDIA GeForce 920M\n\nBroken: 2.80\n\nThe UV of all the display vertices become (0, 0) when switching to Sculpt Mode, it happened because I added a Multiresolution modifier.\n\n- Step 1: Download the .blend file below and open it.\n- Step 2: Switch to Sculpt Mode.\n- Step 3: Now you see a bug, the mesh turns into red because the color of the pixel at (0, 0) is red.\nWhen you try to reproduce the error from beginning then don't forget to click on Subdivide in the Multiresolution modifier otherwise the bug won't happen.\n[Bug_with_Multiresolution.blend](Bug_with_Multiresolution.blend)\n", "Texture maps of objects with multires tessellation modifiers cannot be displayed in sculpt mode\nOperating system: Windows-10-10.0.19035-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.10.1 26.20.13025.10004\n\nBroken: version: 2.82 (sub 5)\nWorked: (optional)\n\nTexture maps of objects with multires tessellation modifiers cannot be displayed in sculpt mode\n\n1 Open a scene with a multires subdivision modifier object (for example:[d.blend](d.blend)\n2 Enter engraving mode\n3 stickers cannot be displayed\n\n", "Multires Sculpting changes Object's Material appearance\n\n\n\n(click pictures to see animation of problem)\n\nI've noticed that Sculpting characters with the Multires Modifier on leads to strange Material displays both in Eevee and Cycles.\nSomehow it messes with the Base Color, Roughness and Alpha? Note how this only happens when \"Sculpt Base Mesh\" is disabled.\nI tried reducing the scene to its basics and managed to replicate it on a simple cube.\n\nI usually use 3.0 but have also tested it on the experimental 3.1.0, to the same results.\n\nHere's the example file:\n\n[multires problem.blend](multires_problem.blend)\n\n\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.1.0 Alpha\n\nas stated above\n\n\n.Open attached example .blend file\n.Select cube Object\n. Make sure Multires modifier's Sculpt is on 1 and \"Sculpt Base Mesh\" is disabled\n. switch from Object to Sculpt Mode\n.notice how the material changes (takes on the background's color)\n\n", "Image Textures not visible in Sculpt Mode when using Multiresolution modifier.\nOperating system: Mac OS X and Windows 10\nGraphics card: \nNVIDIA GeForce GT 750M 2 GB / Intel Iris Pro 1536 MB (mac)\nNVIDIA GeForce GTX 1650 (windows)\n\n2.83 Beta, eaee2b411935, 2020-05-10\n2.90 Alpha, 51ac411ce80c, 2020-05-10\n\n\nImage textures do not display in sculpt mode when using MultiRes modifier but they do display in sculpt mode when not using MultiRes.\n\nOpen default startup file.\nChange Render Engine to Eevee.\nChange Viewport Shading to Material Preview mode (or Rendered mode).\nSelect the default cube and add an image texture to the base color of the default material.\nNotice that you can see the image texture on the default cube.\nSelect the default cube and enter Sculpt Mode.\nNotice that you can STILL see the image texture on the default cube.\nAdd Multiresolution modifier.\nClick Subdivide.\nNotice that you can no longer see the image texture on the default cube.\n", "No textures in Sculpt Mode in Workbench Color Mode Texture\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.81 dcad1eb03ccc from 2019-08-06\n\nTextures (linked to Base Color) on objects cannot be seen in Sculpt Mode in Workbench - Color Mode: Texture. Looks like vertex color visibility was fixed but textures are still not working and showing as gray.\n\n1. Open Blender and apply some texture on a default Cube.\n2. Switch Color Mode to Texture and then switch to Sculpt Mode.\n\nHere is a test file just in case, left Plane is in Sculpt Mode and right Plane is in Object Mode.\n[SculptNoTextures.blend](SculptNoTextures.blend)", "Viewport render (cycles or Eevee) not showing texture when sculpting with multiresolution modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 2.93.2\n\nWhen sculpting an object with multiresolution modifier, If viewport shading is changed to material or render, any image texture in the object's material goes black or invisible in cycles render. everything works fine in object mode. \nUpon more inspection, the UV of the object with multires modifier is completely black when in sculpt mode and normal otherwise\n\n\n\n - Add a cube\n - switch 3D viewport shading to material or render\n - create a new material\n - add any image texture to the material and connect it to the base colour of principled BSDF\n - go to sculpt mode\n - add a multiresolution modifier on the cube and subdivide (ctrl + 2)\n # and the texture does not show (or cube object is invisible in cycles)\n\n\n\n\n\n\n\n\n\n", "Multires cannot display texture in Sculpting\nOperating system:Windows-10-10.0.19041-SP0 64 Bits\nGraphics card:GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: Broken: version: 2.83.4, branch: master, commit date: 2020-08-24 12:20, hash: c113af82881a\nBroken: version: 2.90.0 Beta, branch: master, commit date: 2020-08-24 12:20, hash: ebf10b72b05f\n\n\nMultires cannot display texture in Sculpting.\nBut Subdivision can display texture in Sculpting\n\nBased on the default startup or an attached .blend file (as simple as possible).[2020-08-23 19-06-08.mkv](2020-08-23_19-06-08.mkv)\n\nOperation video\nO13KeoGII34", "No textures in Sculpt Mode with subdivided Multires\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.80 up to e3c586e262dd from 2019-07-12\nWorked: 2.79\n\nSubdivided Multires modifier stops showing textures when you enter Sculpt Mode.\n\n1. Open Blender, add some base color texture to the default Cube's shader.\n2. Add Multires modifier, press Subdivide\n3. Enter Sculpt Mode\n\n- In 2.79 it is still possible to see your textures and masks and everything works as expected.\n- In 2.80 all your textures and masks becomes disabled which makes it extremely hard to work.\n\nI have noticed that when I change the texture my object changes its color so it looks like Multires in 2.8 loses UVs during the Sculpt Mode for some reason. This becomes a very big problem when you have to work on landscapes.\n\n[NoTextureDuringMultiresSculpting1.blend](NoTextureDuringMultiresSculpting1.blend)" ]

[ "Texture stencil \"Reset Transform\" doesn't work properly\n**System information**\nLinux Mint 17.3 (x86_64)\nLinux Mint 18 (x86_64)\nWindows 8.1 64bit\n\nNvidia Geforce GT640\nNvidia Geforce 820M\n\nBroken: 2.78, 2.77a\n\nIn texture paint mode (wether in 3D or 2D), the \"Reset Transform\" under \"Texture\" doesn't work once you clicked on the \"Reset Transform\" under \"Texture Mask\".\n\n\n\n - Open this .blend file [stencil Reset transform bug.blend](stencil_Reset_transform_bug.blend)\n\n - Click on the upper \"Reset transform\"\n\n - it works.\n\n - revert file\n\n - click on the lower reset transform, then on the upper one\n\n - it doesn't work.", "Cycles principled BSDF artifact with transmission and IOR 1.0 (GPU)\nOperating system: win 10 pro\nGraphics card: 1070\n\nBroken: 2.79b\n\ncircular banding with transmission and ior set to 1 using principle shader. (only happens in gpu rendering not cpu)", "Sculpt mode transform tools. Weirdness with 3d cursor.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.2 26.20.13003.1007\n\nBroken: version: 2.81 (sub 11)\n\n1. In sculpt mode transform tools strange behavior with 3d cursor. Trying rotate part of the mesh, first rotation might be ok and second sometimes ok, but then rotation is going crazy. Exit to object mode then again enter sculpt mode, rotation is ok, but only for 1-2 times then again it acts weird (watch the video 1).\n\n2. Scaling in sculpt mode with 3d cursor not like in edit mode, it is very strange (watch the video 2).\n\n1. Open attached *.blend file, rotate several times, (do not cancel rotation with rmb!).\n\n2. Open attached *.blend file, select scale tool, try to scale, go to edit mode try to scale, see the difference?[video_1.mp4](video_1.mp4)\n\n[video_2.mp4](video_2.mp4)\n\n[bug_rot_scale.blend](bug_rot_scale.blend)", "Mesh cache Modifier cant unselect Flip axis once selected \nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nin Mesh cache Modifier i cant unselect X,Y,Z Flip axis once selected ..it can only be interchanged\n\n\n\n", "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.", "Grease Pencil Shear Tool Todo\n## Grease Pencil Shear Tool Todo\n * - [x] {icon circle color=red} The tool should execute on release, so when you click and drag, it stops. Currently you need to click an extra time, which is inconsistent and annoying.\n * - [ ] {icon circle color=green} Add Tool Setting to switch between horizontal and vertical shearing\n * - [ ] {icon circle color=green} Shear should have a manipulator to shear in any direction, the orientation on which is controlled by the Orientation setting, just like the Transform manipulators. Dragging any of the handles shears in that direction.", "Bisect Tool rotation Gizmo doesn't behave correctly\nOperating system: Linux-5.15.0-27-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.3.0 Alpha\n\nI wasn't sure how to call the title. \nThe issue is that if you use the Bisect tool in the toolbar, you get an adjust last operation gizmo after using it.\nBut the rotation gizmo doesn't seem to take the mouse movement relative to the viewport rotation into account that well.\nIt behaves quite strange and unintuitively.\n\n- Go into Edit Mode on a cube\n- Select everything\n- Use the Bisect Tool from the toolbar on the cube\n- Use the blue ring on the gizmo\n- Try using it from different angles (rotate around the cube)", "GPencil: Randomize brush's 'Position' attribute doesn't work when camera is too close to Grease Pencil object\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.93, 3.1.0\nWorked: N/A\n\nExact steps to reproduce the error:\n\n- Open file\n- try to use Randomize brush\n- Strength and Thickness work, but not Position \n- Switch to the other camera that's farther away from the GP object, and randomizing the position works fine.\n\n[randomize_not_working_close_NEW.blend](randomize_not_working_close_NEW.blend)\n\n\nwatch?v=4pTrEm5HqVU", "Hair particles roots moving when using curl kink type and simple children\nOperating system:Windows 10\nGraphics card: Nvidia RTX\n\nBroken: 3.0+\n\n\n\nWhen you use particle hair with simple children and you try to add the curl kink. The roots move with the amplitude. The only thing that keeps the roots in their place is to turn on the clumping. This doesn't happen when you use the interpolated children\n\nI don't know if it's a bug (most likely) but it is extremely frustrating\n\n Take a look at the video.I've added the file just in case\n \n Thanks\n\n", "\"Clean Keyframes\" in Dope Sheet only works if channels are selected\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 2.93.0 Alpha\nWorked: unknown\n\nThe \"Clean Keyframes\" and \"Clean Channels\" operators in the Dope Sheet editor only work if the channels containing the selected keyframes are also selected. This is unlike the \"Delete Keyframes\" operator, which works even if the channels are not selected.\n\n- Load the default startup scene.\n- Enable Auto Keying in the Timeline editor.\n- Move the cube up a bit.\n- Seek the playhead to another frame and move the cube up a bit more.\n- Switch to the Animation workspace.\n- In the Dope Sheet editor, click in an empty space of the keyframe region to deselect all keyframes and channels.\n- Expand the \"Object Transforms\" channel group and, with the mouse cursor in the keyframe region, press A to select all keyframes (but not the channels).\n- Press X and select \"Delete Keyframes.\" All keyframes and channels are deleted as expected. Press Ctrl-Z to revert.\n- Press X again, but this time select \"Clean Keyframes.\" Nothing happens despite there being plenty of keyframes to clean.\n- Move the mouse cursor to the channel region and press A to select all channels.\n- Move the mouse cursor back to the keyframe region and run \"Clean Keyframes\" again. This time, the cleanup works as expected.\n\nThe \"Clean Channels\" operator behaves in the same way.\n\nThe reason this only happens in the Dope Sheet editor and not the Graph Editor is likely that the Graph Editor automatically selects the channels for the selected keyframes, but the Dope Sheet editor does not. (It's not limited to \"Select All\", either; if you box-select keyframes from multiple channels, the same difference is observed.)\n\nSo rather than making \"Clean Keyframes\" and \"Clean Channels\" independent of channel selection, the real fix might be to automatically select the relevant channels in the Dope Sheet editor too.\n\nApart from this, it might make sense to move the \"Clean Channels\" operator to the \"Channel\" menu (and the \"X\" button of the channel region) and make it depend on channel selection *only* - that is, clean all keyframes of the selected channels, even if there are no keyframes selected. That way, there'd be some nice symmetry between the \"Channel\" and \"Key\" menus, both having their own \"Delete\" and \"Clean\" operators.", "Transform node with bicubic filtering distorts image\nWin 7 64bit\n\nBroken: 2.79\n\nWith untouched settings every other option gives proper \"difference\" result, except Bicubic.\n\n\nOpen file, switch between filtering options and see difference from source image.\n[Bicubic_scale.blend](Bicubic_scale.blend)", "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", "Copy Rotation Constraint - adding rotations causes unexpected behaviour\nOperating system: Windows\nGraphics card: GTX 1650 Max-Q`\n\nBroken: v2.81a, v2.81, v2.82\n\nWhen adding a Copy Rotation constraint to an object, the `Add` mode seems to not work correctly\n(or at least how I would expect it to work). For example, setting the rotation of the object to (x,x,x) and\nthe target to (-x, -x, -x) does not consistently result in having no net effect. The value for which this *stops* \nworking is x >= 54.\n\n1 - Add an object, give it a rotation of (80, 80, 80), Euler XYZ (default)\n2 - Add an empty, give it a rotation of (-80, -80, -80)\n3 - Add a Copy rotation constraint on the object, and set the target to empty\n\nThe included `bug.blend` file contains an animation that goes over the values of x as described in the\nabove example from 0-100. The problem can be seen around halfway through the animation at the\ncritical value above.\n\n**Result**\nObject seems to have a weird rotation, which is not the expected outcome. The same happens\nwhen only one of the axes is rotated more, and also when they don't necessarily add up to 0.\n\nThis has been tested on multiple Windows machines.\n\n[bug.blend](bug.blend)\n\n\n\n\n\n\n\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)", "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" ]

[ "rotate using R shortcut in orthographic mode from front/side/top is not accurate.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\n\n\n\nRotate in orthographic mode from one of the views (front, side, left, top, bottom, etc) affect also other axis.\nNo problem with move.\n\nbe sure to be in ortho mode, than go in front/side/top view and press R to rotate.\n\nPlease check the video to understand what I mean\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", "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "Fade Geometry state changes selectability\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 10)\n\nWith Fade Geometry enabled, other objects can not be selected while in pose mode.\nWith Fade Geometry disabled, other objects can be selected while in pose mode.\n\n[#70907.blend](T70907.blend)\n\n- Open file\n- Try clicking on bone and cube - selected item and interaction mode should be changed\n- With the bone selected and in pose mode: in Viewport Overlays, check Fade Geometry\n- Repeat step 2 - once in pose mode, cube can not be selected\n\n\n", "Sculpt Mode Border Mask Tool Todo\n## Sculpt Mode Border Mask Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from mask, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "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", "OpenSubdiv with \"On Cage\" shows vertices of edges that don't make any faces even when everything is hidden\nBroken: version: 2.90.0 Alpha\n\n**Description**\nWhen using the sub-surf modifier with cage enabled, if a mesh has edges that don't make any faces, then the vertices of those edges will still be visible when everything is hidden.\n\n[Open subdiv bug.blend](Open_subdiv_bug.blend)\nOpen the file and just press 'H'\n\n\n", "Edge masking artefacts on higher subdiv levels when removing the mask from lower subdivs\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90 (sub 2)\n\nThis is a follow-up report on this bug report I made: T76386\n\nTo quickly summarise, there are still masking artefacts that aren't removed when you delete a mask at a lower subdiv level. It only deletes the mask that all subdiv levels share, but in the process the edges of the mask remain at the higer levels because said geometry doesn't exist on the lower levels. This causes problems like these to occur:\n[Desktop 2020.05.17 - 00.35.46.01.mp4](Desktop_2020.05.17_-_00.35.46.01.mp4)\n\n\n1) Take a cube and subdivide it.\n\n2) Go down to level 0 and try to mask the mesh, which will be completely invisible. Then pick any subdiv level above it and mask.\n\n3) Remove the mask at a lower subdiv above level 0 and then move up one level. The mask edges should still be there.\n\n4) Repeat 3) until you reach the highest subdiv level.", "Particle edit mode - Hide hairs doesn't work\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 50)\nWorked:\nThe \"hidden\" hairs can't be selected or edited\n\n\nThe hidden hairs are still visible.\n\nAdd a hair system to the default cube \nSwitch to particle edit mode and then switch to point display/select mode\nSelect any number of particles, press H to hide\n- >The hairs are only locked, not hidden\n\n\n", "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", "Debug build BM_mesh_triangulate() will hang forever if mesh face count is high.\nOperating system: Xubuntu 20.04\nGraphics card: NVidia K5100M\n\n\n**Broken ONLY WITH `Debug` build**: Blender 3.0.0 Alpha (It should have been broken way earlier)\nWorked only with `Release` and 'RelWithDebInfo' build: Blender 3.0.0 Alpha\n\n\nThe call to `BM_mesh_triangulate(bm, quad_method, ngon_method, 4, false, NULL, NULL, NULL)` does not exit on some bigger meshes. Specifically, it seems to have been stuck inside `BM_face_kill(bm, faces_double->link);`.\n\n(if you call it with bmesh `op` and `slot_in/out` arguments it will run properly)\n\n\n1. Open 0_rougue_bucket.blend provided below.\n2. Add -> GPencil -> Scene Line Art **OR** go into sculpt mode and enable dynatopo (where it uses the same triangulation call).\n\nOn my machine the bucket runs fine with subdiv levels 1-2 and above 3 the bug shows. The subdiv value in that file is 3.\n\nNote that the bug is only reproducible in `Debug` build. Seems that function doesn't like meshes that has face count higher than a certain amount...\n\nMy guess would be there's a lot of checks in debug code path in the function, somewhere it reaches a case where the memory pool gets corrupted. It never quits, in the task manager, memory doesn't show any changes at all. (It's way below my 32G system memory so it can't be there being not enough memory).\n\nSince this triangulation call is related to sculpt as well so I'm gonna ask if this happens to @PabloDobarro in debug build...\n\n[0_rouge_bucket.blend](0_rouge_bucket.blend)\n\n", "Join Geometry Node makes vertices unselectable + disappear on cage preview\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\n\nUsing Join Geometry makes the vertices unselectable when Geometry Nodes is being visualized in Edit Mode.\n\nWhen using geometry nodes to act as solidify I need to add a Join Geometry at the end. This makes my vertices both disappear and they are unselectable. This happens when the \"On Cage\" overlay is activated. It properly displays the wireframe but the vertices are gone and unselectable. Since it appears and works normally when I disable On Cage I figure this must be a bug.\n\n[Blender 2022-09-08 12-37-19.mp4](Blender_2022-09-08_12-37-19.mp4)\n[JoinGeometryBug3.3.blend](JoinGeometryBug3.3.blend)\n\n\n\n", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "Hiding Armature in Outliner while in Pose Mode, leaves viewport without ability to select or exit the Pose Mode.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0\n\nWhen Armature is hidden via Outliner in Pose Mode, the selection, active object, and the Mode remains on that armature, not allowing to select anything anymore. Same happens with Meshes and Edit Mode, but one is still able to exit the Edit Mode. I assume it's likely that one either shouldn't be able to hide the object one is in Edit/Pose mode with, or the Mode probably should be exited upon hiding it's object. Or, at least, switching the Mode off shouldn't be disabled if the object is considered still active/selected.\n\n[armature.blend](armature.blend)\n - Select Bone,\n - Press Disable in Viewports for Armature object in Outliner,\n - > Can't select other objects in viewport now, or exit the pose mode.", "Mask paint is invisible in Sculpt Mode.\nOperating system:Mac OS 12.3.1\nGraphics card: 24-core GPU (?)\n\n**Blender Version** 3.2.1\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nThe mask in sculpt mode is invisible. I have the overlay turned on and I don't have any unapplied modifiers. I also don't have any physics or particle systems turned on. \n\nThank you for your help.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n" ]

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

[ "Rigid body baked cache not invalidated\nOperating system: Windows 10 Pro 64-bit\nGraphics card: 4095MB NVIDIA GeForce GTX 1080 (NVIDIA)\n\nblender-2.80rc1-windows64\nWorked: (optional)\n\nSimple physics object is trapped in previous (deleted) animated properties.\n\nI have included a blend file which consist of just a cube with physics properties added.\nIt is supposed to fall but it moves to the origin and stays there.\nThe file is a working file from which everything has been deleted and a cube added.\nRun the animation and the cube will behave oddly.\nIf the cube is deleted and a different mesh added, say a sphere and moved and basic physics assigned. It will do the same.\nThis is likely to be a problem with my file from which everything has been deleted??\n[physics-problem.blend](physics-problem.blend)", "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", "Cannot to make single user in object properties (if object is used by multiple collections)\nOperating system:\nGraphics card:\n\nBroken:\n\n\nI made a linked copy of an object (not object data!) in another collection by dragging the object from one window of the outliner to another.\nNow in object properties showing amount users equals 2:\n\n\n\nif you click on button \"make a single copy\" then nothing will happen. I am not sure but seems this UI inconsistency\n\n\nOpen the file and try to make single user to click in object property window:\n\n[make-single-copy.blend](make-single-copy.blend)", "Changing the geometry type in the Vertex Weight Proximity modifier disables \"Invert Falloff\" and \"Normalize Weights\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\nWorked: \n\nIn the **Vertex Weight Proximity** modifier if the proximity mode is set to *Geometry*, changing the geometry type between *vertex, edge and face* disables the options *Invert falloff* and/or *Normalize Weights*.\n[bug.mp4](bug.mp4)\n\nAdd an object, add the vertex weight proximity modifier, set the proximity mode to geometry, enable the options normalize weight and invert falloff and change the geometry type between vertex, edge or face.\n[Based on the default startup]\n\n", "Custom properties without a name cannot be edited/deleted\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.93.6 Release Candidate\n\nA custom property without a name cannot be edited or deleted (gives an error), however in the worked version as stated above, the unnamed property can still be manipulated without triggering an error.\n\n1. In the default scene, create a new custom property for the cube and remove its name completely.\n\n2. Press OK\n3. Blender gives an error, as shown below:\n\n4. Dismiss the pop up and click on either the gear/cross icons:\n\n\n[unnamed_prop.blend](unnamed_prop.blend)\n", "Move some parameters to Blender's DNA\nThese parameters are supported (or going to be) by EEVEE-Next, and we should avoid duplicating the settings for each engine:\n- Motion blur curve\n- Panoramic camera settings\n- View Layer material override\n\nThis is a big change and 4.0 should be the right time to do this.\n\n", "Crash undoing in certain scenario (disabling Global Undo)\nOperating system: Linux-5.10.12-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.82a\n\nCrash undoing in certain scenario (disabling Global Undo)\n\nFrom the default startup file (order of operations is important here):\n- move the cube (could be any objectmode operator) {key G Z 3}\n- disable `Global Undo` in Preferences {key F4} > `Preferences` > `System` > uncheck `Global Undo`\n- add an armature {key Shift A} > `Armature`\n- go to pose mode\n- select bone\n- move bone\n- Undo {key Ctrl Z}\n - > crash\n\n```\n1 BKE_scene_object_base_flag_sync_from_base scene.c 2914 0x35b41a9 \n2 BKE_scene_set_background scene.c 2125 0x35b2957 \n3 setup_app_data blendfile.c 386 0x4b63950 \n4 setup_app_blend_file_data blendfile.c 416 0x4b639e4 \n5 BKE_blendfile_read_from_memfile blendfile.c 524 0x4b63e38 \n6 BKE_memfile_undo_decode blender_undo.c 88 0x4b62cc0 \n7 memfile_undosys_step_decode memfile_undo.c 193 0x486eb47 \n8 undosys_step_decode undo_system.c 214 0x4bb97ec \n9 BKE_undosys_step_load_data_ex undo_system.c 809 0x4bbb2df \n10 BKE_undosys_step_undo_with_data_ex undo_system.c 870 0x4bbb4a4 \n11 BKE_undosys_step_undo_with_data undo_system.c 880 0x4bbb4d3 \n12 BKE_undosys_step_undo undo_system.c 889 0x4bbb511 \n13 ed_undo_step_direction ed_undo.c 278 0x486c907 \n14 ed_undo_exec ed_undo.c 489 0x486d214 \n15 wm_operator_invoke wm_event_system.c 1332 0x3a17b06 \n16 wm_handler_operator_call wm_event_system.c 2161 0x3a198e3 \n17 wm_handlers_do_keymap_with_keymap_handler wm_event_system.c 2486 0x3a1a617 \n18 wm_handlers_do_intern wm_event_system.c 2782 0x3a1b591 \n19 wm_handlers_do wm_event_system.c 2914 0x3a1bafc \n20 wm_event_do_handlers wm_event_system.c 3445 0x3a1d2a3 \n```\n```\n \n```\n\n\n", "Outliner: Object selected/deselected when clicking with RMB on it's object data [`Sync Selection` option causes this]\nBroken: version: 3.0.0\nBroken: version: 2.91.2\nBroken (differently): 2.90.1, 2.83\nWorked: 2.82\n\nWhen clicking with RMB on *some* object data in outliner (can confirm for materials), parent object is selected/deselected (both in outliner and in 3D viewport). That can lead to undesired actions. For example, when click RMB on material object data from a cube and choosing `Delete` you'll get one of the following:\n- Delete only material object data if parent object is not selected\n- Delete cube object itself **and** material object data if parent object is selected\nMesh/ligh/camera object data also have this \"parent object selection/deselection\" behavior but for this object data it's not so apparent in terms of functionality since in both cases mesh/light/camera object data is deleted and object can't exist without those so it's deleted too.\nModifiers and constraints are handled consistent with context menu - deleting only modifier - although it's something to be discussed since it shows that parent object is selected.\nFor shortcut behavior there is already #94062.\n\nIn 2.90.1 core issue is same but behave slightly different - it'll not always change selection/deselection, can provide details if requested.\n\nFor materials:\n1. Open attached file. You'll see two objects with same mesh object data.\n2. Repeatedly click with RMB on material object mata in outliner to see parent object selected/deselected.\n3. Choose `Delete` from context menu when parent object is selected - one of the objects is deleted and one material that was clicked on (you can see it on other objest mesh object data since they share it).\n4. Undo\n5. Choose `Delete` from context menu when parent object is not selected - only one material is deleted.\n\nFor showcasing mesh/light/camera data behavior:\n1. Open attached file.\n2. RMB on `Sphere` mesh object data to a point where parent object is either selected or deselected.\n3. Choose `Delete` from context menu - in both cases all objects are deleted.\n[RMB outliner selection bug.blend](RMB_outliner_selection_bug.blend)", "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)", "Can't edit new driver on an overriden property on a linked object with no animation data\n## Simplified Report\n\n- The following file contains an object with no animation data.\n- Link the object to a new file and make a library override from it.\n- Add a new driver on one of its location channels.\n- Notice that driver options are grayed out and can't be edited.\n- One expects to be able to edit the driver since the object has no animation data. \n\n[libraryFileWithNoAnimationData.blend](libraryFileWithNoAnimationData.blend)\n\n## Original Report\n\n\nOperating system: Linux-5.15.60-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0\nWorked: ??? I could have sworn this worked in 3.2 but it seems to have the same behavior. Same in 2.93.\n\nUsing drivers with overridden properties is not really usable. I can add a driver, but then I cannot edit it.\n\nLink a collection into a file and make a library override. Right-click on a property and choose \"Add Driver\".\nRight click on the property (which should turn purple) and then choose \"Edit Driver\" Notice that the\ndriver's controls are all blurred out! You can't edit them in the UI.\nIt gets worse!\nOpen a driver-editor window so you can watch what happens in the next step, and select the driver you\njust created- open the \"Drivers\" tab in the window. Look at the expression.\nIn the main window (not the driver window), click on the driven property and type ~~\"#1\" - when you\nprepend a hash symbol, that tells Blender to edit the expression of a driver (it's a handy way to make\nnew drivers with simple expressions. Try it at home!)~~ **edit: it looks like you don't need the hash when it is already driven.**\nNow, notice the expression change in the driver window that you aren't normally able to edit!\nI have also confirmed that you can edit some properties with the Python API that you cannot edit in\nthe user interface.\n\n**My Thoughts** (If you're interested)\nI do not know if the design for overrides is intended to support using drivers like this. It feels a little squishy\nbecause I don't know if Blender will keep the driver around when I resync the override. On the other hand, it's\nreally handy when doing animation that is easier to do programmatically, such as causing a bone to oscillate\nwith sine-waves (e.g. a plant waving with the wind). Sometimes I use a driver to bake keyframes - so I set up the\ndriver and then bake its motion to an action, and get rid of the driver. It is my opinion that driver support is\nnecessary for overrides, because it's something I expect to be able to use, as an animator. I don't know if the\nold Proxy system supported drivers, though.\nAt any rate, if it is blocked from editing in one place, it should be blocked from editing through the API, too.\n\nI apologize if this is a known issue. I don't see any similar bug reports but it appears things have been like this\nfor a while.", "Regression: unhide now is global even in local mode\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.79b\n\nAlt+H in local view unhides objects all over the scene instead only local context, as it work in 2.79\nPlease fix. It is very handy feature and we have lost it.\n\n**Step to Reproduce**\n- Open .blend file\n- Select a sphere and Hide: {key H}\n- Select all three cubes and enter in Local view: {key /}\n- Hide cubes\n- Now unhide cubes in Local view: {key Alt H}\n- sphere is also visible (Either check outliner or Switch back from Local view)\n\nTest File:\n[#92527.blend](T92527.blend)\n[2021-10-27_12-23-23.mp4](2021-10-27_12-23-23.mp4)", "Add Object Tool, Resolve UI Issues & Polish\nThis task is to track the add-object tool.\n\n- - [x] Resolve behavior when axis aligned, see: #57210 (currently creates very large object). Done 1501c3adad\n- - [ ] Review design changes proposed by @DanielBystedt #57210#1010083", "Array modifier is crazy, when using \"object offset\" pointed to empty, which is parented to curve\nOperating system: Mac OS Catalina 10.15.4 (latest)\nGraphics card: Intel HD 6000\n\nBroken: 2.83 beta as of 8-th of May\n\nArray modifier is crazy, when using \"object offset\" pointed to empty, which is parented to curve. And when the CURVE CONVERTED TO MESH -- it just destroys scale of object!\n\n1) Open .blend\n[plants.blend](plants.blend)\n2) Try to move empty -- everything works fine\n3) Select \"empty\" and \"petals\" (with shift) then parent them (Ctrl + P -- to object) to \"bezier curve\"\n4) Select bezier curve and \"convert to mesh\"\n5) Now try to move empty\n\nBefore:\n\nAfter:\n", "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", "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" ]

[ "Going out of local view when editing the context menu of a new objekt\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.93.1\n\n\nWhen you edit the context menu while being in local view blender goes out of Local view.\n\n1. open a new blend file \n2. add a new objekt\n3. then go into local view\n4. bring the context menu with the shortcut F9 back.\n5. edit one of the parameters ideally the size or the position\n6. that should bring you out of local view\n\n", "Property changes get reset when changing parameters of previously added primitive\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\nProperty changes get reset when changing the parameters of a previously added primitive, see the attached screen capture for an example, however it seems to occur for any property and any parameter changed.\n\n- Add a primitive, keep the in-viewport parameter menu open.\n- Change unit (or anything else in the property editor that doesn't close the on-screen menu)\n- Change any of the primitive's parameters\n- The property change get reset\n\n[Schermopname 2021-08-29 om 21.37.15.mov](Schermopname_2021-08-29_om_21.37.15.mov)", "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", "Adjust Last Operation UI might get in conflict with setting properties outside this UI as well\nBroken:\n2.80 (sub 35), branch: blender2.8, commit date: 2018-12-04 16:52, hash: 7e5f31be418\n\n\nCurve settings like Fill Mode and Bevel stettings get reset if you change the curve settings via popup.\n(Setting some properties)\n\n...then changing something in the popup cancels former settings\n\n\nWhen i add a curve and change the bevel settings in the properties, i still can change the settings via the popup in the left bottom window corner, which results in resetting the settings in the properties. \n\nI think a user would expect the popup to close the moment he/she alters settings in the properties.", "changing the state of an object in the outliner resets while changing a value in the option-panel for the adding of another object\nOperating system: Linux-4.19.0-14-amd64-x86_64-with-glibc2.28 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.181.07\n\nBroken: version: 2.93.0 Alpha\n\nDuring the adding of an object (only tried this with a mesh and a lamp) it is not possible to change the state (visibility in the viewport or renders) of another object in the outliner.\n\n\n*Based on the default startup*\n\n* change the viewport shading to wireframe mode (to see overlapping objects)\n* add an object (for example a uv sphere)\n* make any change to the other objects' visibility settings in the outliner\n* change any value in the option-panel for the adding\n\n\n", "Renaming a new object before adjusting the parameters resets the object name\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: 3.0.0 Alpha\nWorked: the issue is here since many Blender versions (tested 2.93 and 3.0a)\n\nRenaming a new object before adjusting the parameters resets the object name\n\nWith default startup configuration or any blend file :\n- Add any object (cube or whatever).\n- Rename it.\n- Adjust one parameter of this new object in the popup in the bottom left corner (or type F9 to reopen the popup).\n- After adjusting any kind of parameter, the object name resets automatically with the old name.\n- Try again to rename another time the same object and adjust the parameters and the object name resets automatically.\n\n", "Reset Unit setting in Scence Properties menu\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nReset unit setting\n\nThe initial state: New file - Genral. Example Cube - Deleted. Set Object mode\n\nSteps\n\n1. Menu: Add - Mesh - Torus\n2. Scene properties - Units System, set Metric; Length set Millimeters\n3. Open menu Add Torus\n4. Dimension Mode - Major/Minor\n5. Change value Major Radius, enter a number\n6. Click Enter or click LMB in field Minor Radius\n7. Field units changed to meter\n8. Look at menu Scence Properties - Units - Length. Units changed to Meter.\n\n", "using the redo menu in isolation mode cancels out of isolation\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\n\nusing the redo menu in isolation mode cancels out of isolation.\n\n\n\n - create two boxes and while the redo menu is still up for the second box's creation, go into isolation mode by pressing / on the numpad.\n - press f9 to bring the redo menu back up (it dissapears when you enter isolation mode)\n - change a parameter\n - you are no longer in isolation mode.\n # \n\n\n", "Hidden objects reappear\nOperating system: Linux-5.8.0-53-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10\n\nBroken: version: 2.93.0 Beta\nBroken: version: 3.0.0 Alpha\nBroken: version: 2.83.16 Release Candidate\nBroken: version: 2.92.0\nMore I have not tested\n\nIf I add a new object, hide the others with / and then change a value with F9 then the hidden objects reappear.\n\nOpen Blender, with Shift+A add a object, numpad / and change a value with F9\n\n" ]

[ "The result of Dynamic paint Image sequence is brighter than intended when using initial color.\nOperating system:Windows 10 64bit\nGraphics card: GTX 1060\n\nBroken: 2.79b, 2.80\nWorked: \n\nthe result of baked Image is birghter than it displays on properties panel. \nNot sure but seems like it is gamma correcting the color but the input color is already in sRGB space, not in linear space!\n\n\nset any color that is not too bright or dark to \nDynamic paint - Canvas - Image Sequence - Initial Color : color.\nthen press \"Bake Image sequence\".\nThe color of baked Image will be brighter than the color you set.\n[dynamic paint color.blend](dynamic_paint_color.blend)", "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", "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", "Rendered object in displayed as a transparent png\nOperating system: Windows-10-10.0.19043\nGraphics card: Radeon AMD Radeon HD 8500M (4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001)\n\nWorked: (3.2.0)\n\nidk if it is even a bug but when i render my object, it shows the object as a transparent png. how do i fix it?\n\n[donut.blend](donut.blend)", "Film Exposure Affects Shadow Catcher Pass Environment\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3080 Ti\n\nBroken: 3.5.1\nWorked: Unsure\n\nChanging \"Film -> Exposure\" with \"Film -> Transparent\" affects background of Shadow Catcher Pass. Effect on compositing is that the composite gets an additional darkening in \"transparent\" areas from multiplying Shadow Catcher pass.\n\n1. Switch to Cycles.\n2. Create plane under default Cube.\n3. Set the plane to be a Shadow Catcher.\n4. Enable Shadow Catcher pass in render layers.\n5. Change Film->Exposure on render tab to something less than 1.0.\n6. Turn on \"Transparent\" in render tab.\nRender and check Shadow Catcher (not noisy one) pass: areas that are \"transparent\" (not covered by the default cube or the shadow catcher plane) should be 1.0 but will be more or less equal to the Exposure value set.\n\nI believe this is incorrect: multiplying this shadow catcher pass over an already-exposure-compensated rendered image will cause an additional darkening affect in areas where the shadow catcher isn't present in the view.\n\nAttached JPG shows a scene where the shadow catcher plane ends, and the transparent world exists beyond. The shadow catcher is correctly at 1.0 where there aren't any shadows, but the world background is .75 which is what the Exposure value was set to be.\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.", "\"New material\" tooltip should be \"Copy current material\"\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.25\n\nBroken: version: 4.0.0 Alpha\nWorked: Unknown\n\nThe tooltip in the image is not correct and might cause confusion. Clicking the button instead of just creating a new material, it copies the material to a new one, instead of creating a new material from a blank template.\n\nHover mouse over the icon pointed by the red arrow in the attached image (located in the shader editor).\n\nThe tooltip says: \"New material\".\nI think the tooltip should say:\n\"Copy material\"\n\"Creates a new material by duplicating the current one\"\n\n**Observation**\nThis issue is similar to issue #107625, but in another part of Blender.", "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", " 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", "Rendering in cycles causes objects with materials to go black and shiny when using the GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 7900 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\nWorked: N/a\n\nWhen my render engine is set to cycles and device is set to GPU Computer (with HIP and my 7900 XT selected), if I look at an object with a material applied in either viewport shading or as a rendered image the model will appear black and shiny or occasionally will just show as a flat blue colour. \n\nThis issue does not occur when using the CPU as the device instead and also did not begin to occur until a few days ago (prior to which it was working fine).\n\nI've checked the same blender file on a laptop with a 3060 GPU which worked correctly so I don't think the file itself is corrupted.\n\nI have also checked multiple blend files, some of which work fine, others do not, one file has some things working and other things broken (I will attach it to this bug report)\n\n\n1. Load the attached blend file \"ArkenV1R1_Interior.blend\".\n2. Go to edit > preferences > system > cycles render devices, set it to HIP with RX 7900 XT selected.\n3. Under scene settings, change the render engine to cycles and device to GPU compute.\n4. Switch to Viewport shading.\n5. Observe that the bullets and floor panel are shown as black and shiny while the table renders correctly (grey and blue).\n6. Press F12 and observe that the rendered image also shows the bullets and floor panel as black and shiny.\n\n\n**Additional**\nIncorrectRender.png was rendered using GPU\nCorrectRender.png was rendered using CPU\n\nI will be happy to provide anything else needed to figure this out, thanks!\n\n", "Cycles GPU rendering is broken on Apple M1/macOS Ventura\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.3.0 Release Candidate\nWorked: 3.2.2\n\nCycles GPU rendering is broken, CPU rendering works as expected.\n\nCycles - CPU:\n\n\nCycles - GPU Compute:\n\n\n1. Create any scene\n2. Switch Cycles to GPU Compute\n[simple_test.blend](simple_test.blend)\n", "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.", "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", "GPU: Share GPU Textures when using the same file path.\nCurrently the GPU textures that Workbench and Eevee uses are cached inside the image data-block.\nIn productions scenes were textures are reused by different materials sourcing from different blend files the GPU textures are not shared, although they might use the same file on disk.\n\nThe idea is to share the GPU textures between those image data-blocks.\n\n## Corner cases\n* GPU textures can only be shared when data-block isn't modifier. This could mean that GPU textures could be shared, until the user starts modify-ing one.\n* GPU textures for movies and sequences can only be shared when they reflect the same frame number. Currently a eevee cannot handle drawing multiple frames from the same image data-block. A work around for this is to duplicate the image block. For the short term we could also not support sharing GPU textures for movies and sequences at all as this isn't used that much to our knowledge.\n* Both single tiled and multi-tiled images should be supported.\n\n## Implementation\n* Use a single GPUTexture cache. Store GPU textures with a key. Key could be some values stored as a string. Per key a group of GPU Textures can be retrieved (Tiled, TileIndex, Image, left/right) etc.\n* Additional benefit is that usage tagging can be done faster as we don't need to go over all the image data-blocks in the scene. (although don't think this would be noticeable to users)\n* Key could contain:\n**Type of image** filename\n** Optional the IDBlock name+library for when images are modified.\n\n## Related changes\n* `eImageTextureResolution` isn't used anymore and could be removed. There is no need anymore to support multiple texture resolutions at the same time. Will reduce some code complexity and nano improvement in performance. {f41c7723c93b}\n* `IMA_NOCOLLECT` can be removed aswell\n\nNOTE: Request made by the Heist project.", "Solid Viewport Transparency Artifacts/Dots\nOperating system: Windows 10 Home Build 19044\nGraphics card: iGPU on Intel Core i7 1185G7 (Iris Xe Graphics)\n\nBroken: 3.1.2\n\nI downloaded a 3D model from TurboSquid of an Aston Martin Vantage (the model is free, [find it here ](3d-aston-martin-s-1685480)) and the viewport has strange dots at object edges when looked at through the partially transparent glass. I tracked the issue down to the alpha of the Glass material in `Properties > Material Properties > Viewport Display`, the dots only appear when the alpha value is not 0.0 or 1.0.\n\n - Open `TransparencyBug.blend` or `astonAston MArtinV12 Vantage S 2016 .blend` (files at the bottom)\n - Set Viewport Shading to Solid\n - Set transparency of Transparent or Glass material (Properties>Material Properties>Viewport Display, select Transparent or Glass material) to some decimal value other than 0.0 and 1.0\n - Dots appear at edges of materials looked at through transparent objects\n\n\n**Images**\n\nastonAston MArtinV12 Vantage S 2016 .blend:\nAlpha 1.0: \nAlpha 0.201: \nAlpha 0.0: \n\nTransparencyBug.blend:\nAlpha 1.0:\nAlpha 0.5: \nAlpha 0.0: \n\n**Affected Files**\n[TransparencyBug.blend](TransparencyBug.blend)\n[astonAston MArtinV12 Vantage S 2016 .blend](astonAston_MArtinV12_Vantage_S_2016_.blend)" ]

[ "Objects with multiple materials are not displaying correctly - transparent faces\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\n[Objects with multiple materials are not displaying correctly - transparent faces\n\nMake a plane, subdivide a few times, unwrap, assign a material\nSelect some faces, add a new material, assign it to those faces\nThe second material now has lots of transparent faces?\n\nThanks\nWayne\n\n" ]

[ "Crash with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "Multiresolution displacement baking do not work properly\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Beta\n\nOriginal on the left produces map, thad displace surface like on the right.\nI suppose, there is wrong gamut/ color conversion or baking ray shoots from Hipoly to lowpoly instead measuring height difference from lowpoly to hipoly. Displacement baking is not equal to normal baking!\n\n{[F10039179](изображение.png) size=full}\n\n[mr bake.blend](mr_bake.blend)\n\n[2021-04-26_15-44-07.mp4](2021-04-26_15-44-07.mp4)", "Viscosity instability in mantaflow\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.3.1\n\nI'm pretty new too blender so I might be doing something wrong but anyway I've been experimenting with viscosity and higher resolutions cause the liquid to \"explode\" I tried for a week to find the problem and couldn't figure out what's causing it so I assume its a bug\n\nDemonstration:\n[[agbOUYPQpJ0]]\n\nOpen the .blend and play it or bake data at a high resolution (150 in my case) and see the instability, This scene is slightly complex but I can confirm just a domain and inflow will do the same \n[House flood 2.blend](House_flood_2.blend)\nSimplified scene, 128 res, 2 m domain\n[Instability demo.blend](Instability_demo.blend)\nSimplified scene with cache\n[Instability demonstration zipped.zip](Instability_demonstration_zipped.zip)\nIncase this helps\n[system-info.txt](system-info.txt)\n", "Hiding faces on a specific mesh causes random hidden edges to display in place of non-hidden ones\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.2\nWorked: unknown, but same bug occurs in 3.5\n\nWhen selecting certain faces on this mesh (see attached STL file), pressing H or shift-H to hide faces will cause a random set of floating edges to display in the hidden regions, and the visible region will display with no edges (making it impossible to see your selection in edge select mode). The set of edges is truly random, as undo / redo will show a different set of edges each time.\n\n| Here is the full mesh with an example selection | Here is the result of pressing shift-H |\n| -- | -- |\n|  |  |\n\n1. Open the attached blend file bugball.blend, and enter edit mode on the ball to see the random floating ghost edges.\n2. Press 2 and try selecting things (selections on the un-hidden faces are invisible, and the ghost edges can't be selected).\n3. Press Alt-H and Shift-H to see that a different set of floating edges appears every time.\n\nIf the blend file doesn't work, try and import the attached STL file using file -> import -> stl and observe the same behavior.\n\n", "Remesh with small voxel size sometimes generates mesh with many holes\nOperating system: macOS-14.0-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: 3.1 - 4.0\n\nRemeshing breaks objects\n<video src=\"attachment\" controls></video>\n\nIn a new scene add a monkey model and jump into sculpting, change the voxel size to 0.0024 m and remesh...the object breaks\n\n", "Blender full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "Fluid/Smoke modifier has an \"Apply\" button, which is misleading/dangerous (only meaningful for mesh-baked liquid domains)\n(All systems)\n\n- 2.81a and earlier (pre-mantaflow)\n- and 2.82 Alpha (2020-01-05) 5c66739b782e (mantaflow)\n\n**Short description of the error**\nAll objects involved in a fluid (gas or liquid) simulation, including domains, effectors, etc, have a modifier in the modifier stack.\n\nHowever, in all cases except one, the \"Apply\" button in this modifier is (as far as I can tell) just a synonym for \"remove the modifier and the physics settings (destructively!)\". It only actually \"applies\" something when we're dealing with mesh-baked liquid domains.\n\nSuch \"Apply\" button may be misleading and dangerous if a user were to, for instance, try to \"freeze\" a frame of a smoke simulation, which will just result in them losing all cache.", "GPU texture baking with large tile size fails\nOperating system: Windows 10\nGraphics card: Vega56\n\nBroken: 2.90.1\nWorked: 2.83.8\nNot sure if this was a particular commit (or if libraries changed at that time) but this broke between 51ac411ce8 and 5c5a638b57\n\nI was trying to bake 8k emissive map but it doesnt work so i was searching for some error about hour a then try to make 4k emissive map and everything worked jsut fine with same settings, only thing i change was resolution of image from 8k to 4k. After this i try again bake 8k emissive but doesnt work image was empty so this must be some sort of bug.\nBased on the default startup or an attached .blend file (as simple as possible).\n[bug.blend](bug.blend)\n\nThis file has its tile size at 8192x8192.\nWith a tile size of 4096x4096 it works fine.", "Cycles Bake Selected to Active with transparency gives undesirable results\nSystem Information:\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GT 635M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\nBroken: version: 2.81 (sub 16)\n\n\nBug or unintended behavior:\nBaking using \"Selected to Active\" does not take into account transparency \n\nHow to reproduce:\nCreate two objects with materials and textures assigned to each;\n```\n One texture to be baked to\n One texture with an alpha channel (optionally a normal map)\n```\n\nIn the shader editor, modify the material of the object with a transparency channel\n```\n Join the transparent textures' alpha into the alpha of the shader that is being used\n (optionally join the color of a normal map)\n```\n\nIn render properties, enable Selected to Active and use an appropriate ray distance\n```\n Finally bake.\n```\n\nResult:\nWhen baking combined or most channels, the transparent areas will assume the color as if it were completely opaque,\nWhen baking normals with transparency, the transparent areas will mix with the normal of the geometry that is being baked to the active selection.\nBoth outcomes are unfavorable when working with transparent cards/ribbons.\n\n[bugreport.blend](bugreport.blend)\n\nI packed the textures edited the project to make the issues that I am having more clear.\n\n{[F8286028](image.png), size=full}\nThere are now 3 overlapping objects with transparency.\nAfter baking normals or color, none of the colors or normals behind the transparent objects appear because the object appears to draw over top without transparency.\nThis example also shows that with full normal transparency, the normal will then be the geometry normal of the object rather than a flat normal or anything that is below the object.", "Data lost to a severe crash was auto-recovered and forcefully overrid data that was saved to disk even tho no recovery options were used\nOperating system: Windows 11\nGraphics card: Gigabyte Windforce RTX 2060 OC Super 6GB\n\nBroken: (steam 3.4.x-3.6.2)\nWorked: ()\n\nnote: this is not related to the recovery or auto recovery systems but about pre-crash data being used from ram instead of reading saved data from disk\n\nnote 2: i verified it's old data as it happened with a mask this time and the vertex ids it was assigned after the crash corresponded to the ones that the mask was assigned to after the bug, but was improperly recovered as ids changed due to changes to the mesh, and unmasking those vertices caused them to be moved a random locations as the shapekey they where assigned to did not exist anymore\n\nAfter a severe crash that was not induced by hardware crashes(ie: out of memory/vram, ran out of pagefile memory etc)\nbut from an error internal to blender, even tho data and changes where saved to disk, blender auto recovered data that was not saved and lost to a crash, and it possibly corresponded to a block of ram that was not freed reported by blender in the cmd window;\nafter the unprompted recovery the data even tho it was corrupted it forcefully overrid the data that was saved to disk upon load\n\nthis error seems to recover all kinds of data, it restored a sculpt mask that had been corrupted and was after deleted and saved the file to disk as not having said mask, to even internal textures/texture paint, and changes to properties\n\ni came to this correlation as this type of forceful recovery seems to specifically happen before the ram drops in utilization after a save and a sizable chunk of ram sometimes in the gigabytes is reported as not freed upon closure from the crash\n\nthis also seems to cause blender to not generate crash.log files\n\n\n\nimportant: blender has to terminate from an internal system and not the OS, as even tho blocks of ram still weren't freed windows took care of it in the cases of hardware related crashes causing this error to not happen\n\n\n\nobtain a crash from any of blender's systems not the OS(import, sculpt mask, operators/geometry nodes with faulty input seem to be the most reliable)\n\nif the file is still saving and completes but the ram has not yet been cleared and a crash happens there is a very high chance the old data will be used instead of the data saved to disk\n\n**regarding a blend file:**\nthere is no way for me to provide a blend file as it's dependent on data that is left in the ram by the crash and happened the same way regardless of file, and would require me to find a reliable way to crash blender in this specific conditions, which is out of my knowledge.\n\n", "Motion Blur weird artifacts when rendering MeshSequenceCache USD\nOperating system: Windows 11\nGraphics card: RTX 2080 Ti\n\nBroken: 3.6 LTS, but it also seem to happen in older versions\n\n\nI'm getting some weird artifacts when rendering a USD mesh cache with motion blur enabled.\n\nI've exported the mesh from maya 2023 using the Arnold USD export method. \n\nWhat i've tried:\n\n- Disable Auto Smooth Normals and removing every Subdivision Surface Modifier.\n- Trying to change the position of the motion blur from Center to Start or End\n\nThe problem persist.\n\nExport a high res mesh animation from Maya using Arnold USD as export option.\n\nImport it in Blender and try to render the sequence with Motion Blur activated.\n\nBlend file Link : view?usp=sharing \n", "Bake artifacts with multimaterial in object\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nThen i try bake Ambient Occlusion in object with 2 or more assigned materials, Ambient Occlusiun bakes grey or black squares\n\n\n- Open attached file and bake ambient occlusion.\n[Bake_Test.blend](Bake_Test.blend)\n\n", "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.", "Inconsistent color space baking to float and byte images\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14742 Core Profile Context 21.8.2 27.20.22025.1006\n\nBroken: version: 2.93.6\nWorked: ---\n\nIn blender we can create an image with 32 bit resolution (See image):\n\n\nThe new 32bit image can be used for baking in order to obtain a normal map.\nThis map works perfectly until saved in PNG (16bit or 8bit).\nInterestingly you can bake directly on a 16bit image and the resulting image works even if it is saved in 8bit.\n\nHere is a file where I put different pixel resolution combinations on textures saved in PNG:\n[TesteNormal.blend](TesteNormal.blend)\n\n\n\n1 - Bake a normal map image with 32 bit option enabled. (see the pic \"sample3.jpg\")\n```\n A simple cube can be used, no need to add any detail.\n```\n2 - Save the image as PNG in 8 bit or 16 bit.\n3 - Create a material and connect the saved baked normal map image to the normal map node. \n```\n Change color space option to \"non-color\" \n```\n4 - Observe the object becomes dark in rendered mode in Eevee or Cycles. \n\n[Teste_Normal_Textures.blend](Teste_Normal_Textures.blend)\n", "Blender 4.0.0 - Armature Rig with IK broken\nOperating system: MacOs Ventura 13.4.1\nGraphics card: Radeon Pro\n\nBroken: version: 4.0.0 Alpha, branch: main, commit date: 2023-08-23 19:52, hash: 7c2dc5183d03, type: release\nCaused by 6b872079fec9336865638ad9cfa76e37e8e627c5\n\nI have rigged mesh, commercially available at ArtStation. It worked well up until now. In 4.0.0 it is broken:\n- shapes not rendered until i switch to wireframe mode and back\n- IK ignored\n\nLook at video - i open the file in 3.6.3 and in 4.0.0. In 3.6.3 everything fine, in 4.0.0 the problem mentioned occur.\nBlend file also attached\n\n" ]

[ "Corrupted mesh display on macOS\nOperating system: Darwin-17.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.60.26\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nOn opening a file the model has extra faces that did not exist before. See the attached two files. One is from the May 28th build and the other is from May 31. The model is fine in the May 28th build with no problems. The model form the May 31 build has the extra faces connecting external boundaries. \n\nThe model made from a was scanned hand drawn image, imported into Adobe Illustrator, Cleaned up, saved as an SVG, Imported into blender and converted to a mesh from curves. It was then cleaned up, extruded and material applied.\n\n1 Open Blender\n2 Open recent \n\n[Build 28 May 2019 Buck and Doe NO problem.blend](Build_28_May_2019_Buck_and_Doe_NO_problem.blend)\n\n[Build 31 May 2019 Buck and Doe problem.blend](Build_31_May_2019_Buck_and_Doe_problem.blend)\n" ]

[ "AMD: Rendering Instances On Points using a Collection crashes Blender on Linux\nBroken\nOperating system: Linux-6.2.0-060200-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.2.0-060200-generic) AMD 4.6 (Core Profile) Mesa 23.1.0\nversion: 3.5.1\n\nBroken\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\nversion: 3.5.1\n\nFine (same system as above, but using nvidia)\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\nversion: 3.5.1\n\n\nOn Linux, using Geometry Nodes to have a Collection Info node feed instances of like items to an Instance on Points node going to Group Output will work properly, but will crash Blender when Rendering.\n\nDoing the obligatory Donut Tutorial. When creating the sprinkles using the Collection Info node to feed Instance on Points will create a nice set of sprinkles. The sprinkles share a Linked Material to randomize colors. Using Render Preview in the Layout (or Shading) tab correctly displays randomly colored sprinkles. However, actually rendering crashes Blender. Using the Realize Instances geometry node before the Output node will allow it to render, but then every sprinkle has a single, random color.\n\nReproduce (using Linux): \n1. Using the attached file, render using the Realize Instances node on the Icing's Geometry Nodes (file's current setup). Blender will not crash, but all sprinkles have same color. \n2. Remove the Realize Instances geometry node, and the sprinkle colors will be properly randomized. Render, and blender will crash.\n\nWarning: This is a hard system freeze, not a simple Blender crash. Typically requires a system reset to recover.\nUpdate: AMD graphic cards only. Eevee rendering only.", "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", "Shader compilation is crash\nOperating system: Linux-6.3.0-1-MANJARO-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 23.0.3\n\nBroken: version: 3.5.1, 3.6.0\nWorked: 2.93.17, 3.3.6\n\n\nI am creating a shader and I need to use a lot of color mix node:\n| Version | Result |\n| -- | -- |\n| 2.93.17 |  |\n| 3.3.6 |  |\n| 3.5 |  |\n\n\nLaunch attached blend in different the Blender versions", "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", "Node groups' new method doesn't throw errors at inputs and outputs collections\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 3.1.0 Alpha\n\n\nNode groups' new method doesn't throw errors at inputs and outputs collections\n\n1. Create a geometry nodes modifier, get node group:\n\n```\nnodes = C.object.modifiers[0].node_group\n```\n\n2. Add new input or output by command \n\n```\nnodes.outputs.new(\"RGBA\",'new')\n```\n3. Note that there are no errors, but a new socket hasn't been created. \n\n\n\n", "Line Art doesn't exclude object's instanced by geo node\nOperating system: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.3.1\nBroken: version: 3.5.0 Alpha\n\nCollection Line Art includes instances that are distribute my geometry nodes, even if that object is not within the Line Art target collection.\n\n\n[Line_art_Geo_Nodes_instance_bug.blend](Line_art_Geo_Nodes_instance_bug.blend)\n**Exact steps for others to reproduce with example file**\n1. Open Attached File \n2. Observe Line Art is on objects outside target collection\n\n**Exact steps for others to reproduce the error from Startup**\n1. Distribute Objects from a collection with Geo-Nodes\n2. Create a second collection with a Line Art Target Object only\n3. Add Collection Line Art and target collection from step 2\n4. Line Art will be drawn on Geo-Nodes instanced objects\n\n\n\n", "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)", "Geometry node - setting lacunarity to 0 crashes Blender (musgrave texture)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.2.2\n\nIn a fairly simple geonode tree, trying to set lacunarity to 0 will crash Blender instantly.\n\n- Use attached Blend.file\n- In the 'set position' branch, try to set 'musgrave texture' lacunarity to 0\n- Crashes everytime for me\n\n[Geonode attribute.blend](Geonode_attribute.blend)", "Crash when loading a geometry nodes asset into itself\nOperating system: Win 11\nGraphics card: 2070\n\nBroken: 3.4, 4.0\nWorked: none\n\nWhen working on an geometry nodes asset in an asset library - if you search for the name and adding it to the graph it causes a crash. \n\nDrag n drop from the asset browser behaves correctly here - so I think its just the node search code which is missing the check for self referencing.\n\n1. Download the blend file.\n2. Put into a folder.\n3. Add folder as asset library in prefs -> file paths -> asset libraries.\n4. Open the blend file from that folder.\n5. Go to the geometry node graph (should be open already).\n6. `Shift` + `A` to add new nodes.\n6. Search \"noop\" and press enter.\n\n", "Glitches with Curve Fill Node\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked version: never\n\nIf you instance circles or other curves on a curve and you will realize those instances, and you will use the curve fill node on them. There are some glitches or inconsistencies.\nIf you change the scale, the fill node will also randomly decide what should be filled.\n\n\n\n\nTest File:\n[#95518.blend](T95518.blend)\n", "Materials linked to the object's data are lost when removing attributes from instances in geometry nodes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\nMaterials linked to the object's data are lost when removing attributes from instances in geometry nodes.\n\n1.Instance a collection using geometry nodes.\n2.Remove an attribute from the instances (the attribute doesn't need to exist).\n3.Materials stored on the object data are now lost.\n\n\n[BugExample.blend](BugExample.blend)\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", "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: 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", "Make Instances Real doesn't work for geometry instances\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0\n\nWhen I want to make instances real on object that has geometry nodes, blender create duplicate of whole mesh, togather with instances, on each place (point) where single instance mesh should be. I have attached screenshots and test scene that reproduces the bug. \n\nOpen .blend file I sent you, hover with mouse over 4 instaced spheres, and pres ctrl+A... select make instances real. You will see that geometry nodes instances are not created properly (whole geometry is duplicated on each geometry node point).\n\nSimilar thing happens when instancing collections, and trying to make them real - the parent relationship/hiararchy is not working. So there is a bug there also.[geom_nodes_bug.zip](geom_nodes_bug.zip)\n\n\n\n\n" ]

[ "Blender Collapses with Geometry Nodes Applied To Second Object\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.148202 Core Profile Context 21.3.1 27.20.15003.1004\n\nBroken: version: 2.93.0 Beta\nWorked: Never\n\nProgram shuts down when I apply **geometry nodes** to secondary object.\n\n[#88454.blend](T88454.blend)\n\n- Open file\n- Connect Point Distribute node to geometry input/output\n" ]

[ "Shader Displacement issues with dicing camera\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\n**Short description of error** \nWhen using a Dicing camera, it doesn't update on its own, you have to make a change to the shader or the mesh for the dicing to update. \n\n\n\n- Open default .blend file\n- Switch to viewport rendering.\n- Force update the viewport (as shown in the video, just click and exit any node socket value)\n", "Cycles: Motion blur Artifacts and high render time with Metaball\nOperating system: Ubuntu Linux 22.04 / Windows 10 64-bit\nGraphics card: Nvidia GeForce RTX 3080\n\nBroken: 3.60, 3.61, 3.62, 4.0.0-alpha+main.d0dcfb815964\nWorked: unknown\n\n**Short Description**\nActivating motion blur in Cycles results in artifacts and higher render time for 2% of frames\nReproducible across Ubuntu/Windows, CPU/CUDA/OptiX.\n\n\n- Open attached file \"phoenix12-reprocase.blend\"\n- Enable motion blur (should already be enabled)\n- Reduce transmission bounce\n- Render frame 189\n- Render frame 190 (takes significant time to render. Also notice Artifacts)\n\nIn the provided file, frames 74, 124, 179, 190 seem to have this problem. Turning off motion blur fixes the problem.\n\n|189 | 190 |\n|---|---|\n|  |  |", "EEVEE AOV of full transparency is bad compared to Cycles\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4\n\nAOV of full transparent shader is barely noticeable. Cycles works fine.\n\n\n[eevee_aov_transparent.blend](eevee_aov_transparent.blend)\nFor default scene:\n\n - Set fully transparent shader (alpha clip or hashed) and add AOV layer for it\n - Render EEVEE -> AOV layer is bad\n\n", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Very slow rendering on RTX 3080!\nOperating system: windows 11\nGraphics card: RXT 3080 (Gainward RTX 3080 Chasing Wind)\n\nBroken: 3.4.1; 3.4; 3.3.1\nWorked: Works on the vega 11 video card built into the processor, also works stably on the CPU. Works on RTX 3080 graphics card with driver 497.29 on all blender versions\n\nAt times while working in the blender program, I encounter absurdly long render times for one frame: oB4BJ5L.png (shreenshot).\n\nI ran render tests on different driver versions (527.56, 522.30, 526.86, 497.29). In all versions of the drivers, after some time, performance dropped hundreds of times, except for driver 497.29. It works stably. Also tests were carried out on blender versions 3.3, 3.4, 3.4.1.\n\nIt would seem that the problem is solved, you can simply install the 497.29 driver and work stably on it, but this is not so. Only blender works on this driver version, other programs crash and require drivers of at least 520. Regardless of the driver version, the video card is always loaded at 100%\n\nI've done some testing and may have found what's wrong. I made a scene with several cubes, a volume and a strong light source, and also set a large sample size.\nResults:\n497.29 driver - 4 minutes 12 seconds (806 MB of video memory used)\n527.56 driver - 3 minutes 45 seconds (806 MB of video memory used)\nAt the same time, the viewport works quickly and responsively in the cycles render mode. Just like I planned\nI also ran a test with a complex scene and then everything got much worse:\n497.29 driver - 22 minutes 51 seconds (8775 MB VRAM used)\n527.56 driver - 35 minutes 37 seconds (8775 MB of video memory used)\nThe viewport is quite buggy and poorly responsive in both versions of the drivers (but this is logical since the scene is complex). In the viewport, the view mode in cycles on the 497.29 driver works as expected - it gradually develops the picture. On the 527.56 driver, cycles almost doesn't work in the cycles view mode (more precisely, it works, but it's even slower than my four-core processor).\nIn render mode 527.56 the driver is unstable. I had to wait 11 minutes for the first sample to load. And I'm still lucky. Sometimes the render time can be 44 hours for a single frame (oB4BJ5L.png)\n\nAs a result, we can come to the conclusion that with the new drivers, the blender is unstable when the video memory is almost completely loaded.\n\nI recorded the workflow of all tests on video in an accelerated version: 1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link . I advise you to download the video to your computer so that it does not compress when viewed through Google Drive ...\n\n1. Make a complex scene with lots of textures, lots of geometry and use the latest Nvidia drivers.\n2. Engage in scene editing often switching between working scenes\n3. Start rendering the scene at a high resolution and a lot of sampling\nI made a screen recording of the editing process: 1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link\n.blend: 1MY37OWlYleiusnEbxDuTwIx63F_eQIVK?usp=share_link\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", "Viewport Slowdown on 11th gen Intel Xe graphics\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\n| Graphics card: | Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 27.20.100.8935 | @tommyoliversays, @CuriousHobbyist (#93114), @Jonathan-Monsonego (#93039), @Pyer (#93505), @Charlie3521 (#93257), @ImaRealBoi (#87147)\n| -- | -- | -- |\n| | Quadro RTX 3000 with Max-Q - 4.5.0 NVIDIA 472.39 | @Stay_Here\n\nBroken: version: 2.92.0, 2.93\nWorked: 2.83 LTS (better but not perfect, just takes longer for it to start occuring, maybe an hour as opposed to around 20 minutes in 2.92).\n\nWorking on a model slowly brings viewport down to single digit framerates.\nIt seems to be a twofold issue. Whenever you hit spacebar to playback animation, Blender starts using up more RAM. After working for about 15 minutes, 2.92 RAM usage increased from ~500MB at launch to over 3GB in the same scene while idle. Rotating the viewport also spikes GPU usage to over 50%, which immediately drops back to single percent digits when idling.\n|  |  | \n| -- | -- | -- |\n| Memory at launch | 15 mins after | Spikes rotating viewport\n\n- moving verts around over time or\n- hit spacebar to playback animation or\n> In #93114#1254781, @Stay_Here wrote:\n> The most likely scenario in my case is when two or more Blender(s) are launched. For example, open Blender.exe twice, then load two different characters in the two Blender windows. Let's say, character A and character B are loaded in the Blender window A and window B, respectively. After that, I spend some time on sculpting character A, and use the character B as a reference character. In this setup, Blender window B is seldom touched or manipulated, since it is just for reference. \n> \n> After about 10 mins to 2 hours on sculpting character A on the window A and open YouTube to listen some music, I jump to the Blender window B to navigate and change the view to the reference character B. At this moment, the lag in the solid viewport in the window B can be quite likely to happen. However, at the same moment, navigating in the window A is still smooth and unaffected.\n\n\n[imp2.blend](imp2.blend)\n\n", "Some GUI Pannel takes forever to load\nHello,\nOperating system: windows 10\nGraphics card: NVDIA RTX a2000 with latest driver\nIntel I7 with desactivated integrated gpu\n\nBroken: 3.5, 3.6\n\nBlender starting up is very slow\nmore importantly GUI is unresponding ( often around 25 sec ) when accessing to:\n>\"shading\" panel\n>Window explorer ( loading an image texture for example)\n>Material preview mode\n>Display render preview\n>Accessing preferences\n>Rendering window\n\nNo problem for modeling rendering etc. loading theses GUI parts seems to be the only lag itself.\n\nWhat i've tried:\n>Disable all addons\n>Factory user prefs\n>Deleted user pref app data folder\n>Updating driver to the latest version\n\ntried on 3.5. > Still the same\n\nThe lag is present even with the most basic file available\nIt has always been like so since i installed my pc.\n\nThanks\n\n", "Regression: Pixels in render result appear blurry during rendering\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.4.1\n\nPixels in the render result can appear to be stretched into 1x2, 2x1 or 2x2 pixels depending on window resolution. \nThis is only the case while the render is still going; when it finishes the pixels appear as they should.\n\n\n1. Start rendering any scene, most noticeable in scenes with easily visible noise like this one: \n[noisebox.blend](noisebox.blend)\n2. Resize the window while the render is running\n3. Observe pixels changing size\n[blender_2023-02-07_04-11-02.mp4](blender_2023-02-07_04-11-02.mp4)\n", "Grease Pencil: Visual glitches in viewport when using guides \nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.82a\n\n\nWhen using one of the guides that enable the drawing of straight lines, visual glitches in the viewport appear.\n\n\n - Open Blender with the 2D Animation template\n - Enable Guides\n - Use \"Parallel\" guides\n - Start drawing a horizontal line -> move the cursor perpendicular to the tip of the stroke (up or down; not too fast)\n\n\n\n\n\n", "VDB sequences are rendered blocky here and there ( issues with Volume Displacement Modifier )\nOperating system: Windows 10 \nGraphics card: RTX 2070 CUDA\n\nBroken: blender-3.0.0-alpha+master.ef5a362a5b24-windows.amd64-release.zip\n\n\nBlender renders these blocky frames here and there during the actual render. The VDBs seem to be fine, the same botched render frames look fine in the viewport render. These anomolies are happening only during the actual render. See the attached image (middle right image) for what is happening please.\n\nThe same sequence renders without any issues in Houdini.\n\n(Cycles)\n\n\n\n\nHere is an actual movie render (with Eevee) that shows how horrible this issue is.\n[borkedframes_0001-0200.mp4](borkedframes_0001-0200.mp4)\n\n\n[#88966.blend](T88966.blend)\n[steam.4.0001.vdb](steam.4.0001.vdb)\n\n- Open .blend file\n- Render sequence with CUDA\n\nIssue should appear within 30 frames\n", "New 3D Viewports do not show X-Ray shading correctly\nOperating system:win11\nGraphics card:3070\n\nBroken:3.41‘s bug (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nNew 3d views after the first one cant show X-Ray mode normally 视图显示“材质预览”下的编辑模式，透视打开，最初的第一个3d窗口可以显示背面的点，之后的3d窗口无法显示背面的点\n\n* Start with the default .blend file\n* Change the Timeline editor into a new 3D Viewport\n* Go into Edit mode for the Cube object\n* Turn on X-Ray mode in both 3D Viewports\n* Change the Viewport shading mode as follows\n * Solid mode works correctly in both editors\n * Material Preview only works for the original editor\n * Rendered only works for the original editor\n\n(see solid.png, preview.png, and rendered.png below)\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)", "(Linux; AMD Radeon GPU) Rendering a complex scene with eevee crashes desktop environment / causes rendering and viewport artifacts\n```\nOperating system: EndeavourOS Linux / Fedora Linux (Same issue on both distros)\nGPU: AMD Radeon RX 6800 XT (16 GB VRAM)\nCPU: AMD Ryzen 5 3600\n```\n\n```\nrenderer:\t'AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64)'\nvendor:\t\t'AMD'\nversion:\t'4.6 (Core Profile) Mesa 22.3.7'\ndevice type:\t'AMD'\nbackend type:\t'OPENGL'\n```\n\nBroken: 3.4.1, 55485cb379f7, blender-v3.4-release; 3.5.0 Release Candidate, d5d8246441a5, blender-v3.5-release (both version exhibit the issue)\n\nWhen rendering complex scenes in Eevee (Scenes with many different objects), one of the following occurs:\n\n 1. On **X11**: Computer freezes for about 5 seconds before all monitors cut to black. After about 5 seconds on a black screen, the login screen appears and I can log in as normal, as if I logged out. All of the applications have closed.\n 2. On **Wayland**: Render finishes rendering, but many of the objects appear broken; they are semi transparent or appear as if they were using the holdout shader. Returning to the viewport causes all objects with transparency to flicker randomly and appear distorted. Occasionally, the desktop of the computer itself will become broken and artifacted, only logging out or restarting fixes it. This usually isn't possible, however, as after a short while everything all displays cut to a black screen. Unlike X11, however, the only way to recover from this is to restart the PC by holding down the power button.\n\nThis issue **only occurs on linux and does not occur on my Windows 10 partition**, even with the exact same settings and scene. It also only occurs when actually trying to render the scene. In the viewport everything works just fine, even on rendered view where everything looks the same as it should in the render.\n\nThis issue seems to occur regardless of the GPU Usage; even when I limit the GPU clock and power draw significantly it still happens.\n\nThe attached .blend file is an example of a simple scene which triggers the bug. It seems to occur no matter what the render settings are set to.\n\n", "2.83 3D viewport performance\nOperating system: Ubuntu 20.04 LTS\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2), version: 4.5 (Core Profile) Mesa 20.0.4\n[system-info.txt](system-info.txt)\n\nBroken: 2.83\nWorking: 2.82\n\nProblem seen in Workbench, Wireframe and Eevee.\nViewport performance it's really bad, I'm moving around just the initial cube scene at 15-20 Fps, older Blender versions movement is perfectly smooth.\nNo matter the scene/blend file, 2.83 offers worse viewport movement performance compared to older versions,\nIt's important to mention that only the viewport movement is being affected by this performance drop, everything else including rendering works smooth as butter just like older versions or even better. Splitting up the scene in windows kinda fixes this problem." ]

[ "rendering bug\nwin7 gf 750ti\n\nBroken: (example: 2.78.4 96868a3)\nWorked: (optional)\n\nweird artefacts on faces while rendering in viewport\n1. open a file [bug_1.blend](bug_1.blend)\n2. shift+z to change to viewport shading rendered\n3. move (G and shift for slower movement) the object on Y axis , artefacts disappear. they are only on Y axis and in some range of grabing ", "Artefacts appear when ambient occlusion (AO) is enabled\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.63\n\nBroken: version: 3.1.0 Alpha\nWorked: N/A\n\nI use AO for all my textures. When I render out models in Cycles with those AO textures, sometimes I see these artefacts on the model caused by the AO (I know they are caused by the AO because they do not appear when I turn it off, and the colour of the artefacts depends on the colour of the AO). The artefacts do not follow any edges or vertices, and they seem to decrease (though not disappear) when more topology is added (for example, when the model is bevelled or a subsurf modifier is used). Strangely, the artefacts tend to change or even completely disappear when their position is changed in the model (so there isn't any other mesh occluding the model, nor is it a topology issue). The issue may or may not persist when the model is taken to a different file.\n\n1. Open the attached .blend file.\n2. Switch to 'rendered' view mode in Cycles.\n\n[BGRep.blend](BGRep.blend)\n\n\n\n\n\n\n\n\n\n" ]

[ "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\n", "Cursor frozen when switching to walk/fly navigation while moving the mouse\nOperating system: Windows 10\n\nBroken: 2.82 (sub 3)\n\nSwitching to walk/fly navigation through the shortcut while moving the mouse, causes the cursor to become stuck. The cursor remains stuck until the mouse isn't moved anymore for a short moment.\n\n\n - Move the mouse around in 3D view.\n - While moving the mouse press the shortcut to enable walk/fly navigation.\n - Continue to move the mouse and observe the cursor not following the mouse movement.\n - Stop moving the mouse.\n - Move the mouse again and the cursor should follow as expected.\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) ", "\"No Render\" volume of space with motion blur and GPU render\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.27\n\nBroken: version: 3.4.1\nWorked: N/A\n\nThere appears to be a volume of virtual space where objects do not render.\n\nLoad attached file. Set render frame to 110 and render the scene. Note the progress it makes as the large cube slowly vanishes with each render pass, while the smaller thin cube only partially renders. Set the frame to 50 and it renders fine. The problem starts with frame 106 and gets progressively worse for the large cube, while it seems to somewhat recover for the thin cube in later frames.\n\nThe problem does not repro with CPU rendering, and did not repro with my older graphics card way back when I first made this scene (GeForce 1080Ti). It repros with GPU rendering on both 3.4.1 and 3.1.0. It does not repro with motion blur disabled (hence the viewport render is also fine).\n[GPU Motion Blur Bug.blend](GPU_Motion_Blur_Bug.blend)\n", "Unwanted camera movement\nOperating system:\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.6.1, 2023, non of the versions I have tried has worked \n\n\nI have enabled the feauture to \"fly around\" by pressing shift + f. When you press those buttons you will be able to fly using W D A S keys. Sometimes when I use this feauture it works fine but after a while it starts bugging. For example I use this tool for zooming in on objects really close and when this bug comes in this happens: I go really near the object and everything looks fine but when i left click like your supposed to do the camera moves places. It usally starts just moving a little, but the closer you get to an object the more it moves. Like it snaps out of place.\n\n\n- click shift + F \n- move near an object (cube) \n- left click to settle the camera\n- and see how it moves\n\n", "weird viewport visual glitch\nOperating system: Windows 11 64 bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti Gaming X Trio\n\nBroken: version: 3.3.1\nWorked: cant bother sorry\n\nits like the position of the viewport has an offset relative to the orientation of the camera, and the viewport has a set size and cant change.\n\nfirst go to the layout workspace and have an animation playing (must have an animation playing for the bug to happen), then create a new viewport by sliding it like im doing in the video. then change the viewport into rendering mode like im doing in the video and when you resize the viewport, it has a set size and cant be changed and the position of all parts have an offset according to the position and orientation of the camera.\n\n", "Node Group Texture slot problem\nOperating system: Windows 10\nGraphics card: gtx1060\n\nBroken: 2.9\nWorked: N/A\n\nIn the Texture Paint mode, when all textures are inside a node group, if you change brush radius it jumps to the top texture slot every time.\n\n- Open attached file\n- In the property editor, select `test` texure slot\n- Change brush radius.\nThe top texture slot (`test`) was selected automatically\n[Node Group Texture Slot Problem.blend](Node_Group_Texture_Slot_Problem.blend)", "Hair Dynamics Strange Behaviour\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0\n\nI have not seen hair behave this way before. For this example file, I have simply used the default hair dynamics settings. I have a bake in the file attached, and you can try bake yourself to replicate the issue. The hair will fly all over the place, it is not colliding with anything and I cannot figure out what is causing the issue. It was recommended by a developer that I post the issue here for others to have a look, many thanks.\n[HairProb.blend](HairProb.blend)\n\n", "Library Override Bug\nOperating system: Windows 10\nGraphics card: MSI 3060 Nvidea RTX\n\n2.6.1 LTS\n\nLibrary Override is bugged in this versión, rigs, mesh and some times materials too, i make library override in this version and the \"Alt+D\" objects or rigs was working well while the file is open but at the momment when i save and close the file and re-open the file most of the objects are broken or was deleted\n\n", "Horizontal mouse wheel support for MS-Windows\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nLogitech MX Master 3 horizontal scrollwheel button works in mac os x, but not in windows 10 although both have the same settings in Preferences in Blender and Logitech Options App.\n\n\nSTEPS TO REPRODUCE ISSUE:\n\n1. Rez object, select it and orbit around it in Mac OS High Sierra and Blender 2.81 using MX Master 3.\n2. Do the same, but in Windows 10.\n\nBased on the default startup:\nA. Performance in Mac OS is the expected: when using the horizontal scrollwheel button (thumb button mouse) orbits. Works in a similar way than when Orbit with the Magic Mouse.\n\nB. In Windows 10 the thumb button doesn't work, even when the settings are the same in both computers for Blender and the mouse. \n\nWhy this happens and how can I get to make the thumb button to work in Blender for Windows?\n\n\n\n\n", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "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", "Extremely frequent crashing when using the compositor. Especially when using the glare node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I believe it was far more stable before the realtime compositor implementation. (Blender 3.3-ish)\n\nBlender crashes extremely frequently when using the compositor on my system, especially when the glare node is being used at all. Does not seem related to vram or system specs, and looking through logs has not come up with any errors - it just closes.\n\nAdjust compositor glare node values with the viewer enabled. It seems to crash within a minute of doing so, usually sooner.\n\n", "Metal Backend causes UV editing to glitch out, crash Blender\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.5.1, 3.6.3, 4.0 alpha\n\nTrying to do UV editing with the Metal backend causes unexpected UI behavior. Islands will glitch out, disappear, randomly stretch and contort, or Blender will crash entirely. It makes Metal useless for work and requires a switch to OpenGL to have expected performance. This happens on my M1 Air, M1 Pro MacBook Pro, and M1 Max Mac Studio. They all had to be switched back to OpenGL.\n\n<video src=\"attachment\" title=\"error.mov\" controls></video>\n<video src=\"attachment\" title=\"Screen Recording 2023-09-09 at 5.50.49 PM.mov\" controls></video>\n\n- Open the included Blender file with Metal backend\n- Make sure the 3D viewport has either Material Preview or Rendered View enabled.\n- Start UV editing on the `Azumi` object (go to Object Mode > Select the Azumi object > go to UV Editing Workspace)\n- Zoom, pan, scale, rotate...\n\nIt'll happen eventually.\n\nEDIT: This issue seems to stem from having multiple UV Maps on the model somehow. If the additional UV Maps are removed, the issue stops occurring.\n\nEDIT 2: Further digging seems to show that it specifically has to do with the texture atlas expression swapping using the UV Map and Mapping Nodes in the \"Colors.001\" material. Clearing the field in the UV Map node also immediately resolves the issue.\n\nI've attached two screen recordings of some of the behavior, as well as the error log when Blender crashed, and the file I'm working with.\n\nEDIT 3: Uploaded a simple test file with just a cube using the same material setup as my character file. It exhibits the exact same behavior.", "UV: Copy/Paste UVs sometimes merges vertices\nOperating system: Windows 10\nGraphics card:\n\nBroken: 3.5.1, 3.6.0 (2023-05-24), 4.0.0 (2023-05-24)\n\n\nCopy/Paste UVs sometimes merges vertices.\n\nTest file: [UV - Copy Paste.blend](attachment)\n\n\n\n" ]

[ "Middle Click navigation in 2.8 UV Editor randomly stops and starts working\nOperating system: Windows 10\nGraphics card: GTX 960\n\nBroken: 2.8, January 14th release\n\nWorked: 2.79\n\nFor no apparent reason, in the UV editor, using the scroll wheel to zoom in and out, or pressing the middle mouse (also the scroll wheel) to pan around, will suddenly stop working and just as randomly, start working again.\n\nJust open the UV editor and start zooming and panning around with the middle mouse button and scroll wheel. If it helps, I'm using a Logitech M705 wireless.", "Region below transparent sidebar panels captures mouse input\nOperating system: Windows 10 x64 latest update\nGraphics card: gtx 1060 3gb\n\nBroken:\n2018-12-22-9:56 hash 4c5e76025d83\n\nWhen navigating the UV from the UV editor, it doesnt respond consistently whenever I roll the scrollwheel. The icon and the sugestions at the border of the space indicates that my input is being captured, but the zoom level and pan is not captured. Also tried with the touchpad just in case the mause was the trouble, but no luck.", "Viewport Navigation Canceled Out Due to Menu Free Space\nOperating system: Windows 10 1809 Build 17763.379\nGraphics card: GTX 1060 3GB\n\nBroken: 2.80 Date: 2019-04-06 12:26 Hash: cc73d59ad580\n\nError or not, I've found myself trying to navigate, rotate around, in the viewport to suddenly think either the version of Blender I was using was borked or my mouse was. Turns out, the free clear space of the UI is effecting the navigation of rotating around, acting as if the menu is still there.\n\nMiddle mouse button in the freespace in any scene where a toolbar would be at.\n[bug_blender.mp4](bug_blender.mp4)\n[f7db6537eeb74fdade1f36697b5653c1.mp4](f7db6537eeb74fdade1f36697b5653c1.mp4)" ]

[ "Custom Properties within PropertyGroups cannot be animated when attached to a PoseBone\nUbuntu Linux 14.04 (64-bit)\nNVIDIA GTX 960 (NVIDIA Driver Version 367.35)\n\nBroken: 2.77a abf6f08\nWorked: N/A\n\nI've found that custom properties stored within PropertyGroups and/or CollectionPropertys cannot actually be animated if they are associated with a PoseBone (Error returned when inserting keyframe is \"Failed to resolve path to property, try manually specifying this using a Keying Set instead\"). (If the exact same custom properties are associated with an Object, they can be animated by inserting keyframes normally.)\n\nIt's possible that I'm mistaken and it is possible to manually specify the property within a CollectionProperty/PropertyGroup using a Keying Set in a more straightforward manner (or at all), but to manually add a Keying Set for every potential instance of a property within a CollectionProperty for every PoseBone that uses the custom properties is an unrealistic for any use case involving a CollectionProperty (and honestly I'm doubtful whether this is even possible, I was unable to successfully create a Keying Set for keyframing a property within a CollectionProperty/PropertyGroup, getting error 'Keying set failed to insert any key frames', although I can't deny the possibility I got the path to the property wrong somehow).\n\n1. Open the provided .blend file\n2. Install/Enable the provided add-on\n3. Select a bone in the armature in pose mode.\n4. Go to the Bone panel. At the bottom, you'll see a new section called 'Custom Properties Bug'.\n5. Try to insert a keyframe for 'Animatable PropGroup Property'. It will fail.\n6. Click the 'Add Collection Item' button to add an item to a CollectionProperty.\n7. Try to insert a keyframe for 'Animatable Collection Property' (a property within the Item you just added to a collection associated with the PoseBone). It will fail.\n\n[bug_report.zip](bug_report.zip)", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\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", "Animation: Replacing bone layers + groups with bone collections\nThis design describes the replacement of armature _bone layers_ & _bone groups_ with a new _bone collections_ system.\n\nImplementation is in #109976 and #112271.\n\n## Goals\n\n- Named collections, instead of numbered layers, should give a better indication as to what the collection contains / is for.\n- Increased flexibility in number of collections.\n- More similarity to the scene object collections, including features like 'not selectable' which can increase clarity of how to use a rig by animators.\n- Compatibility with library overrides, so that new shot-specific bone collections can be added.\n- Unification of numbered bone layers (for organisation) and named bone groups (for coloring).\n\n## Properties of the System\n\n- Armatures have one or more bone collections.\n - If there is only one collection it cannot be removed.\n- Every bone is in zero or more bone collections.\n- Bone collections **cannot be nested**. At least not for 4.0, can be added later.\n- Bone collections must have a **unique name** within the armature.\n- Library Overrides:\n - New bone collections can be added.\n - Existing ones cannot be reordered / removed.\n- Bone collections have the following properties:\n - Name\n - Selectable: 'set' wins over 'cleared'\n - Visible: 'set' wins over 'cleared'\n - `IDProperties` (aka Custom Properties) for use by add-ons.\n- Bones will get individual color properties.\n - The color system of bone groups will be used, which allows selection of 'default', 20 theme-defined colors, and a custom RGB value.\n - Bones have a color defined as part of the armature data. Here 'default' is the default grey color.\n - Pose Bones have a color defined as part of the object/pose data. Here 'default' means 'uncolored', and will thus show the edit bone color.\n\n## Operations\n\nThese operations can be performed on/with bone collections:\n\n- (De)select one or more collections themselves\n- (De)select all bones in active collection\n- (De)select all bones in collections containing the currently selected bones\n- Create a new collection\n- Delete a collection. Bones in the collection that are now 'orphaned' are assigned to the 'default' collection.\n- Move collection up/down in the list.\n- Move selected bone(s) to a collection.\n- Select Bones of Same Color.\n\n## User Interface\n\nFor Blender 4.0 the UI is kept intentionally simple. I'm thinking of reusing the Bone Groups interface, with the addition of a few per-collection icons (visible, selectable, color palette) as well as an indicator of which collection(s) contain the selected bone(s).\n\n## Conversion from Old to New\n\n- Layers converted to `Layer {NUM}` collections.\n- Bone groups converted to `{name}` collections.\n- Selection Sets converted to `SelSet {name}` collections.\n- Maybe even automatically merge these when they contain the same bones?\n\n## Uses of the Current System\n\n### Bone Layers\n\n- Visibility\n- Logical grouping\n\n### Bone Groups\n\n- Coloring of logical groups\n- Set by rigger\n\n### Edit Mode vs. Pose Mode\n\nThis describes Blender's **current** behavior:\n\n| Property / Action | Edit | Pose |\n|---------------------------------------|------|------|\n| Name Bone | ✅ | ✅ |\n| Set Bone Layers | ✅ | ✅ |\n| See Bone in Group Color | ❌ ¹⁾ | ✅ |\n| Create / Assign Bone Group | ❌ ¹⁾ | ✅ |\n| Select Bones in Group | ❌ ¹⁾ | ✅ |\n| Set Bone Group Color | ✅ | ✅ |\n| Set Armature Viewport Display options | ✅ | ✅ |\n| Set Bone Viewport Display options | ❌ ²⁾ | ✅ |\n\n¹⁾ The new system should allow these in Edit mode too.\n²⁾ Bones can only be hidden, which is separated between edit mode & pose mode.\n\n## Future Work\n\nThese are ideas for future improvements / extensions:\n\n- Nestable bone collections.\n- Integration with the Outliner.\n- Per-collection option whether bones are deforming or not (rather than setting that per bone)\n- Per-collection viewport display mode (octo, line, bbone, etc)\n- Possibly unification of Selection Sets as well.\n\n## Code Location\n\nThis work will kickstart a new module in `source/blender/animrig`. This will become the place for new animation/rigging related code. The intention is that also a subset of the already-existing animation-related code from both `blenkernel` and `editors` is going to move there, to help clean up the API and make it more consistent.\n\n-------------------------\n\n## Ongoing Work\n\n**Targets for 4.0-bcon1: tracked in #109976**\n\n**Targets that could be pushed back to 4.0-bcon2:**\n\n- [x] Add ID Properties support to bone collections, including a UI.\n- [x] Removal of bone group RNA access & UI\n- [x] Ensure that library overrides can add new bone collections & assign bones to them (#112271)\n- [x] Removal of bone groups from the UI, including the Ctrl+G menu\n- [x] Add bone collections to the outliner (replacing the current list of bone groups)\n- [x] Operators to move/add selected bones to a collection:\n - [x] move to collection (similar to 'm' for objects & collections, from viewport)\n - [x] add to collection (similar to 'shift+m' for objects & collections, from viewport)\n- [x] Select Similar operator (by collection, by color) / Shift+G menu\n- [ ] Fixing the Collada I/O, as that also handles bone layers.\n- [x] Make bone collections on linked-but-not-overridden armatures usable. The object itself may be overridden, so changing the active bone collection should work (even when it cannot be saved), and then 'Select Bones' and 'Deselect Bones' operators should work.\n\n**Potential push back to later:**\n\n- [ ] Add selectability toggles to bone collections (only for pose mode)\n- [ ] Add armature-global override to selectability, so that a rigger can still opt to select all the bones, then lock them down for animators.\n- [ ] Managing bone assignments to collections from the outliner.\n", "isolate collection doesn't work on nested collections.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nisolate collection doesn't work on nested collections.\n\n\nSee attached video. I've set the alt key to trigger collection isolation by the way.\n\n", "Render Animation in Video Editor doesn't warn that source video files are missing\nOperating system: Fedora 35\nGraphics card:\n\n\nBroken: 2.90.1\n\n\nThis is more of a feature request / usability improvement than a bug.\n\nI spent quite a few hours trying to figure out why a segment of a video from a Video Editing project was rendered all black. The segment looked fine in the video editor. It turns out that I had created a proxy for the video, then I accidentally deleted the non-proxy version of the video.\n\nIt would have been very helpful for Blender to open a dialog saying something like, \"Source video file foo.mp4 missing.\" It would have saved me literally hours.\n\n\n1. Create a proxy for a video in a Video Editing project.\n2. Delete the non-proxy version of the video.\n3. Render Animation\n", "KeyingScreen Compositor node emits \"black holes\" \nThe attacged folder shows a bug in the KeyingScreen compositor node.\n\nIn the Screenshot GreenPlateBug-Screenshot.png it can be seen in the above compositor window that some areas are filled with black\ninstead of grey / green.\n\nThat appeared after creating the \"last\" track marker (the selected / larger track marker in the below window).\n\nIf you remove that larger marker, the bug disappears.\n\nTo reproduce, open the attached blend file, close render window, disconnect / reconnect the viewer node to the keying screen node to\nsee in backdrop display.\n\nThe bug appeared in a different usage of the KeyingScreen node with much fewer track markers, but since the circumstances of\nthe bug to appear is unclear, i had to add a lot marker here.\n\n\nBlender version 2.80 (snap Ubuntu version).\nOS: Ubuntu 19.04 x86\nGraphics Card: Prime Laptop (NVidia / Intel combination) Dell Inspirion 4500 Laptop in Intel mode\n", "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.", "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", "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", "VSE View menu - missing hotkeys for sidebar and toolbar in Preview mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 3.0.0 Alpha\n\n\"Caused\" by 6aef124e7d\n\nThe VSE is missing the default hotkeys to open the sidebar and toolbar in Preview mode. T and N\n\nWhen you add them by yourself, then these hotkeys gets added in the Window section. Which can lead to override conflicts.\n\n\n- Open Blender\n- Switch to VSE\n- Watch the View menu in the upper Preview window\n\n\n\n\n\n\n\n\n", "PointerProperty in UI slows down extremely\nWindows 10\n\nBlender 2.83.17\n\nCreating a python script that utilizes bpy.props.PointerProperty suddenly slows down when rendered in the UI. This happens proportional to the amount of elements in a custom CollectionProperty in bpy.types.scene.\n\n- Run the script attached\n- You should see a two categories in your 3d viewport.\n- The category UI called \"INT PROPERTY\" has normal behavior and speed.\n- the category UI called \"POINTER PROPERTY\" is extremely slow.\n (change the amount of items in line 161 of the script to slow down even more.)\n\nThis is a simplified version of the problem that occours for a huge addon developed in my company. We have hundreds of items in the bpy.context.scene.CollectionProperty as well as tens of UIs with tens of PointerPropertys. We are running into huge performance problems.\n\n[bug_pointer_property.py](bug_pointer_property.py)", "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", "Disabling Collections in the Outliner filters overlaps the Mode Column icons with the expansion arrows\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIf you disable the \"Collections\" filter in the Outliner, the space of the Mode Column disappears even if the \"Show Mode Column\" filter is enabled, and the icons of the Edit Mode Column overlap with the object expansion arrows.\n\nAdd any mesh object, disable the Collections filter in the Outliner, enter edit mode.\n", "Join Palettes\nActually is impossible to Join several Palettes and a operator to do that is needed." ]

[ "Cant animate object outliner properties\nOperating system: Linux\nGraphics card:AMD 580rx\n\nBroken: 2.80 from 9th Feb build\nWorked: 2.79\n\nIn blender 2.80 the properties of collections & objects cannot be animated from the outliner.\n\nLoad the default blender startup scene\nselect the cube or collection\ntry to set a keyframe on the cube for any of the properties in the outliner:\n- hide object in viewport (the eye icon)\n- disable object selection in viewport (the cursor icon)\n- disable object in the viewport (the monitor icon)\n- disable object in render (the camera icon)\n\nSome will set frames, but they dont work (looks like no value is assigned?). Others will report the error 'no active keying set'.\nThis worked fine in 2.79 without any special keying sets etc...", "Keyframeing outliner \"view in...\" crashing blender\nOperating system: Windows 10\nGraphics card: GTX 770\n\nBroken:\na1ae04d15a9f\n\n\nWhen I'm trying to keyframe \"visible in render\" and \"visible in viewport\" I can't see my keyframes, and it's all not working.\nSometimes crashing blender.\n\nI'm trying to keyframes spaw_mały and spaw_mały_2 in a file that I upload.\n\n[BTH_3.blend](BTH_3.blend)", "Unable to add Keyframes to object visibility (eye in the outliner)\nOperating system: Win 10 64bit\nGraphics card: Geforce 940M\n\nBroken:\n2.80, 1fc75dbbceea, blender2.8, 2018-12-19\n\nwhen I press 'i' with the cursor above the eye icon in the outliner, I get an error message (no active keying set)\nVisibility is not available when creating a keying set though\n\nanimating the viewport visibility gives no error, but doesn't seem to work either", "Fail to animate Disable Obejct from Preview or Render from Collection list\nOperating system: Ubuntu Studio 18.04 64 bits\nGraphics card: GeForce GTX 970\n\nBroken: 2.80, 25772c9e1d2d, blender2.8, 2019-01-26\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\nFail to animate Disable Obejct from Preview or Render from Collection list\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nWhen to an object (a cube from default startup) you insert a key (i) in a frame from the Collection list in the \"Disable Object\" icon of Preview or/and Render as visible, and a later frame you disable it to hide and re-add a key from the list of Collection in the\"Disable Object\" icon of Preview or/and Render, this does not work, although the keys are visible in the Dope Sheet. It remains hidden or visible according to what we activate in the list, and not according to the action keys." ]

[ "Graph Editor: Curve drawing improvements\nProblem: keyframe dots can be somewhat hard to see, especially behind the current frame marker line.\n\n\n\n**Proposal**:\n- Change the default theme to draw the keyframe dots larger. The current theme draws at 6px, for modern displays this should probably be increased to 7-9px. It's probably better to defer a concrete choice for this until #68982 (Graph Editor: UI Scale effect on Curves drawing) is done.\n- Draw keyframe dots of selected keyframes on top of current frame line. Keep drawing unselected keyframe dots behind the line.\n", "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", "NLA: Action Track Hold Forward Inconsistency\nBug Report: #66946 (NLA strip unexpectedly auto-switching from Hold to Hold Forward)\n\n**Problem:** For the Action Track (non pushed action), extrapolation `None` and `Hold` is respected but `Hold_Forward` is not. It's a source of confusion. \n\n**Solution:** [Originally proposed by angavrilov]]. We treat extrapolation `Hold_Forward` as bounded on the left and infinite on the right.*FModifiers note:*It's important to note that the Action Track does not evaluate the same as normal strips which is [[https:*developer.blender.org/T66946#723602 |intentional](https:*developer.blender.org/T66946#724251). FModifiers will affect the track's boundaries so keyframes don't necessarily define the Action Track's evaluation bounds. So adding a default cyclic modifier to channels effectively makes the Action Track's evaluation bounds infinite. Even extrapolation `None` in this case appears to not work properly. This behavior is still intentional even though it appears broken. The user-side solution is to restrict the modifier's frame range. ", "Rigid body : the animation of the angle constraint parameters does not work with an animated object\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: 2.92\nWorked: don't know \n\n\nRigid body : A rigid body \"animated\" object + a another rigid body object connected with hinge rigid constraint. The animation of the angle constraint parameters does not work with an animated object. I have bugs sometimes also with other parameters like breakable . (see the blend)\n\n[rigidconstraint.blend](rigidconstraint.blend)\n\n", "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", "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", "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)", "Render errors [glitchy frames] with baked cloth [from the UI, commandline as well as rendering with 'Lock Interface' is OK]\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.91.0 Alpha, branch: master, commit date: 2020-10-07 21:43, hash: d8fcd8a316\n\n\nI have a simple scene I press render animation and some of the frames come out messed up. \nIt looks like some sort of motion blur bug. Looks similar to this bug #74457 (Mantaflow foam particles as objects break motion blur)\nI have rendered this on two different PC's, the problem is the same.\nWith baked cloth physics.\n\n\n\n[Jelly Jery (buggy render) - Cycles 256 samples Intel denoised.mov](Jelly_Jery__buggy_render__-_Cycles_256_samples_Intel_denoised.mov)\n\n\n[Jelly Jery.blend](Jelly_Jery.blend)\n\n\n\n\n | cycles | glitchy |\n | -- | -- |\n | cycles command line render | OK |\n | cycles with Lock Interface | OK |\n | eevee | glitchy |\n | eevee without motion blur | glitchy |", "Particle Instance from interpolated children works unexpected\nOperating system: win10 74bit\n\nBroken: 2.8, 2.79b\n\n\"Children\" option works good only with \"Along path\". Otherwise it just duplicates extra geometry where parent particles are located. \n\nOpen file and enable \"Children\" option, see how poly count is changed without visual appearance. Then check both \"Children\" and \"Along Path\" to see the difference.\n[Particle_instance_child.blend](Particle_instance_child.blend)", "Exact Boolean with Incorrect Result - multiprecision/float round trips not exact\nOperating system: Windows 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.91.0 Beta dca36a8ec922\n\nAnother case, where the exact boolean does not work as expected. (Sorry @howardt, I had to break it. I have to admit, that I have not run into this problem in a real scene.)\nAgain, this manifests after applying the same difference operation several times.\n\n[boolean_rotated_box3.blend](boolean_rotated_box3.blend)\nLook at the scene.\nThe first run of the modifier works as expected, the second creates overlapping faces, the third removes most of the mesh.\nThis \"bug\" is very erratic, and if the transform of the objects is slightly changed, it does not occur.\n\nThis is what I see:\n\n\nThe expected behavior is that the second and third modifier do nothing.", "Diffuse Direct, Indirect Bake to Vertex Color Artefacts\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nWorked: This has never worked properly (At least in my experience)\n\nWhen baking Diffuse light to vertex color, black triangles and random dark spots appear in vertex color. This effect is more apparent with:\n- Area lights.\n- Emissive surfaces.\n- Lights with very high power.\n\n1. Create geometry and give each a byte_color vertex color channel.\n2. Place area lights in scene with high power.\n3. Bake diffuse direct and indirect to color attribute.\n\nSee .blend of my project attached. In the file i've already baked the emissive light to vertex color where you can see the artefacts. Switch to cycles live render view to see the correct output. I think the tiled texture may have something to do with it. I've added a tiled texture and packed it in the example.\n\n", "No error prompted when Cuda fails during GPU bake\nOperating system: Linux Debian 10 (buster) - kernel 4.19.0-19-amd64\nGraphics card: GeForce GTX 1060 Mobile\n\nBroken: 3.1.0\nWorked: -\n\nWhen you try to bake, having GPU set as compute device, and CUDA has an error, no error is shown.\nYou only notice the error when you try to render and get \"*Failed to create CUDA context (unknown error)*\"\n\nIt is useful to show an error, in the same way that, for example, \"Circular dependency for image...\" is shown during the bake.\n\nNote that this report is not about the error itself. It is about Blender not reporting any errors during baking, which causes user confusion.\n\nThank you,\nRiccardo", "Blender baking's margin overlap if multiple meshes are selected\nBasically just a duplicate of T51134 that Aaron Carlisle asked me to send as a new report.\n\n\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: AMD RAVEN (DRM 3.35.0, 5.4.0-58-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 2.90.1\nWorked: never with Cycles as far as I know.\n\nCycles overlap the region margin on other islands in the final result.\n\nCycles will bake an object/island, apply the margin, then proceed to do the same to the next one on top of the previous and they will overlap if the margin is bigger than the distance of the UVs, instead of applying to the finished bake and having the margins having an equal distance between islands, as Blender Internal used to do.\n\nJust press bake on the file. Or any multiple objects with a margin bigger than the UV islands.\n\nAs far as I know this has always been a problem with the Cycles baking implementation, besides some other issues of performance and usability. For instance if baked with multiple objects selected it is much, much slower than if I collapse them and merge, as I mentioned in the previous bug report.\n\nI understand it should be slower if they are separated, but I don't imagine it should be that much slower.\n\n\n\n", "Rigid body baked cache not invalidated\nOperating system: Windows 10 Pro 64-bit\nGraphics card: 4095MB NVIDIA GeForce GTX 1080 (NVIDIA)\n\nblender-2.80rc1-windows64\nWorked: (optional)\n\nSimple physics object is trapped in previous (deleted) animated properties.\n\nI have included a blend file which consist of just a cube with physics properties added.\nIt is supposed to fall but it moves to the origin and stays there.\nThe file is a working file from which everything has been deleted and a cube added.\nRun the animation and the cube will behave oddly.\nIf the cube is deleted and a different mesh added, say a sphere and moved and basic physics assigned. It will do the same.\nThis is likely to be a problem with my file from which everything has been deleted??\n[physics-problem.blend](physics-problem.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." ]

[ "Fcurve Problem after baking animation\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 528.49\n\nBroken: version: 3.5.0\nWorked: 2.79, 2.93, 3.4.1\n\nIn 3.5, after baking animation on bone with a damped track modifier to an empty, there are these extra overshot keys overlapping which can be seen in graph editor.\n[blender_RfczosDT71.mp4](https://projects.blender.orgattachment)\n\n- Open attached .blend file\n- Go to `Pose` > `Animation` > `Bake Action...`.\n- Enable `Visual Keying` and `Overwrite Current Action`\n- Press `OK`\n\n" ]