Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "Python console history gets rearranged when editing lines\nDebian unstable, GeForce GTX 980\n\nBroken: 2.76\n\nEditing lines in the Python console causes the console's history order to be manipulated in unintuitive ways. There is a certain logic to it, but that logic is different from just about every other shell in existence(*). Most importantly, it's different from Python's own interactive interpreter.\n\n(*) Based on a sample (n=4) consisting of bash, python3, cmd.exe and Opera's Javascript console\n\nBecause Python console contents are not saved, I think it's pointless to attach a .blend file.\n1. Open Python console in Blender\n2. Seed the history with the integers 1, 2 and 3 in this order\n3. Press up arrow two times to get back to 2\n4. Edit the value to 42 and press enter\n5. Press up arrow repeatedly and observe the history cycling order\nThe history order is now 42 -> 2 -> 1 -> 3 -> back to empty line.\nIf you press the down arrow twice between steps 4 and 5 (it cycles to 3 and then empty line), the history order becomes 3 -> 42 -> 2 -> 1 -> back to empty line. One press of the down arrow is not enough to trigger this.", "Custom Property list not updating in UI when editing properties from Python\nOperating system: Arch Linux\nGraphics card: GTX 970\n\nBroken: 2.80.60 (1c5860407068)\n\n\nSetting a custom property from Python does not update the corresponding entry under Custom Properties until mouse over forces a refresh.\n\n\nUsing default blend file.\n\n1. Add a Python Console panel somewhere\n2. Select the cube object\n3. Switch to the object properties tab, unfold the Custom Properties panel\n4. In the python console:\n```\no = C.active_object\no['value'] = 456\n```\n5. No new entry is shown in the Custom Properties panel\n6. Move the mouse to the Custom Properties panel -> new value prop appears\n7. The same thing happens when updating a property value, a mouse over is also needed to refresh the property list being displayed\n", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "Small improvements to 3D View Transform Manipulators\nAs per feedback from the Spring team, we would like to make some smaller improvements to the 3D View transform manipulators:\n\n\n - Increase the treshold for hiding the planar transform widgets, so that users don't accidentally drag the plane when they meant to drag the arrow\n - Increase arrow click threshold. Currently it's very unforgiving. Even if you click outside the arrow by one pixel, it doesn't register as an arrow click. Give it a few more pixels all the way around.\n - Separate the view-aligned rotation handle from the X, Y and Z rotation handles, so that users don't accidentally click the wrong one. We can make the view-aligned handle offset, like it was in 2.79\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)", "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", "blender::Set exhibits poor behavior if growth occurs after a round of removals\nI noticed `blender::Set` behaving poorly when an `add` operation requiring container growth comes after various `remove` operations. The net effect being that the container actually shrinks.\n\nI'm guessing that what I'm seeing below is not expected.\n\nThe sequence went something like the following:\n\n```\nmy_set.reserve(64);\n\n// a series of adds and removes\n\nmy_set.add(...); *start of poor behavior* Current state of the container\n* removed_slots_\t54\n* occupied_and_removed_slots_\t64\n* usable_slots_\t64\n\n*The value 11 is passed into \"realloc_and_reinsert\" indicating we need space for at least 11 items (i.e. size + 1)* The following values are calculated\n* total_slots\t32\n* usable_slots\t16\n\nshrinkage :(\n\n// At the end of \"realloc_and_reinsert\" the state of the container is\n* removed_slots_\t0\n* occupied_and_removed_slots_\t10\n* usable_slots_\t16\n\n\n\n```", "Improve unclear/broken File Browser User Preferences\nThe current File Browser settings are a mess and/or don't work.\n\n# Problems\n\n## 1) \"Show Hidden\" space parameter conflicts with user preference\nWhether to show hidden files is determined by a per-space flag, which is automatically saved (see `PARAMS_FLAGS_REMEMBERED`). But this flag also tries to get initialized with the userpref flag `USER_HIDE_DOT`.\nThe former **overrides** the latter, meaning the option does nothing when using temporary windows (which is factory default).\n\n## 2) Hidden Data-Blocks is confusing (and broken)\nFor those who don't know, this is a feature which hides dot-prefixed data-blocks not only from file browser, but also when searching in any ID selector.\nHowever, for the file browser, it's (confusingly) not tied to this user preference, but to the \"Show Hidden\" flag of the editor (the tooltip of which does not mention data-blocks at all)!\nAdditionally, this feature does not work in the file browser on Windows due to an `#ifndef WIN32`.\n\n## 3) Unnecessary \"Filter Files\" user preference\nSince the file browser already has the capability to remember its settings (see point 1), it seems reasonable to remove the explicit user preference and use `PARAMS_FLAGS_REMEMBERED`.\n\n## 4) \"Show Recent/System Locations\" are hard to discover\nOther editors (e.g. status bar sections, or Navigation Bar of the preferences editor) allow configuring directly in the editor, either via right click or in the editor's header.\nThese two file browser settings are only found in the preferences.\n\n---\n\n# Proposed Solutions\n\n## 1+2) Cut \"Show Hidden Files/Data-Blocks\" preference in half\n[D14650](D14650)\n- Rename the preference to \"Show Hidden Data-Blocks\" and put it into e.g. the Editing user preferences section.\n - Moving this setting makes it clear it doesn't only affect file browser, but also ID selectors.\n- Consequently, this user preference will no longer affect the \"Show Hidden\" flag of file browsers (this is already handled via `PARAMS_FLAGS_REMEMBERED` anyway).\n- For file browser, show dot-prefixed data-blocks if either this user preference is set *or* the file browser show hidden flag is set.\n - Update the tooltip of the file browser flag, to clarify that data-blocks can also be hidden.\n- Fix hidden data-blocks for file browser not working on Windows.\n\n## 3) Remember \"Filter Files\" automatically\n[D14650](D14650) (can be split into another commit, since it doesn't strictly belong to this patch)\n- Remove \"Filter Files\" user preference and corresponding userpref UI flag `USER_FILTERFILEEXTS`.\n- Instead remember the flag via `PARAMS_FLAGS_REMEMBERED`, making this completely transparent to the user.\n\n## 4) Add \"Show Recent/System Locations\" to file browser\n[D14649](D14649)\n- Include in either the right click menu, or the header menu, options to toggle these two user preferences.\n - It might be worth storing them as per-editor parameters at this point, though I personally don't see much of a desire to have these differ per editor.", "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.", "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", "Drivers don't refresh simulations.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.90.0\nAs far as i can remember this bug exists at least from Blender 2.81\n\nAdding Drivers to any of the cloth simulation values will result in them not refreshing the bake when changing that value. When any of these values are changed by the Drivers, user needs to manually go back into the cloth simulation settings and either switch a random setting or Re-Bake the simulation for it to update to the current settings.\n\nAdd custom property to any object -> Copy that value as driver -> Paste it into any of the cloth simulation value settings -> Values will update but cloth simulation won't refresh, forcing you to go back into the cloth settings and refresh them manually. \n\n", "Switching Curve Shapekeys in Edit Mode go haywire if relative to one another\nOperating system:\nLinux\n\nBroken in 2.79 onwards\nWorked in 2.78\n\nPossibly caused by\n6f1493f68f\n5e1d4714fe\n\nShapekeys on curves do not reset properly when switching between them in edit mode, and one shapekey is relative to another.\n\nSelect the circle and enter edit mode. Repeatedly switch between shapekeys 'Key 1' and 'Key 2' while staying in edit mode. 'Key 2' will change over time from just this.\n[bug_report_shapekeys_curve.blend](bug_report_shapekeys_curve.blend)\n\n**How to reproduce the scene**\nCreate a Curve object. Add Basis, Key 1, Key 2 shapekeys. Set 'Key 2' relative to 'Key 1'. Select 'Key 1' and translate/scale it. ", "Cannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager\nOperating system: Win10\nGraphics card: Nvidia GTX 1060 6G\n\nBroken: 2.82\nWorked: None\n\nCannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager\n\nFor example, this is an operator called by WM to manipulate the location of the selected object. We cannot insert keyframes to the property from RMB > Insert Keyframe or from the anim dot after the property\n\n```\nimport bpy\n\nclass HelloWorldOperator(bpy.types.Operator):\n \"\"\"Creates a Panel in the Object properties window\"\"\"\n bl_label = \"Hello World Modal Operator\"\n bl_idname = \"test.hello\"\n\n def draw(self, context):\n layout = self.layout\n layout.use_property_split = True\n layout.use_property_decorate = True\n\n obj = context.active_object\n\n layout.label(text=\"Hello world!\", icon='WORLD_DATA')\n layout.prop(obj, 'location')\n \n def execute(self, context):\n return {'FINISHED'}\n \n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_dialog(self)\n\n\ndef register():\n bpy.utils.register_class(HelloWorldOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(HelloWorldOperator)\n\n\nif __name__ == \"__main__\":\n register()\n bpy.ops.test.hello('INVOKE_DEFAULT')\n\n```\n\nThis kind of problem exists in all modal-like panels or operators called by WM. The file picker from file_select is also not working. Is it RNA problem? I hope developer can generate its error message in the console. For now, I don't know what to do next. Please let me know how can I insert keyframes to properties in such panel/operators with right click\n\nBest wishes, thank u", "Physics / Simulation Nodes Baking User Interface\nThis proposal unifies the Physics panels to be closer to the modifiers. There is no functional change besides the user interface.\n\nThen it adds the Simulation panel as a panel which is always visible for the objects. It is not part of the Add Physics.\n\n\n\nOpen questions:\n* Should Delete / Bake All Dynamics also take into account Simulation Nodes?\n\n", "Can't uninstall completely and clean\nwindows 7 SP1 64 bit\n\nBroken: 2.75a c27589e\n\nCan't uninstall completely when used \"Uninstall blender\" from Start menu, and need to manually delete\n\n\nthe old version (with .exe packed ) has an option that let's you select \"leave user setting\" or \"remove all things\" when you uninstall, but the new version (with .msi packed) no this option for uninstall, and will leave some files on your computer, by the way, it's have't choice for your install, e.g. create a desktop shortcut, use blender for .blend flies, and create start menu, all blender default at install, and I can't custom setting for this, although this no affect for our used, but i'm a little OCD :D\n\nsorry for my bad English :)\n" ]

[ "Broken UI after creating new file in 2.79 test and daily builds\nWindows 10x64 Home Ru Version 1607 Build 14393.639 + latest autoupdates\nNVIDIA GeForce GTX 970 with 378.66 NVIDIA drivers (latest)\nIntel Core i7-4790K\n[system-info.txt](system-info.txt)\n\nBroken:\n2.79 testbuild x64 e0bc5b5\n2.79 daily build x64 c2d285f\nWorked:\n2.78c x64 e92f235283\n\nCreating new file leads to UI bug: \n1. all windows titles becomes hidden\n2. outliner windows scale is changed\nUI can be fixed by main window resizing.\n\n\n\nCreate new file by \"File / New\" menu command.\n\n" ]

[ "VSE: No simultaneous strip snapping on left & right side [and right side favoured]\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\n{[F10300365](no-dual-strip-snapping.png),size=full}\nA strip in VSE cannot snap at left and right ends simultaneously. Annoying when the end that does not snap is the end that you're wanting to know the orientation of (especially when you're zoomed out and can't tell by eye). \n\nFurther to this, the right side snap will always prefer over the left. It seems it just searches the right side first, and if it snaps it just doesn't check the left side at all. I would find it very odd if dual snapping isn't intended, but if somehow there is no plan to add it in the near future, at least the behaviour should not prefer one side - like maybe prefer the side based on the direction the strip is dragged or something (snap first to the side of the direction the strip is heading?).\n\n[strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred.blend](strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred.blend)\n- Open the blend file, and drag colour strip along x-axis\n- Only the right end will snap, despite both ends clearly lining up with the metastrips\nNOTE: There is a reason I used a metastrip as the snap-to strips here, as there is another snapping bug I will be filing soon (and I didn't want that bug to mess up the behaviour in this one).\n", "Sequencer Preview : area_join() doesn't join well\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI join two Sequencer preview areas with a script and both stay, but one is like broken. If I resize the view, it goes back as expected : the residual broken view disappears.\n\n- Open the provided blend file\n- There are two Sequencer preview views\n- Run the script in the text editor\n- The display of one view changes a bit and you cannot resize it.\n- Resize the main view, the residual view disappears.\n- NB: You can run the script again to split views and re-run it to join them again. The bug remains the same.\n\n[BugSplitView.blend](BugSplitView.blend)", "Color > Multiply doesn't multiply alpha channels\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) 3.6.2\n\nThe Color > Multiply section in a video sequencer strip no longer multiplies the alpha channel when that feature is pretty important for creating outlines using the glow effect. Perhaps adding an option whether to multiply alpha or not would be beneficial?\n\nStart up blender 4.0.0\nSwitch to Video Editing workspace\nAdd a white color strip with 0.1 opacity\nAdjust the Color > Multiply value and notice how it doesn't affect alpha anymore\n\n", "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", "Use draw manager for clip editor drawing\nCould be stalled to 2.93 as there isn't an real issue here as far as we are aware of. The compositor issues are more tangable.", "Regression: Crash on deleting NLA strip in tweak mode\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.0, 3.6.0\nWorked: 2.93\n\nWhen using the 'Previous Layer' function of the Action Editor to tweak NLA strips, trying to delete a (green) strip in tweak mode crashes Blender.\n\n\n- Open `109430.blend`\n- In the NLA area, press X to delete the green strip.\n- Blender crashes\n\nOriginal/from fresh file:\n\n- In the default startup file, open 2 areas; a Dope Sheet set to Action Editor, and a Nonlinear Animation.\n- Keyframe any property of the default cube.\n- In the Action Editor, click Push Down on the newly created action.\n- Also in the Action Editor, click the 'Previous Layer' button (the small down arrow). This activates tweaking for the NLA strip.\n- In the NLA area, click the green strip so it's highlighted.\n- Press X to delete it. Blender crashes.\n\n", "VSE: issue moving strips with changed speed factor\nOperating system: Linux-5.18.10-76051810-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: AMD Radeon Vega Frontier Edition (VEGA10, DRM 3.46.0, 5.18.10-76051810-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.3.5\n\nBroken: version: 3.5.0 Alpha\n\nIn the Video Sequence Editor, when moving strips that have the speed factor different than default 1.0 the strips seem to glitch so the start and end of each strip fluctuates.\n\nNew file\nGo to VSE\nAdd a movie strip\nUse \"K\" to cut the movie strip a few times (so you have maybe 10-15 strips)\nSelect a strip, go to the Time panel and change the speed factor to 1.5\nOne by one, do the same with all the strips (perhaps giving them various values between 1.1 and 1.5)\nMove each strip up against each other, so there's no dead space between\nSelect all of them and move them around...\n{[F14115112](vse_speedup_movement_glitch.mp4)}you will see the length of each strip fluctuates\n\n", "Image Editor Blank After Switching Slots, Even If There Is A Render In That Slot\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: (2.80, 79f67acccb36, blender2.7, 2019-03-24)\n\nSwitching the slots in the image editor for the render result (hotkey \"j\") can show a blank image, even if there is an image available in that slot.\nSelecting the render layer in the dropdown menu brings it back.\nThis is irritating, especially since the image is shown right after rendering.\nThis only happens if the compositor is disabled.\n\n- Load [bug.blend](bug.blend).\n- Press F12 to render. The image editor comes up.\n- Press \"j\" to switch to switch the slot.\n- Press F12 to render again.\n- Press \"j\" to switch back to the previous slot. It now appears blank.", "Region overlap crashes when interacting with action zones\nEnable region overlap user preference.\n\nIn the default 3D viewport, press NKey, then drag on the corner widget. -> Blender crashes.\n\nAttached asan output: [region_overlap_azone.txt](region_overlap_azone.txt), [region_overlap_azone_2020_01_28_update.txt](region_overlap_azone_2020_01_28_update.txt) (found while investigating #46764).\n\nUpdated asan output\n\n\n----\n\nNote: Blender internals aren't well suited of handling regions being manipulated like this while the rest of Blender is being used. We could either prevent interaction during the fade, or disable it since its not really needed.", "(Video editing) Different audio/video lenght after import strip\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 2.92.0\n\nAs shown in these images, the same media file (with audio and video) shows different lengths between audio and video in VSE:\n\n\n\n\n\n\n-\n\n", "Blender freezes when calling an operator after a dialog window.\nOperating system: Windows 10 x64\n\nBroken: 2.80 win64, 2019-04-01 19:15\nWorked: 2.79b win64, release\n\n\nIf an operator from `bpy.ops` is called after a dialog window / popup is closed, Blender freezes and has to be manually terminated. A script to reproduce the error is located at the bottom of this task description.\n\n\n - Copy / Paste the code at the bottom of the task description into Blender's text editor\n - Press \"ALT P\" to run the script\n - Place the mouse cursor over a 3D Viewport\n - Select any object in the 3D View (for example the default cube)\n - Press \"F3\" to bring up the search bar\n - Type in \"Popup Input Test\" to launch the script\n - Press \"P\" to generate a popup dialog\n - Click the \"OK\" button in the dialog\n # Watch Blender freeze and stop responding to input.\n\n**Additional Notes**\n\n - The freeze happens at the `bpy.ops.transform.translate` call in the `run_transform` function. The following `print(\" after bpy.ops.transform\")` statement never executes.\n - The freeze up when executing the `run_transform` function does not happen if...\n - a popup dialog is not opened first (Press \"T\" instead of \"P\" when the script is running).\n - the `run_transform` function is called from the `execute` method in the `POPUP_OT_input_panel` class instead of the `draw_callback_px` function.\n - the contents of the `draw_callback_px` function (`if self.wait_for_popup` ...) are relocated inside the `modal` method in the `POPUP_OT_main` class.\n - the script is run in Blender 2.79 instead of 2.80 (the script below can be run in both 2.79 and 2.80).\n\n```\nimport bpy\nprint(\"\\nLoaded add-on.\\n\")\n\n# globals\npopup_active = False\npopup_cancel = False\n\n\ndef run_transform():\n print(\"before bpy.ops.transform\")\n bpy.ops.transform.translate(value=(0.0, 0.0, 1.5))\n print(\"after bpy.ops.transform\")\n\n\nclass POPUP_OT_input_panel(bpy.types.Operator):\n bl_idname = \"object.popup_input_dialog_op\"\n bl_label = \"Popup Input Dialog Panel\"\n bl_options = {'INTERNAL'}\n\n def execute(self, context):\n print(\"\\nPOPUP_OT_input_panel: exec\")\n global popup_active\n popup_active = False\n #run_transform()\n return {'FINISHED'}\n\n def invoke(self, context, event):\n print(\"\\nPOPUP_OT_input_panel: Invoke\")\n return context.window_manager.invoke_props_dialog(self)\n\n def cancel(self, context):\n print(\"\\nPOPUP_OT_input_panel: Cancelled\")\n global popup_active, popup_cancel\n popup_active = False\n popup_cancel = True\n\n\ndef draw_callback_px(self, context):\n if self.wait_for_popup:\n global popup_active, popup_cancel\n if not popup_active:\n if popup_cancel:\n popup_cancel = False\n self.wait_for_popup = False\n elif not popup_active:\n run_transform()\n self.wait_for_popup = False\n\n\nclass POPUP_OT_main(bpy.types.Operator):\n bl_idname = \"view3d.popup_main_op\"\n bl_label = \"Popup Input Test\"\n\n @classmethod\n def poll(self, context):\n return context.mode == 'OBJECT' or context.mode == 'EDIT_MESH'\n\n def exit_addon(self):\n bpy.types.SpaceView3D.draw_handler_remove(self._handle, 'WINDOW')\n print(\"Exiting addon\")\n return {'CANCELLED'}\n\n def modal(self, context, event):\n context.area.tag_redraw()\n global popup_active\n\n if event.type in {'A', 'MIDDLEMOUSE', 'WHEELUPMOUSE',\n 'WHEELDOWNMOUSE', 'LEFTMOUSE', 'TAB'}:\n return {'PASS_THROUGH'}\n\n if event.type == 'P' and event.value == 'PRESS':\n if not self.wait_for_popup and not popup_active:\n self.wait_for_popup = True\n popup_active = True\n bpy.ops.object.popup_input_dialog_op('INVOKE_DEFAULT')\n\n if event.type == 'T' and event.value == 'PRESS':\n if not self.wait_for_popup and not popup_active:\n run_transform()\n\n elif event.type == 'D' and event.value == 'RELEASE':\n # start debug console\n __import__('code').interact(local=dict(globals(), **locals()))\n\n elif event.type == 'ESC' and event.value == 'RELEASE':\n return self.exit_addon()\n\n elif self.force_quit:\n return self.exit_addon()\n\n #if self.wait_for_popup:\n\n return {'RUNNING_MODAL'}\n\n def invoke(self, context, event):\n if context.area.type == 'VIEW_3D':\n args = (self, context)\n self._handle = bpy.types.SpaceView3D.draw_handler_add(\n draw_callback_px, args, 'WINDOW', 'POST_PIXEL')\n self.force_quit = False\n self.wait_for_popup = False\n context.window_manager.modal_handler_add(self)\n print(\"Add-on running\")\n return {'RUNNING_MODAL'}\n else:\n self.report({'WARNING'}, \"View3D not found, cannot run operator\")\n return {'CANCELLED'}\n\n\ndef register():\n bpy.utils.register_class(POPUP_OT_input_panel)\n bpy.utils.register_class(POPUP_OT_main)\n\ndef unregister():\n bpy.utils.unregister_class(POPUP_OT_input_panel)\n bpy.utils.unregister_class(POPUP_OT_main)\n\nif __name__ == \"__main__\":\n register()\n```\n", "Panning with spacebar in clip editor stops after some movement\nOperating system: Windows-10-10.0.22581-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.10.00.22 30.0.21000.22018\n\nBroken: version: 3.1.0\n\nWhen I set the spacebar to pan (disabling the play animation, tools, or search options for the same keymap), in all windows the shortcut works properly - when I press spacebar and move the mouse, the screen pans, but the clip editor window. It works for a second and then it stops working. It only works if right after pressing spacebar, I press ctrl, shift or alt, or any other key in fact. I think it causes a reset and it forgets to cancel the shortcut. Also, if I put the shortcut to be release sensitive (not press), it also works, but there's no point in making that, cause I'd have to press spacebar again in another window to apply the pan.\n\n- In default scene, switch to clip editor\n- From preferences tab, Set the spacebar as shortcut for panning in clip editor\n- Pan around by Holding `spacebar` key (stops after some movement)\n\n", "The Shortcut keys of Play Aniamtion not work in Spreatsheet Editor\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nThe Shortcut keys of Play Aniamtion({key Space}) not work in Spreatsheet Editor\n\n[play animation bug.mp4](play_animation_bug.mp4)\n\n", "Proportional Editing O key shortcuts bug/deceptive?\nOperating system and graphics card\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nI am using Blender GIT Rev b6df448 on a Fedora 20 Linux 64Bit Box with an Intel 3000HD gfx\ndebug build.\n\nI noticed that when in Edit Mode with a Mesh Object selected pressing the [o Key] while over\nthe 3D Viewport only enables or disabled Proportional Editing Mode. It never cycles through\nall the other available options (Connected & Project 2d) in the\n[3D View Editor Header > Mesh > Proportional Editing] sub-menu even though it has the shortcuts\nnext to their names. This is different from the Proportional Editing Falloff entries which use\n[SHIFT Key + o Key] they do have all their entries cycled through when using their shortcut (and\nkeyboard shortcuts next to they names).\n\nShould the short cut names against the entries that are not cycled through be removed?\n\n[3D_View_Editor_Header-Mesh-ProportionalEditing-OkeyBug.blend](3D_View_Editor_Header-Mesh-ProportionalEditing-OkeyBug.blend)\n\n[system-info.txt](system-info.txt)", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)" ]

[ "Bug sequence editor with sound file cutting in Blender 2.79a\nBlender 2.79a don't cut a sound anymore. When you cut it the second part of the sound strip started to be unplayable. You can reproduce this from scratch in new file.\n[sequence_bug_in_2_79a.mp4](sequence_bug_in_2_79a.mp4)" ]

[ "Some icons cannot be overriden from python (e.g. 'Constraint.mute', 'use_fake_user')\nBroken: version: 3.3.0 Alpha\nWorked: Looks like this was once working in 2.80 (but has stopped working in 2.81)\n\nSome boolean properties apply an offset to their icon depending on the state of the boolean. This offset is applied even when an icon override is used, like so: `UILayout.prop(icon=whatever)`.\n\n**Workaround**\n```python\ndef get_icon_value(icon_name: str) -> int:\n icon_items = bpy.types.UILayout.bl_rna.functions[\"prop\"].parameters[\"icon\"].enum_items.items()\n icon_dict = {tup[1].identifier : tup[1].value for tup in icon_items}\n\n return icon_dict[icon_name]\n\ndef draw_with_icon_fix(layout, prop_owner, prop_name, icon: str, offset=1, invert_checkbox=False, **kwargs):\n \"\"\"Drawing some booleans in the UI with a custom icon can be \n annoying because Blender might offset the icon based on the boolean state.\n You can use this function to counter that offset. To find the offset, you have to \n trial and error, it's either 1 or -1. (Or 0 but then you don't need this)\n \"\"\"\n\n bool_value = getattr(prop_owner, prop_name)\n offset = offset * int(bool_value)\n if invert_checkbox:\n offset = 1 - offset\n icon_value = get_icon_value(icon) + offset\n layout.prop(prop_owner, prop_name, icon_value=icon_value, invert_checkbox=invert_checkbox, **kwargs)\n```\n\n- File with script within: [icon_madness.blend](icon_madness.blend)\n- Script should self-execute, look for a \"FixMe\" panel in the sidebar.\n\n\nSo this file works in 2.80 and is broken in 2.81:\n[icon_madness_2.blend](icon_madness_2.blend)", "Greasepencil operators (e.g.bpy.ops.gpencil.stroke_join) fail when running outside the 3Dview\nOperating system: Linux, pop-os 20.04\n\nBroken: 2.91.0 Alpha\n\nbpy.ops.gpencil.stroke_join operator fails ( but returns {'FINISHED'} without error ) when executed from a python script or the build-in python interpreter.\n\nThe operator works fine from the GUI\n[Bug_reproduce.mp4](Bug_reproduce.mp4)", "Status bar information gets cut off when using a monospaced font\n\nOperating system: Arch Linux\nGraphics card: NVIDIA GTX 980\n\n\nBroken: Blender 2.90.1\nWorked: I don't think this has ever worked when using a monospaced font (fira mono regular)\n\n\nWhen using a monospaced font, if you want to display scene statistics, blender version, system memory and video memory on the status bar the text will always get cut off and you need to scroll to see it. Its position on the status bar also gets reset everytime you interact with the viewport which makes it super annoying.\n\nI don't see how the empty unused space to show mouse shortcuts is more useful than scene statistics and other information.\n\nI also reported it on the actual task that prompted all these changes to the status bar and was completely ignored.\n\n\nGo to blender *Preferences* > *Interface* > *Text Rendering* and set the *Interface Font* to fira mono regular or another monospaced font.\n\nThis is how it looks with the default font:\n\n\n\nThis is how it looks with a monospaced font:\n\n", "macOS: touch input fails to work on a Wacom Intuos Pro tablet\nOperating system: macOS 11.1 Big Sur build 20C69\nGraphics card: n/a\n\nBroken: Top of tree git pull from today\nWorked: probably never since 2.8\n\nWacom Intuos Pro tablets support touch in addition to pen entry. When using touch, two fingers will scroll up and down. In Blender, two finger touch should work like an Apple touch pad or Apple magic mouse: two finger movement will orbit the view; holding down command zooms, holding down shift pans. Instead, it simply does nothing.\n\nBlender.app, default cube. Place two fingers down on a Wacom Intuos Pro tablet and move them around; it should orbit, but nothing happens. Well, the bottom status bar flickers back and forth as though command/shift or alt is pressed. \n\nThere are two reasons why this happens. \n1. Blender has incorrect Cocoa/AppKit code. I worked on AppKit for ~13 years at Apple. Below is a diff that addresses some of the issues. The code attempts to keep track of m_multiTouchScroll, but this isn't needed. It should key off of hasPreciseScrollingDeltas instead. I tested this diff with: Apple Magic Mouse, old school Apple scroll wheel mouse, Wacom tablet; all things work the same (except Wacom, which has the bug I'm reporting fixed). There is also a comment about intuos5, but that seems to be incorrect and outdated, but I don't have an Intuos 5 to test with.\n\n[0001-Fix-scrolling-with-wacom-tablets-using-them-as-a-tou.patch](0001-Fix-scrolling-with-wacom-tablets-using-them-as-a-tou.patch)\n\n2. Wacom's tablet touch drivers do link-checked behavior based on the bundle identifier \"org.blenderfoundation.blender\". In other words: they change the touch behavior when they see the target application is Blender. Wacom needs to fix this, but I'm not sure how to log a bug report for them.\n\nTo prove this, I created the sample application:\n\n[TabletTest.zip](TabletTest.zip)\n\nThe sample application has the blender bundle identifier set, as seen in this screen shot:\n\n\n\nIn ViewTest.m I log the flagsChanged:\n\n``` - (void)flagsChanged:(NSEvent *)event\n```\n{\n NSLog(@\"%@\", event);\n}\n```\n```\nIf you run the app and do a two finger scroll in the window you will see some flagsChanged logged, which is very strange because Shift/Alt/Cmd have not been pressed! Wacom is faking them for some reason, and changing the scrolling data, which messes up Blender.\n\nChange the applications's bundle identifier to \"org.blenderfoundationXX.blender\" (you can simply edit the info.plist) and run it again; it will then behave correctly.\n\n\n\nI don't know how to fix item 2 for Blender; I'm fixing it in my own build of Blender by changing the bundle identifier to org.blenderfoundation.bl3nder after it is built. I looked into identifying the events, and I can could identify the source as coming from the wacom driver but I can't fix them. \n\nI'm trying to find a contact at Wacom to have them fix this, but once it is fixed we still need item 1 fixed. \n\n\n\n", "VSE: Snap to the 'Hold Offset' of strips being transformed\nA strip does not snap to itself, but `Hold Offset` is something whose position may remain unchanged in some cases:\n{[F10243791](hold_snap.gif),size=full}\n\n**Proposal**\nThe idea is to track those cases where the `Hold Offset` of transformed strips doesn't change and allow snapping for them.\n\n", "Grease Pencil Proportional Edit \"Connected Only\" fails to delimit unconnected strokes if they are selected\nVersion 2.80 rc3 (Linux 54)\n\n[GP_proportional_edit_bug.blend](GP_proportional_edit_bug.blend)\n\nHow to reproduce:\n\n - Open attached file, remain in edit mode.\n - Note the proportional edit settings and selected stroke vertices.\n # Move around the whole blue stroke, along with one vertex at the tip of the black stroke.\n\nObserve how the black stroke is affected by the selected vertices of the blue stroke, even though the two strokes are not connected and are on different layers. This is not the expected behavior of the \"Connected Only\" setting. The strokes should only be affected by their own vertices, but as long as any vertex of either stroke is selected, they will affect each other as though the \"Connected Only\" setting is ignored!", "Sculpt mode - program crash: brush smooth + graphics tablet\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.30\n\nBroken: version: 3.6.0\n\nUnless explicitly specified in \"preferences > input > tablet > tablet API > wintab or windows ink\", it crashes when using smooth brush. If I use the \"automatically\" setting.\nFor the bug to recur, the brush must take a force or size parameter from the pressure force on the graphics tablet. If I use the mouse, the error does not occur.\nThis error is repeated in any scene and with any object. I created a cube, remesh it and used a smooth brush in sculpt mode. Blender crashes to completion.\n\ngraphics tablet: xp-pen star 06\n\n", "Setting the brush radius unit to \"scene\" does not automatically use correct stroke spacing distance\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nThe brush settings have an option to fix the radius to either the view or scene, called \"Radius Unit\".\nIf the Scene setting is used, it will not automatically use the correct spacing distances for the stroke.\nThis needs to be toggled manually with separate stroke setting called \"Spacing Distance\" from view to scene.\n\nIf the viewport orientation is very close to the world origin, rotated towards an object that is further away from the world origin, it will lead to a much higher spacing distance.\n\n[2022-05-13 10-24-15.mp4](2022-05-13_10-24-15.mp4)\n\n**Exact steps to reproduce**\n- Move the default cube 4 units away from the world origin\n- Add a multires modifier and subdivide 5 times\n- Enter sculpt mode\n- Use the draw brush\n- Switch the Radius Unit setting from View to Scene\n- Orient your viewport so that you are positioned very close to the world origin, looking at the cube\n- Sculpt on the cube (Notice the very high spacing distance)\n- Rotate your view around to the other side of the cube (Now the viewport is positioned further away from the world origin)\n- Sculpt on the cube from that angle (The stroke distance should be much smaller now)\n\n- To fix the issue switch the stroke setting \"Spacing Distance\" from View to Scene\n- Retry sculpting from the same angles", "Brush cursor (sculpt, vertexpaint, weightpaint) stuck/doesn't draw under transparent part of N-panel\nBroken: 2.80 to 3.1 (and currently 3.2.0 alpha 4fa3eadce99a) (technically 2.79 as well, but back then region ovelap was drawn a bit diferently).\nWorked: Never\n\nTools brushes don't draw over the transparent property panel, even though Region Overlap is on.\n\n* Ctrl + N → Sculpting\n* N (to open the Properties region).\n* Move the mouse to the right, beyond the alignment line of the properties editor panels.\n\n\n\nThe brush drawing doesn't follow the mouse cursor. The tool itself works though, and the brush is even drawn if you click in that part.\n\n---\n\nVideo from the original report: [F8795403](2020-08-20_05-04-02.mp4)", "Bug when working with the Child Of constraint and the Selection to Cursor command\nBroken: version: 3.0.0 Alpha\nWorked: Never\n\nWhen working with the Child Of constraint the `Select To Cursor` command does not work correctly.\n\n- Open attached file\n- In the 3d View press {key Shift S} and `Select To Cursor`\n[Bug_ChildOf_Selection2Cursor.blend](Bug_ChildOf_Selection2Cursor.blend)\n\n---\n**Original Report:**\nWhen working with the Child Of constraint, it is impossible to use it several times by enabling and disabling the influence of the constraint. \nHe second time the offset is different and the child object jumps away from the desired position. \nIt's hard to put it in the right place. I tried to use a 3D cursor for this, but the Select To Cursor command does not work correctly when working with this the Child Of constraints.", "Weird artefacts from emission surface\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M (but this occurs also on CPU)\n\nBroken: 3.6.2\nWorked: don't know\n\n\nIn the attached .blend file I have set up an emission shader to emit light from one end of a long thin surface. The screenshot illustrates the problem: a bunch of weird artefacts appear.\n\nIf I change it to emit from the other end of the surface, by swapping the 'Map Range' node in the screenshot for the disconnected one, the problem goes away.\n\n\n\n\nLoad the attached .blend file and switch the view to rendered.\n\n", "Current frame indicator has misaligned and inconsistent pixel positioning\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060 TI\n\nBroken: 3.1.2\nWorked: Probably never\n\nThe current frame indicator is aligned inconsistently against the keyframes depending on where the current frame indicator is within the 2D viewport.\n\n[framewiggle.mp4](framewiggle.mp4)\n\nThere is an additional issue that is probably contributing to this as well. The frame indicator is 4 pixels wide (shadow included). Note that this is an *even* number. Because the background grids, keyframes etc. all have *odd* widths, it is mathematically impossible for the frame indicator to ever be properly centred over any of them. The current frame indicator should be made to be 3 pixels wide, or perhaps 5 pixels wide so that it can actually be centred with other elements in the UI.\n\n\n\n1. Make a bunch of keyframes on an action.\n2. Position the current frame at a frame that has keyframes.\n3. Pan the 2D viewport of the action editor.", "Grease Pencil: stroke placement \"Surface\" projects onto lamps and empties\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: AMD Radeon HD 5700 Series ATI Technologies Inc. 4.5.13417 Core Profile Context 15.301.1901.0\n\nBroken: version: 2.83 (sub 5)\n\nIf you draw with *Stroke Placement* set to *Surface*, Blender interprets objects such as lamps and empties as surfaces and projects the stroke onto them. \nThis might be a feature rather than a bug. Maybe just \"unexpected behaviour\"?\n\n\n\n\n1) Create a new \"2D animation\" Blender file.\n2) Create a mesh (A) to project your strokes onto, like a plane for example.\n3) Create a lamp object or an empty (B), and place it in front of A, closer to your viewpoint in space than A.\n4) Select the GP object and go into draw mode.\n5) Set \"Stroke Placement\" to \"Surface\". (You can add an offset of 0.1 for easier visibility.)\n6) Draw over A, crossing over B here and there.\n7) Rotate your viewpoint. The stroke you've drawn should be projected onto A, with a few points projected onto B where they crossed over it.\n\n", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg", "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" ]

[ "Wacom tablet input doesn't work in \"mouse mode\" in 2.92.0 Alpha (Nov 25th build)\nOperating system: Windows 10\nGraphics card: Geforce 2070\n\nBroken: 2.92 Alpha e09d0c0d077c\nWorked: 2.91\n\nUsing my Wacom tablet in \"mouse mode\" in Blender 2.92.0 Alpha seems to scale the input. It is difficult to explain but the video below demonstrates the issue.\n\nThis happens on a fresh system startup and only in Blender (no other software). It also doesn't matter whether I had it set to mouse-mode before or during Blender being active.\n\nI had posted this video previously on a different ticket but I had not gotten a response then so I am trying again as this bug is not yet resolved. Thank you!\n\nSee video below...\n[pen mouse mode input scaling issue.mp4](pen_mouse_mode_input_scaling_issue.mp4)" ]

[ "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "(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", "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)", "No visible mesh on Viewport Screenshot in sculpt mode with Multires\nOperating system: Linux-6.2.11-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.36 64 Bits, X11 UI\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhat the title says.\n\n- Add a cube\n- Enter sculpt mode\n- Add a multiresolution modifier and subdivide\n- Use the operator: Header -> View -> \"Viewport Render Image\"\n\n", "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "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", "popup window call operator will crash blender\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0 Beta\n\nThis script is use to check the active material, it can be run correct in the main window, but not popup window(change the pref window to node editor)\n```\nimport bpy\n\nbpy.ops.screen.userpref_show(\"INVOKE_AREA\")\narea = bpy.context.window_manager.windows[-1].screen.areas[0]\n\n\narea.type = 'NODE_EDITOR'\nflip_header = True\narea.ui_type = 'ShaderNodeTree'\narea.spaces[0].node_tree = bpy.data.materials['Material'].node_tree\n\nfor region in area.regions:\n if region.type == 'HEADER':\n with bpy.context.temp_override(area=area, region=region):\n if flip_header: bpy.ops.screen.region_flip('INVOKE_DEFAULT') # this line will not\n\n if region.type == 'WINDOW':\n with bpy.context.temp_override(area=area, region=region):\n bpy.ops.node.view_all(\"INVOKE_AREA\") # this line will report context error\n```\n\n- Open .blend file\n- Execute script\n[#98491.blend](T98491.blend)\n\n\n\n", "Alembic mesh cache viewport performance affected even when disabled for viewport\nOperating system: manjaro-kde-21.0.3-210428-linux510 switched to linux512 kernel\nGraphics card: rx6800\n\nBroken: 2.93\n\n\nViewport animation playback performance is affected even when alembic modifier is disabled for viewport and no visible changes are visible.\n\n[blend and abc.zip](blend_and_abc.zip)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nAdd mesh sequence cache modifier with alembic file, select an object from abc, hit play in viewport, watch fps go down, disable modifier, watch fps go up, remove modifier or change selection to none, watch fps go up even more. ", "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).", "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", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n", "Crash when auto script execution is enabled\nOperating system: Windows 10 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: Blender 4.0.0 7372b3bdda35 and later\nWorked: never? 2.93 fails too\n\nBlender daily build crashes immediately on launch. The blender start screen isn't shown at all, only a grey window which then immediately closes. The crash log indicates that it is a memory EXCEPTION_ACCESS_VIOLATION (see log file attached).\n\n- Open preferences, enable `auto script execution`\n- Save prefs and close blender\n- Rename attached file and replace it with existing startup file\n- Launch blender (crash)\n\n- - -\n<details>\n <summary> Original report </summary>\nStart Blender through Steam, Blender Launcher, blender_debug_log.cmd, blender_debug_gpu.cmd, or blender_debug_gpu_glitchworkaround.cmd.\nA grey window opens with the Blender logo in the top bar.\nThe window closes as Blender crashes.\n\n[ Crashing_4-0-0_daily.blend](https://projects.blender.orgattachment)\n</details>", "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" ]

[ "Blender crashing a lot randomly in the rendered viewport\nOperating system: Win10 Pro\nGraphics card: GeForce GTX 770/PCIe/SSE2 4.5.0 NVIDIA 456.38\nCPU : Ryzen 9 3900X\n\n2.90.1\nAlso crashed on 2.83LTS\n\nBlender crashes within few minutes looking around in rendered view (Cycles CPU mode)\nCrashes even in very simple scenes like a default cube\nsudden GPU usage spike a the moment of the crash\nTried using 2 versions, default settings, uninstalling all addons.\nVideo card drivers are up to date\nWindows is up to date too.\n\nI'm unable to understand the nature of crash by looking at the cmd or the crash log.\n\n[wtf.blend](wtf.blend)\n[wtf.crash.txt](wtf.crash.txt)\n\n\n\n```\nStack trace:\nblender.exe :0x00007FF633BEED80 embree::avx2::BVHNIntersector1<4,1,0,embree::avx2::ArrayIntersector1<embree::avx2::InstanceIntersec\nblender.exe :0x00007FF6332A4C80 rtcIntersect1\nblender.exe :0x00007FF6330DA860 ccl::kernel_path_trace\nblender.exe :0x00007FF633086280 ccl::kernel_cpu_avx2_path_trace\nblender.exe :0x00007FF632D9A700 ccl::CPUDevice::render\nblender.exe :0x00007FF632D9B590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF632D9BA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF632D960B0 std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call\nblender.exe :0x00007FF63534F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFE631037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFE631037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFE630F51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFE630FA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFE631019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE631019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFE8C2F1430 configthreadlocale\nKERNEL32.DLL :0x00007FFE8C5A6FC0 BaseThreadInitThunk\nntdll.dll :0x00007FFE8E3BCEA0 RtlUserThreadStart\n```\n\n", "Consistent crash in Embree SSE42, SSE2 code in older Intel CPU.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.83.7 Before Embree (and maybe TBB) was made default.\n\nThis has been occurring since Embree was made the default path tracer for CPUs. I just haven't figured out a repeatable test case until now. \nThis crash is similar to #81354 (2.9.1 Close without error message)\nA scene with a torus and a Suzanne. The Suzanne has a Subdivision modifier set to level 4. Setting the Viewport Shading to rendered and the Render Pass to UV results in a crash.\nIt won't crash if the torus is deleted. It won't crash if the subdivision modifier is turned off.\n\nOpen attached file.\nSet Viewport Shading to Rendered.\nSet Render Pass to UV\n\n[T73199_simple_v2.blend](T73199_simple_v2.blend)\n\n[MSVC_debug_call_stack.txt](MSVC_debug_call_stack.txt)\n\nLet me know if you need anything else out of MSVC.\n\n\n\nGot it to load the UV once without crashing. As you can see, Suzanne's topology is in quite some disarray.\n\n\n\n\n\n[T73199_simple_v2.crash_v2.txt](T73199_simple_v2.crash_v2.txt)\n\n```# Blender 2.91.0, Commit date: 2020-10-09 15:00, Hash 2d94b0d6b062\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.data.screens[\"Layout\"].(null) = 'UV' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF726233E08\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters- [x] : 0x0000000000000000\n\tParameters- [x] : 0x00000188C31B4050\n\n\nStack trace:\nblender.exe :0x00007FF726233DF0 embree::sse2::TriangleMi<4>::loadTriangle\nblender.exe :0x00007FF7275030A0 embree::sse42::BVHNIntersector1<4,1,1,embree::sse42::ArrayIntersector1<embree::sse42::TriangleMiInt\nblender.exe :0x0000000000000000 \nblender.exe :0x00007FF725F74CD0 embree::sse42::BVHNIntersector1<4,1,0,embree::sse42::ArrayIntersector1<embree::sse42::InstanceInter\nblender.exe :0x00007FF725F74CD0 rtcIntersect1\nblender.exe :0x00007FF725C41C10 ccl::kernel_path_trace C:\\blender-git\\blender\\intern\\cycles\\kernel\\kernel_path.h:692\nblender.exe :0x00007FF725C39820 ccl::kernel_cpu_sse41_path_trace C:\\blender-git\\blender\\intern\\cycles\\kernel\\kernels\\cpu\\kernel_cpu_impl.h:99\nblender.exe :0x00007FF725A87B20 ccl::CPUDevice::render C:\\blender-git\\blender\\intern\\cycles\\device\\device_cpu.cpp:937\nblender.exe :0x00007FF725A88AF0 ccl::CPUDevice::thread_render C:\\blender-git\\blender\\intern\\cycles\\device\\device_cpu.cpp:1291\nblender.exe :0x00007FF725A88F90 ccl::CPUDevice::thread_run C:\\blender-git\\blender\\intern\\cycles\\device\\device_cpu.cpp:552\nblender.exe :0x00007FF725A82CC0 std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional:903\nblender.exe :0x00007FF727F866B0 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute C:\\blender-git\\lib\\win64_vc15\\tbb\\include\\tbb\\task.h:1049\ntbb.dll :0x00007FFD609837A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFD609837A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF724F3B5A0 tbb::internal::task_group_base::wait C:\\blender-git\\blender\\intern\\cycles\\util\\util_task.cpp:168\nblender.exe :0x00007FF727F86DB0 ccl::TaskPool::wait_work\nblender.exe :0x00007FF725E7BFC0 ccl::Session::run_cpu C:\\blender-git\\blender\\intern\\cycles\\render\\session.cpp:738\nblender.exe :0x00007FF725E7BB80 ccl::Session::run C:\\blender-git\\blender\\intern\\cycles\\render\\session.cpp:776\nblender.exe :0x00007FF727F89680 ccl::thread::run C:\\blender-git\\blender\\intern\\cycles\\util\\util_thread.cpp:53\nblender.exe :0x00007FF72567F910 std::thread::_Invoke<std::tuple<void (__cdecl ceres::internal::ThreadPool::*)(void),ceres::internal C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\thread:44\nucrtbase.dll :0x00007FFD80F90D40 beginthreadex\nKERNEL32.DLL :0x00007FFD81B97BC0 BaseThreadInitThunk\nntdll.dll :0x00007FFD83AECE30 RtlUserThreadStart```\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", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Bump Map and Normal Map causes flat shading.\nOperating system: windows 10 1903\nGraphics card: 1080ti * 2\n\nBroken: 2.82.7 stable versioin\n\nThis issue appears both on eevee and cycles.\nWhile using smooth shading, simply add a bump map and the shading lookes flattened.\n\n\nThis problem will occur on a high poly model if the camera is close enough.\n\n\nBevel the cube with several segments and simply plug a bump map to the normal port of the shader node.\n\n[smooth shading issue.blend](smooth_shading_issue.blend)", "Unable to undo subdivision with Multiresolution modifier\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 2.93.6\n\n**Bug**: If i subdivide with Multiresolution modifier after a sculpt action it doesn't undo subdivision but it needs to undo the sculpt action to undo that subdivision done with Multisolution modifier.\n**Note**: If no sculpt action is done before subdivision with Multiresolution modifier, the undo for subdivision just works (No need to undo the action done just before the subdivision to get the result back).\n**Mode** : Sculpt\n\n**Steps**:\n1. File> New> Sculpting. \n2. Add Multiresolution modifier.\n3. Sculpt with Grab brush.\n4. Subdivide once at Multiresolution modifier.\n5. Undo (Doesn't work).\n\n**File**:[Multiresolution_subdivision_bug.blend](Multiresolution_subdivision_bug.blend)\n\n", "Wrong editor type saved in workspace\nOperating system: Win11\nGraphics card: AMD Radeon (TM) Graphics (Included Graphics)\n\nBroken: 3.5.1\nWorked: N/A.\n\nMy properties editor is glitched and keeps resetting to nonlinear animation editor.\n(When saving file and reopening)\n\nIdk how to repreduce it, but here are steps for my blender file:\n1. Switch editor type to properties editor.\n2. Save file.\n3. Close blender .\n4. Open the saved file.\n5. Properties editor switched to nonlinear animation editor.\n6. (When repeating 1-4 with all objects deleted, then its working normally without the switch at restart).\n7. Viedeo: EDgFd6MIzjM.\n\n", "Voxel Bug Holes after Remesh\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\n\nVoxel Bug Holes after Remesh\n\n\nClick on Voxel Remesh, I think any voxel size produces the same result.\n\n\nI tried on default sculpt spear it works fine that way but not on the model I am using.\n\nThe model was originally produced from Reality Capture software, then I cleaned it up using decimate and smooth modifier. I fixed the details and did some more cleaning in Sculpt Mode. Unfortunately when I tried Remesh this issue happened.\n\nThank you in advance.\n\n[VeniceBaseSculptingVoxelBug.blend](VeniceBaseSculptingVoxelBug.blend)\n\n", "Wrong SubSurf modifier results with inconsistent normals\nOperating system: Windows 10 Enterprise Version 1803\nGraphics card: 2 x GTX1080 ti\n\nBroken:\nblender2.8, 2018-12-05\n\nFrom latest builds subsurf modifier make a wrong subdivision of geometry as displayed in the attached files.\nBefore 18/20 November the behaviour of subsurf modifier was ok.\nI am sure because I did an animation on that date and the subdivided vase was ok.\n\nBest regards,\n\nUmberto\n\n\n\n\n\n[ceramic.blend](ceramic.blend)", "Sculpt, Mask extract with certain mesh produces broken mesh (hidden geometry)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nMesh made as «mask extract» from sculpt, then I fill and triangulated top.\nIt looks like mesh contains non-selectable geometry, that prevents to make proper operation Origin to geometry.\nTry to do it. Origin will stay at the same place.\n\nAfter exporting obj and importing back bug gone. After remesh too.\nIt is the second time, I`ve encountered such issue.\nMay be related to #82209 (Blender hanging with «separate selection» in particular model/file (svg imported).)\n\n[mesh.blend](mesh.blend)\n\n[2021-03-24_11-40-49.mp4](2021-03-24_11-40-49.mp4)\n\n\n\n", "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", "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", "clay strip brush (and probably any brush) create some strange shading and geometry artifacts...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\n\nclay strip brush (and probably any brush) create some strange shading and geometry artifacts...\n\n1. open blender, subdivide the default cube in edit mode a few times,\n2. add subdiv modifier with 3 levels (25,1 million in total) and apply modifier.\n3. go to sculpt mode and start playing with the clay strip brush and brush settings a little bit...\n4. change the sculpt plane to view plane, and add a stroke continuously in the edge of the cube, and some transparent shading bug appears when i go to check the back side of the stroke made, but this get fixed when i use the smooth brush a little bit in those boundary edges...\n\n\n5. change the sculpt plane to area plane again, and try on other edge the same again, and some grid topology starts to appear suddenly in the first stroke when drawing, but when i keep drawing it was less noticeable the artifact but was still there...\n\n\n\n", "Subdivision modifier breaking custom normals.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.6.0 Core Profile Context 23.7.2.230718\n\nBroken: version: 4.0.0 Alpha (Also tested in v3.5.0 & v3.6.1)\nWorked: N/A\n\nIdentical normals are slightly messed up when a subdivision surface modifier is enabled, breaking cell shaders.\n\n1. Download the attached .blend file\n2. Change Viewport Shading to \"Rendered\"\n3. Enable/Disable the subdivision surface modifier.\n4. You might need to rotate the light slightly on the x-axis.\n\n\nSome notes:\n- All mesh normals were copied and pasted via \"Mesh/Normals/Copy Vector\" and \"Mesh/Normals/Paste Vector\".\n- \"Subdivision modifier/Use Custom Normals\" property is enabled.\n- Changing \"Render/Performance/High Quality Normals\" or \"Subdivision modifier/Use Limit Surface\" changes alters where the issues appear on Suzanne. (Sphere is unaffected.)\n- Issue doesn't occur on flat meshes.\n- Even after applying the modifier, repasting normals still leaves some artifacts.", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Undo/Redo if Sculpt Mode toggle doesn't have Undo History produces Draw Brush in Sculpt Mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha\n\nUndo/Redo if Sculpt Mode toggle doesn't have Undo history produces Draw Brush in Sculpt Mode\n\nCreate new 2D animation project\nInstall the following addon, which binds a \"gpencil.sculptmode_toggle\" with no Undo history to \"LEFT_CTRL\" and \"ed.undo\" to \"D\" \n[no_undo_sculpt.py](no_undo_sculpt.py)\nDraw lines in paint mode\nHold \"LEFT_CTRL\" to switch to sculpt mode, press \"Z\" to undo\nDraw brush is now in Sculpt Mode\nAlso affects redo if you use \"D\" to undo and not switch to Sculpt Mode, use \"CTRL+SHIFT+Z\" to redo\nWhile in this state, pressing \"TAB\" to switch modes produces \"Unable to execute 'Strokes Sculpt Mode Toggle', error changing modes\"\nPressing \"TAB\" again switches to Object Mode\n[2021-04-08 16-51-03-00.00.00.000-00.00.28.016.mp4](2021-04-08_16-51-03-00.00.00.000-00.00.28.016.mp4)", "Dyntopo: detail flood fill with smoothed mask expands too much\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\n\n\n[#78755.blend](T78755.blend)\n- Open file\n- Dyntopo > Detail Flood Fill (this is still expected, sticks to unmasked area)\n- Undo\n- Mask > Smooth Mask (this already has a bit of an unexpected shape)\n- Dyntopo > Detail Flood Fill (this spreads out)\n\nTo reproduce: create icosphere with 5 subdivisions, mask spot, invert mask, soften mask, make detail flood fill\n[2020-07-09_09-38-22.mp4](2020-07-09_09-38-22.mp4)" ]

[ "Undo after remeshing or dyntopo creates a flat shading on normals\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nCaused by d9c6ceb3b8\nFixes c8814fb610 & 9ce1135440 apparently were not enough to fix this all the way\n\nSimilar to #95185, after using undo the normals break. but in this case, it happens after you undo a remesh or a dyntopo\n\n- Open .blend file\n- Switch to sculpt mode\n- Remesh or Sculpt with dyntopo\n- then ctrl+z\nTest File:\n[#95843.blend](T95843.blend)\n[2022-02-17 13-16-52.mp4](2022-02-17_13-16-52.mp4)\n\n" ]

[ "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)", "Crash 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)", "use after free Fluid sim seg fault\nIn Debian testing, and Debian stable.\n\nbroken: blender 3.0.0 f7b22fc3d27113715e8726c69ab3264e1d487439\nbroken: Blender 2.93.0, Commit date: 2021-05-10 22:16, Hash ce62d650945f \nbroken: blender 2.92\n\nSegfaults on bake of modular fluid sim.\nReproducible each time I run blender on it.\n(Building a debug build now. the crash text isn't so useful yet).\n\n1. Load .blend (attached)\n2. Bake fluid\n3. Segfault\n\n[flu.blend](flu.blend)\nAsan report on f7b22fc3d27113715e8726c69ab3264e1d487439 [T88475_asan_use_after_free.txt](T88475_asan_use_after_free.txt)\nTwo crash reports on blender 2.92: \n[Blender_2021-05-22-145034_MACBOOKAIR.crash](Blender_2021-05-22-145034_MACBOOKAIR.crash)\nSimilar to #88113#1157996: [Blender_2021-05-22-193554_MACBOOKAIR.crash](Blender_2021-05-22-193554_MACBOOKAIR.crash)", "Blender stops updating display after GPU spike\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 2.92.0 Beta\nWorked: I have not found a version that works as expected on this computer. I have tried 2.79, 2.8, 2.91\n\nI was premature in saying the problem is gone for [#85061 ](T85061).\n>After a few minutes of using Blender, the window freezes. Windows does not detect that it is not responding, but Blender does not respond to any input, including clicking on the close button. All elements that are drawn by Blender remain as they were at the moment of the crash except if I resize the window smaller.\n\nIf I watch the performance tab on Windows Task Manager, the freeze coincides with a 100% spike on the GPU.\nAs long as that spike doesn't happen, there is no problem, but once it does, Blender stops responding to any input, but it does not crash.\nI have updated my graphics drivers.\n[blender_debug_output.txt](blender_debug_output.txt)\n\nI have not determined exact steps. It has occurred on multiple files doing multiple different tasks. As far as I can tell, there is no correlation between what I am working on or what task I am performing, and the error occurring.\n", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "Vega GPU crash during render\nOperating system: Debian 11 bullseye x86_64 Linux 5.10.0-17-amd64\nGraphics card: gfx900 AMD/ATI Vega 10 XTX [Radeon Vega Frontier Edition]\n\nHip info: \n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release hipconfig\nHIP version : 5.2.21152-4b155a06\n\n== hipconfig\nHIP_PATH : /opt/rocm-5.2.1\nROCM_PATH : /opt/rocm-5.2.1\nHIP_COMPILER : clang\nHIP_PLATFORM : amd\nHIP_RUNTIME : rocclr\nCPP_CONFIG : -D__HIP_PLATFORM_HCC__= -D__HIP_PLATFORM_AMD__= -I/opt/rocm-5.2.1/include -I/opt/rocm-5.2.1/llvm/bin/../lib/clang/14.0.0 -I/opt/rocm-5.2.1/hsa/include\n\n== hip-clang\nHSA_PATH : /opt/rocm-5.2.1/hsa\nHIP_CLANG_PATH : /opt/rocm-5.2.1/llvm/bin\nAMD clang version 14.0.0 (llvm-project roc-5.2.1 22204 50d6d5d5b608d2abd6af44314abc6ad20036af3b)\nTarget: x86_64-unknown-linux-gnu\nThread model: posix\nInstalledDir: /opt/rocm-5.2.1/llvm/bin\nAMD LLVM version 14.0.0git\n Optimized build.\n Default target: x86_64-unknown-linux-gnu\n Host CPU: znver2\n\n Registered Targets:\n amdgcn - AMD GCN GPUs\n r600 - AMD GPUs HD2XXX-HD6XXX\n x86 - 32-bit X86: Pentium-Pro and above\n x86-64 - 64-bit X86: EM64T and AMD64\nhip-clang-cxxflags : -std=c++11 -isystem \"/opt/rocm-5.2.1/llvm/lib/clang/14.0.0/include/..\" -isystem /opt/rocm-5.2.1/hsa/include -isystem \"/opt/rocm-5.2.1/include\" -O3\nhip-clang-ldflags : -L\"/opt/rocm-5.2.1/lib\" -O3 -lgcc_s -lgcc -lpthread -lm -lrt\n\n=== Environment Variables\nPATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/home/ian/.local/bin\n\n== Linux Kernel\nHostname : *****Linux***** 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux\nNo LSB modules are available.\nDistributor ID:\tDebian\nDescription:\tDebian GNU/Linux 11 (bullseye)\nRelease:\t11\nCodename:\tbullseye\n```\n\nBroken: blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release\nWorked: N/A\n\nBlender crashes when attempting to render more complex scenes on Vega GPU.\n\n[lone monk demo](lone-monk_cycles_and_exposure-node_demo.blend)\n./blender ../lone-monk_cycles_and_exposure-node_demo.blend\nrender on gpu\n\n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | tee log.txt\nRead prefs: /home/ian/.config/blender/3.3/config/userpref.blend\nRead blend: /home/ian/Downloads/lone-monk_cycles_and_exposure-node_demo.blend\nWARNING: Shader warning [node_vertex_color]: Invalid attribute.\nMemory access fault by GPU node-1 (Agent handle: 0x7f2683fa6400) on address 0x7f2400000000. Reason: Unknown.\n[1] 25965 abort ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | \n 25966 done tee log.txt\n```\n\n```\n:0:rocdevice.cpp :2652: 2702732952 us: 249488: [tid:0x7f1dd0b76640] Device::callbackQueue aborting with error : HSA_STATUS_ERROR_MEMORY_APERTURE_VIOLATION: The agent attempted to access memory beyond the largest legal address. code: 0x29\n[1] 249488 abort ./blender --factory-startup --debug-all\n```", "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", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "Crash 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", "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 Instantly Crashes When Rendering Cycles Or Clicking Wrong Setting\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nCPU: 12th Gen Intel(R) Core(TM) i7-12700KF, 3600 Mhz, 12 Core(s), 20 Logical Processor(s)\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.1.230821\n\nBroken: version: 3.6.2\n\nWhenever Blender attempts to render in cycles mode it exits immediately. It doesn't try for a few seconds, there's no loading, just click and instantly the process dies. This happens whether Preferences>System>Cycles Render Devices is set to \"None\", \"HIP\" with my GPU selected, or \"HIP\" with my CPU selected. Regardless of the cycles render device setting when I turn on viewport shading it works as it defaults to Eevee. However, if I try to change it to cycles, the moment I click cycles Blender crashes.\n\nThis same instant crash happens when I try to click OptiX or CUDA in Preferences>System>Cycles Render Devices instead on None or HIP.\n\n\n- Start Blender with a default project\n- Press Z then 8 to go into rendering mode\n- On the sidebar click render properties\n- Click the dropdown to change render engine\n- Click Cycles\n- Should see it crash instantly\n\nTo see the settings crash\n- Start Blender with a default project\n- Navigate to Edit>Preferences>System>Cycles Render Devices\n- Click between None, HIP, and OneAPI without issue\n- Click CUDA or OptiX and see the instant crash\n\n", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n", "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n" ]

[ "Crash during launch\nOperating system: Linux Mint 19.3 Tricia, x64, updated\nGraphics card: NVIDIA Titan 24GB + Quadro 2000 5GB\n\nBroken: blender-2.83-6fff73e3f001-linux-glibc217-x86_64\nWorked: unpacking the archive\n\nCrash: SIGSEGV in SEGV_MAPERR, si_addr=0x137\n\nUnpack 2.83 alpha form developers red corner, run in system Linux using mate-terminal console. Crash is immediate.\n\nIncluded are strace output with blender -debug-all option, ldd output and inxi output with extended info about the machine.\n[strace.txt](strace.txt)\n\n[ldd.txt](ldd.txt)\n\n[inxi.txt](inxi.txt)" ]

[ "Sculpt crash in certain scenario (PBVH vert number does not match)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.6\n\nCrash upon altering the model in any way.\n\n1. Open file\n2. Use a tool/brush to alter the model.\n3. Instant Crash\n\nI have updated GPU drivers and the latest Blender version as of today, still crashes.\n\nCould not find any duplicate bugs of crashes when interacting with models, only crash on startup and others. \n\nI expect my GPU is just too trash.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Goblin.crash.txt](Goblin.crash.txt)\n\n[Goblin.blend](Goblin.blend)\n", "Node Editor gets unusably slow in scenes of average production complexity\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.1.2\nWorked: Probably never\n\nThe node editor, as well as other parts of Blender get unusably slow when the scene complexity reaches level of average production scenes from about 5-10 years ago (About 30 million triangles on average). This even includes the operations, which should not require re-evaluation of the entire complex scene dependencies, such as moving unconnected nodes in the shader editor.\n\n[SlowScene_Base.blend](SlowScene_Base.blend)\n1. Open the attached .blend file:\n2. Select all the objects in the scene and convert them to meshes using Object->Apply->Visual Geometry to Mesh (this step was necessary to keep the repro file size small)\n3. Attempt regular material editing operations in shader editor, such as adding nodes, moving nodes around, editing properties of nodes, such as color ramp sliders, and so on\nResult: The constant UI blocking freezes make it impossible to work with the node editor when scene complexity exceeds trivial level.\nExpected: The performance of the node editor remains acceptable in the scenes of production complexity.\n\nNote: Feel free to duplicate the objects in the viewport to increase the severity of the lags and freezes.\n\n---\n\nBit of research: this is because of UNDO.\n\nIf you turn OFF `Global Undo` in the Preferences (or set `Undo Steps` to zero) everything is back to being snappy fast.\nNot sure if this can be smarter, but this does make sense in a way because Global Undo keeps a copy of the whole file in memory?", "Script node with shader output crashes Eevee\nOperating system: OSX Monterey (12.6)\nGraphics card: Radeon Pro Vega 20\n\nBroken: git versions: blender-v3.2-release, blender-v3.3-release, master\nWorked: 3.2 release\n\nI'm testing the MaterialX standard surface shader. It seems to work when in Release versions, but in a debug build, it crashes when you connect the output of the shader to 'surface' in the terminal node.\n\nUsing the default scene, switch from Eevee to Cycles + Open Shading Language. Select the Cube, switch to Shading tab. Create a new material, and add a new Script node. Load the attached .oso file (to compile the attached .osl, you need to have MaterialX installed. I'm using 1.38.5). Attach the output of the script node to the 'Surface' input of the terminal. Boom! Where the crash occurs depends on whether your in Eevee preview, or Cycles preview.\n\n[out.osl](out.osl)\n\n[out1.oso](out1.oso)", "Python API docs Error\n\nI'm not sure that it needs to be sent here\n\nThe Python API Docs contains an error - it says that blender as a python module need to be compiled independently. but this has not been the case for a long time\n\n\n\n", "Addons in custom scripts path do not get loaded without restarting blender\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 520 Intel 4.5.0 - Build 31.0.101.2115\n\nBroken: version: 3.6.2\nWorked: none\n\n\nWhen adding a custom script directory the addons can not be enabled unless blender is restarted.\n\n\n1. make a scrips folder\n2. add a subfolder called addons\n3. put a addon in there\n4. open blender\n5. add a new scripts directory to the scripts folder created in #1\n6. go to the addon panel and find the addon.\n7. trz to enable the addon\n8. this throws a python error\n`Traceback (most recent call last):\n File \"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\3.6\\scripts\\modules\\addon_utils.py\", line 333, in enable\n mod = __import__(module_name)\nModuleNotFoundError: No module named 'modifier_list'\n`\n\n\n", "Node editor: Allow editing geometry node tree without context\nLike the \"Material/World\" toggle in the shader editor, add an option to allow choosing any node group regardless of the context.\n\n", "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.", "Native addons lose the \"Report a bug\" button when using a custom Config folder\nOperating system: Windows\n\nBroken: 4.0\nWorked: -\n\nReport by @Todor-CGDive (moved from 104635).\nPre-installed addons have a \"Report a bug\" button. However, if you create a custom Config folder, that button changes to \"Remove\". I am not sure if that's by design but it looks suspicious.\n\n\n- On Windows, go to directory `%USERPROFILE%\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\` and copy de `config` folder\n- Past it in the your blender installation directory `/4.0` folder\n\n", "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", "Application templates crashes if the startup.blend of the application template contains scene named \"Asset\"\nOperating system: Windows-10-10.0.22621-SP0'\nGraphics card: NVIDIA GeForce RTX 2070 Super with Max-Q Design/PCIe/SSE2\n\nBroken: 3.5.1 2023-04-24 18:00 e1ccd9d4a1d3\nWorked: Never\n\nApplication templates that contain certain pattern in startup.blend lead to Blender to crash.\nApparently occurs when the scene is created with the name \"Asset\" and used as a application template.\n\n- Download attached [MCE.zip](attachment) file\n- Install the attached application template file (`Blender` menu > `Install Application Template...`).\n- Load it (choose the new \"MCE\" option in `File` > `New`).\n\nBlender crashes.\n\nAttached also the `blender.crash.txt` and another template.\n\n[MCE.zip](attachment)", "Geometry Nodes: writing attributes (from procedurally created geometry) to vertex groups not working\nOperating system: macOS Monterey 12.4\nGraphics card: RX 6800 XT\n\nBroken: 3.1 & newer\nWorked: 3.0.1\n\n\nIn Blender 3.0.1, it was possible to write attributes from procedurally created geometry (created by geometry nodes) to vertex groups, as long as the \"Group Input\" node was joined with the procedural geometry. However, no version newer than 3.0.1 seems to have this capability. From what I understand, this may have been done intentionally in anticipation of attributes replacing vertex groups entirely... but it seems odd to kill this feature before that transition is complete, so I'm reporting this as a bug.\n\n\nOpen the attached .blend file in Blender 3.0.1:\n[geonodes_attrib_to_vgroup.blend](geonodes_attrib_to_vgroup.blend)\nThis file contains a geonodes setup where half of a procedurally generated grid is extruded using a solidify modifier. The \"geonodes\" object should look exactly the same as the \"Expected Result\" object. \n\nNext, open the file in Blender 3.3 (or 3.1, or 3.2) and notice how the \"Expected Result\" object no longer matches the \"geonodes\" object.\n", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Skipping node auto-attachment doesn't work with custom keymap\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nBy default holding `ALT` while dragging a node disables auto-attachment. However, this doesn't work when using a custom keymap that has been imported from previous version. The prompt doesn't show which key to hold, and holding `ALT` just makes the prompt flicker like crazy, but doesn't disable auto-attachment.\n\n\n\n\n**Steps to reproduce the bug**\n\n - Switch to a keymap that has been created with an earlier Blender version\n - Move a node in any node editor\n - Hold `ALT`\n\n\n\n", "Objects with physics referred to by PointerProperty throw find_node_operation: Failed for (RIGIDBODY_REBUILD, '') when rendering\nOperating system: Ubuntu 20.04, Windows 10\nGraphics card: GeForce GTX 2080, GeForce GTX 1080\n\nBroken: 3.1.2\nWorked: Unknown\n\n\nWhen you have a PointerProperty, and that property refers to an object that has a rigid body, the following is output to the console when rendering:\n\n```\nfind_node_operation: Failed for (RIGIDBODY_REBUILD, '')\nadd_relation(Rigid Body Rebuild -> Point Cache Reset) - Could not find op_from (OperationKey(type: TRANSFORM, component name: '', operation code: RIGIDBODY_REBUILD))\nadd_relation(Rigid Body Rebuild -> Point Cache Reset) - Failed, but op_to (ComponentKey(OBBox, POINT_CACHE)) was ok \n```\n\nThis doesn't seem to have any other adverse effects, as rendering still succeeds with the object in the correct simulated position, but these types of messages fill up the console extremely quickly.\n\nOpen the following blend file, and render a frame. For some reason this requires the file to be opened via the UI.\n[repro2.blend](repro2.blend)\nAlternatively, unzip the following and run with `blender -b --python repro.py`.\n[repro.zip](repro.zip)\n", "Tangent node used as a vector on Texture Nodes yields nothing through a Bump Node\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nIf you plug a tangent node into any procedural noise texture as the vector, it will work, however once you plug the result into a vector bump node it will draw as an empty bump map. \n\n1. In the shading workspace, grab a noise texture\n2. Grab the tangent node and plug it into the noise textures vector input. Any tangent mode will do fine (x,y,z)\n3. Grab a vector bump node and plug the noise texture into height. \n4. View the resulting bump, nothing will be yielded (however if plugged into the normal input it will)\n[Example.blend](Example.blend)\n" ]

[ "CustomNodeTree throws constant warnings when socket is added\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.0.0\nWorked: 2.93\n\nWith custom nodetrees if you add a single node into the node tree and the node tree is visible in an area a warning about the nodetree.type enum being set to something that doesn't exist constantly shows up in the system console.\n```\nWARN (bpy.rna): C:\\Users\\blender\\git\\blender-v300\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1352 pyrna_enum_to_py: current value '-1' matches no enum in 'CustomTreeType', 'NodeTree', 'type'\n```\n\n- Open a new blend file in Blender 3.0\n- Run the 'Custom Nodes' template in the Text Editor\n- In sidebar, add socket in groups tab \n\nI understand this might not be technically an error but it makes debugging custom nodetrees difficult as any errors are quickly whisked away up the terminal window by these warnings. As well as this is from a deprecated attribute.\n", "`group` tab in custom node tree types\nOperating system: Windows 10\nGraphics card: Nvida RTX 2030\n\nBroken: 3.4.1, ef9ca44dee7f, as found on the splash screen\n\nConsole spams `WARN` messages when using custom node types using python scripts.\n`WARN (bpy.rna): C:\\Users\\blender\\git\\blender-v340\\blender.git\\source\\blender\\python\\intern\\bpy_rna.c:1341 pyrna_enum_to_py: current value '-1' matches no enum in 'CustomTreeType', 'NodeTree', 'type'`\n\nThis happens when `group` tab is opened in the custom node tree editor side panel and input sockets or output sockets are added.\n\n\n**1. Creating a custom node type**\n- Create a new Blend file.\n- Open a new text editor window.\n- Create a new text file and browse the `Templates` for `Python -> Custom Nodes` .\n- Run the `Custom Nodes` script to create a new custom node type\n\n**2. Creating a new custom node tree**\n- Open the `Custom Node Tree Editor` and create a new node tree.\n\n**3. Adding group node sockets**\n- Open the `group` tab in the side panel.\n- Add an input or an output socket. \n\nThis will spam the Blender system console with the above `WARN` messages.\n" ]

[ "Toggling edit mode messes with active attribute\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 3.6.0 Alpha\n\nToggling edit mode does not properly preserve the active attribute.\n\n\n\nFrom default startup:\n- go to attribute panel\n- select UVMap as active\n- go to edit mode\n- nothing is active\n\n", "No Vector Displacement On Instances\nWindows 10 x64\n\n2.79.4\n\nVector displacement doesnt work with instances, It mirrors the displacement on the first object, Im sure this is working as intended but there are many cases where you need to displace actual instances as well.\n\nHaving a checkbox somewhere to enable instance displacement would be amazing\n\n\n\n\n\n[instances.blend](instances.blend)\n", "Sculpting: Shape Keys: Sculpting should show the mesh using a shape key value of 1\nOperating system: Linux-5.3.0-46-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.8\n\nBroken: version: 2.90 (sub 2)\n\n\nSculpting: Shape Keys: Sculpting should show the mesh using a shape key value of 1.\nThis should work similarly to when enting edit mode while using shape keys;\nthe mesh should shown using a value of 1 and the value slider in the shape key panel should be greyed out.\n\nThis was found with [D7826](D7826)\n\n\n- . Create base shape key and a second key\n- . modify the mesh of the second key \n- . set value to 0\n- . Enter edit mode and then sculpt mode comparing the differences.", "Regression: Curve wire line not displayed in edit mode when it has evaluated mesh/point/volume\nBroken: 3.0, 3.1, 3.2\nCaused by b9febb54a4\n\nThe original line for edit mode curves is not displayed in edit mode .\n\nThis change only applies when the curve is changed during evaluation, for example, when it is replaced by an evaluated \"tube\" mesh, or points, or a volume, etc.\n\n| Before | After |\n| -- | -- |\n|  |  |\n(Ignore the change in lightness there, it's just a different UI scale)", "object display as wire , invisible when overlay is turned off \nwin 10\nintel i5\namd radeon \n\nblender 2.8 \n6b39dc7672eb\n\n\nNot sure if it's abug or intended behaviour \n\nWhen an object is set to wireframe ( object properties , viewport display ) , when overlays is turned off , the object is not shown ", "Grease pencil edit mode proportional edit \"connected\" bug\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nProportional edited vertices from a mesh behave different when editing in \"only connected\" than GP points do. Mesh points (vertices) calculate the influence by the length of the path, while GP strokes react as soon as they get into the influence circle.\nTheleft rectangle in the picture is a mesh, the rectangle on the right is a grease pencil object. Notice how the points react differently.\n\n\n\n[ProportE.bug.blend](ProportE.bug.blend)", "Copy/Paste Behavior in Viewport\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.91.0 Alpha\nWorked: Never worked in 2.8+\n\nWhen pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended.\nThe pasted object also is not active for direct manipulation despite the visual indication with the gizmo.\n\nIf there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example:\n\n\nIf there is no selection before pasting, there is no gizmo appearing at all. Example:\n\n\nA directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example:\n\n\n**Potential fix**\n1. The gizmo could always appear and show where the object is pasted (belonging to the new object).\n2. The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting.\n\nThank you :)\n", "Curves edit mode extend/extrude operator\nTo replace the extrude operator in the legacy curve edit mode.\n\nOne potential simplification is only allowing extrusion from the end points. But for a final implementation that covers all use cases, extruding from curve midpoints is probably necessary.\n\n", "EEVEE: Spotlight Parented To Scaled Object Behaves Incorrectly\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: Blender 2.82a, 2.90 alpha eaf7d36d66e5\n\nIn EEVEE, Spotlights parented to a scaled object cast an incorrect shape once they are rotated.\nThe viewport overlay, however, indicates the correct shape.\n(Note: This does not apply to Cycles, see #76823)\n\n[spotlight_ellipse_parented.blend](spotlight_ellipse_parented.blend)\n\nSet view to rendered.\n\nThe scene has a Spotlight (unscaled, not rotated) parented to an Empty (scaled).\nThis results in an elliptical spot.\n\nHowever, if the Spotlight is rotated around its Z-Axis, the spot's shape should stay identical. (As indicated by the overlay.)\nBut it does not.", "Edges created by a bevel modifier are visible even for hidden items in edit mode (in wireframe display)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I did not follow it back to n previous versions.\nThe Problem is also reproducable in the latest nightly e362a2f0d41f\n\n\nIn mesh editting mode, if you hide an edge that is affected by a bevel modifier, the edges created by the bevel modifier are still visible. I expect them not to be visible because the edge is hidden.\n\n\n1. Open the attached file.\n2. There is one mesh in edit mode. One of the edges is affected by a bevel modifier.\n3. One face is already selected. Press Shift+H to hide all unselected items, including the aformentioned edge.\n4. You still see the result of the bevel modifier even if the edge is hidden. I expect it not to be visible. \n\nIn practice, this caused many confusing \"ghost\" lines of invisible items.\n\n", "UV Editor Tools Todo\n\n\n# UV Editor\nCurrently, the UV editor has a bunch of confusingly overlapping tool-modes. This should all be simplified via the new active tools system.\n\n * - [x] {icon circle color=red} Add Radius, Strength and the other relevant UV Sculpt settings to the tool settings & top bar\n * - [x] {icon circle color=red} Add Move tool to the toolbar\n * - [x] {icon circle color=red} Add Rotate tool to the toolbar\n * - [x] {icon circle color=red} Add Scale tool to the toolbar\n * - [ ] {icon circle color=red} Add Scale Cage tool to the toolbar\n * - [x] {icon circle color=yellow} Add Pan & Zoom gizmos in top right corner, same as 3d view.\n * - [x] {icon circle color=green} Add the Placement option to the Annotate tool settings (Current default is to only draw in the view, which is not so useful)\n * - [ ] {icon circle color=green} Add Shear tool to the toolbar\n * - [x] Split UV Editor from Image Editor\n * - [x] Remove old tools panels \n * - [x] Add 2D Cursor tool to toolbar\n * - [x] Add Transform tool to the toolbar\n * - [x] Make the Transform Scale Cage Gizmo only appear when Scale Cage transform tool is used\n * - [x] Fix Annotate tool in the toolbar, so that it actually works\n * - [x] Add UV Sculpt tools to the toolbar \n\n\n\nWhen in the Image Editor Paint Mode, we should follow the design of the Paint modes in the 3D View, meaning;\n\n * - [x] {icon circle color=red} Tool Settings should be in top bar\n * - [x] {icon circle color=red} Toolbar should work the same as in 3D View\n\n", "Mask invisible on object with modifiers when entering sculpt mode\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: unkown\n\nWhen selecting a previously unselected object with a modifier and a sculpt mask, the mask is invisible at first when entering sculpt mode.\nPainting the mask reveals it.\n\n- Create an object with a modifier (e.g. mirror or array) and paint a sculpt mask on it. Or use the file attached.\n- Outside the sculpt mode first make sure the object is unselected, then select it and enter sculpt mode.\n- The object appears with no mask visible, still you can not sculpt the masked parts.\n- Painting the mask reveals it.\n\n[mask.blend](mask.blend)\n\n[mask.mp4](mask.mp4)", "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", "Bent concave 2D curve triangulation problem w/ modifiers applied\nBroken: 2.80\n\n[BUG.blend](BUG.blend)\n\n(I think the problem is triangulation)\nTriangulation sometimes has problems with concave shapes, and I believe this is caused by triangulation (without overlaps) being much more difficult in 3d than 2d. But the problem shouldn't really exist (at least in my case) because the triangulation would work fine using 2D triangulation by projecting the points to 2d along the average normal of the face (it bends less than 90 degrees, so 2D triangulation would be perfect).\n\nOpen the project, the shape is completely wrong on the flat faces when using the curve modifier. It's supposed to be a concave crescent shape, instead of the convex hull sorta shape it has now.", "Curves edit mode radius editing\nThis consists of two features, a connection to the \"Shrink-Fatten\" transform mode and a corresponding active tool in the sidebar. \n\n\n\n" ]

[ "E shortcut prop moves instead of extrudes\nOperating system: Windows 10\nGraphics card: 1080\n\nBroken: 546e20f5a2c0\nWorked: \"a few months ago...\"\n\nPressing E to extrude enables proportional move. It also actually performs the extrude, because pressing G immediately after does show a second vertex/face/edge.\n\n1. Add a cube\n2. Edit and select a vertex/face/edge\n3. Press E and move the mouse\n\nResult:\n\nYour selection moves AND the proportinal editing circle pops up (and can be resized).\n\nExpected result:\n\nAn extruded version of your selection should move.\n\nComment:\n\nSince prop mod is currently being developed, did someone accidentally leave debug functonality in today's build?", "Extrude has proportional editing turned on all the time in the latest build resetting to factory defaults doesn't help\nOperating system: Windows 10 64-bit\nGraphics card: Nvidia Geforce GTX 1070 8 gb Vram\n\nBroken: blender-2.80.0-git.546e20f5a2c0-windows64\nWorked: blender-2.80.0-git.b46245470f79-windows64\nAlso worked fine with yesterday's build (April 29th)\n\nHello, wonderful Blender devs! I have encountered weirdest bug ever imagined. As soon as I downloaded today's build I've encountered weirdness with the way extrude function works. It seems that extrude function now has proportional editing turned on all the time without the ability to turn it off! I have tried resetting Blender to factory defaults and the error persists =((.\n\nI have made a video with commentaries:\n[Proportional_Editing.flv](Proportional_Editing.flv)\n\nOpen any file,\ngo to edit mode\nstart extruding any object, whether it's a face, vertex, edge\nSee that proportional edit is on all the time preventing you from having normal extrusion\n\nSee video for details:\n[Proportional_Editing.flv](Proportional_Editing.flv)\n\nI don't know if it's happening only on my machine, but that's weirdest thing ever =))." ]

[ "UDIM grid changes and enhancements\nThe UDIM tile grid behaves oddly/inconsistently in many circumstances for both configuration and display. This design tasks will hopefully a) enumerate the most egregious issues b) provide a place for artist feedback on the proposals c) document the ultimate decision for each item below.\n\nComplete\n- [x] The UV tile grid no longer disappears as soon as an image is loaded into the UV editor space (4fb7217043)\n- [x] [D11862](D11862): Provide a way to disable the grid entirely and respond to the Overlay toggles. Move current UI into Overlay panel as well. \n\nFuture design / discussion required\n- [ ] Should the tile grid only have manual/static dimensions or should it automatically adjust if the user moves a UV point outside the current dimensions of the grid?\n- [ ] Should the tile grid also be shown in the Paint/Mask/Viewer modes in addition to UV edit?\n- [ ] Should anything different be done about the grid when displaying non-square images?\n\nFeedback thread: 20136\n\nThis task will be used for general organization. Most feedback should be provided on the DevTalk thread above.", "Inconsistency of some tools/operators (e.g. Subdivide) in regards to hidden geometry\nBroken: all or none\n\nI'm not really sure this is even an issue, though it feels like it. As far as I understand it, mesh editing tools are not supposed to affect hidden geometry. But the Subdivide tool does. Consider this mesh:\n\n\nIf you hide the middle face...\n\n\n...and then Subdivide the two remaining faces...\n\n\n...Subdivide will create new edges cutting through the hidden face, also creating inconsistent selection (i.e. selected edges in face select mode). Shouldn't the operator check that that face is hidden and not create edges through it?", "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", "Texture paint undo sometimes changes texture slot\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 2.80 (sub 48), 2019-03-12 13:53, hash: 936014ea8c74\n\nWhen texture painting on a particular texture slot, then undoing that painting, sometimes the selected paint slot will change.\n\nI couldn't reproduce from the default startup file, so I've stripped down the file that's having problems as much as I can.\n\n1. Open attached file\n2. Select paint slot \"Skin mask\" from either topbar or properties panel.\n3. Paint some strokes on the model or image editor\n4. Press Ctrl-Z\n5. Notice the paint slot is no longer set to \"Skin mask\"\n\n- - -\n\n- Change to the Skin Mask slot.\n- Paint a single stroke in the image editor.\n- Undo two times.\n- Paint another single stroke in the image editor.\n- Undo one time.\n- Notice that the slot changed.\n[texturepaintbug.blend](texturepaintbug.blend)", "Multires the Apply Base add to Quick Favorites can't change mesh.\nOperating system:Windows-10-2004 64 Bits\nGraphics card:GeForce RTX 2080 Ti/NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-07-21 18:41, hash: 64bb49fa4e3c, type: release\n\nMultires the Apply Base add to Quick Favorites can't change mesh.\n[0000-2931.mp4](0000-2931.mp4)\n\n\n- Add multires to cube, subdivide few times\n- Go to sculpt mode, sculpt mes a bit\n- Add Apply Base to Quick Favourites\n- Use Apply Base invoked from Quick Favourites\n\nOperator doesn't work this way", "creating custom (combined ) texture brush is not visually updated in texture brush tab\nWin 10 \nIntel i5\namd radeon \n\nblender 2.8 \n8996e26116f0\n\nGo into the texture for the brush settings and enable ''úse nodes'' \nGive the new texture brush a name \nMix two textures together , the output result is not reflected in the text.brush tabe\nThis was not the case wiith blender 2.7 \n\n\n\n\nAlso , when rotating the brush (ctr-F) ,the alpha overlay of the brush texture is nor", "High Resolution Render support\nSome fields needs to be able to output really high resolution renders out of EEVEE.\n\nFor now, we just try to allocate the asked buffer size and live with the consequence.\n\nMost GPU have a limit of 16K² texture resolution and some really high renders could not fit GPU memory in some cases.\n\nTo workaround this issue, we need to implement a multipass rendering.\n\nThe issue with this approach is that Screen Space effects (GTAO, SSR, SSRefract, SSSubSurfaceScattering) cannot take the whole picture into account.\n\nWe can split the rendering into tiles, scanlines, checkerboard pattern but the artifacts of SS effects will likely to be different for each", "Outliner crash/assert when deleting an override on a mesh\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nOutliner crash/assert when deleting an override on a mesh\n\nIn a debug build:\n- open `main.blend`\n- clear the override on the mesh in the Outliner\n\n\nThere seems to be something wrong with updating the tree, it still wants to draw the mesh override?\n(tried some additional stuff with `DEG_relations_tag_update`, `outliner_cleanup_tree`, `BKE_view_layer_synced_ensure` in `id_override_library_clear_single_process` to no avail...)\n\n```\n==1574045==ERROR: AddressSanitizer: heap-use-after-free on address 0x61c00030490c at pc 0x00000b189b87 bp 0x7ffe8b70fea0 sp 0x7ffe8b70fe98\nREAD of size 4 at 0x61c00030490c thread T0\n #0 0xb189b86 in outliner_but_identity_cmp_context_id_fn /blender/source/blender/editors/space_outliner/outliner_draw.cc:1973\n #1 0xa1946d9 in ui_but_equals_old /blender/source/blender/editors/interface/interface.cc:732\n #2 0xa19822c in ui_but_update_from_old_block /blender/source/blender/editors/interface/interface.cc:967\n #3 0xa1a07ab in UI_block_update_from_old(bContext const*, uiBlock*) /blender/source/blender/editors/interface/interface.cc:1869\n #4 0xa1a1cea in UI_block_end_ex(bContext const*, uiBlock*, int const*, int*) /blender/source/blender/editors/interface/interface.cc:1964\n #5 0xa1a2cd5 in UI_block_end(bContext const*, uiBlock*) /blender/source/blender/editors/interface/interface.cc:2058\n #6 0xb1a58dc in blender::ed::outliner::draw_outliner(bContext const*) /blender/source/blender/editors/space_outliner/outliner_draw.cc:4097\n #7 0xb210d95 in outliner_main_region_draw /blender/source/blender/editors/space_outliner/space_outliner.cc:88\n #8 0x7025c43 in ED_region_do_draw(bContext*, ARegion*) /blender/source/blender/editors/screen/area.cc:539\n #9 0x42a3126 in wm_draw_window_offscreen /blender/source/blender/windowmanager/intern/wm_draw.cc:1000\n #10 0x42a482a in wm_draw_window /blender/source/blender/windowmanager/intern/wm_draw.cc:1166\n #11 0x42a78e4 in wm_draw_update(bContext*) /blender/source/blender/windowmanager/intern/wm_draw.cc:1564\n #12 0x428bfd8 in WM_main(bContext*) /blender/source/blender/windowmanager/intern/wm.cc:645\n #13 0x8ef1a5 in main /blender/source/creator/creator.cc:593\n #14 0x7f56eb04a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)\n #15 0x7f56eb04a5c8 in __libc_start_main@GLIBC_2.2.5 (/lib64/libc.so.6+0x275c8)\n #16 0x8ee494 in _start (/build_linux_debug/bin/blender+0x8ee494)\n\n0x61c00030490c is located 140 bytes inside of 1712-byte region [0x61c000304880,0x61c000304f30)\nfreed by thread T0 here:\n #0 0x7f56f4cb9388 in __interceptor_free.part.0 (/lib64/libasan.so.8+0xb9388)\n #1 0x4278fad in MEM_lockfree_freeN /blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:104\n #2 0xdd817a in BKE_id_free_ex /blender/source/blender/blenkernel/intern/lib_id_delete.cc:170\n #3 0xdd9f4d in id_delete /blender/source/blender/blenkernel/intern/lib_id_delete.cc:366\n #4 0xdda2a9 in BKE_id_delete_ex /blender/source/blender/blenkernel/intern/lib_id_delete.cc:384\n #5 0xdda304 in BKE_id_delete /blender/source/blender/blenkernel/intern/lib_id_delete.cc:389\n #6 0xb1d5a80 in id_override_library_clear_single_process /blender/source/blender/editors/space_outliner/outliner_tools.cc:1489\n #7 0xb1da009 in outliner_liboverride_operation_exec /blender/source/blender/editors/space_outliner/outliner_tools.cc:1959\n #8 0x43624d5 in WM_menu_invoke_ex(bContext*, wmOperator*, wmOperatorCallContext) /blender/source/blender/windowmanager/intern/wm_operators.cc:1046\n #9 0x4362a0b in WM_menu_invoke(bContext*, wmOperator*, wmEvent const*) /blender/source/blender/windowmanager/intern/wm_operators.cc:1071\n #10 0x42b76d9 in wm_operator_invoke /blender/source/blender/windowmanager/intern/wm_event_system.cc:1530\n #11 0x42b943e in wm_operator_call_internal /blender/source/blender/windowmanager/intern/wm_event_system.cc:1731\n #12 0x42b96a7 in WM_operator_name_call_ptr(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1779\n #13 0x42babf9 in WM_operator_name_call_ptr_with_depends_on_cursor(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*, char const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1972\n #14 0xa2348a7 in ui_apply_but_funcs_after /blender/source/blender/editors/interface/interface_handlers.cc:1038\n #15 0xa2c8f30 in ui_popup_handler /blender/source/blender/editors/interface/interface_handlers.cc:11657\n #16 0x42b0485 in wm_handler_ui_call /blender/source/blender/windowmanager/intern/wm_event_system.cc:818\n #17 0x42d0410 in wm_handlers_do_intern /blender/source/blender/windowmanager/intern/wm_event_system.cc:3319\n #18 0x42d17cf in wm_handlers_do /blender/source/blender/windowmanager/intern/wm_event_system.cc:3436\n #19 0x42dbd54 in wm_event_do_handlers(bContext*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:4063\n #20 0x428bfc0 in WM_main(bContext*) /blender/source/blender/windowmanager/intern/wm.cc:639\n #21 0x8ef1a5 in main /blender/source/creator/creator.cc:593\n #22 0x7f56eb04a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)\n\npreviously allocated by thread T0 here:\n #0 0x7f56f4cba097 in calloc (/lib64/libasan.so.8+0xba097)\n #1 0x42796e2 in MEM_lockfree_callocN /blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:210\n #2 0x42646c0 in DNA_struct_reconstruct /blender/source/blender/makesdna/intern/dna_genfile.cc:1236\n #3 0x44e9d47 in read_struct /blender/source/blender/blenloader/intern/readfile.cc:1810\n #4 0x44f74ff in read_libblock /blender/source/blender/blenloader/intern/readfile.cc:2955\n #5 0x450125d in blo_read_file_internal /blender/source/blender/blenloader/intern/readfile.cc:3624\n #6 0x44d538b in BLO_read_from_file /blender/source/blender/blenloader/intern/readblenentry.cc:414\n #7 0x913295 in BKE_blendfile_read /blender/source/blender/blenkernel/intern/blendfile.cc:1014\n #8 0x4301733 in WM_file_read(bContext*, char const*, ReportList*) /blender/source/blender/windowmanager/intern/wm_files.cc:1024\n #9 0x430e599 in wm_file_read_opwrap /blender/source/blender/windowmanager/intern/wm_files.cc:2718\n #10 0x430f626 in wm_open_mainfile__open /blender/source/blender/windowmanager/intern/wm_files.cc:2841\n #11 0x430e957 in operator_state_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2754\n #12 0x430f889 in wm_open_mainfile_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2865\n #13 0x430ec2d in wm_open_mainfile__discard_changes /blender/source/blender/windowmanager/intern/wm_files.cc:2793\n #14 0x430e957 in operator_state_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2754\n #15 0x430f889 in wm_open_mainfile_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2865\n #16 0x430f8b6 in wm_open_mainfile_invoke /blender/source/blender/windowmanager/intern/wm_files.cc:2870\n #17 0x42b76d9 in wm_operator_invoke /blender/source/blender/windowmanager/intern/wm_event_system.cc:1530\n #18 0x42b959e in wm_operator_call_internal /blender/source/blender/windowmanager/intern/wm_event_system.cc:1765\n #19 0x42b96a7 in WM_operator_name_call_ptr(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1779\n #20 0x42babf9 in WM_operator_name_call_ptr_with_depends_on_cursor(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*, char const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1972\n #21 0xa2348a7 in ui_apply_but_funcs_after /blender/source/blender/editors/interface/interface_handlers.cc:1038\n #22 0xa2c8f30 in ui_popup_handler /blender/source/blender/editors/interface/interface_handlers.cc:11657\n #23 0x42b0485 in wm_handler_ui_call /blender/source/blender/windowmanager/intern/wm_event_system.cc:818\n #24 0x42d0410 in wm_handlers_do_intern /blender/source/blender/windowmanager/intern/wm_event_system.cc:3319\n #25 0x42d17cf in wm_handlers_do /blender/source/blender/windowmanager/intern/wm_event_system.cc:3436\n #26 0x42dbd54 in wm_event_do_handlers(bContext*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:4063\n #27 0x428bfc0 in WM_main(bContext*) /blender/source/blender/windowmanager/intern/wm.cc:639\n #28 0x8ef1a5 in main /blender/source/creator/creator.cc:593\n #29 0x7f56eb04a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /blender/source/blender/editors/space_outliner/outliner_draw.cc:1973 in outliner_but_identity_cmp_context_id_fn\nShadow bytes around the buggy address:\n 0x0c38800588d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 0x0c38800588e0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa\n 0x0c38800588f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c3880058900: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c3880058910: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n=>0x0c3880058920: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058930: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058940: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058950: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058960: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058970: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n Addressable: 00\n Partially addressable: 01 02 03 04 05 06 07 \n Heap left redzone: fa\n Freed heap region: fd\n Stack left redzone: f1\n Stack mid redzone: f2\n Stack right redzone: f3\n Stack after return: f5\n Stack use after scope: f8\n Global redzone: f9\n Global init order: f6\n Poisoned by user: f7\n Container overflow: fc\n Array cookie: ac\n Intra object redzone: bb\n ASan internal: fe\n Left alloca redzone: ca\n Right alloca redzone: cb\n==1574045==ABORTING\n```\n\n", "Crash/Bugs with material's Surface dropdown + undo\nOperating system: Linux-4.15.0-45-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 4)\nAlso confirmed to crash in 2.80.\nWorked: 2.79b does not crash (works as expected)\n\nWhen changing the surface/volume in material properties (the list view of the shader nodetree) and undo, opening the dropdown directly afterwards again can crash Blender.\n\n- Download repro blend file (it's just a Cube with a Principled BSDF) [shaderlistRepro.blend](shaderlistRepro.blend)\n- In Properties Editor, click on Surface (Principled BSDF) and select any option in the dropdown\n- Move your mouse over the Surface dropdown and keep it there!\n- Press CTRL+Z to undo\n- Click on the Surface (Principled BSDF) dropdown again (your mouse may not leave the dropdown box)\n- Blender crashes\n\nThe same happens when done with the Volume dropdown instead.\n\n[2020-02-24 15-09-16.mp4](2020-02-24_15-09-16.mp4)\n\n**Possibly related issue**\nIn another file, doing the exact same steps as above has some other effects:\n- Either it spawns this popup (clicking any of these options crashes Blender) \n- Or it spawns a blank popup \nThis is the reproduction file which caused this: [shaderlistRepro2.blend](shaderlistRepro2.blend)\n\nWhich effect happens is really inconsistent and I am not sure how to reproduce one or the other.", "EEVEE: User preference settings (anisotropy, texture size limit) affect rendering\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[Viweport texture limit size affects eevee rendering.]\n\nWhen I change the \"texture limit size\" setting it also limits the size of the texture in the render.\nAs the setting is in the \"viewport\" tab I believe it should only affect the viewport, not the rendering.\n\n", "Unsubdivide and rebuild subdivisions from multires.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.1\n\nModel with multires applied doesnt works with unsubdivide option or rebuild subdivisions.\nI´ve applied the modifier, cleaned the data blocks but persist...\nThere is something strange in the mesh because it works with the default cube...\n\n- Open attached .blend file\n- In the Multires modifier, click in Subdivide\n- Apply modifier\n- Add multiresolution modifier again\n- Click in Unsubdivide\n\n> No valid subdivisions found to rebuild a lower level\n\n[UnsubdivideMultires.blend](attachment)\n\n", "bpy.ops.paint.image_paint with a texture requires initialization with manual paint stroke otherwise color not quite right\nWin 10 5820K GTX 970\n\n2.79b and latest daily build\n\nbpy.ops.paint.image_paint with slightly wrong colors when painting on object with texture on brush before a manual paint stroke applied\n\n1. Load attached file\n2. Run script\n3. With mouse over the cube - press space and type Simple Modal Operator to activate modal paint operator\n4. move mouse about to paint. \n5. left click to stop modal paint operator\n6. now paint on the cube normally by holding mouse button down\n7. you will see this is a slightly different color \n8. press space and type Simple Modal Operator to activate modal paint operator again\n9. move mouse around\n10. you should now see modal operator painting correctly\n\nThis seems to happen each time I change the texture on the brush to a new one (with obviously different colors on it)\n\nImage is attached showing this.\n\nPossibly something not being initialized properly?\n\nThanks you in advance for any work on this.\n\n[modal_paint.blend](modal_paint.blend)\n\n\n", "Adjust Last Operation: Other changes outside that panel are reverted back automatically\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n\nHere the demo and file\n[2020-06-23_20-30-11.mp4](2020-06-23_20-30-11.mp4)\n[Scene state reset.blend](Scene_state_reset.blend)\n\n1. Add some objects, add last one\n2. Change visibility for other objects via outliner\n3. Change property in adjustment popup\n4. Scene settings resetted to previous", "Regression: GPU subdivision - Mesh does not immediately count viewport statistics\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\n\nBroken: version: 3.3.0 Alpha\nWorked: blender-3.3.0-alpha+daily.`d095fcd6b417`\n\nI didn't do rigorous bisecting but I suspected this is caused by 163f6a17e4 so I tested with a daily build before it was committed.\n\nMesh does not immediately count in viewport statistics with GPU subdivision enabled.\n\n\n\n- Open startup file.\n- Add Subdivision Surface modifier to the cube\n- See the mesh is not counted towards viewport stats\n- Deselect the cube (or do some other action related to viewport display, for example, ticking viewport display options), and see now it is counted towards viewport stats\n", "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" ]

[ "Manual texture space not working with boolean modifier\nOperating system: Win 10 \nGraphics card: nvidia gtx 1060\n\nBroken: official 2.80, blender-2.81-0547a7753643-windows64\nWorked: 2.79b\n\nCustom object texture space is ignored if a boolean modifier is used on the mesh\n\n- add any mesh\n- add a shader to the mesh and add a noise texture (or any other kind of texture) with generated mapping. Connect it so that it will be visible in the viewport (any kind of shader, emit shader is best for this)\n- activate Material preview or rendered mode in the viewport so that you can see the texture\n- (optional) activate the \"Display object texture space\" option in the Object properties/ viewport display tab\n- In the Object Data/Texture space tab, deactivate the \"auto texture space\" and change the location or size. It will work\n- add a boolean modifier to the mesh and perform any kind of operation with any kind of mesh (do not apply the modifier\n\nyou'll see at this point, that the texture space should get reset to the bounding box of the resulting mesh of the boolean operation. \n\nhere is a blend file with the bug TextureSpace_Bug_001.blend?dl=0", "Manual generated texture coordinates are overwritten by auto-generated ones when certain modifiers are applied\nOperating system: Windows 10\nGraphics card: Nvidia GeForce RTX 2070\n\nBroken: 2.8 and 2.81 experimental\nWorked: 2.79 and below.\n\nManual texture space position and scaling for an object are overwritten by auto-generated ones when certain modifiers are applied to the object.\n\nModifiers that cause the issue (Only generate modifiers seem to have this issue):\n - Bevel\n - Boolean\n - Decimate\n - Edge split\n - Mirror (when bisect is used)\n - Remesh\n - Skin\n - Triangulate\n - Wireframe \n\nSelect mesh object, go under mesh properties > Texture Space > untick \"Auto Texture Space\" and set some custom coordinates.\nAdd any of the above modifiers to the object. Generated coordinates for textures will be overwritten by auto-generated ones as if you had never unticked \"Auto Texture Space\". \n\n2.79 result (Expected):\n\n\n2.8 result (Broken):\n\n\n[issues.blend](issues.blend)", "bevel modifier affect box projection mapping.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nHi,\nIf \"Auto Texture Space\" option (object data panel) is turned OFF and I use custom values for the size and location, looks like the bevel modifier turn it ON by default producing unwanted effects.\n\n\nopen the scene, be sure to be in eevee look-dev mode and turn on/off the bevel modifier visibility.\n\nthank you\n\n\n[bevelmod.blend](bevelmod.blend)\n", "Bevel modifier breaks texture space settings\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 74)\nBroken: version: 2.81 (sub 1)\nWorked: (optional) 2.79\n\n\nIf the \"Bevel Modifier\" is used on a mesh object which has \"Auto Texture Space\" deactivated and some custom settings for \"Location\" and \"Size\", its texture space behaves like set to \"Auto Texture Space\" and ignores the custom settings. When the modifier is applied to the mesh, its texture space behaves normal again.\nThis is also present in the Windows versions of the above mentioned.\n\nSee above and attached Blendfile.\n[BugBevel.blend](BugBevel.blend)\n", "Bevel mod brakes Texture \nOperating system: Windows 10 \nGraphics card: GeForce GTX 780\n\n\nBroken: 2.80\n\n\nAdding a bevel modifier to an object effectively ticks the \"Auto Texture Spece\" tickbox in mesh settings - when in object mode.\n\n\nIn the above image, you can see how the texture is correct in edit mode, but not in object mode.\n\n\nSee [Texturing Bug.blend](Texturing_Bug.blend)\n\nSelect the cube, and tab into edit mode.\n\nSelect all and scale through X by 4\n\nSet up a new material: Texture Coordinate: generated into an image texture (coordinates set to box) into Colour of a principled shader\n\nIn the mesh settings for the cube > texture space, untick \"auto texture space\" and set size to 1,1,1\n\nIn eevee, Texturing looks fine in edit mode but not in object mode or rendering.\nIn cycles, it's just broken.", "Incorrect Auto Texture Space in both viewport and render, and with and w/o modifiers \nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\nBroken: version: 2.80 (sub 68)\n\nLet me know if it's better to split these into multiple bugs. They're just very related, like different expressions of the same problem, and I wanted to show them all at once\n\n**Short description of error(s)**\n\nA) During render and with a modifier on a mesh, even with Auto Texture Space (ATS) OFF, it will behave as if ATS is ON, and not even in the shape of the original mesh, but one that stretches and bounds the entire modified mesh (eg if a mesh has a mirror modifier, the bounds of the Texture Space is a wide as the final mesh, something that doesn't happen in 2.79) (I haven't tested every modifier)\n\nB) If you were using ATS OFF with custom bound values, and then turn it ON back again, the values of the bound won't update to reflect it until you reload the file or undo. (In 2.79 you could simply enter into edit mode and the values would update) But this has weird consequences for that period in which ATS is ON but the values don't reflect it:\n\nC) During render, and without a modifier, even with ATS ON, it will render with ATS OFF and the old bound values. But if it has a modifier, bug A) happens\n\nD) On the Lookdev viewport however, you can see the correct ATS on the material as soon as you turn it ON, even on meshes with modifers and even though the values of the bound still won't updated. But you realize that it's not truly working when you render and bugs C) and A) happen, or when you enter and exit edit mode and see the old custom Texture Space still working instead of the ATS that we want\n\nAll in all, bug C) and bug D) would disappear if bug B) got fixed to update the values more instantly. But that still leaves bug A) Meshes with modifiers during render won't use either the custom texture space nor the ATS of the original unmodified mesh (render engine doesn't seem to matter)\n\n\nUse lookdev or rendered shading mode\nTo observe bug A) open the file and just render F12. The entire column of objects with modifers will have the wrong texture space\nTo observe bugs B) C) and D), since these get cured as soon as a file is reloaded, you have to turn off Auto Texture Space on the last two rows of objects, input custom texture space bound values (like Loc0,0,0 Scale 1,0.2,0.2 to use the same I used) and then turn ATS on again. You have to enter and exit edit mode on the last row too and this should replicate the images attached. Observe how the bound values remain the same still.\nTo observe the ATS updating the bounding values, Save and Reload.\n\nI hope the checkmarks gives you an idea on how things should look properly. With and without modifier, with and without ATS, and the same across viewport and render with no differences\n\n[texture space bug.blend](texture_space_bug.blend)\n\n\n\n\n\n\n\n\n\n\n", "Bevel modifier overrides compleatly the generated texture space\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe bevel modifier \nBasically that manual texture space doesn't work if bevel modifier its active. \nModifier ON\n\n\nModifier OFF\n\n\n[texture generated overrided .blend](texture_generated_overrided_.blend)\n1- change the 3d view to render.\n2-turn on and off the bevel modifier.\n3-try change the Texture Space values with and without bevel modifier. \n\n\nNOTE: I wasn't sure if it is related to #64739 so i add this new report \n" ]

[ "Grease Pencil mask error\nOperating system:windows10\nGraphics card:GTX1060ti\n\nBroken: 2.83&2.9\nWorked:greasepencil-Mask error\n1.When 2.83 or later, creates two objects, the masks collide, causing a strange phenomenon, and in 2.82 there are no errors.\n2.And creating two masks under the same object can cause problems too。\niJlqkf556sA\n[GP剪贴测试.blend](GP剪贴测试.blend)", "EEVEE-Next: Known Issues\nThis task lists the minor missing features that are known for not yet working with EEVEE-Next.\n\nPriority of each task needs to be assessed and assigned.\n\n# LookDev\n- [ ] camera world alignement isn't working.\n- [ ] blur background isn't working.\n- [ ] diffuse contribution isn't taken into account.\n\n# Shadow\n- [ ] big performance bottleneck caused by rendering method\n\n# Hardware support\n- [ ] Metal backend doesn't support shadow rendering and GI baking yet", "Generative modifiers (solidify, mirror) draw face normals from original face (wrong direction)\n@Baszczer information\nOperating system: Ubuntu 20.04\nGraphics card: Radeon Pro WX 7100\n\n@Alaska information\nOperating system: Linux-5.4.0-7629-generic-x86_64-with-debian-bullseye\nGraphics card: GTX 1050Ti 440.82\n\nBroken: 2.83 (2020-05-26 22:42) `f772a4b8fa`, 2.90 (2020-05-26 20:02) `eb5422828a`\nWorked: 2.82a\n\n**Short description of error:**\nThe viewpoint overlay for displaying faces normals in edit mode for faces that are part of a solidify modifier will always point in the direction of the face normal being solidified with Blender 2.83 and 2.90.\n\n\n2.82a\n\n\n2.83/2.90\n\n**Exact steps for others to reproduce the error:**\n1. Open Blender.\n2. Add a plane.\n3. Give the plane a solidify modifier.\n4. In the modifier panel, enable the \"On cage\" option for the solidify modifier.\n5. Enter edit mode on the plane. \n6. In the viewport overlays enable the \"Display normals\" option for faces. \n\n[#77090 - Solidify Normals.blend](T77090_-_Solidify_Normals.blend)\n\nIn 2.82a, this will be have as expected. The normal lines will be perpendicular to the faces of the solidifies plane. In 2.83, all the normal lines align with the normal line of the face being solidified.\n\nVideo because I feel like I'm having a hard time explaining this in words:\n[2020-05-27 22-55-31.mp4](2020-05-27_22-55-31.mp4)", "Momentary interface freezes while EEVEE rendering causes progress bar malfunction\nOperating system: Windows 10, 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.80, 2.81\n\n**Rendering in EEVEE has been causing momentary complete interface freezes for each frame**, which caused the progress bar on the frame render to malfunction and jump very quickly from one value to another, thus giving momentarily true but useless information (note that the progress bar never moved to an incorrect position, it just froze). One thing that assures me this is a bug is **minimizing all Blender windows causes the progress bar visible on the minimized icon to work properly** (but unfortunately one cannot see what frame it's on).\n\nOpen the default blend file.\nRender the animation. The interface on 2.81 has frozen for each frame.", "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", "Grease Pencil ripped line when rendering in EVEE\nOperating system: Windows 10\nGraphics card: GeForce 1050 ti\n\n3.62\n\nGrease pencil object is displayed normally in the viewport, but when rendering the line becomes jagged, not like in the viewport. In Cycles all is good.\n\n\n\n", "UI: Image/UV Editor\nThe UI of the Image and UV Editor can be improved.\n\n* Move smooth edges option to user pref\n* Move overlays to an overlay popover\n\n\n\n\n* Move display settings to a popover\n* Change the Pixel Coordinates toggle into an enum to choose between Pixels or Normalized\n\n\n* Slightly re-arrange the header:\n\n* Move th UV Vertex panel away from the Image Sidebar category and into Item, and include Coordinates option here too:\n\n", "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", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)", "Render Artifacts with SSS + Motion Blur + Use Spacial Splits\nWhen you have the \"perfect storm\" of Subsurface Scattering, Motion Blur, and \"Use Spacial Splits\" (Render>Performance) all applied to an animated mesh, the rendered image will exhibit some pretty severe artifacts and mesh cracking on certain frames of an animation.\n\nThe main issue appears to be related to \"Use Spacial Splits\"\n\nOpen the attached zip - watch the comparison video. Open the .blend file, hit F12 to render (frame 34 is a good example)[Spacial Splits +Motion Blur Artifact Bug.zip](Spacial_Splits__Motion_Blur_Artifact_Bug.zip)\n\n[Render Bug - Spacial Splits + Motion Blur + Sss-1.m4v](Render_Bug_-_Spacial_Splits___Motion_Blur___Sss-1.m4v)", "Subdivision modifier artifacts in Blender 2.80\nOperating system: Windows 10\nGraphics card: 1080ti\n\nBroken: \n2.80 downloaded on the 3rd of Feb, 2019 as found on the download beta section\nWorked: (optional)\n\n\nSome artifacts around the out circle in the blend file, this is not present in Blender 2.79\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nload attached file, doesn't matter if it is Cycles or Blender the artifact is present.\n\n[ukelele.blend](ukelele.blend)", "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", "UV Editor face select mode fails to select ngons reliably\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.4.1\nWorked: never? (2.83 fails too)\n\nUV Editor face selection mode fails to select ngons reliably, because it uses face dot based selection, which can not be turned off. I was told to report scenarios where face dot based selection fails to work as bugs, so I am doing so here.\n\n1. Open the attached file\n2. Select the mesh object, enter the edit mode, and in the UV editor, switch selection mode to face\n3. Attempt to select some of the larger ngon UV face\nResult: The selection of larger ngon UV faces fails in many cases\nExpected The UV faces under the mouse cursor are selected when clicked on\n\n[UVSelectBug.blend](UVSelectBug.blend)\n[2023-02-06 12-20-58.mp4](2023-02-06_12-20-58.mp4)", "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", "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" ]

[ "Face artifacts in Edit mode Blender 2.83 LTS\nOperating system: Windows 10\nGraphics card: Intel integrated graphics\nProcessor: Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz 2.00 GHz\nInstalled memory (RAM): 4.00 GB\nSystem type: 64-bit Operating System, x64-based processor\n\nBroken: 2.83.0\n\nAfter updating to 2.83 LTS, in Edit mode object faces are showing artifacts similar to that usually appear when there are double faces. But there are no double faces. It had no problem with 2.82.\n\nThis is a screenshot ", "3d viewport artifacts for blender 2.83 and 2.9\n\n\n\n\n\n\n{[F8578249](1.PNG)}Operating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.4531\n\nBroken: version: 2.83.0\nWorked: the problem is only in blender 2.83 but older version 2.82 works completly fine and stable and fast\n\nblender 2.82 was working very well but when I switched to 2.83 I got these artifacts whenever I selected any verticies and the same thing for sculpting using face sets and when I add a reference image it also has artifacts that are visable through the mesh and the mesh keeps disapearing and comes back when I zoom in or out\nsame thing happens for 2.9 for me and when I switched back to 2.82 it stopped\nopen bleder and go to edit mode and select all and you'll get those artifacts \ngo to sculpt mode and you'll see those artifacts in face sets\nif you add a reference image you'll see artifacts in the image itself that are visable through the mesh infront of the image and the mesh itself keeeps dissapearing\n[BUG.blend](BUG.blend)\n", "Blender Model *Faces* glitching\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics Intel 4.3.0 - Build 20.19.15.4963\n\nBroken: version: 2.83.0\n\ni dont know if this is considered as an error but yes blender models glitch out in the modelling tab\n1aa80119a18c5efc4a34088100a0e86f [untitled.blend](untitled.blend)\nedit: also tried reinstalling a couple of times\nsadly this issue happens to me everytime...even in new .blend filles\n\n", "Artifacts in edit mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 5500 Intel 4.4.0 - Build 20.19.15.5058\n\nBroken: version: 2.83 (sub 17) (same issue on alpha)\nWorked: 2.82a\n\nArtifacts when in edit mode\n\n\nEnter edit mode.\n\n", "mesh glitch in edit mode\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4531\n\nBroken: version: 2.83.0\nWorked: (newest version of Blender that worked as expected)\n\nsome glitch appears when i am in edit mode but only on solid view (works fine in materiel view and rendered view)\n\nhappens when i enter edit mode in solid view\n\n", "Flickering and strange arttifacts when entering edit mode\nOperating system: windows 10 pro\nGraphics card: intel HD graphics card\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nbender version 2.83\nWhen i enter edit mode the screen starts to ficker and then itt enters edit mode with artifacts on tthe default cube\nBased on the default startup or an attached .blend file (as simple as possible).\nopen blender\nthen go to LAYOUT tab and hit TAB to enter edit mode\n\nor \nclick on modeling tab{[F8577631](system-info.txt)}\n\n", "More than Single-Pass Anti-Aliasing Causes Flickering and Incorrectly Colored Faces in Edit Mode\nOperating system: Windows 10.0.18363 Build 18363\nGraphics card: Intel(R) HD Graphics 5500\n\nBroken: 2.83b (2.83.17), Hash: 8a8c61190b06, Date: 05-21\nWorked: Blender 2.82\n\nUpon opening any file, when in edit mode, faces will flicker and have a diagonal line of boxes drawn across them.\n\nIf, however, I go edit>preferences>viewport and changes antialiasing to single-pass antialias, then the faces are drawn as normal. See photos for examples of each on the default cube.\n\nAlso, if I increase the number of anti-aliasing samples from 5 to 8, ..., 32 the flickering will last longer before stopping on the screenshot of the incorrectly drawn faces. This happens with the default cube, so there definitely isn't overlapping mesh somehow.\n\n\n\n\n\n\nOpen the default file and go into edit mode. The cube will flicker and faces will be colored incorrectly.", "Viewport : Edit Mode : Jagged Lines on Box Faces\n\n\n\n\nOperating system: Window 10 version 1909\nGraphics card: intel i5 5200U\n\nBroken: 2.83 release\nWorked: 2.82a\n\nJagged Lines on Box Faces in Edit Mode\n\nWhen I click on the Box then enter Edit Mode, there are Jagged Edges on the Box Faces.\nAlso when I tick 'Overlay Smooth Wire' or Edit-Mode Smooth Wire' in the preferences Viewport Menu. The Text fonts disappear. See attached images.\n\nIf I select 'No-Antialiasing' the Box looks fine, as it did in Blender 2.82a.\nThe Viewport is in it's default settings, nothing has changed. The only thing I noticed was the Grease Pencil menu had gone, which was there in Blender 2.82a", "Selected faces in Edit Mode shows incorrect highlight\nOperating system: Windows 10 Home Single Language\nGraphics card: Intel(R) Graphics Family\n\nBroken: 2.83\nWorked: 2.82a\n\nSelected faces in Edit Mode show corrupted highlight it corrects itself when moving the scene and turns transparent when hovering over a gizmo\n\n1 Enter Edit Mode \n2 Select a face\n\n\n\n\n[REPORT.blend](REPORT.blend)\n\n[Blender - [x].mp4](Blender__1_.mp4)\n\n[Blender 2020-06-05 21-39-40.mp4](Blender_2020-06-05_21-39-40.mp4)", "Faces almost dissapear when in edit mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.4531\n\nBroken: version: 2.90 (sub 0)\n\n\n[when selecting a face in edit mode it starts looking weird(see photo), it doesn't seem to happen in neither wierframe rendered nor shader preview modes\nalso sometimes when grabing a face or extruding, it looks like its in wireframe mode(i couldn't take a picture of that)\nwhen moving around it doesn't seem to be weird(see 2nd photo\nalso works ) there is no effect with a subdivision surface modifier ]\n\n[open blender and open a default scene, then go into edit mode and select any face ]\n[{[F8526544](image.png)}]\n\n\n\n\n", "Overlay glitches 2.83 beta on intel HD cards. \nEdit by @Alaska\n\nIn the mean time, a work around that's worked for a few people is to disable anti-aliasing. This can be down with the steps below:\n\n1. Select from the top of Blender select `Edit>Preferences`.\n2. Navigate to the `Viewport` tab.\n3. Change \"viewport anti-aliasing\" to `Single pass` or `No anti-aliasing`.\n\n---\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 5500 Intel 4.4.0 - Build 20.19.15.5070 \nIntel HD 4400 too. \nIntel HD 4600 too.\n\nBroken: version: a68bd94d11 (problematic commit)\nWorked: a68bd94d11^\n\nSelection overlay and weightpaint overlays looks like if they are glitched. Also overlays seems to occlude view when resizing a brush.\n\nBased on factory settings:\n - Select cube\n - Go to editmode or weight_paint mode.\n - Pan or rotate view.\n\n---\n \nvideo: [F8503651](Overlay_glitches_bug_720.mp4)\n", "Glitchy triangle-like pixelated highlight of faces in edit mode.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.5107\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83.0 Beta Date: 2020-04-15 12:03 Hash: 54736d505866\n\nGlitchy visuals while in edit mode.\n\n\n\nNew File -> General\nThen press TAB. Effects are immediatly apparent. \n\n", "The Objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 400 Intel 4.4.0 - Build 20.19.15.4531\n\nBroken: version: 2.83.0\n\n[When I start up a New Blend File the Objects I use have this weird texture error. 84a870112324bb537211014d67441c24\n\n\n" ]

[ "Cycles does not respect the texture alpha mode\nOperating system: Gentoo Linux \nGraphics card: AMD 290x\n\nBroken:\n2.79b\n2.80 f15205b93f56e454b76d5a222fdb9a9665b99907 2018-01-02\n\nEevee respect the alpha mode in the texture settings, however cycles does not.\n\n[alpha_test_pack.blend](alpha_test_pack.blend)\n\n1. Load the attached .blend file\n2. Change the texture settings for the `Alpha:` setting for the image texture node (with use alpha on).\n3. Notice that in cycles the `Alpha:` setting has not effect, the texture alpha is always premultilied.", "Missing modal keymap settings for operators such as `Inset Faces`\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\nWorked: unknown\n\nHi. Today I noticed that in the preferences there is no panel to customize hotkeys in modal mode for the \"Inset Faces\" operator.\n\n", "Regression: Mesh render artifacts\nOperating system: Windows 10\nGraphics card: GTX 1070 TI\n\nBroken: 3.1, 3.6\nWorked: (3.0.1)\n\nNormals on hair mesh is corrupted in newer versions of blender while being perfect in older ones.\nMesh name is LOD0_1_front_hair_omote597.\n\n- Open the attached .blend file\n- View the model/mesh in normals/ambient occlusion render pass (cycles)\n\n", "\"Z\" changed to \"depth\" breaks consistency in compositing and in Render layers\n\nwin7 gtx 550ti\nOperating system and graphics card\n\nBroken by: 4cf7fc3b3a\n\n\"Z\" changed to \"depth\" breaks consistency in compositing and in Render layers\n\n\n- Make sure that the **z**-pass is checked in the Render Layers tab\n- Open node editor, notice that the**z**-pass is now **depth**-pass\n- Notice as well that everywhere else it is still consider as**z**-pass even in the manual z_combine.html\n\n\n\nAlthough **depth** is more meaningful name, it is breaking consistency. Suggestion: we bring back the old behavior or we change everywhere to z-depth or depth.\n", "pressing z key to switch between extrusion \n intel i5 ,win ,amd radeon \nblender 2.8 \n490a385c8124\n\n\n\n\nThis happens when transform orientation set to Global \nCreate a sphere , select a face and extrude \nBy default it will extrude along the normal , when pressing z it will now extrude along the global but it won't go back to normal when pressing the 'z'key again \n \n\n\n ", "Sculpt: masks / face sets invisible in X-ray mode\nOperating system: Windows 10\n\nBroken: 2.91.0\n \nSculpt mask is invisible in X-ray view mode, but you can still paint the mask while in Xray.\nThis makes it hard to trace the background image when masking.\n\n \n\n", "Backface culling is not working for mask in edit mode\n2.80 (sub 45), 893fa598319e, 2019-02-24 22:02\n\nAnd wireframe too heavy.\n\n\n\nIdk if it is bug or intended, but it will be nice, if it will work like on the 2nd or 3rd picture: much more readable.\nAnd when x-ray is on, wireframe on the background will be faded too, accordingly slider-setting.\n\n\n\n\n", "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", "Cycles: Pointiness has artefacts on extremely small mesh size\nOperating system:\nGraphics card:\n\nBroken: version: 3.6.0 Alpha\nWorked: Never\n\nPointiness has artefacts on extremely small mesh size. \n\n| Normal size | Small size | Smaller size |\n| -- | -- | -- |\n|  |  |  |\n\n1. Create cube with beveling edges. Create small copies on vertices (as on example pictures).\n2. Set shader to cube. Shader with:\n a. Inputs: Geometry -> Pointiness.\n b. Map range: From Min: 0.5, From Max: 0.54.\n c. Material Output.\n3. Render that cube with applied different sizes.", "Visualized face normals are duplicated when Edit Cage is enabled in subdivision modifier (GPU subdivision turned OFF)\n### Simplified Report\n\nHaving Edit Cage on subdivision modifier enabled causes visualized face normals to be duplicated started from the origin. Here is a simplified file with a single face:\n\n\n\n[editCageWrongNormalDisplay.blend](editCageWrongNormalDisplay.blend)\n\nThis issue exists back to 2.83.\n\n### Original Report\n\nOperating system: Ubuntu 22.04 LTS\nGraphics card: Nvidia Quadro M4000\n\nBroken: 2.93.10, 2.83\nWorked: Unknown.\n\n\"Flying\" normals everywhere\n\nI have not discovered a correlation. The alignment of the normal is random, it changes when you exit edit mode and return.\n\n\n\n\n\n\n\n\n\n", "Using Viewport Navigation Gizmos can execute tool gizmos or sculpting\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.91.0 Alpha\nWorked: never worke in 2.8+\n\nLeft Mouse dragging on those two buttons can lead to unexpected/undesired behavior. \n\nThe dragging executes whatever tool is currently active:\n- if the selection tool is active, a selection is drawn\n- if the move tool is active and an object selected, the object is moved\netc.\n\nWhy this is a problem:\nIf one of these two buttons get accidentally dragged a little, it can apply a tiny yet destructive change to your scene which isn't noticed at first (as this behavior is unexpected).\n\n\n\nThis example is for the move tool:\n1. Open a new scene\n2. Activate the move tool\n3. Select the cube\n\n4. Drag the camera or perspective button to the side\n5. See how the cube is moved\n\n\n\nThis example is for sculpting:\n1. Open new sculpting scene\n\n2. Drag the camera or perspective button to the side\n3. See how the mesh gets distorted\n\n\nThanks\n", "Weight paint: front face falloff checkbox looks inactive (dimmed)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\nBroken in 2.93.7 too\n\nFront face falloff checkbox Looks dimmed, but it is active\n\n\nAlso in the n-panel there is correct variant. And another one incorrect.\n\n\n[2021-12-19_04-11-58.mp4](2021-12-19_04-11-58.mp4)\n", "Draw Face Set brush bug\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\nDraw Face Set brush doesn't work properly and select faces randomly\n[DjHiCdF9fE.mp4](DjHiCdF9fE.mp4)", "Symmetry in sculpt mode weird behavior with mask and face set\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.90.0 Alpha\nWorked: --\n\nWhen sculpting a non-symetric object with symmetry on, using shift+a or shift+w creates a weird behavior\n\n\n\n[bug.blend](bug.blend)\n- Open the file above.\n- use shift+a in the second finger like this:\n\n- Turn symmetry off and try it again:\n\n\nThe origin is far off those two fingers and also all the transformations are applied, so I don't think its an expected behavior,\n\n\nBesides, it doesn't happen when you try using brushes on the mesh. \n\n", "EEVEE Next - 'Alpha Blend' - distant objects - shadow buffer overflow\n### Reported as per @fclem [request](111809#issuecomment-1014998)\n\n--\n\nLinux Mint 21.2 Cinnamon kernel 6.2.0-32\n3400G\n\n- Broken\nblender-4.0.0-alpha+main.b5c89822ac40-linux.x86_64-release.tar.xz\n\n- Worked\nN/A (new feature).\n\n- Short description of error:\nWhen an object's shader uses Alpha, and (Material tab) 'Blend Mode' uses 'Alpha Blend', distant objects cause a shadow buffer overflow.\n\n- Exact steps\n1. Open following .blend file and zoom (far) out / back in.\n[EEVEE Next - 'Alpha Blend' shadow buffer overflow.blend](attachment)\n\n2. Appears no issue while using 'Alpha Clip' or 'Alpha Hashed'.\n\n'Alpha Blend' preferred for preventing Z fighting in Orthographic view.\n\nKind regards.\n\n**Screenshot**\n\n\n" ]

[ "visual glitch in edit mode\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.6.0 Alpha\n\nThere is a visual glitch when you jump into edit mode, all the selected faces are not solid. I downloaded Version 3.6.0 (3.6.0 2023-04-04) and the problem is still there.\n\nUpdate: the glitch is there even if the faces are not selected, it's not as noticeable but it's there\n\nLaunch Blender and jump into edit mode, there is no need to do anything else. The more complex the object the more it's noticeable. see video\n\n", "macOS Metal viewport: Blocking artefacts on selected faces\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.6.0 Alpha\nWorked: N/A\n\nmacOS Metal: Blocking artefacts on selected faces\n\n\n - Open the attached blend file on latest Trunk on macOS \n - Make sure it's set to use Metal GPU backend\n - Enter Edit Mode and select a face on the head.\n \n Notice the blocking artefacts. These are not present with OpenGL.\n\n" ]

[ "Grease Pencil ignores collection Line Art usage settings\nversion: 3.3.0 Beta, branch: master, commit date: 2022-07-28 22:39, hash: 6ca602dd9fa1, type: release\nbuild date: 2022-07-29, 00:21:12\nplatform: 'Windows-10-10.0.22000-SP0'\n\nrenderer:\t'NVIDIA GeForce RTX 3090/PCIe/SSE2'\nvendor:\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 516.59'\n\nGrese Pencil ingnores Collections Line Art usage settings. See my attachment and screenshot.\n\nOpen the attached file and check the line art settings in the torus collection.\n\n\n\n[gpencil_outlines-test-3_3.blend](gpencil_outlines-test-3_3.blend)", "Grease pencil eraser settings not loaded on startup when using ctrl+LMB with the Draw tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 2.90.0\n\nWhen first opening a blend file, your eraser settings are set to default when using ctrl+LMB with the draw tool, and only update after switching to the eraser tool and using it.\n\n\n- Open attached file (the Stroke object is selected and the Draw tool activated in Draw mode).\n- Draw a line\n- Erase part of the line using the same tool but with Ctrl selected. Notice how it behaves as if the `\"Eraser Soft\"` brush is used. \n- Switch to the Eraser tool, erase part of the line. Notice how it behaves according to the specified Brush: `\"Eraser Point\"`. \n- Switch back to Draw tool, and hold down ctrl to erase another part of the line, it should now start behaving like the `\"Eraser Point\"` brush.\n\n[eraser bug.blend](eraser_bug.blend)\n\n", "Grease Pencil mask error\nOperating system:windows10\nGraphics card:GTX1060ti\n\nBroken: 2.83&2.9\nWorked:greasepencil-Mask error\n1.When 2.83 or later, creates two objects, the masks collide, causing a strange phenomenon, and in 2.82 there are no errors.\n2.And creating two masks under the same object can cause problems too。\niJlqkf556sA\n[GP剪贴测试.blend](GP剪贴测试.blend)", "Grease Pencil datablock property 'use_onion_skinning' doesn't work\nOperating system:\nGraphics card:\n\nBroken: 3.4\nWorked: \n\nThe datablock-level property \"use_onion_skinning\" on the Grease Pencil datablock doesn't seem to do anything. Toggling the property with Python doesn't affect the visibility of onion skinning.\nWorking as expected, this property will be useful when drawing among multiple Grease Pencil objects.\n\nOpen attached blend, toggle use_onion_skinning in the Python console: bpy.context.object.data.use_onion_skinning = False [onion_bug.blend](onion_bug.blend) ", "unable to use 'grid fill' or 'fill' on screwed object\nOperating system: Window 10\nGraphics card: NVIDIA GeForce RTX 2060 SUPER\n\nBroken: Blender 2.83\nWorked: Blender 2.76 \n\n\nI am trying to create a solid spring using Screw modifier. After applied grid fill, I expected a full capped end of the screwed object, but it turns out to be like figure below. The complete file also attached in this post. Hope to get your response soon. \n\n[screw.blend](screw.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "No projection onto empty object types\n(This is was coming from a discussion with @ideasman42 )\n\nThere are Tools and Operators that will take empties into account, even though this is very counter-intuitive in most workflows.\nOne example of this is the 3D Cursor being projected onto image empties. In the workflow of creating characters and props it's common to import images as references, especially turntable drawings.\nIn Blender 2.8 These these need to be imported as empties and set up to be visible in the background from different angles.\n\n\nIt is very anoying to try to place the 3D Cursor to add new objects and have it projected onto one of the empties. The empties are reference. They should not be taken into account for the tools (Except for snapping to an empty origin).\n\nAnother example is when drawing a curve and using the surface depth method for drawing. This way it will draw the curve onto surfaces instead of around the 3D Cursor.\nIf there's an empty in the way, it will take the wires & surfaces of the empty also into account, which really has no use.\n\nThis needs to be further discussed if this functionality should be completely changed or made optional if there are any workflows that benefit from this.", "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", "Selection Operators\nAll the selection operators will have to be ported to the new grease pencil structure.\n\nInteractive selection operators:\n- [x] `GPENCIL_OT_select` -> 108660\n - See 7f218277c360f54d96e59888201fe66444d42465\n- [x] `GPENCIL_OT_select_circle` -> 108662\n - See fde2eca1d2b1d6c1acad75f10a70dfcb81de96e9\n- [x] `GPENCIL_OT_select_box`\n - See 7f4f771442bdbc7d8c1bf08a54edb3af0a92f490\n- [x] `GPENCIL_OT_select_lasso` -> 108663\n - See 3ca67a7a5d258cb1444c642549b372e416f52ac1\n\nNon-interactive selection operators: \n- [x] `GPENCIL_OT_select_all`\n - See b29ba95caeb9a82eb7bb1f957000f2f50d953b41\n- [x] `GPENCIL_OT_select_linked` -> #108750\n - See 126bff3099998f0041c8b4f086e6440ae8470480\n- [x] `GPENCIL_OT_select_more` -> #108752\n- [x] `GPENCIL_OT_select_less` -> #108752\n - See 825d2d301ba12dbba0d9afc6cd482c40f9e0eee1\n- [x] `GPENCIL_OT_select_first` -> #108802\n- [x] `GPENCIL_OT_select_last` -> #108802\n - See e165dae3b856258a6a9f159421ea8b46cd238189\n- [x] `GPENCIL_OT_select_alternate`\n - See fdc0402a506225cd9f490460270bc4f3d1f6a78b\n- [x] `GPENCIL_OT_select_random` -> #108933\n- [ ] `GPENCIL_OT_select_grouped` / `GPENCIL_OT_select_vertex_color` -> #109734\n\n", "Grease Pencil sculpt tool affecting strokes behind camera\nOperating system: Windows 11 Home\nGraphics card: Nvidia GeForce MX350\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked: ?\n\nIf the 3D view camera has strokes in front of it (visible on screen) as well as behind it (not visible on screen), in Grease Pencil's Sculpt Mode, using the grab tool will affect not only the strokes that you can see, but also the ones behind the camera that you do not see.\n\n1. Move the Camera object to the origin\n2. Create an empty Grease Pencil object\n3. Place the 3D cursor a little bit in front of the Camera object, set the Stroke Placement to 3D Cursor and the Drawing Plane to View. Align the 3D view to the active camera object.\n4. Draw some strokes, make sure to cover a good portion of the screen. The strokes will be visible.\n5. Rotate the active camera object around the Z-axis 180 degrees. Move the 3D cursor to again be a bit in front of the camera and make sure the 3D view is aligned to the active camera object again.\n6. Draw some more strokes. They will be visible, while the strokes from before are now no longer visible since they are behind the camera.\n7. Go to Sculpt Mode and select the grab tool.\n8. Grab and manipulate some strokes that you can see.\n\nExpected outcome: only the strokes from step 6 are manipulated, and the ones from step 4 are not.\nActual outcome: both the strokes from step 6 and step 4 are manipulated.", "custom brushes icon won't show up is some cases\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\nIn some cases the custom icon of the brushes won't load properly. Even by reassigning it it doesn't work.\n\nOpen the attached file and try to assign the accatech custom icon to the active brush (but anykind of image won't load)\n\nThankyou\n\n\n\n[icon.blend](icon.blend)", "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)]", "Resetting default value does not work in popovers or menus\nOperating system: Windows 10, 64 bits, \nGraphics card: Nvidia GTX 1080 8 gb, Nvidia GTX1070 8 gb\n\nBroken:\nblender-2.81.0-git.ce2368cf69f5-windows64\n\nWorked: (optional)\n\nResetting options in the context menu (right click) of things like brush stroke strength, Autosmooth, plane offset and other parameters does not work at all, but does work through active Tool side panes and top bar. Probably it should work everywhere? If I'm working full screen I would want to be able to reset it in the context menu with my stylus as I sculpt.\n\n\n\n1 Create any mesh\n2 Enable Sculpt mode\n3 Select any brush\n4 Right click to invoke context menu\n5 Try resetting any of the parameter to default values\n", "Gpencil: Delay & Frames field values in Build Modifier should be integers only\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\nIn the Grease Pencil Build modifier, when using the mouse or the arrows to change Start Delay or Frames, the value goes through decimals instead of going directly to the next frame value.\n\nLoad a Grease Pencil Build modifier,\nIn the Start Delay or Frames field, use the arrows or the mouse left button to change the value, or type a number with decimals.\n", "Line Art Thickness doesn't consider Render Resolution Percentage\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1122\n\nBroken: version: 3.2.2\nBroken: version: 3.4.0 Alpha\nBroken\n\nWhen using Line Art Modifier, on a Grease Pencil Object in Screen Space Mode, Line Thickness doesn't scale with resolution as expected. \n\n1. Open new General Startup File\n2. Create New Object>Grease Pencil>Scene Line Art\n3. Under Object Data Properties>Strokes>Stroke Thickness and set to World Space\n4. Set Render Resolution % to a factor. line thickness will be different than expected\n\n\n\n\n\n", "Known-issues with interaction handling inside pop-ups\n# Known-issues with interaction handling inside pop-ups\n\n*Pop-up in this case includes menus and popovers.*\n\nThere are quite some old and some new issues with pop-ups. Their increased usage after 2.80 means that users run into them more and more.\n\nIn this task all related known issues should be listed, to give a good view over the situation. Eventually it should help deciding how to move forward.\n\n* Resetting default value does not work in popovers or menus. (#69200)\n* Context Manual Help Operator does not work in context menus. (#67201)\n* Add Driver : Clicking the picker doesn't work. (#58341)\n* Popover: Color Sampling doesn't work. (#63890)\n* No color drag'n'drop in Viewport Shading popover. (#70654)\n* Eyedropper does nothing on \"New\" in Uv image editor (button is disabled as workaround). (#32396)\n* ~~Most ID selectors (like e.g. the 'target' ones in constraints and modifiers) do not show difference between local and linked IDs. Even worse, they do not allow to select linked ones when a local one exists with the same name. (#73156)~~ (d6cefef98f)\n* Double-click not working in UI_Lists in popovers (e.g., grease pencil layers renaming) (#66286)\n* #76833 (Eyedropper in object selection box doesn't work)\n* #76124 (Cannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager)\n\nMost of these issues probably have similar roots (e.g. code not checking if `CTX_wm_menu()` can be used over `CTX_wm_region()`, but often times the former returns `NULL` when it shouldn't)." ]

[ "Grease Pencil top material list not working after commit 92d185faebeac60ec2591c2a7c0f870e7726593d\nAfter the commit 92d185faebeac60ec2591c2a7c0f870e7726593d, the materials in the top bar are not working.\n\nThere are an error in python:\n\n\n\n```\n File \"C:\\MyBlender\\BlenderBin\\bin\\Debug\\2.80\\scripts\\startup\\bl_ui\\properties_grease_pencil_common.py\", line 864, in poll\n ma = context.material\nAttributeError: 'Context' object has no attribute 'material'\n\nlocation: C:\\MyBlender\\BlenderBin\\bin\\Debug\\2.80\\scripts\\startup\\bl_ui\\space_topbar.py:342\n\n```" ]

[ "Geometry 100% transparent still affects Subsurface Scattering in the same mesh\nrenderer:\t'NVIDIA GeForce RTX 3060/PCIe/SSE2'\nplatform: 'Windows-10-10.0.19044-SP0'\nAMD Ryzen 2990wx 32-core 64gig ram no overclock\n[system-info.txt](system-info.txt)\n\nVersion: 3.2.2 - 3.4.1\n\nThe included file is a section of a skull with eyebrows close to the surface. \n\nUsing SSS for the skull and transparency for the eyebrows, the result is the eyebrow is light on the surface of the skull.\nThis is using CLOSURE_BSSRDF_BURLEY_ID walk.\nUsing random walk the eyebrow renders transparent.\nHappens on CPU or GPU\n\n\n- Load up the supplied file.\n- render by hitting F12 (Notice the eyebrows are leaving a bright silhouette on the skull surface).\n- Now switch both the eyebrow and skinhead scatter shaders materials to random walk for method.\nIssue goes away and the eyebrows are 100% transparent.\n\n[badeyebrowswithscatter.blend](badeyebrowswithscatter.blend)\n", "Inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken:\n3.2.0 Alpha 2022-05-01 a5644f9a28ea\n3.1.2 2022-03-31 cc66d1020c3b\n3.0.1 2022-01-25 dc2d18018171\n2.93.9 2022-04-19 31712ce77a6a\n2.83.19 (can't find build details)\n\nWorked: -\n\nThere's an inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys.\n\nWith Subdivide Edge Ring, no matter what kind of interpolation and profile factor you use, the one applied to all other shape keys will use \"Linear\" and \"0\" respectively.\n\nWith Subdivide, if you use it on the Basis shape key, all other shape keys will inherit half of the transform of the \"smoothness\" setting, and they will be transformed in some undefined manner by the \"fractal\" setting as well. If you use it on non-Basis shape key, in addition to the described behavior with remaining shape keys, the Basis shape key will always use the default settings (smoothness and fractal = 0).\n\n**Exact steps for others to reproduce the error / sort-of-transcript of the video**\nwatch?v=s9dPcdHOlpo\nIf you use the Subdivide Edge Ring, leave the default settings, and go through the shape keys, you can see that the positions of vertices are slightly off between the current/modified shapekey and others.\nHowever, that changes when you change interpolation to \"Linear\" - then they start being the same.\nWhen you go through various options it seems that the only thing applied properly across all shape keys is the number of cuts.\nAll shape keys other-than-the-active-one seem to always be using the \"Linear\" interpolation, and profile factor = \"0\"\nFrom my tests it doesn't matter which shape key you use this action on - it will always have the same effect between the current shape key and all other.\n\nNow, there's something even weirder goin on with the regular Subdivide.\nIf we Subdivide the mesh with default settings, it will look the same in all shape keys - that's great.\nHowever, if we change something, then the mesh across shapekeys will look different.\nAs a general rule, if we Subdivide a shapekey like Key 2, then the Basis will look like it was Subdivided with the default settings instead of the chosen ones (besides the number of cuts), but all other shape keys will also be modified, just in a different way than the active shapekey.\nFor example, if we change the smoothness of our Subdivide, then other shapekeys will look just \"less modified\". If we check the coordinates of the vertices, then we can see that in Key 1 they are transformed exactly half-way to their position in Key 2.\nHowever, if we use the Fractal setting, then the results are different: The Basis is still default-Subdivided, but the vertices of Key 1 are not just halfway there to the positions of Key 1 - they're completely different.\nOn a final note, with regular Subdivide, if, instead of Subdividing Key 2 you did that to the Basis, then both Key 1 and 2 would look like Key 1 in my example. There would be no shape key that stays with default Subdivide settings.", "Incorrect Rendering For Weighted/Custom Normals\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.1.2\nWorked: Unknown\n\nRendering in Evee and Cycles appears incorrect when using the Weighted Normals modifier or when manually creating custom normal data. This can be seen quite easily using the \"Normal\" Render Pass in the Material Preview or Rendered viewport shading modes, but it also affects rendering in the normal \"Combined\" mode.\n\n\n1. Delete all but the top and one side (facing the x-axis) of the default cube.\n2. Select the remaining edge and bevel it using a width of 0.1 with a single segment.\n3. In Object Mode, set the object to smooth shading and enable Auto Smooth on the Object Data Properties panel.\n4. Add a Weighted Normals modifier and set it to: Mode = \"Face Area\", Weight = 100.\n5. Applying the modifier does not seem to matter, but it makes it possible to view the vertex normals in edit mode by selecting the \"Display Split Normals\" in the Viewport Overlay panel. The normals on the beveled edges should point straight up and down the x-axis.\n6. Select the Material Preview shading mode and click the drop-down next to it to set the Render Pass to \"Normal\".\n7. Rotate the camera around the object so that the angle is similar to the screenshot (a low pitch). Note how harsh the beveled edge is at the top. This *should* be a smooth transition to \"blue\" as the normals are pointing straight up at this location.\n8. Now rotate the camera so that it is looking directly at the beveled face similar to the second screenshot. The camera should have a pitch of roughly 45 degrees. Notice how the hard edge disappears and there is now a smooth transition from red to purple to blue. This should be the appearance from any camera angle.\n\nAs a second test I exported this object to glTF and brought it into Unity where I could create a shader to preview the normals there. The results were as expected and no harsh edge exists at any camera angle in Unity.\n\n\n\n[IncorrectNormals.blend](IncorrectNormals.blend)", "Regression: Ambient Occlusion causes shading artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.1\nWorked: 2.91, 2.92\n\n Under lookdev mode, when object has \"alpha blend\" turned on in the shader, \"ambient occlusion\" with \"bent normal\" option enabled will cause shading artifact that looks like the object is shading flat. \n\nSwitch the scene to lookdev mode. \nCreate a UV sphere\nShade it smooth\nTurn on Ambient Occlusion and make sure \"Bent Normals\" is checked. \nAssign a material to the sphere. \nUnder the material settings turn on \"Alpha Blend\". \nNow the object will look like it's shaded flat/without smoothing. \n\n[Eevee_bug_scene.blend](Eevee_bug_scene.blend)\n\n", "Weight paint vertex select difficult to see (depends on surface color)\nThis is an issue since 3.2x\n\n**Short description of the issue**\nVertex selection is difficult to see in some cases, depending on the surface color.\n\nChanging the view-port shading \"Color\" can make the unselected vertex color match the selected vertices color.\n\n<video src=\"attachment\" title=\"screenshot.webm\"></video>\n\n**Exact steps for others to reproduce the issue**\n- Open attached .blend file.\n", "Render difference with big quad light and ray visibility\nall vendors\n\nBroken: 1ebc14064b\nWorked: 2.79a\n\nsome parts of principled shader render very glossy in latest master\n\nOpen attached file [bug principled v2.blend](bug_principled_v2.blend), render. \nIn 2.79a you get this (correct):\n\nand in latest master this:\n\nNote that I replaced wood tex by voronoi in file, but differences are also obvious.", "Cycles shaders show up in EEVEE list (Properties > Material tab > Surface panel)\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.80 (sub 75)\nAlso confirmed broken in 2.80 release candidates 2 and 3\nWorked: ----\n\nSome shaders not yet available in EEVEE, such as the Toon shader, are included in the list of shaders in the materials tab of the properties window even when EEVEE is selected as the render engine. When such shaders are selected, adjusting most of their parameters has no effect on the viewport/render. Currently, the only way to know which shaders are supported is either by trial and error or by using the node editor.\n\n1. With a fresh blender scene, check that EEVEE is the selected render engine, and go to materials tab in the properties window\n2. You should already have a material if it's the default cube scene. In the surface panel, click on the shader selector (set to principled BSDF by default)\n3. The menu that shows up includes Toon shader among other unsupported ones.\n\n[Based on the default startup]\n\n**Screenshot**\n\n\n", "Mesh Normals and Auto Smooth in 4.1\n## Background\n\nThis document describes changes to the calculation of mesh normals meant to address some of the performance and usability problems, non-exhaustively listed here:\n- Vertex normals are always calculated, even if the shading is sharp and they are unnecessary.\n - Similarly, when auto smooth is enabled, per-face-corner normals are always calculated, even if the mesh is shaded entirely smooth or sharp.\n- \"Auto Smooth\" is a mesh property, even though it can be exposed more intuitively as an **action** applied to meshes.\n - As an action, auto smooth is unified with other ways to control the sharpness of mesh edges and faces, unifying the system and removing the need to learn another method of control.\n- The **extra step** of enabling auto smooth is required to have mixed sharp and smooth shading.\n - For example, marking sharp edges on a smooth shaded mesh doesn't do anything. That's why some modifiers have to tell you to \"Enable Auto Smooth in mesh properties!\"\n- Without further configuration, auto smooth **always recalculates** sharp edges. With deforming meshes, it generally makes no sense to change sharp edge flags over deformation.\n - Even understanding this issue is confusing because, as mentioned, auto smooth is portrayed as a property rather than an action.\n- Using custom normals forces calculating normals per-face-corner, even in cases where splitting normals across edges isn't necessary. This is much worse for performance.\n- Custom normals are always stored as `short2` in a special coordinate space defined by the automatically calculated normals. Converting to and from this coordinate space is expensive.\n - This forces calculating automatic face corner normals to view them, even if the custom normals were hypothetically generated procedurally.\n - Custom normal spaces also make per-vertex custom normals impossible.\n\n## Solutions\n\n### Procedural Custom Normals\n\nTwo new geometry nodes features can allow reading and writing custom normals in a procedural context.\n\n1. **Set Custom Normals** has a choice between creating vertex and face corner normals, a vector input, and an option for whether to write normals in the stable-over-deformation custom normals space (the one currently used for custom normals), or as regular vectors.\n - The last part represents another new feature. If they are stored in this \"plain vector\" format, further use of normals doesn't have to recalculate anything, compared to the existing custom space system, where the automatic normals need to be calculated to find the actual custom normal vectors. That works well when normals are set procedurally at the end of modifier stack anyway.\n - With the vertex domain, only the plain vector format would be supported, unless we wanted to add another normal space option for vertices.\n2. The **True Normal** output/node adds to the existing \"Normal\" node. It outputs normals without custom normals.\n - This could be a new node, or a new socket to the existing \"Normal\" node.\n - Versioning would replace existing nodes with this output.\n\nFor the \"plain vector\" format, the regular `float3` attribute type can be used. Potentially, meta-data could tell geometry processing algorithms to interpolate the attribute differently if they support it (a simple case is the \"Transform Geometry\" node). But generally the existing custom normals space `short2` storage should be used if better interpolation is necessary.\n\n#### Curve Normals\n\nCustom normals should be possible for curves too, though with a separate node since the options are different. The existing \"Set Curve Normal\" node can be used to set custom per-point normals. These may be automatically changed later to make them perpendicular with the tangents.\n\nThe creation of a per-curve \"up\" vector attribute to influence the starting direction used for normals calculated automatically with the existing modes could be supported too.\n\n\n### Replace \"Auto Smooth\"\n\n\n_The existing auto smooth option_\n\nBy writing to the `sharp_edge` attribute, we can have the same effect as auto smooth with a geometry nodes modifier. Versioning code replaces the property with this modifier.\n\n\n_The modifier that replaces the property_\n\nThe modifier keeps the same behavior as before, but often it isn't necessary to change the sharp edges in the modifier stack-- doing it once in edit mode is enough. Similarly, applying the modifier can avoid changing sharp edges over deformation and give better performance. Using a modifier also gives an intuitive way to disable the effect in the viewport, without requiring drivers.\n\n\n_This existing edit mode operator is also useful_\n\nTo keep the existing behavior accessible, an new operator with the same \"Auto Smooth\" name can add this modifier. Eventually though, the node group should be moved to the Essentials asset bundle. That can happen as soon as we have a quick way to add node groups assets as modifiers in the property editor.\n\nCombined with the next auto-domain-choice change, this gives proper control of split face corner normals to geometry nodes. Without the auto smooth option, joining meshes with different sharp/smooth attributes would just work, without relying on the first mesh having auto smooth set. Having the final sharp edge status as part of the visible state of the mesh is essential to make this work.\n\nUsing modifiers for this sort of behavior unifies Blender's design to use user-controllable geometry nodes for geometry processing operations. This design is more obvious in the big picture considering a future where \"everything nodes\" improves the consistency, power, and reliability of Blender features, makes UX more consistent, and improves the development process.\n\n### Automatically Determine Necessary Domain\n\nWith the `sharp_edge` and `sharp_face` boolean attributes, we have all the information we need to know whether we need normals per-face, per-vertex, or per-face-corner. This information is important, because the performance difference between the three is quite large. When the mesh is entirely sharp, face normals are enough. When the mesh is entirely smooth, we need to calculate vertex normals. If there is a mix, we need \"split\" face corner normals.\n\nThis change makes the \"Auto Smooth\" property unnecessary, since one of its main uses was to avoid the performance cost of face corner normals. It's easy to figure the necessary normals automatically, completely removing this step in using mixed smooth and sharp shading, without paying a performance cost in the simpler cases.\n\nThe previous workflow:\n- Enable auto smooth\n- Set auto smooth angle, or set to 180 degrees for complete manual control \n- Run \"Shade smooth\"\n- Mark some edges sharp\n\nThe new workflow:\n- Run \"Shade Smooth\"\n- Mark some edges sharp\n\nPartially this is just a performance optimization (enabled by the removal of auto smooth as a property), but it's also a conceptual change. After the change, the sharp shading status is clearly part of the visible state of the mesh that can be \"frozen\", it's only the shading that's automatic. Before, both of those things were automatic, happening only internally.\n\n## FAQ / Common Concerns\n\n1. This disrupts implicit instancing of objects using the same mesh\n - Implicit sharing of mesh data negates negative aspects of this.\n - Applying the modifier removes the issue completely. Since there aren't any other modifiers, there shouldn't be much of a downside to this anyway.\n - In the future, the \"auto instancing\" could take identical modifiers into account.\n2. Managing auto smoothing on many objects may get more difficult\n - As more features are tied to geometry nodes and modifiers recently, this is clearly a more general issue.\n - It's easy to imagine features to add or remove a modifier on all selected objects.\n - The existing \"hold alt\" feature already works with modifier visibility.\n - The \"Copy to Selected\" modifier feature is also important here.\n3. How accessible is the feature now?\n - Extending add modifier menu with assets (#111717) combined with searching of menus and remembering recent searches (all planned for 4.0) addresses this\n - While the location of auto smoothing moves, and has to be relearned, the consistency and flexibility is worth it\n4. This impacts exporter's special features relating to auto smooth\n - It is true that handling auto smooth as a special feature in exporters becomes more difficult. My hope is that the simplification of behavior (no need for the option, just working with sharp tags, etc.) offsets the downside of this.\n5. There is extra \"stuff\" in geometry nodes modifier panel\n - The extra unused panels can be removed one the node panels features make their way to the modifier.\n - The data-block picker doesn't have to be displayed when adding modifiers from assets, but that is lower priority.\n\n## Technical Info\n\n| Sharp Edges | Sharp Face | Normal Domain | Approximate Cost |\n| ----------- | ---------- | ------------- | ---------------- |\n| All True | All True | Face | 1.0x |\n| Any | All True | Face | 1.0x |\n| All True | Any | Face | 1.0x |\n| All False | All False | Vertex | 4.0x |\n| Mixed | Mixed | Face Corner | 10.0x |\n\nA function `eAttrDomain Mesh::normal_domain_all_info() const;` gives us this information. We can use its result to optimize normal sampling in many places. Viewport drawing would be one important example.\n\nCorner normals are now shared with a `SharedCache`, meaning they don't have to be recomputed just because a mesh is copied.\n\n## Implementation TODOs\n\n- [ ] Double check shape key export workflow\n- [x] Update PR description to be more clear about what parts of the Python API change and to reference the modifier add menu changes\n- [x] \"Unpublish\" the \"Smooth by Angle\" asset in 4.0\n- [ ] Test PR with module members\n- [ ] Work on viewport normals simplification option that skips corner normals and custom normals\n- [ ] Iterate on the \"Smooth by Angle\" asset\n - [ ] Potentially not exactly reimplement auto smooth behavior\n - [ ] Potentially add options to give higher level access to different behavior\n - [ ] Reconsider name based on above decisions\n- [ ] Start implementation of custom normals geometry nodes\n\nRelated PRs: #108014", "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.", "Light clamping from Normal or Bump maps near shadow terminator in Cycles\nOperating system : Windows 11\nCPU : AMD Ryzen 9 3900X\nGraphics card : RTX 3090\nRAM : 32GB\nHas also been tested on a Ryzen 7 Laptop with Ubuntu.\n\nHas been tested on every major release post 2.9, and on 3.6 build d5fc1b9ba4b8, identical behavior on all of them.\nAll provided screenshots of the test file (and the test file itself) were made with 3.5.1 Stable (build e1ccd9d4a1d3)\n\nAll normal information from a Height map passed through a Bump Node or from a Normal Map passed through a Normal Map node introduces some sort of light-clamping around the shadow terminator. The effect starts being visible at an angle of around 66° from the light source.\nThis is especially visible when the target object is Cylindrical and/or Spherical, and lit by a single Light source (Sun Lamp).\nIt looks like this behavior doesn't affect the Displacement node, since using it in Bump Only mode instead of the Bump node gives different results (they should both give identical results, as I understand it).\n\nFrom looking at other renderers (and aesthetically speaking) it looks like the way the Displacement node does it is supposed to be the correct one.\n\nA test Blend file is provided.\n\nSimplest way to reproduce it from scratch is to put a simple repeating height pattern on a smooth cylinder, using a bump node and a simple diffuse node, and lighting that cylinder from the side with a single Sun lamp.\n\nThe behavior of the Displacement node can be tested (and compared with the Bump/Normal) by plugging the same Height pattern into a Displacement node with the Shader Option set to \"Bump Only\", and plugging that displacement node into the Material Output.\n\nI was initially thinking it to be related to (or the same issue as) this one :\n95729\nBut it has apparently been fixed (105776), while the clamping is still clearly visible even in very recent builds.\n\n", "Fluid simulation result not visible after reloading file\nOperating system: MacOs\nGraphics card: Intel Iris Plus Graphics 640\n\nBroken: 2.91\nWorked: -\n\nHello. After I opened project, that I closed before, the fluid simulation didn't exist. It is very easy, to know the issue. Thanks for attention.\n- New file\n- Quick liquid effect on default cube\n- Save file\n- Close Blender\n- Open the same file again\n- The domain is just a smooth shaded cube until you play the file long enough for it to loop back to the first frame.", "Backface culling is not working for mask in edit mode\n2.80 (sub 45), 893fa598319e, 2019-02-24 22:02\n\nAnd wireframe too heavy.\n\n\n\nIdk if it is bug or intended, but it will be nice, if it will work like on the 2nd or 3rd picture: much more readable.\nAnd when x-ray is on, wireframe on the background will be faded too, accordingly slider-setting.\n\n\n\n\n", "Cycles: principled BSDF thin surface support\n[D2354: Thin surface approximation for Cycles Disney BSDF](D2354)\n\nRebase and benchmark performance impact.", "Render artifacts in Cycles with multi material with sss combined with glass or transparent \nOperating system:\nGraphics card: rtx 2080 TI\n[Bug_joined_object_sss_and_transparency_01.blend](Bug_joined_object_sss_and_transparency_01.blend)\n\nBlender version 3.0 stable\nRender artifacts in Cycles when rendering a multi material mesh with sss combined with glass or transparent shader. the transparent shader is shadowing the sss part of the model. this is not the case when the shaders are also separated in to two different objects. \n\nCreate two boxes assign a sss shader to one and transparent shader to the other. render in viewport. It works as supposed to. Now join the two objects in to one mesh. Render and see the \"shadow\" artifacts. or see attached file", "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations." ]

[ "Cycles Terminator Effect\nOperating system: Win 10 latest\nGraphics card: GTX 1060\n\nBroken: 2.80 in general\nWorked: seems to be a general issue\n\nShading of meshes will get \"flat shaded shadow borders\". This effect is called \"Terminator Effect\".\n\nJust setup a scene with a standard sphere. Smooth it and use a lighting with harder shadows.\n\nThis is the effect with HDRI lighting: \n\nThis is the effect with an Area Light: \n\nScaling the Area Light from 1m to 0,3m: " ]

[ "Add size of IDs on disk to Outliner info\nIn complex files/production context, it can be very useful to be able to quickly see the size used by data-blocks, which ones are very heavy, etc.\n\nThis could be done e.g. by checking the last undo step, size is stored in memory chunks, so by doing a quick loop over all BHeads we should be able to get the size of each ID on disk? Or maybe even more efficient, storing that info in IDs after each undo step is written, generating it would then be almost for free.\n\nOutliner could then have a optional column to display that info.", "Some bone animations break upon performing unrelated actions\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.2.0\nWorked: Unsure\n\nI have noticed that sometimes, doing random actions will break existing working animations in a blender project, but only for some bones. I'm not even sure what random actions will cause this - I've always had to resort to just loading from the last saved version. However, I do have a way to reproduce this issue almost 100% of the time really easily:\n\n*Open this blender file:\n*Select the armature (It's called \"Armature\")\n*Open the action \"Reload\" in the action editor\n*Play the animation, see that it is working\n*Now, turn on or off the fake user save toggle button (the shield icon)\n*Play the animation again, notice how the wrists no longer move, but everything else still moves.\n\n[template.blend](template.blend)\n\nThis can also be prevented by:\n- open file\n- select the armature (It's called \"Armature\")\n- go to posemode\n- select all bones\n- go back to objectmode \n- continue with the steps above (\"*Open the action \"Reload\" in the action editor\")\n- bug does not occur\n\nNote this does not have to be the the fake user save toggle button (the shield icon), e.g. toggling Manual Frame Range in the Action Editor triggers this, too\n\nworkaround (until this is fixed for good):\n\n- go to posemode\n- select all bones\n- change any setting that triggers re-evaluation of the action (this might be clicking the fake user save toggle button (the shield icon) again, or toggling Manual Frame Range in the Action Editor, or changing a keyframe or curve visibility in the Graph Editor\n- Action is working again\n", "When changing the width of frame, it also changes frame location.\nIf you create frame and set it into (0,0) location. Then grab right side of the frame node and make frames width bigger. Now using python read the frame \nlocation again and it is not (0,0) anymore. \n\n", "Transform orientation undo is inconsistent.\n\nBroken: 3.0\nWorked: ?\n\nTransform orientation undo is inconsistent. It works in object mode, but doesn't work properly in edit mode. In edit mode it sometimes won't undo, or undoes together with another different step(like changing mode, or moving vertex).\n\n- Open default startup;\n- Change the Transform Orientation from Global to something else\n- Undo/redo - it works;\n\n---\n- Reopen default file\n- Go to edit mode\n- move vertex\n- Change the Transform Orientation\n- undo multiple times - Will never undo the Transform Orientation. (now deselect cube and perform undo operation: will revert selected transform orientation)\n\n", "Perstistant data causes point cloud objects to move\nOperating system: WIndows 10\nGraphics card: RTX 3070Ti\n\nBroken: Latest 3.4 Alpha of time of writing\nWorked: Tested back to 3.0 where the domain size node doesn't exist.\nCorrect location, no persistent data: \nRandom location, using persistent data \nA combination of animating the point cloud count and Persistent data causes the point cloud to move from its set location. \nBased on the default startup or an attached .blend file (as simple as possible).\nRender with and without persistant data.\n[Bug_test.blend](Bug_test.blend)", "Always write unused IDs on save\n#61141 raises again the issue of not writing IDs with zero users on file save. This has also been a long known pain for artists, especially when starting to work with Blender.\n\n*Historical reason for this behavior was that it used to be pretty impossible to properly delete an ID while Blender was running, and that undoing such deletion was impossible. Those issues have been fixed since several years now.*\n\nProposal\n----------\n\n* - [ ] Do write datablocks with zero users on save *(the only exceptions could be library and linked data-blocks, I think?)*.\n* - [ ] When deleting some IDs, also delete its 'dependencies' if they are no more used at all.\n** - [ ] Main case: when deleting object, also delete its object data, shape keys, particle systems, ... *(this solves most of 'free large amounts of memory' issue)*\n** - [ ] Likewise, when deleting any ID, also delete its animdata's Action if not used anywhere else.\n** - [ ] This could also be options in the user preferences (similar to what we have currently to control what gets duplicated).\n* - [x] Make Purge accessible from the File menu and Blender File view in the outliner.\n* - [ ] Add an option to the Preferences, to run recursive purge on file save (see also #87490 (Recursive Purge Orphans datablocks on file save)).\n* - [ ] Changes to Purge operator itself:\n** - [x] Make purge recursive (i.e. also delete IDs that are currently used, but would have no users once currently unused ones get deleted).\n** - [x] Before it runs, show a popup with info on data types that will be deleted (5 materials, 3 meshes, etc) and allow users to confirm or cancel.\n** - [ ] Ideally should also allow expanded view to see exactly which datablocks?\n** - [ ] Add option to select which data types to purge.\n** - [x] After running, show \"X datablocks deleted\" message in the status bar.\n** - [x] Make it not save and reload?\n** - [x] Support undoing ID purge/deletion.\n\nAbout Fake User\n-------------------\n\n* - [ ] Tweak the ID template: remove the 'fake user' button, and have an 'unlink' button (`X` icon), and a delete button (`trashcan` icon).\n\n**Alternative 1**\n* - [ ] Keep fake user for use in the Outliner mostly (orphaned view, allows to do batch deletion while keeping some IDs with the purge button).\n* - [ ] Enable fake user by default for some data-block types:\n** - [ ] Materials, Textures, Images, Node groups.\n** - [ ] Brushes (already done iirc), Palettes…\n** - [ ] Others?\n\n**Alternative 2**\n* - [ ] Fully remove Fake User, and instead rely on the new `marked as asset` feature to protect IDs from purge deletion.\n** - [ ] This would imply a `do_version` to convert existing 'fake users' to 'marked as assets' IDs.\n\nNotes\n-------\n\n* Code wise, changes should be very minimal, unless we have to do a lot of UI work (would not expect it).", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Bone isn't affected by influence keyframe if the action is shared (*).\n(*) The complete tittle would be: \"Bone isn't affected by influence keyframe if the same action is shared with another armature with bones with different names\".\n\n[80-influence-not-respected.blend](80-influence-not-respected.blend)\n\n- Open the file.\n- Move in timeline and see what the bone (armature \"B\") does with its constraint.\n- Select armature \"C\".\n- Move across the timeline in DopeSheet: **bone of armature \"B\" isn't affected by influence keyframe**\n\nThe channel of the armature \"C\" gets red underlined. So, the Action is affected of this \"red-underlineness\"... so, armature \"B\" is affected too.\n\nI know that this is a kinky bug... it is not normal/suggested to use the same action in different armatures with different bones. I discovered this bug by doing that, by mistake.\n\nMaybe it is not usefull to put time on fixing it, because it is not a normal configuration. You guys decide.\n\n", "Memory leak with no actions at all.\nOperating system: Linux-5.13.0-44-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.2.2\nWorked: version: 2.93.9\nI just open any version of Blender since 3.0 and just moving the mouse around makes the amount of memory used by Blender rise. It doesn't stop. It doesn't liberate the memory, ever. It just goes higher and higher, until the memory is full. At first, I thought it was something related to the projects and operations I was doing. I tried to reduce the undo steps and everything else that's advised to reduce memory consumption, and today I realized that simply moving the mouse around was already increasing the memory usage of Blender. I don't need to do any actions\n\nNow, I have two versions of Blender open, to compare 2.93.9 and 3.2.2. Both have the same scene: Susanne, a camera, and a point light. At first, Blender 3.2.2 started with a smaller amount of memory, something around 260K, against the 320K of Blender 2.93.9. But slowly it grows and doesn't stop. Just moving the mouse around or navigating through the scene. \n\nAt some points, for any reason, the memory in 2.93.9 also rises, but then it goes back to normal, but not in 3.2.2. It only rises. \nAt this point, this is the difference in memory usage for both for that specific scene:\n\nTried to create a new scene to see if Blender releases the memory, but no result. When working on my projects, I need to restart Blender to get the memory back to normal. That happens several times a day, depending on the size of the project.\n\nNow that I am finishing to explain, I see that the 2.93.9 memory usage raised a bit, it's on: \nBut if I open the window there, it goes back to normal, but not the 3.2.2.\n\nTo prove that, I just opened the 2.93.9 window and see what happened: it went back to the initial amount of memory. But the 3.2.2 only rises. Now, at the end of this report: \n\nOpen blender in a default scene and see the memory consumption rise as you move the mouse around.\n\nI tried to find similar reports to avoid duplicating them, but I did not find any similar ones.\n\n\nPS: I've tried all versions of Blender since 3.0 I have here and the same happens to all of them.\n", "Drawing boolean\nOperating system: Gentoo Linux\nGraphics card: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti]\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 2.92\nWorked: (newest version of Blender that worked as expected) N/A\n\nFor some reason, displaying a UIList with many collection properties next to a bool property somewhere in the same property tab causes a huge amount of lag.\n\nA bool property which is part of another property group seems to be another workaround to this issue.\n\nI'm developing an add-on which requires the display of large collection properties for construction management of 3D buildings in Blender, which is how I came across this bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nSee attached script, or attached blend file on how to reproduce. The lag seems proportional to the the number of properties in the collection property.\n\nRun script, go to scene properties tab and scroll. Then comment out L19 and try again, lag disappears.\n\n[blenderbug.py](blenderbug.py)\n\n[untitled.blend](untitled.blend)", "View -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes.\nOperating system: Manjaro Linux\nGraphics card: nVidia\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nView -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes. \n\nExpand open the Timeline editor, now adjust the horizontal scale of the view (squeeze or expand), then Ctrl+TAB to swith to Graph Editor mode. Notice the scale does not stay in sych as it does when they are separate windows. ", "Data-block Selector Design Changes (latest iteration)\nNOTE: This task does **not** cover the search menu of the data-block selector. There were ideas for this in the past, but they are not covered here.\n\n## Motivation\n\nThis initially was motivated by the addition of library overrides. Data-block selectors need a way to show library override operations.\n\nThere are a few other issues the following proposal addresses:\n* **Scalability**: The current solution of adding little icon buttons next to the data-block name field doesn't scale well. It only works if there's a small number of operations. We need to be able to place more items for better data-block management. Especially with the introduction of library overrides.\n* **Discoverability**: It's not obvious what some of the icons do. They appear and disappear, but it's not clear why some are available at times and others not.\n* **Unclear Status**: Currently their library status (linked, indirectly linked, broken link, library override) isn't really clear.\n* **Unusual behavior**: Some of the icon buttons allow Shift or Ctrl clicking to invoke alternative behaviors. This is not a usual pattern in Blender.\n* **Misleading/incorrect terms and icons**: The current design mixes \"Duplicate\" and \"New\", as well as \"Delete\" and \"Unlink\". So it's unclear what a click on the duplicate-icon does for example.\n\nThere is a conflict here: Many of the data-block selectors have little space, but users want to see many things at once: Fake user status, user count, name with sufficient space for long ones, often used operations (duplicate, unlink), etc. And there needs to be access to a data-block search box and advanced operations.\n\n## Proposal\n\n[TODO properly explain this]   \n\n**Operations Menu**\n\n**Necessary Changes**\n\n**Remaining Issues**\n\n* Space is still an issue. The proposed design may be an improvement in some regards, but only slightly reduces needed space.\n* For now, this design won't display the library status icon (linked, indirectly linked, broken link, overridden, is-asset). There is just too little space for this. What other ways could we communicate this?\n\n## Higher Level Issues\n\nThere are at least two higher level issues, which are not addressed in this proposal, but can be addressed in a more or less orthogonal way:\n* Fake user is an ancient concept that should probably go (see #61209). Once that is done we don't need to show the fake user status icon. Maybe we can show the library status icon instead then.\n* Data-block selector is \"abused\" for general data-block management, because there is no proper place for that. E.g. the data-block could visualize the data-block relations (e.g. see <2.5 OOPS schematic) and provide better tools for managing them. A data-block selector should really just be used for managing a simple data-block user.", "Multi-object mode support (parent task)\nThis is a parent task to manage to todo's for multi object editing.\n\nThere are many small todo's.\n\n### Reference Patches:\n\nFor anyone interested in helping out, here are some example commits which can be used as a reference.\n\n- Edit Mesh Face Poke - 3a9669bfff *Committed without indentation, so you can see lines changed more easily.*\n- Edit Mesh Flip Normals - 4704f2687a\n- Pose Mode: Flip Quaternions - 7560aabf71\n\n\nOther commits may be useful too.\n\n### Object Loops\n\nThere is some duplicate code for looping over objects.\n\nWe'll keep the option of having a way of simplifying the looping open.\n\n----\n\nNote: to collect operator ID's.\n\n- this script helps copy them from menus: [P656](P656.txt)\n- this is a more efficient version that watches the x11 clipboard so you can hover over items and press Ctrl-C: [P657](P657.txt)", "Animation: create a full separate copy of BoneCollections while in armature edit mode\nThis is to avoid touching the main data structures in the Armature datablock while in edit mode, which interacts badly with undo.\n\nRelevant:\n- #111965\n\n", "Instancing Performance Improvements\nPerformance of instances in the viewport is much worse than is should be. This task is mean to keep track of possible improvements.\n- [ ] Use a vector or similar data structure instead of an linked list for storing an objects instances.\n- [ ] Don't recompute an object's instance list on every redraw.\n- [x] Store bounding box in geometry so that it is not recomputed for every geometry instance (#96968).\n- [ ] Remove the nested instance limit, avoiding the need to realize instances in some cases\n- [ ] Support passing many instances of the same to the render engine at once to reduce per-instance overhead. " ]

[ "Usercount of active action increases when editing things with COW enabled\n# Case 1: Adding Poses to Pose Library\n\n1) With the given test file [bone_cow-poselib_usercount_bug.blend](bone_cow-poselib_usercount_bug.blend)\n2) Add a Pose Library (via properties editor)\n3) Add a new pose to pose library (via properties editor)\n4) Note that usercount of active action (see Dopesheet) increases\n5) Repeat... usercount increases every time.\n\nTested with 0636acc59ab + `--enable-copy-on-write`\n\n\n# Case 2: Rotating bones in Pose Mode\n\n(Reported on IRC)" ]

[ "Changing the 'Render Region' when rendering with Python with 'Persistent Images' checked results in glitched renders\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 1)\nWorked: -\n\n\nI have a (simplified) script that moves to a specific frame, sets the render region to a specific position and renders, before repeating the process for the next frame with a new render region position. When the 'Persistent Images' option in *Render> Performance> Final Render* is on, some of the resulting renders are glitched (they open but have artifacts) and the objects do not seem to be in the correct position. \n\nTurning off 'Persistent Images' results in renders with the objects in the expected location and without artifacts.\n\nFor some context, I do not specifically *want* to have 'Persistent Images' on; I have an add-on which repositions the render border on a per-frame basis and a user reported glitching renders.\n\n**Frame 8** - Persistent Images **off**- Correct location in render\n\n\n\n**Frame 8** - Persistent Images **on**- Incorrect location in render and artifacts\n\n\n\n**Frame 7** - Persistent Images **off**- Correct location in render\n\n\n\n**Frame 7** - Persistent Images **on**- Incorrect location in render\n\n\n\n\n[Render Region + Persistent Images bug.blend](Render_Region___Persistent_Images_bug.blend)\n\n 1. Open the attached blend file and set an output directory for the render.\n 2. Press 'Run Script' in the open text editor to render out the images.\n\nImages 3, 7, 8 and 9 will probably have artifacts and for the other frames the objects will be in the incorrect location (the border should be positioned perfectly around them).\n\n**Note**: I have set the script to render 10 frames because it seems to depend on what was rendered previously as to whether the glitches/incorrect positions will appear. Rendering the glitched frames on their own does not produce the errors consistently.\n\n", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Cropping of Emitter (Face) By Hair In Render preview\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90 (sub 2)\nWorked: Never\n\nEverything goes back to working order when I press \"Delete Edit\" for the particles. \nI've tried opening the file on two other computers. On one it works as I'd hope but on the other the same issue occurs. \n\nI haven't ran into this issue before now and I can't replicate it.\n\n[Head Hair Bug.blend](Head_Hair_Bug.blend)\n\n\n\nHope the solution to this is simple and easy. Thank you for constantly making Blender better and better.", "Move To Line Begin and Reset View operators in the console editor conflict when pressing Home key\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\n\nIn the python console editor, both the Move To Line Begin and the Reset View operators have the same shortcut \"Home\", so it is not possible to invoke the Move To Line Begin operator.", "render lagging behind tiles\nOperating system: win10\nGraphics card:rts 2070 super\n\n2.81\nwhen rendering, the picture doesnt appear for a while after the render tile already finished rendering that region, not sure if its a bug. didn't see anything like this online. here is a video\n\n\n[bug (2).blend](bug__2_.blend)\n\n- Open file and render\n\n[gnVknluHJZ.mp4](gnVknluHJZ.mp4)", "Momentary interface freezes while EEVEE rendering causes progress bar malfunction\nOperating system: Windows 10, 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.80, 2.81\n\n**Rendering in EEVEE has been causing momentary complete interface freezes for each frame**, which caused the progress bar on the frame render to malfunction and jump very quickly from one value to another, thus giving momentarily true but useless information (note that the progress bar never moved to an incorrect position, it just froze). One thing that assures me this is a bug is **minimizing all Blender windows causes the progress bar visible on the minimized icon to work properly** (but unfortunately one cannot see what frame it's on).\n\nOpen the default blend file.\nRender the animation. The interface on 2.81 has frozen for each frame.", "Statistics Viewport Overlay Showing Incorrect Value\nOperating system: Windows 11\nGraphics card: Nvidia GeForce RTX 1650\n\nBroken: 3.6\nWorked: Every other version I've used so far\n\nWhile working in the viewport, the \"Viewport Overlay: statistics (edges count)\" glitches out and shows the wrong number. Sometimes being absurdly high. The image shows the main objects in my scene with the most geometry, mostly being 2k to 10k faces each. It gets a bit annoying when I can't see the right count. I'm not sure how to reproduce the error on command, but I'll keep looking!\n\nBased on the default startup or an attached .blend file (as simple as possible).\nIt happens mostly while I swap in and out of pose mode but then again, I'm not too sure. However, this is usually the last action I take before I notice. I'm sorry for the insufficient information, but I hope you find the problem.\n\n", "Particle systems render wrong on frame 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5 Release Candidate\n\nA particle system renders moving particles in the wrong place on frame 0, if particles are spawned (=Frame Start) before frame 0.\n\n1. Create a particle system\n2. Set Frame Start to something smaller than 0 (with bigger negative numbers the effect is more obvious, so f.e. Frame Start = -20) (the effect is even more obvious if \"End\" is set to 0 or close to 0)\n3. Set particle object to render (Render -> Render As -> Object; Select Instance Object)\n4. Setting timeline start to 0 and rendering the frames, the wrong particle placement in frame 0 is clearly observable in relation to the next few frames. \n\nMoving the whole project/particle system timing to later frames manually, fixes this location jump. This shows, the problem is only the frame being 0.\n\n[particle_system_bug.blend](particle_system_bug.blend)\n", "Persistent Data causes the Image Editor to not update during rendering + pixel glitches in topper pixel lines\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.1.0 Beta\n\nVery often, when you render a sequence, it was on nearly every scene I was working on, there is not shown the render results, and you see the transparent background.\nUpdate in the image Editor is only shown once the whole render completes.\nSometimes it works randomly on some frames. And sometimes you have even a pixel glitch when the progress is not shown. As shown at the end of the video, you have sometimes that glitch on the top. When it is there, it is always the first\\second pixel line.\nThe Pictures are properly rendered and saved, but often the progress in the render results window is not shown and there are some glitches. But they will not appear in the final picture. ONLY in the render preview.\n\nWorks on my projects every time. Nothing particularly.\n\nWait a little bit. The second frame in the video has a glitch.\n[2022-02-01 19-39-28.mp4](2022-02-01_19-39-28.mp4)\n\nProblem is from on frame 3:\n[2022-02-04 08-09-30.mp4](2022-02-04_08-09-30.mp4)\n[Citty.blend](Citty.blend)", "Gpencil: Build modifier stop woking iwhen we use dot Dash modiifer with Dash=1\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.2.0 Beta\n\nbuild modiifer don't work if Dash modifier use Dash=1 and the Gap diffent to 0 .....that we have dash modifier first and then build modifier\n\nbefore playing\n\n\n\nafter playing \n\n", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "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", "LineArt; Crahes when I reopen a file\nAn old HP laptop with\nOperating system: Linux Ubuntu 18.04.5 LTS\nGraphics card: Mesa DRI Intel(R) HD Graphics 5500 (BDW GT2)\n\nBroken: Blender 2.93.0 Alpha, 3ea1779365b5, master, 2021-03-23 18:34\n\n\nI added two GP LineArt on the scene and it worked and then I saved the scene, with new grease pencil modifiers activated, but when I try to reopen in Blender the same scene crashes every times and I'm not able to see anythings after waiting the processing until crashes without any report. the file is attached.\n\n[yach.tar.xz](yach.tar.xz)", "Wintab rarely gets into a bad state and prevents Blender startup\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nFor a few months now, I have been getting a fairly rare, but reoccurring issue (maybe once a week on average) where Wintab gets into some erroneous state and prevents Blender from starting if the Tablet API setting of the Input preferences is set to `Wintab` or `Automatic`.\nWhen Wintab gets into this erroneous state and Blender is already open, Blender will crash if I attempt to open the User Preferences. I'm not sure what else might cause a crash when Blender is already open.\n\nBy adding extra logging to a custom build of Blender, I've determined that the crash when starting Blender occurs when calling the `open` (`WTOpenA`) function: GHOST_Wintab.cc#L85\n\nMy drawing tablet's software also reports an exception in `WTOpen`, the value of which appears to equal 0xC0000005 which I think indicates a `STATUS_ACCESS_VIOLATION` according to 596a1078-e883-4972-9bbc-49e60bebca55.\n\n\nIn the drawing tablet's software, this exception only occurs if I actually connect the tablet to my PC, whereas Blender crashes even when the tablet is not connected.\n\nCurrently, if I don't actually need my tablet, I'm working around the issue by starting Blender headless, changing the Tablet API setting to Windows Ink, and then starting Blender normally.\n\nI have already tried updating the drivers for my tablet to the newest version and it made no difference.\n\nIf I start Blender with `--debug-wintab`, all that's printed is:\n```\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release> .\\blender.exe --debug-wintab\nRead prefs: \"C:\\Users\\Thomas\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\config\\userpref.blend\"\nLoading Wintab for window 00000000000910C4\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release>\n```\n\nEvery version of Blender I've tried between 2.79 and 4.0.0a crashes unless I have the Tablet API set to `Windows Ink`.\n\nI don't know the specifics of how Wintab is handled, but could it be possible to either catch the exception in `WTOpen` and allow Blender to continue loading, or to check for a connected tablet before attempting to call `WTOpen`, similar to what my tablet's software appears to be doing?\n\nUnfortunately, Wintab getting into this erroneous state where it crashes in `WTOpen` occurs too rarely for me to figure out how to reproduce it and I'm not even sure if it's Blender that is causing it to get into this state in the first place.\n\n", "Deferred deletion of depsgraph copied data\nThis idea is generated from the development of LANPR, but might also be useful for other render engines as well.\n\n**Current Problem:**\n\nIn some cases, a render engine will need to process the copied scene data for a while before anything can be displayed. At the same time, we may not want the UI to be frozen (during viewport preview). So we can do this in a background thread. However, when the background thread is processing the data, the data is deleted by the Depsgrapgh, since the particular draw loop is already concluded by the time our background process ends.\n\n**Suggested Solution:**\n\nTo give a function that tells the Depsgrapgh: \"I'm done with your data, you can delete now\". \n\nFor example, when you need deferred deletion, call something like `DEG_evaluated_scene_set_deferred(s)`, and upon finish processing, call `DEG_deferred_evaluation_finished(s)`.\n\nThere could be some more benefits for EEVEE and Cycles as well. For example, When toggling render preview in those render engines, you don't need to wait until the initial blocking loading process finishes, and it's quick to revert to workbench shading if you accidentally switched to render (You don't need to wait until the interface to unstuck).\n\nAny thoughts on this one :) ?\n\n" ]

[ "Blender 2.8. Clip start minimum value bug \nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nIn \"Clip Start\" field (both as for viewport as for Cameras) you can put NULL (\"0\") and it will change value from nimimum = 0.001m to new minimum = 0.000001m\nAnd in viewport you will see messy of your mesh. I don't know what the purpose of this.. but in my work scene (and in default file too) it always looks like(effect) all mesh is broken. \n7bb4a627ff7bc86bbf959b4a7af707b1.mp4\n\n\nOpen default. Put monkey head. Press N and put into 'Clip Start' field '0'.\n\n" ]

[ "Allow node inputs named A and B to be swapped\nPossible fix to allow node inputs to be swapped.\n\nThis is defined in the `node_link_socket_match` function.\n\nReported in chat by @SimonThommes \n\nIt may be a better solution to add a swappable flag to sockets.", "Lookdev HDRIs are interpreted incorrectly when using different colour spaces\nOperating system: Any\nGraphics card: Any\n\nBroken: 2.82 (sub 1), type: Release\n\nHDRIs installed into Blender for use in Lookdev Mode don't offer an option to set their colour space.\n- Blender probably assumes they are encoded in Rec.709, but this doesn't hold up if they're not.\n- Alternatively, when using a different OCIO config, the Rec.709 colour space is almost never listed as just 'Linear', so Blender picks a different space from the config.\nBoth scenarios cause undesired hue shifts. This is most probably also true for MatCaps, but to be fair I haven't looked yet into how they work.\n\n\n- Install a differently encoded HDRI into Blender, for example one of the EXRs from the imageworks/OpenColorIO-Configs repo on GitHub.\n- Switch the viewport to lookdev mode and activate the newly installed HDRI. The colours will have shifted.\n\nor:\n\n- Start Blender using an alternate OCIO config, such as one from said imageworks/OpenColorIO-Configs repo.\n- Switch the viewport to lookdev mode and try the HDRIs that ship with Blender by default. Those colours will also have shifted.", "Annotation tool: wrong undo order and different in different modes\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: 2.93.2\nBroken: 3.0.0 Alpha, `c1f5ac7cfe`, 2021-07-25 18:36\nBroken: 2.83.17\nWorked: never\n\n\n| Object mode | works correct, as expected. Each undo action undoes 1 stroke |\n| -- | -- |\n| Weight paint | works properly |\n| Vertex paint | works properly most of the time, sometimes as Texture paint |\n| Texture paint | do not undoes each stroke but after number of {key Ctrl+Z} (n=strokes) undoes all strokes simultaneously or disables em at n=strokes+1 and undo previous action (mode switch in my case) |\n| Edit mode | same as Texture paint |\n| Sculpt mode | Undoes strokes one by one, but on the last stroke it do not react to {key Ctrl+Z} once, and then on the secon disables stroke and previous action (mode change) |\n\n**Steps to Reproduce**\n- Open default scene\n- Switch to Edit or texture paint mode\n- Draw 4 strokes with annotation tool\n- Undo 4 times (nothing happens to any stroke)\n- Undo again: Clears all strokes\n[2021-08-15_15-46-27.mp4](2021-08-15_15-46-27.mp4)\n\n", "Bevel modifier profile direction depends on edge/face order\n[2021-04-18 01-18-54.mp4](2021-04-18_01-18-54.mp4)\n\n[01.blend](01.blend)\n\n\n\nIt is recommended that the Solidify modifier reorder the faces. \n\nThis is the problem I encountered when I was making a column. I thought it was bug. \n\nIt was later found that after the Solidify modifier, the Bevel direction is controlled by the face order, and the Bevel modifier has no option for the face order.", "Inconsistent input drag editing\nOperating system:\nGraphics card:\n\nBroken: \nWorked: \n\nSome inputs that allows editing whit mouse drag can change values with any drag movement, and the will be clamped to \nmin-max values, but other inputs relies on mouse position rather that the drag movement, this makes that if the user makes a drag beyond bounds, to be able to edit the values the user need to move the mouse again within the bounds of the input, that is not necessary because mouse is not visible.\n\n\n1. Use the color picker and move the mouse to the left beyond limits\n2. Move the mouse to the right, see that there not instantly a value change, the invisible mouse need to enters within bounds\n\n\n\nHere in the video, i edited the surface radius and is is visible that any movement changes the value\nBut for Surface the mouse need to be reallocated in the input box\nAlso for color picker\nImportant Note: **I force to show the mouse** to see the actual mouse movement, using the slider or color picker without knowing where the mouse is makes it feel weird \n<video src=\"attachment\" title=\"2023-08-16 17-58-31.mp4\" controls></video>\n\n", "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", "Polishing Correct Face Attributes\n- [ ] Initialize operators options based on the \"correct face attribute\" value (e.g., edge slide).\n- [ ] Unify naming of the option and the operator options.\n\nThe way we do Proportional Editing seems to be a good example to follow. These issues have been raised on 4387aff", "Metal Viewport flickering on interaction\nOperating system: Mac OS Monterey, Version 12.6.2\nGraphics card: Apple M1 Max, Mac Book Pro 16 inch 64 GB, LG Ultra Fine Display as secondary monitor\n\nBroken: 3.5.1 release candidate\nWorked: 3.4 with Open GL does not have these issues\n\n\nWhen interacting in the viewport say moving a camera the viewport flickers. Also when adjusting shaders in a cycles window the viewport also flickers depending on the speed of the interaction. Evee viewport does not have this issue, but solid render does\n\nBased on supplied file Look through camera and split the viewport in two. Left side has cycles rendering turned on. Change the default renderer from Eevee to Cycles and change to GPU compute. Rotate camera with the empty and cycles view on left flickers. Next select cube and change the shader colour from pink to any other colour you like. Again viewport flickers like crazy.\n\n", "ShaderToRGB Node plugged to alpha does not work with Alpha Clip or Alpha Hashed mode in 2.90\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.90.0\nWorked: 2.83\n\nIf ShaderToRGB Node is plugged to alpha socket of another princepled BSDF, it does not work if blend mode is alpha clip or alpha hashed in blender 2.90.\nThis combination worked in 2.83\n\nI attached a snapshot image in both cases 2.90 and 2.83.\n\n\n\nLeft image is 2.90, and Right image is 2.83.4.\nThe object becomes fully transparent in 2.90 case.\n(Though, It works if blend mode is alpha blend. \nThe problem is only in alpha clip or alpha hashed mode.)\n\n- Open the attached file in blender 2.83 and 2.90\n- Compare the viewport of both\n[ShaderToRGB_Problem.blend](ShaderToRGB_Problem.blend)", "Alpha mode 'Straight' on Image Texture node behaves differently between Cycles and Eevee\nOperating system: Windows 10 Pro x64\nGraphics card: GTX 1080Ti for display, RTX 3090 for render\n\nBroken: 3.3.1\nWorked: I don't know\n\nWhen the `Alpha` property is set to `Straight`, the result is different between Eevee and Cycles.\n\n\n- Open the .blend file provided\n- Set one of the viewports to Material Preview and the other to Rendered\nNote that the results of the images are different\n[alpha_mode_eevee_vs_cycles.blend](alpha_mode_eevee_vs_cycles.blend)\n\nOriginal file\n[test leaking_ori.blend](test_leaking_ori.blend)\n", "Filter color bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.1\n\n\nHue color and color bar doesn't sinchronize\n\n1) change object in sculpt mode\n2) use colore filter\n3) option fill\n4) try to change hue color\n\n", "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", "UnMeta Strip messing up strip order\nOperating system: Linux-5.15.28-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.15.28-1-MANJARO, LLVM 13.0.1) AMD 4.5 (Core Profile) Mesa 21.3.7\n\nBroken: 2.79b, 3.1.0, version: 3.2.0 Alpha\nWorked: -\n\nIn some cases, unpacking a meta strip with unmeta messes up the order of the included strips, breaking the compositing setup.\nWhen creating a meta strip, the original absolute channel number of each strip seems to be saved in the meta strip, so, on unpacking, if there is another strip occupying the original channel, there is a \"collision\", no matter how much the meta strip has been moved away vertically from the occupying strip. The \"collision\" is solved by moving only the colliding strips from the meta strip to the top.\n\nFor example, if a source strip of the meta strip was in channel 1 and the meta strip is moved so that channel 1 is occupied by another clip, instead of unpacking the strips relative to the vertical position of the meta strip, the original absolute strip channel values are used and since two strips can't occupy the same space, just the colliding strip is moved.\n\n- Start Blender with the Video Editing preset\n- Add a red color strip to channel 1 and a blue color strip to channel 2\n- select both and Ctrl-G turn them into a meta strip (meta strip is created on channel 2)\n- add a new color strip to channel 1\n- unmeta the meta strip in channel 2\n- now you have blue in the lower channel and red in the upper channel, the order has switched\n\n", "Cycle Shader Displacement does not distinguish Instances by Geometry Nodes\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.0.0 Beta\n\nThe color of shader is different on each instance, but the shader displacement has all the same result for each one.\n\n\n[DISPLACEM.blend](DISPLACEM.blend)", "Opening the Preferences/Render window replaces the current opened window with the other interface\nBroken: version: 2.83 (sub 13) \nWorked: Never\n\nOpening the Preferences/Render window replaces the current opened window with the other interface.\n\n\nMethod 1:\n* Open a new scene/or an existing scene.\n* Press F11 to render the scene.\n* Once rendered, go to the menu “Edit | Preferences...”\n* The preferences interface replaces the render interface in the same window.\n\nMethod 2:\n* Open a new scene/or an existing scene.\n* Go to the menu “Edit | Preferences...”\n* Press F11 to render the scene.\n* The render interface replaces the preferences interface in the same window.\n\nThere is no reason to replace a window/interface by an interface of different functionalities or with a different purpose." ]

[ "EEVEE ignores SSS when mixing shaders \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.83 (sub 6)\n\nEEVEE seems to partially ignore the material mix node (it looks like subsurface pass only) when mixing an SSS shader and a non SSS shader.\n\n\n\n\n\n\n\n - Create material with Principled BSDF and SSS with value of 1 as a control\n - Create material with a mix node that has connected 2 Principled BSDF nodes where they have SSS with value of 1 and 0\n # Repeat 2. but with reversed mix node connections and mix value of 1\n\n[EEVEE SSS bug.blend](EEVEE_SSS_bug.blend)", "Mix Shader Acts Differently in Cycles and Eevee\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\nWorked: never\n\nThe mix shader's factor has been set to 1, however it does not output the second shader in Eevee, it works as expected in Cylces though.\n\nIn the Blender Manual, this is what it says: \"Factor: Blend weight to use for mixing two shaders; at zero it uses the first shader entirely and at one the second shader.\" It does not mention anything about the difference in Eevee and Cycles, so I am assuming it to be a bug.\n\n[Based on an attached .blend file]\n1. Open the attached .blend file, toggle render view\n2. It is currently in Cycles, the two object's mix shaders are working as expected\n3. switch the render engine to Eevee, see how the shaders are acting strange.\n[Mix Shader Bug.blend](Mix_Shader_Bug.blend)\nCycles:\n\nEevee:\n\n\n" ]

[ "Error code in NodeShader Color default_value\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\ncode in files\nthe color default_value require a 3-dimensional array , but when specified as a 3-dimensional array, the red channel is missing\n\n\n", "The alpha channel set in Viewport Display settings for an object's material appears as if it's set to 0 when a background image is behind it\nOperating system: Linux x64 (Debian-based)\nGraphics card: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a)\nNvidia drivers, version: 440.31\nKernel: 4.19.0-6-amd64\n\nBroken: v2.81a and v2.80, downloaded from blender.org as a tar.gz\n\nWhen you change the Viewport Display color for an object to have an alpha channel < 1.0 but > 0.0, then manipulate the scene so that there's a reference or background image behind that geometry, the overlapping area will appear completely transparent (alpha 0.0).\n\n\n1. New scene\n2. Add a cube: Shift a -> Mesh -> Cube\n3. Add an image: Shift a -> Image -> Reference (or background)\n4. Select an image\n5. Position the image behind the cube in the viewport. Select the cube.\n6. In the properties panel, select Material Properties\n7. In the Material Properties panel, select Viewport Display\n8. Change the Color to have an alpha between 0.0 and 1.0, exclusive\n\n**Observed behavior**\nLike the screenshots, the overlapping area allows the background image to completely shine through.\n\nQQxLCpv\n\n**Expected behavior**\nThe object will become uniformly translucent and allow the background/reference image to be partially visible, not make the image fully transparent in the overlap.\n\n", "Front Faces sometimes doesn't work with the Mask tool\nOperating system:\nGraphics card:\n\n3.5.0 beta 24/2/2023\n\n**lasso mask brush mask outside the border when symmetry enable**\n\nThe same as #103163 but in a more extreme case\n\n- Open attached .blend file\n- (optionally) Disable `X axis` mirror\n- Use Lasso or Box Mask tool in the region indicated\n\n[untitled.blend](https://projects.blender.orgattachment)\n", "Alpha textures do not work with holdout collection in Eevee\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Beta\nWorked: None\n\nWhen setting a collection to holdout in Eevee, objects with an alpha texture will display as the entire object being held out, but the expected behaviour is possible using a Holdout shader. This can be very inconvenient as then you have to duplicate and remove all models using alpha textures from the collection and create unique materials for them.\n\nThe collection set to holdout.\n\n\nThe expected behaviour using a material with alpha blend to hold out the object.\n\n - Create an object using an alpha texture (blend mode doesn't seem to matter) in Eevee\n - Set the collection containing it to holdout\n\n\n[HoldoutAlpha.blend](HoldoutAlpha.blend)\n", "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)", "Black Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0\n\nBlack Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field, if Shader Color is not pure white (similar problem with Layer Weight)\n\n**Exact steps for others to reproduce the error**\n- Open attached file (Just a simple box (can be a plane) with Transparent BSDF. Camera' distance or depth of focus influences the result. Attached pictures in Image Editor from a real case).\n- Press F12 to render\n[transprarent_shader_artifacts_with_camera_DOF1.blend](transprarent_shader_artifacts_with_camera_DOF1.blend)\n\n\n", "Eevee render display error in orthographic camera mode: Mesh material color changes during scaling \nOperating system: Win7 Home Premium 64-bit, SP1\nGraphics card: Nvidia GeForce GTX 750\n\nBroken: 2.80, c9df453ce70b, blender2.8, 2018-12-21\n2.80, d96596de294e blender2.80, 2018-12-31\n\nWorkspace: Layout\nObject mode\nDisplay rendered view: Eevee (other rendered views with Cycles, etc. do not have this problem)\nCamera orthographic view (!! in perspective or panoramic view, problem is not there)\nCamera type: orthographic\nLight: Sun shining perpendicular onto objects\n\nThree cube mesh objects with individual materials\n- Principled BSDF\n- Base Color (either Red, Green or Blue)\n\nThe *scaling** of one or more objects changes the color appearance in the camera view *and* in rendering.\n\n**scaling*can happen either:\n- pressing 's' key and move mouse\n- changing scale values in transform tab\n\n - > I thought there seemed to be an dependency on scale values. For example, scaling to 1.0 would always be a lighter tone than in a different scaling factor. But simply pressing 's' to scale and escaping can change the color tone of the mesh as well.\n\nThe direction of the sunlight makes of course a difference when viewing the objects, but after changing sunlight angles there is still the color changes during scaling.\n\nBlend file attached.\n\n\n - Select Display render preview \n - Simply choose one or more cubes \n # scale these slowly and the color will change from a fade color to a strong color infrequently\n\nIt seems the problem is the camera orthographic mode!?\n\n[Scale-Color-error.blend](Scale-Color-error.blend)\n", "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)", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Eevee in VSE as Scene strips - erratic behaviour\nOperating system: Win 10\nGraphics card: Radeon RX580\n\nBroken: 2.80 version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-16 23:08, hash: 12da679fa094, type: Release\nbuild date: 16/06/2019, 17:07\n\nWhen using Eevee Scene Strips in VSE , the VSE viewport shows the wrong items on screen in OpenGL preview, and then the Render also does not show correct layering or camera moves\n\nOpen Blend file\nSee 3 scenes. \n- 2x animated (linked) scenes that render several layers in Eevee properly, then composite as expected\n- 1x Edit scene that has those linked scenes as Scene Strips in the VSE.\n\na) Observe in VSe that the viewport doesn't not reflect each Eevee scene in preview.\nb) Press render in VSE scene, and observe the render layers are broken and don't match the orig scene.\n\n[20190626.blend](20190626.blend)", "Cycles shaders show up in EEVEE list (Properties > Material tab > Surface panel)\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.80 (sub 75)\nAlso confirmed broken in 2.80 release candidates 2 and 3\nWorked: ----\n\nSome shaders not yet available in EEVEE, such as the Toon shader, are included in the list of shaders in the materials tab of the properties window even when EEVEE is selected as the render engine. When such shaders are selected, adjusting most of their parameters has no effect on the viewport/render. Currently, the only way to know which shaders are supported is either by trial and error or by using the node editor.\n\n1. With a fresh blender scene, check that EEVEE is the selected render engine, and go to materials tab in the properties window\n2. You should already have a material if it's the default cube scene. In the surface panel, click on the shader selector (set to principled BSDF by default)\n3. The menu that shows up includes Toon shader among other unsupported ones.\n\n[Based on the default startup]\n\n**Screenshot**\n\n\n", "shadow catcher appearing in vector pass\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\nvector data is present for the shadow catcher objects. This needs to be omitted otherwise the vector blur node can't be used to add motion blur to the 3d elements, because unwanted motion blur will be added to the environment pass. If it a backplate was used then it wouldn't be a problem, transparent film could be set, and the blur would only affect the geometry. This also has an issue though, because the vector blur pass modifies the alpha too, so the shadow catcher vector could still affect the blur of the 3d geometry even if it's hidden by transparency.\n\n\n1. open attached file\n2. go to frame 10\n3. open the compositor\n4. render still frame\n5. check the compositor backdrop (shows vector data for the shadow catcher).\n\nSame result if film is set to transparent.\n\n", "Regression: Some particles have darker faces\nOperating system: Windows 10 1909\nGraphics card: GTX 1070 512.15\n\nBroken: 3.1 (also 3.1.1 RC)\nWorked: 3.0.1\n\nSome object instances, in a hair particle system, have darker faces\n\n3.0.1\n\n\n3.1 and 3.1.1 RC\n\n\nPress F12 in this test file:\n[Dark Particles.blend](Dark_Particles.blend)", "Eevee RGB Curves node inaccurate compared to Cycles\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\n[eevee_rgb_curve.mp4](eevee_rgb_curve.mp4)\nThe transformation that the RGB curves node applies to a color differs slightly between Eevee and Cycles, even if the curve is left as default.\nNot sure if this is a bug or just a known limitation, but it breaks compatibility between Eevee and Cycles in edge cases.\n\n[eevee_rgb_curve.blend](eevee_rgb_curve.blend)\n\n", "Broken 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" ]

[ "[Shading] Backside obsures frontside when Alpha Blend is on\n`Operating system:` Windows 10 Family Edition\n`Graphics card:` Intel(R) HD Graphics 630 & NVIDIA GeForce GTX 1050\n\n`Broken:` 2.80, 9149e894210, blender2.8, 2018-10-16\n\nWhen the material's blend mode is set to *Alpha Blend* and *Show Backside* is on, said backside completely obscures the frontside (at least when transparency 0%, as the frontside gradually becomes more visible as transparency increases).\n\n\n[test-show-backside.blend](test-show-backside.blend)" ]

[ "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Tablet/Pen Usability Problems\nFor the most part any user who is using a Pen/Tablet can easily use Blender but there are still a few inconsistencies in the navigation and functions where in the worst case, you need to constantly switch to a mouse.\n\nFor one there is the inability to scroll through certain areas without using the mouse wheel.\nWhen opening a popup list for example when selecting a material, texture, brush, etc, you can only scroll through the window by using the mouse wheel or by typing in the result that you are looking for. But in all other menus that are not popup related, there is the option to scroll by holding the middle mouse button and moving the cursor up/down. \nAdding this option to these popups or at least adding a scrollbar to the side would make it possible for pen users to scroll through these windows without switching to the mouse temporarily.\n\n\nSome tools have a radius that can be adjusted by either using the mouse wheel or using the Numpad +/- keys. \nThis is the case for example in the Circle Selection and Proportional Editing.\nFor pen users the Numpad +/- keys work but are slow and awkward to use because because you have to cross your arms (depending on your layout & right/left handed) and you have to hit the keys in very quick succession for a while or hold it which created a delay of when the scale changes. \nAdding an extra key like using the F key to change the radius in the Paint/Sculpt Modes could be a solution but can be equally awkward and even more confusing to use. Maybe mapping the increase/decrease radius to the +/- keys as well for the non-numpad users and make holding the key more responsive and fast in resizing is a good improvement at least.\n", "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", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "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.", "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 when switching to Sculpt mode\nOperating system: \nLinux bu-dvl-2 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux\n\nGraphics card:\n0:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)\n\nBroken: 3.2.0\n\ncrashed when switching to Sculpt mode\n\n- Open alien.blend (attached) \n- Switch to Sculpt mode\n\n[alien.blend](alien.blend)\n\ncrash.txt: \n[alien.crash.txt](alien.crash.txt)", "Linked Text Object Data Bug\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.42\n\nBroken: version: 2.93, 3.0.0\nWorked: -\n\nText objects with linked object data behave strangely. Some letters change their shape, which may vary from instance to instance. (see uploaded image)\nMaybe i´ve got the bug is because i use the Small Caps format.\n\n\n1. Create several same text Objects (you maybe should use Small Caps format in them)\n2. Link their Object Data\n3. Try to switch several times between Object and Edit mode and you will see the bug. It occurs everytime on different letter. And every instance of the text looks often different then the others.\nI am attaching the Blend file\n[bug.blend](bug.blend)\n", "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: 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", "Array/Skin-Modifier-Combo causes crash\nOperating system: Linux Mint 19\nGraphics card: GT630\n\nBroken:\n2.80 (sub 39), branch: blender2.8, commit date: 2018-12-20 23:46, hash: 7a26e930a8c0\n\n\nPlease try to toggle the \"visibility\" of the skin modifier in my simple file. It crashes instantly and repeatingly:\n[Procedural leaves feathered1.blend](Procedural_leaves_feathered1.blend)\n", "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", "persisting issue: MacOS, Blender's system device usage rights (info.plist) add camera & mic usage descriptions\nOperating system: MacOS (13.2.1) \nGraphics card: any\n\nBroken: (All Blender addons that would need external peripheral like camera or microphone access, will cause Blender to CRASH, because of MacOS)\nWorked: (it's a MacOS dependent issue (since maybe macOS 12?)\n\n*\n\"Termination Reason: Namespace TCC, Code 0\nThis app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an com.apple.security.device.camera key with a string value explaining to the user how the app uses this data.\"*\n\n\nInstall an anddon that would need camera / microphone access. After checking the checkbox in blender addon menu, Blender crashes (or at the point that addon is running code that would need such peripheral. Nowadays you cannot add it manually and this needs to be addressed globally.\n\nFIX:\nglobally add info.plist usage rights for camera, mic and other widely used peripherals for blender's MacOS version, since the current state of MacOS, doesn't allow addon's to access any of those, and it really hinders the blender as a core, those of course aren't used if not needed, but at the moment addon developer cannot have any modules that use any of those without MACOS causing the blender to literally crash. I hope this could be corrected asap. Before it was still possible to manually grant access to applications via macos settings, but alas, its not anymore possible.\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n" ]

[ "Crash when increasing text object bevel depth\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.83 (sub 11)\nWorked: unknown\n\nWhen I add some bevel depth to a text object, blender crashes. This is the error from the terminal:\n\nBlender(6343,0x700003ec2000) malloc: Incorrect checksum for freed object 0x7f808c457090: probably modified after being freed.\nCorrupt value: 0x3c9bd233bbca8474\nBlender(6343,0x700003ec2000) malloc: ***set a breakpoint in malloc_error_break to debugWith the default blender scene: delete cube. Add text object. In data properties -> geometry -> bevel depth, click on the right arrow a few times to increase the value. Blender crashes, sometimes after clicking once, sometimes after a few times." ]

[ "Confirm On Release in Radial Control doesn't work with Right Mouse Button\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\n\nBroken: version: 3.1.2\nWorked: Never\n\nRadial Control option \"Confirm On Release\" doesn't work if assigned to Right Mouse Button.\n\nGo to Preferences -> Keymap -> 3D View -> Sculpt -> Sculpt (Global) -> Radial Control (not necessarily in this mode it is possible in any other where there is a radial control).\nAssign Right Mouse Button to Radial Control check \"Confirm On Release\" option.\nRMB-drag in 3D viewport then release button and the action will be canceled.", "Touch on Gizmos can return invalid cursor coordinates\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ecb9, type: Release\nbuild date: 23/12/2018, 17:14\nplatform: Windows\n\n\nWhen using a pen, as in a Microsoft Surface or similar device, using the camera Gizmos and moving the pen outside the 3D viewport seems to return null/invalid coordinates, and it breaks. They can ONLY be used inside the 3D viewport. It's an absolute deal breaker for touch screen users (Surface, Wacom, etc)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nAny default .blender. On a touch device using a stylus pen, click on a Gizmo (axis, zoom, or drag) and move the pen outside the 3D viewport.\n\n\nWhen using a regular mouse the cursor gets hidden and it works as intended.", "GHOST/Wayland Support\nGHOST/Wayland support has been committed to master and is enabled for daily builds, this task is an overview of the remaining TODO's. \n\nNote that these could be expanded into their own tasks, listing here for now.\n\n**Library Linking**\n\n- [x] dynamically load libwayland (e58e023e1a)\n\n**Integration**\n\n- [ ] Support display server reconnecting (new feature, not yet supported by main-line MESA), see [KWIN/Restarting](Restarting)\n- [ ] IME (text input) support (see: [text-input-unstable-v3](text-input-unstable-v3)), See: [D17030: [WIP] initial GHOST/Wayland IME support](D17030)\n- [x] Primary clipboard support b0eff51fb7\n\n\n**Input Devices**\n\n* [x] #104272 Touch-pad support for detecting inverted (natural) scroll events 98272e5bb24b865380ad580ce0354ccacb0fa52d (depends on Wayland v1.22 release).\n- [x] Tablet support (pressure sensitivity, angle), 97f894881c\n- [x] NDOF (3D mouse) support 8841bd9660 \n- [x] Detectable key repeat events (`GHOST_TEventKeyData.is_repeat`).\n- [x] #98793 (Wayland clamps cursor movement failes with gnome-shell (fixed up-stream)), up-stream bug in gnome-shell, worked around in Blender.\n- [x] #76429 (GHOST/Wayland event's don't correspond to physical keys)\n- [x] #77311 (Mouse cursor stays in-place with Ghost/Wayland for operators that grab cursor input)\n- [x] High resolution track-pad scroll events 30d9a6245f\n- [x] Touch-pad gesture support (zoom, swipe, rotate.. etc). *lower priority, not supported by Blender under X11.* 8bb211a771\n\n\n**Display**\n\n- [x] Support for DPI detection (`GHOST_GetDPIHint`) 2770010224\n- [x] Support fractional scaling (`fractional-scale-v1`) cde99075e87032d99d986182e98d9c367b22d417\n\n**Windowing**\n\n- [x] Support activating windows 3071ec486bffd0fef180f221a85f0b15f07b7950\n- [x] Support dialog windows (so they're always in-front `GHOST_CreateDialogWindow`, respecting parent windows).\n- [x] #98612 (Window Decorations Not Present on GNOME - Wayland) 29755e1df8\n\n**OpenGL**\n\n- [x] Switch from GLEW to libepoxy, to support dynamic loading of either `libOpenGL.so` or `libGL.so`, patch: [D15291](D15291) (see [D12034](D12034)#312834).\n- [x] #98462 (Save Screenshot (glReadPixels) fails under Wayland)\n- [ ] Enable EGL by default for X11 (This is trivial at this point. Just remove the `USE_EGL` ifdefs in `GHOST_SystemX11.cpp` and `GHOST_WindowX11.cpp`)\n- [ ] Support `libOpenGL.so` and EGL in OpenSubdiv and USD `glLoader`\n\n\n----\n\n**Limitations**\n\nWayland has constraints that might not be practical to work around.\n\n- [ ] #102985 (Wayland: Unable to lower windows)\n- [ ] #98928 (Wayland: Unable to access window position, finding the window under the cursor doesn't work)\n- [ ] #100276 (Wayland: Windows reset when reloaded on a multi-monitor configuration)\n- [ ] Window decorations look out of place (libdecor) see, #101176 and this [merge-request ](43).\n\n**Bugs**\n\n- [x] #100855 (GHOST/Wayland: Terminal Ctrl-C closes the window while Python is running) *Low priority, needs further investigation.*\n- [ ] #103059 (GHOST/Wayland: Huge cursor when using a graphics tablet in KDE) *Low priority, needs further investigation.*\n- [ ] #102999 ([Wayland] Incorrect UI scaling on high-resolution screen under GNOME 42.5 w/ fractional scaling) *Fixed in GNOME 43, not clear how Blender would workaround the bug.*\n\n**Bugs with LibDecor**\n\n- [ ] #109194 Window decoration size doesn't match Blender window size.\n- [ ] #108308 Crash on startup with LibDecor on Wayland.\n- [ ] #107797 Resizing window causes crash on Wayland.\n\n**Bugs with GPU Drivers**\n\n- NVidia\n\n - #110327 Only 3D View-port region is transparent on Wayland (NVidia + Nouveau)\n\n**Bugs with Other Components**\n\nHere are issues that are noticeable with Blender.\n\n- [ ] Gnome-shell doesn't scale custom cursors with Hi-DPI displays: 1215\n- [ ] Gnome-shell doesn't receive tablet input for new windows #107778 2658\n- [ ] #98927 (Cursor input \"low resolution\" with Hi-DPI in gnome-shell), reported to mutter: 2311", "No (selection) tool in Image editor mask mode (Left-click and drag selection doesn't work)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nLeft-click and drag selection doesn't work in Image editor -> Viewer Node -> Mask mode\n\nCreate a mask in the Image Editor and try to select it with left-click and drag selection\n\n\n", "Text editor slider now blocked\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.81 (sub 1)\nWorked: 2.80\n\nNow that the sidebar got moved to the right side, there's times when the slider gets blocked by the arrow and you can't select and move down. \n\n\n\n", "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", "Cannot use Chinese input or Japanese input\nOperating system: Linux-5.4.0-70-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Beta\nWorked: 2.92 ([#issuecomment-224988](87578#issuecomment-224988), [#issuecomment-225000](87578#issuecomment-225000))\n\nCannot use Chinese input or Japanese input\n\nWhen I use Chinese or Japanese input, I get a warning like this on the console \n\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7fca129c0900 0x7fca36c513c0\n\n", "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", "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", "Touchscreen 'Continuous Grab'\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Mobile Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.0.2\n(bug also tested on Windows 10)\n\n\nBroken: version: 2.80 (sub 74)\nWorked:\n\n\n* Activate a gizmo using the **touchscreen** on a computer. (The 3D navigation gizmo for example)\n* Drag your finger outside the original editor\n* The gizmo is manipulated incorrectly\nThis bug disappears if \"*continuous grab*\" is disabled in the User Preferences.\nI think it's a matter of auto-disabling *continuous grab* while receiving touch input, like how pen tablets are handled.", "Greasepencil operators (e.g.bpy.ops.gpencil.stroke_join) fail when running outside the 3Dview\nOperating system: Linux, pop-os 20.04\n\nBroken: 2.91.0 Alpha\n\nbpy.ops.gpencil.stroke_join operator fails ( but returns {'FINISHED'} without error ) when executed from a python script or the build-in python interpreter.\n\nThe operator works fine from the GUI\n[Bug_reproduce.mp4](Bug_reproduce.mp4)", "Python - operator called by gizmo always called the invoke() from the combination ALT + LEFTMOUSE (also asserts)\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.87\n\nBroken: version: 2.83.0\n\nWhen an operator is called by a gizmo, the combination of the event ALT or CTRL or SHIFT + LEFTMOUSE always initialize the operator by calling the invoke(). \nOther combination of keys + LEFTMOUSE does not call the invoke()\nThis problem makes impossible to take into account the industry compatible keymap in the 3dview with the target_set_operator in gizmo.\n\nOpen the file gizmo_operator_invoke.blend\n- Toggle the system console to view the prints\n- Run the script :\n - In the 3dView, click once on the gizmo (gizmo now follows you mouse)\n - now press {key Alt} and start clicking -- using the combination ALT+LEFTMOUSE will call invoke() [inspect in the console] each time\n - use RIGHTCLICK or ESC repeatedly to stop the modal (if you clicked multiple times you have to do {key RMB} multiple times as well )\n - now press {key S} and start clicking -- use the combination \"S\"+LEFTMOUSE will **not** call invoke() [inspect in the console] each time\n - use RIGHTCLICK or ESC a single time to stop the modal\n\nNote: in a Debug build, an Assert should be triggered when pressing {key Alt} and start clicking\n\n```\nBLI_assert failed: source/blender/windowmanager/gizmo/intern/wm_gizmo_map.c:1068, wm_gizmomap_modal_set(), at 'gzmap->gzmap_context.modal == ((void *)0)'\n```\n\n\nThanks for your help\n\n[gizmo_operator_invoke_phi.blend](gizmo_operator_invoke_phi.blend)\n", "Box Select (B) changed to Left Mouse unable to Deselect\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: 3.0, 3.5\nWorked: 2.93.9 (31712ce77a6a), 3.0.0 broke it\n\nBox Select (standard B) changed to Left Mouse ignores Gesture Box Deselect. Instead Deselect now selects Objects.\n\n(See attached Image. These preferences work different until 3.0.0. The Image and Full Version below is basically an alternative to Blenders standard \"Left Mouse Drag Box Select\" which removes the need to hold the mouse button)\n\nPreferences > 3D View > Box Select:\n\n-SHORT VERSION-\n1. Set Left Mouse as Event (Press)\n2. Go to Gesture Box\n3. Change \"Begin - Left Mouse\" to \"Release\"\n4. Use a Left Mouse click + release in 3D View to begin the Box.\n\nProblem: Middle Mouse (Deselect) only selects Objects.\n\n-FULL VERSION-\n1. Set Left Mouse as Event (Press)\n2. Set Mode to Extend\n3. Go to Gesture Box\n3.1 Change \"Begin - Left Mouse\" to \"Release\"\n3.2 Change \"Select - Left Mouse\" to \"Press\"\n3.3 Deactivate \"Begin - Middle Mouse\"\n3.4 Change \"DeSelect - Middle Mouse\" to \"Press\"\n4. Use a Left Mouse click + release in 3D View to begin the Box.\n\nExpected: Left Mouse will select, Middle Mouse will deselect.\nProblem: Middle Mouse (Deselect) only selects Objects.\n\n------\n\nI could not find a way to have it Deselect or if there is a conflict with other settings. Can you take a look at this? Thank you.\n\n", "Use draw manager for clip editor drawing\nCould be stalled to 2.93 as there isn't an real issue here as far as we are aware of. The compositor issues are more tangable.", "Using Ctrl to select bones in weight paint mode with Xray on is broken with left click select\nOperating system: Gentoo Linux\nGraphics card: AMD 5700xt\n\nBroken: 2.90 master, 2020-05-25\n\nWhen using X-ray in weight paint mode, you can no longer select bones with left click select (the right click select keymap works)\n[weightpaint.mp4](weightpaint.mp4)\n[test_gradation_T01_01.blend](test_gradation_T01_01.blend)\n\n1. Open the attached file.\n2. Go to the \"viewport shading\" drop down menu and activate X-ray with something less than 100%\n3. Try to select any bones with ctrl + left mouse\n4. Notice that you can't select any bones with X-ray on.\n\nI noticed that this is caused by a \"Select\" key binding in weight paint mode. This binding only exists in the left click select key map.\nIf I remove this binding, I can select in xray mode again. This doesn't seem to remove any functionality, so I am a bit confused why this binding exists here at all.\n" ]

[ "Traceback error\n{[F8487595](Captufdgre.PNG)}Operating system: windows 10\nGraphics card: radeon rx 580 8gb\n\n\nBroken: (v2.82a)\n\n\nError info is appearing when clicking with left mouse button on view port, can't select anything as the info is appearing. It happened I suppose after pressing left ctrl+z for going back multiple times.\nIt worked on previous version, (2.82b I think, where the mesh transparency button was changed on the up right corner of the view port). \n\nHope this would be helpful \nThank you!" ]

[ "Property Search Improvements\n**Ctrl-Tab Improvement**\nCurrently ctrl-tab doesn't know about which tabs have search results. It should change a little bit:\n* If used while the text field is in focus, keep that focus.\n* Only cycle through tabs with results.\n\n**Fuzzy Search**\n[D9145](D9145) *Needs to be altered to not use per-word comparison, instead compare the entire text block at once.*\n\n**Performance**\nIt's not yet known if search will be a bottleneck for anyone on lower end hardware. At least some efforts should be made to identify any performance issues, and possibly address them. I did some initial profiling. Although I didn't find any major bottleneck, it's possible some things could be looked at.\n\nI tested by maximizing the property editor in a relatively complex file and ctrl-scrolling up and down very quickly, so it should be redrawing as quickly as it can.\n\n\nHere are some interesting items from the \"Bottom up\" results:\n* `__strcmp_avx2`: 5.52%\n** `buttons_context`: 1.15%\n* `UI_panel_begin`: 0.85%\n* `BLI_strcasestr`: 0.617% -- *called from property search only*\n* `panel_add_check`: 0.61%\n* `uiItemFullR`: 0.582%\n\nI think the first thing I would consider is using GHash for `buttons_context.c`, similar to the recent changes in `screen_context`.\n", "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?", "Make All Operators Accessible from Menus\nThis task proposes all operators should be available in menus.\n\nAs of 2.90, the operator search functionality no longer lists all available operators, instead, it expends menus, see #74157 (Use menus for operator search & various improvements).\n\nFrom replies to this task, some users/developers were only accessing operators via search, so scanning menus made some operators un-searchable.\n\nInstead of considering this something to be fixed, this task proposes that operators which users may want to access from search, also be included in menus.\n\n**Notes**\n\n- Popovers could be included in the menu search as well. \n\n-------\n\n**Exceptions**\n\n- Internal operators (operators with `INTERNAL` flag set).\n- User interface operators (re-ordering constraints, modifiers for e.g).\n- Some interactive operators which only make sense to activate interactively (`SCULPT_OT_brush_stroke`).\n- Operators which don't work or don't make sense in the given context (operators from other editors, other modes etc)\n\n------\n\n**Status**\n\nThere is a utility to report operators not yet exposed by menu search.\n\nThis can be generated using: `./source/tools/utils_maintenance/blender_menu_search_coverage.py`\n\nThis paste shows it's output at the time of writing [P1618](P1618.txt)", "VSE UI: Change Path/Files is over exposed \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nChange Path/Files is exposed in four places. \n{[F10401818](image.png),size=full}\nAs this function is only working(afaik) on the active strip(why Files in plural?), it should only be exposed in the strip sidebar. See: #91306 If the function is basically the same as changing the path to the source file then the folder button next to the path should be enough. \nAlso, having it as a secret pop-up menu, shortcut key \"C\", is inconsistent with anything in Blender and this should be removed. \n\n\n", "\"Repeat History\" unavailable after \"Undo\"\nCurrently undo clears the operator history,\nideally this should instead keep these actions in sync with the undo history.\n", "Undo in Armature Edit Mode does not undo Custom Properties\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.5 Beta\n\nUndo in Armature Edit Mode does not undo changes to Armature Custom Properties\n\n- [optionally] In default scene delete all objects\n- Add an \"Armature\" object\n- Go to `Edit Mode`\n- In `Object Data Properties` add a `Custom Property`\n- Change the value of the property (to for example `0.0`) in order to add an Undo step\n- Try undo (`Ctrl+Z`)\n\nThe step is not undone in edit mode.\nInterestingly, changes to the Custom Properties of Bones are correctly undone in Edit mode.\nThis makes it seem that changes to Armature Custom Properties were perhaps missed in the Armature Edit Mode Undo Context.\n\n---\n**Original Report**\n[Video](3RZNWd5tRQI)\nNote when changing the **head size** in the redo panel, you can observe how the number of elements in in the Collection Property `bones_for_delete` grows.\n\n1. Execute the script generate_rig.py from the file, if you do not have automatic script execution enabled\n2. After execution, the Generate Rig panel will appear in the Rig category\n3. Select Empty.021 first, then Armature.001. Switch to armature editing mode, and click Generate Rig on the panel\n4. The bones will appear, and also the text on the panel will notify that there are elements in bones_for_delete. After that, you can scroll the **head size** on the redo panel, or simply undo the operator. the label in the panel will notify you that the number of items will not change\n\n", "Add Asset Browsers to Default Workspaces\nThe Asset Browser should become a crucial editor for many tasks. Therefore it should become part of our default workspaces, wherever reasonable.\n\nIn some workspaces we may run into space issues. In fact the Asset Browser is a good example of why we should have editor tabs, but that is a separate topic and unlikely to be a thing anytime soonish.\n\n### Workspaces to be Updated\n\nThese workspaces should contain the Asset Browser in 3.0:\n* - [ ] ... TBD\n\n", "Junction addon directories have their contents nuked when loadin preferences from previous version\nOperating system: Windows 10 x64\nGraphics card: NVIDIA GTX 1080\n\nBroken: 3.2.1\nWorked: never\n\nWhen an addon is present in form of a junction, Blender will nuke files and folders in the linked directory in certain situations.\nThese instructions are specific to the scenario in which I encountered the problem (Moving to new Blender version when debugging Blender addon using [Blender VsCode extension ](blender_vscode)). There probably exist other constellations which cause similar problems related to junctions.\n\n- Make sure `%APPDATA%\\Blender Foundation\\Blender\\3.0\\config` exists; if necessary, run Blender 3.0.0 once so it is created.\n- Make sure `%APPDATA%\\Blender Foundation\\Blender\\3.2\\config` does not exist\n- Make sure path `%APPDATA%\\Blender Foundation\\Blender\\3.2\\scripts\\addons` exists\n- run command `mklink /J \"%APPDATA%\\Blender Foundation\\Blender\\3.2\\scripts\\addons\\myaddon\" \"path-to-directory-that-will-be-destroyed\"`\n- run command `mklink /J \"%APPDATA%\\Blender Foundation\\Blender\\3.0\\scripts\\addons\\myaddon\" \"path-to-directory-that-will-be-destroyed\"`\n- Launch Blender 3.2.1.\n# In first-time setup splash screen, click \"Load 3.0 Settings\".\n\nAfter this, every file in the folder structure of `path-to-directory-that-will-be-destroyed` will be truncated to 0 bytes in size.\n\nPerhaps it would even be sufficient for the 3.0 `addons` directory to contain a normal directory by the same name as the junction in the 3.2 `addons` directory instead of having to also be a junction itself.\n\nA mitigated variant of this problem is encountered when using the addon \"Remove\" button of an addon in the addon preferences window, where only an OSError is thrown.\n", "Asset Manager “Basics”\nThe description was moved to the #asset_browser project description (click the tag to see it), the Milestone 1 description to #asset_browser_milestone_1.\n\n----\n\n**Milestone ?: Online Repository**\n\nHere we want to be able to append assets from an online repository like the Blender Cloud, BlenderKit and similar.\n\nThere would be a Python API to register custom asset repositories as part of add-ons. The main operations would be to provide a list of assets and metadata, provide .blend with an asset to append/link into the scene, and functions to add/remove/update an asset.\n\n**Milestone ?: Usability**\n\nOnce the asset manager is working for the basics and the UI can do its job, we can start to make things nice. This includes better handling of thumbnails, re-configuring the ID browser to allow for asset browsing, a nice UI widget for managing tags and tag-based filtering.\n\nA key part of making the UX nice, is to make it effortless to drag assets into the scene. When dragging in objects & meshes, they should be able to snap to surfaces. When dragging in materials, the underlying target objects should highlight on rollover. You should be able to add multiple assets at a time. \n\n**Milestone ?: Collection Variations**\n\nNot strictly part of the asset manager since this would be a core feature of Blender also usable without the asset manager. We would like to support variations for all datablock types, but the first step could be collections (it's effectively like automatically toggling visibility on subcollections to show only one). \n\nOnce this is in the place, the asset manager will need to be modified to understand variations.\n\n**Milestone ?: Project Repositories**\n\nUp to this point the asset manager will handle only the use case of appending files from a local or online repository. The next step would be making it works also for projects.\n\n* The root project directory would contain a `.blender_project` file indicating that it is a project (similar to e.g. `.git`)\n* When opening a .blend file within the project folder, Blender will automatically know which project it is part of\n* Folder structure, file names and file saving are left to the user. The asset browser will not add or remove .blend files in the project. That's all done using File > Save and file browsers as usual.\n* The assert browser will have a \"Project\" repository that can be chosen, which will show all assets within the project\n* The user will have to mark relevant datablocks as assets in each .blend file in the project so it shows up in the asset browser.\n* Assets can be linked between files within the same project. This is different from other repositories, where only append is possible. Linking between projects or to other repositories should not be possible, a project must be self-contained and not link to any .blend file outside of it.\n* The project folder would be indexed exactly like other asset folders.\n\nThe idea here is that we don't want to make many assumptions about how users might structure their project. It should be possible to simply add or remove files, reorganize project directories, and the asset browser should keep working. It will merely provide a view on the existing project structure, and functions to create links to other assets in the project. It will not introduce an alternative linking system as an earlier iteration of the asset manager design did.\n\nThis system does not preclude a studio from making an add-on that takes more control over file saving, version control, partial repository checkouts and so on. Such an add-on would likely need to integrate in various places in the Blender user interface, one of which can be the asset browser. For example it might include a custom asset repository to browse assets that are not on the artist's computer, and right before the user links an asset into the scene, download the corresponding .blend file.\n\nBut for most projects that are not e.g. feature films, the built-in project repository and automatic indexing system should already be quite powerful. \n\n---\n\n**Further links**:\n* [Asset Manager]] design blogpost*-- March 2020** [[ https:*code.blender.org/2021/06/asset-browser-project-update/ | Asset Browser Project Update ](https:*code.blender.org/2020/03/asset-manager/) *-- June 2021*\n* [Asset Browser Workshop Outcomes ](https:*code.blender.org/2021/06/asset-browser-workshop-outcomes/)*-- June 2021//\n* #54642 (Asset Project: User Interface)", "GP/Annotation UI: The Annotation options are both exposed as a Tool panel and as a View panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\nAs I was asked to make a new report on these GP UI issues in [D11347](D11347), here they are:\nThe Annotation options are both exposed as a Tool panel and as a View panel(in the VSE). Could the one in the View sidebar be removed?\n{[F10134961](double_exposure.gif),size=full}\n\nIs Onion Skin missing from the tool settings?\n{[F10134979](image.png),size=full}\n\nIf is is, should Onion Skin also be exposed in the Tool header?\n\n", "File Browser and Preference Windows open at unusable position/scale.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.8\n\nOn a multi-monitor set up the File Browser and Preferences windows open up on the \"wrong\" monitor and insanely small. They require being resized *every single time* they are opened - does not remember last position or scaling.\n\nScreenshot of both monitors. The main monitor is a 4k and the secondary, on which I regularly run Blender, is a Cintiq 22HD (1080).\n\n\n\n\n\nOn a multi-monitor display, especially one with a 4k as main, open the File Browser and/or Preferences windows.\n\n", "Collection Assets: To Instance or Not to Instance\nWhen using collections as assets, it needs to be defined when dropping a collection should use instancing and when not. Instancing collections basically means a non-editable version of the collection is added to the scene, with an empty acting as the pivot point. So the collection can be transformed by transforming the empty, but the contents of the collection aren't editable without further steps.\n\ncollection.html\n\n## Proposal: Operator Option\n\nWhile we could just add another option for instancing to the Asset Browser, next to the *Import Type* option, it adds clutter and also requires setting up things before dragging: If you dragged in an asset and used the wrong setting or change your mind afterwards, you'd have to undo and perform the operation again, or manually replace the collection.\nSo it violates the [Operate -> Settings design paradigm ](Paradigms#Operate_-.3E_Settings) of Blender. Instead the proposal is to have this controlled via an operator option, whereby the option will remember what it was set to last. Another setting could still be added, but the operator setting should be useful either way.\n\n***Current File* Asset Library**\n\nIn the *Current File* asset library we often reuse data, but not as often as with the *Append (Reuse Data)* option. E.g. materials are shared, but objects are duplicated including their mesh. [D12879](D12879) tries to make things more unified & explicit, but it's on hold.\n\nNo strong opinion on how this should be handled, I'd say let's avoid confusing users by sharing meshes. So:\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, all objects will be duplicated.\n\n**Other Asset Libraries**\n\n**Link:**\n- Use drop operator option to determine if instancing should be used (*Instance* option)\n\n**Append:**\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, all objects will be duplicated.\n\n**Append (Reuse Data):**\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, a new collection is created but the object's meshes are shared.\n\n**Determining the Drop Location & Rotation**\n\nIdea is to make the drop location and rotation be defined visually. So when dropping a collection, it is transformed to land under the mouse cursor (and later use bounding-box snapping), regardless of where the instance empty is, or regardeless of the collection instance offset. They are reverse applied.\n\nNotes:\n- The drop transform will have to be applied to all added objects, including objects used by the objects inside the collection, which are not in the collection itself. E.g. if an object has a parent or a boolean modifier, the parent or boolean-object is imported along, and the relative transform needs to be preserved. We already do this for dropping object assets, code can be shared.\n- When linking without instancing, the dropped collection will use the drop location of the source file.\n\n**What Should be the Default**\n\nThere seems to be some agreement that in production environments, instancing should be the default. However for beginners (or anybody unfamiliar with collection instancing) this may be a bit confusing. Needs some feedback, for now instancing can be the default behavior.\n\n", "NLA: Moving Strips Auto Changes Between Hold and Hold_Forward\nBug Report #42808 (NLA: Moving one strip resets extrapolation on other strip) #45854 (Hold forward is reseted in NLA)\n\n**Source of Problem**: #42808#843296 \n\n**Solution:** I think the code enforcing this can be removed. I don't think this restriction was ever necessary. When an animator uses a Full Replace Hold strip above other strips, it's expected behavior that it occludes the lower strips. That's what a Full Replace strip is supposed to do. Full means strip influence = 1. For consistency, we'll have to add support when a strip has extrapolation `None` leading to a strip with `Hold`. We'll also have to add support for `Hold_Backwards` extrapolation for completeness. In the case of conflicting adjacent strips (`Hold` into a `Hold`), we let the first strip have priority which leads to the next strip as behaving as `Hold_Forward`.\n\n**Potential Problems with Solution:** \n- When two adjacent strips have `Hold` extrapolation, which should evaluate? It seems natural to let only the preceding strip evaluate.\n- When a strip has `Hold_Forwards` extrapolation and the next has `Hold_Backwards`, which should evaluate? Here, I think we should still let only the preceding strip evaluate, for consistency with the previous point. \n\n____\n\n**Implementation/Patches**\n[D9942: NLA: Remove Hold resetting between Hold_Forward Behavior](D9942) \n[D9943: NLA: Strip Evaluate Held Strips Even When Not First Strip](D9943) (depends on previous patch)\n(todo) Patch3: Add `Hold_Backwards` support. Unsure about whether this is actually useful. Maybe we should wait till there is a concrete use-case for it? \n", "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", "Asset Browser - Append (Reuse Data) without instancing collections doesn't add more objects\nOperating system: Windows 10 Home 64bit (10.0, Build 19044)\nGraphics card: Nvidia RTX 3080\n\n\nBroken: 3.2.0\n\nWhen dragging a collection item from the Asset Browser with \"Append (Reuse Data)\" and \"Instance Off\" it doesn't add the collection again, it moves one object and leaves the rest where they were.\n[Asset Browser Reuse data issue.mp4](Asset_Browser_Reuse_data_issue.mp4)\n\n1. Create a collection asset with at least two items inside\n2. Save that collection to your library (save file inside the correct folder)\n3. Open a new scene\n4. Drag your new collection asset into your scene with Append (Reuse Data) active\n5. In the tool window (not sure about its name) lower left turn off \"Instance\"\n6. Drag out another of the same collection asset\n7. It should now have moved one of the two items" ]

[ "Recurse Into Nested Folders of an Asset Library\nCurrently the Asset Browser lists all assets stored in all .blend files of a single directory, but not the nested directories. This may be useful however since it doesn't limit users that much in how they store their assets.\nMay want to make this optional though." ]

[ "Dead Keys failing (accented letters, double strokes)\nOperating system: Windows 10 X64 Enterprise\nGraphics card: Nvidia RTX 2070 MaxQ\n\nBroken: 2.73, 2.91.0\nWorked: Never\n\nIn a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).\nIf I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?\nActually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.\n\n- In the text editor, press and hold the dead key\n- without releasing the dead key, press the key to be transformed. (this will fail)\n\nIf you release the dead key before pressing the key to be changed, it will work normally.", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "Displacement baking with Cycles\n", "Simplify duplication options in user preferences.\nCurrently we have one duplicate option for each and every object data type (in user preferences, 'Editing' section, 'Duplicate Data' panel).\n\nTopic of this task is whether we should keep things like that, or if we should rather simplify options by defining 'categories' instead.\n\nCategories could be:\n* Geometry *(meshes, curves, surfaces, fonts, mballs, lattices, armatures, gpencil)*\n* Physics *(hair, pointcloud, volume, particles)*\n* Lights *(lamp, lightprobe)*\n* Actions *(actions)*\n* Shading *(materials)*\n* Camera *(cameras)*\n* Speaker *(speakers)*\n\nThis could also include better handling of 'new' things, e.g. duplicating (deep copy) of geometry nodes when 'Geometry' is enabled, duplicating (deep copy) of shading nodes when 'shading' is enabled, and so on.\n\nNOTE: this was triggered by #90638 (Inconsistent object data behavior when link-duplicating collections.) and its fix 65dbeb1d81, which required adding three new options there to fully cover all current object types...", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "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", "Auto-Merging keyframes in the Driver Editor has unappropriate threshold (merges keyframes that shouldnt)\nOperating system: windows 10 & Linux ubuntu\nGraphics card: GTX 1070\n\nBroken: 3.6.2\nWorked: unknown\n\nSee att. blendfile and pictures; moving the base of the armature in the Y direction drives the shapekey of the torus.\nIf you edit a driver keyframe by just slightly moving it to the right, the keyframe next to it is removed\n\nTry editing keyframes in the driver f-curve editor\n\n\n**Note**\nDrivers editor has the driver value as the x-axis (this can be arbitrary low, e.g. in the report, this was the x location [in meters] so handling quite small values where \"keyframes\" where ~0.01 apart\n\n`BKE_fcurve_merge_duplicate_keys` acts with a threshold of `BEZT_BINARYSEARCH_THRESH 0.01f`", "Assert when drawing annotations on surface\n- In the default scene, change to the annotate tool with surface placement.\n- Draw two strokes on the cube.\n- Blender hits the following assert.\n\n```\nBLI_assert failed: source/blender/gpu/intern/gpu_texture.cc:605, GPU_texture_read(), at 'GPU_texture_usage(tex_) & GPU_TEXTURE_USAGE_HOST_READ'\n The host-read usage flag must be specified up-front. Only textures which require data reads should be flagged, allowing the backend to make certain optimiastions.\n```\n\nAdding `GPU_TEXTURE_USAGE_HOST_READ` in `gpu_viewport_textures_create` fixes the issue.\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGABRT\n * frame #0: 0x00007ffff7df564c libc.so.6`___lldb_unnamed_symbol3503 + 268\n frame #1: 0x00007ffff7da5958 libc.so.6`raise + 24\n frame #2: 0x00007ffff7d8f53d libc.so.6`abort + 215\n frame #3: 0x0000000013fa57f9 blender`_BLI_assert_abort at BLI_assert.c:46:3\n frame #4: 0x000000001279abfd blender`::GPU_texture_read(tex_=0x00007fffd2ee4b08, data_format=GPU_DATA_UINT_24_8, miplvl=0) at gpu_texture.cc:602:3\n frame #5: 0x0000000008ca0c96 blender`view3d_depths_create(region=0x00007fffe428b208) at view3d_draw.cc:2278:9\n frame #6: 0x0000000008ca0b7e blender`::ED_view3d_depth_override(depsgraph=0x00007fffd2c19b08, region=0x00007fffe428b208, v3d=0x00007fffe42f8a08, obact=0x0000000000000000, mode=V3D_DEPTH_NO_GPENCIL, r_depths=0x00007fffd2c2c340) at view3d_draw.cc:2382:19\n frame #7: 0x00000000082f5d95 blender`annotation_paint_strokeend(p=0x00007fffd2c2c308) at annotate_paint.c:1667:5\n frame #8: 0x00000000082fa307 blender`annotation_paint_cleanup(p=0x00007fffd2c2c308) at annotate_paint.c:1698:5\n frame #9: 0x00000000082f6771 blender`annotation_draw_exit(C=0x00007fffec9de248, op=0x00007fffc6f5f188) at annotate_paint.c:1868:5\n frame #10: 0x00000000082f5a80 blender`annotation_draw_modal(C=0x00007fffec9de248, op=0x00007fffc6f5f188, event=0x00007fffc6da4758) at annotate_paint.c:2715:7\n frame #11: 0x0000000006e8d888 blender`wm_handler_operator_call(C=0x00007fffec9de248, handlers=0x00007fffe4243020, handler_base=0x00007fffc14d3aa8, event=0x00007fffc6da4758, properties=0x0000000000000000, kmi_idname=0x0000000000000000) at wm_event_system.cc:2406:16\n frame #12: 0x0000000006e8c1a7 blender`wm_handlers_do_intern(C=0x00007fffec9de248, win=0x00007fffe4242f08, event=0x00007fffc6da4758, handlers=0x00007fffe4243020) at wm_event_system.cc:3311:21\n frame #13: 0x0000000006e8a60f blender`wm_handlers_do(C=0x00007fffec9de248, event=0x00007fffc6da4758, handlers=0x00007fffe4243020) at wm_event_system.cc:3361:16\n frame #14: 0x0000000006e897c2 blender`::wm_event_do_handlers(C=0x00007fffec9de248) at wm_event_system.cc:3955:17\n frame #15: 0x0000000006e79d47 blender`WM_main(C=0x00007fffec9de248) at wm.c:640:5\n frame #16: 0x000000000602869d blender`main(argc=1, argv=0x00007fffffffe9d8) at creator.c:585:5\n frame #17: 0x00007ffff7d90290 libc.so.6`___lldb_unnamed_symbol3141 + 128\n frame #18: 0x00007ffff7d9034a libc.so.6`__libc_start_main + 138\n frame #19: 0x00000000060281a5 blender`_start at start.S:115\n```", "Transfer shape key is only working for meshes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: Never\n\nTransfering shape keys is option in panel menu, but it only works for meshes. This is not mentioned in documentation and only evident after running the operator.\n\n\nDuplicate object in provided file and try to transfer shape keys.\n", "Assets: the same catalog UUID appearing in different asset libraries causes failed assertions in the 'All' library\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.182.03\n\nBroken: version: 4.0.0 Alpha, branch: main, commit date: `Mon Jun 5 14:21:39 2023 +0200`, hash: `c18ee2e84dcebaf5831640c987e5fd434219e46c`\nWorked: probably broken since the introduction of the 'All' library\n\nHaving two asset libraries that both have a catalog with the same UUID cause an error:\n\n```\nBLI_assert failed: blender/source/blender/blenlib/BLI_map.hh:1093, add_new__impl(), at '!this->contains_as(key)'\n```\n\n\n- Extract the attached ZIP file. It contains a blend file and two asset libraries.\n- Run Blender in debug mode.\n- Open the blend file.\n- Run the script in the text editor (which adds the two asset libraries to your preferences; don't worry, they won't be saved)\n- Refresh the 'All' asset catalog.\n- See the failed assertion\n\n**Workaround**\n\nApplying this patch will work around this issue:\n\n```diff\ndiff --git a/source/blender/asset_system/intern/asset_catalog.cc b/source/blender/asset_system/intern/asset_catalog.cc\nindex d27763c08d7..8512824b6d4 100644\n--- a/source/blender/asset_system/intern/asset_catalog.cc\n+++ b/source/blender/asset_system/intern/asset_catalog.cc\n@@ -686,7 +686,7 @@ static void copy_catalog_map_into_existing(const OwningAssetCatalogMap &source,\n {\n for (const auto &orig_catalog_uptr : source.values()) {\n auto copy_catalog_uptr = std::make_unique<AssetCatalog>(*orig_catalog_uptr);\n- dest.add_new(copy_catalog_uptr->catalog_id, std::move(copy_catalog_uptr));\n+ dest.add(copy_catalog_uptr->catalog_id, std::move(copy_catalog_uptr));\n }\n }\n \n```\n\nA better solution would be to implement some comparison function like `bool AssetCatalog::is_consistent_with(const AC &other);` that tests both the UUID and the catalog path are identical, and issue a warning if they are not, similar to what `AssetCatalogService::parse_catalog_file()` is doing.\n\n", "Assertion reloading space_headers.blend (UI test file)\nLinux-6.3.3\n\nBroken: `b567b249d40488e5d90235e1a89c98853c5fd099` (4.0 main branch)\nWorked: (needs investigation)\n\n\nLoading `lib/tests/ui_tests/space_headers.blend` twice asserts.\n\n\n1. Run `blender ../lib/tests/ui_tests/space_headers.blend`.\n2. Ctrl-O (and open the file again).\n\nBlender exits with:\n```\nBLI_assert failed: source/blender/editors/space_file/filesel.cc:1094, ED_fileselect_init_layout(), at 'layout->rows != 0'\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", "bpy.ops.object.vertex_weight_copy() fails in multi edit mode\nOperating system: windows 10 amd ryzen 9 5950x 2 x 3090 (not in nvlink)\nGraphics card:\n\nBroken: 3.12\nWorked: don't think it ever has\n\nin multi edit copy vertex to selected fails and does not create new groups or copy the weights, you have to join the mesh first then do copy to selected then separate the mesh again which is problematic in more complex rigging scenarios with shape keys etc. \n\nincluded example blend file with both meshes selected tab into edit mode highlight 1 vertex on the cylinder and then select all the verts on the ico sphere and select copy, the copy fails. If you join the ico sphere to the cylinder mesh and do the same it works as expected.\n\ngoing to write a script as a workaround but I think it's really a bug ? (all be it a small one :-) )\n\n\n[copyfail.blend](copyfail.blend)", "Move To Line Begin and Reset View operators in the console editor conflict when pressing Home key\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\n\nIn the python console editor, both the Move To Line Begin and the Reset View operators have the same shortcut \"Home\", so it is not possible to invoke the Move To Line Begin operator.", "Visual glitches With adaptive domain enabled when object is duplicated or transformed\nOperating system: windows 10\nGraphics card: 3080ti\n\n**Blender Version** 3.3 lts\n\nVisual glitches With adaptive domain enabled when object is duplicated or transformed\n\n- Open default scene\n- Add quick smoke on cube\n- enable `adaptive domain`\n- play animation\n- move domain around or duplicate it (snaps back to original place)\n- play animation again (will move to transformed position)" ]

[ "Assert on dragging keyframes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013\n\nBroken: 81b3933abbbff4844253c04eeaf1ede672dcb566\n\nAssert when I move keyframe(s) back and forth\n\n- Open .blend file\n- select and move that keyframe to-and-fro.\n\nTest File:\n\n[test-anim.blend](test-anim.blend)\n" ]

[ "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Cycles/Compositor: The denoiser returns a black image if not all requirements are fulfilled\nOperating system: Default KVM (Proxmox, Linux)\nGraphics card: None\n\nBroken: Blender 3.0\nWorked: Before Blender 3.0 the frame was just not denoised\n\nIf you enable OIDN/Optix denoising without having the needed CPU flags you will get a black frame back.\nThe desired outcome would be an aborted render with a helpful error.\n\n\n1. Set up a default KVM \n2. Enable denoising \n3. Render over the CLI one Frame\n4. It will be black\n\n**Further information**\nThe config of a default KVM:\n```\nArchitecture: x86_64\nCPU op-mode(s): 32-bit, 64-bit\nByte Order: Little Endian\nAddress sizes: 40 bits physical, 48 bits virtual\nCPU(s): 6\nOn-line CPU(s) list: 0-5\nThread(s) per core: 1\nCore(s) per socket: 6\nSocket(s): 1\nNUMA node(s): 1\nVendor ID: AuthenticAMD\nCPU family: 15\nModel: 6\nModel name: Common KVM processor\nStepping: 1\nCPU MHz: 3399.998\nBogoMIPS: 6799.99\nHypervisor vendor: KVM\nVirtualization type: full\nL1d cache: 384 KiB\nL1i cache: 384 KiB\nL2 cache: 3 MiB\nL3 cache: 16 MiB\nNUMA node0 CPU(s): 0-5\nVulnerability Itlb multihit: Not affected\nVulnerability L1tf: Not affected\nVulnerability Mds: Not affected\nVulnerability Meltdown: Not affected\nVulnerability Spec store bypass: Not affected\nVulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization\nVulnerability Spectre v2: Mitigation; Full AMD retpoline, STIBP disabled, RSB filling\nVulnerability Srbds: Not affected\nVulnerability Tsx async abort: Not affected\nFlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm rep_good nopl cpuid extd_apicid tsc_known_freq pni cx16 x2apic hypervisor cmp_legacy 3dnowprefetch vmmcal\n l\n```\nThe command that I used to render one frame: \n```\n./blender -b --debug --debug-cycles --python-expr 'import _cycles;print(_cycles.with_openimagedenoise);print(_cycles.with_embree);print(_cycles.with_osl)' \"your path to the .blend\" -f 1 \n```\n\n[oidn_disabled.blend](oidn_disabled.blend)\n[oidn_disabled.txt](oidn_disabled.txt)\n\n[oidn_enabled.blend](oidn_enabled.blend)\n[oidn_enabled.txt](oidn_enabled.txt)\n\n[optix_enabled.blend](optix_enabled.blend)\n[optix_enabled.txt](optix_enabled.txt)\n\n\nIf I set up the KVM to use HOST at least OIDN works\nHOST config:\n```\nVirtualization: AMD-V\nHypervisor vendor: KVM\nVirtualization type: full\nL1d cache: 384 KiB\nL1i cache: 384 KiB\nL2 cache: 3 MiB\nL3 cache: 16 MiB\nNUMA node0 CPU(s): 0-5\nVulnerability Itlb multihit: Not affected\nVulnerability L1tf: Not affected\nVulnerability Mds: Not affected\nVulnerability Meltdown: Not affected\nVulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp\nVulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization\nVulnerability Spectre v2: Mitigation; Full AMD retpoline, IBPB conditional, STIBP disabled, RSB filling\nVulnerability Srbds: Not affected\nVulnerability Tsx async abort: Not affected\nFlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx1\n 6 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw perfctr_core ssbd ibpb vmmcall fsgsbase tsc_adjust bm\n i1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr virt_ssbd arat npt nrip_save arch_capabilities\n```\n**Why it would be nice to have the bug fixed:**\nWe have a renderfarm that consist out of random machines and it is always a problem if random frames are black/not denoised/strange colored/broken/out of order. ", "Viewport render gives black background when overlays are turned off.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: \n - 2.92.0 Beta\n - 2.92.0 Beta \nWorked: \n - 2.92.0 Beta\n - 2.91\n\nviewport render gives black background, this happens only when the overlays are turned off.\n\nopen the file, go to view/viewport render image.\n\nthank you\nMax\n\n\n[black_bg.blend](black_bg.blend)\n\n\n", "Crash when playing animation in rendered view (cycles)\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0, 3.5\nWorked: unknown\n\nPlaying animations in cycles rendered view frequently crash blender. With the attached file I consistently get a crash within 1-2 minutes of starting the animation.\n\nThe crashes do not occur when running the intel version through rosetta. They occur much faster/more often when using the CPU than when using the GPU.\n\nOpen attached file\nSwitch to rendered view (Crashes with and without Metal preference)\nPress spacebar to play\n\n[Boat boating.blend](Boat_boating.blend)\n[Animation crash.txt](Animation_crash.txt)\n```\nThread 17 Crashed:\n0 Blender \t 0x10319354c tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 340\n1 Blender \t 0x103193644 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 588\n2 Blender \t 0x103192c60 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 184\n3 Blender \t 0x103183300 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252\n4 Blender \t 0x10318c3b8 tbb::internal::market::process(rml::job&) + 40\n5 Blender \t 0x10318d6b0 tbb::internal::rml::private_worker::run() + 288\n6 Blender \t 0x10318d584 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n7 libsystem_pthread.dylib \t 0x1b39cd4ec _pthread_start + 148\n8 libsystem_pthread.dylib \t 0x1b39c82d0 thread_start + 8```", "Segfault after F12 render with multi-GPU Intel ARC A770 and experimental oneAPI packages on Debian\nOperating system: Linux-6.4.0-1-amd64-x86_64-with-glibc2.37 (Debian sid)\nGraphics card: two identical Intel ARC A770 Limited Edition 16GB\n\nBroken: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-25 19:23, hash: aebc743bf1c7\nWorked: 3.4, 3.4.1, 3.5.1\n\nSegfault when rendering Victor benchmark scene with F12 with second Intel ARC A770. This happens only when the second GPU is chosen as rendering device in Cycles. If both GPUs are selected first one seems to work correctly, but the second one causes a crash/error.\nEmbree on GPU does not seems to matter.\n\nBoth F12 and viewport renders with the second GPU give:\n`oneAPI kernel \"shader_eval_curve_shadow_transparency\" execution error: got runtime exception \"Native API failed. Native API returns: -50 (PI_ERROR_INVALID_ARG_VALUE) -50 (PI_ERROR_INVALID_ARG_VALUE)\"`\n\nRelevant info:\nI'm using following packages from experimental sources (I'm impatient I know :) ), so this crash might be very well caused by their incompatibility with Debian sid:\n`libigc1` - 1.0.13822.1-1\n`libigdfcl1` - 1.0.13822.1-1\n`intel-opencl-icd` - 23.13.26032.7-1\nRest of the packages, including all dependencies are from Debian sid.\n\nFull backtrace:\n\n```\n(gdb) backtrace full\n#0 0x0000000001cfee77 in ?? ()\nNo symbol table info available.\n#1 0x0000000001cffab9 in ?? ()\nNo symbol table info available.\n#2 0x0000000001b0fa9c in ?? ()\nNo symbol table info available.\n#3 0x0000000000f376a3 in ?? ()\nNo symbol table info available.\n#4 0x00007fffebaa63ec in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444\n ret = <optimized out>\n pd = <optimized out>\n out = <optimized out>\n unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737147199792, -8317621660586406251, -286296, 11, 140737488344416, 140734520795136, 8317937541230038677, 8317594907036290709}, mask_was_saved = 0}}, priv = {\n pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}\n not_first_call = <optimized out>\n#5 0x00007fffebb26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\nNo locals.\n(gdb)\n```\n\n1. On Debian sid install experimental packages mentioned above.\n2. Set second ARC GPU as a rendering device in Blender. \n3. Open Victor benchmark scene.\n4. Hit F12 and wait for the crash.", "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", "Blender Instantly Crashes When Rendering Cycles Or Clicking Wrong Setting\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nCPU: 12th Gen Intel(R) Core(TM) i7-12700KF, 3600 Mhz, 12 Core(s), 20 Logical Processor(s)\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.1.230821\n\nBroken: version: 3.6.2\n\nWhenever Blender attempts to render in cycles mode it exits immediately. It doesn't try for a few seconds, there's no loading, just click and instantly the process dies. This happens whether Preferences>System>Cycles Render Devices is set to \"None\", \"HIP\" with my GPU selected, or \"HIP\" with my CPU selected. Regardless of the cycles render device setting when I turn on viewport shading it works as it defaults to Eevee. However, if I try to change it to cycles, the moment I click cycles Blender crashes.\n\nThis same instant crash happens when I try to click OptiX or CUDA in Preferences>System>Cycles Render Devices instead on None or HIP.\n\n\n- Start Blender with a default project\n- Press Z then 8 to go into rendering mode\n- On the sidebar click render properties\n- Click the dropdown to change render engine\n- Click Cycles\n- Should see it crash instantly\n\nTo see the settings crash\n- Start Blender with a default project\n- Navigate to Edit>Preferences>System>Cycles Render Devices\n- Click between None, HIP, and OneAPI without issue\n- Click CUDA or OptiX and see the instant crash\n\n", "Cycles motion blur: The start and end of the motion blur range are not exposed like the rest of the range.\nOperating system: Fedora Linux\nGraphics card: AMD (rendered on AMD CPU)\n\nBroken: 3.5.1\n\nWhen rendering motion blur with Cycles (with the constant shutter curve preset) it seems like the shutter is not fully open at the start and end of the motion blur range.\n\nBased on the attached .blend file (as simple as possible).\n\nRender the first frame with Evee and Cycles and compare the motion blur.\n\n", "Error when denoising (Optix) large image\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090, 3060 Driver 522.30\n\nBroken: version: 3.3.1\nWorked: Never (3.0 failed, 2.90 did not start rendering)\n\nDenoising large image will fail and may result in crash.\n\nShortened log:\n```\nIllegal address in CUDA queue synchronize (film_convert_float3 filter_guiding_preprocess)\nE1122 18:16:01.843204 7088 denoiser_optix.cpp:470] Error converting denoising passes to RGB buffer.\nIllegal address in CUDA queue copy_from_device ()\n```\n\n[#102515.blend](T102515.blend)\n\nOpen file and render image.", "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)", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)", "Image sequence render just stops on Cycles on MacOS Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Ultra 1.2\n\nBroken: version: 3.5.0\nWorked: none, tried 2.93, 3.3\n\nafter about 100 or so frames render just stops, Blender is still responsive, its not frozen or crashed, render bar just sits at %0. I'm doing motion tracking to get some kitbashed 3d elements into the scene. Plays fine in Eevee in the viewport. This is the error I get: CommandBuffer Failed: cycles_metal_shader_eval_displace. Attached ram usage for last 24 hours, I still have plenty of ram!\n\nI've closed the file and retried, several times, never got a render all the way through.\n", "CommandBuffer Failed: cycles metal integrator_ shade_volume --MacOS--\nOperating system: macOS-13.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 4.0.0 Alpha\n\nStarts rendering fine until the error. About 2-3 min. into the render.\n\n\nOpen the ziped blend file with 'Intel MacOS' blender 4.0a and hit render in the compositor!\n\n\nProbably related to: 104744\n\nPS: MacOS blender fails with most Volumes on latest major addons like PureSky, CloudScapes, etc... since blender 3.x .... ! The same applies when creating Volume emtys and volume Modifiers (mesh to volume & volume displace). At some point, blender will quit when clicking on the data tab (cloud icon) for volumes, as reported before.\n\n", "Alpha bug on Principaled BSDF with GPU\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.92\n\nBroken: version: 3.2.1\n\nDecreasing alpha makes material black in the Principaled BSDF shader when using GPU compared to CPU \n\n\n\n - Decrease \"Alpha\" on the Principaled BSDF shader\n - Change to device to either \"GPU Compute\" or \"CPU\" \n - Adjust alpha value to discern difference if not apparent when switching Device property\n\n\n**Notes**\nCPU appears to work correctly with this value, it's only on GPU on my machine that causes alpha to make the material black. Bug appears in rendered images too and not just viewport, and is present in both CUDA and Optix. \n\nMake my alpha 0% if duplicate.\n\n[Blender GPU Alpha Bug.blend](Blender_GPU_Alpha_Bug.blend)", "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" ]

[ "CUDA error: Unknown error in cuCtxSynchronize() : does not recover\n%%%I could reproduce this bug using windows xp 32 bit and linux 64 using a geforce gtx 580 card and there are many reporters of this bug, but noone i found used animations. I decided to open this report, because I came to the opinion that my observations are going deeper than those I found here, so that I cannot really say if they belong together.\n\nthe bug: while rendering an animation with cuda a cuCtxSynchronize-error occurs at some point and the following frames ain't rendered any more. it isn't always the same frame, but seems to be roughly after the same count of frames rendered. additionally i noticed, that glossy surfaces started to glow in purple without additional geometry entering the scene. in the console i found \"CUDA error: Launch failed in cuMemFree(cuda_device_ptr(mem.device_pointer))\" making me think, that there is a memory leak, which influences following frames in the animation. interesting: after canceling the rendering of the animation and redoing it it doesn't work and presents the same message immediately, but using the preview-renderer works fine AND after using it I am even able to continue rendering the animation! it seems to me as if all the code to reinit the cuda-engine is there, but should be executed before rendering any frame.\n\n\n* sadly i was not allowed to redistribute the textures i used\n* but i included the video which came out: i restarted once%%%" ]

[ "Weight paint brush: front faces only not working.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 11)\nAlso 2.82a broken\ndisabling and enabling «Front faces only» do nothing. Brush still paint backfaces.\n\n[2020-04-08_10-48-06.mp4](2020-04-08_10-48-06.mp4)\n\n\n\n", "Hair particle system duplicates objects on some faces and don't fill the rest\nOperating system: Ubuntu 19.04\nGraphics card: AMD Radeon RX580\n\nBroken: (2.81 release compiled from source)\nWorked: (optional)\n\nEven with even distribution enabled, 1 particle per face and a low count of particles to spawn, the particle system put two particles on the same face but with different sizes.\n\n1) Create a cylinder with 32 vertices.\n2) Create a small (scale 0.05) cylinder to use as a reder for particle.\n3) Delete the top and bottom faces of the small cylinder so it becomes like an empty tube.\n4) Enable particle system hair on first cylinder and, choose 30 as number, 1 per face source and disable random order, select as render object the small cylinder, the scale 1.0 and choose to randomize the scale a few (0.5 is ok).\n5) Play with the number of particles and the seed and more than sometimes you will notice two or more small cylinders rendered on the same place overlaping (specially on the top and bottom faces).\n\nWhat I expect:\nIf you count the number of faces of the cylinder (added with default parameters) it will have near 30. If I choose \"even distribution\" of particles and \"1 for each face\" without random, what I expect is that all the faces of the cylinder have at least 1 particle, no more, no less.\nIf there are 30 faces and if I limit the number of particles to exactly 30, there must be exactly one particle for each face.\nWhat happens actualy is that there are 4 particles lying around on the top and bottom faces and I don't know why. And there are no particles on some other faces. And sometimes two spawns on the same place on the bottom or top face of the cylinder.\n\nWith complex meshes it makes a mess, specially if I need to paint the weight to affect density. In that case there are more particles on some places and there are no particles on places with a high value of weight. \n", "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", "Default Particle System colourization in Particle Edit Mode (Hair) doesn't follow theme wire/verts settings\nArch Linux + GTX 780ti\n\n\nAll versions since 2.5alpha. Currently using Blender v2.79 8ef39d5c882\n\n\n * Choose a dark Blender UI theme (Dark 3Dview background)\n * Working in `Particle Edit Mode` with different different particle systems (PS) the currently selected hair PS wire/verts colours are set to *black* instead. This is ok with light `3DView` (opengl) backgrounds. With black or dark themes or blender scenes the user can't see particle paths.\n * Adding more than one PS shows all unselected PS colours just fine using their set material colour. That is not what this bug report is about. Here the focus is on wire/vertices default colourization for the **currently selected** PS.\n * It looks like selecting the first PS uses black as default wire/verts colour. While selecting all other PS they use theme wire colour somehow, but changing `User settings -> Themes -> 3D View -> Wire/Wire Edit` colour has no impact?!\n\n\n**Side effects**\n * Switching `Particles->Render->Emitter` brings viewport PS colourization \"back\" somehow. Broken, but unselected PS are showing their material colour. randomly (?)\n * Working with three hair PS and playing with Emitter influences only some unselected PS (random)?\n\n\n**Current Workaround**\nWhile editing (Particle Edit mode) the current PS just *select all* and then use the brush to edit them. \n\n\n * Use the attacked blend file [PS.blend](PS.blend)\n * and play around while switching between `PS Red/Green` in `Particle Edit Mode` and randomly switch `Emitter` on/off.\n\n\n**Suggested Result**\nThe currently selected hair PS follows theme wire/verts colourization. All unselected PS are using their material diffuse/base colour.\n\n**PS**\nI added a cloned PS, too. Which was cloned from the Red one `ParticleSystem Green (cloned Red)`. Switching its visibility brings all PS material back.\n\n**Possibly Related Sources**\n* Blender Artists: [How Do I Change Hair Colour In Particle Edit Mode?](showthread.php?320868-How-Do-I-Change-Hair-Colour-In-Particle-Edit-Mode)\n", "particle system locations not as expected\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\n\nif i parent an animated cube vertex to a vertex with a particle system and rotate that cube, it works fine. \nIf i copy that vertex with the particle system to another position - the locations get a bit weird.\n\n- tab -> edit mode\n- select vertex\n- Shift-D -> double vertex\n- Mesh -> Separate -> selection\n- rename that to vertex (not important, just for me)\n- add a default particle system to vertex\n- select vertex, ctrl select cube -> edit mode -> ctrl-p\n- select vertex -> origin to geometry -> run\n- works fine\n- select cube, insert keyframe scale/rot/loc\n- go to frame 100\n- location.z: 8 rotation.z: 360*8 -> keyframe both\n- run, works fine, all locations as expected\n\n- select the vertex\n\n- shift-d X -2\n\nrun -> weird location \"disorders\"\n\n\n[particle_bug.blend](particle_bug.blend)\n\n---\nor\n\n- open .blend file\n- select Vertex from outliner\n- {key Shift D} and place the duplicate Vertex anywhere\n- Play animation\n\n[#90494.blend](T90494.blend)\n\n---\nVideo:\n[particle_bug.mov](particle_bug.mov)", "Particles cache ignores animated lifetime\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0\nWorked: not sure if it worked after 2.80, maybe it worked in 2.79, but I'm not sure.\n\nIf you animate the lifetime and bake the particles everything in the same blender session everything works correctly, no matter if you bake them to disk or to memory.\nWhen you save the file, and open the file again the particle cache is broken and it's loading all the animation with the lifetime present in the first frame, no matter if it's a disk cache or a memory cache.\n\n\nBlende file: [test.blend](test.blend)\n\nSteps to reproduce:\n\nYou can watch the video I did or follow this steps:\n\nVideo:[particle_lifetime_an_bug.mp4](particle_lifetime_an_bug.mp4)\n\n1.- Open the attached blend file with Blender 2.90 release\n2.- Clean the cache if there is one, change some parameter like particle count (don't touch particle lifetime, it's animated)\n3.- Bake the animation, and you will see the correct result\n4.- create a new file\n5.- reload our test file\n6.- you will see how the cache is not behaving correctly and it's ignoring the animated lifetime\n\nIt's impossible to trustworthy bake particles without this working, because not even the disk cache is working\n\n\n", "Particle volume distribution calculation is not creating particles inside the volume\nOperating system: Win 10\nGraphics card: Gtx 3090\n\nBroken: 2.91\n\n\nTrying to fit particles inside a simple volume using the grid based particle volume distribution creates mostly misplaced particles.\n\n\nPlease see the attached image and the attached .blend for what is going on and for the settings.\n\n\n\n[vol_28012021_1313_27.blend](vol_28012021_1313_27.blend)\n\n\n\n", "Texture Painting not updating cycles shader in viewport\nOperating system: Linux-5.8.0-44-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa Intel(R) Xe Graphics (TGL GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.92.0\n\n\nLevel 1. When texture painting in the 3D viewport, the image is updated, but the visible shader on the object doesn't update in cycles until switching to viewport shading and back to cycles.\nIt still works when switching to Eevee shading. When reloading the image in the shader image texture node, it updates in cycles, but the problem persists when the image is updated (painted on) again.\n\nLevel 2. The above bug becomes worse as follows:\n\nIn cycles the image stops updating even when switching to viewport shading and back to cycles.\n(A)-When reloading the image in the shader image texture node, it updates in cycles, but any new paint on the texture in the viewport or image editor -> paint mode won't update until step A is repeated. \n\nI do not know exactly what triggers this 2nd level bug, but it doesn't take long to show up. \nI was able to repeat it just by painting and switching between Eevee and cycles using my test .blend file (attached)\n\n\n\n\n1. Assign a material with an image node to an unwrapped object\n2. Switch to viewport texture painting and start painting on the image in cycles shading. \n3. The image updates in viewport shading, but not the visible shader on the object in cycles. \n4. Switch to Eevee shading - now eveything works as expected.\n\n5. I do not know what triggers the level 2 bug.\n\n[Cycles not painting on Cube.blend](Cycles_not_painting_on_Cube.blend)\n\n\n\n\n\n", "GPU Subdivision not optimized in Weight Paint mode\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\nI'm not sure if it's unimplemented/unplanned or just overlooked, so I'm here to report in case.\nWhen you have a mesh using an Armature modifier and Subdivision modifier, the Subdivision will affect performance while posing the armature but enabling GPU Subdivision will noticeably improve performance during posing and animation. \n\nHowever, if you select the armature and the mesh and go into weight paint mode, allowing you to pose the rig, the GPU Subdivision will not boost performance with the Subdivision modifier. Weight Paint Pose is slower regardless as to the Subdivision modifier, just GPU Subdivision seems to be disabled here. \n\n- Open attached .blend file\n- Make sure `GPU Subdivision` is enabled in Preferences\n- in Weight Paint Mode, pose the rig (move any bone)\n- Go to object mode, select the rig and go to Pose mode\n- Compare performance when posing the rig\n\n[#101485.blend](T101485.blend)\n", "Particles: texture density vs density vertex group [very different result]\n\nOperating system: Windows 10 \nGraphics card:2060 Super \n\nBroken: 2.92\nWorked: 2.92\n\nHello developers! I student and texture particle density not working properly. It should work like “vertex group (destiny)”. Sample:\n\n\n[desinty.blend](desinty.blend)\n", "Dynamic paint sub-steps don't work when the brush position is set in geometry nodes\n\nI believe this **may** be the same issue as T40597\n\nIn order to have a brush follow a potentially very large collection of curves in sequence, I'm using geometry nodes to set the position, which avoids the pain of having to join the curve paths or painstakingly tweak the offsets and influence keyframes for each and every one.\n\nThis works, but with sub-steps enabled it seems that the nodes are still only being updated once/frame. Or, if they are being updated, then the `seconds` input from the `Scene Time` node is being derived from the `frames` value which is clamped to an integer.\n\n\n[text_path_test.blend](text_path_test.blend)\n", "Particle Angular velocity doesn't work\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nRotation > Angular velocity section of particle system settings doesn't rotate particles over time.\n\n\n[#81671.blend](T81671.blend)\n* open attached .blend\n* play animation\n", "Crashes when trying to mirror particles\nOperating system: Windows 11\nGraphics card: Nvidia RTX 2060\n\nBroken: 3.6.1\n\nWhen I try to mirror hair particles Blender crashes. I've tried it multiple times and it happens every single time. Ive tried applying the mirror modifier I have on the character but it still crashes.\n\nI have a retopologized character. I make a particle system for eyebrows. I try to mirror the eyebrows by selecting all the particles, going to particles and selecting mirror and blender crashes.\n\n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "Particle system with collision modifier hangs on baking\nOperating system: Linux-5.8.0-55-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: 2.81a\n\n[#88965.blend](T88965.blend)\n\n- Open file\n- Bake particles on LRG_Submarine_Propeller object\n\nIt fails. When you disable collision modifier on LRG_Submarine_Hull object or simplify it considerably, it works." ]

[ "Vertex groups of particles are not dynamically evaluated\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\n\n**Brief description of the error\nWhen dynamically changing vertex groups in particle simulation, the evaluation is static and does not change correctly.\n\n**Exact steps for others to reproduce the error**.\n1. Add particles to any object.\nCreate two vertex groups and paint them with different weights.\n3. Use the weight composite modifier to change the influence by key animation.\n4. Specify the vertex group to be changed to the density of the particle's vertex group, etc.\n5. Playback the particles after baking, but they will not change dynamically in response to changes in Weight.\n\n\n8Im8TwQ72vo\n\nat Blender Artists\n5\n\n", "Dynamic vertex groups (Dynamic Paint, Weight Proximity modifier, Geometry Nodes, ...) do not update density of particles in viewport display\nOperating system: windows 10\nGraphics card: Quadro M620\n\nBroken: 2.90\nWorked: Never\n\nI want to use my dynamic vertex group to generate particles on a plane.\nIt just works when I change parameters during the playback but it's not realtime when I hit play.\n\n- Open attached file\n- Play animation\n- Change any property of the particle during the playback\n[dynamic_paint_test.blend](dynamic_paint_test.blend)", "Particle system do not updates properly in viewport with dynamic painted weight\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Alpha\n\nYou can test with file\n[2021-01-13_14-39-35.mp4](2021-01-13_14-39-35.mp4)\n\nHow it should be (render)\nBaking dynamics do not help at all.\n[0001-0040.mp4](0001-0040.mp4)\n\n[DP hairs update.blend](DP_hairs_update.blend)\n", "Particle system does not deal well with the weights that are generated/updated dynamically.\nOperating system: Windows 10\n\n\nBroken: 2.93.5\nBlender 2.93.5\n```\n build date: 2021-10-06\n build time: 06:44:49\n build commit date: 2021-10-05\n build commit time: 12:04\n build hash: a791bdabd0b2\n build platform: Windows\n```\n\n\n```\n \n```\n\n\n\nThe particle system is not properly utilizing the weights that are generated dynamically via the dynamic paint or weight proximity modifiers. The `regrow` option does not help either.\n\n\nPlease see the video\n\n[sAGumNnPEt.mp4](sAGumNnPEt.mp4)\n\n\n\nLoad the attached .blend file\nPlay the animation\n\n[particle_no_weights.blend](particle_no_weights.blend)" ]

[ "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "crash when x-ray and wireframe are enabled\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.1 Release Candidate\n\nWhen I am working and periodically switch to x-ray and wireframe mode, the program crashes. It just shuts down and that's it. I thought it was related to GPU-subdiv, but today it was not confirmed, I turned off GPU-subdiv and literally after about 20 minutes of work when switching on X-ray and wireframe mode the program crashes. I turn on mode the shift+z hotkeys.\nThis happens randomly!!!\n\n\n\n", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Crash when shading\nModel: HP Probook x360 435 G7 (independently upgraded SSD and RAM)\nOperating system: Windows 11 Pro 22H2 22621.1555\nGraphics card: AMD Radeon Graphics (Built-in graphics of AMD Ryzen 5 4500U with Radeon Graphics)\n\nBroken: 3.5.1 and 3.3.1 were tested, both had this issue.\nWorked: 3.1.2 – At the time of issue creation, there are no newer versions that have worked, including the latest build of 3.6.0 Alpha.\n\nBlender freezes for a second or so, and then crashes.\n\nI don't know if it *is* reproducable, but I have tested multiple conditions under which it crashes. These conditions are accompanied with the crash logs of that test. The problem does not seem to be (V)RAM usage, as the usage remains constant from before Blender is opened to long after.\n- Press F12 to Render Image: Crash [Log](itihmb)\n- Select Default Cube, Click on Shading workspace: Crash [Log](nxyeck)\n- Select Default Cube, Go to Materials tab: Crash [Log](ixgrhp)\n- Change Viewport Shading mode to Material Preview: Crash [Log](diwmma)\n- Change Viewport Shading mode to Render Preview: Crash [Log](ztajes)\n- DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: Crash [Log](gcaded)\n- Change Render Engine to Cycles, Press F12 to Render Image: **No** crash\n- Change Render Engine to Cycles, Click on Shading workspace: Crash [Log](chmkgj)\n- Change Render Engine to Cycles, Go to Materials tab: **No** crash\n- Change Render Engine to Cycles, Change Viewport Shading mode to Material Preview: Crash [Log](fhfyfo)\n- Change Render Engine to Cycles, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Cycles, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\n- Change Render Engine to Workbench, Press F12 to Render Image: **No** crash\n- Change Render Engine to Workbench, Click on Shading workspace: **No** crash\n- Change Render Engine to Workbench, Go to Materials tab: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Material Preview: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Workbench, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\nThank you for your help.\n\n", "Eevee Light Limitation testcase T91611 crashes on Win11 Intel Arc GPU \nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) Arc(TM) A770 Graphics Intel 4.5.0 - Build 31.0.101.4090\n(note: also tested on driver .4032 latest stable, which also crashes)\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 3.3.2, 3.4.1\n\n \n\nWhile tracking down another bug (direct lights not appearing in Eevee), I found that the test case for #91611 hard crashes blender.\n\nAnalyzing the code, the crash happens because the GPU module cannot create a 3D texture with dimensions `4096x4096x576`. The result is `nulltptr`\n```\nif (!success) {\n delete tex;\n return nullptr;\n}\n```\n\nbacktrace:\n\n```\n>\tblender.exe!blender::gpu::Texture::attachment_type(int slot) Line 257\tC++\n\n \tblender.exe!GPU_framebuffer_texture_attach_ex(GPUFrameBuffer * gpu_fb, GPUAttachment attachment, int slot) Line 316\tC++\n \tblender.exe!GPU_framebuffer_texture_layer_attach(GPUFrameBuffer * fb, GPUTexture * tex, int slot, int layer, int mip) Line 331\tC++\n \tblender.exe!EEVEE_shadows_draw_cubemap(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata, int cube_index) Line 203\tC\n \tblender.exe!EEVEE_shadows_draw(EEVEE_ViewLayerData * sldata, EEVEE_Data * vedata, DRWView * view) Line 316\tC\n \tblender.exe!eevee_draw_scene(void * vedata) Line 247\tC\n \tblender.exe!drw_engines_draw_scene() Line 1111\tC\n \tblender.exe!DRW_draw_render_loop_ex(Depsgraph * depsgraph, RenderEngineType * engine_type, ARegion * region, View3D * v3d, GPUViewport * viewport, const bContext * evil_C) Line 1767\tC\n \tblender.exe!DRW_draw_view(const bContext * C) Line 1637\tC\n \tblender.exe!view3d_draw_view(const bContext * C, ARegion * region) Line 1552\tC++\n \tblender.exe!view3d_main_region_draw(const bContext * C, ARegion * region) Line 1587\tC++\n \tblender.exe!ED_region_do_draw(bContext * C, ARegion * region) Line 551\tC\n \tblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 960\tC\n \tblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 1127\tC\n \tblender.exe!wm_draw_update(bContext * C) Line 1385\tC\n \tblender.exe!WM_main(bContext * C) Line 648\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 589\tC\n \t[External Code]\t\n\n```\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n- Download and open any of the test cases bellow\n- Click Render Preview in viewport\n\n[Light ViewportRender ERror.blend](Light_ViewportRender_ERror.blend)\n[lighttest2.blend](lighttest2.blend)", "Adding Clearcoat freezes Blender with error \"Execution of the command buffer was aborted due to an error during execution\"\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 5700 XT 1.2\n\nBroken: version: 3.5.0\nWorked: Unknown\n\nAdding Clearcoat to a Surface freezes Blender, with Console logs showing only an \"Execution of the command buffer was aborted due to an error during execution. <private>\" error.\n\nOnly appears to happen when using Metal, using Blender in OpenGL mode doesn't have this issue. The issue is also present on brand-new projects with just the default cube.\n\n1. Create new file (Eevee renderer)\n2. Change the Clearcoat amount of the default cube from the Materials tab.\n3. Blender crashes usually within seconds, with the default cube I've found it freezes more easily if you use the sliding mechanism to change the Clearcoatness.\n\n", "Pack UV's crashes blender\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\n\n", "MultiRes+Solidify while trying to use Sculpt Mode cause Blender to crash\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nI tried deactivating one modifier while keeping the other one active to see if Blender would crash, but this was not the case. Only when I used both simultaneously did the program reliably crash every time, regardless of brush.\n\nAdd the modifiers that are active in the video and follow along. \n[Desktop 2019.09.23 - 00.49.39.02.mp4](Desktop_2019.09.23_-_00.49.39.02.mp4)\n", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "Blender crashes instantly when trying to render with Cycles (HIP)\nOperating system: Windows 11\nGraphics card: AMD RX 6600 / Adrenalin 23.9.1\n\nBroken: Blender 3.4.x / 3.5.X / 3.6.2 / 4.0 Alpha\nWorked: 3.3.X\n\nBlender instantly crashes when trying to render with Cycles using HIP. Apparently only happens with files that have high number of polygons. New Project with cube doesn't crash. Using CPU doesn't crash.\nAlso, System preferences shows that I have 2 GPU units, but I have only one. It disables both when trying to disable a single one (idk if this is normal)\n\n", "Regression: Crashes when uses preview or final render modes\nOperating system: Mac Os Monterey 12.6.1\nGraphics card: AMD Radeon R9 M380 2 GB\n\nBroken: blender 3.6.2\nWorked: Blender 3.4.1\n\nBlender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements.\n\nSimply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.\n\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Blender crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n" ]

[ "Video Editor Crash\nOperating system:windows 10 home\nGraphics card: intel(R) hd graphics 530\n\nBroken: 2.91\nWorked: none\nBlender closes when video editor tab opens\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nPlus tab + (Video editor tab) CRASH\n\n\n```lines\nStack trace:\nblender.exe :0x00007FF71251DC90 imb_bmp_decode\nblender.exe :0x00007FF7124F7B30 IMB_loadifffile\nblender.exe :0x00007FF7124F7D70 IMB_loadiffname\nblender.exe :0x00007FF712510E20 thumb_create_ex\nblender.exe :0x00007FF7125107E0 IMB_thumb_manage\nblender.exe :0x00007FF71582BB80 filelist_cache_preview_runf\ntbb.dll :0x00007FFE27F251D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF715FBCA20 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFE27F337A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFE27F337A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFE27F251D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFE27F2A490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFE27F319C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE27F319C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFE3CF31430 configthreadlocale\nKERNEL32.DLL :0x00007FFE3EC57020 BaseThreadInitThunk\nntdll.dll :0x00007FFE3F43CEA0 RtlUserThreadStart\n```\n\n{F9425343}\n", "Crash : Malformed .bmp files lead to crash.\nThere is no bounds checking in `source\\blender\\imbuf\\intern\\bmp.c` leading to out of bound access if the bmp file is malformed. \n\nrepro:\n\n1) Copy the attached bmp files to the default folder (on windows `c:\\Users\\[username]\\Documents\\` \n2) Click the Shader tab\n3) The file dialog in the upper left will try to make thumbnails, and crash while doing it. \n\nNote: The problem exists in the 16bpp (rgb565) codepath as well but i had nothing that could write that format.\n\nNote2: The header checks also do not respect the buffer bounds, i didn't have time to make to make a crashing bmp, but whoever will work on this will have to fix that as well. \n\nnote3: the crashy bmp files are created by taking a regular bmp file and truncating it to about half their size, leading to a correct header, but not enough image data in the file. \n\n\n\n\n\n\n\n\n[Original report]\n\nOperating system: Windows 10 Pro, Version 1903, Build: 18362.476\nGraphics card: Nvidia GTX 980 TI Driver 441.20\n\nBroken: 2.181 release\nWorked: (optional)\n\nOn fresh install of 2.81, startup with default project. \nSelect the Shader tab and Blender crashes with: \n\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF63621A4B0\nModule : C:\\Program Files\\Blender Foundation\\Blender 2.81\\blender.exe\n" ]

[ "Box with beveled vert will damage, if use multires modifier in simple mode.\nOperating system: Fedora 32, 64bit\nGraphics card: GTX 650Ti\n\nBroken: version: 2.91.0 Alpha\nWorked: blender-2.82a-windows64\n\nAdd cube, bevel one vert (1 segments) add multires modifier, select simple mode, and subdivide 2 or 3 times. Mesh will damaged.\nIf beleled 2 or more verts subdivision works stability, but not always. Sometimes it will damaged, sometimes properly.", "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)", "Png artefact\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.1\n\nThere is an issue with displaying a vector map in PNG 16-bit format. For comparison, I saved the vector map in EXR 16-bit format with compression, but no artifacts were observed.\n\n", "Poor stroke quality when a model is far from the world origin\nOperating system: Win 10\nGraphics card: Nvidia Rtx 2070\n\nBroken: 2.83, master\nWorked: perhaps never?\n\njittery strokes when mesh is far from the world origin in perspective mode\n\nHow to reproduce this bug : \n- Create a grid (set the location to x : 2000 m and y : 1000 m)\n- Create a multires modifier, with 5 subdiv.\n- Sculpt with the clay brush\n- In Perspective mode (left stroke) the stroke is ugly\n- In ortho mode (right stroke) the stroke is clean\nTo fix the stroke poor quality, i had to fine tune the Clip start and the clip end values of the 3d view. \n[#102747.blend](T102747.blend)\n", "Sculpted models in Solid or Wireframe viewports do not update in other Material or Rendered viewports when changes are undone (Undo). This can cause a desync that the artist may not notice until it's too late.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90.0\n\nSuppose there are two viewports, one in Material Preview or Rendered shading mode and the second viewport in Solid or Wireframe shading. I sculpt the mesh in the Solid or Wireframe (I don't sculpt in Wireframe at all, but this problem occurs in that mode as well) viewport and then undo the changes, but the undo does not update the model in the Material Preview or Rendered viewports.\n\nWhy I sculpt this way and why this error (or by design) is problematic and annoying:\n- I can see the topology much better in Solid shading with matcaps. However, I also want to be able to see how the sculpt looks under more finalized lighting settings in real-time while I edit and experiment with different sculpting or placement of facial features, for example.\n- I am constantly undoing brush strokes in a sort of error-correction method of sculpting. Naturally, reducing undoing strokes would be more efficient overall, but not being able to see the reverted mesh from undoing strokes absolutely debillitates confidence of an artist when they're suddenly not working on the most updated model.\n- This can cause bad sculpting errors as one looks from one viewport to the other to \"sanity check\" or simply check progress and be fooled into thinking that the models are synced, when they're actually desynced. The artist might not notice this and continue sculpting, which will update both views again, but it can cause unintentional sculpting errors.\n\nI'm not sure if this was a conscious design choice (2.82 also has this problem. I did not test pre-2.79 versions), but if it was, it makes absolutely no sense why there is even the possibility of anything desyncing between viewports, no matter how the artist works. It just makes me question all the time whether or not me activating Undo actually did anything at all, which causes even more frustration.\n\n1) Create a sphere.\n2) Split window into two viewports.\n3) Change shading mode of one viewport to either Material Preview or Rendered and the other viewport to Solid or Wireframe.\n4) Sculpt sphere in solid mode.\n5) Ctrl+Z to Undo.\n6) Undo is not updated in Material Preview or Rendered viewports.\n\n\n", "Artefacts when enabling shadows in solid shading viewport mode\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: unknown\n\nEnabling shadows in solid shading mode results in flickering blocky artefacts\n\nDefaults scene, delete everything\nAdd a plane, scale up 20 times\nSwitch to solid shading and enable shadows\nMove around the viewport\n\n\n\n[Schermopname 2021-12-06 om 12.24.41.mov](Schermopname_2021-12-06_om_12.24.41.mov)", "Transform Tools influence on Hidden Face Sets with Multires Modifier\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\n\nThere seem to be multiple strange effects that the Transfrom Tools (Move, Rotate, Scale, Transform) have on an object with Multires in Sculpt Mode.\nWhen hiding face sets the boundaries are still being effected but are lagging behind.\nIf the operation is cancelled (Esc) the boundary edges will move half of the way anyway.\nIf the operation is accepted it will unhide all face sets.\n\n[2020-07-27 14-06-58.mp4](2020-07-27_14-06-58.mp4)\n\n- In the default cube, add the Multires modifier\n- Subdivided the mesh a few times.\n- In sculpt mode, draw a Face Set for one of the faces.\n- Hide the rest\n- Enable the Transform tool and move the object.\n", "2.91 - Undo in Sculpt Mode switches tool to inflate brush (specific to attached file)\nOperating system: Win 10 64-bit\nGraphics card: Nvidia GFX 1060 6GB\n\nBroken: \n - 2.90.1\n - 2.91.0, from steam, seems *file specific*\n - 2.92.0\nWorked: 2.91.0, same version, fresh file\n\nWith attached file: In sculpt mode calling undo changes the tool to \"Inflate\" besides undoing.\n\nAdditionally, when undo is called via menu, the undo operation happens only when undoing so far back sculpt mode was entered. On reentering Sculpt Mode, tool is set to \"Inflate\". \n\nThis issues seems to be tied to this specific file, as it's not reproducible in a fresh file. The file was created with blender 2.91.0. I sculpted multiple objects using both Dynamesh and Remesh in Sculpt Mode. I deleted the sculpts to keep the file size small and since the same behavior persisted with newly created geometry (in this case a cube). I don't know how to debug this any further, any hints appreciated. As a workaround I will try to reimport the geometry into a new file.\n\nBased on the attached .blend file [SculptModeBug.blend](SculptModeBug.blend)\n\nUndoing with shortcut:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - hit ctrl + z\n - tool switched to \"Inflate\"\n\nUndoing via menu:\n - Select object \n - enter sculpt mode\n - select any other tool than \"Inflate\"\n - modify mesh with tool\n - modify mesh with tool\n - call \"undo\" from menu \"edit/undo\" - this has no effect\n - call \"undo\" from menu \"edit/undo\" until the point object goes back to Object Mode - changes get undone\n - On entering Sculpt Mode again, the active tool has switched to \"Inflate\"\n", "Multires disp bake doesn't smooth UV\nOperating system: Windows 10\nGraphics card: RTX 3060ti\n\nBroken: 2.92, 02948a2cab44\nWorked: Don't know\n\nWhen baking a multires sculpt it will bake the disp towards a subdivided mesh but not a smoothed UV.\n\nGuess the best way is just to download my attached .blend, make sure the image texture is selected, that the Level Viewport on the multires modifier is at 0 and use the bake under Render properties. The resulting texture should not have this clear square in the middle as in my example picture below, but it do because the UV ain't getting smoothed. I did make sure that I had UV smooth enabled when I first subdivided the mesh.\nAlso added an example from what happens when I do this on a real project. This is baked and then applied to a subdivded mesh, look at the wrinkles below the eye.\n[multires_bug.blend](multires_bug.blend)\n\n", "Changing Resolution Preset doesn't allow to Undo\nBroken: 3.6.0\n\nChanging Resolution Preset and then trying to undo doesn't work, like if the action is not registered.\n\n\n- Open Blender\n- Click on the Format panel on the right icon to change preset\n- Select a preset\n- Undo\n\n", "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", "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)", "Sculpting: Vector Displacement option not enabled on appended brushes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.0\n\n\nWhen sculpting with imported brushes in 3.5 when applying an anchored brush (settings the same as in 3.3.5 LTS), the result looks lifted up from the surface.\n\n**Caused by** disabled \"Vector Displacement\" option when brushes from 3.3 were appended into 3.5, likely a versioning issue.\n\nThe option is added with #104481.\n\n\n\n\nSteps used in both releases:\n- Add Cube\n- Add Multisres modifier\n- Subdivide times 6\n- Apply modifier\n- Ctrl-A, origing to Geometry\n- Append brushes\n- Go to sculptmode\n- Choose a brush\n- Apply brush on object\n\nUsing 3.3.5 The brush is nicely put on the object, in 3.5 (with the same settings) you get a pimple. Lowering strength doesn't do the trick in 3.5.\n\n", "Cycles does not render geo with Multires modifier while in Sculpt mode\nOperating system: Windows 10, Linux\nGraphics card: Nvidia GTX 960\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nAdding a Multires modifier with the Sculpt parameter > 0 (to further develop the model I'm working on) makes the geo disappear when using Cycles in the viewport, while in Sculpt Mode. As a first time Blender user, I'm not sure if this is the expected behaviour for this. I have checked with other users and they can reproduce the error. \n\nIt would be useful to render in viewport without leaving Sculpt Mode.\n\nCreate a geometry. Add a Multires modifier. Set Sculpt to a value greater than 0. Enter Sculpt Mode. Change the viewport render from Eevee to Cycles. The geometry disappears on rendering. I have a sample of the problem in this tweet I published several hours ago: 1150657198374080512\n\nThanks!", "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" ]

[ "Multires Level switching undo bug\nOperating system: Linux-5.4.0-42-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.90.0 Beta\n\nWhen sculpting in multires, the switching between different levels of subdivision is not included in the undo stack.\nBecause of this, when sculpting changes in the model, then switching between levels and sculpting more and afterwards using undo, it will not reliably undo the strokes.\nIn some cases it won't undo at all unless it exits sculpt mode or reaches some point in the undo stack where the level gets changes another time.\n\n\n[2020-08-03 15-38-50.mp4](2020-08-03_15-38-50.mp4)\n\n- Add an object with a multiresolution modifier and subdivide it a few times\n- Sculpt changes on the highest level, then on a lower level and then again on a higher level\n- Undo all those strokes until the mesh breaks or you exit sculpt mode and all is reverted at the same time" ]

[ "Snap cursor gets too small sometimes\nBroken: version: 2.93.6 Release Candidate\nWorked: Never\n\nWhen the snap cursor doesn't snap anything (or is snapped to grid) and you zoom in on the scene, it gets too small.\n|||\n| -- | -- | -- |\n\nNOTE: the cursor displays increments that are not actually used for snapping. This can be confusing when trying to increment over small distances.\n\n- Enable the `Add Cube` tool (to display the cursor)\n- Point to a region of the Grid further in the background.\n- Zoom In\n\n", "3D Connexion Space Mouse Pro - Blender 2.82a on macOS\nmacOS Catalina 10.15.4 (19E287)\n3D Connexion 3dWare10 10.6.5\n\nBlender 2.82a\n\n\nThe mouse appears to almost match the 3D Connexion training app in terms of movement when in object/edit mode but it would appear that none of the buttons & especially the MENU do not work. \n\nI have installed the 3D Connexion drivers a second and third time with firewall and anti-virus off and the problem with these mice seem to persist. \n\n>> This has been edited by another but im wondering if there is some resource file missing where keys are mapped, either this is a 3D Connexion plug in or something to do with Blender?\n\n\nI've seen these tasks; It's still a problem for me. \n#67686 (NDOF mouse not working in code signed macOS builds)\n#67971 (3D Connexion Space Mouse Enterprise Custom Buttons 1-10 Not working in Blender 2.8 (macOS))", "Multi-touch gesture: Zooming is reverse in shader editor comparing to viewport\nOperating system: macOS-11.4-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.6.4\n\nBroken: version: 2.93.1\n\nZooming is reverse in shader editor (other 2d editors are fine)\n\n- Hold ctrl and drag downwards\n- This will zoon in the viewport but zoom out in shader editor\n\n- - -\nsteps from original report:\nOn MacOS, by holding CMD and scrolling on the magic mouse you can zoom on the object. the correct behavior is that dragging down should zoom-in. but it's reverse in the shader editor.\nand if I set the \"Invert zoom direction\" in the settings, it will do both of those oppositly\n\n", "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).", "Camera to View and zoom do not work with orthographic cameras\nIf you switch to ortographic camera (point 1), and try to zoom in with the camera viewport active, the camera behaves as \"view lock>camera to view\" unchecked.\nThe correct behavior is that you can get near the object without changing the camera \"unlock view > camera view\" (point 3). Even though it's checked, it's not working as intended (check point 2 in the picture)\n\n\n- Open attached .blend file\n- Try zoom in, dolly in...\n[ortho_bug.blend](ortho_bug.blend)\n\n", "Lag Adjusting Value Sliders & Navigating Nested Menus with a Wacom Tablet\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93.2\n\nTrying to change the value of shapekeys or shader sliders with my stylus doesn't get detected the first few seconds, then picks up, but in a non responsive way. Also while using my stylus, if I navigate to a nested menu like say \"Object > Transform\" There's a Lag when moving to another option in the \"Object\" Menu.\n\nThe steps above should apply. I did notice though, that if I change my Tablet API from 'Automatic' to 'wintab' in the the input preferences, it helps, but its still not as responsive as it is in 2.93\n\nAll these issues though, were non existent, if I tried using my laptop's trackpad. Also, my tablet is a Wacom Intuous Touch 5 with a stylus that supports up to 2048 levels if pressure sensitivity and has tilt support, just incase it could be any of these causing the issue. \n\nThanks.\n\n", "object monitor and menu bar flickers when i move move my cursor\nOperating system: Windows-11-22H2\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.92\n\nBroken: version: 3.6.2\n\n\n\n", "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", "Intermittent: Shift + MMB unresponsive or very sluggish\nOperating system: MacOS Ventura 13.4.1\nGraphics card: M1\n\nBroken: 3.5.1, Hash: e1ccd9d4a1d3, Branch: blender-v3.5-release\n\nShift+MMB to pan view in perspective mode becomes either completely unresponsive to keyboard input or extremely sluggish compared to the mouse pointer speed for the rest of the application. Agnostic to mouse pointer speed setting for the OS. \n\nAny model in perspective view. Attempt to pan view via SHIFT+MMB.\n\n", "Broken/weird Continuous Grab behaviour\nOperating system: Linux-5.8.0-43-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: SVGA3D; build: RELEASE; LLVM; VMware, Inc. 3.3 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0 Alpha\n\nbroken/weird behaviour under VMWare Player/Workstation 14.1.2+, Ubuntu 20.04.2 LTS\nEdit -> Preferences -> Input -> Continuous Grab\n|[2021-02-27 03-11-16.mp4](2021-02-27_03-11-16.mp4)|[cursorbug.mp4](https://archive.blender.org/developer/F13560997/cursorbug.mp4)\n| -- | -- |\n\n- activate grab mode (G-key) in the viewport or in any blender's area which support 'Continuous Grab'\n- drag mouse toward area top or bottom edge\n\nAlternatively:\n- Active walk navigation and quickly move the mouse outside of the Blender window. \n", "Compiling shaders for Eevee locks up the viewport until the process is complete (MacOS)\nOperating system: macOS-11.2.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.0.7\n\nBroken: version: 2.93.0 Beta\nWorked: I don't believe this has ever been good on the Mac platform\n\nWhen working in a heavy scene (the spring or barbershop demo, for example), the UI will \"beach ball\" or lock up while blender calculates Eevee shaders. On a pc, these calculations don't appear to lock up the interface the way it does on Mac. The expected behavior would be that the UI remains responsive at all times.\n\nOpen the Spring or Barbershop demos. Switch the viewport to full Eevee interactive rendering. The UI will lock up while Blender calculates the shaders. Once this process is complete, the viewport will return to normal behavior.\n\n", "Grease Pencil phasing through objects even when 3d location is selected \nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2060 SUPER\n\n3.1.2\n\nGrease Pencil strokes that should be under the floor/behind objects are phasing through with a weird grainy texture. Looks perfectly fine in viewport rendering but when I render an image/animation it looks weird. Not sure what im missing or if its a bug?\n\n**Blender project**\n[clothtest.blend](clothtest.blend)\n\n", "Draw Face Set brush bug\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\nDraw Face Set brush doesn't work properly and select faces randomly\n[DjHiCdF9fE.mp4](DjHiCdF9fE.mp4)", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "GP Fill Tool not working on Mac with Metal GPU Backend\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.12.7\n\nBroken: version: 3.5.1\n\nWhen my GPU Backend is set to Metal, the Fill Tool in Grease Pencil is not working. It either doesn't fill, or fills randomly (and yes, my shapes are closed). If I switch my GPU Backend to OpenGL, the Fill Tool works as expected (although I have to click twice)\n\n<video src=\"attachment\" title=\"IMG_8032.MOV\" controls height=\"360\"></video>\n\nWith the Metal Backend turned on in Preferences...\n1. I open a new 2D Animation file.\n2. I select Ink Pen as my brush type.\n3. I draw some simple shapes.\n4. I switch to the Fills layer.\n5. I switch to the Fill Tool.\n6. I switch to a fill material.\n7. I click inside the drawn shapes.\n8. Some shapes fill and some shapes don't.\n\nIn this file there is a case where the Fill tool works with OpenGL but not with Metal: [fill_metal_bug.blend](attachment)" ]

[ "Zoom to Mouse Position is broken in Node Editor (with Trackpad, macOS)\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.90.0 Alpha\nBroken: 2.79b, 2.8x\n\n\n- if the \"Zoom to Mouse Position\" preference is enabled\n- in the Node Editor\n- zooming with `Cmd + Trackpad Pan` or `Trackpad Zoom`\n- always zooms to the center of the *canvas*, it is almost impossible to zoom\n\n[trackpad-zoom-node-editor.mov](trackpad-zoom-node-editor.mov)" ]

[ "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", "Keyed Particles don't render as expected\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n[KeyedParticlesJL.blend](KeyedParticlesJL.blend)\n\n- Open file\n- Go to frame 105\n- Render\n- Compare render to viewport\n\nRender is different to viewport\n\nThat's what I expected:\n[ViewportRender.mp4](ViewportRender.mp4)\n\nThat's what I get when rendering with Eevee:\n[EeveeRender.mp4](EeveeRender.mp4)\n\nThat's what I get when renderng with Cycles:\n[CyclesRender.mp4](CyclesRender.mp4)\n", "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", "Viewport material is darker than the rendered version\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 10.18.14.5067\n\nBroken: version: 2.82 (sub 3)\nConfirmed in 2.81 release\n\n\nThe material consists \na transparent shade mixed with a translucent shade, mixed with an emission shade with\nfrenel node multiplied with a noise texture as the factor\n\nThe sample sizes are the same\n\nJust render\n\n\n[necro_core_reduced.blend](necro_core_reduced.blend)", "Viewport switches needlessly to perspective mode, when changing from camera-view to local-view // Auto perspective is turned OFF.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0\n\nWhen in camera-view and hitting Numpad Dash to get into local view of selected object, the 3D-Viewport ALWAYS goes into perspective mode needlessly. **Auto-perspective is turned off.**\n\n\n- Open attached .blend file.\n- Cube is already selected.\n- Camera-view **(Numpad 0**) is also already set\n- Hit **Numpad Dash** to go to local view of selected Cube. (**3D-Viewport is now in perspective mode.**)\n[Perspective.blend](Perspective.blend).\n\n\n\n**To further add to the unnecessary switch of view-mode:**\nWhile in perspective local view of the cube as described above, hit **Numpad 5** to switch to orthographic view.\nNow tab**Numpad 0** to go back to camera-view.\nHit **Numpad Dash** again to go to local-view of the cube again.\nOnce again, you are needlessly in perspective mode.\n\nThanks for any fix on this issue.", "Eevee Incorrect rendering of the volume\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\n\n\n[bug_volume_eevee.blend](bug_volume_eevee.blend)\n", "Eevee motion blur causes ghosting on image sequences when steps are greater than one\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nAlso tested on Windows-10-10.0.19041\nGraphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\n\nThe next frame of an image sequence/video texture is added onto the current one when the step count in Eevee's motion blur is any value greater than one.\n\n\n\nDemo file: [blur.blend](blur.blend)\nVideo used: [demo.mov.zip](demo.mov.zip)\n\n1. Create a material that references a video or image sequence in any form\n2. Turn on motion blur and set step count to any value greater than one\n3. Render", "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\n\n", "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", "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", "Eevee alpha blend mode bug\nOperating system: Linux-5.4.0-74-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\n\nThis bug happened since blender 2.90\n\nIn the scene the two objects with alpha blend mode, flip the transparency depending on the point of view.\n\n[0000-0050.mp4](0000-0050.mp4)\n\nTest file:\n[Ui1.blend](Ui1.blend)\n", "Eevee in VSE as Scene strips - erratic behaviour\nOperating system: Win 10\nGraphics card: Radeon RX580\n\nBroken: 2.80 version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-16 23:08, hash: 12da679fa094, type: Release\nbuild date: 16/06/2019, 17:07\n\nWhen using Eevee Scene Strips in VSE , the VSE viewport shows the wrong items on screen in OpenGL preview, and then the Render also does not show correct layering or camera moves\n\nOpen Blend file\nSee 3 scenes. \n- 2x animated (linked) scenes that render several layers in Eevee properly, then composite as expected\n- 1x Edit scene that has those linked scenes as Scene Strips in the VSE.\n\na) Observe in VSe that the viewport doesn't not reflect each Eevee scene in preview.\nb) Press render in VSE scene, and observe the render layers are broken and don't match the orig scene.\n\n[20190626.blend](20190626.blend)", "The Viewport Display setting of Particles affect the Render result with Eevee \nOperating system: Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe Viewport Display setting of Particles affect the Render result with Eevee \n\nWith Particles selected Change \"Display as\" to \"Path\" in Viewport Display setting and Render with Eevee . error : Pathes will be dislpayed in render result \n[partical_render.blend](partical_render.blend) press render\n\nFrom other reports what is also affected:\n- `Viewport Display` > `Strand Steps`\n- `Viewport Display` > `Amount`", "Lineart in viewport inconsistent with bound cameras\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.4.1\n\nWhen I'm using lineart with bound cameras on the timeline and View Lock, Camera to view is True, sometimes the lineart updates dynamically, sometimes I have to click the Clear Baked Line Art button to force an update in the viewport.\n\n1. Open the attached file.\n2. Clear the baked line art. Do *not* try to bake.\n3. Keep \"Camera to View\" set on. (Note that in frame 1, lineart is updated as you navigate through the view)\n4. Step through each of the 3 frames, and rotate the view with middle-mouse-drag.\n\nOnly one of the frame/camera will properly update the lineart. As the viewport moves to the rear of the cube in the other two, the lines are missing. I haven't found an obvious reason why one frame is working, or why that frame. The working one has been 1 or 2 just while I wrote this report.\n\nClicking Clear Baked Line Art again will update the cureent viewport so it is correct, but rotating the view will again show one camera binding working, the other two not. It does not seem to matter which frame is active when the Clear Baked Line Art is clicked.\n\n", "Hair Strand or Strip only shows in Eevee for the viewport \nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nHair Strand or Strip toggles only shows in Eevee for the viewport. If you only use Cycles you won't even know you have the option to display hair particles by thickness. \nIf you toggle it with Eevee enabled the settings port to Cycles though." ]

[ "Strange EEVEE flickering and lack of clarity\nOperating system: Linux-5.4.0-65-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Alpha\nWorked: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-06 19:20, hash: d2c102060d44, type: Release\n\n\nWhen in render or material view and while rotating an object or moving it appears like there is shifting. The view port isn't as smooth as it used to be.\nI've attached a video comparison below\n\nBelow are two videos. The one with the problem is from the latest master build identified above. And the one without the problem is from\nversion: 2.92.0 Alpha, branch: master, commit date: 2020-11-06 19:20, hash: d2c102060d44, type: Release\n\nThis commit seems to be related:\n75580fa6a661eba58f9d39f8332985b1b72d3bc3 Fix flashing eevee render passes in viewport\n\nBut it doesn't appear to fix the entire problem\n\nLook at the neck line in both videos. The flicker is quiet noticeable there.\n\nVideo showing the problem\nmOl7cv_jz8o\n[blender-flicker.mp4](blender-flicker.mp4)\n\nVideo without the problem\nbjLunAuB1Ho\n[blender-noflicker.mp4](blender-noflicker.mp4)", "Viewport \"vibrates\" when mouse input is active\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\nWorked: version: 2.93.0 Alpha\n\nCaused by 000a340afa\n\nAny kind of rotation/translation/zoom in viewport induces constant render shaking in all visible objects\nThis issue persists as long as mouse sends any kind of input\nThis issue is only in EEVEE mode (cycles, Workbench, solid, Wire don't show any problems)\nThis issue is specially severe in tablet users\n[2021-02-13 15-21-52 2.mp4](2021-02-13_15-21-52_2.mp4)\n\n\n- Open default file\n- Change viewport to render mode in EEVEE\n- rotate camera around, navigate throught space\n- notice that objects are shaking\n\n" ]

[ "Cache of cloth simulation is not read by blender after reopening the file (pre-roll)\nOperating system: Windows-10-10.0.10240 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 75)\n\n\nI bake the cloth simulation. I see the *blendcache_cloth* folder. When I close and reopen the .blend file, the data in the cache folder is not read. When I go to the physics tab, I see the *Delete Bake* button. This means that blender recognizes that I baked the simulation before but the cloth plane is not animated.\n\nNote 1 : For a small project, when I choose *Automatically Pack into .blend* it works but for some large project it doesn't work even after choosing *Automatically Pack into .blend*. Anyway, I wouldn't like to pack All because this will double the size of the texture, audio files, ...etc on my hard drive. \n\nNote 2 : I also tried the method of exporting the cloth simulation as .mdd file. When I import this file again using **File>Import**, the cloth plane is animated but it is inserted in a very very far location from its original location. The solution is to use Mesh Cache modifier and to modify the axes and to clear all transformation.\n\n1. Download the attached .blend file.\n2. Select the plane.\n3. Go to the Physics tab to see the properties of the cloth simulation.\n4. Click on \"Delete Bake\" if you find it.\n5. You may reduce the End frame so that you don't bake the whole 500 frames. You can make it 100 or 200 depending on your computer's speed.\n5. Click on \"Bake\" to bake the animation with the Disk Cache option enabled. \n6. Save the file. Close blender. Re-open the file. \n7. Try to play... No animation!\n\nI wish if there was an option to enter the path or the location of the cache folder. Thank you for your support and for caring about our bug reports. That's really appreciated :)\n[cloth.blend](cloth.blend)\n\n\n", "Rigid Body Constraint - Generic Y axis problem\nOperating system: Windows 10\nGraphics card: Gigabyte RX 590 gaming x 8 gb\n\nBroken: 3.2.0\nWorked: I don't know. I haven't tested in previous versions.\n\nWhen using \"Rigid Body Constraint - Generic\", a problem occurs when I restrict rotation in the y-axis. When I try other axes they are fine. I haven't tested this on other versions. Or I'm causing the physics to be miscalculated, I'm not sure. I leave the file below;\n\n**Steps to Reproduce**\n- Open .blend file\n- Play animation\n[Rigid Body Constraint - Generic.blend](Rigid_Body_Constraint_-_Generic.blend)\nVideo: [F13411735](2022-08-22_21-41-37.mp4)", "Removing Effectors (from a Collection, or deleting corresponding object) does not refresh physics, hair properly\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.83.8\n\n**Desription**\nHairs do not react to force deleting.\n\n**To reproduce**\nOpen file, delete force field object.\nHair system will keep it`s deformed shape, despite force do not exist anymore.\n\n[2020-11-08_22-34-26.mp4](2020-11-08_22-34-26.mp4)\n[late responce.blend](late_responce.blend)\n\n- in `build_effector_relations` the relation is properly **not** built anymore, but there is no way to detect if this actually changed compared to the previous state. \nAnd since nothing else changed in participating objects (e.g. it doesnt even refresh if you have two forcefields and remove one of them), no \"proper\" update happens.", "Animated particle emitter refuses transforms within simulation range\nOperating system: Win8.1x64\nGraphics card: 3xgtx580\n\nBroken: 2.79, 2.82\n\nAn animated object with a particle system it is not properly transformed in the frames within the simulation range.\nIn **Blender 2.79** the object jumps back to it's animated location on confirmation on hotkey or widget transformation.\nIn **Blender 2.82** the object doesn't even transform, but its particles does.\n\nTemporarily setting particle system Subframes parameter to 0 seems to be a workaround, eliminating the behavior.\n\nHere is a gif showing the bug in 2.82 and 2.79:\n\n\n- Open attached file\n- (G)grab move the emitter\n[particle-subframes.blend](particle-subframes.blend)\n\nIn blender 2.82 you must change the visibility of objects. If you want to skip this step, use this file:\n[particle-subframes-283b.blend](particle-subframes-283b.blend)", "\"Updating Objects Flags\" Stalling Blender\n{[F10130762](22_Nautilus_through_City_-_Cycles___Eevee.zip)}Operating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 2.92.0\nWorked: Not working down to 2.83 LTS\n\nThis file will not render the Scene named \"Cycles\" with the Cycles render engine. \n\n\n1. Open attached blend file. Note everything except camera and lights are turned off.\n\n2. Using command line, attempt to render a single frame (say 130).\n\n3. Result = Everything initialises but the render stalls on \"Updating Objects Flags\".\n\n4. Open the file in UI\n\n5. Render image renders a blank image (expected).\n\n6. Turn on Buildings and Landscape, 9 collections from the top, and Nautilus and Submarine Search Lights at the bottom. \n\n7. Render a single frame, or the cycles render layer in the compositor.\n\n8. Result = A single image may render in cycles (followed by the second scene in Eevee that composites).\n\n9. Render animation\n\n10. Result = Blender hangs on \"updating objects flags\" and it does not render, and it is not possible to cancel the render.\n\nIt may be possible to get back rendering by saving the file as a new file. But as soon as rendering an animation as attempted, \"updating objects flags\" hangs Blender either in command line or in UI mode.\n\nNotes: \n\n1. I have tried the same file on multiple machines and multiple Operating Systems with the same result.\n\n2. Quite a number of files have similar kinds of problems. Most commonly, the files will not render in UI mode. Usually though, rendering in command line works. In this case it does not.\n\n3. I have tried every permutation of trouble-shooting I can think of. I have added meshes back in one by one, re-baking ocean modifer, particles, everything. Trying recently, I had to re-bake the particles after which rendering stopped working in any configuration. The particle systems have been baked to a disk cache.\n\n4. Reconstructing from a new blend file is pointless - new blend files are fine and I do not know what is happening to bring about the bug.\n\n5. It may be necessary to re-send the file in its state when it cannot render. Please let me know if anymore information is required.", "Adding and Removing RigidBodyWorld is broken\nSystem Information\nOperating system: MacOS 10.13.6 \nGraphics card: NVIDIA GeForce GT 750M 2048 MB\n\nBlender Version\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nRemoving RigidBody World and then adding it again doesn't work.\n\n- Add a floor and several cubes\n- Check that they collide as usual\n- Under Scene tab, select Remove Rigid Body World\n- Add it again and select the Collection as RigidBodyWorld as it was prior to removing\n# Simulation doesn't work as before.\n\n\n", "Particle System Orientation Axis set incorrectly after file load\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken:\n2.82 Beta, 507a331f0182, blender2.8, 2020-01-27\n\nAfter undoing any change, every particle system in the scene resets its orientation axis. To fix this, you have to manually change the orientation axis to something else and back again. There may be other situations where the particle orientation gets reset, but this one is easily reproducible.\n\n1. Open the attached file\n2. Set the ParticleSettings>Rotation>Orientation Axis to Global Z\n3. Shift-A and add a cube (or any change at all to the scene)\n4. Ctrl-Z\nThe particles are not longer aligned on the global z-axis. \n\nAlternatively, it also breaks if you:\n1. Open the attached file\n2. Set the ParticleSettings>Rotation>Orientation Axis to Global Z\n3. Save the file\n4. Close and reopen the file\n\n[ParticleBug.blend](ParticleBug.blend)\n", "v2.79 - Particle System \"Current Cache to Bake\" Not Work\nWindows 10 Enterprise 64-bit\nNvidia GeForce GTX1080Ti\n\nBroken: v2.79（5bd8ac9）\nWorked: (optional)\n\nAfter previewed and cached the simulation, I cannot read back the cached files after hitting \"Current Cache to Bake\", instead I have to hit the \"Bake\" button to bake it all again(spend the same amount of time as the first time caching it). This way I can read back the baked files and use on any new objects. However It would be nice if \"Current Cache to Bake\" works so I can save some time on every simulation I have already cached.\n\n1. Create a simple mesh(e.g. a plane).\n2. Add a new particle system.\n3. Set up a simple simulation(e.g. set normal velocity to 40 to simulate a fountain).\n4. Go to Cache tab, check Disk Cache, double click the cache and give a simple name(e.g. 001).\n5. Put timeline indicator to frame 0 and hit play, and then it will cache the simulation on a new folder next to your .blend file.\n6. After it is cached, hit \"Current Cache to Bake\".\n7. In the same Cache tab, check \"external\", locate the file path, and leave the cache file name as \"001\"(as you named it). Leave the Index Number to 0.\n8. It shall now indicate that \"2 Points are Found!\"(where you shall have 1000 points by default). If you hit play it will only play 2 out of the 1000 particles you have cached.\n9. Now return to Step 6, hit the \"Bake\" button instead of \"Current Cache to Bake\", the progress bar will show and it will take the same amount of time as your first time played(cached) the simulation.\n10. After baked, repeat Step 7, you should get \"1000 Points Found!\" now.\n", "Blender shuts down when playing a Rigid Body animation in a linked scene \nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.13492 Core Profile Context 22.19.677.257\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nBlender shuts down when playin the animation of a rigid body object in a linked scene\n\nLoad Factory Settings\nAdd the cube as Rigid Body\nCreate a new scene, Linked Copy\nPlay the animation in any of the two scenes\nWhen switching to the other scene, Blender shuts down\n\n", "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", "Metaball properties do not update during animation playback\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.8, 2.9\nWorked: 2.79\n\nMetaball particles do not update during animation playback when their location, radius, stiffness and other properties are animated within one object (when one metaball object has multiple particles). I'm not the only one who have this problem: 2-8-metaball-animation-viewport-metasurface-doesnt-update\n\n1. Create one Metaball object, enter Edit Mode and insert keyframe to its location, radius, stiffness, hide or other properties.\n2. Change the frame, move the metaball or change its property and insert another keyframe. Notice that if you will try to use Autokey, it won't work and just show corresponding parameter in orange.\n3. Play animation.\n\nIn 2.79 you will be able to see your particle being updated in real time.\nIn 2.8 and 2.9 you will only see particle's radius circle moving (or property checkbox changing its status) but not the particle itself. ", "Keyframes and drivers on custom nodes properties seem not working\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 540 Intel Inc. 4.1 INTEL-12.4.7\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI'm not able to animate the properties of custom nodes. Keyframes do not work properly: when I set one all the others seem to disappear and only the last value set as a keyframe is shown on every time step.\n\n1. Go to the text editor, import the 'Custom Nodes' template and run the script.\n2. Open the 'Custom Node Tree' area.\n3. Add a 'Custom Node', in the 'Some Nodes' category.\n4. Add a keyframe for 'my_float_prop' on frame 1.\n5. Change the frame, change 'my_float_prop' value and set a keyframe.\n6. Now I should see (at least it was like this in the last version) the property changing while scrolling through the timeline between the two keyframes I just set, but I don't. The property keeps the last value.\n", "Hair Dynamics does not work for all strands when hair has been cut\nSystem 1:\nOperating system: Linux Mint 18.3 Cinnamon 64-bit\nCinnamon version: 3.6.7\nLinux Kernel: 4.13.0-39-generic\nProcessor: Intel Core i5-4430 CPU @ 3.00GHz (4 cores)\nMemory: 23.2GiB\nGraphics card: NVIDIA GTX 1070 + NVIDIA GTX 760\n\nTested and verified on secondary PC with Linux Mint 18 Cinnamon + Intel Core M-5Y10c CPU (duo core) as well.\n\nBroken:\n - 2.79 (official),\n - 2.79.6 (build hash: e50a3dd4c4e),\n - 2.79.6 (build hash: 5c10c92b23c),\n - 2.76b (official),\n - 2.80 Alpha 2 (build hash: ee7236859df),\n - possibly more.\n\nSimulating hair dynamics using the hair dynamics option (standard settings) does not work for all hair particles when the hair has been cut in particle edit mode. In particular, hair simulation only works for some strands, the others remain stationary throughout the simulation. The affected particles are seemingly random depending on the cut shape, although shorter strands seem to have a larger likelihood of remaining stationary. The affected strands do not change over time, they only change depending on the cut.\n\nSee attached .blend file for the finished result.\n[hair_dynamics_bug.blend](hair_dynamics_bug.blend)\n\nSimplest way to reproduce:\n1. Add a particle system to the default cube. (Rotate the cube 45 degrees to prevent vertical hairs - this is to allow gravity to work on all hairs.)\n2. Change particle system type to 'Hair'. Do not change any of the other settings.\n3. Go to particle edit mode with the cube selected. Using either the 'cut' tool, shrink tool or shape cut, cut the hair to some arbitrary shape (preferably with both long and short strands).\n4. Enable 'Hair Dynamics' in the particle settings tab. Do not change the settings there (although changing any does not resolve the error to my knowledge).\n5. Perform the simulation by pressing the 'play' button in the timeline. If the bug has been reproduced, you should see some of the hair particles fall down normally, whereas some of them will remain stationary. If not, try a different cut.\n\nWhen performing all steps above, except for the particle edit, the bug does not occur. Therefore, the culprit seems to be in the length of individual guide hairs.\n\nThe bug seems to occur using more complex geometry as well.\n\nAnother note: using a hair length texture does not produce the bug - because the guide hairs still have uniform length.", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)", "Particle Systems don't inherit object velocity when emitted on one frame. \nOperating system: Windows 10 64-bit\n\n2.90.1\n\nIf a particle system is set to emit all particles on a single frame, it will not be able to emit using an objects velocity. Instead they are simple emitted with zero velocity. Increasing the emit time will improve accuracy. But of course then you cannot emit particles on one frame\n\n- Open attached file (It has two moving objects each with a particle system that should theoretically start with the velocity of the object)\n- Run the animation\nor\n - Apply particle system to mesh\n - Keyframe mesh movement\n - Set object velocity parameter to 1.0\n - Emit all particles on single frame\n\n[particle_object_velocity.blend](particle_object_velocity.blend)\n\n**Proposed Fix**\nHave the particles use the derivative of the F-curve functions to get instantaneous velocities. \n\n\n\n\n" ]

[ "force fields not updating for rigid bodys\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 61)\nWorked: (optional)\n\n\n\n\njust play animation and then change force field strengh and play again. it will not update . found out if you click on Steps per second in properties wwindow > scene > rigid body world > steps per second. not sure for other force field types but few months ago was still same bug\n\n[Force Fields problem.blend](Force_Fields_problem.blend)\n", "Rigid body doesn't work well \nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.21 355.11.10.50.10.103\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nRigid body seems not to work well on my computer. If I add force field with an empty and I want it to interact with the Rigid body, it doesn't work sometimes. It looks like the cache doesn't empty itself. I tried to empty it manually through the Rigid Body cache (clear cache) but it doesn't work.\n\nThe only way I found, is to reload the file and then the force field interact with the rigid body correctly. Sometimes it works, but sometimes it doesn't. \n\nI first thought it was a normal behaviour but then I launched the old version of blender (2.79) and I worked perfectly fine on it.\n\n\nAdd sphere and apply rigid body on active mode\nAdd empty with force field harmonise\nChange the strength of the harmonise \nPlay the animation each time you change the harmonise value and something weird appends.\nSeems like the cache doesn't work well." ]

[ "Hair Dynamics: simulation doesn't work depending on smooth/flat shaded surfaces (and nvidia gpus?)\nOperating system: Windows 10\nGraphics card: RTX 2070 QMax\n\nBroken: v 2.80\nWorked: (optional)\n\nhair dynamics doesn't work, hair stuck in place, doesn't follow the mesh\n\n- build simplest possible model with hair dynamics\n- add simple animation\n- with hair dynamics disabled: hair follows mesh\n- with hair dynamics enabled: hair just stays behind and stretches to the mesh\n- changing settings, clearing cash ... all to no avail\n\n[190814_test_hair_dynamics.blend](190814_test_hair_dynamics.blend)\n\n", "After duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\n\nBroken: `master` branch\nWorked: Don't know if it ever worked\n\nAfter duplicating a collection with rigidbody objects, the simulation doesn't apply to the new rigidbody objects\n\n**Steps to Reproduce**\n\nIn a new blender project, add a new collection. Add a cube to the collection. Add a rigidbody to the cube. Verify that playing the simulation causes the object to fall under gravity.\n\nCopy and paste the cube to create a new cube inside the collection. Move the new cube so both are visible. Verify that playing the simulation causes both cubes to fall under gravity.\n\nIn the outliner right-click on the collection and select \"Duplicate Collection\". Move the two new cubes so all four cubes are visible. Run the simulation.\n- The two cubes in the original collection will fall under gravity.\n- The two cubes in the duplicate collection do not move and are not affected by the simulation.\n\n \n\nIt appears the two cubes in the duplicated collection are not added to the RigidBodyWorld collection.\n\n", "RBD sim ignores mesh (cloth) deformation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.0.0 Alpha\nWorked: BLENDER 2.79b\n\nOpen below file and press play. RBD sim ignores mesh deformation and reacts to its undeformed state instead. The setting of 'deforming' shown below is ignored in versions after 2.79b:\n\n\n\n[rbd sim ignores mesh deformation .blend](rbd_sim_ignores_mesh_deformation_.blend)\n\nHere's another file, this time using an alembic as the deforming object. It still acts as though the mesh is not deforming...which is strange considering it's an imported deforming object.\n\n[rbd sim ignores mesh deformation on imported USD as well .blend](rbd_sim_ignores_mesh_deformation_on_imported_USD_as_well_.blend)\n\n\nAll works as expected in 2.79b\n\n[279b physics .blend](279b_physics_.blend)\n\n[2021-09-04 19-46-49.mp4](2021-09-04_19-46-49.mp4)", "Viewport not updated after changing material properties\nWindows 10\nGraphics card:\nGTX 1660TI\n\n\nBroken: version: 3.2.0 Beta\nWorked 3.0\n\nHello. If you create an object, for example, a sphere, assign it a material with a base color, for example, red or something else, then copy the material, create another object, create a material for it, and then paste the material on the new object, the material that was copied will be inserted, but if after that you start changing it it will not change on the object until it is reselected.\nWhy don't its settings change immediately after changing them in the settings? Is this a bug or is it supposed to be like this?\n\nI copied the material from the sphere to the cylinder, it was added to it, after that I replaced the base color on it with green but it does not change on the cylinder.\n\n**Steps to reproduce**\n[#98458.blend](T98458.blend)\n\n- Open file\n- Copy material from selected (green) cube\n- Paste material to other cube\n- Change Base Color in pasted material\n\nColor is not updated in viewport.", "why some hairs are not moving with dynamic hair? in blender 2.90/2.91\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.1\n\nwhy some hairs are not moving with dynamic hair? in blender 2.90/2.91\nif I don't modifer the hair weight all the hairs will move,but when I brush some weight to the hair ,\nsome hairs are not moving in dynamic.\n\n[dynamic hair error.blend](dynamic_hair_error.blend)\n\n", "Modifying keymap won't tag prefs dirty\nWindows 7 Professional 64-bit service pack 1\nIntel Core i7-2600\n8GB RAM\nNVIDIA GTX 1060 6GB\n\nBroken: blender-2.80.0-git.aa003c73245f-windows64\n\n\"Save Preferences\" button, shown when \"Auto-Save Preferences\" is turned off, stays unavailable after modifying keymap.\n\n1. Make sure \"Auto-Save Preference\" is turned off. If it isn't, turn off this and press \"Save Preferences\" button.\n2. Modify keymap, editing the settings used to activate an operator (example: search for `Clear Rotation` operator, changing the `Clear Delta` option will not tag prefs dirty).", "Boolean Modifier not working \nOperating system: Windows \nGraphics card: Nvidia Geforce GTX 770\n\nBroken: 2.93.4\nWorked: 2.90\n\nIf one tries to apply the boolean modifier \"Difference\" it does nothing. In previous version it functions.\n\n1. Download the Blender File from above \n2. There a 3 objects in the collections. The objects are in the positive xy-quardant. (Sorry that they are not centered)\n3. If one tries to apply the modifier on the Frame object there is no error message but the frame object doesnt get modified.\n\nGreetings Philip \n\nTest File:\n[#71360.blend](T71360.blend)", "Action Editor: Animations no longer work after renaming bones.\n**Information & Blender version**\nWindows 10, 64 bit, CPU integrated/no graphics card [doubt it's relevant but: AMD A8-7600 Radeon R7]\nBroken Blender Version: 3.3.0, master, 2022-09-06, hash: 0759f671ce1f\nNo idea if it worked in a previous Blender version.\n\n**Description**\nThis happens while using Action Editor and creating several actions to store different animations.\nIf at some point you rename bones, the action that is currently active will automatically update it's paths and continue to work, but any previous actions will not update their path and the animation will no longer play. \n\nFixing it requires either:\n1) manually changing the name of each affected path through the graph editor.\n2) Select the bone, select the affected channel under the action summary, temporarily change the name back to what it used to be, then change it again to the new name. This way the path gets updated.\n\n\n**Reproduce Error & File**\nYou'll need to create at least 1 bone first.\nCreate an action [dope sheet/action editor] and make an animation.\nCreate a new action, make a new animation, and change the name of the bone. The action that is currently active continues to work, but any previous actions now have a broken path and no longer work.\n\nIn this file I made 2 actions with different animations, I had \"Action 1\" active while I renamed the bone form \"Box\" to \"Bone\". Now \"Action 1\" continues to work, while \"Action 2\" no longer plays.\n\nFor this test I changed the name of the bone while in pose mode through Bone Properties.\n\n**Important note: This seems to not happen all the time, I'm not sure why.**\nWhile making this file to recreate the issue, I first created both actions actions and animations, and I had \"Action 2\" active when I changed the bone's name from \"Bone\" to \"Box\". This seemed to create the error for a moment, but when I changed from \"Action 2\" to \"Action 1\" and back to \"Action 2\" it resolved itself and I was able to see both animations.\nI then had \"Action 1\" active while I changed the name of the bone from \"Box\" to \"Bone\", and now the error persisted. [even after closing and reopening the file]\n\nI made the test again with a new file [not attached] and the error persisted, I saved the file, closed it, and after re-opening the file the error was gone.\nSo it seems sometimes the paths get updated automatically and other times they don't.\n\n[BrokenActionTest.blend](BrokenActionTest.blend)", "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)", "Rigid Body Constraints ignoring keyed rotation limits\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\n\nRigid Body Constraint limits seems to be only taking initial values, ignoring keyed values.\n\n\n1. Open attached blend file\n2. Verify that `Constraint.002` object has Rigid Body Constraint, Generic type, and Z upper angular limit keyed (from frame 1->40, 90->20 deg).\n3. Play animation.\n4. From frame 40 and on, that Z upper angular limit is keyed to be 20 deg, but the cube being hit will still rotate to 90 degrees (expecting limited to 20 deg).\n\nTested \"Generic\", \"Hinge\", \"Generic Spring\", none respects the keyed rotation limit.\n\n-----\n\nOriginal description:\n\n\nGeneric and Generic Spring constraints will ignore keyframed changes in their lower and upper limits.\n\n1. Create 4 Rigid body cubes and a passive ground plane under them.\n2. Line 3 of the cubes up on the X axis.\n3. Connect each of the 3 cubes with rigid body constraints set to generic.\n4. Set one of the cubes on the end to animated.\n5. Select the constraint between the animated cube you just made and the next one in line and set all limits to 0.\n6. Select the next constraint in the line and set all angular rotation limits to zero except the z angle upper limit, set that to 90.\n7. Set a keyframe on the upper limit Z axis of that same constraint on frame 1.\n8. Go to frame 40 and set the upper limit Z axis to 20 and keyframe it.\n9. Take the 4th cube you made and position it behind the cube on the end that is not set the animated.\n10. Take that same cube and make it animated and keyframe it on frame 40.\n11. Move that 4th cube to hit the none animated cube at the end of the line and keyframe it.\n12. Then hit play, the constraint will ignore the changed upper limit and rotate to 90 even though it shows as being only 20 in the properties panel.", "Bone isn't affected by influence keyframe if the action is shared (*).\n(*) The complete tittle would be: \"Bone isn't affected by influence keyframe if the same action is shared with another armature with bones with different names\".\n\n[80-influence-not-respected.blend](80-influence-not-respected.blend)\n\n- Open the file.\n- Move in timeline and see what the bone (armature \"B\") does with its constraint.\n- Select armature \"C\".\n- Move across the timeline in DopeSheet: **bone of armature \"B\" isn't affected by influence keyframe**\n\nThe channel of the armature \"C\" gets red underlined. So, the Action is affected of this \"red-underlineness\"... so, armature \"B\" is affected too.\n\nI know that this is a kinky bug... it is not normal/suggested to use the same action in different armatures with different bones. I discovered this bug by doing that, by mistake.\n\nMaybe it is not usefull to put time on fixing it, because it is not a normal configuration. You guys decide.\n\n", "Viewport gizmos in selection tools not updating.\nOperating system: Windows 10 64Bits\nGraphics card: GeForce GTX 1050 Ti latest driver\n\nBroken: version: 2.80.69 hash:4f6e25280558\n\nswitching between Active tools gizmos and viewport gizmos keeps the manipulators in it's previous position until a second selection...i assume because we have two different and unrelated gizmos!! \n\n\n- Activate transform gizmos in the gizmo popover.\n- Use Active tools manipulators and do transformation.\n- Switch to the selection tools.\n\nThe gizmo center is not updated.\n\n**Attachment**\n", "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)", "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)", "Smoke artefacts when baking smoke simulation based on particles\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.2\nWorked: none\n\nI have a baked particle simulation that is propelled by a wind force field. Next, I have a smoke simulation whose flow source is set to particle system.\nWhen I run the simulation it takes much longer than usual and ends up creating lines of smoke in random directions.\n\nI add that all the sliders in the field weights tab of the domain object are at 0 (gravity, all...) so no force field can be the cause of this scattering\n\nHere are some pictures of the problem :\n\n\n\nWith higher resolution :\n\n\n- Open the blend file\n- Bake Particles\n- Bake Smoke\n\n[SceneProblem2.blend](SceneProblem2.blend)\n\n" ]

[ "Rigid body cache not invalidated when field settings are changed\nOperating system: macOS 10.14.4\nGraphics card: GeForce 650M\n\nBroken: 2.8 2019-05-14 22:59 fc59\nWorked: (optional)\n\nNew force field settings don't take effect unless an object is moved\n\n\n1. For clarity, disable gravity\n2. Add a cube and make it a rigid body. Move the cube a few units along the +X axis\n3. Add a wind field with all default settings (so it's at world origin pointing up)\n4. Press space to start the animation and let it run for N frames (say, N = 100). As expected, nothing will happen because the wind is pointing up\n5. Rotate the wind so it's pointing at the cube and increase the strength to 100\n6. Replay the animation\n\n***Up until frame N, nothing happens--the old cached movement is used. The field only seems to take effect at frame N + 1***\n\n7. Move the cube a tiny bit in any direction\n8. Replay the animation\n\n***The wind takes effect starting in frame 1***\n" ]

[ "GPencil: Square type strokes do not react to Rotation option with Solid Shading\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 3.0.0 Alpha\nWorked: ?\n\nThe stroke type Squares draw little squares at the points of the stroke. The rotation is controlled by the alignment option and the rotation slider, which in this case does nothing if solid shading mode is selected. Note that textures are not displayed in solid shading mode and even if used the squares don't rotate as long as I am in solid shading mode.\n\n1. Add default Stroke Grease Pencil Object\n2. Navigate to the Material and change Line Type to Squares\n3. Make sure you are in Solid Shading Mode with \"Color\" not set to \"Texture\"\n4. Change the Rotation slider from the same panel, which says in the tooltip it should rotate the squares\n5. observe how the squares do nothing at all.\n\n", "Cursor doesn't change to the Edit Mode cursor when you use a tablet in some cases.\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics (ICL GT1) Intel 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: version: 3.1.0 Alpha\nBroken: 3.1, 3.0, 2.93.7, 2.83.18, 2.80.\nWorked: In a way, 2.79 behaved better in that regard (but 2.79 did not change the cursor in slider fields).\n\nWhen you use a tablet in Edit Mode, when you hover over a number field, and then lift your pen and lower it again in the Edit Mode window, the cursor don’t change back to the Edit Mode cursor (the cross). \n\nUse a tablet. Go to edit mode and place your cursor on one of the transform fields on the right hand side. Than lift your pen untill it disconnects from your tablet. Place your pen in the Edit Mode space on your tablet and lower your pen untill it connects with your tablet. The cursor doesn’t change to the Edit Mode cursor. If it does, try again.", "Clicking on a pie menu item doesn't work when holding the pie menu key.\nOperating system: Windows 10\n\nBroken: 2.79, 2.92\n\nClicking on a pie menu item doesn't work when holding the pie menu key. This is a problem because sometimes the pie menu key release isn't detected by blender and then the it locks the UI.\n\n1. On the 3D Viewport hold Z for the shading pie menu.\n2. While still holding Z try clicking on the pie menu items. Doesn't work.\n3. While still holding Z, left click on Windows's Taskbar then release z.\nAfter that, clicking on the pie menu items doesn't work even though the user isn't holding the pie menu key anymore, blender still considers that the key is held. Then Blender gets locked to the user unless he knows to press esc or right click. The solution is making the pie menu clickable even when the pie menu key is held.", "Dopeheet (in the Grease Pencil submodule) take account the transform keys of the GP object wen you press jump to previous/next key frames.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.14802 Core Profile Context FireGL 21.Q4 30.0.14011.2006\n\nBroken: version: 3.4.0 Alpha\n\nDopeheet (in the Grease Pencil submodule) take account the transform keys of the GP object wen you press jump to previous/next key frames.\nIn this Grease Pencil submudule only the GP drawing keys should be taken into account.\n\n**Steps to Reproduce**\n- Open .blend file\n- Select Grease pencil mode in Dope Sheet\n- Jump to next keyframe \n[#100538.blend](T100538.blend)\nHere a quick video with the issue:\n [2022-08-21 15-13-26.mp4](2022-08-21_15-13-26.mp4)\n\n\n\n", "Sculpt mode - program crash: brush smooth + graphics tablet\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.30\n\nBroken: version: 3.6.0\n\nUnless explicitly specified in \"preferences > input > tablet > tablet API > wintab or windows ink\", it crashes when using smooth brush. If I use the \"automatically\" setting.\nFor the bug to recur, the brush must take a force or size parameter from the pressure force on the graphics tablet. If I use the mouse, the error does not occur.\nThis error is repeated in any scene and with any object. I created a cube, remesh it and used a smooth brush in sculpt mode. Blender crashes to completion.\n\ngraphics tablet: xp-pen star 06\n\n", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n", "\"Dots\" stroke method is ongoing even without moving the cursor when using a pen\nOperating system: Linux-5.15.0-50-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.4.0 Alpha\n\nThe Dots stroke method is meant to apply the strength of the brush on each stroke dab.\nThis is working like intended when using the mouse. If you don't move the cursor, the stroke stops.\n\nBut when using a pen, even when holding the pen perfectly still, the stroke is ongoing on the stop.\nThis way the stroke method is working very much like the Airbrush stroke method,\n\n- Add a cube and subdivide it many times\n- Use the draw brush in sculpt mode\n- Set the stroke method to \"Dots\"\n- Draw a stroke and hold it on a single spot without moving the cursor or releasing LMB\n- Try this with a mouse and a pen and see how they compare.", "Scene Line Art problem when used with Grease Pencil objects.\nOperating system: Windows 10\nGraphics card: Radeon RX 590\n\nBroken: (2.93.0 Beta, 0f66dbea904f, master, 2021-04-21)\nWorked: ()\n\nScene Line Art or Object Line Art are located in front of the Grease Pencil objects.\n\n\n[SceneLineArt_and_GPencil.blend](SceneLineArt_and_GPencil.blend)", "Weight paint brush: front faces only not working.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 11)\nAlso 2.82a broken\ndisabling and enabling «Front faces only» do nothing. Brush still paint backfaces.\n\n[2020-04-08_10-48-06.mp4](2020-04-08_10-48-06.mp4)\n\n\n\n", "Greasepencil 3.0: Unable to switch to drawmode from sculptmode\nOperating system: Linux-5.15.0-73-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 4.0.0 Alpha\n\nEnable GP 3.0\nOpen 2D session\nSwitch from the initial draw mode to sculpt mode via header button.\nTry to switch back to draw mode.\nAn error message appears:\n\n", "GPencil: Hard to erase drawing when layer parented to animated object\nOperating system: MacOs 10.15.4\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: Version 2.90 (2.90 2020-05-20)\nWorked: ?\n\nSorry for the potentially misleading title. I think that when a Grease Pencil drawing is parented, and the parent animated, the erase tool (using control/Alt/Right Click or the Brush eraser) is somehow offset and it's near impossible to erase precisely. Going in Edit mode and Selecting/Deleting the vertices/strokes works though... \n[GP_EraseWhenParentedIssue.mp4](GP_EraseWhenParentedIssue.mp4)\nHere is the Blend file.\n[GP_EraseWhenParentedIssue.blend](GP_EraseWhenParentedIssue.blend)", "Shortcut detection problem for tablet user\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\n\nThere are 2 types of shortcuts in Blender.\n1. General shortcuts that work regardless of the location of the mouse pointer. such as 'Ctrl+S'\n2. Window specific shortcuts that work only when the mouse pointer is hovering on the specific window.\n\nThe issue is about the second type of shortcuts that happens to tablet users.\nThe problem is that Blender shortcuts don't work even though the mouse pointer stays on the specific window if the tablet stylus is further from the tablet surface. \nThis behavior can't be reproduced with mouse on.\nBecause there's no indication on screen whether the window is activated to register shortcuts, users will be difficult to pinpoint why the shortcuts are not working.\nIt's also very difficult to utilize shortcuts when users need to press the shortcuts with a stylus in hand or shortcuts that require two hands to operate.\n\n\n\n\n\n1. Start up Blender on PC with a graphic tablet\n2. Make sure no mouse is connected on PC\n3. Select the cube mesh and go into edit mode\n4. Select one of vertice of the cube mesh\n5. Lift your stylus out of the tablet while making sure your mouse pointer stays on the desired window\n6. Try shortcut such as 'L' to select linked\n7. You will see the shortcuts don't work\n\n\n\n\n**Solution that I can think of is:**\n\nTo be able to recognize and register the shorcut inputs as long as the mouse pointer stays on the specific window even if the stylus is out of the distance of the tablet surface.\n\n", "Some hotkeys stop functioning after conforming Chinese/Japanese text input\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93.4\n\nSome hotkeys stop functioning after conforming Chinese/Japanese text input.In my case,the pie menu on {key ~}{key ,}{key .} are disabled, though if after input,switch to another input method, these hotkeys become available again.\nI‘m using **Microsoft Pinyin** input method on Win10.\n\n**Exact steps for others to reproduce the error==\n{icon fa-plus} OS Conditon: **WIN 10** |Blender: **3.0 Alpha**\n- Install **Microsoft Pinyin** input method:\n\n- Default setup.\n- Rename the cube in Chinese/Japanese.\n- Test the hotkey {key ~}{key ,}{key .}, they shouldn't be functioning.\n- Change the input method to something else, test {key ~}{key ,}{key .}, they should be functioning again.\n- Input some Chinese/Japanese in the text field, test {key ~}{key ,}{key .}, they shouldn't be functioning again.\n\n", "grease pencil fast draw loses details in macOS\nOperating system: macOS 10.13.4\nMacBook Pro (Retina, 13-inch, Early 2015)\nIntel Iris Graphics 6100 1536 MB\n\n2.83.3\n\nFrom the grease pencil refactor demo, smoother drawing of fast strokes is achieved. \n\nBut when I tested, from the left drawing of the attached file, slow drawing produce smooth and accurate line. but the right drawing losses details in fast drawing and easily create corner. Is it an issue for macOS?\n[fast_stroke.blend](fast_stroke.blend)\n\nComparison with drawing in Preview.app\n\n\n\n**Steps to redo:**\nNew file > 2D animation\nScribble real fast.\n\n", "Grease Pencil: stroke placement \"Surface\" projects onto lamps and empties\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: AMD Radeon HD 5700 Series ATI Technologies Inc. 4.5.13417 Core Profile Context 15.301.1901.0\n\nBroken: version: 2.83 (sub 5)\n\nIf you draw with *Stroke Placement* set to *Surface*, Blender interprets objects such as lamps and empties as surfaces and projects the stroke onto them. \nThis might be a feature rather than a bug. Maybe just \"unexpected behaviour\"?\n\n\n\n\n1) Create a new \"2D animation\" Blender file.\n2) Create a mesh (A) to project your strokes onto, like a plane for example.\n3) Create a lamp object or an empty (B), and place it in front of A, closer to your viewpoint in space than A.\n4) Select the GP object and go into draw mode.\n5) Set \"Stroke Placement\" to \"Surface\". (You can add an offset of 0.1 for easier visibility.)\n6) Draw over A, crossing over B here and there.\n7) Rotate your viewpoint. The stroke you've drawn should be projected onto A, with a few points projected onto B where they crossed over it.\n\n" ]

[ "Unable to Sculpt or Lack of Pen Pressure Response\n\nOperating system: Windows 10 64-bit\n\nGraphics card: Nvidia GTX 970\n\n\n\nBroken: 2.83.4, 2.81, (maybe others too)\n\nWorked: None\n\n\n\nSculpting with a graphics tablet does not affect the mesh unless a second window is opened. It will then only function in the second window as long as the first window remains open on the same file. Occasionally, the mesh will be affected except pen pressure will not be interpreted. \n\n\n\n - Open WIP1.blend{[F8796311](WIP1.blend)}\n - Select the Sculpting Workspace\n - Activate pen pressure control for Strength\n - Draw on mesh with any tool\n\n\n\n\n\n\n\n\n\n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "VEIKK A15 lag in win_tab mode and pen button doesn't work in win_ink mode\n**System** Notebook Lenovo Ideapad Y700 - 17isk \nOS: Windows 10 latest build 19041.450 (clean install some days ago)\nGraphics card: intel HD530 + GeForce GTX960M \nTablet VEIKK A 15\n*`All hardware work perfectly and drivers are updated`*\n\n\n\n**Blender Version** 2.83.5, branch: master, commit date: 2020-08-19 06:07, hash: c2b144df395f, type: Release\nbuild date: 2020-08-19, 04:10:17\n\n**Short description of error** in wintab mode the tablet heavily lag making impossible to draw smooth lines (see photo attached please); in win_ink mode draw is perfect but button of the pen doesn't work and clicking them sometimes seems that freeze everithing; pen pressure works always fine in both modes; i have also tried 2.9x beta and is the same problem.\n\n\nPLEASE READ THIS: as krita user i have experienced same issues there, except that with one krita option in tablet config, the problem IS FIXED.. i have to ask to you if is possible to do something in Blender? \n\njust try the tablet also in default 3d view" ]

[ "Working on a mesh that has a high multires subdivision causes blender to build Up memory even on lower levels.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\nRAM: 16GB\nCPU: AMD Ryzen 7 3800\n\nBroken: version: 3.6.0\n\nWhen editing a mesh that has been subdivided a few times will cause blender to increasingly start to consume more and more memory aggressively even if the modifier is turned off.\n\nSubdivide the mesh a few times using the multiresolution modifier, noted on 5-up levels on a mesh with originally 9 272 faces. then either switch the modifier Viewport Level to either 1 or disable It entirelly, start editing the mesh in edit mode the memory consumption stats will start to skyrocket with no signs of going back down until blender starts slowing down the computer and/or crashes entirely. (Got to about 32 GBs some times about where the computer would stop handling It anymore) I haven't tried doing it in workbench I think so I'd suggest trying to do It in Eevee mode too.\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "Blender 3.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.", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n", "Assert in debug for dyntopo sculpt\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: Today main.\n\nSee attached stack trace file.\n\nIn debug:\n1. Sculp mode.\n2. Enable Dyntopo option.\n3. Do something.\nSee the crash.\n\n", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "Mask brush stops working in tiling sculpting mode after changing its size through \"F\" hotkey\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 2.93, 3.3.0\nWorked: -\n\nWhen an object has the Multires modifier, mask brush stops working in tiling sculpting mode after. (See video below)\n[Desktop 2022.09.17 - 21.18.10.07.mp4](Desktop_2022.09.17_-_21.18.10.07.mp4)\n\n- Open attached file or\n - Add a grid object\n - Add a multires modifier\n - Subdivide Simple a few times\n - Select mask brush in sculting mode\n - set tiling on x and y axis to 1 or 2m \n- try paint mask (sometimes the tiling doesn't work at this stage, you need to paint again and undo)\n- change brush size through F hotkey\n- try paint mask (tiling stops working)\n- press undo\n- try paint mask (tiling works again)\n\n[tiling_sculpt_bug.blend](tiling_sculpt_bug.blend)\n\n", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n", "Modifiers disabled in viewport are not rendered if the object is in edit mode\nVersion 2.83\n\n\n - Open: [medieval_house_lights_camera.blend](medieval_house_lights_camera.blend)\n - Render with the object in edit mode and then in object mode.\nScene in object mode\n\nRender:\n\n\nScene in edit mode:\n\nRender:\n", "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)", "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "EEVEE: Blender Crashes when rendering specific File\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.93.0\nWorked: (N/A)\n\nBlender crashes when rendering specific file. It only seems to happen with this file - when I render other (even larger) files with the same inputs it works fine, but with this one it crashes every time. The error message is EXCEPTION_ACCESS_VIOLATION, but I received the data from an open source website and it is placed in a folder on my computer that I have full access to. Debug report: [blender_debug_output.txt](blender_debug_output.txt)\n\nSave NZ_Compressed40pc.jpg to desktop \nOpen Dev.blend\nIn the shader editor for the plane, ensure the image texture has NZ_Compressed40pc.jpg linked as input.\nRender>render image\n\nTest File:\n[Dev.blend](Dev.blend)\n", "Crash with Boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.1.2 (appears to have been broken since 3.2.0)\n\nBlender crashes when performing an Intersection Boolean between a cube and a bunch of loose faces. (Granted, this is probably not something you should do in the first place, but at least it should be limited to producing a bad result, not a crash.)\n\nI didn't find a crash log, but it's easy to reproduce.\n\n* Load the attached .blend file.\n* Scrub the timeline to frame 209. Blender crashes.\n\n[crash.blend](crash.blend)\n", "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" ]

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

[ "Bevel profile incorrect when using arc for inner miter\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.3.0 Alpha\n\nThe Bevel operation and modifier has an incorrect profile when the inner miter is set to arc and the profile value is either very high or low.\nthis happens in both edge bevel and vertex bevel mode.\n\n|Inner miter sharp (Ok):\n|---\n|\n\n|Inner miter arc:| \n|---|---\n||\n|Shape 0.93|Shape 0.5\nIn this case the Bevel kind of overshoots.\n\nProbably related to #95916 (Pinching effect when using bevel and bevel modifier).\n\n- Open attached .blend file\n[Test.blend](Test.blend)\n\nThank you and have a great day!\n\n---\nUPDATE:\nIn some cases it can also happen with Inner Miter Sharp (#105064)\n", "Transfer attributes in the fill curve node\nThis is like [D12363: Geometry Nodes: Transfer attributes in the curve to mesh node](D12363), but most likely much simpler.\n\nWhen there are non-builtin attributes on the curve (anonymous or named), they should be transferred to the vertices created by the curve fill node. The Delaunay triangulation can generate an index map for such situations, which should make the transferring quite simple.\n\nThe Delaunay index map shouldn't be created if no attributes will be transferred anyway, since it has a performance cost.", "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", "Fillet Curve Node: Merge points with limit radius mode\nWhen \"Limit Radius\" is turned on, the new points often meet in the middle and end up in the same location. This creates curves that are harder to work with in later nodes.\nAs a new option, these points could be merged by the node.\n\nThe point merges should be calculated before `calculate_result_offsets` so the new curves only need to be created/resized once.", "Wrong SubSurf modifier results with inconsistent normals\nOperating system: Windows 10 Enterprise Version 1803\nGraphics card: 2 x GTX1080 ti\n\nBroken:\nblender2.8, 2018-12-05\n\nFrom latest builds subsurf modifier make a wrong subdivision of geometry as displayed in the attached files.\nBefore 18/20 November the behaviour of subsurf modifier was ok.\nI am sure because I did an animation on that date and the subdivided vase was ok.\n\nBest regards,\n\nUmberto\n\n\n\n\n\n[ceramic.blend](ceramic.blend)", "Connected Proportional Editing cuts of in special case\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: ?\n\nWhile creating the ladder as attached, connected proportional editing seems to be stopped at certain points. It deforms the points near it, but as soon as it gets around one hole it does not propagate any further. This issue only appear with this indice order of the mesh.\n\n\n\n[connecteddeformbug.blend](connecteddeformbug.blend)\nTo prove that it is not a corrupted mesh, here is how to create it: (follow the steps exactly, otherwise it might not work)\n1. Create a plane object and tab into editmode\n2. Scale the plane 0.3 along the X-axis\n3. Add 3 loop cuts simultaneously to make almost squares (so there are 3 new edges pointing along the x axis)\n4. select everything and inset individual faces by 0.1.\n5. delete the interior faces (all at once) to get a ladder-like geometry\n6. try moving the long internal edges on the -Y side of the mesh.", "linking spring character breaks the nose!\nOperating system: Linux-6.3.8-zen1-1-zen-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.0 Beta / 4.0.0 alpha\nWorked:\n\nwhen reloading (opening) saved file of linked spring character, her nose is broken.This does happen only in linking, appending is working fine.\n\n1. Launch blender `./blender --factory-startup`\n1. File -> Link -> CH-spring (collection)\n1. Object -> Library Override -> Make\n1. Save the file\n1. File -> Revert\n\nas I said before, if you go append in the second step `File -> Append -> CH-spring (collection)`, the model works correctly!\n\nEdit: The model is a Blender Studio character [here]()", "Curve sculpting: occlusion by hidden parent makes the curves unresponsive to brushes.\nOperating system: Fedora Linux (Gnome Wayland)\nGraphics card: AMD\n\nBroken: 3.5.1\n\nSculpting the curves is not possible when hiding the parent and \"occluding\" the curves with the now invisible parent.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nAdd empty hair to the cube.\nAdd curves in sculpt mode.\nHide the cube.\nTry to sculpt the curves from the other side of the cube. \nDragging from inside the hidden cube and dragging from outside the hidden cube give different results, when it feels like it should not.\n\n", "Linked group breaks Object Mapping in Texture Coordinates\nWindows 10\n\nBroken: 2.79b official release\n\nLinked group breaks Object Mapping in Texture Coordinates, when:\n- a texture (on a plane) uses another object (empty) as texture coordinates\n- all objects are in the same group\n\nFurther explanation in the blend file.\n\n1) Link the group \"object_mapping\" from the blend file\n2) move the group in any direction\nDespite the gradient texture on the plane using the empty's coordinates, this is completely ignored once linked as a group\n[object_mapping.blend](object_mapping.blend)", "Broken curve drawing in normalized view in graph editor\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.1\nWorked: ?\n\nin the normalized mapping in the graph editor, the curve behaves strangely. In the normal display, everything is fine\n[2022-04-20 22-13-05.mp4](2022-04-20_22-13-05.mp4)\n\n- Open attached .blend file\n- In graphics editor pan view up and down\nDisable Normalized to hide the problem\n[bandit_anim.blend](bandit_anim.blend)", "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", "“Surface Deform”-modifier is overwriting the whole modifier stack\nOperating system and graphics card\nFedora 27 / GeForce GT 740\n(OS-independent issue)\n\n2.79a - offical release - 8928d99270f\n\nUnlike the “Mesh Deform”-modifier, which is applying the changes in a relative fashion, the “Surface Deform”-modifier just overwrites the previous modifier/s with the absolute values of the transform.\n\n[bug_report_surface_deform_modifier.blend](bug_report_surface_deform_modifier.blend)\n\nPlease look into the attached blend-file to follow the examples:\n\nExample1: adding two times the same “Surface Deform”-modifier on top of each other yields the same result as just one or in fact any number of copies of this modifier, thus rendering the nature of the modifier-stack here somewhat useless. In contrast e.g. the “Mesh Deform”-modifier would apply each copy of itself as a relative transform, thus building upon the previous modifiers in stack and changing the output-mesh with every copy of itself.\n\nExample2: Using the “Multi Modifier”-option of the “Armature”-modifier usually takes the same data as the previous modifier as input. The results of the previous modifier and the “Armature”-modifiers are then mixed together, using the weights of the Vertex Group as “mixing guides”. But in the case of the “Surface Deform”-modifier being the previous modifier this seems not to apply and the “Multi Modifier”-option takes no effect at all.\n\nExample3: Adding the “Surface Deform”-modifier on top of “Armature”-modifier overwrites the effect of the “Armature”-modifier (and all other modifiers prior to the “Surface Deform”-modifier.\n\n( An additional oddity seems to me that there is no option to control the overall influence of the “Surface Deform”-modifier with a vertex group, as is usually the case with all other deform modifiers. This though is not part of the bug report and rather a small feature request – but if someone is already looking into the above issue, I figured it wouldn't hurt to mention it here as it is probably just a matter of copy and paste from any modifier that already has this implemented - I might be wrong here though of course - please forgive my ignorance.)\n\nThank you for taking your time to look into that issue.\n\n\n", "Uncontrolled vertex movement in symmetric editing\nOperating system: Windows 7\nGraphics card: AMD Radeeon `R9` 200 Series\n\nBroken: version: 2.82 (sub 7), type: Release; build date: 2020-02-13, 01:56:46\nWorked: (optional)\n\nWhen symmetrical editing about the X axis with proportional editing of an almost symmetric object, model changes are detected in places where editing was not performed. \n\nMoreover, these changes occur asymmetrically. For example, in a key with a changed shape of the legs of a human model, a significant asymmetric change in the neck region with a shift of the line of symmetry itself was found. So it is with most other shape keys. Thus, the symmetry of the entire model is violated, which entails other undesirable consequences. These problems cannot be solved programmatically or manually, and the data on the coordinates of the vertices strangely diverge from the observed form.\n\n[#74340.blend](T74340.blend)\n\n- Open file\n- Move selected vertex\n# vertices in unconnected mesh on mirror side will move\n\nModel Genesis 8 exported from DAZ Studio in Base Resolution .obj file and imported to Blender.\nHMiU6BYcl2E\n", "Curve Deform Node\nNOTE: The design below is outdated. A curve deform node should be a field node now, with a vector input and output, and a curve input. Arguably it should just be a node group too.\n\n\n| {[F10152887](image.png) size=full}| {[F10152878](image.png) size=full} | {[F10152882](image.png) size=full} |\n| -- | -- | -- |\n\n\nThis is task is for a port of the \"Curve\" modifier to a node.\n{[F10150643](image.png), size=50%}\n\n\n**Details**\n* Any geometry component with a position attribute is supported by this node.\n* Only the first spline of the curve is used for deformation.\n* Two input modes modes are available. \n**The position mode uses point positions for the curve parameters.*** The position input is provided for convenience. In most common cases, a single axis of the position is used as a parameter for the curve.\n***The position is mapped to the curve based on length. So \"x=5m\" means, transform by traveling 5m along the spline. This is how the modifier works.** The attribute input mode uses any float attribute between zero and one, as a factor along the length of the curve.\n** For convenience, a \"Float\" option is available for the attribute when the whole geometry should have the same parameter.\n* Extrapolation should be handled by a separate node that can extrapolate a spline.\n \n\n**Further Questions**\n* Is an \"influence\" attribute input really necessary? The same thing could be achieved by mixing a copied position attribute before starting the operation.\n** The answer to this question will apply to other operations as well.\n* Which of the three \"Curve Deform\" settings are necessary in this node? \"Use Radius\" is likely not necessary, the attribute could just be filled beforehand.\n\n**Related Nodes**\n* A \"Curve Sample\" node could do a similar operation, but instead of deforming positions, it would sample an attribute along the length of a curve based on the same mapping controls.\n** This could be useful to have more flexible control of attributes with curves.\n\n\n**Implementation**\nThe implementation should be straightforward. Sampling arbitrary points along the curve is an natural extension of the uniform sampling that is already implemented.\nCurve parameters should be sorted before, and then changed into evaluated point indices and factors.\nThen, interpolation between the transform of neighboring evaluated points should be quite simple.\n", "F-curve editor displays incorrect curve for reversed NLA strips\n**Operating System, Graphics card**\nLinux SuSE 12.2 (x86_64)\nNVidia GTX560ti (official driver)\n\n**Blender version with error, and version that worked**\nBroken: 2.67b - 2.91 and recent buildbot binaries\n\nReversing a strip in the NLA editor makes the f-curve editor display animation curves incorrectly. This is only a UI/display issue - object will still animate as expected.\n\n**Steps for others to reproduce the error (preferably based on attached .blend file)**\n- add a couple of keyframes to an object and switch to NLA\n- turn action into action strip (snowflake icon)\n- in the strip properties, enable 'Reversed'\n- go into edit/tweak mode for the strip then switch to f-curve editor\n- animation curves are drawn incorrectly\n\n[#35708-nla-reverse-display-issue.blend](T35708-nla-reverse-display-issue.blend)\n\nNormal:\n\n\nReversed:\n\n\n" ]

[ "Modifiers which deform spline points propagate across all users of the same data unexpectedly\nVersion: 2.81 build Oct 23 (Linux 64)\n\nWhen a Curve Object Modifier uses the \"Apply On Spline\" setting, it seems to affect the curve data directly. This means that if a curve data block is used by multiple objects, a modifier on one of those objects will affect all the others.\n\n[curve_modifier_bug.blend](curve_modifier_bug.blend)\n\nTo reproduce, open and inspect the attached file. Notice that the objects on the left both have deformation modifiers, while their clones on the right do not. However, the curve object still appears to be modified because it uses the same data as the modified curve object. This is not how modifiers are supposed to behave. \n\nThe expected behavior is demonstrated by the two mesh objects. Like the curve objects, they also share the same data, but the effect of the modifier is limited to the owner of the modifier.", "Link-duplicated curves acting weird if a Hook modifier is attached\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.82 (sub 7)\n\nLink-duplicated Curves (alt-D) are somehow creating dependencies to the original Curve if a Hook modifier is attached to the original. It seems the Duplicates mirror the original Curve along with the Hook dependency, regardless if they have a Hook modifier on their own.\nI also had trouble to assign a new Hook modifier on one of these copied Curves. They are not responding at all, even if no other Hook modifier is attached in the scene.\n\n\n[LinkedCurveHookModifierBug.blend](LinkedCurveHookModifierBug.blend)\n\n" ]

[ "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "simulation in new scene causes crash in original scene's simulation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\n**steps**\n- make cube an active rigid body. \n- play simulation\n- then click on new scene button and on full copy.\n- in the new scene, rewind playhead to frame 0\n- run the simulation.\nBlender should crash.\n\nThere are more ways to cause crash when full scene copy is done (see comments), but I guess these will stem from single issue.", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "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 randomly causes system to crash when rendering\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory)\nCPU: Intel Core i9 9900k\nRAM: 32GB DDR4\n\nBroken: 3.0.0\n\n\nI'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know.\n\nI have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash.\nThe amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory.\n\nI'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine.\n[ocean_final.blend](ocean_final.blend)\nThe scene makes use of a lot of volumetric light and I also calculate the bloom.\n\nThere aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here.\n\nAll drivers are up to date and I also reinstalled Blender.\n\nNot sure, but I attached the .blend file as well as logs created in debug mode.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "Blender 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)", "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", "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", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Pack UV's crashes blender\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\n\n", "Excessive Memory Usage and crash in Material Properties\nOperating system: Windows 10\nGraphics card: NVidia RTX 2060 Studio Drivers \n\nTested latest lts, latest stable, and latest daily, same result.\n\n**Description**\nI am using the UDIMS texture system for the model I am currently working on. During the rendering process, I have not encountered any issues, using approximately 20GBs of RAM. However when entering the \"Material Properties\" tab, Blender's memory usage increases. If I remove and readd a material, Blender recalculates all the materials in the scene, and the memory usage increases until my PC runs out of memory and Blender crashes. The memory usage grows this much since I have two UDIMS spaces assigned for the \"Base color,\" \"Roughness,\" and \"Normal Map\" textures, at a 4K resolution. I could understand that the size of my project or the textures are too big for my computer, but it renders without issues.\n\nThe only temporary solution I have found is to disable the image nodes in the \"Body\" material, which uses 8K images. I am unsure if this is due to an error on my part or if there is an option available to bypass this pre-calculation during work or while in the viewport.\n\n\nIf asked, I can upload a .blend file and all the necessary additional files, so you can observe the error, but it is too large to upload here.\n\nThank you very much for your attention.\n\n", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Set as Background crashes blender instantly.\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080 Ti and RTX 3060\n\nBroken: 3.62\n\nI'm trying to do object tracking. Have tracked an object and clicked Solve Object Motion, then when I click on Set as Background Blender crashes instantly. Trying to load in a 400 frame 1920x1080 png sequence. Blender also crashes if I try to load the background image sequence via the camera properties (Background Images > Add Image).\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Solid mode in EEVEE looks pixelated (NEW)/ CYCLES in GPU 3D AMD driver problem (OLD KNOWN Problem)\n**Xeon E3 1230 V2 - 16Gb RAM**\nOperating system: Windows 10\nGraphics card: AMD RX 570 8Gb VRAM\n\n**Blender Version 2.92.0**\n\n\nI opened an old work of mine that I was mading on same 2.92.0 before. Today when I opened the solid mode as default and appears very pixelated and like matrix effect, as AMD error was giving in Cycles before... \nMaybe is AMD driver problem or materials render data. \nSome months ago was Cycles incompatibility. Cycles is still working only on CPU and now Eevee have problems in solid mode. \nI've tested in 2.83.5 version and worked. \n\n\nattached photos. In 2.92.0 isn't \n\n**Work in a project\nfews days later (about 20 days) open the archive and solid mode was pixelated  \n\n[estilizada unir cabeca retopo.blend](estilizada_unir_cabeca_retopo.blend)\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Crash as soon as press material button in properties panel\nWindows 10 64 bits - Compiled source with last version at 20/06/2018 16:00 using MSVSC 2017 Debug mode\n\nTo reproduce:\n\n1) blender --factory-startup\n2) Select material icon in properties panel\n3) Crash\n\nLog details: [P733](P733.txt)\n\nDoing some debug, the function GPU_texture_bind() is failing because text field is NULL.\n\nThe line with error is this:\n\n```\nif (tex->bindcode != 0)\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", "Shading or Lighting Discrepancy issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nSo I’ve been having this problem since working in 2.8 and I don’t have a clue what could be causing this issue but I went and stripped down a project as simple as possible trying to isolate the root cause. It seems its a mesh that has an emissive material and when I disconnect the node or hide the mesh the problem disappears. Weird thing is that the brighter version is when hiding mesh number 2. I am attaching the file.\n\nYou will see how the tone changes. This never happened to me after so many years using Blender until now already in a few projects in 2.8. \n\n- Open attached file.\n- Render once using slot 1.\n- Hide mesh 2 or disconnect the emissive node.\n- Render again using slot 2.\n# Toggle with J\n\nNotice the different lighting between each result.\n\n[Shading Issue - Simplied.blend](Shading_Issue_-_Simplied.blend)", "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", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "clay strip brush (and probably any brush) create some strange shading and geometry artifacts...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\n\nclay strip brush (and probably any brush) create some strange shading and geometry artifacts...\n\n1. open blender, subdivide the default cube in edit mode a few times,\n2. add subdiv modifier with 3 levels (25,1 million in total) and apply modifier.\n3. go to sculpt mode and start playing with the clay strip brush and brush settings a little bit...\n4. change the sculpt plane to view plane, and add a stroke continuously in the edge of the cube, and some transparent shading bug appears when i go to check the back side of the stroke made, but this get fixed when i use the smooth brush a little bit in those boundary edges...\n\n\n5. change the sculpt plane to area plane again, and try on other edge the same again, and some grid topology starts to appear suddenly in the first stroke when drawing, but when i keep drawing it was less noticeable the artifact but was still there...\n\n\n\n", "Edge-slide seems to highlight an edge now (visually noisy and inconsistent)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\nWorked: not sure, maybe early july?\n\nEdge-slide seems to highlight a split edge now which seems a bit visually noisy and inconsistent. It's visually noisy since it's not adding much for the user (it's not an indication of snapping target for instance) and represents another visual color change that distracts the user from the primary operation. Inconsistent because it's based on the location of your mouse when invoking the operation which leads to really weird cases like the following.\n\nA hidden edge being highlighted on this cube:\n\n\nOr different edges depending on slight differences in mouse position between edge-slide attepts:\n\n\n\n\n\n- Go into edit mode on default cube in default scene\n- Add an edge loop and attempt to slide it\n\n", "PBVH Pixels should check on center uv coordinate.\nCurrently it checks on bottom left corner, but the painting is half a pixel shifted. By adding an offset of half a pixel this should reduce some artifacts.", "Eevee viewport soft shadows are broken on higher sample count\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: ---\n\nEevee soft shadows in viewport have color spills. But it works fine on final render (F12)\n\n\n\n- Open .blend file\n\n[bug_soft_shadows.blend](bug_soft_shadows.blend)\n\n- Switch to Rendered Mode of Viewport Shading\n- Wait half a min and see the problem(", "Wire objects that are being displayed on front only updates visibility after interaction\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nThis problem is similar to the one found in #84717, but in this case it is only affecting objects that are marked as in front and wired mode. I noticed it happening in a rig, but It can be applied at anything that is wire.\n\n\n- Using Any object go to viewport display and mark in front and set it to wire in the display as. (you can also use a rig with custom shapes, e.g. the one in rigify.)\n```\n{F12895660}\n```\n- Disable and then Enable Overlays\n[2022-03-03 11-21-26.mp4](2022-03-03_11-21-26.mp4)", "VSE: In Multicam all strips gets white outline\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nAll channels/strips get a white active strip outline when a multicam strip is selected. \n\nOpen this .blend file:\n[VSE_MultiCam.blend](VSE_MultiCam.blend)\n\nNotice that all previews have a white active strip outline, though it's only the multicam strip selected:\n{[F10961426](image.png),size=full}\n\n", "Same pattern looks different for Cycles and Eevee\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.1\n\nThis is the difference\n\n\n\n\nsimplified file\n[pixels tiled1.blend](pixels_tiled1.blend)\n\n\nold file \n[pixels tiled.blend](pixels_tiled.blend)\n\nI suppose the difference in Color Ramp or Noise node.\n", "Rounding error in ColorRamp node\nOperating system: Windows 10\nGraphics card: GeForce GTX 1080 8K\n\nBroken: 2.83.4, a322b43e3d08, 2020-02-24\n\nIn the Cycles implementation of the ColorRamp node, marker positions seem to be rounded to the next higher multiple of 1/255, leading to unexpected output, especially when set to 'Constant' interpolation.\n\nEDIT: Happens in EEVEE too, but only when there are two or more markers set on the ColorRamp, and with multiples of 1/256.\n\n\n[rounding error.blend](rounding_error.blend)\n\n - Open the attached .blend file and switch the 3D View to Rendered mode\n - See ColorRamp node in the Shader Editor\n - Set yellow marker to a position just slightly above a multiple of 1/255, e.g. `0.2197` (> 56/255)\n - Set 'Fac' input to just slightly below the next higher multiple, e.g. `0.2235` (< 57/255)\n # The node will output the red color from the left of the spectrum, even though the input value is greater than the yellow marker's position. ~~This only occurs in Cycles, EEVEE correctly outputs yellow.~~\n\nAs a side note, 0.2335 should be rounded up to 0.234 when displayed with three decimals, but isn't.\n\nEDIT: To reproduce in EEVEE:\n\n - Steps 1 & 2 from above\n - Add a third marker to the ColorRamp and slide it to 1.0, where it shouldn't affect the other markers\n - Set yellow marker to a position just slightly above a multiple of 1/256, e.g. `0.5001`\n - Set 'Fac' input to just slightly below the next higher multiple, e.g. `0.5039`\n # (As with Cycles)\n\n", "Eevee: Soft shadows causing flickering in animation and temporal AA in scenes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.80\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nEevee soft shadows in objects with thin reflections causes flickering in animation and temporal AA in still images. This type reflections common in interior Arch Viz.\n\nScene 1 example of flickering of soft shadows in animation. I have remove all light probes and effects to focus only light and shadows. Open attach file \"Scene1_AA_eevee.blend\".\nRender the animation with Soft Shadows ON. Then Render animation with Soft Shadows OFF.\n[Scene1_AA_eevee.blend](Scene1_AA_eevee.blend)\n\nAnimation with Soft Shadows ON. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_eevee.mp4](Scene1_AA_eevee.mp4)\n\nAnimation with Soft Shadows OFF. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_No_SShadow_eevee.mp4](Scene1_AA_No_SShadow_eevee.mp4)\n\nAnimation in Cycles for comparison. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_cycles.mp4](Scene1_AA_cycles.mp4)\n\n******************************************************************************************************\nScene 2 example of temporal anti-aliasing cause by soft shadows. I have simplify the scene 2 to focus only light and shadows. Open attach file \"Scene2_AA_eevee.blend\".\nRender Image with Soft Shadows ON. Then Render Image with Soft Shadows OFF.\n[Scene2_AA_eevee.blend](Scene2_AA_eevee.blend)\n\nRender image with Soft Shadows ON. Make sure to view at full size. Notice the temporal AA on the edges on horizontal counter, vertical counter, oven handle and oven racks.\n\n\nRender image with Soft Shadows OFF. Make sure to view at full size. Notice the temporal AA is gone.\n\n\nRender image with Cycles for comparison. Make sure to view at full size.\n\n\n", "HDRI Preview Spheres appear in surface reflections\n\n\nBroken: version: 2.82 (sub 7)\nMaster\n\nWhen using material shading and overlays in the viewport, the gizmo at the bottom-left corner (sphere displaying the environment map used for preview) is reflected by shiny surfaces in the 3D world, despite technically being a part of the UI. Using the icon to show / hide overlays affects this, the reflection also disappears when overlays are hidden.\n\nShould work in any setup, if there are issues replicating this let me know and I'll extract the relevant part from my project's blend file. Just add a plane, lower its material roughness so it's shiny, move the view upward so the overlays appear under it, and you should see the strange reflection.\n\n\n\n[HDRI_reflected_in_viewport.blend](HDRI_reflected_in_viewport.blend)", "GPencil – Unwanted Dots In Strokes\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\n\nWhen rendering thick lines the lines will have some unwanted transparent dots. Especially if you turn the percentage of the render resolution up to 200%. Take a look at the attached images (in full size) wehre I marked the dots with red circles:\n\n**100% of the standard render resolution** (less unwanted dots)\n\n\n\n**200% of the standard render resolution** (more unwanted dots)\n\n\n\nThis issue might occur on NVIDIA graphics cards only ([see comment from](T80906#1020570) @JSM).\n\n\n[GPencil_Unwanted_Dots_r0.blend](GPencil_Unwanted_Dots_r0.blend)\n\n\nRender the attached .blend file, or:\n\n1. Open Blender and select *2D Animation* on the *Splash Screen*\n2. Draw some thick lines\n3. Turn the percentage of the standard render resolution up to 200%\n4. Render the image and inspect the lines\n\n\n––––––––––––––––––––--\n\nHave fun in the sun! 😁" ]

[ "Eevee: Specular Light: The sepecular light contribution should be limited to samples with a normal pointing toward the camera\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\nEevee produces render artifacts on the specular light contribution when the normal vector points away from the camera (for example because of active smooth shading). This can be seen as bright (wrong) reflections near the visibility boundary of the geometry. Cycles does not produce these artifacts, there seems to be no specular light contribution on normals facing away from the camera.\n\nEevee (wrong specular reflection on the left): \n\nCycles (correct specular reflections): \n\nLoad the attached .blend file and render the image with Eeevee (and to compare) with Cycles. To better understand the problem a dark red color has been added (as Emission) to the parts of the geometry with normals pointing away from the camera, and dark green for parts with normals pointing towards the camera. The specular reflections are white. The .blend file also contains a node group \"View Clamped Normal\" that allows to \"correct\" the normals (by changing them so they are not pointing away from the camera). This can be connected to the \"Normal\" input of the BSDF to hide the problem, as a workaround.\n\n[eevee-specular.blend](eevee-specular.blend)\n\n**Suggested fix**\nAttached is a patch file for a suggested fix in blender/draw/engines/eevee/shaders/lights_lib.glsl by adding the check if dot(N, V) > 0.0 before calculating the specular contribution and returning 0.0 otherwise. \n\n[0001-Correct-the-specular-light-contribution.patch](0001-Correct-the-specular-light-contribution.patch)\n\nEevee (with the attached patch applied) \n\n\n" ]

[ "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)", "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", "Render animation cycles-x bug March 11, 2022\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nRender count from 1 to 1200 frames\n\n\nBlender 3.2.0 Alpha within Cycles-x\nPush the 'Command + F12\" and render animation cause bug between start to end (855 - 1200 frames)\n\nBlender and video file: [Blender 3-2-0 by Kent Davis March 11 2022.zip](Blender_3-2-0_by_Kent_Davis_March_11_2022.zip)\n\n\n\n\n\n\n\nRadeon Pro 575:\n\n```\nChipset Model:\tRadeon Pro 575\nType:\tGPU\nBus:\tPCIe\nPCIe Lane Width:\tx16\nVRAM (Total):\t4 GB\nVendor:\tAMD (0x1002)\nDevice ID:\t0x67df\nRevision ID:\t0x00c4\nROM Revision:\t113-D000AA-931\nVBIOS Version:\t113-D0001A1P-025\nEFI Driver Version:\t01.00.931\nMetal Family:\tSupported, Metal GPUFamily macOS 2\nDisplays:\n```\niMac:\n```\nDisplay Type:\tBuilt-In Retina LCD\nResolution:\tRetina 5K (5120 x 2880)\nFramebuffer Depth:\t30-Bit Color (ARGB2101010)\nMain Display:\tYes\nMirror:\tOff\nOnline:\tYes\nAutomatically Adjust Brightness:\tNo\nConnection Type:\tInternal\n```\n\n", "(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", "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", "Shader node connections in v3.0 file broken in v3.3\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.3.0\nWorked: 3.0\n\nRendering in 3.3 a file created in 3.0 (using both Cycles & Eevee) showed major differences from rendering made in 3.0. Investigation showed that critical node connections in multiple shader trees were broken when opening file in 3.3. Unable to determine if broken connections are consistent in terms of node type. Which nodes have broken connections seems consistent from file to file using the same shaders -- sample .blend was constructed with shaders used in file where bug was first observed. All shaders were originally created in versions prior to 3.0 but later than 2.80.\n\nAttached GIMP .xcf file has exemplary renderings and explanatory screenshots from file where bug was first identified. Sample .blend file was created in v3.0 using shaders from this file. Bug does occur in other files which render fine in 3.0 but have broken shaders in 3.3\n\n\n[REVISED sample file 300.blend](REVISED_sample_file_300.blend)\n\nOpen \"sample file 300.blend\" in v3.0 and inspect shader trees. Open in 3.3 and inspect shader trees, some nodes of which are now disconnected. \n\n\n", "Blender editing performance with many datablocks\n**Status:** 1st milestone almost complete, need final optimizations.\n\n---\n**Team**\n**Commissioner:** @brecht \n**Project leader:** @mont29\n**Project members:** @ZedDB \n**Big picture:** In heavy scenes, new features in Blender 2.8x are making the inherently linear (`O(N)`), when not quadratic (`O(N²)`), complexity of most operations over data-blocks more problematic than in 2.7x era. The general goal is to bring those operations back to a constant (`O(1)`) or logarithmic (`O(log(N))`) complexity.\n\n**Description**\n**Use cases:**\n*Need specific test cases.*\n* Undo changes in object mode in a heavy scene.\n* Undo changes in pose mode in a heavy scene.\n* Duplicating objects in a heavy scene.\n* Adding many objects in a scene.\n\n*Note:* There are two types of “heavyness” in scenes (that can be combined of course):\n * Scenes that have many objects and/or collections.\n * Scenes that have very heavy geometry, either in the geometry data itself, or generated from modifiers like subdivision surface.\n\n**Design:**\n # Dependency graph should not have to re-evaluate objects that did not change.\n ** This is mainly a problem currently during global undo, as all data-blocks are replaced by new ones on each undo step.\n # Handling naming of data-blocks should be `O(log(N))` (it is currently close to `O(N²)`, or `O(N log(N))` in best cases).\n **This will require caching currently used names.*** We will probably also have to handle smartly the numbering in that cache, if we really want to be efficient in typical “worst case” scenarii (addition of thousands of objects with same base name e.g.).\n - Caches/runtime data helpers should be always either:\n - Lazily-built/updated on-demand (code affecting related data should only ensure that the 'dirty' flag is set then).\n *** This approach can usually be easily managed in a mostly lock-less way in a threaded context (proper locking is only needed when actually rebuilding a dirty cache).\n ## Kept valid/in sync all the time (code affecting related data should take care of updating it itself, code using the cache can always assume it is valid and up-to-date).\n ***Such cache should be easy to incrementally update (it should almost never have to be rebuilt from scratch).****This implies that the cache is highly local (changes on a data-block only ever affect that data-block and a well-defined, easy to reach small number of “neighbors”).*** In general keeping this kind of cache valid will always be harder and more error-prone than approach #A.\n *** This approach often needs proper complete locking (mutexes & co) in a threaded context.\n \n *Note: The ViewLayer's collections/objects cache e.g. currently uses the worst mix of #A and #B - it is always assumed valid, but updating it requires a complete rebuild from scratch almost all the time.*\n\n *Note: Approach #B is usually interesting only if a complete rebuild of the cache is **very** costly, and/or if the cache is invalidated very often while being used.*\n\n**Engineer plan:** `-`\n\n**Work plan**\n\n**Milestone 1 - Optimized per-datablock global undo**\nTime estimate: `6 months`\n\n* Re-use as much as possible existing data, and try to swap newly read (modified) data to the original memory, during 'memfile' undo step. Updating the depsgraph should then be much less work.\n** #60695 (Optimized per-datablock global undo)\n** [D6580: WIP/Demonstration patch about undo speedup project.](D6580)\n\n**Milestone 2 - Lazy collection synchronizations**\nTime estimate: `1 month`\n* Fix view layer collection syncing (to not require looping over all objects, or to be ran much less often...).\n** #73411 (Fix ViewLayers cache building)\n\n**Milestone 3 - Data-blocks management performances with many of them**\nTime estimate: `5 months`\n\n# Investigate how to best handle naming conflicts issues.\n**Most obvious idea would be store all used base-names in a GHash (one per ID type), along with used indices. Needs further design though.** #73412 (Improve name conflict handling in ID management)\n# Investigate the best way to cache bi-directional relationships info between data-blocks.\n**We already have a start of this with `BKE_main_relations_create()` & co, but it is heavily under-used and needs better design to be usable more widely.** #73413 (Cache data-block relationships info )\n# Fix/Improve handling of the Bone pointers (which are sub-data of `Armature` ID) stored in poses (which are sub-data of `Object` ID).\n**Ideally such horrible pointers should not exist ever. They are a very solid recurrent source of bugs in Blender.** Not sure how to best deal with them, at the very least we could add some generic ID API to ensure those kind of caches are up-to-date?\n\n\nSee also #68938 (Blender editing performance with many datablocks).\n\n**Later**\n\n* Dependency graph rebuild to be `O(1)` or `O(log(N))` (it is also `O(N)` at the moment). *???? would assume linear would already be nice performance for such a code?*\n\n**Notes:** -\n\n---\n", "GPU Subdivision not optimized in Weight Paint mode\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\nI'm not sure if it's unimplemented/unplanned or just overlooked, so I'm here to report in case.\nWhen you have a mesh using an Armature modifier and Subdivision modifier, the Subdivision will affect performance while posing the armature but enabling GPU Subdivision will noticeably improve performance during posing and animation. \n\nHowever, if you select the armature and the mesh and go into weight paint mode, allowing you to pose the rig, the GPU Subdivision will not boost performance with the Subdivision modifier. Weight Paint Pose is slower regardless as to the Subdivision modifier, just GPU Subdivision seems to be disabled here. \n\n- Open attached .blend file\n- Make sure `GPU Subdivision` is enabled in Preferences\n- in Weight Paint Mode, pose the rig (move any bone)\n- Go to object mode, select the rig and go to Pose mode\n- Compare performance when posing the rig\n\n[#101485.blend](T101485.blend)\n", "\"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", "Cycles GPU/CPU render difference with more than 64 transparent bounces and coplanar faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\n\n\nWhen using particle plane with transparency ( to fake volume scatter ), we have a color mismatch between CPU and GPU rendering. \n\n\n see attach file\n\n\n\n[cpu_gpu_issue.blend](cpu_gpu_issue.blend)\n \n", "EEVEE Material Preview works significantly slower than before. \nOperating system: MacOS Mojave 10.14.6 (18G9323)\nGraphics card: Intel Iris Graphics 550 1536 MB\nMemory: 16 GB 2133 MHz LPDDR3\nProcessor: 3,3 GHz Intel Core i7\n\nBroken: (example: 3.0.1, 2.93.8 edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: 2.83.19 \n\nSwitching to \"Material Preview\" view mode (or Rendered) and any manipulation of a material (like adding new node) takes significantly longer than in previous version. \n\n1. Open attached file\n2. Click \"Material Preview\" view mode\n3. Wait until material is fully visible in the viewport\n\nI know my machine is not a great performance beast and my OS is pretty outdated (but I can't upgrade because of other apps that I use), but you can clearly tell that 3.0.1 works much slower. I tried also 2.93.8 version (LTS tab on blender.org) and the result is the same. Only 2.83.19 worked faster. I attached a video, it's realtime screen recording (the only editing within the video is blurring the mess on my desktop). Also you can find a blend file that was use to perform the test. [performance-test.blend](performance-test.blend)\n\n[blender_performance.mp4](blender_performance.mp4)", "Cycles GPU CUDA rendering high number of points seems broken in LTS (main is fine, request for backport)\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.3.3\nWorked: latest 3.5 alpha\n\nRendering point \"clouds\" with Cycles - CUDA seems to make some chunks of points disapear randomly\nThis looks like this has been fixed in 3.5, but i didn't find when. Can this be fix in LTS ?\n\nDelete the default cube and add a plane\nAdd a Geonode Modifier on that plane\nDistribute Points on Faces > Density : 250'000\nSet Point Radius > 0.0025 (for convenience)\n \nSwitch to Cycles, GPU\nSwitch the render device to CUDA\n\nResults with :\n\n|  CPU |  CUDA |  OPTIX\n| -- | -- | -- |\n\n\n\nBug is visible in both viewport shading and Render.\n\n", "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.", "PBVH task scheduler performance issues\nThis is a task to investigate a possible issue in the PBVH task scheduler. \n\n**Issues**\n - Some users report bad performance in sculpt mode, while others can work without problems on really high poly meshes with similar hardware.\n\n - On my main computer, brush strokes with TBB disabled feel more responsive regardless the mesh vertex count. When TBB is enabled, strokes usually stop generating new samples in the middle of the stroke or take a fraction of a second to start. I know this is happening to some other users. \n\n - Simple operations that need to loop over all vertices on high poly meshes are extremely slow for no specific reason. (doing x = 1.0f - x on a 25M elements array often takes up to 5 seconds). When the operation is more complex (like updating the normals or updating the nodes on the GPU), this can take minutes to finish. \n\nWe are not getting the reports of people that may be affected by this issue because most of them assume that Blender sculpt mode performance is just bad by default, so I can't tell if this is a problem with a specific configuration of hardware/software or a general problem in how the scheduler works. It would be nice to have more data from this test (and sculpt mode performance in general) on different hardware/software configurations to have a better understanding of how we can improve it. \n\n**How to test:**\n\n - Apply this patch: [P1202](P1202.txt)\n - Add a cube, subdivide N number of times and apply\n - Enter Sculpt Mode\n - Run \"Invert Mask\" (press A + drag left)\n\n\n**My results**\n\nOperating system: Linux-5.4.2-1-MANJARO-x86_64-with-glibc2.29 64 Bits\nCPU: Intel i7 6700K @ 4.00GHz x 8\nRAM: 32GB\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nSubdivide default cube N number of times:\n\n| N Subdivisions | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|--------------|----------|------------|------------------|-------------------|---------|\n| 11 | 25165826 | 7596 | 2.474073 | 0.571511 | 432.90% |\n| 10 | 6291458 | 1920 | 0.307948 | 0.159395 | 193.20% |\n| 9 | 1572866 | 464 | 0.111459 | 0.096845 | 115.09% |\n| 8 | 393216 | 112 | 0.002289 | 0.007297 | 31.37% |\n\n\nSubdivide default cube 6 times, use multires to N level.\n\n| Level | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|-------|----------|------------|------------------|-------------------|---------|\n| 6 | 26763264 | 3696 | 1.076635 | 0.322183 | 334.17% |\n| 5 | 7102464 | 912 | 0.074586 | 0.113303 | 65.83% |\n| 4 | 1990656 | 232 | 0.012938 | 0.048273 | 26.80% |\n| 3 | 614400 | 56 | 0.004059 | 0.012778 | 31.77% |\n\n\nAs you can see, a simple loop over all vertices in the mesh is way faster on my setup with TBB disabled.\n\nIf I change the ##LEAF_LIMIT## in ##pbvh.c## to 100000 (x10) in order to increase the amount of work each node has and reduce the number of total nodes: \n\n| N Subdivisions | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|--------------|----------|------------|------------------|-------------------|--------|\n| 11 | 25165826 | 760 | 0.106868 | 0.210985 | 50.65% |\n| 10 | 6291458 | 184 | 0.029088 | 0.105376 | 27.60% |\n| 9 | 1572866 | 56 | 0.007168 | 0.029653 | 24.17% |\n| 8 | 393216 | 8 | 0.002261 | 0.006321 | 35.77% |\n\nIf we compare the two results with TBB on:\n\n| Vertices | 1000 LEAF_LIMIT (default) | 10000 LEAF_LIMIT (new) | Perf. gain |\n|----------|-----------------|------------------|------------|\n| 25165826 | 2.474073 | 0.106868 | 2315.07% |\n| 6291458 | 0.307948 | 0.029088 | 1058.68% |\n| 1572866 | 0.111459 | 0.007168 | 1554.95% |\n| 393216 | 0.002289 | 0.002261 | 101.24% |\n\nIt seems like if we avoid starting TBB with a large number of nodes the performance improvement is huge. Increasing the leaf limit makes these kinds of operations up to 23 times faster, but that would be like disabling multithreading for small brush strokes.\n\n- Is there a way to fix this in the scheduler?\n- Can we do something like sending small chunks of nodes to TBB instead of starting the loop with 7000 nodes at the same time?\n- Can we find a better optimal leaf limit to get a better workload per core suitable for modern processors by comparing the results on different hardware? Dyntopo leaf limit is in 100 elements, which I think it does not make much sense. ", "Viewport performance slows down when using OptiX Denoiser on Windows machine with dual GPUs.\nOperating system: \nWindows 11 (Windows 10 has the same bug)\nGraphics card: \n2x Geforce RTX 3090\nGraphics driver\nNvidia Driver 511.65 / 511.79 / 472.12 ...\n\nBroken: \nBlender 3.10 05697470abd0d / All versions of 3.1, 3.0 and 3.2 are the same.\n\nWorked: \nBlender 2.90\n\nViewport render slows down when using the OptiX viewport denoiser with two GPUs enabled using OptiX.\nIf you check only one GPU, it will work at a normal speed.\n\nAs far as I know, it is a bug in Windows 10 and Windows 11, probably it works normally in Linux.\n\n1. Run Blender on Windows.\n2. Check the two GPUs on OptiX in Preferences.\n3. Turn on Viewport Denoiser (OptiX)\n4. Rotate the basic cube. It's slowly rendered.\n5. Uncheck one GPU. It works fast normally.\n\n[1.mp4](1.mp4)" ]

[ "blender3.3 HIP performance down 30% on Windows\nOperating system:windows10 21h2\nGraphics card:rx6800xt\n\n**Blender Version**：3.3 Long-term support version\nBroken: Version ：3.2 has no problems\nWorked: no\n**Short description of error**3.2\n3.2 version of the classroom scene only needs 32s, 3.3lts need 44s\nStandard classroom, no need for me to provide it.\n\n\n" ]

[ "\"Shape Key Edit Mode\" toggle for correct mesh deformations\nWhen using the toggle \"Shape Key Edit Mode\" it gives me a representation of all shapekeys mixed together but it's only a visual preview. \n\n\n\nIt doesn't affect the result of rotating or scaling the mesh since you still only work on the shapekey that is selected instead of the mixed representation that is shown. \nAnd since it's all just based on vertex location the results can be pretty odd, especially when using the 3D cursor as a pivot point. \n\n[2019-07-15 11-23-25.mp4](2019-07-15_11-23-25.mp4)\n\nSince working with multiple shapekeys is a great way to work non-destructively it would be a big improvement if the mixed shapekey representation would also be used for any deformations made.\nThis could be by default or as an additional toggle.", "Select next active fails in some cases (default cylinder, cube)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro K2100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 3.1.2\n\nWhen adding object: circle or cylinder, when selecting vertices, it does not select the next vertex at command: shif + ctrl + (+).\nif I select several vertices manually and give the command: shift + ctrl + (-) deselect, it works perfectly.\n\nany other option works, works well with other objects, sphere, monkey sesame, the circle object works if you select two consecutive vertices, if you select one vertex yes one no, it no longer works. .]\n\n- add cylinder object\n- Edit mode\n- Select 2 vertices then {key shift ctrl +}\n\n[2022-05-24 19-58-17.mp4](2022-05-24_19-58-17.mp4)", "Option to Apply multi-user\n### Motivation\n\nCurrently in Blender when you try to apply the transforms of an object that has its object data shared across multiple objects it will give an error message and abort the operation.\n\n\n\nIn order for #83927 to get implemented this case needs to be tackled. So instead of failing the operation there needs to be an option to apply the transforms of the current or all affected objects anyway.\n\n### Proposal\n\nWhen trying to apply the transforms of an object with shared objetct data it will promt the user with a p[opup message with the text:\n\" Warning\nThe selected objects have shared data. Do you want to continue to apply?\"\n\nThere should be 3 options presented:\n\"Make single user and apply\", \"Apply all affected\" and \"Cancel\"\n\nThis should cover all desirable outcomes.\n\n### Unknowns\n\nMore possible issues by including this feature need to be discussed.", "AutoMerge Keyframes only deletes unselected keyframes (scaling muliple selected to zero or snapping to the playhead fails)\n\n\nLinux Ubuntu & GeForce GTX 580\n\n\nBroken: master\n\nWith \"AutoMerge Keyframes\" toggled on it simply doesn't do that, whether you're scaling keyframes or moving them around.\n\n[auto_merge.blend](auto_merge.blend)\n\nMake an armature, go to pose mode and set keyframes on the bone. Scroll forward a few frames, move the bone around (and rotate) and key it again. Do this a couple of time so you have some keys to work with.\n\nIf you select all the keys in the dopesheet editor and scale them down so some of them land on the same frame, blender doesn't automerge them. The keys seem to still exist on the same frame, as you can see in the graph editor. Even if you select all the keys and move them by one frame (which should trigger the automerge) it still doesn't merge the keyframes.\n", "No snapping for objects referenced in modifiers (even if disabled)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\nWorked: probably never; hopefully it's just an oversight. Even 2.79b is broken\n\nI've experienced this a handful of times but finally sat down to investigate from the user perspective here today (sorry, haven't looked at the code). But apparently the object you use as Simple Deform's \"origin\" will not be snap-able to the object that has Simple Deform on it. It doesn't matter if the modifier is enabled or disabled or if the settings actually produces no deformation, it always breaks snapping for the origin object.\n\n[snap-issue.blend](snap-issue.blend)\n\n- Open the attached .blend file OR follow next instructions to setup\n - Start with default scene and add an Empty to the scene\n - Add a Simple Deform modifier to the Cube\n - Set the Simple Deform's \"origin\" object to the Empty, the mode to \"Bend\" and the \"Angle\" to 0deg (to prevent any deformation)\n - Set the scene snapping mode to vertex\n\n- Grab the Empty and attempt to snap it to verts of the Cube -- it cannot snap (bug)\n\n- Disable the modifier and repeat the snap attempt -- it still cannot snap to the Cube (bug)\n\n- Create a new object and attempt to snap the empty to that new object -- it succeeds (the Sphere in the attached .blend file)\n\n- Delete the modifier and repeat the snap -- finally, it is able to snap to the Cube\n\n", "Dead Keys failing (accented letters, double strokes)\nOperating system: Windows 10 X64 Enterprise\nGraphics card: Nvidia RTX 2070 MaxQ\n\nBroken: 2.73, 2.91.0\nWorked: Never\n\nIn a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).\nIf I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?\nActually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.\n\n- In the text editor, press and hold the dead key\n- without releasing the dead key, press the key to be transformed. (this will fail)\n\nIf you release the dead key before pressing the key to be changed, it will work normally.", "Python API : OBJECT_OT_convert can't be fully abstracted from context with override\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 2.93.5\nIt didn't work in latest Beta build either.\nWorked: I don't think it ever worked otherwise ?\n\nOverriding the context of an operator with a dictionary enables us to call them from pretty much anywhere in the code without having to make sure the context is correct (selected objects, active object, called from a particular editor, etc.)\n\nHowever the `OBJECT_OT_convert` called with `bpy.ops.object.convert` operator still requires an active object to be selected to function with an override, which defeats the purpose of using an override.\n\nIt is explained quite thoroughly in this BSE Q&A 86891\n\nScript to reproduce in an empty file :\n\n```\nimport bpy\n\nbpy.ops.curve.primitive_bezier_curve_add()\n\n# Commenting these 2 lines removes the RuntimeError (context incorrect) on last line\nbpy.context.active_object.select_set(False)\nbpy.context.view_layer.objects.active = None\n\nbpy.ops.object.convert({\"selected_objects\": bpy.data.objects}, target=\"MESH\")\n```\n\n", "UV space aware triangulation\nPlease see #102683 for details, since the issue is described and discussed there. The basic suggestion is:\n\n> Add an option to the \"Triangulate Faces\" operator. It currently has Quad/N-gon methods for Beauty, Fixed, Longest edge etc. It seems reasonable to add options for \"Prevent UV overlaps\" and specify the source UV map.\n\n", "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", "Limited dissolve ruins UV\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nI made 3 or 4 times cycles of \"Limited dissolve - triangulate\" and get ruined UV after 3-rd or 4-th iteration. \nthe goal is to rid of exceeding geometry like on a screen.\n\n\n", "Shape keys for surface not working - no active option\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.17\n\nBroken: version: 3.5.0\nBroken: version: 3.6.0\nWorked: don't know any version where this working, but last time no option for use this doing hard work\n\nShape keys for surface not working - no active option. \n\nThis not working like expected as typical object have verts. See screen.\n\n", "pressing z key to switch between extrusion \n intel i5 ,win ,amd radeon \nblender 2.8 \n490a385c8124\n\n\n\n\nThis happens when transform orientation set to Global \nCreate a sphere , select a face and extrude \nBy default it will extrude along the normal , when pressing z it will now extrude along the global but it won't go back to normal when pressing the 'z'key again \n \n\n\n ", "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", "`Object().users_collection` and `Object() in Collection().objects.values()` don't work in drivers.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\n`self.id_data.users_collection` always reads out to an empty `tuple` in drivers.\n\n`self.id_data in bpy.data.collections- [x].objects.values()` always evaluates out to `False` in drivers, even when the equivalent expression evaluates as `True` in the interactive terminal.\n\n* Add a driver to any property of the default cube.\n* Enable \"Use self\" on the driver.\n* Set the driver code as follows: `[print(self.id_data.users_collection),0][-1]`\n\nThe empty `tuple` will be printed out to the console.\n\n* Set the driver code as follows: `[print(next(iter(c for c in bpy.data.collections if self.id_data in c.objects.values()))),0][-1]`\n\nA `StopIteration` exception will be raised.", "Gizmo position is wrong for meshes with modifiers\nWin10, Win7, Mac OS Sierra\nGTX970, GTX750\n\nBroken: 2.78a e8299c8 , 2.66.0 r54697\n\n\nWhen a joint (for example, an arm) is bent, paint weight is not enough to express deformation around the joint. So it's a common practice to add a shape key for the bent shape and edit it.\nBut when you enter edit mode and select polygons to edit it, the manipulator is on wrong position. \n\nJust select faces. Manipulator is supposed to sit on the selected faces but it's not.\n\n[manipulator bug.blend](manipulator_bug.blend)" ]

[ "transformUV() and vertex.UV don't work on rigged objects\nArchlinux\n\nBroken: 2.77\n\nAnimating UVs doesn't work on rigged objects\n\n1. Open [BGE_animated_texture_on_rigged_object.blend](BGE_animated_texture_on_rigged_object.blend)\n2. Start the game (P)\n3. Note that the texture isn't animated\n\n4. Do any one of the following: delete the armature modifier, remove all vertex groups, or unparent the mesh object\n5. Start the game (P)\n6. Note that the texture is now animated correctly" ]

[ "Sculpting Brush size becomes too big or too small outside the object when the radius unit is in scene\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\nSculpting Brush size becomes too big or too small outside the object when the radius unit is in the scene This is not file-specific it is happening in all files and for all objects. its sometimes hard to adjust the side at all when that happens. Attaching a video for reference\n\n- Create a new object and scale up or down a lot\n- Switch to sculpt mode\n- Change the Radius Unit to Scene\n- Examine the brush cursor size changes along the surface and in empty space from different angles & zoom", "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", "Viewer node draw depth issue in x-ray mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nViewer node viewport overlay is having some Z-depth drawing issues. Seems to be caused by the X-Ray toggle.\n\n\n\nAdd an object in geometry nodes and view with viewer node\n\n", "OSL on the GPU displays all black for Voronoi Distance > Bump Height\nSystem:\nWindows 11\nRTX3090Ti gpu\n\nBump output is pitch black when using Voronoi (Distance) output into Bump Height. Colorramp in between does not fix it. Noise output into Bump Height works fine.\n(Blender 3.5 in cycles)\n\nedit: more useful info + screenshot + isolated blend file\n\nRunning OSL on the CPU works fine, only the new GPU support seems affected.", "Limited dissolve ruins UV\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nI made 3 or 4 times cycles of \"Limited dissolve - triangulate\" and get ruined UV after 3-rd or 4-th iteration. \nthe goal is to rid of exceeding geometry like on a screen.\n\n\n", "UI: Sequencer/Preview jumps to cover entire preview area\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\n\n- In the Sequencer Preview, select Sequencer/Preview.\n- Adjust regions so both Preview and Sequencer are visible.\n- Adjust the height of the area.\n- Notice that when the area height meets the region height, the Sequencer region jumps to fill the entire area.\nExpected behaviour: that the sequencer region doesn't jump to cover the entire area, but is scaled with the change of the area height. Or in other words that the sequencer region height is scaled to the area height, instead of being fixed. \n{[F10144522](sequencer-preview-jump.gif),size=full}\n\nAn additional annoyance is when changing the area height:\n{[F10144525](sequencer-preview-jump2.gif),size=full}\n", "Generic Rigid Body Constraint Bug\nOperating system: Windows 10\nGraphics card: Radeon RX 470\n\nBroken: 2.83.0\nWorked: Unknown if it ever worked\n\nAngle limit not only doesn't work but causes weird neverending twitching back and forth\nUPDATE:\nTwitching happens for both cases when both rigid bodies are active and when one of them is passive.\n[M0DJ38oWQo.mp4](M0DJ38oWQo.mp4)\n\n1. Add 2 rigid bodies, 1 active, 1 passive animated\n2. Position them active on top, passive on the bottom\n3. Add an empty in between them, add a rigid body constraint to it, select the 2 rigid bodies in its settings, uncheck disable collisions.\n4. Change the joint type to Generic, limit location to 0-0 on each axis.\n5. Play. Now it works, once you select the passive RB and move it it should behave normal.\n6. Undo. Check angle limit on Z and choose some angle range (I had it set to -30 to 30).\n7. Play. Move the passive RB and watch it breaking.\n", "Continuous Grab doesn't work with tablet on Linux\nOperating system: Manjaro Linux\nGraphics card: Nvidia GeForce GTX 750 Ti\n\nBroken: 2.92 and 2.93\nWorked: 2.93 on Windows\n\nContinuous grab function doesn't work with a tablet\n\nHave a tablet set to Relative Mode (Mouse mode). Select the cube. Press G and move the cursor to the edge of the screen. On linux with a tablet the cursor and the cube will stop at the edge of the screen but with a mouse (and with a tablet on Windows) you can keep moving them. Same thing happens when scrolling the menus with the middle mouse click (for example in outliner)\nPlease watch the video. I demonstrate the issue in the 3D viewport, as well as in the blender preferences menu\n[2021-06-20 12-55-33.mp4](2021-06-20_12-55-33.mp4)", "Asset browser: Collection position offset on toggling instance option\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013\n\nBroken: version: 3.3.0, 3.2\n\nAssets imported with link option offsets position when `Instance` option is toggled\n\n- Create collection asset and save it in user library\n- Open default scene\n- Change timeline to asset browser (and in asset browser select library where asset collection is present)\n- Change import type to link\n- Drag collection to viewport\n- toggle `Instance` option (notice collection instance moves from its original position)\n\n[Blender 2022-06-16 10-26-03.mp4](Blender_2022-06-16_10-26-03.mp4)\n", "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.", "Particle Emitter - Particles collisions not accurate\nOperating system: Linux-5.11.0-40-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha\nWorked: This has been an ongoing problem since starting with Blender from 2.8\n\n\nParticles are not respecting collision system in every case.\n\n- Create plane and add particle system\n- Give emitted particles a positive or zero gravity value in field weights\n- Add wind force field running roughly parallel to plane.\n- Add turbulence.\n- Add collision system to plane\n\nExpected behaviour is for the particles to bounce off the plane as they are emitted in a positive Z direction and blown by turbulence against the plane. Instead they often break through. In the past this has meant that particles are bypassing the collision system such that emitted bubbles break through the hull of a submarine, and in my current case, half my sand particles to be hidden from view in a desert scene.\n\nNote attached file which shows the behaviour. Watch the simulation side on and particles can clear be seen breaking through the mesh.\n\n[Sand Wind Test.zip](Sand_Wind_Test.zip)\n\n\n\n", "Displacement map, wrong normals and shadows on triangle geometry\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.69\n\nBroken: version: 2.92.0\nWorked: ?\n\nExperimental Cycles displacement introduces rendering artifacts on some geometries made of triangles. The problem seem to disappear on quad geometry.\n\nOpen the attached \"displace-problem.blend\" file.\nRender an image, or enable Cycles preview in viewport.\nThe left object is made of triangles, and appears with problems.\nThe right object is made of 1 quad, and appears fine.\n\n[displace-problem.blend](displace-problem.blend)\n", "Connected child bone's nominal location values affected when transformed about 3D cursor\nBroken: 2.79, 2.90.1\nWorked: N/a\n\nAs expected, when moving a single connected child bone, its location is not affected, only the rotation.\nBut it is still possible to affect them accidentally if transforming about the 3D cursor.\nThis is a minor bug, but it's a definite inconsistency.\n\n - Open attached file.\n - Move/Rotate/Scale the child bone about the 3D cursor.\nNote the bone's nominal location values in the side panel.\n\n[Connected Bone Pose Bug.blend](Connected_Bone_Pose_Bug.blend)", "UV: Add 3D Gizmos for UV projections, Cube, Cylinder and Sphere projection\nThe \"Unwrap > Projection\" operators are powerful, but would be even better with artist control over exact placement in 3D space.\n\nPropose to add gizmos in the 3D viewport to allow precise artistic control over the cube, sphere and cylinder.\n\nConsider adding Planar Projection as well.\n\nThanks @BlenderBob for the suggestion!\n\n", "GPencil: Randomize brush's 'Position' attribute doesn't work when camera is too close to Grease Pencil object\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.93, 3.1.0\nWorked: N/A\n\nExact steps to reproduce the error:\n\n- Open file\n- try to use Randomize brush\n- Strength and Thickness work, but not Position \n- Switch to the other camera that's farther away from the GP object, and randomizing the position works fine.\n\n[randomize_not_working_close_NEW.blend](randomize_not_working_close_NEW.blend)\n\n\nwatch?v=4pTrEm5HqVU" ]

[ "Asset browser: dropping object on grid in orthogonal view misses the floor plane\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 3.1.0 Alpha\n\nDropping an object on the grid should go the Z 0 but instead it goes under the floor plane if done in othogonal view\n\n[Asset.blend](Asset.blend)\nDrag & drop the Cube asset into the left screen\n\nThe cube will be dropped below the floor (check the right screen)\n", "Asset Browser crashes Viewport in orthographic mode when Auto Perspective turned off and Orbit around selection is turned on.\nOperating system: Windows 10 64 bit, Linux Manjaro 21.1.2 Cinnamon\nGraphics card: Nvidia GTX 1080, 1070\n\nBroken: 3.0 release version\nWorked: never, as there were no asset browser implemented in previous versions\n\nHi! I've switched to 3.0 today and was migrating my kitbash assets to the new Asset Browser and immediately encountered a bug when your **viewport crashes and glitches** when you have **Auto Perspective turned off** and **Orbit around selection** is **turned on** in the preferences and you use Asset Browser. I always model in **orthographic mode**, I believe this to be the best practice for modeling and it's very easy to replicate the bug and crash your file while you're working on it in orthographic view. \n\n1. Go to Preferences and make sure to tick **Auto Perspective turned off** and **Orbit around selection** is **turned on**, save settings\n\n2. Create a new scene with default objects, immediately **press A and delete them all**. (It's easier to replicate the bug when there's nothing in the scene)\n3. Turn **orthographic mode on** and position your camera to **frontal/side/ views** so that you can see the grid.\n4. Roll out asset browser window and start putting assets down into the viewport\n5. Hold MMB and start rotating your viewport view and see wierd things happening.\n\nI'm not sure what is the culprit here, it's either orthographic mode or it's Orbit around selection when nothing is selected in the scene, IDK. I get this viewport bug randomly sometimes when I work in 3.0 in orthographic mode when nothing is selected, but with Asset Browser I could replicate it all the time whenever I've tried.\n\n\nHere's a video reproduction of the said bug with comments:\n[2021-12-04 13-58-19.mp4](2021-12-04_13-58-19.mp4)\n\n*P.S. Also, you should implement mkv video format preview in developer.blender.org mp4 video format is not FOSS XD.*" ]

[ "VSE strip can't be seen with frame all\nOperating system:\t\tWindows 7\nGPU:\t\t\t\tRadeon Vega 64\nGPU Software Version:\t20.4.2 (2020.0515.1537.28108)\nCPU:\t\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t\t`2.79 (sub 00), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b, type: Release, build date: 2018-03-22, 09:59 AM`\nBroken:\t\t\t\t` blender-2.90.0-ba2d1c889819-windows64` (BF Build Bot)\n\n\nChannel 32 can't been seen with Frame All\n\n\n|  |  |\n| -- | -- |\n\n\nHave at least 2.00 Display Scaling\n\n[Channel_32.blend](Channel_32.blend)", "VSE: The blend and opacity settings that strips are created with does not match the default values they revert back to\nOperating system: Linux-5.4.0-80-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\nStrips are created by default with blend method \"Cross\" and blend opacity \"1\", however reverting to default values results in \"Replace\" and \"0\".\n\n- Open VSE\n- Add/create any strip\n- Under strip properties in sidebar, note that blend method is \"Cross\", and opacity value is \"1\"\n- Choose \"Reset to default value\" from context menu for both of these settings\n- Blend method will change to \"Replace\"\n- Opacity value will change to \"0\"", "Crash with certain file. Sculpt mode. Vertex color fill + edge.\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\nWhen I try to apply vertex color Fill (Sculpt mode) on edge in this particular file, I get crash\nAnd all fine for shapes/triangle.\n\n[VC + edge crush.blend](VC___edge_crush.blend)\n\n[debug_logs.7z](debug_logs.7z)\n", "Suzanne (monkey) UV map is not symmetrical and has bad stretching around the beginning of the ear\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: has never worked as expected\nWorked: never worked, looking at the original task for default uv map for monkey primitive, it's wrong there also.\nT47488\n\nThe current UV map for the monkey default model is not symmetrical and has bad stretching around the beginning of the ear. \n\nNot symmetrical\n\n\n\nBad stretching\n\nExpected result\n\n\nThis also effects the way monkey was uv unwrapped since the uv islands cannot be unfolded correctly in a straight and symmetrical line due to the seams being misplaced.\ncurrent\n\nexpected\n\nexpected result .blend\n[Fix_Monkey_UVMap.blend](Fix_Monkey_UVMap.blend)\nmade a quick proposal for an improved version also for the eyes, currently they are rotated in a way which makes it bad for texturing since the margins are so thin in some places that the texturer can bleed over due to midmaping in some rare cases, this version fixes it. Also looks nicer. \n\n[Improved_Monkey_UVMap.blend](Improved_Monkey_UVMap.blend)\nshift a, add mesh, monkey\n\nenter edit mode and select all uvs in uv editor, UV, seams from islands\n\nAdd uv cheacker grid and look closely at where the ears start and notice that the seams are not symmetrical and some bad stretching around the beginning of the ear. \n\nbug .blend:\n[Suzanne (monkey) UV map Bug.blend](Suzanne__monkey__UV_map_Bug.blend)\nexpected result .blend:\n[Fix_Monkey_UVMap.blend](Fix_Monkey_UVMap.blend)\nimproved version .blend\n[Improved_Monkey_UVMap.blend](Improved_Monkey_UVMap.blend)\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.", "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.", "Edges are selected in face mode when deselecting vertices from vertex group Panel\nBlender Version\nBroken: Current main.\nWorked: N/A.\n\nShort description of error\nDeselect Button in Vertex Groups Panel will deselect vertices that are not assigned to any groups. Edges become selected while in Face Mode as well. Also the Select Button will Select Faces that are not assigned too but those Edges that are active in face mode must be Selected for the Bug to work. Pay attention to the Edge around the triangle Fan at the top of the uv Sphere While in face mode.\n\nBlend File Incuded for simplicity\nJust Press the Deselect and notice the Faces that Get removed. and the Edges are actively Selected.\n\n", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "Cycles 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", "Solidify cause wrong vertex selection in edit mode\nLinux-4.19.0-12-amd64-x86_64-with-debian-10.6 64 Bits\nMesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6\n\nWindows 10-10.0.19041 SP0 64Bit\nGeForce 9600 GT PCIe SSE2 Nvidia Corporation\nRadeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.83.2\nBroken: version: 2.90.1\nBroken: version: 2.91.0 Beta\nWorked: unknown\n\nIn 3d viewport, vertex selection, solid mode, X-Ray off, you cannot predict what you are selecting when using solidify:\nBlender is ignoring the X-Ray (\"Allow selecting through the items\") and is selecting, randomly, occluded items.\nHaving a very narrow clipping does not mitigate the issue.\n\nExplanation video [SelectLight.mp4](SelectLight.mp4)\n\n[#82182.blend](T82182.blend)\n\n- Open file\n- Click inside blue circle\nOccluded vertex will be selected\n", "Unable to select vertex paint face mask faces while retopology overlay is active\nOperating system: Ubuntu 23.04\nGraphics card: AMD Radeon RX 570\n\nBroken: `main` (`e151425c5c1085d7be5f8bb2ad694a869bc16dc7`)\n\nIf the new retopology overlay is active in edit mode, vertex paint faces can't be selected \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. With default cube in _Edit_ mode, enable the Retopology overlay\n2. Switch to _Vertex Paint_ mode\n3. Enable face selection masking\n4. Try to select a face\n\nA small video is attached, showing first successful selection of a vertex paint face mask while the retopology overlay is inactive, then the inability to select vertex paint face mask faces after it's activated.\n\n", "UV Editing move/scale/rotate tool, add option to respect pins\nFor Live Unwrap to work correctly, the move/scale/rotate etc tools all allow the user to move the *pinned* UVs, while the live unwrap algorithm moves all the other UVs in a nice manner.\n\nHowever, without Live Unwrap, the \"Pin\" concept could be extended to actually Pin the UVs in place.\n\nThis is a feature request to add an option to actually Pin the Pinned UVs when using the move tool, with an additional option to respect the falloff parameters around the pinned UVs as well as the user selection.\n\nFrom a design perspective, this should probably consider the \"Grab\" Sculpt tool and the generic Transform tool as well.\n\n", "Custom color attribute vs. vertex color - difference in color managed render\nOperating system: Linux-4.15.0-137-generic-x86_64-with-glibc2.23 64 Bits\nGraphics card: GeForce 920MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130\n\nBroken: version: 2.93.0 Alpha\n\nThere is a mismatch while displaying the vertex color layer and vertex color set as a custom-attribute.\n\n1. Run the script which sets the vertex color layer (Col) and custom attribute vertex color (GN-Col).\n2. Then change the `max` input of *Attribute Randomize*, it will update the colors.\n3. In shader nodes switch between two vertex colors: *Col* and *GN-Col*. \n\n[custom_attributes4.blend](custom_attributes4.blend)", "keyboard shortcut to switch between vertex / edge / face not present in tooltip\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nI rely on the tooltips to learn keyboard shortcuts.\nWhen hovering above the vertex / edge / face select button, the shortcut to enable this button is not mentioned.\nexpected: \nVertex Select: 1\nEdge Select: 2\nFace select: 3\n" ]

[ "Vertex Slide - Using Operator Factor value slides along wrong edge\nOperating system and graphics card\nBlender build 2.74 50c6e3 Ivybridge gfx card (Fedora 21 64Bit)\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nI am on using Blender build 2.74 50c6e3 on a Linux 64Bit Box with a Ivy Brige GFX card.\n\nI noticed that when using the Vertex Slide feature (shift+v) that the operator panel\nshows a factor slider. If you use the factor slide though it doesn't slide the vertices\nalong the correct edges that you originally slided the vertice on. Am I right in\nassuming that the Factor slider is there to allow you to tweek your previous completed\nVertex Slide?\n\nI also noticed that the operator panel has a confirm on release tickable option\nwhich seems to do nothing.\n\nI have attached a blend file showing the issue, a video showing the issue and my\nsystem-info.txt file.\n\nAlso on trying to research this tool I noticed that in the new Blender Manual it say that\nkeyboard hotkeys:\n```\n Snap to Midpoint Shift\n Snap to Endpoint Alt\n Snap and Merge to Endpoint Ctrl\n```\n\nLink to new manual entry:\n```\n \n vertices.html?highlight=vertex%20slide\n \n```\nOnly when I tried using these keyboard shortcuts none of the features seems to be mapped to\nthose keys. So my question there is should those keys do that or is this a mistake in the\nmanual (or a change in code).\n\n[system-info.txt](system-info.txt)\n\n[VertexSlide-FactorBug.blend](VertexSlide-FactorBug.blend)\n\n[VertexSlideFactorIssue.webm](VertexSlideFactorIssue.webm)", "Vertex Slide - Correct UV Bug?\nOperating system and graphics card\nBlender 2.74 d33b564 Fedora 21 64Bit Ivybridge\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nI am using Blender 2.74 d33b564 on a Fedora 21 Linux 64Bit Box with Ivybridge GFX\n\nI noticed that when using Vertex Slide (SHIFT+V) that the operator panel Correct UVs\noption is very odd/risky because the edge that a vertex gets slid along is reset to the\nwrong location. It also act very differently depending on weather Correct UVs is\nalready active or not when Vertex Slide is executed.\n\nI have attached my system-info.txt file, a blend file showing the issue and a video\nalso showing what happens.\n\nI am posting this as a separate bug even though it could be related to bug:\n```\n \n T44608\n```\n\n[system-info.txt](system-info.txt)\n\n[VertexSlideCorrectUVBug.webm](VertexSlideCorrectUVBug.webm)\n\n[VertexSlide-CorrectUvsBug.blend](VertexSlide-CorrectUvsBug.blend)" ]

[ "Theme > Shader Editor, Sidebar > Alpha value does not work\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A3000 12GB Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.1\n\nIn side of the Shader editor, if you want to change the color works correctly, but if you want to change the Alpha value, is not working.\n\nGo to Preferences > Themes > Node editor > Theme space > Region Background\n\n", "Integer attributes not usable in shader nodes\nOperating system: Linux-5.15.23-76051523-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54\n\nBroken: version: 3.2.0 Alpha\n\n[integer_attribute_rendering-2022-04-04_19.04.26.mp4](integer_attribute_rendering-2022-04-04_19.04.26.mp4)\nInteger attributes seem to be snapping to 0 and 1,073,741,824 (2^30) when used in shader nodes. This happens with both Eevee and Cycles. When the attribute is output as a float instead, everything works fine.\n\nFor interpolation I expect the renderer to handle integers internally as floats but currently integer attributes are simply unusable for shading.\n\nFile:\n[integer_rendering.blend](integer_rendering.blend)", "Alembic doesn't import vertex colors for meshes made of only vertices\nOperating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.125.06\n\nBroken: Version: 3.6.0\nWorked: Never.\n\nWhen importing Alembic caches, vertex colors are only imported correctly when the imported geometry is made of faces.\nWhen the geometry is only vertices, no vertex colors are imported. (ex. point clouds)\n\nI suspect this has to do with vertex colors encoded as a point attribute instead of a face corner attribute.\nI've checked both provided alembic files in other software to make sure they're not the issue and they work fine everywhere else.\n\n1. Import mesh.abc.\n2. Vertex colors are read correctly and are stored and accessible as a Face Corner attribute.\n3. Import `points.abc`.\n4. Vertex colors aren't read at all, expected behavior is that they're stored stored as a Vertex attribute.\n", "Viewport Shading 'Attribute' Option Broken for Instanced Geometry\nOperating system: Windows 10\nGraphics card: Nvidia GTX 2080\n\nBroken: 3.5\nWorked: 3.4, 3.4.1\n\nWhen instancing a mesh to another meshes vertices, the Solid Viewport Color Option 'Attribute' is no longer displaying the vertex color data.\n\nCreate A Sphere, and using \"Vertex Paint Mode\" Paint a color onto the sphere.\nUsing geometry nodes set up the following, Group Input (Geometry) -> Mesh to points - > Instance on points -> Realize Instances -> Output (Geometry)\nSet a simple sphere as the object to be instanced.\nSet Shading mode to 'Solid'.\nToggle 'Attribute'\n\n", "Missing undo push for Paint Mask and Vertex Selection in weight paint\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.0 Alpha\n\nEnabling or disabling of the Paint Mask and Vertex Selection modes is missing an undo push\n\n\n\n[Weight.blend](Weight.blend)\nEnable Paint Mask\n\nPaint on the model\nUndo\nResult: Both the paint and the paint mask mode are undone", "Vertex group (memory access?) change after applying modifier \nOperating system: Linux-4.15.0-159-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.0.0\nWorked: 2,93\n\nLooks like this came with 263fa406cd: Fix #90087: Assigning object data doesn't copy vertex groups / 99738fbfdc: Fix memory leak from 263fa406cd\n\nI have an object with an existing vertex group.\nI then run a script, that creates a new vertex group and stores it in a variable accordingly.\nThe script then creates a modifier - any kind I think - and applies it using the `object.modifier_apply()` op.\n\nIn 3.0 the vgroup variable now references the existing vertex group instead of the newly created one, that was assigned to it.\nThe memory address remains unchanged however - at least on linux.\nRemoving the vgroup referenced by the variable will then remove the existing one, instead of the new one.\nI think on windows, it may cause an exception but I need confirmation of that from a Windows user.\n\nIn 2.93, everything works as expected, the vgroup assigned to the variable never changes and is removed properly\n\nSee this [video demo ](WMGjQKEgNco).\n\n[vgroup_changs_after_applying_modifier3.blend](vgroup_changs_after_applying_modifier3.blend)\n\n\n* open the attached blend file in 2.93 and 3.0\n* go to the Scripting workspace and run the script\n* note how in 3.0 the print out of the vgroup variable changes after the modifier is applied\n\n", "Viewpor render includes color management, even if the view shading mode does not\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.77\n\nBroken: version: 3.1.2\n\nA viewport render should look exactly as what's seen in the viewport, especially if that viewport is set to, for example, solid shading. Right now, it does not, because color management is taken into account even in shading modes which do not use it.\n\n1. Set viewport to shaded mode\n2. Set viewport background to a white color\n\n3. Set something in the color management panel to something crazy\n4. Observe how the viewport does not change.\n5. Make a viewport render\n\nResult:\n\nThe viewport render includes the crazy values from color management.\n\nExpected:\n\nIt should look like the viewport and nothing else. It's *technically* not a viewport render currently.", "Weight gradient tool auto normalizes over locked groups\nOperating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.36 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhen gradient painting over a group, the auto normalization affects other groups that are locked.\n\n[Weight Gradient Normalize.blend](attachment)\n1. Notice the weighing of the **Bone 1** vertex group.\n\n2. Select the **Bone 2** vertex group.\n3. Drag over the model to gradient paint.\n\n4. Select **Bone 1** again.\n**Bone 1** has been auto normalized even when it's locked\n", "Eyedropper values are slightly off from target color\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nEyedropper values are slightly off from target color, unless in hex mode press enter.\n\nIn attached file using eyedropper replace green color of selected strip with grey from above strip -> result is a bit darker color\nGo to hex color mode, place cursor at value and hit enter -> color is ok\n[color_picker.blend](color_picker.blend)", "Transfer attributes in the fill curve node\nThis is like [D12363: Geometry Nodes: Transfer attributes in the curve to mesh node](D12363), but most likely much simpler.\n\nWhen there are non-builtin attributes on the curve (anonymous or named), they should be transferred to the vertices created by the curve fill node. The Delaunay triangulation can generate an index map for such situations, which should make the transferring quite simple.\n\nThe Delaunay index map shouldn't be created if no attributes will be transferred anyway, since it has a performance cost.", "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)", "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)", "Spreadsheet not reading evaluated `bevel_weight_edge` attribute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 4.0.0 Alpha\n\nthe `bevel_weight_edge` isn't being displayed with the correct value in the spreadsheet, both for GN geometry[^1] and original[^2] geometry [not made in GN]; both when the bevel weight is set in GN[^1], and when it's set in edit mode[^2].\nalthough, when using the *viewer node* the correct value is displayed[^1].\n\nThis could be happeding with other attribute, but I haven't tested.\n\nset the bevel weight (any way you'd like) and look in the spreadsheet.\n\n[^1]: <video src=\"attachment\" title=\"2023-07-08 22-47-22.mp4\" controls></video>. \n[^2]:<video src=\"attachment\" title=\"2023-07-08 23-02-16.mp4\" controls></video>\n\n", "EEVEE Shading: string sockets node group interface value doesn't work\nBroken: version: 3.0.0 Alpha\nWorked: n/a\n\nin shading, String sockets exposed via node group interface don't use the value from the node group interface\n\nSteps to illustrate the problem\n\n* Use a quick smoke effect on a cube\n* Add a principled volume and connect it to material volume output\n* Change the Density Attribute to other text\n* Group the principled volume\n* Change the Density Attribute back to density\n\n[volume.blend](volume.blend)\n\n", "Regression: Changes in curve normal behavior\nBroken: 3.0\nWorked: 2.92\n\nInstead of a simple arrow, the scene is something very remotely in the neighbourhood of that shape plus random extruded edges. \n\nOpen example file.\n\n" ]

[ "Regression: Bake to color attributes - target is always the first one (no matter the active index)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.2.0\nWorked: 3.1.2\nNo matter which color attribute is active or set for render, the baking target is always the attribute with index 0 (first one).\n\n\n\n # Open the attached blend\n[bake-to-col-attr_always_first.blend](bake-to-col-attr_always_first.blend)\n - Hit Bake\n - Watch how the first attribute (*Col*) has been updated instead of the second (*AO*) one (despite it is the one which is active & set for rendering)\n\n", "Bake vertex color to selected channel are not working.\nOperating system: Windows 10\n\nBroken: 3.2.0\nWorked: 3.1.2\n\nSet desired vertex color channel by click on camera icon to bake doesnt work. Baking are always happened for channel which was created first. I.e. it doesnt matter how you name you channels, it doesnt matter which of them are marked as active for baking by camera icon on the list. Baking will always write info into channel which was created first.\nIf you press on adding button and have Color, Color.001, Color.002,... baking will happen for Color because it was the first one created.\n\n\nCreate at least 2 vertex color channels. Try to select any vertex color channel by click on camera icon, but not the first one which was created, top make that channel active for bake. Bake something. Baking will happen for first created channel." ]

[ "Texture Node Editor Using nodes causes weird issues in sculpt mode.\nOperating system: Linux-5.15.0-48-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.76\n\nBroken: version: 3.3.1\nWorked: perhaps never? (can redo in 2.83)\n\nAdding an image from the nodes of the texture editor for example, a sculpting brush, causes really weird issues. Disabling nodes and using the texture properties does not have this issue.\n\n- Check the blend file. Try sculpting, you will see weird noise being displaced with the texture.\n- Now disable the nodes and set the texture type from the texture properties to the same image. Sculpting again you see the issue is not happening.\n[bug.blend](bug.blend)\n\n\n\n", "Regression: Vertex colors are now broken in hair strands\nOperating system: Gentoo Linux kernel 5.18.0-gentoo\nGraphics card: RX 480\n\nBroken: 3.2.0, 3.3.0\nWorked: 3.1.0\n\nCaused by b9799dfb8a\n\n\nVertex colors are strange and patchy when moving from 3.1.0 to 3.2.0 or later: \n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Make something with vertex colours and a hair system which utilises them in Blender 3.1.0. In my instance I used geometry nodes to generate them; this may differ when making them manually as one of my other projects which does it manually does not seem to exhibit this issue. \n2. Open file in Blender 3.2.0. \n\nI created the following .blend file to demonstrate the issue: [Color_test_3s.blend](Color_test_3s.blend)", "EEVEE: Nishita Sky change Sun Rotation causes shader recompilation\nBroken: version: 3.4.0 Alpha\n\nAdjusting Sun Rotation in Nishita Sky texture in EEVEE causes shader recompilation\nwhile adjusting sun elevation is not causing shader compilation and allow to realtime adjustments\n\nThis makes impossible to have animated sun position.\n**Steps to Reproduce**\n- Open .blend file -> switch to viewport rendering\n- Change rotation value with slider\n[#101197.blend](T101197.blend)\n[nitsha.mp4](nitsha.mp4)", "Improve auto offset when inserting new node\nIn the example below the Noise Texture node should be moved automatically as well, not just the Set Position node.\n\n[screen_recording-2021-12-13_17.34.37.mp4](screen_recording-2021-12-13_17.34.37.mp4)\n\nThe exact behavior in more complex trees still has to be designed.", "Mix Node Modes\nThe new mix node has different options according to data type.\n\nThe idea of this task is to look at adding the mix modes to float and vector data types.\n\nThe color blending modes could be used but a number of these modes assume that the\ndata is in the range of 0-1.\n\n[D16024: Node: Add mix type to Mix Node](D16024) \nThis a patch adds non-color mix types to float and vector data types.\n\nAdditionally, it would be good to look at how different interpolation modes could also be added. ", "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", "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)", "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", "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", "16 bit transparent Image renders color data on CPU Cycles\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02\nCPU: Intel i7-4770k\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nRendering a transparent Filmic Log 16bit PNG image plane (meaning node color space set to filmic log) with Cycles the CPU renders color data where there should not be any. The GPU works as expected.\n\nevery thing with Cycles (have not tested eevee)\n1) render something with transparent background and save as PNG (RGBA, 16bit)\n2) import image as plane ( shadeless )\n3) set image node color space to Filmic log and background to transparent \n4) rendering with CPU or CPU+GPU results in the tiles rendered by the CPU to have color data (see image)\n\nSwitch Display Channels to color to see this issue\n\n[test.blend](test.blend)\n\nRedner: \n\n- on the left is no image plane, only the transparent background\n\nUsed image:\n\n\n", "Creating over 2047 instances overrides object color viewport display\n[pointcloud-object-color.mp4](pointcloud-object-color.mp4)\n\n[#93245 cleaned up.blend](T93245_cleaned_up.blend)\n\n**Steps to Reproduce**\n- Open file\n- Toggle switch node or increase the \"False\" value to 2048\n\nAnother file that demonstrates the issue:\n\n\n### Original Report\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nIt seems that a geometry node scattering system created on one object can somehow change the display color of other point-cloud type objects, see gif \n\nIf we change the density of a scatter system assigned to this blue object, it can somehow change the display color of the other scatter object with a point cloud type\n\n\nIn file below, enable the node \n\n[bug.blend](bug.blend)\n\n\n\n\n", "vertex paint sample color not working as intended.\nplatform: Windows-10-10.0.19042-SP0\nGraphics card: 1080\n\nBroken: 3.1.0 Alpha\ncommit date: 2021-11-14 00:26 hash: 7e82c840b7a4\nbuild date: 2021-11-15, 00:51:48\n\n**Short description**\nVertex color that is sampled changes.\nChange in sample color after moving mouse over panel\n\n**Steps to Reproduce**\n- Go into Vertex paint mode. (make sure viewport shading mode is set to rendered)\n- Select an object then press s to sample a vertex color and left click the mouse (to add to palette)\n# move the mouse over panel (selected color will be changed)\n\nThis seems to happen when you move the cursor over any part of the U.I.\n\n[Vcol.blend](Vcol.blend)", "Issues with HDRIs and render result pixel values that exceed half float limits\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n(Also tested in latest 3.3 Alpha)\n\nSome lookdev HDRI's give the scene a colored tint, that also does not disappear after lowering the strength\n\nI imported this HDRI to preview lighting in my Eevee scene: lenong_2\n\nAt first, this looks okay in blender:\n\n\nBut after lowering the strength, you will notice that there is a yellow light that should not be there, as well as a white spot from where the sun used to be, even if strength=0\n\n\nI found a workaround by adjusting the exposure of the HDRi in advance by -1 in affinity photo. This makes the image only a tiny bit darker, but the end result is as you would expect it.\nNo yellow light, no sun.\n\n\nI tried this with another HDRi from HDRIhaven (from another creator, this one specifically ehingen_hillside) and the issue also existed there. \n\nHere is the blend file for testing:\n[HDRI_Test.blend](HDRI_Test.blend)\nAnd the HDRI fixed by me\n[lenong_2_1k_fixed.hdr](lenong_2_1k_fixed.hdr)", "EEVEE-Next: Refactor renderpass storage\nCurrently render-passes are allocated in multiple texture buffers.\nThey take a lot of binding points and currently prevent the deferred pipeline to output diffuse color correctly.\n\nThe plan is to combine all render-passes into the same array texture and use an associated UBO containing offset to the layer of each pass type.\n\nThis would very similar to the AOV support.\n\nAnother direct benefit of this would be that the GBuffer encoding could be simplified.\n\n", "Geometry Nodes: Curve primitives issues with object material\nBroken: version: 3.2.0 Beta, 3.3.0 Alpha\nWorked: n/a\n\nMaterials assign to the object don't work in some cases for curve primitives created in the geometry nodes tree.\n\nOpen file, you will see that the star doesn't get the red object material.\n\n[curve_object_material.blend](curve_object_material.blend)\n\nUnhiding any of the hidden nodes (Grid or Set Material) will make the object material show up." ]

[ "Can not set one image node to non-color without changing it for every node using that image\nOperating system: Linux-4.4.0-151-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79, and 2.80 until a while ago\n\nOften you want to load an image texture and use it both as input for color, as well as roughness or bump. \nPreviously it was possible to just duplicate the image node, set the second node to non-color and it would work as expected. \nNow if you use the same image data-block, setting the colorspace will always set the colorspace for all instances of that image.\nI know this is also kind of expected, but also breaks many older shaders. \n\nOpen this blendfile and try to change the colorspace of just one image node to non-color. [image_colorspace.blend](image_colorspace.blend)\n\n", "Color Data for Image Texture Nodes\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX970\n\nBroken: 2.8\nWorked: (optional)\n\nWhen working in the Shading workspace and adding multiple image texture nodes pointing to the same image file, changing the color space on one node changes it in all image nodes pointed to the same file for that material. I feel like they should stay independent.\n\nCreate a material.\nSwitch to the shading workspace.\nAdd two image texture nodes pointing to the same image file.\nChange the color space on one from sRGB to Color Data, and they both change.\n\n[Bug.blend](Bug.blend)", "Color space configuration of copies of image texture nodes is not independent.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.6859\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe color spaces of two image texture nodes using same image cannot be configured independently.\n\nStep 1: Create any new material.\nStep 2: Create an image texture node with any image.\nStep 3: Copy the image texture node in step 2 above so it uses same image. At this point, both image texture nodes have same color spaces. \nStep 4: Try changing the color space of any one of them. The color space of the other one changes automatically.\n\n** Can be reproduced on simple default startup blend file as well. I was assuming this is not the expected behavior - that we can change the color space of each image texture node independently. Please let me know if I'm wrong in my assumption." ]

[ "COLORSPACE SELECTOR: Group box fails to show all possible colour transforms\nDebian Stretch\n\nTrunk\n\nTrial against ACES 1.0.3 set won't show all possible colour transforms when choosing via the UV Image Editor\n\nLoad the ACES 1.0.3 configuration from the official repository. Try to change the colour transform on a loaded image.\n\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", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "UV Editor Tools Todo\n\n\n# UV Editor\nCurrently, the UV editor has a bunch of confusingly overlapping tool-modes. This should all be simplified via the new active tools system.\n\n * - [x] {icon circle color=red} Add Radius, Strength and the other relevant UV Sculpt settings to the tool settings & top bar\n * - [x] {icon circle color=red} Add Move tool to the toolbar\n * - [x] {icon circle color=red} Add Rotate tool to the toolbar\n * - [x] {icon circle color=red} Add Scale tool to the toolbar\n * - [ ] {icon circle color=red} Add Scale Cage tool to the toolbar\n * - [x] {icon circle color=yellow} Add Pan & Zoom gizmos in top right corner, same as 3d view.\n * - [x] {icon circle color=green} Add the Placement option to the Annotate tool settings (Current default is to only draw in the view, which is not so useful)\n * - [ ] {icon circle color=green} Add Shear tool to the toolbar\n * - [x] Split UV Editor from Image Editor\n * - [x] Remove old tools panels \n * - [x] Add 2D Cursor tool to toolbar\n * - [x] Add Transform tool to the toolbar\n * - [x] Make the Transform Scale Cage Gizmo only appear when Scale Cage transform tool is used\n * - [x] Fix Annotate tool in the toolbar, so that it actually works\n * - [x] Add UV Sculpt tools to the toolbar \n\n\n\nWhen in the Image Editor Paint Mode, we should follow the design of the Paint modes in the 3D View, meaning;\n\n * - [x] {icon circle color=red} Tool Settings should be in top bar\n * - [x] {icon circle color=red} Toolbar should work the same as in 3D View\n\n", "Boolean merges CustomData inconsistently (UVs, VCols), breaks UV Map Node\nOperating system: Linux-5.0.0-25-generic-x86_64-with-Ubuntu-19.04-disco 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.34\n\nBroken: version: 2.81 (sub 2)\nWorked: (optional)\n\nThe UV Map of an object with Boolean Modifier doesn't work when the UV is assigned to the texture with the UV Map node. \n\nOpen this file:\n[boolean_uv_map.blend](boolean_uv_map.blend)\nThe UV layout of the bigger cube is not used. Once you unplug the custom UV Map node in the shader, the UV Map works again. It also works when you disable the Boolean Modifier. ", "Cycles HIP RT geometry artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600 ATI Technologies Inc. 4.5.0 Core Profile Context 23.5.2.230523\n\nBroken: version: 3.6.0\nWorked: 3.5.1\n\nMesh in blender cycles looks weird, some faces in the geometry don't show correctly in Blender 3.6 with the new HIP RT\n\nJust installed and opened blender, turned on HIP RT in the settings tab and then opened a file with a model i made with blender 3.5.1 and switched to cycles.\n\ni attach a screenshot of how it looks with HIP RT and how it's supposed to look (how it looks with HIP RT deactivated)\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 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", "Fast highpoly mesh editing\n**Status:** Need work plan \"approval\", all tasks listed already. Could use a design / engineer plan and ideally a commissioner (though if the scope here is super technical just having some artists testing may be enough.\n\n---\n\n**Team**\n**Commissioner:** `?`\n**Project leader:** @ideasman42 \n**Project members:** @fclem\n\n**Description**\n**Big picture:** 2.7x level of performance for mesh editing.\n\n**Use cases**:\n* Editing high poly objects with good performance without modifiers.\n* Sample file with 3M avaiable on request, file is ~300MB.\n\n**Design:** #74186 (Proposal for fast high poly mesh editing)\n\n**Engineer plan:** `?`\n\n**Work plan**\n\n**Milestone 1**\nTime estimate: `?`\n\n- [ ] Skip EditMesh to Mesh Conversion [D7169](D7169) (committed)\n\n - [x] Create API function to lazily initialize an edit-mesh objects evaluation mesh #64262\n - [x] Lazily initialize by disabling edit-mesh to mesh conversion in the modifier stack, calling lazy initialization where needed.\n - [ ] Replace lazy initialization with code that uses the edit-mesh, where practical. *(partially done)*\n - [ ] Evaluate production scenes *(yet to be defined)* to ensure that conversion isn't required for common editing operations.\n - [x] Draw manager support deformed edit-meshes, so an edit-mesh conversion isn't required when drawing an edit-meshes deformed cage *(similar to 2.7x support).*\n\n- [ ] Minimize GPU Transfer Overhead\n\n - [ ] Create API functions for tagging edit-mesh changes.\n - [ ] Limit updates to: selection data, active element.\n - [ ] Edge Flags Sharpness Seam\n - [ ] Limit updates to: deformations.\n\n - [ ] Coordinates, Face centers & normals.\n - [ ] Custom normals.\n - [ ] UV-tangents.\n\n - [ ] Limit updates to: custom-data layers.\n\n - [ ] UV coordinates.\n - [ ] UV selection.\n - [ ] Vertex color.\n - [ ] Vertex group color.\n - [ ] Custom normals.\n\n - [ ] Limit updates to: mesh properties.\n\n - [ ] Edge crease.\n - [ ] Edge flags (sharp, seam).\n - [ ] Face flags (freestyle).\n\n\n- [ ] Multi-Thread bmesh to mesh conversion.\n\n - [ ] For evaluation mesh *(uses simplified logic)*. [D6947](D6947)\n - [ ] For the full bmesh to mesh coversion *(uses more complex logic).*\n\n- [ ] Optimize edit-mesh GPU updating code\n\n *Benchmark production files, and investigate if the current code has room for improvement, making necessary optimizations.*\n\n**Milestone 2**\nTime estimate: `?`\n\n- [ ] Partial Geometry Updates\n\n - [ ] Support updating only modified geometry when transforming vertex coordinates.\n\n - [x] Coordinates.\n - [x] Normals.\n - [ ] Custom Normals *(note: need to investigate feasibility)*.\n - [ ] UV-tangents *(note: need to investigate feasibility)*.\n\n - [ ] Support partial updates for custom data layers.\n\n - [ ] UV mapping.\n\n - [ ] Mesh UV coordinates.\n - [ ] Mesh UV-tangents.\n - [ ] UV editor coordinate display.\n\n *note: we may run into diminishing returns with UV layer partial updates for custom-data layers, since only updating a single layer will already give us significant benefits. I'd suggest only to support this if it doesn't add a lot of code-complexity.*\n\n- [ ] Multi-object edit-mode\n\n - [ ] Undo optimization: skip mesh conversion for meshes which aren't modified.\n\n- [ ] BMesh support for the modifier stack.\n\n**Milestone 3 - opensubdiv**\n*Fast mesh OpenSubdiv viewport implementation.*\nTime estimate: `?`\n\n**Unknown Milestone**\n\n- [ ] Multi-thread edit-mesh to GPU data uploading.\n- [ ] Improve geometry buffer configuration (data layout used by the draw manager). \n\n\n**Notes:** Optimizing modifiers is out of the scope.\n\n---\n\n**Relevant links**:\n* #57936 (Mesh modeling performance regressions)", "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", "weird unremovable noise which looks like white or semitransparent squares\nWindows GTX NVIDIA 860M Lenovo Y50 laptop 16GB RAM and 2GB VRAM\n\nBroken: (2.77, weird unremovable noise which looks like white or semitransparent squares)\n\n\n**I have horrible flickering noise during my animation and it flickers like a sparks. What causes this noice is alpha images with holes or models of the grids with holes + method of reducing it by using Z and normal passes combined with bilaterural blur (advised by Barteck Skorupa). But i still wanna use it since it still better and only way to properly reduce other types of noice presented in my scene. So this noice looks like SQUARE PIXELS which are flickering during animation. Change of iterations of bilatural blur helps a bit but not completely and not on all frames. \n\nI will give you more info now about this strange things -\n\n\n1- At most frames there is no such noise (because i removed it by using bilateral blur and determinator) but at other frames they are still appear and not despeckle not bilatural blur helps and the weird thing - THEY BECOME MORE VISIBLE AT HIGHER SAMPLES!!!!\n\n\n2 - At some frames this squares are transparent at others - semitransparent or completly white like you can see on the screenshot\n\n\n3 - If i render same image at small samples - like 125 for example - i may not see them at all. But if i change to 150 - they become very visible!!!. \n\n4 - They mostly appear around grids holes models or grids holes alpha images.\n\n\n5- Even if camera not moving they may still appear and look at different frames - differently (white or semitransparent )\n**\n\n\n\n\n\n\n\n\n\n**To reproduce the error you whould probably need to render scene when camera moves and looks directly on grids png images with holes or even models of grids with a holes and also try to use bilatural blur node with determinator + z pass and normal pass combined ro remove noise - since most of the issues appearing when you using this nodes combinations (but its necessarily to use them)**\n\n\nIf you will need a blend file please leave me a comment on [email protected]. Thanks\n", "Un-subdivide operator damages UVs\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha\n\nOriginal\n\nUnsubdivided Level 2\n\n\n[unsubdivide UVs.blend](unsubdivide_UVs.blend)\nPress Ctrl+E / Un-Subdivide\nSet operator to step 2 or 4", "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", "Bevel modifier UV problem with corners\nBroken: 2.79. 2.8*\n\n**Description**\nImportantly for games with Weighted Normals and Bevels workflow it would be very desirable for Corners of UV to scale and connect correctly so there are minimal distortions and UV disconnections. \n\n\nThis is how it opens in max post export:\n\n\nPlease also note that in 2.8 Bevel modifier completely distorts UVs in \"Vertex average\"(and possibly other) Normal Modes. Works as in 2.79 without any normal mode.\n\n\nPrepared debug scene (as requested by Howard): \n\n[debug_bevel_uv.blend](debug_bevel_uv.blend)\nAlso available here: debug_bevel_uv.blend\n\nThank you!\n", "Particle Edit Breaks After Selecting a Mesh with Cloth Physics\nOperating system: macOS 10.13.6\nGraphics card: NVIDIA GeForce GT 650M 1024 MB\n\nBroken: at least 2.82 up to 2.92 experimental (I suspect it never worked since 2.80)\nWorked: 2.79\n\nParticle edit behaves like object edit mode, but the UI shows \"Particle Edit\" being active.\n- There is no circle typical for the comb tool around the mouse cursor.\n- No additional key points to select or black hair strands are rendered.\n- Instead of e.g. combing you will move the object around once you drag with the mouse.\nBasically everything except for the UI stays in \"Object Mode\".\n\nEffect On (broken):\n\n\nEffect Off (works as expected):\n\n\nBased on the default startup:\n1. Go to \"Particle Properties\"\n2. Add a particle system\n3. Set its type to \"Hair\"\n4. Add a second particle system\n5. Set its type to \"Hair\" too\n6. Add a new mesh e.g. \"Plane\"\n7. Go to \"Physics Properties\"\n8. Add \"Cloth\" physics\n9. Select the original \"Cube\" again\n10. Switch mode to \"Particle Edit\"\n\nWays to reverse the effect (make \"Particle Edit\" work properly again):\n- Either: Make a new file and append both objects of the old file\n- Or: Delete one of the particle systems on the \"Cube\" and undo the operation\n\nEven after reversing it you can restore the effect by selecting the \"Plane\" once.\nAt least two particle systems are required for the effect.\n\nThe effect can even be saved and stays the same after loading from the file again.\nThus I was able to create two files one with the effect and one without.\nThe file without the effect is a little bigger in size.\n\n[EffectOn.blend](EffectOn.blend)\n\n[EffectOff.blend](EffectOff.blend)\n\nIt took me a whole day to find the cause and boil it down so far.\nHope it helps and that it can be fixed with the provided info." ]

[ "subdivision surface with UV smooth \"keep corners\" destroys UV/seams\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Alpha\n\n\nwhen applying a subdivision surface modifier with UV smoothing set to \"keep corners\" it rips the UVs and therefore creates additional seems when hitting \"seams from islands\". This seems to be only happening with the \"keep corners\" option, and when the original mesh (before applying the subdiv modifier is appied) is not super low res. The UV islands look visually fine, however has vertices ripped apart. It can be solved by merging by distance with a very low threshold. I tried in official 2.91 release and having the same result there.\n\n\n- apply a subivision modifier with a level 2 to the default cube (already set up in provided scene)\n- in UV editor select all and hit \"seams from islands\"\n- apply a new subdivision modifier with any level to the cube and UV smoothing set to \"keep corners\" (already set up in provided scene, but not applied yet)\n- in edit mode delete all seams\n- in UV editor select all and hit \"seams from islands\"\n- additional seams have been added based on where the vertices in UV got ripped apart\n\n[cube_UV_test.blend](cube_UV_test.blend)\n\n\n", "Multires Modifier: Subdivide / Unsubdivide damages UV\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.4\n\nApplying subdivisions via modifiers ends up in corrupted UV's\n\nWhen you apply a subdiv or multires modifier, it will split the UV's at various areas, creating additional UV edges in the process.\nThis can be easily visualised by tagging Seams in the 3D Viewport.\nTo tag the seams we can use the menu operator `Seams from Islands` in the UV Editor under the menu `UV`.\n\nWe can use the Monkey primitive as an example since it is created with multiple UV islands.\nHere is where Blender tags the Seams before the subdivisions are applied:\n\nAnd when doing the same thing after the modifier is applied it will look like this:\n\n\n\n- Object mode -> Add -> Mesh -> Monkey\n- Add a Subdiv/Multires modifier \n- Subdivide any number of times\n- Apply modifier\n- Switch to the UV Editing workspace\n- Select all vertices of the 3D Viewport\n- In the UV Editor use the menu operator `UV` -> `Seams from Isalnds`\n\nYou will see that the UV islands don't match the tagged seams.\nIf you proceed to drag UV points in the UV Editor around the pupil, you can see that a lot of UV edges have been split when the modifier was applied:\n\n \n" ]

[ "Curve Pen Error\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 4.0.0 Alpha\n\nNothing happened when I left click my mouse using Curve Pen in Edit Mode, but it is fine with blender on my windows laptop.\n\nI added a Bezier and I enter the edit mode, I deleted all the vertices and decided to draw a line using Curve Pen. However, it did not work.\n\n", "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", "Support Attribute Search In Material Nodes\nThe \"Attribute\" node in shader node trees could support attribute search based on the context data. The search code would be generally the same, but the data would be accessed directly from the evaluated geometry set of the active object. \n\nTherefore attribute search should not be used when the node tree is pinned, or alternatively it could depend on the pinned object context of the node editor, if that is available.\n\nNote that fewer attributes are available for EEVEE. There will have to be a special case there until more attribute access is implemented there.\n\nSome starting points / references:\n`node_geometry_attribute_search.cc`\n85421c4fab\nc0b2c75c44\n[D10623: Geometry Nodes: Add domain and data type to attribute search](D10623)", "Split Draw curve tool in two distinct tools [properties of one mode dont make sense for other mode]\nOperating system: Win10 x64\nGraphics card: GTX 1080Ti\n\nBroken: 2.82 - 2.90\n\nDraw Curve F9 \"Error\" slider doesn't do anything if curve is set to Poly\nIn fact, none of the provided settings work\n\n\nMake a new curve\nEdit mode\nUse toolbar draw curve (Toolbar - 9)\nSwitch it's type to Poly in N - Tool - Active tool\nDraw any curve\nF9 to adjust the Error slider - no effect\nOther settings also have no effect\nSwitch mode to Bezier and the slider works", "Unable to select certain vertices (regression from 2.79)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nSome vertices are impossible to select.\n\nAt first I thought it was because the vertices formed a concave area (see first file) but then I hit a second concave case (see second file).\n\n\nWithout rotating or zooming the view try to select one of the marked vertices in both files.\n[Select1.blend](Select1.blend)\n[Select2.blend](Select2.blend)\n\n----\n\n2.79 worked in this case, open this file in 2.79 to test.\n\n[Select1(1)_279.blend](Select1_1__279.blend)", "Geometry Attributes panel in Edit Mode (design pending)\nThis task is going to adding a unified panel for editing attributes of the selected element by value in edit mode. It makes users able to pass arbitrary per-element data to geometry nodes, opening up more possibilities for procedural modeling.\n\nAll data types (int, color etc.) should be supported. \nDomain supports should match selection modes in edit mode (eg. no face corner support for meshes). \n\n## Basic\nAttributes on the active element is listed in the side panel. \nItems are grouped by domain.\n\n\n## Multiple Selection\nfor float types (float, vector, 2d vector): \n* Show a mean value computed from all selected elements. \n* Button offsets values of all selected elements.\nfor other types: \n* If an active element with a matching domain exists, show the value of it.\n* Button only affects the value of the active element.\nFill operators are provided for batch editing. It fills current button value into all selected elements.\n\n", "Knife tool fails on a non-planar n-gon\nBroken: 2.74 up to and including 2.92 master\nWorked: 2.73 (yes, I bisected that far back ;) )\n\n\nKnife tool fails to cut between verts in n-gons of certain configuration.\n\n\nLoad the attached .blend and try to make a knife cut between the two selected verts (i.e. try to create an edge connecting them).\n\n[knife_fail.blend](knife_fail.blend)\n\n(If you want to test in 2.73 yourself, copy the object from a running instance of 2.9x into 2.73 using ctrl+c/ctrl+v, then replace the mesh in another existing mesh object).", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "Blender crash in bmesh.to_mesh() while using it to modify weights\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCrash in bmesh.to_mesh() if using it to modify weights in weightpainting while playing animation\n\n*Remove any lights or cameras, keep just one cube in the scene (for the simple script to work).\n*Subdivide it 5 times and apply the modifier.\n*Add the script below to the script editor and run it\n*Go to weight paint mode for the cube\n*Run the animation and try to paint. If you just click the left mouse button it will paint a dot and the script will work, but if you hold and drag, Blender crashes.\n\n\n```\nimport bpy, bmesh\n\n\ndef add_handler():\n # remove existing handlers\n old_handlers = []\n for h in bpy.app.handlers.frame_change_post:\n if \"paint_test\" in str(h):\n old_handlers.append(h)\n for h in old_handlers: bpy.app.handlers.frame_change_post.remove(h)\n # add new handler\n bpy.app.handlers.frame_change_post.append(paint_test)\n\ndef paint_test(scene):\n for ob in scene.objects:\n me = ob.data\n \n print(str(scene.frame_current) + \": Creating Bmesh\")\n bm = bmesh.new()\n bm.from_mesh(me)\n \n group_index = ob.vertex_groups.active_index\n dvert_lay = bm.verts.layers.deform.active\n \n for vert in bm.verts:\n dvert = vert[dvert_lay]\n try: dvert[group_index] -= 0.1\n except: pass \n \n print(str(scene.frame_current) + \": Writing Bmesh\")\n bm.to_mesh(me)\n bm.free()\n \nadd_handler()\n```", "The button \"Draw Curve\" for Stroke mode Curve probably doesn't work.\nOperating system: Windows 10\nGraphics card: AMD Ryzen 7, 2700, 8-core\n\nBlender Version: 3.0.1\n\nThe button \"Draw Curve\" from properties editor doesn't work.\n\nMy steps:\n1) Add any mesh object.\n2) Change Layout to Texture Paint (Default)\n3) Press + button below \"Mode: Material\". Add \"Base Color\". Press Ok.\n4) Scroll Down parameters to Stroke section. Expand Stroke section.\n4) Change Stroke Method to Curve.\n5) Press Ctrl+RMB button on mesh some times.\n6) Press \"Draw Curve\" button in properties editor - nothing happens!\nBut if I press Enter on my keyboard or Ctrl+LMB on mesh its drawing stroke.", "UV space aware triangulation\nPlease see #102683 for details, since the issue is described and discussed there. The basic suggestion is:\n\n> Add an option to the \"Triangulate Faces\" operator. It currently has Quad/N-gon methods for Beauty, Fixed, Longest edge etc. It seems reasonable to add options for \"Prevent UV overlaps\" and specify the source UV map.\n\n", "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", "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", "Optix fails when geometry nodes instance has animated translation and scale 0 and motion blur is on\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.4.1\n\nRendering will not start. It stops at \"Building OptiX acceleration structure\"\n\n\n\nThe culprit seems to be a combination of animated Translation and Scale 0 together with animated Rotation of the object and motion blur.\n\n\n\nDoesn't work in OptiX. Cuda and CPU both work.\n\nOpen the .blend file and render the frame.\n\n", "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" ]

[ "Mesh from Curve not working on curves beveled by curves\nWindows 10 Pro - version 1803 - build 17134.285\nIntel Core i5-3350p\nNvidia GeForce GTX 780\nRAM DDR3 2x4GB 1333mhz running dual channel\n\nBroken: 2.8 (Downloaded 21. 09. 2018)\nWorked: 2.79\n\nObject Mode > Object > Transform > Mesh from Curve\\Meta\\Surf\\Text\nWhen applied to a curve directly beveled by shape of another curve, it does not create a mesh, only turns the original curve into edges.\n\n- open new file\n- add two bezier curve circles, one bigger and one smaller\n- go to properties panel of the big circle > object data > bevel > choose the second smaller circle as object\n- in the same menu move the \"bevel start\" slider to make the bevel appear, you should have a torus now\n- in 3D view in object mode go to Object > Transform > Mesh from Curve\\Meta\\Surf\\Text\n- **RESULT IN 2.8: Turns the curve into circle of vertices, not a torus mesh.**\n# **RESULT IN 2.79b: Turns the curve into a torus-shaped mesh.**\n\n" ]

[ "Add sticky keys support for accessibility\nOperating system: Windows 10\nGraphics card: Geforce GTX-970m\n\nblender-2.80.0-git.1fa527bfa3a-windows64\n\n\nSticky keys not working properly.\nSfZ7Ua-ReuQ", "Bone's Custom Properties are invisible in the Bone Properties Editor if bone in hidden layer\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\n3.0.0\n\nWhen a bone is selected in the Outliner, but is not on a visible bone layer, its Bone Properties are accessible, but it will not appear to have any Custom Properties.\n\n[BoneBug.blend](BoneBug.blend)\n\n - Open attached file. \n - Select \"Bone B\" in the Outliner.\n - View the properties of Bone B in the Properties Editor. The Custom Properties panel is empty!\n - Go to Armature Properties and enable the hidden layer.\n # Bone B's Custom Property has magically re-emerged.\n\nThis is very misleading!\n", "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", "Formalize Default Selection Behavior and Key-map\nSelection should behave as consistent as possible throughout Blender. There should be a formal description for that to help avoiding inconsistencies.\n\nNOTE: This task is WIP, all content is tentative.\n\nWe *may* have to draw distinctions between right-click vs. left-click and 2D vs. 3D editors. For the latter, there are rather different requirements.\n\n### 2D Editors\n\n| Key-map item | Action\n| ---------------- | --------\n| {key Click} | Select item (and activate) an item. Deselect others.\n| {key Shift Click} | Toggle selection (and activate):\n| | * Select (and activate) if item was *not* selected\n| | * (Activate it item was selected)\n| | * Deselect item (if already active, or) if selected.\n| ... | ...\n\n\n[TODO make table per-tool?]", "Add Keying Set and New Keyframes options to the Timeline Sidebar \nIn Blender 2.8, we made the Timeline simpler by moving many options into popovers. \n\nHowever, there are a few advanced features that some users would like to be able to see at a glance without opening up the popover to check.\n\nWe can support this by adding these items to the Timeline Sidebar, which is currently empty. \n\n\n\nThe main options where this is relevant is the Keying Set option, as well as the New Keyframes setting.\n\nWith this solution, the Timeline can remain simple and uncluttered, but with added complexity if users open the Sidebar. ", "Cannot access add-on user preferences from register if using --addons command line flag\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Beta\n\nAn add-on cannot access its user preferences in the `register()` function if it is activated through the `--addons` command line flag, but has not been manually activated before.\n\n* Install the following add-on stub:\n[test_register.py](test_register.py)\n\n```\nbl_info = {\n \"name\": \"Preference Register Test\",\n \"author\": \"Your Name Here\",\n \"version\": (1, 0),\n \"blender\": (2, 80, 0),\n \"location\": \"\",\n \"description\": \"\",\n \"category\": \"Test\",\n}\n\nimport bpy\n\ndef register():\n addon_prefs = bpy.context.preferences.addons[__name__].preferences\n print(\"Found preferences\")\n\ndef unregister():\n pass\n```\n* Run blender with this command: `blender -b --addons test_register`\n * The add-on fails with the following error:\n```\nTraceback (most recent call last):\n File \"/home/damien/blender-git/build_linux/bin/2.93/scripts/modules/addon_utils.py\", line 386, in enable\n mod.register()\n File \"/home/damien/.config/blender/2.93/scripts/addons/test_register.py\", line 14, in register\n addon_prefs = bpy.context.preferences.addons[__name__].preferences\nKeyError: 'bpy_prop_collection[key]: key \"test_register\" not found'\n```\n* Open Blender, activate the add-on from the User Preferences and save them\n* Run Blender in the background again (`blender -b --addons test_register`)\n * Now the add-on prints the expected `Found preferences`", "Keymap - Different shortcuts & keymaps are mistakenly merged \nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken: Blender 3.0\n\nWhen swapping the Select Edgering and Pick Shortest path operators around in my custom keymap, the two functions were mistakenly merged by Blender, despite being two different operators and despite having different inputs associated. \n[Keymap items disappear.mp4](Keymap_items_disappear.mp4)\n\nAs you can see at the end, there no longer was any keymap with Pick Shortest path within the Mesh category. \nTo further help trouble shooting, these were all the keymap items that had Shift+LMB associated within the Mesh category.\n\n\n**Steps to reproduce**\n1. Go to Edit > Preferences > keymap editor\n2. Load my keymap: [SW_WindowV2_done_a.py](SW_WindowV2_done_a.py) > For some reason it doesn't occur in Blender when factory reset, the only difference with my version is that I added a shortcut to Edit > Preferences > Ctrl + K, changed some navigation settings and loaded my custom theme before saving preferences, so it is very very close to being factory reset.\n2. Go to > 3D view > Mesh > Mesh (Global)\n3. Locate the Edge Ring select and Pick Shortest path entries\n4. Copy the operator names to the clipboard\n5. Replace the \"mesh.shortest_path_pick\" operators with \"mesh.edgering_select\"\n6. Replace the \"mesh.edgering_select\" operators with \"mesh.shortest_path_pick\"\n7. Set the options like the image below:\n\n8. Notice that when the buttons are configured to be the same (shift + LMB), click and double click are merged across two different operators. \n\nSee: [Keymap items disappear - Steps to reproduce.mp4](Keymap_items_disappear_-_Steps_to_reproduce.mp4)\n\nE: This bug also occurs when I remove the old \"mesh.shortest_path_pick\" operators and edit the top two items under 3D view > Mesh > Mesh (Global) to become \"mesh.shortest_path_pick\" with Shift + LMB click and Ctrl+Shift + LMB Click.\n\nAlso, it does not occur if I remove the old operators and add new items to the keymap with these operators.\n[2022-01-17 15-28-30.mp4](2022-01-17_15-28-30.mp4)\n", "Node Tools not exposed in the Preferences > Keymap\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R9 380 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.3.1\n\n**Short description of problem**\nFor the Node Editor keymap, there are hidden Node Tool keymaps that exist within Blender (they are only visible via search filter) that override the keymaps that are exposed, and can't be customized properly.\n\n\n\nThis report stems from this bug report:\nT102422 ", "UI: Cursor flickering when hovering over properties\nBroken: version: 3.0.0 Beta\n\nWhen hovering from one property to another in property area, sometimes cursor changes from <--> to standard cursor. There are no instances where you stop moving it and it stays as standard one - it always changes to <--> after a fraction of a second. UI scaling does not affect it.\n\nNote that when tried without recording problem was more apparent, almost always cursor was flickering.\n[UI Cursor flickering take 2 2021-11-27 10-58-42-112.mp4](UI_Cursor_flickering_take_2_2021-11-27_10-58-42-112.mp4)", "UI: Discussion Topics & Possible To-Do's for 3.0\n3.0 is the next chance to do breaking changes which should not go into normal releases. That may be: higher level design changes, muscle memory breaking, documentation breaking (e.g. changed operator names) or non-trivial visual changes. There should still be no .blend file compatibility breaking changes.\n\nIn this task we can collect such changes for consideration. This is not a \"wish a feature\" list. These are things we discussed already but couldn't do earlier because they would be too disruptive.\n\n* Active vs. selected (#82359 (Stronger binding of Active and Selected))\n* Keymap polish\n\n - Consistent selection with modifier keys #78253 (Formalize Default Selection Behavior and Key-map)\n - {key 1}/{key 2}/{key 3} for changing into vertex/edge/face edit mode #88071 (Keymap: use number keys for mode switching (2nd Iteration))\n - {key D} for view-navigation sub-menu #88092 (Keymap: use D-key for view navigation pie-menu (2nd iteration)).\n - {key Alt} usage #83689 (Default Keymap Update: Improve tool access using Alt-LMB)\n\n* Toolsystem wrap-up (change toolsystem defaults if needed)\n* Theme polish (#74358)\n* General defaults (Preferences, startup configuration, bundled workspaces, etc)\n - [ ] Set default subdivision modifier levels to be 1 for viewport and render.\n* More dynamic file selection (e.g. show import/export settings based on file selection)\n* Reevaluate closing popups on mouse moves.\n* Improve naming:\n**Avoid \"link\" for anything unrelated to link/append (e.g. *Link Materials* -> *Share Materials*).** Correct usages of \"copy\" (e.g. *Copy Modifiers* -> *Replace Modifiers*).\n* 3D cursor default orientation method to \"Surface\"\n* #89266 (Investigate renaming the \"Video Sequencer\" editor)\n* #83612 (UI: Tracking: Migrate to active tools based toolbar)", "Add error message feedback on constraints, similar to what already exists for modifiers.\nCurrently de-activated constraints only show their status through a small red icon. It would be better for users to also show an error message explaining what is the issue, similar to what modifiers already do.\n\nSee e.g. the invalid settings for the IK constraint of the first bone in this file from #100128: [lib.blend](lib.blend)", "Search Filter, when used, vanishes collapsed modifiers headers texts.\nOperating system: Linux-6.4.6-76060406-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05\n\nBroken: version: 3.6.2\n\nSearch Filter, when used, vanishes collapsed modifiers headers texts.\n\n\n\n<video src=\"attachment\" title=\"Peek 2023-08-23 15-53.mp4\" controls></video>\n\nType any text in the search filter for some object with a bunch of modifiers collapsed and the texts on the box are gone. They are only displayed if modifiers are expanded.\n\n", "Pie menu assigned buttons freezes switching during mouse movement\nOperating system: Linux Mint\n\n\nBroken: 2.8 official\nWorked: 2.79\n\nZ, Tab and ` by default calls pie menu.\nEven if pie menu is disabled in keymap, they seems to wait for pie menu drag before switch their mode, so they sticks while mouse is moved.\n\nSteps to reproduce:\n\n1) Remove Shading checkbox assignment (VIEW3D_MT_shading_pie) from Z key\n2) Spam Z in 3D viewport\n\n3) If \"pie menu on drag\" checkbox is on\n\n 3a) When mouse is still, Z switches wireframe mode immediately\n\n 3b) When mouse is moving, Z stops switching.\n\n4) If \"pie menu on drag\" checkbox is off, Z key stops switch wireframe mode at all.\n\nGIF to compare 3a and 3b:\n\n\n\nGif to reproduce 4:\n\n\n\n", "Custom Node Trees: Selected node tree is lost when editor is switched to other node editors\n1. Run the official Custom Nodes Python template\n2. Switch to the newly registered Custom Node Tree editor\n3. Create a node tree\n4. Switch to another node editor (Shader Editor for example)\n5. Switch back to the custom node tree editor\n6. The selected node tree was switched back to None", "After setting a shortcut for the \"Auto Keyframe\" button, there is an exception in the status display.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\nWorked: none\n\nSee below\n\nUse right click->assign shortcut key\nCreate a shortcut for the auto keyframe button e.g. ctrl+alt+n\nThen test the shortcut in a different viewport and you will see that it looks like nothing is happening.\nBut,**The auto keyframe state is actually changed**, but the button display is not refreshed, and the button dispaly state is changed only when the mouse moves to the timeline window.\n\n" ]

[ "Imported key configurations are missing the preference menu\n**System Information:**\nCPU: Ryzen 5 2600\nGPU: RX 570 4GB\nOS: Windows 10 Home\n\n**Blender Version:**\nBroken: Blender 2.8 Beta 925380050d0\n\n**Short description of error:**\nExported key configurations don't appear to save the \"preferences\" tab and thus when imported are missing the \"preference\" tab and ignores information that should of been saved when exporting the key configuration.\n\n**Exact steps for others to reproduce the error:**\n1. Open user preferences (Edit>Preferences).\n2. In the user preferences change to the input tab, notice the preference tab.\n\n3. Export your key configuration using the \"Export Key Configuration\" button and re-important it using the \"Import Key Configuration\" button.\n4. Notice that the preference tab is missing. It also appears that any settings in the preference tab is ignored (*presumably because they don't exist in the original file*) and the preferences from the previously selected keyboard configuration will be used instead. (*You may also notice that the bottom bar is now on the top, this is a bug for a different report if you wish to make it*)\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", "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", "Blender 3.1 CPU/GPU rendering denoise is broken on M1 Mac / Monterey\nOperating system: MacOS Monterey (M1 Max)\nGraphics card: Integrated GPU\n\n**Blender Version** 3.1.0 release for M1 Macs\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (newest version of Blender that worked as expected) 2.93.3\n\nOn all my projects, when rendering via the CPU or GPU, the render works as expected, but on completion the entire screen blacks out to a solid color and the render is LOST! I suspected it must be a post render step, and I have confirmed that it is the DENOISER that is broken in this version of blender. When I go into the scene and remove the denoiser, the render completes, and I can save the image!\n\nBased on the default startup or an attached .blend file (as simple as possible).\nYou need a project that uses denoising as a final compositing step. Attached is a simple matt object set to denoise at the end. Render it, and at the end you get a gray screen. Go into compositing and remove the denoise node, and you get the render.[TestRenderWithDenoise.blend](TestRenderWithDenoise.blend)\n", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Cycles Shadow Catcher Creating Multiple Shadows\nHi,\n\nThis .blend file will demonstrate two shadow catchers overlapping each other and creating double shadows. It would perhaps be interesting to add a termination value for the amount of shadows cast or just removed entirely.\n\n\nThanks!\nBeau\n\nSystem:\nWindows 10 64 bit\n\nBlender 2.79b f4dc9f9d68b\n\n\n\n\n\n[shadow_catcher_double_shadows.blend](shadow_catcher_double_shadows.blend)", "just activating osl, without using it, makes any render 3 to 4 times slower\nWin7 x64\n\nBroken: 2.76b\n\nTake any prodution render with CPU, just activate osl in the render tab, it will render \" to 4 time slower, without using it in the scene. Compared to GPU render wich is already 5 times faster than a cpu render, it is = 15 to 20 times slower. OSL is unusable with this bug. Note that other renderer with OSL don't have this speed hit.\n\nWith CPU and 16x16 tiles, render this scene: pabellon_barcelona_v1.scene_.zip\nthen just activate osl, render again and compare times. although there isn't any use of OSL in the scene, the render times crawls down.\n(you can also lower the samples to 10 to make it faster for both render)", "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", "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", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)", "gpu.states.line_width_set doesn't work (on Mac Air)\nOperating system:\nGraphics card:\n(just copy pasted specs here)\n Model Name:\tMacBook Air\n Model Identifier:\tMacBookAir7,2\n Processor Name:\tDual-Core Intel Core i5\n Processor Speed:\t1,8 GHz\n Number of Processors:\t1\n Total Number of Cores:\t2\n L2 Cache (per Core):\t256 KB\n L3 Cache:\t3 MB\n Hyper-Threading Technology:\tEnabled\n Memory:\t8 GB\nIntel HD Graphics 6000:\n\n Chipset Model:\tIntel HD Graphics 6000\n Type:\tGPU\n Bus:\tBuilt-In\n VRAM (Dynamic, Max):\t1536 MB\n Vendor:\tIntel\n Device ID:\t0x1626\n Revision ID:\t0x0009\n Metal Family:\tSupported, Metal GPUFamily macOS 1\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nBlender 3.6\n??\nOn this specific Macbook, gpu.states.line_width_set simply does nothing - Just tested also on WIndows and there it works.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nJust try the 'Operator Modal Draw' Template in Python templates in Blender text editor - the function is used there so it's very fast to check.\n\nAnd yes, I know this is probably outdated hardware, but didn't want to not report bug if I already found one ;)\n\n", "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\n\n", "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", "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\n\n", "Unable to output pictures correctly when rendering version 3.2 demo with 65536*65536 resolution\nOperating system:win11 -workstationedition\nGraphics card:4090\n\nBroken: 3.4.0 release\nWorked: \n\nUnable to output pictures correctly when rendering version 3.2 demo with 65536 * 65536 resolution.\nWhen nearly 4 hours of rendering ends, blender does not work any picture out, as the picture atteched. And the image attribute say this image is 32768 * 32768.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nusing the dome file for blender3.2\n\n" ]

[ "Cycles not using both NUMA Nodes on Dual Xeon Setup\nOperating system: Windows 7 pro 64bit\nCPU: 2*Intel Xeon e5-2696v3\n\nBroken: 2.80.xx\nWorked: 2.79\n\nWhen i render, Cycles wont use both NUMA Nodes (or CPU Groups) but only one. Even if i change from \"Auto detect\" to \"Fixed\" and fill in \"72\" inside the Performance-Tab, it spawns 72 Buckets but will actually use only 36 CPU Threads. While the auto detect option also didnt work in 2.79, the \"fixed\" parameter worked and used all 72 Threads for rendering.\n\nSince this occurs only on this machine and not my second one (only 48 threads), my guess is that this is an issue with Windows CPU Grouping that will split everything that exceeds 64 Threads into Groups. If a software is not aware of this, they can only use one NUMA Node (or cpu Group). In my case that would be exactly 36 Threads.\n" ]

[ "Inconsistency of some tools/operators (e.g. Subdivide) in regards to hidden geometry\nBroken: all or none\n\nI'm not really sure this is even an issue, though it feels like it. As far as I understand it, mesh editing tools are not supposed to affect hidden geometry. But the Subdivide tool does. Consider this mesh:\n\n\nIf you hide the middle face...\n\n\n...and then Subdivide the two remaining faces...\n\n\n...Subdivide will create new edges cutting through the hidden face, also creating inconsistent selection (i.e. selected edges in face select mode). Shouldn't the operator check that that face is hidden and not create edges through it?", "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", "Wireframe modifier strange behaviour\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.2\n\nStrange behaviour from wireframe modifier\n\n\nTook a plane and subdivided, added a wireframe modifier, unsubdivided. Some corner vertices are pushed to the edge of scene.\n[Based on the default startup or an attached .blend file (as simple as possible)][Wireframe.BugReport.blend](Wireframe.BugReport.blend)\n\n", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "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", "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", "Toggling Autosmooth changes evaluated bbox `obj.bound_box` when SUBSURF mod (using GPU subd) is present\nOperating system: Linux-6.2.0-76060200-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.5.0\nWorked: -\n\nOn a mesh object with a SUBSURF mod active (using GPU Subdivision), the (evaluated) bounding box at `obj.bound_box` will only produce the correct coordinates when `obj.data.use_auto_smooth` is enabled. Otherwise it will be produce the coordinates of the original mesh bounding box, even though the evaluated mesh is clearly smaller, and so the bbox should be too.\n\nThat makes relying on `obj.bound_box` impossible, when working with the bounding box and assuming it represents the evaluated mesh object.\n\nInterestingly, boolean mods don't share this behavior, the bbox created using booleans, works properly with either auto smooth setting.\n\nSee watch?v=KKnWbRL5h7o for demonstration\n\n\n* open the attached blend file\n* toggle Autosmooth and see the bound box change, even though the evaluated mesh displayed does not change at all.\n\n", "Asymmetric boolean union\nOperating system: Windows 10 Pro 10.0.19041 N/A Build 19041\nGraphics card: Intel HD Graphics 520\n\nBroken: 2.93.1 (22 June)\n\nIncorrect output of boolean operations on meshes.\n\nThis bug report is going to expose many more flaws in my understanding of Blender than in Blender itself! But as per Howard_Trickey's comment, 2 Sep 2020 on 160, I'm adding this data point to aid debugging, and if I can get any advice, so much the better.\n\n[AsymmetricUnion.blend](AsymmetricUnion.blend)\nThe attached file contains two mesh objects. If you select \"Verticals\" and then add a modifier to \"union\" it with \"Horizontals,\" then the result is calculated correctly. However, if you do this in reverse—select \"Horizontals\" and union it with \"Verticals\"—then the result is missing some pieces.\n\nIn this case, of course, the obvious fix is to just do it the first way! However, this minimal example is part of a scripted sequence with lots of Boolean operations, and if I can find out why this (the second method) is failing, there might be some hope of getting the script as a whole producing the right output.\n\nI've tried I think every permutation of fast/exact, self and hole tolerant.\n\nAfter looking through some of 160, I've also tried joining the two objects into one, and then calculating the self intersection under edit mode rather than via a modifier, and that DOES work correctly. Are the modifier booleans still the old code, before Howard's marathon revamp of the boolean calculations? In that case I may be fine just using the edit mode functionality, if it's all exposed in the Python API. I can't see how to find the intersection or difference of two meshes via edit mode though; there are buttons for the three boolean operations, but I don't see how to specify the second operand.\n\nThanks!", "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", "Viewport Z-Bias & retopology overlay related issues\nSince this is being reported frequently and retopology overly has caused some weird issue with mask display as well previously, it's best we keep track of them in a central place so we could check if any particular fix is working for all situations:\n\n------\n\nProblem still presents:\n\n- Retopology overlay affecting other parts of the drawing/picking operation: #109115 #107768 ~~#109277~~ ~~#107411~~\n- (Potentially related) Selecting when X-Ray turned on is not visually effective and then switching to face mode crashes: #110136\n\n------\n\nFixed:\n\n- ~~Wireframe visible in close distances: #110048 #109040 #109514 #109499 #109685~~\n- ~~Retopology overlay 0 z offset problem: #109662~~\n\n-------\n\nProbable cause:\n\nAs suggested in 107768#issuecomment-937545 , I believe the problem here is that\n\n1. `DRW_object_is_in_edit_mode` does not exclusively check if object is in edit mode, but it combines other logics that affects drawing and stuff.\n2. `XRAY_ENABLED` marco is not always accompanied with `RETOPOLOGY_ENABLED`, this leads to inconsistencies in the user interaction and the display.", "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", "Advancing Displace and Solidify modifiers to handle overlaps\nI briefly discussed this with C. Barton. I often I solidify and displace surfaces in the processes I work on -- recently for 3d printing custom assistance devices including molds for casting rubber, customized computer peripherals, etc. Whether or not they use clear-cut geometric forms, or are of organic nature, they often succumb to the issue of intersections with displace/solidify. I've wanted to work out some details on processes which would enhance these modifiers, but need some help. I'd attempt to implement it so it would be inactive normally, and use thresholds when enabled, so as not to slow down the normal modifier functionality, and a require a minimum processing when the features are used.\n\nThe main issue I'm having is that the modifiers do not presently have access to information on adjacent vertices, and my first approach to an algorithm would examine, with some function fn(vertex_normal, displacement_amount), if there would be a crossing (e.g. if faces would intersect). Then the simplest method would angle the normals away from each other. However, this does all require the ability to examine adjacency, and I'm relatively inexperienced in blender internals, having only contributed minor bits to sculpting tools and physics code. Your guidance would be appreciated.\n\n", "Bevel when part of mesh is hidden results sometimes in wrong selection of vertices\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 3.2.0 Alpha\nalso broken in the latest official release of version 3.1.2, also broken in 2.93.\n\nBevel when part of the mesh is hidden and the selected points are not all connected results sometimes in the wrong selection of vertices and lines. I have noticed that the selection is wrong if the number of segments in the bevel attrributes is odd.\n\nOn the default startup file do the following:\n1. Edit the default cube, inset the top and bottom face \n2. Inset again, but only 0.001 \n3. Scale the selection in the Z by 0, \n4. Expand the selection (CTRL++)\n\n5. Shift+H to hide everything currently not selected\n6. Only select the top and bottom \n7. Try beveling, play a little with the segments and switch between vertex and line selection, you will see that not all the lines and not all the vertices that should be selected are selected. It seems to be wrong when you try odd number of segments\n\n\n\n\n\n\n\n", "Modifiers header misalignment on change Resolution Scale [pixel perfect thing]\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5161\n\nBroken: version: 2.92.0; blender-2.90.0-d7c4e9649320\nWorked: don't know\n\nModifiers/Constraints header buttons misalignment on different (especially smaller) Resolution Scale value\n\nSimple as that. Tried set Resolution Scale down on a notebook, and saw the modifier name input \"jump\" out of the modifier box.\nSo checked that any value bellow 1, varnishes the \"top margin\" of it. The same on constraints, bones included.\nThan i suppose it has something to do with the dragging feature.\n\nOpen Blender.\nAdd any modifier/constraint an object.\nGo to Preferences -> Interface -> Display -> Resolution scale, and click the input's left arrow.\nSe the bug on the modifier header\n\n\n\n", "Modifier sub-panel drawn over selection outline\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.1.0 Alpha\n\nThis is just a visual bug and nothing serious, but I wanted to point out that the sub-panel background is drawn on top of the selected modifier outline, which causes it to look broken up when expanded. This is visible but not obvious in the default theme, but very obvious in custom themes where the sub-background alpha is set to 1. \n\n\n\n1. Add a Bevel or Subdiv modifier\n2. Expand a sub-panel \n3. Set the properties editor Sub Background theme color to an alpha of 1 \n\n" ]

[ "BMesh booleans fail with holes\nBroken: 2.79 and 2.8 all version. Latest checked version 2.8 9541ce2c261b\nSystem: windows 10 x64, GTX 1050 4GB\nI use the boolean modifier very often. Since its introduction BMesh Solver, I have problems with boolean modifier. \nBMesh Solver can't do the same as Carve Solver. Very often a hole appears in place of a boolean or nothing happens, a boolean does not work. But Carve Solver works fine with same geometries. And this happens again and again with BMesh Solver in 2.8\n\n\n\nIn blendfile switch on/off Bevel modifier, and switch on/off Boolean modifier.\n\n[BMsesh Solver.blend](BMsesh_Solver.blend)" ]

[ "Invisible object in preview mode\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon HD 8600/8700M ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0\n\nWhen I enable Material Preview mode in Blender, the object becomes invisible regardless of the Render Engine. Also the object is invisible with Rendered mode enabled when I use the Render Engine - Eevee. \n\nI don't know how it happened but I can't repair Blender. I reset all settings to factory, reinstalled the application, but it did not help. Can you help me, please?\n\n\n\n\n\n\n\n\n\n", "Make Links > Objects to Scene: Does not changes origing point color. We have no visual indication!\nOperating system: Linux-5.11.0-7620-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 2.93.2\n\n\n\n\nIn 2.79 it was visually distinguishable per scene linked objects by a bluish tinted origin point but this behavior is missing since 2.8 series has started (for no apparent reason).\n\nThis visual feedback is very important. It basically tells you:\nHey! If you touch me, you change me in all scenes I'm living at! Be aware!\n\nAnd the fact now I have remember what can I touch and what I can't, since my project is increasing in complexity, is overwhelming.\nYou might say: use library overrides then! But no, these are different features and both accomplish different purposes and they can keep coexisting. (unless we could now make a library override for a datablock in the same file, but that is not the case).\n\nAlso, the 2.93 manual states the expected behavior:\n\nBut this is not the case anymore for a while!\nI have been silently waiting for this to be fixed but its time to ask our dear developers to take a look onto this. Please, bring it back!\nOr maybe even enabling the ability to define a different outline color too. (honestly a tinted dot for me is enough)\n\nBest regards,\nJulio.\n\n", "Linked Instances Across Scenes have unreliable updates when editing their common mesh data.\n\nBroken: 2.93.4 LTS;\nBroken: master\n\nWith two different objects in two different scenes sharing a same obdata Mesh, editing the mesh in one of the scene can fail to properly update object in the other scene.\n\n- Open attached file.\n- Go to scene 2.\n- Switch to Edit mode.\n- Assign the red material (first slot) to the cube in edit mode.\n- Switch back to Object mode.\n- Go to Scene 1, the Cube in Scene one still uses the second slot material (green).\n# Switch to edit mode and back, now the cube is shown with expected first material slot (red) as well.\n\nNOTE: If you replace step 4 by a mesh geometry editing (e.g. rotate the mesh in Edit mode), in current master there is the same missing update issue in Scene 1, but in 2.93LTS it is properly updated... Regression introduced by 51568030e9.\n\n[Example.blend](Example.blend)\n\n------------------------\n\n# Original report\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.0\n\nIf you link an instanced object to another scene, having it's material link to object, it can have a different material from the non-instance. However upon saving and re-opening the scene, the instance's material will revert to that of the non-instance. \n\n- Open attached file or\n - Take the default cube and assign a material to it. In the viewport display settings assign a color for the material, this will give feedback in the viewport to highlight the issue. \n - Create another material on the same cube and once again assign a color in the viewport display settings.\n - Set both materials to Object Link in the material properties. \n - Name the current scene \"Scene 1\" and proceed to create another scene named \"Scene 2\".\n - Return to Scene 1, and using Alt+D instance the cube.\n - Using Ctrl+ L, link the instance to Scene 2. Delete the newly created instance in Scene 1.\n- In Scene 2, assign the instance a different material than Scene 1 in edit mode. You now have 2 scenes, with 2 cubes that share mesh data, but that are using 2 different materials. This is the desired goal in practice.\n- Save the file and re-open it. Blender will have automatically assigned both cubes to 1 material.\n[Example.blend](Example.blend)\n", "Two materials: volumetric being in second slot causes error in EEVEE\nOperating system: Windows 10 64 bit\nGraphics card: Intel HD Graphics\n\nBroken: 2.90.1\nWorked: IDK, but I've been using blender since 2.79 and have not encountered this problem when I have done this kind of thing.\n\nWhen I have a mesh object that has both solid and Volume Scatter materials on it (in different slots), in EEVEE, the volumetric material only works if it is not in the second slot. If it is in the second slot (top down), it causes the black \"shader missing\" to be applied. Moving the volume slot up to the top with the solid material in the slot at the bottom causes normal operation.\n\nGo into edit mode on the default cube.\nDuplicate the mesh, but leave it at 0 0 0. Scale the duplicate up a little.\nCreate a second material slot, and assign the duplicate larger cube to it. Leave edit mode.\nCreate a \"Volume Scatter\" material for the second slot. The outer cube will turn black.\nMove volumetric material up in list of materials. The outer cube will change to the proper fuzzy grey.\n\n[#83538.blend](T83538.blend)\n", "Hair density maps increases hair children amount on reopening scene file (or rendering which will get slow)\nOperating system: window 10\nGraphics card: 2080 Ti\n\n**blender 2.93.00**\n\nWorked: dont know when it worked\n\nHair density changes on reopening scene file\n\n- Open the attached file and first turn of and turn on and of interpolated children\n- see how the density changes. The number of children increases. \n- save the file and reopen it to see that its back to a lower number of children. \n- affects both viewport and offline render \n\nTest File\n[Hair_Density_bug_01.blend](Hair_Density_bug_01.blend)\n\n", "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)", "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", "Objects colors bug\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.0.0\n\nWhen change frame colors are rebuilding... When there was less objects was no problems. I can upload this file if you need.\nSee in video. \n[2022-01-25 18-51-54.flv](2022-01-25_18-51-54.flv)\n\n[#95200.blend](T95200.blend)\n- Open file\n- Scrub timeline\n\nColor of objects will change. In original file ([F12825448](ADS-800-CDC_монтаж_ушка.rar)) color would change even to black.\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", "Particle Info Node does not return particle information in light nodes\nOperating system: Windows 10 Home\nGraphics card: Nvidia GTX 1080 \n\nBroken: 3.2.0 e05e1e369187\nWorked: N/A\n\n\nThe [Particle Info Node](particle_info.html) does not properly output values when used inside light nodes. It outputs the same values for all particles regardless of index, age, or position.\n\nNote that driving material properties of particles does work as expected. This problem seems to only be for lights using the \"Use Nodes\" cycles feature.\n\n\n\n1. Set the render mode to cycles\n1. Add a collection with a light in it\n1. Enable light nodes\n1. Import the \"Particle Info Node\" into the node graph and use one of the per-particle values to drive the color of the \"Light Output\" node\n1. Add a particle emitter\n1. Set the particle to the collection that houses the light\n1. Add a surface to cast light onto\n1. Render using cycles\n\nIn the attached `.blend` file each particle (rendered from frame 50) is expected to have a different light color. However, all lights within the particles are emitting the same color (see attached render).\n\n", "Can't Animate Texture Mapping Offset For Particle Hair\nWindow 7 64bit 8gb\nnvidia 660\n\nBroken: 2.72 RC\nWorked: I thought this was possible all the way back into the 2.4 series.\n\nAdd a single keyframe to particle texture mapping coordinates.\nMove to another frame and type a new number in the *Offset* mapping field and it will jump back to the number of the first keyframe.\nIn this state there is no way to animate the*Offset*. Even if I insert the same value at the new time location and edit the value in the graph editor the system still refuses to use the *Offset*information for the particle system hair density.\n\nOpen the Attached BLEND file and type a new number in the *X Offset* field.\nThe system refuses to accept the input and resets to the keyframe value.\n\nNOTE: This seems to only be a problem in the *Offset* and *Size* properties for Mapping. You will also see in the BLEND file that I have successfully keyframed the R value of the RGB without experiencing the same problem.\n\n[27_sequin_star_curtain_1a.blend](27_sequin_star_curtain_1a.blend)\n", "In Particle Edit mode, Emitter particles are not visible in the viewport\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.83 (sub 0)\nWorked: 2.79.7, 2.79b\n\nThe Particle Edit mode does not work with Emitter type particle. The particle (particle paths) are not visible in the viewport.\n\n- Open this file: [#73168-particle-edit-crash.blend](T73168-particle-edit-crash.blend) (or add a particle system, Emitter type, and bake to memory)\n- Switch to \"Particle Edit\" mode (particle disappear).\n- Click on Sidebar > \"Tool\" > \"Options\" > \"Viewport Display\" > \"Particles\" (blender crash).\n\nReports:\n\n[blender.crash.txt](blender.crash.txt)\n[macos.crash.txt](macos.crash.txt)", "Particle hair (chilrden) not showing up on viewport - Blender 3.1\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15\n\nBroken: version: 3.1.2\nWorked: 3.0.1\n\nHey guys, Not sure if I am doing something wrong but on 3.1 + 3.1.2. hair particles are not showing up after a certain number on the \"display amounts\" - For the attached project for example if I go beyond 16 on the display amounts, all the hair disappears. The same happens if I increase the Stand steps on the Viewport Display panel\n\nmay that be a bug ? I am not sure, it looks like one because in 3.0 the problem does not appear. \n\n\nIncrease the number of the Children Display amount.\n\nthanks a lot! \n\n\n[hair-particles-issue-Mac-AMD-3-1.blend](hair-particles-issue-Mac-AMD-3-1.blend)", "Remove unused slots fails with non-mesh objects\nOperating system: all\nGraphics card: all\n\nBroken: 2.83 2.93 3.0daily \n\nwhen object type is Volume or metaball click remove unused slots button.\nWill delete all material slot whether the material been used.\n\nbut if object type is mesh, this action will keep the used \n\n- Open .blend file\n- Material properties tab -> materials specials -> remove unused slots button\n\nTest File:\n[#90338.blend](T90338.blend)", "Particle Edit Breaks After Selecting a Mesh with Cloth Physics\nOperating system: macOS 10.13.6\nGraphics card: NVIDIA GeForce GT 650M 1024 MB\n\nBroken: at least 2.82 up to 2.92 experimental (I suspect it never worked since 2.80)\nWorked: 2.79\n\nParticle edit behaves like object edit mode, but the UI shows \"Particle Edit\" being active.\n- There is no circle typical for the comb tool around the mouse cursor.\n- No additional key points to select or black hair strands are rendered.\n- Instead of e.g. combing you will move the object around once you drag with the mouse.\nBasically everything except for the UI stays in \"Object Mode\".\n\nEffect On (broken):\n\n\nEffect Off (works as expected):\n\n\nBased on the default startup:\n1. Go to \"Particle Properties\"\n2. Add a particle system\n3. Set its type to \"Hair\"\n4. Add a second particle system\n5. Set its type to \"Hair\" too\n6. Add a new mesh e.g. \"Plane\"\n7. Go to \"Physics Properties\"\n8. Add \"Cloth\" physics\n9. Select the original \"Cube\" again\n10. Switch mode to \"Particle Edit\"\n\nWays to reverse the effect (make \"Particle Edit\" work properly again):\n- Either: Make a new file and append both objects of the old file\n- Or: Delete one of the particle systems on the \"Cube\" and undo the operation\n\nEven after reversing it you can restore the effect by selecting the \"Plane\" once.\nAt least two particle systems are required for the effect.\n\nThe effect can even be saved and stays the same after loading from the file again.\nThus I was able to create two files one with the effect and one without.\nThe file without the effect is a little bigger in size.\n\n[EffectOn.blend](EffectOn.blend)\n\n[EffectOff.blend](EffectOff.blend)\n\nIt took me a whole day to find the cause and boil it down so far.\nHope it helps and that it can be fixed with the provided info." ]

[ "particle hair color abnormality \nOperating system: windows 10\nGraphics card: RTX 2060\n\nBroken: blender 2.90 and above, including 2.93A\nWorked: blender 2.83 LTS\n\nthere are 3 planes, each plane has two particle hair systems. the particle hairs that on the same plane has the same material. \nin blender 2.83 LTS. the color display as intended. since 2.90, when both hair system are active, the color is mix with others of different planes and different materials. if either one of the hair systems that on the same plane is disable, the color return to normal. in 2.83 it looks right, but in 2.90 and above, the blue and green materials also mix with red somehow.\n\n\n\n\n\n\nopen attached blend file in 290 and above, switch to preview render to see the color mixed within different materials. \nchange the color_ramp.interpolation to different type from each other would fix the issue, for example, mat1's color_ramp.interpolation to linear, mat2's color_ramp.interpolation to ease, mat3's color_ramp.interpolation to cardinal\n \n\n[particle hair color.blend](particle_hair_color.blend)", "Some hair particles are rendered the wrong material in EEVEE\nOperating system: Windows 10\nGraphics card: GTX 1060 6GB\n\nBroken: 2.90, ee5c2f6ead37, master, 2020-07-11\nWorked: 2.83.2\n\nCaused by b18c2a3c41\n\nthere are 3 planes, each plane has two particle hair systems. the particle hairs that on the same plane has the same material. \nin blender 2.83 LTS. the color display as intended. since 2.90, when both hair system are active, the color is mix with others of different planes and different materials. if either one of the hair systems that on the same plane is disable, the color return to normal. in 2.83 it looks right, but in 2.90 and above, the blue and green materials also mix with red somehow.\n\n\n\n\n\n\nopen attached blend file in 290 and above, switch to preview render to see the color mixed within different materials. \nchange the color_ramp.interpolation to different type from each other would fix the issue, for example, mat1's color_ramp.interpolation to linear, mat2's color_ramp.interpolation to ease, mat3's color_ramp.interpolation to cardinal\n \n\n[particle hair color.blend](particle_hair_color.blend)\n\n\nSome of the hair particles (the right eyebrow specifically) in the provided file are shaded with other material, unless some of the other objects are hidden (the left eyebrow or both eyelashes)**\n\n1. Open the attached .blend file.\n2. Make sure viewport shading is set to Material Preview Mode.\n3. Notice the hair of the object to your right is rendered with the wrong material in EEVEE.\n4. Disable \"eyebrow scalp.R\" from the viewport.\n5. Notice that the eyebrow that was previously being rendered with the wrong material is now correct.\n\nNote that this is not the same issue as described in [this issue ](T68548), the provided file used to work on older blender versions and the scale of the objects is always positive.\n\n[hair_material_bug.blend](hair_material_bug.blend)" ]

[ "Modal Operator Breaks on Workspace Change\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83.0\nBroken: 2.82.7\nBroken: 2.81.16\n\nWorked: 2.79b\n\nModal Operators appear to break when changing work spaces or fullscreening a window space.\n\nOpen attached file\nRun script (OperatorModalDraw.py)\nIn view3D run operator\nEither change workspace or RClick the header to maximize the view3D. \nDrawing broken and a console error is thrown persistently: \"internal error: modal gizmo-map handler has invalid area\". This message is only shown for 2.83.\n\n[bug_op_modal_fullscreen.mp4](bug_op_modal_fullscreen.mp4)\n\nBlend file: [modal_op_fullscreen.blend](modal_op_fullscreen.blend) \nIt's an empty scene. The script used is the template Operator Modal Draw with a few minor changes to allow events to pass through and to not end on L/RClick. \n\n", "Link-drag-search unsupported in texture node editor\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\nWorked: 3.0.0, since there is no such feature.\n\n\"Auto-completion/search\" is not working as intended with Texture Node Editor. For some reason, only reroutes are being displayed. [2022-11-23 22-42-21_1.mp4](2022-11-23_22-42-21_1.mp4)\n\nOpen Texture Node Editor -> Drag from any socket.\n\nNote: sorry for the incorrect spelling of word \"reroute\"\n", "Reload Image (in Image Texture Node) not worked with Cycles selected. bpy.ops.image.reload()\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.1\nAlso not working in 3.6 beta\n\nReload Image (in Image Texture Node) not worked with Cycles. bpy.ops.image.reload()\nIf Cycles selected as active render - it's not working, but if set to Workbench or Eevee - all works fine.\n\n1. Create a plane, assign a texture. Set render to Cycles in settings and in viewport active render.\n2. Change texture, press reload image button - the texture won't change.\n\nSee video in attach for preview.", "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related.", "Cycles: Viewport rendering is restarted when selecting bone in a rig with drivers\nOperating system: Linux-5.15.11-76051511-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: Unsure, possibly never\n\nWhen selecting bones or objects in very simple cases, the Cycles viewport rendering is not interrupted.\nHowever, if the armature has any drivers on it, selecting a bone will restart the viewport rendering.\n\n- File: [re_render_on_bone_select_with_drivers.blend](re_render_on_bone_select_with_drivers.blend)\n- Start viewport rendering.\n- Select one bone or another.\n- Viewport rendering is restarted on every selection.\n\n- Remove the driver from the bone's X location.\n- Issue is gone.", "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", "Assert/crash during COW phase of depsgraph evaluation due to mismatch mask info in code updating mesh data from multires subdiv ccg runtime data.\nFound after fixing #84002 (Sculpt: Masking operations crash if multires is in play).\n\n`BLI_assert(grid_element.mask != NULL)` in `multires_reshape_assign_final_coords_from_ccg()` will fail after undoing from Sculpt mode to Object mode, since in Object mode mesh data does not have paint mask cdlayers yet (it is added when switching to Sculpt mode), while runtime `subdiv_ccg` coming from sculpt undo step does.\n\nWill commit a temp workaround to make Blender usable, but not sure at all if this is actually valid/expected situation, or if there are more layers of worms in that giant barrel. Need @Sergey's enlightenment here, both on depsgraph side and multires side of the question.\n\nSteps to reproduce:\n- Default startup cube\n- Add multires, subdivide at least once.\n- Switch to sculpt mode, draw a sculpt stroke.\n- Undo twice to object mode\n\nAnd it asserts:\n\n```\n1 __GI_raise raise.c 50 0x7fae6ac53c81 \n2 __GI_abort abort.c 79 0x7fae6ac3d537 \n3 _BLI_assert_abort BLI_assert.c 50 0x290e6d84 \n4 multires_reshape_assign_final_coords_from_ccg multires_reshape_ccg.c 78 0x1091bc37 \n5 multiresModifier_reshapeFromCCG multires_reshape.c 158 0x1091613b \n6 object_update_from_subsurf_ccg object.c 1476 0x109bcc4d \n7 BKE_object_free_derived_caches object.c 1557 0x109bd60d \n8 blender::deg::ObjectRuntimeBackup::restore_to_object deg_eval_runtime_backup_object.cc 112 0x28d41ddc \n9 blender::deg::RuntimeBackup::restore_to_id deg_eval_runtime_backup.cc 97 0x28d3584f \n10 blender::deg::deg_update_copy_on_write_datablock deg_eval_copy_on_write.cc 954 0x28c8f38f \n11 blender::deg::deg_evaluate_copy_on_write deg_eval_copy_on_write.cc 1088 0x28c902bf \n12 std::__invoke_impl<void, void ( *&)(Depsgraph *, blender::deg::IDNode const *), Depsgraph *, blender::deg::IDNode *&> invoke.h 60 0x28d19f6d \n13 std::__invoke<void ( *&)(Depsgraph *, blender::deg::IDNode const *), Depsgraph *, blender::deg::IDNode *&> invoke.h 95 0x28d153cf \n14 std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>::__call<void, Depsgraph *&&, 0ul, 1ul>(std::tuple<Depsgraph *&&>&&, std::_Index_tuple<0ul, 1ul>) functional 416 0x28d0cea4 \n15 std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>::operator()<Depsgraph *, void>(Depsgraph *&&) functional 499 0x28d05809 \n16 std::__invoke_impl<void, std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>&, Depsgraph *>(std::__invoke_other, std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>&, Depsgraph *&&) invoke.h 60 0x28cfca8c \n17 std::__invoke_r<void, std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>&, Depsgraph *>(std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>&, Depsgraph *&&) invoke.h 110 0x28cf1cca \n18 std::_Function_handler<void (Depsgraph *), std::_Bind<void ( *(std::_Placeholder<1>, blender::deg::IDNode *))(Depsgraph *, blender::deg::IDNode const *)>>::_M_invoke(std::_Any_data const&, Depsgraph *&&) std_function.h 291 0x28ce9b7c \n19 std::function<void (Depsgraph *)>::operator()(Depsgraph *) const std_function.h 622 0x28e2c749 \n20 blender::deg::(anonymous namespace)::evaluate_node deg_eval.cc 113 0x28e27e58 \n... <More> \n```\n\n", "updates to the Purge operator in the Outliner\nThe Purge unused IDs operator has been updated recently (2718ea80d2), it can now recursively delete all unused IDs, including indirectly unused ones, and also only affect linked or local data.\n\nThis is fully exposed in the `File -> Clean Up` menu, but the Outliner `Orphaned` view still only have one button with default (old) behavior.\n\nOptions are:\n- Keep things as they are.\n- Keep a single button, but change its behavior to `recursive purge`.\n- Change it to a menu with same options as in `File` cleanup menu.\n- Others?\n\n", "Texture Paint - Clone tool not working when clone source area out of viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nTexture Paint - Clone tool not working when clone source area out of viewport\n\nImport image as plane- select part of image to clone in bottom part of image. Scroll up to the top part of image so the bottom is not visible = clone tool doesnt draw anything.\n\n\n\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "Blender crashes with EXCEPTION_ACCESS_VIOLATION when executing the sequencer.duplicate_move operation while in background\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0\nWorked: *unknown*\n\n\nWhen running the operator: `bpy.ops.sequencer.duplicate_move` while Blender is backgrounded with the `--background` command line argument the process crashes.\nSee more details in in `bug-report.zip/README.md` and `bug-report.zip/render-frames.crash.txt`\n\nA snippet of the python code triggering this crash is here (the entire source can be seen in the attached .zip):\n```\n override = bpy.context.copy()\n override[\"workspace\"] = bpy.data.workspaces[\"Scripting\"]\n override[\"screen\"] = bpy.data.screens[\"Scripting\"]\n override[\"area\"] = editor\n override[\"region\"] = editor.regions[-1]\n strip_len = len(strip.elements)\n retry = 5\n while(not bpy.ops.sequencer.duplicate_move.poll(override)):\n retry -= 1\n if retry < 0:\n print(\"Couldn't duplicate for pingpong ... quiting\")\n return False\n bpy.ops.sequencer.duplicate_move(\n override,\n SEQUENCER_OT_duplicate={},\n TRANSFORM_OT_seq_slide={\n \"value\": (strip_len, 0),\n \"snap\": False,\n \"snap_target\": 'CLOSEST',\n \"snap_point\": (0, 0, 0),\n \"snap_align\": False,\n \"snap_normal\": (0, 0, 0),\n \"release_confirm\": False,\n \"use_accurate\": False\n }\n )\n```\n\nDownload bug-report.zip and extract it. Follow detailed steps in README.md.\nIn summary:\n\n- Notice the happy case when running the following command a test movie of 6 frames is rendered to the output directory set in `render-frames.blend` by default this is in `/tmp/`. Blender is left in the forground because `--background` was not supplied\n\n```\n\"C:\\Program Files\\Blender Foundation\\Blender 3.0\\blender.exe\" render-frames.blend --python-text render-frames\n```\n\n- The crash occurs when supplying the `--background` flag in addition to the above\n\n```\n\"C:\\Program Files\\Blender Foundation\\Blender 3.0\\blender.exe\" render-frames.blend --background --python-text render-frames\n```\n[bug-report.zip](bug-report.zip)", "material_slot_remove_unused operator cannot operate on a specific object(s) using a context override\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.91.0, (also 2.93.7, 3.2.0, 3.3.0 Alpha (branch: master, commit date: 2022-06-07 18:08, hash: `173a15bcda`))\nWorked: 2.90.1\n\nPreviously, the context override `{'active_object': my_object}` could be used to override the object that `bpy.ops.material_slot_remove_unused` would operate on to `my_object`.\nI'm thinking this may have stopped working in 1a650fdcb2, in particular, the change of using `object_array_for_shading_edit_mode_disabled` which calls `object_array_for_shading_impl` (now appears to be `ED_object_array_in_mode_or_selected` in `source/blender/editors/object/object_edit.c`) to get the objects to operate on instead of using `CTX_data_active_object`.\nAs far as I can tell, `ED_object_array_in_mode_or_selected` now gets the objects to operate on directly from the `view_layer` of the context.\nI could not find any context attributes that I could override to change the object(s) the operator operates on (besides overriding `view_layer` with a newly created view layer where I've selected only the objects I want to operate on).\n\nGiven the default startup .blend file:\n - Select the default cube as the active object\n - Add a new material slot to the default cube\n - Open the Python Console and run `default_cube = bpy.context.object`\n - Duplicate the default cube\n - Deselect the default cube\n - Select the duplicate cube as the active object\n - In the Python Console used earlier, run `bpy.ops.object.material_slot_remove_unused({'object': default_cube})`\n - Note that on 2.90.1 and older, the context override must instead be `{'active_object': default_cube}`, (attempting to use this override on 2.91.0 and newer will result in `RuntimeError: Operator bpy.ops.object.material_slot_remove_unused.poll() failed, context is incorrect`)\n # Note that on 3.2 and newer, you can alternatively use `with bpy.context.temp_override(object=default_cube): bpy.ops.object.material_slot_remove_unused()`\n\nOn 2.91.0 and newer, the selected duplicate cube will have its unused material slots removed instead of the default cube specified in the context override.\n(On 2.90.1 and older, the default cube will have its unused material slots removed and the selected duplicate cube will remain unchanged)\nReplacing the `material_slot_remove_unused` operator with `material_slot_remove` or `material_slot_add` in all of these steps (though, also using the override `{'object': default_cube}` on 2.90.1 and older) will cause the operator to operate on the default_cube as expected.", "Python scripts calling bpy.ops.paint.image_paint operates undo steps for \"individual calls\" rather than \"all calls\" during modal operation\n5820K and GTX970\nWindows 10\n\nLatest daily build (but same problem in earlier ones too)\n\nI have a modal operator which uses image_paint function.\nAfter using it, if I do an undo, I would expect all paint operations during modal operation to be undone.\nHowever every call to image_paint adds another item to the undo list which means I have to undo through every mouse move.\nIf I have moved the mouse more than (max undo items) then I can't get back to the position before I started the operator at all (making the undo pointless)\n\nThis doesn't seem to be the consistent with other modal operator. For example, in the docs [bpy.types.Operator.html ](URL) the modal excecution example (with the addition of UNDO added to bl_options) moves a cube. Many changes can be made to the position of the cube during the modal operation. However one undo (correctly in my option) puts the cube back in the original place before the operator is run.\n\nI did try using UNDO_GROUPED in my bl_options as well as UNDO - neither worked.\n\nIf I am doing something wrong or stupid in my code - sorry!\n\nLoad the attached scene. \nPress Run Script\nHover over cube. \nRight click\nPress space\nType in Simple Paint Operator <return> to activate operator\nPress mouse button to stop the operator\nTry Undoing - it undo things one mouse move at a time\n\n[modal_paint.blend1](modal_paint.blend1)", "GRAB_CURSOR bl_option stops working as soon as modal operator returns PASS_THROUGH the first time\nOperating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67\n\n\nBroken: version: 2.80 (sub 57)\n\n\nUsing the `GRAB_CURSOR` bl_option in a modal operator, works fine until the operator returns `PASS_THROUGH` the first time - for instance, to adjust the viewport using `MIDDLEMOUSE`, while the modal is active.\nAfter the first `PASS_THROUGH` the cursor is no longer warped to the opposite side.\n\n\n* open attached blend file\n* run the script\n* in the 3d view, look for 'GrabCursorBug' operator in the search menu and run it\n* move the mouse horizontally across the region borders, notice how it warps to the opposite side accordingly\n* hold down `MIDDLEMOUSE` and move the mouse to adjust the viewport, release again\n* try moving the mouse across the region borders again, it won't warp to the other side anymore\n\n[video demo ](watch?v=liPmg5Z_hCk)\n[grab_cursor.blend](grab_cursor.blend)\n\n\n", "VSE: Overlap during handle transform fails\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nOverlap during handle transform fails:\n{[F11318256](overlap_fail.gif), size=full}\n\nEx.\n- Import a bunch of images.\n- Select the strip. \n- Separate the images(y)\n- Select all strips.\n- Select the right handle.\n- Hit G to transform.\n- Make the strips overlap in both Overwrite and Extend.\nThe result it that it is shuffling, where it was expected to Overwrite or Extend.\n\n**Slideshow**\nAn example of where the Extend in the same channel would be useful is when making slideshows, where the steps from above and Extend in the end should allow users to batch extend all strips in one go. Combined with this patch: [D10207](D10207) slideshows would be much easier to do. \n\n" ]

[ "regression: After first search field is prefilled with full path to operator/option and it is not re-executable\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.83.9\n\nCaused by 98eb89be5d\n\nGo to edit mode, select faces,\ncall serch, type «poke faces» for example and press enter.\nOperator works.\nCall search again.\nSearch field is prefilled and this can not be executed, so I should type «poke faces» again.\nIt is not possible to repeat action with shift+R after few actions, so I expect that I can repeat it from search.\n\nworks for\nMesh ▶ Extrude (Alt E) ▶ Extrude Faces\nmesh.poke ▶Poke Faces\n\nbut not for\nFace (Ctrl F) ▶ Extrude Faces\nFace (Ctrl F) ▶ Poke Faces\n\nSo can be worked around by carefully selecting the item in search that does not start with a menu including the menu shortcut.\nBut should work either way?\n\n\n2.93:\n{[F9768047](изображение.png) size=full}\n\n\n2.83.9\n{[F9768052](изображение.png) size=full}\n\nHere is demonstration\n[2021-02-10_11-03-40.mp4](2021-02-10_11-03-40.mp4)\n\n" ]

[ "Crash Guide during render complete 2 December 9, 2022\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.4.0\n\nCrash Guide during render 2\n\nSame crash guide during render before and today.\nSee youtube: ZeCA2p5wISY\n\nHistory previous.\nT100691\n\n\n\n\n[Blender-2022-12-09-161546.ips](Blender-2022-12-09-161546.ips)\n\n[Horizontal Video.zip](Horizontal_Video.zip)", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "Blender 2.71 (rc2) crashes when a UV sphere is added\nMac OS X 10.10 (beta) / AMD Radeon HD 6750M 512 MB\n\nBroken: 2.71 (release candidate 2)\nWorked: -\n\nBlender 2.71 (rc2) crashes when a UV Sphere is added to a existent project in Edit Mode.\n\nUsing the attached file, select the figure (stickman), go to Edit Mode and add a UV Sphere. After executing these steps, Blender stops responding and it's necessary to force quit and reopen. \n\nIt seems that's something to do with the modifiers (in the attached file, I'm using Mirror, Skin and Sub-surf). One or more of them are causing the crash when the UV Sphere is added. If I create a new project with no modifiers, I'm able to add UV Sphere. \n", "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", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "Blender 2.92.0 crashes when baking steam simulation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\nCPU: Intel Core i7-8700K\nMemory: 32 GB\n\nBroken: version: 2.92.0\nWorked: I have not tried any other version than 2.92.0 (sorry)\n\nI tried to make a simple steam simulation following the steps described here: watch?v=_K0XsHht6pg. It crashed while baking, and tried to simplify the setup with a minimal set of objects, and it still crashes after baking about 30-50% of the 300 frames.\n\nFollow the steps as described in the video watch?v=_K0XsHht6pg\n\nAttached is .blend file that I tried to make as simple as possible: [steam.blend](steam.blend)\n\n - Open the attached file\n - Press \"Bake Data\" for Physics Properties for the cube\n - Blender crashes after 30%-50% of baking\n\nI have not tried a newer experimental release or an older release.\n\nI was able to reproduce the issue with the default 32 Resolution Divisions (which is way faster to reproduce than the 160 in the included file). I then tried experimenting which exact setting caused the crash. I got it to crash with Adaptive Domain disabled, and Gas Heat 1.5 and Dissolve Time 30, but now I'm not able to reproduce anymore with any setting (at least with 32 Resolution Divisions).\n\nAfter some more experimenting, it seems it randomly crashes and sometimes works. It is definitely reproducible with 32 Resolution Divisions. I kept all settings as I had before, which had worked successfully, but then changed the Time Scale to 0.8, and then it crashed again when baking. However, it had previously crashed at least once with the exact same settings with which I had also successfully baked (and the Time Scale at the default 1.0), so it is not the Time Scale that is causing the issue.", "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```", "Open Blender\nHello\n\nI can't open the app, i dowload all versión windows, windows store and portable.\n\nsxstrace.exe\n\nI have windows 10, but i can open the app,\n\nI hope you can help me\nThanks\n\n", "Microsoft store: Blender cannot be used in terminal\nWindows 11\n\nBroken: 3.4\nWorked: 3.3\n\n**Short Description**\nEver since blender 3.4 released, I have been unable to use blender in the command line. Running just the command \"blender\" gives error 0xc0000022 and whenever I try to run any actual command like \"blender -b untitled.blend -a\" nothing happens. I have never had any issues like this in versions prior to 3.4. I am running the Microsoft store version.\n\nIssue only happens with blender from Microsoft store\n\n**Steps to Reproduce**\n * Assuming that blender is already in your system path, which it should be by default,\n * open a terminal in absolutely any folder;\n * run absolutely any blender command;\n * for example, run \"blender -E help\"\n\n- - -\n!!For now, workaround is to type \"blender-launcher\" instead of \"blender\" to launch blender from command line (but that won't accept any arguments)!!", "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", "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", "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", "Connect failed in certain case\nWin8 64bit | GTX680 \n\nBroken: 2.71.6 a0b3604\n\nWhen select two vertices and press J to connect, it fails to add vertices to edges in between.\n\nPlease see the attached case for example. Thanks for checking.\n\n\n\n[vertex_connect.blend](vertex_connect.blend)", "Linux: SSL/HTTPS Request Unable to Get Local Issuer Certificate\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.35 64 Bits (Ubuntu 22.04.1)\nGraphics card: SVGA3D; build: RELEASE; LLVM; VMware, Inc. 4.1 (Core Profile) Mesa 22.0.5\n\nBroken: version: 3.3.1\nWorked: version: 2.79b, date: 2018-03-22 14:10, hash: `f4dc9f9d68b`\n\nHTTPS requests made via urllib always result in `urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)>`\nCert paths point to locations that do not exist on the machine and seem to be specific to the build environment: `/home/sybren/buildbot-builder/linux_glibc217_x86_64_cmake/build_deps/deps/Release/ssl/certs`\nWhereas I'd expect it to be `/usr/lib/ssl/certs` which is the case in version 2.79b and in a separate python 3.10 interpreter.\n\nTo view cert paths:\n```\nimport ssl\nssl.get_default_verify_paths()\n```\nTo make HTTPS request:\n```\nfrom urllib import request\nrequest.urlopen('https://blender.org').status\n```", "My Blender won't open anymore\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: Every version\n\nWhen I try to open Blender the terminal appears then disappears and nothing else happens.\nBlender worked until today in all its versions, but now it no longer opens.\n\nI tried opening it as administrator, on different versions. I restarted my PC. I updated my drivers. There no bug/crash report or anything.\n\nI don't know what to do.\n\n" ]

[ "Blender OpenGL crash on startup (Linux)\n\nHARDWARE: \nCPU: Intel i5 3337U\nGPU: Intel HD Graphics 4000 \n\nSOFTWARE:\nArch Linux\nKernel: 4.17.2-1 to 4.17.2-1\nMesa: 18.1.1-1 to 18.1.3-1\n\nBroken: current build (98d20550897)\nWorked: (about a month ago (early June))\n(2.79b still works fine)\n(crashes with both buildbot and home built versions (all done on a system with no 2.80 files in ~/.config/blender))\n\n**error**\n\nwhen opening blender2.8 (either home built debug version with default cmake options, or the buildbot version), blender crashes on launch \n(this error is also mentioned [| here ](T55584) )\n\nterminal output: \n```\n./blender --debug --debug-all\n```\n\n```\nSwitching to fully guarded memory allocator.\nColor management: using fallback mode for management\nBlender 2.80 (sub 20)\nBuild: 2018-07-02 21:01:33 Linux Debug\nargv[0] = ../build_linux_debug/bin/blender\nargv[1] = --debug\nargv[2] = --debug-all\nndof: spacenavd not found\nread file \n Version 272 sub 2 date unknown hash unknown\ndeg_graph_id_tag_update: id=GRCollection 1 flags=COPY_ON_WRITE\ndeg_graph_id_tag_update: id=GRCollection 1 flags=COPY_ON_WRITE\ndeg_graph_id_tag_update: id=GRCollection 1 flags=COPY_ON_WRITE\ndeg_graph_id_tag_update: id=WS3D View Full flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSAnimation flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSCompositing flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSGame Logic flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSMotion Tracking flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSScripting flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSUV Editing flags=TRANSFORM, GEOMETRY, TIME\ndeg_graph_id_tag_update: id=WSVideo Editing flags=TRANSFORM, GEOMETRY, TIME\nColor management: scene view \"Filmic\" not found, setting default \"Default\".\nReceived X11 Error:\n error code: 167\n request code: 152\n minor code: 34\n error text: GLXBadFBConfig\nReceived X11 Error:\n error code: 167\n request code: 152\n minor code: 34\n error text: GLXBadFBConfig\nReceived X11 Error:\n error code: 167\n request code: 152\n minor code: 34\n error text: GLXBadFBConfig\nED_screen_refresh: set screen\nReceived X11 Error:\n error code: 8\n request code: 152\n minor code: 34\n error text: BadMatch (invalid parameter attributes)\nX Error of failed request: BadMatch (invalid parameter attributes)\n Major opcode of failed request: 152 (GLX)\n Minor opcode of failed request: 5 (X_GLXMakeCurrent)\n Serial number of failed request: 205\n Current serial number in output stream: 205\n```\nBlender crashes before it can produce a backtrace. However, I stepped it through slowly with gdb (to find the point of crash) i get a completely different error (this time producing a backtrace)\n\n```\n# Blender 2.80 (sub 20), Commit date: 2018-07-02 18:25, Hash 98d20550897\n\n# backtrace\n/home/henry/Desktop/build_linux_debug/bin/blender(BLI_system_backtrace+0x35) [0x5555581f8afb]\n/home/henry/Desktop/build_linux_debug/bin/blender(+0x1a08027) [0x555556f5c027]\n/home/henry/Desktop/build_linux_debug/bin/blender(+0x1a08229) [0x555556f5c229]\n/usr/lib/libc.so.6(+0x368f0) [0x7ffff1f688f0]\n/home/henry/Desktop/build_linux_debug/bin/blender(+0x256ec33) [0x555557ac2c33]\n/home/henry/Desktop/build_linux_debug/bin/blender(GPU_framebuffer_current_get+0x9) [0x555557ac377b]\n/home/henry/Desktop/build_linux_debug/bin/blender(WM_opengl_context_create+0x5c) [0x555556f9169a]\n/home/henry/Desktop/build_linux_debug/bin/blender(DRW_opengl_context_create+0x93) [0x555557afa27f]\n/home/henry/Desktop/build_linux_debug/bin/blender(WM_init_opengl+0x82) [0x555556f7802c]\n/home/henry/Desktop/build_linux_debug/bin/blender(WM_init+0x18f) [0x555556f78228]\n/home/henry/Desktop/build_linux_debug/bin/blender(main+0x390) [0x555556f57ae1]\n/usr/lib/libc.so.6(__libc_start_main+0xeb) [0x7ffff1f5506b]\n/home/henry/Desktop/build_linux_debug/bin/blender(_start+0x2a) [0x555556f575ea]\n```\nwith it crashing on the line:\n```\nWM_opengl_context_create () at /home/henry/Desktop/blender/source/blender/windowmanager/intern/wm_window.c:2201\n2201 BLI_assert(GPU_framebuffer_current_get() == 0);\n(gdb) \nGPU_framebuffer_current_get () at /home/henry/Desktop/blender/source/blender/gpu/intern/gpu_framebuffer.c:447\n447 return gpu_framebuffer_current_get();\n(gdb) \ngpu_framebuffer_current_get () at /home/henry/Desktop/blender/source/blender/gpu/intern/gpu_framebuffer.c:180\n180 return GET_UINT_FROM_POINTER(BLI_thread_local_get(g_currentfb));\n(gdb) \n\nThread 1 \"blender\" received signal SIGSEGV, Segmentation fault.\ngpu_framebuffer_current_get () at /home/henry/Desktop/blender/source/blender/gpu/intern/gpu_framebuffer.c:180\n180 return GET_UINT_FROM_POINTER(BLI_thread_local_get(g_currentfb));\n(gdb) \nsig_handle_crash (signum=32767) at /home/henry/Desktop/blender/source/creator/creator_signals.c:112\n```\nI suspect that these 2 crashes are somewhat related " ]

[ "3.4.1 Not Displaying GTX 1660 TI\nOperating system: Windows 10 Home 22H2\nGraphics card: GTX 1660 TI\n\nBroken: These versions do not display my GPU under CUDA/OptiX: 3.4.1, 3.4.1, 3.3.4, 3.3.3 and 3.3.2 (I was also getting Python errors when trying to install addons. (This is true whether they are installed or run from the unzipped .rar downloads.\n\nWorked: blender-2.93.15 candidate+v293.400f35914421-windows.amd64-release is the most recent version that works - everything works as it should!\n\n\nI tried uninstalling/installing the latest Nvidia game ready drivers, the studio drivers, the CUDA Toolkit (which asked for me to install Visual Studio, C++, etc... 🤦‍♂️ ), tweaking the registry settings etc... none of these things worked. \n\nOnly using the older version would detect my GPU. A user on the Discord forum asked me to run the GPU debugger in the latest version 3.4.1 and when I open the program that way, my GPU was finally showing! I sent him the error reports (I can post them below) and he said that Blender IS SEEING my GPU, it's just not displaying it for use.\n\n", "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", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n ", "Sculpting Has Unexpected behavior when Saving work\n**Broken**: 2.83.4, 2.90 beta 97dc370c50ed\n**Worked**: 2.82\n\n\nGlitches in the non-active mesh after sculpting the active mesh, saving, and updating the viewport.\n\n\n[Ogre.blend](Ogre.blend)\n\n* Sculpt\n* Save\n* Refresh viewport (e.g., continue sculpting)\n\nThe artifacts should be visible immediately.\n\n**Original message**\n\nWhen I am sculpting and I go to save my work, after a successful save I get weird artifacts in the mesh that I havent made edits on in sometime. And it seems to be the same mesh every time. This has happened over 5 times so i figure its just a visual bug.\n\nGet 2 seperate meshes ready to sculpt, then sculpt on one and save your work. This is all i did to see the bug arise.\n\n\n", "High Resolution Render support\nSome fields needs to be able to output really high resolution renders out of EEVEE.\n\nFor now, we just try to allocate the asked buffer size and live with the consequence.\n\nMost GPU have a limit of 16K² texture resolution and some really high renders could not fit GPU memory in some cases.\n\nTo workaround this issue, we need to implement a multipass rendering.\n\nThe issue with this approach is that Screen Space effects (GTAO, SSR, SSRefract, SSSubSurfaceScattering) cannot take the whole picture into account.\n\nWe can split the rendering into tiles, scanlines, checkerboard pattern but the artifacts of SS effects will likely to be different for each", "Dual monitor issue\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.5.0\n\nUsing a new Mac Mini Pro with single monitor (Apple Studio Display), Blender 3.5 is very fast.\nAdd in a second Studio display and the interface becomes 'clunky', contextual menus take sometimes 2 or 3 seconds to appear, playback is jerky. \n\nTried various settings in preferences but no change. Unplugging the second monitor returns good performance...\n\nUodate:\nSetting 'GPU Backend' to 'OpenGL' improves things a little...\n\nUpdate-2:\nVersion 3.4.1 seems to have similar issues\n\nUpdate-3\nI seem to have solved some of the issue..\nThe Apple Studio Displays have 4 input ports, one Thunderbolt port and 3 USB-C ports.\nThe external display was plugged into one of the USB-C ports.\nSwapping input to the Thunbderbolt port seems to speed things up.\nStill a lot of lag on contextual menu pop-up,and selection box drag out.\n\nUpdate-4\nSo it tried reducing the Blender window to 1/4 screen, Blender becomes smooth again.\n\nI then methodically made it bigger and bigger until the latency suddenly reappears.\n\nProvided I leave around 15mm of gap around the edge of the Blender window with the desktop peeking around the edge, Blender stays very smooth.\n\nPull it a bit further out and the latency returns.\n\nIt can’t cope with absolute full screen, knock it back 5% smaller and it’s fine.\n\nWeird!!\n\n\n\n", "Cycles GPU Compute 5000 x 5000 pixels render F12 crashes\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0 Alpha\n\nCycles GPU Compute 5000 x 5000 pixels render F12 crashes\n\nMacOS 13.5\nSee youtube about Blender crash guide during 5000 x 5000 pixels.\n\nNot matter both same crash Blender 3.6.3 and 4.0\n\n", "Topbar gliches\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.3 Beta\n\nThis only happened on windows.\nWhen Status Bar is hidden and Resolution Scale is greater than 1, the Top Bar sometimes becomes unusable. (look at the end of video)\nMy guess it has something to do with notifications that are now displayed at Top Bar.\n[bug.mp4](bug.mp4)\n\nSame as in the video\n- On the `Windows` tab disable `Show Status Bar`\n- Go to {nav Edit > Preferences... > Interface} and change the `Resolution Scale` to 1.2\n- Save Preferences\n- Close the Temporary Window\n- Reopen the `Blender Preferences` window ({nav Edit > Preferences...})\n- Press `Save Preferences`\n\nInvoking save as temporary window also causes this issue\n\nTrying to resize Top Bar area or maximizing some other area fix the issue.", "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", "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)._", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "Command Line Rendering with EEVEE is slow\nWin 7 Pro 64Bit \nGTX 1070\nDriver: 417.22\n\nBroken:\nblender-2.80-606223f6a61-win64\n\n\nIf I render with EEVEE via Command Line, the GPU Load is around 40-50% (4min 33sec).\nRendered the same scene in a normal way via Gui, the GPU Load is around 90-98% (3min 20sec).\n\nIf I render the same scene with Cycles via Command Line, the GPU Load is around 90-98%\n\nblender -b PathToBlend -a\n\n\nI've tried several scenes with the same result all the time.\n\n[cube-eevee.blend](cube-eevee.blend)\n\n[cube-cycles.blend](cube-cycles.blend)\n", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n" ]

[ "Screen Scramble\nOS X Yosemite 10.10.3 Graphics Card NViDIA GeForce GTX 780M 4096 MB\niMac 27 ince 3.5 GHZ Intel Core i7\nMemory 32GB 1600MXZ DDR3\n\nBroken: (Latest 2.74)\nWorked: (optional)\n\n\nIts been like this for last 3-4 versions where when I use blender my whole screens start looking garbled scrambled especially when rendering not just on software but entire screen. Only way to get rid of it is restart computer when I finish with Blender. If Blender is open it will continue.{[F189752](Screen_Shot_2015-06-11_at_8.04.46_AM.png)}" ]

[ "No color drag'n'drop in Viewport Shading popover\nOperating system: Linux Mint\nGraphics card:\n\nBroken:2.81-a856c5eccffb-linux-glibc217-x86_64\n\n\nNo color drag'n'drop in 3d view solid (and wireframe) shader options dropdown.\n\nOpen default scene,\nclick on solid shading,\nopen the shader options dropdown,\nunder \"Color\" choose [Single],\nunder \"Background\" choose [Viewport],\ntry to drag the color of one to the other.\n\nAlso not works in wireframe shading dropdown.\n\n", "Wrong result mixing 2 nodes of an image texture\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.3, 2.93\nWorked: unsure\n\nWhen using 2 nodes of the same texture and connecting the Color output from one and the Alpha from another, the result looks different in comparison when using both outputs from one node. Broken in EEVEE\n\n1) Open the file, switch to material preview/rendered\n2) Reconnect the color (or the alpha) link to another texture\n[Bug1.blend](Bug1.blend)", "Using python handlers introduces artifacts with EEVEE motion blur\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Beta\n\n\nRendered image has \"wrong\" motion blur\n\n0. Open attached .blend file\n[motion_blur.blend](motion_blur.blend)\n1. It contains a script, which sets the cube position via a follow path constraint based on the current frame:\n\n2. Set motion blur steps to 1, render:\n\n3. Set motion blur steps to 8, render:\n\n", "Quad view viewport background color is not respected\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\nQuad view viewport background color is not respected\n\n- inspired this task by post and instructions:\nXL1v/ Viewport - Black and White template/style (not only black)\n\nThere is limitation, where user trying change view by NUMs to get FRONT, REAR, SIDE individually per square - by this we doing 2 quads to reach TOP, DOWN view for objects.. but alwyas user is limited to switch other views by NUMs or gizmo. I think that this blockade is stupid.\nfFdbbc/ Quad view needs improvement\n \n\n[#89337.blend](T89337.blend)\n\n1) Open file\nBackground color in ortho view is gray, even though viewport background is not.\nWhen `use_box_clip` property is disabled, background color is correct.\n", "Object/Collection Previews: Which Render Settings to Use?\nWhen rendering an object without full materials (as we do for object previews, for performance & compatibility reasons), there are two basic object colors we can use: The material and the material's viewport one.", "Object.display_type \"Solid\" behaves the same as \"Textured\"\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.8.1 26.20.13001.29010\n\nBroken: version: 2.81 (sub 12)\nWorked: 2.79b\n\nIn a viewport set to \"Textured\" mode (either on Cycles or Eevee), setting Object.display_type = \"SOLID\" still shows a textured object.\nOn Blender 2.79 this property was called \"Maximum Draw Type\" and was behaving as expected.\n\n1.-Set the viewport to Textured mode.\n2.-Select a textured object and set its property \"Display As\" to Solid.\nIt will stil be shown as Textured so theres no difference between the two modes (Solid, Textured)\n\nBlender 2.81\n\n\nBlender 2.79b\n\n\nExample blend.\nThe viewport is set to \"Textured\", the monkey set to \"Solid\" but is shown as Textured.\n[solid_object_display_type.blend](solid_object_display_type.blend)\n", "Alpha hashed material produces shifting artifacts when animated in EEVEE\nWhen an object with material that has alpha hashed transparency is animated in EEVEE, the noise pattern may look either unstable or shifting as shown below: \n[alpha-hashed-transparency-problem.mp4](alpha-hashed-transparency-problem.mp4)\n\n\n\nYou can observe that the artifacts on top staying in place rather than rotating with the cube while those on the sides keep flickering, thus producing shifting and unstable appearance.\n\nThe symptom is also noticeable when changing the camera position in rendered viewport mode in Blender. And it's particularly problematic in UPBGE (a fork of the old BGE based on the latest Blender source) because a game engine must animate objects in realtime with relatively small number of samples per frame.\n\nUpon an examination from the developers of UPBGE, it is found that the problem is due to the fact that the current implementation of alpha hashed transparency uses the world coordinate instead of the object space, as it is often recommended (e.g. [2017 ACM SIGGRAPH Symposium on Interactive 3D Graphics and Games](p4TYf5DDpbQ)).\n\nIt appears that a simple change from the world to object coordinate fixes the problem as shown in this [test commit (see line 80) ](e0a8638d0b255f2fc6ce778d10dd0d12a467b4d3#diff-2b8bf4f9e10009510d02c14e3659ee032c73f829de5453d6abcdf6a3f884fdfdR80), which produces the following result:\n[alpha-hashed-problem-solved.mp4](alpha-hashed-problem-solved.mp4)\n\nIt's my understanding that the [original author ]() decided to use the world matrix to avoid the difficulties with certain corner cases, like when the object is scaled by an extreme factor. However, while such a problem may be circumvented relatively easily (e.g. discard the scale information from the matrix) such a problem described above may pose more substantial issues with making an animation or rendering in realtime.\n\nSo, I hope this problem and the suggested fix may be evaluated again since we have more people interested in using Blender for such purposes now, thanks to the gaining popularity of EEVEE.", "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)", "Shader color affects Shadow Pass in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.1.0\n\nShadow Pass is not working as it should in Cycles. It somhow works much better in EEvEE (altough other problems arise).\n\nEasiest setup is just adding a plane, a sphere and setup cycles as a render engine.\nActivate **Shadow Pass** (not the Shadow Catcher Pass).\nDo an image render and everything works, more or less, as expected. So you get as a result a Black and White image (right side) where black is shadow and white is none:\n\n\nBut, as soon as you texture the objects with any image you get the darkest areas of those images in the Shadow pass (something like if one of the rgb channels is leaking to the final image):\n\n\nI have already tested it in Blender 2.83, 2.93, 3.1, 3.2 and 3.3 alpha and I have got always the same behaviour... so no idea if it ever worked or not as it should do. Right now it is absolutelly useless as you can't compose it without textures afecting the masked shadow.\n\nAs I said I already tested in EEvEE and it works better:\n\nBut another problem arises, tesselation of the objects aren't smoothed, like if it is not using Smooth Shade setting at all.\n\n\nI attach a scene that reproduces the problem: [Shadow_Pass_3.1_Packed.blend](Shadow_Pass_3.1_Packed.blend)\n\nAs a last detailed behaviour, in the scene I'm actually working, I nottice that some Specularity and Diffuse are also \"leaking\" to the Shadow Pass:\n\n\nI hope it can be fixed.\n\nOf course, If I can somehow workaround it let me know as it would be of much help as I didn't found, yet, a way to overpass the trouble other than creating a new scene with untextured materials.\n\nThanks in advance, and cheers!\nIgnasi.\n\n", "2.81 shadows are incompatible with flat toon shaders and Data transfer modifiers\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nNew shadows in EEVEE are incompatible with flat (toon) shaders and custom normals\n\nCreate a simple Toon shader in Eevee (Diffuse BSDF->ShaderToRGB->ColorRampConstant->Mix->Output\nShadows are jagged and unusable, even on maximum Cube Size and Cascade Size and high sample count. In previous version 2.8, the shader will appear clean and sharp even on low settings\nIn addition, the new shadows do not respect normal editing via Data Transfer Modifier. Attach a Data Transfer Modifier to an object with the shader, Check Face Corner Data, Custom Normals, add a source mesh to source mesh. In mesh data under normals check Auto Smooth. in 2.81 the shadows will not obey the custom normals and will add shadows where there are none on the source. In previous version 2.8, the shader will obey the custom normals and not add extra shadows. See attachments\n\n\n\n\n\n[BadShadowsExample.blend](BadShadowsExample.blend)\n\n", "Normal maps appear faceted in Eevee when using Closest or Cubic interpolation \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0\nAlso broken in 3.0 alpha \n\nIf a normal map has its image texture set to Closest or Cubic, the result in Eevee looks incorrect. I'm not sure if this is a fundamental limitation of the method or if it's something that could be fixed in the implementation, but I've found the Closest interpolation to be really useful when heavily messing with an image's vector coordinates.\n\n1. Load up a normal map and apply it to a smooth shaded object\n2. Set the image texture's interpolation to Closest or Cubic\n\n[closest_interpolated_normal_map.blend](closest_interpolated_normal_map.blend)\n\nLinear filtering:\n\nClosest filtering:\n\nCubic filtering:\n\n", "Holdout doesn't work with Mix Shader correctly in Eevee\nOperating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.91.0\n- 2.90.1\nWorked: 2.83.x\n\nHoldout doesn't work with Mix Shader correctly in Eevee. \n\nWhat I expect when mixing with 100% Holdout:\n\n\n\nWhat I get instead:\n\n\n\n\n\n - Open the simple blend below\n - Move the timeline from 0-100, which moves the Mix Shader Fac from 0-1.\n - When at frame 1, it should be a 100% Holdout, but notice that this isn't the case\n - Switch to Cycles and verify that it indeed handles this case correctly\n\n[holdout_eevee_bug.blend](holdout_eevee_bug.blend)\n\n", "Objects colors bug\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.0.0\n\nWhen change frame colors are rebuilding... When there was less objects was no problems. I can upload this file if you need.\nSee in video. \n[2022-01-25 18-51-54.flv](2022-01-25_18-51-54.flv)\n\n[#95200.blend](T95200.blend)\n- Open file\n- Scrub timeline\n\nColor of objects will change. In original file ([F12825448](ADS-800-CDC_монтаж_ушка.rar)) color would change even to black.\n", "Display Workbench Textures On Curve Objects\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D500](D500) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.24\n\nBroken: version: 2.82 (sub 6)\nSame on Windows version with same hash as well as in older versions of the 2.8x series.\n\nWorked: (optional)\nWorked in 2.7x Blender viewport ('Texture' mode)\n\nTextures don't display on curve extrusions in 'Solid' viewport shading mode even when UVs are assigned and 'Texture' is chosen as the object color. Instead, Curve extrusions simply stay gray.\nThese same textures show up fine on regular mesh objects in the same viewport. Also the curves display as intended in Material Preview and Rendered modes.\n\n\nIdeally open attached blend file to see the issue right away.\n\nAlternatively :\n1. Create a curve object and give it depth and UVs and apply a material\n2. Import a bitmap texture, attach to the curve's material and select it\n3. Switch to Solid shading mode and activate Texture as object color\n4. Compare look in Solid and Material Preview\n5. Repeat the above steps for a mesh object with UVs\n\n\n[textures_on_curves.blend.zip](textures_on_curves.blend.zip)", "HDRI Preview Spheres appear in surface reflections\n\n\nBroken: version: 2.82 (sub 7)\nMaster\n\nWhen using material shading and overlays in the viewport, the gizmo at the bottom-left corner (sphere displaying the environment map used for preview) is reflected by shiny surfaces in the 3D world, despite technically being a part of the UI. Using the icon to show / hide overlays affects this, the reflection also disappears when overlays are hidden.\n\nShould work in any setup, if there are issues replicating this let me know and I'll extract the relevant part from my project's blend file. Just add a plane, lower its material roughness so it's shiny, move the view upward so the overlays appear under it, and you should see the strange reflection.\n\n\n\n[HDRI_reflected_in_viewport.blend](HDRI_reflected_in_viewport.blend)" ]

[ "EEVEE can't show reflections from hdri - blender v2.83.13 beta\n{[F8485512](EEVEE_blackreflections_bug.mp4)}Operating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 2500 Intel 4.0.0 - Build 10.18.10.5069\n\nBroken: version: 2.83 (sub 13)\nWorked: version: 2.82.7 (2.82a release)\n\nEEVEE can't show reflections from hdri\n\n- Open attached file\n[0 roughness sphere.blend](0_roughness_sphere.blend)\n\n\n", "Eevee won't display reflections from world environment HDR texture\nOperating system: Microsoft Windows 8.1 Single Language\nGraphics card: Intel(R) Graphics HD 4400\n\nBroken: 2.83 LTS, as available on blender.org\n\nUpon creating a scene with an world environment texture, and adding a Principled BSDF material with 1.0 Metallic and low roughness, the reflections of the world texture do not appear on the object's (standard cube) surface. The direct light reflection, however, does appear. A few additional details of the bug can be found [here ](metallic-reflective-material-not-displaying-reflections-of-the-world-hdri-on-ee).\n\nChange the render engine to eevee, change Viewport Shading to Rendered, or render from the camera, as is.[doesntwork.blend](doesntwork.blend)\n" ]

[ "Regression: unhide now is global even in local mode\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.79b\n\nAlt+H in local view unhides objects all over the scene instead only local context, as it work in 2.79\nPlease fix. It is very handy feature and we have lost it.\n\n**Step to Reproduce**\n- Open .blend file\n- Select a sphere and Hide: {key H}\n- Select all three cubes and enter in Local view: {key /}\n- Hide cubes\n- Now unhide cubes in Local view: {key Alt H}\n- sphere is also visible (Either check outliner or Switch back from Local view)\n\nTest File:\n[#92527.blend](T92527.blend)\n[2021-10-27_12-23-23.mp4](2021-10-27_12-23-23.mp4)", "Scene strips don't include passes\nOperating system: Linux-5.8.11-1-MANJARO-x86_64-with-glibc2.32 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.8.11-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.1.8\n\nBroken: from 2.79 to version: 2.92.0 Alpha\nWorked: -\n\nThe render passes of another scene (as scene strip) are ignored in the master scene.\nThis will most probably be categorized as limitation. Since it is a severe one, it should at least be documented here:\nPagename: `video_editing/sequencer/strips/scene`\n\nName current scene \"A\", create new scene, in the sequencer add scene strip for \"A\", hit F12\nThe content of scene \"A\" will be rendered, but the Z channel (enabled by default / other channels if activated) of scene \"A\" will not be rendered, the Select Pass dropdown is not there and the layers are not saved to multilayerEXR.\n\n", "volumes breaking data passes\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\nWorked: never\n\npixel data for surface data passes and shader AOV's are rendering black if there's a volume.\n\n\n1. Open attached file\n2. go to compositor\n3. render frame\n4. check the data and aov passes\n\nexamples:\n\n\n\n\nI understand it's necessary for the volume to affect the colour passes that build the combined pass, but for data passes and custom AOV's that only represent the surface, it would be useful for that data to not be obscured. For example if you want to replace textures in comp, or add vector motion blur to an object which is behind a volume etc. I think rule of thumb should be, if something doesn't have that type of data, then it shouldn't affect passes of that type of data.\n\nIt makes it impossible to make use of the data otherwise, forcing the user to render twice. Perhaps data and custom AOV's could have exclude lists where users could specify which objects shouldn't have any influence on the pass? Would be nice to have that on the environment pass too, so shadow catchers wouldn't mask the environment?\n\n", "Viewport display of multiple Dupli-Collections when different draw-types are used : wireframe might disappear (only selected are garuanteed to draw)\nOperating system: Windows 10 / Ubuntu 20.04\nGraphics card: GTX 1080 / RTX 3080\n\nBroken: 2d9d08677e a2d59b2dac \nBroken: all versions >= 2.8\nWorked: 2.79\n\nViewport display of Dupli-Collections is inconsistant.\nDigging deeper into it, it looks to be when there are different draw types on the same dupli-collection\n\n1. Open attached blend file\n2. select the empties in the middle of the screen which do not look like they have anything attached\n3. notice how they randomly appear / disappear upon selection.\n4. note that one of instancer is set to `Textured` draw type, the other to `Wire`, if all are set to `Wire` the issue is gone\n\nThis has happened in quite a few of our production scenes.[bug.blend](bug.blend)\n\nNOTE: Might boil down to be the same as #101822 (Collection instance set to Display As Wire doesn't show in Solid mode when not selected) or #86732 (Instanced wire objects are hidden in solid mode instead wire appearance)\n\n", "Files don't appear in File Browser while Asset Browser loads assets\nOperating system: Linux-5.8.0-59-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10\n\nBroken: version: 3.0.0 Alpha\n\nLinux: When opening a file or import a file while the Asset Browser loads assets, the files do not shown up in the File Browser. Only after all assets were loaded. This happens with at least the 4 lasts builds.\n\n\nOpen an Asset Browser with an asset library that takes a moment to load, open >File > Open , then the directory contents do not appear in the File Browser\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?", "Asset Browser don't show my asset's and crash Blender\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: 3.4, 3.5.0\nWorked: \n\n\nI created my asset browser and at first it worked well. But after it's worked strange. Then i opened asset browser i don't see my assets, but after refreshing Blender was crashed. I tried to re-specify the path to the library, but was changed nothing. I tryed to install new Blender (3.5) and it take change but don't fix it. I can't see assets in asset browser, but then a refresh it, Blender don't crash.\n\n\n- Download and extract the attached .zip file\n- In Preferences -> File Paths -> Asset Libraries, add the directory of the unzipped file\n- Go to Asset Browser an look for the assets in the added library - You cannot find then\n- Refresh - crash", "Compositor seam after rotation\nOperating system: windows\nGraphics card: gtx1050\n\nBroken: 2.93, 3.0, 4.0\nWorked: \n\nThere is a seam after the rotate node, which isnt present before it. Also If you set the rotation to 0 degree there will be no seam.\n\ncheck in the provided file: [compositor seam bug.blend](compositor_seam_bug.blend)", "Inaccuracy in 'Info' editor\nThis bug is difficult to describe specifically, since I have no idea of *all* of the affected properties. All I noticed is that *some* are reported inaccurately (i.e. the reported rna path does not exist or does not point to the changed property).\n\nA few I found are on the View Layer tab in the Properties editor:\n`bpy.context.scene.view_layers- [x].cycles.denoising_store_passes` is reported as `bpy.context.scene.denoising_store_passes`\n`bpy.context.scene.view_layers- [x].cycles.pass_debug_render_time` is reported as `bpy.context.scene.pass_debug_render_time`\n`bpy.context.scene.view_layers- [x].cycles.use_pass_volume_direct` is reported as `bpy.context.scene.use_pass_volume_direct`\n`bpy.context.scene.view_layers- [x].cycles.use_pass_volume_indirect` is reported as `bpy.context.scene.use_pass_volume_indirect`\nPlus all of the Cryptomatte and Denoising properties.\n\nI have no idea how the Info editor receives this information, but it looks as if the message is partially hard-coded and not up to date?", "Mist pass saves as black using full OpenEXR\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.6.0\n\nEven though the Render Results clearly show a greyscale image in the Mist pass, when you attempt to save it to an OpenEXR format (full float) the result is all black.\n\n1. Open the attached file\n2. Render image\n3. Switch to the Rendering workspace (already showing mist)\n4. Save As from the Image menu and choose OpenEXR full float\n\nResult:\n\nFile is all black\n\nExpected:\n\nThe greyscale Render Result should be saved as a 32-bit image\n\n", "CPU render will look different to GPU render and fails randomly\nWin 10, GTX 880M, GTX 1080TI Founders Edition\n\nBroken: blender-2.79.0-git.2ca1f29-windows64\nWorked: na\n\nAttached you'll finde a scene what has issues with GPU rendering. The scene is using the old shaders with a bevel shader (OSL).\n\nThe preview will not start or maybe it takes a very long time. Here nothing happened.\nIn GPU mode the preview starts as expected.\n\nWhen I try to render with F12 in CPU mode it doesn't start or maybe it will start after a long time. Here nothing happened after 10 minutes.\nWhen I render a small region with CPU it takes a long time till it starts to render.\nWhen I start rendering in GPU mode it starts fast as expected ignoring OSL of course.\n\nIn the ZIP and attached you'll see a picture with a split screen. Left side is GPU. Right CPU. The results are different. Transparent parts with DOF will have extreme noise.\n\nLoad the scene and press F12. Here CPU render will not start as expected.\nSwitch to GPU and press F12. Rendering will start.\nDefine a small region where the transparent parts are. Press F12. It will take really long but start. Result has noise at the transparent parts.\nThis might be a bug in the Cycles render engine or an issue with the shader tree.\n\n[170902_Blender_279_Cycles_CPU_Issue.zip](170902_Blender_279_Cycles_CPU_Issue.zip)\n\n\n\n", "UV: (investigate) Render UVs of selected object in UV Editor while in Object Mode\nCurrently, the UV Editor only works while in \"Edit\" mode.\n\nHow firm is that restriction?\n\nIt would be nice if we could view UVs in the UV editor, even in \"Object\" mode.\n\nIf would be even nicer if we could use the basic edit tools, such as move, scale and rotate on those UVS, again, even in Object mode.\n\nUVs can be generated and adjusted procedurally, but there's no good way to see them. It would be nice to allow displaying (not editing) evaluated UVs. Combined with features like visualizing overlapping faces, this could save a lot of time.\n\nThis is an *investigate* task, to see if such a thing is even possible. If we discover it's possible, we'll then need to decide if it's desirable.\n\nThanks @BlenderBob for the inspiration!\n\n", "Compositor doesn't render if VSE contains strips\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.0.0 Alpha\n\nCompositor doesn't render if VSE contains strips.\nIn some cases user may want to have for example sound strip to play sound while compositing. This can cause only VSE to be used for rendering.\n\nAdd color strip to VSE, in compositor check Use Nodes and render.", "Node Operators: Show node group inputs in redo panel\n_No response_\n\n", "File Output node doesn't keep layer names when switched to Multilayer EXR\nWin10 64bit\n\nBroken: 2.79\n\nOpen file, change file type in File Output node from **PNG to Multilayer EXR -> names set to default,** changing to others works good.\n[Input_names.blend](Input_names.blend)\n" ]

[ "openexr bug\nwin7 64bit, GTX650ti\n\nBroken: 2.75a\nWorked: 2.74\n\nI used file output node set with openexr file type to output render layers and render passes . When I wanted to use these openexr file to composite, I found the image input node only showed one render layer.\n\nI had create a file named \"bug\", you can use this one to create a openexr file. I also created a file named \"bug_1\" with openexr file.\n{[F225064](bug.blend)}[bug_1.blend](https://archive.blender.org/developer/F225065/bug_1.blend)\n1, open the bug_1 file, then use view node to check each output node of the image node. Only one render layer can show up and work. If open the bug_1 file with 2.74, every output node of the image node works.\n" ]

[ "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", "UI: In Preferences, Invisible Execute Region in Nav_bar, blocks resize of area.\nBroken: 957b4547ae, 6b082278d1\nWorked: never?\n\nWhen you try to resize preferences, you grab the execute region edge instead(Only for nav_bar side).\nThe default state, has the area open but invisible. Blocking resize.\n\nSeparate preference window, does not have a problem.\n\n[2019-05-10 09-01-29.mkv](2019-05-10_09-01-29.mkv)", "Redo panel overlaps part of the interface\nIn the image editor, the redo panel covers part of the pixel values. \nWould be nice if such panel could be dismissed, or if it would take into account the possible presence of the pixel value subheader.\n\n[open_image_overlay.mov](open_image_overlay.mov)", "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "Design: Animation Editors UI Redesign\n**Problem**\nSeveral proposals have been made to improve the usability of the Animation Editors' (Graph Editor, Nonlinear Animation, & Dope Sheet) Headers and Menus:\n\n - [Redesign Graph editor Header and Menus to 2.80 Blender UI standards ](T89069)\n - [Design: More frame snapping options ](T91973)\n\nThe main issues outlined by these proposals are:\n - “View” Menu cluttered with Overlay checkboxes rather than Overlay popover as in 3D View\n - 2D Cursor, Frame Snapping, & Proportional Editing button right-aligned location does not match other Editors. Frame Snapping full-text Enum is too wide and inconsistent with other icon-only Popovers\n - Frame Snapping menu only allows for one snapping option as opposed to multiple-option snapping in 3D View\n - Graph Editor “View” Panel has one utility/poor usage\n - There is a need for a separate a Timeline Editor with Graph Editor, NLA, & Dope Sheet (e.g. changing Playback options, Keying Set) however the Timeline has many redundant options to Dope Sheet and is only needed for its Header.\n - Full-text \"Keying\" dropdown is wide, inconsistent with icon-only popovers, and separate from Auto-keying popover\n # Full-text \"Playback\" dropdown is wide, inconsistent with icon-only popovers, and separate from Playback controls\n\nThis design task addresses the issues brought up in these proposals and breaks them into subtasks.\n\n**Proposed Solutions**\n\n - Move Markers, Curve Extrapolation, Only Selected Curves Keyframes, Show Handles, Only Selected Keyframes Handles and 2D Cursor from View to a new Overlays Menu\n - Center Pivot, Snapping and Proportional Editing Header buttons. Change Snapping to icon-only popover.\n - Create UI allowing for implementation of multi-snapping options\n - Move Normalize Button from Graph Editor Header to View Panel. Rename \"View\" Panel to \"Graph\".\n - Add Playback & Frame Range Controls to Timeline Header\n - Add Keying Set Controls to icon only popover near Playback Controls\n # Add Playback options to popover by Playback Controls\n\n\n\n**Stretch Goals**\n - Add fixed height mini-timeline element to Playback & Range footer\n\n**Implementation Patches**\n\n\n - [Playback, Keying Set, and Frame Range controls update](D15626)\n - [Center Pivot, Snap, and Proportional Editing in Animation Editor Headers ](D15631)\n\n", "Preset icon overlaps panel header text\nOperating system: Mac 10.9.5\nGraphics card: Macbookpro NVIDIA GeForce GT 750M 2048 MB\n\nBlender 2.8 downloaded today\n\nIn movie editor\nthe text tracking settings is somehow mixed up with a button.\nI can sent a pic if you want.\n\nI am a amateur and English is not my first language, so i'm very sorry if i've wasted your time.\n\nGreetz \nLes", "Preferences: `Interface Font` doesn't open path set in `File Paths`\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 526.67\n\nBroken: version: 3.3.0\nWorked: never\n\nWhen hitting the folder icon button to open the file browser to select an interface font, it does not open the path set for fonts under Preferences > File Paths.\n\n1. Set folder path for fonts\n\n2. Open file browser under Preferences > Interface > Text rendering\n\n\n", "Graph Editor: Link Visible and Selected states\nWorking with many curves in the GE currently requires animators to often toggle the visibility of curves and then select the newly visible curves.\nLinking 'visible' and 'selected' would make it faster to use the GE. However, having those two always linked would remove the feature of having certain curves visible \"in the background\", i.e. visible but unselected. We do not want to lose this feature.\n\n**Proposal**: Add a user preference to link 'visible' and 'selected'. When this mode is enabled:\n- The visibility icon can be removed from the graph editor UI.\n- Selection state determines visibility.\n\nWe think a user preference is best for this, as we suspect it's a personal preference and not so much something you want to manage per GE editor.\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?", "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", "Modifying keymap won't tag prefs dirty\nWindows 7 Professional 64-bit service pack 1\nIntel Core i7-2600\n8GB RAM\nNVIDIA GTX 1060 6GB\n\nBroken: blender-2.80.0-git.aa003c73245f-windows64\n\n\"Save Preferences\" button, shown when \"Auto-Save Preferences\" is turned off, stays unavailable after modifying keymap.\n\n1. Make sure \"Auto-Save Preference\" is turned off. If it isn't, turn off this and press \"Save Preferences\" button.\n2. Modify keymap, editing the settings used to activate an operator (example: search for `Clear Rotation` operator, changing the `Clear Delta` option will not tag prefs dirty).", "Grid doesnt show\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Preferences: no default key map export name and file type\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nPreferences: no default key map export name and file type\n\nWhen I wanted to export the default map keys ther was no default file name and file type.\nSo I tried to guess it was .txt and then exported. The exported file was \".py\", only the\nfile type whithout a file name. It would be nice to have someting like when saving a\nblend file aka \"untitled.blend\" -> \"untilted-key-map.py\", or something like that.\n\n- Open Blender (factory settings)\n- Go to Preferences > Keymap\n- Export \n- In the field where the file name needs to be specified there is no default name, that indicates the file type (and name)\n\n\n\n", "Invisible color picker in the preferences menu\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\n\n**Short description of error**\nDepending on your position in the preferences menu the colour picker becomes invisible\n\nDepending on your position in the themes menu (preferences/themes), the colour picker may be above or under the setting you want to change, but there is a specific position in which the colour picker becomes invisible. This bug only occurs if there are multiple settings above, at least one submenu open and you edit one of the settings in the middle. E.g. \"Inner\" and \"Inner selected\" in the user interface section. The colour picker is not only invisible but also not functioning. The \"RGB\" and \"HSV\" sliders work as well as the \"HEX\" section.\nClosing the picker and scrolling down the page, only by a single line (up or down) fixes the glitch, also resizing the window works. \n\nBased on the default startup\n\n", "Restore default value operator removes redo panel\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.0\nWorked: 3.4.1\n\nWith user installed add-ons (sometimes Blenders own operators too) if the user tries to reset a value by RightMouseClick / \"Reset To Default Value\", the redo panel closes.\n\n1) Activate the user installed add-on\n2) Change a value\n3) RMB on the property from redo panel, select \"Reset To Default Value\"\n\nThis will close the panel and end the active add-on (may not happen on first attempt)\n\nYouTube video at the link:\n4woEVTFSrtw\n\n" ]

[ "Settings, Save Startup File and Load Factory Settings - gone from menus\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.34\n\n\nBroken: version: 2.80 (sub 64)\nWorked: (optional)\n\n\nSettings are gone from the Edit Menu\n\nSave Startup File and Load Factory Settings is also gone\n\n\nThe settings Editor is stille there when I open it by changing an editor type to it.\n\n", "No User Preferences in Edit Menu\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.22\n\n\nBroken: version: 2.80 (sub 66)\nWorked: 2.80 (sub 55)\n\n\nThe User Preferences menu appears to be missing from the Edit Menu in this build.\n\n\n" ]

[ "Geometry Nodes Mesh Boolean unexpected difference result\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 83\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nGeometry Nodes Mesh Boolean Difference does not work as expected.\nNode setup:\n\n\nUnexpected boolean difference:\n\n\n- Open the attached .blend file\n- Press G to move the selected Cube.001 and the small cubes will flicker.\n# At certain positions of Cube.001 some of the small cubes will disappear when they should not.\nThanks!\n[test06.blend](test06.blend)\n", "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", "Painting across different resolution UDIM tiles in image editor crash.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\n\nIf you have UDIMs of different resolutions, and you paint in the Image editor window across the tiles, you get a crash.\nIf you do the same thing in the 3D viewport, there is no problem.[CrashFile.7z](CrashFile.7z)\n\n\nCreate a UDIM texture, with at least two tiles, of different texture resolutions. \nIn the image editor in paint mode, draw a line across the tiles and it will crash. Sometimes I need to draw two lines crossing the tiles for it to crash.\n\nThat's all, you don't need to apply the textures to a model or anything else.\n\n\n", "Multires Can't Bake to NGons\nSystem Information\nOperating system: Linux-5.19.0-43-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBlender Version\nBroken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:25\nWorked: never? (2.83, 2.79 are affected too) \n\nShort description of error\nTrying to bake from a multires does not work for faces (on the level 0 mesh) that are ngons. Normal and displacement mode are affected by this.\n\nExact steps for others to reproduce the error\nFrom blend file hit bake. The cylinder has an ngon on the top and the bottom so nothing gets saved to the texture for those two faces.\n\n", "Cycles: principled BSDF thin surface support\n[D2354: Thin surface approximation for Cycles Disney BSDF](D2354)\n\nRebase and benchmark performance impact.", "Crashing and freezing when working on files with assets\nOperating system: macOS-12.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 580 1.2\n\nBroken: version: 3.5.0\n\nCrashing and freezing when working on files with assets\n\nif I open the demo file cube_diorama.blend the whole system freezes and either crashes or logs out needing to login again.\nevery blender crash a WindowsServer log is created.\n\n cube_diorama.blend never crashed in previous versions of blender for me.\n\n", "Crash 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", "Ngon with more edge crash blender when using Multires/Subdivision Modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha, 2.93.2, \nWorked: None\n\nPlease check the video, it shows the difference when blender deal will small ngon(edge < 10) and large ngon (~=600).\nI think it should take over aleast 5000 points ngon(for some svg file)\n[2021-08-15 17-50-41.mp4](2021-08-15_17-50-41.mp4)\n\nCreat a ngon with more than 600 points\nextrude it and add Subdivision Modifier\ncrash\n[test.blend](test.blend)\n", "Exact boolean is inaccurate when cutting planar geometry\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\nWorked: don't know\n\nPerforming boolean operations in `Exact` mode on thin geometry (eg. a plane) can be inaccurate in some cases. It usually happens if \"cutter\" object has a slightly curved edge. It happens both in Boolean modifier and Geometry Nodes node.\n\n\n1. Open the .blend file.\n2. Select the plane.\n3. Toggle between `Fast` and `Exact` modes in the Boolean modifier.\n4. You should see a difference in the top edge.", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)", "EXCEPTION_ACCESS_VIOLATION when baking between linked objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen experimenting with the idea of having linked duplicate objects and bake materials between them I found a reproducible crash.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF63BB28F6E\nModule : C:\\Program Files\\Blender Foundation\\Blender 2.82\\blender.exe\n```\n\n- Oppen attached file\n- Try to bake the textures (blender crashes)\nSometimes it doesn't crash the first time but always atleast on the second or third attempt.\n\n[mushroom.blend](mushroom.blend)\n", "unwanted uv-gap created by bevel modifier\nOperating system and graphics card\nwindows 7\nNVIDIA GeForce GTX 660\n\nBroken: 3d243eb\nWorked: same error on offical release 2.78\n\nbevel modifier (bevel by weight) creates an unwanted UV-gap at a vertex with 5 edges connected. 2 edges has bevel weight. Error visible if bevel modifier is applied of if subdiv modifier is active. The UV-gap disappears if 4 out of 5 edges has a 90 degree angle to one another.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nHard to explain how to model. Easiest for you is to open the .blend and test it. I put a shape key on the \"error mesh\". Turn the shapekey on/off to show the error.[bevel modifier error.blend](bevel_modifier_error.blend)", "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", "Crash on sculpt mask brush when Multiresolution modifier is copied from another object\nOperating system: Windows 11\nGraphics card: GTX 1060\n\nBroken: 3.3.0 / 3.2.0 / 2.93.10\nWorked: (First time trying multires hasn't worked on any of the versions I've tested on)\n\n\nCrash on sculpt mask brush when Multiresolution modifier is copied from another object.\n\n\nReplicate problem 1:\n\n - Add a Cube (#1)\n - Add Multiresolution modifier to Cube (#1)\n - Subdivide 4 times\n - Add a Cube (#2)\n - Copy Cube (#1)'s modifier onto Cube (#2) through the use of Link/Transfer Data > Copy Modifier\n - Select Cube (#2) and enter sculpt mode\n - Select Mask Brush\n - Use Mask Brush (Should crash blender)", "Regression: Damaged normals in sculpting with Multires modifier\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nWhen sculpting, sometimes breaks normals. Switching between modes fixes this.\n| Edited sculpture | Object mode |\n| -- | -- |\n|  |  |\n\n1. Open attached file.\n2. Go to Sculpt mode.\n3. Do something.\nLook at the fact that in some places the normals are damaged." ]

[ "Boolean produces faces with holes which isn't supported by BMesh\nblender-2.69-b096845-win64-vc12\n\n[Bevel_crash_blender.blend](Bevel_crash_blender.blend)\n\n1) Open attached scene\n2) Press Ctrl+B\n3) Move mouse\n\nThe file produced by subtracting geometry from the middle of the face." ]

[ "Mantaflow: charge force field crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen I try to add the charge force field and play the simulation the blender 3.0.0 Alpha crashes\n\nMake a simple water simulation and add the charge force field\n**Crash seems to happen only in release builds**\n\n[#92110.blend](T92110.blend)", "Force field can't expand smoke evenly.\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 650 Ti\nProcessor: Intel® Core™ i7-3770\n\nBroken: (2.83 Beta, 8956e9e5f6c0, 2020-05-11 19:18 )\nWorked: (never)\n\nBlender smoke can't expand in all directions evenly.\nThe video below shows two situations: one where particles are emitted in an omnidirectional fashion, and one where the \"Force\" force field is used to push the smoke outwards.\n[ExpansionDemoC.mp4](ExpansionDemoC.mp4)\n\n**Exact steps to reproduce the error**\n[Spherical Expansion (Force).blend](Spherical_Expansion__Force_.blend)\n\n1. Add a sphere.\n2. Press F3 and select Quick Smoke.\n3. Add a \"Force\" force field in the center of the sphere.\n4. (optional) Set Buoyancy Density and Heat to zero, to ensure that the only movement the smoke has is the push from the force field.\n", "Fluid domain renders as the original object when particle mesh is momentarily disappear\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0\n\nIf there is no mesh generated from active particles within the domain, the frame will render with the domain as its original surface.\n\nI have an emitter object that periodically (cycles) emits fluid into the domain. At times when there is no mesh generated from particles in the domain the rendering is correct -- the fluid mesh:\n\n\n\nAt some point when there is no mesh generated particles inside the domain, the render is incorrect -- the surface coloring on the domain boundary:\n\n\n\nIn the attached file, I would know when I might start to include the Fluid Domain in the rendering, but it would be rather difficult to tell when there are no more particles if velocities or emissions are complicated with noise.\n\nHere is the [StackExchange ](fluid-simulation-gives-a-obscured-render-when-active-fluid-particles-are-absent) discussion and an example blend file.[fluid render problem.blend](fluid_render_problem.blend)\n\n\n\n", "Particle display problem in rendering when using the Time remapping option\nOperating system: Mac Os Mojave 10.14.6 (18G95) and Windows 10 (Last update)\nGraphics card: AMD Radeon R9 M295X 4 Go & Nvidia GTX 1070\n\nBlender 2.80\n\nThere is a problem of particle rendering if we use the Time remapping function which makes it possible to make a film slower by multiplying the number of images of an animation. The particle animation is not continuous, some disappear and then reappear creating a jerky effect.\nThe problem does not appear when launching the animation directly in the software but only by doing a rendering calculation whether it is in film or frame-by-frame mode or movie (with Cycle or Eevee rendering)\n\nIf I leave the time remapping by default (old 100, new 100) there is no problem.[torus particules.blend](torus_particules.blend)\nIf I change the time remapping to have a movie with 4 times more image (old 25, new 100), the problem appears: the particle animation is not continuous, some disappear and then reappear creating a jerky effect.", "Mantaflow does not maintain color on Noise enabled (Upres Factor > 1)\nSystem Information\nOperating system: Ubuntu 20.04.2\nGraphics card: GTX 980Ti\nBlender Version\nBroken: 2.93.3, 8b80d19f3641, master, 2021-08-17\nWorked: version: 2.83.16\n\nShort description of error\nNoise with Upres Factor > 1 changes original color of smoke simulation in Mantaflow.\n\nExact steps for others to reproduce the error\n\n```\n Open Blender\n Select default Cube\n F3 > Quick Smoke\n Select default Cube > Physics Properties Tab > Change Color to blue (or whatever color you like)\n Select the Smoke Domain > Physics Properties Tab > Cache > Type Modular (Is Resumable: On)\n Bake a few frames > Press Esc\n Physics Properties Tab > Enable Noise > Upres Factor = 2 (default)\n Bake a few frames > Press Esc\n Review the simulation in the Viewport\n```\n\n**Note: Works with Upres Factor = 1. With some colors the effect is not that obvious. See blend-file / video.\n\n[Video on YouTube ](JzO22fS6p0E)\n\n[20210826_Blender_MantaTest.blend](20210826_Blender_MantaTest.blend)\n\n\n", "Particle Angular velocity doesn't work\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nRotation > Angular velocity section of particle system settings doesn't rotate particles over time.\n\n\n[#81671.blend](T81671.blend)\n* open attached .blend\n* play animation\n", "overlays extras option being ignored\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Beta\nWorked: (unsure, definitely 2.8 possibly 3.0)\n\nbounding box representation of particle instanced geometry (hair) where the object being instanced is set to bounding box is not being hidden from the viewport when the 'extras' option is checked. \n\n\n", "Mantaflow gas under 2.9 renders very different than 2.83\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12028.2\n\nBroken: version: 2.90.0 Alpha\nWorked: version: 2.83.3\n\nThe same mantaflow gas scene taken from 2.83.3 and re-simmed under 2.90.0 results in a very different sim. I can't say which is *proper*, but the differences are big enough to be problematic in trying to use it or learn to use it. It's as if the 2.83 gas is more buoyant for the same values and the 2.9 stick very close to the original particles throughout.\n\nSim this scene under each version, saving the caches separately, since 2.90.0 caches don't work at all under 2.83.3 \n\n[explosionB2.83.blend](explosionB2.83.blend)\n\n\n\n", "Force fields don't work on a fire simulation with Flame Smoke 0\nOperating system: Windows 7 (64 bits)\nGraphics card: Radeon R7 200\n\nBroken: 2.83, 2.92.0\nWorked: -\n\nSetting the Flame Smoke to 0 makes the fire simulation to ignore all forces except gravity.\n\n* create a Quick Smoke simulation\n* set the Flow object to Fire, behaviour to Inflow\n* set Domain object Flame Smoke to 0 in the domain object of a fire simulation\n\nI've also added a particle system to visualize the force, while the fire remains unaffected:\n\n\nHere's a test file:[fire-test.blend](fire-test.blend)", "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)", "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)", "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.", "Connected Only option of Proportional Editing in Particle Edit mode doesn't work\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\n\nConnected Only option of Proportional Editing in Particle Edit mode doesn't work\nWhen you try to edit a single hair curve, Proportional Editing affects the nearest curves as well, whether the Connected Only option is enabled or not.\n\n", "Can't stop audio playback when using multiple windows\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29\n\nBroken: version: 3.3.1\n\nAfter creating New Main Window, the Video Editing cannot be played normally\n\n1、Create a new scene \"Scene001\" in the Video Editing interface Sequencer window of “scene” \n2、Create a New Main Window to open another scene\"scene001\" and enter 2D Anmation,and draw\n3、At this time, the picture of the \"scene\" cannot be played normally, but the sound will continue\n\n[ceshi.blend](ceshi.blend)\n", "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)" ]

[ "Mantaflow: Same particles for Spray, Foam and Bubble\nOperating system: Windows 10 Pro\nGraphics card: RTX 2070 and GTX 1060\n\nBroken: ( 2.82, 5467f3de3a4a, master, 2019-12-18, as found on the splash screen)\n\nEvery time I press bake on the Particels of my Fluid Domain the Particle systems of Spray, Foam and Bubble are/look the same.\n\nOpen:\n[mantaflow.blend](mantaflow.blend)\n- Bake simulation.\n- Bake particles.\n- Check out the resulting particles." ]

[ "Multires clay brushes performance issue\nOperating system: Linux-5.4.0-42-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.90.0 Beta\n\nWhen using the multires modifier for sculpting the performance seems to suffer significantly for certain brushes. This gets even worse on lower levels so the performance often is much worse on level 1 when compared to level 3.\n\n[2020-08-03 16-22-39.mp4](2020-08-03_16-22-39.mp4)\n\nThe performance seems to be especially bad on the Clay & Clay Strips brushes.\n\n**Example .blend file**\n\nJust to make sure the performance is as reproducible as possible, here is the file of the jacket.\nWhen trying to reproduce this performance on a cube or Suzanne head it wasn't as bad but still noticeable.\n[jacket.blend](jacket.blend)", "Geometry 100% transparent still affects Subsurface Scattering in the same mesh\nrenderer:\t'NVIDIA GeForce RTX 3060/PCIe/SSE2'\nplatform: 'Windows-10-10.0.19044-SP0'\nAMD Ryzen 2990wx 32-core 64gig ram no overclock\n[system-info.txt](system-info.txt)\n\nVersion: 3.2.2 - 3.4.1\n\nThe included file is a section of a skull with eyebrows close to the surface. \n\nUsing SSS for the skull and transparency for the eyebrows, the result is the eyebrow is light on the surface of the skull.\nThis is using CLOSURE_BSSRDF_BURLEY_ID walk.\nUsing random walk the eyebrow renders transparent.\nHappens on CPU or GPU\n\n\n- Load up the supplied file.\n- render by hitting F12 (Notice the eyebrows are leaving a bright silhouette on the skull surface).\n- Now switch both the eyebrow and skinhead scatter shaders materials to random walk for method.\nIssue goes away and the eyebrows are 100% transparent.\n\n[badeyebrowswithscatter.blend](badeyebrowswithscatter.blend)\n", "Autosmooth + Custom Normals is slow\nOperating system: Windows 10\nGraphics card: Nvidia mx230\n\nBroken:\nmaster\n\n\nUsing autosmooth and custom normals at the same time is slow, even in situations where you wouldn't\nexpect normal calculation to happen (like moving an object in object mode).\n\n\n[normal_autosmooth_slow.blend](normal_autosmooth_slow.blend)\n\n - Load the .blend file. Move the object around, it should be slow. \n - Either disable autosmooth, or clear custom split normals.\n # Moving the object should now be a lot faster\n\n", "Clay strips brush freeze when coming from outside the horizon of surface curvature\nOperating system: Linux-5.4.0-121-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.151\n\nBroken: version: 3.2.1\n\nClay strips brush freeze when reaching horizon of surface curvature\n\nOpen blender, then open a new sculpt file, select the clay strips brush, change the direction of the effect to subtract and change the space distance to scene and disable the adjust strength for spacing.\nWhen coming from outside the object blender freezes or lags creating sometimes artefacts in the horizon of the object.\n\nIn this video you can see the normal behaviour with view spacing distance and with scene spacing distance wile adjust strength for spacing is enable, and then the buggy behaviour.\n\n[vokoscreen-2022-07-12_15-29-16.mp4](vokoscreen-2022-07-12_15-29-16.mp4)\n", "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", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "Node Editor gets unusably slow in scenes of average production complexity\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.1.2\nWorked: Probably never\n\nThe node editor, as well as other parts of Blender get unusably slow when the scene complexity reaches level of average production scenes from about 5-10 years ago (About 30 million triangles on average). This even includes the operations, which should not require re-evaluation of the entire complex scene dependencies, such as moving unconnected nodes in the shader editor.\n\n[SlowScene_Base.blend](SlowScene_Base.blend)\n1. Open the attached .blend file:\n2. Select all the objects in the scene and convert them to meshes using Object->Apply->Visual Geometry to Mesh (this step was necessary to keep the repro file size small)\n3. Attempt regular material editing operations in shader editor, such as adding nodes, moving nodes around, editing properties of nodes, such as color ramp sliders, and so on\nResult: The constant UI blocking freezes make it impossible to work with the node editor when scene complexity exceeds trivial level.\nExpected: The performance of the node editor remains acceptable in the scenes of production complexity.\n\nNote: Feel free to duplicate the objects in the viewport to increase the severity of the lags and freezes.\n\n---\n\nBit of research: this is because of UNDO.\n\nIf you turn OFF `Global Undo` in the Preferences (or set `Undo Steps` to zero) everything is back to being snappy fast.\nNot sure if this can be smarter, but this does make sense in a way because Global Undo keeps a copy of the whole file in memory?", "Viewport performance slows down when using OptiX Denoiser on Windows machine with dual GPUs.\nOperating system: \nWindows 11 (Windows 10 has the same bug)\nGraphics card: \n2x Geforce RTX 3090\nGraphics driver\nNvidia Driver 511.65 / 511.79 / 472.12 ...\n\nBroken: \nBlender 3.10 05697470abd0d / All versions of 3.1, 3.0 and 3.2 are the same.\n\nWorked: \nBlender 2.90\n\nViewport render slows down when using the OptiX viewport denoiser with two GPUs enabled using OptiX.\nIf you check only one GPU, it will work at a normal speed.\n\nAs far as I know, it is a bug in Windows 10 and Windows 11, probably it works normally in Linux.\n\n1. Run Blender on Windows.\n2. Check the two GPUs on OptiX in Preferences.\n3. Turn on Viewport Denoiser (OptiX)\n4. Rotate the basic cube. It's slowly rendered.\n5. Uncheck one GPU. It works fast normally.\n\n[1.mp4](1.mp4)", "GPU Subdivision: Slow operations with Shape Keys\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3, 3.2\n\nWith the GPU subdivision turned on, many operations with shape keys (locking, changing the active shape key) are quite slow, but the reason for the delay is the GPU subdivision itself, because when it is turned off, the speed of operation is several times higher\n\nselect the body itself, and perform various operations with the shape keys (for example, changing the active one). Compare the speed with the GPU subdivision turned off and on\n[kira_lite.blend](kira_lite.blend)\n[2022-10-09 22-50-29.mp4](2022-10-09_22-50-29.mp4)", "Cycles subsurface handled differently in the diffuse passes\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.1\nWorked: version: 2.93.8\n\nWhen a material has subsurface, the diffuse passes now show a discrepancy in how they are handled compared to versions prior to 3.0.\nIn 2.93, the diffuse color pass for Cycles was similar to Eevee. Now the color pass is brightened even when the subsurface value is low (but nonzero).\n\n|Eevee|Cycles 2.93.8|Cycles 3.1.2|\n| -- | -- | -- |\n||||\n\nTest file:\n[#96967.blend](T96967.blend)\nThis is a part of the [junk shop file from the blender cloud.](5dd6d7044441651fa3decb56)\nThe diffuse color pass is sent to the composite output.\nYou can compare rendering using Eevee and Cycles.\n\n\n", "Cycles: GPU Performance\n**Memory usage**\n\n- [x] Auto detect good integrator state size depending on GPU (hardcoded to 1 million now)\n- [ ] Reduce size of IntegratorState\n - [x] Don't store float4 as float3\n - [x] Don't allocate memory for unused features (volumes, sss, denoising, light passes)\n - [x] Dynamic volume stack size depending on scene contents ([D12925](D12925))\n - [ ] Overlap SSS parameters with other memory\n - [ ] Compress some floats as half float\n - [ ] Reduce bits for integers where possible\n - [ ] Can diffuse/glossy/transmission bounces be limited to 255?\n\n- [ ] SoA\n - [ ] Individual arrays for XYZ components of float3?\n - [ ] Pack together 8bit/16bit values into 32bit?\n\n- [ ] Reduce size of ShaderData\n - [ ] Compute some differentials on the fly?\n - [ ] Read some data directly from ray/intersection?\n - [x] Don't copy matrix if motion blur is disabled\n\n- [ ] Reduce kernel local memory\n - [ ] Dynamically allocate closures based on used shaders\n - [ ] Dynamically allocate SVM stack based on used shaders\n - [ ] Check if SVM stack is allocated multiple times\n - [ ] Check on deduplicating ShaderData instances\n - [ ] Check for other unknown sources of memory usage\n - [x] Use either `shade_surface` or `shade_surface_raytrace` for reserving memory\n\n**Kernel Size**\n\n- [x] Replace megakernel used for last few samples? Only helps about 10% with viewport render, barely with batch render. But makes OptiX runtime compilation slow.\n- [x] Make `svm_eval_nodes` a templated function and specialize it for\n - [x] Background\n - [x] Lights\n - [x] Shadows\n - [x] Shader-raytracing\n - [x] Volumes\n- [x] Avoid shader ray-tracing for AO pass ([D12900](D12900))\n- [x] Verify if more specialization is possible in `svm_eval_nodes` (seems not)\n- [ ] Deduplicate shader evaluation call in `shade_background`\n\n**Scheduling**\n\n- [x] Make shadow paths fully independent so they do not block main path kernels ([D12889](D12889))\n- [x] Accurately count number of available paths for scheduling additional work tiles\n- [x] Compact shadow paths similar to main paths ([D12944](D12944))\n- [x] Consider adding scrambling distance in advanced options ([D12318](D12318))\n- [x] Compact path states for coherence\n- [ ] Tweak tile size for better coherence\n- [ ] Tweak work tiles or pixel order to improve coherence (many small tiles, Z-order, ..)\n- [ ] Try other shader sorting techniques (but will be more expensive than bucket sort)\n - [ ] Take into account object ID\n - [ ] Take into account random number for BSDF/BSSRDF selection?\n- [ ] Overlapped kernel execution\n - [ ] Use multiple independent GPU queueus? (so far was found to be 15% slower)\n - [ ] Use multiple GPU queues to schedule different kernels?\n- [ ] Optimize active index, sorting and prefix sum kernels\n - [ ] Parallelize prefix_sum\n - [ ] Build active/sorted index array for specific based on another array indicating active paths for all kernels, especially when number of paths is small\n- [ ] Try pushing (part of) integrator state in queues rather than persistent location, for more coherent memory access\n - [ ] Check potential performance benefit by coalescing state\n - [ ] Shadow paths\n - [ ] Main path\n- [ ] Cancelling renders and updates can be slow due to the occupancy heuristic that schedules more samples. Find a way to reduce this problem.\n- [ ] Shader sorting and locality balancing ([D15331](D15331))\n - [ ] Find better heuristics for scenes with many shaders\n - [x] Use for GPU devices other than Metal\n- [ ] Shader sorting by node graph similarity, to find coherence if e.g. the graph only has different image textures\n\n**Display**\n\n- [x] For final render, let Cycles draw the image instead of copying pixels to Blender\n - [x] Render pass support\n\n**Render Algorithms**\n\n- [x] Use native OptiX curve primitive for thick hair\n- [x] Transparent shadows: can we terminate OptiX rays earlier when enough hits are found? ([D12524](D12524))\n- [x] Transparent shadows: tune max hits for performance / memory usage\n- [ ] Detect constant transparent shadows for triangles and avoid recording intersection and evaluating shader entirely\n- [ ] Detect transparent shadows that are purely an image texture lookup and perform it in the hit kernel\n- [ ] For volume stack init, implement volume all intersection that writes directly into the stack\n\n**Tuning**\n\n- [ ] Automatically increase integrator state size depending on available memory\n- [ ] Tweak kernel compilation parameters (num threads per block, max registers)\n - [ ] Different parameters per kernel?", "Solidify (Complex, Constraints) - very rare glitch\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.1\nWorked: 3.1.2\n\nbehavior changed in c2e8e68b6517b91eb14270707d7182c1727861c4\n\nSolidify modifier creates a weird glitch at a specific vertex.\n\nI have a model with about 40000 verticies that I wanted to solidify. Everything works fine, except the surroundings of a single vertex. The topology does not seem any particular there. The model is made out of triangles, but the glitch also appears if I convert it to quads. I copied the vertex and the surrounding faces to a sperarate blender file and recorded how the glitch appears depending on moving one of the verticies:\n\n(the glitch looks exactly the same when the vertex is part of the larger object)\n\nSolidify Modifier Settings:\nMode: Complex\nThickness Mode: Constraints\n(other settings does not affect the glitch)\n\n", "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", "Ngons creating unwanted lines in Freestyle\nWindows 7 Pro 64-bit\nIntel Core i7-4770K CPU @3.50GHz\nASUS nVidia GeForce GTX 760 2GB GDDR5 DirectCU Mini\n\n\nBroken: (example: 2.70 47e9057\n```\n ...also broken in Blender official 2.69 and official 2.70\n```\n\n\n\nFreestyle has a problem rendering Ngons in such a way that extra, unwanted lines are generated.\n\nIt appears to be a faulty subdivision of the Ngons during that part of the render process where the information is passed through to Freestyle for creating the strokes.\n\nIf the Ngons are first triangulted – either by hand or else using the triangulate modifier – then the faulty lines do not appear in the Freestyle render.\n\nThe images show the problem.\n\nImage 01 shows the render with the faulty lines indicated. \n\nImage 02 shows the mesh. The Ngons that give the problems are selected. \n\nImage 03 again shows the mesh, this time with the Ngons triangulated. \n\nImage 04 shows the correct render following triangulation of the Ngons that give the trouble. \n\nHere is the blend file. [FS_bad_Ngon_render.blend](FS_bad_Ngon_render.blend)\n", "Eevee slower than cycles when using a lot of particles or collection instances\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 17)\n\nWhen using a lot of collection instances with particles in them, or with a lot of objects, Eevee seems to be very slow in evaluating the scene. \neevee: 2min and 2sek \ncycles (gpu): 9sek\n\nopen the file switch to cycles - hit render\nswitch to eevee hit render\n" ]

[ "Freeze when you add a Subdivision Surface modifier to an ngon with many sides\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.60\n\nBroken: version: 3.2.0 Alpha\n\nBlender crash when you apply a Subdivision Surface modifier to an object\n\n\n1- Open the attached file [bug1.blend](bug1.blend)\n2- Apply a Subdivision Surface modifier to selected object (Cylinder.001)\n\nResult: Blender crash\n\nBye!\n\n", "Blender monstrously slow in sculpt mode\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\n\nI doubt this is a bug but to me it makes no sense at all that Blender can be this slow. I've always avoided sculpting in Blender because it's so slow but someone reassured me that it got faster in recent versions.\n\n[2022-08-20 10-43-38.mkv](2022-08-20_10-43-38.mkv)\nHere's a video to show what I mean. Simply going from around 50k faces to 100k via one increase in subdivision level takes almost a minute of Blender not responding. Surely this isn't by design? The scene is just one UV sphere.\n\n", "Subdivision Surface Performance Degrades Markedly With Non-Quad Meshes\nOperating system: Windows 7 Pro X64\nGraphics card: Nvidia Geforce GTX 980 Ti\n\n\nBroken: Date: 2019-01-21\n```\n Hash: dd3f5186260e\n Branch: Blender 2.7 (although it's supposed to be a 2.80 Beta)\n```\n\n[OpenSubDiv_PerformanceBug.zip](OpenSubDiv_PerformanceBug.zip)\n\nSubdivision surfaces are fast and responsive in Edit mode *with all-quad meshes*, but very slow (~ 10x slower) with meshes comprised of triangles and quads.\n\n\nOpen the attached blend file and select **Cube.001**\n\nGo into Edit mode. Turn on Proportional Editing. Grab a point and move it - observe how responsive the viewport is with the all-quad mesh.\n\nGo back to Object Mode. Select **Cube**. Go back into Edit Mode. Grab a point and move it (with proportional editing still turned on) Observe how slow it is.\n\n", "Adding subdivision surface modifier freezes (or takes incredibly long) with a certain mesh\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0 Beta\n\nWhen adding a subdivision surface modifier to the object in the attached .blend file, Blender will lock up for some time (I haven't seen it actually finish, it's possible it might at some point?)\n\nEven when removing the modifier and merging vertices by distance to clean the mesh up a bit, the problem remains\n\nI wish I could describe in the report what it is about this mesh specifically that led to this, but I'm out of ideas\n\nOpen the attached .blend file, and attempt to add a subdivision surface modifier to the object inside.\nBlender will freeze calculating, as though this mesh was many times higher poly than it actually is.\n\n[subdiv_freeze.blend](subdiv_freeze.blend)\n\n", "Subdivision Modifier problem with n-gons\nOperating system: Win 10 home\nGraphics card: Gtx 970\n\n**Blender Version** \nBroken: 2.80 Beta \nDate 2019-01-04 a77b63c56943\n\nAdding Subdivision Modifier to a cylinder with n-gon caps is too slow.\nIt work Ok if the cylinder is all quads\nAdd a cylinder go edit mode subdivide a few times , back to object mode and try to add Subdivision modifier \nBased on the default startup or an attached .blend file (as simple as possible).\n", "Certain objects (probably depend on mesh topology) will cause extrime lag after adding Subdivision modifier\nOperating system: WIndows 10 Home\nGraphics card: RTX 2060, Studio Drivers\n\nBroken: 2.93, 3.1.2\nWorked: -\n\nObject with 15k polygons, empty modifier stack will create **huge** lag (can crush blender as well i guess) if you try to put Subdivision Modifier on it.\nFor same Blender scene object with 49k polygons will not create any really noticiable lag in same situation. \nIt will happen in both GPU Subdivision on or off.\n\nTry to put Subdivision modifier into object next to the cube. It will create huge lag before (even if) it will finally apply and whole Blender window will response again. [subd_issue.blend](subd_issue.blend)\n\n**additional info**\nThe file was also tested on different PC with Linux Manjaro 64bit OS, GTX 1070 with same results. It create huge lag, make Blender window not responding, and after lag it finally apply the modifier.", "Ngons + Subdivision modifier causing massive performance issues\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 61)\nWorked: (optional)\n\n\nI have an object called 'Base' in the attached blend file. It has a number of ngons. It has a sub surf modifier. If I add another object, such as a circle and attempt to use the Last Operator panel, each operation takes around 22 seconds. Undos take an equal amount of time. If I delete or triangulate the ngons the problem is mitigated. If I turn off the Subdivision modifier the problem is also much lessened. The same object appended to 2.79 causes no such performance issues. It's largely down to poor modeling practices on my part, but it feels wrong and I wonder what's causing it?\n\n1 Open file\n2 Shift+A and add a Circle\n3 Change the number of vertices in the Last Operator panel\n4 Note the time it takes before user control is returned\n5 Move the newly added circle\n6 Undo\n7 Note the time it takes before the undo operation is completed.[goblin_mini.blend](goblin_mini.blend)\n\n", "2.8 - Subdivision Surf Modifier poor performance in this mesh\nOperating system: Linux-5.0.1-050001-generic-x86_64-with-Kubuntu-18.04-bionic 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.43\n\n\nBroken: version: 2.80 (sub 50)\n\nOpen this .blend file:\n[bad_perform_subsurf.blend](bad_perform_subsurf.blend)\nAdd subsurf modifier on the selected object by default. On my machine Blender hangs, one thread of the CPU working 100%\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", "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).", "UI Accessibility: The color of grid emphasis lines is not light/dark enough to see easily. A color setting for accessibility would fix this.\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.3.0 Alpha\n\n\nSometimes the colors of grid lines and the grid emphasis lines are very similar. Especially when zooming in or rotating. Grid color can be controlled in the settings area but not grid emphasis color.\n\n\nJust open a file and zoom so the grid fills the screen. When you are close it is almost impossible to see the difference between grid line and emphasis line.\n\n\n\n\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)", "Smoke Shadow glitches in Cycles (workaround only with Fluid \"Empty Space\" option)\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D700](D700) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.21\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nWeird artifacts and boxes appear in the shadows of smoke simulations\n\n\nI've seen this happening in different simulations with different results. Sometimes it is a big square in the shadows like in the image attached. Sometimes it's just little squares.\n\nGenerally speaking the workflow I'm following when I see these errors is the following:\n\nSet the scene to cycles\nCreate ground plane\nCreate Sun Light\nCreate smoke domain\nCreate smoke emitter with particles\nSet smoke flow to emit fire and smoke from particles\nCaches simulation\nRender with Cycles\nGlitches appear in the shadows of the smoke\n\nAttached is a blend file and the render result with glitches\n\n[VolumetricsTest.blend](VolumetricsTest.blend)\n\n", "Render glitches on cycles when 'Motion Blur' and 'Use Limit Surface' are turned on. \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\nAlso broken in: 2.93.0 Alpha, branch: master, commit date: 2021-03-20 21:00, hash: 9ca67c47a152, type: Release\nbuild date: 2021-03-20, 23:00:48\nWorked: unknown. This file was created within 2.92\n\nWhen rendering this file I get (for me) random glitches in the render, when Motion Blur is active in Cycles.\nIn the attached file you can see this in for example frames 13,46,77 and 153 (amongst others) for the figure on the left and in frames 57,65 and 82 for the figure on the right.\nTurning off motion blur makes the glitches go away. It happens - for me - both with CPU only and with GPU renders.\n\nThe only objects - as far as I can tell - that produce these glitches are the two 'jasjes' with the material called 'overhemd'. (changing 'overhemd' to a different color also changes the glitches to that same color) Apart from the very obvious triangular glitches, you can also see some sort of wrinkly render errors near the ties on the shirt that only appear when the glitch is visible.\n\nFrame (13) with a glitch: \nFrame (14) without a glitch: \n\nThe objects started out as duplicates of each other.\n\n- Open attached file\n- Render frame 153 (or any of these: 13, 46, 77)\n\nI'm sorry the file is as large as it is, but I haven't had this happen in other renders/files yet, so I couldn't reproduce with another file.\nPlease let me know if you prefer to get Dropbox links instead of an actual upload.\n\n[Statler_en_Waldorf_animatie_013.blend](Statler_en_Waldorf_animatie_013.blend)", "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 |", "Evee Shading artifacts on metallic surfaces with mid roughness\nOperating system: Windows 64bit\nGraphics card: GTX 950\n\nBroken: (example: 2.81 Alpha, ad21a6c22461, 2019-09-08\n\nWhen renderign with Eevee I get ring shaped bright spots around GGX highlights.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nStart with a new file, delete the vertex at position 1, -1, 1\nAdd a metarial to this cube.\nset metallic to 1\nset roughness to a value between 0.2 and 0.4\n\nset the power of the pointlight to 100W\nset the radius to 0\nmove it to (0.5, -0.5, 0.5)\n\nset the background color to black\n\nview it from the top in perspective mode\nyou should see a grey ring at a corner.\n\nIn my personal experience this might be caused by an unnormalized vector in the ggx calculation.\n\n\nThe .blend file and a screenshot:\nIndirect Lighting settings dont help since there is no indirect lighting going on. As far as I can see it's a problem with the microfacet shading.\n[bug.blend](bug.blend)\n\n", "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", "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", "Orange tile boxes appear in the wrong place when using border render and viewing a different slot than the one being rendered in\n\nOperating system: Linux Mint 18.3 64-bit\nGraphics card: N/A; rendering on Intel i5-4460\n\n2.80 beta, 918941483f7e, blender2.7, 2019-02-27, 00:14\n\nWhen using border render (but not if rendering the full image), the orange tile boxes show up in the wrong place *when viewing another slot aside from the slot being rendered in*. They are a few hundred pixels too low.\n\n[F6720951](render-2019-02-26_21.28.51.mp4)\n\nOpen Blender.\nHit F12.\nAfter it renders, press CTRL+B, and select some portion of the render area.\nRender.\nPress J to switch to Slot 2 and render there too, so the canvas becomes visible.\nRender on either slot, and switch to the other.\nTake note of where the boxes are compared to where you set your render border at.\nCancel rendering/let it finish.\nSwitch back to Slot 1 to verify that the correct area was rendered and that the boxes were below it.\n\nI discovered this on 893fa5983193e from 3 days ago, but downloaded the latest version and did a quick test to make sure it still happens.\n\nI also noticed that after I rendered, set a render border, and started rendering again, it actually rendered the whole image - only the bordered area was visible, but it rendered everything else too. After that first time, it only rendered the bordered area, as it should.\n\n[F6721094](render-2019-02-26_22.08.33.mp4)\n\n(I set samples to 512 in order to slow rendering so I would have time to switch slots and show what happens before it finishes rendering.)\n", "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)", "Icon Alpha property also affects the thumbnails of matcaps/studio lighting...\nOperating system: Win 10\n\nBroken: blender-2.91.0-68797982025c-windows64\nWorked: ?\n\nThe \"Icon Alpha\" property in the Themes settings also affects the thumbnails of stuff like matcaps/studio lights....\n\nGo to: Edit -> Preferences -> Themes -> User Interface -> Styles; now try to adjust the \"Icon Alpha\" property while the matcaps panel is open to see the effect...\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)", "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" ]

[ "Blender crashes when using Cycles Progressive Refine in OptiX CPU + GPU mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.92.0 Alpha, branch: master, commit date: 2020-12-14, hash: `010f44b855`\n\nWhen Optix with CPU + GPU is activated in the Preferences, the Render Properties ➔ Performance ➔ Tiles ➔ Progressive Refine option makes Cycles crash, at least on my system.\n\n- In the Preferences, switch to OptiX and check both CPU and GPU.\n- In the Render Properties, switch To Cycles and GPU.\n- In the Render Properties, switch on Performance ➔ Tiles ➔ Progressive Refine.\n- Start a rendering with F12.\n- Blender crashes shortly after the rendering has started." ]

[ "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", "Having too much hair particles creates visual glitches\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: not really sure, but it may have been in blender for some time\n\nHair strips gets a really bad distortion once they reach a certain threshold of number, children and \"additional subdivisions\"\n\n\nUsing a ball with 2 subdivisions:\n\n| 1 | Furball with hair strips, 0 additional Subdivisions, 20000 particles and 80 interpolated children |  |\n| -- | -- | -- |\n| 2 | Furball with hair strips, 1 additional Subdivisions, 20000 particles and 80 interpolated children |  |\n| 3 | Furball with hair strips, 1 additional Subdivisions, 20000 particles and 60 interpolated children |  |\n| 4 | Furball with hair strips, 1 additional Subdivisions, 18000 particles and 60 interpolated children |  |\n| 5 | Furball with hair strands, 1 additional Subdivisions, 18000 particles and 60 interpolated children (hair gets scrambled where the glitch is happening) |  |\n| 6 | Furball with the exact same configuration as the first glitchless one, but with 3 Strand steps on Viewport Display instead of 2 |  |\n\nSo it seems like a mix of a lot of segments and a lot of particles create those glitches.\n\nThe file bellow contains the furball with the second configuration\n[furball.blend](furball.blend)\n", "\"Long Hair\" children pulled to world origin when using Texture (2.93.4 regression)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.4\nWorked: 2.93.3\n\nMy particle hair system works as expected in 2.91+ up to 2.93.3:\n\n\nIn 2.93.4, the children are pulled towards world (not object) origin:\n\n\nThis appears to only happen IF a texture is used to affect Density AND \"Long Hair\" is checked.\n\n\n\n1. Move default cube away from origin\n2. Add particle system\n3. Enable interpolated children\n4. Check \"Long Hair\"\n5. Add a Texture (even a cloud texture works)\n6. Enable Density influence\n\n\n\nBlend file with error:\n\n[Bug3.blend](Bug3.blend)\n", "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", "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", "Hair particles: rekeying, cut tool, subdividing do not interpolate existing weights (breaking simulation)\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 51)\nWorked: (optional)\nJust click once sometimes work right\n\n\nThis bug happen in both 2.79 and 2.8\nClick and drag the hair cut tool mess up the vertices position, especially after subdividing one or 2 segments of the hair. After the hair is messed up, it can't be fixed using rekey command.\nDragging the cut tool on a hair that is not subdivided also cause the problem, but not as severely, the vertices become unevenly positioned.\n\n\nCreate a hair system on the default cube, set the emission number to 1.\nGo to particle edit mode, subdivide one or 2 segments of the hair.\nUse the cut tool, click and drag from the tip of the hair.\nThe hair is now completely messed up.\n", "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.", "Particle system behaves inconsistently in viewport and render when instance object visibility is disabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro [P2200](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.91.0 Beta\nWorked: The behavior was different in 2.80\n\nWhen the instance object of a particle system is disabled in the viewport the particles are also disabled in the viewport. However when the instance object is disabled in render they still appear in the render.\n\n1. Open the default scene.\n2. Create another object (B).\n3. Create a particle system modifier on the default cube (A).\n4. Set Particle Settings to Hair (A).\n5. Set Render -> Render As to \"Object\" (A)\n6. Set the Instance Object to the other object (B).\n7. Disable the object (B) in viewport and render\n8. Render the scene, observe that the object has particles rendered\n[particle_visibility_bug.blend](particle_visibility_bug.blend)\n", "Mantaflow - Enabling \"Noise\" breaks fast-moving smoke\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 650 Ti\nProcessor: Intel® Core™ i7-3770\n\nBroken: 2.83.0\nWorked: Never\n\nEnabling noise on fast-moving smoke produces a \"grainy\" result that doesn't match original simulation.\n[C - High Speed Noise - Demo.mp4](C_-_High_Speed_Noise_-_Demo.mp4)\n\nAlso, this problem is less profound when the cache type is set to \"Final\", though still clearly visible.\n\n**Exact steps to reproduce the error**\n1. In any smoke simulation, dramatically increase the velocity of the smoke, either in the emitter settings, or with a force-field.\n2. Bake Data\n3. Bake Noise\n\n[Noise on High-Speed Smoke.blend](Noise_on_High-Speed_Smoke.blend)", "Regression: Mesh render artifacts\nOperating system: Windows 10\nGraphics card: GTX 1070 TI\n\nBroken: 3.1, 3.6\nWorked: (3.0.1)\n\nNormals on hair mesh is corrupted in newer versions of blender while being perfect in older ones.\nMesh name is LOD0_1_front_hair_omote597.\n\n- Open the attached .blend file\n- View the model/mesh in normals/ambient occlusion render pass (cycles)\n\n", "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", "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 stopped working after editing and combing in \"Particle Edit\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.1.0 Alpha\n\nHair dynamics stopped working after editing and combing in \"Particle Edit\"\nPossible duplicates: #91258, #56818\n\n[#93344.blend](T93344.blend)\n\n- Open file\n- Cut hair with Cut brush\n# Comb hair with Comb brush with disabled Preserve Strand Lengths option\n\nSimulation no longer works", "Mantaflow - Flickering Square pattern of the particles\nOperating system: Windows 10\nGraphics card: Quadro RTX 4000\nCPU: Ryzen Threadripper 2950x\nRAM: 64GB\n\nBroken: (2.90.0 // 2.83.5)\n\n\nI got the Problem both in the 2.83 LTS & 2.9 Version:\nIf i bake the fluid simulation in Mantaflow the particles of Bubble & Foam result in flickering squares: In one frame the particles are present and in the next frame they are abscent (in a square pattern). If I render an animation sequence out of this the video is flickering. I added the .blend-File for the used Settings and also two screenshots to demonstrate the square Pattern. Furthermore a rendered animation of another scene of mine shows the flickering result when rendered. \n\n\n[Mantaflow Flickering.avi](Mantaflow_Flickering.avi)\n\n[2020_09_19 - Fluid Test.blend](2020_09_19_-_Fluid_Test.blend)\n\n\n\n\n\nJust bake the attached .blend File (You need to change the saving location)", "One of four edited hair systems won't simulate unless edit is deleted\nOperating system: Win10\nGraphics card: GTC 1060\n\nBroken: **2.92.0 master 2021-02-24 16:25 02948a2cab44** and **2.93.0, master 2021-06-02 11:21 84da05a8b806**\nWorked: Didn't find a working version\n\n4 particle systems, one (\"Back\") won't sim unless the edit is deleted. It stays in place and stretches towards the animated head cap.\n\n**Attempted things to fix it:**\nDelete all bakes and resim - failed\nChecked the weight painting - doesn't seem to be the source of the issue\nAppend into new files and resim - failed\nDisabled dynamics - now everything moves with the haircap, but obviously no sim\nRemoved hair edit - now it works but I loose the edit\n\nOpen the file and press space to run the sim and animation. I would not know how to make a sim from scratch which won't work though so I'm sending the file.[hair_bug.blend](hair_bug.blend)" ]

[ "Hair Dynamics (no collision): exploding...\nOperating system: windows 10 version 1803\nGraphics card: NVIDIA GeForce GTX 1060 3GB\n\nBroken: blender-2.80-d986b04bd302-win64\\blender-2.80.0-git.d986b04bd302-windows64\nWorked: (optional)\n\nHair dynamics not working. Tried baking etc but no joy. \n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nJust press render\n[Hair_explosion.blend](Hair_explosion.blend)\n" ]

[ "Meshes that are generated with the screw modifier cant use the box projection type\nOperating system:\nGraphics card:\n\nBroken: 83f9218801d4\n\nThe meshes that are modified or extended by the screw modifier can't use the box projection of an image map. All the objects in the screenshot use the same material and the texture projection. As you can see the box and the plane has no problem with the projection type.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLoad the attached .blend\n\nEnable the material preview and check the object named \"Screw\"\n\nCtrl-A -> \"visual geometry to mesh\" to see that the texture would normally work on the mesh, except ehwn the modifier is enabled.\n\n[_23012023_1655_00.zip](_23012023_1655_00.zip)", "Image Texture sampling by int X and Y pixel indices\nImplement the ability to sample an image not only by the position vector, but also by the pixel coordinates.\n\nSince this implies some simplification of the already implemented code, it would be convenient to either reuse the existing sampling code for another node, or switch the mode of operation in the original node. The variant of the `image_closest_texture_lookup` method for `ImageFieldsFunction` with integer support looks as close as possible.\nThis also implies, there is no need for interpolation methods.", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "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", "Texture properties not working with OSL enabled and unpacked textures\nOperating system: Linux-5.11.7-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (SKL GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.92.0\nBroken: version: 2.93.0 Alpha\n\nI have a texture with RGB channels set to 1 and alpha set to 0. When trying to use this texture with OSL, the alpha property (at least) of the image texture node does not work when the texture is unpacked. I set it to channel packed, expecting the color data to be always white. The problem is that when the texture is unpacked, the color data is black.\n\n1. Open the attached file.\n2. Set viewport shading to rendered.\n3. The plane shows as white (as it should).\n4. Unpack the texture.tga file.\n5. Toggle between preview and rendered viewport shading to refresh.\n6. The plane now shows as black.\n7. Pack the texture again.\n8. The plane shows as white again.\n\n[bug.blend](bug.blend)", "\"Material preview\" shows always eevee mat branch / never cycles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.82 (sub 6)\nWorked: never, I think\n\n\"Material Preview\" shows always the material output assigned to eevee, but I want the cycles branch. Changing renderengine or the active material output node doesn't change anything.\n\nOpen the blendfile and try to preview the material with \"cycles\" image - without going to rendered viewport. The material preview seems to always use the node tree going to the Eevee material output node, even when the render enging is set to Cycles.\n[specific_material_output.blend](specific_material_output.blend)\n\n\n", "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", "Cycles: Baking to an externally loaded image fails to update the image buffer results in Cycle's Rendered Viewport Shading\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0, 2.93\nWorked: probably never\n\nBaking to an externally loaded image will not changed the baked image as displayed in the Viewport Shading's Rendered Mode.\nThe newly baked image buffer is shown correctly in the image editor and (EEVEE's) Material Preview, but wrong in Cycles's render view.\n\n- Open the attached .blend file.\n- Open the attached baked image in the image texture node.\n- Use it to bake any type of pass to the loaded image.\n- Observe that the image looks unchanged in the Rendered View by connecting the image texture node to the material output.\n[#98063.blend](T98063.blend)\n\n[2022-05-12 09-12-20.mp4](2022-05-12_09-12-20.mp4)", "Texture UV/Image Editor coordinates slightly inaccurate\n**System**\nGentoo with old Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550]\n\nSlightly broken: media-gfx/blender-2.79b-r1\n\nWhen zooming in as much as possible on a texture in the UV/Image Editor, there seems to be a pixel border at y≈235.994 instead of exactly at y=236 like I'd expect.\n\nAssuming the error was due to 32-bit floating-point rounding, the border coordinates should have at least 2 more digits of precision.\n\n", "VSE: Cycles displayed as Rendered in Scene strip makes Blender hang - and other Scene strip bugs\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nThe Render modes of Scene Strips are either missing or broken:\n- When Cycles is set as render and Rendered set as display, it'll make Blender hang.\n- Wireframe and Rendered doesn't work with any Render. \n- The only thing working is Eevee with either solid or Material Preview. \n- Workbench and Cycles settings seems to just use the Eevee render, since these are producing the same results in Solid and Material Preview.\n\n{[F10177251](scenestrip.gif),size=full}\n\nTest file:\nCycles is set up as render in the 3D Footage scene. In the Master Edit scene, switch display mode to Rendered. Blender will hang.\nTry the various other display modes and renders(by changing the render in the 3D Footage scene), to see wireframe and rendered doesn't work with any render. \n[multicam_3d_c.blend](multicam_3d_c.blend)\n\n\n", "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", "Crushed Velvet Eevee render problems in Cycles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: \n- 2.93.0 Alpha\n- 2.82 (sub 7)\nWorked: ?\n\n\nThe *Crushed Velvet* material from the *Material Library* does not render properly with Cycles when setting the device to *GPU*.\n\n- Load the simplified material attached below\n- Set the render device to *CPU* and render. The output should be all black\n# Set the render device to *GPU* and render.. Depending whether you have only GPU(s) activated in the preferences or also CPU(s) you should see one of the following. When only GPU(s) are enabled you should get a proper render. When CPU(s) are also enabled you should get dark render tiles that are rendered on the CPUs.\n\n[VelvetTestSimplified2.blend](VelvetTestSimplified2.blend)\n\n---\n\nOriginal description:\nI'm attaching the .blend file I used to test this issue. I'm not even sure this is a bug or simply me not being overly familiar with materials yet, but it feels like a bug. An dit may be a Blender bug and nothing to do with this add-on. Obviously, this material renders fine in Eevee, but it also renders fine in Cycles when using CPU to render, but has major artifacts when using GPU to render. I've attached a render to show what I'm getting in case you don't experience it.\n\nThe steps I took to get here are, \n\nBasically, I have a default scene I use to do my modeling or as a start point. It's very basic. I was experiencing this issue in another project I was working on and noticed it went away when I changed the material on one object. \n\n- I loaded up my basic start file\n- selected the sphere\n- Scrolled down to the Material Library VX panel in the Material Properties tab\n- Loaded the Sample Library\n- Chose the Crushed Velvet Eevee material and clicked Apply to Selected\n\nThat's it. I had initially thought it was simply a problem rendering in Cycles but for my first render, I forgot to switch from CPU to GPU and noticed it rendered fine. So I did a few more tests and it renders fine with CPU every time, but not with GPU.\n\n[VelvertTest.blend](VelvertTest.blend)\n\n", "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", "EEVEE: Blender Crashes when rendering specific File\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.93.0\nWorked: (N/A)\n\nBlender crashes when rendering specific file. It only seems to happen with this file - when I render other (even larger) files with the same inputs it works fine, but with this one it crashes every time. The error message is EXCEPTION_ACCESS_VIOLATION, but I received the data from an open source website and it is placed in a folder on my computer that I have full access to. Debug report: [blender_debug_output.txt](blender_debug_output.txt)\n\nSave NZ_Compressed40pc.jpg to desktop \nOpen Dev.blend\nIn the shader editor for the plane, ensure the image texture has NZ_Compressed40pc.jpg linked as input.\nRender>render image\n\nTest File:\n[Dev.blend](Dev.blend)\n", "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)" ]

[ "Eevee mp4 texture \nOperating system: macOS Sierra\nGraphics card: AMD Radeon R9 M390 2048 Mo\n\nBroken: 2.80 Beta\nDate : 2018-11-04\nHash c192ce6717d\nBranch: blender2.7\n\nHi. I've seen that a mp4 texture cannot be rendered in Eevee. The animation doesn't appear (it's stuck in a frame of the mp4)\nI've simply added a mp4 video as a texture with a diffuse and doesn't work. If I switch the render method to Cycle, I can clearly see that the video is working but not on Eevee :-)", "Movies do not play\n Windows 10\n\nblender 2.8 - 7e9389b83d8\n\nYou can add a video or a video on a plane as texture. Now a frame of the video is going to be shown. But the video won't play. Even not in the final render. It stands still at the same frame.\n\n[issue.blend1](issue.blend1) \nThe video won't be played on both things.\n", "eevee render - import video as plane \"not working\"\nOperating system: Interl(R) Core(TM) i5-8250U @1.60GHz 1.80 Ghz\nGraphics card: NVIDIA GEFORCE\n\nDate: 2018-12-25\nHash: 60b930ad3e73\n\nI cannot play a video on eevee. Is there any solution for this? \n\nI import a video using \"Import>Images as Planes\" . I'm using eevee, but when I play it doesn't make any changes. I don't want to use cycles. \n", "image sequence cant load\nOperating system: win10\nGraphics card: GeForce Gtx 1050 ti\n\nBroken: 2018-11-30 Hash: 0f5b53ba4dc\nWorked: 2.79b\n\nThe image sequence is not working - images are badly loaded or it looks like it has only one frame and can't find others.\n\nOnly basic steps - load new default blender, unwrap the cube > node editor > add image texture node > load the sequence > moving time line - slider > nothing00 happed\n\nhere is the blend file and sequence. In 2.79 it is functional.\nblender file: t-rIZkEpoaCX", "Video as texture EEVEE\nOperating system: Windows\nGraphics card: 940mx\n\nBroken: 2.80-7c438e5366b2-win64\nWorked: Animation\n\nI use video as texture and I try to play the video but it doesn't play during render and even play on viewport.\nI also try to import video as plane and video did not play also.\nBut I try it on CYCLE and no problem video played. \n\nBased on the default startup or an attached .blend file (as simple as possible).", "Blender 2.8 beta / Import image as planes - no movie refresh of frames\nOperating system: Windows 10 64 Bit\nGraphics card: 2 x Geforce GTX Titan X\n\nblender-2.80-a205493426b-win64 (2018-12-03)\n\nWhen importing an image as a plane, with a movie mateiral applied, the system does not refresh the frames.\n\nNo matter whether I apply a movie amteiral to a diffuse shader or PBR shader, or I Import a movie Clip as a plane, blender 2.8 beta does not seem to support Auto Frame refresh, at all.\nThis is - from my Point of vioew - a serious issue, since this - under 2.79xxx it works seamlessly! - is an essential asset for professional film making.\n", "Reference/Background Image with Movie don't refresh\nOperating system: Windows 7, 64 bit\nGraphics card: GTX 950\n\nBroken: 2.80, 91a155833e59, blender2.7, 2019-01-07\n\n**Reference** and **Background** Image with *movie* or *image sequences* not refresh on frame change or play animation (Alt+A) under **Eevee** and **Cycles** in Solid, LookDev and Rendered view.\n\n\n\n\nOpen attached file, play animation or change frame on timeline.\nChange render engine to Cycles, change view mode and change frame. \n\nBut when add the **background images** in the settings of the **Camera**, then the *image sequences* and *movie* is work, playing and display correctly under Eevee and Cycles. \nAlso, in Rendered view (Cycles) viewed only **Reference** and **Background** Image, but **background images** in the settings of the **Camera** not displayed.\n\n[Ref_Back_Cam.rar](Ref_Back_Cam.rar)", "Frames does not refresh in Shader Editor> Image Texture> source \"Movie\" or \"Image Sequence\" when animation with eevee\nOperating system:\nGraphics card:\n\nBroken:\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n****\n# Blender 2.80 (sub 39) System Information\n****\n\n\nBlender:\n****\n\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-30 15:30, hash: d96596de294e, type: Release\nbuild date: 31/12/2018, 01:58\nplatform: Windows\nbinary path: 'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\blender.exe'\nbuild cflags: /W3 /w34062 /w34189 /wd4018 /wd4146 /wd4065 /wd4127 /wd4181 /wd4200 /wd4244 /wd4267 /wd4305 /wd4800 /wd4828 /wd4996 /we4013 /we4133 /we4431 /w35038 /DWIN32 /D_WINDOWS /W3 /nologo /J /Gd /MP -openmp \nbuild cxxflags: /W3 /w34062 /w34189 /wd4018 /wd4146 /wd4065 /wd4127 /wd4181 /wd4200 /wd4244 /wd4267 /wd4305 /wd4800 /wd4828 /wd4996 /we4013 /we4133 /we4431 /w35038 /DWIN32 /D_WINDOWS /W3 /GR /EHsc /nologo /J /Gd /MP /EHsc -openmp \nbuild linkflags: /MACHINE:X64 /SUBSYSTEM:CONSOLE /STACK:2097152 /INCREMENTAL:NO /NODEFAULTLIB:msvcrt.lib /NODEFAULTLIB:msvcmrt.lib /NODEFAULTLIB:msvcurt.lib /NODEFAULTLIB:msvcrtd.lib /ignore:4049 /ignore:4217 /ignore:4221\nbuild system: CMake\n\nPython:\n****\n\nversion: 3.7.0 (default, Aug 26 2018, 16:05:01) [MSC v.1900 64 bit (AMD64)]\npaths:\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\addons_contrib'\n\t'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\scripts\\\\addons'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\addons'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\startup'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\modules'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\python37.zip'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\python\\\\DLLs'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\python\\\\lib'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\python'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\python\\\\lib\\\\site-packages'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\freestyle\\\\modules'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\addons\\\\modules'\n\t'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\scripts\\\\addons\\\\modules'\n\nPython (External Binary):\n****\n\nbinary path: 'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\python\\\\bin\\\\python.EXE'\nversion: Python 3.7.0\n\nDirectories:\n****\n\nscripts:\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts\\\\modules'\n\t'C:\\\\Program Files\\\\Blender Foundation\\\\Blender 2.8\\\\2.80\\\\scripts'\n\t'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\scripts'\nuser scripts: 'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\scripts'\npref scripts: None\ndatafiles: 'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\datafiles\\\\'\nconfig: 'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\config\\\\'\nscripts : 'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\scripts\\\\'\nautosave: 'C:\\\\Users\\\\CLENET\\\\AppData\\\\Roaming\\\\Blender Foundation\\\\Blender\\\\2.80\\\\autosave\\\\'\ntempdir: 'C:\\\\Users\\\\CLENET\\\\AppData\\\\Local\\\\Temp\\\\blender_a14748\\\\'\n\nFFmpeg:\n****\n\navcodec: '58, 18, 100'\navdevice: '58, 3, 100'\navformat: '58, 12, 100'\navutil: '56, 14, 100'\nswscale: ' 5, 1, 100'\n\nSDL:\n****\n\nVersion: 2.0.8\nLoading method: linked (WITH_SDL_DYNLOAD=OFF)\n\nOther Libraries:\n****\n\nOpenColorIO: 1, 1, 0\nOpenImageIO: 1, 8, 13\nOpenShadingLanguage: 1, 9, 9\nOpenSubdiv: 0, 0, 0\nOpenVDB: 5, 1, 0\nAlembic: 1, 7, 8\n\nOpenGL:\n****\n\nrenderer:\t'GeForce GTX 1050/PCIe/SSE2'\nvendor:\t\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 391.25'\nextensions:\n\tGL_AMD_multi_draw_indirect\n\tGL_AMD_seamless_cubemap_per_texture\n\tGL_AMD_vertex_shader_layer\n\tGL_AMD_vertex_shader_viewport_index\n\tGL_ARB_ES2_compatibility\n\tGL_ARB_ES3_1_compatibility\n\tGL_ARB_ES3_2_compatibility\n\tGL_ARB_ES3_compatibility\n\tGL_ARB_arrays_of_arrays\n\tGL_ARB_base_instance\n\tGL_ARB_bindless_texture\n\tGL_ARB_blend_func_extended\n\tGL_ARB_buffer_storage\n\tGL_ARB_clear_buffer_object\n\tGL_ARB_clear_texture\n\tGL_ARB_clip_control\n\tGL_ARB_color_buffer_float\n\tGL_ARB_compressed_texture_pixel_storage\n\tGL_ARB_compute_shader\n\tGL_ARB_compute_variable_group_size\n\tGL_ARB_conditional_render_inverted\n\tGL_ARB_conservative_depth\n\tGL_ARB_copy_buffer\n\tGL_ARB_copy_image\n\tGL_ARB_cull_distance\n\tGL_ARB_debug_output\n\tGL_ARB_depth_buffer_float\n\tGL_ARB_depth_clamp\n\tGL_ARB_depth_texture\n\tGL_ARB_derivative_control\n\tGL_ARB_direct_state_access\n\tGL_ARB_draw_buffers\n\tGL_ARB_draw_buffers_blend\n\tGL_ARB_draw_elements_base_vertex\n\tGL_ARB_draw_indirect\n\tGL_ARB_draw_instanced\n\tGL_ARB_enhanced_layouts\n\tGL_ARB_explicit_attrib_location\n\tGL_ARB_explicit_uniform_location\n\tGL_ARB_fragment_coord_conventions\n\tGL_ARB_fragment_layer_viewport\n\tGL_ARB_fragment_program\n\tGL_ARB_fragment_program_shadow\n\tGL_ARB_fragment_shader\n\tGL_ARB_fragment_shader_interlock\n\tGL_ARB_framebuffer_no_attachments\n\tGL_ARB_framebuffer_object\n\tGL_ARB_framebuffer_sRGB\n\tGL_ARB_geometry_shader4\n\tGL_ARB_get_program_binary\n\tGL_ARB_get_texture_sub_image\n\tGL_ARB_gl_spirv\n\tGL_ARB_gpu_shader5\n\tGL_ARB_gpu_shader_fp64\n\tGL_ARB_gpu_shader_int64\n\tGL_ARB_half_float_pixel\n\tGL_ARB_half_float_vertex\n\tGL_ARB_imaging\n\tGL_ARB_indirect_parameters\n\tGL_ARB_instanced_arrays\n\tGL_ARB_internalformat_query\n\tGL_ARB_internalformat_query2\n\tGL_ARB_invalidate_subdata\n\tGL_ARB_map_buffer_alignment\n\tGL_ARB_map_buffer_range\n\tGL_ARB_multi_bind\n\tGL_ARB_multi_draw_indirect\n\tGL_ARB_multisample\n\tGL_ARB_multitexture\n\tGL_ARB_occlusion_query\n\tGL_ARB_occlusion_query2\n\tGL_ARB_parallel_shader_compile\n\tGL_ARB_pipeline_statistics_query\n\tGL_ARB_pixel_buffer_object\n\tGL_ARB_point_parameters\n\tGL_ARB_point_sprite\n\tGL_ARB_polygon_offset_clamp\n\tGL_ARB_post_depth_coverage\n\tGL_ARB_program_interface_query\n\tGL_ARB_provoking_vertex\n\tGL_ARB_query_buffer_object\n\tGL_ARB_robust_buffer_access_behavior\n\tGL_ARB_robustness\n\tGL_ARB_sample_locations\n\tGL_ARB_sample_shading\n\tGL_ARB_sampler_objects\n\tGL_ARB_seamless_cube_map\n\tGL_ARB_seamless_cubemap_per_texture\n\tGL_ARB_separate_shader_objects\n\tGL_ARB_shader_atomic_counter_ops\n\tGL_ARB_shader_atomic_counters\n\tGL_ARB_shader_ballot\n\tGL_ARB_shader_bit_encoding\n\tGL_ARB_shader_clock\n\tGL_ARB_shader_draw_parameters\n\tGL_ARB_shader_group_vote\n\tGL_ARB_shader_image_load_store\n\tGL_ARB_shader_image_size\n\tGL_ARB_shader_objects\n\tGL_ARB_shader_precision\n\tGL_ARB_shader_storage_buffer_object\n\tGL_ARB_shader_subroutine\n\tGL_ARB_shader_texture_image_samples\n\tGL_ARB_shader_texture_lod\n\tGL_ARB_shader_viewport_layer_array\n\tGL_ARB_shading_language_100\n\tGL_ARB_shading_language_420pack\n\tGL_ARB_shading_language_include\n\tGL_ARB_shading_language_packing\n\tGL_ARB_shadow\n\tGL_ARB_sparse_buffer\n\tGL_ARB_sparse_texture\n\tGL_ARB_sparse_texture2\n\tGL_ARB_sparse_texture_clamp\n\tGL_ARB_spirv_extensions\n\tGL_ARB_stencil_texturing\n\tGL_ARB_sync\n\tGL_ARB_tessellation_shader\n\tGL_ARB_texture_barrier\n\tGL_ARB_texture_border_clamp\n\tGL_ARB_texture_buffer_object\n\tGL_ARB_texture_buffer_object_rgb32\n\tGL_ARB_texture_buffer_range\n\tGL_ARB_texture_compression\n\tGL_ARB_texture_compression_bptc\n\tGL_ARB_texture_compression_rgtc\n\tGL_ARB_texture_cube_map\n\tGL_ARB_texture_cube_map_array\n\tGL_ARB_texture_env_add\n\tGL_ARB_texture_env_combine\n\tGL_ARB_texture_env_crossbar\n\tGL_ARB_texture_env_dot3\n\tGL_ARB_texture_filter_anisotropic\n\tGL_ARB_texture_filter_minmax\n\tGL_ARB_texture_float\n\tGL_ARB_texture_gather\n\tGL_ARB_texture_mirror_clamp_to_edge\n\tGL_ARB_texture_mirrored_repeat\n\tGL_ARB_texture_multisample\n\tGL_ARB_texture_non_power_of_two\n\tGL_ARB_texture_query_levels\n\tGL_ARB_texture_query_lod\n\tGL_ARB_texture_rectangle\n\tGL_ARB_texture_rg\n\tGL_ARB_texture_rgb10_a2ui\n\tGL_ARB_texture_stencil8\n\tGL_ARB_texture_storage\n\tGL_ARB_texture_storage_multisample\n\tGL_ARB_texture_swizzle\n\tGL_ARB_texture_view\n\tGL_ARB_timer_query\n\tGL_ARB_transform_feedback2\n\tGL_ARB_transform_feedback3\n\tGL_ARB_transform_feedback_instanced\n\tGL_ARB_transform_feedback_overflow_query\n\tGL_ARB_transpose_matrix\n\tGL_ARB_uniform_buffer_object\n\tGL_ARB_vertex_array_bgra\n\tGL_ARB_vertex_array_object\n\tGL_ARB_vertex_attrib_64bit\n\tGL_ARB_vertex_attrib_binding\n\tGL_ARB_vertex_buffer_object\n\tGL_ARB_vertex_program\n\tGL_ARB_vertex_shader\n\tGL_ARB_vertex_type_10f_11f_11f_rev\n\tGL_ARB_vertex_type_2_10_10_10_rev\n\tGL_ARB_viewport_array\n\tGL_ARB_window_pos\n\tGL_ATI_draw_buffers\n\tGL_ATI_texture_float\n\tGL_ATI_texture_mirror_once\n\tGL_EXTX_framebuffer_mixed_formats\n\tGL_EXT_Cg_shader\n\tGL_EXT_abgr\n\tGL_EXT_bgra\n\tGL_EXT_bindable_uniform\n\tGL_EXT_blend_color\n\tGL_EXT_blend_equation_separate\n\tGL_EXT_blend_func_separate\n\tGL_EXT_blend_minmax\n\tGL_EXT_blend_subtract\n\tGL_EXT_compiled_vertex_array\n\tGL_EXT_depth_bounds_test\n\tGL_EXT_direct_state_access\n\tGL_EXT_draw_buffers2\n\tGL_EXT_draw_instanced\n\tGL_EXT_draw_range_elements\n\tGL_EXT_fog_coord\n\tGL_EXT_framebuffer_blit\n\tGL_EXT_framebuffer_multisample\n\tGL_EXT_framebuffer_multisample_blit_scaled\n\tGL_EXT_framebuffer_object\n\tGL_EXT_framebuffer_sRGB\n\tGL_EXT_geometry_shader4\n\tGL_EXT_gpu_program_parameters\n\tGL_EXT_gpu_shader4\n\tGL_EXT_import_sync_object\n\tGL_EXT_memory_object\n\tGL_EXT_memory_object_win32\n\tGL_EXT_multi_draw_arrays\n\tGL_EXT_packed_depth_stencil\n\tGL_EXT_packed_float\n\tGL_EXT_packed_pixels\n\tGL_EXT_pixel_buffer_object\n\tGL_EXT_point_parameters\n\tGL_EXT_polygon_offset_clamp\n\tGL_EXT_post_depth_coverage\n\tGL_EXT_provoking_vertex\n\tGL_EXT_raster_multisample\n\tGL_EXT_rescale_normal\n\tGL_EXT_secondary_color\n\tGL_EXT_semaphore\n\tGL_EXT_semaphore_win32\n\tGL_EXT_separate_shader_objects\n\tGL_EXT_separate_specular_color\n\tGL_EXT_shader_image_load_formatted\n\tGL_EXT_shader_image_load_store\n\tGL_EXT_shader_integer_mix\n\tGL_EXT_shadow_funcs\n\tGL_EXT_sparse_texture2\n\tGL_EXT_stencil_two_side\n\tGL_EXT_stencil_wrap\n\tGL_EXT_texture3D\n\tGL_EXT_texture_array\n\tGL_EXT_texture_buffer_object\n\tGL_EXT_texture_compression_dxt1\n\tGL_EXT_texture_compression_latc\n\tGL_EXT_texture_compression_rgtc\n\tGL_EXT_texture_compression_s3tc\n\tGL_EXT_texture_cube_map\n\tGL_EXT_texture_edge_clamp\n\tGL_EXT_texture_env_add\n\tGL_EXT_texture_env_combine\n\tGL_EXT_texture_env_dot3\n\tGL_EXT_texture_filter_anisotropic\n\tGL_EXT_texture_filter_minmax\n\tGL_EXT_texture_integer\n\tGL_EXT_texture_lod\n\tGL_EXT_texture_lod_bias\n\tGL_EXT_texture_mirror_clamp\n\tGL_EXT_texture_object\n\tGL_EXT_texture_sRGB\n\tGL_EXT_texture_sRGB_decode\n\tGL_EXT_texture_shared_exponent\n\tGL_EXT_texture_storage\n\tGL_EXT_texture_swizzle\n\tGL_EXT_timer_query\n\tGL_EXT_transform_feedback2\n\tGL_EXT_vertex_array\n\tGL_EXT_vertex_array_bgra\n\tGL_EXT_vertex_attrib_64bit\n\tGL_EXT_win32_keyed_mutex\n\tGL_EXT_window_rectangles\n\tGL_IBM_rasterpos_clip\n\tGL_IBM_texture_mirrored_repeat\n\tGL_KHR_blend_equation_advanced\n\tGL_KHR_blend_equation_advanced_coherent\n\tGL_KHR_context_flush_control\n\tGL_KHR_debug\n\tGL_KHR_no_error\n\tGL_KHR_parallel_shader_compile\n\tGL_KHR_robust_buffer_access_behavior\n\tGL_KHR_robustness\n\tGL_KTX_buffer_region\n\tGL_NVX_blend_equation_advanced_multi_draw_buffers\n\tGL_NVX_conditional_render\n\tGL_NVX_gpu_memory_info\n\tGL_NVX_multigpu_info\n\tGL_NVX_nvenc_interop\n\tGL_NV_ES1_1_compatibility\n\tGL_NV_ES3_1_compatibility\n\tGL_NV_alpha_to_coverage_dither_control\n\tGL_NV_bindless_multi_draw_indirect\n\tGL_NV_bindless_multi_draw_indirect_count\n\tGL_NV_bindless_texture\n\tGL_NV_blend_equation_advanced\n\tGL_NV_blend_equation_advanced_coherent\n\tGL_NV_blend_minmax_factor\n\tGL_NV_blend_square\n\tGL_NV_clip_space_w_scaling\n\tGL_NV_command_list\n\tGL_NV_compute_program5\n\tGL_NV_conditional_render\n\tGL_NV_conservative_raster\n\tGL_NV_conservative_raster_dilate\n\tGL_NV_conservative_raster_pre_snap_triangles\n\tGL_NV_copy_depth_to_color\n\tGL_NV_copy_image\n\tGL_NV_depth_buffer_float\n\tGL_NV_depth_clamp\n\tGL_NV_draw_texture\n\tGL_NV_draw_vulkan_image\n\tGL_NV_explicit_multisample\n\tGL_NV_fence\n\tGL_NV_fill_rectangle\n\tGL_NV_float_buffer\n\tGL_NV_fog_distance\n\tGL_NV_fragment_coverage_to_color\n\tGL_NV_fragment_program\n\tGL_NV_fragment_program2\n\tGL_NV_fragment_program_option\n\tGL_NV_fragment_shader_interlock\n\tGL_NV_framebuffer_mixed_samples\n\tGL_NV_framebuffer_multisample_coverage\n\tGL_NV_geometry_shader4\n\tGL_NV_geometry_shader_passthrough\n\tGL_NV_gpu_program4\n\tGL_NV_gpu_program4_1\n\tGL_NV_gpu_program5\n\tGL_NV_gpu_program5_mem_extended\n\tGL_NV_gpu_program_fp64\n\tGL_NV_gpu_shader5\n\tGL_NV_half_float\n\tGL_NV_internalformat_sample_query\n\tGL_NV_light_max_exponent\n\tGL_NV_multisample_coverage\n\tGL_NV_multisample_filter_hint\n\tGL_NV_occlusion_query\n\tGL_NV_packed_depth_stencil\n\tGL_NV_parameter_buffer_object\n\tGL_NV_parameter_buffer_object2\n\tGL_NV_path_rendering\n\tGL_NV_path_rendering_shared_edge\n\tGL_NV_pixel_data_range\n\tGL_NV_point_sprite\n\tGL_NV_primitive_restart\n\tGL_NV_query_resource\n\tGL_NV_query_resource_tag\n\tGL_NV_register_combiners\n\tGL_NV_register_combiners2\n\tGL_NV_sample_locations\n\tGL_NV_sample_mask_override_coverage\n\tGL_NV_shader_atomic_counters\n\tGL_NV_shader_atomic_float\n\tGL_NV_shader_atomic_float64\n\tGL_NV_shader_atomic_fp16_vector\n\tGL_NV_shader_atomic_int64\n\tGL_NV_shader_buffer_load\n\tGL_NV_shader_storage_buffer_object\n\tGL_NV_shader_thread_group\n\tGL_NV_shader_thread_shuffle\n\tGL_NV_stereo_view_rendering\n\tGL_NV_texgen_reflection\n\tGL_NV_texture_barrier\n\tGL_NV_texture_compression_vtc\n\tGL_NV_texture_env_combine4\n\tGL_NV_texture_multisample\n\tGL_NV_texture_rectangle\n\tGL_NV_texture_rectangle_compressed\n\tGL_NV_texture_shader\n\tGL_NV_texture_shader2\n\tGL_NV_texture_shader3\n\tGL_NV_transform_feedback\n\tGL_NV_transform_feedback2\n\tGL_NV_uniform_buffer_unified_memory\n\tGL_NV_vertex_array_range\n\tGL_NV_vertex_array_range2\n\tGL_NV_vertex_attrib_integer_64bit\n\tGL_NV_vertex_buffer_unified_memory\n\tGL_NV_vertex_program\n\tGL_NV_vertex_program1_1\n\tGL_NV_vertex_program2\n\tGL_NV_vertex_program2_option\n\tGL_NV_vertex_program3\n\tGL_NV_viewport_array2\n\tGL_NV_viewport_swizzle\n\tGL_S3_s3tc\n\tGL_SGIS_generate_mipmap\n\tGL_SGIS_texture_lod\n\tGL_SGIX_depth_texture\n\tGL_SGIX_shadow\n\tGL_SUN_slice_accum\n\tGL_WIN_swap_hint\n\tWGL_EXT_swap_control\n\nImplementation Dependent OpenGL Limits:\n****\n\nMaximum DrawElements Vertices:\t1048576\nMaximum DrawElements Indices:\t1048576\n\nGLSL:\nMaximum Varying Floats:\t124\nMaximum Vertex Attributes:\t16\nMaximum Vertex Uniform Components:\t4096\nMaximum Fragment Uniform Components:\t4096\nMaximum Vertex Image Units:\t32\nMaximum Fragment Image Units:\t32\nMaximum Pipeline Image Units:\t192\n\nCycles:\n****\n\nCPU device capabilities: SSE2 SSE3 SSE41 AVX AVX2\n\nOpenCL device capabilities:\nNumber of platforms: 2\nPlatform #0\n\tPlatform Name: Intel(R) OpenCL\n\tPlatform Vendor: Intel(R) Corporation\n\tPlatform Version: OpenCL 2.1 \n\tPlatform Profile: FULL_PROFILE\n\tPlatform Extensions: cl_intel_dx9_media_sharing cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_d3d11_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_fp64 cl_khr_gl_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_spir\n\tNumber of devices: 2\n\t\tDevice: #0\n\t\t\tDevice Name: Intel(R) HD Graphics 630\n\t\t\tDevice Vendor: Intel(R) Corporation\n\t\t\tDevice OpenCL C Version: OpenCL C 2.0 \n\t\t\tDevice Profile: FULL_PROFILE\n\t\t\tDevice Version: OpenCL 2.1 \n\t\t\tDevice Extensions: cl_intel_accelerator cl_intel_advanced_motion_estimation cl_intel_d3d11_nv12_media_sharing cl_intel_device_side_avc_motion_estimation cl_intel_driver_diagnostics cl_intel_dx9_media_sharing cl_intel_media_block_io cl_intel_motion_estimation cl_intel_planar_yuv cl_intel_packed_yuv cl_intel_required_subgroup_size cl_intel_simultaneous_sharing cl_intel_subgroups cl_intel_subgroups_short cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_fp16 cl_khr_fp64 cl_khr_gl_depth_images cl_khr_gl_event cl_khr_gl_msaa_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_gl_sharing cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_khr_spir cl_khr_subgroups cl_khr_throttle_hints \n\t\t\tDevice Max clock frequency (MHz): 1100\n\t\t\tDevice Max compute units: 24\n\t\t\tDevice Max work group size: 256\n\t\tDevice: #1\n\t\t\tDevice Name: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\n\t\t\tDevice Vendor: Intel(R) Corporation\n\t\t\tDevice OpenCL C Version: OpenCL C 2.0 \n\t\t\tDevice Profile: FULL_PROFILE\n\t\t\tDevice Version: OpenCL 2.1 (Build 10)\n\t\t\tDevice Extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_gl_sharing cl_khr_fp64 cl_khr_image2d_from_buffer \n\t\t\tDevice Max clock frequency (MHz): 2800\n\t\t\tDevice Max compute units: 8\n\t\t\tDevice Max work group size: 8192\nPlatform #1\n\tPlatform Name: NVIDIA CUDA\n\tPlatform Vendor: NVIDIA Corporation\n\tPlatform Version: OpenCL 1.2 CUDA 9.1.84\n\tPlatform Profile: FULL_PROFILE\n\tPlatform Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer\n\tNumber of devices: 1\n\t\tDevice: #0\n\t\t\tDevice Name: GeForce GTX 1050\n\t\t\tDevice Vendor: NVIDIA Corporation\n\t\t\tDevice OpenCL C Version: OpenCL C 1.2 \n\t\t\tDevice Profile: FULL_PROFILE\n\t\t\tDevice Version: OpenCL 1.2 CUDA\n\t\t\tDevice Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer\n\t\t\tDevice Max clock frequency (MHz): 1493\n\t\t\tDevice Max compute units: 5\n\t\t\tDevice Max work group size: 1024\n\nCUDA device capabilities:\n\tGeForce GTX 1050\n\t\tCU_DEVICE_ATTRIBUTE_MAX_THREADS_PER_BLOCK\t\t\t1024\n\t\tCU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_X\t\t\t1024\n\t\tCU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_Y\t\t\t1024\n\t\tCU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_Z\t\t\t64\n\t\tCU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_X\t\t\t2147483647\n\t\tCU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_Y\t\t\t65535\n\t\tCU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_Z\t\t\t65535\n\t\tCU_DEVICE_ATTRIBUTE_MAX_SHARED_MEMORY_PER_BLOCK\t\t\t49152\n\t\tCU_DEVICE_ATTRIBUTE_SHARED_MEMORY_PER_BLOCK\t\t\t49152\n\t\tCU_DEVICE_ATTRIBUTE_TOTAL_CONSTANT_MEMORY\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_WARP_SIZE\t\t\t32\n\t\tCU_DEVICE_ATTRIBUTE_MAX_PITCH\t\t\t2147483647\n\t\tCU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_BLOCK\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_REGISTERS_PER_BLOCK\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_CLOCK_RATE\t\t\t1493000\n\t\tCU_DEVICE_ATTRIBUTE_TEXTURE_ALIGNMENT\t\t\t512\n\t\tCU_DEVICE_ATTRIBUTE_GPU_OVERLAP\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MULTIPROCESSOR_COUNT\t\t\t5\n\t\tCU_DEVICE_ATTRIBUTE_KERNEL_EXEC_TIMEOUT\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_INTEGRATED\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_CAN_MAP_HOST_MEMORY\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_COMPUTE_MODE\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_HEIGHT\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_WIDTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_HEIGHT\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_DEPTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_NUMSLICES\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_SURFACE_ALIGNMENT\t\t\t512\n\t\tCU_DEVICE_ATTRIBUTE_CONCURRENT_KERNELS\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_ECC_ENABLED\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_TCC_DRIVER\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_MEMORY_CLOCK_RATE\t\t\t3504000\n\t\tCU_DEVICE_ATTRIBUTE_GLOBAL_MEMORY_BUS_WIDTH\t\t\t128\n\t\tCU_DEVICE_ATTRIBUTE_L2_CACHE_SIZE\t\t\t524288\n\t\tCU_DEVICE_ATTRIBUTE_MAX_THREADS_PER_MULTIPROCESSOR\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_ASYNC_ENGINE_COUNT\t\t\t2\n\t\tCU_DEVICE_ATTRIBUTE_UNIFIED_ADDRESSING\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_CAN_TEX2D_GATHER\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_GATHER_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_GATHER_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_WIDTH_ALTERNATE\t\t\t8192\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_HEIGHT_ALTERNATE\t\t\t8192\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_DEPTH_ALTERNATE\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_TEXTURE_PITCH_ALIGNMENT\t\t\t32\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_LAYERED_LAYERS\t\t\t2046\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_HEIGHT\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_WIDTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_HEIGHT\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_DEPTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_LAYERED_LAYERS\t\t\t2046\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LINEAR_WIDTH\t\t\t134217728\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_HEIGHT\t\t\t65000\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_PITCH\t\t\t2097120\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_MIPMAPPED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_MIPMAPPED_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_COMPUTE_CAPABILITY_MAJOR\t\t\t6\n\t\tCU_DEVICE_ATTRIBUTE_COMPUTE_CAPABILITY_MINOR\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_MIPMAPPED_WIDTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_STREAM_PRIORITIES_SUPPORTED\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_GLOBAL_L1_CACHE_SUPPORTED\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_LOCAL_L1_CACHE_SUPPORTED\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAX_SHARED_MEMORY_PER_MULTIPROCESSOR\t\t\t98304\n\t\tCU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_MULTIPROCESSOR\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_MANAGED_MEMORY\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MULTI_GPU_BOARD\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_MULTI_GPU_BOARD_GROUP_ID\t\t\t0\n\n\nEnabled add-ons:\n****\n\nio_scene_3ds (version: (1, 0, 0), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_scene_3ds\\__init__.py)\nio_scene_fbx (version: (4, 13, 1), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_scene_fbx\\__init__.py)\nio_anim_bvh (version: (1, 0, 0), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_anim_bvh\\__init__.py)\nio_mesh_ply (version: (1, 0, 0), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_mesh_ply\\__init__.py)\nio_scene_obj (version: (3, 5, 2), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_scene_obj\\__init__.py)\nio_scene_x3d (version: (1, 2, 0), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_scene_x3d\\__init__.py)\nio_mesh_stl (version: (1, 1, 3), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_mesh_stl\\__init__.py)\nio_mesh_uv_layout (version: (1, 1, 1), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_mesh_uv_layout\\__init__.py)\nio_curve_svg (version: UNKNOWN, path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_curve_svg\\__init__.py)\ncycles (version: UNKNOWN, path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\cycles\\__init__.py)\nPBR Materials (version: (3, 1), path: C:\\Users\\CLENET\\AppData\\Roaming\\Blender Foundation\\Blender\\2.80\\scripts\\addons\\PBR Materials\\__init__.py)\nio_scene_gltf2 (version: (0, 0, 1), path: C:\\Program Files\\Blender Foundation\\Blender 2.8\\2.80\\scripts\\addons\\io_scene_gltf2\\__init__.py)\nmanuelbastionilab (version: (1, 6, 1), path: C:\\Users\\CLENET\\AppData\\Roaming\\Blender Foundation\\Blender\\2.80\\scripts\\addons\\manuelbastionilab\\__init__.py)\n[video texture eevee 2.80.blend](video_texture_eevee_2.80.blend)", "Eevee doesn't render sequenced textures\nOperating system: Windows 10\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2\n\nversion: 2.80 (sub 41), branch: blender2.7, commit date: 2019-01-19 20:58, hash: b0dee09a6d55, type: Release\nbuild date: 19/01/2019, 17:08\n\nEevee doesn't render a sequenced textures.\n\nAdd a sequenced image as a texture to any object and render any frame in Eevee. For me, it is pink (shows as missing). But, if I select a single image from that sequence, the image shows. So, a single image shows up as a texture for a material when rendered, but any more than one doesn't.", "Video texture does not work\nOperating system:win 10\nGraphics card:\n\nBroken:blender 2.8.0.41\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI am trying to use video texture but I can not.\nI mean it does not animate. It is display only 1st frame.\nIs there any way to animate video texture?", "Animated Textures dont update on frame change\nOperating system: Windows 10\nGraphics card: GTX 1080\n\n 2.80, 0f5b53ba4dc\n\nHere is a video demonstrating the bug MatureElderlyIrishwaterspaniel\n\nAnytime I use a video file as a texture it never actually plays, it stays stuck on the first frame until I reload the file location. Scrubbing through the timeline or playing the animation doesnt update the texture. The same problem happens when using emptys as images. Ive tried multiple different files.\n\nSteps to reproduce:\nUse a texture node using a video file in any shader or add any background image using a video.\n", "Animated textures used in materials are not working correctly in EEVEE.\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 970\n\nBroken:\n2.80Beta release Date: 2018-12-05 02:05\nHash:1fa527bfa3a\nBranch: blender2.8\n\n**I used mp4 file and png sequence in material node to emit it on modeled screen. Animation is working perfectly in Cycles Render, but in EEVEE it's not refreshing in the viewport and in the render. It just shows one frame from attached mp4 file or png sequence. RGB values of it are weird in some way clipped. In Cycles these values are correct.**\n\n**1. Change cube material to emission and import desired mp4 file as a texture. 2. Plug texture socket into the emission socket. 3. Fix uv mapping. 4.Go to rendered view 5.Go to dopesheet and pick random frames 6. Animation is not refreshed and the RGB values are displaing wrong**\nBased on the default startup or an animation_issue1.blend file.", "Movie as world backgroud doesn't update on Eevee but react as expected with Cycles\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1080\n\nBroken: 2.80, 16fc62e15f0, 2018-12-12\n\n\nWhen adding a Movie as background in the world_node_editor, the background doesn't update when scrubbing the timeline\nwith EEVEE, but it does update as expected with Cycles.\n\n\nin the world node editor:\nadd a texture coordinate + mapping + image texture node.\nadd a movie clip in the image texture node\nfill the Frames / Start frame / offset field\ncheck auto refresh\nconnect the image texture node to the world output node\n\nnow scrubb the timeline.\nWith EEVEE the background doesn't update\nWithe Cycles the background update as expected.\n\nThanks for your amazing job guys !!!! Keep it up !!!!", "Image Sequence Feature that in Image Texture Node Not Working \nOperating system: Windows 10 64 Bit\nGraphics card: Geforce GT 740m\n\nBroken:\n(2.8 release)\nDate: 2019.01.21 Hash: dd3f5186260e \nWorked: (Images and Shaders)\n\nImage Sequence Feature that in Image Texture Node Not Working . I added a plane than unwrap it. Then assign a material. In shader editor i import my image sequence, blender automaticy change image editor node to image sequence. It was cool but in viewport and render my mterial look purple. In 2.7 it wasn't like this.\n\n", "Movie on Plane Not Playing\nOperating system: Windows 10\nGraphics card: Don't know, sorry (using an HP Omen)\n\nBroken:\nBlender 2.8\nWorked: (2.79)\n\n\nWhen I put a movie as a texture on a plane, it does not play whatever settings I change. I have: ticked auto refresh and cyclic, changed the type of video I use (avi and MOV files) and restarted blender and my computer.\n\n\n #1 Open Blender 2.8\n\n #2 Delete the cube and add a plane\n\n #3 Go into edit mode and subdivide the plane by 100 cuts\n\n #4 Got and add a material and set the base colour as an image texture\n\n #5 Add a short video clip as the image\n\n #6 Change the number of frames to match the length of the video and tick Cyclic and Auto Refresh\n\n #7 Play the animation and the video doesn't play for me\n\n\nSorry that I haven't attached the .blend file but I would rather keep the video I'm using private unless I get permission from my cousins to attach it\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n", "Video texture / Image Sequence not refreshing under eevee\n{[F5282778](test.zip)}Mac OSX and gtx 980 ti\n\nBroken: 2.80.0 3bc8bc0709a\n\n**When navigating in timeline, shader with video texture doesn't refresh with eevee , but it's working when I switch to cycles**\n\nEDIT: same result in viewport or render (ctrl F12)" ]

[ "Bug while moving vertices with mirror & subdivision modifier\nOperating system: Windows 10 64-bit\nGraphics card: ATI Radeon HD 5670\n\nBroken: 2.82\nWorked: at least 2.8\n\nWhen I try to move a vertice it seems like the mirror modifier gets applied in an odd way. The result even changes when moving the camera or hide one of the images I use for reference. In fact it becomes distorted when hiding the images.\nThe following link is a recording of my screen:\nview?usp=sharing\nI encountered this bug only recently. The file itself is older and I do not remember which version I used (since I use it via Steam I did not pay attention to the automatic patches).\n\n1. Open this file [Bugged Project.blend](Bugged_Project.blend)\n2. Disable visibility of Subdivision modifier for Edit Mode (which should already cause the bug)\n3. Move a vertice\n\n[system-info.txt](system-info.txt)", " LineArt: (Collection) Issue for Cameras in Orthographic View\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nChecked in Blender version 3.4.0 Apha, commit date: 2022-10-08 02:26 - same issue\n\nFor orthographic Camera without any shifts - Line art modifier (for a Collection) showing lines for objects behind other objects - which otherwise should not be visible. And some lines are not visible which should be.\nHappens with contours option in the Line Art modifier. Slight rotation on z axis solves the issue.\n\nNoticed issue with some specific frames on my complete blend file.\n\nOpen attached blend file and go to front orthographic view.\n\n[BugReport01.blend](BugReport01.blend)\n\n", "3.4.1 Not Displaying GTX 1660 TI\nOperating system: Windows 10 Home 22H2\nGraphics card: GTX 1660 TI\n\nBroken: These versions do not display my GPU under CUDA/OptiX: 3.4.1, 3.4.1, 3.3.4, 3.3.3 and 3.3.2 (I was also getting Python errors when trying to install addons. (This is true whether they are installed or run from the unzipped .rar downloads.\n\nWorked: blender-2.93.15 candidate+v293.400f35914421-windows.amd64-release is the most recent version that works - everything works as it should!\n\n\nI tried uninstalling/installing the latest Nvidia game ready drivers, the studio drivers, the CUDA Toolkit (which asked for me to install Visual Studio, C++, etc... 🤦‍♂️ ), tweaking the registry settings etc... none of these things worked. \n\nOnly using the older version would detect my GPU. A user on the Discord forum asked me to run the GPU debugger in the latest version 3.4.1 and when I open the program that way, my GPU was finally showing! I sent him the error reports (I can post them below) and he said that Blender IS SEEING my GPU, it's just not displaying it for use.\n\n", "Particle display problem in rendering when using the Time remapping option\nOperating system: Mac Os Mojave 10.14.6 (18G95) and Windows 10 (Last update)\nGraphics card: AMD Radeon R9 M295X 4 Go & Nvidia GTX 1070\n\nBlender 2.80\n\nThere is a problem of particle rendering if we use the Time remapping function which makes it possible to make a film slower by multiplying the number of images of an animation. The particle animation is not continuous, some disappear and then reappear creating a jerky effect.\nThe problem does not appear when launching the animation directly in the software but only by doing a rendering calculation whether it is in film or frame-by-frame mode or movie (with Cycle or Eevee rendering)\n\nIf I leave the time remapping by default (old 100, new 100) there is no problem.[torus particules.blend](torus_particules.blend)\nIf I change the time remapping to have a movie with 4 times more image (old 25, new 100), the problem appears: the particle animation is not continuous, some disappear and then reappear creating a jerky effect.", "Texture Painting not updating cycles shader in viewport\nOperating system: Linux-5.8.0-44-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa Intel(R) Xe Graphics (TGL GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.92.0\n\n\nLevel 1. When texture painting in the 3D viewport, the image is updated, but the visible shader on the object doesn't update in cycles until switching to viewport shading and back to cycles.\nIt still works when switching to Eevee shading. When reloading the image in the shader image texture node, it updates in cycles, but the problem persists when the image is updated (painted on) again.\n\nLevel 2. The above bug becomes worse as follows:\n\nIn cycles the image stops updating even when switching to viewport shading and back to cycles.\n(A)-When reloading the image in the shader image texture node, it updates in cycles, but any new paint on the texture in the viewport or image editor -> paint mode won't update until step A is repeated. \n\nI do not know exactly what triggers this 2nd level bug, but it doesn't take long to show up. \nI was able to repeat it just by painting and switching between Eevee and cycles using my test .blend file (attached)\n\n\n\n\n1. Assign a material with an image node to an unwrapped object\n2. Switch to viewport texture painting and start painting on the image in cycles shading. \n3. The image updates in viewport shading, but not the visible shader on the object in cycles. \n4. Switch to Eevee shading - now eveything works as expected.\n\n5. I do not know what triggers the level 2 bug.\n\n[Cycles not painting on Cube.blend](Cycles_not_painting_on_Cube.blend)\n\n\n\n\n\n", "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", "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", "Blender 2.83 smoke or liquid simulation not showing up when switching to Modular mode\nOperating system: Windows 10pro 64 bit\nGraphics card: Nvidia GTX 960\n\nBroken: 2.83, v2.83.0 \nWorked: 2.82\n\nWhen I'm simulating smoke or liquid. If I switch to modular mode, the bake the simulation. I do not see any smoke or liquid after it has run the bake. I can see the domain moving as if particles are filling the domain, but during play back nothing is there.\nIf I change the mode to replay mode. I can see the smoke or liquid as it is simulating. But I don't get this in modular mode\nI have a youtube video link that shows the problem. \n\nIoqbkzs7h5w\n\nI like modular mode, because baking the simulation this was takes less resources by not updating the view port.\n\n- Create a box.\n- Duplicate the box. \n- In physics tab... Make one for the emitter and the other as domain.\n- Scale domain as necessary.\n- By default Blender is in Replay mode. Change it to modular to get the Bake buttons. \n- Bake simulation. \n- Then change scale of emitter and bake simulation again.\nor\n- open attached file\n- Try see simulation with Replay (it should work)\n- Then try with Modular\n[Name_animationV2.blend](Name_animationV2.blend)", "New AMD Drivers (Adrenalin 22.7.1 or 22.8.2) for Windows 10 cause toolbars to be completely black\n\nBroken:\nOperating system: Windows-10-10.0.19044-SP0\n|Graphics card:|Driver:|User:\n|---|---|---\n|Radeon RX 580 Series|4.5.0 Core Profile Context 22.7.1.220725|@GKPrasad\n|Radeon RX 580 Series|4.5.0 Core Profile Context 22.8.1.220810|@Vaskos\n|AMD Radeon RX 5600 XT|4.5.0 Core Profile Context 22.7.1.220725|@ShockHazard1\n|Radeon(TM) RX 460 Graphics|4.5.0 Core Profile Context 22.7.1.220725|@patrickshyee\n|AMD Radeon(TM) Vega 3 Graphics|4.5.0 Core Profile Context 22.8.2.220819|@Alenda\n|AMD Radeon(TM) RX Vega 10 Graphics ATI Technologies Inc.|4.5.0 Core Profile Context 22.10.1.221003|@JaedenREE\n\nWorks fine on:\nOperating system: Windows-10-10.0.22000-SP0 (Windows 11)\n|Graphics card:|Driver:|User:\n|---|---|---\n|Radeon (TM) RX 480 Graphics|4.5.0 Core Profile Context 22.7.1.220725|@mano-wii\n\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\n|Graphics card:|Driver:|User:\n|---|---|---\n|Radeon (TM) RX 480 Graphics|4.5.0 Core Profile Context 22.8.2.220819| @Jeroen-Bakker \n---\nBroken: (3.2)\n\nnon of the tabs are visible. as u can see in the image its entirely black. I wont be able to use the program at all. Please do fix this.\n\nThe error exists as soon as i open blender program\n", "Weird edge lines in 3D Viewport (Edit Mode - Orthographic View)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.3\n\nIn Edit Mode when switching to Orthographic mode the edges sometimes look very thin, jaggy, disappearing in some place, dotted line style or just barely visible. Nothing changes when changing the distance to the object. Nothing changes if selecting Vertex select/Edge select/Face select. However, lines are visible with a very good (usual quality) in Orthographic view when switching to Object Mode and turning on Wireframe on shaded (Overlay dropdown). If Wireframe on shaded option is enabled the edges looks good even in Edit Mode in Orthographic view.\n\nI can't reproduce this error in another scene.\n\n[MAGPUL STR Carbine Stock 009.blend](MAGPUL_STR_Carbine_Stock_009.blend)\n[system-info.txt](system-info.txt)\n\n\n", "Unable to output pictures correctly when rendering version 3.2 demo with 65536*65536 resolution\nOperating system:win11 -workstationedition\nGraphics card:4090\n\nBroken: 3.4.0 release\nWorked: \n\nUnable to output pictures correctly when rendering version 3.2 demo with 65536 * 65536 resolution.\nWhen nearly 4 hours of rendering ends, blender does not work any picture out, as the picture atteched. And the image attribute say this image is 32768 * 32768.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nusing the dome file for blender3.2\n\n", "EEVEE - Screen space reflections artifacts\nOperating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: ?\n\nSSR shows some strips when I have bad data for normals.\n\nOpen the file:\n[ssr_sripts.blend](ssr_sripts.blend)\n\nIf you click anywhere multiple times, viewport gets darker and darker.\n\nBefore:\n\n\nAfter clicking the glossy node header a few times:\n\n", "VSE: Cycles displayed as Rendered in Scene strip makes Blender hang - and other Scene strip bugs\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nThe Render modes of Scene Strips are either missing or broken:\n- When Cycles is set as render and Rendered set as display, it'll make Blender hang.\n- Wireframe and Rendered doesn't work with any Render. \n- The only thing working is Eevee with either solid or Material Preview. \n- Workbench and Cycles settings seems to just use the Eevee render, since these are producing the same results in Solid and Material Preview.\n\n{[F10177251](scenestrip.gif),size=full}\n\nTest file:\nCycles is set up as render in the 3D Footage scene. In the Master Edit scene, switch display mode to Rendered. Blender will hang.\nTry the various other display modes and renders(by changing the render in the 3D Footage scene), to see wireframe and rendered doesn't work with any render. \n[multicam_3d_c.blend](multicam_3d_c.blend)\n\n\n", "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.", "X-Ray and Wireframe-Only modes not working in weight painting mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0 Beta\n\nX-Ray and Wireframe-Only modes not working in weight painting mode.\nIf I remember correctly it worked in earlier versions of Blender, like 3.0 or maybe even earlier, but then was broken.\n\nWatch attached video for demonstration.\n\nCreate any object, go to Weight Paint Mode.\nTry to use X-Ray shading or Wireframe-only shading modes. The 3d-model is fully opaque.\nGoto Vertex selection, With X-Ray set to 1 I can't even select backface vertices, only if I lower it value a bit - it start working, but 3d-object is still opaque.\n+ Looks like Show wireframe checkbox (in viewport overlays panel) in this mode not working also.\n\nvideo:" ]

[ "Very strange visual bug affecting viewport view and rendered results\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\n\nIn wireframe mode objects are seemingly invisible except for their outline while in object mode and appear normal in edit mode.\n\nMaterial preview mode produces a very strange visual effect where it's as if the studio lighting background image smears onto the edges of the 3d object and in a way that disregards it's actual shape. The image then stays on the object unless I orbit around it and \"smear more background image on it\". Same thing happens in edit mode.\n\nRendered mode will make the object seem invisible just like in wireframe mode but keeps the smeared parts of the background image from the material preview mode, object then turns gray (seemingly invisible) if I orbit around it and smear the gray background on it. Edit mode still works and shows it's actual shape.\n\nIf I render an image the object will show as a transparent shape.\n\nNote that updating from Blender 2.91.0 did not fix the issue.\n\nOpen Blender, enter wireframe mode, material preview mode or rendered mode.\nBased on the default startup\n\n", "Wireframe not displaying with AMD GPU\nOperating system: Windows 10\nGraphics card:\n - Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n - Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003 \n - Radeon RX520\n - Radeon RX550/550 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009\n - Radeon RX 570 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n - Radeon RX 570 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.12.1 27.20.14501.28009\n - Radeon RX 580 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n - AMD Radeon(TM) Vega 3 Graphics\n\nBroken: 2.82.0, 2.91.0, 2.92.0\nWorked: Issue appears to be caused by AMD graphics driver later than 20.11.1\n\nWhen setting *Viewport Shading* to wireframe in object mode only the outline is displayed\n\n- Set *Viewport Shading* to *Wireframe*" ]

[ "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", "Working on a mesh that has a high multires subdivision causes blender to build Up memory even on lower levels.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\nRAM: 16GB\nCPU: AMD Ryzen 7 3800\n\nBroken: version: 3.6.0\n\nWhen editing a mesh that has been subdivided a few times will cause blender to increasingly start to consume more and more memory aggressively even if the modifier is turned off.\n\nSubdivide the mesh a few times using the multiresolution modifier, noted on 5-up levels on a mesh with originally 9 272 faces. then either switch the modifier Viewport Level to either 1 or disable It entirelly, start editing the mesh in edit mode the memory consumption stats will start to skyrocket with no signs of going back down until blender starts slowing down the computer and/or crashes entirely. (Got to about 32 GBs some times about where the computer would stop handling It anymore) I haven't tried doing it in workbench I think so I'd suggest trying to do It in Eevee mode too.\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "OptiX Denoiser fails with large output resolution (final rendering completely black)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nDuring my final rendering, in 100% resolution, the final rendering is completely black. When calculating the image everything looks normal, I can see the tiles generating normally. Then the final render appears black. The other layers (shadow, OA, etc.) are well rendered. \n\nThis looks to be caused by OptiX failing to denoise a very large final image.\n\nThe example here will attempt to render a 6144x6144px image on an 8gb 1070 and fail during the Denoising step (leaving a completely black image too).\n\nThe original report attempted to render at >10240px (so adjust accordingly if it doesn't happen at first with your GPU).\n\n- Load attached `denoise.blend` file.\n- Attempt to F12 render\n\n```\nI0301 12:53:47.768775 15952 path_trace.cpp:971] Processing full frame buffer file T:\\Temp\\blender_a18956\\cycles-tile-buffer-15716-2377920588664-0-0.exr\nI0301 12:53:49.619309 15952 denoiser_gpu.cpp:51] Creating temporary buffer on denoiser device.\nI0301 12:53:50.388029 15952 device.cpp:669] Buffer allocate: RenderBuffers, 2,868,903,936 bytes. (2.67G) in device memory\nI0301 12:53:50.995292 15952 device_impl.cpp:80] using cuda device \"NVIDIA GeForce GTX 1070 with Max-Q Design\" (6.1), buffers: fp16, Winograd convolution, rt v11060\nI0301 12:53:52.356184 15952 device.cpp:669] Buffer allocate: __denoiser_state, 2,999,350,016 bytes. (2.79G) in host memory\nI0301 12:53:52.356184 15952 device_impl.cpp:80] layers created for resolution 4352 4352, inp 8, outp 3\nE0301 12:53:52.356184 15952 device_impl.cpp:74] copy of converted weights failed (CUDA error string: invalid argument, CUDA error code: 1)\nFailed to set up OptiX denoiser\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nE0301 12:53:52.356184 15952 denoiser_optix.cpp:577] OptiX denoiser configuration has failed.\n\n```\n\nVerbose 5 logs attached.\n\n", "Blender 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", "EEVEE: Crash if computation is too heavy for the system (TDR issue)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nAny time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[NebulaV2.blend](NebulaV2.blend)", "CUDA misaligned address error when rendering the image\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nThe error occurs when rendering in a scene. It only occurs on the gpu and consistently occurs on optix and cuda. The scene starts rendering and gets to about 20/40 samples before the error occurs and it completely stops rendering. This happens both in viewport and render modes. Blender cannot be closed normally or go into viewport mode after the error occurs. It just crashes\n\nThe GPU is not running out of VRAM, Task manager shows blender barely uses 3GB VRAM before running into the error even though the gpu has 6GB\n\n`Misaligned address in CUDA queue copy_from_device (integrator_shade_volume integrator_queued_paths_array)`\n\n\n\n1. Open the scene\n2. Render image\n\nI have tried updating drivers, rolling back drivers, using previous versions (all the way back to 3.4)\n\nTest file: view?usp=drive_link", "EEVEE: Shader error for incorrect type connected to a AOV Output\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: version: 4.0.0 Alpha\n\n\n\n\n```Cpp\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n 8604 | node_output_aov(vec4_from_Closure(tmp34), node_tree.u36, cons37, tmp38);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n |\n 8622 | node_output_aov(vec4_from_Closure(tmp72), node_tree.u74, cons75, tmp76);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n```\n\n1. Material node tree:\n a. Add `AOV Output`.\n b. Connect `Principled BSDF` to a `AOV Output`.\nSee terminal.\n\n", "USD: Crash when loading the Intel Moore Lane demo asset (related to Color Attributes)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nBroken: version: 4.0.0 Alpha\nWorked: version: 4.0.0 Alpha\n\nCrashes during import of the Intel 4004 Moore Lane asset. Seemingly related to Color Attribute processing though the stack traces for the crash are not related.\n\n- Download the \"4004 Moore Lane v 1.1.0\" asset: 4004-moore-lane/\n- Attempt to import the `USD\\4004MooreLane_III_03_ASWF.usd` file with default settings --> observe crash\n- Attempt to import the same file but with the \"Color Attributes\" option unselected --> works\n\nOddly, the crashing stack occurs inside tbbmalloc and while seemingly dealing with mesh normals...\n```\n...\ntbbmalloc.dll!00007ffd7fa29f4e()\tUnknown\nblender.exe!MEM_lockfree_mallocN_aligned(unsigned __int64 len, unsigned __int64 alignment, const unsigned char * str) Line 310\tC\n[Inline Frame] blender.exe!blender::GuardedAllocator::allocate(unsigned __int64) Line 47\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::allocate(__int64) Line 425\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::get_buffer_for_size(__int64) Line 419\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::{ctor}(__int64) Line 122\tC++\nblender.exe!blender::bke::mesh::mesh_normals_loop_custom_set(blender::Span<blender::VecBase<float,3>> positions, blender::Span<blender::VecBase<int,2>> edges, const blender::offset_indices::OffsetIndices<int> faces, blender::Span<int> corner_verts, blender::Span<int> corner_edges, blender::Span<blender::VecBase<float,3>> vert_normals, blender::Span<blender::VecBase<float,3>> face_normals, const bool * sharp_faces, const bool use_vertices, blender::MutableSpan<blender::VecBase<float,3>> r_custom_loop_normals, blender::MutableSpan<bool> sharp_edges, blender::MutableSpan<blender::VecBase<short,2>> r_clnors_data) Line 1368\tC++\nblender.exe!blender::bke::mesh::mesh_set_custom_normals(Mesh * mesh, float[3] * r_custom_nors, const bool use_vertices) Line 1642\tC++\nblender.exe!blender::io::usd::USDMeshReader::process_normals_face_varying(Mesh * mesh) Line 797\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh_sample(blender::io::usd::ImportSettings * settings, Mesh * mesh, double motionSampleTime, bool new_mesh) Line 853\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh(Mesh * existing_mesh, USDMeshReadParams params, const char * * __formal) Line 1094\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_object_data(Main * bmain, double motionSampleTime) Line 249\tC++\nblender.exe!blender::io::usd::import_startjob(void * customdata, bool * stop, bool * do_update, float * progress) Line 288\tC++\n\n```\n\n", "HIP related bugs\nThere are multiple bug reports following the release of 3.6 on the stability and the consistency of HIP, combine them here for easier access:\n\n- #109415 Geometry appears to be tearing up\n- #109417 #110459 Crashes\n- #109418 #109421 Material appears to be white\n- #109477 #110841 crash with RT enable\n- #109521 HIP binary kemel for this graphics card compute capability (9.0) not found.\n- #109553 \"Out of memory\" when HIP is on but fine when off.\n - ~~#110126 Under-reporting memory usage on windows+AMD, could be the same cause as the above one.~~ Mis-categrization, This one does not have HIP enabled.\n- #109562 libamdhip64.so library location/install issue\n- #109811 Linux crash with `HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid.`\n- #110392 #111198 Crash on driver `AMD Adrenaline 23.7.1` and `23.7.2` but fine on `AMD Adrenaline 23.5.2`.\n- #111546 Crash on `23.8.1` with `Radeon RX 6800XT`\n- #111569 Crash on `23.7.2.230718`\n- #111685 5700xt `22.20.27.09.230330` hangs (not sure if this is real crash yet)\n- #112177 \"Instant crash on high polygon\", User pref erroneously shows two identical AMD cards instead of one.\n- #112608 6950 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.3-300.fc39.x86_64) crash without backtrace, Fedora Linux 39", "Subdiv of certain model causes huge memory consumption and crash (regression bug)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n2 guys from 3d-chat also checked it too and caught the same memory leak and crash.\n\nBroken: version: 2.82 (sub 1)\nand 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e\n\nWorked: 2.79 (sub 0), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b\n\nBlender 2.80+ consume a lot of memory and crashes (before memory filled), when I try to subdivide this certain model. \n[2019-11-18_17-17-06.mp4](2019-11-18_17-17-06.mp4)\n\nOpen file with 2.80+, press Ctrl+1 to subdivide.\n[killsubdivdragon.7z](killsubdivdragon.7z)\n", "Eevee randomly causes system to crash when rendering\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory)\nCPU: Intel Core i9 9900k\nRAM: 32GB DDR4\n\nBroken: 3.0.0\n\n\nI'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know.\n\nI have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash.\nThe amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory.\n\nI'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine.\n[ocean_final.blend](ocean_final.blend)\nThe scene makes use of a lot of volumetric light and I also calculate the bloom.\n\nThere aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here.\n\nAll drivers are up to date and I also reinstalled Blender.\n\nNot sure, but I attached the .blend file as well as logs created in debug mode.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "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", "Image sequence render just stops on Cycles on MacOS Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Ultra 1.2\n\nBroken: version: 3.5.0\nWorked: none, tried 2.93, 3.3\n\nafter about 100 or so frames render just stops, Blender is still responsive, its not frozen or crashed, render bar just sits at %0. I'm doing motion tracking to get some kitbashed 3d elements into the scene. Plays fine in Eevee in the viewport. This is the error I get: CommandBuffer Failed: cycles_metal_shader_eval_displace. Attached ram usage for last 24 hours, I still have plenty of ram!\n\nI've closed the file and retried, several times, never got a render all the way through.\n", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n" ]

[ "Regression: Eevee bad performance when using procedural bump map.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.2.0\nWorked: 3.1.2\n\nCaused by 80859a6cb2\n\n**Steps to reproduce**\n[#98989.blend](T98989.blend)\n\n- Open file\n- Play animation\nBlender 3.2 will play at ~4x slower framerate than 3.1.2\n\nIn addition i am seeing even worse performance when navigating (not reproducible by @iss). \n\nPerformance also influence compile times and RAM usage during compilation on AMD GPUs.\n" ]

[ "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "Outliner: Alt+disable is work for all selected, but Alt+Enable is not\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n{key Alt LMB} generally enables a feature that repeats the operation on all selected items in the outliner.\nBut that seems to work only if the object is selected in 3d View.\n[2020-01-12_20-44-23.mp4](2020-01-12_20-44-23.mp4)\n\nOpen:\n[untitled4.blend](untitled4.blend)\n- select the three objects (either in 3d view or outliner).\n- {key Alt LMB} click on the icon that disables object in viewports.\n- {key Alt LMB} again to try to enable them all.\nOnly one object is enabled, because the others are not selected in 3dview.\n\n", "Trackpad Support Improvement (Parent Task)\n## Trackpad related tasks\n\n- [ ] Can't scrub timeline with alt + pan trackpad gesture #76464\n- [ ] Orbit inverted on Mac with Magic Mouse #86025\n- [ ] Zooming is reverse in shader editor comparing to viewport #89906\n- [ ] Zoom axis affects trackpad zoom speed #92221\n- [ ] Scroll direction Natural doesn't work on node canvas views on macOS #102762\n- [ ] Pan gesture behaves randomly #103973\n- [ ] Panning the viewport on touchpad is inverted #109400\n- [ ] Zoom to mousepos makes 2D Views pan after zoom limits are reached #110766\n- [ ] Button flickering when scrolling popovers using the trackpad #110834\n- [ ] Trackpad scrolling is too sensitive in Text Editor #110833\n- [ ] Fly Navigation using the trackpad is broken #110848\n- [ ] UV Stitch and Minimize Stretch do not support the trackpad #110849\n- [ ] Improve support for Rotate and Pinch trackpad gestures #110852\n- [ ] Allow changing Color Picker value with the trackpad #110853\n\n## Archived patches\n\n- [x] [D6481](D6481) Fix Loop Cut with trackpad or magic mouse #61259\n- [x] [D6483](D6483) Scrolling popovers with trackpad #65350\n- [x] [D6588](D6588) Add trackpad smart zoom event support\n- [x] [D7279](D7279) Keymap orbit/pan preference now applies to the trackpad\n- [ ] [D8521](D8521) General fixes for 2D/3D navigation #89906 #92221 \n- [x] [D8522](D8522) Make Clip/Image editor respect the Zoom Axis, fix zoom speed and Invert Zoom\n- [x] [D8527](D8527) 3D View Zoom and Dolly improvements and fixes\n- [x] [D8530](D8530) Fix Ctrl + Trackpad-Pan to cycle values\n- [x] [D8535](D8535) Ctrl + Trackpad-Pan to cycle values, support more button types\n- [ ] [D8542](D8542) Ability to change the frame `screen.frame_offset` with the Pan gesture #76464\n- [x] [D8550](D8550) Change the default of Trackpad Natural preference #64917 #71431\n- [ ] [D8675](D8675) Ability to scrub Timeline `anim.change_frame` with the Pan gesture\n- [x] [D8682](D8682) Fix Crash with Continue zoom in the Node Editor #65714\n- [x] [D8683](D8683) Fix Zoom to Mouse Position is broken for View2D #78211 #70749\n- [ ] [D8684](D8684) Zoom to Mouse Position makes 2D Views pan after zoom limits are reached #43554\n- [x] [D8685](D8685) Fix Zoom Axis is not working in the Node Editor #65837\n- [x] [D8686](D8686) Fix Zooming out a lot faster than zooming in #73575\n- [x] [D8760](D8760) Fix 3D view navigation with Auto Depth enabled #77509\n- [ ] [D8797](D8797) Improve distinguish between a mouse scroll-wheel and trackpad scroll #86223\n- [ ] [D8811](D8811) Trackpad support for `ui_colorpicker_small_wheel_cb`\n- [ ] [D8812](D8812) Support for `stitch_modal` and `minimize_stretch_modal`\n- [x] [D9402](D9402) Read the `directionInvertedFromDevice` property and push it to the event system\n- [x] [D9533](D9533) Add smooth scrolling for Popovers\n- [ ] [D9552](D9552) Better scrolling in the Text Editor\n- [ ] [D9641](D9641) Bring back the ability to change the speed while Fly navigating\n- [x] [D9723](D9723) Fix wrong scroll deltas on the retina display\n- [x] [D10291](D10291) Trackpad scroll direction reversed in list views\n- [ ] [D13320](D13320) Improve scrolling of the search box with the trackpad\n- [ ] [D13437](D13437) Fix button flickering when scrolling popovers\n- [ ] Scrolling menus instead of changing the active item\n- [ ] Smart zoom feature for image editor and others", "macOS: touch input fails to work on a Wacom Intuos Pro tablet\nOperating system: macOS 11.1 Big Sur build 20C69\nGraphics card: n/a\n\nBroken: Top of tree git pull from today\nWorked: probably never since 2.8\n\nWacom Intuos Pro tablets support touch in addition to pen entry. When using touch, two fingers will scroll up and down. In Blender, two finger touch should work like an Apple touch pad or Apple magic mouse: two finger movement will orbit the view; holding down command zooms, holding down shift pans. Instead, it simply does nothing.\n\nBlender.app, default cube. Place two fingers down on a Wacom Intuos Pro tablet and move them around; it should orbit, but nothing happens. Well, the bottom status bar flickers back and forth as though command/shift or alt is pressed. \n\nThere are two reasons why this happens. \n1. Blender has incorrect Cocoa/AppKit code. I worked on AppKit for ~13 years at Apple. Below is a diff that addresses some of the issues. The code attempts to keep track of m_multiTouchScroll, but this isn't needed. It should key off of hasPreciseScrollingDeltas instead. I tested this diff with: Apple Magic Mouse, old school Apple scroll wheel mouse, Wacom tablet; all things work the same (except Wacom, which has the bug I'm reporting fixed). There is also a comment about intuos5, but that seems to be incorrect and outdated, but I don't have an Intuos 5 to test with.\n\n[0001-Fix-scrolling-with-wacom-tablets-using-them-as-a-tou.patch](0001-Fix-scrolling-with-wacom-tablets-using-them-as-a-tou.patch)\n\n2. Wacom's tablet touch drivers do link-checked behavior based on the bundle identifier \"org.blenderfoundation.blender\". In other words: they change the touch behavior when they see the target application is Blender. Wacom needs to fix this, but I'm not sure how to log a bug report for them.\n\nTo prove this, I created the sample application:\n\n[TabletTest.zip](TabletTest.zip)\n\nThe sample application has the blender bundle identifier set, as seen in this screen shot:\n\n\n\nIn ViewTest.m I log the flagsChanged:\n\n``` - (void)flagsChanged:(NSEvent *)event\n```\n{\n NSLog(@\"%@\", event);\n}\n```\n```\nIf you run the app and do a two finger scroll in the window you will see some flagsChanged logged, which is very strange because Shift/Alt/Cmd have not been pressed! Wacom is faking them for some reason, and changing the scrolling data, which messes up Blender.\n\nChange the applications's bundle identifier to \"org.blenderfoundationXX.blender\" (you can simply edit the info.plist) and run it again; it will then behave correctly.\n\n\n\nI don't know how to fix item 2 for Blender; I'm fixing it in my own build of Blender by changing the bundle identifier to org.blenderfoundation.bl3nder after it is built. I looked into identifying the events, and I can could identify the source as coming from the wacom driver but I can't fix them. \n\nI'm trying to find a contact at Wacom to have them fix this, but once it is fixed we still need item 1 fixed. \n\n\n\n", "Allow changing Color Picker value with the trackpad\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\n\nWe can use the mouse wheel while hovering over the Color Picker to edit the value.\nBut this feature doesn't work when we use the trackpad scroll.\n\nThe required changes are quite simple: D8811\n\nInside the Color Picker popup box, scroll over the color wheel.\n\n", "Button flickering when scrolling popovers using the trackpad\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.6.1\nWorked: never\n\n\nButtons flicker when scrolling popovers using the trackpad. See the attached video.\n\nThe fix seems to be pretty straightforward:\nD13437\n\n\n- Reduce the size of Blender window\n- Properties editor > Camera > \"Camera Presets\" menu\n- Scroll this popover with the trackpad\n\n", "Annotations (D) do not work with 3d cursor tool (keymap issue)\nMacBook Pro (Retina, 15-inch, Mid 2015)\n2.5 GHz Intel Core i7\n16 GB 1600 MHz DDR3\nAMD Radeon R9 M370X 2048 MB\nIntel Iris Pro 1536 MB\n\nBlender 2.80 Alpha 2\nHash: c94f806dc73\n\ndate: 2018-11-14 22:51\n\nAnnotation tool does not work when pressing D and LEFT MOUSE BUTTON.\n\nAnnotation tool will work when searching with CMD+F; but also within the search, if you click ENTER the annotation tool will pop up for a split second and disappear. \n\nAttaching a short video.\n[Annotation Bug.mov](Annotation_Bug.mov)\n", "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.", "Multi mesh edit mode select assert\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 3.6 alpha, main branch as of writing.\nWorked: Not sure, any release build I suppose.\n\nWhen editing multiple meshes while xray is enabled, using pick select can call assert:\n```\nBLI_assert failed: C:\\GitHub\\Blender\\blender\\source\\blender\\blenkernel\\intern\\object.cc:1756, BKE_object_eval_assign_data(), at 'object_eval->runtime.data_eval == nullptr'\n```\n\nMake sure you're using a debug build.\n1. Add one cube, or two if you don't have one yet.\n2. Select both cubes and enter edit mode.\n3. Enable x-ray.\n4. Click on a vertex on one object, then on the background, then on a vertex on the other object, then on the background again.\n5. Repeat this a few times and it should raise an assert.\n", "multiview: overwrite and file naming \n\n\"not overwrite\" option doesn't work with multiview when some views already exist on disk, could be a minor problem but rendering one single view with views option activated create a 0 byte \"myfile_L.jpg\" file but save only myfile.jpg\n\n\n\n\n\n", "Sculpt undo bug, mixing sculpt brush and multi-res modifier changes.\nWith current master (also 2.83).\n\nThe following steps show and error when redoing sculpt mode undo, when mixing multi-res subdivisions.\n\n- Startup file\n- Add multi-res modifier.\n- Enter sculpt mode.\n- *Repeat this 3-5 times.*\n - Multi-res subdivide.\n - Brush Stroke.\n\n- Now undo until the very beginning.\n- Now redo until the very end.\n\nWhen redoing, there are glitches where the multi-res has tearing/artifacts.\n\nSee video: [sculpt_undo_bug.mp4](sculpt_undo_bug.mp4)", "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`.", "Armature combined with subdivision incorrect normals\nOperating system: Windows 10 Pro\nGraphics card: GeForce 1050ti\n\nBroken: 2.82 (broken in a different way), 2.83.14, 2.92, 2.93 beta, 3.0 alpha\nWorked: 2.79b (important is working in 2.81)\nWhen using an armature modifier and subdivision modifier on the same mesh you get the wrong normals. If the armature is applied to the mesh then the subdivision normals are correct. The problem with the armature and subdivision together only applies if the armature is posed.\n\nThis broke between good ba1e9ae4733a and bad da6929488a64, probably 9516921c05\n\nI think that a bug has come into 2.82 a fix has been applied but it has broken it differently. So between 2.81 and 2.82 something broke, then a fix was put in that is still broken but in a different way. So 2.81 is the good version.\n\nCreate a mesh and create an armature on the mesh. Add a subdivision modifier. Make sure the armature has a pose. Show the normals.\nThe consequences will mean that the surfaces are wrong and the subsurface and general render will just look wrong.\nGood:\n\nBad:\n\n\n[blender2_79b.blend](blender2_79b.blend)\n\n[blender2_92.blend](blender2_92.blend)", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "Regression: GPU Subdivision: EEVEE doesn't refresh viewport correctly with Armature modifier\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.3LTS, master\nWorked: 3.2.2\n\nGPU Subdivision doestn't refresh viewport correctly an object when Armature and Subdivision Surface Modifiers are used.\n\n1) Start Blender.\n2) Add Armature object\n3) Switch to \"Shading\" workspace.\n4) Select the Cube and add `armature modifier` then `Subdivision Surface Modifier`.\n5) Switch to Properties Editor to \"Modifier Properties\"\n6) Add armature in armature modifier's object property. \n7) Switch between object-edit mode\nIt works fine when \"GPU Subdivion option\" is turned OFF (Prefrences > Viewport > Subdivision > GPU Subdivision)\n\nI added \"BeforeGPUSubDBug.blend\". You can reproduce this issue by loading the blend file and doing step 7)\n" ]

[ "No way to increase falloff size in proportional edit mode on laptops\nMacBook Pro (Retina, 13-inch, Early 2015)\nOS X Version 10.11.4\n\n2.77a\n\nWhen proportionally editing using trackpad, there is no way to increase the size of the falloff \n1. Go into edit mode on a sphere\n2. Hit o on the keyboard to enable proportional editing.\n3. Attempt to change falloff size using scroll.\n\nIt seems like trackpad interaction is a HUGE problem for blender (I have run into all sorts of very similar \"bugs\" which are more like prodigious developer oversights). The trackpad should get its own project status!!!!! Not being able to use critical scroll based features of blender on my brand new laptop is very disappointing. I shouldn't have to carry around a clunky mouse when I have a super sexy force touch, multitouch trackpad built in with pressure sensitivity (please take advantage of it) and haptic feedback. I can only imagine how bad it must be for artists that use a wacom tablet when blender can't even handle a run of the mill trackpad, let alone an Apple engineered one." ]

[ "Cascaded shadows produced with EEVEE with orthographic camera loose resolution.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0 Alpha\nWorked: no idea?\n\nAs you can see in the image below, to the left side we have an orthographic camera, to the right we have a normal perspective view and the shadows are broken through the orthographic one, \n\n\nCreate a new scene\nPut a plane to cast shadows from the light source\nselect the camera and switch it to orthographic.\nturn the light to sun light\ntada!\n\nIt doesn't seem to happen with the lights in either point, spot or area.\n", "Viewport display of multiple Dupli-Collections when different draw-types are used : wireframe might disappear (only selected are garuanteed to draw)\nOperating system: Windows 10 / Ubuntu 20.04\nGraphics card: GTX 1080 / RTX 3080\n\nBroken: 2d9d08677e a2d59b2dac \nBroken: all versions >= 2.8\nWorked: 2.79\n\nViewport display of Dupli-Collections is inconsistant.\nDigging deeper into it, it looks to be when there are different draw types on the same dupli-collection\n\n1. Open attached blend file\n2. select the empties in the middle of the screen which do not look like they have anything attached\n3. notice how they randomly appear / disappear upon selection.\n4. note that one of instancer is set to `Textured` draw type, the other to `Wire`, if all are set to `Wire` the issue is gone\n\nThis has happened in quite a few of our production scenes.[bug.blend](bug.blend)\n\nNOTE: Might boil down to be the same as #101822 (Collection instance set to Display As Wire doesn't show in Solid mode when not selected) or #86732 (Instanced wire objects are hidden in solid mode instead wire appearance)\n\n", "Alpha hashed material produces shifting artifacts when animated in EEVEE\nWhen an object with material that has alpha hashed transparency is animated in EEVEE, the noise pattern may look either unstable or shifting as shown below: \n[alpha-hashed-transparency-problem.mp4](alpha-hashed-transparency-problem.mp4)\n\n\n\nYou can observe that the artifacts on top staying in place rather than rotating with the cube while those on the sides keep flickering, thus producing shifting and unstable appearance.\n\nThe symptom is also noticeable when changing the camera position in rendered viewport mode in Blender. And it's particularly problematic in UPBGE (a fork of the old BGE based on the latest Blender source) because a game engine must animate objects in realtime with relatively small number of samples per frame.\n\nUpon an examination from the developers of UPBGE, it is found that the problem is due to the fact that the current implementation of alpha hashed transparency uses the world coordinate instead of the object space, as it is often recommended (e.g. [2017 ACM SIGGRAPH Symposium on Interactive 3D Graphics and Games](p4TYf5DDpbQ)).\n\nIt appears that a simple change from the world to object coordinate fixes the problem as shown in this [test commit (see line 80) ](e0a8638d0b255f2fc6ce778d10dd0d12a467b4d3#diff-2b8bf4f9e10009510d02c14e3659ee032c73f829de5453d6abcdf6a3f884fdfdR80), which produces the following result:\n[alpha-hashed-problem-solved.mp4](alpha-hashed-problem-solved.mp4)\n\nIt's my understanding that the [original author ]() decided to use the world matrix to avoid the difficulties with certain corner cases, like when the object is scaled by an extreme factor. However, while such a problem may be circumvented relatively easily (e.g. discard the scale information from the matrix) such a problem described above may pose more substantial issues with making an animation or rendering in realtime.\n\nSo, I hope this problem and the suggested fix may be evaluated again since we have more people interested in using Blender for such purposes now, thanks to the gaining popularity of EEVEE.", "X-Ray mode shows flickering edges of planar mesh\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 2.80, 2.83.20, 2.93.9, 3.2.0 release, 3.3.0 Alpha\nWorked: never, from what I can see. Didn't test older than 2.80.\n\nX-Ray solid shading of a mesh shows flickering edges when rotating the camera. \n\nThis could have something to do with the mesh being planar.\n\n- Open the attached file.\n- Rotate the viewport camera with {key MMB}.\n- See that some edges flicker into and out of existence.\n\n[bugreport.blend](bugreport.blend)\n\n[Desktop 2022.06.25 - 14.38.23.03.mp4](Desktop_2022.06.25_-_14.38.23.03.mp4)", "Boolean modifier - Intersect option - not working / artifacts while doing 3D Sectioning\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0 Beta\nWorked: in Blender 2.92\n\nStrange artifacts using 3D sectioning using Boolean modifier - Intersect (see sectioning animation issues below)\n\nExpected behavior:\n3D slice working correctly in Blender 2.92 (to view internal section of object)\n```\n-Create Mesh Plane (larger than object)\n-Select Plane - Add Boolean Modifier \n\tOptions - Intersect\n\tObject - STL or Object\n\tSolver - Exact\n\n```\n\n\nActual behavior:\n3D slice issues using Blender 2.93 beta (to view internal section of object)\n1) Not showing object as a 3D section like in 2.92 (see animation above)\n2) Artifacts Showing up when moving cutting plane back and forth (see animation below) \n\n\n\n\nIn the blend file, move the `Plane_xy` along the z axis, or move the `Plane_xz` along the y axis.\n[section.blend](section.blend)\n\n", "Eevee Volume Artifacting\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.3.1\n\nI'm rendering some nebulae in Eevee and despite having 256 render samples, 256 volumetric samples and 128 volumetric shadow samples with 0.9 distribution and 2px tile size with proper start and end clipping distance both in camera and volume settings I'm getting really ugly flickering where the whole volume just artifacts which is really irritating. I'd love it if you could fix this issue in the upcoming blender release because even though I have a good computer it still takes 30 minutes to render the exact same scene in Cycles (where the issue is absent). watch?v=8ImqpM4zOEU\n\n[#101826.blend](T101826.blend)\n\n- Open file \n- Render animation\n\nIssue is visible after rendering ~10 frames when animation is inspected.\n\n", "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)", "Missing overlays in the viewport when viewing through transparent shader\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6.1\n\nwhen viewing an LGT-shadow_caster.004 object, all overlays disappear from a certain side of it\n\n\nSee LGT-shadow_caster.004 in blender 3.6 splash screen\n\n", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "Geometry Nodes: Weird RayCast Accuracy\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 531.61\n\nBroken: version: 4.0.0 Alpha\n\n\nThe black dots inaccuracy only appears on the point domain. On the face domain everything is expected.\n\n", "Cycles: Motion blur artifacts\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.88\n\nBroken: version: 3.2.2\n\n\n**description of error**\nWhen rendering an animated rigged model on cycle **with motion blur** ; if the model has **auto smooth enable AND a subdivision modifier**, then it is possible that strange artefact will appear during the render. (doesn't happen in the viewport) \n- This bug do not happen if auto smooth is disable or doesn't have a subdivision modifier. \n- The bug also only appear during some specfic poses. So this is mainly noticiable when rendering an animation.\n- Those artefact often appear near sharp edge.\n- Only happen on Cycle, Eevee render seem fine.\n- [Edit] changing the shutter values of the blur will sometime remove the bug on some frames OR make the bug appear on frame that was fine before.\n\nHere 2 Render exemple with and without autosmooth , both has motion blur enabled :\n \nAnd here an animation where you can notice the bug.\n[Animated0035-0318.mp4](Animated0035-0318.mp4)\n\n\n[MotionBlurCycleArtefact.blend](MotionBlurCycleArtefact.blend)\nIn this blender file, rendering the frame 302 will make the bug happen. \n- If you disable auto smooth on the model (the main body and not the cloth) then the render will be fine.\n- If you disable the subdivision modifier on the model then the render will be fine.\n- If you disable the subdivision modifier AND the auto smooth on the model then the render will be fine.\n\nThank\n", "Faces culled with \"backface culling\" still receive shadows in the viewport\nSorry if this is a repeat report. I was unable to find another report for this.\n\nOperating system: NA\nGraphics card: NA\n\nBroken: All versions of Blender 2.8X and 2.90 that I am able to test.\nWorked: Never\n\n**Short description of error:**\nWhile the \"Backface culling\" option is enabled in the viewport, the culled backface will still receive a shadow when the \"shadow\" option is also enabled.\n\n\n\nFor example, here's a box with all it's normals facing inwards. With backface culling, we are able to see inside the box. But with shadows also enabled (as seen in the picture), shadows are cast onto the \"culled\" faces.\n\n\n\n**Exact steps for others to reproduce the error:**\n1. Create scene with an object that has it's normal facing away from the camera (you're seeing the backface).\n2. Enable \"Backface culling\" in the viewport shading options.\n3. Enabled \"Shadows\" and adjust the position of the \"light\" such that the \"back face is in shadow.\n4. The backface should now have a shadow placed on it.\n5. If you reproduce the steps above for the workbench render engine, the same issue applies.\n\n[Backface Shadowing.blend](Backface_Shadowing.blend)", "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.", "Redo causes pointy mesh artifacts in Multires\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.90 (sub 0)\n\nIn the new multires, if I sculpt on a level, then subdivide, sculpt on that layer again, then undo to the base level and redo back to the higher levels, it creates a pointy mess in the place of where I'd sculpted.\n[bad undo redo multires.blend](bad_undo_redo_multires.blend)\n[2020-05-02 01-39-06.mp4](2020-05-02_01-39-06.mp4)\n1. Remove default cube, add UV sphere. Go to sculpting workspace. \n2. Add a multires modifier and create a few subdivision levels.\n3. Sculpt on those levels and undo back to the lowest level.\n4. Redo back to the higher levels. Some of those steps would have pointy shapes.\n", "Edges, generated with Triangulate modifier looks differend and do not disappear with hiding.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 640/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n2.83 release\n\n\n[2020-06-18_15-14-00.mp4](2020-06-18_15-14-00.mp4)\n[untitled.blend](untitled.blend)\n\nDefault cube with Triangulate modifier, wireframe mode, edit mode.\nSelect all, hide. You will have this.\n\n\nThere is no way to part of mesh with generated edges and hide another part.\nAlso weird shading for polygons.\n\n\n" ]

[ "Blender 2.81 — Shadow glitches with Workbench render-engine (in viewport and same at render)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.81 (sub 9)\n\n\nBroken shadows \"traced path\" glithc effect in the air in places where geomety have \"complex area\" (when you use shadows from Workbrench render and same in viewport).\n[Screenshot ](l2ZRNEjhzLYbl2.jpg)\nHere is on [video ](#!0OoB2I7R!h1qq3DB20nOOgoxoYw9QT_kyoZO-a-1C7OSqRifExcs) uou can see it. Sorry for broken english.\n\n\nDon't know how to reproduce it step by step, so I've put the file here: \n[broken.blend](broken.blend)\n\n\n" ]

[ "Viewport: Auto-Depth rotation ignore transparent image reference empties\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90 (sub 0)\n\ncant rotate around partially occluded image objects.\n\n\nopen file, make sure rotate around mouse is enabled in preferences. hover mouse over either side images and hold in the mouse wheel, move the mouse, the view will rotate around the mouse. Now do the same for the middle image, the view no longer rotates around the mouse.\n\n[rotate around mouse bug with image objects that are occluded.blend](rotate_around_mouse_bug_with_image_objects_that_are_occluded.blend) \n\n", "Viewport display: in front should be listed under visibility as it also affects final render\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nUnder object properties, viewport display: in front affects both the visibility in the viewport and in the final render, and as such should probably be listed under visibility rather than viewport display.\n\n-", "2.93 EEVEE ScreenSpace Reflections - Trace Precision Factor - Faded Reflections (Reflections Not Fully Reaching The Upper Surface of Objects ''\nOperating system: Windows-10\nGraphics card: GeForce GTX 960M\nBroken: version: 2.93.0 Beta\n\n\n\n\n\n\n\n\n\n\n\n\nThe new 2.93 screenspace reflection implementation' s trace precision is not enough to put reflections on all the surface of object (especially near the top parts of surface near upper edge) compared to the screenspace reflections with same or less trace precision in old 2.92 implementation. Its like reflection always fades to top and increasing trace precision doest fix it.\nNormally trace precision allows for reflections go all the way up on (for example cube surface) to make its surface fully reflected, but new 2.93 Trace precision 1 doesnt allow for fully making surface reflective and give darker less reflective areas near upper side edges or upper corners\n\nFor instance, in most cases: 2.92' SSR with trace precision 0.25 is almost = (almost equal to ) = 2.93 SSR with trace precision 1 (maxed)\n\n(Even though camera is further away enough to get all the reflections from screenspace , new SSRI 2.93 trace precision is inadequate and kind of gives the effect of ''as if'' we make zoom in so screenspace doesnt see all objects and the top part of cube didnt get any reflections and get darker and faded into weak reflections) \n\nMoreover, when its compared with cycles, with trace precision of 1 ob both , 2.92 one looks closer to cycles while 2.93 has faded reflection on upper pars of surface (maybe even though new reflection implementation uses cycles implementation, new implementations inadequate trace precision might be making it differerent from cycles)\n\n\n1. Create a plane scale by 5 and move -1 (down)\n2. Edit the material of default cube and previously created plane by using same material and give it a red color FF0000 with max saturation 1 \n3. Optional step: make base color saturation of material lower to see faded darkening effect more Plus Make it metallic if you want to see the result more with metallic or just leave it as it is\n4. Ensure viewport shading settings do not use scene world but use the forest HDRI and maximize world opacity and remove blur\n5. In properties rendering tab, Enable screenspace reflections and make edge fading zero. Also uncheck half-res trace\n6. Go camera view and dont zoom too much on viewport so screenspace reflection can see everything around\n7. !!Do same processes in 2.92 and 2.93 releases to compare \n8. Then, set 2.92 and 2.93 have trace precision to 0.25 - and observe\n- In 2.93 U will notice the reflected surface of the cube as u approach top edges/as u go up, have darker/unsaturated or ''Faded'' screenspace reflections caused by the trace preciison is not enough to reach there\n- however in 2.92, the reflection reaches better to all the surface and it has almost no faded or darker look\n9. Make 2.93 SSR trace precision 1 while 2.92 SSR is still 0.25 and observe:\n- then u will notice, ''the result of 2.93 SSR Trace precision 1 '' is more similar to ''2.92 SSR with trace precision of 0.25 ''\n10. When 2.93 SSR Trace precision is 1, make 2.92 SSR trace precision 1 and observe agan\n- Then u will notice 2.92 SSR Trace precision is the ideal to fully trace all reflection to surface perfectly without having any faded area with less reflection. On the other hand, 2.93 Trace precision 1 is still not adequate to put reflection to upper parts of cubes surface near top edges with full power and precision\n\n'!! Compare these on both 2.93 and older 2.92 version with old SSR implementation\n\nIn summary in 2.92 when we increase trace precision from 0 to 1, the tracing or visibility of reflections go all the way up to top edge of cubes surface making it fully reflected as trace precision maxed\nOn the other hand, in 2.93 if we increase trace precision from 0 to 1, the reflections still cannot reach all the way up to cubes surface near top edge which gives a faded and partially traced upper surface area.\n\nMaybe, To solve this maybe, the screenspace trace precision factor can be multiplied by 4-6 or maybe the it should be square cubed so the 2.93 trace precision of 2.92.\n\n[2.93&92 SSR-TRACE PRECISION 1 - CAMERA VIEW .blend](2.93_92_SSR-TRACE_PRECISION_1__-_CAMERA_VIEW_.blend)\n\n[2.93&92 SSR-TRACE PRECISION 0.25 - VIEWPORT VIEW POSITIONED .blend](2.93_92_SSR-TRACE_PRECISION_0.25_-_VIEWPORT_VIEW_POSITIONED_.blend)\n\n[2.93&92 SSR-TRACE PRECISION 1 - VIEWPORT VIEW POSITIONED .blend](2.93_92_SSR-TRACE_PRECISION_1_-_VIEWPORT_VIEW_POSITIONED_.blend)\n\n[2.93&92 SSR-TRACE PRECISION 0.25 - CAMERA VIEW.blend](2.93_92_SSR-TRACE_PRECISION_0.25__-_CAMERA_VIEW.blend)", "USD Export: 'specular' input does not conform to UsdPreviewSurface specification\nOperating system: Windows\nGraphics card: NV\n\nBroken: Blender 3.6.0 - universal scene description branch 82ffff9a9117, and below\nWorked: N/A\n\nUsdPreviewSurface UsdShade nodes are authored with a [_float specular_](usd_writer_material.cc#L293) input as opposed to the _color3f specularColor_ input described by the [specification](spec_usdpreviewsurface.html#preview-surface).\n\nAdditionally, the _useSpecularWorkflow_ input needs to be set to 1 in order for the _specularColor_ input to have any effect.\n\n1. Export a USDA file with materials\n2. Locate a UsdPreviewSurface shading node and find the _specular_ input:\n```\ndef Shader \"Principled_BSDF\"\n{\n uniform token info:id = \"UsdPreviewSurface\"\n float inputs:clearcoat = 0\n float inputs:clearcoatRoughness = 0.03\n color3f inputs:diffuseColor = (0.8, 0.8, 0.8)\n color3f inputs:emissiveColor = (0, 0, 0)\n float inputs:ior = 1.45\n float inputs:metallic = 0.33333\n float inputs:opacity = 1\n float inputs:roughness = 0.5\n float inputs:specular = 0.7777\n token outputs:surface\n}\n```\n\n", "object display as wire , invisible when overlay is turned off \nwin 10\nintel i5\namd radeon \n\nblender 2.8 \n6b39dc7672eb\n\n\nNot sure if it's abug or intended behaviour \n\nWhen an object is set to wireframe ( object properties , viewport display ) , when overlays is turned off , the object is not shown ", "EEVEE is ghosting with viewport denoising enabled.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHere's a viewport render:\n[EEVEE ghosting0001-0090.mp4](EEVEE_ghosting0001-0090.mp4)\n\nHere's what it looks like during playback if viewport denoising is enabled:\n[2021-10-23 17-07-44.mp4](2021-10-23_17-07-44.mp4)", "Eevee viewport soft shadows are broken on higher sample count\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: ---\n\nEevee soft shadows in viewport have color spills. But it works fine on final render (F12)\n\n\n\n- Open .blend file\n\n[bug_soft_shadows.blend](bug_soft_shadows.blend)\n\n- Switch to Rendered Mode of Viewport Shading\n- Wait half a min and see the problem(", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Viewport display broken for fire- solid and rendered mode (Cycles & Eevee)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\n[Fire seems to get 'stuck' in the viewport (as in it does not disappear), it does however behave correctly when F12 rendered.\nThis happens in 2.83Alpha and 2.82Beta (both downloaded as of today, approx 16:00 Sydney time 15 Jan 2020)]\n\n[Bake the attached and observe.\nhere's what it looks like-\n[ViewportFire_2-82+2-83.mp4](ViewportFire_2-82_2-83.mp4)\n\nIt works Ok when F12 rendered as seen here-\n[Fire26Nov20190001-0050.mp4](Fire26Nov20190001-0050.mp4)\nI couldn't be bothered to render out the clip in Cycles but stills show the error is only in the viewport-\n\n\nHere's the .blend-\n[Fire2.83A.blend](Fire2.83A.blend)\n\nThis works properly in the 26November2019 build, here's what that looks like-\n{[F8279386](ViewportFireMantaflow_26-11-19Build.mp4)}]\n\n", "Image Editor Blank After Switching Slots, Even If There Is A Render In That Slot\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: (2.80, 79f67acccb36, blender2.7, 2019-03-24)\n\nSwitching the slots in the image editor for the render result (hotkey \"j\") can show a blank image, even if there is an image available in that slot.\nSelecting the render layer in the dropdown menu brings it back.\nThis is irritating, especially since the image is shown right after rendering.\nThis only happens if the compositor is disabled.\n\n- Load [bug.blend](bug.blend).\n- Press F12 to render. The image editor comes up.\n- Press \"j\" to switch to switch the slot.\n- Press F12 to render again.\n- Press \"j\" to switch back to the previous slot. It now appears blank.", "In eevee, shading disappears when SSS is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: -\n\nShading disappears in Eevee if one object is located on another object and both have Subsurface enabled\n\nWhen an object has no shading, it looks unrealistic and wrong.\nTo get around this bug, I render two images and connect them in the compositor.\n\nMaybe it is possible to somehow enable these shading without a second render?\nSSS is needed for both objects.\n\nBall Subsurface On (0.02)\n\nBall Subsurface Off (0.0)\n\n\n.Blend file\n[bugshafowsubsurface.blend](bugshafowsubsurface.blend)\n", "COLORSPACE SELECTOR: Group box fails to show all possible colour transforms\nDebian Stretch\n\nTrunk\n\nTrial against ACES 1.0.3 set won't show all possible colour transforms when choosing via the UV Image Editor\n\nLoad the ACES 1.0.3 configuration from the official repository. Try to change the colour transform on a loaded image.\n\n\n", "\"Reset to Default Value\" sets alpha incorrectly in [Material Properties > Viewport Display > Color]\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.5.0\n\nRight-clicking \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] sets both the color's \"value\" and \"alpha\" bars to 0.8, when the alpha one specifically should reset to 1. Alpha resets incorrectly.\n\nRight-click \"Reset to Default Value\" on [Material Properties > Viewport Display > Color] on any material.\n\n", "Viewport and final render differs in lighting/materials\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nSimple scene, only one sun light and HDRI lighting. Shows different result in viewport render and final render.\n\nJust compare viewport and final render and see the difference in specular highlight of the sun on the main (green) material.\nAlso, I don't know if this is important, I use Agx color transform in Blender, not Filmic or Standard.\n\n", "Viewport Shading 'Attribute' Option Broken for Instanced Geometry\nOperating system: Windows 10\nGraphics card: Nvidia GTX 2080\n\nBroken: 3.5\nWorked: 3.4, 3.4.1\n\nWhen instancing a mesh to another meshes vertices, the Solid Viewport Color Option 'Attribute' is no longer displaying the vertex color data.\n\nCreate A Sphere, and using \"Vertex Paint Mode\" Paint a color onto the sphere.\nUsing geometry nodes set up the following, Group Input (Geometry) -> Mesh to points - > Instance on points -> Realize Instances -> Output (Geometry)\nSet a simple sphere as the object to be instanced.\nSet Shading mode to 'Solid'.\nToggle 'Attribute'\n\n" ]

[ "EEVEE - Specular Light Viewport Render Pass Behavior (AO and Screenspace Reflection - Over-Darkening Effect on Metallic Object)\nOperating system: Windows-10\nGraphics card: GeForce GTX 960M\n\nBroken: version: 2.93.0 Alpha\n\nWith Metallic objects, New Screenspace reflections and AO implementation (or another cause or bug is maybe the reason) creates over-darkening and unexpected results (when there is a metallic object) that can also be seen on Specular Light Pass from viewport passes as well as just by looking at a metallic object in combined pass\n||\n| -- | -- |\n||\n||\n\n\n- Open attached file or:\n - Create a plane without adding or changing its material and scale by 5 and move -1 (down)\n - Edit the material of default cube and set metallic value to 1\n - Ensure viewport shading settings do not use scene world but use the forest HDRI and maximize world opacity and remove blur\n - Then in Render Pass set the Specular Light pass for example\n - Go to properties and first activate ambient occlusion - (it will make it everything over-dark)\n - then second activate screenspace reflections and - (it will make everything dark on specular light pass)\n - Also Go to combined pass of viewport- the metal cube will have strange dark shadows and darker reflections due when u use AO+SSR\n!! Compare this with 2.92.0 and there specular light pass is working properly and metal cube doesnt have strange over-dark look etc. when AO and SSR is active\n[eevee_ssr_bug.blend](eevee_ssr_bug.blend)\n\n\n\n\n\n" ]

[ "Angle input fields fail to accept units when scene rotation units are set to radians\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nAngle input fields usually accept rotation units as 'd' for degrees and 'r' for radians after the entered number, however when scene rotation units are changed to radians in the scene properties, this functionality stops working. Blender reports an error when units are entered: \n\n\n> Error evaluating number, see Info editor for details: File \"<string>\", line 1\n> 2d\n> ^\n> SyntaxError: unexpected EOF while parsing\n> \n\n\n\n\n\n\n1. Open new scene and change rotation units to radians in the Properties Editor, Scene tab, Units section. \n2. Type some number followed by 'd' for degrees in any rotation input filed.\n\n\n", "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.", "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", "Keyframed group inputs bound to index not property\nOperating system: Windows 10\nGraphics card: GTX 1070 (Laptop)\n\nBroken: 2.80.0 009dbc2bc9fb\n\nKeyframing a property on the group input stack, maintains the keyframe at the stack index rather than the mapped property. This means when the ordering of group inputs is changed the keyframe is maintained at the previous position/index rather than moving with the initial property.\n\n\nBased on the default startup\n\n1. Create node group with multiple inputs\n2. Keyframe 2nd property\n3. Push this group input up or down the input stack (while inside node group)\n4. 2nd property will stay keyframed rather than moving up/down stack with the correct property.\n", "Weighted normals modifier produces different results on objects of different scales\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.0\n\n\nWeighted normals modifier is not consistant on small objects \n\nOpen Blender\nCreate a cube 1mmx1mmx1mm, scale applied, \nadd bevel and weighted normals modifiers\nYou can notice the différence by doing the same process on a 1mx1mx1m cube\n\nI can do a work around by modifying the unit scale parameter but I think it should work on 1mm objects, like a lot of watch pieces. \n\n[weightednormals_defect.blend](weightednormals_defect.blend)\n", "Statistic doesn't update if object deleted due to object data deletion with RMB\nBroken: version: 3.0.0\nBroken: version: 2.80 (sub 75)\nWorked: unsure (didn't find scene statistics in 2.79...)\n\nScene statistic (both in footer and 3D viewport) does not update correctly if object data is deleted with RMB\n\n1. Open default scene.\n2. Make sure you enable scene statistic either in 3D viewport or footer.\n3. In outliner unroll object to show it's object data, i.e. default cude.\n4. Click on object data, i.e. cube mesh, with RMB and delete it.\nObject will be deleted since it doesn't have mesh/camera/light object data. Notice that scene statistic is not updated (number of objects, vertices, selected status etc.). To update it you can select any object or click on outliner (doesn't matter on object or not).\n\nThat works correctly if object is not deleted, i.e. adding subdivision modifier (statistic will update) and then deleting it with RMB in outliner (statistic updated again).", "imported scenes in video sequencer, don't use the scenes own dimensions\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nmaking a video editing scene, and importing scene clips from different sizes all clips will have the same dimensions or bounding box despite them not actually being the same size\n\nLook at the attached blend. When selecting the scene 1 clip with the monkey, you can see that it's bounding box is much bigger than the actual clip. Which makes it just a bit harder to align correctly. And regardless of impact it seems wrong\n\n", "Remove normalization from original coordinate attribute (CD_ORCO)\nFrom #95776:\n\n> The internal CD_ORCO attribute is normalized to 0..1 which is not really helpful, not even as default texture coordinates. It would be good to do some refactoring so these are stored unnormalized and then applying any additional texture space scaling for rendering only.", "VSE: The blend and opacity settings that strips are created with does not match the default values they revert back to\nOperating system: Linux-5.4.0-80-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\nStrips are created by default with blend method \"Cross\" and blend opacity \"1\", however reverting to default values results in \"Replace\" and \"0\".\n\n- Open VSE\n- Add/create any strip\n- Under strip properties in sidebar, note that blend method is \"Cross\", and opacity value is \"1\"\n- Choose \"Reset to default value\" from context menu for both of these settings\n- Blend method will change to \"Replace\"\n- Opacity value will change to \"0\"", "No Vector Displacement On Instances\nWindows 10 x64\n\n2.79.4\n\nVector displacement doesnt work with instances, It mirrors the displacement on the first object, Im sure this is working as intended but there are many cases where you need to displace actual instances as well.\n\nHaving a checkbox somewhere to enable instance displacement would be amazing\n\n\n\n\n\n[instances.blend](instances.blend)\n", "When changing the width of frame, it also changes frame location.\nIf you create frame and set it into (0,0) location. Then grab right side of the frame node and make frames width bigger. Now using python read the frame \nlocation again and it is not (0,0) anymore. \n\n", "Simulation Nodes Reset Behavior\nCurrently, the simulation range for geometry nodes is the scene range. So whenever the cache becomes invalid and we go back to frame 1 (or whatever the scene range start is), the cache is reset. \n\nNow, we want to add support for giving individual simulations separate frame ranges. Those might not match the scene range anymore. The simulation start might be before the scene start frame to support preroll (potentially even at a negative frame). Therefore, using the scene start frame as the reset point, does not make sense anymore.\n\nThe new behavior should/could work like this:\n* Invalidated simulations reset whenever the current frame is at or before the simulation start frame.\n* There is a new \"Play with Preroll\" button in the timeline that starts playback at the first simulation start frame in the scene. \n * Since this frame is at or before all simulation start frames, all invalidated simulations are reset.\n\nOpen Questions:\n * Are all or only invalidated simulations taken into account when determining the first frame for the \"Play with Preroll\" operator.\n * Where to put the new \"Play with Preroll\" button exactly, what should it be called and what should it look like?\n\n", "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", "RAM fills up when switching scenes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\n\nIf the user switches from one scene to another the systems RAM fills up.\n\n1. open a task manager or something to watch RAM usage\n2. Create Suzanne and subdivide it to get a somewhat heavy object\n3. Duplicate Suzanne several 100 times to get a somewhat complex scene so that you can see your see RAM usage increase\n4. Click the \"New Scene\" Button and hit \"Linked Copy\"\n5. Repeat step 4 a couple of times and note that RAM usage will increase\n6. If RAM usage exceeds the available system RAM Blender will crash\n\nBlender apparently fails to clear the RAM from unused scenes when switching to or creating a new scene.\n\n\n", "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top." ]

[ "Mapping Node \"Scale\" Vector has Incorrect Default Value\nOperating system: macOS 11.2 Big Sur\n\nBroken: 2.81 – 2.93\nWorked: 2.80\n\nThe “Scale” vector in the Shader Editor’s Mapping node has an incorrect default value of (0, 0, 0). In Blender 2.80, the default value is (1, 1, 1) which makes much more sense for the mapping’s scale.\n\n1. Add a “Mapping” node in the Shader Editor. The “Scale” vector has an initial value of (1, 1, 1).\n2. Right-click on the “Scale” vector and choose “Reset All to Default Values”.\n3. The vector resets to (0, 0, 0).\n\n", "Geometry Nodes: Scale resets to 0 on Transform Node\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n\nHello,\nWhen resetting the Scale value on the Geometry Transform Node, it resets to value of 0,0,0 instead of 1,1,1.\n\n[reset to default.blend](reset_to_default.blend)\nOpen the Attached scene, hover over the Scale of the Transform node and hit Backspace to reset its values. They will become 0 instead of 1." ]

[ "Regression: Some particles have darker faces\nOperating system: Windows 10 1909\nGraphics card: GTX 1070 512.15\n\nBroken: 3.1 (also 3.1.1 RC)\nWorked: 3.0.1\n\nSome object instances, in a hair particle system, have darker faces\n\n3.0.1\n\n\n3.1 and 3.1.1 RC\n\n\nPress F12 in this test file:\n[Dark Particles.blend](Dark_Particles.blend)", "Attribute Edit Mode\nThis is an extract from the now archived Vertex Color/Attribute Edit Design (#71947).\nThe design needs further investigation an discussion with the #geometry_nodes module.\n\n## Attribute Edit Mode\n\n\n\nAttribute Edit is intended to be a mode to modify and visualize any kind of data stored in mesh elements. Some use cases for it could be:\n\n- Editing IDs on face corners to modulate materials in a shader\n- Painting velocity vectors on vertices to guide a particle system\n- Editing the weights of a rig\n- Editing per face colors for low poly models without using textures\n- Setting custom values on edges for a motion graphics animation\n- Modifying mesh values for procedural modeling\n\nSome of these task could use a brush, but they don’t need a brush with artistic painting functionality. It does not make sense to edit the weights of a rig with a brush with wet paint and density noise.\n\nFurthermore, these task could take advantage of a mode with more control and precision tools than an artistic painting mode, like precise elements selection and data editing, controlled value interpolation…\n\nThe plan is to use the current Vertex Paint mode as a base implementation for this mode and start adding all necessary features during multiple releases. It already has quite some work done because most users were using it with these use cases in mind.\n\nThis task is not as detailed as the Sculpt/Paint mode, but it should be enough to have an idea of its purpose, use cases and design goal.\n\n### Tools\n\n**Simple brush tools**\n\nThe current Blender brush functionality is enough to support this kind of painting, if we consider painting changing the values of elements that are inside the cursor radius. We can reuse the current brush code for that.\n\n**Value interpolation tool**\n\nThis tool could produce controllable interpolations of an attribute between two mesh elements following the mesh topology. For example:\n - Select the base of a cone and assign the value of one \n- Select the top vertex of the cone and assign 0 \n- Let the tool generate the rest of the values across the cone surface\n\n**Mesh elements selection**\n\nAttribute paint should provide tools for selecting mesh elements and assign values directly to them. This provides much more control than a brush. This could be useful when working with low poly models, where you want to assign values like armature weights in a precise way.\n\n**Mesh element masking**\n\nWe can support a basic masking functionality for the brush that supports all mesh elements (not only vertices like the Sculpt/Paint mask). This can make easier some painting task.\n\n### Features\n\n**Data conversion operators**\n\nAttribute edit mode should provide a set of conversion tools to convert data between elements and other Blender data layers when possible. For example:\n\n- Convert a per vertex attribute to a per face corner attribute\n- Convert a per edge attribute to a vertex attribute averaging the\n```\n values\n```\n- Generate material slots from an ID attribute stored on faces\n- Generate an editable 2D vector attribute from an UV layer\n\n**Per face corner color data to sculpt/vertex color data**\n\nThis is a specific case of a conversion operator. Other conversion operators can be added in the future as we support more attribute types.\n\n**Internal attribute conversion**\n\nWe need to identify what element/attribute type conversion combinations are more frequent and design how they can work (usually averaging the values). For example\n\n- Converting an attribute from face corners to faces by averaging the\n```\n values of all the face corners in the face\n```\n- Converting from vertex to edges by averaging the value of the two\n```\n vertices of the edge\n```\n- Converting from vertex to face corners assigning the same vale of\n```\n the vertex to all the face corners that use that vertex\n```\n\n**Topology symmetry**\n\nWe could support editing operations with symmetry based on the mesh topology instead of mirroring the XYZ axis.\n\n**Attribute data type selection**\n\nThe use should be able to choose what kind of data he/she wants to edit and in which mesh element that data should be stored. For example\n\n- A float factor stored on faces\n- A vector stored on vertices\n- A color stored on face corners (Current supported MLoopCol)\n\nAll tools should be aware of the data type of the layer and behave accordingly.\n\n**Import/Export**\n\nIt should be possible to import and export meshes with different attributes in mesh elements. We need to check format compatibility.\n\n### Rendering\n\n**Attribute edit overlay**\n\nAs we can make assumptions that the attributes are colors, we need to render a configurable overlay to display the data in an appropriate way.\n\n**Attribute rendering mode selector**\n\nThe attribute rendering overlay should provide and UI to choose which rendering mode the user wants to render the data. This should include tools like a gradient editor, rendering two attributes at the same time, render vectors and randomly generated ID maps.\n\n**EEVEE/Cycles attribute node**\n\nThe current attribute nodes exposes MLoopCol and UVs to the render, which are both loop attributes. We need to investigate how to expose face, vertex and edge values.", "Crash entering editmode on an object with particles and ridgidbody parented to another rigidbody\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\nThe hair particles are facing the opposite direction and blender crashes, trying to solve this.\n\n\n[Donut2-1.blend](Donut2-1.blend)\n\n[Donut2-1.blend1](Donut2-1.blend1)\n\nCreated a donut according to site watch?v=jNmnPXY9UQA\n\nSteps:\nParticle Properties\n+\nHair (Not showing ?!?)\nFirst frame -> Hair showing downwards!\nTab\nBlender crashes repeatable.\nSteps:\nParticle Properties\n+\nHair (Not showing ?!?)\nFirst frame -> Hair showing downwards!\nTab\nBlender crashes repeatable.\n\n", "Make force fields support solid objects\nCurrently, if a force field is created with a *Surface* shape, particles (and hair and cloth) will be attracted or repelled along the normals of the mesh. With a positive force, particles are always repelled away from the nearest face. This works well for surface meshes, i.e. where the faces are two-sided. However, it is not useful for simulating solid meshes.\n\nFor a solid mesh, the faces should be considered to be single-sided: the direction of the force should not change when the particle crosses the face, as shown in B in the following diagram.\n\n\n\n - A: Current behaviour: force direction always reverses at face boundary and at midpoint between faces. Particles can get trapped inside solid objects.\n - B: Proposed behaviour: force direction is consistent across face boundary, but still reverses at midpoint. Allows particles to be repelled from surface and pushed out from inside.\n\nThis `.blend` file demonstrates the problem: if the particles or cloth end up inside the cube, they never escape. Under this proposal they should be repelled, because the force field strength is positive.\n\n[cloth_cube_repel.blend](cloth_cube_repel.blend)\n\nIf this is option is implemented, it could be exposed as a new option, or the *Both Z* / *+Z* / *-Z* options could be reused for it.", "Cycles: tapering hair transparency fails in '3D Curves' mode [regression] (probably caused by embree)\nOperating system: Ubuntu 20 LTS and MacOS Mojave\nGraphics card: Quadro p2000\n\nBroken: 2.92 and latest 2.93.0 alpha 5f1f233dc97de34f6be0f51edd3cbf2d8247fbda\nWorked: 2.82a and 2.83.4\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nSetting a transparent BSDF shader to hair in 3D curves mode yields a visible error where parts of the hair are black.\nThis issue is visible in the viewport and at render time. It affects both CPU and GPU rendering.\n\nIn ribbons mode, transparency works almost as expected. I noticed that when hair strands overlap and they have transparency, they are not transparent but they take the background opaque color instead, so the hair strands below are \"covered\" with background color.\n\nembree\n\nbefore embree\n\n\n[#86500.blend](T86500.blend)\nOpen file and switch to rendered view\n\n---\n\nOriginal report:\n\nInitial setup in viewport: a cube with 20 hair strands:\n\n\nRender in version 2.83.4:\n\n\nRender in version 2.92+\n\n\n\nAttached is a .blend file example (so that you don't need to reproduce the steps below). [transparent_hair_curves_issue.blend](transparent_hair_curves_issue.blend)\nIf you run it on Blender 2.82a, rendering should show only a cube. Blender 2.92+ will show the issue.\n\nSteps:\n- Open a new default blender scene with a cube\n- Choose Cycles renderer\n- Under Render Properties > Hair, select 3D Curves\n- Add a hair particle system to it\n- Lower particle count to 10\n- Set segments to 5\n- Enable Hair Dynamics, play the timeline for a while until hair bends\n- Go to simulated frame 30 (just an example)\n- Scroll down in psys panel to Render, enable b-spline with steps 2\n- In Timing, set start to 0.361 (just for testing purpose)\n- In Hair Shape, set Diameter Root 0.5, Tip 1, Radius Scale 1.00\n- Render in viewport or to an image (same result)", "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", "Low hair children and viewport display numbers cause hair to be excluded from parts of the mesh \n**System Information:**\nOperating system: Windows 10 and Linux (both show issues)\nGraphics card: RTX 2060 SUPER (452.06 Windows) (450.66 Linux)\n\n**Blender Version:**\nBroken: 2.79, 2.80, 2.81, 2.82, 2.83, 2.90, 2.91.0 Alpha\nWorked: Not sure\n\n**Short description of error:**\nWhen an object with a hair particle system has the `Viewport display` percentage set to a low amount and the `Hair Children viewport display` option set low, hair is excluded from parts of the mesh. Here's a video demonstrating the issue:\n[0029-1590.mp4](0029-1590.mp4)\n\n**Exact steps for others to reproduce the error:**\n1. Obtain a object with a high number of faces (I used a cude subdivided 5 times)\n2. Give the object hair particle system and increase the hair count to something like 10,000 or 100,000 to make the effect more apparent.\n3. In the hair particle settings scroll down to the `Viewport display` section and change the `Amount` slider to a low percentage (E.G. 2% or 5%)\n4. Notice how there are hairs distrobuted across the entire mesh.\n5. In the `Children` tab of the hair particle settings tab, enable one of the options `Simple` or `Interpolated`.\n6. Notice how the hair is now only distrobuted over part of the object rather than the entire object. As you increase the `Viewport display - > Amount` value and/or the `Viewport display number` for the children, this issue goes away.\n\nHere's a .blend file show casing the issue: [#81117 - Hair excluded from parts of a mesh.blend](T81117_-_Hair_excluded_from_parts_of_a_mesh.blend)", "Curve sculpting: occlusion by hidden parent makes the curves unresponsive to brushes.\nOperating system: Fedora Linux (Gnome Wayland)\nGraphics card: AMD\n\nBroken: 3.5.1\n\nSculpting the curves is not possible when hiding the parent and \"occluding\" the curves with the now invisible parent.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nAdd empty hair to the cube.\nAdd curves in sculpt mode.\nHide the cube.\nTry to sculpt the curves from the other side of the cube. \nDragging from inside the hidden cube and dragging from outside the hidden cube give different results, when it feels like it should not.\n\n", "Hair Dynamics: simulation doesn't work depending on smooth/flat shaded surfaces (and nvidia gpus?)\nOperating system: Windows 10\nGraphics card: RTX 2070 QMax\n\nBroken: v 2.80\nWorked: (optional)\n\nhair dynamics doesn't work, hair stuck in place, doesn't follow the mesh\n\n- build simplest possible model with hair dynamics\n- add simple animation\n- with hair dynamics disabled: hair follows mesh\n- with hair dynamics enabled: hair just stays behind and stretches to the mesh\n- changing settings, clearing cash ... all to no avail\n\n[190814_test_hair_dynamics.blend](190814_test_hair_dynamics.blend)\n\n", "Keyframing object scale with object hair particles makes particles scale in viewport\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 75)\n\nObject with hair particles (rendered as objects or collection) if scaled, scale only emiter, not particles (that is desired effect), but after keyframing scale on object, particles also are being scaled with emiter. This happens only in viewport (any type of shading), renders are ok.\n\n1. Add emiter mesh (plane)\n2. Add particles object (cube)\n3. Create particle system with plane as emiter\n4. Set particle system to hair\n5. Set particle system to render object then select cube\n6. For emiter object (plane) add two keyframes with different scale\n[scaling particles.blend](scaling_particles.blend)\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", "Randomization in Mask Brush for Curves Sculpt Mode\nRef #96673 (Masking tools for curves sculpt mode.).\n\nDepends on #96850 (Mask Brush for Curves Sculpt Mode).", "Booleans causing shadow artifacts in solid render mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 3.0.0 Alpha\nWorked: Unknown\n\nI built up a random shape using a bunch of booleans via the box cutter addon.\nThis seems to have introduced artifacts when the shape is viewed from certain angles.\n\nThe artifacts remain when applying all the modifiers. I also tried to reset various edge data like bevel weight and crease without any effect.\nAdding a triangulate modifier however cleans it up, so maybe something about the automatic triangulation is off.\n\nI compared the output with the stable release: It also shows artifacts but they look slightly different, at least with my current configuration.\n\nv.2.93.1\n\n\nv.3.0.0 (see version info above)\n\n\nIn motion from another angle, showing convergence on a point and something that looks like an [even/odd fill rule](Even%E2%80%93odd_rule) of a shape being used to draw the shadow:\n[streaks.mp4](streaks.mp4)\n\n\nI cannot offer concrete steps; my default file also has certain settings already applied.\nHere is the file that may help show the issue: [shadow-streaks.blend](shadow-streaks.blend)\n", "Particle system texture added via API not working ['blend_type' when created using the interface is MULTIPLY, whereas when created through API, its value is MIX]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83 (sub 17)\n\nHi,\n\nI have been trying to write a script that automatically adds a clouds texture to control the density of hair particles/instances. I have been able to successfully add a texture to the active particle system of the selected object with the Density checkbox under Influence activated -- all done through API. However, there is no effect on the density of the particles.\n\nI am clueless of why this is happening. Is this a bug?\n\nI have attached a blend file (with an internal script) for reproducing the bug.\n\n - Open the attached blend file.\n - Allow execution of scripts (in case not allowed)\n - Select the plane (already has a particle system) and search for 'Particle Density Texture' and execute the script.\n\nThe texture will get added successfully to the particle system's texture slots with the density option on, but will have no effect on the particle distribution whatsoever. The script also has an UNDO panel. You could try changing values there or in the properties panel as well, but will have no effect.\n\nAm I doing something wrong? Or is this a bug or a known issue or any API limitation?\n[particle_density_texture.blend](particle_density_texture.blend)\n\n", "Using Sculpt Collision clips some of the hair curves in Rendered viewport shading\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 528.49\n\nBroken: version: 3.5.0 Alpha\n\nEnabling the new Sculpt Collision, combing some hair and then switching to render mode clips parts of the hair.\n\n\n- Open attached file\n- Select CUDA device\n- Disable cage opacity property\n- Enable viewport rendering and comb curve hairs\n[Add hair curves, add some hair, activate Sclupt Collisions, comb the hair, hit render viewport shading]\n[attached .blend file (as simple as possible)]\n\n" ]

[ "particle edit \nOperating system: windows 7 x64\nGraphics card: Quadro 600\n\nBroken: (2.80, cd92f8ea4626, master, 2019-03-28)\n\n\n\nwhen using hair brush in side of mesh it affect the opposite side despite a polygon barrier between them\n\n" ]

[ "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "Fill material act weird when two layers masks each other and one of them has Fill Holdout 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 472.39\n\nBroken: version: 3.1.0\nfill material act weird when two layers masks each other and one of them use holdout material and inverting mask.\nalso that happen when we use stroke material as holdout or both stroke and material holdout\n see video \n[0001-1466.mp4](0001-1466.mp4)\n", "Particle edit mode - Hide hairs doesn't work\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 50)\nWorked:\nThe \"hidden\" hairs can't be selected or edited\n\n\nThe hidden hairs are still visible.\n\nAdd a hair system to the default cube \nSwitch to particle edit mode and then switch to point display/select mode\nSelect any number of particles, press H to hide\n- >The hairs are only locked, not hidden\n\n\n", "Wrong undo/redo sequence with direct transform change (via Item/transform panel or addon)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 2.93.1\n\n\nUndo operation is not working properly with `Copy attributes addon`.\n[refer the video to understand the situation better]\n\n\n**Exact steps to Reproduce the error**\n\n[2021-07-28_13-59-32.mp4](2021-07-28_13-59-32.mp4)\n\n**To reproduce**\n- 0. Make sphere, go to sculpt mode.\n- 1. Draw «1» on sphere\n- 2. Change location via item panel\n- 3. Draw «3» on the sphere\n- 4. Undo actions with {key Ctrl+Z}: undo order is broken\n\n---\n\n**Exact steps to Reproduce the error (Addon Case)**\n\n- Open .blend file\n- Enable Copy attributes addon\n- Select both mesh objects\n- Do {key Ctrl C} -> `Copy Locations`\n- Switch to edit mode\n- Perform some changes to the mesh\n- Switch to object mode\n- Perform undo operation.\n\n[Notice that the undo operation ignores all the steps from edit mode and directly switches the mesh to the initial position]\n\n\n[2021-07-27_13-33-38.mp4](2021-07-27_13-33-38.mp4)\n\nTest File:\n[#90234.blend](T90234.blend)", "Mantaflow: Smoke simulation is affected by point force field in a wrong way \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n[particles with point force.blend](particles_with_point_force.blend)\n\n\n\n\n\n[smoke with point force.blend](smoke_with_point_force.blend)\nI have seen the issue first with version 2.8x but it is on all later versions including 3.0.\n\nI found that a point force field affects a smoke simulation in the wrong ways while it affects particles in the correct way.\n\nIn my example I use a mesh uv-sphere as emitter for a smoke simulation. I use mainly default settings in the flow emitter and smoke domain but I disabled gravity for this scene.\nA point force field is set in the middle of the sphere emitter so I would expect that the smoke became and holds a spherical shape that’s growing only in size over the time.\n\nBut the result that I see is a kind of 3d cross ( a cross on all 3 axes ). To me it seems that some vector math is not done correctly .\n\nAs force fields affect smoke and particles I did the same setup with a particle system instead of smoke domain. The uv-sphere is now the emitter . Gravity is also disabled as well as all kinds of start velocity.\nThe particles are emitted only in the first three frames.\n Then particles are affected from the point force field is set in the middle of the sphere emitter. As expected the particles always keeps the shape of a sphere as it should be.\n\nI will add blend files and screenshots to illustrate the issue.\n\n", "Mesh Analysis broken by Hidden Wireframe\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.93\n\n\nThe Mesh Analysis overlay seems to draw only back faces when the Hidden Wireframe overlay is also enabled:\n\n\n\nThe vertical red streak is Suzanne's right ear, which should probably be occluded. The back faces of the right eyebrow are also rendered green, but the front faces of the left one aren't.\n\n\nTurn on both the \"Mesh Analysis\" and \"Hidden Wireframe\" overlays in Edit Mode.", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg", "Polishing Correct Face Attributes\n- [ ] Initialize operators options based on the \"correct face attribute\" value (e.g., edge slide).\n- [ ] Unify naming of the option and the operator options.\n\nThe way we do Proportional Editing seems to be a good example to follow. These issues have been raised on 4387aff", "Objects in front of the selection stay in front in wireframe mode\nBroken: version 2.80+\nWorked: version 2.79\n\nIn blender 2.79, the wireframe of objects selected or in edit-mode was drawn in front of the wireframe of all other objects in the scene.\nIn blender 2.80 onwards, this doesn't happen anymore.\n\nHere's a model shown in 2.79b, with my usual theme:\n\n\nThe object in edit mode is behind the objects seen with gray wireframe. But because it is in edit mode, it is drawn in front of the others.\nThe same is true if the object is in object-mode but selected.\n\nNow compare the same model in 2.8x:\n\n\nHere the same object is seem in edit-mode. Now it is drawn behind everything else, which creates a noisy, low-contrast appearance, making it hard to see and sometimes hard to edit. \nSometimes it forces me to rotate the view to get other things out of the way (especially if the foreground objects have a lot of detail/geometry).\n\nIf you zoom in real close on an area where a foreground object overlaps the selection, snap a screenshot, and then scale or zoom the image, you can see how the foreground object is definitely being drawn in front of the active one:\n\n\nBottom line: In my opinion, in a normal view mode like Solid or Lookdev/Material, the selection of course should remain behind everything else (unless changed via its Object properties), but in Wireframe view mode the selected object should appear in front of other stuff.\nPerhaps an option is needed the Preferences to force the old 2.79b draw order.\n\n- Open attached file\n- Change the wire theme to something gray (or use the attached theme).\n[wireframe_in_2_79.blend](wireframe_in_2_79.blend)\n[classic-look.xml](classic-look.xml)\n\nThe original model is probably too big to upload here: Hypercube%20printer%20model%20(320x320%20bed,%20540x510x540%20frame).blend", "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", "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", "Concave cutter causes bevel with arc outer miter to produce weird geo with protrusions inside the negative space of the cutter\nOperating system: Manjaro Linux\nGraphics card: NVIDIA GeForce GTX 1060 6GB\n\nBroken: 3.1.2\nWorked: 2.79.0\n\nCreate a mesh and give it a concave wall (i.e. a cylinder with 6 sides, subdivide one face from top to bottom, and move it in towards the center on the x and y axes), and create a difference boolean on the top of the default cube and hide the cutter. Next, grab a cylinder a decent number of sides (32 is fine), and create a union boolean inside the negative space of the cut. Finally, add a bevel modifier to the cube, set the Miter Outer setting under Geometry to Arc, and you should see geo similar to as shown in the screenshot below.\n\nThe bottom surface of the cutter is completely flat, however rotations of the complete surface does not affect the bug. There is a workaround to prevent the weird geo by performing separate bevels before and after the protrusion boolean.\nHere is a sample blend file demonstrating the bug using the instructions above:\n\n[sample.blend](sample.blend)", "Proportional Editing Influence Is Far Outside Of Influence Circle In Graph Editor\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.6.3 Release Candidate\n\nProportional Editing reaches way too far from influence circle when using the graph editor causing non-highlighted neighboring keys to move even if they are far from highlighted keys.\n\n<video src=\"attachment\" controls></video>\n\nI'm providing a video for reference.\n\n• Have an f-curve with keys on every frame.\n• Move a few keys up several values away from the main line of keys.\n• Turn on Proportional Editing (smooth default) use small influence circle.\n• Adjust key on the original base value next to keys that have been moved.\nNormally influence will only affect the keys in influence range and not keys so far away.\n\nThanks,\nTim\n\n", "QuadriFlow with the new symmetry option creates holes at the center\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\n\n\nQuadriFlow creates hole artifacts like these when remeshing. Usually occurs after using Voxel Remesher and/or Dyntopo which can break symmetry at the center very often.\n\n\n1) Sculpt something in Sculpt Mode and use Voxel Remesher/Dyntopo.\n2) Start QuadriFlow. It doesn't always produce these holes in the mesh, but keep repeating part one and two and you will eventually get these holes where each side hasn't been properly merged together." ]

[ "Hair strands can be edited thru emitter in Solid/lookDev/Rendered mode\nOperating system: Win10 x64\nGraphics card: GTX 1070, 419.67\n\nBroken: 2.80 (sub 51), master, 2019-03-28 16:07, eeefea86cddb\n\nJust create some hairs on one side of a cube and try to edit them from the opposite view in the solid view mode." ]

[ "Running a script that registers an operator from the same operator crashes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIf you execute an `bpy.ops.text.run_script()` through the operator through the panel in a Text editor, then blender crashes.\n\nP.s. maybe it's my fault and I did something wrong, but is blender supposed to crash?\n\nCopy the script or download the file:\n```Py\nimport bpy\n\nclass Op(bpy.types.Operator):\n bl_idname = 'op.op'\n bl_label = \"Op\"\n def modal(self, context, event):\n bpy.ops.text.run_script() # <------- here -------\n return {'FINISHED'}\n def invoke(self, context, event):\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n self.layout.operator(Op.bl_idname, text='Click me')\n\n\nclasses = (Op, Panel)\n\ndef register():\n for c in classes:\n bpy.utils.register_class(c)\ndef unregister():\n for c in reversed(classes):\n bpy.utils.unregister_class(c)\n\nif __name__==\"__main__\": register()\n```\n\n", "Modifying keymap won't tag prefs dirty\nWindows 7 Professional 64-bit service pack 1\nIntel Core i7-2600\n8GB RAM\nNVIDIA GTX 1060 6GB\n\nBroken: blender-2.80.0-git.aa003c73245f-windows64\n\n\"Save Preferences\" button, shown when \"Auto-Save Preferences\" is turned off, stays unavailable after modifying keymap.\n\n1. Make sure \"Auto-Save Preference\" is turned off. If it isn't, turn off this and press \"Save Preferences\" button.\n2. Modify keymap, editing the settings used to activate an operator (example: search for `Clear Rotation` operator, changing the `Clear Delta` option will not tag prefs dirty).", "Blender crashes when calling ArgumentParser.parse_args() if sys.argv is anything other than [\"path/to/blender.exe\"]\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.1\n\nBlender crashes when calling `ArgumentParser.parse_args()` if `sys.argv` is anything other than `[\"path/to/blender.exe\"]`\nI discovered this bug while trying to run a script using the `exec()` function. Any script that uses argparse makes blender crash.\n\nYou can run this code\n```Py\nimport argparse\nimport sys\nimport bpy\n\nsys.argv = [bpy.app.binary_path]\nsys.argv.append(\"--some_arg\") # Comment this line and everything works fine\n\nparser = argparse.ArgumentParser()\nargs = parser.parse_args()\n```\n\n", "Blender crashes when merging mesh.vertices with a python script\nOperating system: Pop_OS 20.04\nGraphics card: Intel 4th Generation Core Proc \n\n\nBroken: 2.82a\n\n\nLink to stackoverflow question:\n\nblender-crashes-when-merging-mesh-vertices-with-a-python-script\n\nI have reuploaded the question here because I think It could be an error with blender code rather than mine. The steps to reproduce the crash would be creating an icosphere mesh, setting the max_distance variable to 0.3 and just moving nodes nearby to other ones and clicking run_script then. At some point it will close and save an ico.crash.txt. I have attached mine.\n\n[ico.crash.txt](ico.crash.txt)\n\n[#88022.blend](T88022.blend)\n\n[#88022.webm](T88022.webm)", "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", "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", "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)]", "Removing and readding hotkeys adds them in the wrong section of the keymap\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\n\nWhen you remove let's say the hotkey to call the toolbar in the 3D view, and then readd it, then it gets readded in the wrong section of the keymap. The result is that this hotkey may be troubled now. See example below.\n\nThis behaviour breaks the functionality to manage your hotkeys from within the right click menu of the operators in the UI. This is a showstopper bug for user configured keymaps. \n\n\nOpen Blender. In the View menu of the 3D view remove the hotkey for Toolbar. This hotkey is local, just for the 3D view. It's initally located in the generic section of the 3D view.\n\nNow readd the hotkey. Watch in the keymap where it gets readded. In the Window section. And this section acts global.\n\nNow switch to the Scripting Layout. Press the hotkey that you have readded in the 3D View. You will get a error message now. The hotkey is now global, it is in the Windows section. But the toolbar does not exist in the Text editor. And so we get a error message.\n\n\n\n\n\n\n\n\n\n\n\n", "Blender Crashing When Painting Stroke into a \"Moving Animated Character\" (heap-use-after-free)\nBroken: 4.0 alpha\nBroken: version: 2.79 - 2.82 (sub 7)\nWorked: Never\n\nI have this experiment of making LIVE talking head, via OSC. And I noticed that if I tried painting a stroke on a talking moving animated head, it will crash. Even with timeline not running.\n\nI got a video (Might need iPhone X with MOM addon to test this....) :\njhHdG6ZXFDU\n\n- Open attached file\n- Run animation\n- Paint over the animated object\n[paint_animated_shapekey_bug.blend](paint_animated_shapekey_bug.blend)\n\n\n", "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", "Nodes: Assert and crash: Editing nodes through the material panel and undo.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8729\n\nBroken: 3.4, 3.3, ... 2.8\nWorked: never\n\nWhen I select certain nodes from the materials tab after pressing undo on the last node change, blender crashes. But only if the last click is made with my wired USB mouse. Or even if the cursor was left on the button to switch tabs before clicking with the touchpad.\n\n\n```lines=10\n# Blender 3.4.0, Unknown revision\nbpy.context.space_data.context = 'MATERIAL' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF717820508\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n\n\nStack trace:\nblender.exe :0x00007FF7178203F0 blender::ed::space_node::ui_template_node_link_menu F:\\Blender_build\\first\\blender\\source\\blender\\editors\\space_node\\node_templates.cc:659\nblender.exe :0x00007FF71736AAF0 ui_block_func_POPUP F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_menu_popup.cc:183\nblender.exe :0x00007FF717463480 ui_popup_block_refresh F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_popup.cc:566\nblender.exe :0x00007FF717463050 ui_popup_block_create F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_popup.cc:796\nblender.exe :0x00007FF71736CA60 ui_popup_menu_create F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_region_menu_popup.cc:358\nblender.exe :0x00007FF717397CC0 ui_block_open_begin F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:4224\nblender.exe :0x00007FF717391810 button_activate_state F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8338\nblender.exe :0x00007FF71739CD50 ui_do_but_BLOCK F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:5982\nblender.exe :0x00007FF7173A7AB0 ui_do_button F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8027\nblender.exe :0x00007FF7173A9D20 ui_handle_button_event F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:9189\nblender.exe :0x00007FF7173BA070 ui_region_handler F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:11275\nblender.exe :0x00007FF7156CFE60 wm_handler_ui_call F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:786\nblender.exe :0x00007FF7156D1CE0 wm_handlers_do_intern F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3217\nblender.exe :0x00007FF7156D01F0 wm_handlers_do F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3334\nblender.exe :0x00007FF7156CB580 wm_event_do_region_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3754\nblender.exe :0x00007FF7156CB440 wm_event_do_handlers_area_regions F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3784\nblender.exe :0x00007FF7156DCD90 wm_event_do_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3979\nblender.exe :0x00007FF7156A5E50 WM_main F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm.c:643\nblender.exe :0x00007FF714C52160 main F:\\Blender_build\\first\\blender\\source\\creator\\creator.c:579\nblender.exe :0x00007FF7186F9260 invoke_main D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7186F9010 __scrt_common_main_seh D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7186F8FF0 __scrt_common_main D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7186F9320 mainCRTStartup D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThreads:\nThread : 00002514\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e60\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002ab8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e20\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000026a0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002404\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002234\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000ddc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000305c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002640\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ec4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002130\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ff0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000002f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000e8c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001b88\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001f10\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFE8C312176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFE7F734B90 register_onexit_function\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000132c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE58561C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFE582EF73C Symbols not available\n\n\nThread : 000000c0\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFEA2020350 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE58597770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE58597770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002298\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE58561C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001e98\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002b4c\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002278\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000014f8\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFE8DD7458B Symbols not available\n\n\nLoaded Modules :\n0x00007FF712C80000 3.4.0.0 blender.exe F:\\Blender_build\\first\\ninja_lite_debug\\source\\creator\\Debug\\blender_private.pdb \n0x00007FFEA4250000 10.0.19041.2130 ntdll.dll \n0x00007FFEA2540000 10.0.19041.1889 KERNEL32.DLL \n0x00007FFEA1FD0000 10.0.19041.2130 KERNELBASE.dll \n0x00007FFEA3550000 10.0.19041.2130 USER32.dll \n0x00007FFEA1B50000 10.0.19041.2130 win32u.dll \n0x00007FFEA2600000 10.0.19041.2130 GDI32.dll \n0x00007FFEA1CC0000 10.0.19041.2130 gdi32full.dll \n0x00007FFEA19B0000 10.0.19041.789 msvcp_win.dll \n0x00007FFEA1A50000 10.0.19041.789 ucrtbase.dll \n0x00007FFEA2630000 10.0.19041.2075 SHELL32.dll \n0x00007FFEA30A0000 10.0.19041.2130 ADVAPI32.dll \n0x00007FFEA34B0000 7.0.19041.546 msvcrt.dll \n0x00007FFEA3790000 10.0.19041.1865 sechost.dll \n0x00007FFEA38B0000 10.0.19041.1806 RPCRT4.dll \n0x00007FFEA2410000 10.0.19041.1202 ole32.dll \n0x00007FFEA39E0000 10.0.19041.2130 combase.dll \n0x00007FFEA22B0000 10.0.19041.2075 SHLWAPI.dll \n0x00007FFEA3270000 10.0.19041.1865 shcore.dll \n0x00007FFE83ED0000 14.32.31332.0 MSVCP140D.dll \n0x00007FFE8C790000 14.32.31332.0 VCRUNTIME140D.dll \n0x00007FFE9CEF0000 14.32.31332.0 VCRUNTIME140_1D.dll \n0x00007FFE7F6C0000 10.0.19041.685 ucrtbased.dll \n0x00007FFE844B0000 6.10.19041.1110 COMCTL32.dll \n0x00007FFE9C5E0000 10.0.19041.546 VERSION.dll \n0x00007FFE9B860000 10.0.19041.867 dbghelp.dll \n0x00007FFE9F730000 10.0.19041.746 dwmapi.dll \n0x00007FFE8C310000 tbb_debug.dll \n0x00007FFE7EC20000 epoxy-0.dll \n0x00007FFE67340000 3.10.8150.1013 python310_d.dll \n0x00007FFEA2F50000 10.0.19041.546 WS2_32.dll \n0x00007FFE98DC0000 14.32.31332.0 VCRUNTIME140.dll \n0x00007FFEA2310000 10.0.19041.546 IMM32.DLL \n0x00007FFE9FA40000 10.0.19041.2130 windows.storage.dll \n0x00007FFEA12E0000 10.0.19041.2075 Wldp.dll \n0x00007FFEA18A0000 10.0.19041.844 profapi.dll \n0x00007FFE9F460000 10.0.19041.2130 uxtheme.dll \n0x00007FFE9F840000 10.0.19041.546 kernel.appcore.dll \n0x00007FFEA1C30000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFE8B530000 tbbmalloc_debug.dll \n0x00007FFEA3150000 10.0.19041.2075 MSCTF.dll \n0x00007FFEA2FC0000 10.0.19041.985 OLEAUT32.dll \n0x00007FFE824C0000 10.0.19041.2075 OPENGL32.DLL \n0x00007FFE8C420000 10.0.19041.2075 GLU32.dll \n0x00007FFEA3400000 2001.12.10941.16384 clbcatq.dll \n0x00007FFE9ADF0000 10.0.19041.2075 AppXDeploymentClient.dll \n0x00007FFE57830000 30.0.14.9649 nvoglv64.dll \n0x00007FFEA3D40000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFEA1960000 10.0.19041.1620 cfgmgr32.dll \n0x00007FFEA1FA0000 10.0.19041.1023 bcrypt.dll \n0x00007FFE9D780000 10.0.19041.546 WTSAPI32.dll \n0x00007FFEA1250000 10.0.19041.546 CRYPTBASE.DLL \n0x00007FFEA1470000 10.0.19041.546 msasn1.dll \n0x00007FFE9C570000 10.0.19041.906 cryptnet.dll \n0x00007FFEA1DD0000 10.0.19041.1889 CRYPT32.dll \n0x00007FFE9AEF0000 10.0.19041.1949 drvstore.dll \n0x00007FFEA1650000 10.0.19041.1620 devobj.dll \n0x00007FFEA1F30000 10.0.19041.2075 WINTRUST.dll \n0x00007FFEA0AA0000 10.0.19041.546 ntmarta.dll \n0x00007FFE93710000 10.0.19041.546 dxcore.dll \n0x00007FFEA17D0000 10.0.19041.546 powrprof.dll \n0x00007FFEA17B0000 UMPDC.dll \n0x00007FFEA1740000 10.0.19041.2075 WINSTA.dll \n0x00007FFE87CC0000 10.0.19041.1387 dataexchange.dll \n0x00007FFE9D990000 10.0.19041.2075 d3d11.dll \n0x00007FFE9E1C0000 10.0.19041.2075 dcomp.dll \n0x00007FFEA0340000 10.0.19041.2075 dxgi.dll \n0x00007FFE94780000 10.0.19041.1865 twinapi.appcore.dll \n0x00007FFE93EB0000 10.0.19041.2075 textinputframework.dll \n0x00007FFE9ED10000 10.0.19041.746 CoreMessaging.dll \n0x00007FFE9EF10000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFE9E060000 10.0.19041.2130 wintypes.dll \n0x00007FFE7E100000 10.0.19041.1949 explorerframe.dll \n0x00007FFE8DD60000 10.0.19041.1566 directmanipulation.dll \n0x00007FFEA1230000 10.0.19041.546 CRYPTSP.dll \n0x00007FFEA0960000 10.0.19041.1052 rsaenh.dll \n\n# Python backtrace\n```\n\n```lines=10\n# Blender 3.4.0, Commit date: 2022-10-20 00:36, Hash 3915f5300ad2\nbpy.context.space_data.context = 'MATERIAL' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF6E6FDF4EA\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x00000000000001A1\n\n\nStack trace:\nblender.exe :0x00007FF6E6FDF4C0 nodeRemLink\nblender.exe :0x00007FF6E80A8DA0 blender::ed::space_node::node_socket_add_replace\nblender.exe :0x00007FF6E80A9980 blender::ed::space_node::ui_node_link\nblender.exe :0x00007FF6E7EBCF50 ui_apply_but_funcs_after\nblender.exe :0x00007FF6E7EC87F0 ui_handler_region_menu\nblender.exe :0x00007FF6E7495810 wm_handlers_do_intern\nblender.exe :0x00007FF6E7494C40 wm_handlers_do\nblender.exe :0x00007FF6E749B1B0 wm_event_do_handlers\nblender.exe :0x00007FF6E7480BC0 WM_main\nblender.exe :0x00007FF6E65512F0 main\nblender.exe :0x00007FF6EC6F4380 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThreads:\nThread : 000032c8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000778\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000015a8\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000018f0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000f34\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000265c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000458\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000fdc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000198c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000026e4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001088\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001234\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001aac\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002a14\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002228\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000030f8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000c60\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nblender.exe :0x00007FF6ED271160 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6ED270970 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6E6713C20 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022e4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002248\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00003084\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001ff0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002e60\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002514\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000b84\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000005dc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE4F811C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFE4F59F73C Symbols not available\n\n\nThread : 00002fec\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFEA2020350 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE4F847770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE4F847770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001754\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE4F811C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000e54\nntdll.dll :0x00007FFEA42F0B00 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFEA42A26D0 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000029ac\nntdll.dll :0x00007FFEA42EDC00 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFEA2020370 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\ncombase.dll :0x00007FFEA3A83390 InternalTlsAllocData\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002474\nwin32u.dll :0x00007FFEA1B5A0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFEA3570730 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFE8DD7458B Symbols not available\n\n\nThread : 000007a4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002ed4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000022dc\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00001410\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 0000154c\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00002bf4\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 00000f78\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nThread : 000031e0\nntdll.dll :0x00007FFEA42ED130 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFEA1FF2FE0 WaitForSingleObjectEx\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFE988AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFEA1A71B20 configthreadlocale\nKERNEL32.DLL :0x00007FFEA2557020 BaseThreadInitThunk\nntdll.dll :0x00007FFEA42A2680 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF6E63E0000 3.4.0.0 blender.exe F:\\Диск I\\programm\\blenders\\свежак 24-14-9-11\\b \n0x00007FFEA4250000 10.0.19041.2130 ntdll.dll \n0x00007FFEA2540000 10.0.19041.1889 KERNEL32.DLL \n0x00007FFEA1FD0000 10.0.19041.2130 KERNELBASE.dll \n0x00007FFEA2F50000 10.0.19041.546 WS2_32.dll \n0x00007FFEA38B0000 10.0.19041.1806 RPCRT4.dll \n0x00007FFE98DA0000 tbbmalloc.dll \n0x00007FFE988A0000 tbb.dll \n0x00007FFEA3550000 10.0.19041.2130 USER32.dll \n0x00007FFEA1B50000 10.0.19041.2130 win32u.dll \n0x00007FFEA2600000 10.0.19041.2130 GDI32.dll \n0x00007FFEA1CC0000 10.0.19041.2130 gdi32full.dll \n0x00007FFEA19B0000 10.0.19041.789 msvcp_win.dll \n0x00007FFEA1A50000 10.0.19041.789 ucrtbase.dll \n0x00007FFEA30A0000 10.0.19041.2130 ADVAPI32.dll \n0x00007FFE8C700000 14.29.30139.0 MSVCP140.dll \n0x00007FFE999F0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFEA34B0000 7.0.19041.546 msvcrt.dll \n0x00007FFE9A080000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFEA3790000 10.0.19041.1865 sechost.dll \n0x00007FFEA2630000 10.0.19041.2075 SHELL32.dll \n0x00007FFEA22B0000 10.0.19041.2075 SHLWAPI.dll \n0x00007FFEA1960000 10.0.19041.1620 CFGMGR32.dll \n0x00007FFE9B860000 10.0.19041.867 dbghelp.dll \n0x00007FFEA1FA0000 10.0.19041.1023 bcrypt.dll \n0x00007FFE68390000 5.7.0.7 sycl.dll \n0x00007FFEA2410000 10.0.19041.1202 ole32.dll \n0x00007FFEA39E0000 10.0.19041.2130 combase.dll \n0x00007FFEA3780000 10.0.19041.546 PSAPI.DLL \n0x00007FFE81390000 epoxy-0.dll \n0x00007FFEA3270000 10.0.19041.1865 shcore.dll \n0x00007FFE556F0000 cycles_kernel_oneapi.dll \n0x00007FFEA2310000 10.0.19041.546 IMM32.dll \n0x00007FFE53FA0000 9.0.0.0 openvdb.dll \n0x00007FFE67640000 59.16.100.0 avformat-59.dll \n0x00007FFE51AA0000 59.18.100.0 avcodec-59.dll \n0x00007FFE944D0000 59.4.100.0 avdevice-59.dll \n0x00007FFE7EBF0000 57.17.100.0 avutil-57.dll \n0x00007FFEA2FC0000 10.0.19041.985 OLEAUT32.dll \n0x00007FFE8C5C0000 6.4.100.0 swscale-6.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFE83E80000 1.21.1.0 OpenAL32.dll \n0x00007FFE82490000 2.0.20.0 SDL2.dll \n0x00007FFE99D20000 libgmpxx.dll \n0x00007FFEA3D40000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFE67170000 3.10.2150.1013 python310.dll \n0x00007FFE99A30000 tbbmalloc_proxy.dll \n0x00007FFE942E0000 10.0.19041.1 AVIFIL32.dll \n0x00007FFE844B0000 6.10.19041.1110 COMCTL32.dll \n0x00007FFE9C5E0000 10.0.19041.546 VERSION.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFE9F730000 10.0.19041.746 dwmapi.dll \n0x00007FFE92F80000 10.0.19041.546 Secur32.dll \n0x00007FFE8C530000 4.3.100.0 swresample-4.dll \n0x00007FFE98880000 10.0.19041.1 AVICAP32.dll \n0x00007FFE936E0000 10.0.19041.546 WINMM.dll \n0x00007FFE9CED0000 10.0.19041.1 MSACM32.dll \n0x00007FFE8C420000 10.0.19041.1 MSVFW32.dll \n0x00007FFE96EB0000 10.0.19041.1 winmmbase.dll \n0x00007FFEA1820000 10.0.19041.2130 SSPICLI.DLL \n0x00007FFE9F840000 10.0.19041.546 kernel.appcore.dll \n0x00007FFE9FA40000 10.0.19041.2130 windows.storage.dll \n0x00007FFEA12E0000 10.0.19041.2075 Wldp.dll \n0x00007FFE9F460000 10.0.19041.2130 uxtheme.dll \n0x00007FFEA1C30000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFEA18A0000 10.0.19041.844 profapi.dll \n0x00007FFEA3400000 2001.12.10941.16384 clbcatq.dll \n0x00007FFE9CFC0000 10.0.19041.1503 MMDevApi.dll \n0x00007FFEA1650000 10.0.19041.1620 DEVOBJ.dll \n0x00007FFE9D0C0000 10.0.19041.1865 AUDIOSES.DLL \n0x00007FFEA17D0000 10.0.19041.546 powrprof.dll \n0x00007FFEA17B0000 UMPDC.dll \n0x00007FFEA3150000 10.0.19041.2075 MSCTF.dll \n0x00007FFE80380000 10.0.19041.2075 OPENGL32.DLL \n0x00007FFE8B550000 10.0.19041.2075 GLU32.dll \n0x00007FFE9ADF0000 10.0.19041.2075 AppXDeploymentClient.dll \n0x00007FFE4EAE0000 30.0.14.9649 nvoglv64.dll \n0x00007FFE9D780000 10.0.19041.546 WTSAPI32.dll \n0x00007FFEA1250000 10.0.19041.546 CRYPTBASE.DLL \n0x00007FFEA1470000 10.0.19041.546 msasn1.dll \n0x00007FFE9C570000 10.0.19041.906 cryptnet.dll \n0x00007FFEA1DD0000 10.0.19041.1889 CRYPT32.dll \n0x00007FFE9AEF0000 10.0.19041.1949 drvstore.dll \n0x00007FFEA1F30000 10.0.19041.2075 WINTRUST.dll \n0x00007FFEA0AA0000 10.0.19041.546 ntmarta.dll \n0x00007FFE93710000 10.0.19041.546 dxcore.dll \n0x00007FFEA1740000 10.0.19041.2075 WINSTA.dll \n0x00007FFE87CC0000 10.0.19041.1387 dataexchange.dll \n0x00007FFE9D990000 10.0.19041.2075 d3d11.dll \n0x00007FFE9E1C0000 10.0.19041.2075 dcomp.dll \n0x00007FFEA0340000 10.0.19041.2075 dxgi.dll \n0x00007FFE94780000 10.0.19041.1865 twinapi.appcore.dll \n0x00007FFE93EB0000 10.0.19041.2075 textinputframework.dll \n0x00007FFE9EF10000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFE9ED10000 10.0.19041.746 CoreMessaging.dll \n0x00007FFE9E060000 10.0.19041.2130 wintypes.dll \n0x00007FFE7E100000 10.0.19041.1949 explorerframe.dll \n0x00007FFE8DD60000 10.0.19041.1566 directmanipulation.dll \n0x00007FFEA1230000 10.0.19041.546 CRYPTSP.dll \n0x00007FFEA0960000 10.0.19041.1052 rsaenh.dll \n0x00007FFE66EB0000 30.0.14.9649 nvcuda.dll \n0x00007FFE4D460000 30.0.14.9649 nvcuda64.dll \n0x00007FFE788A0000 30.0.14.9649 nvapi64.dll \n\n# Python backtrace\n\n```\n\nBlenders: 3.4, 3.2, 3.0, 2.9, 2.83\n```lines=10\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-14-8-11\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.4\\config\\userpref.blend\nWarning: File written by newer Blender binary (304.3), expect loss of data!\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFE8C723020\nModule : MSVCP140.dll\nThread : 0000207c\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-12-1\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.2\\config\\userpref.blend\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF73481F663\nModule : blender.exe\nThread : 000029c0\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 24-9-10\\blender.exe\"\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\config\\userpref.blend\nERROR (bke.node): C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\blenkernel\\intern\\node.cc:2222 nodeAddStaticNode: static node type 200 undefined\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7A47ABC94\nModule : blender.exe\nThread : 00000674\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 22-14\\blender.exe\"\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF776C49221\nModule : blender.exe\nThread : 00000cc0\nWriting: C:\\Users\\rfnei\\AppData\\Local\\Temp\\blender.crash.txt\n\nC:\\Users\\rfnei>\"F:\\Диск I\\programm\\blenders\\свежак 20-6\\blender.exe\"\nfound bundled python: F:\\╨Ф╨╕╤Б╨║ I\\programm\\blenders\\╤Б╨▓╨╡╨╢╨░╨║ 20-6\\2.83\\python\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6508070ED\nModule : F:\\─шёъ I\\programm\\blenders\\ётхцръ 20-6\\blender.exe\n```\n\n1: Open blender to the default startup file.\n2: Go to the materials tab.\n3: Click on the button next to \"Surface\" labeled \"Principled BSDF\" and select a different node to switch it out.\n4: Press Ctrl + Z on the keyboard to undo the previous action.\n5: Repeat steps 3 and 4 with various nodes until it crashes.\n(There used to be a more consistent way of replicating this, making a mix shader, putting a glossy bsdf node in the top slot, then pressing undo and selecting an emission node instead, but it stopped crashing with that just before I sent this.\n. . . And it just started crashing with that again. I'm sorry I can't give you something more consistent.)\n\nBased on the default startup file.\n", "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)", "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", "Assertion Failure: Moving Keyframe in Graph Editor beyond enum range\nOperating system: Linux Mint Mate 19\nGraphics card: Nvidia GTX 850M\n\nBroken: master 2020-11-12 @ Merge branch 'blender-v2.91-release' only on debug builds 987732181f779ca792de933aa5f001168b1f6f26\nWorked: Anything that is not a debug build will not show any problems\n\nThis issue is split off from #44219 (Pose Breakdowner bug in Gooseberry rigs)\nMoving a keyframe of an enum in the graph editor allows it to go beyond the range of the enum. This causes an assert to fail\n\n\n\n* Open the file\n* Move the keyframe up\n* Blender crashed as soon as you exceed the enum range\n[enum_property_crash.blend](enum_property_crash.blend)", "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)" ]

[ "Blender crashes when I press F8\nKubuntu 13.10 x64 NVidia GTX 560\n\n2.69.7 a5cb222\n\nF8 crash\n\nPress F8 and Blender crashes. Here is the crash log:\n\n# Blender 2.69 (sub 7), Commit date: 2014-01-03 03:20, Hash a5cb222\n\n# backtrace\n./bin/blender() [0xc8c0e6]\n/lib/x86_64-linux-gnu/libc.so.6(+0x370b0) [0x7fe3580600b0]\n./bin/blender(rna_idproperty_check+0x19) [0x179b019]\n./bin/blender(RNA_property_collection_begin+0x77) [0x17a0107]\n./bin/blender(WM_operator_properties_sanitize+0x30) [0xca1a20]\n./bin/blender(WM_keyconfig_update+0x8c) [0xc9bc1c]\n./bin/blender(wm_event_do_handlers+0x537) [0xc94b97]\n./bin/blender(WM_main+0x18) [0xc8d4b8]\n./bin/blender(main+0xd7f) [0xc58a3f]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fe35804aea5]\n./bin/blender() [0xc8ac11]\n" ]

[ "Scroll drag stuck after specific MMB click\nBlender 2.80rc1, 2.83 (sub 2)\n\nHere is the video\n[2019-02-26_06-35-31.mp4](2019-02-26_06-35-31.mp4)\n\n - Open Blender\n - In `Preferences -> Interface -> Menus` enable `Open on Mouse Over`\n - Close preference windows and go to any paint/sculpt mode\n - Display the sidebar and go to the Tool tab\n - Move mouse pointor over brush`s big icon and before it reacts with highlight (brush-search window appear) press and hold MMB\n - Then LMB to discard.\nNow scroll sticks. It releases after Esc or MMB. But at first I was forced to restart blender, because pointer stuck there.\n", "Wrong status bar keymap for release confirms and right click select\nOperating system: Manjaro x64\nGraphics card: HD5770\n\nBroken:\n2.80, 81ea815dcb6, blender2.8, 2018-12-12\nWorked: 2.79b\n\nWhen grabbing something(object, vertex, etc) by right clicking on it and then releasing/clicking on the same button the action is not performed, object doesn't return to its initial position. \nHowever if you use G or a Tool to grab instead of mice click Cancel by Right clicking option works.\n\nRight click on a Cube(in 2.79 thats enough to start moving an object but not here here you have to hold the button) AND HOLD the button\nDrag mice somewhere to move the Cube\nRight Click again to Cancel movement\nNothing happens.\n[blender_bug-2018-12-13_22.18.53.mkv](blender_bug-2018-12-13_22.18.53.mkv)\nI'm also attaching video file for it to be more clear.", "Touchscreen 'Continuous Grab'\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Mobile Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.0.2\n(bug also tested on Windows 10)\n\n\nBroken: version: 2.80 (sub 74)\nWorked:\n\n\n* Activate a gizmo using the **touchscreen** on a computer. (The 3D navigation gizmo for example)\n* Drag your finger outside the original editor\n* The gizmo is manipulated incorrectly\nThis bug disappears if \"*continuous grab*\" is disabled in the User Preferences.\nI think it's a matter of auto-disabling *continuous grab* while receiving touch input, like how pen tablets are handled.", "Geometry Nodes: Different result of Distribute Points in Volume on Mac M1 and Windows\nOperating system: Mac M1 Pro 2021, with Blender 3.4.1 and Ventura 13.1. and Windows on AMD Ryzen 7\nGraphics card: On Windows RTX 3080\n\nBroken: Current master.\nWorked: Maybe newer.\n\n**Short description of error:**\n\nOne file on Mac Os and Windows:\n\n\n**Exact steps for others to reproduce the error:**\n1. Open attached `GN_mac_vs_windows__bug_positions.blend` file\n2. Compare the final positions of points using Windows and using Mac\n[GN_mac_vs_windows__bug_positions.blend](GN_mac_vs_windows__bug_positions.blend)\n\n---\n**Original Short description of error:**\nI started reproducing This tutorial about Plexus effect on GN. I was doing on Mac M1 Pro 2021, with Blender 3.4.1 and Ventura 13.1\nI reach this exact point: tj6ZZYO5qPY?t=943\nIn Mac I get just 12 points while video reports 14.\nI first think that something in Blender change since 3.4.0 beta (the version used in the video) and 3.4.1, but then tried the file in a Windows machine with Blender 3.4.1 and it worked reporting 14 points, so it seems mac is doing things wrong\n\n**Original Steps of the report:**\nExact steps are in the video until 15:43\nI uploaded a file that show the progress until that exact point \n[GN_Plexus_redo1.blend](GN_Plexus_redo1.blend)", "Camera to View and zoom do not work with orthographic cameras\nIf you switch to ortographic camera (point 1), and try to zoom in with the camera viewport active, the camera behaves as \"view lock>camera to view\" unchecked.\nThe correct behavior is that you can get near the object without changing the camera \"unlock view > camera view\" (point 3). Even though it's checked, it's not working as intended (check point 2 in the picture)\n\n\n- Open attached .blend file\n- Try zoom in, dolly in...\n[ortho_bug.blend](ortho_bug.blend)\n\n", "Continuous Grab doesn't work with tablet on Linux\nOperating system: Manjaro Linux\nGraphics card: Nvidia GeForce GTX 750 Ti\n\nBroken: 2.92 and 2.93\nWorked: 2.93 on Windows\n\nContinuous grab function doesn't work with a tablet\n\nHave a tablet set to Relative Mode (Mouse mode). Select the cube. Press G and move the cursor to the edge of the screen. On linux with a tablet the cursor and the cube will stop at the edge of the screen but with a mouse (and with a tablet on Windows) you can keep moving them. Same thing happens when scrolling the menus with the middle mouse click (for example in outliner)\nPlease watch the video. I demonstrate the issue in the 3D viewport, as well as in the blender preferences menu\n[2021-06-20 12-55-33.mp4](2021-06-20_12-55-33.mp4)", "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)", "Touch on Gizmos can return invalid cursor coordinates\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ecb9, type: Release\nbuild date: 23/12/2018, 17:14\nplatform: Windows\n\n\nWhen using a pen, as in a Microsoft Surface or similar device, using the camera Gizmos and moving the pen outside the 3D viewport seems to return null/invalid coordinates, and it breaks. They can ONLY be used inside the 3D viewport. It's an absolute deal breaker for touch screen users (Surface, Wacom, etc)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nAny default .blender. On a touch device using a stylus pen, click on a Gizmo (axis, zoom, or drag) and move the pen outside the 3D viewport.\n\n\nWhen using a regular mouse the cursor gets hidden and it works as intended.", "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.", "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", "Box select fails to select bones at certain zoom levels\nOperating system: Linux-5.19.0-43-generic-x86_64-with-glibc2.36 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 4.0.0 Alpha\nAlso 3.5 and 3.6\n\nBox select fails when zoomed out\n\n\n- Open [Select.blend](attachment)\n- Box select some of the bones in the provided file.\n- It doesn't work for me unless you zoom in first\n- If you display the bone as \"Wire\" or \"BBone\" then everything is selecting correctly, otherwise not.\n\nIt fails in both pose and edit modes, perspective or orthographic.\n\n", "Multi-Button Drag: not working properly for Object Dimensions\nWindows 7\n\nBroken: 2014-02-11\n\nMulti-Button Drag - D270 - doesn't work properly in N panel for Dimensions\n\nIf you drag over all 3, only X and Z change, Y remains unchanged. As mouse button is released, the first selected property will reset, only the last hovered is kept (and scale changed)", "Zoom stops at certain level and won't go further\nOperating system: Windows 10\nGraphics card: GeForce GTX 1070\n\nBroken: 2.92, 3.0 alpha\n\nIn this simple model, I cannot zoom my view closer to mesh than I already did. I saved the closest achievable view position in the .blend.\nI can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me.\nThe issue is linked to this particular model - if I copy the object (there's only one in the scene) to a new model, the issue is gone.\nThe model was originally saved in Blender 3.0 alpha, only then in stable 2.92. Could it be the cause of this bug?\n\nBased on the default startup or an attached .blend file:\n[zoom issue.blend](zoom_issue.blend)", "Impossible to use any other mouse button than MMB to navigate in Knife tool mode\nOperating system: Windows 10\nGraphics card: GTX1080Ti\n\nBroken: 2.8 latest master\nWorked: Probably never\n\nThe way Knife tool mode is executed makes it impossible to navigate 3D viewport in the Knife tool mode as long as navigation buttons are mapped to any other key than middle mouse button (MMB). This does not interfere with default Blender kemap, where Orbit (Rotate), Pan and Zoom viewport navigation actions are mapped to MMB, but doesn't allow viewport navigation in the other custom keymaps, including the proposed industry compatible one: T54963 \n\nThere is no combination of settings in Knife Tool Modal Map section which would allow to solve this issue and make non-MMB based viewport navigation function in Knife tool mode.\n\n\n1, In factory default setup Blender, got to edit mode of the default cube, activate Knife tool using K key, and notice MMB to orbit, Shift+MMB to pan and Ctrl+MMB works.\n2, Go to User Preferences, Keymap section, and in 3D View>3D View (Global) \n3, Change Rotate View from Middle mouse to Alt+Left Mouse and change the action type from \"Press\" to \"Click-Drag\" (To distinguish from Alt+LMB click, which selects edge loops)\n4, Change Zoom view from Ctrl+Middle Mouse to Alt+Right Mouse\n5, In 3D viewport, notice that Alt+LMB and Alt+RMB work correctly to activate Viewport Rotate and Viewport Zoom respectively\n6, Enter Knife tool mode, and notice that Alt+LMB and Alt+RMB do not work to Rotate or Zoom the viewport.\n7, In Keymap editor, under 3D View>Knife Tool Modal Map, notice there is no possible setup to make these new navigation hotkeys work.\n\nResult: There is no way to configure Knife Tool Modal Map so that viewport navigation in Knife Tool Mode works with any other mouse buttons than MMB.\n\nExpected: It is possible to configure Knife Tool Modal Map so that it works with non-MMB based viewport havigation configuration.", "Cycles is not working in 3.5.1 on a MacBook M1 Max—causes the program to immediately freeze!\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.1\nWorked: (This started happening two days ago, and I only updated to 3.5.1 today. But in the days/weeks prior it was 3.4)\n\nOn my MacBook M1 Max (with all upgrades possible), I have had to force quit Blender countless times in the last 48 hours after turning on viewport Cycles view. Upgrading to 3.5.1 has seemingly made it a constant problem. Even now opening a brand new project, then turning on Cycles render, it starts saying it’s loading kernels (very slowly), and never renders, freezing the viewport, forcing me to force quit. So it seems I no longer can turn on Cycles in 3.5.1.\n\nThere is no further steps really, this is happening on a new project for me. Hopefully you all can see this and figure out something! I’m happy to provide further details if you need anything. I use Blender for my day-to-day at work so fingers crossed this isn’t the new normal for the foreseeable future. Also, love you all!\n\n" ]

[ "Camera view doesn't support continuous zoom\n%%%--- Operating System, Graphics card ---\nMac OSX - NVDIA 650\n\n - Blender version with error, and version that worked ---\n2.69. Has never functioned properly for me.\n\n - Short description of error ---\nWhen I use pinch gesture to zoom in and out, it functions properly in the 3d workspace and the image/uv editor. However, when I try the same gesture in any other window, there is not a smooth transition and it will often cause blender to freeze for a few seconds. \n\nHere is a video that shows what I'm talking about. \nwatch?v=VvzI34wjB6s&feature=youtu.be\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nUse pinch zoom gesture in different windows and panels.%%%", "Continuous zoom fails to work in camera view \nosx 10.10.1 AMD Radeon HD 6750M 512Mb\n\n2.73 b4d8fb5\n\ncontinous zoom once in camera view ceases\n\n- head into 'user preferences' - input\n- under 'zoom style' change to continue \n- enter an active camera, zoom should return to dolly\n" ]

[ "Blender hangs on Intel UHD 620 when switching to lookdev mode\nOperating system: 'Windows-10-10.0.19044-SP0'\nGraphics card: Intel UHD 620\n\nBroken: 3.5.1\n\n\nBlender hangs on when switching to lookdev/render mode on even simple shaders.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open crasherexample.blend on an Intel UHD 620 (Dell Inspiron 3581)\n2. This will be in solid preview mode in Shading view.\n3. Switch to lookdev mode. Blender hangs (Task Manager shows high CPU percent usage on the process, which goes down to zero percentage after a few seconds, after which Blender refuses any interaction).\n4. Use Task Manager to kill Blender. Now restart Blender and reopen crasherexample.blend which will be in solid preview mode in Shading view.\n5. Use Node Wrangler right-click drag to cut the Normal, Roughness, Displacement noodles. Leave just Base color noodle.\n6. Switch to Lookdev mode. It works! Now reconnect Normal noodle too. Switch to Lookdev. It works! Now reconnect Roughness noodle too. Switch to Lookdev. It works! Now reconnect Displacement noodle too. Switch to Lookdev. It works! Yet if you immediately switch to lookdev mode as did in step 3, it hangs. \n\nResult is opening/importing just about any file in Blender causes a hang. Not just crashexample.blend. Nearly any shader however simple causes this. But crashexample.blend file works fine on non-Intel UHD 620 PCs.\n\nWe've been plagued by this bug ever since Blender 2.8. Tried every version of the driver (Dell and Intel), but none ever fixed it. Result is we can't safely switch to lookdev/render mode on these PCs. Tried investigating and suspect perhaps a race condition related to shader compilation. Loading a typical Blender file begins with a message like eg '(some number) shaders to compile', and it hangs.\n\nThis only happens in EEVEE. Cycles is fine.", "Assert in debug for dyntopo sculpt\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: Today main.\n\nSee attached stack trace file.\n\nIn debug:\n1. Sculp mode.\n2. Enable Dyntopo option.\n3. Do something.\nSee the crash.\n\n", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "Blender locks into Pose Mode if rig-object or the rig's collection is hidden\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.0.0\nWorked: 2.9 \n\nBlender locks into Pose Mode if rig-object or the rig's collection is hidden\n\nOpen Blender, add a rig.\nGo to pose mode, hide the rig object (toggle its viewport render or deactivate the collection the rig is in).\nBlender now stays in Pose-Mode unable to leave it without restoring rig visibility.\n\nIn 2.9 Blender automatically exits Pose mode in this scenario. (Desired behavior)\n", "(Grease pencil) Blender freezes indefinitely when drawing using stabilize stroke function. \nOperating system: Windows 10 business 64bit\nGraphics card: Intel UHD 620/630\n\nBroken: both 3.2.2 and the experimental build 3.4.0 alpha\n\n\nWhile drawing using the stabilize stroke function (in blank grease pencil object), after some times blender freezes and stop responding, tested on both an HP prodesk g5 ( I5 8500, intel IGP UHD 630 and 8 GB of RAM) and asus zenbook (I5 7200U, UHD 620, 8GB RAM).\n\nThis only happened on both PCs equipped with intel IGP, I redid the same test on my home PC (I5 9400f, GTX 1060, 16GB RAM) and everything worked fine.\n\nIs this purely a performance issue ?\n\nJust create a blank grease pencil object and directly start drawing using the stabilize stroke function, test setup must be similar or close to the two PCs equipped with Intel IGP.", "Transform: Snap to the visualized cage of the edited mesh\n## Motivation\nCurrently in editing mode the snap is always made on the values of the bmesh.\nBut intuitively the user tries to snap on the displayed cage which can be affected by the `On Cage` option.\n\n## Proposal\nUse `mesh_eval_final` or similar when the cage does not match bmesh.\nVertices and edges originating from modified faces can be ignored in snapping.", "Wrong status bar keymap for release confirms and right click select\nOperating system: Manjaro x64\nGraphics card: HD5770\n\nBroken:\n2.80, 81ea815dcb6, blender2.8, 2018-12-12\nWorked: 2.79b\n\nWhen grabbing something(object, vertex, etc) by right clicking on it and then releasing/clicking on the same button the action is not performed, object doesn't return to its initial position. \nHowever if you use G or a Tool to grab instead of mice click Cancel by Right clicking option works.\n\nRight click on a Cube(in 2.79 thats enough to start moving an object but not here here you have to hold the button) AND HOLD the button\nDrag mice somewhere to move the Cube\nRight Click again to Cancel movement\nNothing happens.\n[blender_bug-2018-12-13_22.18.53.mkv](blender_bug-2018-12-13_22.18.53.mkv)\nI'm also attaching video file for it to be more clear.", "soft body issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nWith some soft body basic setting sometine the object go crazy and disappear, with almost same setting sometime it work fine. \n\nMake a Suzane and a subsurf by 3 applied, make a plane for the floor and make it collision.\nMake Suzane softbody and uncheck the goal button. Make pull and push a hight value (9.5 for exemple) and a hight Bending value (like 9). Bake it and see what append, if it work just tweak a little bit the setting and sometime the scene go crazy (Suzane disappear at frame 2 or 3).\nIf I reduce the poly count (suzane with subsurf at 2) it append less but sometime the same thing append.\n\n\n", "Front Faces sometimes doesn't work with the Mask tool\nOperating system:\nGraphics card:\n\n3.5.0 beta 24/2/2023\n\n**lasso mask brush mask outside the border when symmetry enable**\n\nThe same as #103163 but in a more extreme case\n\n- Open attached .blend file\n- (optionally) Disable `X axis` mirror\n- Use Lasso or Box Mask tool in the region indicated\n\n[untitled.blend](https://projects.blender.orgattachment)\n", "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 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", "Blender 2.71 (rc2) crashes when a UV sphere is added\nMac OS X 10.10 (beta) / AMD Radeon HD 6750M 512 MB\n\nBroken: 2.71 (release candidate 2)\nWorked: -\n\nBlender 2.71 (rc2) crashes when a UV Sphere is added to a existent project in Edit Mode.\n\nUsing the attached file, select the figure (stickman), go to Edit Mode and add a UV Sphere. After executing these steps, Blender stops responding and it's necessary to force quit and reopen. \n\nIt seems that's something to do with the modifiers (in the attached file, I'm using Mirror, Skin and Sub-surf). One or more of them are causing the crash when the UV Sphere is added. If I create a new project with no modifiers, I'm able to add UV Sphere. \n", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "Expand face sets freeze blender when cursor is on mesh boundaries\nOperating system: Linux (Mint 21) \nGraphics card: RTX 3070 Ti\n\nBroken: 4.0.0 alpha, 12f51bd1c77b, master, 2023-09-21, as found on the splash screen)\nWorked: 3.6\n\nTry to create new face sets from first or last face loops on a cylinder.\nBut expand Face Set from boundaries is frozen in 4.0 alpha.\n\n\n- Open the blend file\n\n- Switch to Sculpt mode\n\n- Move your cursor outside boundaries and press Expand Face Set (Shift +W). (See on pictures)\n\nAt this point, Blender freeze, not crash. No more info in console.\n\nBug :\n\n\nExpected (3.6 version): \n\n\nThanks for your help.\n\n", "rigid body behaves incorrectly when there is a cloth simulation on a passive object\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1\n\nrigid body does not take into account cloth simulation, even if it is noted that the shape for collisions is a mesh after all modifiers\n[2022-07-19 22-53-31.mp4](2022-07-19_22-53-31.mp4)\n1. create an object with a rigid body\n2. create an object with cloth simulation and rigid body\n3. play simulation" ]

[ "Blender locks up almost instantly when starting to sculpt on a multires object.\nOS - Windows 10 64 bit; CPU - Third-gen i7; GPU - ATI HD 7xxx; RAM - 24 gigs\n\nBroken: Hash ede7429\nWorked: Hash 2d8db0d (May 8)\n\nSculpting on a multires object will cause Blender to lock up while applying a stroke (when using a very recent build). There's no crash, Blender just freezes indefinitely.\n\nOpen the .blend file and start sculpting on the object, Blender will lock up before you even finish the first stroke. The root cause of this may also be causing a bug where it's not possible to open a .blend file containing a multires object (Blender will lock up instead).\n\n**.blend**\n[Multires_lockup.blend](Multires_lockup.blend)\n", "Blender freezes in multi-threaded tasks since recent rB98123ae91680, on windows - atomic ops issue?\nWin 7x64, Nvidia GTX 580\n\nbroken: blender-2.77.0-git.b72aef9-AMD64\nWorking: blender-2.77.0-git.898d040-AMD64\n\nBlender freezes while trying to do vertex snapping with subdivision modifier enabled both in object and edit mode.\n\n1. Create Suzanne\n2. Add Subsurface modifier, duplicate mesh\n3. Try to manipulate meshes with vertex snapping enabled\n\nSometimes i can reproduce this instantly, sometime not, so try open attached file, it freezes all the time.\n[bug.blend](bug.blend)", "Raycast + subsurf freeze blender\nI7-5820K / Win7 family 64bits / gtx780\n\nBroken: 2.77 a83bc4f\nWorked: official 2.77\n[RayCastSubsurf.blend](RayCastSubsurf.blend)\nBlender freeze when using a raycast operator with a subdiv of += 4\n\nOpen the attached file, run the script (raycast template) with space \"Raycast ...\", click on the object, blender freeze.\n" ]

[ "Proportional editing lag\nWin7 x64, GTX 460\n\nBroken: 2.73, 2.74\nWorked: 2.63 \n\nWith proportional editing on, I get a few seconds freeze when activate translating (G); than after freeze, \neverything goes ok. I thought that the problem was a large mesh, but 2.63 works great and without lags in the same file. \n\nMy \"bugged\" file is the one, I am working with. If it is possible, can i sent it in private and not give it to the world here?\n\nThank you!", "Stereoscopic Display Mode (Side-by-Side, Top-Bottom): Mouse Cursor stays monoscopic\nWorked: Never\n\nWhen in Side-by-Side Stereoscopic Display Mode, the mouse cursor is just shown on the left side of the stereoscopic UI.\n\nEnable Side-by-Side Stereoscopic Display Mode:\n - “Properties Editor” → “Output Properties” → “Stereoscopy”: Checkmark\n - Title Bar → “Window” → “Set Stereo 3d”: “Side-by-Side”\n - Title Bar → “Window” → “Toggle Window Fullscreen”\n\n\n\n", "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", "Motion Pasths: \"Clear Motion Paths\" default to \"only selected\"\nProblem: \nAs with \"calculating\" motion paths you expect the clear motion paths function to default to the one selected, In the same way you create Keyframe the selected objects. The default deletes all motion paths in scene and wanting to clear one motion path is more common than wanting to clear them all.\n\nSolution:\nChanging the default of clear motion paths to \"clear motion path\" and turn \"Only Selected\" to default.", "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) ", "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?", "Fly and walk navigation in AZERTY issues\nOperating system: windows 10\nGraphics card: rtx 3060\n\nBroken: Blender 3.6.1 (Steam)\n\n\nHello,\nIm on a AZERTY keyboard and the problem is that when i change my movements keybinds for fly (or walk) navigation it keeps repeating the action (even if i unpress the key) for the binds that i changed. For exemple i changed \"forward\" key by Z and when i press Z the camera will keep going forward forever.\n\n- Go in the View 3d fly (or walk) modal keymap settings\n- In \"Forward\" replace W by Z, \"Left\" Q by A, \"Down\" A by Q, \"Z axis correction\" Z by W\n- Go in fly (or walk) navigation mode\n- Try to move with ZQSD, A and E\n- Then when you press S,D or E it will work normaly but if you press Z, Q or A and release the key it will keep going in that direction exept if you press the opposit direction key (S for Z, D for Q, E for A)\n\nThanks for paying attention, lov u <3\n\n", "Laucnh error since version 3.4\nOperating system: High Sierra 10.13.6\nGraphics card: ATI 6970M 2 GB RAM\n\nBroken: (example: 3.4 and 3.4.1 2022-12-20, master)\nWorked: (Blender 3.3.1)\n\nWhen I launch blender a get this error that I have found others on the web reporting also on similar setups:\nError opening window.\nFailed to create metal device for offscreen GHOST Context.\n \n\nPrevious versions worked a charm and I really hope 3.3.1 wont be the last version for my humble setup.\n\nThanks and as always appreciate your amazing work!", "Can't setting camera.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.19\n\nBroken: version: 3.6.1\n\n\nWhen I render, will jumpback to the camera.002\n\n", "UI: In Preferences, Invisible Execute Region in Nav_bar, blocks resize of area.\nBroken: 957b4547ae, 6b082278d1\nWorked: never?\n\nWhen you try to resize preferences, you grab the execute region edge instead(Only for nav_bar side).\nThe default state, has the area open but invisible. Blocking resize.\n\nSeparate preference window, does not have a problem.\n\n[2019-05-10 09-01-29.mkv](2019-05-10_09-01-29.mkv)", "Graph Editor - Multiple Windows Problem\nOperating system: Windows 10 - 64\nGraphics card: Radeon RX 5500 XT\n\nBroken: 2.93.0\n\nI split my single Blender window to two Graph Editor/Node Editor & 3D Viewport for my multiple screens. If my mouse hovering anything but node editor(Include Graph editor or 3D Viewport) and I press play that timeline cursor like starts twitching.\n\nCreate two different windows. Graph Editor and 3D Viewport. Than press play on 3D Viewport window selected.\n\nTest file:\n[Bugfile.blend](Bugfile.blend)\n\nVideo:\n[2021-06-10 15-35-41.mp4](2021-06-10_15-35-41.mp4)", "Brush cursor (sculpt, vertexpaint, weightpaint) stuck/doesn't draw under transparent part of N-panel\nBroken: 2.80 to 3.1 (and currently 3.2.0 alpha 4fa3eadce99a) (technically 2.79 as well, but back then region ovelap was drawn a bit diferently).\nWorked: Never\n\nTools brushes don't draw over the transparent property panel, even though Region Overlap is on.\n\n* Ctrl + N → Sculpting\n* N (to open the Properties region).\n* Move the mouse to the right, beyond the alignment line of the properties editor panels.\n\n\n\nThe brush drawing doesn't follow the mouse cursor. The tool itself works though, and the brush is even drawn if you click in that part.\n\n---\n\nVideo from the original report: [F8795403](2020-08-20_05-04-02.mp4)", "Space Mouse not working properly\nOperating system: Mac OS Ventura 13.3.1 (a)\nGraphics card: Apple M1 Max\n\nBroken: 3.5.0\nWorked: 3.0.0\n\nNo buttons of the Spacemouse work anymore.\nEverything worked with Blender 3.0.0 and 3D Connexion Driver 10.7.0.\n\n1. Install latest 3D Connexion Driver 10.8.0.\n2. Set up some buttons in 3DxWare 10 like:\n a. \"Button 1\" = Keystroke \"Tab\".\n b. \"Button 2\" = Keystroke \"1\".\n c. \"Button 3\" = Keystroke \"2\".\n3. Start Blender.\n4. Try to switch between Edit and Object mode with \"Button 1\":\n a. No Function.\n5. Try to switch between select Modes with \"Buttons 2-3\":\n a. No Function.\n6. Try to select more Objects with holding \"shift\" on Space Mouse:\n a. No Function.\n\nI miss the combination so hard, it's impossible to work without my space mouse, I'm used to it for a decade. :(\nThe Space Mouse works fine in all other Programms, its an Blender Issue exclusively.\n\nAdditional Infos:\nSometimes restarting Blender multiple Times, re-installing it, fixes temporary the function of the basic Keys \"shift, cmd, etc\". The other buttons never work. They worked always in the past and still work in all other programs where I use the mouse. ", "Intermittent: Control + MMB to zoom non responsive or sluggish vs mouse speed\nOperating system: MacOS Ventura 13.4.1\nGraphics card: M1\n\nBroken: 3.5.1, Hash: e1ccd9d4a1d3, Branch: blender-v3.5-release\n\nZoom via Control + MMB becomes very sluggish to the point where excessive movement of the mouse is required. Does not match the mouse pointer speed for the rest of the application. \n\nAny model in perspective mode. Attempt to zoom view to the object.\n\n", "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" ]

[ "Strange blender user interface bug where UI lags behind user input.\nWindows 7 64-bit\nAcer Aspire 5750G (i5-2450M - Intel HD Graphics 3000, NVIDIA GT 630M)\n\nBlender 2.75\nAlthough this bug is present in most (if not all) blender versions after 2.5. Unsure if it is present on blender versions before 2.5.\n\nThis is a bug in the updating of the user interface. When doing something in the viewport like selecting a vertex. The vertex will not be highlighted until another action is performed. Another example is when you press file on the info view. The file menu will not appear until you move the mouse cursor. It looks like the user interface is lagging behind by 1 step. Selecting different window draw methods in Preferences -> System does not help solve the problem. Please view attached video:\nwatch?v=zA4dkWD_Pnk\n\nNot sure how widespread this bug is. But if you have a laptop with windows vista or windows 7 (perhaps even window 8 and windows 10). With optimus technology with an NVIDIA card. The bug will occur if you disable windows AERO. This means you cannot use the Basic or Classic themes. This is also means that for users experiencing this bug, enabling AERO will circumvent the UI bug. \n\nIt is important for laptop users to be able to use blender with AERO disabled since AERO uses resources that could be allocated to blender. Having AERO disabled also allows other programs to interact with Blender properly. For instance screencasting with OBS.\n\n", "GUI/OpenGL display delay (one step behind Input)\nOperating system: Windows 7\nGraphics card: Intel (R) HD Graphics Family\n\nBroken: Blender 2.71 for Windows\n\nAs the title states, the graphics user interface output seems to be one step behind any kind of input. I'll give three examples of this, but it occurs for every kind of input I give the software.\n\nex 1) If I click on the \"file\" menu option, or any other menu option, It simply highlights and nothing happens. Click it a second time, it un-highlights and still nothing happens, but click it the third time, then it highlights and displays the drop down menu.\n\nex 2) When I hover my mouse over any of the buttons in the developer, they don't highlight, when I hover the mouse outside the bounding box of any button, it highlights for a brief moment and un-highlights again in a flash.\n\nex 3) When I zoom in on my mesh, I have to zoom in twice with my mouse for it to zoom once on the screen, then it zooms normally. When I zoom back out, it zooms in one more time before zooming out normally. If I scroll left, then zoom in, it scrolls left one more time before zooming in, etc.\n\nex 4) When I click on the parameters to change the numbers, I click it once and it highlights normally. Type a number, it remains highlighted and unchanged. Press the number again, then it shows up in the parameter entry box. Press enter, then I find that the number has been entered twice. If I press enter before it displays any edit, however, it displays the edit after pressing enter, but it shows the number highlighted as if I'm still typing in the box.\n\nStart up the program and use it for five seconds." ]

[ "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "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).", "Set Material Node does not reuse existing empty slot\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\n\n\nIf I set material with Set material node, it will not appear after remesh modifier.\nNo matter if i set material to initial instance or to final geometry after Realize node.\nHere the file for tests and demo\n[remesh after GN.blend](remesh_after_GN.blend)\n\n\n\n[2021-11-29_01-09-32.mp4](2021-11-29_01-09-32.mp4)\n\n[2021-11-29_01-13-43.mp4](2021-11-29_01-13-43.mp4)\n\n", "\"Ctrl+Scroll\" to pan horizontally cause issue inside geometry node editor \nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.93.0\n\n[ The two actions (Pan horizontally & change any float value of the parameters) are linked to same key combo (Ctrl+Scroll) inside geometry node editor which conflicts,]\n\n[1. Add cube and goto Geometry node editor\n2. add Transform or any node inside geometry node editor.\n3. Try to pan horizontally with Ctrl+scroll. As soon the node hit your mouse pointer while panning, the panning action will stop and it will change the slider value where the node hit the mouse pointer, this cause accidental change in value and other issue. either use Alt+scroll to pan. this same thing should be fundamental everywhere that Alt+scroll to change different tabs and Ctrl+scroll to change values, if possible.{[F10173799](Untitled.png)}]\n\n", "Normal map support in Cycles standalone\nWindows 8.1 64-bit\n\n**Cycles Version**\nd553b8de7180\n\n\nIn the latest version available in the Cycles standalone repository, commit d553b8de7180, using a normal map node in a shader graph will cause Cycles to crash. This behavior was not present in release 1.7.0 but has been added since then.\n\nThis looks to be caused by an improperly initialized member variable in the ccl::NormalMapNode type. Upon creating an object of type NormalMapNode, the ustring named 'attribute' is initialized such that attribute.c_str() will return a nullptr.\n\nCycles crashes when the nullptr used to construct a std::string in NormalMapNode::attributes in this bit:\n\n```\t\n\t\telse {\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent\").c_str()));\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent_sign\").c_str()));\n\t\t}\n```\n\n\nI have attached a simple cycles standalone scene that triggers this error here: [sample_scene.xml](sample_scene.xml)", "Geometry Node boolean input socket broken when recursive linked file is reloaded in the Outliner\nOperating system: Windows 10 19044.1645\nGraphics card: GeForce RTX 3070\n\nBroken: 3.6.1, 8bda729ef4dc, branch: blender-v3.6-release, 2023-07-17\nWorked: none\n\nGeometry Node with boolean group input socket will show error \"Property type does not match input socket (socket name)\" and the input socket will not get evaluated if the recursively linked source file is reloaded in the Outliner 'Blender File' view mode.\n\nBrief description of the file linking structure\n\"01_source_GN-bool-Input.blend\" is the blend file that contains the source geometry node.\n\n\"02_GN_linked_level1.blend\" linked the \"01_source_GN-bool-Input.blend\" geometry node and using it on a local object.\n\n\"03_GN_linked_level2.blend\" linked \"02_GN_linked_level1.blend\" \"GN Cube\" object.\n\nTested with Integer input socket, works as expected in the above file linking condition.\n\n1. Open the attached blend file \"03_GN_linked_level2.blend\"\n2. In the Outliner 'Blender File' view mode (on the middle right of the UI from file), right click on the file \"//02_GN_linked_level1.blend\" and click \"Reload\"\n3. Noticed that the boolean input 'Switch' checkbox is now showing error \"Property type does not match input socket \"(Switch)\"\"\n\n", "Retopology: Active Object Geometry gets Occluded by Semi-Transparent Reference Object in Edit Mode\nOperating system: Linux Ubuntu 16.04\nGraphics card: Nvidia GeForce MX130\n\nBroken: 2.83.0\nWorked: 2.82.a\n\nActive mesh is occluded by high poly or another reference mesh in Edit mode. This is: I want to edit mesh A. I need mesh B to get a reference. So I make B to have a semi-transparent material for Viewport view. I select A and go to Edit mode to edit it. However, its edges and vertexes are occluded by B. We can see a comparison of 2.83.0 (first image) with 2.82a (second image): version: 2.83.0 does not show active object geometry so that we can not edit it. On the other hand 2.82a does show required geometry.\n\n \n\n1. Open Blender 2.83.0\n2. Create a Sphere mesh in the world origin so that it fits inside the default cube.\n3. Assign a semi-transparent viewport display material to the Cube so that we can see the Sphere inside. Change color also to have a better view.\n4. Select Sphere and go to Edit mode.\n5. Press A to select all vertexes.\n6. We can see that Edges and Vertexes are occluded by the Cube so that we can not edit the Sphere properly.\n\n\n[bug-report.blend](bug-report.blend)\n", "Nodes: Reroute node disappear when pressing `Ctrl H`\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: Never.\n\nIf the reroute is not connected to anything, then pressing `Ctrl + H` will make the reroute invisible.\n\n\n1. Add reroute in nodetree using `Shift + A`.\n2. Press `Ctrl + H`.\n\n", "Viewport shading solid mode not displaying geometry nodes color attributes correctly\nOperating system: Win10\nGraphics card: 960m\n\nBroken: 3.5\nWorked: never\n\n\nWhen using geometry nodes to add color attributes, there are several situations where the viewport solid mode attribute option does not display the color attributes correctly.\n\nAs can be seen by this example. The first image shows a cube with a color attribute added. The geometry nodes setup adds a red color to the \"Color\" attribute. This all works as expected as can be seen in the viewport and the spreadsheet. \n\n\n\nIf a GN cube is added instead of the standard mesh cube (which has been bypassed by the switch node) then the color attribute is added as expected. This can be seen in the spreadsheet as to be the same as the previous screenshot for the color attribute. However, it is not being displayed in the viewport.\n\n\n\nThis is a problem seen with any procedural geometry made with just nodes. As a workaround, you can have a single vertex as the only \"real\" geometry and use a join node to join with any nodal procedural geometry. Strangely though, this has to be the first connection in the join node, and won't work if it is second. This can be seen by the next 2 images:\n\n\n\n\n\nA similar related case is that some mesh nodes will also make the viewport lose the displayed attribute. For instance, if you create a cube, add a GN modifier and add a dual mesh node to the chain, the color attribute is still there, but no longer displayed in the viewport. This happens with some nodes (like mesh to volume and back to mesh) but not others (like subdivide or extrude).\n\n\n\nThere is also a related issue that when exporting to obj or gltf the color attributes are not exported if they are not displayed in the viewport. If apply the GN modfier, you have to actually click on the color attribute in the properties panel to see it in the viewport or to be able to export it. \n\nOddly, the fbx exporter seems fine without applying the modifier. It also doesn't matter if the color attribute is on the vertices, or face corners, or if the color is float or byte color. The same issues happen regardless.\n\n", "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", "Moving reroute nodes with click-drag behaves unpredictably\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.1.0 Alpha\n\nThe recent builds of Blender 3.1 add an option to finally move reroute nodes with mouse only, like any other node types. Unfortunately, there is no pre-selection highlight to let the user know which action they are about to perform on click-drag action. According to the anti-features page, pre-selection highlight section, if such feature does not behave reliably and predictably, it should be reported as a bug: AntiFeatures \n\nThis is why I am reporting it as such.\n\n[2022-01-24 11-25-05.mp4](2022-01-24_11-25-05.mp4)\n\nCurrent implementation suffers from following issues:\n1. The circular area/radius where move operation occurs is not visible. It is not visible how far from the reroute node position the node can still be transformed.\n2. Click dragging slightly outside the reroute node circle will still result in node wire drag rather than transform, further adding to the confusing behavior.\n3. It is not obvious that the click-drag transforms works **only** when the reroute node is selected first, which is inconsistent with click-drag transform behavior of the other nodes.\n\n1. Add a reroute node to any node graph\n2. Select the reroute node\n3. Click-drag around near the reroute node in various distances\nResult: What happens when LMB click dragging near the reroute node is not reliably predictable\nExpected: Outcome of LMB click-drag input operation near a selected reroute node can be reliably predicted\n\nProposed solution:\nWhen the reroute node is selected, and therefore can be transformed, draw a simple transform gizmo representing the screen area, which results in the transform operation when click-dragged, but only for reroute node closest to the mouse cursor, and only when the mouse cursor is near it (the same the scrollbars are dynamically drawn only in the close proximity of the mouse cursor):\n", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "Point Clouds only support one material\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken version: Current main.\nWorked: Never\n\nWhen using the `Join Geometry` node in Geometry nodes to join two points together, their material is reset to default. This only happens when joining two or more \"lone\" points.\n\n1. Recreate the geometry node setup found in the image below\n2. Change the render engine Cycles (necessary to see points with a material)\n3. Render the scene.\n4. Notice that the materials you assigned to the points are not applied.\n\nI have also included a .blend file with steps 1 and 2 done.\n[Missing Material - Join Geometry.blend](attachment)\n\n\n", "Joining meshes or realizing instances in geometry nodes removes custom normals data\nOperating system: macOS Big Sur 11.5.2\nGraphics card: Apple M1\n\nBroken: 2.93 and 3.0 Alpha\n\n\nUsing the collection info node in geometry nodes destroys custom normals data when the geometry node modifier is applied (or when the project is exported).\n\n\nApply the geometry node modifier on the \"Dummy\" object in the attached blender project. I've also included a video that shows the issue.[collection_info_test.blend](collection_info_test.blend)\n\n[collection_info_bug.mov](collection_info_bug.mov)", "Support geometry node in glTF exporter\nThis should be possible when API will manage it.\nCurrent code used by glTF exporter:\n\n```\ndepsgraph = bpy.context.evaluated_depsgraph_get()\nblender_mesh_owner = blender_object.evaluated_get(depsgraph)\nblender_mesh = blender_mesh_owner.to_mesh(preserve_all_data_layers=True, depsgraph=depsgraph)\n```" ]

[ "Reroute points change types randomly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 2.93.0 Beta\nWorked: no\n\nMultiple reroute points cause the types of them to change randomly, this happens to both shader editor and geometry nodes\n\nBased on the default startup\n1. Click on either the Shader workspace or Geometry Nodes workspace, in my screenshots it will be the shader editor\n2. Shift right click drag to create two reroute points, so far so good\n\n3. Let's create a third one\n\nOops\n4. Create more and see how the yellow socket shifts between them\n\n\n5. Ctrl Z undo and see how it reacts randomly\n\nNow they are all green but the line is still red\n6. Create some more and click drag a line from the yellow point, then let go\n\n\nAfter you let go, the yellow socket shifts again" ]

[ "Viewport switches needlessly to perspective mode, when changing from camera-view to local-view // Auto perspective is turned OFF.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0\n\nWhen in camera-view and hitting Numpad Dash to get into local view of selected object, the 3D-Viewport ALWAYS goes into perspective mode needlessly. **Auto-perspective is turned off.**\n\n\n- Open attached .blend file.\n- Cube is already selected.\n- Camera-view **(Numpad 0**) is also already set\n- Hit **Numpad Dash** to go to local view of selected Cube. (**3D-Viewport is now in perspective mode.**)\n[Perspective.blend](Perspective.blend).\n\n\n\n**To further add to the unnecessary switch of view-mode:**\nWhile in perspective local view of the cube as described above, hit **Numpad 5** to switch to orthographic view.\nNow tab**Numpad 0** to go back to camera-view.\nHit **Numpad Dash** again to go to local-view of the cube again.\nOnce again, you are needlessly in perspective mode.\n\nThanks for any fix on this issue.", "Sclupt brush goes back to default (draw) when pressing ctrl+z\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.1\nWorked: 2.90.0\n\nSclupt brush goes back to default (to \"draw brush\") when pressing ctrl+z.\n\n1 - Load default startup.\n2 - Select a cube.\n3 - Go to sculpt mode.\n4 - Pick any brush (I recommend \"grab brush\").\n5 - Manipulate the geometry of the cube a few times.\n6 - Press ctrl+z.\n7 - You will see that the brush jumps back to \"Draw brush\" for no reason.\n", "Color Filter: Sliding UI\n# Issue\n\nCurrently when using using the Filter tools in Sculpt Mode, like the Color, Mesh or Cloth Filter, to start the operation you need to click anywhere in the viewport.\nClick and drag from left to right will have a positive effect and from right to left the inverse effect.\n\nThe exact behaviour is very hard to understand and no information on the actual strength is given in the UI.\nSo we should add a UI element to give additional information.\n\n# Solution\n\nLuckily [D9314](D9314) and [D9054](D9054) already implemented such a UI element and modal keymap that could be reused for the Filters.\nSo when executing a Filter it should display a scale in the header to know how strong or inverted the effect currently is.\nUnlike with the Pose Mode Breakdowner the slider should start at the 0 % mark.\nThe shortcuts `E` for overshoot, `Ctrl` for increments and `Shift` for precision should also be included.\n\nThe capped 100% and -100% points will have to be tested so as a user it is rarely necessary to press `E` to overshoot the range.", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "Ability to cancel viewport operations (rotate/pan/zoom)\nSince most transforming view-port operations can be cancelled, it would be useful if viewport operations such as rotate/pan/zoom could be cancelled by pressing Escape. [See request ](showthread.php?392619-Call-for-Quick-Hack-ideas-(for-beginner-students-to-complate-in-a-day)&p=3010312&viewfull=1#post3010312).\n\nWhile not high priority, this is nice to support for consistency with other parts of Blender.", "3D Paint Mode stencil disappears when panning viewport.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.4\n\nWhen panning viewport in 3D paint mode with stencil mask enabled, the stencil mask disappears when moving the viewport, however does not disappear when zooming it, which indicates it's not a technical limitation.\n\n1. Enter 3D paint mode\n2. Enable texture mask, select some texture and set mapping to stencil\n3. Navigate the viewport\nResult: The stencil disappears when moving the viewport, which makes it very difficult to line up stencil projection with the 3D geometry\nExpected: The stencil does not disappear when navigating the view\n\n", "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", "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)", "No visible mesh on Viewport Screenshot in sculpt mode with Multires\nOperating system: Linux-6.2.11-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.36 64 Bits, X11 UI\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhat the title says.\n\n- Add a cube\n- Enter sculpt mode\n- Add a multiresolution modifier and subdivide\n- Use the operator: Header -> View -> \"Viewport Render Image\"\n\n", "Bug while moving vertices with mirror & subdivision modifier\nOperating system: Windows 10 64-bit\nGraphics card: ATI Radeon HD 5670\n\nBroken: 2.82\nWorked: at least 2.8\n\nWhen I try to move a vertice it seems like the mirror modifier gets applied in an odd way. The result even changes when moving the camera or hide one of the images I use for reference. In fact it becomes distorted when hiding the images.\nThe following link is a recording of my screen:\nview?usp=sharing\nI encountered this bug only recently. The file itself is older and I do not remember which version I used (since I use it via Steam I did not pay attention to the automatic patches).\n\n1. Open this file [Bugged Project.blend](Bugged_Project.blend)\n2. Disable visibility of Subdivision modifier for Edit Mode (which should already cause the bug)\n3. Move a vertice\n\n[system-info.txt](system-info.txt)", "Nodes: Different mouse drag effect for float properties\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.5.0 Alpha\n\nDrag step inconsistent of float data type that between of geometry nodes in modifier and editor.\nAnd float of vector also.\nThis caused the mouse to drag far to reach the maximum value when going from 0-100.\n\n\n[drag_step.blend](drag_step.blend)\n\n", "Support Viewport roll - around the cursor position\nCurrently view orbit supports zoom-to-mouse-position as a way to rotate and zoom around the cursor position.\n\nView roll however always uses the view center.\n\nWhile low priority, this would be nice to support. See: #70761 (Roll View ignores Auto Depth)", "Grease pencil edit mode proportional edit \"connected\" bug\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nProportional edited vertices from a mesh behave different when editing in \"only connected\" than GP points do. Mesh points (vertices) calculate the influence by the length of the path, while GP strokes react as soon as they get into the influence circle.\nTheleft rectangle in the picture is a mesh, the rectangle on the right is a grease pencil object. Notice how the points react differently.\n\n\n\n[ProportE.bug.blend](ProportE.bug.blend)", "Cursor warping not supported on Remote Session\nOperating system: Linux-3.10.0-1160.59.1.el7.x86_64-x86_64-with-glibc2.17 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.2\nNever worked on previous Blender Version as far as I am aware\n\nMouse wrapping (seem in `Walk Navigation` for example) in Remote Sessions is unusable.\nAs Unreal had a similar issue that was fixed, I was wondering if that was something that could be fixed for Blender as well.\nIt happens both on Linux and Windows.\n\nInfo from the Remote tech used and possible issue:\nrelative_mouse_support/\nInfo on Unreal Problem and Solution:\n141157\n\n- Under a Remote session, go to View > Navigation > Walk Navigation to activate the tool.\n- panning and tilting around,\nthe camera will lag a lot and get out of control by over-panning/tilting\n\nThanks a lot :)\n\n", "Transform & Drag Action \nWhen switching the transform tools in the toolbar, there are times when you would still like to be able to box select while gizmos are active.\n\nWe can solve this by adding a Drag Action tool option to all the transform tools:\n\n\n\nWhen set to Box Select, you can still drag in the viewport to select, while using the gizmo to move, rotate or scale.\n\nDetails:\n - This option should ideally be shared between all tools with gizmos, I think. If you set one tool to work this way, you likely want them all to\n - This works best if we add back the Transform tool\n\n" ]

[ "Using Viewport Navigation Gizmos can execute tool gizmos or sculpting\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.91.0 Alpha\nWorked: never worke in 2.8+\n\nLeft Mouse dragging on those two buttons can lead to unexpected/undesired behavior. \n\nThe dragging executes whatever tool is currently active:\n- if the selection tool is active, a selection is drawn\n- if the move tool is active and an object selected, the object is moved\netc.\n\nWhy this is a problem:\nIf one of these two buttons get accidentally dragged a little, it can apply a tiny yet destructive change to your scene which isn't noticed at first (as this behavior is unexpected).\n\n\n\nThis example is for the move tool:\n1. Open a new scene\n2. Activate the move tool\n3. Select the cube\n\n4. Drag the camera or perspective button to the side\n5. See how the cube is moved\n\n\n\nThis example is for sculpting:\n1. Open new sculpting scene\n\n2. Drag the camera or perspective button to the side\n3. See how the mesh gets distorted\n\n\nThanks\n" ]

[ "Cycles HIP device crash on rendering on latest AMD Adrenaline Driver\nOperating system: Windows 11 Pro for Workstation\nGraphics card: AMD Radeon RX 6750XT (Driver: AMD Adrenaline 23.7.1, 23.7.2 23.8.1 23.9.1)\n\nBroken: 3.6.1 LTS (On latest driver)\nWorked: 3.6.1 LTS (On old driver: AMD Adrenaline 23.5.2)\n\nAfter synchronizing objects, Blender crash\nBut render the default cube scene Blender works well even using 23.7.1 driver\n\nBased on the default startup or an attached .blend file (as simple as possible).\nScene is from Blender official demo file: \nbarbershop_interior/\nCrash log file: \n\n", "blender 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", "Pack UV's crashes blender\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\n\n", "Multiresolution - Crash when Linear Subdivision level is above 1\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.91.0\nWorked: Never? (2.90 and 2.92 dailies seem to crash on this one as well)\nWhen using multiresolution modifier on this part of my model and using linear subdivision level above 1, Blender crashes.\nThis does not happen with other subdivision methods, as shown in video.\nI've also tried to make this mesh manifold, but Blender crashed either way.\n\n\n1. Open attached Blend file\n2. Add multiresolution modifier to a mesh\n3. Press on \"linear\" button twice\n\n[Crash_SampleFile.blend](Crash_SampleFile.blend)\n\n[MultiresCrash0001-2375.mp4](MultiresCrash0001-2375.mp4)\n\n", "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 after executing the script\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.1 Release Candidate\n\nApplication crashes when clicking on the script run button\n\n1/ launch Blender\n2/ click on \"Scripting\" tab; click \"New\"\n3/ paste the following chatgpt generated script and run it: \n```\nimport bpy\nfrom math import sqrt, sin, cos\n\n# Define the vertices of the tetrahedrons\nvertices1 = [\n (1, 1, 1),\n (-1, -1, 1),\n (-1, 1, -1),\n (1, -1, -1)\n]\n\nvertices2 = [\n (1, -1, -1),\n (-1, 1, -1),\n (-1, -1, 1),\n (1, 1, 1)\n]\n\n# Define the faces of the tetrahedrons\nfaces1 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\nfaces2 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\n# Create new meshes and objects\nmesh1 = bpy.data.meshes.new(\"Tetrahedron1\")\nobj1 = bpy.data.objects.new(\"Tetrahedron1\", mesh1)\n\nmesh2 = bpy.data.meshes.new(\"Tetrahedron2\")\nobj2 = bpy.data.objects.new(\"Tetrahedron2\", mesh2)\n\n# Set the object locations and scene context\nobj1.location = (-2, 0, 0)\nbpy.context.scene.collection.objects.link(obj1)\n\nobj2.location = (2, 0, 0)\nbpy.context.scene.collection.objects.link(obj2)\n\n# Create the vertices and faces of the meshes\nmesh1.from_pydata(vertices1, [], faces1)\nmesh1.update(calc_edges=True)\n\nmesh2.from_pydata(vertices2, [], faces2)\nmesh2.update(calc_edges=True)\n\n# Hinge the tetrahedrons together by one edge\nedge1 = mesh1.edges[0]\nedge2 = mesh2.edges[2]\n\nbpy.ops.object.select_all(action='DESELECT')\nobj1.select_set(True)\nobj2.select_set(True)\n\nbpy.context.view_layer.objects.active = obj2\nbpy.ops.object.mode_set(mode='EDIT')\nbpy.ops.mesh.select_all(action='DESELECT')\nedge2.select = True\nbpy.ops.mesh.edge_face_add()\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Add an armature to the tetrahedrons\nbpy.ops.object.armature_add()\narmature = bpy.context.object\narmature.name = \"HingeArmature\"\narmature.location = (0, 0, 0)\n\n# Add bones to the armature\nbpy.ops.object.mode_set(mode='EDIT')\nbone1 = armature.data.edit_bones.new('Bone1')\nbone1.head = (0, 0, 0)\nbone1.tail = (-2, 0, 0)\nbone1.use_deform = False\n\nbone2 = armature.data.edit_bones.new('Bone2')\nbone2.head = (0, 0, 0)\nbone2.tail = (2, 0, 0)\nbone2.use_deform = False\n\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Parent the tetrahedrons to the armature\nobj1.parent = armature\nobj1.parent_type = 'BONE'\nobj1.parent_bone = 'Bone1'\n\nobj2.parent = armature\nobj2.parent_type = 'BONE'\nobj2.parent_bone = 'Bone2'\n\n# Animate the hinge\nframes = 30\n\nfor frame in range(frames):\n bpy.context.scene.frame_set(frame)\n\n angle = frame / frames * 2 * 3.14159265\n\n bone1.tail = (-2 * cos(angle), 0, -2 * sin(angle))\n bone2.tail = (2 * cos(angle), 0, 2 * sin(angle))\n\n bone1.keyframe_insert(data_path='tail')\n bone2.keyframe_insert(data_path='tail')\n```", "Blender crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Batch Rendering Crashes if EEVEE set in scene\nOperating system: Windows 10\nGraphics card: Any or None\n\n2,83, 2,90, 2.92\n\nEEVEE is set as renderer in the scene file.\nThe scene is send to the render farm. \nOpenGL is not available as render farm is running as background service OR blades machines do not have any GPU at all.\nBlender in Commandline Crashes.\n\n(Side Note: Cycles works fine as CUDA is available within background service)\n\n\n**Expected Behavior**\nReport an error \"EEVEE requires OpenGL. Unable to find/initialize openGL32.dll\"\n\nTo reproduce the issue, you either need some helper service that starts Blender in commandline mode (I can provide one) OR you can use any machine that does not have a GPU installed.\nCreate a new scene with EEVEE as renderer.\nTry to commandline-render the scene.\n\nCommandline that we used:\n\"C:\\renderer_exe\\blender\\win_x64\\Blender_2.90\\blender.exe\" -b \"\\\\isilonai\\woodspeople\\Boar (With fur).blend\" -o \"\\\\isilonai\\woodspeople\\Boar (With fur)\\Brawler####\" -F PNG -x 1 -s 10 -e 10 -j 1 -t 24 -a -y\n\n\nCommandline output:\nR 6| >\"C:\\RR_localdata\\renderer_exe\\blender\\win_x64\\Blender_2.92\\blender.exe\" -b \"C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\" -o \"C:\\RR_localdata\\renderout\\A\\3D\\Blender\\render\\myOut####\" -F PNG -x 1 -s 2 -e 3 -j 1 -t 24 -a -y \nR 7| Blender 2.92.0 Alpha (hash 719bea0d6d06 built 2021-01-12 23:10:47)\nR 8| Read blend: C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\nR 9| Writing: C:\\RR_localdata\\temp\\A\\cube.crash.txt\nR 10| StdErr: Warning! Using result of ChoosePixelFormat.\nR 11| StdErr: Warning! Using result of ChoosePixelFormat.\nR 12| StdErr: Warning! Using result of ChoosePixelFormat.\nR 13| StdErr: Warning! Using result of ChoosePixelFormat.\nR 14| StdErr: Warning! Using result of ChoosePixelFormat.\nR 15| StdErr: Warning! Using result of ChoosePixelFormat.\nR 16| StdErr: Warning! Using result of ChoosePixelFormat.\nR 17| StdErr: Warning! Using result of ChoosePixelFormat.\nR 18| StdErr: Warning! Using result of ChoosePixelFormat.\nR 19| StdErr: Warning! Using result of ChoosePixelFormat.\nR 20| StdErr: Warning! Using result of ChoosePixelFormat.\nR 21| StdErr: Warning! Using result of ChoosePixelFormat.\nR 22| StdErr: Warning! Using result of ChoosePixelFormat.\nR 23| StdErr: Warning! Using result of ChoosePixelFormat.\nR 24| StdErr: Win32 Error# (127): The specified procedure could not be found.\nR 25| StdErr: Error : EXCEPTION_ACCESS_VIOLATION\nR 26| StdErr: Address : 0x00007FFF8DBA1C81\nR 27| StdErr: Module : VCRUNTIME140.dll\nR 28| StdErr: Thread : 00001c94\n[Boar.crash.txt](Boar.crash.txt)\n\n\n", "Blender crashes when calling ArgumentParser.parse_args() if sys.argv is anything other than [\"path/to/blender.exe\"]\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.1\n\nBlender crashes when calling `ArgumentParser.parse_args()` if `sys.argv` is anything other than `[\"path/to/blender.exe\"]`\nI discovered this bug while trying to run a script using the `exec()` function. Any script that uses argparse makes blender crash.\n\nYou can run this code\n```Py\nimport argparse\nimport sys\nimport bpy\n\nsys.argv = [bpy.app.binary_path]\nsys.argv.append(\"--some_arg\") # Comment this line and everything works fine\n\nparser = argparse.ArgumentParser()\nargs = parser.parse_args()\n```\n\n", "Blender crash on combining textures (intel)\nOperating system: Windows 10\nGraphics card: Intel HD Graphics 4400\n\nBroken: 2.93.2\nWorked:\n\nWhen I tried to combine 2 textures like this blender is crashing.\n  \n\n[Test.blend](Test.blend)\n[Test.blend1](Test.blend1)\n[system-info.txt](system-info.txt)\n[Test.crash.txt](Test.crash.txt)\n[2021-11-12 09-11-32.mp4](2021-11-12_09-11-32.mp4)\n", "Blender 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", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "Decals crash Eevee on AMD graphics card\nOperating system: Linux 6.2.7 Manjaro \nGraphics card: AMD 7900XT\n\nBroken: 3.3LTS, 3.4.1\n\nUsing decals will crash blender in Eevee. cycles works\n\nas an example file please see the .blend that was linked here by the decalmachine creator: 66438\n\nThe issue there is unrelated but the file can serve to show the issue I am having. The moment I switch to rendered view or materials preview blender will crash. I see no error message in console. The log files states just: \n\n```\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.space_data.context = 'RENDER' # Property\nbpy.context.scene.render.engine = 'BLENDER_EEVEE' # Property\n \n```\n\n", "Blender 2.90.1 crashes after rendering the first few frames of animation.\n**System Information** \nOperating system: windows 10 64 bit\nGraphics card: Nvidia GeForce GTX 1650\n\nBroken: (2.90.1 3e85bb34d0d7; master)\nWorked(didn't): (only tried on 2.8.3 and did not work at all)\n\nWhen I try to render the animation, after about 50 or so frames(varies randomly), blender crashes with no alerts or anything that tells me what the error is, it simply closes.\nI've rendered another project, and that did indeed render, so I'm left confused why this short animation would cause a crash.\n\nEdit: I disabled motion blur, and it rendered fine. However, I would really like to know why blender won't render if motion blur is enabled. The renderer is Eevee and while my laptop isn't a super computer, it should be able to handle it. Thank you all in advance!\n\n- Open attached file\n- render the animation\n[cube-loop-tut-V1.0.blend](cube-loop-tut-V1.0.blend)" ]

[ "Blender won't open anymore.\n1326c9465d3c2aead8fd1a8e0e773e22\n\nBroken: Blender 2.69 AND 2.70 \nWorked: both worked\n\nI've downloaded yesterday the newest driver for my GT529 Nvdia Geforce and after that the consolewindow told me Reading now userprefs. but nothing else happend. so i deleted all blender files and also the userprefs.blend than i downloaded my older driver again and unpacked the blender version 2.70 again. but now the console window stays blank. and blender is still not opening. ( i've plugged in Avastar ( new: for Blender 2.70 we provide Avastar-1.1 RC(*) ) by avastar/ ) but it did work perfectly untill yesterday. \n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n", "Error Opening Blender\n**Windows 7 Home Premium\nIntel(R) HD Graphics**Operating system and graphics card**Blender Version**Broken: (2.71)**When i try to load Blender up the command screen appears for a few seconds then says something about writing temp files then disappears and nothing else loads after that.**\n\n**Opening Blender Application**\n\n", "Blender refuses to start\nWindows 7, Nvidia Geforce GTX 660M\n\n2.7.1.0\n\n\nWhen I click on Blender the program doesn't start.\n\nI get an error saying \"Blender has stopped working\" and the following is in problem details: \n\n\"Problem signature:\n```\nProblem Event Name:\tAPPCRASH\nApplication Name:\tblender.exe\nApplication Version:\t2.7.1.0\nApplication Timestamp:\t53ab4087\nFault Module Name:\tMSVCR120.dll\nFault Module Version:\t12.0.21005.1\nFault Module Timestamp:\t524f7ce6\nException Code:\t40000015\nException Offset:\t000a7676\nOS Version:\t6.1.7601.2.1.0.768.3\nLocale ID:\t1033\nAdditional Information 1:\t9247\nAdditional Information 2:\t92475ba88a5179decb56fdf16644d67d\nAdditional Information 3:\tc75b\nAdditional Information 4:\tc75b28280e5be7f54359dc58e7665ab3\"\n```\n\nI realize others have reported similar problems but I haven't found a good solution on the forums. I tried re-downloading the Microsoft C++ redistributable (MSVCR120.dll) and copying it into the blender install folder but this doesn't help.\n\nAny help is appreciated! \n\nThanks so much!\n\n", "Blender 2.71 64 dont start!!!!\nHello everubody! maybe (I think) I use card Firepro?\nWhen I try to run crash and Give me this error:\n\nProblem signature:\n```\nProblem Event Name:\tAPPCRASH\nApplication Name:\tblender.exe\nApplication Version:\t2.7.1.0\nApplication Timestamp:\t53ab381a\nFault Module Name:\tblender.exe\nFault Module Version:\t2.7.1.0\nFault Module Timestamp:\t53ab381a\nException Code:\tc000001d\nException Offset:\t0000000001f382e1\nOS Version:\t6.1.7600.2.0.0.256.48\nLocale ID:\t1033\nAdditional Information 1:\tbca9\nAdditional Information 2:\tbca970da058e36b3a1372e890300089c\nAdditional Information 3:\t71e3\nAdditional Information 4:\t71e3263276bdf650686718295aed3d97" ]

[ "error in custom view3d.move Keymap Setting\nOperating system: Windows11\nGraphics card: It doesn't matter\n\nBroken: up to 3.5.1\n\n\n\nBecause I often use the 2D features in Blender, and the pan view function in Blender is not very convenient (requires using Shift + MMB), I made the settings as shown in the picture to add a new pan view keymap to Spacebar + LMB. In the normal object mode, I can indeed pan the view by using the new shortcut, but once I switch to any other mode, this shortcut key will be disabled. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "View -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes.\nOperating system: Manjaro Linux\nGraphics card: nVidia\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nView -> Lock Time to Other Windows does not maintain scale when CTRL+TAB between two animation editor modes. \n\nExpand open the Timeline editor, now adjust the horizontal scale of the view (squeeze or expand), then Ctrl+TAB to swith to Graph Editor mode. Notice the scale does not stay in sych as it does when they are separate windows. ", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Cursor jumping to edge of screen when lifting pen from tablet area (wintab)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93\n\nTablet model: Huion h950p\nTablet api: Wintab\n\nWhen lifting the pen away from the tablet area, the cursor occasionally jumps to the edge of the screen, causing unexpected camera jumps or preventing hotkeys from being used in the 3d view.\n\nThe problem only happens with the Wintab api.\n\n\n - Set the tablet api to Wintab\n\n - Start creasing some edges and repeatedly lift and return the pen to the tablet area\n\n[cursorjump.mp4](cursorjump.mp4)\n\n", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)", "\"View\" settings not refreshing when going out of camera view\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.80 (sub 74)\n\nNot a big bug, but I'm reporting anyway.\n - Open file:\n[viewport_camera_settings_bug.blend](viewport_camera_settings_bug.blend)\n - Use middle mouse button to go out of camera view. Simple click should be enough.\n - Some of the settings in \"View\" will be greyed out until hovered over with mouse cursor:\n\n\n", "Viewroll doesn't respect QuadView's 'Lock Rotation'\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\n\nA bit of an inconsistency.\n\n- In the viewport, press Ctrl + Alt + Q to enter Quad view.\n- In one of the axis aligned views, F3 Search -> View Roll.\n- The view rolls even though \"Lock Rotation\" is enabled in the side panel.", "Change UV Channels from the UV Editor on multiple selected objects\nWhen multiple objects are selected and user is in edit mode in the 3d viewport, she/he can change uv channel of the**active object** in the top right corner in the UV Editor. It would be a nice change to **iterate through each selected object**and if the iterated object has a uv channel with the current name in the UI, that uv channel will be made active on the iterated object.\n\n", "Rendering large scene causes viewport shading rendered to go out of memory\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\n\nwhen dealing with large files and scenes in Cuda or optix, rendering the scene then stopping and closing the render, causes the viewport shading rendered view to give out of memory when switch back to it, it renders normally before hitting F12, after hitting render and everything compile and render, when closing the rendered and switching back to viewport rendered view it gives out of memory and its stuck with it and I need to restart blender to make the viewport render work again.\n\nseems it keeps the memory full even after I close the render so there is no memory for viewport I have no idea (I'm not a programmer :D) \n\nWorks normally in 3.4.1\n\nThank you\n\n- Open large files (like view?usp=sharing)\n- set Cycles Render to Cuda or Optix\n- Press F12 to Render and ESC to cancel\n- Close render window\n- Set viewport shading to rendered\n\nSee \"out of memory\" issue\n\n", "\"Align Active Camera to View\" doesn't match properly\nOperating system: windows 10 21h2\nGraphics card: gtx 1070 ti\n\n3.1.2\n\n\"Align Active Camera to View\" doesn't match to the active and wanted 3D view boundaries and the object distance properly. See the attachments below. \n\n \n\nThe steps for this: hit the \"Align Active Camera to view\" button in the \"View -> Align view\" menu in the 3D viewport, from where you want to achieve the desirable and proper view result, this result will be the same as I wrote in the short description. Which is very disturbing, mainly if someone came from eg. Maya or C4D to Blender. This is my blend file: [camera align problem.7z](camera_align_problem.7z)\n\nPlease correct this disturbing snapping malfunction in the near future! I would really appreciate that!\n\nThank you!", "Opening preferences while rendering causes rendering not to be finished (but computing continues)\nOperating system: W10\nGraphics card: 980Ti\n\nBroken: 2.80 19-03-31\nWorked: (optional)\n\nWhile rendering in a separate window, you can go back to main window, open preferences and boom, preferences are opened in the render window. You can see the progress bar on windows taskbar still going on, everything is being computed, but you are not going to get the full image. You can open the Rendering tab and see your render as 'finished' even though it's still computing. After it finishes - it does not update the image. It's in the state from the moment of opening settings.\n\n1. Click F11 to open rendering window\n2. Start rendering\n3. Minimize/switch windows to the main blender window\n4. Open preferences from the menu\n5. No profit, see desciption.", "Tracking: Selecting camera maker in 3D-View with other active camera\nWhen fixing #72162 (Crash when selecting camera maker in 3D-View when different camera is active) we came into uncharted territory. This task is for the expedition to this territory.\n\nIn the setup where you have a track connected to a camera, but have activated another camera, the selection logic is not working.\nIt is expected that when selecting a marker in this case, it would select the camera where the marker belongs to and select the marker that is under the mouse button.\n", "Viewport fps tanks when application is full screened on macOS\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.5.1\n\nI've noticed that when using either my M1 Air or M1 16\" Pro, when running Blender, the viewport performance is heavily dependent on the physical size of the viewport on screen. At first I thought this was just a limitation of my base model M1 Air, but it also happens on my M1 Pro Mac when plugged into a 4K or 5K display. Having Blender fullscreen will drastically reduce the viewport performance, but scaling the window down will fix it. Setting the scaling in macOS lower can also reduce the issue.\n\nAs far as I can tell, this happens in both 3.5 and 3.6, Metal and OpenGL backend. \n\nPerhaps this is intended functionality, but I can run Blender on potato PCs and not have frame drops like this. Even just the default cube will drop tons of frames on both my Macs. \n\nOpen Blender on a high resolution display and just start using it. The viewport performance is usually pretty poor on 4K / 5K displays if not scaling the window down.\n\n", "Eevee alpha blend mode bug\nOperating system: Linux-5.4.0-74-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\n\nThis bug happened since blender 2.90\n\nIn the scene the two objects with alpha blend mode, flip the transparency depending on the point of view.\n\n[0000-0050.mp4](0000-0050.mp4)\n\nTest file:\n[Ui1.blend](Ui1.blend)\n", "Topbar gliches\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.3 Beta\n\nThis only happened on windows.\nWhen Status Bar is hidden and Resolution Scale is greater than 1, the Top Bar sometimes becomes unusable. (look at the end of video)\nMy guess it has something to do with notifications that are now displayed at Top Bar.\n[bug.mp4](bug.mp4)\n\nSame as in the video\n- On the `Windows` tab disable `Show Status Bar`\n- Go to {nav Edit > Preferences... > Interface} and change the `Resolution Scale` to 1.2\n- Save Preferences\n- Close the Temporary Window\n- Reopen the `Blender Preferences` window ({nav Edit > Preferences...})\n- Press `Save Preferences`\n\nInvoking save as temporary window also causes this issue\n\nTrying to resize Top Bar area or maximizing some other area fix the issue." ]

[ "Toggle Quad View - maximize issue\nBroken: 2.72, 2.73 and prior ??\nWorked: 2.63 ( see QRWAXsbFAWY?t=10m39s )\n\nusing shortcut CTR+ALR+Q to maximize the viewport which lies under the mouse cursor does not work anymore, it always maximizes to user perspective\n\nthanx for fixing it, it is a great time saver\n\nwith friendly regards\n\nJozef alias Zajo\n\n" ]

[ "GPU Subdivision slows down in Sculpt mode, Weight paint mode.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.1\n\nGPU Subdivision slows down the work in Sculpt mode and Weight paint mode\n\n1. Turn on the GPU Subdivision.\n2. Enable the subdivision surface modifier on the model.\n3. Try to do something in Sculpt mode, Weight paint mode.\n4. Turn off the GPU Subdivision and follow step 3.\n\nWith GPU Subdivision enabled, the Sculpt mode and Weight paint mode tabs work much slower.\nIf it can't be fixed, then it would be logical for GPU Subdivision not to be enabled on these tabs.\n\nAt the same time, the GPU Subdivision works correctly in Object mode.\n", "GPencil: Brush and stroke size related issues\n**Description**\n\nWhen drawing in grease pencil, control over the brush size and the thickness of the stroke is of course extremely important. Currently, there are some inconsistencies and confusing behavior that need to be addressed. Here is a list of current issues and some new proposals.\n\n - **Brush Radius:** Currently, the brush size can be changed via this slider in draw mode.  The name displays \"Radius\" and the tooltip reads \"Radius of the brush in pixels.\", but this is not consistent with the thickness of the strokes. If the user sets the **radius** to 100px and the *Stroke Thickness* option in the object data properties is set to *Screen Space* the stroke has a **diameter** of 100 pixels. If the *Stroke Thickness* is set to *World Space* the stroke has a **diameter** of 0.1 meters. A simple solution is to change the UI name from \"Radius\" to \"Size\" and clarify in the tooltip that the thickness or diameter of the stroke is meant.\n - **Radial Control:** When the user changes the brush size via the radial control (shortcut {key F}) the control has a **radius** of the given pixel value, not (like mentioned before) a **diameter** of the pixel value set.  \n - **Brush size in World Space** When the *Stroke Thickness* in the object data properties is set to *World Space* the displayed thickness of the strokes in that grease pencil object are calculated via the following formula: `((line_change + stroke_thickness) * pressure * pixel_factor) / 1000.0f` E.g. when all adjustment values are set to their default value then **1px (stroke thickness) = 1mm (world space)**. Currently, there is no way for the user to know this. The UI gives no indication of this and the manual also does not mention it. A possible solution is to change the units of the brush from pixels to meters and also do the right conversion so that the size is correctly displayed in the UI.\n - **Drawing in screen space/world space:** The user can change the stroke thickness (screen space/world space) in the object data properties. That means that *all* strokes in the grease pencil object will be either drawn using the screen space thickness in pixels or the world space thickness in meters. But there is currently not a way to choose the brush size to be in screen or world space. In sculpt mode, the user can choose the brush size \"reference\" (Radius Unit).  This would also be useful for grease pencil. \n # **Brush size indicator:** At the moment there is no visual feedback on how big the current brush is. A solution could be a \"ring\" around the cursor and deactivate it during drawing so it only shows up before starting the stroke.\n\n---\n**Related reports:**\n#83675, ", "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)", "Symmetry in sculpt mode weird behavior with mask and face set\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.90.0 Alpha\nWorked: --\n\nWhen sculpting a non-symetric object with symmetry on, using shift+a or shift+w creates a weird behavior\n\n\n\n[bug.blend](bug.blend)\n- Open the file above.\n- use shift+a in the second finger like this:\n\n- Turn symmetry off and try it again:\n\n\nThe origin is far off those two fingers and also all the transformations are applied, so I don't think its an expected behavior,\n\n\nBesides, it doesn't happen when you try using brushes on the mesh. \n\n", "Color Filter: Sliding UI\n# Issue\n\nCurrently when using using the Filter tools in Sculpt Mode, like the Color, Mesh or Cloth Filter, to start the operation you need to click anywhere in the viewport.\nClick and drag from left to right will have a positive effect and from right to left the inverse effect.\n\nThe exact behaviour is very hard to understand and no information on the actual strength is given in the UI.\nSo we should add a UI element to give additional information.\n\n# Solution\n\nLuckily [D9314](D9314) and [D9054](D9054) already implemented such a UI element and modal keymap that could be reused for the Filters.\nSo when executing a Filter it should display a scale in the header to know how strong or inverted the effect currently is.\nUnlike with the Pose Mode Breakdowner the slider should start at the 0 % mark.\nThe shortcuts `E` for overshoot, `Ctrl` for increments and `Shift` for precision should also be included.\n\nThe capped 100% and -100% points will have to be tested so as a user it is rarely necessary to press `E` to overshoot the range.", "Grease Pencil: smaller objects have an export SVG-PDF Issues\nOperating system: Linux-4.15.0-144-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 5500 (BDW GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 3.0.0 Alpha\n\nI found an issue on the scale for smaller objects when they it is exported to SVG or PDF from new Grease pencil feature and LineArt. This was modeled in millimeters (0.001) and this is what happen when is exported. the bounding box is X84.6 Y35.3 Z78.2\n\n\nAnd this is the same object exported scaled up to 1000\n\n\n\n\n[tattoo-machine_Eevee.blend](tattoo-machine_Eevee.blend)\n", "UI: Merge Text Style \"Widget Label\" into \"Widget\", Add \"Tooltip\"\nWhen controlling how big interface elements are displayed, users can not only change the Resolution Scale and Region Zoom but can change the size and styles of some elements separate from others. This document proposes changes to our Text Styles.\n\nIf you go to Preferences / Themes / Text Style you will see that you can change the size of different UI elements independent of the overall UI scale. You can make it so that regardless of scale you always have Header text twice as large as regular text, for example.\n\nBut the design is not fleshed out well. We have just \"Panel Title\", \"Widget\", and \"Widget Label\". There are many areas where one type of UIBut uses one when it should use another. There are assumptions, like in #102687, that \"Widget\" and \"Widget Label\" are the same size. The function mentioned in that bug report - `ui_text_icon_width_ex()` - is trying to estimate an element's width but does not have the information needed to know what style to use, so just uses UI_FSTYLE_WIDGET, which is hardcoded for the \"widget\" style.\n\nIt seems like a nice idea that we can have labels displaying differently to the inputs beside it. And I have personally proposed adding to these options to include width, weight, slant, spacing and other text features.\n\nHowever, our interface is laid out programmatically using quite rough rules. We necessarily have a very tabular layout. For example we don't have (and might not be able to supply) a \"line height\": the vertical spacing between interface rows. This value is calculated from UI element width, considering scale and line width. So can't for example, leave the resolution scale the same but change the line-height to better accommodate languages that use fonts that are very tall (Arabic) or squat (Chinese).\n\nThis all means that we have little chance to make Label and Widget have varying sizes. The line-height can't vary with the largest of them, and we have to keep all interface rows the same height anyway.\n\nI propose that we merge \"Widget Label\" into \"Widget\" text styles, leaving us with only two styles \"Header\" and \"Widget\". And then add a third back for \"Tool Tips\" because that text size is currently set as a hardcoded fraction of the widget size - and I can imagine some users with vision impairment wanting those proportionally larger.\n\nThe only real downside is this would remove the ability for \"Widget\" and \"Widget Label\" to have differences unrelated to the size. There could be some users who have the same size but have them differ in shadow. Right now the only non-size changes possible are shadow-related but, as mentioned, we could add other options. For example we could allow one to be bold and the other italicized. But I don't personally think this is important. I don't like our text shadowing and use of weight and slant differences should be more selective than this, having sematic meaning. I would rather embolden important words, italicize special sections, etc.\n\n", "Cloth Brush solver improvements\n\nThis is a list of possible improvements that can be done in the cloth brush physics solver:\n- The solver is creating length constraints using all possible combinations between each vertex and its neighbors because the Sculpt API does not provide extra information about the mesh topology. This has multiple problems:\n - The same constraint is created multiple times from different vertices, which affects performance and memory usage \n - There is no easy way to split constraints per type (bending/shearing) as it is not possible to know which vertices are being connected. This limits the amount of control and the deformation types for the brush that can be implemented. \n - A possible solution is in ([D7471](D7471)), but I'm still not sure if that approach is going to work in Multires.\n\n\n - ##cloth_brush_satisfy_constraints## is not multithreaded and I'm not sure if it can be multithreaded at all with the current implementation\n\n- It should be possible to control the speed of the simulation by exposing the time_step parameter\n\n- There should be an option to use a persistent base (similar to the layer brush) to always start the simulation from the initial state of the mesh instead of creating the constraints with a different length each time a brush stroke is made. \n\n- Collisions and self collisions are not supported. It would be nice to experiment if collisions with other meshes can be added without affecting performance too much, but I don't know how this could be implemented. \n", "Object transforms affecting Sculpt Mode Brush behaviour\nThis is a design proposal to change some underlying behaviour of the brush system in Sculpt Mode.\n\n**The issue:**\nWhen scaling or rotating an object and then proceeding to sculpt on it in Sculpt Mode, the brush behaviour is generally affected by the transforms of the object.\nSo if the scaling is 1 on X & Y but 3 on Z, the brush radius will be 3 times as high. \nIf the object is scaled down in general, the brush strength will be lower in total.\nIf the object is also rotated, the brush radius will be as well and rake effects like for the Snake Hook brush will be badly affected since the object rotation is added to the rotation of the brush.\n\nIn recent versions the brush radius is at least reflecting the object transforms, which helps spotting these negative influences and reminding the user to apply the object transforms before sculpting.\nBut there is not benefit to having the Sculpt Mode being affected by the object transforms, so this is just a limitation of the current system.\nIt's also good to add that on the other hand Edit Mode is not negatively affected by the transforms of the object.\n\n[2020-03-02 11-42-04.mp4](2020-03-02_11-42-04.mp4)\n\n**The proposal:**\n\nTo make the sculpting workflow easier on the user it would be ideal if the brushes are not affected by the local transforms of the object but are instead based on the world scale & orientation.\nOnly symmetry options should be directly influenced bu the local transforms.", "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)", "Mask brush stops working in tiling sculpting mode after changing its size through \"F\" hotkey\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 2.93, 3.3.0\nWorked: -\n\nWhen an object has the Multires modifier, mask brush stops working in tiling sculpting mode after. (See video below)\n[Desktop 2022.09.17 - 21.18.10.07.mp4](Desktop_2022.09.17_-_21.18.10.07.mp4)\n\n- Open attached file or\n - Add a grid object\n - Add a multires modifier\n - Subdivide Simple a few times\n - Select mask brush in sculting mode\n - set tiling on x and y axis to 1 or 2m \n- try paint mask (sometimes the tiling doesn't work at this stage, you need to paint again and undo)\n- change brush size through F hotkey\n- try paint mask (tiling stops working)\n- press undo\n- try paint mask (tiling works again)\n\n[tiling_sculpt_bug.blend](tiling_sculpt_bug.blend)\n\n", "Brush Radius still displays pixel units while adjusting brush radius using the \"F\" key in Sculpt Mode after changed to scene units\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0\n\n \n\n Brush Radius still displays pixel units while adjusting brush radius using the \"F\" key in Sculpt Mode after changed to scene units\n\n\n\n\n - Change the brush radius unit in sculpt mode to use scene units\n\n\n - Then try changing it using the F key. At the top left corner it still displays pixel units.\n\n\n\n\n\n", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg", "Texture Mapping issues on large brush radius\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\n\nWhen a large brush radius for textured brushes in sculpt mode, the outer-most affected geometry doesn't apply the texture fully. This is especially noticeble on the Clay Strips and Paint brushes when the stroke method is set to anchored.\n\n\n\n\n\nBlend file = [bug.blend](attachment)\n\n- Open the File\n- Use the provided paint brush and clay strips brush on a subdivided cube or suzanne head like shown\n- Notice how the outer edges of the falloff is not updating the geoemtry fully\n\n", "Grease Pencil Sculpt/Vertex Paint Tool is exponentially slower when using tablet instead of mouse\nOperating system: Win10\nGraphics card: RTX 3070 FE\nTablet: Xp-Pen Deco 03 (Wireless)\n\nBroken: 3.1\nWorked: N/A\n\nWith high-geometry Grease Pencil strokes, the Sculpt Tool (and the Vertex Paint Tool) is exponentially slower when using tablet. \n\nVideo explanation:\nDavVZXsxBmI\n\nBlend File:\n[SculptToolExponentiallySlowerWithTabletThanMouse.blend](SculptToolExponentiallySlowerWithTabletThanMouse.blend)\n\n" ]

[ "Brush resizing got locked to 1 axis.\nOperating system: Linux-5.0.12-050012-generic-x86_64-with-neon-18.04-bionic 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50\n\nBroken: version: 2.81 (sub 14)\nWorked: blender 2.80 release\n\nThis makes it hard to resize the brush while using a tablet. In fact, makes it nearly impossible to get the exact size you want on first try.\n\n1. Add an object\n2. Go to Texture Paint mode\n3. Hit F to resize the brush\n\n" ]

[ "Eevee alpha blend mode bug\nOperating system: Linux-5.4.0-74-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\n\nThis bug happened since blender 2.90\n\nIn the scene the two objects with alpha blend mode, flip the transparency depending on the point of view.\n\n[0000-0050.mp4](0000-0050.mp4)\n\nTest file:\n[Ui1.blend](Ui1.blend)\n", "GPencil: Hardlight blend issue\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83.0\n\nThe semi-transparent textures of Grease Pencil material turn black when their layer is in HardLight blend mode.\n\n- open the provided blend file\n- see, wrong alpha blending\n- NB: change the blend mode and it works as expected\n\n[GP-hardlight-blend-issue.blend](GP-hardlight-blend-issue.blend)\n\n", "Dopeheet (in the Grease Pencil submodule) take account the transform keys of the GP object wen you press jump to previous/next key frames.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon (TM) Pro WX 7100 Graphics ATI Technologies Inc. 4.5.14802 Core Profile Context FireGL 21.Q4 30.0.14011.2006\n\nBroken: version: 3.4.0 Alpha\n\nDopeheet (in the Grease Pencil submodule) take account the transform keys of the GP object wen you press jump to previous/next key frames.\nIn this Grease Pencil submudule only the GP drawing keys should be taken into account.\n\n**Steps to Reproduce**\n- Open .blend file\n- Select Grease pencil mode in Dope Sheet\n- Jump to next keyframe \n[#100538.blend](T100538.blend)\nHere a quick video with the issue:\n [2022-08-21 15-13-26.mp4](2022-08-21_15-13-26.mp4)\n\n\n\n", "Armature modifier taking a performance impact, even when set to not be visible.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.2\n\nSome part of the Armature modifier is still calculating even when set to not be visible.\nCausing a performance impact, when an artist expects none. Other modifiers like Subdivision Surface do not have this issue.\n- unrelated, also kinda sucks that I get sub 24fps with 100k poly videogame ready models.\n\nHave a high poly model weighted and bound to an armature, with any simple animated movement. Take note of the viewport performance when viewing playback of the simple animation. Disable all visibility options on the Armature modifier on the model. Performance only increases slightly. Uncheck 'bind to vertex groups' on the modifier. See performance improve drastically, even though the modifier is set to not be visible in the first place.\n\nWith the attached blend file, a high poly model is already bound to an armature with a simple animation.\n[ArmatureModifierBug.blend](ArmatureModifierBug.blend)\n\n", "Grease Pencil Draw Tool Settings displayed in the wrong context\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52, hash: a0f3...\nbuild date: 2019-07-06, 01:03:01\n\n\n\n**To reproduce:**\n\n - Create a Grease Pencil Object\n - Enter Draw Mode\n - Display tool settings, either in the header or the properties window\n - In the toolbar, click on the Erase or Fill tool\n - Now click on one of the Add tools (Line, Arc, Curve, etc.)\n - Look at your tool settings\n\nNote that when you switch from the Erase or Fill tool to an Add tool, the settings do not change to the correct ones! Instead, the settings or the Erase or Fill tools remain. You have to select the draw tool before selecting an add tool in order to refresh the settings. \n\nThis bug appears for the tool settings in both the properties window and the header.", "Grease Pencil - Straight line at beginning of stroke\nOperating system: Mac OS Mojave\nGraphics card: Intel UHD Graphics\n\nTablet: Wacom Cintiq\n\nBroken: 2.83.0\n\nWhen making fast strokes, there is delay that causes a straight line. Most noticeable when drawing quick circles. It seems to be there's a delay between starting the cursor pressing down and starting the stroke.\n\n\nBased on the default startup, adjusting setting doesn't change the behaviour. The straight line is present with all brushes.", "2.93 texture coordinate display bug\nOperating system: win10\nGraphics card: 2070 super\n\nBroken: 2.93.0-321eef6a0c0f 4/2\n\n\n\ntexture coordinate display bug differently in viewport compared to render\n\ni used a generated coordinate. in the viewport it seems that blender applied the coordinate after the curve modifier (maybe)\n\nbut in render it will apply the coordinate before the curve modifier, so the gradient is able to follow the curve which is my desired look.\n\nsometimes it will display the coordinate correctly but I don't know how I achieved it\n[bug.blend](bug.blend)\n\n", "GPencil: Layers used as mask and with viewlayer filter applied are rendered in all passes. \nOperating system: Linux-5.4.43-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.90.0 Alpha\n\n\nLayers, used by other layers as masks, are always rendered when they have a viewlayer filter applied in all render passes.\nI feel a layer used as a mask for other layers and with viewlayer filtering it should work as a mask even when it is not rendered in a pass.\nI don't know if this is intentional, a time limitation, or a complex implementation.\nAssess whether this squares as a bug or feature recuest. Thank you very much for your wonderful work.\n\n- Download the blend file.\n- Note that the layer called \"masc\" is used as a mask for the other two and all layers are filtered in viewlayer filter.\n- Render and note that the mask appears in both passes.\n[GP bugreport viewlayerfilter and layers mask.blend](GP_bugreport_viewlayerfilter_and_layers_mask.blend)\n", "Missing overlays in the viewport when viewing through transparent shader\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6.1\n\nwhen viewing an LGT-shadow_caster.004 object, all overlays disappear from a certain side of it\n\n\nSee LGT-shadow_caster.004 in blender 3.6 splash screen\n\n", "Artifacts appear in texture bakes [stripe pattern]\nOperating system: Windows 10 Pro 64-bit\nCPU: i7 4790\nGraphics card: GTX 1050\n\nBroken: Every Blender Build on this PC, Baking.\nWorked: never\n\nWeird artifacts appear in bakes, especially visible in the AO bakes (see attached images)\n\n\n\n\n\n[AOArtifacts_Test.blend](AOArtifacts_Test.blend)\n- Open blend\n- hit `Bake`", "GPencil: Canvas Overlay becomes inconsistent when both Object and Layer are transformed\nOperating system: Windows\nGraphics card:\n\nBroken: 3.4.1\nWorked: never?\n\nModifying Grease Pencil Layer transforms affects the Canvas overlay, but when both the Object and Layer have transforms the overlay does not describe the drawing plane actually being used by tools.\n\n- Open attached .blend\n- Draw new strokes into the Lines layer\n- Rotate the viewport to view the stroke placement.\n\n", "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "GPencil: Modifiers don't work after separate strokes and use hide in outliner [issue with multiuser gpencil objects and modifiers]\nOperating system: Ubuntu 20.04\nGraphics card: Mesa Intel® HD Graphics 620 (KBL GT2\n\nBroken: (2.83.3)\n\n\nThe mirroring of a grease pencil object briefly stops being visible after performing a stroke separation.\n\n1. Boot up Blender's default 2D animation workspace\n2. Draw a stroke on the GP object \"Stroke\"\n3. Add a mirror modifier to the object.\n3. Draw another stroke\n4. Change to edit mode and select the new stroke\n5. separate said stroke with P, creating \"Stroke.001\"\n6. Still on edit mode, click on the 'eye' icon on the outliner to make \"Stroke\" invisible\n7. Click on the eye icon again, the mirroring will have stopped being visible.\n8. Clicking twice on the \"Display modifier on viewport\" button in the modifier tab fixes the issue.\n\n**Status**\nThe \"wrong usercount when separating\" is fixed, see 4251a87bf6, however the underlying issues with multiuser gpencil and modifiers still remains.\nTo reproduce:\n- add a gpencil stroke\n- {key Alt + D} duplicate linked\n- add a Thickness modifier.\n- Hide/Unhide the object in outliner.\n", "Grease Pencil Tint / Also Vertex Paint on Grease Pencil Objects very slow with Cintiq Pro 24\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.1\n\nWhen i use Grease Pencil Tint with the a Cintiq 24 Pro it's very very slow. I have to wait after each stroke to continue. Drawing with the mouse is no problem.\nSame with vertex paint on a grease pencil object.\n\nWindows Ink and Wintab made no difference\n\nJust tinting with the cintiq stylus in the attached scene on the current layer.\n\n", "Grease Pencil: draw pixels don't scale to pixels.\nCurrently grease pencil uses pixels in a very confusing way, since it doesn't actually relate to pixels.\n\nEither:\n\n- The size of a brush should use the current zoom level and use pixels as we do for all other draw tools.\n- We should use blender units for grease pencil brushes." ]

[ "Grease pencil: effect mask color and alpha mode causing problems\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 5)\nWorked: (optional)\n\nUsing effects like Rim or Glow with a grease pencil object cause weird artifacts. The mask color in the Rim effect will not recognize a color-picked color and \"Use Alpha Mode\" in the Glow effect causes weird rims inside a fully opaque part of the picture.\n\n\nI have attached a file containing this picture. \n\nIn the screenshot w,e can see the effects that are having problems (at least these ones). The Mask Color in Rim effect will not leave the red text uncolored even if it is selected/colorpicked as the mask color. The same thing applies to the \"Select Color\" in the Glow effect. I haven't shown it in the screenshot since I wanted to show what kind of weird rim artifacts are produced by the effect when \"Use Alpha Mode\" is turned on. Intuitively at least it should just prevent the glow from bleeding to fully transparent areas. That's what the name sounds like but that isn't what's happening.\n\nIf you set the Glow mode from Luminance to Color and use the color picker to select the gray color of the tree, no glow is applied. Only after a minor tweaking of the value we, get the glow to work. The blender file is in Standard Color management mode, so I don't really know why the color picker values don't work like they should.\n[greasepencil-anomalies.blend](greasepencil-anomalies.blend)\n" ]

[ "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?", "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "Mixing sequencer and preview regions causes logical problems\nWith the addition of many editing operations to the sequencer preview,\nthere are an increasing number of logical problems with parts of the\nUI that operate on the area, not the region.\nMainly menu items and the tool-system.\n\nNote that this is only a problem with both are enabled at once.\n\nTo pick some examples:\n\n- Delete from a menu (should this delete the selection in the preview or the sequencer?)... same for select-all... and in the future copy/paste.\n- Transform (Move for e.g. is a different operation for the sequencer and preview).\n- Box select from the menu currently can't run in both sequencer and preview regions.\n\nIf the code-base is left in it's current state I'm concerned users will run into glitches/bugs (finding the mixed preview/sequencer to be broken).\nFor the most part these won't be things that can be resolved in isolation, so I think it's worth considering a solution now.\n\n----\n\n**Supporting Mixed Preview/Sequencer**\n\nTechnical solutions for this are possible but impractical in my opinion, for example the operator_context could support multiple items:\n\n```\n layout.operator_context = {'INVOKE_REGION_PREVIEW', 'INVOKE_REGION_WIN`}\n```\n\nFor the sake of argument we could have 2x menu items for Delete, Select-All... etc.\n\nOther options include introducing an \"Active Region\" concept or having a header for each region.\n\nThis amounts supporting functionality in separate regions that areas already handle.\n\n---\n\n**Proposed Solutions**\n\nNote that I don't have a strong opinion on the exact solution,\nonly that it should not over complicate the current code-base\n*(unless we wish to support larger changes to Blender's windowing in general).*\n\nWhen mixing preview/sequencer:\n\n* Remove the preview region interactive behavior.\n\n```\nThis would make it view-only, any interactions, menu items, tools etc\nwould only apply to the sequencer.\n```\n\n* Remove support for mixing preview/sequencer at once.\n\n```\nWe could handle this with versioning (splitting the area).\n```\n\n", "GPencil: Improve Dopesheet display for keyframes\nThe actual display only shows the actual keyframe, but not all the range where the keyframe is used.", "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", "Image sequences used on brushes do not update while texture painting (despite auto refresh option)\nBroken: 2.8x and later\nWorked: 2.79 and probably older\n\n\npainting with image sequencer (sprite) no longer works when holding click, but it updates when clicking again and again while painting\n\n\nSteps to reproduce the error (you must be in 2.8 or later)\n1) go to Texture tab\n2) create a new texture and open\n3) select the images that contain the same name with order numbers\n4) enable Cyclic and Auto Refresh\n5) make sure you set it as Texture Mask and not Texture\n6) set it to View Plane so the texture image follows the brush\n7) play the timeline and begin to draw on the mesh\n\nNotice how the image texture does not change when dragging on the mesh, but if you try to click again and again, it changes.\n\nthis is how it should look when it works:\n\n\nThis must be brought back, it has soo much potential and possibilities!\nif this is something that is already considered and being worked on for the new upcoming blender version, then I'd be very happy\n\n[Desktop.zip](Desktop.zip)", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "NLA Strip influence slider doesn't respond to autokey correctly.\nOperating system: Win 10\nGraphics card: GeForce GTX 1070\n\n\nBroken: 2.82 Release\n\n\nThe Influence property of the NLA's strip, has some strange behavior and something that might be a bug.\nThis was reported before in #63865, which was supposedly resolved, but the problem still exists\n\nWhen changing the value of the influence slider with the autokey turned on, it jumps back to its previous value and does not update to the new one. After repeating it 2 or 3 times it applies the value. When applying the value numerically it works fine, it seems to be a problem with the update of the slider.\nMoreover, when turning influence on it always adds a keyframe to the first frame of the action (where the action is on the timeline ). It sets a keyframe with the value 0, instead of the current value.\n\n- Open attached file\n- Select one of the Action strips.\n- In the Sidebar, go to {nav Strip > Active Strip} and turn on `Animated Influence`. (Note that a keyframe is added to the first frame of the action).\n- Go to a new frame with the Autokey turned on, change the value of the influence slider.\n- Go to a new frame - the value should jump back to the previous one\n\nI've made a short video which describes the errors\nwatch?v=Sh5MwYCH9T4\n\nSample file:\n\n[Influence_bugreport.blend](Influence_bugreport.blend)", "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", "Crash when selecting line art\nOperating system: Linux mint 21. Blender installed using flatpak.\nGraphics card: See attached system_information.txt\n\nBroken: version: 3.5.1\n\nBlender Crashes.\n```\nbacktrace\n\nPython backtrace\nFile \"/app/blender/3.5/scripts/startup/bl_ui/space_view3d.py\", line 704 in draw\nFile \"/app/blender/3.5/scripts/modules/bpy_types.py\", line 903 in draw_ls\n```\n\n```Py\nbpy.ops.outliner.item_activate(deselect_all=True) # Operator\nbpy.ops.outliner.item_activate(deselect_all=True) # Operator\n```\nWith attached blend file, in the outliner, select cameras, line-art then try to change the color of the background.\n\n", "Schrodinger's Animation errors\nOperating system: Windows 10\nGraphics card: GTX 760\n\nBroken: 2.80, Hash: d30f72df8ac, 2019-06-19\n\nIf you filter the action editor by errors it will not show any unless you have seen them. This makes it very tedious to find errors with my keyframes. I've added a gif to show the problem better.\n\nMake an armature with several bones and create an action with keyframes for all of the bones. \n\nDelete one of the bones. \n\nIf you don't have enough space to show all the channels in the action editor then the filter by error thing will not correctly show you the keyframes for the missing bone.\n\nIf you scroll down and see the errors with your own eyes, the filter will work.\n\n", "NLA: Fix Dragging Strips\nNOTE: test the patches for Solution1 temp-[D10103](https://archive.blender.org/developer/D10103)-nla_support_strip_overlap_during_transform/temp-[D10103](D10103)-nla_support_strip_overlap_during_transform-blender-2.92.0-5065c0e6d5bc-windows64.zip\n\nThis is no longer true, we would rather remove them and improve the interaction with HOLD type ****Update design since transition strips should be kept.****\nTodo: Add concrete examples where transitions are useful in the ideal case (where strips animate through the transition).\n___\nReport: #82195 (NLA tracks won't pass through actions or locked tracks)\n\n**Summary:** The ideal solution is to get rid of transition strip types. They're useless. Let strips overlap. When they do, they get blended in order like an upper strip. Then we don't have to restrict movement.\n\n___\n\nBehavior can be found in: (transform_convert_nla.c) *recalcData_nla()*\n**Problem**: The core intent of the function is to prevent moved strips from overlapping other strips. The restriction is reasonable since NLA evaluation is undefined in this case. However, the implementation prevents the ability to move a strip to its destination even if it wouldn't result in overlap. \n\nWhen moving strips:\n* You cannot move a strip through a locked track, even if not the intended final destination.\n\n* You cannot move a strip past another in the same track, even if the intended final destination would not result in overlap.\n\n* You cannot move a strip into through or into a track if doing so results in overlap. \n\n* Vertically moving strips, when there are no more nla tracks, leads to strips being vertically compressed. This breaks the animation when strip extrapolation is important.\n\n___\n**Solution1:** (Simpler solution) We only apply the restriction on the final strip location. If the strip cannot be placed without overlap, then we either cancel the move operation (not ideal) or notify the user (show the strip as red?) without cancelling.\n\n[D10101: Cleanup: Nla: Refactor nla.c functions](D10101) (independent patch) Does a little bit of refactoring which [D10103](D10103) relies on.\n[D10102: NLA: Strip Post-transform Horizontal Shuffle](D10102) (independent patch) Adds support for horizontal shuffling so users can horizontally drag strips past eachother.\n[D10103: NLA: Strip Post-transform Vertical Shuffle and Auto-Grow Track List](D10103) (depends on prior patches) Adds support for vertical shuffling so users can vertically drag strips into a new track even if it results in overlap or the user moves the strip into a locked track.\n\nPatches have been made for this solution since it's simpler and faster to implement. Overlap support can still be worked on but is a lower priority and still has design problems to figure out.\n___\n**Solution2:** (Ideal solution, but would take longer to implement) We change NLA evaluation to work properly when strips overlap. Then we can completely remove the restriction and let the animator freely move strips. \n \n**Patch1: Completely remove transition types**\nWe can simplify NLA evaluation here a bit. NLA transitions are problematic and ineffective. *Transition strip types should be completely removed.* They do a lerp between the previous strip's last pose and next strip's first pose. Generally in animation, lerping 2 poses is a problem you fix, not something you ever want. Support-wise, transitions are a bit broken anyways (see [D9711](D9711) and [D9713](D9713))\n\n**Patch2: Implement new behavior when strips overlap**\nInstead of an explicit transition strip type, we'll let action and meta strips support a new transition behavior. When two strips overlap, we simply blend the next strip as if it was an upper strip. That's the core idea. \"Transitioning\" strips of the same track would used for convenience and organization. This would simplify the keyframe remapping math. In [D8296](D8296), I couldn't figure out the math to properly invert through transitions between a Quaternion Combine strip and a Quaternion Replace (or any non-Combine) strip. With the new behavior, keyframing through transitions is simplified to inverting through any other strip. \n\n**Patch3: Re-add support for holding poses through the transition**\nThough, as is, both strips are always animated through the transition. We don't have the ability to hold one strip's boundary pose while the other animates through the transition. I propose a few new strip properties: `hold_left_duration` (unit: scene frame), `hold_right_duration`. The influence over these regions can be automatically calculated when strips overlap. Or they can be keyed into shape using the existing influence fcurve. As an example of these new properties, we'll have two strips that only overlap over this held duration. \n*Note. I'm having second thoughts on the properties. Yes, there should be support for holding poses through the transition. But the problem is how these properties are anchored relative to the strip bounds and what's most convenient. I want to avoid problems like the ones we already have with nla strip frame_start/end being tightly related to the action clips frame_start/end, scale and repeat values. This leads to unintuitive strip frame_start/end changes.*\n\n**Patch4: Finally loosen strip dragging logic (only relies on patch2)**\nWe can completely remove the dragging restriction and let the animator freely move and overlap strips.\n \n___\n\n(Pretend the two strips are in the same row/track. I did not draw them that way because I'm not sure how the UI should look. This also isn't a suggestion for how the UI should render)\n\nThis results in *nearly*the same result as old Transition clips. Only *nearly*, because the old implementation would first blend the prev strip with the lower NLA stack, then blend the next strip with the lower NLA stack, then lerp the two. The new behavior holds the previous strip's last pose over the light green area. The next strip's first pose is held over the pink area. The influence of the next strip increases linearly. \n___\n\nThis holds the previous strip's last pose. The next strip animates as it's blended.\n___\n\n\nAnother possibility.\n___\n\n**Problematic UI case**: I'm not sure what the proper UI should look like when one strip completely overlaps. The animator can always just move the strip out above as a work around. Logically, it would evaluate fine. It would just be a UI issue. What if N strips overlap? It still all works out. We blend the strips in the order of their start frame. What if all strips are on the same start frame? That case won't be properly supported and considered undefined (as in we won't fix it). The animator can and should fix it themselves. \n__\n\n**Alternative WorkAround:** Add operators that can be used as workarounds.\n* ([RCS]())Send strip to the end of the active strip or track, with options to handle overlap properly. \n\n___\nPatches:\n\n**(Abandoned)Patch set 1: Removal of transitions** \n*Note: I'm not sure how file versioning should be handled? I haven't removed the strip type NLASTRIP_TYPE_TRANSITION yet. I'm not sure if the enum should remain so it can be used for file versioning to either delete transitions or convert them to the new behavior (after Patch set 3).*\n[D9702: Nla Transitions Obselete: remove ui icon](D9702)\n[D9703: Nla Transitions Obselete: Nla Stack no longer evaluates Transitions](D9703)\n[D9704: Nla Transitions Obselete: Remove Operator Add Transition](D9704) \n[D9705: Nla Transitions Obselete: Remove themed drawing](D9705) \n[D9706: Nla Transitions Obselete: Remove default naming case](D9706) \n[D9707: Nla Transitions Obselete: Special case for adjacent strip deletion](D9707) \n[D9708: Nla Transitions Obselete: Adjacent strip overlap resolution](D9708) \n[D9709: Nla Transitions Obselete: nlastrip_get_frame()](D9709) \n[D9710: Nla Transitions Obselete: RNA strip frame_start/end set functions](D9710) \n[D9711: Nla Transitions Obselete: Transform, redundant check](D9711) \n[D9712: Nla Transitions Obselete: Transform, Cancelling](D9712) \n[D9713: Nla Transitions Obselete: Transform, broken strip exceed resolution](D9713) \n[D9714: Nla Transitions Obselete: Loose comments](D9714)\n**Abandon Reason:** I misunderstood why transitions were limited. Yes, their current implementation only supports single pose transitions. But they would be more useful if the strips animated through the transition. Alexander Gavrilov suggested we keep transitions for their branched evaluation behavior.\n", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "Stereoscopy not working properly with time remapping and motion blur\nOperating system: Windows 7\nGraphics card: GTX 1070\n\nBroken: Blender Version: 2.83 LTS\nWorked: Never\n\nI encountered two weird issues when using stereoscopy, time remapping and motion blur at the same time.\n\nThe first issue is easy to reproduce because it happens every time stereoscopy and time remapping are enabled.\nFor example if we set time remapping to be Old: 100 and New: 200 and try to render the frame 100 there is no issue while rendering the left camera, but the right camera reports it as the frame 50 (but it does actually render the correct frame - 100). Also the playhead gets set to the frame 50 after rendering. If we were to render again, it would render the frame 50 and set the playhead to 25 and so on and so on.\n\nThe second issue I have not been able to reproduce in a fresh scene, but I have a .blend file where it is present. \nSo again when rendering some frame with time remapping enabled, the left eye is fine, but the right eye renders some objects with motion blur that should not be there.\nI believe these two things are related and possibly the result of a single bug, so I'm not splitting these into two bug reports.\n\nThis is a stripped down version of my scene - it was a complete animation with a character.\nThe motion blur wasn't present on the character's body, but it was present on the character's eyes and teeth (both parented to a specific bone through Object Properties > Relations), and that sphere parented (with a 'child of' constraint) to the root bone.\n\n[stereoscopy bug.blend](stereoscopy_bug.blend)\n\n- Open file\n- Render\n\nOne eye have motion blur, another one does not.\n\n", "Glitches on Video Sequence timeline\nOperating system: Linux 5.9.11\nGraphics card: Intel Haswell\n\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nShowing glitches on video sequence timeline when area of Video Sequencer resizing\n\nSteps shown on video\n\n[2020-12-02_15-19-26.mov](2020-12-02_15-19-26.mov)" ]

[ "Video Sequence \"Slip\" tool ignores handle offset constraints\nWhen transforming video sequencer handles, there are limits beyond which you cannot move them which is enforced by the transform code.\n\nThe Slip operator ignores these constraints - allowing the strip content to be dragged with offsets that are outside the strip start/end.\n\nTo redo:\n\n- Start a new Video Sequencer Template\n- Add a new scene\n- Add that scene as a sequence strip.\n- Press 'S' to slip the selected strip.\n- Move the strip to the right of the strip (500 frames eg) so the strip has no content in it.\n- As an example of how this isn't properly supported:\n\n - Change the \"Strip offset start\" - *The Scene flips and becomes negative, showing handles in the opposite directions.*\n" ]

[ "Crash when auto script execution is enabled\nOperating system: Windows 10 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: Blender 4.0.0 7372b3bdda35 and later\nWorked: never? 2.93 fails too\n\nBlender daily build crashes immediately on launch. The blender start screen isn't shown at all, only a grey window which then immediately closes. The crash log indicates that it is a memory EXCEPTION_ACCESS_VIOLATION (see log file attached).\n\n- Open preferences, enable `auto script execution`\n- Save prefs and close blender\n- Rename attached file and replace it with existing startup file\n- Launch blender (crash)\n\n- - -\n<details>\n <summary> Original report </summary>\nStart Blender through Steam, Blender Launcher, blender_debug_log.cmd, blender_debug_gpu.cmd, or blender_debug_gpu_glitchworkaround.cmd.\nA grey window opens with the Blender logo in the top bar.\nThe window closes as Blender crashes.\n\n[ Crashing_4-0-0_daily.blend](https://projects.blender.orgattachment)\n</details>", "Regression: Crash on deleting shape key from Blender File view.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0, 3.2\nWorked: 3.1\n\nCaused by a71a513def202b119328035dbd68e86c2c47f7ac\n\nOutliner on Blender File when delete cause crash guide.\n\n- Open attached file\n- Add shape key\n- Switch outliner to Blender file display mode\n- Expand Shape key\n- select `key` then delete it from context menu\n\nr2jrCca\n\nYoutube:\nOlegeJrBbmE\n\nMy Dropbox file:\nLola%20Bunny.zip?dl=0\n\n- - -\nFirst create new ticket I unable to paste picture this here.\nI did drag there 250MB and (Remove) cause appear <html><head></head><body></body><html> please fix without <html> k5RFuuy\n\n", "FBX vertex parent to curve export crash (python acces to matrix_local issue / 'give_parvert' misses curve_cache)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.72\n\nBroken: version: 2.81 release\nBroken: version: 2.82 (sub 6)\nWorked: 2.79\n\nBlender crashes when trying to export mesh that is vertex parented to curve\n\n\n\n1. Create mesh and curve\n2. Vertex parent mesh to curve control point\n3. Export mesh\n[crashb.mp4](crashb.mp4)\n\n\n\n", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\n\n", "Blender 2.71 (rc2) crashes when a UV sphere is added\nMac OS X 10.10 (beta) / AMD Radeon HD 6750M 512 MB\n\nBroken: 2.71 (release candidate 2)\nWorked: -\n\nBlender 2.71 (rc2) crashes when a UV Sphere is added to a existent project in Edit Mode.\n\nUsing the attached file, select the figure (stickman), go to Edit Mode and add a UV Sphere. After executing these steps, Blender stops responding and it's necessary to force quit and reopen. \n\nIt seems that's something to do with the modifiers (in the attached file, I'm using Mirror, Skin and Sub-surf). One or more of them are causing the crash when the UV Sphere is added. If I create a new project with no modifiers, I'm able to add UV Sphere. \n", "2.8: Python API: Changing area type on frame change crashes Blender\nOperating system: Windows 10\nGraphics card: Quadro P4200/PCIe/SSE2\n\nBroken: 2.81a (also crashes in 2.79 and 2.80)\n\nI am attempting to sample the individual frames of an image on frame change, using a solution similar to the one described here: 5. I cannot seem to set the viewer area, however, from this context, as `bpy.context.screen` is `None`, and `bpy.context.window_manager.windows- [x].screen` seems to crash Blender in some situations.\n\nFrom the default startup file, run the following basic code:\n\n```\nimport bpy\n\ndef on_frame_change(scn):\n bpy.context.window_manager.windows[0].screen.areas[0].type = \"IMAGE_EDITOR\"\n\nbpy.app.handlers.frame_change_pre.append(on_frame_change)\n```\n\nRun the `Render Animation` operator to crash Blender.\n\nNote: This code runs fine when playing the animation in the 3D Viewport. It seems that this bug relates to the render context only.", "Undoing the removal of a vertex group in edit mode changes other vertex groups and doesnt bring the removed vertex group back\nOperating system: Linux-5.4.13-201.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional)\n\n\nUndoing a vertex group changes the rest. The video should show the issue. There's 3 vertex groups, A = A, B = B and C = C. If you delete A, B = B and C = C. If you delete A and then undo it, B = A and C = B.\n\nTy9U5rj_6Sw\n\n[#63434.blend](T63434.blend)\n- Open File\n- you should be in editmode\n- remove the `zero_weight` vertex group\n- Undo {key Ctrl Z}\n- `zero_weight` vertex group is not back\n- `half_weight` vertex group now has zero weights\n- `full_weight` vertex group now has half weights\n\n\n", "Bug with autosave in edit mode\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.3.0\n\nBlender creates autosave when in edit mode but doesn't save the file as in edit mode\n\n- Set `Auto save` timer to 1 minute\n- Open attached file\n- Switch to edit mode\n- Make changes until auto-save file will generate\n- Open another blender instance and open auto-saved file (you'll find default cube in there)\n[try-auto-save.blend](try-auto-save.blend)", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Blender 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)", "Crash with certain file. Sculpt mode. Vertex color fill + edge.\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\nWhen I try to apply vertex color Fill (Sculpt mode) on edge in this particular file, I get crash\nAnd all fine for shapes/triangle.\n\n[VC + edge crush.blend](VC___edge_crush.blend)\n\n[debug_logs.7z](debug_logs.7z)\n", "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\n\n", "Regression: Multires Unsubdivide destroys the vertex groups\nOperating system: Windows 10\n\n\nBroken: 3.0 release, 3.0 (b42354672e)\nWorked: 2.93LTS, 3.0 (cec103d5a9) \n\n\nIt seems like unsubdividing using the Multires Modifier destroys the vertex groups, interesthingly enough other kind of mesh data stays intact (like the vertex colors) after the same operation.\n\nThe Decimate modifier's Unsubdivide does not destroy the data, but using the Decimate modifiers not option in these kinds of usage because the multires one is about getting the prior subd levels for sculpting purposes.\n\n[byUQjUlY19.mp4](byUQjUlY19.mp4)\n\n\nLoad the .blend file\nSelect the torus\nMultires->Unsibdivide\nMove your mouse to the 3d viewport to get the UI update properly\nThe Vgroups are gone\n\n[multires_09122021_1051_52.blend](multires_09122021_1051_52.blend)\n", "MeshDeformModifier Crashing\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\nWorked: -\n\nAfter binding, with the Dynamic attribute driver value set to 1 in driver editor, it crashed.\n\n1. Add a driver to use_dynamic_bind.\n2. Click Bind\n3. Set the driver value to 1\n\n\n\n\n" ]

[ "Crash when deleting last face using adaptive subdivision in render shading mode\nOperating system: Linux-4.15.0-70-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50\n\n**Blender Version** \nOlder Version: blender-2.79-e045fe53f1b0-linux-glibc217-x86_64 date: 2019-06-27 10:41\nLatest Version: 2.82 (sub 1)\n\nWorked: Unknown\n\nWhen in render shade mode deleting the last face will crash blender.\n\n - Open Blender.\n - Switch to Cycles.\n - Change Feature set to Experimental.\n - Add \"Subdivision Surface\" modifier to default cube.\n - Make \"Subdivision Surface\" modifier Adaptive by checking box.\n - Switch to Rendered Shade Mode.\n - Enter edit mode.\n - Delete all vertices" ]

[ "OPTIX_ERROR_INTERNAL_ERROR when rendering using Cycles with OptiX\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nAlso tested on:\n- 3.0.0 — got same error\n- 2.93.18 — same error but different line of code\n\nOPTIX_ERROR_INTERNAL_ERROR when rendering with OptiX.\n\nError on 3.6.2\n\n\nError on 2.93.18\n\n\nThe issue is **not** presented when I'm using _NVIDIA Studio Driver 472.84_. However I've tried several newer versions and got this error for all of them.\n\n\n1. Open blender (just the default cube)\n2. Edit -> Preferences -> System -> OptiX -> NVIDIA GeForce GTX 1060 6GB\n3. Render Engine: Cycles\n4. Device: GPU Compute\n5. Shading (Z) -> Rendered or Render Image (F12)\n\n", "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)", "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)", "Select Loop Inner-Region issue\nWin8 64bit | GTX680\n\nBroken: 2.77 509270e\n\nWhen working with face loop, this tool doesn't always work as expected.\n\n\n\n\nNot sure if this can be a bug. Please check.", "\"Illegal address in CUDA queue\" error occurs when I use both Principled BSDF and Adaptive Subdivision\nOperating system: Windows 11 Pro 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\n-**\"Illegal address in CUDA queue\"** error occurs when I activate both Principled BSDF and Adaptive Subdivision at the same time.\n-It would work fine if I don't use both at the same time.\n-Here are the possibilities of the error occurring when I use different settings:\n1. Principled BSDF + Adaptive Subdivision = **error**\n2. Texture Coordinate surface + Adaptive Subdivision = **no error**\n3. Principled BSDF + NO Adaptive Subdivision = **no error**\n\n-I can use a high poly count without Adaptive Subdivision *(e.g. Level viewport = 7)*, works fine. But as soon as I turn it on *(even with low poly count, e.g. Dicing scale = 1)* combined with Principled BSDF, the error occurs.\n\nIn the file I sent, I've already activated Principled BSDF + Adaptive Subdivision, you need to turn on the \"Rendered Viewport Shading\" and then slide the Scale parameter of the Noise Texture very quickly and the error should occur.\n", "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", "Unable to execute Toggle Edit Mode - error changing modes\nOperating system: Linux-5.15.11-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.3.2\n\nBroken: version: 3.1.0 Alpha\n\n\nIt happens when I try to toggle to Edit Mode on second scene if first scene has edit mode a object\n\n\n\n1) Open file\n2) Select scene \"Scene.001\" and try to toggle to Edit Mode\n3) Get a error\n\nIt is issue or planned (user) error? Getting the error don't full inform an user. Why the error happens? A user may be confused :)\n\nP.S. For fix the error need in scene \"Scene.002\" to disable Edit Mode and than can be to switch to edit mode in \"Scene.001\"\n\n[edit-mode.blend](edit-mode.blend)\n", "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", "Subdivision Surface: Out of memory exception in in post 2.79 versions\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\nWorked: (2.79)\n\nWhen rendering a displacement heavy blend file, We consistently get out of memory exception in blender 2.8x and 2.9.\n\n - Open the attached blend file.\n - Click F12 (Render Image).\n # Wait till it crashes (approximately 6min).\n\nMore info about this blend file:\n```\nResolution: 650px by 650px\nCycles: 10\nAll polygons are triangles.\nOne material with a displacement map on all objects.\nSubdivision modifier with Catmull Clark with 1.0 adaptive value, on all 3 objects.\nSimplify->Render->Maximum Subdivion is equal to 2.\nSimplify->Render->Texture Limit is equal to 8192.\nSimplify->Viewport->Maximum Subdivion is equal to 0.\n```\n\n[Bug-Upload(2.79).blend](Bug-Upload_2.79_.blend)", "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", "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 3.6 problem by rendering scene on EEEVEE (Freeze and crash GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9)\nOperating system: Windows 11 Home\nGraphics card: Radeon Graphics\n\nBroken: (example: 3.6, as found on the splash screen)\n\n\nBlender 3.6 doesn't render the scene as blender demo file in EEVEE\nOpen Blender splash fox of blender 2.90\nRender the scene\nFreeze and crash of blender when rendering on EEVEE\n\n", "bake operator reports uninitialised image that isn't even in use in the shader..\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\ncan't bake due to strange error\n\nopen blend file\nselect object\nselect the baked image texture node in the shader editor\nclick bake in the render setting (leave settings as is)\n\nstrange error pops up saying \n\"uninitialised image \"nightmare0134.png\" from object 'pavement.002'\n\nThis image isn't even in use by the shader.\n\nPS, it seems intermittently not possible to paste screengrabs into this new bug reporter. Also, how to do bullet points and embed video?\n\n", "Set as Background crashes blender instantly.\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080 Ti and RTX 3060\n\nBroken: 3.62\n\nI'm trying to do object tracking. Have tracked an object and clicked Solve Object Motion, then when I click on Set as Background Blender crashes instantly. Trying to load in a 400 frame 1920x1080 png sequence. Blender also crashes if I try to load the background image sequence via the camera properties (Background Images > Add Image).\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "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" ]

[ "Bevel modifier produces erroreous output with \"Loop Slide: On\" setting\nOperating system:\nWindows 10 pro\n\nGraphics card:\nGeforce 3080\n\n\nBroken: \n3.1.0 beta master 2022-02-22\n2746238dde66\n\nWorked: unknown\n\n\nBevel modifier produces erroreous shape with with specific settings.\n\n\nExtrude out 4 faces of the default cube and put a bevel modifier on it. Use settings: Miter outer: Arc. Loop Slide: On.\nSelect an edge loop connected to the \"original cube\" as shown in the scene/screenshot. Nudge the vertices around just a little bit (holding shift while you do it) to see the error.\n\nThe errors happen also with other Miter settings but just not as prominently.\n\n\n\n[bevel_bug.blend](bevel_bug.blend)", "Regression: Bevel operator Loop Slide overshoot\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0 LTS and forward\nWorked: 2.93 LTS\nCaused by 4886ed2863\n\nSee thread for details: 2\n\nLoad the attached .blend in Blender 2.93 and see that there is no overshoot- then load it in 3.x and see a very dramatic overshoot, several orders of magnitude larger than the bevel width is even set to.\n\n[bevel_overshoot_bug.blend](bevel_overshoot_bug.blend)\n\n" ]

[ "Object drivers driven by outliner visibility not updating automatically\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb\n\nBroken: 2.90.0-874af5301cdf (June 20)\n\n\nDrivers on object modifiers that are driven by outliner settings (Hide in viewport, hide in render, etc.) won't work when toggling said outliner settings and has to be forced manually with Update Dependencies.\n\n\n\n\n\n\n - Have 2 cubes in a scene, Cube 1 and Cube 2.\n - Add a modifier on Cube 2 (In my case, a mask, in which Cube 2 is subdivided twice and has a vertex group)\n - Add a driver on the Realtime button on said mask modifier.\n - Have it be driven by Cube 1's \"Disable in Viewports\" button with the following settings:\n\n\nSingle Property\nProperty: Object Cube 1\nPath: hide_viewport\n\n\n\n 6. Disabling Cube_1 from the viewport in the Outliner will not enable the driver on Cube_2's mask modifier.\n 7. Updating Dependencies in the driver editor will correct this.\n\n\n\nAfter updating dependency, enabling Cube_1 will disable the mask in the viewport, although the mask is still enabled in the modifier tab. Clicking once in the viewport will correct this.\n\nExample .Blend File \n[BrokenDriverTest.blend](BrokenDriverTest.blend)", "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", "Caustics not work as expected\nHi,\nI'm going crazy with shadow caustics.\nOddly they work when they turn off.\nIn the attached scene [caustics_not_work.blend](caustics_not_work.blend), if you disabled caustics on lights or objects, they will be displayed, otherwise no caustics will be displayed.", "Proposal for sequencer tool interactions \nThis task is intended to address design issues necessary for adding tool-system tools to the sequencer.\n\nCurrent state:\n\n- Immediately activating actions with keys operates on the selection.\n- The only tool that isn't selection (Blade), operates on the sequence strip directly under the cursor (not the selection).\n\nThe patch proposed to add the Slip tool, was also isolating the strip under the cursor, which I think is overly limiting since it means tools which behave this way can't operate on more than one item at a time. see: [D7063: VSE: Add slip tool](D7063)\n\n----\n\n## Proposes Solution\n\nTools should behave like the \"Tweak\" tool, unless there is a good reason not to *(The blade tool could be kept an exception - although cutting multiple strips vertically might be useful to support too)*.\n\n- A single click selects (with Shift-Click to toggle... etc).\n- A click-drag action runs the tool on the selected strips.\n\nThis means the Slip tool (in this case), would behave much the same as the tweak tool. Where you could quickly operate on many different sequence strips by clicking and dragging on them. With the ability to select multiple then click-drag on any one of them to operate on all strips.", "Camera Gizmo - Turning off Focus Distance has no effect\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.81 (sub 1)\nWorked: (optional)\n\n\nViewport Gizmos - Turning off Focus Distance has no effect\n\n[Based on the default startup or an attached .blend file (as simple as possible)\n\nSelect the camera. Turn on Limits in Viewport Display Panel of the camera. Focus Distance is dependant of this to be on. Now turn off Focus Distance. \n\nNothing changes. Shouldn't the yellow widget disappear? And why hide a widget that you explicitely have to turn on before?\n\n\n\n", "GPencil: A layer used as mask for 2 or more other different layers makes the GP object partially unselectable in the viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74\n\nBroken: version: 2.83.0 Beta\nWorked: /\n\nA layer (let's call it layer A) is masking more than one layer (B and C, for example; so B and C have in their \"mask(s) list\" layer A in it). Doing it makes the grease pencil object unselectable in the viewport unless you click on the shapes that have been drawn on layer A (or, at the precise point where the origin of the grease pencil is located, but only if the origin is displayed in the viewport).\n\nStrangely, saving with \"ctrl+S\" makes everything works as expected, but only until the file is closed. Opening it again and the problem is back.\n\nIn a concrete case scenario, it is a problem since if you use a layer as an invisible mask to hide strokes that go beyond certain limits, it makes it random to select the GP object (or forces to use the outliner).\n\n- Create a GP monkey\n- Create a new layer (layer A) that will mask the 2 already existing layers (\"Lines\" and \"Fills\")\n- In \"Lines\" and \"Fills\" layer, check the \"mask(s)\" option and add \"Layer A\" in each list\n- Back in \"Layer A\", draw a filled shape anywhere\nNow, in object mode you can only select the GP monkey by clicking on the filled form in layer A. You can invert the mask layer in the mask list of the layer named \"Fills\": It seems that it doesn't matter whether the masked parts are visible or not.\n\nBased on the attached .blend file:\n- Open file\n- Try to select the monkey by clicking on the part supposed to act as a mask (the \"selectable\" part in the screenshot)\n- Try to select the monkey by clicking in any other part of the monkey.\n\n{[F8563683](select_bug.png), size=full}\n\n[mask_selection_bug.blend](mask_selection_bug.blend)", "Slow and laggy transforms using the tool pop-up box after clicking the transform gizmo\nOperating system: Windows 10 \nGraphics card: Geforce GTX 1650 Super\n\n3.5.0 (also same issue in 3.4.1)\n\nWhen I move/rotate the gizmo in the viewport with the mouse it is nice and responsive. However, when I use the rotate and move transform value sliders in the transform pop-up box the values are very slow to update and the viewport object being transformed lags quite drastically. Not only when using the mouse to slide value but using the increment arrows too. This seems to only be when using the TRANSFORM_OT_translate.value / TRANSFORM_OT_rotate.value / TRANSFORM_OT_resize.value \nAs a note the viewport side panel Item-Transform (Object.location, Object.rotation_euler, Object.scale) doesn't seem to have this problem and updates as it should, allowing nice responsive viewport updates as the value slider is dragged.\n\n- Unzip attached file\n- Open .blend file\n- Select any object\n- Rotate it with the help of viewport gizmo\n- Now change values from redo panel (notice slowdown).", "Mesh-based armature interaction (\"Mesh Gizmos\", \"Face Maps\")\n# Preface\n\nThe current way of interacting with bones in a production environment is based on Custom Shape Objects, which can disappear inside the mesh, be at a completely different place from the area they control, and in general require a fair bit of design from the rigger and learning from the animator to efficiently use.\n\nUsing the Python Gizmo API, I created a prototype of an alternative system, where we can click on geometry on the deformed mesh itself to select bones and control said mesh.\n\nThe goals of this task are:\n- Gather feedback from animators and riggers.\n- Finalize a design, to the extent that is possible within the limitations of a Python prototype.\n- Find developers who could implement this in core Blender.\n\n### The Prototype: \"Bone Gizmos\" add-on\n\n[Video: Setting up a single bone gizmo](attachment)\n[Video: The add-on in use](attachment)\n\n\nYou can [download the addon](bone_gizmos) as part of the Blender Studio Pipeline. You have to download the whole repository from the repo's home page, then extract the `bone_gizmos` folder into your addons folder.\n\n### Features\nA list of proposed features, partially working in the prototype, although there is plenty of space for UX discussions.\n\n- A gizmo's shape can be:\n - An entire object (in the bone's local space, with the already existing transform offset options applied)\n - A vertex group/face map/any attribute of an object (in world space).\n- Gizmo Colors:\n - There are three states to worry about: Unselected, selected, hovered.\n - Currently, user can specify two colors: Unselected and Selected. Hover-state is indicated by opacity ONLY. Having only one color, or three colors, is something to discuss.\n - The colors can be taken from the bone group's colors, if the bone has a group assigned, or set uniquely on a per-bone basis.\n - Colors should actually NOT be this customizable. Instead, users should be forced into a set of pre-defined colors, that can only be customized at the Theme level.\n- Gizmo Display:\n - A gizmo's visibility is based on the bone's visibility; From user POV, a bone and its gizmo should be a single entity.\n - If the selected object/vertex group cannot be used to construct any faces, draw the edges with line drawing instead.\n- Interaction:\n - Since it's just a prototype, it's currently left-click only, and doesn't account for mouse drag threshold, which is very bad for auto-keying. In the final implementation, it should behave the same way as bones do now, except:\n - Default transform mode: Translate/Rotate/Scale, including trackball rotation, rotating along view, and locking any transformation to 1 or 2 axes. These defaults are defined by the rigger on a per-bone basis, and can be bypassed by the animator with a button press, or in a nuclear fashion by disbaling them altogether as a user preference.\n - Snapping: It is possible, only through Python, to specify an operator name and parameters that should be executed when a gizmo is touched. This can be used for automatic IK/FK snapping. But it would need an interface similar to a Keymap entry, where we can pick an operator and feed it parameters.\n\n\n**Design Questions**:\nWhile making the prototype, I ran into some design questions where the answers aren't so simple:\n- Ways to minimize set-up time? Currently, each gizmo needs a vertex group. That's fine, but may need workflow operators to quickly switch from Pose Mode to Edit Mode on the relevant mesh.\n- How to avoid overlapping gizmos? I think there are cases where they might be necessary, and a system that allows the rigger to create bone layers that are mutually exclusive, would be a potential solution.\n- If there is more than one way to deform some geometry (eg.: Shape Key, Armature, Lattice), how to communicate which out of several potential controls was used to achieve the current shape?\n\nThere might be no perfect answer to all of these, but they are things to keep in mind and mitigate.\n\n### Prototype Limitations\nThese issues are listed just to clarify that these behaviours are known, and would most likely be easy to fix/avoid in the final implementation, but can't really be addressed in the prototype:\n\n- - [ ] Mouse hovering does not take depth into account. This was fixed! [#94794]\n- Visual depth culling stops working when gizmo is being hovered. [#94792]\n- Transparent lines appear between the triangles. [#94791]\n- Currently the mouse movement threshold user preference is not being taken into account, which is terrible when trying to use the system with auto-keying enabled.\n- Performance is poor; Grabbing the vertex positions from the evaluated mesh takes about 2ms per gizmo.\n- Interaction is always with left click and cannot be customized.\n- Gizmo can not be visible during interaction.\n- When the mesh is modified, user must press a Refresh button to synchronize the gizmos.\n- Renaming bones will leave a gizmo orphaned, don't do it! :D \n\nFeedback and discussion welcome! Also about how to structure this document.", "Statistic doesn't update if object deleted due to object data deletion with RMB\nBroken: version: 3.0.0\nBroken: version: 2.80 (sub 75)\nWorked: unsure (didn't find scene statistics in 2.79...)\n\nScene statistic (both in footer and 3D viewport) does not update correctly if object data is deleted with RMB\n\n1. Open default scene.\n2. Make sure you enable scene statistic either in 3D viewport or footer.\n3. In outliner unroll object to show it's object data, i.e. default cude.\n4. Click on object data, i.e. cube mesh, with RMB and delete it.\nObject will be deleted since it doesn't have mesh/camera/light object data. Notice that scene statistic is not updated (number of objects, vertices, selected status etc.). To update it you can select any object or click on outliner (doesn't matter on object or not).\n\nThat works correctly if object is not deleted, i.e. adding subdivision modifier (statistic will update) and then deleting it with RMB in outliner (statistic updated again).", "Grease Pencil drawing only show up when pen is lifted from tablet\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800S ATI Technologies Inc. 4.5.14802 Core Profile Context 21.40.64.30 30.0.14064.30001\n\nBroken: version: 3.6.1\n\n\nGrease Pencil is not the same as before. When I press down to draw something with the pen, it won't show up- until after I lift my pen up from the tablet and then it shows what I drew. This is bad because I can't draw if I can't see what mark I made. It only shows up after and ruins the workflow.\n\n\nI open up Blender, the updated version: 3.6.1. I click: 2d animation to start. Then I click pen as my grease pencil drawing tool. I draw something on the canvas. I press down to draw a shape. Nothing shows up as I press down on the canvas. I lift my pen off the tablet and then I see what I 'drew'. A horrible squiggle line because I cannot see what I'm drawing as I'm drawing. I did not have this problem with the past version of blender that I had: Blender 3.3.1. \n\n~Karina\n\n", "Regression: Image Editor Texture Draw Stops Updating\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0 (probably introduced by {f663a1dc09}?)\nWorked: 3.0\n\nthis was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues -- @lichtwerk)\n\nImage on Image Editor -> Paint does not update when being drawn on at certain close view levels until the viewport is moved \n\nLoad default scene\nSwitch to Texture Paint tab\nCreate new image\nZoom in 7 or 8 times (for reference I am using a scroll wheel that has steps)\nDraw on the image\nIt will sometimes update fine, sometimes stop updating when it passes over a what looks like a UV boundry, that extends off the screen\n\nSee gif where I added a material to it\nSorry if this has already been reported, haven't been able to find a public bug tracker\n[image_paint_bug.blend](image_paint_bug.blend)\n\nThis is the file I (-- @lichtwerk) used on linux to bisect/reproduce on a 1920x1080 display (since this seems to depend on monitor/zoom etc):\n[image_paint_bug_repro.blend](image_paint_bug_repro.blend) ", "Grease pencil eraser settings not loaded on startup when using ctrl+LMB with the Draw tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 2.90.0\n\nWhen first opening a blend file, your eraser settings are set to default when using ctrl+LMB with the draw tool, and only update after switching to the eraser tool and using it.\n\n\n- Open attached file (the Stroke object is selected and the Draw tool activated in Draw mode).\n- Draw a line\n- Erase part of the line using the same tool but with Ctrl selected. Notice how it behaves as if the `\"Eraser Soft\"` brush is used. \n- Switch to the Eraser tool, erase part of the line. Notice how it behaves according to the specified Brush: `\"Eraser Point\"`. \n- Switch back to Draw tool, and hold down ctrl to erase another part of the line, it should now start behaving like the `\"Eraser Point\"` brush.\n\n[eraser bug.blend](eraser_bug.blend)\n\n", "Instancing a collection with an object that has been Disabled in Viewport fails to correctly link in disabled objects breaking \"Make Instances Real\" operator\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0\n\nInstancing a collection into a scene fails to properly link in objects that have been disabled in viewport (henceforth disabled object) using either the \"Disable in Viewport\" icon in the outliner or by setting obj.disable_viewport = True in a script or console. This bug doesn't appear when you hide an object using the H key or obj.hide_set(True)\n\nThis means that if you instance a collection and then \"Make Instances Real\" that the disabled objects will not be transformed with the parent object even if they have been parented to it in the original file and Keep Hierarchy is checked. \n\nThis is a problem because if you have used the disabled object as the operand in e.g. a boolean modifier then as soon as you make a collection real your collection breaks. This is doubly a problem since the default behaviour in the new asset browser is to instance collections into the scene rather than appending them. This bug also affects instancing a collection in the same scene as well as instancing in a collection from an external file. \n\nStart from default file. \nAdd a second cube.\nTransform second cube and place on corner of default cube.\nMake second cube a child of default cube.\nAdd a boolean difference modifier to default cube.\nSet second cube as Object in boolean modifier\nDisable second cube in viewport in the outliner\nInstance collection into scene by dragging and dropping collection from outliner somewhere which isn't the origin.\nEverything appears as it should.\nSelect instanced collection\nSelect Object > Apply > Make Instances Real\nWhile the none disabled cube has been made real the second cube hasn't and if we look in the modifier you can see that the boolean object is still set to the original second cube.\n\nIf instead of disabling the second cube we instead hide it and then instance the collection into the scene the second cube is linked in (although it's also unhidden which is annoying). If we the make this collection real everything works as it should (i.e. the second cube used as a boolean is also made real)\n[link bug.blend](link_bug.blend)", "Transform constraints not working with rigid body simulation\nOperating system: Ubuntu 16.04\nGraphics card: MSI 1080Ti\n\nBroken: 2.80, 337eb8c1de4c, master, 2019-03-27,\nWorked: 2.80, 8beab3e33922, master, 2019-01-21\n\nThe new blender release (as of hash: 936014ea8c74), seems to have disabled constraints from animations. \nIf you set a Minimum Z for a rigid body object, it will ignore that minimum.\n\n - Open the default room.\n - Place the cube at (0, 0, 5)\n - Add “Active” rigid body to the cube\n - Add “Limit Location” object constraint and check minimum Z = 0\n - Press play\n\nIn previous versions, the cube would drop and stop at z = 0, but now it falls to -infinity.", "Sculpt mode pivot ignores object transform when pivot mode is \"Active Element\"\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 3.4.0\nWorked: unknown\n\nWhen the pivot mode is set to \"Active Element,\" the sculpt mode pivot location ignores the transform of the object.\n\n- move and/or rotate default cube\n- Set `Transform Pivot Point` to `Active Element`\n- To see the pivot position, enable `Move` Object Gizmos (in popover of `Viewport Gizmos`)\n- enter sculpt mode. (note that the pivot has moved back to origin)\n- Go to {nav Sculpt > Set Pivot} and run any of the `Set Pivot Operation` operators (such as `Pivot to Origin`, `Pivot to Unmasked`, `Pivot to Mask Border`, etc)\n\nThe pivot location will be relative to the world origin, not the transformed object (which is also active).\n\n---\nTo be honest, it's strange to me that operations such as \"Set Pivot -> Pivot to Mask Border\" generate a pivot that's different for different pivot selection modes in the first place --- it's very unintuitive for the pivot location to not appear at the actual (world space, post-transform) mask border when you run an operation that's supposed to set it to that location. I haven't thought through the nuances of sculpt pivot vs 3d cursor vs pivot mode interaction, though, so maybe there's a good reason for this --- in which case take this as UX feedback that I spent an hour trying to figure out why my pivots weren't working before finding this issue :)\n\nAt any rate, the Active Element behavior seems broken" ]

[ "Viewport gizmos in selection tools not updating.\nOperating system: Windows 10 64Bits\nGraphics card: GeForce GTX 1050 Ti latest driver\n\nBroken: version: 2.80.69 hash:4f6e25280558\n\nswitching between Active tools gizmos and viewport gizmos keeps the manipulators in it's previous position until a second selection...i assume because we have two different and unrelated gizmos!! \n\n\n- Activate transform gizmos in the gizmo popover.\n- Use Active tools manipulators and do transformation.\n- Switch to the selection tools.\n\nThe gizmo center is not updated.\n\n**Attachment**\n" ]

[ "Access violation in `vk_icdNegotiateLoaderICDInterfaceVersion` when putting computer to sleep.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.3 Release Candidate\nWorked: (3.6.2)\n\naccess violation when putting computer to sleep. crash log is created immediately after clicking sleep.\n\n\n1. launch blender.\n2. open a file\n3. save it\n4. put the computer to sleep\n\nEdited steps because it just happened when blender was launched normally. Wasn't saved this time, and was a different blend file.", "Adding Clearcoat freezes Blender with error \"Execution of the command buffer was aborted due to an error during execution\"\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 5700 XT 1.2\n\nBroken: version: 3.5.0\nWorked: Unknown\n\nAdding Clearcoat to a Surface freezes Blender, with Console logs showing only an \"Execution of the command buffer was aborted due to an error during execution. <private>\" error.\n\nOnly appears to happen when using Metal, using Blender in OpenGL mode doesn't have this issue. The issue is also present on brand-new projects with just the default cube.\n\n1. Create new file (Eevee renderer)\n2. Change the Clearcoat amount of the default cube from the Materials tab.\n3. Blender crashes usually within seconds, with the default cube I've found it freezes more easily if you use the sliding mechanism to change the Clearcoatness.\n\n", "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", "Crashing and freezing when working on files with assets\nOperating system: macOS-12.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 580 1.2\n\nBroken: version: 3.5.0\n\nCrashing and freezing when working on files with assets\n\nif I open the demo file cube_diorama.blend the whole system freezes and either crashes or logs out needing to login again.\nevery blender crash a WindowsServer log is created.\n\n cube_diorama.blend never crashed in previous versions of blender for me.\n\n", "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", "Material Tab freeze still\n|**Operating system**:|Linux version 5.11.11-200.fc33.x86_64 ([email protected]) (gcc (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9), GNU ld version 2.35-18.fc33)\n| -- | -- |\n|**Graphics card**:|OpenGL version string: 4.3 (Compatibility Profile) Mesa 20.3.5\n||NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) (prog-if 00 [VGA controller])\n\nBroken: 2.83lts - 2.92.0 (Blender version has been downloaded from the Snap Store).\nThis same freeze also happens if using Blender from the Software store (2.91.2) or via the \"dnf\" command.\nWorked: N\\a\n\nIn Eevee, when opening the material tab, either blender crashes or my entire system freezes up and becoming completely unusable and requires a hard reset.\nwatch?v=te6IaP12Gbg&ab_channel=WhitequillRiclo\n\nPerhaps it is related to the compilation of shaders in the material icon.\n\n- Open the Material tab", "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", "Decals crash Eevee on AMD graphics card\nOperating system: Linux 6.2.7 Manjaro \nGraphics card: AMD 7900XT\n\nBroken: 3.3LTS, 3.4.1\n\nUsing decals will crash blender in Eevee. cycles works\n\nas an example file please see the .blend that was linked here by the decalmachine creator: 66438\n\nThe issue there is unrelated but the file can serve to show the issue I am having. The moment I switch to rendered view or materials preview blender will crash. I see no error message in console. The log files states just: \n\n```\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.space_data.context = 'RENDER' # Property\nbpy.context.scene.render.engine = 'BLENDER_EEVEE' # Property\n \n```\n\n", "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", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "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)", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "Crash when 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" ]

[ "Segfault when accessing Cycles Render Devices preferences with two OpenCL platforms, AMD Mesa Clover and Intel Gen9 NEO\nOperating system: Linux-5.1.20-desktop-2.mga7-x86_64-with-mageia-7-Official 64 Bits\nGraphics card 1 (integrated): Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.1.3\nGraphics card 2 (discrete): AMD VEGAM (DRM 3.30.0, 5.1.20-desktop-2.mga7, LLVM 8.0.0) X.Org 4.5 (Core Profile) Mesa 19.1.3\n\n\nBroken: version: 2.80 (sub 75)\n 2.81 (sub 0)\nWorked: unknown\n\n\nMy HP Spectre x360 laptop has an Intel HD Graphics 630 IGP and an AMD Radeon RX Vega M GL dGPU.\nThe AMD card uses Mesa's Clover OpenCL platform, which Blender does not seem to support (cf. #68009 and [D2171](D2171)).\n\nI built and installed compute-runtime for the Intel Gen9 IGP, and confirmed that it works fine for an example OpenCL program.\n\n```\n$ ./clinfo --list\nPlatform #0: Clover\n `-- Device #0: AMD VEGAM (DRM 3.30.0, 5.1.20-desktop-2.mga7, LLVM 8.0.0)\nPlatform #1: Intel(R) OpenCL HD Graphics\n `-- Device #0: Intel(R) Gen9 HD Graphics NEO\n```\n\nIn Blender, when I access Edit > Preferences > System to review what OpenCL platforms were detected, Blender segfaults:\n```\nThread 1 \"blender\" received signal SIGSEGV, Segmentation fault.\n0x00007fffffffb154 in ?? ()\n(gdb) bt\n- 0 0x00007fffffffb154 in ?? ()\n- 1 0x00007ffff7f836d7 in __pthread_once_slow () from /lib64/libpthread.so.0\n- 2 0x00007fffb306cc54 in ?? () from /lib64/libigc.so.1\n- 3 0x00007fffb2f0dab0 in ?? () from /lib64/libigc.so.1\n- 4 0x00007fffb2e0cfff in ?? () from /lib64/libigc.so.1\n- 5 0x00007fffb2e0e2ef in ?? () from /lib64/libigc.so.1\n- 6 0x00007fffb2dda483 in ?? () from /lib64/libigc.so.1\n- 7 0x00007fffb2ddb298 in ?? () from /lib64/libigc.so.1\n- 8 0x00007fffb2e88eb7 in ?? () from /lib64/libigc.so.1\n- 9 0x00007fffb2e8b873 in ?? () from /lib64/libigc.so.1\n- 10 0x00007fffb9b3b8b2 in ?? () from /usr/lib64/intel-opencl/libigdrcl.so\n- 11 0x00007fffb9b1ebcb in ?? () from /usr/lib64/intel-opencl/libigdrcl.so\n- 12 0x00007ffff7f836d7 in __pthread_once_slow () from /lib64/libpthread.so.0\n- 13 0x00007fffb9b1f472 in ?? () from /usr/lib64/intel-opencl/libigdrcl.so\n- 14 0x00007fffb9b92e7d in ?? () from /usr/lib64/intel-opencl/libigdrcl.so\n- 15 0x00007fffb9af8e9b in ?? () from /usr/lib64/intel-opencl/libigdrcl.so\n- 16 0x00007fffc603b0ba in ?? () from /lib64/libOpenCL.so\n- 17 0x00007fffc603d2a4 in clGetPlatformIDs () from /lib64/libOpenCL.so\n- 18 0x0000000003220776 in ccl::device_opencl_info(ccl::vector<ccl::DeviceInfo, ccl::GuardedAllocator<ccl::DeviceInfo> >&) ()\n- 19 0x00000000031e87c6 in ccl::Device::available_devices(unsigned int) ()\n- 20 0x0000000001548699 in ?? ()\n- 21 0x000000000174f969 in _PyMethodDef_RawFastCallKeywords ()\n- 22 0x000000000174fa25 in _PyCFunction_FastCallKeywords ()\n- 23 0x000000000114f33f in _PyEval_EvalFrameDefault ()\n- 24 0x0000000001803c23 in _PyEval_EvalCodeWithName ()\n- 25 0x000000000174f4a6 in _PyFunction_FastCallKeywords ()\n- 26 0x000000000114dfa3 in _PyEval_EvalFrameDefault ()\n- 27 0x0000000001145530 in ?? ()\n- 28 0x000000000114dfa3 in _PyEval_EvalFrameDefault ()\n- 29 0x0000000001145530 in ?? ()\n- 30 0x000000000114dfa3 in _PyEval_EvalFrameDefault ()\n- 31 0x0000000001145530 in ?? ()\n- 32 0x000000000174f3e6 in _PyFunction_FastCallDict ()\n- 33 0x00000000013e69ce in ?? ()\n- 34 0x00000000014f2c2f in ?? ()\n- 35 0x0000000002d48623 in ?? ()\n- 36 0x0000000002d4ab86 in ED_region_panels_layout_ex ()\n- 37 0x0000000002d4b06d in ED_region_panels_ex ()\n- 38 0x0000000002d4ebf1 in ED_region_do_draw ()\n- 39 0x0000000001517513 in wm_draw_update ()\n- 40 0x0000000001514c30 in WM_main ()\n- 41 0x00000000010c0abe in main ()\n```\n\nI tried to reproduce the issue with a self-compiled build of 036312ecff459f7600361d5aba9a0dba896849a1 (current `master` branch) and it does not crash, though it also does not list any platform for OpenCL.\n\nNote that before I installed intel/compute-runtime, no segfaults happened (but Clover wasn't recognized).\nI now also get a segfault trying to get `system-info.txt`, so here's the report from before installing compute-runtime:\n[system-info.txt](system-info.txt)\n\nComplete `clinfo` output with both platforms installed:\n[clinfo.txt](clinfo.txt)\n\n- Install Mesa OpenCL for AMD dGPU + Intel Computer Runtime for Intel IGP on Linux.\n- In Blender 2.80, access Edit > Preferences > System." ]

[ "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", "unable to use 'grid fill' or 'fill' on screwed object\nOperating system: Window 10\nGraphics card: NVIDIA GeForce RTX 2060 SUPER\n\nBroken: Blender 2.83\nWorked: Blender 2.76 \n\n\nI am trying to create a solid spring using Screw modifier. After applied grid fill, I expected a full capped end of the screwed object, but it turns out to be like figure below. The complete file also attached in this post. Hope to get your response soon. \n\n[screw.blend](screw.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Blender crashes when merging mesh.vertices with a python script\nOperating system: Pop_OS 20.04\nGraphics card: Intel 4th Generation Core Proc \n\n\nBroken: 2.82a\n\n\nLink to stackoverflow question:\n\nblender-crashes-when-merging-mesh-vertices-with-a-python-script\n\nI have reuploaded the question here because I think It could be an error with blender code rather than mine. The steps to reproduce the crash would be creating an icosphere mesh, setting the max_distance variable to 0.3 and just moving nodes nearby to other ones and clicking run_script then. At some point it will close and save an ico.crash.txt. I have attached mine.\n\n[ico.crash.txt](ico.crash.txt)\n\n[#88022.blend](T88022.blend)\n\n[#88022.webm](T88022.webm)", "Linux todo list\nNOTE: this is a direct dump of Install-OS\n\n- [ ] Drives could be auto-mounted as they are in Ubuntu's file manager (selecting an unmounted drive mounts it). see #30518\n- [ ] Support Freedesktop clipboard management, see #38674\n- [ ] Support xkbset accessibility #39047\n- [ ] Support XINPUT matrix for cursor warping #48901 (edit: this depends on a bug-fix in xorg, see task)", "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", "Cycles: principled BSDF thin surface support\n[D2354: Thin surface approximation for Cycles Disney BSDF](D2354)\n\nRebase and benchmark performance impact.", "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)", "Just selecting the IK Pose brush with more than one segment and/or smooth iterations heavily slows down Blender when working with high poly sculpts\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\nThe way it has been explained by Pablo, this brush isn't supposed to be used on high poly sculpts because of performance issues. That I understand. However, at the moment Blender begins to freeze and slow down heavily by just selecting the IK Pose brush with segments and/or smooth interactions active, which is a bit too much. Even if you know about the slowdowns beforehand you can still easily select the brush by accident and have your project slow down to a crawl. There should be a better solution that prevents the brush from slowing down Blender when it is not in use. Just having one segment like the older version of the brush doesn't behave like this.\n\n1. Have a fairly high poly mesh at around 1 million vertices selected in Sculpt Mode.\n2. Select the IK Pose brush with segments and/or smooth iterations activated. You should get heavy slowdowns as shown in the video below.\n[Desktop 2020.01.16 - 21.12.24.01.mp4](Desktop_2020.01.16_-_21.12.24.01.mp4)", "Instancing Performance Improvements\nPerformance of instances in the viewport is much worse than is should be. This task is mean to keep track of possible improvements.\n- [ ] Use a vector or similar data structure instead of an linked list for storing an objects instances.\n- [ ] Don't recompute an object's instance list on every redraw.\n- [x] Store bounding box in geometry so that it is not recomputed for every geometry instance (#96968).\n- [ ] Remove the nested instance limit, avoiding the need to realize instances in some cases\n- [ ] Support passing many instances of the same to the render engine at once to reduce per-instance overhead. ", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "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```", "Image sequence render just stops on Cycles on MacOS Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Ultra 1.2\n\nBroken: version: 3.5.0\nWorked: none, tried 2.93, 3.3\n\nafter about 100 or so frames render just stops, Blender is still responsive, its not frozen or crashed, render bar just sits at %0. I'm doing motion tracking to get some kitbashed 3d elements into the scene. Plays fine in Eevee in the viewport. This is the error I get: CommandBuffer Failed: cycles_metal_shader_eval_displace. Attached ram usage for last 24 hours, I still have plenty of ram!\n\nI've closed the file and retried, several times, never got a render all the way through.\n", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "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" ]

[ "User interface lag\nblender's entire interface is very slow.\ni tried various methods for youtube and the web and also reinstalling \neverything i do is very slow " ]

[ "Workbench refactor causes significant performance regression with workbench shadows\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.83.0\nCaused by c476c36e40\n\nWorked: 2.82a\n\n2.83 solid viewport shading work slowly than 2.82 when shadows is on\n\nReduction of performance in viewport very high in heavy scenes as example scene with sculpts 6 millions of triangles\n\n", "(Grease pencil) Blender freezes indefinitely when drawing using stabilize stroke function. \nOperating system: Windows 10 business 64bit\nGraphics card: Intel UHD 620/630\n\nBroken: both 3.2.2 and the experimental build 3.4.0 alpha\n\n\nWhile drawing using the stabilize stroke function (in blank grease pencil object), after some times blender freezes and stop responding, tested on both an HP prodesk g5 ( I5 8500, intel IGP UHD 630 and 8 GB of RAM) and asus zenbook (I5 7200U, UHD 620, 8GB RAM).\n\nThis only happened on both PCs equipped with intel IGP, I redid the same test on my home PC (I5 9400f, GTX 1060, 16GB RAM) and everything worked fine.\n\nIs this purely a performance issue ?\n\nJust create a blank grease pencil object and directly start drawing using the stabilize stroke function, test setup must be similar or close to the two PCs equipped with Intel IGP.", "Blender 3.6 problem by rendering scene on EEEVEE (Freeze and crash GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9)\nOperating system: Windows 11 Home\nGraphics card: Radeon Graphics\n\nBroken: (example: 3.6, as found on the splash screen)\n\n\nBlender 3.6 doesn't render the scene as blender demo file in EEVEE\nOpen Blender splash fox of blender 2.90\nRender the scene\nFreeze and crash of blender when rendering on EEVEE\n\n", "Cycles rendering world origin extremely slow when using hair particle system with density maps (no, really!)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.1\nTested in 2.93.1, 2.90 on CPU and Nvidia GPU.\n\nCycles is rendering the world origin extremely slowly, even if there is nothing at all in view.\nSeems to be caused by Hair particle system using a texture influencing density.\n\nWatch this video for me walking through the bug:\nwatch?v=3DdTrC-qN2M\n\n[particle_render_slow.blend](particle_render_slow.blend)\nRender image\n\n", "Vertex/Edge Slide stuttering with modifier.\nOperating system: Windows 11\nGraphics card: RTX 3070\nCPU: Ryzen 5900x\n\nBroken: 2.83 and all other.\nWorked: 2.79b\n\nVertex/Edge Slide freezes a lot with subdiv modifier in a relatively simple object.\n\n| With `Use Limit Surface` | Without `Use Limit Surface` |\n| -- | -- |\n| https://projects.blender.orgattachment | https://projects.blender.orgattachment |\n\n1. Import attached fbx.\n2. Add subdivision modifier set to 1 subdivision.\n3. Select the loop in the middle.\n4. Edge slide.\n\n", "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)", "non stop cpu usage after motion tracking.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\nWorked: (unknown)\n\nafter tracking forward one core is running high continuously, and blender becomes unuseably sluggish until restart.\n\n\nimport a 400 frame 1080p png sequence into the motion tracker (I wont upload mine, it's too much bandwidth)\nplace 8 markers at default settings\nclick detect forward\nselect a few of the markers in the dope sheet and lock and hide them\n\nA single core and it's hyperthread will continue to run high endlessly making Blender unusable.\n\n", "GUI: The curser is heavily lagging if GSync is set to windowed and full screen mode\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: Blender 2.79b up to Blender 3.0.0\n\nEverything is as expected if the mode is set to \"Fullscreen only\" (the default)\nBut as soon as you set to it to \"Window- and Fullscreen mode\" the mouse curser will lag heavily.\n\n\n1. Enable GSync\n2. Set it to \"Enable for windowed and full screen mode\"\n3. Save\n4. Open Blender and move the curser\n\n**Workaround** \nJust set it back to full screen mode only.\nOR\nIf you go to nVidia Control Panel > Manage 3d Settings > Program Settings.\n\nAdd Blender under Select Program To Customize. Changing to the following settings can fix it:\n\nMonitor Technology: Fixed Refresh\nPreferred Refresh Rate: Application-controlled\n\n**Desired behavior** \nA fluid curser on the screen even with \"windowed and full screen mode\" enabled", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "blender's UI repeatedly freezes when editing a material while the material settings are open.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.2 Release Candidate\n\nWhen I load any .blend file containing at least 1 material that has image texture maps assigned to it, and I open the material settings, blender's UI will freeze for a while when I change any value or property related to said material, either in the shader editor or the material settings. \n\nThe whole process will repeat whenever you change any value/property in the materials settings or shader editor. The time it freezes depends on what formats and resolutions the textures are. In the below example with 16k textures, it should freeze for about 10 seconds on a fast computer, but if you replace the textures with 8 or 16k PNGs (which are available from the same site where the blend is hosted), the freeze time increases significantly: 120 seconds or more. \n\nThe only way to get it to stop repeatedly freezing is to close the material settings. \nIt will keep happening in render preview or in solid mode, it also happens regardless of whether the material preview in the material properties is enabled or disabled. \n\nThis also happens with 8k and 4k textures, but it's less noticeable.\n\n\n1. download and open clay_floor_001.blend\n2. select the sphere.\n3. open the material settings.\n4. change any property or value in the material properties or in the shader editor\n5. wait for a moment and blender's UI should freeze completely for 10-25 seconds. \n6. after it unfreezes, change any value/property in the materials properties or shader editor again, and the process should repeat.\n\ndownload the blend hosted here: clay_floor_001\nNote: you can also download png versions of the textures for this blend by clicking the little menu button to the top right of the site.\n", "Blender GUI freezes when using activate_init = True\nOperating system: W10 64bit\nGraphics card: nVidia GTX 970\n\nBroken: blender-2.83-71b1ee940bb0-windows64\n\n\nOnce this bug T71112 was fixed I tried to \"use activate_init = True\" in my addon, but I'm still getting Blender GUI to freeze.\n\n* Open up [bugreport.blend](bugreport.blend) and run the script in Text Editor\n* Search for \"Name Location\" operator and run it\n* Type a text and hit OK. An Empty object is placed into the scene, named by what you typed in, but whole GUI becomes unresponsive.\n", "Slow camera view navigation in Cycles rendered shading mode with many instances\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nWhen looking through camera and navigating the viewport (with Lock Camera to View for example), the movement is much slower than a regular perspective view. This happens in rendered shading mode with Cycles, when many object instances are in the scene. Instances can be generated with Geometry Nodes or the old particle system. Also they don't even have to be visible on screen, you could be looking at a single cube somewhere to the side, and the camera navigation will still be slow.\n[camera navigation bug.blend](camera_navigation_bug.blend)\n\n\n - Use the provided file\n - Switch to rendered mode and disable overlays\n - Try looking around\n - Switch to camera view\n # Navigation should be much slower and unresponsive\n\n\n\n", "Redo panel overlaps part of the interface\nIn the image editor, the redo panel covers part of the pixel values. \nWould be nice if such panel could be dismissed, or if it would take into account the possible presence of the pixel value subheader.\n\n[open_image_overlay.mov](open_image_overlay.mov)", "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", "Shadow buffers\nIn order to reduce Shader register pressure during shading phase, we need to transfer the shadow sampling of opaque surfaces to a fullscreen pass.\nWe would store 1 or 2 bits per lights (limiting number of shadowed lights per pixels to 32 or 16) and use noise to dither the shadow shape.\nThe noise would disappear with accumulation.\nThis idea was explored in this presentation [link](view).\nThe issue is that this technique will not work for alpha-blended surfaces that will still need the standard shadow code.\nContact shadow and cascade shadows cost could be reduced. This could be the opportunity to remove support for contact shadows for alpha blend surfaces.\nThis also will permit to have raytraced shadows in the future.\n\nEstimate : 2 weeks\n" ]

[ "blender hangs\ni5 7th gen nvidia 940mx 4 gb 8gb ram\n\nBroken: 2.78a\nit is hanging very much\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Quad View Exiting Behavior\nUsers coming from other software expect Quad View to behave a certain way. Since d71db08f6d, when exiting Quad View we always toggle to the *User Perspective* (top right) view, rather than the one the mouse currently hovers. That differs from what users probably expect (see #43523, #42462, #42368, #43452, #69717).\nIt should not be hard to get the (presumably) expected behavior to work again while addressing the reasons it was removed.\n\nQuick proposal:\n* Maximize the hovered view when exiting Quad View\n* Keep rotation of that view locked if it wasn't the *User Perspective* one\n* Keep the view transform of the *User Perspective* stored so when going back to Quad View, it shows that in the top right.\n\nFor more details, see d71db08f6d.", "Wrong UV after Vertex Slide or moving mesh with Correct Face Attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: unknown\n\nAfter Vertex Slide with \"Correct UV\" checked, or after moving mesh with \"Correct Face Attributes\" UV mapping is wrong. Vertices in UV get split and wrongly offset.\n\n\nExample 1\n1) Open attached Blend file\n[wrong_uv.blend](attachment)\n2) Locate objects plane01_small and plane01_larger. They are identical models with the same UVs. Just one is slightly smaller and one larger and they have different position.\n\n3) Now we will be vertex sliding this vertex to the diagonal one with snapping on vertex on (see picture) with \"Correct UV\" checked. See that the larger model has UV correct, but the smaller one has wrong UV after the vertex slide\n\n4) now go back (Undo) and lets try grab/move with snapping instead of vertex slide. Be sure to have checked ON \"Correct Face Attributes\" and \"Keep Connected\" in Tool Settings/Option - see picture. Now UVs are wrong in both cases\n\n\nExample 2:\n1) Lets look at plane02_01 and plane02_02. They are totally identical duplicated objects (not instances) just with different position.\n\n2) Vertex slide works OK in both cases here, so lets try Grab/move with vertex snapping and \"Correct Face Attributes\" + \"Keep Connected\" ON again. Here result UVs are OK in case of plane01_02 but wrong in case of plane01_01\n\n\n", "Multi-touch gesture: Zooming is reverse in shader editor comparing to viewport\nOperating system: macOS-11.4-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.6.4\n\nBroken: version: 2.93.1\n\nZooming is reverse in shader editor (other 2d editors are fine)\n\n- Hold ctrl and drag downwards\n- This will zoon in the viewport but zoom out in shader editor\n\n- - -\nsteps from original report:\nOn MacOS, by holding CMD and scrolling on the magic mouse you can zoom on the object. the correct behavior is that dragging down should zoom-in. but it's reverse in the shader editor.\nand if I set the \"Invert zoom direction\" in the settings, it will do both of those oppositly\n\n", "Different extrude operations use the scale of the object differently\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.4.0, 2.93\nWorked: - never?\n\nThe four different extrude operations (avaliable on the Alt+E menu) can take or not the scale of the object in consideration when applying the command.\nThe screenshot below, in which all objects were originally simple planes scaled by 2 (in object mode), shows the difference between the operations when trying to extrude it by 1 meter.\n\nAs shown, the \"Extrude Faces Along Normals\" and \"Extrude Individual Faces\" use the scale of the object, resulting in a 2 meter extrusion, which is not the intended value of 1 meter.\nGiven that most actions in edit mode don't take the scale of the object into consideration, I believe these two operations cited above are a bug.\n\n- Using a plane, scale it by 2 (or any number different than 1) and copy it 4 times.\n- In each plane, extrude it by the same amount (i.e. 1 meter), using a different extrude operation given by the Alt+E menu.\n- You should notice the \"Extrude Faces Along Normals\" and \"Extrude Individual Faces\" operations will interfere on the extrusion amount given.\n\nThe result should be the same as the screenshot above and can be checked in the file below:\n[Extrusion Bug Report.blend](Extrusion_Bug_Report.blend)", "Continuous Grab occasionally fails\nOperating system: Linux 5.9.10-arch1-1 (KDE Plasma desktop)\nGraphics card: NVIDIA GTX 980Ti (455.45.01)\n\nBroken: 2.80 - 2.92 master\nWorked: N/A\n\n\nMouse wrapping sometimes fails to transition screen edges, requiring at least a pixel of backpedaling with the mouse. This seems to affect all mouse-wrapping operators. Initially this report was written in terms of Shear, with which I've discovered this behavior.\n\nMesh edit mode Shear operator sometimes gets stuck on the toolbar side of window, showing the system mouse pointer (perhaps due to mouse passing over the toolbar?), needing at least one pixel of motion to the right to untangle it.\n\n[Video ](PeSL2fzKfT4).\n\nThis does not seem to occur if:\n- viewport is not touching window edge\n- window is made fullscreen\n\n\n- Make sure your window is not made fullscreen and that the 3D viewport is bordering window edges\n- Enter edit mode, select all and invoke Shear operator. Move the mouse continuously to the left, until it eventually gets stuck.", "Addon: 3d Viewport Pie Menus. Press-move-release behaviour inconsistency\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\n\n\nBroken: version: 2.92.0 Alpha\n\nName: 3D Viewport Pie Menus (1, 2, 9)\nAuthor: meta-androcto\n\nIn pie-menus Option, who have additional menus do not react to fast action P-M-R or local hotkeys\n[2020-12-16_20-50-47.mp4](2020-12-16_20-50-47.mp4)\n\n- In sculp mode press W and then 2 or M\n", "Particle System Orientation Axis set incorrectly after file load\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken:\n2.82 Beta, 507a331f0182, blender2.8, 2020-01-27\n\nAfter undoing any change, every particle system in the scene resets its orientation axis. To fix this, you have to manually change the orientation axis to something else and back again. There may be other situations where the particle orientation gets reset, but this one is easily reproducible.\n\n1. Open the attached file\n2. Set the ParticleSettings>Rotation>Orientation Axis to Global Z\n3. Shift-A and add a cube (or any change at all to the scene)\n4. Ctrl-Z\nThe particles are not longer aligned on the global z-axis. \n\nAlternatively, it also breaks if you:\n1. Open the attached file\n2. Set the ParticleSettings>Rotation>Orientation Axis to Global Z\n3. Save the file\n4. Close and reopen the file\n\n[ParticleBug.blend](ParticleBug.blend)\n", "Support Viewport roll - around the cursor position\nCurrently view orbit supports zoom-to-mouse-position as a way to rotate and zoom around the cursor position.\n\nView roll however always uses the view center.\n\nWhile low priority, this would be nice to support. See: #70761 (Roll View ignores Auto Depth)", "Inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken:\n3.2.0 Alpha 2022-05-01 a5644f9a28ea\n3.1.2 2022-03-31 cc66d1020c3b\n3.0.1 2022-01-25 dc2d18018171\n2.93.9 2022-04-19 31712ce77a6a\n2.83.19 (can't find build details)\n\nWorked: -\n\nThere's an inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys.\n\nWith Subdivide Edge Ring, no matter what kind of interpolation and profile factor you use, the one applied to all other shape keys will use \"Linear\" and \"0\" respectively.\n\nWith Subdivide, if you use it on the Basis shape key, all other shape keys will inherit half of the transform of the \"smoothness\" setting, and they will be transformed in some undefined manner by the \"fractal\" setting as well. If you use it on non-Basis shape key, in addition to the described behavior with remaining shape keys, the Basis shape key will always use the default settings (smoothness and fractal = 0).\n\n**Exact steps for others to reproduce the error / sort-of-transcript of the video**\nwatch?v=s9dPcdHOlpo\nIf you use the Subdivide Edge Ring, leave the default settings, and go through the shape keys, you can see that the positions of vertices are slightly off between the current/modified shapekey and others.\nHowever, that changes when you change interpolation to \"Linear\" - then they start being the same.\nWhen you go through various options it seems that the only thing applied properly across all shape keys is the number of cuts.\nAll shape keys other-than-the-active-one seem to always be using the \"Linear\" interpolation, and profile factor = \"0\"\nFrom my tests it doesn't matter which shape key you use this action on - it will always have the same effect between the current shape key and all other.\n\nNow, there's something even weirder goin on with the regular Subdivide.\nIf we Subdivide the mesh with default settings, it will look the same in all shape keys - that's great.\nHowever, if we change something, then the mesh across shapekeys will look different.\nAs a general rule, if we Subdivide a shapekey like Key 2, then the Basis will look like it was Subdivided with the default settings instead of the chosen ones (besides the number of cuts), but all other shape keys will also be modified, just in a different way than the active shapekey.\nFor example, if we change the smoothness of our Subdivide, then other shapekeys will look just \"less modified\". If we check the coordinates of the vertices, then we can see that in Key 1 they are transformed exactly half-way to their position in Key 2.\nHowever, if we use the Fractal setting, then the results are different: The Basis is still default-Subdivided, but the vertices of Key 1 are not just halfway there to the positions of Key 1 - they're completely different.\nOn a final note, with regular Subdivide, if, instead of Subdividing Key 2 you did that to the Basis, then both Key 1 and 2 would look like Key 1 in my example. There would be no shape key that stays with default Subdivide settings.", "Snap Increment with \"Absolute Grid Snap\" not working correctly in XY plane\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.Q3.230719\n\nBroken: version: 3.6.2\n\nDescription of error\nWhen moving an object by using Increment Snapping with \"Absolute Grid Snap\" enabled and constraining the plane the object no longer moves with the mouse cursor. It is best demonstrated in the video I have captured.\n\nTo repeat follow these steps:\n1. Make a new default blender scene with an object to move.\n2. Enable Snapping, set to Increment.\n3. Select the object and then \"G\" to move it.\n4. Constrain movement to XY plane and move the object around the 3D space.\n5. Next cancel the transform and Enable in the Snapping Setting, \"Absolute Grid Snap\".\n6. Press \"G\" to move the object once again and contrain its movement to the same plane as before and move the object around.\n7. The object will no longer follow the cursors movement.\n\nAdditionally, this is a recent bug as of this version as tested both 3.4.1 and 3.5 version of blender and they both work as expected, with no Discrepancy.\n", "Fly and walk navigation in AZERTY issues\nOperating system: windows 10\nGraphics card: rtx 3060\n\nBroken: Blender 3.6.1 (Steam)\n\n\nHello,\nIm on a AZERTY keyboard and the problem is that when i change my movements keybinds for fly (or walk) navigation it keeps repeating the action (even if i unpress the key) for the binds that i changed. For exemple i changed \"forward\" key by Z and when i press Z the camera will keep going forward forever.\n\n- Go in the View 3d fly (or walk) modal keymap settings\n- In \"Forward\" replace W by Z, \"Left\" Q by A, \"Down\" A by Q, \"Z axis correction\" Z by W\n- Go in fly (or walk) navigation mode\n- Try to move with ZQSD, A and E\n- Then when you press S,D or E it will work normaly but if you press Z, Q or A and release the key it will keep going in that direction exept if you press the opposit direction key (S for Z, D for Q, E for A)\n\nThanks for paying attention, lov u <3\n\n", "The viewport lock modes are super glitch (in general) with zooms and centering\nOperating system: Windows 10\n\n\nBroken: blender-3.0.0-alpha+master.eae4e2251839-windows.amd64-release\n\n\n\nThe viewport lock modes like 3d cursor or object locking is super glitchy in general which creates a disorienting experience. The main issue is sudden jumps in zooms also sometimes the center or rotation becomes jumpy as well. Some jumps in the video is worse than the others. Bear in mind that I am not zooming intentionally when there is a sudden jump.\n\nThis gets even worse in different scene scales and scene layouts. Here I am demonstrating it only with the cursor but this erratic behavior happens with object locking too. This becomes even worse with a Wacom tablet since it is harder to keep the pen movement as static as the mouse while zooming.\n\n\n- Load the attached .blend file\n- Make sure the viewlock is set to the cursor, and have similar preferences as shown in the pictures\n- Try repositioning the cursor, just move the cursor to different objects.\n- Move the cursor to the surface of another object then try ctrl+single middle click to activate the zoom\n\n\n\n\n\n\n\nTest File:\n[glitchy_lock_modes_28082021_2053_04.blend](glitchy_lock_modes_28082021_2053_04.blend)\n\n[A7ysxb6GVc.mp4](A7ysxb6GVc.mp4)", "Zoom stops at certain level and won't go further\nOperating system: Windows 10\nGraphics card: GeForce GTX 1070\n\nBroken: 2.92, 3.0 alpha\n\nIn this simple model, I cannot zoom my view closer to mesh than I already did. I saved the closest achievable view position in the .blend.\nI can reach further close-ups using some more advanced navigation tools, like dolly zoom, but standard zoom won't let me.\nThe issue is linked to this particular model - if I copy the object (there's only one in the scene) to a new model, the issue is gone.\nThe model was originally saved in Blender 3.0 alpha, only then in stable 2.92. Could it be the cause of this bug?\n\nBased on the default startup or an attached .blend file:\n[zoom issue.blend](zoom_issue.blend)", "Sculpt Mode - Face Set FK, mirror X is wrong when Scale/Translate using Pose brush with Lock Rotation When Scaling\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\nBroken: 2.92, 3.5.0 Alpha\nWorked: Never.\n\n\n- Change to pose brush.\n- Change brush deformation mode to Scale/Translate.\n- Enable brush Lock Rotation When Scaling.\n- Try to pose the hand.\n- The other hand is flipped.\n\n\n\n\n\nThis is the file I'm using:\n\n[20221205_model_human_sculting_pose_brush_using_facecets_0001.blend](20221205_model_human_sculting_pose_brush_using_facecets_0001.blend)\n", "Rigid Body Constraint - Generic Y axis problem\nOperating system: Windows 10\nGraphics card: Gigabyte RX 590 gaming x 8 gb\n\nBroken: 3.2.0\nWorked: I don't know. I haven't tested in previous versions.\n\nWhen using \"Rigid Body Constraint - Generic\", a problem occurs when I restrict rotation in the y-axis. When I try other axes they are fine. I haven't tested this on other versions. Or I'm causing the physics to be miscalculated, I'm not sure. I leave the file below;\n\n**Steps to Reproduce**\n- Open .blend file\n- Play animation\n[Rigid Body Constraint - Generic.blend](Rigid_Body_Constraint_-_Generic.blend)\nVideo: [F13411735](2022-08-22_21-41-37.mp4)" ]

[ "Strange jumping while moving an object using grab and MMB\nOperating system: Windows 10\nGraphics card: GTX 560 Ti\n\nBroken: blender2.80 beta, hash: 1d908bffddb4, build date: 23/01/2019, 17:34\n\n\nWhen using MMB to constraint the movement of an object in Local transform orientation after releasing the MMB the position of the object changes.\nThis doesn’t happen when rotating or scaling. (or moving in Global transform orientation)\n\nCreate a cube, rotate it, grab it and use MMB to move and constraint the cube in some direction. After releasing the MMB the position of the cube changes.\n\n" ]

[ "UI: Excessive cut-off while searching in keymap preferences\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 2.50alpha1 (searchbox for input first appeared)\nWorked: never\n\nWhen searching in keymap text name of a category will be cut too much.\nIt does not happen with add-ons or properties editor search.\n\n1. Open Keymap in preferences.\n2. Resize window. Notice that category name will be cut off only when it really doesn't have any spare space.\n3. Start searching for anything, for example `grease pencil`.\n4. Resize window. Now category name will be cut off way too easily, having spare space several times largen than it's full text.\n[Excessive cutoff2022-01-19 12-55-36.mp4](Excessive_cutoff2022-01-19_12-55-36.mp4)", "Shortcuts for Tools (design task)\nOne of the major issues with the tool system, is that switching tools isn't easy enough using the keyboard with the default keymap. \n\nWe would like to introduce a way to make the keyboard shortcuts switch tools, without having to click on the toolbar, or opening menus. Here's how we think we can solve it:\n\nWe want to leverage muscle memory for shortcuts users already know, such as G, R, S for the transform tools, as well as K for Knife, Alt-S for Move Along Normals, and so on. \n\n## Leader Keys\nTo do this, we use the concept of *leader keys* (also known as *chained keys*). This makes it so that tapping (but not holding) a modifier will change the following shortcut. In this case we think we will use Alt to switch tools. \n\nIn practice, this means users will tap Alt, then G to switch to the Move tool, and so forth.\n\n## Visual Feedback\nWe want to make it obvious that a leader key has been entered, so that users know that the following key stroke will differ from normal. We do this in a few ways:\n\n**Status Bar**\nHere we can see the leader key, plus the shortcuts:\n{[F7753731](Screenshot_2019-09-15_at_21.50.34.png), size=full}\n\n**Toolbar**\nAfter the leader key is pressed, we can also display the hotkeys inside the toolbar buttons. This gives a more direct association with the tools in the toolbar and their corresponding shortcut. \n{[F7753735](Screenshot_2019-09-15_at_21.43.58.png), size=full}\n\n## Implementation\n\n- Pressing Alt and releasing (without pressing another key) would prompt for input.\n - Pressing any of the mapped keys would activate the tool immediately. \n - Pressing any key not mapped - such as painting or using mouse buttons to pan the view - would cancel the prompt and perform the action (preventing unintended leader key press from Blocking other actions). Pressing escape would also cancel.\n\n## Precedents\n\n- Firefox supports accessing menu this way (Tapping Alt, then F opens the file menu).\n- Typing in accent characters on macOS uses [leader-key like functionality. ]()\n- Spacemacs relies heavily on a [leader key ](QUICK_START.html#the-leader-keys).\n\n", "Action Editor Name/Title field causing crashes, which further causes total loss of all stashed action data.\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.4.1\nWorked: Never\n\nThis is happening in a very specific file (I have similar files with similar models, which this does NOT happen for) - I have 2 monitors: one has a window for the layout & timeline, and the other monitor has a single, docked window for the Action editor, the graph editor, and NLA editor. So in the ACTION editor, I try to set a name in the in the title field for a new action (to be \"stashed\" for later use) - and the moment I hit enter or click out of the field, Blender crashes immediately. I don't even have to change the default name for this to occur. This happened a dozen or so times, and somewhere in that series of crashes, all the actions I had made and \"stashed\" were deleted from the file entirely, and as far as I can tell, are completely lost. Upon closing the docked windows, and again separating windows from within the blender window on my MAIN monitor, opening up the action editor again and going through the same process, this problem does NOT persist. So the crashing can be addressed with work-arounds, but the total loss of the existing action data is a big concern, as I cannot predict when this issue will happen again. See videos linked in the google drive file below. (Honestly not sure if the google drive file will replicate this issue, but I redownloaded it from google drive, and it opened the graph/nla/action editor in a separate docked window, and the bug persists - so it SHOULD be repeatable on your end too). In any event, the dumping of stashed action data I believe is the biggest issue to address here, since the crash problem can be worked around, although the crashing in and of itself is obviously a concern, since it seems to have been the cause of the loss of action data.\n\nIn the below Gdrive folder there are: 2 videos, 2 images, and the original .blend file that this problem persists within.\n\n1Gi62lbXBRlkQxFB2m7E5t5pjkqeQQrPY?usp=share_link\n\n[#104293.blend](T104293.blend)\n- Open file\n- In window with action editor, rename the action\n\nBlender should crash.\nIt doesn't crash if asset browser window is activated or if file is saved to different location.\n", "Auto Hide Channels\nThe problem:\nWhen working on the graph editor, more often than not you concentrate on 1 curve at a time, it's imperative that getting from selecting a control/object to the desired curve takes as little steps as possible.\n\nLets set an example considering the graph editor is already visible like this:\n![2020-10-27 21_44_32-Blender_ [C__Users_elect_Desktop_RUN_.blend].png](2020-10-27_21_44_32-Blender___C__Users_elect_Desktop_RUN_.blend_.png)\n\nCurrently to get to a particular channel like TY an animator has to:\n\n - select the desired controller\n - un collapse the \"bone\" in the channel panel in the graph editor.\n - click the desired channel\n - press shift H to hide all the other channels.\n # start working.\n\nThen if he wants to move to an other channel he needs to:\n\n - press alt H to unhide the rest of the channels.\n - select the new channel\n # hide the rest of the channels with shift H again.\n\nAlternatively an animator can turn on the option \"only selected curve keyframes\" which will dim the secondary channels instead on a similar fashion that we're looking to achieve with \"auto hide channels\" but this option has 2 issues.\n\n - its stored in the file hence the animator needs to turn it on every single time he wants to use it, instead of it being a permanent setting.\n - given that it only lowers the opacity on the rest of the curves, they are still being drawn which could be a win in performance when you have several bones / objects selected.\n\nSolution:\nWith an \"Auto Hide Channels\" option we can set in the user preferences to auto hide channels when the user clicks the name of the channel the result will:\n\nReduce the first encounter to just 4 steps.\n\nAnd the latter and more common exercise of changing from channel to channel which happens hundreds if not thousands of times during the production of 1 shot, will convert those 3 steps into 1 which would be just clicking the right channel.\n\n\n---\nThis is inspired by the \"auto lock\" channels created by the Grease Pencil team to aid not drawing in the wrong layer and will make it easier for the user to focus on one curve at a time which is what you normally want to do. \nIt'll improve performance as more often than not you will be only drawing one curve at a time.\n", "Asset Browser: F2 renames active object instead of the selected asset\nOperating system: Linux-6.5.3-gentoo-r1-x86_64-AMD_Ryzen_9_5950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.104.05\n\nBroken: version: 4.0.0 Alpha\n\n\nSpoke about this with @JulianEisel , it's not exactly a bug but I have his permission to report this regardless.\n\n- make some datablock an asset\n- go to asset browser and select it\n- press `F2`\n\n", "AlembicObjectPath has a fixed-size char[]\nAlembicObjectPath (see `DNA_cachefile_types.h`) has a fixed-size char- [ ] buffer. \n\n> In 3128600a8a#142412, @LazyDodo wrote:\n> if the object path can be arbitrarily large it's gonna be a matter of time before someone comes with a file with 4097 byte object path, why not just allocate the ram you need? \n\n\nI think that's a good idea, and that's what this task is for.\n", "Group nodes starting with \".\" is no longer hidden from search\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.4.0\nWorked: 3.3.0\n\nGroup nodes starting with \".\" is no longer hidden from search.\nNot sure if this is a change made or an actual regression bug.\nSometimes we don't want some group nodes to be shown, such as some group nodes inside a group nodes.\n\n\n[Search.blend](Search.blend)", "GP: File with linked collection is too big when there's a custom property driving layer Location\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.3.1\n\nDiscovered this potential bug while animation some characters in a cut-out form using Grease Pencil to draw the characters.\nWhen we have a Grease Pencil character in a blender file, then we Link it's collection and we apply a Library Override (in order to animate it in a new file), the file size is almost the same from the original file, instead of being small. I noticed it happens when the original character have a Custom Property, and this Custom Property is in use to drive some other property as Location of a GP layer.\n\n\n\n\nI could provide 4 files as examples attached.\n\nA) The file \"A CHARACTER.blend\" has one GP draw with a Custom Property (called MOVE) driving his only GP Layer Location. The file \"A CHARACTER LINKED.blend\" has the linked character with a library override. As you can see, the file size is almost the same (4 MB) even though the liked character has nothing other than the linked character.\n\nB) Almost the same, the only difference is the file \"B CHARACTER without driver.blend\" has the same Custom Property but it's not used to drive anything (just deleted the driver from GP Layer Location). And as you can see, the file \"B CHARACTER without driver LINKED.blend\" has only 758 KB size.\n\nImportant to notice that just delete the driver from the files in the A example, not necessarily will make the file size goes down. I couldn't figure out why it worked only sometimes.\n\n- Create a heavy GP Draw and put it in a Collection called \"CHARACTER\" (heavy only to make more clear when the file size goes up);\n- In \"Object Properties\" tab, create a Custom Property;\n- In this Custom Property, do a \"copy as a new driver\" command;\n- Go to \"Object Data Property\" tab, select the GP Layer, go to \"Transform\";\n- In \"Location X\" do a \"paste driver\";\n- Save the file.\n\n- Create a new blender File;\n- Go to File -> Link...\n- Select the blender file created before and Link the collection with the GP draw.\n- Go to the menu \"Object\" -> \"Library Override\" -> Make;\n- Save the file;\n- This second file should have almost the same file size from the first file, instead of be a light file to animate.\n\nThis steps was used to reproduce the files \"A\" attached. The \"B\" files only lack the driver option, and the file size is way smaller.\n\n\n\nA)\n[A CHARACTER.blend](A_CHARACTER.blend)\n[A CHARACTER LINKED.blend](A_CHARACTER_LINKED.blend)\n\nB)\n[B CHARACTER without driver.blend](B_CHARACTER_without_driver.blend)\n[B CHARACTER without driver LINKED.blend](B_CHARACTER_without_driver_LINKED.blend)\n\n", "UI: Wrong text cut-off without \"…\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 2.80 (where `…` first appeared)\nWorked: never\n\nWhen text can't fit into designated area Blender will cut off last characters and adds `…` at the end. However in some cases it will not add it, instead plainly showing incomplete test.\nAdditionally with long text and limited space Blender will cut middle of a text like this: `start text … end text`. Issue also affecting this case and sometimes will make text to look like this: `start text … end tex`, without last letter.\nThat works for other areas like `Properties Editor`.\n\n1. Open preferences, go to `Keymap`.\n2. Resize window carefully and look how end of a text is behaving.\n[Wrong cut-off with ...2022-01-19 14-02-00.mp4](Wrong_cut-off_with_...2022-01-19_14-02-00.mp4)\n", "Weight paint vertex select difficult to see (depends on surface color)\nThis is an issue since 3.2x\n\n**Short description of the issue**\nVertex selection is difficult to see in some cases, depending on the surface color.\n\nChanging the view-port shading \"Color\" can make the unselected vertex color match the selected vertices color.\n\n<video src=\"attachment\" title=\"screenshot.webm\"></video>\n\n**Exact steps for others to reproduce the issue**\n- Open attached .blend file.\n", "GPencil: A layer used as mask for 2 or more other different layers makes the GP object partially unselectable in the viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74\n\nBroken: version: 2.83.0 Beta\nWorked: /\n\nA layer (let's call it layer A) is masking more than one layer (B and C, for example; so B and C have in their \"mask(s) list\" layer A in it). Doing it makes the grease pencil object unselectable in the viewport unless you click on the shapes that have been drawn on layer A (or, at the precise point where the origin of the grease pencil is located, but only if the origin is displayed in the viewport).\n\nStrangely, saving with \"ctrl+S\" makes everything works as expected, but only until the file is closed. Opening it again and the problem is back.\n\nIn a concrete case scenario, it is a problem since if you use a layer as an invisible mask to hide strokes that go beyond certain limits, it makes it random to select the GP object (or forces to use the outliner).\n\n- Create a GP monkey\n- Create a new layer (layer A) that will mask the 2 already existing layers (\"Lines\" and \"Fills\")\n- In \"Lines\" and \"Fills\" layer, check the \"mask(s)\" option and add \"Layer A\" in each list\n- Back in \"Layer A\", draw a filled shape anywhere\nNow, in object mode you can only select the GP monkey by clicking on the filled form in layer A. You can invert the mask layer in the mask list of the layer named \"Fills\": It seems that it doesn't matter whether the masked parts are visible or not.\n\nBased on the attached .blend file:\n- Open file\n- Try to select the monkey by clicking on the part supposed to act as a mask (the \"selectable\" part in the screenshot)\n- Try to select the monkey by clicking in any other part of the monkey.\n\n{[F8563683](select_bug.png), size=full}\n\n[mask_selection_bug.blend](mask_selection_bug.blend)", "Linked data-block has \"pointer\" property still active\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Probably never\n\n\n\n[torus.zip](torus.zip)\n\nOpen torus.blend. It has a linked collection containing the selected object `Torus`.\n\nAs you can see in the image, the \"Object\" rna properties (parent, and the array modifier one) are both active:\n\n{[F13627034](image.png), size=full}\n\nIn fact you can even click on the property to change it (the popup show up, but clicking on it at least doesn't change it):\n\n{[F13627039](image.png), size=full}", "New Icons: Global Menus & Animation Editors\n**Big Picture**\nThese 37 new icons provide functionality and visual feedback for menu commands primarily found in the Graph Editor, but some of the icons would be used in other parts of Blender. They adhere to the visual language of the current icons and are pixel-perfect where possible for greater UI contrast & clarity at small sizes.\n\n**Use cases**\n* Users trying to understand text-only commands (e.g. Jump to Keyframes, Sample Keyframes)\n* Commands can be identified by one symbol as opposed to long strings (e.g. Bind Cameras to Markers, Revive Disabled F-Curves)\n* Disambiguating commands (e.g. Duplicate [Keyframe] / Duplicate Marker)\n* Providing Blender community & Add-On developers more icon options\n* With Blender-wide icons, users can quickly understand tools' functionality (e.g. Box Select, Circle Select)\n\n**Design**\nHere is the latest design with User Interface feedback incorporated\n\n\nAnd here they are in context:\nGraph Editor - View\n\n\nGraph Editor - Select\n\n\nGraph Editor - Marker\n\n\nGraph Editor - Channel\n\n\nGraph Editor - Key\n\n\n3D Viewport - Select\n\n\nImplementation patch:\nD14662", "Drivers of sub-ID properties do not get removed along with the sub-ID\nBy \"Sub-ID\" I mean things like Modifiers, Constraints (bone & object), custom properties, shape keys, bones, VSE strips, etc. Not sure how to get a complete list of these types of things.\n\nWhen one of these things, such as a modifier, is removed, drivers on its driven properties are not removed. This makes it easy to leave behind broken drivers that now target nothing. These can be cleared up in the Driver Editor UI fairly easily, but the fact that we must do so is annoying. Experienced users end up learning that you can't just remove a modifier or constraint without removing its drivers first - Just to save you a trip to the Driver Editor.\n\nForgetfulness in this habit results in console warnings, which in a production environment trickle down from assets to shot files, and contribute to the users' sense of \"console warnings aren't important, I will ignore them\".\n\nI always thought this was a known issue but @Sergey told me it's fixable and that I should make a report. Here ya go! \n\nThis would be a really, really welcome improvement for the studio and probably the whole world.\n\n", "Avoid Dynamic Menu Text\nThis tasks proposes that dynamic menu should not be used (with some exceptions, below).\n\nExamples of dynamic menu text include terms generated by blend-file data and text that changes based on the current selection.\n\n\nThis causes the following problems:\n\n- **Visual Noise**\n\n```\nTo take this to some logical extreme, imagine we could do this everywhere:\n```\n\n - `Delete \"Cube\"`\n - `Parent to \"Sphere.001\"`\n - `Save \"my_filename.blend\"`\n - `Revert \"my_filename.blend\"`\n\n```\n... etc.\n```\n\n```\nThis adds more information in the interface in a way that's not very helpful.\n```\n\n```\nWhen using an interface users learn to quickly identify unique terms.\nHaving the text changed based on data-block names means you have the hint that something is changing when you visually scan the menu, when the changes are only based on the selection.\n```\n\n```\nAside from the distraction of changing text, some names are already quite long, adding data / operator names as part of other actions means we will end up with awkwardly cramped text in some cases.\n```\n\n- **Unpredictable Menu Search**\n\n```\nIf data-block names are included in menu item labels, search will give less predictable results as the names of data in the scene will be included in the search too.\n```\n\n```\nSo if you know searching for a short combination of letters can activate a tool, this change means there would be a chance that typing in this sequence will perform a different action based on the current selection.\n```\n\n- **Complicates Documentation**\n\n```\nIf you have to clearly describe steps which include dynamic names, it means you need to\n```\n\n```\n`Edit -> Rename \"{active object or bone name}\"`\n```\n\n- **Complicates Translations**\n\n```\nWe need to take care to handle translations properly, currently this patch doesn't account for this *(translating the operator names but not the data-names).*\n```\n\n- **Complicates Menu Memory**\n\n```\nCurrently popup menus remember the last action based on the text,\nwith dynamic changing text, our menu hashing function `ui_popup_menu_memory` would need to somehow support this too, at least if this is used for menu items in popup menus.\n```\n\n**Exceptions**\n\n- Menus where their only purpose is to list data-blocks,\n```\nthe \"Add -> Collection Instance\" menu for example.\n```\n\n- Undo / Redo may include the name of the action they're operating on.\n\n\n" ]

[ "Material names unreadable when linked from file with long name.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83\n\nMaterial names unreadable when linked from file with long name.\nWhen i want to browse the linked materials i can´t read the names when the name of the linked file is too long.\n\n\n- Link the material called \"Material Test\" from the attached file.\n- In the default cube, browse the materials to search for the \"Material Test\".\n- Compare the material name in blender 2.83 and 2.90.\n[Very very long name linked file.blend](Very_very_long_name_linked_file.blend)\n" ]

[ "Cycles doesn't render smoke properly with adjusted clipping distances\nWindows 10 / AMD Radeon 6800 Series \nBroken: 2.79.1 1802d14\n\nI need to render a cross section of a smoke simulation. I set up the simulation and adjust the start/end clipping distances of the active camera to the desired values and in OpenGL viewport it works fine, renders exactly the cross section I want.  \nHowever, when I go into cycles and render it out, I get nothing: [*The second camera next to the active one is just for the convenience sake, mimicking the clipping values. Cycles behaves the same without it.*] \nI know that the materials are working fine because I can render it outside the camera's view: \nIf it helps, here's something else that I've found. When the end clipping distance goes beyond the Flow mesh (emitter) I get this weird result: \nAnd when it (end clipping distance) goes even outside the adaptive domain box, then it renders the smoke: \n[smoke.blend](smoke.blend)", "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", "Vertex paint. Brush mode Color gives only black.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 17)\n\nIt ruins colors to black with any strength.\nExpected: full or partial replacement of Hue and Saturation and keeping Value/Luminosity.\n[2020-05-22_16-52-13.mp4](2020-05-22_16-52-13.mp4)\n[untitled.blend](untitled.blend)", "Cycles smoke is not exported to render without baking\nOperating system: win 10\nGraphics card: geforce 1080 ti\n\nBroken: blender-2.80-4488056f3d9-win64\\\nWorked: (optional)\n\nSmoke is visible in viewport but not in render.\n\n\n- Select default cube.\n- Run quicksmoke\n- Select the domain and in the simulation cache settings choose `Replay`(step added to be reproducible in mantaflow)\n- Run play so you get some smoke.\n- Press f12 (or switch to cycles and press f12).\n- Renders cube but no smoke.\n\nManually setting it up gives the same result.", "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)", "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.", "gpu.types.GPUOffscreen renders nothing when samples > 0\nOperating system: Linux-5.3.0-55-lowlatency-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83.0\nWorked: None known 2.90 alpha has same issue\n\nOffscreen rendering from Python fails if GPUOffscreen buffer is created with any number of of samples > 0. If samples > 0, nothing is drawn (nor is there any error)\n\nRun the small script in the attached .blend (it is the sample script for offscreen rendering from the documentation but with samples>0)\nThe generated image is empty.\n\n(full system info also in .blend in text buffer system-info.txt)\n[MSAA bug.blend](MSAA_bug.blend)\n", "Render will not load anything but a cube silhouette in a new untouched file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.14830 Core Profile Context 21.09.04 27.20.20904.1\n\nBroken: version: 3.6.2\n\nSo, when I open in a new file, new to blender and following a tutorial, I go to render the cube immediately, but instead of a gray cube with shading, it is a transparent silhouette. I have touched nothing, just installed from steam, and opened. Then that, IDK what's going on with it.\n\nIDK what to put here, since I didn't do anything.\n\n\n", "adding outflow object removes smoke from viewport\nOperating system: Windows 10\nGraphics card: Geforce RTX 2060\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nversion: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0d7\nversion: 2.91.0 Alpha, branch: master, commit date: 2020-10-02 22:11, hash: 743eca0f316d, \n\nWorked: (newest version of Blender that worked as expected): \nunknown\n\nA simple smoke simulation with a plane inflow works fine. When a torus shaped outflow mesh is added the smoke is not calculated.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Start Blender\n2. Add Fluid Domain to default cube\n3. Add 0.5m plane mesh\n4. Add Flow->Inflow to plane\n5. Cube-Fluid->cache->type->Modular\n6. Cube-Fluid->cache->Frame end->50\n7. Bake data\n8. Verify smoke is seen rising in view port\n9. Free data\n10. Add torus mesh object, major radius 0.8, minor radius 0.1\n11. Add Flow->Outflow to torus\n12. Free data\n13. Bake data\n14. Verify that smoke is not seen in view port (this is assumed a bug)\n\n[#81423.blend](T81423.blend)", "Can't display .blend thumbnail in the Windows explorer\nwindows 7 64 bit\n\nBroken: blender 2.75a c27589e\n\nCan't display .blend thumbnail in the Windows explorer!\n\nboth v2.75 and 2.75a all can't display .blend thumbnail in the windows explorer! I have install and uninstall again and again ,it's still don't display thumbnail. \n", "Quick smoke vorticity is broken.\nOperating system: Windows 10.\nGraphics card: NVIDIA GeForce RTX 2080 Super\n\nBroken: (version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29c0, type: Release \nThe same is on experimental 2.91\n[system-info.txt](system-info.txt)\n\nI'm not sure, but in video tutorial of Blender 2.7 is working correctly. Link to vid: watch?v=BhjK-6t9Gqs&t=2m10s\n\nWhen you add vorticity to smoke sim it does something crazy,video with 0 vorticity:\n[smoke_novorticity.wmv](smoke_novorticity.wmv)\n\n\nWith vorticity value of 3 here is what happens:\n[smoke_vorticity.wmv](smoke_vorticity.wmv)\nIt happens a bit differently on different strength but once you add any vorticity it goes wrongly.\n\nThe file is simple - adding icosphere, make couple keyframes to animate it. Add quick smoke, adjust domain. For emitter make temp.diff -1, enable initial velocity. For smoke domain set vorticity to 3.\n[smoke_voticity.blend](smoke_voticity.blend)", "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", "Smoke does not leave through open domain boundary\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.90.1\nunknown\n\nSmoke does not leave through open domain boundary\n\n\n\n1. start blender\n2. add fluid domain to default cube\n3. add border collision to bottom\n4. Change cache type to Modular\n5. Change gas bouyancy density to 0 and Heat to 0\n6. Add 0.5m mesh plane\n7. add fluid->inflow to mesh plane\n8. set inflow initial temperature to 0\n9. enable initial velocity to mesh plane\n10. set initial z-velocity to -1m/s\n11. bake fluid domain\n12. See how smoke is crawling up along side walls despite that border collision is not enable for these walls. I see this as a bug.\n\n[#81442.blend](T81442.blend)\n \n", "Eevee Attribute Rendering is Having Problem with Scene Referred/Open Domain Data\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: None\n\nEevee attribute rendering fails to render scene referred/open domain data\n\n\nAnd here is Cycles that does it properly:\n\n\nBased on the attached .blend file\n\n1. Turn on Rendered view, see how Eevee clips all values above 1 and the sweep end up with the six colors on the right side and it doesn't go to white at all (The Notorious Six)\n2. Switch to Cycles and see how Cycles renders open domain data properly\n\n[Eevee Attribute Rendering Open Domian Bug.blend](Eevee_Attribute_Rendering_Open_Domian_Bug.blend)\n\n[Eevee Attribute Rendering Open Domain Bug.mp4](Eevee_Attribute_Rendering_Open_Domain_Bug.mp4)", "Creating over 2047 instances overrides object color viewport display\n[pointcloud-object-color.mp4](pointcloud-object-color.mp4)\n\n[#93245 cleaned up.blend](T93245_cleaned_up.blend)\n\n**Steps to Reproduce**\n- Open file\n- Toggle switch node or increase the \"False\" value to 2048\n\nAnother file that demonstrates the issue:\n\n\n### Original Report\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nIt seems that a geometry node scattering system created on one object can somehow change the display color of other point-cloud type objects, see gif \n\nIf we change the density of a scatter system assigned to this blue object, it can somehow change the display color of the other scatter object with a point cloud type\n\n\nIn file below, enable the node \n\n[bug.blend](bug.blend)\n\n\n\n\n" ]

[ "Smoke simulation doesn't work in viewport\nWindows 7 64-bits, Intel Core i5-2410M, Intel HD Graphics 3000 \n\nBroken: Blender 2.77 RC2 1e1118e\n\nSmoke simulations doesn't shows in viewport\n\nOpen the .blend file and bake the simulation\n\n[untitled.blend](untitled.blend)", "Solid Black smoke domain\nMac OSX 10.11.3\nIntel HD 3000\n\nBroken: 2.77 RC2 1e1118e\nWorked: 2.76b f337fea\n\nFire and Smoke domain show as black solid instead of the actual simulation.\n\nI added a UV Sphere, hit space and typed 'quick smoke' as usual and the simulation inside the domain turns to be completely black. I started getting this problem since the introduction of OpenVDB.\n\nBlend file: [smoke_sim_test.blend](smoke_sim_test.blend)\n\nViewport screenshot:\n\n" ]

[ "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "Denoise + Pixel Size + Render Region = Artifacts in Viewport\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: \nNVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84, \nNVIDIA GTX 1080.\nOptix is used.\n\nBroken: version: 3.2.0 Alpha\nWorked: Don't know.\n\nWhen the pixel size for render preview is increased, (2X, or 4X), Render region is set, and viewport denoiser is turned on, the viewport render gives weird artifacts.\n\n\nTurn on render preview, and zoom in this file:\n[Pixl Size Denoise Render region.blend](Pixl_Size_Denoise_Render_region.blend)\n\n", "Erase Alpha in vertex paint not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\nWorked: latest 2.7 nightly build date 2019/06/27\n\nErase Alpha not showing in viewport.\n\ngo to vertex paint set mode to erase alpha and when painting nothing happens.\nalso found no ways to use the alpha data.\n\nVertex Alpha painting are needed for asset creation on some game engines like creation engine.\n", "Image Editor: Viewing a value buffer could use incorrect channel selector\nThis is a long outstanding issue in the image editor that should be fixed.\nWhen rendering a value based AOV and switching in the render result to the AOV would render incorrect as the wrong channel selector is selected (Still Color + Alpha).\n\nThis is also visible when reading single channel images or OpenEXR files.\n\n**Solution**\nAdd an option to view `Value` option to the channel selector and change RNA get/set/itemf + add support of this to the image engine.", "Objects with \"In Front\" don't appear when overlays are reenabled until viewport update\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBut works on:\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.91.2\n\nMight be the same as #102199 (Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)) (which was bisected down to 0f95f51361)\n\nWhen an object (specific ones) is set to be displayed in front of everything else, it will not come back immediately when reenabling the overlays. This happens only in solid shading mode as far as I can tell.\n\nThe objects affected by this are first off all objects which have some kind of lines, so camera, lights, the wireframes of meshes, outlines of reference images, empties, ...\nThen there is also the armature which is special in the way that it is rendered solid, but it also vanishes just like the lines.\n\n1. Add an armature\n2. set it to In Front in Armature > Viewport Display\n3. toggle the viewport overlays on and off (that button next to x-ray)\n4. if your rendering was set to solid shading, the armature should be gone now\n5. rotate the view, the armature will reappear\n6. you can do the same with the default camera and light and on the cube if wireframes are enabled (globally or locally on the cube) \n\n", "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", "Grease Pencil phasing through objects even when 3d location is selected \nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2060 SUPER\n\n3.1.2\n\nGrease Pencil strokes that should be under the floor/behind objects are phasing through with a weird grainy texture. Looks perfectly fine in viewport rendering but when I render an image/animation it looks weird. Not sure what im missing or if its a bug?\n\n**Blender project**\n[clothtest.blend](clothtest.blend)\n\n", "Black artifacts on smooth surface in 2.79 64bit daily build\nOperating system: Windows 10\nGraphics card: RTX 2080Ti\n\nBroken: blender-2.79.0-git.d7cecc2ba3f6-windows64\nWorked: 2.79b\n\n\nThe software renders black artifacts on a smooth surface. This happens both in the rendered preview and in the final render. Artifacts disappear when smooth is not applied.\n\n\n\n\n\n\n\nJust go in rendered preview mode in the editor, or just F12 to see the artifacts in the render.\n\n[bug report.7z](bug_report.7z)", "viewport problem\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\n\nwhen I move inside the viewport, some objects become hidden.\n\n", "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", "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)", "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", "Alpha Blend material has inconsistent behavior with Geometry nodes\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nAlpha Blend material renders differently on the object, which is referenced inside Geometry Nodes tree of another object, despite this another object is already hidden and has muted GN modifier.\n\nIn attached file:\n* Remove/Select *Shell* object inside GN tree of object *Mesh*\n* Activate/Deactivate *Viewport Disable* for *Collection* or object *Mesh*\nIn both cases material becomes transparent or not\n\n", "Material setting \"show_transparent_back\" (Show Backface) gives weird results\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nMy materials are messed up by having blend mode set to \"Alpha Blend\" and \"Show Backface\" set true.\n(The checkbox for \"Show Backface\" pops up if a materials blend mode is set to Alpha Blend\")\n\nIs this normal behaviour?\nThe intend here was to see every side of the cube with a bit of transparency.\n\n[ShowTransparentBackBug.blend](ShowTransparentBackBug.blend)\n1. Add a Cube (subdivide a few times) and give it a material\n2. Go to material settings and set the materials...\n- Blend mode to \"Alpha Blend\"\n- Backface Culling to False\n- Show Backface to True", "Clipping Region in blender v3.2 and up is causing a werid artifact\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.10.1.221003\n\nBroken: version: 3.3.1\n\nweird colorful noise when using Clipping region ALT+B\n\nit happens by simply using the clipping region, it happens in both object mode and edit mode\n\n**Diagnosis that I tried** (USEFUL NOTES{[F13703419](Untitled.png)} FOR FIXING THE PROBLEM)\nwhat is causing it?: \n- I noticed that the bug is only on the Viewport Overlays it seems like it's smth related to the graphical smoothing done by \"viewport overlay smooth wires\" from blender preferences -> viewport -> Quality -> Smooth Wires. I can turn of that for Overlay and for Edit mode, but it's just hiding the problem not fixing it, also the selected objects highlight (active element and not active element) are both still showing the same artifact and I don't know how to turn off smoothing for this part.\n\nis it gpu driver problem?\n- it most likely is a conflict between blender and my gpu, I don't think it's a driver problem tho because I tried the latest two gpu drivers available from amd, and both of them are showing the same problem. I tried running blender using my integrated gpu and tried my RX6600M gpu and in both cases it happend, I don't know if the smoothing is done on the gpu level or cpu level tho so it could be not related to which gpu I use\n\nWhat versions of blender does it happen in?\n- I mainly use blender from steam with auto updates, I noticed the problem when I was using v3.3.1 then I tried few older versions by manually installing them from the offical blender website, the bug doesn't show up in v3.1.2 and v2.79b however it's in showing up in v3.2.0 and v3.3.0 and v3.3.1 -not steam version- I didn't test more versions tho\n\nP.S. my device -Legion 5- has a mux switch, when I did the bug report the mux switch is turned off which means the integrated GPU is disconnected thus it's not showing up in the bug report, however when I tried to check the bug \n\n\n\n\n\n\n\n[untitled.blend](untitled.blend)" ]

[ "Eevee dark edges on 8bit sRGB textures\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 64)\nWorked: 2.80, commit date: 2019-05-11 18:20, hash `ebc44aae9897`\n\n\nCurrent builds of Blender 2.80 seem to be discarding colour information in textures under specific conditions. Any texture you use in a material node tree with an alpha channel and \"Use Alpha\" turned on displays incorrectly: any pixels that are black on the alpha channel are also black on the red, green, and blue channels . This did not happen with earlier builds and, weirdly, affected images display correctly when viewed in the image editor.\n\nThis is leading to the following side effects:\n\n - Opaque parts of alpha transparent textures now have soft black lines around their edges (see included screenshots) and appear more aliased and sharp than they should\n - Channel packing -- a technique popular in video game development where several greyscale masks are placed in the red, green, blue, and alpha channels of a texture to save memory, \"packing\" them into one image that can then be split up and used with a \"Separate RGB\" node -- now no longer works correctly on an image with an alpha channel since the masks in the red, green, and blue channels are \"blacked out\"\n\nDrag and drop any texture with an alpha channel (PNG or TGA) into a material node tree. Do not disable \"Use Alpha\" for the texture. Hook up the Color output to Base Colour. Observe that all pixels where the alpha channel is black are now black in the red, green, and blue channels as well. If necessary, to examine each channel individually, place and connect up a \"Separate RGB\" converter node. Note this issue persists regardless of whether you're using Eevee or the Cycles render engine.\n\nTo help reproduce the bug, I've attached a Targa file below which is a colour gradient with the words \"This is a test\" written on the alpha channel. This serves as an ideal example of an image that has colour data in the 100% transparent pixels that you can view in Blender's image editor by isolating the \"Color\" channel.\n\nAlso included are two screenshots of the \"black lines around edges\" issue: \"Before.png\" is how it looked prior to the bug, \"After.png\" is how it looks now. Note the considerably more jagged edges to the letters.\n\n  " ]

[ "Poor stroke quality when a model is far from the world origin\nOperating system: Win 10\nGraphics card: Nvidia Rtx 2070\n\nBroken: 2.83, master\nWorked: perhaps never?\n\njittery strokes when mesh is far from the world origin in perspective mode\n\nHow to reproduce this bug : \n- Create a grid (set the location to x : 2000 m and y : 1000 m)\n- Create a multires modifier, with 5 subdiv.\n- Sculpt with the clay brush\n- In Perspective mode (left stroke) the stroke is ugly\n- In ortho mode (right stroke) the stroke is clean\nTo fix the stroke poor quality, i had to fine tune the Clip start and the clip end values of the 3d view. \n[#102747.blend](T102747.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", "Normal map node worked is not correct\nOperating system: win10 x64\nGraphics card: gtx 1650\n\nBroken: 3.5.0, 1be25cfff18b, 2023-03-29\nBroken: 2.93\nWorked: 2.92\n\nCaused by 1c22b551d0\n\n\nI do not think that this is an error or a bug, rather it is not a refinement. \nIn some cases, the normal map node does not display them as you would like. \n\n\nI created a Hight poly model and bake it into a plane. Then I applied the resulting texture to the Low poly base mesh. It didn't display correctly there, only part of it smoothed out, but the other part showed sharp edges, very similar to the Fresnel effect\n\n", "Design issue: Icon next to overridden property does not perform the function it strongly suggests\n3.0.0\n\nWhen a propertry is overridden, the \"animate property\" button next to it is replaced by this \"reset\" icon:\n\nThese really seem to suggest that clicking them will remove the override. Instead it just adds a keyframe as usual. This seems misleading.\n\n - Override a property of some library override asset\n - Click the button to the right of that property\n\n", "UI: Merge Text Style \"Widget Label\" into \"Widget\", Add \"Tooltip\"\nWhen controlling how big interface elements are displayed, users can not only change the Resolution Scale and Region Zoom but can change the size and styles of some elements separate from others. This document proposes changes to our Text Styles.\n\nIf you go to Preferences / Themes / Text Style you will see that you can change the size of different UI elements independent of the overall UI scale. You can make it so that regardless of scale you always have Header text twice as large as regular text, for example.\n\nBut the design is not fleshed out well. We have just \"Panel Title\", \"Widget\", and \"Widget Label\". There are many areas where one type of UIBut uses one when it should use another. There are assumptions, like in #102687, that \"Widget\" and \"Widget Label\" are the same size. The function mentioned in that bug report - `ui_text_icon_width_ex()` - is trying to estimate an element's width but does not have the information needed to know what style to use, so just uses UI_FSTYLE_WIDGET, which is hardcoded for the \"widget\" style.\n\nIt seems like a nice idea that we can have labels displaying differently to the inputs beside it. And I have personally proposed adding to these options to include width, weight, slant, spacing and other text features.\n\nHowever, our interface is laid out programmatically using quite rough rules. We necessarily have a very tabular layout. For example we don't have (and might not be able to supply) a \"line height\": the vertical spacing between interface rows. This value is calculated from UI element width, considering scale and line width. So can't for example, leave the resolution scale the same but change the line-height to better accommodate languages that use fonts that are very tall (Arabic) or squat (Chinese).\n\nThis all means that we have little chance to make Label and Widget have varying sizes. The line-height can't vary with the largest of them, and we have to keep all interface rows the same height anyway.\n\nI propose that we merge \"Widget Label\" into \"Widget\" text styles, leaving us with only two styles \"Header\" and \"Widget\". And then add a third back for \"Tool Tips\" because that text size is currently set as a hardcoded fraction of the widget size - and I can imagine some users with vision impairment wanting those proportionally larger.\n\nThe only real downside is this would remove the ability for \"Widget\" and \"Widget Label\" to have differences unrelated to the size. There could be some users who have the same size but have them differ in shadow. Right now the only non-size changes possible are shadow-related but, as mentioned, we could add other options. For example we could allow one to be bold and the other italicized. But I don't personally think this is important. I don't like our text shadowing and use of weight and slant differences should be more selective than this, having sematic meaning. I would rather embolden important words, italicize special sections, etc.\n\n", "Upgrade the Line Type Dots\nUpgrade the line type _Dots_ to the stamp brush. \nThis is the todo list of the stamp brush development at stage one, detailed in 30884\n\nBranch: [`gpencil_articluated`](gpencil-articulated)\n\nGeneral:\n\n- [x] A quick demo\n- [ ] Maintainable code framework \n- [ ] Basic GUI\n\nVertex attributes:\n\n- [x] Position\n- [x] Radius\n- [ ] ~~Aspect ratio~~: technically impossible\n- [ ] ~~Hardness~~: unnecessary\n- [ ] Color\n- [ ] Strength\n- [x] Rotation\n\nOther features:\n\n- [ ] Texture\n- [ ] Stroke order, depth and blending\n- [ ] Holdout\n- [x] Lighting\n- [x] Alignment types\n\n", "editor's type pop up shows the wrong shortcut!\nOperating system: Linux-6.4.14-x64v2-xanmod1-x86_64-with-glibc2.38 64 Bits, X11 UI\nGraphics card: Mesa DRI Intel(R) HD Graphics 2500 (IVB GT1) Intel Open Source Technology Center 4.2 (Core Profile) Mesa 21.3.9 Amber\n\nBroken: version: 3.6.2\nWorked:\n\nwhen hover the mouse over the editor's type, it shows the name, description and the shortcut, but the shortcut shown is the same for every editor (Shift F1).\n\n\n1. new scene.\n1. put the mouse under the editors type (without clicking) as if want to change it.\n1. read the popup.\n\n\n\n", "Metaball fixes\n- [ ] Dependency graph integration\n- [ ] Naming based design is weak\n\nThere are many issues with the current version of metaballs. If we won't fix them we may want to consider to deprecate/remove this in future releases.", "UI: File Browser Incorrect uiFontStyles\nOperating system: All\nGraphics card: All\n\nBroken: 3.1\nWorked: 2.79\n\nFile Browser uses an odd mixture of uiFontStyles to draw interface\n\nEdit / Preferences / Themes / Text Style\nChanging \"Widget\" points changes the font size of \"Bookmarks\", \"Recent\", the browsed directory, and the line height of the entries:\n\n{[F11861179](FBWidget.gif),width=100%}\n\nChanging \"Widget Label\" changes Volumes, System, and the text size (but not line height) of entries:\n\n{[F11861234](FBLabel.gif),width=100%}\n\n", "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.", "3.4.1 Not Displaying GTX 1660 TI\nOperating system: Windows 10 Home 22H2\nGraphics card: GTX 1660 TI\n\nBroken: These versions do not display my GPU under CUDA/OptiX: 3.4.1, 3.4.1, 3.3.4, 3.3.3 and 3.3.2 (I was also getting Python errors when trying to install addons. (This is true whether they are installed or run from the unzipped .rar downloads.\n\nWorked: blender-2.93.15 candidate+v293.400f35914421-windows.amd64-release is the most recent version that works - everything works as it should!\n\n\nI tried uninstalling/installing the latest Nvidia game ready drivers, the studio drivers, the CUDA Toolkit (which asked for me to install Visual Studio, C++, etc... 🤦‍♂️ ), tweaking the registry settings etc... none of these things worked. \n\nOnly using the older version would detect my GPU. A user on the Discord forum asked me to run the GPU debugger in the latest version 3.4.1 and when I open the program that way, my GPU was finally showing! I sent him the error reports (I can post them below) and he said that Blender IS SEEING my GPU, it's just not displaying it for use.\n\n", "Intel (R) HD graphics 4600 also has the problem of cubemaps shows black\nIntel (R) HD graphics 4600 also has the problem of cubemaps shows black\n\nSystem Information\nOperating system: windows7 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 3.4.0 - Build 10.18.14.5117\n\nBlender Version\nBroken: since 2.83.3 branch: master\nCurrent broken: 2.93.7\nWorked: 2.82a\n\nShort description of error\nLike #75943 and #79158, HDRI cannot be displayed normally\n\nCan be resolved adding \"**HD Graphics 4600**\" to the blacklist\n\nComment from #79158: \"*I'm not sure whether Intel's graphics cards are like this. Can you put this repair method in preferences as an option?*\"\nOr perhaps adding command line flag like: **--disable_texture_cube_map_array**", "Auto-Merging keyframes in the Driver Editor has unappropriate threshold (merges keyframes that shouldnt)\nOperating system: windows 10 & Linux ubuntu\nGraphics card: GTX 1070\n\nBroken: 3.6.2\nWorked: unknown\n\nSee att. blendfile and pictures; moving the base of the armature in the Y direction drives the shapekey of the torus.\nIf you edit a driver keyframe by just slightly moving it to the right, the keyframe next to it is removed\n\nTry editing keyframes in the driver f-curve editor\n\n\n**Note**\nDrivers editor has the driver value as the x-axis (this can be arbitrary low, e.g. in the report, this was the x location [in meters] so handling quite small values where \"keyframes\" where ~0.01 apart\n\n`BKE_fcurve_merge_duplicate_keys` acts with a threshold of `BEZT_BINARYSEARCH_THRESH 0.01f`", "Japanese translation | \"Wrong\" translation (Value)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\n\nThe Japanese translations of \"Value\" are \"値\" and \"明度\" depending on the context.\nThe correct translation for \"Value\" in the Color Picker and Hue Saturation Value Node is \"明度\".\n\"値\" and \"輝度\" are incorrect translations.\n\nOn the other hand, \"値\" is the correct translation for the Value Node, so there is no need to correct it as it is now.\n\nThank you!\n\n-----\n\n- [x] Color Picker: Value input field\n- [x] Separate and Combine nodes, HSL mode: Lightess input socket\n- [ ] Separate and Combine nodes, HSV mode: Value input socket\n- [x] HSV node: Value in title\n- [x] HSV node: Value input socket", "Blender's search in data-blocks is case-sansitive in cyrilic letters\nUbuntu 14.04\n\nBroken: 2.73\n\nSupporting of Utf-8 characters chars in names of objects and data-blocks are not completely done. While searching, uppercase and lowercase letters in the Cyrillic alphabet are considered as different letters. \n\nHere is the test file [casetest.blend](casetest.blend)\n\n\n\n\n" ]

[ "UI: Font: decreased readability because of less spacing\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\nDisplay resolution: 2560x1440\n\nBroken: version: 3.4.0 Alpha\nWorked: Blender 3.3.0\nChanged in e9bd6abde3\n\n\nNotice how the `i` of the `Window` button gets pressed into the `W`.\nOr the `i` into the `F` of `File`.\n\nBlender 3.3.0\n\nBlender 3.4.0\n\n\n| Blender 3.3 | Blender 3.4 |\n| -- | -- |\n|  |  |\n|  |  |\n\n\nOpen Blender" ]

[ "Regression: Crash on Start Up\nOperating system: Mac OS 12.6.9\nGraphics card: AMD FirePro D500 3 GB\n\nBroken: blender-3.6.3-stable+v36.d3e6b08276ba-darwin.x86_64-release.dmg\nWorked: blender-3.6.3-candidate+v36.71b55b491e9c-darwin.x86_64-release.dmg\n\nApp crashes at start up.\n\nClick on App icon, app attempt to start, crash. I restarted my computer with same results. Not opening app from a .blend file. Tried opening default app with same result.\n\n", "Blender-3.1 (git) boolean in Geomenty Nodes issue\nOperating system:\nGraphics card:\n\nBroken: All\n\nBulean issue like T91889\nbut now in GN\n[2021-11-25_22-29-42.mp4](2021-11-25_22-29-42.mp4)\nTest Scene\n[parktronic1-Blender-3.blend](parktronic1-Blender-3.blend)", "Themes→3dViewport→Active vertex color do nothing\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.5.0\n\nThis one influence nothing. Should it be deleted?\n\n\n[2023-04-13_07-48-03.mp4](attachment)\n\n\np.s. Dull colors and other issues about wireframe [described here](426) and I am sad, that it looks abandoned and ignored…\n\n", "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", "My blender doesnt open\nOperating system: Windows 10\nGraphics card: ?\n\n\nBroken: 3.6.2 LTS\nWorked: ?\n\n\nWhenever I try to open blender a Pop up appears saying \" No se pudo inicia la aplicacion;la configuracion en paralelo no es correcta.Consulte el registro de eventos de la aplicacion o use la herramienta sxstrace.exe para obtener mas detalles\"\n\nI have no idea, the one thats dowloaded by ZIP, i have already tryed this by the installer and the same problem\n\n\nWay literally, download blender and try to open it\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Regression: Blender text editor lost support for dead keys\nOperating system: Linux-4.19.0-11-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 2.93.0\nWorked: 2.92\n\nCaused by cafd6b519c\n\n\nOn any text input field, on the Python Console, on the text editors, I cannot type any of the characters that need dead keys (I use English International with dead-keys to type English, Spanish, and German).\nI cannot, for example even type quotes, which makes Python expressions hard - let alone accents, etc. \n\nThis used to work on previous versions of Blender. The latest I found it working on is on a 2.92 release candidate I had somewhere on my hard drive.\n\n\n1. On a computer configured with dead-keys input, open the default scene\n2. Switch the main display to be a Text Editor.\n3. Press \"New\" to create a new file.\n4. Try to type \"é\" (by pressing 'e) or \"'' by typing (' space).\n\nExpected behaviour: Blender accepts the typed-in characters.\nActual behaviour: Blender ignores the typed-in characters.\n\nSomething like this gets printed to the console:\n\n```\nBad keycode lookup. Keysym 0x0 Status: XLookupNone\n'' 0x7f80237f2980 0x7f804905d0c0\n```", "Edit Source operator missing the \"see XXX.py in the text editor\" info in the status bar\nOperating system: Linux-6.4.13-200.fc38.x86_64-x86_64-with-glibc2.37 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 16.0.6, DRM 3.52, 6.4.13-200.fc38.x86_64) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6 LTS\n\nCaused by 1251b7c4001b3f7de158c089256b04c887d6c5bb\n\nEdit Source operator missing the \"see XXX.py in the text editor\" info in the status bar\n\n- use the context menu on a button in the UI and call Edit Source\n- this is missing the following info in the status bar:\n\n\n", "foreach_get/set doesn't work for enum\nOperating system: Linux-5.11.0-38-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.74\n\nBroken: version: 2.93.6 Release Candidate\n\n`foreach_get/set()` function doesn't work to set/get enums properties. \n\n- Based on default `Video Editing` template.\n- Create a color strip.\n\nSet\n----\n- Type in python console:\n```\nblends = [\"DIFFERENCE\"]\nC.scene.sequence_editor.sequences.foreach_set(\"blend_type\", blends)\n```\n- Got:\n```\nTypeError: an integer is required (got type str)\nTraceback (most recent call last):\n File \"<blender_console>\", line 1, in <module>\nTypeError: couldn't access the py sequence\n```\n\nGet\n----\n- Type in python console:\n```\nblends = [None]\nC.scene.sequence_editor.sequences.foreach_get(\"blend_type\", blends)\nblends\n```\n- Got an int value which is not consistent between blenders neither after another `foreach_get`.\n\n\n", "USD import: investigate texture color space conversion issue\n\n@brurpo Reported the following issue:\n\n> When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb.\n> Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space.\n> Is there a workaround for this, or is this planned?\n\n\nI'll be looking into this.\n\n\n", "Error when denoising (Optix) large image\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090, 3060 Driver 522.30\n\nBroken: version: 3.3.1\nWorked: Never (3.0 failed, 2.90 did not start rendering)\n\nDenoising large image will fail and may result in crash.\n\nShortened log:\n```\nIllegal address in CUDA queue synchronize (film_convert_float3 filter_guiding_preprocess)\nE1122 18:16:01.843204 7088 denoiser_optix.cpp:470] Error converting denoising passes to RGB buffer.\nIllegal address in CUDA queue copy_from_device ()\n```\n\n[#102515.blend](T102515.blend)\n\nOpen file and render image.", "Isolate File Encoding Colour Management\nCurrently, a pixel pusher with the correct view set for an `Apple Display [P3](P3.txt) Display`, ends up baking in the `Display [P3](P3.txt)` transform into file encodes due to the way Blender encodes the file based off of the currently selected view.\n\nSolution is to isolate the file encoding from the other output contexts such as displays and views.", "Eevee Attribute Rendering is Having Problem with Scene Referred/Open Domain Data\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: None\n\nEevee attribute rendering fails to render scene referred/open domain data\n\n\nAnd here is Cycles that does it properly:\n\n\nBased on the attached .blend file\n\n1. Turn on Rendered view, see how Eevee clips all values above 1 and the sweep end up with the six colors on the right side and it doesn't go to white at all (The Notorious Six)\n2. Switch to Cycles and see how Cycles renders open domain data properly\n\n[Eevee Attribute Rendering Open Domian Bug.blend](Eevee_Attribute_Rendering_Open_Domian_Bug.blend)\n\n[Eevee Attribute Rendering Open Domain Bug.mp4](Eevee_Attribute_Rendering_Open_Domain_Bug.mp4)", "Collection don't change text color\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\n\nActive object's text is not visible if the selected object is collection (in the outliner).\n \n\n**Steps to Reproduce**\n- Open the directory where blender.exe is\n- Place the `test.xml` file inside `\\blender_version\\scripts\\presets\\interface_theme\\`\n- Run Blender\n- Change the theme to `test` from preferences tab\n- Select the collection in outliner (Collection name is not clearly visible because of changed `active Highlight` color)\n\n[test.xml](test.xml)", "Font rendered incorrectly with text object\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nThe font is displayed incorrectly when added to 3d text object\n\nFont and blend file in attachment\n[untitled.blend](untitled.blend)\n\n[roadrage.ttf](roadrage.ttf)\n\n", "Color attributes in sculpt mode not showing in instance objects\nOperating system: Linux-5.15.0-47-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.226.00\n\nBroken: version: 3.4.0 Alpha\n\nWhen sculpting an object its instance reflect the changes after the stroke, but not with color attributes, you have to go out of sculpt mode to see the color attributes.\n\n1. Open a new sculpt file.\n2. Make and instance in object mode with Alt D\n3. Enter sculpt mode of the original object.\n4. Paint some color attributes\n5. Sculpt with clay brush to see the expected behavior.\n\n[Grabación de pantalla desde 17-09-22 16:08:53.webm](Grabación_de_pantalla_desde_17-09-22_16_08_53.webm)\n\n\nOne funny thing is that if you give the original object a mirror modifier, the changes to the instance are in real-time, not after the stroke, both for sculpt and for paint. But not when you sculpt or paint in the one without the modifier.\n\n\n[Grabación de pantalla desde 17-09-22 16:22:16.webm](Grabación_de_pantalla_desde_17-09-22_16_22_16.webm)\n\n" ]

[ "Color Management render view only has 'standard'\nPlatform: Windows\nGPU:\t'GeForce GTX 960/PCIe/SSE2'version:\t'4.5.0 NVIDIA 432.00'\n\n**Version:** 2.90.0, type: Release\n\n\nWhen placing Blender in a directory with Katakana (Japanese characters) as name, OCIO fails to find the configuration file. Blender thus only provides the \"Standard\" view transform in the color management options.\n\nThe path for the Blender directory is ` C:\\Users\\nanam\\OneDrive\\デスクトップ\\blender-2.90.0-windows64`.\n\n[system-info.txt](system-info.txt)\n\n\n - Change the Windows locale to Japanese in the \"Language for non-Unicode programs\" settings.\n - Place Blender in a directory with Katakana in the name.\n # Start Blender.\n\nInstead of changing the Window's locale language, placing the portable version of Blender on a non-C drive as Step 1. will also show the issue." ]

[ "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", "Cycles: Bump node doesn't distort normals\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 10)\nWorked: Never\n\nHeight input have no effect on bump node output in cycles.\nThe main problem, that Generated texture cordinates give seams with bump. That is why I desided to try Normal input.\n\nEevee:\n\n\nCycles:\n\n\nHere the example file.\n[WhereNormals.blend](WhereNormals.blend)\n", "Loop Cuts and Inset Faces cutting Meshes\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 750 TI\n\nBroken: 3.2\n\nTrying to add regular edge loops with Control + R, or even trying inset a face, they are cutting my mesh, or merging the ends. (I shared this on reddit, and it was suggested I create bug for it. \n\nAll I did was delete the bottom face of the mesh since I would not need it, but somehow I created invalid geometry and when I add an edge loop near the end it merges. If I try to inset the faces, it gives me weird end geometry.\n\n(This is what was noted from someone on Reddit: Update: just checked the file and here are my findings:\n\n```\n Adding a loop, be it length ways, long ways, or any other way seems to works just fine with the CTRL-R shortcut\n```\n\n```\n The loop cut tool also works just fine.. except if you try and loop cut around the XY plane instead of the XZ plane (drawing a line around the thinnest faces) at which point the mesh seems to collapse to zero height\n```\n\n```\n Insetting faces also works fine, be it via the tool or pressing I... but if you then try and extrude the inset suddenly the model collapses\n```\n\nOther things of note: the face orientation is inside out for this mesh (turning on Face Orientation in the Overlays menu (two overlapping circles in the header) shows them as red) and the object-level scale hasn't been applied. Fixing both of these doesn't correct any of the above issues -- although it IS normally advised since it prevents a few shading and modelling issues -- but it does, for some reason, change how the errors manifest, like the model collapsing in a slightly different way or the CTRL-R shortcut suddenly causing the same issues the tool version of loop cut and slide has.\n\nConclusion: you've somehow managed to turn this mesh into some form of invalid geometry that Blender can't seem to handle properly. You may wish to report it as a bug, including this file as a demonstration.\n\n- Open .blend file\n- enter edit mode and select face mode\n- press numpad 3 for YZ plane view\n- Add loopcut on visible face side (it'll merge the edges)\n\n---\n- repeat first 2 steps from above\n- press numpad1 for XZ plane view\n# select visible face -> extrude + scale (will merge edges). Works with inset tool\n\nTest File:\n[Issues Build2.blend](Issues_Build2.blend)", "Adaptive Subdivision - Stray vertex / Spikes\nOperating system: Ubuntu 18.04\nGraphics card: GTX 1080 Ti\n\nBroken: 2.81 2019-12-05\n\nI'm using adaptive subdivision for micro-displacements to turn a surface mesh into a thick scarf with yarn geometry. In some of my animation's frames I have found spikes in the rendering such as here:\n\nIt seems to be deterministic in that I can reproduce it for a single frame of the animation; I attached the blend file for a minimal example of a single frame with the issue.\nThis issue does not happen in the progressive viewport render. Also, since the ao-map that I'm using to drive the displacement does not change over time but this happens only in some frames, it is likely not related to the displacement map but more to the *mesh and the adaptive subdivisions*.\n\nOpen the blend file and press F12 to render\n[adaptivesubdiv_issue_updated.blend](adaptivesubdiv_issue_updated.blend)", "Skewed Rotation Bug - Using snap invert with align rotation on skews the rotation of the Mesh\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.73\n\nBroken: version: 3.1.2\n\nWith align rotation enabled from the snapping menu, snapping an object to another using *snap invert (pressing the ctrl button)* works normally until you move your cursor before clicking ctrl to snap. In other words, moving your mouse cursor and snapping skews the rotation for the next time you try to snap again. In the steps below, I'll be snapping to *face* with *median* selected, but the bug is also there with *edge mode*, and even *center* and *active*.\n\n* From the snapping menu, select *Face mode*, and choose to snap with the *median*, and only turn on *align rotation.* Do not turn on *snap during transform (the magnet)*, we will use *ctrl* to snap onto the mesh using *snap invert.*\n* Do not delete the default cube. Instead, create a cylinder, and move it away from the cube, and scale it down. We will be snapping the cylinder onto one of the cube's faces to demonstrate this bug, so you can enter side view if you'd like.\n* Click the cylinder, and enter *edit mode.* Press 'A' to select all vertices. Click 'G' to enter Transform mode, and try not to move your cursor.\n* Click ctrl to snap the cylinder onto the cube using *snap invert*. Next, click the RMB to cancel the transformation.\n* Click 'G' to enter Transform mode again. Next, move your cursor a notable distance to the side of the cube's face. Click ctrl to snap the cylinder onto the cube's face. Again, click the RMB to cancel the transformation.\n* Finally, click 'G' again, and click ctrl to snap the cylinder onto the cube's face, and notice that the rotation has been skewed.\n* (Bonus info, not needed) To return to your original snap rotation, you have to cancel the transformation and enter it again to snap, even multiple times. \n\n1) Here's a screenshot of the skewed rotation\n\n\n2) Since this is a bit more difficult to reproduce, I have provided a video on how to exactly reproduce this bug: [Video](xw4vYG9MOIA)\n\n3) Finally, here's the blend file:\n[Skewed_rotation_bug.blend](Skewed_rotation_bug.blend)\n\nP.S. I would also appreciate it if you can mention how align rotation works in edit mode.\n\nThank you so much for you work. Very much appreciated!!", "Bevel tool creates asymmetrical results on symmetrical objects\nOperating system: Kubuntu 19.10\nGraphics card: NV GTX 1650\n\nBroken: 2.90.1 (snap package manager), build date 2020-09-23, hash 3e85bb34d0d7\n\nWorking on cylinder based objects, it seems that bevel tool leads to asymmetrical results on some symmetrical edges. On first screenshot, left and right sides of beveled loop are clearly different. On the second one top and bottom created faces are also different.\n\n **First case:**\n\n- Open attached file or:\n - create a cylinder, \n - loop-cut in the middle and bevel the resulting edge loop.\n - Select two or more contiguous faces on the middle face ring and extrude them.\n- Select the upper or lower horizontal edge loop where the extruded faces meet the cylinder and bevel it.\n[asymmetrical_bevel_bug.blend](asymmetrical_bevel_bug.blend)\n\n---\n**Second case:**\n\n- create a cylinder,\n- inset top and bottom faces.\n- Select two or more contiguous vertical faces and extrude them.\n- Then select the horizontal edges where the extruded faces meet the cylinder and bevel them.\nTop and bottom created elements are asymmetrical.\n", "Solidify modifier rotates custom normals incorrectly\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.4.1\nWorked: not as far as I know.\n\nWhen solidifying an object with custom normals, the newly created geometry rotates (destroys) these normals on the newly created geometry. So a smooth surface gets a non-smooth (faceted-looking) surface on the other side. \nHowever, activating the Normals --> Flip option in the modifier actually produces the correct (smooth) normals on the new geometry, but destroys the custom normals of the original surface. The newly created surface then has flipped normals, but these can be flipped again inside edit mode after applying the modifier. They are then facing the right way and still smooth. So the modifier actually has the code to correctly calculate the new split normals.\n\n\n- Take a mesh surface with custom normals, make two copies.\n- Object 1: Add a solidify modifier with a relatively small thickness. Look at the newly created surface: it's not smooth but faceted. \n- Object 1:Apply modifier, turn on display of custom normals, zoom in on new geometry: the normals on the new vertices are divergent.\n- Object 2: Add a solidify modifier activate with Normals --> Flip. Look at newly created surface: it's smooth as the original one. Great. But the original surface is now broken up and not smooth.\n- Object 2: Apply modifier, turn on display of custom normals, zoom in on new geometry: the normals on the new vertices are identical, do not diverge, they are simply facing the wrong way. Apply \"Normals (ALT-N) --> Flip\", now they are correct.\n\nSo basically there is a work-intensive workaround (which also means losing the flexibility of having a modifier): make two copies of the object, add modifer with flipped normals, apply, flip normals again in edit mode, manually select and delete original geometry, join with the original object (original geometry). This is what the modifier itself should be doing.\n\n- See the attached Blend file. Four objects: original, two solidify copies, and one created with the workaround.\n\n", "Merge by distance produces unexpected results\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.48\n\nBroken: version: 2.90.0 Alpha\nWorked: N/A\n\nMerging vertices of a few straight edgeloops produces jagged edgeloop instead of straight one.\n\n1. Open attached blend file\n2. Select vertices of three edgeloops in the middle.\n3. Apply Merge by distance and increase threshold until they collapse into single edgeloop.\n4. Check attached image to compare results of same operation in other editors.\n\n[by_distance.blend](by_distance.blend)\n", "F-curve editor displays incorrect curve for reversed NLA strips\n**Operating System, Graphics card**\nLinux SuSE 12.2 (x86_64)\nNVidia GTX560ti (official driver)\n\n**Blender version with error, and version that worked**\nBroken: 2.67b - 2.91 and recent buildbot binaries\n\nReversing a strip in the NLA editor makes the f-curve editor display animation curves incorrectly. This is only a UI/display issue - object will still animate as expected.\n\n**Steps for others to reproduce the error (preferably based on attached .blend file)**\n- add a couple of keyframes to an object and switch to NLA\n- turn action into action strip (snowflake icon)\n- in the strip properties, enable 'Reversed'\n- go into edit/tweak mode for the strip then switch to f-curve editor\n- animation curves are drawn incorrectly\n\n[#35708-nla-reverse-display-issue.blend](T35708-nla-reverse-display-issue.blend)\n\nNormal:\n\n\nReversed:\n\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", "Apply scale normal flipping\nThe apply transforms operator in blender can apply negative scaling to an object.\nHowever there is two ways to do this. If you scale your model with a negative\nvalue in editmode, you get flipped normals. This is because the vertex order in the\nfaces is preserved and that is what determines the normal. In object mode however,\nthere is a flag in the render engines to flip the normals back, if they are flipped due\nto negative scale. This inconsistency creates the problem with the apply transforms\noperator. The following image shows on top the behavior in editmode and at the\nbottom the behavior in object mode.\n\n\n\nOf course both behaviors have their reasoning to exist.\n\nOne reason for the rendering flag to exist is, that instances of the same object can\nbe mirrored without causing normal problems. Obviously there is no other solution\nto that, since the underlying mesh is the same for all instances, so the render engine\nhas to handle negative scales.\n\nOn the other hand, in editmode you don't want to change the loop order for all your faces\nif you are just scaling. It makes much more sense for editmode scaling to just change\nvertex coordinates. That means you need to fix the normals manually.\n\n\nThe apply operator can only be called in object mode. From object mode the current\nbehaviour looks as if it was flipping the normals. Actually it is just applying the\ntransform \"in editmode\", which looses the negative scale information for rendering.\nThis looks like a bug to some users and is confusing for new users. Users have actually\nrequested this to be changed:\n\n4Zdbbc/\n\nI also heard this request on the BCON22.\n\nHowever the question arises, do we add another option or do we just always flip the\nnormals to make it consistent with rendering? Another question is what happens to\naddons which are using this operator if the operator gets changed in this way?\nHow many addons are actually using apply scale on negatively scaled objects?\nDo those addons fix the normals by flipping them manually?\n\nThere is already a patch available to add this normal flipping without an option:\n\nD16382", "Same pattern looks different for Cycles and Eevee\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.1\n\nThis is the difference\n\n\n\n\nsimplified file\n[pixels tiled1.blend](pixels_tiled1.blend)\n\n\nold file \n[pixels tiled.blend](pixels_tiled.blend)\n\nI suppose the difference in Color Ramp or Noise node.\n", "Path Guiding: Cycles in viewport produce inconsistent results\nOperating system: Windows 11\nGraphics card: Geforce 1660S\n\nBroken: 3.5\n\nJust moving the camera around the viewport gives inconsistent cycles renders. I am not sure if it's directly related to path guiding as the issue is only visible in the mirror caustics.\n\n\n\n\n", "Generative modifiers (solidify, mirror) draw face normals from original face (wrong direction)\n@Baszczer information\nOperating system: Ubuntu 20.04\nGraphics card: Radeon Pro WX 7100\n\n@Alaska information\nOperating system: Linux-5.4.0-7629-generic-x86_64-with-debian-bullseye\nGraphics card: GTX 1050Ti 440.82\n\nBroken: 2.83 (2020-05-26 22:42) `f772a4b8fa`, 2.90 (2020-05-26 20:02) `eb5422828a`\nWorked: 2.82a\n\n**Short description of error:**\nThe viewpoint overlay for displaying faces normals in edit mode for faces that are part of a solidify modifier will always point in the direction of the face normal being solidified with Blender 2.83 and 2.90.\n\n\n2.82a\n\n\n2.83/2.90\n\n**Exact steps for others to reproduce the error:**\n1. Open Blender.\n2. Add a plane.\n3. Give the plane a solidify modifier.\n4. In the modifier panel, enable the \"On cage\" option for the solidify modifier.\n5. Enter edit mode on the plane. \n6. In the viewport overlays enable the \"Display normals\" option for faces. \n\n[#77090 - Solidify Normals.blend](T77090_-_Solidify_Normals.blend)\n\nIn 2.82a, this will be have as expected. The normal lines will be perpendicular to the faces of the solidifies plane. In 2.83, all the normal lines align with the normal line of the face being solidified.\n\nVideo because I feel like I'm having a hard time explaining this in words:\n[2020-05-27 22-55-31.mp4](2020-05-27_22-55-31.mp4)", "Remesh Resolution strange behaviour (Shift-R)\nOperating system: MacOS 10.14.6\nGraphics card: AMD Radeon R9\n\nBroken: Daily Build\nWorked: Don't know\n\n**Description**\nSetting the remesh resolution with Shift-R during sculpt when object is unproportional in size makes the grid fade (too quickly) and when zoomed in the numeric display of scale is upside down\n\nIn this small video clip, first part is correct behaviour.. second with disproportional object\n<video src=\"remesh_behaviour.mov\" controls></video>\n\n**Steps**\n- Use default cube\n- In edit mode scale the object 10x in Z only\n- Enter Sculpt mode\n- zoom in\n- Shift-R\n- observe grid fading and display upside down..\n\n[remesh_behaviour.mov](remesh_behaviour.mov)\n\n\n" ]

[ "Bridge: uses an unpredictable direction between loops placed side-by-side\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta\nBroken: version: 2.83.3\n\nThe Bridge Tool calculates the wrong direction for the start and end points in different situations.\n\nExamples in attached .blend file\n\n\n\n\n[Bridge_Start_End_Points_Behavior.blend](Bridge_Start_End_Points_Behavior.blend)", "Bridge Edge Loops operation has inconsistent results\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.83 (sub 11)\nWorked: N/A\n\n*Bridge Edge Loops* operation result is different when mesh is duplicated in *Edit Mode* vs. duplicated in *Object Mode* and joined into one object.\n\n\nWorks in default startup file.\n\n - Add plane through *Add > Mesh > Plane*\n - In *Edit Mode* duplicate it and move the duplicate a bit sideways (along X or Y axis)\n - Select All vertices and go *Edge > Bridge Edge Loops*to connect them with an arch. Set *Number of cuts* to 2+.\n - The resulting arch is weirdly 'cut' in the middle, introduces non-manifold faces and flipped normals.\n\nNo such issues occur when the original plane is duplicated in *Object Mode*and joined into one object. Only direct duplicating in *Edit Mode* causes this behavior.\n\n*Duplicated in Edit Mode. Gives weird results.*\n{[F8434956](bridge_loops_edit_mode.gif), size=full}\n\n*Duplicated in Object mode and joined. Creates a nice arch.*\n{[F8434969](bridge_loops_object_mode.gif), size=full}\n\nThanks a lot for looking into this problem.\n\n" ]

[ "Snapping issue while rotating and 'Align Rotation to Target' is ON - can't set correct origon rotation for simple object \nOperating system: Windows 10\n\n\nBroken 2.81 new feature of origon \n\nsnaping rotation origon bug - can't set correct origon rotation for simple object \n\nrotation snaping of origon is tha same important as moveing origon to spec place\n \nI need to specyfy Z direction also x and y direction. To working with this propably I need to have 2 directions snaping z and x or z and y to work with this.\nso for example Z with snaping and then hold shift seting Y snaping... \n\nThis will help with orientation objects in space by orientation of another objects like aligment rotation object to another object ect. \n\nThanks for great work.\n\n\n[origon snaping rotation video.mp4](origon_snaping_rotation_video.mp4)", "Pose Mode X-Axis Mirror is not working properly with IK when skeleton is moved\nIntel Core i7, 16 Gb RAM, NVidia GeForce 2070 RTX\nWindows 10 x64\n\nBroken: 2.83 cfdb5d9a8b07 from 2020-02-19\nWorked: 2.83 5df494d75c9a from 2020-01-27 although it seems that this feature was introduced recently so technically it wasn't working before because symmetry didn't work with IK at all.\n\nPose Mode X-Axis Mirror is not working properly with IK when skeleton is moved or rotated from zero in Pose Mode.\n\n1. Open provided test file and try moving selected bone - opposite side will twitch weirdly instead of moving symmetrically.\n2. Now reset the skeleton to its default position and move the same bone - symmetry will work properly.\n3. Rotate first bone and try again - weird twitching again.\n[IK_Symmetry_Error.blend](IK_Symmetry_Error.blend)", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "Crash on accessing Bone Driver in Python\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nAccessing Bone Driver via Python:\n\n```\nbpy.context.active_object.animation_data.drivers['pose.bones[\"Bone.001\"].bbone_curveinz']\n```\ncauses crash.\n\n[python.blend](python.blend)\n - Press enter in console.", "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", "X RAY mode cannot be toggled while in pose mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R4 Graphics ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15018.12\n\nBroken: version: 2.93.5\n\n while modifying animations i tried to turn on xray mode to see inside a mesh while moving bones around only to find it was not functioning\n\nstep 1: create mesh\nstep 2: go to pose mode\nstep 3: toggle xray and see it do nothing\n", "context override for bpy.ops.view3d.view_selected doesn't work\nBlender 3.6\n\nTried to override currently selected items and run `bpy.ops.view3d.view_selected` (default blender operator binded on \"Numpad .\" by default) and it doesn't work. If I select objects manually with `obj.select_set(True)` it works.\n\nI've compared context's dict produced by `bpy.context.copy()` - the only difference between the context after `.select_set` were `selected_objects`, `selected_ids`, `selected_editable_objects` and I've overidden them.\n\nWay to reprodiuce:\n1) Open default blender scene.\n2) Make sure nothing is selected and move camera away.\n3) Run the code below - nothing happens\n4) Uncomment first two lines of code - operator works.\n\n```python\nimport bpy\n\n#for obj in bpy.data.objects:\n# obj.select_set(True)\n \nfor area in bpy.context.screen.areas:\n if area.type == 'VIEW_3D':\n for region in area.regions:\n if region.type == 'WINDOW':\n override = {\n 'area': area, \n 'region': region\n }\n override['selected_objects'] = bpy.context.view_layer.objects[:]\n override['selected_ids'] = bpy.context.view_layer.objects[:]\n override['selected_editable_objects'] = bpy.context.view_layer.objects[:]\n with bpy.context.temp_override(**override):\n bpy.ops.view3d.view_selected()\n # print(bpy.context.copy())\n```\n\n", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "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", "3D cursor sometimes can't do absolute grid snap\nOperating system: windows 10 v2004\nGraphics card: GTX 970\n\nBroken: 2.83.5\nWorked: none\n\n3D cursor sometimes can't do absolute grid snap.\nHere is the link of the bug capture. \n[Bug capture on YouTube](QzOqgiRM97c)\n\n\n\nDon't know how to reproduce from scratch, but many of my blender files has the same problem.\n[base.blend](base.blend)", "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\n\n", "Rolling the viewport always use last selection as pivot point\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 496.49\n\nBroken: version: 3.1.0\n\nWhen using the navigation setting Orbit Around Selection and Auto Depth, rolling the viewport always use the last selection as the pivot point, even when nothing is selected.\n\nThe expected behavior should be the same as having the orbit around selection disabled, when nothing is selected the rolling should pivot around the center of the screen.\n[blender_roll_bug.mp4](blender_roll_bug.mp4)\n\n1. Activate orbit around selection and auto depth in the navigation preferences\n2. Bind view3d.view_roll in the keymap using roll angle\n\n3. Select an object and roll the viewport\n4. De-select the object and roll the viewport again, the pivot remains in the same place\n\n", "3D cursor not respecting orientation setting if other tools are active.\n**System Information:**\nNA\n\n**Blender Version:**\nBroken: Blender 2.8 Beta 0f5b53ba4dc\nRetested with Blender 2.90 c880e54a95dd (2020-05-14 22:52)\n\n**Short description of error:**\nThere are a few inconsistencies with the 3D cursor in the 3D viewport. Here are the steps to reproduce.\n1. Load up Blender. For this example I will use left click select. Right click select also experiences this issue.\n2. Select the 3D cursor from the tool bar and in the tool settings change the orientation to something other than \"View\" (I'll use \"Geometry\" in my example).\n3. Switch to any other tool on the toolbar and move the 3D cursor using `Shift-RMB`. The 3D cursor will move, but it will take on the orientation of the viewport, not the set 3D cursor orientation.\n\nHere's some interesting things to note:\n\nIf the tool you have selected is \"Tweak\" (found by cycling through the \"Box select\" tool until you get to tweak), the 3D cursor orientation will respect the orientation set in the 3D cursor settings.\n\nThis is interesting because as @lichtwerk has pointed out in the comments, there are settings in the keymap panel to control this. In the keymap there are options under the section \"3D View>3D View (Global)>Set 3D cursor\" and \"3D View>Object mode>3D View Tool (tweak)>Set 3D cursor\". Both of these options default to have the orientation as \"View\" (but gray out) which is technically the cause for the behavior I saw in the original copy of this report, but for some reason, the \"tweak\" tool doesn't follow the keymap. Or both keymaps are supposed to reference the orientation set by the user (signified by the grayed out buttons in the keymap) and \"3D View (Global)>Set 3D cursor\" isn't doing that.", "Pose mode, Hotkey conflict between Bend and Bone Settings\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, branch: master, commit date: 2021-05-16 05:49, hash: \nThe Bend tool has the same hotkey than calling the Bone Settings menu.\n\nPose mode, Hotkey conflict between Bend and Bone Settings\n\n- Create an armature\n- Enter Pose mode\n- Go to Pose menu, expand Transform menu\n- Have a look at the Bend hotkey and the hotkey for the Bones settings menu.\n\nRelated task. T88342\nResolving this task may make this task here invalid. \n\n\n\n\n\n", "3D View - removing Hotkeys for Toolbar/Sidebar throws empty keymap 3D View Generic error\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\n\n3D View - removing Hotkeys for Toolbar/Sidebar in the View menu throws empty keymap 3D View Generic error in the console.\n\n\nOpen Blender. In the View menu of the 3D View remove the hotkeys for Toolbar and Sidebar. Open the Console ...\n\n\n\n" ]

[ "Bone Selection Issue\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics Intel 4.0.0 - Build 10.18.10.5069\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nCan not select bones using LMB/RMB in the same way as in 2.79b.\n\nI tried both mouse selection settings LMB/RMB, made no difference.\nI tried resetting to factory settings that did not solve the issue.\n\nIn Edit & Pose Modes I can only select the root bone and its head end using LMB/RMB.\nIf I repeatedly select the root bone or its head end it will cycle to the next bone or head end.\n\nBox select does not work on child bone(s), but will select all of the bones if the root bone is in the selection.\n\nCircle select will select child bone(s) and bone end(s). It also selects any bones that may be behind the target bone. \n\nI searched for a solution online with no luck.\nI found a post saying the had been solved (May 28, v2.80.72).\nI'm using a newer version (v2.80.75) guess it has returned.\n\nNo special setup, just make some bones and try to edit or pose them.", "you cannot select bones individually\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.2.0 - Build 10.18.10.3496\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nwhen creating a skeleton with several bones, in the pose mode, it is impossible to select individual bones without having to do it by clicking on the parent bone\n\nI created a simple three bone system with strusion, I entered the pose mode to individually select each bone and check if each one was selected, I did not get it with the left click, and with the right click the context menu of the bones opens , in the video I show the problem and the configuration of user preferences, which are the ones that are set by default{[F7638022](BUG_BONES_SELECT.mp4)}\n\n", "Cannot select most bones in Blender 2.80 release\nOperating system: Windows 10\nGraphics card: Intel HD Graphics\n\nBroken: 2.80 Release\nWorked: 2.79 and earlier versions\n\nCan only select the root bone of the armature using the mouse, any further bones are only selectable through the outliner or with circle select.\n\n1. Create a new armature\n2. Extrude one bone out\n3. See if the new bone is selectable or if only the first one is able to be selected\n\n**Solutions already attempted**\n- Switching between right and left mouse select\n- Checking and unchecking “lock object modes”\n- Uninstalling and reinstalling Blender 2.8, even deleting it’s folder in AppData\\Roaming\\Blender Foundation\\Blender\\2.80" ]

[ "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", "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", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Port Temporal AntiAliasing to Grease Pencil\nPort should be as simple as copying what Workbench does, with the addition of [D10414](D10414).\n\nSee parent task for more detail.", "EEVEE Material Preview works significantly slower than before. \nOperating system: MacOS Mojave 10.14.6 (18G9323)\nGraphics card: Intel Iris Graphics 550 1536 MB\nMemory: 16 GB 2133 MHz LPDDR3\nProcessor: 3,3 GHz Intel Core i7\n\nBroken: (example: 3.0.1, 2.93.8 edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: 2.83.19 \n\nSwitching to \"Material Preview\" view mode (or Rendered) and any manipulation of a material (like adding new node) takes significantly longer than in previous version. \n\n1. Open attached file\n2. Click \"Material Preview\" view mode\n3. Wait until material is fully visible in the viewport\n\nI know my machine is not a great performance beast and my OS is pretty outdated (but I can't upgrade because of other apps that I use), but you can clearly tell that 3.0.1 works much slower. I tried also 2.93.8 version (LTS tab on blender.org) and the result is the same. Only 2.83.19 worked faster. I attached a video, it's realtime screen recording (the only editing within the video is blurring the mess on my desktop). Also you can find a blend file that was use to perform the test. [performance-test.blend](performance-test.blend)\n\n[blender_performance.mp4](blender_performance.mp4)", "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.", "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", "Crash using get_devices_for_type() to choose cycles device with python\nOperating system: Ubuntu 20.04.1 LTS\nGraphics card: GTX 1070 + GTX 1070 + GTX 1050 Ti, NVIDIA 440.100\n\nBroken: 2.91.0 nightly, Commit date: 2020-10-19 22:48, Hash ea4d28aea034\nWorked: 2.83.7\n\nThis is a follow-up of #81520. Commit 1001adb500 fixes get_devices() but get_devices_for_type() remains broken. As previously something about the combination of OPTIX and OPENCL messes up the CUDA devices. Also I have since discovered that by changing the order getting OPTIX devices can mess with OPENCL devices.\n\nThis may be an issue specific to multi-gpu systems. I am willing to reconfigure hardware to help test if needed.\n\n\n```\nblender --factory-startup --python-expr \"import bpy; \\\n cuda_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('CUDA'); \\\n optix_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPTIX'); \\\n opencl_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPENCL'); \\\n cuda_devices[0].use = True\"\n```\n\nor\n```\nblender --factory-startup --python-expr \"import bpy; \\\n cuda_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('CUDA'); \\\n opencl_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPENCL'); \\\n optix_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPTIX'); \\\n cuda_devices[0].use = True\"\n\n```\n\n**More information:**\nIt seems like something is overwriting something else. Are these device locations supposed to be inter-related across types? Perhaps this can help. Consider the _different_ CUDA and OPENCL devices for the CPU at 0x7fa3700c8088 and 0x7fa370412188 respectively in the first example. In the second example below the single device at 0x7f72950c8088 is both the **CUDA and OPENCL** device. Which behavior is correct? (And does any of this potentially indicate other issues?)\n\nMy output (formatted)\n```\nblender --factory-startup --python-expr \"import bpy; \\\n cuda_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('CUDA'); \\\n print('CUDA devices before getting anything else', cuda_devices); \\\n optix_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPTIX'); \\\n print('CUDA devices before getting OPENCL devices', cuda_devices); \\\n print('OPTIX devices before getting OPENCL devices', optix_devices); \\\n opencl_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPENCL'); \\\n print('CUDA devices after getting OPENCL devices', cuda_devices); \\\n print('OPTIX devices after getting OPENCL devices', optix_devices); \\\n print('OPENCL devices', opencl_devices); \\\n cuda_devices[0].use = True\"\n\nCUDA devices before getting anything else [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa3700c7f08>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa3700c7f88>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7fa3700c8008>,\n <bpy_struct, CyclesDeviceSettings(\"AMD Ryzen 9 3900X 12-Core Processor\") at 0x7fa3700c8088>\n]\nCUDA devices before getting OPENCL devices [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa3700c7f08>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa3700c7f88>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7fa3700c8008>,\n <bpy_struct, CyclesDeviceSettings(\"AMD Ryzen 9 3900X 12-Core Processor\") at 0x7fa3700c8088>\n]\nOPTIX devices before getting OPENCL devices [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa370412208>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa370412288>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7fa370412308>\n]\nCUDA devices after getting OPENCL devices [\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7fa3700c7f08>,\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7fa3700c7f88>,\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7fa3700c8008>,\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7fa3700c8088>\n]\nOPTIX devices after getting OPENCL devices [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa370412208>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7fa370412288>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7fa370412308>\n]\nOPENCL devices [\n <bpy_struct, CyclesDeviceSettings(\"AMD Ryzen 9 3900X 12-Core Processor\") at 0x7fa370412188>\n]\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\nand\n```\nblender --factory-startup --python-expr \"import bpy; \\\n cuda_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('CUDA'); \\\n print('CUDA devices before getting anything else', cuda_devices); \\\n opencl_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPENCL'); \\\n print('CUDA devices before getting OPTIX devices', cuda_devices); \\\n print('OPENCL devices before getting OPTIX devices', opencl_devices); \\\n optix_devices = bpy.context.preferences.addons['cycles'].preferences.get_devices_for_type('OPTIX'); \\\n print('CUDA devices after getting OPTIX devices', cuda_devices); \\\n print('OPENCL devices after getting OPTIX devices', opencl_devices); \\\n print('OPTIX devices', optix_devices); \\\n cuda_devices[0].use = True\"\n\nCUDA devices before getting anything else [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7f72950c7f08>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7f72950c7f88>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7f72950c8008>,\n <bpy_struct, CyclesDeviceSettings(\"AMD Ryzen 9 3900X 12-Core Processor\") at 0x7f72950c8088>\n]\nCUDA devices before getting OPTIX devices [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7f72950c7f08>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7f72950c7f88>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7f72950c8008>,\n <bpy_struct, CyclesDeviceSettings(\"AMD Ryzen 9 3900X 12-Core Processor\") at 0x7f72950c8088>\n]\nOPENCL devices before getting OPTIX devices [\n <bpy_struct, CyclesDeviceSettings(\"AMD Ryzen 9 3900X 12-Core Processor\") at 0x7f72950c8088>\n]\nCUDA devices after getting OPTIX devices [\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7f72950c7f08>,\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7f72950c7f88>,\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7f72950c8008>,\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7f72950c8088>\n]\nOPENCL devices after getting OPTIX devices [\n <bpy_struct, CyclesDeviceSettings(\"\") at 0x7f72950c8088>\n]\nOPTIX devices [\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7f7295420108>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1070\") at 0x7f7295420188>,\n <bpy_struct, CyclesDeviceSettings(\"GeForce GTX 1050 Ti\") at 0x7f7295420208>\n]\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n", "Can't control image transparency\nSystem:\n```\nKernel: 5.4.64-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 \nDesktop: GNOME 3.36.6 Distro: Manjaro Linux\n```\nCPU:\n```\nTopology: Dual Core model: Intel Core M-5Y10c bits: 64 type: MT MCP \narch: Broadwell rev: 4 L2 cache: 4096 KiB \nflags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx \nbogomips: 7981 \nSpeed: 798 MHz min/max: 500/2000 MHz Core speeds (MHz): 1: 798 2: 798 \n```\n 3: 798 4: 798 \nGraphics:\n```\nDevice-1: Intel HD Graphics 5300 vendor: Hewlett-Packard driver: i915 \nv: kernel bus ID: 00:02.0 \nDisplay: x11 server: X.org 1.20.8 driver: intel unloaded: modesetting \nresolution: <xdpyinfo missing> \nOpenGL: renderer: Mesa Intel HD Graphics 5300 (BDW GT2) v: 4.6 Mesa 20.1.7 \ndirect render: Yes \n```\n\nBroken: Blender 2.90.0\n\tbuild date: 2020-09-04\n\tbuild time: 21:14:50\n\tbuild commit date: 2020-08-31\n\tbuild commit time: 11:26\n\tbuild hash: 0330d1af29c0\n\tbuild platform: Linux\n\tbuild type: Release\n\nI've also tested on 2.83 from the site, and some appimages i found on github of 2.9 and 2.83 it did not work on any of those.\n\nCan't control transparency of images on this machine, the image keeps the same transparency with every value except 0.0 where it completely disappears.\nI've used blender on a different system (with different hardware and linux distro) and this error does not occur there, just to check I was pressing the right buttons.\nI can control the transparency of the basic cube through Materials>Viewport Display>Color, so it's not problem with transparency in general\n\nSince this only happened on this system I can't give many details I just added a image (background or reference) and tried to control it's transparency\n\nThanks for your time, have a nice day.", "Trouble starting Blender on Wayland with dedicated NVIDIA card\nOperating system: openSUSE Tumbleweed\nGraphics card: NVIDIA Corporation GA106M / GeForce RTX 3060\n\nBroken: 3.61, 8bda729ef4dc, 2023-07-17\n\nWhen trying to launch Blender, with Wayland using my dedicated graphics card through switcherooctl, I'm getting \"EGL_BAD_SURFACE\" errors:\n```\nEGL Error (0x300D): EGL_BAD_SURFACE: An EGLSurface argument does not name a valid surface (window, pixel buffer or pixmap) configured for GL rendering.\n```\n\nThis causes Blender to hang, and cannot respond to Wayland events and can't close, so I have to end the process with GNOME system monitor, or with the command: `killall -s 9 blender`.\n\nswitcherooctl launch -g 1 ~/Downloads/blender-3.6.1-linux-x64/blender\n\n", "Segfault after F12 render with multi-GPU Intel ARC A770 and experimental oneAPI packages on Debian\nOperating system: Linux-6.4.0-1-amd64-x86_64-with-glibc2.37 (Debian sid)\nGraphics card: two identical Intel ARC A770 Limited Edition 16GB\n\nBroken: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-25 19:23, hash: aebc743bf1c7\nWorked: 3.4, 3.4.1, 3.5.1\n\nSegfault when rendering Victor benchmark scene with F12 with second Intel ARC A770. This happens only when the second GPU is chosen as rendering device in Cycles. If both GPUs are selected first one seems to work correctly, but the second one causes a crash/error.\nEmbree on GPU does not seems to matter.\n\nBoth F12 and viewport renders with the second GPU give:\n`oneAPI kernel \"shader_eval_curve_shadow_transparency\" execution error: got runtime exception \"Native API failed. Native API returns: -50 (PI_ERROR_INVALID_ARG_VALUE) -50 (PI_ERROR_INVALID_ARG_VALUE)\"`\n\nRelevant info:\nI'm using following packages from experimental sources (I'm impatient I know :) ), so this crash might be very well caused by their incompatibility with Debian sid:\n`libigc1` - 1.0.13822.1-1\n`libigdfcl1` - 1.0.13822.1-1\n`intel-opencl-icd` - 23.13.26032.7-1\nRest of the packages, including all dependencies are from Debian sid.\n\nFull backtrace:\n\n```\n(gdb) backtrace full\n#0 0x0000000001cfee77 in ?? ()\nNo symbol table info available.\n#1 0x0000000001cffab9 in ?? ()\nNo symbol table info available.\n#2 0x0000000001b0fa9c in ?? ()\nNo symbol table info available.\n#3 0x0000000000f376a3 in ?? ()\nNo symbol table info available.\n#4 0x00007fffebaa63ec in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444\n ret = <optimized out>\n pd = <optimized out>\n out = <optimized out>\n unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737147199792, -8317621660586406251, -286296, 11, 140737488344416, 140734520795136, 8317937541230038677, 8317594907036290709}, mask_was_saved = 0}}, priv = {\n pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}\n not_first_call = <optimized out>\n#5 0x00007fffebb26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\nNo locals.\n(gdb)\n```\n\n1. On Debian sid install experimental packages mentioned above.\n2. Set second ARC GPU as a rendering device in Blender. \n3. Open Victor benchmark scene.\n4. Hit F12 and wait for the crash.", "OSL on the GPU displays all black for Voronoi Distance > Bump Height\nSystem:\nWindows 11\nRTX3090Ti gpu\n\nBump output is pitch black when using Voronoi (Distance) output into Bump Height. Colorramp in between does not fix it. Noise output into Bump Height works fine.\n(Blender 3.5 in cycles)\n\nedit: more useful info + screenshot + isolated blend file\n\nRunning OSL on the CPU works fine, only the new GPU support seems affected.", "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)", "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", "Fix big LIghtCache restriction\nAs reported in #78529 saving big lightcache is impossible due to blocksize restriction.\n\nFor now we restrict the lightcache size that can be written to disk but it would be better to slice the huge textures to avoid such limitation.\n\nHowever this needs some refactors in GPUTextures namely the need of a properly exposed `glTexSubImage2D` and `glTexSubImage3D`." ]

[ "Blender runs super slow after nVidia Driver Update\nWindows 10 64bit\nNVIDIA GeForce 940MX\n\nBroken: 2.78a\nWorked: 2.78a\n\nThe blender app worked perfectly, it ran 100% correctly and I had no problem. I made an update to the NVIDIA driver a day ago and I tried opening blender today and it was soooooo slow. I have no idea why. As my CPU I have Intel i5 7th Gen. Blender ran just fine when I had it running on the CPU's graphics too but right now it doesn't. I have tried the portable version and the installer on 64bit.\n\nNot really any steps. I just updated the driver and that was all. Other apps work just fine.\n" ]

[ "Blender-3.1 (git) boolean in Geomenty Nodes issue\nOperating system:\nGraphics card:\n\nBroken: All\n\nBulean issue like T91889\nbut now in GN\n[2021-11-25_22-29-42.mp4](2021-11-25_22-29-42.mp4)\nTest Scene\n[parktronic1-Blender-3.blend](parktronic1-Blender-3.blend)", "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", "Including node group attribute into NodeTreePath\nAt this moment `SpaceNodeEditorPath` has method append with parameters `node_tree` and `node`. This method is adding `NodeTreePath` into path. But event if `node` parameter was added into `append` method the `NodeTreePath` object does not have any information about root node of group tree.\n[bpy.types.SpaceNodeEditorPath](bpy.types.SpaceNodeEditorPath.html#bpy.types.SpaceNodeEditorPath.append), [bpy.types.NodeTreePath](bpy.types.NodeTreePath.html)\n\n\n\nAccording the fact that one group tree can be used by many group nodes it quite important to have information about via which group node the group tree is eddited. Sverchok addon is used to color problem nodes. Without information about group nodes in path it is impossible to mark such nodes.\n\nI would not bother if there was any workaround. What I actually was trying:\n```\nnode_tree_path.name = 'group_node'\nAttributeError: 'NodeTreePath' object has no attribute 'name'\n\nbpy.types.NodeTreePath.node = bpy.props.StringProperty()\nnode_tree_path.node = 'name'\nAttributeError: 'NodeTreePath' object attribute 'node' is read-only\n\nnode_tree_path['node_name'] = 'name'\nTypeError: bpy_struct[key] = val: id properties not supported for this type\n\narea_names = {}\narea_names[node_tree_path] = 'my_name'\n```\nEven last example would not work for several reasons. ID of path can be changed on undo event for example. If area is splitting into two I'm not able to update second area in the dictionary.\n\nI think, for API consistency, either `node` parameter should be removed out from the `update` method or `node` attribute should be added to `NodeTreePath` object. I would prefer second choice.", "Undo doesn't consider changes in nodetree when object is in edit and texture paint mode\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.79-3.4\n\nFor reference: this is due to this commit 4a08b974f4\nFrom the commit message:\n\"don't store undo steps for property changes in paint & edit modes.\"\n\nWhen in edit and texture paint mode, I can't undo changes, that I made in the shader editor. \n\n\n - Open .blend\n - Move some verts.\n - Change a shader node setting.\n - Press {key Ctrl Z}.\n # The verts move back, but the node setting remains.\n[#71895-undo-not-undoing-shader-nodes.blend](T71895-undo-not-undoing-shader-nodes.blend)", "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", "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", "Blender development todo list -- Render\nNOTE: this is a direct dump of Render (without cherrypicking the valid items)\n\n### Render & UI\n\n- [ ] While rendering, manipulating images (like reload, resizing generated) can still crash Blender. Better image \"owner\" locking is required for 2.5 (#28477)\n- [ ] While rendering, several UI changes can cause crashes (#24758)\n- [ ] Rendering can't really use normal scene data if ui is interactive without causing all kinds of trouble, for examples and related issues see the item above this one.. and the reports (#26535)\n- [ ] Renaming scene leads to missing rendered result in image editor and compositor (see (#30222))\n- [ ] Rendering with File Output nodes could produce unwanted output images, see (#38605)\n- [ ] Shaded draw mode (using render code for vertex colors) is most certainly not coming back\n- [ ] Color Management can be communicated better, like when sampling colors in Image Window it confuses (could indicate such). Color Management also wasn't added backward compatible, disabling it gives dark results.\n- [ ] Compositor \"file out\" node doesn't work for FSA, and as color management troubles too.\n- [ ] FSA render uses temp files with names preventing other Blender instances to render too. (#28314)\n- [ ] Texture nodes have been implemented by recursively (backwards) calling parent nodes, this gives issues for viewers, previews and threads in general.We will try to keep it stable, but the functionality for this is going to replaced with a better shader system in 2.6. (compositor and material nodes call nodes forward, sorted on dependency. Each node is only called once this way).\n- [ ] Render display in Image window, for a window previously showing UV editor, doesn't restore correctly. (#26828). Code for this is too much spread around and fuzzy, needs full revision.\n- [ ] Object transform is not possible during rendering #37019\n- [ ] Don't render and warn when a driver or pre-render script can't be executed, a texture is missing, physics are not baked. Needed e.g. when renderfarms have scripts blocked.\n\n### Node Textures\n- [ ] Grouping texture nodes affects on data range #45696\n\n### Baking\n- [ ] add option to smooth vertex colors as a post process after baking #35066.\n- [ ] Baking to a low-res textures might miss pixels which lies on the UV island boundary #37681\n- [ ] Vertex baking might cause AO artifacts #44178\n- [ ] Support dupligroups #43553\n- [ ] Modifier produces non deterministic effects #42015\n- [ ] Update Blender side baking to support different topologies needed for adaptive subdivision #49405", "bpy.context.temp_override - TypeError: Area not found in screen\nBlender 3.5.1\n\nWhen I try to run `bpy.context.temp_override` with area that's not present on current screen I get the error below. \nIt's useful feature that helps to run operators without switching screen.\n\nTried the same thing with old context override workflow like `bpy.ops.node.clipboard_copy(temp_override)` and it works without errors.\n\n```\n# Error: Python: Traceback (most recent call last):\n# File \"test_nodes_copy.blend\\error\", line 37, in <module>\n# File \"test_nodes_copy.blend\\error\", line 25, in copy_node_graph_to_active_object\n# TypeError: Area not found in screen\n```\n\n## ways to reproduce\n\nI've attached .blend file with the setup and code below that's causing the error - to reproduce you can open it and just play the \"error\" script from \"Scripting\". There is also \"working\" script that using old context override and it works without errors.\n\nCode that causes error (the code itself is copying node graph from one material to another - haven't found other method to do so besides calling operators on areas from other screen):\n\n```python\nimport bpy\n\ndef get_shader_editor_context():\n for screen in bpy.data.screens:\n for area in screen.areas:\n if area.type == \"NODE_EDITOR\":\n for space in area.spaces:\n if space.tree_type == \"ShaderNodeTree\":\n context_override = {\"area\": area, \"space\": space, \"screen\": screen}\n return context_override\n\ndef copy_node_graph_to_active_object(material):\n temp_override = get_shader_editor_context()\n old_material = bpy.context.object.active_material\n new_material = material\n \n # remove all nodes from the current material\n for n in old_material.node_tree.nodes[:]:\n old_material.node_tree.nodes.remove(n)\n \n # change current material and make other window's shader editor is updated\n bpy.context.object.active_material = new_material\n temp_override['space'].node_tree = new_material.node_tree\n \n with bpy.context.temp_override(**temp_override):\n # select all nodes and copy them to clipboard\n for node in new_material.node_tree.nodes:\n node.select = True\n bpy.ops.node.clipboard_copy()\n\n # back to original material\n bpy.context.object.active_material = old_material\n temp_override['space'].node_tree = old_material.node_tree\n bpy.ops.node.clipboard_paste(offset=(0,0))\n\n\ncopy_node_graph_to_active_object(bpy.data.materials['test'])\n```\n\nDeprecated temp context override method that's working:\n```python\nimport bpy\n\ndef get_shader_editor_context():\n for screen in bpy.data.screens:\n for area in screen.areas:\n if area.type == \"NODE_EDITOR\":\n for space in area.spaces:\n if space.tree_type == \"ShaderNodeTree\":\n context_override = {\"area\": area, \"space\": space, \"screen\": screen}\n return context_override\n\ndef copy_node_graph_to_active_object(material):\n temp_override = get_shader_editor_context()\n old_material = bpy.context.object.active_material\n new_material = material\n \n # remove all nodes from the current material\n for n in old_material.node_tree.nodes[:]:\n old_material.node_tree.nodes.remove(n)\n \n # change current material and make other window's shader editor is updated\n bpy.context.object.active_material = new_material\n temp_override['space'].node_tree = new_material.node_tree\n \n # select all nodes and copy them to clipboard\n for node in new_material.node_tree.nodes:\n node.select = True\n bpy.ops.node.clipboard_copy(temp_override)\n\n # back to original material\n bpy.context.object.active_material = old_material\n temp_override['space'].node_tree = old_material.node_tree\n bpy.ops.node.clipboard_paste(temp_override, offset=(0,0))\n\n\ncopy_node_graph_to_active_object(bpy.data.materials['test'])\n```\n\n", "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", "Simulation Nodes: bake UI in simulation node\n_No response_\n\n", "\"Assign Material Slot\"-Shortcut is created in the wrong place\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n\"Assign Material Slot\"-Shortcut is created in the wrong place, therefore does not work.\n\n\n[Material Shortcuts.blend](Material_Shortcuts.blend)\n\nBy rightclicking, the shortcut is created in the Input Preferences under `3D-View > Object Mode > Object Mode (Global)` which is wrong. It simply does nothing in Object mode. In order to work it has to be manually created under `3D-View > Mesh > Mesh (Global)` with the same entry name.\n\n\n\n", "Geometry Nodes: Store Named Attribute does not propagate existing data when the domain changes\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 3.6.0 Beta\nWorked: Never.\n\nWhen using `Store Named Attribute` using a selection to store data on a subset of the geometry, the remaining elements keep their data that is already stored in that attribute. Because the name space of all attributes is shared, regardless of the domain, storing under the same name on a different domain will overwrite the attribute data. However, this will not implicitly propagate the existing attribute data for elements outside of the selection. That would be the expected behavior, as without a change of domain this is what happens and implicit domain conversions happen regularly in geometry nodes as necessary.\n\n| On a top face | On bottom vertex |\n| -- | -- |\n|  |  |\n\n[store_attribute_propagation.blend](attachment)\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)", "Animated Values in Node Trees and Geometry Nodes Modifier are not distinguishable \nOperating system: all\nGraphics card: all\n\nBroken: blender-3.0.0-alpha+master.12e8c783535c and below\n\nHello dear Blender devs,\nHello dear Geometry Nodes developers and maintainers,\n\nI did wait some time before reporting this as a \"bug\" as from some perspective this might sound like a feature request. But as there are some, to users unidentifiable names used, I guess this is may very well count as a bug.\n\nWhen working in Geometry nodes it is important to be able to keyframe some values and properties to achieve more controlled and art directable Animation of the Asset. While the setting of keyframes works really well, it gets really complicated to tell the different animation channels apart as they neither show the nodes name nor the nodes Label.\n\n\nOpen attached file, try to figure out which graph in the editor belongs to which Node.\n[geonodes_01.blend](geonodes_01.blend)\n\nFor simplification I added three screenshots each showing one of the three cases I could Isolate where this bug appears:\n\n1.) Animating Node Values in the Geometry Nodes Tree\n\n\n\n2.) Animating Exposed Custom Properties of the Geometry Nodes Modifier\n\n\n\n3.) Animating Node Values inside the Shader Graph.\n\n\nThank you in advance for your evaluation of this bug report\n\nAlex / zuggamasta", "crash when i try to make instances real for nodes\nhi , in attached files all info about the crash , its when i try to make instances real for nodes modifier addon scifi pro + flex\nso can i fix it ?\n\n" ]

[ "\"Copy data path\" incorrect with a cycles lamp strength value\nBroken: 2.80\n\nRight clicking the 'Strength' value of a cycles node-based lamp, and selecting 'copy data path' results in:\nnodes[\"Emission\"].inputs- [x].default_value\n\nThis seems to be incorrect, as it cannot be pasted into a driver directly, rather it should be:\nnode_tree.nodes[\"Emission\"].inputs- [x].default_value\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", "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```", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "Blender Crashing When Painting Stroke into a \"Moving Animated Character\" (heap-use-after-free)\nBroken: 4.0 alpha\nBroken: version: 2.79 - 2.82 (sub 7)\nWorked: Never\n\nI have this experiment of making LIVE talking head, via OSC. And I noticed that if I tried painting a stroke on a talking moving animated head, it will crash. Even with timeline not running.\n\nI got a video (Might need iPhone X with MOM addon to test this....) :\njhHdG6ZXFDU\n\n- Open attached file\n- Run animation\n- Paint over the animated object\n[paint_animated_shapekey_bug.blend](paint_animated_shapekey_bug.blend)\n\n\n", "Crash when baking a normal map from procedural materials\nOperating system:\nManjaro w/ KDE\nGraphics card:\nNvidia GTX 1060 6GB\n\nBroken: 2.80 Beta, 5e626e766459, branch: blender2.7, 2019-06-13\n\n\nI've sculpted a high poly model from the lowpoly one - baking normals from that works fine.\nWhen I created procedural materials using Geometry Pointiness, Noise, a painted texture and other sources to create additional normal information - the baking crashes.\n\nHere's the project file. It's huge (781 MB), but compresses very well (turns out the painted texture was wasting a lot of space), without it the file is only 12 MB).\n\n[Barrel_02 08.zip](Barrel_02_08.zip)\n\nNormal map baked from Highpoly model to Lowpoly model:\n\nIf you disconnect the two materials on the highpoly model and just use a default Principled shader, it bakes fine.\n\n\nThe baking process crashes at various stages. First bake crashed after an hour or so, next attempts crashed much quicker.\n\nCrash logs:\n\n[Barrel_02 08.crash.txt](Barrel_02_08.crash.txt)\n\n[Barrel_02 07.crash.txt](Barrel_02_07.crash.txt)\n\n[Barrel_02 06.crash.txt](Barrel_02_06.crash.txt)", "Crash opening file using Clump Curves on Particle Children \n****\n\nversion: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d49d, type: Release\nbuild date: 2019-12-04, 14:30:40\nplatform: Windows\n\n***********************************************************\n\nWhen I worked on a project using particles, after a short break I wasn´t able to reopen the project. The project crashed right after opening. When starting Blender from console the only error I could find was:\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF706DC271E\n\nno Blender log file was written!\n\nEven in debug mode there were no more hints but his one. I opened the project in an Ubuntu VM and it also crashed there. No chance to recover the file.\n\n\nUsing Particle following a nurbspath with Force Field \"Curve\".\nParticles rendered as objects.\nUsed Simple Children.\nWhen ticking the box: Use Clump Curve it crashes.\n\nEither Blender crashes right after ticking the box or when reopen the project. The latter then means that I´m not able to recover my work at all.\nI might have to do with particles already baked or not. Not sure. \n\n[T72763_crash_log.txt](T72763_crash_log.txt)\n\nfile written from c2a37867f2 that crashes on file read:\n[#72763.blend](T72763.blend)\nfile written from 2.79b that crashes on file read:\n[T72763_279.blend](T72763_279.blend)", "Blender GUI freezes when using activate_init = True\nOperating system: W10 64bit\nGraphics card: nVidia GTX 970\n\nBroken: blender-2.83-71b1ee940bb0-windows64\n\n\nOnce this bug T71112 was fixed I tried to \"use activate_init = True\" in my addon, but I'm still getting Blender GUI to freeze.\n\n* Open up [bugreport.blend](bugreport.blend) and run the script in Text Editor\n* Search for \"Name Location\" operator and run it\n* Type a text and hit OK. An Empty object is placed into the scene, named by what you typed in, but whole GUI becomes unresponsive.\n", "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", " EXCEPTION_ACCESS_VIOLATION when entering Edit Mode\nOperating system: Windows 10 1903 (18362.239)\nGraphics card: Intel HD Graphics 4000\n\n***Broken:***\nBlender 2.80 (sub 75) / 2019-07-29 09:44 AM Windows / Stable\nBlender 2.81 (sub 1), branch: master, commit date: 2019-08-13 11:31, hash: 6f9cbbc8ec4f\n***Worked:***\nBlender 2.79 (copied mesh over through copybuffer.blend)\n\n\nWhen entering edit mode of a specific object Blender crashes with EXCEPTION_ACCESS_VIOLATION. Logs and example .blend provided.\n\nThe issue shouldn't be in my GPU, since the same issue persists even with Software Rendering.\n\n1. Open up example file\n[window_broken.blend](window_broken.blend)\n\n2. Select `window_panes` and enter Edit Mode\n3. Get EXCEPTION_ACCESS_VIOLATION\n\n**Logs (2.80 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n**Logs (2.81 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "simulation in new scene causes crash in original scene's simulation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\n**steps**\n- make cube an active rigid body. \n- play simulation\n- then click on new scene button and on full copy.\n- in the new scene, rewind playhead to frame 0\n- run the simulation.\nBlender should crash.\n\nThere are more ways to cause crash when full scene copy is done (see comments), but I guess these will stem from single issue.", "Changes to the asset catalog UI\n- - [x] Nest real catalogs under \"All\" item. (e38532773b)\n- - [x] Remove `'HOME'` icon. (fca6a9fe3f)\n- - [ ] Improve layout to make relationships more clear.\n- - [x] Expand the selected item on click. (56ff954030)\n- - [x] Don't expand all top-level catalogs. (c0122cc888)\n- - [ ] Add hierarchy lines.\n- - [ ] Asset catalog icon for each row?", "Crash choice asset library\nOperating system: Win 10\nGraphics card: RX460 2gb\n\nBroken: (3.2)\nWorked: (3.0)\n\n[Tests.zip](Tests.zip)\n\n- Extract archive and add `...\\Tests\\Test Asset\\` path to asset libraries\n- Open Asset library blend file\n- Open New file\n- Change any editor to Asset Browser\n# List contents of `Test Asset` library\n\nIt should crash.\nSometimes, omitting step 2 would prevent crash, but no assets would be shown.\nAlso omitting `tests` folder somehow prevented the crash, \n\nCrash log:\n[P3143: (An Untitled Masterwork)](P3143.txt)\n```\n# Blender 3.4.0, Commit date: 2022-08-14 18:40, Hash 659b63751d63\nbpy.context.space_data.params.asset_library_ref = 'Test Asset' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : UNKNOWN EXCEPTION\nException Address : 0x00007FFF3F66D759\nException Module : KERNELBASE.dll\nException Flags : 0x00000001\nException Parameters : 0x4\n\tParameters- [x] : 0x0000000019930520\n\tParameters- [x] : 0x000000FB7C5FD460\n\tParameters- [x] : 0x00007FF678278398\n\tParameters- [x] : 0x00007FF66CA80000\n\n\nStack trace:\nKERNELBASE.dll :0x00007FFF3F66D6F0 RaiseException\nVCRUNTIME140.dll :0x00007FFF283E63F0 CxxThrowException\nblender.exe :0x00007FF672BC42D0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC36C0 nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_string<char,std::char_traits<char\nblender.exe :0x00007FF672BC82B0 blender::io::serialize::JsonFormatter::serialize\nblender.exe :0x00007FF66E27B970 blender::ed::asset::index::AssetIndexFile::write_contents\nblender.exe :0x00007FF66E277D40 blender::ed::asset::index::update_index\nblender.exe :0x00007FF66E653B90 filelist_readjob_list_lib\nblender.exe :0x00007FF66E654370 filelist_readjob_recursive_dir_add_items\nblender.exe :0x00007FF66E653710 filelist_readjob_asset_library\nblender.exe :0x00007FF66DB341A0 do_job_thread\nblender.exe :0x00007FF672E5A810 _ptw32_threadStart\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThreads:\nThread : 00000448\nntdll.dll :0x00007FFF41D2C620 ZwDelayExecution\nblender.exe :0x00007FF672B3A220 BLI_thread_is_main\n\n\nThread : 000069ac\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003130\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069cc\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000054bc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000026c0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008788\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000aa4c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000608c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009c7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008d78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029c4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009918\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000162c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001478\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000040b4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000036d0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003468\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007444\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005208\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000059e4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a018\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000085a8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b1ac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000921c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005544\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad94\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067e0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000401c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b360\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008b38\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005884\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003334\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008c60\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a2e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nnvoglv64.dll :0x00007FFE819D057C Symbols not available\n\n\nThread : 00009be0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFF3F690C30 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003f9c\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007978\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ace0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ada4\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFF3012457B Symbols not available\n\n\nThread : 00009dbc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005f9c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009dac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000405c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000834c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000099e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00006284\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005ec8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a8fc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003240\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00000a10\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000082dc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000196c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004374\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007dec\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004294\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000559c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a90\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004cc8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000055f8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069a4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005c40\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001a80\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004308\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000081c8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b0d4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004bc0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009d28\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008010\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF66CA80000 3.4.0.0 blender.exe C:\\Users\\John\\Desktop\\blender-3.4.0-alpha+master.659b63751d63-windows.amd64-release\\blender.pdb \n0x00007FFF41C90000 10.0.19041.662 ntdll.dll \n0x00007FFF40620000 10.0.19041.662 KERNEL32.DLL \n0x00007FFF3F640000 10.0.19041.662 KERNELBASE.dll \n0x00007FFF40C70000 10.0.19041.546 WS2_32.dll \n0x00007FFF41310000 10.0.19041.662 RPCRT4.dll \n0x00007FFF41170000 10.0.19041.685 USER32.dll \n0x00007FFF1D640000 tbb.dll \n0x00007FFF3FCC0000 10.0.19041.662 win32u.dll \n0x00007FFF41940000 10.0.19041.685 GDI32.dll \n0x00007FFF1D600000 tbbmalloc.dll \n0x00007FFF3FAB0000 10.0.19041.685 gdi32full.dll \n0x00007FFF3FA10000 10.0.19041.546 msvcp_win.dll \n0x00007FFF3F910000 10.0.19041.546 ucrtbase.dll \n0x00007FFF417D0000 10.0.19041.610 ADVAPI32.dll \n0x00007FFF406E0000 7.0.19041.546 msvcrt.dll \n0x00007FFF41980000 10.0.19041.662 sechost.dll \n0x00007FFF3FED0000 10.0.19041.662 SHELL32.dll \n0x00007FFF283E0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFF3AE70000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFF40F00000 10.0.19041.546 SHLWAPI.dll \n0x00007FFEC90D0000 14.29.30139.0 MSVCP140.dll \n0x00007FFF3FC70000 10.0.19041.546 CFGMGR32.dll \n0x00007FFF36DA0000 10.0.19041.488 dbghelp.dll \n0x00007FFF3FBC0000 10.0.19041.662 bcrypt.dll \n0x00007FFF40CE0000 10.0.19041.546 ole32.dll \n0x00007FFF41470000 10.0.19041.662 combase.dll \n0x00007FFEC8180000 10.0.19041.546 OPENGL32.dll \n0x00007FFF41440000 10.0.19041.546 PSAPI.DLL \n0x00007FFF41A20000 10.0.19041.662 shcore.dll \n0x00007FFF3FEA0000 10.0.19041.546 IMM32.dll \n0x00007FFEB74B0000 9.0.0.0 openvdb.dll \n0x00007FFEC5BE0000 59.16.100.0 avformat-59.dll \n0x00007FFEB4FB0000 59.18.100.0 avcodec-59.dll \n0x00007FFF1D5D0000 59.4.100.0 avdevice-59.dll \n0x00007FFF40FC0000 10.0.19041.546 OLEAUT32.dll \n0x00007FFEC9030000 6.4.100.0 swscale-6.dll \n0x00007FFEC5A00000 57.17.100.0 avutil-57.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFEC5190000 1.21.1.0 OpenAL32.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFEC29E0000 2.0.20.0 SDL2.dll \n0x00007FFF39630000 libgmpxx.dll \n0x00007FFEC0D70000 3.10.2150.1013 python310.dll \n0x00007FFF40780000 10.0.19041.546 SETUPAPI.dll \n0x00007FFF300E0000 tbbmalloc_proxy.dll \n0x00007FFF31280000 6.10.19041.488 COMCTL32.dll \n0x00007FFF1C490000 10.0.19041.1 AVIFIL32.dll \n0x00007FFF39120000 10.0.19041.546 VERSION.dll \n0x00007FFF3D210000 10.0.19041.546 dwmapi.dll \n0x00007FFF1C460000 10.0.19041.546 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFF27EE0000 10.0.19041.546 Secur32.dll \n0x00007FFECB6B0000 4.3.100.0 swresample-4.dll \n0x00007FFECBF00000 10.0.19041.1 AVICAP32.dll \n0x00007FFF2EBF0000 10.0.19041.546 WINMM.dll \n0x00007FFF20660000 10.0.19041.1 MSACM32.dll \n0x00007FFECB5D0000 10.0.19041.1 MSVFW32.dll \n0x00007FFF24F20000 10.0.19041.1 winmmbase.dll \n0x00007FFF3F280000 10.0.19041.662 SSPICLI.DLL \n0x00007FFF3D240000 10.0.19041.546 kernel.appcore.dll \n0x00007FFF3D520000 10.0.19041.662 windows.storage.dll \n0x00007FFF3EE40000 10.0.19041.662 Wldp.dll \n0x00007FFF3CE80000 10.0.19041.610 uxtheme.dll \n0x0000022043090000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFF3F300000 10.0.19041.546 profapi.dll \n0x00007FFF41880000 2001.12.10941.16384 clbcatq.dll \n0x00007FFF38BE0000 10.0.19041.546 MMDevApi.dll \n0x00007FFF3F180000 10.0.19041.546 DEVOBJ.dll \n0x00007FFF38EF0000 10.0.19041.662 AUDIOSES.DLL \n0x00007FFF3E980000 10.0.19041.546 powrprof.dll \n0x00007FFF3E840000 UMPDC.dll \n0x00007FFF41AD0000 10.0.19041.662 MSCTF.dll \n0x00007FFF39850000 10.0.19041.662 AppXDeploymentClient.dll \n0x00007FFE80E80000 31.0.15.1640 nvoglv64.dll \n0x00007FFF3AE30000 10.0.19041.546 \n```\n\n\n - The conditions have been changed, but the error is still present. -----------------------------------------------------------", "Blender crashes when computing normals of a particular mesh\nOperating system: macOS (Monterey) 12.1 (21C52)\nGraphics card: AMD Radeon Pro 5300M 4 GB\nGraphics card: Intel UHD Graphics 630 1536 MB\n\nBroken: 3.0.0 (3.0.0 2021-12-03)\nWorked: Was not observed to work\n\nCrashes on opening file attached. Crashes on other files. Randomly crashes when editing using models exported from Roblox (.obj files).\n\nOpen attached blend file. You get the crash report (crashes with different stacks for other files and when editing):\n\n[hacker_revenge.blend](hacker_revenge.blend)\n\n```\nlines=12, name=Translated Report\nProcess: Blender [2869]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.0.0 (3.0.0 2021-12-03)\nCode Type: X86-64 (Native)\nParent Process: zsh [1661]\nResponsible: Terminal [1596]\nUser ID: 501\n\nDate/Time: 2021-12-21 10:11:52.0228 +0100\nOS Version: macOS 12.1 (21C52)\nReport Version: 12\nBridge OS Version: 6.1 (19P647)\nAnonymous UUID: BAF76297-0E65-F3CC-0672-23E0B08EE74B\n\n\nTime Awake Since Boot: 28000 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 1\n\nException Type: EXC_CRASH (SIGSEGV)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11\nTerminating Process: Blender [2869]\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x10bf80451 loop_split_worker_do(LoopSplitTaskDataCommon*, LoopSplitTaskData*, BLI_Stack*) + 209\n1 Blender \t 0x10bf7f289 loop_split_generator(TaskPool*, LoopSplitTaskDataCommon*) + 361\n2 Blender \t 0x10bf7efa6 BKE_mesh_normals_loop_split + 502\n3 Blender \t 0x10bf685aa BKE_mesh_calc_normals_split_ex + 426\n4 Blender \t 0x10bde8e75 mesh_calc_modifier_final_normals(Mesh const*, CustomData_MeshMasks const*, bool, Mesh*) + 165\n5 Blender \t 0x10bde8f42 tbb::interface7::internal::delegated_function<mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)::$_0 const, void>::operator()() const + 66\n6 Blender \t 0x10c355b7b tbb::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long) + 75\n7 Blender \t 0x10bde7482 mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**) + 1602\n8 Blender \t 0x10bde6b45 mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool) + 133\n9 Blender \t 0x10bde5cc5 makeDerivedMesh + 133\n10 Blender \t 0x10bfe1bb8 BKE_object_handle_data_update + 1016\n11 Blender \t 0x10bfe1ff4 BKE_object_eval_uber_data + 52\n12 Blender \t 0x10c491b76 blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*) + 134\n13 Blender \t 0x115d6f092 tbb::internal::function_task<Task>::execute() + 18\n14 Blender \t 0x10c362679 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 393\n15 Blender \t 0x10c361cc1 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 225\n16 Blender \t 0x10dff0f58 tbb::internal::task_group_base::wait() + 24\n17 Blender \t 0x115d6ed02 BLI_task_pool_work_and_wait + 482\n18 Blender \t 0x10c491941 blender::deg::deg_evaluate_on_refresh(blender::deg::Depsgraph*) + 673\n19 Blender \t 0x10c02d868 scene_graph_update_tagged + 424\n20 Blender \t 0x10c36bab3 wm_event_do_depsgraph + 179\n21 Blender \t 0x10c376068 wm_file_read_post + 312\n22 Blender \t 0x10c3752fd WM_file_read + 749\n23 Blender \t 0x10c37adb6 wm_open_mainfile__open + 342\n24 Blender \t 0x10c372de9 wm_operator_invoke + 521\n25 Blender \t 0x10c36cde9 wm_operator_call_internal + 329\n26 Blender \t 0x10c36d5d4 WM_operator_name_call_ptr_with_depends_on_cursor + 164\n27 Blender \t 0x10ce91b76 ui_apply_but_funcs_after + 310\n28 Blender \t 0x10ce8e023 ui_handler_region_menu + 387\n29 Blender \t 0x10c373706 wm_handlers_do_intern + 950\n30 Blender \t 0x10c36f0b4 wm_handlers_do + 52\n31 Blender \t 0x10c36e4e3 wm_event_do_handlers + 1539\n32 Blender \t 0x10c3665d0 WM_main + 32\n33 Blender \t 0x10bdd54eb main + 907\n34 dyld \t 0x1254f84fe start + 462\n\nThread 1 Crashed:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 13:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 caulk \t 0x7ff810c831c0 caulk::mach::semaphore::wait_or_error() + 16\n2 caulk \t 0x7ff810c6a08a caulk::concurrent::details::worker_thread::run() + 36\n3 caulk \t 0x7ff810c69d4e void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 41\n4 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n5 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 14:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 15:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t 0x7ff8081c2aba mach_msg_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff8081c2e2b mach_msg + 59\n2 CoreAudio \t 0x7ff809e4695b HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 CoreAudio \t 0x7ff809cd50ff HALC_ProxyIOContext::IOWorkLoop() + 3937\n4 CoreAudio \t 0x7ff809cd3bc1 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63\n5 CoreAudio \t 0x7ff809e9c76c HALB_IOThread::Entry(void*) + 72\n6 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n7 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 16:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 17:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 18:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 28:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 29:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 30:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 31:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 32:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t 0x7ff8081c2aba mach_msg_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff8081c2e2b mach_msg + 59\n2 CoreFoundation \t 0x7ff8082c6af2 __CFRunLoopServiceMachPort + 319\n3 CoreFoundation \t 0x7ff8082c51cb __CFRunLoopRun + 1325\n4 CoreFoundation \t 0x7ff8082c45dd CFRunLoopRunSpecific + 563\n5 AppKit \t 0x7ff80ae61d98 _NSEventThread + 132\n6 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n7 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\n\nThread 1 crashed with X86 Thread State (64-bit):\n rax: 0x000000000000000e rbx: 0x0000600003c40090 rcx: 0x000070000d0a5f08 rdx: 0x0000000000000028\n rdi: 0x0000000000002403 rsi: 0x0000000000000003 rbp: 0x000070000d0a5f20 rsp: 0x000070000d0a5f08\n r8: 0x0000000000002503 r9: 0x0000000000000000 r10: 0x0000000000002403 r11: 0x0000000000000246\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000600003c40090 r15: 0xffffffffffffffff\n rip: 0x00007ff8081c2af6 rfl: 0x0000000000000246 cr2: 0x000070000d0a5ff8\n \nLogical CPU: 0\nError Code: 0x01000024 \nTrap Number: 133\n\n\nBinary Images:\n 0x10bc58000 - 0x118253fff org.blenderfoundation.blender (3.0.0) <8acf8f8a-1a0b-37b4-a45b-75aaca58c182> /Applications/Blender.app/Contents/MacOS/Blender\n 0x1254f3000 - 0x12555efff dyld (*) <cef5a27a-d50b-3020-af03-1734b19bc8c5> /usr/lib/dyld\n 0x7ff8081c2000 - 0x7ff8081f8fff libsystem_kernel.dylib (*) <5aa1e5be-b5b8-3a02-9885-a8c99e0ca378> /usr/lib/system/libsystem_kernel.dylib\n 0x7ff808046000 - 0x7ff80808cfff libdispatch.dylib (*) <c8f7bfb6-4b1a-37cd-a32d-cd5069c916df> /usr/lib/system/libdispatch.dylib\n 0x7ff8081f9000 - 0x7ff808204fff libsystem_pthread.dylib (*) <6c7561b4-4b92-3f45-921e-abe669299844> /usr/lib/system/libsystem_pthread.dylib\n 0x7ff810c68000 - 0x7ff810c8afff com.apple.audio.caulk (1.0) <e76d1ab3-89c2-3a93-990b-30827fcf89b0> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7ff809b1e000 - 0x7ff80a245fff com.apple.audio.CoreAudio (5.0) <33f55d9c-eaef-3fbd-add5-ed3e54925762> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7ff808246000 - 0x7ff808748fff com.apple.CoreFoundation (6.9) <eab0e216-2a9e-31ce-9164-fdf3ebcf7bd3> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7ff80acb5000 - 0x7ff80bb43fff com.apple.AppKit (6.9) <d23b9681-3764-3298-a716-fbb511dd5a7c> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\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=2.3G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.3G(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 384K 3 \nActivity Tracing 256K 1 \nCG backing stores 2688K 4 \nCG image 76K 4 \nColorSync 224K 25 \nCoreAnimation 116K 9 \nCoreGraphics 12K 2 \nCoreUI image data 972K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 436.3M 85 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.4G 12 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 132K 33 \nStack 55.8M 33 \nVM_ALLOCATE 34.1M 147 \nVM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)\n__DATA 98.7M 349 \n__DATA_CONST 17.0M 205 \n__DATA_DIRTY 774K 118 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 698.8M 17 \n__OBJC_RO 81.8M 1 \n__OBJC_RW 3136K 2 \n__TEXT 479.1M 361 \n__UNICODE 588K 1 \ndyld private memory 1088K 3 \nmapped file 163.7M 24 \nshared memory 808K 22 \n=========== ======= ======= \nTOTAL 3.8G 1487 \nTOTAL, minus reserved VM space 2.0G 1487 \n```\n\n```\nlines=12, name=Full Report\n{\"app_name\":\"Blender\",\"timestamp\":\"2021-12-21 10:11:52.00 +0100\",\"app_version\":\"3.0.0\",\"slice_uuid\":\"8acf8f8a-1a0b-37b4-a45b-75aaca58c182\",\"build_version\":\"3.0.0 2021-12-03\",\"platform\":1,\"bundleID\":\"org.blenderfoundation.blender\",\"share_with_app_devs\":0,\"is_first_party\":0,\"bug_type\":\"309\",\"os_version\":\"macOS 12.1 (21C52)\",\"incident_id\":\"9B83A860-E322-4D03-B0CE-187C62682666\",\"name\":\"Blender\"}\n{\n \"uptime\" : 28000,\n \"procLaunch\" : \"2021-12-21 10:11:31.6855 +0100\",\n \"procRole\" : \"Foreground\",\n \"version\" : 2,\n \"userID\" : 501,\n \"deployVersion\" : 210,\n \"modelCode\" : \"MacBookPro16,1\",\n \"procStartAbsTime\" : 28935533255199,\n \"coalitionID\" : 1696,\n \"osVersion\" : {\n \"train\" : \"macOS 12.1\",\n \"build\" : \"21C52\",\n \"releaseType\" : \"User\"\n },\n \"captureTime\" : \"2021-12-21 10:11:52.0228 +0100\",\n \"incident\" : \"9B83A860-E322-4D03-B0CE-187C62682666\",\n \"bug_type\" : \"309\",\n \"pid\" : 2869,\n \"procExitAbsTime\" : 28955868010950,\n \"cpuType\" : \"X86-64\",\n \"procName\" : \"Blender\",\n \"procPath\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"bundleInfo\" : {\"CFBundleShortVersionString\":\"3.0.0\",\"CFBundleVersion\":\"3.0.0 2021-12-03\",\"CFBundleIdentifier\":\"org.blenderfoundation.blender\"},\n \"storeInfo\" : {\"deviceIdentifierForVendor\":\"39CB2ACC-1148-5821-AB90-8D6F120CC508\",\"thirdParty\":true},\n \"parentProc\" : \"zsh\",\n \"parentPid\" : 1661,\n \"coalitionName\" : \"com.apple.Terminal\",\n \"crashReporterKey\" : \"BAF76297-0E65-F3CC-0672-23E0B08EE74B\",\n \"responsiblePid\" : 1596,\n \"responsibleProc\" : \"Terminal\",\n \"bridgeVersion\" : {\"build\":\"19P647\",\"train\":\"6.1\"},\n \"sip\" : \"enabled\",\n \"isCorpse\" : 1,\n \"exception\" : {\"codes\":\"0x0000000000000000, 0x0000000000000000\",\"rawCodes\":[0,0],\"type\":\"EXC_CRASH\",\"signal\":\"SIGSEGV\"},\n \"termination\" : {\"flags\":0,\"code\":11,\"namespace\":\"SIGNAL\",\"indicator\":\"Segmentation fault: 11\",\"byProc\":\"Blender\",\"byPid\":2869},\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\" : 1,\n \"threads\" : [{\"id\":1319763,\"queue\":\"com.apple.main-thread\",\"frames\":[{\"imageOffset\":3310673,\"symbol\":\"loop_split_worker_do(LoopSplitTaskDataCommon*, LoopSplitTaskData*, BLI_Stack*)\",\"symbolLocation\":209,\"imageIndex\":0},{\"imageOffset\":3306121,\"symbol\":\"loop_split_generator(TaskPool*, LoopSplitTaskDataCommon*)\",\"symbolLocation\":361,\"imageIndex\":0},{\"imageOffset\":3305382,\"symbol\":\"BKE_mesh_normals_loop_split\",\"symbolLocation\":502,\"imageIndex\":0},{\"imageOffset\":3212714,\"symbol\":\"BKE_mesh_calc_normals_split_ex\",\"symbolLocation\":426,\"imageIndex\":0},{\"imageOffset\":1642101,\"symbol\":\"mesh_calc_modifier_final_normals(Mesh const*, CustomData_MeshMasks const*, bool, Mesh*)\",\"symbolLocation\":165,\"imageIndex\":0},{\"imageOffset\":1642306,\"symbol\":\"tbb::interface7::internal::delegated_function<mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)::$_0 const, void>::operator()() const\",\"symbolLocation\":66,\"imageIndex\":0},{\"imageOffset\":7330683,\"symbol\":\"tbb::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long)\",\"symbolLocation\":75,\"imageIndex\":0},{\"imageOffset\":1635458,\"symbol\":\"mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)\",\"symbolLocation\":1602,\"imageIndex\":0},{\"imageOffset\":1633093,\"symbol\":\"mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool)\",\"symbolLocation\":133,\"imageIndex\":0},{\"imageOffset\":1629381,\"symbol\":\"makeDerivedMesh\",\"symbolLocation\":133,\"imageIndex\":0},{\"imageOffset\":3709880,\"symbol\":\"BKE_object_handle_data_update\",\"symbolLocation\":1016,\"imageIndex\":0},{\"imageOffset\":3710964,\"symbol\":\"BKE_object_eval_uber_data\",\"symbolLocation\":52,\"imageIndex\":0},{\"imageOffset\":8625014,\"symbol\":\"blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*)\",\"symbolLocation\":134,\"imageIndex\":0},{\"imageOffset\":168915090,\"symbol\":\"tbb::internal::function_task<Task>::execute()\",\"symbolLocation\":18,\"imageIndex\":0},{\"imageOffset\":7382649,\"symbol\":\"tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long)\",\"symbolLocation\":393,\"imageIndex\":0},{\"imageOffset\":7380161,\"symbol\":\"tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*)\",\"symbolLocation\":225,\"imageIndex\":0},{\"imageOffset\":37326680,\"symbol\":\"tbb::internal::task_group_base::wait()\",\"symbolLocation\":24,\"imageIndex\":0},{\"imageOffset\":168914178,\"symbol\":\"BLI_task_pool_work_and_wait\",\"symbolLocation\":482,\"imageIndex\":0},{\"imageOffset\":8624449,\"symbol\":\"blender::deg::deg_evaluate_on_refresh(blender::deg::Depsgraph*)\",\"symbolLocation\":673,\"imageIndex\":0},{\"imageOffset\":4020328,\"symbol\":\"scene_graph_update_tagged\",\"symbolLocation\":424,\"imageIndex\":0},{\"imageOffset\":7420595,\"symbol\":\"wm_event_do_depsgraph\",\"symbolLocation\":179,\"imageIndex\":0},{\"imageOffset\":7463016,\"symbol\":\"wm_file_read_post\",\"symbolLocation\":312,\"imageIndex\":0},{\"imageOffset\":7459581,\"symbol\":\"WM_file_read\",\"symbolLocation\":749,\"imageIndex\":0},{\"imageOffset\":7482806,\"symbol\":\"wm_open_mainfile__open\",\"symbolLocation\":342,\"imageIndex\":0},{\"imageOffset\":7450089,\"symbol\":\"wm_operator_invoke\",\"symbolLocation\":521,\"imageIndex\":0},{\"imageOffset\":7425513,\"symbol\":\"wm_operator_call_internal\",\"symbolLocation\":329,\"imageIndex\":0},{\"imageOffset\":7427540,\"symbol\":\"WM_operator_name_call_ptr_with_depends_on_cursor\",\"symbolLocation\":164,\"imageIndex\":0},{\"imageOffset\":19110774,\"symbol\":\"ui_apply_but_funcs_after\",\"symbolLocation\":310,\"imageIndex\":0},{\"imageOffset\":19095587,\"symbol\":\"ui_handler_region_menu\",\"symbolLocation\":387,\"imageIndex\":0},{\"imageOffset\":7452422,\"symbol\":\"wm_handlers_do_intern\",\"symbolLocation\":950,\"imageIndex\":0},{\"imageOffset\":7434420,\"symbol\":\"wm_handlers_do\",\"symbolLocation\":52,\"imageIndex\":0},{\"imageOffset\":7431395,\"symbol\":\"wm_event_do_handlers\",\"symbolLocation\":1539,\"imageIndex\":0},{\"imageOffset\":7398864,\"symbol\":\"WM_main\",\"symbolLocation\":32,\"imageIndex\":0},{\"imageOffset\":1561835,\"symbol\":\"main\",\"symbolLocation\":907,\"imageIndex\":0},{\"imageOffset\":21758,\"symbol\":\"start\",\"symbolLocation\":462,\"imageIndex\":1}]},{\"triggered\":true,\"id\":1319769,\"threadState\":{\"r13\":{\"value\":0},\"rax\":{\"value\":14},\"rflags\":{\"value\":582},\"cpu\":{\"value\":0},\"r14\":{\"value\":105553179443344},\"rsi\":{\"value\":3},\"r8\":{\"value\":9475},\"cr2\":{\"value\":123145521094648},\"rdx\":{\"value\":40},\"r10\":{\"value\":9219},\"r9\":{\"value\":0},\"r15\":{\"value\":18446744073709551615},\"rbx\":{\"value\":105553179443344},\"trap\":{\"value\":133},\"err\":{\"value\":16777252},\"r11\":{\"value\":582},\"rip\":{\"value\":140703264680694,\"matchesCrashFrame\":1},\"rbp\":{\"value\":123145521094432},\"rsp\":{\"value\":123145521094408},\"r12\":{\"value\":0},\"rcx\":{\"value\":123145521094408},\"flavor\":\"x86_THREAD_STATE\",\"rdi\":{\"value\":9219}},\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319770,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319771,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319772,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319773,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319774,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319775,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319776,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319777,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319778,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319779,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319780,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"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_2_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319784,\"name\":\"AMCP Logging Spool\",\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":111040,\"symbol\":\"caulk::mach::semaphore::wait_or_error()\",\"symbolLocation\":16,\"imageIndex\":5},{\"imageOffset\":8330,\"symbol\":\"caulk::concurrent::details::worker_thread::run()\",\"symbolLocation\":36,\"imageIndex\":5},{\"imageOffset\":7502,\"symbol\":\"void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)\",\"symbolLocation\":41,\"imageIndex\":5},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319824,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1319830,\"name\":\"com.apple.audio.IOThread.client\",\"frames\":[{\"imageOffset\":2746,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":3627,\"symbol\":\"mach_msg\",\"symbolLocation\":59,\"imageIndex\":2},{\"imageOffset\":3311963,\"symbol\":\"HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int)\",\"symbolLocation\":111,\"imageIndex\":6},{\"imageOffset\":1798399,\"symbol\":\"HALC_ProxyIOContext::IOWorkLoop()\",\"symbolLocation\":3937,\"imageIndex\":6},{\"imageOffset\":1792961,\"symbol\":\"invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)\",\"symbolLocation\":63,\"imageIndex\":6},{\"imageOffset\":3663724,\"symbol\":\"HALB_IOThread::Entry(void*)\",\"symbolLocation\":72,\"imageIndex\":6},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319965,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1319975,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319976,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319977,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319978,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319979,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319980,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319981,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319982,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319983,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319984,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319985,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319991,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1319993,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1320011,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1320012,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1320013,\"name\":\"com.apple.NSEventThread\",\"frames\":[{\"imageOffset\":2746,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":3627,\"symbol\":\"mach_msg\",\"symbolLocation\":59,\"imageIndex\":2},{\"imageOffset\":527090,\"symbol\":\"__CFRunLoopServiceMachPort\",\"symbolLocation\":319,\"imageIndex\":7},{\"imageOffset\":520651,\"symbol\":\"__CFRunLoopRun\",\"symbolLocation\":1325,\"imageIndex\":7},{\"imageOffset\":517597,\"symbol\":\"CFRunLoopRunSpecific\",\"symbolLocation\":563,\"imageIndex\":7},{\"imageOffset\":1756568,\"symbol\":\"_NSEventThread\",\"symbolLocation\":132,\"imageIndex\":8},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]}],\n \"usedImages\" : [\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4492460032,\n \"CFBundleShortVersionString\" : \"3.0.0\",\n \"CFBundleIdentifier\" : \"org.blenderfoundation.blender\",\n \"size\" : 207601664,\n \"uuid\" : \"8acf8f8a-1a0b-37b4-a45b-75aaca58c182\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"name\" : \"Blender\",\n \"CFBundleVersion\" : \"3.0.0 2021-12-03\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4920913920,\n \"size\" : 442368,\n \"uuid\" : \"cef5a27a-d50b-3020-af03-1734b19bc8c5\",\n \"path\" : \"\\/usr\\/lib\\/dyld\",\n \"name\" : \"dyld\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703264677888,\n \"size\" : 225280,\n \"uuid\" : \"5aa1e5be-b5b8-3a02-9885-a8c99e0ca378\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_kernel.dylib\",\n \"name\" : \"libsystem_kernel.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703263121408,\n \"size\" : 290816,\n \"uuid\" : \"c8f7bfb6-4b1a-37cd-a32d-cd5069c916df\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libdispatch.dylib\",\n \"name\" : \"libdispatch.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703264903168,\n \"size\" : 49152,\n \"uuid\" : \"6c7561b4-4b92-3f45-921e-abe669299844\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_pthread.dylib\",\n \"name\" : \"libsystem_pthread.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703410061312,\n \"CFBundleShortVersionString\" : \"1.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.caulk\",\n \"size\" : 143360,\n \"uuid\" : \"e76d1ab3-89c2-3a93-990b-30827fcf89b0\",\n \"path\" : \"\\/System\\/Library\\/PrivateFrameworks\\/caulk.framework\\/Versions\\/A\\/caulk\",\n \"name\" : \"caulk\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703291269120,\n \"CFBundleShortVersionString\" : \"5.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.CoreAudio\",\n \"size\" : 7503872,\n \"uuid\" : \"33f55d9c-eaef-3fbd-add5-ed3e54925762\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreAudio.framework\\/Versions\\/A\\/CoreAudio\",\n \"name\" : \"CoreAudio\",\n \"CFBundleVersion\" : \"5.0\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64h\",\n \"base\" : 140703265218560,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.CoreFoundation\",\n \"size\" : 5255168,\n \"uuid\" : \"eab0e216-2a9e-31ce-9164-fdf3ebcf7bd3\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreFoundation.framework\\/Versions\\/A\\/CoreFoundation\",\n \"name\" : \"CoreFoundation\",\n \"CFBundleVersion\" : \"1856.105\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703309713408,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.AppKit\",\n \"size\" : 15265792,\n \"uuid\" : \"d23b9681-3764-3298-a716-fbb511dd5a7c\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/AppKit.framework\\/Versions\\/C\\/AppKit\",\n \"name\" : \"AppKit\",\n \"CFBundleVersion\" : \"2113.20.111\"\n }\n],\n \"sharedCache\" : {\n \"base\" : 140703261675520,\n \"size\" : 15216738304,\n \"uuid\" : \"40432a03-88d3-305f-9c0c-e7549e71d927\"\n},\n \"vmSummary\" : \"ReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\\nWritable regions: Total=2.3G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.3G(100%)\\n\\n VIRTUAL REGION \\nREGION TYPE SIZE COUNT (non-coalesced) \\n=========== ======= ======= \\nAccelerate framework 384K 3 \\nActivity Tracing 256K 1 \\nCG backing stores 2688K 4 \\nCG image 76K 4 \\nColorSync 224K 25 \\nCoreAnimation 116K 9 \\nCoreGraphics 12K 2 \\nCoreUI image data 972K 7 \\nFoundation 16K 1 \\nKernel Alloc Once 8K 1 \\nMALLOC 436.3M 85 \\nMALLOC guard page 48K 10 \\nMALLOC_MEDIUM (reserved) 1.4G 12 reserved VM address space (unallocated)\\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\\nOpenGL GLSL 256K 3 \\nSTACK GUARD 132K 33 \\nStack 55.8M 33 \\nVM_ALLOCATE 34.1M 147 \\nVM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)\\n__DATA 98.7M 349 \\n__DATA_CONST 17.0M 205 \\n__DATA_DIRTY 774K 118 \\n__FONT_DATA 4K 1 \\n__GLSLBUILTINS 5176K 1 \\n__LINKEDIT 698.8M 17 \\n__OBJC_RO 81.8M 1 \\n__OBJC_RW 3136K 2 \\n__TEXT 479.1M 361 \\n__UNICODE 588K 1 \\ndyld private memory 1088K 3 \\nmapped file 163.7M 24 \\nshared memory 808K 22 \\n=========== ======= ======= \\nTOTAL 3.8G 1487 \\nTOTAL, minus reserved VM space 2.0G 1487 \\n\",\n \"legacyInfo\" : {\n \"threadTriggered\" : {\n\n }\n},\n \"trialInfo\" : {\n \"rollouts\" : [\n {\n \"rolloutId\" : \"601d9415f79519000ccd4b69\",\n \"factorPackIds\" : {\n \"SIRI_TEXT_TO_SPEECH\" : \"6194416f2171a2330e561f05\"\n },\n \"deploymentId\" : 240000355\n },\n {\n \"rolloutId\" : \"5fc94383418129005b4e9ae0\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000192\n },\n {\n \"rolloutId\" : \"607844aa04477260f58a8077\",\n \"factorPackIds\" : {\n \"SIRI_MORPHUN_ASSETS\" : \"6103050cbfe6dc472e1c982a\"\n },\n \"deploymentId\" : 240000066\n },\n {\n \"rolloutId\" : \"5ffde50ce2aacd000d47a95f\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000090\n },\n {\n \"rolloutId\" : \"602ad4dac86151000cf27e46\",\n \"factorPackIds\" : {\n \"SIRI_DICTATION_ASSETS\" : \"6193d03f2171a2330e561dfc\"\n },\n \"deploymentId\" : 240000290\n },\n {\n \"rolloutId\" : \"60da5e84ab0ca017dace9abf\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000008\n }\n ],\n \"experiments\" : [\n\n ]\n}\n}\n\nModel: MacBookPro16,1, BootROM 1715.60.5.0.0 (iBridge: 19.16.10647.0.0,0), 6 processors, 6-Core Intel Core i7, 2,6 GHz, 32 GB, SMC \nGraphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In\nGraphics: AMD Radeon Pro 5300M, AMD Radeon Pro 5300M, PCIe, 4 GB\nDisplay: Color LCD, 3072 x 1920 Retina, Main, MirrorOff, Online\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, Micron, MT40A2G8NEA-062E:J\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, Micron, MT40A2G8NEA-062E:J\nAirPort: spairport_wireless_card_type_wifi (0x14E4, 0x7BF), wl0: Jul 12 2021 18:02:56 version 9.30.464.0.32.5.76 FWID 01-c081cfed\nBluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB31Bus\nUSB Device: T2Bus\nUSB Device: composite_device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```", "Console warning \"ToolSettings\"/ \"snap_node_element\"\nOperating system: Windows 10\nGraphics card: Geforce GTX 970\n\nBroken:\n2.80, 8c8979067490, blender2.7, 2019-01-31\n\nI was importing a file from an older blender version and I noticed this error in the console:\n\nIt appears when you hover over the node editor and when toggling edit mode.\n\nThe reason I think it's not an issue which appears because of the different blender version is that I recently released an addon for managing nodes with layers and a few people noticed similar errors when editing a mesh with KitOps or similar addons and then trying to change the nodes.\nI also don't think it's an issue with my addon as I didn't change the file (included) with the addon and I tried it with a clean blender version as well.\n\n[warning_message.blend](warning_message.blend)\n- Open the file\n- Open blender console to see error messages\n- Hover over node editor with the cursor\n- > Warning message should appear", "2.8: Python API: Changing area type on frame change crashes Blender\nOperating system: Windows 10\nGraphics card: Quadro P4200/PCIe/SSE2\n\nBroken: 2.81a (also crashes in 2.79 and 2.80)\n\nI am attempting to sample the individual frames of an image on frame change, using a solution similar to the one described here: 5. I cannot seem to set the viewer area, however, from this context, as `bpy.context.screen` is `None`, and `bpy.context.window_manager.windows- [x].screen` seems to crash Blender in some situations.\n\nFrom the default startup file, run the following basic code:\n\n```\nimport bpy\n\ndef on_frame_change(scn):\n bpy.context.window_manager.windows[0].screen.areas[0].type = \"IMAGE_EDITOR\"\n\nbpy.app.handlers.frame_change_pre.append(on_frame_change)\n```\n\nRun the `Render Animation` operator to crash Blender.\n\nNote: This code runs fine when playing the animation in the 3D Viewport. It seems that this bug relates to the render context only." ]

[ "Blender 2.78 crashes after loading data from a blendfile\nWindows 7 64bit, NVIDIA Quadro K3100M\n\nBroken: 2.78a\nWorked: 2.77a\n\n\nBlender 2.78 crashes after loading data from a blendfile\n\n\nI'm importing data from another blendfile as follows:\n\n```\n def import_from_file(filepath):\n with bpy.data.libraries.load(filepath) as (data_from, data_to):\n collections = 'objects', 'groups', 'materials'\n for collection_name in collections:\n collection_from = getattr(data_from, collection_name)\n collection_to = getattr(data_to, collection_name)\n for obj in collection_from:\n collection_to.append(obj) \n \n for obj in data_to.objects:\n bpy.context.scene.objects.link(obj)\n```\n\n\nThe import works fine but afterwards some API operations crash Blender with `Error: EXCEPTION_ACCESS_VIOLATION`. For example `bpy.ops.object.select_all(action='DESELECT')`.\n\nThis is working correctly in 2.77a.\n\n\n" ]

[ "Regression: NODE_OT_add_search ignores NodeItems entries\nBroken: 3.4\nWorked: 3.3\nCaused by bdb5754147\n\nNodeItems entries are not taken into account when using the node `Shift+A` search functionality.\n\n- Load and register the `Python > Custom Nodes` script template.\n- Use the `Shift + A` search functionality.\n- In 3.4 `Node A` and `Node B` are missing.\n\n| 3.3 | 3.4 |\n| -- | -- |\n|  |  |\n\n**Reproduction File**\n[NodeItemsSearchRegression.blend](NodeItemsSearchRegression.blend)\n\n**More Context**\nIn Malt (https:*github.com/bnpr/Malt), we generate most nodes from a few node classes (https:*github.com/bnpr/Malt/tree/Development/BlenderMalt/MaltNodes/Nodes) and auto-generated GLSL reflection data. \nWe also use NodeItems to allow searching directly for node drop-down subcategories. (ie. you can search directly for `Dot Product`, instead of searching for `Vector` and then selecting the `Dot Product` option) \nBut none of this works in 3.4", "GP Fill tool crashes with maximum Precision (macOS, Metal)\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: OpenGL\n\nThe Fill tool leads to crashes when Precision is set to maximum. (macOS, Metal)\n\n- new 2D Animation\n- draw a Circle\n- select Fill tool\n- set Precision to max (8)\n- try to fill\n\n<details>\n <summary>Thread 0 Crashed:: Dispatch queue: com.apple.main-thread ...</summary>\n\n0 libsystem_kernel.dylib \t 0x7ff80c84200e __pthread_kill + 10\n1 libsystem_pthread.dylib \t 0x7ff80c8781ff pthread_kill + 263\n2 libsystem_c.dylib \t 0x7ff80c7c3dbe __abort + 139\n3 libsystem_c.dylib \t 0x7ff80c7c3d33 abort + 138\n4 libsystem_c.dylib \t 0x7ff80c7c30cb __assert_rtn + 314\n5 Metal \t 0x7ff8152fd8a4 MTLReportFailure.cold.1 + 43\n6 Metal \t 0x7ff8152e7c05 MTLReportFailure + 529\n7 Metal \t 0x7ff8152e0378 _MTLMessageContextEnd + 1278\n8 Metal \t 0x7ff815231bdf -[MTLTextureDescriptorInternal validateWithDevice:] + 3296\n9 AMDMTLBronzeDriver \t 0x7ffa28ecc4f5 -[BronzeMtlTexture initInternalWithDevice:descriptor:] + 59\n10 Blender \t 0x112db8230 blender::gpu::MTLTexture::ensure_baked() + 1280\n11 Blender \t 0x112db832f blender::gpu::MTLTexture::get_metal_handle_base() + 15\n12 Blender \t 0x112d8997f blender::gpu::MTLFrameBuffer::bake_render_pass_descriptor(bool) + 879\n13 Blender \t 0x112d7c8c0 blender::gpu::MTLCommandBufferManager::ensure_begin_render_command_encoder(blender::gpu::MTLFrameBuffer*, bool, bool*) + 112\n14 Blender \t 0x112d806b5 blender::gpu::MTLContext::ensure_begin_render_pass() + 325\n15 Blender \t 0x112bdddd7 GPU_clear_color + 71\n16 Blender \t 0x10dd4f9e8 gpencil_fill_modal + 4456\n17 Blender \t 0x10d26677d wm_handler_operator_call(bContext*, ListBase*, wmEventHandler*, wmEvent*, PointerRNA*, char const*) + 1389\n18 Blender \t 0x10d265551 wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 1841\n19 Blender \t 0x10d2647e0 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 48\n20 Blender \t 0x10d263b7a wm_event_do_handlers + 2554\n21 Blender \t 0x10d259950 WM_main + 32\n22 Blender \t 0x10ca4a59e main + 878\n23 dyld \t 0x12095152e start + 462\n</details>\n\n", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "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", "Proposal to show empty search results when the text field is empty\nBefore typing, instead of listing all operators, just keep the UI more compact, like so:\n\n{[F8366112](Screenshot_2020-02-24_at_10.59.27.png), size=full}\n\nWhen the user searches, the popup expands:\n\n\n(split out from #74157 (Use menus for operator search & various improvements)).\n", "Crash when playing animation in rendered view (cycles)\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0, 3.5\nWorked: unknown\n\nPlaying animations in cycles rendered view frequently crash blender. With the attached file I consistently get a crash within 1-2 minutes of starting the animation.\n\nThe crashes do not occur when running the intel version through rosetta. They occur much faster/more often when using the CPU than when using the GPU.\n\nOpen attached file\nSwitch to rendered view (Crashes with and without Metal preference)\nPress spacebar to play\n\n[Boat boating.blend](Boat_boating.blend)\n[Animation crash.txt](Animation_crash.txt)\n```\nThread 17 Crashed:\n0 Blender \t 0x10319354c tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 340\n1 Blender \t 0x103193644 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 588\n2 Blender \t 0x103192c60 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 184\n3 Blender \t 0x103183300 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252\n4 Blender \t 0x10318c3b8 tbb::internal::market::process(rml::job&) + 40\n5 Blender \t 0x10318d6b0 tbb::internal::rml::private_worker::run() + 288\n6 Blender \t 0x10318d584 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n7 libsystem_pthread.dylib \t 0x1b39cd4ec _pthread_start + 148\n8 libsystem_pthread.dylib \t 0x1b39c82d0 thread_start + 8```", "Realtime Compositor - Crash on Mac when using Map UV node\nOperating system: macOS Ventura 13.3.1\nGraphics card: AMD Radeon Pro 5700 XT 16GB\n\nBroken: 3.6 alpha cef128e68af5 (2023-04-13 16:06)\n\nConnecting a Map UV node in Compositing will crash on macOS\n\nIn Blender's startup scene, enable Compositing by checking \"Use Nodes\".\nConnect a Map UV node between the Render Layers node and the Composite node.\nIn a 3D view, turn on Rendered viewport and set Viewport Compositing to Always.\nThis will crash (100% reproducible).\n\nPlease contact summary if more information is required.\n\n", "Blender 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", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "Crash 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```", "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", "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 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", "\"Add [Object]\" menu not working correctly or lagging\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nI found out that the context menu that appears just after adding an object tends to lag or bug if you have split screen the viewport and the compositor with the checkbox \"use nodes\".\n\n1. Make a vertical split and and add the Compositor panel.\n2. Check \"use nodes\" in the compositor panel.\n3. Add any 3D Primitive object in the viewport, )E.G. Icosphere).\n4. Try changing the subdivisions in the \"add icosphere menu\" or just try to drag the logation paramenters whithin that menu.\n5. The result will be a choppy or lagging response, not expected.\n6. I've tracked this error even from the 3.4 version of blender, until now.\n", "Geometry Nodes + Shader Editor + Asset Browser bug\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5 `7bf75231e8c5` , 3.4.1 `55485cb379`\nWorked: (latest 3.3.2 for Mac Intel)\n\nGeometry Nodes Editor + Shader Editor loads in all marked, related assets from Asset Browser causing crash and memory overload\n\n- Extract Asset.zip\n- Open default blender scene and assign asser library path as shown in the image\n- Open node editor\n- SHIFT+A action cause immediate memory overload from Asset Browser\n\n\n\n[Assets.zip](Assets.zip)\n\n[asset-library-indices.zip](asset-library-indices.zip)" ]

[ "Crash using GN Editor or Assetbrowser when \"datafiles/assets\" folder is not there\nOperating system: Linux-6.1.6-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.78.01\n\nBroken: version: 3.6.0 Alpha\n\nSince b3fb73f32545, we should have a `datafiles/assets` folder.\nWhen it is not there (renamed/deleted, or contains wrong stuff), blender crashes when trying to add nodes in the Geometry Nodes Editor and also just switching to the Asset Browser\n\n- (temporarily) rename `datafiles/assets` to `datafiles/assets_`\n- switch any editor to the Asset Browser\n- crash\n\ncrash is in `essentials_directory_path`, giving `what(): basic_string: construction from null is not valid`\n\n" ]

[ "Grease pencil object in some cases look like low poly.\nOperating system: Linux-4.4.0-176-lowlatency-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 11)\nWorked: 2.82 (sub 7)\n\nIn some cases GP objects looks blocky, like a low poly objects.\n\nOpen attached file and render it.\nCompare render result with previous worked blender version.\n\n\n[2.83_bug.blend](2.83_bug.blend)\n", "Camera background image is hidden by GPencil fill with alpha\nOperating system: Linux-4.14.78-gentoo-x86_64-AMD_FX-tm-8350_Eight-Core_Processor-with-gentoo-2.6 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 410.73\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nWhen I change the fill alpha while a background image is loaded, it behaves weirdly. i.e, when the alpha value is 0, the background image is visible, when alpha crosses 0.001, the image mysteriously disappears.\n\nIn Grease Pencil, I added a background image in the camera object data context menu,\nthen I drew a box and changed the alpha of fill, then the above said bug appears.\n\nI have included the blend file and a video to produce the bug.\n\n[blenderGreasePencilBugVid.mp4](blenderGreasePencilBugVid.mp4)\n\n[greasePencilBug.blend](greasePencilBug.blend)\n\n", "Camera background movieclips are not visible if \"Viewport Shading\" is set to \"Rendered\" \nOperating system: Linux-5.4.0-65-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.92.0 Beta\nWorked: 2.90.1\nCaused by 3ffa0452af\n\nWhile static background images of cameras are correctly visualized when \"Viewport Shading\" is set to \"Rendered\", background image sequences defined with the clip editor are only visible when \"Viewport Shading\" is set to \"Material Preview\", \"Solid\" or \"Wireframe\" \n\nIn the following python script adjust the path such that it points to some valid input image.\n\n[background_image_test.py](background_image_test.py)\n\nExcecuting the script creates two cameras. \n\nThe first camera contains a static background image (see the code snippet below)\n```\nstatic_background_image = static_camera_data.background_images.new()\nstatic_background_image.image = bpy.data.images.load(image_fp)\n```\nand is visible for all \"Viewport Shading\" types.\n\n\nThe second camera contains a background image defined by a video clip (see the code snippet below),\n```\ndynamic_background_image = dynamic_camera_data.background_images.new()\ndynamic_background_image.source = \"MOVIE_CLIP\"\ndynamic_background_image.clip = bpy.data.movieclips[first_fn]\n```\nwhich is not visible when \"Viewport Shading\" is set to rendered.", "Grease Pencil Outline Modifier not showing with duplicated camera in outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.33\n\nBroken: version: 3.4.0 Alpha\n\nThe outline modifier of a grease pencil is not showing with a camera that gots duplicated in the outliner\n\n\n- Remove the default cube\n- In the outliner copy and paste the default camera\n- Remove the first camera\n- Add a grease pencil stroke\n- Add a Outline modifier to it\n\nThe outline will not show.\n\nThis bug is related to this report. I am just not sure if it is two different causes and cases, or the same. T102373\n\n\n\n[2022-11-09 10-30-57.mp4](2022-11-09_10-30-57.mp4)\n\n\n\n", "Can't pan more on the viewport when set to camera view with a wide resolution.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.81 (sub 16)\n\nI can't pan to the side more than this with the camera on the viewport. I wanted to have the cube in the center of the viewport but blender just doesn't pan anymore.\n\nHOWEVER! if I change the ratio of the 3D editor, it works (up to a limit), it is a workaround, but a weird one!\nLike this:\n\n\nOpen the file and try to pan to have the cube on the center of the viewport without exiting camera view:\n[Camera_pan.blend](Camera_pan.blend)\nThis happens with this kind of resolution settings and the camera > sensor fit > set to Vertical (that I need in my project).\n", "Proportional Editing in Mask mode only works with \"G\", not with slide_marker\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.93.0 Alpha\nWorked: never\n\nCould be that this is more a design issue, but it feels very inconsitent to me and I cannot find a good reason for it.\nWhen proportional editing is enabled in Mask mode, it only works when you use \"g\" or the move tool to actually grab the mask control point and move it, but when you use the left mouse button (= \"slide_marker\") it only moves the current CV, without proportional editing. I am not sure there should be a difference between \"grab and move\" and \"slide_marker\" when it comes to proportional editing.\nWith keymap set to right click select this is maybe less of an issue because you can right click and drag to tweak the curve (and thereby using proportional editing), but with the default of left click select there is only slide_marker available as a tweaking option, and that does not use proportional editing. \nI suggest to have proportional editing during slide_marker as well. \n@SeanKennedy what do you think about this?\n\nOpen this file:\n[mask_drawing.blend](mask_drawing.blend)\nUse use left mouse button to slide any of the mask points. No falloff is in use.\nNow try the same with \"g\". Proportional editing is in use.", "Grease Pencil: Better render Anti-Aliasing\n## Motivations:\nThin lines are correctly rendered using grease pencil with the currently implemented post process Anti-Aliasing. This is done by making sure the line width is not less than 1.3 and by modulating its opacity.\nHowever, there is cases where this is not enough. For instance really dense drawings with small lines with little to no curvature still tends to flicker a lot.\nAnother case is when the gpencil strokes intersects the scene geometry. This makes the line less thick to the post process which makes it too small.\n\n## Proposed solution:\nWe propose to implement a Temporal AntiAliasing solution. It is robust and will match Cycles & EEVEE's film filtering if using the same filtering function. This only adds one temporary buffer (low VRAM usage compared to rendering at higher resolution) and is completely self contained (works with transparency and don't interfere with other features).\n\nI propose to only implement this for final rendering since it might introduce flickering that might be annoying while drawing.\n\nHowever this wouldn't solve the issue of gpencil strokes intersecting geometry.\nFor this I propose to erode or reproject the render's depth to match the render sample of the new AA scheme. This should fix the second problem completely.\n\n## Technical details:\n- Implementation just need to be ported from Workbench which has a lighter form of TAA than EEVEE. Also [D10414](D10414) can be of great help to reduce render/convergence time.\n- Depth buffer modification can be implemented after new AA is in.", "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.", "Grease Pencil drawing only show up when pen is lifted from tablet\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800S ATI Technologies Inc. 4.5.14802 Core Profile Context 21.40.64.30 30.0.14064.30001\n\nBroken: version: 3.6.1\n\n\nGrease Pencil is not the same as before. When I press down to draw something with the pen, it won't show up- until after I lift my pen up from the tablet and then it shows what I drew. This is bad because I can't draw if I can't see what mark I made. It only shows up after and ruins the workflow.\n\n\nI open up Blender, the updated version: 3.6.1. I click: 2d animation to start. Then I click pen as my grease pencil drawing tool. I draw something on the canvas. I press down to draw a shape. Nothing shows up as I press down on the canvas. I lift my pen off the tablet and then I see what I 'drew'. A horrible squiggle line because I cannot see what I'm drawing as I'm drawing. I did not have this problem with the past version of blender that I had: Blender 3.3.1. \n\n~Karina\n\n", "Grease Pencil ripped line when rendering in EVEE\nOperating system: Windows 10\nGraphics card: GeForce 1050 ti\n\n3.62\n\nGrease pencil object is displayed normally in the viewport, but when rendering the line becomes jagged, not like in the viewport. In Cycles all is good.\n\n\n\n", "Scene Line Art problem when used with Grease Pencil objects.\nOperating system: Windows 10\nGraphics card: Radeon RX 590\n\nBroken: (2.93.0 Beta, 0f66dbea904f, master, 2021-04-21)\nWorked: ()\n\nScene Line Art or Object Line Art are located in front of the Grease Pencil objects.\n\n\n[SceneLineArt_and_GPencil.blend](SceneLineArt_and_GPencil.blend)", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "Grease Pencil vertices selection is offset when Layers/Transform Location as set to a driver\nOperating system: Win10\nGraphics card: RTX3070\n\nBroken: 3.1.0 A\nWorked: N/A\n\n**Short Description of issue**\nMoving a Grease Pencil object's layer via Layers->Transform, by using a Driver, offsets where you have to click to select vertices from that layer.\n\nNOTE: Switching to Draw Mode and drawing a stroke fixes it temporarily, but once you move the controller of the driver again, the problem returns.\n\n**Steps to Reproduce**\n- Open .blend file\n- Select Suzanne and switch to edit mode\n- Try selecting vertices (Does not work)\n- Now attempt to select in circled area\n\n\n\n[#95902.blend](T95902.blend)\nVideo example: iZ_A2wOnAJQ", "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", "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." ]

[ "Gpencil + clipping 0.5m = heavy glitches because ignore clipping planes\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\nAlso:\nWindows 10 x64, GeForce GTX 1050\n\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nIf clipping start is not small (0.3m or more), Gpencil make such glitches\n\n\nDraw some GP sstrokes, Set clipping in viewport to 0.5—50m, orbit scene.\nHere the file\n[GP_obezymel.blend](GP_obezymel.blend)\n" ]

[ "GPencil test system to keep code quality\nGrease pencil module is a big module now in Blender and requires a test system to ensure the quality and avoid bugs introduced by any change.\n\nAs GPencil has only a few test now, this task is a long term one because it will need the addition of tests for old code, not only for new functions.", "Solidify cause wrong vertex selection in edit mode\nLinux-4.19.0-12-amd64-x86_64-with-debian-10.6 64 Bits\nMesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6\n\nWindows 10-10.0.19041 SP0 64Bit\nGeForce 9600 GT PCIe SSE2 Nvidia Corporation\nRadeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.83.2\nBroken: version: 2.90.1\nBroken: version: 2.91.0 Beta\nWorked: unknown\n\nIn 3d viewport, vertex selection, solid mode, X-Ray off, you cannot predict what you are selecting when using solidify:\nBlender is ignoring the X-Ray (\"Allow selecting through the items\") and is selecting, randomly, occluded items.\nHaving a very narrow clipping does not mitigate the issue.\n\nExplanation video [SelectLight.mp4](SelectLight.mp4)\n\n[#82182.blend](T82182.blend)\n\n- Open file\n- Click inside blue circle\nOccluded vertex will be selected\n", "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", "Eevee SSRefraction noisy at low roughness\nOperating system: Windows 10 Pro\nGraphics card: GTX 1050TI\n\nBlender 2.93 and 3.0\n\nScreen space refraction has a weird noisy ball on the center of it, with a kind of low quality pixelated look, only ways to get rid of it partially is by either increasing the IOR, increasing the Refraction Depth, or changing the roughness of the material to something that isn't between 0.01 - 0.3.\n**This applies to both the roughness and trasmission roughness**\n\nSide note : i tried changing all the settings in the render properties, nothing worked, speaking of which, Half Res Trace does NOT apply to Refraction, only Reflections.\n\nJust do a basic setup of SSRefractions, nothing more than that\n\n\n\n[SSRefractionsExample.blend](SSRefractionsExample.blend)\n\nMore extreme example:\n[#90307.blend](T90307.blend)", "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", "GPencil: Screen-space stroke size incorrect\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTS 450/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.92.0 Alpha\nWorked: none found\n\n**Description**\n\nWhen drawing a stroke with a defined pixel size and stroke-thickness-space is set to screen space, the radius of the drawn stroke should measure the set pixel size. This is not the case. The strokes radius measures half the size.\n\n**Steps to reproduce**\n\n - Create a grease pencil object\n - Set the stroke-thickness-space to screen space in objects grease pencil settings\n - Set the brush size to 100px\n - Draw a single dot.\n - Print the screen\n - Measure the dot size in any image editing app.\n # You will see that the radius of measures 50px and the diameter measures 100px. Instead of 100px and 200px respectively.\n\nThis issue can be further seen by trying to change the brush size using the `f` key. The brush size cursor is drawn at the correct size but is double the size of the stroke.\n\n**Investigations**\n\nThis relates to my original report #82707 wherein I thought the cursor size was incorrect. I have now had time to review the code enough to understand how the cursor is drawn; and how the brush size is defined and passed to the rendering engine.\n\nI have confirmed that the brush size takes the following path.\n\nBrush.size user setting: RADIUS → bGPDstroke.thickness: RADIUS → gpencil_vert.glsl thickness: RADIUS\n\n*Simplified for explanation purposes. Path steps missing.*\n\nI originally thought thickness was defined as a diameter but this is not the case.\n\nI also thought this would be a noticeable fix but I haven’t found where the issue lie yet so I thought I would report again. \n\nNote: When drawing a stroke with stroke-thickness-space set to world space the stroke is mapped to the users screen correctly. When world space is used a stroke with a brush size of 2000px is drawn with a radius of 1m in world space as defined internally. \n\n[Bug-GPencil-Screen-Space-Stroke-Size-Incorrect-Report-VID.mp4](Bug-GPencil-Screen-Space-Stroke-Size-Incorrect-Report-VID.mp4)\n", "GPencil: Materials' preview thumbnails cause heavy lag when updating\nOperating system: Windows 10\nGraphics card: RTX 3070 FE\n\nBroken: 3.2.1 RC\nWorked: n/a\n\n\n\nAny action that requires the refreshing of your Grease Pencil materials' thumbnails (isolate/hide materials, etc.) causes major lag until the thumbnails are finished refreshing. The more materials your GP object has, the longer the lag. Sometimes the lag is so bad, that it makes the sound buffer skip while the thumbnails refresh.\n\n\n**Video Explanation**\nwatch?v=5KAWsJkIeRY\n\n\n**Steps to Reproduce**\nCreate a GP object and add 10-20 unique materials\nClick one of the \"Isolate Material\" buttons, and start drawing/moving strokes. You will notice extreme lag until all of the little circle thumbnails are finished updating. \n\nTest File:\n[#99361.blend](T99361.blend)", "GPencil: 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)", "Smoke Shadow glitches in Cycles (workaround only with Fluid \"Empty Space\" option)\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D700](D700) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.21\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nWeird artifacts and boxes appear in the shadows of smoke simulations\n\n\nI've seen this happening in different simulations with different results. Sometimes it is a big square in the shadows like in the image attached. Sometimes it's just little squares.\n\nGenerally speaking the workflow I'm following when I see these errors is the following:\n\nSet the scene to cycles\nCreate ground plane\nCreate Sun Light\nCreate smoke domain\nCreate smoke emitter with particles\nSet smoke flow to emit fire and smoke from particles\nCaches simulation\nRender with Cycles\nGlitches appear in the shadows of the smoke\n\nAttached is a blend file and the render result with glitches\n\n[VolumetricsTest.blend](VolumetricsTest.blend)\n\n", "GPencil: Modifiers don't work after separate strokes and use hide in outliner [issue with multiuser gpencil objects and modifiers]\nOperating system: Ubuntu 20.04\nGraphics card: Mesa Intel® HD Graphics 620 (KBL GT2\n\nBroken: (2.83.3)\n\n\nThe mirroring of a grease pencil object briefly stops being visible after performing a stroke separation.\n\n1. Boot up Blender's default 2D animation workspace\n2. Draw a stroke on the GP object \"Stroke\"\n3. Add a mirror modifier to the object.\n3. Draw another stroke\n4. Change to edit mode and select the new stroke\n5. separate said stroke with P, creating \"Stroke.001\"\n6. Still on edit mode, click on the 'eye' icon on the outliner to make \"Stroke\" invisible\n7. Click on the eye icon again, the mirroring will have stopped being visible.\n8. Clicking twice on the \"Display modifier on viewport\" button in the modifier tab fixes the issue.\n\n**Status**\nThe \"wrong usercount when separating\" is fixed, see 4251a87bf6, however the underlying issues with multiuser gpencil and modifiers still remains.\nTo reproduce:\n- add a gpencil stroke\n- {key Alt + D} duplicate linked\n- add a Thickness modifier.\n- Hide/Unhide the object in outliner.\n", "GPencil: A layer used as mask for 2 or more other different layers makes the GP object partially unselectable in the viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.74\n\nBroken: version: 2.83.0 Beta\nWorked: /\n\nA layer (let's call it layer A) is masking more than one layer (B and C, for example; so B and C have in their \"mask(s) list\" layer A in it). Doing it makes the grease pencil object unselectable in the viewport unless you click on the shapes that have been drawn on layer A (or, at the precise point where the origin of the grease pencil is located, but only if the origin is displayed in the viewport).\n\nStrangely, saving with \"ctrl+S\" makes everything works as expected, but only until the file is closed. Opening it again and the problem is back.\n\nIn a concrete case scenario, it is a problem since if you use a layer as an invisible mask to hide strokes that go beyond certain limits, it makes it random to select the GP object (or forces to use the outliner).\n\n- Create a GP monkey\n- Create a new layer (layer A) that will mask the 2 already existing layers (\"Lines\" and \"Fills\")\n- In \"Lines\" and \"Fills\" layer, check the \"mask(s)\" option and add \"Layer A\" in each list\n- Back in \"Layer A\", draw a filled shape anywhere\nNow, in object mode you can only select the GP monkey by clicking on the filled form in layer A. You can invert the mask layer in the mask list of the layer named \"Fills\": It seems that it doesn't matter whether the masked parts are visible or not.\n\nBased on the attached .blend file:\n- Open file\n- Try to select the monkey by clicking on the part supposed to act as a mask (the \"selectable\" part in the screenshot)\n- Try to select the monkey by clicking in any other part of the monkey.\n\n{[F8563683](select_bug.png), size=full}\n\n[mask_selection_bug.blend](mask_selection_bug.blend)", "Using Sculpt Collision clips some of the hair curves in Rendered viewport shading\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 528.49\n\nBroken: version: 3.5.0 Alpha\n\nEnabling the new Sculpt Collision, combing some hair and then switching to render mode clips parts of the hair.\n\n\n- Open attached file\n- Select CUDA device\n- Disable cage opacity property\n- Enable viewport rendering and comb curve hairs\n[Add hair curves, add some hair, activate Sclupt Collisions, comb the hair, hit render viewport shading]\n[attached .blend file (as simple as possible)]\n\n", "Weird artefacts from emission surface\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M (but this occurs also on CPU)\n\nBroken: 3.6.2\nWorked: don't know\n\n\nIn the attached .blend file I have set up an emission shader to emit light from one end of a long thin surface. The screenshot illustrates the problem: a bunch of weird artefacts appear.\n\nIf I change it to emit from the other end of the surface, by swapping the 'Map Range' node in the screenshot for the disconnected one, the problem goes away.\n\n\n\n\nLoad the attached .blend file and switch the view to rendered.\n\n", "GPencil: Select Circle misses points when dragging fast over strokes in material preview or rendered viewing modes\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.90.0 Alpha\n\nThe Select Circle tool regularly misses points when dragging over them in material preview or rendered viewing mode.\n\n* Open the attached .blend file\n* Drag quickly over the line (solid mode), the points are correctly selected.\n* Switch to Material Preview and drag quickly over the line, not all points on the drag path are correctly selected.\n\n**Notes**\nFor me the cursor movement (UI update?) has a much lower frame rate while in material preview or rendered viewing mode. So while dragging quickly over the points in a stroke, some points never overlap the select circle radius on any of the frames of the drag. And it looks like the position of the Select Circle isn't being interpolated between frames.\n\nThis means that points don't get selected that should have been, so I have to make the selection again. \n\nIn solid or wireframe mode the FPS is high enough that no points are missed, but these modes are often not good enough to get a proper feel for the image i'm working on.\n\n[selectcircle.blend](selectcircle.blend)", "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" ]

[ "Grease pencil seems to ignore clipping planes\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.80 (sub 75)\nWorked: - \n\n\nGrease pencil textured strokes seems to ignore camera clipping planes. Raising up the clipping value should result in cutting out stroke vertex that are behind the camera, the stroke are instead drawn anyway resulting in an always growing and camera occluding stroke. Setting higher camera clipping start seems not to affect the stroke in any way. \n\ncamera actual position\n[GP_TEXSTROKE_CLIPPING.mp4](GP_TEXSTROKE_CLIPPING.mp4)\n\nstroke weirdness when camera passes the gp object\n[GP_TEXSTROKE_CLIPPING_RENDER.mp4](GP_TEXSTROKE_CLIPPING_RENDER.mp4)\n[GP_TEXSTROKE_CLIPPING_RENDER.mp4](GP_TEXSTROKE_CLIPPING_RENDER.mp4)\n\nOpen attached blend file and play the animation through the camera.\n[GP_TEXSTROKE_CLIPPING_BUG_TEST.blend](GP_TEXSTROKE_CLIPPING_BUG_TEST.blend)\n\nThe only workaround i found is animationg the stroke point strength going toward 0 as soon as the camera outreaches the gp object." ]

[ "Undo in Armature EditMode ignores changes to other IDs\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0 Alpha\n\nWhen you rename bones of armatures with some meshes by python scripts and then do Undo (Ctrl +z), then only bone names are reverted and the mesh vertex groups are never reverted.\nIt seems to happen immediately after from Object mode to Edit mode for armatures.\n\n* Open \"bpy_rename_bone_and_undo_bug_report.blend\".\n* Go to Armature Edit mode.\n* Run script \"rename.py\". It will rename selected bones and the mesh vertex groups.\n* Do undo (Ctrl +z)\n* Then you will see only bone names are reverted and the mesh vertex groups aren't reverted.\n\n[bpy_rename_bone_and_undo_bug_report.blend](bpy_rename_bone_and_undo_bug_report.blend)\n\nIt will lost bone deformations.\nI thinks it will cause some human errors.\n\nThanks!\n", "Crash Python API - GPUOffScreen.draw_view3d() crashes blender with draw_type = POST_VIEW but works with draw_type = POST_PIXEL\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.1\n\nWhen using [GPUOffScreen.draw_view3d() ]] in a [[ https:*docs.blender.org/api/current/bpy.types.Space.html?highlight=post_view#bpy.types.Space.draw_handler_add | draw_handler ]], blender crashes when running the [[ gpu.shader.html?highlight=gpu+shader+from_builtin#built-in-shaders | 3D_IMAGE builtin shader ](https:*docs.blender.org/api/current/gpu.types.html?highlight=draw_view3d#gpu.types.GPUOffScreen.draw_view3d) if the draw_type was set to POST_VIEW but works if the draw_type was set to POST_PIXEL.\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script Crash3D and blender will crash\n\n\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script NoCrash2D, and it will draw the camera view in the viewport without crashing\n\nAttachments:\n\n[CrashScriptDrawView3D.blend](CrashScriptDrawView3D.blend)\n[blender.crash.txt](blender.crash.txt)\n\n\n\n\n\n\n", "Crash When Adding Hair Subdivision upon Viewer node\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\n\n\nAdding hair subdivision will cause crash immediately when you are using viewer node to visualize field values in the viewport.\nNote no crash will occur if the viewer node is inactive.\n\n[Hair Crash.crash.txt](Hair_Crash.crash.txt)\n\n1. select default cube\n2. shift+A to add empty hair\n3. in the node tree add viewer node.\n4. Crash if adding subdivision\n[Hair Crash.blend](Hair_Crash.blend)", "MultiRes+Solidify while trying to use Sculpt Mode cause Blender to crash\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nI tried deactivating one modifier while keeping the other one active to see if Blender would crash, but this was not the case. Only when I used both simultaneously did the program reliably crash every time, regardless of brush.\n\nAdd the modifiers that are active in the video and follow along. \n[Desktop 2019.09.23 - 00.49.39.02.mp4](Desktop_2019.09.23_-_00.49.39.02.mp4)\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "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", "Fractured object crashes Render\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.10.12\n\nBroken: version: 3.4.1\n\nRendering image crashes Blender\n\nThe attached file is the output of a fractured cube using RBDLabs, nothing else. It's a series of 965 simple static meshes. When displaying rendered shading in viewport, all is well. When doing Render > Render Image, then Blender crashes. Happens on my Mac M1 and Mac Intel, on Blender 3.3.4, 3.4.1, 3.5 and 3.6 alpha. If I delete the 115 last cells or the 134 first ones, then the render will properly happen. Thanks !\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "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", "Blender Crashes when trying to create a Pivot Constraint for armature\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU\n\nBroken: 3.33, 3.34, 3.35 Beta\nWorked: 2.79\n\nWhen trying to set a bone in the Pivot Constraint for the Armature, it crashes.\n\n1. Create an armature.\n2. Create a Pivot constraint from \"Object Constraint Properties > Add Object Constraint > Relationship > Pivot\".\n3. Select the armature in the Target field.\n4. Then select the Bone in the Bone field. (Blender crashes)\n\n", "inset and bevel edits crashing blender 3.x\nThreadripper 1950x 128 gb ram 2tb SSD (home)\nNVIDA 3080 updated to latest drivers\n\nIntel i7 64 gb ram 2 tb SSD (work)\nAMD 6900xt updated to latest drivers\n\n\nHappens on all 3.x versions of blender.\n\nIssue happens on both my home PC (the thread ripper) and my work PC.\n\nStart editing default cube add bevels, insets place some cuts... crashes within a couple of minutes. Happens in all display modes.. mesh, solid, renders. Happens with a smooth display mesh and hard edges. Super frustrating need to save just before doing any of these procedures on any modeling task. Always update video drivers which probably cant be the issue because two different families of video cards in two different machines have the same issue. Been doing this ever since I updated to Blender 3. I assume it's a plugin I installed because I can't imagine why this would happen on two completely different computers. Is there a dump file or something I can send? Here is a video of a typical crash. No dialog box... just blender vanishes in the the middle of editing.\n\n", "Crash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming)\nOperating system: Win 10\nGraphics card: Nvidia Quadro M5000 \n\nBroken: 3.4.1\nWorked: 3.4.1\n\nCrash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming). \n\n- Download file through the link from Google Drive attached (I leave the file as it is since I don't know what caused the problem)\n- Click in the collection \"Möblierung\",\n- create some new collection in it,\n- rename the new collection (with double click)\n- hit enter - crash\n\nOr create the collection, don't rename it and then click something in the interface (Blenderkit \"eye\" symbol in my case).\n\nReload didn't do anything, just kept crashing.\n\nLoaded a recent autosave, seems to work. Already hat to kill startup file and all settings yesterday, got permanent exception access violation crashes upon file load, after enabling some addon (TrueAssets) it worked.\n\nLink to the blend: view?usp=sharing\n\n" ]

[ "Entering into the edit mode when a curve is selected in a heavy scene crashes Blender ( EXCEPTION_ACCESS_VIOLATION )\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: blender-2.92.0-2d3b29de4fc7-windows64.zip\n\n\nI need to add couple curves in this heavy scene. I add a bezier curve and then try to go into the curve edit mode using the tab key. Blender crashes right at that moment. I can reproduce this exact error in this scene.\n\n\n\n\nI cant share the scene since it is for one of hour projects. However see the crash log I have attached. I am hoping that this will provide the necessary context. Please let me know if you need further debugging details. \n\n[006.crash.txt](006.crash.txt)\n\n", "Crash when entering Armature Edit mode in 3D Viewport aside a UV Editor split window\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Beta\nWorked: 2.91.2\n\n---\n\n## Short description of error:\nCrash when entering __Armature Edit mode__ in __3D Viewport__ if there is also a __UV Editor split window__ in the interface.\n\n---\n\n## Exact steps for others to reproduce the error\n{icon fa-plus} OS Conditon: **WIN 10** |Blender: **2.92.0 Beta**\n- Default scene with default cube deleted.\n- Add an __Armature__ object and split out a __UV editor__.\n- In the __3D Viewport__ ,enter __Armature Edit mode__ .The crash then should be reproduced.\n{icon bicycle spin} Below is a blend file with the setup above:\n[BugReportDemo.blend](BugReportDemo.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", "Regression: Attempt to move object with Copy Location (with Offset) crashes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nA consistent crash when trying to move an object with COPY LOC w/ Offset enabled.\n\n\n1. Open the attached blend file\n\n2. Move the pre-selected object in any direction, you may have to do this two or three times\n\n3. program will crash with EXCEPTION_ACCESS_VIOLATION\n\nThis is happening every time.\n\n```\nStack trace:\nblender.exe :0x00007FF73E03C510 blender::bounds::min_max<blender::VecBase<float,3> >\nblender.exe :0x00007FF73E03BD30 blender::FunctionRef<void __cdecl(blender::Bounds<blender::VecBase<float,3> > &)>::callback_fn<<lam\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF7425212F0 blender::CacheMutex::ensure\nblender.exe :0x00007FF73E042390 BKE_mesh_minmax\nblender.exe :0x00007FF73E0409F0 BKE_mesh_boundbox_get\nblender.exe :0x00007FF73E02E940 BKE_object_boundbox_get\nblender.exe :0x00007FF73E02F410 BKE_object_dimensions_get\nblender.exe :0x00007FF73E613520 RNA_property_float_get_index\nblender.exe :0x00007FF73E235050 dtar_get_prop_val\nblender.exe :0x00007FF73E235410 evaluate_driver\nblender.exe :0x00007FF73E168590 calculate_fcurve\nblender.exe :0x00007FF73E156270 BKE_animsys_eval_driver\nblender.exe :0x00007FF73E4464F0 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF73E446320 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7425175C0 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FF9998CA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FF9A5D192C0 recalloc\nKERNEL32.DLL :0x00007FF9A6F72690 BaseThreadInitThunk\nntdll.dll :0x00007FF9A882AA40 RtlUserThreadStart\n```\n\n", "PaintMode: Face Selection Mask Wireframe Drawing with generated modifiers\nWhen using face selection mask with an object that has generated modifiers the wireframe is drawn from the tesselated object. We should remove the edges that are not part of the original mesh.", "UV Editor face select mode fails to select ngons reliably\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.4.1\nWorked: never? (2.83 fails too)\n\nUV Editor face selection mode fails to select ngons reliably, because it uses face dot based selection, which can not be turned off. I was told to report scenarios where face dot based selection fails to work as bugs, so I am doing so here.\n\n1. Open the attached file\n2. Select the mesh object, enter the edit mode, and in the UV editor, switch selection mode to face\n3. Attempt to select some of the larger ngon UV face\nResult: The selection of larger ngon UV faces fails in many cases\nExpected The UV faces under the mouse cursor are selected when clicked on\n\n[UVSelectBug.blend](UVSelectBug.blend)\n[2023-02-06 12-20-58.mp4](2023-02-06_12-20-58.mp4)", "When \"orbit around selection\" is enabled, the camera orbits around world origin instead of selected object's origin while nothing is selected in edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.0\n\nWhen \"orbit around selection\" is enabled, the camera will orbit around world origin instead of selected object's origin in edit mode while no verts, edges, or faces are selected.\n\nStep 1: Go to Edit>Preferences>Navigation> and then enable \"Orbit Around Selection\"\nStep 2: Add a cube to the scene and move it in \"Object Mode\" away from the world center\nStep 3: Enter \"Edit Mode\" and deselect everything, then try moving the viewport camera.\n\nIntuitively what you'd think would happen in this situation is the camera should orbit around the origin point of the selected object you're currently editing, but instead what happens is the camera orbits around the 0,0,0 point of the scene. Which feels really odd, like blender is just switching to a default behavior or something?\n\n", " Selection future-proof design\nThere is an attempt to use GPU even more for selection, while we still have some long standing issues there:\n\n* Depth Select has performance issues on some systems.\n* Occluded selection is limited by screen resolution #75860 (Faulty selection when zoomed-out).\n\nWe should move forward with our selection design, get this over with, and make sure snap/selection/... all fall in line with the same design, so no effort is wasted going multiple directions.\n\nWorth noting that the VR project, and the eevee / cycles fisheye in the viewport selection task needs an abstraction between what is drawn in the viewport and what we select. It may be possible with the current architecture, but if we are to change things (going cpu?ray cast?) these cases should be taken into consideration.", "Box and Lasso select is extremely unreliable in Face or Edge select mode (selects non-visible faces or edges)\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 430.86\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nUsing box select is extremely unreliable while in Face select or Edge select mode (I didn't observe any problems in Vertex mode). It may end up selecting non-visible faces/edges inadvertently and with seemingly no pattern to its misbehavior or workarounds (shrinking range of the clip start/end doesn't fix it, enabling face centers doesn't fix it etc.)\n\nThis problem has existed for some time now but today I finally got fed up with it after losing several minutes of work again.\n\nI'm using a hidpi 4k screen, using Blender's UI scaling of 1.0, and OS scaling of 2.0 in case this matters.\n\n[box-select-bug.blend](box-select-bug.blend)\n- Start with default .blend\n- Enter edit mode and Subdivide cube twice\n- Switch to Face select mode (or Edge select mode)\n\n- Attempt to box-select a variety of faces on the cube\n- Notice that more often than not, extra faces which are not visible are still selected\n\nNo selection\n\n\nSelecting all visible faces with box-select\n\n\nNon-visible faces being selected :(\n\n\nNon-visible edges being selected :(\n\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", "Viewport Selection is getting slow depending on Scene Hierarchy depth / amount of objects\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Beta\nThis was also tested in 3.5.1 / 3.4 (not working as fast as expected)\n\nSelecting objects in the viewport and in the outliner is taking seconds and produces high CPU load.\nThe spikes on the CPU graph are only produced by selecting a geometry (single left click on geometry in the viewport).\n\nThe scene from the screenshot contains an agency export model with a lot of Emptys that are used for the scene hierarchy / CAD. 33K objects (22K emptys) / 55 Mio Triangles.\nAfter deleting the emptys the selection is getting a little faster but still lacks behind. (from 3 to 1.5 seconds)\nIn Isolation view (1 single mesh) deselecting and selecting a mesh again it also takes around 1 second to select the mesh again. In edit mode selecting a vert / edge is instant as usual.\nThe geometry had Custom Split Normals Data but removing the normals made no difference. \n\nTurning off Emptys selection in The outliner also brought not the same feeling like selecting in Edit Mode. \n\n- Open attached [15000_empties.blend](attachment) file (It is a simplified one)\n- Select any object from the 3D View\n\nNote: The more Empties hidden, the faster the selection becomes.\n\nThanks a lot making Blender this awesome <3\n\n[15000_empties.blend](attachment)", "Mirror Pose: Custom center of symmetry\nAs it is now, the Mirror Pose operator works through a rig/root bone center, which is of limited use when the character has moved away from that center while animating. The center of Mirror Pose should be selected on a per armature basis and should be available in linked/proxied armatures for the animators to change never at rigging stage, so i would potentially display it only in pose mode in the tool bar or under the pose options..\n\n- In the armature, you could have a bone selector box, where you can pick the mirror bone and axis.\n- If nothing is selected then it defaults back to the current behaviour.\n\nNote that this design task is for poses only, and not other places, like sculpting, where mirroring is used.\n", "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", "Formalize Default Selection Behavior and Key-map\nSelection should behave as consistent as possible throughout Blender. There should be a formal description for that to help avoiding inconsistencies.\n\nNOTE: This task is WIP, all content is tentative.\n\nWe *may* have to draw distinctions between right-click vs. left-click and 2D vs. 3D editors. For the latter, there are rather different requirements.\n\n### 2D Editors\n\n| Key-map item | Action\n| ---------------- | --------\n| {key Click} | Select item (and activate) an item. Deselect others.\n| {key Shift Click} | Toggle selection (and activate):\n| | * Select (and activate) if item was *not* selected\n| | * (Activate it item was selected)\n| | * Deselect item (if already active, or) if selected.\n| ... | ...\n\n\n[TODO make table per-tool?]", "Extended Controls for Camera Gizmo\nCurrently, when switching to the camera view, it’s not immediately clear to users how to manipulate it. The camera must be selected, and it requires some difficult multi-step actions to be able to rotate or move the camera. \n\nAdditionally, from a camera operation perspective, users usually need a more optimized and precise way to only affect the pitch, yaw, panning, tracking and zooming, separately. \n\nWe can make this a lot easier by surfacing optimized camera manipulation gizmos right in the viewport when viewing the scene through the camera view:\n\n\n", "Float slider in the redo panel of the \"add object\" operator does not hide the mouse cursor\nBroken: 2.79b, 2.83\nWorked: (None)\n\nThe problem is not seen in editing mode, but in object mode when adding an object\nand changing the properties in the redo panel, the mouse cursor does not disappear.\n\n\n", "Blender 2.80 Canceling of visibility actions during opened panel with object default parameters.\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560\n\n2.80 beta, 1df6a98b176f, blender2.8, 2019-03-05\n\n**Error description**\nLooks like a small flaw. Panel with default parameters(radius, etc..) of standard objects if objects just created - will be canceling your actions with outliner panel (visibility actions) if you dont close it and continue changing parametrs after that\nDemo: 0876b975cd74ce4d9400b6556e5cbe14.mp4\n\n**Steps to reproduce**\n\n- Open new general template\n- Add mesh - circle\n- Hide cube in outliner\n- In Adjust Last Operation panel change radius\n\nCube is no longer hidden" ]

[ "Circle Cursor not selection\nOperating system: MacBook Pro, Mojave 10.14.3\nGraphics card: Intel Iris Plus Graphics 655\n\nBroken: Version 2.80 (2.80 2019-03-18, Blender Foundation) - found in object view \nWorked: (optional)\n\nCircle cursor - with only camera, lamp and cube in object mode, user perspective, the circle cursor will select three items properly. When they are deselected and then one of them is selected again with the circle cursor, the cursor does not select them as they do not turn orange.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nStartup Blender.\nClick to dismiss splash screen.\nSelect circle cursor from \"T\" menu.\nSelect camera, lamp, and cube one at a time holding shift key.\nClick mouse anywhere else to deselect all.\nSelect camera or lamp or cube -- without holding shift key -- none of the items are selected, that is, turn orange.\n\nThis can be repeated on four attempts producing the same results" ]

[ "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "Knife tool fails on a non-planar n-gon\nBroken: 2.74 up to and including 2.92 master\nWorked: 2.73 (yes, I bisected that far back ;) )\n\n\nKnife tool fails to cut between verts in n-gons of certain configuration.\n\n\nLoad the attached .blend and try to make a knife cut between the two selected verts (i.e. try to create an edge connecting them).\n\n[knife_fail.blend](knife_fail.blend)\n\n(If you want to test in 2.73 yourself, copy the object from a running instance of 2.9x into 2.73 using ctrl+c/ctrl+v, then replace the mesh in another existing mesh object).", "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)", "Geometry nodes crash involving point translation and points to volume\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 3.0.0 Alpha\nWorked: Unknown.\nCannot open reference file in stable (crashes immediately). \nMy oldest 3.0 from 2021-08-01 (`836aeebf7077`) also has the issue.\n\nBlender crashes in certain setups involving point translation and points to volume.\n\n- Open .blend file\n- Connect \"Crash\" node with Reroute\n\nUpon some more testing I found that there are more specific values or ranges that cause the problem, when using the power node one is around 2 to the power of 24.003.\nKnowing values that crash, the attribute fill node can be used:\n\n\n[attribute-fill.blend](attribute-fill.blend)\n[attribute-power.crash.txt](attribute-power.crash.txt)", "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", "Toggle to Edit Mode call error when the Blender use linked a object data from another file\nOperating system: Linux 5.10.2\nGraphics card: Intel Haswel (4-th Gen ) HD Graphics 4600\n\nBroken: 2.92\n\n\nToggle to Edit Mode call error when the Blender use linked a object data from another file\n\n\n1) Create any object in a scene and save this file \n2) Create a new blend file and link the object from previous saved a file with `File` → `Link..` and then select this object.\n3) Then convert linked object to local object with `Object` → `Relations` → `Make Local...` → `Selected Objects`\n4) Select the object and press Tab that go to Edit Mode. \n5) Error - Unable to execute 'Toggle Editmode', error changing modes\n\nor download both files and then open linked.blend:\n\n[source.blend](source.blend)\n[linked.blend](linked.blend)\n\n", "Crash on Python API bpy.ops.mesh.rip_move()\nOperating system: Windows 10\nGraphics card: RTX3080\n\nBroken: 3.3.2, 3.4.0, 3.5.0-alpha\n\nCrash on calling `bpy.ops.mesh.rip_move()` from Python API.\n\n - Open new Blender file\n - Switch to Scripting workspace\n - Create file with\n```\nimport bpy\nbpy.context.area.ui_type = 'VIEW_3D'\nbpy.ops.mesh.rip_move()\nbpy.context.area.ui_type = \"TEXT_EDITOR\"\n```\n - Delete all objects\n - `Shift-A` to add cylinder\n - Tab` to edit mode\n - Click edge or vertex selection mode\n - Select an edge or vertex\n - Run script\n - Crash\n\nManually doing a `V` rip move and then using the \"reports\" list to copy over the exact command to line #3, also results in a crash\n[blender.crash.txt](blender.crash.txt)", "Blender (silently) fails when importing Sketchup Collada File\nMid-2014 MacBook Pro with Intel Iris Pro 1536 MB Graphics\n\nBroken: Version 2.79 (2.79 2017-09-11, Blender Foundation)\n\nTried to import a .dae file downloaded from Sketchup, and nothing happened after selecting the file from the Import dialog.\n\n\n\n - Went to K-5299-RA-Highline-Classic-10-gpf-Comfort-Height-two-piece-elongated-toilet-with-Class-Five-flush-technology-and-right-hand-trip-lever \n - Downloaded the Collada File from the page; also uploaded here: [model.dae](model.dae) \n - Opened blender from the command line\n - Selected menu: File > Import > Collada (Default) (.dae)\n - Selected the model.dae in the dialog. The dialog closed, but see an empty scene still. I expected to see an error or something if it couldn't import it.\n\nOn the command line, I see the following:\n\n```\nRead prefs: /Users/myuser/Library/Application Support/Blender/2.79/config/userpref.blend\nColor management: display \"sRGB\" used by scene not found, setting to default (\"sRGB / BT.709\").\nColor management: scene view \"Default\" not found, setting default \"sRGB EOTF\".\nColor management: sequencer colorspace \"sRGB\" not found, will use default instead.\nfound bundled python: /Applications/blender.app/Contents/Resources/2.79/python\ndrop file /Users/myuser/Downloads/model.dae\nWriting node id='ID4', name='skpC9F6'\nWriting node id='ID5', name='instance_1'\nCannot find object for node referenced by <instance_node name=\"\">.\nWriting node id='ID6', name='_5299-RA'\nWriting node id='', name='SketchUp'\nWriting node id='', name='skp_camera_Last_Saved_SketchUp_View'\nWriting node id='ID3', name='instance_0'\ncreate <instance_node> under node id=ID3 from node id=ID4\ngot 25 library nodes to free\n```\n\nThe line `Cannot find object for node referenced by <instance_node name=\"\">.` being output does make me wonder if something is going wrong. However, I can see the file OK in a https:*threejs.org/ based Collada viewer (and the associated https:*threejs.org/examples/js/loaders/ColladaLoader.js )\n\n\n\nHas anyone else seen this problem in 2.79b?\n\n", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "EXCEPTION_ACCESS_VIOLATION when baking between linked objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen experimenting with the idea of having linked duplicate objects and bake materials between them I found a reproducible crash.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF63BB28F6E\nModule : C:\\Program Files\\Blender Foundation\\Blender 2.82\\blender.exe\n```\n\n- Oppen attached file\n- Try to bake the textures (blender crashes)\nSometimes it doesn't crash the first time but always atleast on the second or third attempt.\n\n[mushroom.blend](mushroom.blend)\n", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n", "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)", "2.8: Python API: Changing area type on frame change crashes Blender\nOperating system: Windows 10\nGraphics card: Quadro P4200/PCIe/SSE2\n\nBroken: 2.81a (also crashes in 2.79 and 2.80)\n\nI am attempting to sample the individual frames of an image on frame change, using a solution similar to the one described here: 5. I cannot seem to set the viewer area, however, from this context, as `bpy.context.screen` is `None`, and `bpy.context.window_manager.windows- [x].screen` seems to crash Blender in some situations.\n\nFrom the default startup file, run the following basic code:\n\n```\nimport bpy\n\ndef on_frame_change(scn):\n bpy.context.window_manager.windows[0].screen.areas[0].type = \"IMAGE_EDITOR\"\n\nbpy.app.handlers.frame_change_pre.append(on_frame_change)\n```\n\nRun the `Render Animation` operator to crash Blender.\n\nNote: This code runs fine when playing the animation in the 3D Viewport. It seems that this bug relates to the render context only.", "Latest Blender 4.0 not opening\nOperating system: Linux-5.15.0-83-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: blender-4.0.0-alpha+main.b5c89822ac40-linux.x86_64-release\nWorked: 3.6.3 Release Candidate\n\nAfter double-clicking on the \"blender\" starter-folder, it shows what you can see on the picture, before canceling the session\n\nJust try to start 4.0. I guess it's my drivers and noone can confirm, right?\n\n" ]

[ "Access Violation Exception upon import the geometry via python\nOperating system: Windows 10 Home v1803 Build 17134.706\nGraphics card: NVIDIA GeForce GTX 1050 Ti\n\nBroken: 2.80, e73647bf5b44, 2019-06-18\nWorked: 2.80, d525c76003b3, blender 2.7 (branch), 2019-05-26\n\nWhenever I try to import a mesh (fbx/obj) using bpy.ops.import_scene.fbx(filepath=meshPath) I get the access violation exception and the blender crashes afterward.\n\nIt is happening with an add-on that is communicating with one of our apps. " ]