Datasets:

mano-wii

/

blender_duplicates

like 0

[ "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)", "Proposal to highlight menus during menu search\nThis is a small quality of life feature for menu search.\n\nFor each search result item selected, we highlight the menu where it lives. In this case Clear Seam is in the Edge menu:\n\n\n\n(split out from #74157 (Use menus for operator search & various improvements)).", "addon preferences changed by code (not by user in UI) are not saved\nOperating system: Ubuntu\nGraphics card: RTX\n\nBroken: master\nWorked: ?\n\naddon preferences changed by code (not by user in UI) are not saved at Blender close.\n\n- Open Blender. Load Factory Settings, close Blender. \n- Open Blender\n- In console, change an addon preferences. For example, change device of Cycles : bpy.context.preferences.addons['cycles'].preferences['compute_device_type'] = 1 (this change to CUDA)\n- Close Blender. No log saying preferences are saved.\n- Open Blender again, check that device is still None. pref save is KO\n- Change preferences to \"CUDA\" by clicking with your mouse\n- Close Blender\n- See that a log saying preferences are saved\n- Open again, you can see that preferences are set to CUDA, pref save was OK", "Remap user material selection uses enum menu instead of searchable list \nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\nAlso tried on 2.82 daily build 12/19\nWorked: (optional)\n\nI'm trying to remap some of my materials, but the menu that opens to allow me to choose the replacement material doesn't allow me to see all the materials available--there is no way to scroll down to see more of the list. I tried on the daily build for 12/19, and unlike the stable version, there are arrows, but they also don't open the full menu. \n\nGo to outliner>blender file>materials, right click on a material, choose remap, Outliner ID data remap opens, click on New ID to open that menu, and that's where I can't see all of the choices. I'm attaching a screenshot, because it only happens with a larger file with many materials. In the screenshot, the last material I can access is labelled M_Photo, and can't scroll to any beyond that. \n\n", "Unable to add drivers to bone collections visibility\nOperating system: Windows 11\nGraphics card: RTX 4060ti\n\nBroken: 4.0.0 Alpha 2023-09-06\nWorked: Before bone collections were merged\n\nThis kinda leans into feature requests, but it is a regression nonetheless. Drivers also weren't acknowledged from what i could see.\nBefore bone collections were recently introduced, you could add a driver to each layer to influence it's visibility, and i know many people liked to use that in order to influence the visibility of a group of bones. Currently you cannot influence the visibility of a bone collection through drivers, the only option to do it now being controling the visibility of individual bones.\n\nN/A\n\n", "Restoring Blender keymaps restores other presets, too\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0\n\nMake any changes to the Industry Compatible shortcuts, then to the Blender shortcuts and restore them to the original and the shortcuts for the Industry Compatible shortcuts are restored, too(see attached video).\n[2021-11-10 11-05-14.mp4](2021-11-10_11-05-14.mp4)\n\n1. Go Preferences>Keymap, so you don't loose your valuable shortcuts disable Auto-Save Preferences in the bottom left menu, and change any shortcut in the Industry Compatible mapping\n2. Change the mapping preset to Blender\n3. Change any shortcut mapping, too\n4. Restore the shortcut mapping of the Blender preset\n5. Go back the the Industry Compatible preset and your changes you made in step 1 are unassigned", "Sidebar changes\nCurrently, the Sidebar has several UI-related issues, especially in the 3D View.\n\n\n\n - Use of vertical text\n - Finite space for tabs\n - The tab bar works poorly with Region Overlap, pushing the panels further into the viewport, and overlapping\n\nYou can see an example of using lots of tabs here. This is an extreme example: \n\n\nWe also have a visual clash with the Properties tabs often:\n\n\nTabs also often appear outside the panel region, which looks glitchy:\n\n\n\n----------\n\nWe can address these issues by making a number of changes:\n\n\n\n\n - No vertical text\n - No bar which extends all the way down the viewport\n - Not bound by the viewport height \n - Floating design mirrors the toolbar\n\n\nThe menu at the top could be expanded into a list, which would allow users to re-order sections. If users mainly use a couple of sections, they could move those to the top for easy access. \n\nWe could also add the ability to view several sections at once, something which would be hard to support with tabs:\n\n\n\nNote: This would require changes to UI lists in Blender to support this, but would also benefit other areas.\n\nThese changes could also be adopted by other sidebars in Blender. ", "Preferences window lags with add-ons preferences UI raises an exception\nOperating system: Windows 10 1903\nGraphics card: GTX970\n\nBroken: blender-2.80-9c5d54bfaf48-win64\nWorked:blender-2.80-8ac0fef4dfd1-win64\n\n\nWhen you click on a triangle in the addons list which is corresponds to an addon which contains VISIBLE_IPO_ON in code, it starts to incredibly lag. Seriously, one frame per second or two. Everything is quick and snappy until you press that goddam triangle. After that whole Preferences window behave like this till the restart of Blender. Other windows are unaffected.\nObserve: \nwatch?v=9fObpt0L8B0\n\nIn a log I can see a long and sad error: Traceback (most recent call last):\n```\nFile \"C:\\Users\\ostap\\AppData\\Roaming\\Blender Foundation\\Blender\\2.80\\scripts\\addons\\DECALmachine\\ui\\UILists.py\", line 16, in draw_item\n row.prop(item, \"isvisible\", text=\"\", icon=isvisibleicon, emboss=False)\n```\nTypeError: UILayout.prop(): error with keyword argument \"icon\" - enum \"VISIBLE_IPO_ON\" not found in ('NONE', 'QUESTION', 'ERROR', 'CANCEL', 'TRIA_RIGHT', 'TRIA_DOWN', 'TRIA_LEFT', 'TRIA_UP', 'ARROW_LEFTRIGHT', 'PLUS', 'DISCLOSURE_TRI_RIGHT', 'DISCLOSURE_TRI_DOWN', 'RADIOBUT_OFF', 'RADIOBUT_ON', 'MENU_PANEL', 'BLENDER', 'GRIP', 'DOT', 'COLLAPSEMENU', 'X', 'DUPLICATE', 'TRASH', 'COLLECTION_NEW', 'NODE', 'NODE_SEL', 'WINDOW', 'WORKSPACE', 'RIGHTARROW_THIN', 'BORDERMOVE', 'VIEWZOOM', 'ADD', 'REMOVE', 'PANEL_CLOSE', 'COPY_ID', 'EYEDROPPER', 'AUTO', 'CHECKBOX_DEHLT', 'CHECKBOX_HLT', 'UNLOCKED', 'LOCKED', 'UNPINNED', 'PINNED', 'SCREEN_BACK', 'RIGHTARROW', 'DOWNARROW_HLT', 'FCURVE_SNAPSHOT', 'OBJECT_HIDDEN', 'PLUGIN', 'HELP', 'GHOST_ENABLED', 'COLOR', 'UNLINKED', 'LINKED', 'HAND', 'ZOOM_ALL', 'ZOOM_SELECTED', 'ZOOM_PREVIOUS', 'ZOOM_IN', 'ZOOM_OUT', 'DRIVER_DISTANCE', 'DRIVER_ROTATIONAL_DIFFERENCE', 'DRIVER_TRANSFORM', 'FREEZE', 'STYLUS_PRESSURE', 'GHOST_DISABLED', 'FILE_NEW', 'FILE_TICK', 'QUIT', 'URL', 'RECOVER_LAST', 'THREE_DOTS', 'FULLSCREEN_ENTER', 'FULLSCREEN_EXIT', 'LIGHT', 'MATERIAL', 'TEXTURE', 'ANIM', 'WORLD', 'SCENE', 'OUTPUT', 'SCRIPT', 'PARTICLES', 'PHYSICS', 'SPEAKER', 'TOOL_SETTINGS', 'SHADERFX', 'MODIFIER', 'BLANK1', 'FAKE_USER_OFF', 'FAKE_USER_ON', 'VIEW3D', 'GRAPH', 'OUTLINER', 'PROPERTIES', 'FILEBROWSER', 'IMAGE', 'INFO', 'SEQUENCE', 'TEXT', 'SOUND', 'ACTION', 'NLA', 'PREFERENCES', 'TIME', 'NODETREE', 'CONSOLE', 'TRACKER', 'ASSET_MANAGER', 'NODE_COMPOSITING', 'NODE_TEXTURE', 'NODE_MATERIAL', 'UV', 'OBJECT_DATAMODE', 'EDITMODE_HLT', 'UV_DATA', 'VPAINT_HLT', 'TPAINT_HLT', 'WPAINT_HLT', 'SCULPTMODE_HLT', 'POSE_HLT', 'PARTICLEMODE', 'TRACKING', 'TRACKING_BACKWARDS', 'TRACKING_FORWARDS', 'TRACKING_BACKWARDS_SINGLE', 'TRACKING_FORWARDS_SINGLE', 'TRACKING_CLEAR_BACKWARDS', 'TRACKING_CLEAR_FORWARDS', 'TRACKING_REFINE_BACKWARDS', 'TRACKING_REFINE_FORWARDS', 'SCENE_DATA', 'RENDERLAYERS', 'WORLD_DATA', 'OBJECT_DATA', 'MESH_DATA', 'CURVE_DATA', 'META_DATA', 'LATTICE_DATA', 'LIGHT_DATA', 'MATERIAL_DATA', 'TEXTURE_DATA', 'ANIM_DATA', 'CAMERA_DATA', 'PARTICLE_DATA', 'LIBRARY_DATA_DIRECT', 'GROUP', 'ARMATURE_DATA', 'COMMUNITY', 'BONE_DATA', 'CONSTRAINT', 'SHAPEKEY_DATA', 'CONSTRAINT_BONE', 'CAMERA_STEREO', 'PACKAGE', 'UGLYPACKAGE', 'EXPERIMENTAL', 'BRUSH_DATA', 'IMAGE_DATA', 'FILE', 'FCURVE', 'FONT_DATA', 'RENDER_RESULT', 'SURFACE_DATA', 'EMPTY_DATA', 'PRESET', 'RENDER_ANIMATION', 'RENDER_STILL', 'LIBRARY_DATA_BROKEN', 'BOIDS', 'STRANDS', 'LIBRARY_DATA_INDIRECT', 'GREASEPENCIL', 'LINE_DATA', 'LIBRARY_DATA_OVERRIDE', 'GROUP_BONE', 'GROUP_VERTEX', 'GROUP_VCOL', 'GROUP_UVS', 'FACE_MAPS', 'RNA', 'RNA_ADD', 'MOUSE_LMB', 'MOUSE_MMB', 'MOUSE_RMB', 'MOUSE_MOVE', 'MOUSE_LMB_DRAG', 'MOUSE_MMB_DRAG', 'MOUSE_RMB_DRAG', 'PRESET_NEW', 'DECORATE', 'DECORATE_KEYFRAME', 'DECORATE_ANIMATE', 'DECORATE_DRIVER', 'DECORATE_LINKED', 'DECORATE_LIBRARY_OVERRIDE', 'DECORATE_UNLOCKED', 'DECORATE_LOCKED', 'DECORATE_OVERRIDE', 'TRACKER_DATA', 'HEART', 'ORPHAN_DATA', 'USER', 'SYSTEM', 'SETTINGS', 'OUTLINER_OB_EMPTY', 'OUTLINER_OB_MESH', 'OUTLINER_OB_CURVE', 'OUTLINER_OB_LATTICE', 'OUTLINER_OB_META', 'OUTLINER_OB_LIGHT', 'OUTLINER_OB_CAMERA', 'OUTLINER_OB_ARMATURE', 'OUTLINER_OB_FONT', 'OUTLINER_OB_SURFACE', 'OUTLINER_OB_SPEAKER', 'OUTLINER_OB_FORCE_FIELD', 'OUTLINER_OB_GROUP_INSTANCE', 'OUTLINER_OB_GREASEPENCIL', 'OUTLINER_OB_LIGHTPROBE', 'OUTLINER_OB_IMAGE', 'RESTRICT_COLOR_OFF', 'RESTRICT_COLOR_ON', 'HIDE_ON', 'HIDE_OFF', 'RESTRICT_SELECT_ON', 'RESTRICT_SELECT_OFF', 'RESTRICT_RENDER_ON', 'RESTRICT_RENDER_OFF', 'RESTRICT_INSTANCED_OFF', 'OUTLINER_DATA_EMPTY', 'OUTLINER_DATA_MESH', 'OUTLINER_DATA_CURVE', 'OUTLINER_DATA_LATTICE', 'OUTLINER_DATA_META', 'OUTLINER_DATA_LIGHT', 'OUTLINER_DATA_CAMERA', 'OUTLINER_DATA_ARMATURE', 'OUTLINER_DATA_FONT', 'OUTLINER_DATA_SURFACE', 'OUTLINER_DATA_SPEAKER', 'OUTLINER_DATA_LIGHTPROBE', 'OUTLINER_DATA_GP_LAYER', 'OUTLINER_DATA_GREASEPENCIL', 'GP_SELECT_POINTS', 'GP_SELECT_STROKES', 'GP_MULTIFRAME_EDITING', 'GP_ONLY_SELECTED', 'GP_SELECT_BETWEEN_STROKES', 'MODIFIER_OFF', 'MODIFIER_ON', 'ONIONSKIN_OFF', 'ONIONSKIN_ON', 'RESTRICT_VIEW_ON', 'RESTRICT_VIEW_OFF', 'RESTRICT_INSTANCED_ON', 'MESH_PLANE', 'MESH_CUBE', 'MESH_CIRCLE', 'MESH_UVSPHERE', 'MESH_ICOSPHERE', 'MESH_GRID', 'MESH_MONKEY', 'MESH_CYLINDER', 'MESH_TORUS', 'MESH_CONE', 'MESH_CAPSULE', 'EMPTY_SINGLE_ARROW', 'LIGHT_POINT', 'LIGHT_SUN', 'LIGHT_SPOT', 'LIGHT_HEMI', 'LIGHT_AREA', 'CUBE', 'SPHERE', 'CONE', 'META_PLANE', 'META_CUBE', 'META_BALL', 'META_ELLIPSOID', 'META_CAPSULE', 'SURFACE_NCURVE', 'SURFACE_NCIRCLE', 'SURFACE_NSURFACE', 'SURFACE_NCYLINDER', 'SURFACE_NSPHERE', 'SURFACE_NTORUS', 'EMPTY_AXIS', 'STROKE', 'EMPTY_ARROWS', 'CURVE_BEZCURVE', 'CURVE_BEZCIRCLE', 'CURVE_NCURVE', 'CURVE_NCIRCLE', 'CURVE_PATH', 'LIGHTPROBE_CUBEMAP', 'LIGHTPROBE_PLANAR', 'LIGHTPROBE_GRID', 'COLOR_RED', 'COLOR_GREEN', 'COLOR_BLUE', 'TRIA_RIGHT_BAR', 'TRIA_DOWN_BAR', 'TRIA_LEFT_BAR', 'TRIA_UP_BAR', 'FORCE_FORCE', 'FORCE_WIND', 'FORCE_VORTEX', 'FORCE_MAGNETIC', 'FORCE_HARMONIC', 'FORCE_CHARGE', 'FORCE_LENNARDJONES', 'FORCE_TEXTURE', 'FORCE_CURVE', 'FORCE_BOID', 'FORCE_TURBULENCE', 'FORCE_DRAG', 'FORCE_SMOKEFLOW', 'RIGID_BODY', 'RIGID_BODY_CONSTRAINT', 'IMAGE_PLANE', 'IMAGE_BACKGROUND', 'IMAGE_REFERENCE', 'NODE_INSERT_ON', 'NODE_INSERT_OFF', 'NODE_TOP', 'NODE_SIDE', 'NODE_CORNER', 'SELECT_SET', 'SELECT_EXTEND', 'SELECT_SUBTRACT', 'SELECT_INTERSECT', 'SELECT_DIFFERENCE', 'ALIGN_LEFT', 'ALIGN_CENTER', 'ALIGN_RIGHT', 'ALIGN_JUSTIFY', 'ALIGN_FLUSH', 'ALIGN_TOP', 'ALIGN_MIDDLE', 'ALIGN_BOTTOM', 'BOLD', 'ITALIC', 'UNDERLINE', 'SMALL_CAPS', 'HOLDOUT_OFF', 'HOLDOUT_ON', 'INDIRECT_ONLY_OFF', 'INDIRECT_ONLY_ON', 'CON_CAMERASOLVER', 'CON_FOLLOWTRACK', 'CON_OBJECTSOLVER', 'CON_LOCLIKE', 'CON_ROTLIKE', 'CON_SIZELIKE', 'CON_TRANSLIKE', 'CON_DISTLIMIT', 'CON_LOCLIMIT', 'CON_ROTLIMIT', 'CON_SIZELIMIT', 'CON_SAMEVOL', 'CON_TRANSFORM', 'CON_TRANSFORM_CACHE', 'CON_CLAMPTO', 'CON_KINEMATIC', 'CON_LOCKTRACK', 'CON_SPLINEIK', 'CON_STRETCHTO', 'CON_TRACKTO', 'CON_ARMATURE', 'CON_CHILDOF', 'CON_FLOOR', 'CON_FOLLOWPATH', 'CON_PIVOT', 'CON_SHRINKWRAP', 'MODIFIER_DATA', 'MOD_WAVE', 'MOD_BUILD', 'MOD_DECIM', 'MOD_MIRROR', 'MOD_SOFT', 'MOD_SUBSURF', 'HOOK', 'MOD_PHYSICS', 'MOD_PARTICLES', 'MOD_BOOLEAN', 'MOD_EDGESPLIT', 'MOD_ARRAY', 'MOD_UVPROJECT', 'MOD_DISPLACE', 'MOD_CURVE', 'MOD_LATTICE', 'MOD_TINT', 'MOD_ARMATURE', 'MOD_SHRINKWRAP', 'MOD_CAST', 'MOD_MESHDEFORM', 'MOD_BEVEL', 'MOD_SMOOTH', 'MOD_SIMPLEDEFORM', 'MOD_MASK', 'MOD_CLOTH', 'MOD_EXPLODE', 'MOD_FLUIDSIM', 'MOD_MULTIRES', 'MOD_SMOKE', 'MOD_SOLIDIFY', 'MOD_SCREW', 'MOD_VERTEX_WEIGHT', 'MOD_DYNAMICPAINT', 'MOD_REMESH', 'MOD_OCEAN', 'MOD_WARP', 'MOD_SKIN', 'MOD_TRIANGULATE', 'MOD_WIREFRAME', 'MOD_DATA_TRANSFER', 'MOD_NORMALEDIT', 'MOD_PARTICLE_INSTANCE', 'MOD_HUE_SATURATION', 'MOD_NOISE', 'MOD_OFFSET', 'MOD_SIMPLIFY', 'MOD_THICKNESS', 'MOD_INSTANCE', 'MOD_TIME', 'MOD_OPACITY', 'REC', 'PLAY', 'FF', 'REW', 'PAUSE', 'PREV_KEYFRAME', 'NEXT_KEYFRAME', 'PLAY_SOUND', 'PLAY_REVERSE', 'PREVIEW_RANGE', 'ACTION_TWEAK', 'PMARKER_ACT', 'PMARKER_SEL', 'PMARKER', 'MARKER_HLT', 'MARKER', 'KEYFRAME_HLT', 'KEYFRAME', 'KEYINGSET', 'KEY_DEHLT', 'KEY_HLT', 'MUTE_IPO_OFF', 'MUTE_IPO_ON', 'DRIVER', 'SOLO_OFF', 'SOLO_ON', 'FRAME_PREV', 'FRAME_NEXT', 'NLA_PUSHDOWN', 'IPO_CONSTANT', 'IPO_LINEAR', 'IPO_BEZIER', 'IPO_SINE', 'IPO_QUAD', 'IPO_CUBIC', 'IPO_QUART', 'IPO_QUINT', 'IPO_EXPO', 'IPO_CIRC', 'IPO_BOUNCE', 'IPO_ELASTIC', 'IPO_BACK', 'IPO_EASE_IN', 'IPO_EASE_OUT', 'IPO_EASE_IN_OUT', 'NORMALIZE_FCURVES', 'VERTEXSEL', 'EDGESEL', 'FACESEL', 'CURSOR', 'PIVOT_BOUNDBOX', 'PIVOT_CURSOR', 'PIVOT_INDIVIDUAL', 'PIVOT_MEDIAN', 'PIVOT_ACTIVE', 'CENTER_ONLY', 'ROOTCURVE', 'SMOOTHCURVE', 'SPHERECURVE', 'INVERSESQUARECURVE', 'SHARPCURVE', 'LINCURVE', 'NOCURVE', 'RNDCURVE', 'PROP_OFF', 'PROP_ON', 'PROP_CON', 'PROP_PROJECTED', 'PARTICLE_POINT', 'PARTICLE_TIP', 'PARTICLE_PATH', 'SNAP_OFF', 'SNAP_ON', 'SNAP_NORMAL', 'SNAP_GRID', 'SNAP_VERTEX', 'SNAP_EDGE', 'SNAP_FACE', 'SNAP_VOLUME', 'SNAP_INCREMENT', 'STICKY_UVS_LOC', 'STICKY_UVS_DISABLE', 'STICKY_UVS_VERT', 'CLIPUV_DEHLT', 'CLIPUV_HLT', 'SNAP_PEEL_OBJECT', 'GRID', 'OBJECT_ORIGIN', 'ORIENTATION_GLOBAL', 'ORIENTATION_GIMBAL', 'ORIENTATION_LOCAL', 'ORIENTATION_NORMAL', 'ORIENTATION_VIEW', 'COPYDOWN', 'PASTEDOWN', 'PASTEFLIPUP', 'PASTEFLIPDOWN', 'VIS_SEL_11', 'VIS_SEL_10', 'VIS_SEL_01', 'VIS_SEL_00', 'AUTOMERGE_OFF', 'AUTOMERGE_ON', 'UV_VERTEXSEL', 'UV_EDGESEL', 'UV_FACESEL', 'UV_ISLANDSEL', 'UV_SYNC_SELECT', 'GIZMO', 'ORIENTATION_CURSOR', 'NORMALS_VERTEX', 'NORMALS_FACE', 'NORMALS_VERTEX_FACE', 'SHADING_BBOX', 'SHADING_WIRE', 'SHADING_SOLID', 'SHADING_RENDERED', 'SHADING_TEXTURE', 'OVERLAY', 'XRAY', 'LOCKVIEW_OFF', 'LOCKVIEW_ON', 'AXIS_SIDE', 'AXIS_FRONT', 'AXIS_TOP', 'NDOF_DOM', 'NDOF_TURN', 'NDOF_FLY', 'NDOF_TRANS', 'LAYER_USED', 'LAYER_ACTIVE', 'SORTALPHA', 'SORTBYEXT', 'SORTTIME', 'SORTSIZE', 'SHORTDISPLAY', 'LONGDISPLAY', 'IMGDISPLAY', 'BOOKMARKS', 'FONTPREVIEW', 'FILTER', 'NEWFOLDER', 'FILE_PARENT', 'FILE_REFRESH', 'FILE_FOLDER', 'FILE_BLANK', 'FILE_BLEND', 'FILE_IMAGE', 'FILE_MOVIE', 'FILE_SCRIPT', 'FILE_SOUND', 'FILE_FONT', 'FILE_TEXT', 'SORT_DESC', 'SORT_ASC', 'LINK_BLEND', 'APPEND_BLEND', 'IMPORT', 'EXPORT', 'LOOP_BACK', 'LOOP_FORWARDS', 'BACK', 'FORWARD', 'FILE_CACHE', 'FILE_VOLUME', 'FILE_3D', 'FILE_HIDDEN', 'FILE_BACKUP', 'DISK_DRIVE', 'MATPLANE', 'MATSPHERE', 'MATCUBE', 'MONKEY', 'HAIR', 'ALIASED', 'ANTIALIASED', 'MAT_SPHERE_SKY', 'MATSHADERBALL', 'MATCLOTH', 'MATFLUID', 'WORDWRAP_OFF', 'WORDWRAP_ON', 'SYNTAX_OFF', 'SYNTAX_ON', 'LINENUMBERS_OFF', 'LINENUMBERS_ON', 'SCRIPTPLUGINS', 'SEQ_SEQUENCER', 'SEQ_PREVIEW', 'SEQ_LUMA_WAVEFORM', 'SEQ_CHROMA_SCOPE', 'SEQ_HISTOGRAM', 'SEQ_SPLITVIEW', 'IMAGE_RGB', 'IMAGE_RGB_ALPHA', 'IMAGE_ALPHA', 'IMAGE_ZDEPTH', 'VIEW_PERSPECTIVE', 'VIEW_ORTHO', 'VIEW_CAMERA', 'VIEW_PAN', 'VIEW_ZOOM', 'BRUSH_BLOB', 'BRUSH_BLUR', 'BRUSH_CLAY', 'BRUSH_CLAY_STRIPS', 'BRUSH_CLONE', 'BRUSH_CREASE', 'BRUSH_FILL', 'BRUSH_FLATTEN', 'BRUSH_GRAB', 'BRUSH_INFLATE', 'BRUSH_LAYER', 'BRUSH_MASK', 'BRUSH_MIX', 'BRUSH_NUDGE', 'BRUSH_PINCH', 'BRUSH_SCRAPE', 'BRUSH_SCULPT_DRAW', 'BRUSH_SMEAR', 'BRUSH_SMOOTH', 'BRUSH_SNAKE_HOOK', 'BRUSH_SOFTEN', 'BRUSH_TEXDRAW', 'BRUSH_TEXFILL', 'BRUSH_TEXMASK', 'BRUSH_THUMB', 'BRUSH_ROTATE', 'GPBRUSH_SMOOTH', 'GPBRUSH_THICKNESS', 'GPBRUSH_STRENGTH', 'GPBRUSH_GRAB', 'GPBRUSH_PUSH', 'GPBRUSH_TWIST', 'GPBRUSH_PINCH', 'GPBRUSH_RANDOMIZE', 'GPBRUSH_CLONE', 'GPBRUSH_WEIGHT', 'GPBRUSH_PENCIL', 'GPBRUSH_PEN', 'GPBRUSH_INK', 'GPBRUSH_INKNOISE', 'GPBRUSH_BLOCK', 'GPBRUSH_MARKER', 'GPBRUSH_FILL', 'GPBRUSH_ERASE_SOFT', 'GPBRUSH_ERASE_HARD', 'GPBRUSH_ERASE_STROKE', 'SMALL_TRI_RIGHT_VEC', 'KEYTYPE_KEYFRAME_VEC', 'KEYTYPE_BREAKDOWN_VEC', 'KEYTYPE_EXTREME_VEC', 'KEYTYPE_JITTER_VEC', 'KEYTYPE_MOVING_HOLD_VEC', 'HANDLETYPE_FREE_VEC', 'HANDLETYPE_ALIGNED_VEC', 'HANDLETYPE_VECTOR_VEC', 'HANDLETYPE_AUTO_VEC', 'HANDLETYPE_AUTO_CLAMP_VEC', 'COLORSET_01_VEC', 'COLORSET_02_VEC', 'COLORSET_03_VEC', 'COLORSET_04_VEC', 'COLORSET_05_VEC', 'COLORSET_06_VEC', 'COLORSET_07_VEC', 'COLORSET_08_VEC', 'COLORSET_09_VEC', 'COLORSET_10_VEC', 'COLORSET_11_VEC', 'COLORSET_12_VEC', 'COLORSET_13_VEC', 'COLORSET_14_VEC', 'COLORSET_15_VEC', 'COLORSET_16_VEC', 'COLORSET_17_VEC', 'COLORSET_18_VEC', 'COLORSET_19_VEC', 'COLORSET_20_VEC', 'EVENT_A', 'EVENT_B', 'EVENT_C', 'EVENT_D', 'EVENT_E', 'EVENT_F', 'EVENT_G', 'EVENT_H', 'EVENT_I', 'EVENT_J', 'EVENT_K', 'EVENT_L', 'EVENT_M', 'EVENT_N', 'EVENT_O', 'EVENT_P', 'EVENT_Q', 'EVENT_R', 'EVENT_S', 'EVENT_T', 'EVENT_U', 'EVENT_V', 'EVENT_W', 'EVENT_X', 'EVENT_Y', 'EVENT_Z', 'EVENT_SHIFT', 'EVENT_CTRL', 'EVENT_ALT', 'EVENT_OS', 'EVENT_F1', 'EVENT_F2', 'EVENT_F3', 'EVENT_F4', 'EVENT_F5', 'EVENT_F6', 'EVENT_F7', 'EVENT_F8', 'EVENT_F9', 'EVENT_F10', 'EVENT_F11', 'EVENT_F12', 'EVENT_ESC', 'EVENT_TAB', 'EVENT_PAGEUP', 'EVENT_PAGEDOWN', 'EVENT_RETURN')\n\nAnd after changing VISIBLE_IPO_ON/OFF to HIDE_OFF/ON in the mentioned file issue disappears. Of course you may say that it's the issue with an un-updated addons. but that's weird. when Blender starts to misbehave instead of showing error message about the issue, isn't it?\n\n1. Open any scroll of the addon with VISIBLE_IPO_ON in it. \n2. Enjoy the performance. ", "Sequencer: Can't toggle Channels sidebar when VSE view type is \"Sequencer & Preview\"\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\nversion: 3.2.0\n\nAll in the title.\n\n1) Be in Video Sequencer editor\n2) Switch view type to Sequencer & Preview\n3) Try to toggle Channels sidebar : either with the little arrow (that doesn't show up), or by going to View > Channels (it doesn't toggle the sidebar, its checkbox doesn't get checked)\n\n", "Tweak tool deselects previously selected items.\nOperating system: Windows\nGraphics card: 1060\n\nBroken: All 2.8 versions\n\nTweak tool deselects previously selected items.\n\n\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", "Support for keeping preferences of disabled add-ons\nCurrently disabling an add-on removes it's preferences.\n\nUsers may have many options for an add-on which they don't want to loose when it's disabled.\n\nSee #71451 (Support for keeping preferences of disabled add-ons) for a report on this issue.\n\nProposed solution:\n\n- When disabling an add-on which has preferences, keep the preferences instead of freeing them.\n\n *Internally this could be a list of disabled add-ons, used to restore the preferences when enabling them later.*\n- Add button to add-ons with preferences to reset preferences.\n\n *While not essential, without this there is no way to reset an add-ons preferences, where there was beforehand.*\n- Add a drop-down menu (replacing the current refresh button) which has a menu item to remove all unused add-ons (to prevent accumulation). This menu will contain the \"Refresh\" button too.\n\n *Exact details for the UI can be changed, suggest to replace the \"Refresh\" button to avoid too much clutter for actions that aren't used often.*", "Highlight active item in pop-up menu (eg: Editor Type)\nCurrently the only way for newcomers to learn what is the currently chosen Editor in an Area is to compare the icon in the Editor Type combo-box with the list of icons when the combo box is open (it's not something that long time users think about).", "Missing icons for the release\nThere are typically a few new features for each release that need an icon. We can collect them here and make sure they are added before the release (before Bcon3 really).\n\nCurrently missing:\n\n- [x] Geometry Nodes Editor\n- [x] Line art modifier\n- [ ] Attribute domains {[F10162715](image.png) size=full}\n - Face corner icon is using a node snapping icon\n - Points probably shouldn't have a line\n - An icon for curve control points would be great\n- [ ] Asset icon (? Could re-use the Asset Browser icon, but rather have a dedicated one)\n- [ ] Asset Browser \"Unassigned\" catalog item\n- [ ] Asset Browser \"All\" catalog tree item (? Could also just be a regular parent item)\n- [ ] Asset Browser \"Open Blend File\" button\n\n- [x] Blender File (`FILE_BLEND` currently uses the Blender logo, which is wrong)\n\n**Sculpt tools:**\n*Postponed for the next release.*\n* - [ ] ~~Mask Filter Tool~~\n* - [ ] ~~Scene Project Brush Tool~~", "Modifiers added in edit mode are undone out of order if you go back to object mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 13)\nWorked: Never (2.8+)\n\nModifiers added in edit mode are undone out of order if you go back to object mode and then start undoing.\n\nAffects both old and new undo system. There's often mentions of edit<->object transitions being problematic but just in passing; I think this is a long standing issue. Just wanted to note it down as I test out the undo systems.\n\nHoping the new undo system can account for this now.\n\n- Default scene\n- Go to edit mode on the default cube\n- Add any modifier (bevel, subdivision, etc.)\n- Add any loop cut 1\n- Add another loop cut 2\n\n- Go to object mode\n- Undo --> Modifier is removed first (out of order)\n- Undo --> Loop cut 2 is removed\n- Undo --> Loop cut 1 is removed\n\n\n" ]

[ "Right Clicking some menus, give blank window without Quick Favorites\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 64)\n\nIf you right click a menu, you will almost always get the option to add it to Quick Favorites. \nHowever, I've found multiple menus that just give an empty window. \nI assume this is a bug and these items (and more) aren't \"barred\" from Quick-Favorites.\n\nI've only looked mostly in the 3D Viewport's header, however I know there's more *(probably here but definitely elsewhere)*.\n - Object\n - Set Origin\n - Relations >> Make Local...\n - Convert To\n - Add\n - Grease Pencil\n - Empty\n - Force Field\n - Collection Instance\n - Select\n - Select All by Type\n - Select Grouped\n - Select Linked\n\n", "Add to Quick Favorites and Assign Shortcut missing at places\nOperating system: Linux\nGraphics card: GTX 1070\n\nBroken: 2.80, master, 2019-10-03\n\nFor Object > Set Origin and Objects > Convert to there is no Add to Quick Favorites menu item so the right click menu is empty. Also since there where even shortcuts in 2.79 for these menus there should really also be an Assign Shortcut option to restore the old shortcut quickly and easily when you notice it is missing.", "Quick Favorites: add support for operator/prop enums (e.g. \"Set origin\")\nOperating system: Windows 10\nGraphics card: Nvidia GTX1080\n\nBroken: 2.80, 16fc62e15f0, blender2.8, 2018-12-12\nWorked: 3d92afca7eb\n\nThe Set origin menu is not possible to put into quic favourites.\n\n3dView -> Object menu -> Right click on \"Set origin...\" -> empty menu.", "Set Origin to quick favorites\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 64)\nWorked: (optional)\n\n\nSet Origin menu doesn't has the option to add to quick favorites\n\n- Go to Objet menu in 3D viewport\n- make rigth click over Set Origin\n- the option to add to quick favorites is lose\n\n", "Gpencil: Edit mode / transform fill tool cannot be quick favorited\nBroken: version: 2.92.0 Alpha\nWorked: n/a, 2.91 same thing\n\nTransform fill tool cannot be quick favourited\n\n1) Grease pencil object: Go to edit mode\n2) Select transform fill tool\n3) Try to add Transform / Rotate / Scale as a quick favorite = Doesn't work\n\n[gp_transform_fill_qfav.mp4](gp_transform_fill_qfav.mp4)", "quick favorites option missing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.83.3\n\n[missing option \"Add To Favorites\" in curve context menu on \"set handle type\" and \"set spline type\" all other are ok ]\n\ngo to edit mode of curve. \nleft click\ngo to set spline type\nleft click and try to add to quick favorites.\n\n\n", "Menus like \"Set Origin\" don't have the option to Add to Quick Favorites\nOperating system: Windows 10\nGraphics card: GTX 10603gb\n\nBroken: 2.80\n\nSelect menus don't have the option to Add to Quick Favorites.\n\nRight click on Set Origin and try to add it to your Quick Favorites.\nBased on the default startup or an attached .blend file (as simple as possible).\n\nHere's all the ones I've found so far looking for them in the general menus. I'm sure there's tons more that I haven't been bothered to find but as I use Blender I'll try and report on it here\nif it ends up being tasked to someone.\n\nRYGwg07\n\nObject: Set Origin, Convert to\nAdd: Grease Pencil, Empty, Force Field, Collection Instance\nSelect: Select All by Type, Select Grouped, Select Linked\n", "Adding \"Convert to\" menu in Quick Menu (by RMB) doesn't work\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI can't add \"Convert to\" menu in Quick Menu by right mouse button.\n\n\n", "missing UI elements.\nwindows 10 64bit \n\nBlender Version, \nDate - 2019-01-07-00;16 Hash - 96f762500ef9 Branch - blender2.7\n\nMissing UI elements for adding \"transform orientations\" and \"pivot point\" into the favourites menu, No option available for this.\n\nMissing UI elements for adding rotational limits to rigid body constraints when constraint is of type \"generic\"... However generic spring has the correct options available. \n\n\n", "Add \"set origin\" and \"convert to\" in Quick favorites menu\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 520M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIt can`t be able to select \"Set origin\" and \"convert to\", inside in \"Object\" menu, into the \"Quick Favorites\" clicking with right clic on it. Also assing a shortcut either. The others menus works.\n\nThere's no need blend file to probe it. Opening the default configuration, clic on \"object\" and right clic on \"set origin\" and \"convert to\".\n\n", "Can't add \"Set Origin\" menu to Quick Favorites\nOperating system: Linux-4.15.0-39-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 690/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.77\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nThere is no \"Add to Quick Favorites\" option in the \"Set Origin\" right-click context menu. \n\nStart Blender, click the Object menu, select \"Set Origin\", right click. There is no \"Add to Quick Favorites\". (But it works fine for other menus, like Transform or Mirror.) \n", "Object > Convert to - Path has no option to add it to the quick favourites\nOperating system: Linux-5.4.0-60-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.91.0\n\nIn Object mode try to add the whole \"convert to\" menu+ subpoints to the quick favourites, the option is not there.\nAll other menus with subpoints have this option.\n\nas described above\n\n" ]

[ "Strange background grid pattern appears on the compositor panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9079\n\nBroken: version: 2.93.5\nWorked: 2.91.2\n\nStrange grid pattern appears on the compositor background when zooming in (when backdrop is on).\n\nThis is what it should looks like:\n\n\nThis is what it actually looks like:\n\n\nAnd this only happens when I zoom in. At a very far-away view the background gradually becomes normal:\n\n\n\n\nThis does not happen on my other devices, so I think it might be a hardware compatibility problem. Also, I had the latest graphic driver installed and the graphic card supports OpenGL 4.6:\n\n\n- Open blender\n- Switch to the compositor workspace,\n- Enable backdrop\n- zoom in.\n\n", "Blender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb (Idk if this is very relevant lol)\n\nBroken: 2.82 BETA, 689a873029b9, master, 2020-01-15 21:07\nWorked: -\n\nBlender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\n\nAdd a stroke, hover it with your mouse and press your \"Set 3D cursor\" hotkey combination (by default Shift RMB).\n\n**Expected result**\nWhen doing just this, but when hovering your cursor/mouse over a mesh object instead, the 3D cursor will be set on the surface of the mesh object right where the cursor/mouse is hovering over that mesh/object. As the grease pencil is rather new, Im guessing making this react with the grease pencil strokes were just something that was forgotten when implementing it.", "Grease Pencil Lighting - World light not influencing GP object correctly\nOperating system: Manjaro Linux (Kernel 5.4.18-1-MANJARO)\nGraphics card: Intel Haswell-ULT\n\nBroken: 2.83 (sub 2), c650ea9a13f9, greasepencil-refactor, 2020-02-11, 18:37\nWorked: unknown\n\nGrease Pencil Object (Strokes) unaffected by Background Light \n\nOpen either the General or the 2D Animation default file. Add a grease pencil monkey and a basic mesh, set some background color and change the strength settings once to 0 and once to 1.\nThe shading of the Suzanne object stays the same. When adding a spotlight and aiming it towards Suzanne it gets lit properly.\nThe [demo video ](GP_lighting.mp4) of the grease pencil lighting shows correct black objects where no scene light is hitting them.\n\n", "Grease Pencil Color Management inconsistencies\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nBlender CM for GP is inconsistent between viewport and render. Viewport is not affected by Filmic, but render is.\n\nIn a new file, add a GP Suzanne. Change viewport to RENDERED. Render and compare colors/contrast: they are different.\nChange CM from Filmic to Standard. Render and compare again: they match.\n\n\n\n\n", "Grease Pencil Vibrating Contours\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.4\n\nHi, i i have bug on Grease Pencil contours. When i move camera in animation contours vibrate, changing size. This is not problem with my PC, because i tried it on another and problem is the same. I tried Anit-Aliasing, change render engine (Cyles and Evee), the same bug is in viewport and in render animation. I'm attach the video of this bug. This bug occurs just with camera or object move. \n\n1. Create Grease Pencil object.\n2. Move camera to \"zoom\" it.\n\n[vibrating contours.mp4](vibrating_contours.mp4)\n\n[vibrating contours.blend](vibrating_contours.blend)\n", "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.", "Incorrect occlusion between grease pencil objects\nOperating system: macOS-12.2.1-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 655 Intel Inc. 4.1 INTEL-18.4.6\n\nBroken: version: 3.3.0\n\nIncorrect occlusion occurs with this setup\n\nThe two Suzannes are clearly behind the strip, but one of them appears to be in front of the strip in camera\nIf I rotate the camera a little, both of them are in front\n\nI've tried switching the stroke depth order to 3D Location, it doesn't fix it either\n\nSee the attached file\n[gp_wrong_depth.blend](gp_wrong_depth.blend)\n\n", "Vertex Paint ➔ Paint menu ➔ Smooth Vertex Colors could be improved\nOperating system: Windows 10 Pro 64-bit\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nTested: Blender 2.81 Alpha, September 18, 14:29:45 - b962aca8003d\nWorked: never\n\nVertex Paint ➔ Paint menu ➔ Smooth Vertex Colors tool does not smooth other than direct loop neighbors.\n\n1. Divide the default cube a few times (apply if subdivision is done with modifier).\n2. Enter Vertex Paint mode.\n3. Paint an area with black.\n4. Apply Paint menu ➔ Smooth Vertex Colors.\n5. The vertex paint is not smoothed other than direct loop neighbors.\n\n\nHere is some clarification as the descriptions above are not very clear (I work with vertex colors very regularly and still came out confused by reading this post).\n\n- The Smooth Vertex Colors command will have visible results *if* it is run on vertex colors that have been applied per-face (by first selecting the desired faces in Edit mode, and then filling them with colors in Vertex color mode with the face filter enabled). Think of these as \"harsh\" vertex colors. When such vcols exist, then the smooth operation will indeed smooth out the vcol data so that the harsh separation between painted faces will be smoothed out, blending it with the surrounding faces.\n- But if the command is run on vcol data that has been painted on using the paint brush or on vcol generated by the \"dirty vertex colors\" command then nothing will happen as the vcols will already be point-based.\n\nTherefore there is no bug here, just some very confusing naming of the command and a lack of clarity when the command is run but nothing happens. For any user working with painted-on vertex colors, it will indeed seem like nothing is happening at all since one would expect some sort of global smoothing to be applied.\n\nPart of the confusion is also coming from the fact that this command sits just below \"Dirty Vertex Colors\" in the menu, which generates smooth, per-vertex vcol data. Meaning that for a user exploring vcol mode by trying one feature after the next, \"smooth vertex colors\" will almost always feel like it is doing nothing at all (unless the user first applied some vcol using face masking, which is extremely unlikely).\n\nIf anything the tooltip and/or the menu entry could be changed for clarity :\n\n- The menu item name could be renamed from \"Smooth vertex colors\" to \"Smooth harsh per-face vertex colors\"\n- The tooltip could be changed from \"Smooth colors across vertices\" to \"Smooth colors across vertices. Only operates on harsh, per-face vertex colors\".\n\nAnd then of course it would be great to have a new feature altogether to blur vcols globally, similarly to what the blur brush does.", "MacOS, Metal: Banding artefacts in viewport when using curves in color management\nOperating system: macOS-13.2.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro Vega 64 1.2\nScreen: iMac 27 inch Retina 30bit\n\nBroken: version: 3.5.0\nWorked: same version with openGL viewport API\n\nIn the \"wanderer\" demo file you get white lines in the bright parts of the scene. They are visible in rendered view as well as in the final render (but only inside blender). \nWhen \"Use Curves\" in \"Color Management\" is turned off, they dissapear. \nWhen switching back to openGL api everything looks ok.\n\nOpen the demo file wanderer wanderer.blend\n\n", "Cycles semi transparent materials produce very noisy mist pass\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\n\n\nWhen mix the transparent shader with any other shader using a factor higher than 0 but lower than 1, the mist pass becomes extremely noisy\n\nOpen this file and hit F12 to render a noisy mist pass, even when increase the samples to 1024, the mist pass is still noisy.\n[mist test.blend](mist_test.blend)\n\n\n", "GPencil: Materials' preview thumbnails cause heavy lag when updating\nOperating system: Windows 10\nGraphics card: RTX 3070 FE\n\nBroken: 3.2.1 RC\nWorked: n/a\n\n\n\nAny action that requires the refreshing of your Grease Pencil materials' thumbnails (isolate/hide materials, etc.) causes major lag until the thumbnails are finished refreshing. The more materials your GP object has, the longer the lag. Sometimes the lag is so bad, that it makes the sound buffer skip while the thumbnails refresh.\n\n\n**Video Explanation**\nwatch?v=5KAWsJkIeRY\n\n\n**Steps to Reproduce**\nCreate a GP object and add 10-20 unique materials\nClick one of the \"Isolate Material\" buttons, and start drawing/moving strokes. You will notice extreme lag until all of the little circle thumbnails are finished updating. \n\nTest File:\n[#99361.blend](T99361.blend)", "Texture paint in viewport is not using the color space of the image.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nIf you paint a noncolor texture like a normal map, painting it directly in the 2D image correcly uses the non-color space, but painting in the viewport doesn't.\n\n\n- With any non-color texture, try to paint both in viewport and in the 2D image\n[2022-02-15 10-34-07.mp4](2022-02-15_10-34-07.mp4)\n\nAditional note: This seems to happens when you sample from the 2D image. By contrast, if you sample the color from the 3D view, you can correctly paint on it, BUT in the 2D viewer the color becomes brighter.", "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)", "Unable to see cursor point properly when R/S/G keys are used\nOperating system: macOS-12.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.2.0\n\nAccessibility issue: Unable to see cursor point properly when R or S or G keys are used\nPlease fix copy code from 3D Viewer when push the R or S or G appear color there then paste code into Timeline to become color can see without full black.\n\n- Cursor point can not be seen properly when R/S/G keys are used in timeline (in particular theme as shown in video)\n\n\n\nSee youtube Fh6OYqW2AfU\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 green display bug (related to multisampling)\nOperating system: Mac OSX Catalina\nGraphics card: Radeon Pro 560X 4 GB\n\nBroken: Latest Official 2.80 and 2.82 Alpha\n\n\nMy Grease pencil strokes are all displaying with this weird pattern covering them. I can barely see the actual color of the stroke because of this, though the color is present behind the lines.\n\nIt's the same problem, whether in Eevee or Cycles. Regardless of preview mode, or X-Ray on or off, or Outlines on or Off or anything else I can find to toggle. My old files that didn't do this are also now displaying this way and doing a Render actually outputs strokes looking like this too. \n\nAm I missing a toggle somewhere or is this a recent bug? Thank you!\n\n[grease pencil render bug.mov](grease_pencil_render_bug.mov)\n\n1) Run Blender on Mac OSX running Catalina with a problem Radeon card (such as 560X)\n2) Have a Grease Pencil object in your .blend file.\n\nBy Dalai Felinto's request I've attached this file:\n[grease.blend](grease.blend)\nI'm confident it will display cleanly on most setups except for the cases that are reporting. Thanks!" ]

[ "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", "Add support for more gettext flags to UI translation tools\nAs reported in 101830#issuecomment-1023470 , Weblate `C-format` is not very smart, and generates a lot of false-positives.\n\nThe solution is likely to not enforce these checks over the whole messages, but selectively enable them for messages that actually need it (e.g. (almost?) all RNA-extracted message will not have such formatting).\n\nThis will require updates in the python modules and add-on code generating these translation files.\n\n----------------\n\nParent task: infrastructure/blender-projects-platform#65", "ColorRamp, UI problem to hold the Color Stop\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 655 Intel Inc. 4.1 INTEL-20.2.48\n\nBroken: version: 3.4.1\n\nIn the ColorRamp node, it is difficult to grab a Color Stop by its selection rectangle.\n\nAdd a ColorRamp node in the Shader Editor or in Geometry Node and select a Color Stop rectangle to make it move.\nOnly a small part of the rectangle (red frame on my screenshot) can be grabbed when it should be the whole rectangle (green frame on my screenshot).\nIt is disturbing to regularly move the node by mistake instead of moving the colored rectangle.\n\nI tested several versions with the same result, today's master, 3.3, 2.83, 2.8 and 2.79.\n\n[ColorRamp_UI_problem.blend](ColorRamp_UI_problem.blend)\n\n\n- - - \n\nI can see 2 other problems in the ColorRamp UI, please tell me if I need to create a second report, but maybe it's more convenient to come only once in this area with a report rather than twice.\nThere is a line of transparent (or unfilled) pixels and 2 pixels that overflow to the left of the triangle, see my screenshot with the details in red.\n\n\nNOTE: there is a separate report for this, see #111017\n\nOlivier\n<3 Blender", "Fix preview flickering when using \"Adjust Last Operation\"\nTweaking properties in the \"Adjust Last Operation\" panel removes all previews for a moment, causing quite drastic and annoying flickering.", "Color of header-bar of Graph and Drivers Editors is darker than that of the other editors.\nOperating system: Linux-4.19.69-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\n\n\nColor of header-bar of Graph and Drivers Editors is darker than that of the other editors. This looks a bit inconsistent.\nI feel that the color should be lighter as in Timeline and other editors.\nI'm using the default Blender Dark theme, and haven't changed any of the theme settings.\n\n\n[Based on the default startup .blend file]\n\n{[F7723159](Graph_Editor_header_color_darker.png), size=full}\n\nThanks!", "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", "Default Value for Viewport Display Color's Alpha Wrong.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.92.0 Alpha\nAlso tested on 2.83.8 and same problem.\nWorked: It do not think this has ever worked\n\nWhen reverting to the Default Value for Viewport Display Color the alpha gets down to 0.8 making the object semi transparent.\n\nOpen up a new scene.\nSelect the cube.\nGo to the materials tab.\nScroll down to \"Viewport Display\"\nRight Click on \"Color\"\n\"Reset to Default Value\"\nResult: RGB values go back to the default, but Alpha goes to 0.8\n\n\nThank you so much !", "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.", "Erratic behaviour of materials/material slots for text objects\nOperating system: Linux-5.19.0-45-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.6.0\n\nMaterial assignment for text objects doesn't behave as expected. Removing an unused material slot will cause changes to the materials used by the object. The same happens if you rearrange the material slots.\n\n1. Add a new text object. Leave the default string \"Text\".\n2. Add 3 new material slots with different materials to the object. Use different viewport display colors to be able to see changes.\n(You will now have Material.001, Material.002 and Material.003)\n3. In edit mode, select the last two letters and assign Material.002.\n(You should now have \"Te\" using Material.001 and \"xt\" using Material.002)\n4. In object mode, remove the last material slot containing Material.003.\n(This material was not assigned to any character, and removing it should not cause any change.)\n5. All 4 letters are now using Material.001. \"xt\" should still be using Material.002.\n\nAlternatively, execute step 1-3 above and then.\n4. Move the last material slot up to the first place.\n(This should not cause any change. Normally in blender, the materials used by the geometry will not change if you rearrange the material slots.)\n5. You will now have \"Te\" using Material.004 and \"xt\" using Material.002. \"Te\" should still be using Material.001.\n\nI have attached a blend file where you just need to remove the last (unused) material slot to see the problem, or move the last material slot up to first position.\n\n", "Cycles shading glitch\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.4.1\nWorked: ?\n\nCycles shows incorrect shading, also different from Eevee. (The file is very simplified just to showcase the problem)\nI'm thinking it is a variation of T99933 bug but not sure so tell if that's the case\n\n[bug.blend](bug.blend)\n1) Open the file, switch to rendered view. Normals should look like this\n\n2) In the material disconnect the alpha socket, now it should look different.\n\nIs alpha supposed to affect normals at all?\n3) Repeat the same in Eevee, results look consistent", "[WIP] Design: Painting Color Management\nThis design are based on the next principles:\n\n* When mixing colors, do it always in the linear scene reference space. For Blender that is linear REC709.\n* Include the color space when storing colors for color picker and don't convert it the color channels.\n\n**Issues**\n\nCurrent issues we try to solve:\n\n* #68242 (Color space seems wrong while painting in image editor.)\n* Color picker stores in sRGB or linear REC709. the storage is defined by the RNA (COLOR, COLOR_GAMMA). Since blender 2.80 the default color picker is set to HSV, what has some usability issues (HSV has multiple values that represents the same black in sRGB and linear REC709). User notice this when they set `Value` to 0, that the next time they open the color picker that the `HUE` and `Saturation` are also set to 0. \n\n**Scoping**\n\nThe solution is focused on Sculpt/Paint brushes, but will be reusable in other areas. The solution is designed on single colors. `ImBuf` should be used when working with buffers. Changes to `ImBuf` are not in scope.\n\n**Proposal**\n\nProposal is to implement a framework for color picking and mixing colors. To test the framework we include the first implementation in the Paint and Sculpt Brushes. The idea of this approach is to be more explicit when colors are being used.\n\n__DNA__\n\nIn `DNA_color_types.h` add a struct that can store a color and relevant information of the color.\n\n```\ntypedef struct Color_RUNTIME_Color {\n float color_straight_alpha[4];\n float color_premult_alpha[4];\n} Color_RUNTIME_Color;\n\ntypedef struct Color_RUNTIME {\n /* flag contains the validity of the other fields */\n int flag;\n Color_RUNTIME_Color linear_scene;\n Color_RUNTIME_Color display;\n\n ...\n\n} Color_RUNTIME;\n\ntypedef struct Color3 {\n float components[3];\n float alpha;\n ColorManagedColorspaceSettings color_space;\n Color_RUNTIME runtime;\n} Color3;\n```\n\n`Color3.alpha` is always stored as straight alpha.\nThe runtime caches common conversions of the color in different OpenColorIO roles and alpha association. The `Color3.runtime` field will be flagged to be invalid when the scene color management is changed or a different scene is loaded. The runtime is also updated when the color management roles in the scene are changed, a another scene is loaded.\n\nIn `DNA_brush_types.h` deprecate the `rgb` and `alpha` and add a new field `Color3 color;`.\n\n__BKE__\n\nAdd functions in `BKE_colortools.h` for getting the values for a color in a specific OCIO Role, invalidate all `runtime` fields in loaded data, invalidate one `runtime` field.\n\n__UI__\n\nUpdate the color picker template to support this data structure. This also means that we don't do the pixel read to find the selected color, but interpret the screen coordinate on the wheel to find our what color has been picked.\n\n__Painting/Brushes__\n\nWhen doing this change a lot of compile errors needs to be fixed. This gives us the opportunity to migrate them to the new implementation and make sure we tackle these cases. Textures still needs special attention.\n\n\n__OCIO__\n\nThe color configuration needs to be adjusted with color spaces for the color picker role.\n ", "Text strip duplication with madeup driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken:\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. Then the clone had a driver on 'Location X' set, that the original has not. If You delete that driver, blender crasches (see #91912)\n\n\n- Load attached file\n- Duplicate the Text strip with <Shift><D>\nThe new Text strip now has a driver on Location X\n\n[driver_duplicate_bug.blend](driver_duplicate_bug.blend)", "Movie clip editor theme color unclear for 'Path Before/After'\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.92.0 Beta\n\nThere are 2 repeated fields in the theme as \"Path Before\" and \"Path After\" for a total of 4 theme colors the user doesn't know which color refers to what path or color.\n\nOne set of Before / After is affecting the drawing of the path around a marker (you can even see that in your screenshot)\nThe other set of Before / After is affecting keyframes on the marker (e.g. if search area is keyframed) and this is working fine.\n\nTODO is just to make the UI texts a bit more descriptive\n\n\n\n", "The interface font of the Simplified Chinese version is displayed incorrectly in Blender 3.4\nOperating system: Windows11 Home 22H2\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: 3.4.0 Alpha, f9113b7eb6ee, master, 2022-10-29\nWorked: 3.3.1\n\nAs shown in the picture, in 3.4, some of the interface text does not match the Chinese writing, which seems to be closer to Japanese ? In contrast, version 3.3 and previous versions are roughly correct, but still have some errors. When the font is switched to Noto Sans S Chinese Regular, the display result is completely correct.\n\n\nIn Text Editor:\n\n[example.blend](example.blend)\n[NotoSansHans-Regular.otf](NotoSansHans-Regular.otf)\n\nThanks!\n(I can‘t speak English，the above is machine translated)\n", "Spreadout enum in pie menu gives strange result\nWin7x64GTX660m\n\nBroken: 2.73\nWorked: (optional)\n\nIf \"select similar\" operator is launched from a pie, items are arranged in a weird fashion (happens only in vertex and edge mode), overlapping one another and showing index numbers such as 167.\n\nFrom file, just click run in text editor (replaced example operator in text editor's pie menu template with *pie.operator_enum(\"mesh.select_similar\", \"type\")*).\n\n[overlappingPies.blend](overlappingPies.blend)" ]

[ "ui misalignment of green channel in material color mixer.\n\nui misalignment of green channel in material color mixer.\n\n - Operating System, Graphics card ---\n\ncpu: intel core i3 2350 2.3 ghz\nram: 4 gb\ngfx: intel hd graphics 3000\nos: windows 7 home premium sp 1\n\n - Blender version with error, and version that worked ---\n\nerror found in: 2038eb1 win64 official.\nwas working in: a84bcea win64 official.\n\n - Short description of error ---\n\nui misalignment of green channel in material color mixer.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\n[apparently happens with all blend files including new startup.blend's and factory defaults]\n\nwhen clicking on any diffuse, specular color mixer, the **g:** is to the left of the other two color channels, and it's value is offset to the right. looks odd, so i assume it's a bug." ]

[ "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", "VSE: Meta strip speed changes if the content length changes\nOperating system: Linux-6.3.5-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 525.116.04\n\nBroken: version: 4.0.0 Alpha\n\nBy default the speed handle for strips is placed so that the speed = 100%.\nUnfortunately with Meta strips the content length can change by making edits inside.\nIn that case the speed will change because the speed handle will not adjust to the new length.\n\nA simple solution for now could at least be that the speed handle is automatically adjusted back to the original speed **if** the there is only one segment.\nI can see how this issue becomes more complicated if there are multiple segments with retiming already in use.\n\n- Open a new Video Editing file\n- Add a few strips and group them with `Ctrl G`\n- Switch to the Retime tool in the toolbar and inspect the percentage on the strip\n- Enter the meta strip with `Tab` and add a couple more strips to the end\n- Exit the meta strip with `Tab` and inspect the speed again (now much higher)\n\n", "Blender 2.8 Defaults\nThis is a list of things we should change about Blender's default settings and behaviour.\n\nThe list will grow and change over time.\n\n\nCommits:\n\n- 4d5b7696cb - prefs\n- bcf6cc1f6b - startup\n- Update: default preferences are now maintained in: `./release/datafiles/userdef/userdef_default.c`\n\n## Preferences\n\n- - [x] Python tooltips OFF\n- - [x] Auto Perspective ON ***\n- - [x] Navigation Manipulator ON ***\n- - [x] Region Overlap ON (Could be removed completely, now that it's optimized) ***\n - To make transparent toolbars work better, we would like to:\n - Make the toolbar region height be limited to the contents.\n - Make the toolbar region a separate theme\n\n## Default Settings\n\n- - [x] Default Shader should be set to Principled BSDF\n- - [x] Default Lamp increased strength (10x stronger)\n- - [ ] Playback set to AV Sync (reverted, breaks physics caching)\n- - [x] 3D View Lens = 50mm\n- - [x] Camera film size = 36x24mm Full Frame\n- - [x] Camera Focal Length = 50mm\n- - [x] Render Size Percentage = 100%\n- - [x] Render Display = New Window\n- - [x] Scene Units = Metric\n- - [x] Color Management View = Filmic\n- - [x] Workbench Object Overlap = ON\n- - [x] Absolute Shape Keys Interpolation = Linear\n- - [x] Curve Fill Mode = Full\n\n## Default Renderer\n\n- - [x] Viewport = Workbench + Studio Lighting\n\n\n## Layout\n- - [x] Headers on top for all editors, except the Timeline at the bottom\n- - [x] Default Properties tab = Object Properties\n\n## New Objects\n- - [x] Generate UV's = ON\n\n## Default Theme\n\n- - [x] Flat\n- - [x] Dark UI Chrome\n- - [ ] Universal widget radius\n- - [x] Transparent header in 3D View\n- - [x] Transparent toolbar area in 3D View\n\n## Tools\nVertex Slide:\n- - [x] Correct UV's = ON\n\nExtrude Along Normals:\n- - [x] Even Thickness = ON\n\nLaplacian Smooth:\n- - [x] Lambda Factor = 1.000\n\n## UV/Image Editor\n- - [x] Normalized Coordinates\n\n## Weight Painting\n- - [ ] Auto-Normalize = ON\n\n\n## Cycles\n- - [x] Dithering = 1\n- - [x] Image Sequence Auto Refresh = ON\n\n\n## New Objects\n- - [ ] SubdivisionSurfaces = ON (via OpenSubdiv)\n- - [ ] Shade Smooth = ON (Wait till we have OpenSubdiv)\n\n## Preferences\n - - [ ] Compute Devices ON (Postpone until we can detect crappy GPU's)\n - - [x] Release Confirms Transform\n\n## Text Editor\n - - [x] Line Numbers ON\n\n## Addons\n - - [ ] All exporters should be set to Only Selected by default", "Add \"Link (Library Override)\" option when dragging assets into the scene\nAs a user, I want to be able to drag an object asset into a scene and have it have the following properties:\n\n1. The data block is not copied into the new scene, it should be linked.\n2. The underlying *data block* cannot be edited (i.e., you cannot go into edit mode on a mesh object)\n3. The new object should be able to be modified (i.e., translating, scaling, rotating etc.)\n\nThis is not possible with [the options provided](asset_browser.html#using-assets) at the moment.\n\nI propose that a new option be added, called **Link (Library Override)**.\n\nThis would essentially be the same as using \"Link\", followed by calling the \"Make Library Override\" operator on the linked object.", "Animation: Exiting NLA tweak mode on empty action corrupts entire NLA track\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.0, 3.5.0\nWorked: Unknown\n\n\nWhen tweaking a strip on the NLA, if the user deletes all the keyframes of the action being tweaked, when the user exits tweak mode, all other NLA strips on that track will be moved in an unexpected and undesirable way.\n\n[tweakbug.mp4](tweakbug.mp4)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open the attached .blend file\n2. Delete the keyframes on the track being tweaked.\n3. Exit tweak mode by pressing Tab.\n4. Observe that the NLA strips have been moved.\n\n[tweakbug.blend](tweakbug.blend)", "NLA: Support for Merge Strips\n**Preface:**\nI know this isn't the place for feature requests. However I plan on implementing this myself soon. This is more of a heads up and acts a way to get feedback before or while I'm working on it. Maybe I'm overlooking something or maybe the idea can be developed further. People can discuss problems and improvements here instead of within the patch comments itself. That way the important discussion can remain here for easier reference.\n\nEdit: Diff: [D8867: Feature: NLA Merge Strips](D8867)\n\n**Problem:**\nFor the animation layer workflow, the only way to combine strips into a single strip is to use the Bake Operator. However, it will always bake all active NLA strips to a single full replace strip. Effectively, this is a \"Merge All\" operator. There is no way to merge a selected set of strips. \n", "NLA: Active Strip State lost when dragging Strip between tracks\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: Never Worked\n\nClicking on a strip and dragging or G dragging the Strip on the timeline on the same Track and then hitting TAB to enter tweak mode is working, but if I do the same thing but drag it to another TRACK then hit TAB I get an error\n\nOpen my example Blend file and select the \"Click and Drag Me to the Drag Strip Here track\" STRIP and drag it to \"Click and Drag Me to the Drag Strip Here track\" then hit the TAB key to enter tweak mode, you should see an error as shown in the image. \n\"No active strip(s) to enter tweak mode on\n\"\n\n\n\n", "Library-Override Not able to edit \"Strip time Keyframe\" value in sidebar panel in graph-editor\nOperating system: Windows 10 Pro v.21H2\nGraphics card: NVIDIA GeForce GTX 1060 3GB\n\nBroken: Version:3.3.3, hash:8d94aeb604fa, branch: master, date:2023-01-17\n\nI think is a similar case to this \" blender/blender#81965 \", but more specifically for animated striptime. The striptime key-frame in Graph-Editor is not editable in sidebar and values are grayed out.\n\n\n1. link a collection/character/object\n2. object > relation > make library override\n3. animate\n4. stash action to create NLA track\n5. animate strip time\n6. try to change a keyframe's value in graph-editor's sidebar Fcruve > active keyframe.\nopen the StripTime_KeyLocked.blend file, try to change the selected key's value in graph editor's sidebar\n\n\n\n", "Cursor size for \"Use Cursor for Depth\" in Sculpt doesn't reset properly on undo\nOperating system: MacOS 11.6\nGraphics card: Radeon RX 580 8 GB\n\nBroken: 2.93.4 (2.93.4 2021-09-01)\nBroken: 2.93.5 (2.93.5 2021-10-05)\nBroken: 3.0.0 (3.0.0 2021-10-05)\nWorked: don't know\n\n\nCursor size for \"Use Cursor for Depth\" (Sculpt -> Box/Lasso Trim -> Trim Mode: Join) doesn't reset properly on undo.\n\nBased on the default startup\n\n- File -> New -> Sculpting\n- Select Box Trim (or Lasso Trim)\n- In tool options, select Trim Mode: Join \n- In tool options, select Use Cursor for Depth\n\n- Use tool on the outside of the object (Note that the geometry created has a volume)\n- Undo (if you used the tool more times, repeat the undo each time).\n- Use the tool again. \n\nExpected result:\nTool works normally after all undo.\n\nActual result:\nAfter undoing all tool uses, the tool disregards the cursor size and the next shape created is flat/collapsed. \n\nAdditional notes:\nIt only happens when the file starts in Sculpt mode (hence the New -> Sculpting). If started in Object mode, and then switched to Sculpt, it is not occurring. \nAfter switching tools (even without actually using another tool), it seems to work correctly. \nAlso if switched from Sculpt to Object mode and back, it's working properly. Unless you undo from before switching to the Object mode, and undo all the tool uses, it happens again.", "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.", "NLA animated time strip with a driver displays a wrong frame when going back in time\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.93.0 Alpha\n+ version: 2.92.0\nWorked: never\n\nWhen using a driver on the \"animated time strip\" property of an NLA track, the animation is offseted when going backward in time, with the arrow keys. This makes the animation review process very hard.\n\n(see video attached)\n\n[#86107.blend](T86107.blend)\n\nanimate the default cube (example : revolution on Z axis, from frame 1 to 250\ncreate an empty, add a custom property, set the max to 250\nkeyframe the custom property as : frame 1 value 1.00 ; frame 250 value 250.00.\ntweak the animation curve of the custom property to get a nice S shape\ncopy the custom property as a new driver\ngo to the NLA, push down the cube action, go to it's strip option and check \"animated time strips\"\npaste the driver on the \"animated time strips\" value\nnow if you go forward and backward with the arrowkeys, you'll see that the animation is doing some weird frame offset\n\n\n[bugreport_wrongframe.mp4](bugreport_wrongframe.mp4)\n", "VSE: Animation operators missing cache invalidation\nOperating system: Linux Mint 19.1\nGraphics card: GTX 980\n\nBroken: blender-3.1.0-alpha+master.c34ea3323a3a-linux.x86_64\n\nRemove created action from NLA editor, this will still animate VSE elements\nSome weird VSE action cache?\n\n- Add any image to VSE strip\n- Set Rotation=0 at first frame and Rotation=220 for some another frame. It's rotating now, right?\n- Go to NLA tab -> push down Scene Action and remove it. Thus, we don't have any actions in our project but the image is still rotating. Why?\nAfter rebooting blender app the magick will gone. Is this a bug?\n\nThis has quite broad reach as all of these (if not more) dont invalidate the cache:\n- clearing keyframes\n- deleting actions\n- removing drivers\n- removing dopsheet channels\n- removing graph editor channels\n- removing nla tracks\n- removing nla strips\n- removing fcurve modifiers\n\n\n", "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", "Disappearing buttons in pie menu, depending on button text length and use of align=True\nOperating system: Linux-4.15.0-144-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: - \n\nI have a pie menu, with a section like this:\n\n\n```\n box = pie.split()\n column = box.column(align=False)\n \n row = column.row(align=True)\n row.operator(\"transform.translate\", text=\"(B) Get Backup\")\n row.operator(\"transform.translate\", text=\"(V) Match\")\n\n row = column.row(align=True)\n row.operator(\"transform.translate\", text=\"(D) Project\")\n row.operator(\"transform.translate\", text=\"Unwrap\")\n```\n\nChanging the column's align argument to True, leads to the Unwrap button disappearing.\nIt can be brought back by changing the text length of any of the buttons. For instance, you can shorten or lengthen the Unwrap button's text. Same for the other buttons, changing the text length will usually bring the Unwrap button back. \n\nSee [video demo ](watch?v=v3VkH44p7xk): \n\n[disappearing_button.blend](disappearing_button.blend).\n\nI've checked back until 2.77 and it's present in all versions since, likely before that too.\n\n* open the blend, run the script in the text editor\n* the pie pops up and all 4 buttons are present\n* set the column's align arg to True\n* the Unwrap button disappears\n* change the text length of any of the 4 buttons to make the button re-appear\n\n", "VSE: Ensure all operators in the Strip menu are working on the selected and not only on active strip (+unselected) \nAs it is confusing and inconsistent to have functions in the Strip menu which only works on properties of the active strip even if it is unselected, this design list is for ensuring all functions in the strip menu to work on selection. \n\n- - [x] Swap Strip: #91191 Fix: [D12441](D12441)\n- - [x] Effect menu. Fix: [D12451](D12451)\n- - [x] Movie(Set Render Size + Deinterlace) and Image(Set Render Size + Separate Images) menu entries should be moved into the source sidebar with +alt for selection. Fix: [D12464](D12464)\n- - [ ] Add Modifier in the menu needs to work on selection and is missing +alt for selected, when executed in the sidebar.\n- - [ ] Inputs menu: Swap data should go into the swap menu and the rest into Strip Source sidebar with +alt for selected. Bug report: #91350\n- - [ ] Toggle Meta and UnMeta should go into the strip sidebar, as they are only working on the active strip. Old patch: #74130\n(A checked checkbox means a fix has been submitted, but not necessarily been committed)\n\n" ]

[ "When a strip is cut and edited in nla editor, the strip returns to its original length without the cut. blender 2.92 alpha\nOperating system: WIN 10 64\nGraphics card: GTX 1070 TI\nBroken: 2.92.0 ALPHA (07/01/21)\nWorked: \n\n\nDescription,\nPlease refer to the video attached\n\n\n1. link and make library override of a character with an armature\n2. make an action and push down in the nla editor\n3. cut the action to a desired length.\n4. press tab on the cut strip to edit action\n5. press tab again to exit editing the action.\n6. problem. the strip returns to its original length without the cut.\nthanks\n\nVIDEO: [CUT STRIP OVERIDE.mp4](CUT_STRIP_OVERIDE.mp4)\n\n", "When a strip is cut and edited in nla editor for a library override character, the strip returns to its original length without the cut. blender 2.92 alpha\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\nDescription,\nPlease refer to the video attached\n\n\n1. link and make library override of a character with an armature\n2. make an action and push down in the nla editor\n3. cut the action to a desired length.\n4. press tab on the cut strip to edit action\n5. press tab again to exit editing the action.\n6. problem. the strip returns to its original length without the cut.\nthanks\n\nVIDEO: [CUT STRIP OVERIDE.mp4](CUT_STRIP_OVERIDE.mp4)\n\n", "When editing NLA strip that's cut, it reverts to orignal size\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\n\nWhen having an action. adding it as an NLA strip. And splitting it up (y). When you then edit it (tab) and unedit, it'll revert to it's original length.\nAdditionally having split an action up, you can't rename it, so you'll be left with an action name like Animation_forward**.002**\n\nAnimate the cube a bit for 20 frames, have plenty of keyframes.\nIn the action editor add it as an nlm strip.\nIn nlm editor, split it up on the middle. Remove the surrounding strips, so you're left with a strip starting later and ending earlier than the original.\nEdit it by pressing tab.\nleave edit mode by pressing tab again.\nNow it's back to it's original size\n\n[example](OBEyrPx.gif)\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", "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)", "Regression: Wrong colors editing list items in dark theme\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\nWorked: (3.6)\n\n\n It's same problem that I mentioned here:\n\n111942\n\nbut in dark theme. highlighting(selecting) text to rename it in dark theme is wrong color. I upload an image and compare it to 3.6 take a look at it.\nthe problem is that highlighting text is just same as selecting item and you will not notice that you are renaming it.\n\n", "Smear tool painting vertex colors corrupts color info: part 2\nvertex colors get corrupted under certain blend mode combinations. 3.0.1 master.\n\nusing the smear tool over blue colors introduce green, magenta, yellow, gray and orange not present inside the blue ranges.\n\npainting with blue results in grays instead. \n\ni had this problem in 3.2 alpha using sculpt vertex colors, but when i got back to a project in 3.0.1 it happened with vanilla vertex colors tool. \n\nincluded a file this time\n\n[vertex colors bug.blend](vertex_colors_bug.blend)\n\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1\nWorked: (newest version of Blender that worked as expected) 2.93\n\nSmear tool painting vertex colors corrupts color info\n\nuse paint brush with blue color. paints gray instead.\nuse smear brush. it should smear blues and not oranges and greens.\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", "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)", "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", "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)", "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", "Intersect Boolean does not work properly when mesh has a degenerate face\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001\n\nBroken: version: 2.91 - 3.0.0\nWorked: n/a\n\nThe `Intersect Boolean` Exact mode does not work correctly when the mesh has at least one degenerate face.\nIn this case, it was tested on a mesh with a triangle whose vertices are collinear\n\n- Open attached file - (The edited mesh has a degenerate triangle)\n- Go to `Face` -> `Intersect (Boolean)` - (The operation will not work because of that triangle)\n\n- Undo the operation\n- Move the triangle vertex a little so that the face is no longer degenerate.\n- Reselect that loose geometry ({key L})\n- Redo Boolean operation (now it works)\n[intersect_w_degenerated_tri.blend](intersect_w_degenerated_tri.blend)\n\n", "Geometry Node: Mesh Boolean & Attributes domain\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.40\n\nBroken: version: 3.4.0 Alpha\n\n\nIncorrect save behavior of attributes during Mesh Boolean node if they have different domain or points.\nVideo example based on the example file:\n|  |  |\n| -- | -- |\n[2022-10-10 13-54-06.mp4](2022-10-10_13-54-06.mp4)\n\n\n1. Create 2 meshes and attach a named color attribute of a different color to them.\n2. Perform a cut operation between them using the Mesh Boolean node.\n3. Display the color of the attribute in the preview or otherwise.\n\n[test boolean.blend](test_boolean.blend)", "Eevee: color ramp with 1 color produces 2 colors with various input factor\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\nUnexpected results when deleting right color stop from the Color ramp node. Happens with EEVEE render engine, Cycles produces correct flat color.\n\n\n**Step to Reproduce**\n- Open .blend file\n- Switch to render mode\n- Switch to EEVEE render engine\n- Delete color stop of the right side from the color ramp\n- Compare the output with Cycles render engine\n\n[2021-07-26_04-30-47.mp4](2021-07-26_04-30-47.mp4)\n\nTest File:\n[#90149.blend](T90149.blend)", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "EXCEPTION_ACCESS_VIOLATION error when trying to change object viewport color with the viewport compositing enabled in depsgraph_update_post\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.5.0\nWorked: 3.4\n\nThis error occurs only if the viewport compositor is enabled - rendered mode of the viewport and Compositor = Always.\nWhen trying to change the viewport color of the object by script on depsgraph update event, this error occurs.\n\nThe short script example:\n```\nimport bpy\n\ndef on_depsgraph_update_post(scene, depsgraph):\n if depsgraph.id_type_updated('SCENE'):\n for obj in depsgraph.updates:\n if isinstance(obj.id, bpy.types.Object):\n print('change object color')\n bpy.data.objects[obj.id.name].color = (1, 0, 0, 0)\n\nbpy.app.handlers.depsgraph_update_post.append(\n on_depsgraph_update_post\n)\n```\nAfter executing this script in the Text editor, switching to the \"Rendered\" mode of the 3D Viewport and enabling viewport compositing - when adding or copying the object - Blender throws an error.\n\nThis occurs only if the viewport compositing is enabled, if it is not used - code works as expected.\n\nError occurs on 3.5 and 3.6 alpha.\n\n1. I attached .blend file with the example\n2. Open .blend file\n3. Switch the viewport to the \"Rendered\" mode (z - Rendered)\n4. Execute script in the Text editor\n5. Try to copy cube (shift + d)\n6. Error throws\n\n", "Cycles viewport unneccessary update calls\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia MX150\n\nBroken: 2.83.17, 8a8c61190b06, Beta and 2.90.2, 8f21f867e715, Alpha\nWorked: 2.82a official\n\n[#76970.blend](T76970.blend)\n\n* set scene renderer to Cycles\n* configure two viewports and a shader editor in a single screen\n* set one viewport to cycles preview render\n* set second viewport to workbench texture color\n* add two image texture nodes and load them with different textures\n* by clicking on the texture node both viewports are redrawn." ]

[ "Regression: Overlapping face renders black in render mode\nOperating system: windows\nGraphics card: gtx , rtx\n\nBroken between: c4bedeb0186b - 0379ddac7d68\n\n**Short Description**\nOverlapping faces renders black in both viewport and final render (Cycles render engine)\n\n**Steps to Reproduce**\n- Open attached file\n- Switch to Cycles render engine\n- Change viewport shading to render (or render as image/animation)\n\n[#96958.blend](T96958.blend)\n" ]

[ "Shadow catcher problem with holdout collection\nOperating system: *Windows 10 Pro 64 bits*\nGraphics card: *2x NVIDIA GTX Titan X*\n\nBroken: *master 2.81a*\nWorked: *Worked on blender 2.79b*\n\nWhen shadow catcher is activated in an object located in a collection with the holdout option, alpha is truncated.\n(more visible when there is motion blur)\n\nBased on the default startup :\n- set render engine to cycles\n- set Film parameters to Transparent\n- activate Motion Blur\n- set world backgound color to white (better visibility)\n- delete light\n- create a plane, scale x2\n- move plane to a new collection\n- set plane to shadow catcher\n- set collection 2 (called by default, with the plane) to holdout\n- animate camera for have motion blur (more visible when there is motion blur)\n- in viewport render, you will have that : \n- render.\n\nwithout motion blur :\n antialiasing problem\n\nwith motion blur :\n\n\nsame render result with and without alpha on composite node :\n\n\n\n.Blender here : \n[#73376.blend](T73376.blend)", "Outliner toggle animatability\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release)\nBroken: \t\t\tBlender 2.80-2.82 (official releases)\t\t\n\n\nThe animatability of objects, collection (layers) etc... are not available as they were in 2.7X \n\n| 2.7X UI (friendly) | Data | 2.8X UI (friendly) | Data |\n| -- | -- | -- | -- |\n| Exclude Render Layers from having any influence | `bpy.context.scene.render.layers[\"RenderLayer\"].layers_exclude- [x]` | Exclude from View | `bpy.context.scene.exclude` |\n| Restrict Viewport Selection | `bpy.data.objects[\"In Collection 02\"].hide_select = False` | Disable Selection | `bpy.data.collections.hide_select` |\n| ZMask Scene Layer for solid faces | `bpy.context.scene.render.layers[\"RenderLayer\"].layers_zmask[10] = False` | Holdout | `bpy.context.scene.holdout` |\n| ? (new property) | ? (new property) | Indirect Only | `bpy.context.scene.indirect_only` |\nThese properties will be printed on the info editor.\n\nTo show what I mean, I've created a .blend in 2.79b with all the things listed above.\n\n[2.79_Demo.blend](2.79_Demo.blend)\n\nOpen the .blend file in 2.79b and ues the functionality:\n\n - Restricted Viewport Selection in curtin frames\n\n - Masking until frame 4\n\n - Layer excluded completely until frame 9\n\nNone of this works in the listed broken versions... and there is seemingly no mention in the release notes of this being designed not to function anymore.\n\n___\nI'm not sure, nor can I think, of a reason why you can't animate these and other properties collection wide.\nExample: **All** these toggle are not animatable:\n\nI don't know that would constitute a bug as there's nothing to compare the functionality to. *I'm sure it just hasn't been added (yet).*", "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", "EXCEPTION_ACCESS_VIOLATION error when trying to change object viewport color with the viewport compositing enabled in depsgraph_update_post\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.5.0\nWorked: 3.4\n\nThis error occurs only if the viewport compositor is enabled - rendered mode of the viewport and Compositor = Always.\nWhen trying to change the viewport color of the object by script on depsgraph update event, this error occurs.\n\nThe short script example:\n```\nimport bpy\n\ndef on_depsgraph_update_post(scene, depsgraph):\n if depsgraph.id_type_updated('SCENE'):\n for obj in depsgraph.updates:\n if isinstance(obj.id, bpy.types.Object):\n print('change object color')\n bpy.data.objects[obj.id.name].color = (1, 0, 0, 0)\n\nbpy.app.handlers.depsgraph_update_post.append(\n on_depsgraph_update_post\n)\n```\nAfter executing this script in the Text editor, switching to the \"Rendered\" mode of the 3D Viewport and enabling viewport compositing - when adding or copying the object - Blender throws an error.\n\nThis occurs only if the viewport compositing is enabled, if it is not used - code works as expected.\n\nError occurs on 3.5 and 3.6 alpha.\n\n1. I attached .blend file with the example\n2. Open .blend file\n3. Switch the viewport to the \"Rendered\" mode (z - Rendered)\n4. Execute script in the Text editor\n5. Try to copy cube (shift + d)\n6. Error throws\n\n", "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "Crash 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```", "Viewport Compositor: Render passes support\n# Scope\n\nThis design task describes integration of multiple render passes of the same view layer to the viewport compositor.\n\nWhile ultimately multiple view layers would need to be supported as well, it will be handled separately as there more design considerations to be solved to keep performance and memory usage under control/\n\n# Overview\n\nThe overall overview of the proposal is quite simple:\n\n- Render engine provides GPU textures for all render passes.\n- The compositing is done by the draw manager from the Blender side.\n\n# Breakdown\n\n## GPU texture management\n\nThe render engine manages GPU textures on the engine side, and allows them to be bound for the viewport compositor shaders. This allows the engine to have full control over data management and synchronization for updates. For example, it allows engine to do proper initialization order for the graphics interoperability.\n\n## Overlays\n\nSome of the data which a render engine wants to visualize does not fit into the compositing pipeline, and is better suitable as an overlay. On example of such visualization is the `Active Pixels` (available with `Cycles Debug`).\n\nSuch overlays will be moved from \"being\" baked into the combined pass and instead will become a dedicated call in the render engine `draw_overlay()`.\n\nOn the render engine side it will behave the same way as the current `draw()`: \"just\" draw a texture(s) with overlays.\n\n## Data structures\n\nThe proposal is to base the data passed in the API on the `RenderResult`, and not to create a dedicated specialized data structures. This will allow maximum code re-usaiblity between the viewport, viewport compositor, final renders, and eventually GPU compositor for the final renders.\n\nThere are changes which needs to be done in the `RenderResult` in order to support this, with the final goal is to allow `RenderResult` to point to a GPU texture instead of CPU-side memory buffer. The proposal here is to:\n\n* Make `RenderResult` to use `ImBuf` to store passes data.\n* Make `ImBuf` to have GPU texture without CPU side buffer.\n\nConsiderations for such decision:\n\n* The `RenderResult` is heavily integrated into the image drawing (for the `Render Result` image data-block, multi-layer EXR images). If the `RenderResult` stores data as `ImBuf` then it will simplify drawing, which will no longer need to do shallow copies.\n* The `Image` data-block already uses GPU textures, which can be moved to the `ImBuf`.\n\n## Synchronization\n\nUpdate of the GPU texture and its use by the draw manager happens from different thread, . This is already the case where `DisplayDriver` takes care of synchronization.\n\nTo start with the synchronization strategy will not change:\n\n* The render engine will lock the GPU textures at the moment when it knows its internal render buffer is in a consistent state (in case of Cycles: when the entire wavefront finished sampling), and will copy data to the GPU textures.\n* From within the same lock the render engine will copy data needed for the overlays.\n* Once the data is copied, the render engine releases the textures lock.\n* When draw manager requests `RenderResult` it will lock the textures, and will hold the lock until the drawing and compositing pipeline is finished.\n\nThis potentially introduces wait-on-a-lock for the render thread: if the compositing takes longer than sampling.\n\nWhen CPU rendering is used it is relatively easy and beneficial to allow \"interleaving\": render more samples while the draw manager is still busy with compositing. In the case of Cycles it will mean that the `PathTrace` will need to take time spent in drawing into account and schedule more samples to fill it in.\n\nFor the GPU rendering the story is more complicated:\n\n* If the rendering and compositing done on the same GPU the interleaving might not be desired at all, as a lot of supported GPUs do not allow interleaving GPGPU and viewport rendering without performance impact.\n* If the rendering is happening on a different GPU than viewport rendering then interleaving is possible.\n\nFor the latter either engine could do a guess which GPU is used for viewport, or it would need to be a dedicated API call to provide this information explicitly.\n\n## Used render passes\n\nCurrently for the viewport render the used render passes are in the full control of the render engine. This needs to be changed to something:\n\n* Render engine provides list of supported render passes\n* The viewport compositor provides information which of them are actually needed for the viewport\n\nThe former is probably already covered with the render passes integration used to create sockets in the Render Layers nodes.\n\nThe latter one is needed to make it so unused passes do not take memory: for example if some passes are only used to write to file.\n\nThe render pass display option (currently available in Cycles, and allows to choose which render pass is displayed in the viewport) will behave more like it does in the Image Editor where it is possible to choose between Composite output and View Layer / Passes, can then can work for any render engine.\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", "Hiding a nested collection doesn't immediately update its parent instances in the scene\nBroken: 483ae407d9d1 (blender2.8 HEAD)\nWorked: ?\n\nHiding a nested collection doesn't immediately update its parent instances in the scene.\n\n\n[outliner-deg.blend](outliner-deg.blend)\n\nHide the `Torus` collection (via the screen icon), this should hide this collection objects in the `B - I Instanced a torus` collection, however it doesn't unless you save and re-open or force depsgraph update in other ways.\n\n\n\nIf you toggle the `A - I have a torus` collection off, this one affects the instanced visibility immediately.\n\n*Note 1: The file only has Empties because I was looking at the depsgraph image and it was giving me a simpler depsgraph this way.*", "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).", "Multi-Object Properties Editing\nIn Blender, we want to make it easier to set values for multiple objects, bones, strips, keys and other items at once. \n\nCurrently you can do this in limited circumstances, but you have to right-click on a value after you've changed it and pick Copy to Selected from the menu or hold Alt while editing values. This not only slow, but also very hidden, and the Alt-key conflicts with Emulate 3 Button Mouse. Lastly, it isn't clear at all to users which values work for multi-editing, and which values don't.\n\nHere's how we would like to solve it:\n\n\n## Selection vs Active\n\nThe concept of ***active*** in Blender means that we only show properties and only affect the active object or item. However, if we want to better support multi-item editing, we must start by making it so the Properties reflects the ***selection*** rather than the ***active*** item, of which there can only be one. Going forward, by default the Properties will be set to reflect the selection instead. This could be controlled in the Properties like so:\n\n{[F8363009](Screenshot_2020-02-22_at_17.34.54.png), size=full}\n*(The search box is added here to reflect how the Properties will be updated when that item is also added, but is a separate feature)*\n\nIf set to ***Active***, the Properties will continue to function as it does today, only showing properties for the active item.\n\n## When there are multiple selected items\n\nWhen the user has selected multiple items, a few things change:\n\nInstead of showing the name of the object at the top, Blender tells the user how many items are selected:\n\n\nIn the list of tabs, only properties sections are shown that are common among the selected items. For example, if you select a text and a mesh object, we don't show Modifier, Mesh or Curve Properties, since these properties only exist on a subset of the selected objects:\n\n\nThis rule also goes for individual panels. Here, both a Sun and Spot light are selected, and we only see properties that are shared between them. A note at the bottom clarifies that you are only seeing the shared subset:\n\n{[F8364914](Screenshot_2020-02-23_at_18.49.33.png), size=full}\n\n## When values differ\nWhen multiple items are selected, Blender will compare values to check if they are the same, or if they are different. If they differ, we change the way properties are displayed, like so:\n\n{[F8363037](Screenshot_2020-02-22_at_17.52.51.png), size=full}\n\n\n\n## Manipulating values across multiple items\n\n\n\nFor simply setting a value to be the same. you would simply type a new value, hit Return, and that value is then propagated to the selection.\n\nFor manipulating numbers and sliders relatively, you can just drag on them (like Alt-dragging today), or type the character '=', so the user can type '= -3' to subtract 3 from the value on all selected items.", "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", "Only Render visibility for 3D viewport\nIt should be possible to show only objects that will be in the final render in the 3D viewport.\n\nCurrently disabling the overlay only does half of what the old Only Render option did, which is to hide non-geometry objects. The visibility part is important too, though more complicated now since the regular viewport depsgraph will not evaluate objects that are not visible in the viewport.", "UI Lists Filtering can have non-visible items active (e.g. after deletion) which lets you act on non-visible items\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83 (sub 17)\n\nWhen using any UI list filtering, if you press the \"-\" several times, at some point you'll jump out of the list and start deleting things from the list without seeing them:\n\na short video to show more in detail\n[2020-05-15 08-44-35.mov](2020-05-15_08-44-35.mov)\n\nUse any list, that has more than a few elements,\nfilter it, \nstart deleting, \nthe active highlighting disappears at some point, \nkeep deleting\nfind out that you deleted things outside of the list that was filtered.\n\nOR\n[#76853.blend](T76853.blend)\n- Open File\n- Cube has 2 vertex groups [\"apples\" and \"oranges\"]\n- \"oranges\" is selected/active\n- \"oranges\" is not visible though because a filter for \"app\" is applied on the list\n- \"thus only \"apples\" is visible\n- hit the {key -} button\n- \"oranges\" will be deleted [without user knowing]\n", "Clearing library overrides from the object menu differs from the outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.1 Release Candidate\n\nPlease see the attached movie. Using the \"wrong\" menu will cause the material properties panel to become unresponsive (beginning of movie) with overrides still in place until you use the outliner (end of the movie).\n\n1. Link some objects from a file\n2. Override them down to the materials\n3. Swap out some materials\n4. Use the clear library override from the object menu\n\nResult:\n\nThe material overrides aren't cleared, but you also can't access the properties panel anymore.\n\nExpected:\n\nThe material overrides should be cleared.\n\nWorkaround:\n\nUse the outliner instead.\n\n" ]

[ "Toggle visibility/renderability for object an all child-objects\nThis patch is a proposal for a different behavior of the outliner toggle visibility/renderability buttons (and corresponding keyboard functions): toggle visibility/renderablilty for the object an all child-objects. I tested this different functionality on my own build Blender 2.5 now for awhile and I find this new behavior more intuitiv and useful.\n\nWhat the the patch changes:\n\nWhen you have multiple objects which are linked via the parent relation to some main-object (many times this is an \"Empty\"-object) and you click on the toggle buttons for visibility and renderability for the main-object the visibility and renderability of that object only is changed, not the visibility/renderability of the child-objects. This is IMHO a little confusing and annoying, because to changed the visibility/renderability of the whole multi-part object you have to click on each child-object (please correct me if this functionality is already there and I did not find it). With the patch the visibility/renderability of all child-objects is toggled, too, except those which are not selectable. Thus making the whole multi-object visible/renderable resp. not visble/renderable. The not-selectable-exception is IMHO useful if some object should e. g. never be shown or rendered, like helping objects for making holes in some other object etc.\n\nThe patch contain:\n\n- new function propagate_restrict_flag() which propagate a given restriction flag to the settings of the supplied object\n- when the visibility/renderability of an object is changed, call function propagate_restrict_flag() to propagate the new state down to all child-objects (except those who have OB_RESTRICT_SELECT set)\n\nNote: this task is a copy of #24042 where I do not have access anymore." ]

[ "Jack Audio not detected under High Sierra\nOperating system: OSX High Sierra 10.13.6\nGraphics card: Intel HD Graphics 4000\n\nBroken: (2.83.3)\nWorked: (unknown)\n\n\nBlender is not showing Jack in the audio devices list.\nTyping bpy.app.build_options.Jack in the python console drops False.\nJack server is properly installed prior to Blender and working fine with other applications.\n\n\n\n\nUnder OSX High Sierra 10.13.6 install the latest version of Jack Audio from the official site (JackOSX 0.92_b3). Then install Blender 2.83.3. Although Jack is installed and properly working in other applications, Blender won't detect it and won't show it in the audio devices' list.\n\nWhen building 2.90 from the source I detected the error. The file jack.h and other jack related files weren't found in the location requested by Blender's installer, because the installer was requesting them in a .../jack/ subfolder. Duplicating Jack files to a .../jack/ subfolder solved the problem. Blender built then correctly and Jack appeared in the devices' list afterwards. Timeline sync using Jack Transport is working as well.\n\nIn concrete, I duplicated the files in /Library/Frameworks/Jackmp.framework/Versions/A/Headers/ to the created subfolder /Library/Frameworks/Jackmp.framework/Versions/A/Headers**/jack/** to bypass the error. But the former is the folder where Jack installs by default under High Sierra.", "VSE Sequencer timecodes display almost correct values\nOperating system: Linux-5.4.0-94-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.0.0\n\nsometimes the timeline displays 1m60s instead of 2m. this is kind of correct but actually not correct. I have no idea what could cause this, this appears on various zoom levels and only on specific positions that seem to be fixed positions.\n[superstious.mp4](superstious.mp4)\n[2022-01-14 20-43-02.mp4](2022-01-14_20-43-02.mp4)\n\n\n[#94920.blend](T94920.blend)\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.", "Smoke simulation silently fails in Sync to Audio or Frame Dropping playback\nSmoke simulation silently fails in Sync to Audio or Frame Dropping playback\n\n---\n\n**Original Report:**\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 3.1.2\nWorked: Never (tried 2.93, 2.83)\n\nThe smoke simulation does not simulate beyond the first frame in this particular file. Any smoke simulation added or appended from other files stops working as well.\n\nHowever, everything works fine in new files on the same system & hardware.\n\n[smoke simulation issue.blend](smoke_simulation_issue.blend). \n\nOpen the blend file, move the smoke domain to clear the old cache.\nHit play and the smoke is not moving. Other physics (rigid body, particles) are working fine.\n\nDelete everything, add a cube, add the quick smoke effect, and the same happens.\n\n", "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", "Incorrect Areas affected by Timeline Playback settings\nVersion: 2.80 rc2 (Linux 64)\n\n[Timeline_bug.blend](Timeline_bug.blend)\n\nTo reproduce:\n\n - Open the example file (enable \"Load UI\" too)\n - With the mouse cursor in the 3d view, play the animation using Shift + Space (or Alt + A, whatever your keymap is)\n - Ignore the 3d view. Notice which animation editors show a moving playhead.\n - Inspect the playback settings in the timeline editor.\n - Disable \"All 3d Viewports\" and repeat step 2.\n - Now Enable \"Active Editor Only\" and repeat step 2.\n\nWith certain settings, the Dope Sheet and Timeline show playback even when the Graph Editor and NLA do not. It's as if these windows think they are 3d viewports!", "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)", "\"Whole Character\" keying set not working properly with autokey enabled\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 2.93.4\n\nUsing the keying set \"Whole character\" with autokey enabled creates a keyframe only for the selected bone and not for all bones and properties.\n\n- Open attached file or create a new armature with more than one bone, add a few bone properties to each bone.\n- Enable autokey and set \"Whole Character\" as the keying set.\n- Move one bone and you can see that only the transform values are keyed.\n- If you enable \"Only active keying set\" in the autokey options and move the bone, a keyframe for the custom properties of the selected bones, at least, will be created, but other bones and properties will be unaffected.\n[bugreport.blend](bugreport.blend)\n", "Regression: Performance regression after support modifiers on curve objects commit\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nCaused by b9febb54a4\n\nPerformance regression playing timeline this this file (Modified Mr Elephant):\n\n[mr_elephantAnimed.blend](mr_elephantAnimed.blend)\n\nOpen the file and play the timeline in eevee rendered mode.\n\nFirst problematic commit: b9febb54a492ac6c93802fb0aa189d4c3fd99b0b\n\nPerformances before:\n80 fps on my system (idk why the framerate is not limited to 60 btw)\n\nPerformances after:\n41 fps on my system\n", "BKE_nlatrack_add behavior is incorrect\nOperating system: N/A\nGraphics card: N/A\n\nBroken: 3.1\nWorked: N/A\n\nThe way the `prev` argument is interpreted for the `BKE_nlatrack_add` function makes it impossible to add an `NlaTrack` to the bottom of a track list.\n\nPassing in a `prev` value of `NULL` adds a track to the top (visually). However, this is technically incorrect because to add it to the \"top\" of the list actually means that `prev` should be an existing track (it's slightly confusing because the order in the UI is the opposite of how it's represented in data).\n\nIf I were to speculate, I'd say that interpreting `NULL` as a flag to add it to the \"top\" of the list was done as a convenience, since this is probably what the user would want as a default. However, it's still technically incorrect and wonky. There are only a handful of places were `BKE_nlatrack_add` is called, so cleaning it up shouldn't be too big a job.\n\n\n[nlatrackaddbug.blend](nlatrackaddbug.blend)\nThe following script reproduces the bug:\n\n```\nimport bpy\n\nobject = bpy.context.view_layer.objects[0]\nobject.animation_data_clear()\nobject.animation_data_create()\ntracks = object.animation_data.nla_tracks\n\n# ADD A TRACK TO START\ntrack = tracks.new()\n\n# ADD TO TOP (previous track is the one we just made)\nlast_track = tracks[-1]\ntrack = tracks.new(prev=last_track)\ntrack.name = '01 ADD TO TOP'\n\n- ADD TO BOTTOM\n- ERROR: adds it to the top as well!\ntrack = tracks.new(prev=None)\ntrack.name = '02 ADD TO BOTTOM'\n```", "Particle hair simulation not working\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.93.4\nWorked: unknown\n\nI modeled particle-hair and try to make it dynamic, for whatever reason I cannot make it to work and sometimes Blender crashes.\n\n[Test.blend](Test.blend)\n\n[Test.crash.txt](Test.crash.txt) \n\nIf I try another simple particle-hair system on the-same object it does work. \n\nTry to get the hair in attached file to simulate.", "VSE video strips with audio get packed into the .blend file when auto-packing enabled, leading to crashes with large amounts of videos\nOperating system: Windows 8.1\n\nBroken: 2.80, 2019-04-09\nWorked: 2.79\n\nBlender will try to pack all video/audio files in the vse into the .blend file if \"File>External Data>Automatically Pack Into .blend\" is enabled. This is terrible default behavior since it can very easily lead to blender attempting to save huge multi-gb files.\nIn addition to this, if you have more gb of files than you have ram, blender will crash when you enable auto-pack... really easy to do since a single video can easily be over 32gb.\n\nSome notes:\nBlender seems to only decide to do this for video files that have an audio track, even if the audio track is no longer loaded into the timeline.\nThere are no options to pack/unpack a video track. If the audio track is removed, the file will still attempt to be packed, but it cannot be unpacked.\n\nCreate a new 'Video Editing' file.\nLoad several gb of videos with audio into the vse timeline.\nSelect \"File>External Data>Automatically Pack Into .blend\"\nSave the file...\n", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n", "Sequencer: Can't toggle Channels sidebar when VSE view type is \"Sequencer & Preview\"\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\nversion: 3.2.0\n\nAll in the title.\n\n1) Be in Video Sequencer editor\n2) Switch view type to Sequencer & Preview\n3) Try to toggle Channels sidebar : either with the little arrow (that doesn't show up), or by going to View > Channels (it doesn't toggle the sidebar, its checkbox doesn't get checked)\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" ]

[ ".mp3 files not playing when on sequencer\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.90.0 Beta\n\nSo I opened a few different files with certain random songs I had saved as a .mp3 file and none of the audio would play back, I checked my audio source and those were fine, the only thing that was not working is the latest beta branch. \nImport an mp3 file into the sequencer\nPlay animation using spacebar, or whatever keybind you have it set to. \n\nSong I tested and it didnt work, with multiple blend files: [DuckTales Music (NES) - The Moon Theme.mp3](DuckTales_Music__NES__-_The_Moon_Theme.mp3)\nUPDATE: tested with .wav files too, doesn't seem to work with any of them. " ]

[ "ALT + H\nOperating system: Windows-11 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.34\n\nBroken: version: 3.6.2\n\nALT + H not working. I verified languages installed on my computer and also engaged an informatician to verify if theres no conflicts with shortcuts with another program or so. Also i am not sure if its me, but i cant change the keymapping. in preferrences\n\njust ALT + H not working. I doubt if there is other shortcuts with Alt+ that are not working... Please forgive my english i am french as first language and i live in canada. So the language installed is Canada(fr)\n\n", "EEVEE renders black when no normal NODES connected to mix node --> normal input.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Release Candidate\n\n\nEEVEE renders black when no normal NODES connected to mix node --> normal input. Works fine with Cycles. \n\nOpen below file and click on each material output to see the issue. Switch to cycles and all fine.\n\n[empty normal bug.blend](empty_normal_bug.blend)\n\n\n\n\n", "EEVEE motion blur in cryptomatte\nI have tested this in 2.93.3 and even blender-3.0.0-beta+v30.bd734cc4419a to check if it got added there. \nThe issue is simple to explain: cryptomattes in eevee don't include motionblur. In Cycles they do include the motion blur. Is this a known thing, will it be addressed in the next updates?\nI suppose it could also be an undiscovered bug as the blender manual describes it as following \"[...] mattes will be anti-aliased and take into account effects like motion blur and transparency.\" cryptomatte.html - well in eevee it doesn't take motion blur into account", "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", "Sequencer: Can't toggle Channels sidebar when VSE view type is \"Sequencer & Preview\"\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\nversion: 3.2.0\n\nAll in the title.\n\n1) Be in Video Sequencer editor\n2) Switch view type to Sequencer & Preview\n3) Try to toggle Channels sidebar : either with the little arrow (that doesn't show up), or by going to View > Channels (it doesn't toggle the sidebar, its checkbox doesn't get checked)\n\n", "VDB sequences are rendered blocky here and there ( issues with Volume Displacement Modifier )\nOperating system: Windows 10 \nGraphics card: RTX 2070 CUDA\n\nBroken: blender-3.0.0-alpha+master.ef5a362a5b24-windows.amd64-release.zip\n\n\nBlender renders these blocky frames here and there during the actual render. The VDBs seem to be fine, the same botched render frames look fine in the viewport render. These anomolies are happening only during the actual render. See the attached image (middle right image) for what is happening please.\n\nThe same sequence renders without any issues in Houdini.\n\n(Cycles)\n\n\n\n\nHere is an actual movie render (with Eevee) that shows how horrible this issue is.\n[borkedframes_0001-0200.mp4](borkedframes_0001-0200.mp4)\n\n\n[#88966.blend](T88966.blend)\n[steam.4.0001.vdb](steam.4.0001.vdb)\n\n- Open .blend file\n- Render sequence with CUDA\n\nIssue should appear within 30 frames\n", "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)", "Outliner: Sorting not working for some types in Scene display mode\nBroken: Current master\nWorked: Never\n\n\nSorting elements in the outliner only works for objects. Scenes, collections, and other types are not sorted.\n\n<img src=\"https://projects.blender.orgattachment\">", "Movie Strip not showing in video editing preview only sound is working\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\n\nI was dragging and dropping my usual .mp4 file to my video editing project, the sounds are working but the video isn't showing. I tried the same .mp4 file in VFX project and it worked there. I \n\n{[F8632488](Thank_you_bencrulis.png)}then tried to import the same video file using the add - movie strip but I got an error. Then I renamed the file containing the following characters: C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 18-19-35. And it worked. Bare in mind I have 15 other movie strips carrying the same characters but different numbers. I am using an external drive. I drag and dropped the file (like I normally do) and the preview doesn't show. I copied the file to my computer and still the preview did not show. If I have a video with these characters, then the preview doesn't show: C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 03-56-05 C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 03-20-53 C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 02-33-57 C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 02-27-21. **HOWEVER,** if I have the following characters, the video preview in the video editing shows and works just fine: Call of Duty®_ Modern Warfare® 2020-04-26 21-00-17 Call of Duty®_ Modern Warfare® 2020-04-26 21-16-20 Call of Duty®_ Modern Warfare® 2020-04-26 22-10-30 and so on with previous dates. By renaming the rest of my new .mp4 files, all of them work correctly in the video editing sequencer. \n\nOpen Blender\nSelect the blend.file that you are working on\ndrag and drop a .mp4 video to the sequencer with the following characters of the file name: C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 18-19-35\nClick play\n\n[COD Pro Kills Part 1.blend](COD_Pro_Kills_Part_1.blend)\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.", "Particle hair simulation not working\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.93.4\nWorked: unknown\n\nI modeled particle-hair and try to make it dynamic, for whatever reason I cannot make it to work and sometimes Blender crashes.\n\n[Test.blend](Test.blend)\n\n[Test.crash.txt](Test.crash.txt) \n\nIf I try another simple particle-hair system on the-same object it does work. \n\nTry to get the hair in attached file to simulate.", "VSE: audio animations lost in scene strips\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: AMD Radeon HD 6800 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008\n\nBroken: version: 3.6.0\n\nIn a video project that consists of a main scene that links in several sub-scenes, animations of the audio volume in the sub-scenes are gone in the main scene. The audio will remain at the volume that was set in frame 1 of the sub-scene.\n\n(1) Open the attched .blend file.\n(2) Go to Scene 1 and play it. You will hear that the volume of the audio strip will go from 3.000 to 0.000\n(3) Go to the Main scene and play it. You will hear that the audio remains at volume 3.000 (the initial volume) from beginning to end.\n\nNOTE: If you select Scene 1 in the Main scene, go to a certain frame number (e.g. 600) and type \"1\" in the volume box of the scene strip, the audio will switch to the right volume at that particular frame, but will stay at that volume for the remainder of the frames.\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", "Clip random marker placement in track/mask - not working in 2.8\nWindows 10 x64 with nVidia 1080\n\nBroken: 2.80, 2.83 @ be8879718e24e417d299eb298b8a9d4d2ca324ee\nWorked: 2.79 (because there was no collapsible floating redo panel)\n\nIt's impossible to add a mask (or tracking) using ctrl+left-click in the clip editor.\n\n\n[#57646-clip-marker-placement.zip](T57646-clip-marker-placement.zip)\n\n- Open the above blend file, or:\n - Start Blender in factory settings.\n - Add a VFX → Motion Tracking workspace.\n - Load a video file into the clip editor.\n- {key Ctrl Click} in the clip editor to add a marker.\n- Open the redo panel.\n- {key Ctrl Click} in the clip editor to add a marker, and see that the marker appears at an offset.\n- {key Ctrl Click} again and see that the position is now correct.\n- Close the redo panel.\n- {key Ctrl Click} in the clip editor to add a marker, and see that the marker appears at an offset.\n- {key Ctrl Click} again and see that the position is now correct.\n", "Importing Alembic fails after more than ~510 individual cache files\nOperating system: Windows 10\nGraphics card: RTX 2080\n\nBroken: 3.4.1, 3.5.0\nWorked: -\n\nI am trying to import a lot of alembic character files. After ~510 successful caches following imports fail with error `Could not open Alembic archive for reading! See console for detail.` The console additionally prints `Could not open as ogawa file from provided streams` Individually all of my alembic files import without problems. The alembics are exported from blender. Importing fails for complex characters, as well as the default cube exported as alembic.\n\nOpen the attached blend file and run the script from the text editor. It will start to import the (attached) `cube.abc` without problems until it gets to roughly the 510th import.\nAt this point it is not possible to import any more alembic caches.\n\n" ]

[ "Audio files not playing when on sequencer\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.77\n\nBroken: version: 2.90.0 Beta\n\nSo I opened a few different files with certain random songs I had saved as a .mp3 file and none of the audio would play back, I checked my audio source and those were fine, the only thing that was not working is the latest beta branch. \nImport an mp3 file into the sequencer\nPlay animation using spacebar, or whatever keybind you have it set to. \n\nSong I tested and it didnt work, with multiple blend files: [DuckTales Music (NES) - The Moon Theme.mp3](DuckTales_Music__NES__-_The_Moon_Theme.mp3)\nUPDATE: tested with .wav files too, doesn't seem to work with any of them. " ]

[ "Edge Sliding with subdivision surface is extremely laggy (caused by \"bad\" UVs and UV Smoothing in the modifier)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\n\nSo I've been modelling a raptor the last week and I noticed that viewport performance in edit mode was extremely laggy with subdivision surface modifier enabled. I checked the face count and it was just 150k faces which is not a lot at all. It's definitely a modifier problem because when I apply the subd modifier the lag goes away completely even when sliding twice the amount of edges around. I thought that was maybe a hardware issue so I opened task manager and while sliding edges with subd on I get like 4 fps with severe stuttering to top it off. All that while the cpu was at 10% usage and 5% gpu usage with memory barely touched (6gb used out of 64gb). I have nothing else running in the background like an ativirus or music app, I have the latest version of windows 10, latest gpu and chipset drivers, latest bios etc... I even have gpu subdivision enabled without autosmooth to make sure it actually works properly. I even run an sfc/scannow to check for other kinds of issues but nothing changed. Subd in edit mode however is not only slow when sliding edges and vertices but also in adding loop cuts or insetting faces. It is extremely frustrating so it would be great if you could fix this. I know edit mode was not made to handle massive polycounts but 150k is again not a whole lot and definitely comfortable to run on my PC. Here is the file to see for yourselves.\n\n- Open attached .blend\n- Execute Edge slide/loop cuts/inset faces\n[Broken Subd.blend](Broken_Subd.blend)\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)", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "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)", "Dynamic paint waves: Viewport render and main Render looks very different.\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.82 (sub 7)\nWorked: Never\n\nIn render dynamic paint do notproduce waves as it do in viewport.\n\nViewport:\n[viewport.mp4](viewport.mp4)\n\nRender\n[render.mp4](render.mp4)\n\nFile:\n[DinamicTestPaint.blend](DinamicTestPaint.blend)\n", "Multires: Duplicating objects sets the viewport level to sculpt level\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.1.0 Alpha\n\nWhen sculpting on an object with a multiresolution modifier there are 3 sliders to define the level of subdivision.\nWhen duplicating the object right now, it will set the viewport level to the same value as the sculpt level.\n\n- Add a multires modifier\n- Subdidive the object\n- Set the viewport level to soemthing other than the viewport value\n- Duplicate the object\n\n", "Collada exporter's triangulation option messes up custom vertex normals\nBroken: v3.4.1, v3.2.0, v3.1.2\nWorked: Never, as far as I can tell.\n\nWhen using the Collada exporter to export a mesh with custom vertex normals (with the exporter's triangulation option on), for each quad, one vertex of a split-off triangle will have an incorrect vertex normal.\n\n Figure 1: A grassy slope mesh in Blender.\n\n Figure 2: The same mesh in Unity. Note how the lighting produces a visible seam between the two triangles of each grass quad. (Apologies for the low color contrast in the screenshot)\n\n- In Blender, create a quad mesh and rotate it so that it's standing instead of laying down\n- Use \"point to target\" to point the quad's normals straight up\n- Export the quad with the Collada exporter, with the triangulate option on\n- Import the mesh into some other program to check the exported vertex normals. You should see that one of the vertex normals is wrong.\n\n**Workarounds**\nTriangulating with Ctrl+T does not suffer from this bug.", "Cycles doesn't render volumes when clip end is inside the volume\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 471.11\n\nBroken: version: 3.1.0 Alpha\n\nWhen clip end is set to a value inside a volume, the volume is not renderered at all.\nRelated to [#92491 ](T92491) so an alpha build is needed.\n\n- Open project\n- Press F12 (Volume isn't rendered)\n- Set clip end to something high (e.g. 100)\n- Press F12 again (Volume is rendered)\n\n[volume.blend](volume.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", "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", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Cycles can not render parent particle hair, while Eevee can.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duno\n\n\nIn Eevee, parent particles are successfully rendered both in viewport and final render.\n\n\nHowever, Cycles fail to render the parent particles both in viewport and final render.\n\nA sample Blender file has been attached below.\n\n", "Subdivide with smoothness not symmetrical (not deterministic, depends of order of vertices in face)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 430/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\nBroken: version: 2.83.4\nWorked: Never (2.8+)\n\nMesh is no longer centered along axis after using Subdivide with Smoothness greater zero. Projection of mesh is not exactly rectangular when looking form top.\nThe position of vertices, created with Subdivide with applied Smoothness, is wrong/arbitrary only if the vertex is placed inside the original face/polygon not along the edges of it. (Quads have one vertex inside face after one subdivision, Triangles need atleast two subdivisions for the error to appear because first subdivision creates new vertices only on edges)\n\nFirst example:\n1. Open subdivide_smoothness_plane.blend\n2. Apply Subdivide with Smoothness to the mesh\n3. Mesh is no longer centered along y-Axis. Compare position of vertices created inside the two quads.\n[subdivide_smoothness_plane.blend](subdivide_smoothness_plane.blend)\n\nSecond example:\n1. Open subdivide_smoothness_multiple.blend\n2. Apply Subdivide with Smoothness to the mesh with MORE then one Number of Cuts\n3. Mesh is no longer centered along y-Axis\n[subdivide_smoothness_multiple.blend](subdivide_smoothness_multiple.blend)\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.", "Data block name not unique when use gpu subdivision option turned on\nOperating system: Windows 11\nGraphics card: NVIDIA Quadro P6000\n\nBroken: 3.1 all the way to 3.6\nWorked: Anything before 3.1\n\nWhen the option Viewport->Subdivision->GPU Subdivision is turned on in the preferences, the data block names for meshes that have the subdivision modifier attached are the same.\n\n1. Start with the default scene.\n2. Create a second cube.\n3. Attach a subdivision modifier to each cube.\n4. Run the following script.\n\n```Py\nimport bpy\n\ndepsgraph = bpy.context.evaluated_depsgraph_get()\n\nfor i, ob_inst in enumerate(depsgraph.object_instances):\n \n if ob_inst.object.type == \"MESH\":\n print(\"%s (%s)\" % (ob_inst.object.data.name, ob_inst.object.name))\n```\nThe output you should see is something like this:\n\n```\nMesh (Cube)\nMesh (Cube.001) \n```\nIf you run the script again with the option turned off, you should see this:\n\n```\nCube (Cube)\nCube.001 (Cube.001)\n```\n\nI'm not sure if this is expected, but it's inconsistent behavior. As far as I can tell, it only happens on Windows and Linux. It doesn't happen on my Intel Mac running running macOS Ventura (13.4.1)." ]

[ "Subdivision surface bug in cycles\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.80\n\nBroken: version: 3.1.0 Beta\n and all versions after\nWorked: 3.1.0 Alfa\n\nsubdivision surface doesn't work in cycles viewport render view, and final render.\n\nsubdivision surface doesn't work in cycles viewport render view, and final render.\nunless it has another modifier after it, even if it isn't actually doing anything as long as it's on[the other modifier]. and Adaptive subdivision doesn't have this issue. and also Applying it dose work\n[SubivisionSurface_Bug.blend](SubivisionSurface_Bug.blend)" ]

[ "Vector displacement on top of adaptive subdivision breaks normal\nOperating system: Windows 10 / Ubuntu 22.04\nGraphics card: NVidia A6000 / K5100M\n\nBroken: 4.0\nWorked: never\n\n\nVector displacement on top of adaptive subdivision breaks normal.\n\n\n- Open attached file, switch to render preview in viewport.\n- It's in adaptive subdivision, where the vector displacement is connected.\n - Wrong normal in the \"hanging over\" side (in black).\n- If unmute the Geometry \"True Normal\" node, the normal seems to be correct but it lacks smooth interpolation (observable upon close inspection.\n- Add a displacement modifier (thus disabling the adaptive subdivision), and remove the displacement output link in the material.\n- Set the displacement modifier to the displacement texture (use RGB to XYZ mode).\n - Vector displacement renders normal correctly.\n\n| VD on adaptive subdiv | VD on adaptive subdiv (with true normal) | VD modifier on regular subdiv (correct) |\n|---|---|---|\n|  |  |  |\n\n", "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", "Remesh Modifier in Voxel mode produces surface artifacts when Adaptivity enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: \n - 2.83.9\n - 2.91.0 Beta\n - 2.92.0 \nWorked: never\n\nRemesh modifier produces artifacts on mesh which look like a result of bad triangulation.\n\n1. Open attached blender file\n2. Open modifier panel and select testMesh\n3. Change adaptivity value from 1 to 0 cm and back\n4. Observe black shading artifacts \n[remesh_bug.blend](remesh_bug.blend)\n", "Baking Procedural Wave Textures\nOperating system: Win10\nGraphics card: Nvid 2080ti / 3090 \n\n3.4 (and others)\n\nCannot bake these textures correctly. \n\nCreate an object. \nAdd a wave texture, set it to uv, and scale it to show many even lines. \nAdd a color ramp to tighten those lines, setting it to constant. \nPlug this into the bump/normal to make raised lines. \nNow bake this. \n\nThe lines will be a broken mess most of the time. I have tried almost every trick I can find/think of, and nothing makes this better. \n\nI am not sure it's a bug, but it is certainly a problem.\n\n", "Modifiers after physics ones shouldn't invalidate cache\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.93.0\n\nIn current Blender, any change on modifiers invalidates.\nModifiers *after* physics modifiers won't affect the result of physical simulation, therefore they shouldn't invalidate the cache. \n\n\n1. Create a plane\n2. Give it Cloth and Subdivision modifiers, in this order\n3. Set the end frame to 10\n4. Play animation until the end\n5. Stop animation\n\nNow the simulation is cached.\n\n6. Change the viewport division level on Subdivision modifier\n\nNow the cache is invalidated.\n\n", "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?", "Subdivision modifier does not interpolate zero weights.\nOperating system: Linux\nGraphics card: Intel UHD\n\nBroken: 2.90.1\nWorked: ???\n\n\nThe subdivision modifier usually interpolates both value and membership across subdivided vertices.\n\nThis allows it to be used in non-destructive, modifier-based workflows that operate on or using vertex groups.\n\nIt does not do this, however, when vertex weights are equal to zero. The original vertices retain their (zero-weighted) vertex group membership, while new vertices in between them have no vertex group membership.\n\nAn example of why this is problematic is screenshotted below, with the file attached:\n\n\n\nEach Subdivision'd sphere has a bumpy texture applied using a Displace modifier after a textured VertexWeightMix modifier.\n\nThe rightmost sphere has its vertices weighted to 0.01, and interpolates and behaves correctly.\n\nThe leftmost sphere has its vertices weighted to 0.00. It intuitively (and, numerically/extrapolatively) should be indistinguishable to the 0.01 sphere. Because its weights aren't correctly interpolated, it instead ends up with a bunch of spikes at each of its original vertices.\n\nThe middle sphere has vertices weighted in a gradient from 0.00 to 0.50. It serves as an example of a feasible real-world application which would be broken by this kind of behaviour. Perhaps the original vertex weights act as a sort of base heightmap for a terrain model, and the changes made by the Subdivision and textured VertexWeightMix modifiers add an extra layer of detail. In this case, the clear and useful behaviour would be for behaviour to be continuous in the transition from 0.01 to 0.00. Instead, there is a sharp cutoff at 0.00, and inconsistent and discontinuous behaviour after that.\n[ZeroWeightSubdiv.blend](ZeroWeightSubdiv.blend)\n\nApply a subdivision modifier to a mesh with zero vertex weights, then check the vertex group membership of its vertices afterwards.\n\nOr download and open the attached `.blend` file.", "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", "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", "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", "Panoramic Render in Cycles. Bump bug.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.1\n\nWhen using a material with fine bump and a panoramic camera the bump appears inncorrectly in rendered view.\n\n- Give an object a material with a fine bump (e.g. noise texture 15 detail, .8 roughness. Bump strength 1, distance 1)\n- Bring camera in really close.\n- Set to cycles.\n- Switch camera between panoramic and perspective mode.\n\nPlease let me know if there are any work-arounds, this bug is causing me problems.\nThank you.\n\n", "Multires: Duplicating objects sets the viewport level to sculpt level\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.1.0 Alpha\n\nWhen sculpting on an object with a multiresolution modifier there are 3 sliders to define the level of subdivision.\nWhen duplicating the object right now, it will set the viewport level to the same value as the sculpt level.\n\n- Add a multires modifier\n- Subdidive the object\n- Set the viewport level to soemthing other than the viewport value\n- Duplicate the object\n\n", "Multiresolution Issues\nThis is a temporary parent task to gather long standing and highly problematic issues with the Multiresolution modifier.\nThis mostly concerns bugs, known issues and badly supported existing features and gives an overview of the most pressing issues.\nNew features are not part of this task and don't need to be discussed.\n\n# Goal\nThe intent behind the task is to incrementally fix long standing issues to fix the current experience of subdivision based sculpting.\n\n# List of Issues\n\n## Crashes\n\n- [ ] #99887 - Multires Unsubdivide freezes Blender with hidden geoemtry\n- [ ] #84551 - Multiresolution - Crash when Linear Subdivision level is above 1\n- [ ] #100985 - Crash on sculpt mask brush when Multiresolution modifier is copied from another object\n- [ ] #85065 - Sculpt Mode - Using Mask while Multiress active = Crash\n- [ ] #86114 - Multires Displacement Smear brush + Dyntopo Error\n\n## Long Standing Issues\n\n### Visibility\nOne of the most important badly supported features is face visibility. \n\n- [ ] #87821 - Sculpt mode: annotation and unhide conflicts with Multiresolution modifier\n- [ ] #92372 - Sculpt mode: hide masked do not work when modifier enabled, but hidden part works with modifier\n- [ ] #95419 - sculpt mode: invert visible hides all faces with Multires modifier\n\n### Propagation\nAlso a high prioprity. Spikes and artefacts of details is making switching levels a bad experience.\n\n- [ ] #76374 - Multires: Artefacts from lower subdiv level changes\n- [ ] #94769 - Multires spikes\n\n### Undo\nBroken sculpted levels and other undo issues are very severe, since they are easy to trigger and cannot be easily recovered from. This also makes switching levels worse.\n\n- [ ] #93511 - Unable to undo subdivision with Multiresolution modifier\n- [ ] #79487 - Multires Level switching undo bug\n- [ ] #76311 - Redo causes pointy mesh artifacts in Multires\n- [ ] #76313 - Redo in Multires doesn't bring back stroke made after a subdivide\n\n### Rebuilding Subdivs\nA vital feature that is not reliable and surprisingly destructive.\n\n- [ ] #99857 - Rebuilding subdivisions with multiresolution deletes vertex groups\n- [ ] #81645 - Rebuilding multires subdivisions sometimes puts some vertices at the origin\n- [ ] #85792 - unsubdivide of Multires bug\n- [ ] #95022 - Using \"Rebuild Subdivisions\" in Multires modifier on hires mesh returns an error: Not valid subdivisions found to rebuild lower levels\n\n### Face corner inaccuracies\nVisibility and masking can lead is having different results in multires.\n\n- [ ] #79319 - Transform Tools influence on Hidden Face Sets with Multires Modifier\n- [ ] #79317 - Hidden Face Set Boundaries unmasked after inverting the mask on Multires Modifier\n\n### Grids consistency\nSome common workflows operators lead to severe issues with the multires grids.\n\n- [ ] #76682 - Applying negative scale inverts multires displacement\n- [ ] #76735 - Sculpt: Artifact in Multires when mirror modifier is applied\n\n### Smooth Normals\nSmooth faces is overall a worse expereince and is often avoided as a result.\n\n- [ ] #80641 - Sharp normals along base mesh wires in multires sculpting with smooth shading\n\n### Performance\nSome performance issues were investigated but never fixed.\n\n- [ ] #79488 - Multires clay brushes performance issue\n\n### Other\nVarious issues, arranged by importance.\n\n- [ ] #63581 - Textures not displayed in sculpt mode due to missing UVs (PBVH rendering, Multires)\n- [ ] #94631 - Multires: Duplicating objects sets the viewport level to sculpt level\n- [ ] #107102 - No visible mesh on Viewport Screenshot in sculpt mode with Multires\n- [ ] #73355 - Multires: Missing updates are not communicated in the UI\n- [ ] #90089 - Multires the Apply Base add to Quick Favorites can't change mesh\n- [ ] #76769 - MultiRes cannot \"Apply Base\" when ShapeKey have been added\n- [ ] #81497 - Multires: Editing base mesh creates random results on higher subdiv levels\n- [ ] Reshape is unreliable (Needs report)\n\n## Unsupported\n\n- [ ] Geodesic & Diagonals Expand (Needs report)\n- [ ] Fairing operators (Needs report)\n- [ ] Mask Extract (Needs report)\n- [ ] #95665 - Grab Silhouette broken with Multires \n- [ ] #88999 - Sculpt mode: Pose brush with Face sets FK mode do not work with Multiresolution\n\n## UI\n\n- Graying out/disabling intentionally unsupported features (Like with Remesh)\n - Dyntopo\n - Trimming operators/tools\n - Mask Slice\n\n## Needs Investigation\n\n- [ ] #95557 - Multiresolution sculpting broken after change in base geometry\n\n", "Edge Sliding with subdivision surface is extremely laggy (caused by \"bad\" UVs and UV Smoothing in the modifier)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\n\nSo I've been modelling a raptor the last week and I noticed that viewport performance in edit mode was extremely laggy with subdivision surface modifier enabled. I checked the face count and it was just 150k faces which is not a lot at all. It's definitely a modifier problem because when I apply the subd modifier the lag goes away completely even when sliding twice the amount of edges around. I thought that was maybe a hardware issue so I opened task manager and while sliding edges with subd on I get like 4 fps with severe stuttering to top it off. All that while the cpu was at 10% usage and 5% gpu usage with memory barely touched (6gb used out of 64gb). I have nothing else running in the background like an ativirus or music app, I have the latest version of windows 10, latest gpu and chipset drivers, latest bios etc... I even have gpu subdivision enabled without autosmooth to make sure it actually works properly. I even run an sfc/scannow to check for other kinds of issues but nothing changed. Subd in edit mode however is not only slow when sliding edges and vertices but also in adding loop cuts or insetting faces. It is extremely frustrating so it would be great if you could fix this. I know edit mode was not made to handle massive polycounts but 150k is again not a whole lot and definitely comfortable to run on my PC. Here is the file to see for yourselves.\n\n- Open attached .blend\n- Execute Edge slide/loop cuts/inset faces\n[Broken Subd.blend](Broken_Subd.blend)\n\n", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)" ]

[ "Subdivision surface \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.80\n\nBroken: version: 3.1.0 Beta\n and all versions after\nWorked: 3.1.0 Alfa\n\nsubdivision surface doesn't work in cycles viewport render view, and final render.\n\nsubdivision surface doesn't work in cycles viewport render view, and final render.\nunless it has another modifier after it, even if it isn't actually doing anything as long as it's on[the other modifier]. and Adaptive subdivision doesn't have this issue. and also Applying it dose work\n[SubivisionSurface_Bug.blend](SubivisionSurface_Bug.blend)" ]

[ "Crash (memory use after free) on freeing RigidBody world\nReproducible with current master, probably there since forever.\n\n# Steps\nWith an ASAN build:\n\n- Open `rigid.anim.blend`\n- Close Blender\n\n[rigid.anim.blend](rigid.anim.blend) \n\n(Case found while working on #86379 (When using \"Append\" rigid body objects + empty constraint, none of its constraints work.))\n", "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", "High poly meshes perform poorly with planer decimate\nOperating system: Windows 10\nGraphics card: AMD Asus Vega RX64\n\nBroken: blender-2.81-92736a7b7592-windows64 (plus previous few builds - atleast)\nWorked: 2.8\n\nMy PC is decent, and I have had no problem decimating millions of vertices (albeit some few seconds of lag) usually. Right now, I'm trying to decimate a simple model with about 45k vertices only. The decimate modifier is working fine on default settings i.e., on 'Collapse' setting .. but as soon as I switch to 'Planer' .. Blender becomes unresponsive for several minutes at least (and also indefinitely in some cases). \n\nI noticed that in my task manager, the Blender is only using 29% of CPU.. and regarding RAM .. on one side it shows 61% usage, while the actual usage is only 289MB in the value column (see screenshot). Could this be a memory related overflow/underflow? This definitely does look like a bug to me. \n\n\n\n\n\n", "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", "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", "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", "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)", "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", "closest_point_on_mesh() freezes Blender when called from a driver\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: 2.79\n\nCalling closest_point_on_mesh() from within a driver causes Blender to freeze.\n\n[test2.blend](test2.blend)\nOpen the file allowing scripts -> Freeze", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "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", "problem Blender 4.0 in a mac mini\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\n\nI'm trying to get Blender 4.0 (Alpha) running on a Mac Mini running OS Ventura 13.14.1(c). When the cube appears (by default) it is not surrounded by the yellow paint and cannot be selected with the left mouse button or the pointer of the digital tablet either. It can only be selected in the outliner\n\n\n", "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", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "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" ]

[ "Blender 2.8 internal error app freezes\nHI. i use Mac Book Pro 15-inch, Early 2011\nrunning MAC OS high sierra version: 10.13.1 17B1003\n2 GHz Intel Core i7\n16 GB 1333 MHz DDR3\nIntel H D Graphics 3000 512 MB\n\nSo i was baking a fluid simulation in blender 2.80 but i stopped it along the way.\nSince then blender has frozen.\n1. I cant click anything anymore\n2. It wont tab into edit mode\n3. All keyboard shortcuts wont work\n4. The tools say internal error\n\nif you request i could show a picture of the error.\nfunnily, blender 2.79b works just fine.\nDoes anyone have an idea why this is so.?" ]

[ "Reliable GPU hang on common Intel cards (Linux)\nOperating system: Linux Fedora 32\nGraphics card: UHD Graphics 620 (rev 07) Intel\n\nBroken: 2.80.x, 2.90.0-x\n\n\n\nBlender crashes the computer, freezing, dmesg command shows a GPU Hang error.\n\n\nOnly with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here)\n\nOpen the given blend file [F8892221](gpuhangtest.blend) (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs.\n\nI followed the dmesg output that says to create an issue on freedesktop gitlab: 2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender.\n\nThe problem started from 2.80 if I'm not wrong, not with others earlier versions.\n\n", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "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)", "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.", "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", "UV: select similar enhancements\nAdd support for UV Select similar:\n\n* Islands / Faces / Edges, crossing UDIM boundary\n* Islands / Faces texel density\n\nThanks @BlenderBob !\n\n", "can't use logitech mx master 3 mouse shortcut keys in blender 3.6 LTS\nOperating system: Win 11\nGraphics card: RTX 3070\n\nBroken: (3.6 LTS)\n\n**I can't use the logitech mx master 3 mouse shortcut keys in blender 3.6 LTS.**\n\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", "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", "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.", "Unable to zoom/scale graph editor with [ALT] middle mouse button after frame selected of lowest point\nOperating system: Linux-5.4.0-107-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.2.0 Alpha\nWorked: Likely never\n\nGraph editor goes into locked cycle when frame selecting certain points\n\n[Bug.blend](Bug.blend)\nOn attached file. Box select lowest point of y location on frame 25. Hit Num Pad . to frame the selected point\nAttempt to scale or move graph up and down with [Alt} middle mouse button\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)", "Mesh: Subdivide op flushes selection too eagerly\nBroken: 2.92 master\nWorked: N/A\n\n\nThe Subdivide operator selects geometry that it shouldn't. Consider this example:\n\n\n\nIt looks as if the op flushes selection a bit too much. Note that the 'Expected' selection is valid selection in edge mode, as the edge rings around the rims are **not** selected. Those edges should neither participate in the op, nor be selected as the result of it, if vertex selection mode is not enabled.\n\nA better example:\n\n\n\n...here in face mode, a lone edge is getting selected by the op.\n\n\n1. On the default cube, in face mode select top and bottom faces, inset and bridge them.\n2. In edge mode select vertical edge rings.\n3. Subdivide.\n\nAlternatively, load this simplified example file:\n\n[subdivide_selection_issue.blend](subdivide_selection_issue.blend)\n\n...and Subdivide. Resulting selection of the middle face is unwarranted.", "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", "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" ]

[ "Select no longer works. Can not select vertex, edge or surfaces\nWindows10;Intel Core i5-6400 CPU NVIDIA GeFOrce GT 730\n\nVersion 2.78\n\nWorked: 2.77 Version Worked\nSelect no longer works. Can not select vertex, edge or surfaces\n\nUninstalled and reinstalled both msi and zip. Problem still exists.\n\n" ]

[ "Modal keymap for snapping in the `Corner Pin` widget has no effect\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe bottom bar states that pressing ^ will enable snapping, but it seems it does nothing.\n\n\n\n1. Create a new default file;\n2. Go to the compositor;\n3. Enable nodes;\n4. Add a viewer node (this allows you to resize and test different sizes for the `Corner Pin` Gizmo);\n5. Add a `Corner Pin` node;\n6. Edit the `Corner Pin` widget and try to snap.\n", "Applying Subdivision/Multires Modifier De-merges UV's\n### Update\n\nThe issue of custom-data (UV's specifically) becoming detached remains, this problem existed before b88dd3b8e7, it was just less obvious since selection connected near-by UV's. Now UV's are merged by default at a very low threshold when applying modifiers to mitigate the problem. Keeping this report open as it would be good if subdivision-surface didn't separate UV's, replies to this report contain some notes that could lead to a solution. In practice users should not experience problems caused by this behavior, so marking low priority. ~ @campbellbarton.\n\n----\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha \nWorked: working in 2.90 \n\nCaused by b88dd3b8e7\n\nWhen applying a subdivision modifier, certain UV's points disconnect from their neighbors. This does not seem to occur with the F3 menu subdivide operation.\n\n- Open default blender scene.\n- Subdivide cube - 1 level and apply it. Do this step 4x\n- In the UV editor use \"Alt select\" to select face loops at random.\n- Alt click around until a face loop is not fully completed, this will reveal unmerged vertices.\n- Check area that did not complete by moving faces, vertices, edges etc to confirm unmerged UV's.\nThis does not seem to be an issue with the newly added 9a52b30cc0 in my eyes, rather an issue with subdividing.\n[UV Disconnect.blend](UV_Disconnect.blend)\n\n", "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.", "Splitting two modifier keys between two input devices doesn't work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.0\n\n\nPressing modifier keys from two keyboard device doesn't correctly register in blender.\n\n\n- Have two physical \"Keyboard\" device that both have modifier keys\n- Press Ctrl on keyboard 1 and Alt on keyboard 2\n- Blender doesn't recognize that both Ctrl and Alt are pressed.\n\n-----\n\nOriginal description:\n\nHi - I have modifier keys (shift, alt ctrl) assigned on mouse and keyboard and razer keypad. \nI use alt to select edge/face loops without issue. \nIf I press shift+alt on keyboard then I can select as many loops as I like. Same if I press shift+alt both on mouse. \nHowever, if I use modifier keys combined between deviced (shift on keyboard and alt assigned on mouse, or vice versa) then it lets me add only one additional loop to selection only. \nI initially thought it was accessory issue, but Its true with my default keyboard, razer keypad, logitech G600 and Razer Naga mouse, I suspect the issue is within blender. \n\nIn summary combining modifier keys between keyboard/mouse doesn't seem to work, atleast with loop selections. Any advice? Thanks\n", "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)", "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", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "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", "Objects referenced in the `UVProject` modifier property are not snapped\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.90 (sub 0)\n\nWhen i select an object as projector transform in the UVProject modifier it doesn't snap to the object I added the modifier to.\n\n- add cube\n- add an empty\n- add uvproject modifier to the cube\n- set the empty as projector transform\n- enable snaping to surface\nor\n- open attached file\nWhen moving the empty it does not snap to the cube\n[bug.blend](bug.blend)", "GP brush pin for fill only, makes both stroke and fill\nHi \nI want to have fill and stroke in different color but if I pin, I get both color same.\nSo that I cannot make custom brush, or I have to change it vertex mode every time.\nCan you please check?\n\n[image](attachment)\n\n", "Regression: Particle mirror broken for particular mirrored mesh.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2. also version: 3.3.0 hash: `8d9d5da13706`\nWorked: 3.0.0, commit hash: `8b44b756d850db38ab4d83513682f2012d88a3f4` from branch 3.0.1 to be exact.\n\nCaused by 02ab4ad991\n\nParticle hair x-mirror results in hair going in all directions instead of being properly mirrored, see the following screenshot: \n\n1. Start from the attached blend file which has an emitter sourced from a base model and mirrored by applying a mirror modifier. I could not reproduce the issue from scratch with simpler geometry and I might have reconnected the hair at some point .\n2. Go into particle edit mode on the `Eyebrows_Particle` object.\n3. Enable x-mirror in the top-right `Options` menu.\n4. Observe that the particles change directions.\n\nHere is what it looks like when it's working in the same particle edit mode with x-mirror enabled. The exact commit that introduced the issue is: `77694b571f5bd297ea7228b30f591ebbd333e0ea`.\n\n\n\n[mirror_bug.blend](mirror_bug.blend)\n\n[repro.blend](repro.blend)\n- open file\n- `Particle` > `Mirror`\n- observe wrong mirroring", "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", "Snapping collision object to particle emitter not working\nOperating system: Linux-5.9.3-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.9.3-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.2.1\n\nBroken: 2.79 - version: 2.92.0 Alpha\nWorked: -\n\nIt is impossible to snap an object with Collision to an object with a Particle System (not event the snapping circle showing up), but it works the other way round (SnapTo set to everything but Increment). This seems to have been around for a long time, but I can't find any report regarding the issue.\n\nAdd a particle system to the default cube (P)\nAdd another primitive, activate collision in the physics settings (C)\nTry snapping C to P, it won't work\nBut snapping P to C works and collision objects can be snapped to each other. C to P only works if you remove the collision or the particle system.\n\n", "Volume overlap clipping\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.2\n\n<tr>\n <img src=\"attachment\" alt=\"Snag_a8e98af\" height=400px></td>\n <img src=\"attachment\" alt=\"Snag_a8e98af\" height=400px></td>\n</tr>\n\nOverlapping VDB/Volume objects create clipping issues where empty space of one volume meets another volume. Changing VDB space from Object to world does not address this issue, neither does changing the float precision from from half to full. Neither does increasing the volume steps, volume light bounces, or the transparency light bounces.\n\nThis has been a consistent issue now since maybe as far back as 2.79, then it could be mitigated by the \"optimise empty space\" being disabled, but now that's seemingly gone, the issue is back and really needs addressing. \n\n\n- Open the attached Blend file\n- head into rendered viewport.\n\nYou will see clipping like in the images attached\nAlternatively, just add a vdb or volume bake to a scene and instance it or duplicate it to overlap with one another and in Cycles you will see the clipping happen\n\nDownload from this link [NEW LINK](p6qN69KLpCFbMHc)\n\nThank you for looking into this\n\nEDIT: Updated link", "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" ]

[ "Why clipping not working\nWith the mirror modifier and clipping option activated 2 verts not snapping. \n\n\n\n[clipping.blend](clipping.blend)" ]

[ "Behavior for mathutils.Vector.rotation_difference when vectors are aligned\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001\n\nBroken: version: 2.93.0 Alpha\nWorked: Never? (tested on 2.79)\n\n```\nimport bpy\nfrom mathutils import Vector\n\nvector_a = Vector((0.0,-1.0,0.0))\nvector_b = Vector((0.0, 1.01,0.0))\nquat = vector_a.rotation_difference(vector_b)\n\nobj = bpy.context.object\nobj.rotation_quaternion = quat\n```\nIn the `rotation_difference` method shown in the script above, when the angle between two vectors is 180° or close, the resulting Quaternion, although pointing in the correct direction, also rotates on another axis.\n\n- Open attached file\n- Run script\nNote that the object did not rotate exactly 180° on one axis\n[rotation_difference_bug.blend](rotation_difference_bug.blend)\n\n", "Principled BSDF Anisotropy black faces\nWin10, 1080Ti\n\nBroken: 2.79\n\nIt seems that using anisotropy produces black odd artifacts under certain mesh circumstances. I don't think this happens often as it seems the actual mesh caused it, possibly by being a little bit too symmetrical? \n\nI suppose often it goes unnoticed so I thought it might be good for someone to investigate upon if there isn't some inconsistency.\n\nRotating the object by the tiniest bit helps (probably helps by something being non 0 ^__^).\n\nMoving random vertices randomly produces different results that are often completely correct or at least 50% correct. Good to try that in Rendered mode.\n\nScreenshot: \n\nBlend: [Anisotropy_Bug.blend](Anisotropy_Bug.blend)", "Gizmo shifting to different value after release with tablet input.\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\nWorked: 2.79 (haven't tested this extensively)\n\nWhen using a tablet to manipulate objects, the gizmo will often pop to a different location. A similar thing happens in the dopesheet when moving the playhead, it will pop to a different (usually very close) frame. I assume this is due to how the tablet input is being interpreted but after exploring and changing every setting I can find, the problem still persists to a certain degree. \n\nBasically, just select an object, choose the rotate tool (not the r shortcut) and use a tablet to rotate on an axis. I've attempted to record this issue in the attached video. [tablet issue.mp4](tablet_issue.mp4)\n\n", "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.", "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.", "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)", "[Collada Export] Exporting with origins in Y-UP results in misalignment of mesh and skeleton + broken animations\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1050 Ti\n\nTested on 2.79, 2.8, 2.9 and 3.1.2\n\nImporting collada models with Y-Up origins (such as those exported from UE4 or Unity engines) and exporting them to collada, then reimporting them again will have severely broken animations in Blender, and in other programs such as 3DS Max and Blender 2.79 the skeleton will be rotated outside of the mesh. Models with the skeleton issue can be manually fixed by rotating the origins of the model by -90 degrees on the X-Axis so that the axes align with Blender's, but that does nothing to fix the animations (rigging is otherwise fine). Global orientation settings in export don't appear to do anything. Oddly enough, looking at the mesh in Noesis, the skeleton is aligned correctly but the animations are still broken, and are broken differently depending on if you fixed the origin alignment or not before exporting. Previously (2.9 and backwards) the skeleton issue could be seen there too.\n\n(1) A Y-UP model\n\n\n(2) Expected animation of that same model\n\n\n(3) The same frame but after exporting and reimporting\n\n\n(4) Original Y-UP model in Blender 2.79\n\n\n(5) Exported (from 3.1.2, but this happens on other 2.8+ versions too. It also happens in 2.79, but only appears with the issue in 2.8+ if exported from 2.79) and reimported model in Blender 2.79\n\n\n(Note - the FBX, which was exported from AssetStudio, was converted to Collada via Noesis - may be relevant?)\n1) Import a model with a Y-Up origin (See YUP_Original.dae)\n2) Export that model to Collada format (Result should turn out like Export_YUP_Test.dae)\n3) Reimport the newly exported Collada model into Blender 2.79, 3DS Max, etc - anything that isn't Blender 2.8 and forward\n4) Animations will be broken no matter what program you import into, but the ones above should have a skeleton rotated 90 degrees out of the mesh\n\nI've attached the original Y-UP collada exported from Noesis, the Y-UP exported from Blender, the \"fixed\" Z-Up exported from Blender, and the original FBX exported from Unity. Please let me know if there's any more info I can give to help.\n\n[M001_InBattle.fbx](M001_InBattle.fbx)\n\n[YUP_Original.dae](YUP_Original.dae)\n\n[Export_YUP_Test.dae](Export_YUP_Test.dae)\n\n[Export_ZUP_Test.dae](Export_ZUP_Test.dae)", "Sculpt Pivot Position is Reset when Exiting the Sculpt Mode\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\n\nSculpt Mode has it's own pivot point, which you can set in 4.0 with new shortcut Shift - RMB. But when you exit the sculpt mode and enter again sculpt pivot points resets to object origin point, it is not saved.\n\n1. Enter sculpt mode on Mesh and choose one of the transform tools (Grab, Scale, Rotate)\n2. Set pivot point with Shift RMB\n3. Go to object mode and back to sculpt mode\n\n", "Curve draw tool: taper setting can lead to wrong handles / random tilt behavior\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.15\n\nBroken: version: 3.3.0\nWorked: never\n\nCurve draw tool: taper setting can lead to wrong handles / random tilt behavior.\n\n[#103879.blend](T103879.blend)\n- open .blend\n- draw quick roundish strokes (all should be good at this point)\n- change Taper Start to something non-zero (I set it to 0.05)\n- draw quick roundish strokes again\n- notice \"wrong\" handles\n\nIf I draw a curve like this\n{[F14175937](image.png) size=full}\n\nthen looking at to neighbors (and their handles)\n{[F14175942](image.png) size=full}\n{[F14175944](image.png) size=full}\n\nMakes me think that while the placement of the points are OK, their computed handles are wrong.\n\nTesting more, it seems this is caused by the `Taper Start` being non-zero:\n[#103879.webm](T103879.webm)\n\n**Original report**\n\nCurve Tilt seems to be broken when using tilt. It could be the configuration of the Tool that's being used and the object settings.\nThese may be changes that were added/ done to 3.2 to 3.4.1. Honestly, I have no idea, that's why i am here.\n\n- What I expected to happen? *Draw with the draw tool and the stroke face the viewport so I can see the thickness of the strokes*\n- What happens instead? *Stroke draws randomly miss-aligned to the view randomly giving the appearance of not drawing the stroke*\n- Why's that bad? *Because the user is forced to correct Blenders miscalculation.* \n\nThe objective is to have the 3D curve face front view without any tilt of the points when drawing using the \"Draw Tool\" in edit mode\". Zup method works best for this in the object settings in 3.2.\n\n1. Create is 3D curve \n**Curve Settings:**\n\n\n2. Edit curve delete point.\n\n3. Front view.\n\n4. Select the drawing tool.\n**Drawing Tool Settings:**\n\n\n5. Draw freely in any direction \n6. 3.2 should be no twisting happening with the tilt of the curve. 3.3 twist method is happening twisting is an issue on every setting when using the draw tool. The twisting happens when using the drawing capability. sometimes giving the impression the stroke is not drawing at all\n\nThings to pay attention to working between the tool and the object.\n1. Pen pressure setting on and off.\n2. The twist method seems more consistent in 3.2 working with the current tool settings. Changing this setting of corrected tilt issues that was thought previously to be 3.2 of the Twist (Curve Tilt) method of the object.\n3. in the Tool settings.\n4. The scale of the stroke when drawing.\n5. When there is a floating window the stroke misbehaves in really extreme ways.\n6. Having the stroke in a poly setting mode help the stroke behavior become more consistent\n7. Setting the stroke to bezier can be really unpredictable\n\nFinally, I am going to share this file around with a few communities to see if someone knows why this problem keeps coming up\n\n**Blend File:**\n[Curve Title Broken.blend](Curve_Title_Broken.blend)\n\n**Demo:****Audio is available** in this file. At around **2 minutes 40 seconds**, you can see the random tilt happen. It looks like i draw a stroke and nothing happens. I then rotate the camera and switch mode to **Z Up to show that it doesn't fix the twist**. This behavior seems to happen from any view. Top, bottom, left, right it doesn't matter.\n[Tilt Issue.m4v](Tilt_Issue.m4v)\n\n", "Draw Face Sets smoothing and Relax Face Sets don't respect locked axes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Actually Windows 11, but I'll leave the auto-generated specs here as well).\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 4.0.0 Alpha\nWorked: Assumably never.\n\nThe Tool ➔ Symmetry ➔ Lock X/Y/Z options don't work when:\n● you use Shift in the Draw Face Sets brush to smooth Face Set borders;\n● you use Mesh Filter ➔ Relax Face Sets.\n\nThis is a handicap when you want to smooth borders and don't want the Face Set border vertices to move in a locked axis direction.\n\n1. Start Blender.\n2. Subdivide the default cube by pressing Control + 4.\n3. Press Control + A ➔ Visual Geometry To Mesh.\n4. Go to the Sculpting workspace, and activate the Draw Face Sets tool.\n5. Draw a Face Set area.\n6. Lock an axis in Tool ➔ Symmetry ➔ Lock X/Y/Z.\n7. Smooth the Face Set's border with Shift. The locked axis isn't respected.\n8. Press Undo.\n8. Activate Mesh Filter ➔ Relax Face Sets, then click and drag across the mesh. The locked axis is again not respected.\n\n", "Use proximity for edit mesh mirror and mirror selection operator\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nIt is hard to select the corresponding vertex on the flipped axis side when the topology is non symmetrical and the corresponding vertices on the flipped axis side is slightly offsetted.\n\nIn order to fix this, it would be great with a \"proximity slider\" that selects vertices on the axis flip side that is within the range of the corresponding coordinate of your current selection.\n\n---\nUI mockup for viewport options\n\n\nUI mockup for operator \"Select mirror\"\n\n---\n\nUse cases below:\n---\n\nCurrent behavior works great when **Topology mirror == True** and the mesh on both side of the axis is connected (and the topology was \"built symmetrical\"). Even if vertices on the axis flip side is slightly offseted.\n\n[topology mirror.mp4](topology_mirror.mp4)\n\n---\n\nCurrent behavior does not work when the topology is built symmetrical, but the topology on both side of the axis is not connected (like the eyes in this case). And the mesh is slightly offsetted on the axis flip side.\n\n[symmetry does not work.mp4](symmetry_does_not_work.mp4)\n\n---\n\nCurrent behavior does not work when the topology is not completely symmetrical and the vertices on the axis flip side is slightly offsetted.\n\n[slightly non symmetrical topology.mp4](slightly_non_symmetrical_topology.mp4)\n\n\n\n\n", "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", "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", "Curves sculptmode: brush Strength (and Strength Pressure) UI inconsistencies\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: -\n\nSculpt curves: brush Strength (and Strength Pressure) UI has inconsistencies between the Toolsettings in the header and the sidebar\n\nfrom the default startp:\n- add Curves\n- enter sculptmode\n- `Add` brush: does not have `Strength` in the header toolsettings (correct, not supported) yet the Brush Settings in the sidebar shows Strength (wrong)\n- `Delete` brush: same as above\n- `Slide` brush: shows `Pressure Sensitivity Strength` in the header toolsettings (has a bug, see #100324, should be removed)\n- all other brushes: shows `Pressure Sensitivity Strength` in the header toolsettings (correct) yet the Brush Settings in the sidebar dont show it (wrong)\n\n{[F13666040](image.png) size=full}\n\n{[F13666059](image.png) size=full}\n\n", "Unify Interpolation In Vertex Paint And Sculpt Mode\nVertex paint squares colors when it interpolates, while the paint tools in sculpt mode do not. This should really be made consistent across both modes. \n\n\n" ]

[ "Axes are inclined. The symmetry is shifted. In File, New , General, Sculting.\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nIn File , New, General, Sculpting. Axes are inclined but 2D axles are correct but you start click on the button alt the problem returns.\nIn File , New, General, Sculpting. The symmetry is shifted but 2D axles are correct but you start click on the button alt the problem returns.\nThese problems occur In File , New, General, Sculpting all modes, Lighting, Color, Backgroung, Mode.\n[Axes are inclined. The symmetry is shifted. In File ,NEW, Geral,Sculting blend.blend](Axes_are_inclined._The__symmetry_is_shifted._In_File__NEW__Geral_Sculting_blend.blend)\n[Презентация Microsoft PowerPoint.pptx](Презентация_Microsoft_PowerPoint.pptx)\nBased on the default startup or an attached .blend file (as simple as possible).", "Axes are inclined. The symmetry is shifted. In File , New, General, Sculpting.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.2\n\nIn File , New, General, Sculpting. Axes are inclined but 2D axles are correct but you start click on the button alt the problem returns.\nIn File , New, General, Sculpting. The symmetry is shifted but 2D axles are correct but you start click on the button alt the problem returns.\nThese problems occur In File , New, General, Sculpting all modes, Lighting, Color, Backgroung, Mode.\n[Axes are inclined. The symmetry is shifted. In File ,NEW, Geral,Sculting blend.blend1](Axes_are_inclined._The__symmetry_is_shifted._In_File__NEW__Geral_Sculting_blend.blend1)\n1.Blender.\n2. File.\n3 General.\n4 Sculting\n5 I wrote everything\n\n", "Axes are inclined. The symmetry is shifted. In File , New, General, Sculpting.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.2\n\nIn File , New, General, Sculpting. Axes are inclined but 2D axles are correct but you start click on the button alt the problem returns.\nIn File , New, General, Sculpting. The symmetry is shifted but 2D axles are correct but you start click on the button alt the problem returns.\nThese problems occur In File , New, General, Sculpting all modes, Lighting, Color, Backgroung, Mode.\n[Axes are inclined. The symmetry is shifted. In File ,NEW, Geral,Sculting blend.blend1](Axes_are_inclined._The__symmetry_is_shifted._In_File__NEW__Geral_Sculting_blend.blend1)\n[Axes are inclined. The symmetry is shifted. In File ,NEW, Geral,Sculting blend.blend1](Axes_are_inclined._The__symmetry_is_shifted._In_File__NEW__Geral_Sculting_blend.blend1)\n\n" ]

[ "No way to edit baked cloth simulation with particle edit mode.\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 680\n\nBroken: 2.82\n\nCan not edit the cloth cache inside of particle edit mode. I am aware of the fade time error inside of options, I am not using fade time I am purely just seeing if what the manual says is possible, editing a cloth sim cache\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. add a cloth sim\n2. Bake cloth sim\n3. go into particle edit mode\n4. no way to edit cloth sim\n\n[ClothEditTest.blend](ClothEditTest.blend) I have uploaded the file I am testing it with", "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", "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", "new boolean difference meshing issue with surfaces\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 775M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: New Boolean code - version: 2.91.0\nWorked: Old Boolean code works\n\nnew boolean code does seem to have mesh intersection issues\nwhen dealing with a solid it works better\n\nintersect to surfaces \nadd a boolean difference modifier\n\nto make it work add a solidify modifier before the boolean modifier\n\n[Boolean Issue.blend.zip](Boolean_Issue.blend.zip)\n\n\n\n\n", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script", "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)", "Sculpt mode: Draw Sharp brush artefacts when using Scene Spacing in stroke settings\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.2.0 Beta\n\n**To reproduce**\nBrush stroke important settings:\n1% stepping, scene stepping\n\nI suppose there is no limiter and with very steep angle step become extremely tight instead to keep constant step.\n\n[2022-05-14_08-04-06.mp4](2022-05-14_08-04-06.mp4)\n\n[untitled.blend](untitled.blend)\n[2022-05-14_08-10-44.mp4](2022-05-14_08-10-44.mp4)\n\n", "Sequencer: transforming strips with overwrite enabled sometimes shuffles\nThe overwrite option sometimes shuffles the strips.\n\nWith `838b6ec48af6fb767089784193d8525c5f5faf13` (current master), and the attached file, the following error can be observed.\n\n- `G` key.\n- Type in `654`.\n- Press Enter to confirm.\n\n... if this doesn't shuffle the strips (so one strip is placed above the others), press Ctrl-Z and repeat the steps above.\n\n[sequencer_overwrite_sometimes_shuffles.blend](sequencer_overwrite_sometimes_shuffles.blend)\n\n", "Panoramic Render in Cycles. Bump bug.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.1\n\nWhen using a material with fine bump and a panoramic camera the bump appears inncorrectly in rendered view.\n\n- Give an object a material with a fine bump (e.g. noise texture 15 detail, .8 roughness. Bump strength 1, distance 1)\n- Bring camera in really close.\n- Set to cycles.\n- Switch camera between panoramic and perspective mode.\n\nPlease let me know if there are any work-arounds, this bug is causing me problems.\nThank you.\n\n", "Automatic weight painting doesn't work if part of mesh is masked\nOperating system: Windows 10\nGraphics card: RTX 2060 Super\n\nBroken: v2.83.3\nWorked: Unknown\n\nIf an object has part of its mesh hidden by a mask modifier (ex: hidden cloth on a character), the automatic weight painting from bones will not work.\n\n- Open attached file (The skirt of the character is already hidden by a mask modifier).\n- Optionally edit the weights to better see the problem\n- Weights -> Assign automatic from bones.\n- Disable the mask modifier and try again\n[Slug.blend](Slug.blend)", "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", "Grid lines showing up when origin is far from mesh\nOperating system: Win 10 Home\nGraphics card: GTX 1070\n\nBroken: (example: 3.2.1, a2d59b2dac9e, master, 2022-07-05, as found on the splash screen)\n\n\nGrid lines showing up when origin is far from mesh but only when bumping out the normals in the shader editor, more testing required. (only happens in cycles regardless of optix/cuda or cpu rendering)\n\nopen the attached blend file and go to camera view, then switch to viewport shading or render an image. you will notice a grid on the surface of the plane in certain areas. And the grid goes away when origin is set to centre of mesh. Or you disable the bump node in the shader editor. Seems to be a rendering bug.", "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)", "Quad remesher produces exotic self-intersecting mesh despite apparently simple source mesh\nOperating system: Ubuntu 20.04.1 LTS\nGraphics card: RTX 2060\n\nBroken: 2.93.1\nWorked:\n\n\nDespite an apparently simple source mesh (manifold and normal conditions are met and mesh is not self-intersecting), *Quad* remesh produces an exotic self-intersecting mesh where an area of faces flow together to form a point that pierces through the resulting mesh.\n\n\n[Meshroom](https:*alicevision.org/) produces meshes with a huge number of vertices that I then clean up in Blender - the final step being to remesh with the*Quad// remesher.\n\nHowever, the results often contain unexpected issues - in particular instead of nice clean quads, there are often points where the quads flow together into a point that then pierces through the mesh.\n\nE.g. here we can see quads flowing together on the right and then piercing through the mesh on the left:\n\n\n\n\nThe corresponding area of the original mesh doesn't seem to have any obvious issues:\n\n\n\nI often encounter similar issues with meshes that I work on - despite having applied serious effort to cleaning up the meshes (using the *Mesh / Clean Up* functionality, a lot of manual cleanup and breaking up any intersecting faces in the original mesh with *Face / Intersect (Knife)* with the *Self Intersect* option).\n\nI've attached a 6MB `.blend` file that contains the cleaned-up original mesh as \"low-poly\" and the remeshed version as \"low-poly-remesh\":\n\n[bust-low-poly-bug-report.blend](bust-low-poly-bug-report.blend)\n\nThe original object looks like this:\n\n\n\nAfter remeshing the problem shown up above can be seen on the right:\n\n\n\nI've also highlighted on the left a weird spike that doesn't appear to correspond to anything in the original mesh but that's probably something for a separate bug report.\n\nThe remeshed object was created by duplicating \"low-poly\", renaming it \"low-poly-remesh\", going to *Object Data Properties*, expanding *Remesh*, selecting *Quad* and setting 40000 as the *Number of Faces* value.\n\nI left all the other settings, i.e. *Use Mesh Symmetry* etc., as they were (but separate experiments with them produced different but still problematic results).", "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)" ]

[ "cloth brush makes holes in my mesh\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83 (sub 11)\n\nCloth brush suddenly started making holes on the mesh. \n[2020-04-05_04-29-05.mp4](2020-04-05_04-29-05.mp4)\n\n[Cloth brush error.blend](Cloth_brush_error.blend)\n\nOpen this blend file and do some strokes.\n\n\n\n" ]

[ "System Hangs while Interacting with the Viewport\nOperating system: Manjaro KDE Plasma\nGraphics card: Intel HD Graphics (Cherry Trail) Atom X7-Z8700\n\nBroken: 3.5.0, 3.4.0, 3.4.1\nWorked: 3.3.2 (Haven't tried newer versions in the 3.3.x series)\n\nBlender causes the entire system to hang periodically while performing any task. Simply rotating the camera or zooming in or out results in the system freezing for minutes at a time. The mouse cursor responds to mouse and touchpad movement, but the system does not respond to mouse button clicks or keyboard input for long periods of time. Neither Blender nor the desktop respond.\n\nWhen rotating, moving or zooming the camera text overlays in the viewport flicker, sometimes the entire viewport flickers, then the system hangs. There are no errors or warnings printed to the terminal\n\nDoesn't appear to be related to a specific file. The issue is present in all blend files and when starting with the default setup.\n\n", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at greenstoneleaf@gmail.com\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Crash when adding materials\nOperating system: Linux-5.18.9-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 630 (CFL GT2) Intel 4.6 (Core Profile) Mesa 22.1.3\n\nBroken: version: 3.2.0\n\nBlender crashes when adding a second material (sometimes you need to add some more to crash it)\n\n1. Open the appended .blend file.\n2. Select the object.\n3. Go to material tab.\n4. Try to add a second material.\n\n[crash.blend](crash.blend)", "Crash using blender_debug_log.cmd and \"Reload Scripts\" in Cycles preview render\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nLoading Blender with blender_debug_log.cmd, it crash immediately when I try to reload the scripts if Cycles is running. This is not happening when launching blender.exe \n\nLaunch blender 2.8 using blender_debug_log.cmd.\nIn the view 3d, choose Cycles as render preview.\nIn the search bar, look for \"Reload Scripts\" and click on it.\nBlender Crash.\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n", "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "Blender 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\n", "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", "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 on Mac when starting with `--debug-gpu` flag\nOperating system: Mac OS Ventura 13.1\nGraphics card: Apple M1 Max\n[system-info.txt](system-info.txt)\n\nBroken: 3.4.1\nWorked: 3.3.2\n\nBlender won't start on a Mac when starting with `--debug-gpu` flag.\nThe terminal output is this:\n\n```\n/Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\nRead prefs: /Users/vollstock/Library/Application Support/Blender/3.4/config/userpref.blend\nWARN (gpu.debug): source/blender/gpu/opengl/gl_debug.cc:165 init_gl_callbacks: Failed to hook OpenGL debug callback. Use fallback debug layer.\nzsh: segmentation fault /Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\n```\n\n\nStart with the flag\n\n```\n/Applications/Blender.app/Contents/MacOS/Blender --debug-gpu\n```", "Crash without warning when opening material properties panel.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon RX 540 Series, ATI Technologies Inc., OpenGL, 4.5.0 Core Profile Context 22.20.16.03.220829\n\nBroken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379f7\nBroken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3\nWorked: no newer version works.\n\nWe get a hard crash without warning when opening the material properties panel in the \"Layout\" workspace right after startup (i.e. with a clean \"General\" new file). Opening the material properties panel in other workspaces causes the same crash.\n\nI suspect that this is an EEVEE problem since opening other properties panels (which do not have the material preview) works fine and opening the material properties panel after having selected the Cycles engine in the \"Render properties\" panel also works fine. Somehow, it feels like being a hardware problem, but I cannot explain why. Interestingly, the device for rendering in the [Preferences][System] is set to \"\"None\" and no GPU's are available in the Cuda, OptiX, HIP, and oneAPI sections.\n\nWhen switching the viewport in the \"Layout\" workspace to \"Viewport Shading\" (i.e. rendered by EEVEE), Blender crashes. When Cycles is selected as rendering engine, then \"Viewport Shading\" works fine.\n\nThe crash happens on my colleague's computer in India to which I have no direct access. Updating graphics drivers is not easily possible due to company constraints. My colleague now uses the Cycles rendering engine by default. Some current file of her was saved with the default EEVEE setting, so she cannot load the file without crashing Blender; I have now modified the file on my computer by switching it to Cycles rendering which bypasses that problem for now.\n\n\n[Based on the default startup]:\n- Open Blender.\n- Select \"General\" new file\n- Open the \"Material properties\" panel in the \"Layout\" workspace.\n- Blender crashes.\n\n[Based on the default startup]:\n- Open Blender.\n- Select \"General\" new file\n- Select \"Viewport Shading\" in the \"Layout\" workspace.\n- Blender Crashes.\n\n[Based on the default startup]:\n- Open Blender.\n- Load a previously stored blend file with EEVEE set as the renderer (and I suspect showing the \"Materials properties panel\" or the viewport in \"Viewport Shading\" mode).\n- Blender Crashes.\n\n", "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)", "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)", "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 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)" ]

[ "blender crashed and now I can't open it\nOperating system: windows 11\nGraphics card: NVidia GeForce 1660 ti\n\nBroken: blender 3.4\nWorked: could not find out how to download different versions of blender but I assume it would work in blender 3.3\n\nbasically I was working on a basic mountain scene and then when I went to render view in the view port it crashed which was nothing unusual but then when I tried to re open it it wouldn't open I didn't get an error or nothing a window just pops up for a split second then go's away. I also just tried opening a new blender project but the some thing happened.\n\nI just try and open blender like normal and it wont let me." ]

[ "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "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 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", "Crash with Boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.1.2 (appears to have been broken since 3.2.0)\n\nBlender crashes when performing an Intersection Boolean between a cube and a bunch of loose faces. (Granted, this is probably not something you should do in the first place, but at least it should be limited to producing a bad result, not a crash.)\n\nI didn't find a crash log, but it's easy to reproduce.\n\n* Load the attached .blend file.\n* Scrub the timeline to frame 209. Blender crashes.\n\n[crash.blend](crash.blend)\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "Blender 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", "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", "Viewport Render crashes on macOS 12.3\nOperating system: macOS-12.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Beta\n\n\nUpdated MacOS to 12.3 (Beta) and going to Viewport Render will cause a full Mac freeze then crash. A hard reboot is the only resolution.\n\nNot sure if this is caused from the latest version of MacOS (12.3 Beta) or if it's the latest version of Blender (3.1Beta). \nI haven't tried with the latest Blender 3.1 Beta build with Monterey 12.2 Beta as this would require me to wipe the computer and reload all apps and files in the OS downgrade process.\n\nOpen default scene and toggle the Viewport Render button.\n\n", "Latest Blender 4.0 not opening\nOperating system: Linux-5.15.0-83-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: blender-4.0.0-alpha+main.b5c89822ac40-linux.x86_64-release\nWorked: 3.6.3 Release Candidate\n\nAfter double-clicking on the \"blender\" starter-folder, it shows what you can see on the picture, before canceling the session\n\nJust try to start 4.0. I guess it's my drivers and noone can confirm, right?\n\n", "Crash when 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)", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "Blender 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", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)" ]

[ "Blender 2.83 beta crashes on startup\nOperating system:Windows 10\nGraphics card: Geforece 310M\n\nBroken: (example: 2.83 beta, 76b3aac802f9)\nWorked: 2.82a\n\nCrashes on start up\nBased on the default startup\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)" ]

[ "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)", "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", "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 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", "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 Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at greenstoneleaf@gmail.com\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Crash when using OCIO v2\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0 Release Candidate\n\nWhen I used OCIO v2 config file and used Cycles for rendering with Optix, it worked for viewport rendering. But if I pressed F12 for final render, Blender 3.0 crashed when the render was finsihing.\nI tried with a few scenes even if the Blender default scene still crashed. Then I tried rendering with CPU, it still crashed.\nI also tried in Blender 2.93.5. It crashed again even if the render didn't start.\nI downloaded the OCIO v2 config file from ocio_v2_demo.html.\n\nWhen I used OCIO v1.2 config file, Blender worked perfectly.\n\n[test-ocio2.txt](test-ocio2.txt)\n- Set the OCIO environment variable to the location of the test-ocio2.txt config file.\n- Start blender and set Cycles as the render engine\n- F12\n\n-----\nOCIO v2 Config\n{[F12676993](image.png) size=full}\n\nBlender 3.0 crash video\n[Crash.mp4](Crash.mp4)\n", "Clicking \"Particle Edit\" mode causes Blender to crash\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.89\n\nBroken: version: 3.5.0\nWorked: I dunno\n\nCan't enter into the Particle Edit mode.\n\nThis issue is probably related to: 106927#issue-96303\n\nIn the sample file, in the Curves Sculpt mode, after converting my Curves (name of the layer: \"my_test_4\") to a particle system, then select the newly converted particle system and enter into the Particle Edit mode, and Blender crashes.\n\n\n\nA sample file is attached. Thank you!\n\n", "Blender freezes when using Texture paint or Weight Paint\nOperating system: Windows 10 Insider build19592\nGraphics card: GTX 1660Ti Max Q 6GB\nProcessor: i7-9750H\nRAM: 32GB DDR4-2666Mhz\n\nBroken: version: 2.83 (sub 11)\nWorked: Never (2.79, 2.8+)\n\nBlender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue.\nMoreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting. \n\nAssigned GPU in Preferences>System>CUDA, but the GPU is been barely used.\n\n[Blender.rar](Blender.rar)", "Crash 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)", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script", "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", "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", "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", "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 crashes/closes while doing simple tasks.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon RX 5600 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.3 30.0.14029.5006\n\nBroken: version: 3.1.0\n\nMy Blender always crashes when i try to export or import a file, also saving. Sometimes when I start to move my mouse the screen starts to flicker white.\n\nWhen I start up blender an I try to import or export any file it will just close and I don't know if it is considered crashing. Also the screen will start to flicker white. This has happened on all versions of blender, even experimental.\n\n" ]

[ "Simulation Nodes: bake UI in simulation node\n_No response_\n\n", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "crash when import fbx\nOperating system: Window 10 pro\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc\n\n\nCrash when I imported fbx file \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "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)", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", "UILayout.emboss missing UI_EMBOSS_NONE_OR_STATUS\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 860M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93 release and earlier revisions of 3.0\n\n`UI_EMBOSS_NONE_OR_STATUS` missing from `UILayout.emboss`. There is new `NONE_OR_STATUS`, but it does not work the same.\n\nHere is the difference:\n * `UI_EMBOSS_NONE_OR_STATUS` in Blender 2.93 makes emboss look `None`, but keeping UI active.\n * `NONE_OR_STATUS` in Blender 3.0 makes emboss `None` and UI not active.\n\n[emboss.mp4](emboss.mp4)\n\n - Run script from attached blend file in 3.0 and 2.93 versions.\n - Try to interact with popover elements.\n\n[emboss.blend](emboss.blend)", "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", "GPU: Workarounds and Device Features checks becoming obsolete\nBlender 4.0 bumped its OpenGL version from 3.3 Core profile to 4.3 Core profile. Some workarounds and optional device features were added to the GPU Backend in order to emulate features that were not available on all platforms.\n\nThis issue contains a list of features, workarounds that we should revisit.\n\n* `shader_draw_parameters` In Vulkan these seems to be supported even on low end devices (displayreport.php?id=23923#features_core_11) we might want to consider making this a requirement, although it is not required by vulkan.\n* `compute_shader_support` is required for workbench-next\n* `shader_storage_buffer_objects_support` is required (#112572)\n* `shader_image_load_store_support` is required. \n* `clear_viewport_workaround` should be solved by the editor, not by the gpu backend. IIRC the VSE has fixed this some months ago.\n* remove `--debug-gpu-disable-ssbo` as SSBO's are required. (#112571)\n\n", "(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", "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", "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", "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", "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 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" ]

[ "screen problems\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 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)." ]

[ "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "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", "Blender 3.0.0 breaks compatibility of rigs with the previous version\nOperating system: Windows 11 Pro 21H2\nGraphics card: Nvidia RTX 3070\n\nBroken: 3.0.0\nWorked: 2.93.6\nBlender 3.0.0 breaks compatibility of rigs with the previous version.\n\n1. Open Agent 327 shot 10_03_B-agent_dodges animation file (10_03_B.anim.blend)\n2. Observe that the rigs are completely broken\n\n\n", "Color picker samples merged (display output) colors on a certain object regardless of \"Sample Merged\" setting\nOperating system: Windows 10 v1909\nGraphics card: NVIDIA GeForce GTX 1660 super\n\nThe bug occured on the latest Steam release of Blender (2.90.1). I also tried to open the project file with the said bug in 2.83 LTS steam beta branch but it happened there too.\n\nWhen trying to texture paint a certain project it ignores the \"Sample Merged\" setting and always picks the display output color, while other objects don't share this problem. \nIt happens regardless of the material or texture I'm editing, it seems to be tied to a single object. For example, If I create a cube and assign the material which the bugged object uses color picking works fine with it, and if I assign any other material to the bugged object it still samples display output color regardless of the settings.\n\nI'm sadly not sure how to reproduce it. Though I appended the bugged object to a fresh file: [color_picker_thing.blend](color_picker_thing.blend)\nIt's system info:\n[system-info.txt](system-info.txt)\nI separated it so you wouldn't have to dig through the mess that is my main project file :D. It retained it's weird inabillity to pick colors though.\n\nI couldn't find a solution to this when I tried to google for it, so my only assumption left here is it being a bug. I'm sorry in advance if something I said isn't clear. If needed, I can provide a whole project or try and provide more specific information if what I wrote here isn't enough as soon as possible.\nCheers!", "Collada wrongly export assumes bind_mat is a float array\nOperating system: all systems\nGraphics card: all cards\n\nBroken: 3.1.0 and 3.3.0 alpha \nWorked: none\n\nIf you create the bone custom property \"bind_mat\" with Python or with the GUI, blender generates a double - [ ]. But the collada export only works with float [].\n\nCreate any armature and mesh.\nCreate a new bone custom property \"bind_mat\" in the property panel. \nSet a breakpoint in collada_utils.cpp bc_get_property_matrix(). \nExport your mesh \"sl+open sim rigged\" \"Keep Bind Info\". \nIf you change the cast from float* to double* you get reasonable values.", "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", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "Using another Mesh for Texture Indices (Texture Space / Generated Texture Coordinates)\nOperating system: Windows 10\nGraphics card: Geforce GTX1060\n\nBroken: 2.80.74 and 2.91.0 Beta\nWorked: Blender 2.79b Date: 2018-03-22 14:10 Hash: `f4dc9f9d68b`\n\n\nThe option \"Texture Mesh\" in the \"Texture Space Panel\" of the \"Object Data Properties Tab\" has no effect if the mesh does not have a deform type modifier.\n\n|\n| -- |\n|File is [here ](GeneratedTextureCoordinates4.blend?dl=0).\n\n\n- Open attached file - (Note that the geometry of one mesh affects the texture coordinates of the other)\n- Go to the modifiers tab and disable or delete the modifier\nTexture Mesh has no effect.\n[texspace_texture_mesh_bug.blend](texspace_texture_mesh_bug.blend)", "Bug with environment texture\nOperating system: Windows 10\nGraphics card: Nvidia GeForce RTX 3050 Laptop GPU\n\n3.6.2\n\nAfter I checked and unchecked \"Open Shading Language\" checkbox Blender crashed, after that I opened my project and turned rendered viewport the environment texture become a one solid color, and as I was rotating my camera it was changing the color.\n\nBased on an attached .blend file you can go to the Render viewport and take a look at this error.\n\n", "Blender 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", "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", "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", "Selection not transfering to paint mask (vertexpaint, weightpaint, texturepaint) when a triangulate modifier is present\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.81\n\nBroken: version: 2.92.0\nWorked: -\n\nIf you face select on edit mode, it will carry your selection to weight paint face select or texture paint face select or etc.\nBut if you have triangulate modifier on it will not carry it over.\n\nI did not know this and there was not error message about this anywhere on blender.\n\nLoad this file: [faceselect001.blend](faceselect001.blend)\nyou see some faces selected with triangulate modifier on.\ngo to weight paint or texture paint and you see none.\n\nI know this might not be a bug but how software works BUT for a common artist, at least adding a message that it will not carry over selection would have been nice, or disabling triangulate on view automatically when you go to those modes.\n\n", "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", "Support Alembic export/import of curve objects\nI created this issue as requested [here ](T51195#430327).\n\nWhile the export of animated mesh objects works quite well, exporting and importing curve objects does not work as expected at the moment.\n\nWhen exporting curves there are two main options:\n- Export as curve\n- Export as mesh\n\nBoth of these are very useful. Depending on the specific setup it might not be useful to export a curve as curve but rather as mesh. Being able to export as mesh should always be an option.\n\nI created a little test file that includes a curve object with multiple animated properties and modifiers: [curve_export_test.blend](curve_export_test.blend)\nSome modifiers implicitly convert the curve into a mesh, so when the user wants to export as a curve, it should (if possible) evaluate all modifiers until the curve is converted. If it is not possible to apply only some modifiers, it should still be possible to only export the curve before any modifier is applied (next to the option to export the whole thing as a mesh).\n\nAlso, keep in mind:\n- Curves can consist of multiple splines.\n- The amount of splines per curve object can change over time.\n- The amount of points in a spline can change over time.\n- Curves and spline points have quite properties have quite a few attributes that need to be considered when exporting as curve (bevel radius, ...).\n\nIf I had to choose what to develop first, mesh or curve export of curve objects, I'd vote for mesh, as it allows for more flexibility. Additionally I imagine it to be easier to develop." ]

[ "Error end Export\nOperating system and graphics card\nFX 8350 8 core\n16 gb Ram \ngtx 960 nvidea MSI\nwindows 10\n\nBroken: 2.79\n\n\nHi, I'm talking about a problem that came up in blender. I have been working on a project and I want to export the texturizing models but the problem is the following. when I export the model and I open it in other software, it does not export anything to me or it makes a mistake, I already try with all the formats and none of them export it well, it's the first time it happens to me . I do not know if it is because of the new version of blender or if I activate something that does not allow me to export the mesh (also try with previous versions). I do not know if it is part of the problem. please respond to this message.\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)", "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", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Crash when switching from solid to rendered view\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\n\nI have a scene about 1.7GB in size with 4K textures but renders in 2K using simplify, blender crashes when I open the file > hit F12 and render the scene then close the render windows and switch to render view > it starts compiling then blender closes, in the past it would show out of memory this report: \n\n105522#issuecomment-904934 \n\nThis issue happens only when persistent Data is active\n\nunfortunately I can't share the file at the moment. \n\n\n\n\n", "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)", "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", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Blender crashes when I try to subdivide my model\nOperating system: Windows 11 Pro 64-bit, 12th Gen Intel(R) Core(TM) i9-12900KF (24 CPUs), ~3.2GHz\nGraphics card: NIVIDIA GeForce RTX 3070 Ti\n\nBroken: 3.6, latest version\n\n\n\n- Open Blender, Open File\n- Go to Preferences, Turns off GPU Subdivision\n- Change to CUDA and tick Graphics Card Box\n- Goes to Modifier, Click Subdivision Surface, Processing, Crashes\n\nTo give a bit more context, my current model only has 160000 vertices which I think is quite little? But still it cannot subdivide and crashes whenever I click the subdivide option in modifiers.\n\n", "Entire system freezing while using NLA in Blender 2.91 and newer (Mesa only?)\nOperating system: Fedora 33\nGraphics card: Intel HD Graphics 520 (Mesa 20.2.4)\n\nBroken: 2.91\nWorked: 2.90.1\n\nBlender randomly freeze entire graphics system. After freezing, last 2 frames is flickering if you move mouse. I can even save my work with CTRL+S, but after that i need to restart my computer. Setting INTEL_DEBUG=reemit environment variable fixes the issue.\n\nMethod 1\nAdd a few keyframes.\nScroll up and down in the NLA editor.\n[blender-freeze-2.mp4](blender-freeze-2.mp4)\n\nMethod 2\n\nJust do something, even in Solid view, even in Video Sequence editor. I don't know how to reproduce, it happens after 10 minutes of work. Also i notice some glitches in VSE with image strips. Also bug with Depth of Field was fixed in this version, probably this fix relate to this bug.\n\nBug with depth of view that was fixed:\nT77828\n\nIssue with VSE\n[blender-vse-artifacts-1.webm](blender-vse-artifacts-1.webm)", "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", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "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 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 on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)" ]

[ "Crash after 10 seconds\nI just downloaded Blender 2.79 and tried to start it. Once i start it i could only use the program for only 10 seconds before it crashes. I have a MSI Windows 10 laptop and it has a lot of storage because i just started using my laptop since last month, so it doesnt have so much on it for the storage usage. i deleted blender and re-downloaded to see if it happens again and it still does the same thing. If anyone could tell me why this happens, please tell me because i want to teach myself the basic 3D animations so i could proceed and work hard to get a career of it" ]

[ "Crash (memory use after free) on freeing RigidBody world\nReproducible with current master, probably there since forever.\n\n# Steps\nWith an ASAN build:\n\n- Open `rigid.anim.blend`\n- Close Blender\n\n[rigid.anim.blend](rigid.anim.blend) \n\n(Case found while working on #86379 (When using \"Append\" rigid body objects + empty constraint, none of its constraints work.))\n", "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", "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)", "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", "UDIM tiled images with generated contents dont render in Cycles\nOperating system: Windows 10 pro 64 bit, AMD Ryzen 5 3400 G with radeon vega graphics, 16 gb ram\nGraphics card: nvidia GTX 1650 super\n\nBroken: 2.91.0, 0f45cab862b8, master, 2020-11-25 \n\n\n\nworking on the new udim mode I was proving my uvs with a uv grid and when i went to try to get a render i note that when you change to cycles in the render engine the texture is lost and dont appears in the render but in eevee it works fine. the error only happen when you try to use cycles.\n\n*Open the file\n*Go to render preview mode\n*Change to cycles in the render engine section", "Correct link is shown as invalid\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIn the composer, after some actions, the link is displayed as incorrect, although there is no reason for this.\n\n**Exact steps for others to reproduce the error** \n\n0. Factory settings file (optional).\n1. Switch render engine to Cycles.\n2. Enable any `Scene > ViewLayer > Passes`. For example, this would be `... > Data > UV`.\n3. Enable the compositing nodes and connect the new socket to the \"Composite\" node.\n4. Switch render engine to Eevee.\n5. Make a Render.\n6. Switch render engine to Cycles.\n\n\n\n", "Crash 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", "Crash when rendering animation in Workbench (with workbench shadows)\nOperating system: Windows 10 20H2\nGraphics card: Nvidia GTX1080\n\nBroken: 2.93.0\nWorked: 2.92.0\n\nWhen rendering the attached file as animation Blender ends without notice after the second rendered frame.[mirandaAnimNeu3.blend](mirandaAnimNeu3.blend)\n\nOpen the file mirandaAnimNeu3.blend. Click Render | Render Animation.\n\nThe animation is set to start at Frame 466 and to last until frame 4900. After rendering of frame 467 Blender crashes without notice. No crash file is created. Blender just ends.\n\nBoth rendered images are saved. It is interesting to note that the earlier images of this animation are rendered within seconds but the render times of the last images require minutes although no noticeable content becomes visible. Yesterday I have rendered all 4900 frames at 50% size without anti-aliasing, which worked fine. Each image rendered in a second or two.\nSorry that the blend-file is so big...", "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", "Smoke and Fire simulation bug\nOperating system: Mac osx 10.15.6\nGraphics card: AMD Radeon Pro 5500M 8 GB\nIntel UHD Graphics 630 1536 MB\n\nBroken: 2.90.0 (202-08-31)\n\n\nBlender crashes while trying to bake a fire + smoke simulation in 128 resolution divisions... Sometimes it works. Mostly it doesn't.\n\nAttaching the file.\n\n[Blender Bug copy.rtf](Blender_Bug_copy.rtf)\n\n[fire.blend](fire.blend)", "Error message and unable to edit a skeleton when using a library override armature\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: No idea.\n\nBlender generates an error when you attempt to enter edit mode on a library overriden armature. There's no description of what the error is or if there is some extra step to make it work. Hopefully this isn't one of those, \"works as intended issues,\" because then there's no way to make multiple characters share an updateable base rig.\n\n\n- Add an armature, enter edit mode, extrude out a few bones.\n- Save the file and open a new scene.\n- Link in the armature you just created.\n- Make the armature a library override.\n- Try to enter edit mode. Should get an error.\n\n", "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", "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`.", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "Dither affects 'File Output' image even when \"save as render\" is disabled \nThe dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when \"save as render\" is disabled, when disabled it should not touch the output image, when \"save as render\" is enabled it makes sense to dither.\n\n\nnoise in output file\n\n\n- Open attached file\n- Optionally change the Dither in {nav Output Properties > Post Processing}\n- hit render\nIt will generate an image in the directory pointed to by the node `File Output`.\nNote that Dither also affects this image.\nMaybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data.\n\n[gradient.blend](gradient.blend)" ]

[ "Render permission denied\nI am working with the file output node and rendering with the animation button, but when rendering frame 1 an error arises (Render error (Permission denied) cannot save: '0002.png'). It seems that Blender does not have permission to save in the folder, but the folder has no restrictions.\nI am using the version of Blender 2.79 and a Macbook pro." ]

[ "Crash when rendering animation\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\n\n\nI was rendering a simple camera animation overnight, Blender crashed about 2/3rd the way through. Here's the crash log.\n", "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)", "Render Error using the HIP backend\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 7900 XTX ATI Technologies Inc. 4.5.0 Core Profile Context 22.40.51.06.230425\n\nBroken: version: 3.6.0 Beta\nWorked: Unknown\n\nMessed up renders in multiple of the common Blender Demo files. Classroom being the most obvious.\n\nStarting blender and running the render with the HIP or HIPRT backend using the 7900 XTX GPU causes the render errors in the attached \"broken\" images. Running and finishing a HIPRT render targeting the CPU results in a proper render, and fixes this for subsequent GPU renders with both HIP and HIPRT, see \"non-broken\" images.\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Blender crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "Blender 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 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", "Crash with lineArt modifier and Armature\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nExperienced with 2.93.2\n\nHaving a line art object in the scene applied to an object 'A' when there is an armature on object 'B' makes blender very unstable. A simple scroll in the timeline will crash instantly.\n\n\nIn the attached file, what I did : \n- Create a cube, subdivided along Y, add a simple armature, keyframe it with a simple motion.\n- Duplicate the cube, apply the armature.\n- Select the second cube, shift-a -> Object Line Art\nFrom there : \n- Scroll the timeline... Crash.\n\nIf I delete the animated cube, scrolling works fine. Disabling it in viewport as well.\n\n\nI also tried adding a simple cube, instead of duplicating the initial \"armatured\" cube, and adding the Object Line Art to it, but the same crash occurs.\n\n[LineArtCrash.blend](LineArtCrash.blend)\n\n", "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", "Lots of animation-related operators do not check if the data is editable or not\nMany animation-related operators do not do any check whether the data-block they operate on is linked, liboverride or fully local data. This seems to affect in particular operations from the 3DView (like key insertions), and in the NLA (like adding new tracks, duplicating strips, etc.).\n\nE.g. one can insert keyframes on a linked object (ie create animdata for that linked object, a new local action, and assign that local action to the linked object!).\n\nRelated to issue reported in #98686 (Cant rename local NLA tracks within a local library override data-block.).", "Serious problems with visibility when linking a character\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3\n\n\nwhen linking a collection containing a character model, rig, etc., oddities occur with the visibility of the armature: when the overlays are turned off/ on, the armature is not displayed until some event occurs (this bug applies to the file where the model is located). undo ignores hiding bones (scene with linked and override character) for clarity, two animation files will be attached. in both, sometimes both of these bugs occur, while it is absolutely unpredictable\n[2022-09-16 02-20-35.mp4](2022-09-16_02-20-35.mp4)\n\n[broken_7.zip](broken_7.zip)\n\nfile with character in broken_7/stalker/\nfiles with animation in broken_7/3d_projects/tests/animation/\n", "Blender 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)", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Crash at the end of preview generation for a deleted datablock\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: -\n\nBlender crashes if you trigger the generation of a preview for a data block and then delete the data block itself. Obviously, the preview data is generated, but since the datablock itself no longer exists, I get an `EXCEPTION_ACCESS_VIOLATION` and a crash.\n\n\nRun simple script in attached *.blend file.\n\n", "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" ]

[ "A problem with armatures in Blender\nComputer: MSI K9N6PGM2-V with AMD Athlon simple-core processor\nRAM: 2GB\nOS: Debian 9 with 9wm interface\nGraphics: NVIDIA GForce\nBlender version: 2.78\n\nGood evening,\nI have a problem with the blender version (2.78).\n\nI was editing the armatures for the character, but unexpected, when i was selecting a bone from the armature, Blender crashes!, and leaves an unexpected error code:\n\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.armature.select_all(action='DESELECT') # Operator\n\n# backtrace\nblender(BLI_system_backtrace+0x30) [0x55b10c15fec0]\nblender(+0x1023101) [0x55b10b708101]\n/lib/x86_64-linux-gnu/libc.so.6(+0x33030) [0x7f17f159e030]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x47334d) [0x7f17bd6f934d]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x480a03) [0x7f17bd706a03]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x480add) [0x7f17bd706add]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x1dd004) [0x7f17bd463004]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x1dd250) [0x7f17bd463250]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x143bbd) [0x7f17bd3c9bbd]\n/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x1446af) [0x7f17bd3ca6af]\nblender(GPU_select_end+0x76) [0x55b10bd36fb6]\nblender(view3d_opengl_select+0x110) [0x55b10b8039a0]\nblender(+0x12e07c6) [0x55b10b9c57c6]\nblender(ED_armature_select_pick+0xab) [0x55b10b9c618b]\nblender(+0x11184ce) [0x55b10b7fd4ce]\nblender(+0x102af12) [0x55b10b70ff12]\nblender(WM_operator_call_py+0x5a) [0x55b10b71082a]\nblender(+0x1450803) [0x55b10bb35803]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyCFunction_Call+0xc9) [0x7f17fa4c9259]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x8039) [0x7f17fa5fa6a9]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0x263f94) [0x7f17fa6bbf94]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyEval_EvalCodeEx+0x23) [0x7f17fa6bc073]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0xf7665) [0x7f17fa54f665]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyObject_Call+0x47) [0x7f17fa62b9a7]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0x21f8cc) [0x7f17fa6778cc]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyObject_Call+0x47) [0x7f17fa62b9a7]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0x8c57d) [0x7f17fa4e457d]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyObject_Call+0x47) [0x7f17fa62b9a7]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x3bed) [0x7f17fa5f625d]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0x263f94) [0x7f17fa6bbf94]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyEval_EvalCodeEx+0x23) [0x7f17fa6bc073]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(+0xf7568) [0x7f17fa54f568]\n/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0(PyObject_Call+0x47) [0x7f17fa62b9a7]\nblender(+0x1445afe) [0x55b10bb2aafe]\nblender(+0x19f0cfc) [0x55b10c0d5cfc]\nblender(+0x102ae0f) [0x55b10b70fe0f]\nblender(+0x102c35d) [0x55b10b71135d]\nblender(+0x102c79f) [0x55b10b71179f]\nblender(+0x102cdb6) [0x55b10b711db6]\nblender(wm_event_do_handlers+0x3c5) [0x55b10b712195]\nblender(WM_main+0x18) [0x55b10b708ea8]\nblender(main+0x37e) [0x55b10b6c600e]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f17f158b2b1]\nblender(_start+0x2a) [0x55b10b704d7a]\n\n\nI need to resolve this, because I want to return to create armatures in blender\n\nThanks\n\nEdwin Andres Martinez Suarez\n```\n\n```\nforeach ($list as $item) {\n```\nwork_miracles($item);\n```\n}\n```\n```" ]

[ "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.", "Texture Paint tools lead to incorrect colors on bright HDR textures in 3D\nOperating system: Linux-5.12.0-19.1-liquorix-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 5700 (NAVI10, DRM 3.40.0, 5.12.0-19.1-liquorix-amd64, LLVM 11.0.0) AMD 4.6 (Core Profile) Mesa 21.0.1\n\nBroken: version: 2.93.0\nBroken: version: 3.0.0 Alpha\nWorked: N/A\n\nI am trying to touch up an HDR lightmap using the Texture Paint mode.\nAttempting to soften, smear or clone HDR images in 3D view in Texture Paint mode will lead to pixel values being clamped up to 1.0, unexpectedly removing bright spots. 2D view is not affected and the tools behave as expected. See video:\n[blendertexpaint.mp4](blendertexpaint.mp4)\n\nI have found that this line is responsible for this issue. Commenting it out fixes the problem.\nimageprocess.c#l219\nLine 219: `clamp_v4(outF, 0.0f, 1.0f);`\n\nI am unsure about the purpose of this line, or any unintended consequences of removing it. Someone else needs to take a look.\n\n1. Assign an HDR texture to an object's material.\n2. Enter Texture Paint mode\n3. Attempt to use the Soften, Smear or Clone tools to edit the texture in 3D view, in spots where the value of a pixel's R, G or B component is greater than 1.0\n4. The bright spots will unexpectedly become dark as they are touched by the tools.\n[Sample.blend](Sample.blend)\n\n", "Color swatch in grease pencil in the topbar is half transparant, showing whats underneat\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\n\nThe color swatch in the top bar in Grease Pencil draw mode is half transparant, showing what is in the viewport underneath. I don't want my color swatch to show anything but the solid color that I've chosen. \n\n\n\nPS\nThis is also present in the latest 3.6 beta", "Armature Object's \"Display As\" does nothing\nOperating system: Linux-5.3.0-26-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 6)\nWorked: version: 2.79 release.\n\nWhen I add an armature and change the Viewport Display Mode, nothing happens.\n\n\nOpen the blender;\nDelete the default objects;\nAdd an Armature, single bone;\nIn the Properties Panel, Object Properties, Viewport Display:\nChange 'Display As' to anything, it doesn't work.\n\n\n\n", "Transform Node Messes Up Alpha Channel Manipulation\nArch Linux\nNvidia 750ti\n\nBroken: 2.79 (Tried 2.8 as well and I have the same issue)\n\nAs referenced here:\n4\n\nWhen I take an image in the compositor and scale it up 2x or whatever and then separate the RGBA and dilate/erode the alpha and use that to set the alpha on the image, it only works within the size of the original image and not the scaled up image. Also even if I use the R, G, or B, it still only uses the size of the original image and not that of the scaled up one.\n\n\n\nCropped if I try to mess with the alpha after a transform.\n\n\nUncropped if I mute my changes to the alpha.\n\n\nAlso I believe that if you scale down\n\n[dilatecropissue.blend](dilatecropissue.blend)\n", "Grease Pencil Color Management inconsistencies\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.81 (sub 14)\nWorked: (optional)\n\nBlender CM for GP is inconsistent between viewport and render. Viewport is not affected by Filmic, but render is.\n\nIn a new file, add a GP Suzanne. Change viewport to RENDERED. Render and compare colors/contrast: they are different.\nChange CM from Filmic to Standard. Render and compare again: they match.\n\n\n\n\n", "32 bit Float Image Different Value In 3D Viewport And Image Editor\nOperating system: Linux-6.0.19-3-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.85.05\n\nBroken: version: 3.5 and 3.4.1\nWorked: ¿?\n\nThe 3d viewport and the image editor have different values with 32 bit float images unless you change the image color space to any other but non-color \nis this normal?\nAm I doing something wrong?\n\n1. Create a new file\n2. Create any object\n3. Change to texture paint mode\n4. Create a 32 bit image (displacement, not base color, colorspace to Non Color) \n5. Set the brush color value to 0.8\n5. (Make sure Color Management > Display device is something else than `None`)\n6. Switch to Texture Paint workspace, open the image in the Image Editor\n7. Compare strokes in the Image Editor vs. 3DView (they are not the same color)\n6. While hovering over the image/mesh, press 's' to sample the color.\n\nThis happens only in textures with non-color color space. \nI tried factory settings with no difference.\n\nThank you.\n\n", "Metal backend: View Port drawing issue with face orientation\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API Intel(R) Iris(TM) Plus Graphics 1.2\n\nBroken: version: 3.5.1, 3.6-beta, 4.0\nWorked: with OpenGL backend\n\nWhen enabling \"face orientation\" in the view port the display does not update until I rotate the model. When rotating the model the face orientation colour overlay display is broken.\n\nSee attached screen movie showing the issue.\n\nTo reproduce:\n1. start with a new default scene\n2. enable face orientation overlay from view port overlays menu\n3. rotate the cube\n\nThis was observed using the default startup cube.\n\n", "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", "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", "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", "Using the alpha channel of an image texture corrupts RGB Channels in both EEVEE and cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nUsing the alpha channel of an image texture affects RGB Channels in both EEVEE and Cycles when connecting the alpha channel to another arbitrary node.\n\n\n- See attached .blend files for Eevee and for Cycles\n\n|Blender file that demonstrates that behavior in EEVEE:|The same behavior manifests itself a little differently in Cycles:\n| -- | -- |\n|[Plane_test_file_EEVEE.blend](Plane_test_file_EEVEE.blend)|[Plane_test_file_cycles.blend](https://archive.blender.org/developer/F12860576/Plane_test_file_cycles.blend)\n\n\nAs it seems connecting the alpha channel somehow unpremultiplies the image.\nAll images are stored as openexr, the image alpha is therefore set as premultiplied.", "Grayscale TGA image renders incorrectly in the linear colorspace\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.4.1, 3.5, and 3.6 hash: 498287bca0e2\nWorked: version: 3.3.5\n\nWhen using a grayscale TarGA (tga) image texture in the linear colorspace, the material is rendered incorrectly in the 3d viewport. I attached two images of how it looks in 3.3.5 and 3.5.0.\n\n\n\n\n\n1. The image must be a grayscale tga file with no alpha channel (I attached one - test.tga),\n2. Create an image texture node, load the image and set \"Color space\" to \"linear\",\n3. Connect the node to the \"Base Color\" input of the Principled BSDF shader node.\n\nReverting changes made in commit 37533cd6cb0fcd6e92906cfcec911330df27f52c fixes the issue.\n\n", "Burned Out Screen Space Reflections in Eevee Viewport - Nvidia GT 750M\nOperating system: macOS 10.14.3\nGraphics card: NVIDIA GeForce GT 750M 1024 MB\n\nBroken: 2.90.0\nWorked: 2.79\n\nIn some cases I detected that the Screen Space Reflections in Eevee Viewport gets out of control.\nA few seconds after switching to the viewport (even when viewport samples are set to 1) the issue kicks in and – as the sampling continues – an increasing percentage of the reflections get totally white.\n\n\n\nThe renders are correct.\nSurfaces affected by reflection planes are correct.\nHiding the chandeliers meshes solves the problem. Switch tab and back for this to work.\n\nI was able to strip down the scene and identify the source of the problem: Originally I set up the glass material with \"multiply\" blending. This was converted (when opened with belnder 2.82 alpha) to a \"Shader to RGB\" and a \"Transparent BSDF\" node. [1]\n\nThe \"Shader to RGB\" causes the problem in 2.82.\nThe \"multiply\" blending of the material causes it in 2.8.\n\nOpen the attached file.\nSwitch to LookDev or Rendered viewport.\nWait.\n\n[Chandelier.blend](Chandelier.blend)", "Eevee 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(" ]

[ "3D Viewport Header Alpha setting no longer works in 3.1\nOperating system: Linux-5.8.0-44-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14739 Core Profile Context 21.30\n\nBroken: version: 3.x , 3.1.2\nWorked: 2.93.8\n\n 3D Viewport Header Alpha setting no longer works. 3D Viewport Header can no more be made transparent.\n\nOpen blender Preferences >3D Viewport > Theme Space. Try changing the Alpha value of the Header setting. No effect.\n\nFrom what I can remember this broke when the Active Viewport Colors were inverted. Header becomes lighter when mouse over. This looks really awful and has been an issue for a while. \n\nT92779\n", "UI: Can't make 3d viewport header fully transparent in 3.0\nOperating system: Windows 10 \nGraphics card: 1080, 1070\n\nBroken: blender-3.0.0-beta+v30.11392829adfe\nWorked: 2.93\n\nI really like my header to be completely transparent so that I can only see buttons on top of my viewport, freeing some more space in vertical area to preview more space on the scene I am working. I thought in all previous 2.8 and 2.9 iterations it was ruled out that free vertical space in viewport is more important as we use widescreen monitors. Now when I change my alpha to 0 in header option in 3d viewport theme preferences header is not becoming completely transparent, but at the same time for some reason I can still change it's color. That feels weird and inconsistent and a bit claustrophobic, I hope this trend of minimizing view-port area by default will not continue. \n\nHere's a screenshot how it looks now in 3.0:\n\n\nChanging Alpha value doesn't affect transparency of the header, but you can change color:\n\n\nHere's a screenshot how it's \"supposed\" to look and it looks in 2.93:\n\n\n1) Go to preferences\n2) Theme space\n3) 3d viewport\n4) Open Theme Space tab\n5) Try changing alpha and color values:\n" ]

[ "A combination of shader nodes causes lack of material emission at any brightness (Cycles)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.0(tested as well on 3.3.0 and 3.5.0 alpha)\nWorked: (none)\n\nA difference of bevel node and normal coordinates produces no light at any emission level. Clipping the result due to suspicion about negative brightness has no result.\nNote: adding any value to the result adds corresponding emission, but despite visuals, brightness from combination above does not.\n\n\n- Open attached file\n[cycles_where_is_emission__bug.blend](attachment)\n\n\n", "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)", "Exact Boolean (Union & Self Intersections -- to remove inside geometry) bad performance/memory footprint\nOperating system: Linux-5.15.0-67-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.6\n\nBroken: version: 3.5.0 Beta\n\nI have a group of nodes that gets rid of internal geometry by creating a \"mold\" of an object.\n\nBut it crashes on some meshes and not on other meshes and the crash doesn't give any real information why.\n\nIs there a work around for this?\nNodes works with certain meshes and crashes with others.\n\nWorking mesh and blend file.\n\n**Left side shows internal / overlapping geometry and Right side is free of this after using node network.**\n\n\n\n[doesn't crash.blend](attachment)\n\n\nCashes when I **click the switch node to enable it** (**see red arrow**).\nCrashes in 3.4.1 and 3.5.\n\n\n\n\n\n[this one crashes.blend](attachment)\n\nCrash text files attached below\n\n\nIs there a work around for this?\n\n", "Breaking nodes API changes for 4.0\n- [x] Remove `Node.width_hidden`\n- [ ] Complete \"Spline\" to \"Curve\"/\"Curves\" rename in geometry nodes\n- [ ] Stop storing node locations relative to their parents\n- [ ] Use a separate type for internal links (in RNA too) (see [D16960](D16960))\n- [ ] Use a separate type for node group interface inputs and outputs and node sockets\n- [ ] Use dynamically allocated `char *` array to store string socket default values", "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", "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", "Geometry node - setting lacunarity to 0 crashes Blender (musgrave texture)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.2.2\n\nIn a fairly simple geonode tree, trying to set lacunarity to 0 will crash Blender instantly.\n\n- Use attached Blend.file\n- In the 'set position' branch, try to set 'musgrave texture' lacunarity to 0\n- Crashes everytime for me\n\n[Geonode attribute.blend](Geonode_attribute.blend)", "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", "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", "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)", "Cycles: overlapping VDBs cause rendering artifacts\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.2\nWorked: version: 3.0.1\n\nFirst reported here: #97062\nOverlapping VDBs cause black rendering artifacts.\nThis is likely a known issue or related to a known issue.\nFrom the release notes for 3.1: [Ray Tracing Precision](Cycles#Ray_Tracing_Precision)\n>Many artifacts from rendering small, large and far away objects have been eliminated. There will always be object scales where numerical precision becomes a problem, but it's further out now.\n>\n>There can still be artifacts with rendering overlapping geometry, in some cases more severe than before. Such overlapping geometry should be removed, or have a small distance added in between.\n\n\n|3.0.1|3.1.2 CPU|3.1.2 GPU|\n| -- | -- | -- |\n||||\n\n1) Import a VDB volume.\n2) Duplicate the volume without moving it.\n3) Render with Cycles.\n\nHere is the test file:\n[#97094.zip](T97094.zip)", "Geometry Nodes Inputs `is_animatable` Property Incorrectly Returns False\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0 Alpha\n\nGeometry Nodes inputs' context menus ([WM_MT_button_context ](bpy.types.Menu.html#extending-the-button-context-menu)) incorrectly show the inputs' `is_animatable` property as `False` when the property does accept keyframes (see screenshot, attached).\n\n\n - Open the attached .blend file (attached, below)\n - Run the script in the Text Editor\n - Right-click the Input property of the Cube's Geometry Nodes Modifier\n - Open the System Console to see the `is_animatable` property of `context.button_prop` is `False`\n[is_animatable.blend](is_animatable.blend)", "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.", "Cycles/Eevee texture nodes for modifiers, painting and more\nWith Blender Internal being removed, we have an opportunity to support the same set of textures for Cycles, Eevee, modifiers, particles, painting, compositing, etc. So we plan to port the relevant Cycles / Eevee shader nodes to Blender C code, and make those the new texture nodes that can be used throughout Blender. Blender Internal textures can be removed then, and we can extend the Cycles / Eevee shader nodes to add any important missing features from them.\n\n* Some nodes like color ramps, RGB curves, and similar utilities are already there.\n* Texture nodes like image, noise, voronoi need to be ported.\n* Geometry, attribute and similar nodes as well. These are the most complicated since they access the mesh geometry.\n* Some nodes like BSDF, Mix Shader, Bevel, .. would not be supported.\n\nFurther we need a good UI for this in the texture properties.", "Broken edge lines with boolean and freestyle\nOperating system: Linux-5.0.7-200.fc29.x86_64-x86_64-with-fedora-29-Twenty_Nine 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\n\nBroken: version: 2.80 (sub 58)\nWorked: (optional)\n\n\nI'm seeing two different issues:\n(1) There is a broken line in the edge (see attached render). Rotating the object for a different angle, changing the boolean by moving one of the cylinders, etc. still causes broken lines, sometimes on multiple edges. Also, using the simple surface (without the toon shading setup of Shader-to-RGB and gradient) still causes the broken line. \n(2) The second possible issue is that while Eeevee renders correctly otherwise, Cycles also has the broken line and in addition seems to be rendering incorrectly for the toon shade effect - i.e., all solid color vs. multiple colors expected, see attached render. \n\nCreate a cube and two cylinders. Add two boolean modifiers to the cube to subtract the two cylinders. Add a toon shading setup (shader to RGB and gradient) and free style to render lines for edges. Render with Eevee and Cycles (see above). File attached. [sekhar-04-20.blend](sekhar-04-20.blend)\n\n" ]

[ "the small error in UI nodes when swithing on fullscreen area\nFrom blender version 2.93.7 LTS to 3.0, a small graphical error was noticed when working with geometry nodes, shaders, etc. When switching to the view with the toogle fullscreen area option (ctrl+alt+spacebar), when zooming or panning a node, an artifact appears in the form of a smearing effect or something similar" ]

[ "Nodes: Socket and title click detection is broken for multiple monitors\nOperating system: Windows 11 Home, Version 22H2, OS Build 22621.1265, 64-bit\nGraphics card: NVIDIA GeForce RTX 3060 Ti, NVIDIA GeForce RTX 2070 SUPER\n\nBroken: Blender 3.4.1, Blender 3.5.0 Beta (2cd7e70c18a8), Blender 3.6.0 Alpha (ef60b13c1f29)\n\n\nThe click detection for node sockets and titles does not work when using main windows in two separate monitors.\n\nThis issue is similar to 96255 , but I'm facing this issue even with UI scale = 1.0.\n\n\n1. Create a geometry node tree. Node socket/title click detection works properly.\n2. Create a new Main Window. Click detection still works.\n3. Move a main window to another screen. Click detection fails. Clicking and dragging sockets/titles triggers box selection. \n\n(See attached video)\n\nMain monitor: Dell U2720Q\nSecondary monitor: LG DualUp 28MQ780\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.", "Color space seems wrong while painting in image editor.\nIn the image editor add a new image and with default settings just do a red line paint over a green line paint.\nDark zone appear in the falloff between red and green. it should not be there and should stay clear, not dark. \nI don't know why, but it looks like a color space issue. \n\ndark falloff not ok in blender:\n\n\nclear falloff ok in gimp:\n\n\nblender 2.8\nWindows 7 \n\n\n", "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", "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 ). ", "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", "Curves sculpting collision with surface.\n", "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}", "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", "Mesh Bevel Node\nNOTE: Design outdated. See #98674 for current design and progress. It is a development task though, so please don't add comments like \"when will this be finished?\"", "Geometry nodes preview, clipping Region in the viewport its not working\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nTo be compleatly honest i don't remember if this was a limitation of the preview node or not and i was unable to find the answer. \nSo as the title says viewport clip in viewport doesn't work in the geonodes overlay preveiw\n\n\n- Try to preview any data from geometry nodes. \n- alt+b to do a viewport clip\nshould look like in the left side of the image above, but it seems that a second geometry with the info from geo nodes in alpha blend mode its not being clipped \n\n", "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", "Cycles/Eevee texture nodes for modifiers, painting and more\nWith Blender Internal being removed, we have an opportunity to support the same set of textures for Cycles, Eevee, modifiers, particles, painting, compositing, etc. So we plan to port the relevant Cycles / Eevee shader nodes to Blender C code, and make those the new texture nodes that can be used throughout Blender. Blender Internal textures can be removed then, and we can extend the Cycles / Eevee shader nodes to add any important missing features from them.\n\n* Some nodes like color ramps, RGB curves, and similar utilities are already there.\n* Texture nodes like image, noise, voronoi need to be ported.\n* Geometry, attribute and similar nodes as well. These are the most complicated since they access the mesh geometry.\n* Some nodes like BSDF, Mix Shader, Bevel, .. would not be supported.\n\nFurther we need a good UI for this in the texture properties.", "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", "Research: refactor dotted/dashed lines to support line width.\n Almost all line types in the UI are using shaders that add geometry, so they can be any width even on some Macs that don’t otherwise support line_width greater than 1. Except for one: dotted/dashed lines. We still use these in quite a few places, sometimes even using them as solid lines. Anyway this one shader always makes 1-pixel wide lines on these problematic Macs, and those users quite often have high-dpi displays, making them almost invisible. And then we have some people who need large UI scale and/or wide lines for accessibility reasons, like one fellow who is almost blind. So just hoping that a refactor of that one shader could be on your “to do” list. " ]

[ "Error in UI nodes when switching on fullscreen area\nFrom blender version 2.93.7 LTS to 3.0, a small graphical error was noticed when working with geometry nodes, shaders, etc. When switching to the view with the toogle fullscreen area option (ctrl+alt+spacebar), when zooming or panning a node, an artifact appears in the form of a smearing effect or something similar{[F12806941](Снимок_экрана__136_.png)}\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n" ]

[ "Blender freezes with Metal render device\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.5.0\nWorked: None\nAlso Tested: 3.5.1 RC (April 01, 01:59:41, `6fa464d18971`)\n\nBlender freezes after a few seconds when I enable the Metal Render Device in Preferences, switch to Cycles with GPU Compute and switch Viewport Shading to Rendered.\n\n1. **Do not** delete the default cube\n2. Switch to Metal (GPU) Cycles Render Device in Preferences > System\n3. Set GPU Backend to Metal\n4. Switch Render Engine to Cycles and device to GPU Compute\n5. Switch Viewport Shading to Rendered\n6. Wait for Cycles to compile shaders\n7. Look around for a few seconds\n8. Blender Freezes\n\n", "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", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Vulkan: Better handling of GPU debug when not having vulkan SDK installed.\nBlender libraries only contain a subset of the vulkan SDK. Most important is\nthat validation layers aren't added. These validation layers will be enabled\nwhen starting blender with `--debug-gpu` (or test cases).\n\nIn this case there is an error printed to the console. This should not be an\nerror, but we could add a log line when not found.\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)", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "crash when import fbx\nOperating system: Window 10 pro\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc\n\n\nCrash when I imported fbx file \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Blender Selection Lag\nOperating system: Windows 8.1 64bit\nGraphics card: Intel(R) HD Graphics 4400\n\nBroken: \nblender-2.83-39aa122a0e6d-windows64\nblender-2.90-4f622c9a080b-windows64\nblender-2.90-5254ffa17bf0-windows64\nWorked: \nblender-2.79b-windows64\nblender-2.80-windows64\nblender-2.81a-windows64\nblender-2.82a-windows64\n\n\nBlender's selection tool started to lag noticeably behind the mouse. \n\nSteps to reproduce:\n1. Open Blender 2.83 / 2.90 Beta and Alpha\n2. Select Circle select or Box select\n3. Move around the mouse to see the lag\n\nNot sure if this is intended or a new known issue.[SelectionLag.avi](SelectionLag.avi)", "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.", "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)", "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 crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Blender 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", "Blender 3.5 and 3.5.1 are crashing while using Metal as backend\nOperating system: macOS 12.6.3\nGraphics card: Radeon Pro 580 8GB\n\nBroken: 3.50, 3.51 (Metall Backend)\nWorked: 3.50, 3.51 (OpenGL Backend)\n\nBlender simply hang. I use eevee, if you switch to rendered viewport shading it crashed complete system. I use Metall as backend, if I choose OpenGL it works fine. \n\n \nI attached an .blend file for example.\n\n", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n" ]

[ "blender-2.80-50cb8013ebf-win64 keeps crashing at startup \nwindows 10, graphics card AMD Radeon HD 6470M\n2.80-50cb8013ebf crashed\n2.79 worked\n\nCrashes during startup , have used blender.exe -d --debug-gpu but still it crashes after clicking the first click. 2.79 load with no issues. \nThe background application is on Hang or stuck in a loop with cursor not moving and display driver crashes.\nshows win32 error (8341) \nDetails on Screenshot \n\n\n\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Blender 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 Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at greenstoneleaf@gmail.com\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Array/Skin-Modifier-Combo causes crash\nOperating system: Linux Mint 19\nGraphics card: GT630\n\nBroken:\n2.80 (sub 39), branch: blender2.8, commit date: 2018-12-20 23:46, hash: 7a26e930a8c0\n\n\nPlease try to toggle the \"visibility\" of the skin modifier in my simple file. It crashes instantly and repeatingly:\n[Procedural leaves feathered1.blend](Procedural_leaves_feathered1.blend)\n", "Blender 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", "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", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Blender 3.4 Random Crashing Since GPU Replacement\nOperating System: Windows-10-10.0.19044-SP0\nGPU: NVIDIA GeForce RTX 3060/PCIe/SSE2 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0, branch: blender-v3.4-release\n\n**Short Description**\nI have replaced my RX580 with an RTX3060 earlier and ever since that replacement, I have been having constant crashes whenever I attempt to use Blender, do note that I've been in edit/object mode during these crashes as I'm working on a subd model, I have tried a handful of fixes such as upping TDR values but it didn't seem to fix the issue.\n\nRyzen 5 2600, RTX3060, 16gb RAM, no temperature exceeds 60 degrees Celsius and nothing is active besides Blender 3.4 along with addons I have installed.\n\nHere are the logs I get when I run Blender via the gpu debug cmd: \n\nEdit: I did try disabling UV Packmaster as per the error logs, but that didn't stop the crashing.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[gunflipped.crash.txt](gunflipped.crash.txt)", "Crash of simulation demo file related to bevel modifier on a simulated mesh\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Beta\n\nin the file, play the Animation, and move \"Empty\". It should crash within 1 second.\nI find no crash when there's no bevel modifier.\n\n", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Crash 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>", "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", "Crash with Boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.1.2 (appears to have been broken since 3.2.0)\n\nBlender crashes when performing an Intersection Boolean between a cube and a bunch of loose faces. (Granted, this is probably not something you should do in the first place, but at least it should be limited to producing a bad result, not a crash.)\n\nI didn't find a crash log, but it's easy to reproduce.\n\n* Load the attached .blend file.\n* Scrub the timeline to frame 209. Blender crashes.\n\n[crash.blend](crash.blend)\n" ]

[ "Blender 3.0.1 launch crash\nOperating system: windows 11 home\nGraphics card: NVIDIA® GeForce RTX™ 3060( mobile )6 GB di GDDR6\n\nBroken: 3.0.1\n\nI opened EDIT ( if it’s correct I only installed yesterday) went to USER PREFERENCES then ADD-ONS but accidentally click on something like INSTAL that was exactly at the beginning ( higher ) on the page then the program crashed.\nI wait and click to open a new session , it runs a black page with codes ( as it always did for the day ) but just 1 line then crash and that happens in a in a thousandth of a second. I uninstalled it from my pc and reinstalled nothing change I tried multiple times but I guess the program remember the user profile ( you would tell me thanks ) I tried to instal it from e your webpage, the zip file but had same results. I know I should not use feature that I don’t know and pay more attention but it was an accident, please help me or I would never be able to use it ( I know that it’s not so specifically written and I’m sorry also for my bad English )\n\nI installed a zip from poliigon called POLIIGON MATERIAL CONVERTER FIR BLENDER and try to do what they tell to do in the tutorial … I couldn’t find the zip file when I went in blender- edit or file - user preferences- add ons - click on a section with the beginning with in capital letters INSTALL ( something else but was cut because of the section size ) than it crushed ( and the rest you already know )" ]

[ "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)", "Add cube\" wrong representation of Z-extrusion (Not a bug Just little correction)\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.93.0\n\n\"Add cube\" wrong representation of Z-axis direction\n\nNot an error but an incorrect representation of object depth creation while using \"Add cube\" function.\n\n\n\n", "Rotate bone snapping\nBroken: version: 3.2.0 Alpha\nWorked: -\n\nCannot rotate one bone (in edit or pose mode) to point at a target (any).\n\n- Open attached file or:\n - make an armature\n - edit mode\n - add bone (2 bones total)\n - move and rotate both bones off origin\n - turn on snap, snap to vertex, affect rotate\n - pivot on active element or individual origins\n - edit mode or pose mode\n- try to align one bone to point at the other bone head\n[snap_rotate_bug.blend](snap_rotate_bug.blend)", "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", "Graph Editor generator for angles works in Radians while the graph editor displays the result in degrees.\n**System Information:**\nN/A\n\nBroken: Blender 2.80 Beta (18e5540a48b6) and Blender 2.79 (e290a0b0568e)\n\n**Short description of error:**\nIf you use the \"generator\" modifier in the graph editor for an angle, the generator will work in radians while the graph editor will display the output in degrees.\n\n1. Open the startup file.\n2. Select the default cube and key frame one of the rotational axis.\n3. Open a graph editor and give the \"key framed rotation\" an \"generator\" modifier.\n4. When entering values into the modifier such as 0 and 1 so your polynomial is y=x, the result shown on the graph editor is y=57.3x. This is because the values input to the generator is read as radians while the scale in the graph editor is read in degrees.\n\n", "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:", "Particle system: late update of object`s tracking axis after «object`s rotation» switching.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 13)\nWorked: Apparently never (2.79 has the same problem)\n\nAfter switching on/off object`s rotation for particles, their rotation updates wrong and I need to switch something at initial object to update rotation of particles.\n[2020-04-22_16-08-56.mp4](2020-04-22_16-08-56.mp4)\n\n- Make particle system, that emits object.\n- Switch object`s tracking axis to +Z (relations)\n- Switch Object`s rotation in the particle system render tab.\n- Rotation is wrong and not changing until object`s transform not updated.\nor\n- Open attached file\n- Move the \"Cone\" object to update the particles\n- In the Cube particle settings, enable and disable `Object Rotation`\n[particle system rotation tracking no update.blend](particle_system_rotation_tracking_no_update.blend)", "Bisect Tool rotation Gizmo doesn't behave correctly\nOperating system: Linux-5.15.0-27-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.3.0 Alpha\n\nI wasn't sure how to call the title. \nThe issue is that if you use the Bisect tool in the toolbar, you get an adjust last operation gizmo after using it.\nBut the rotation gizmo doesn't seem to take the mouse movement relative to the viewport rotation into account that well.\nIt behaves quite strange and unintuitively.\n\n- Go into Edit Mode on a cube\n- Select everything\n- Use the Bisect Tool from the toolbar on the cube\n- Use the blue ring on the gizmo\n- Try using it from different angles (rotate around the cube)", "Snapping to vertex for Rotation doesnt work for Empty and Pivot Point\nBroken: 2.92, 3.1.2\nWorked: -\n\nSnapping with Rotation enabled doesnt work for Empty and Pivot Point (In Affect Only Origin mode)\nIn attached file,\ncube was properly aligned during rotation with snapping to vertex on the plane (marked)\nbut rotation of Empty produce unexpected results\n\nPlace any type of Emply object or try to edit Pivot Point and rotate it with snapping to certain object vertex to match rotation. Rotation will always produce unexpected results.\n\nVideo demonstration: watch?v=zB9ElkiEG7U\n\n[snapping_issue_T99279.blend](snapping_issue_T99279.blend)", "Dragging the cursor (shift-right-click-drag) locks it's rotation\nOperating system: ~~Windows-10-10.0.22621-SP0 64 Bits~~ Windows 11 22H2\n> ***Meta Bug: this doesn't seem to recognize I'm on Windows 11.***Graphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\nBroken: version: 3.4.1\nWorked: /\n\nWhen setting the 3D cursor to project to surface and align its rotation to the geometry, it doesn't update when dragging. It only sets the aligned rotation on first click.\n\n1. Change Keybinding setting for shift right-click\n\n2. Add UV sphere\n3. Shift right-click-drag the 3D cursor over different face of the sphere\n4. Notice it only sets the rotation once initially\n\n", "Simple Deform Modifier - Bend Mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional) possibly never?\n\n'Simple Deform' modifier - 'Bend' mode performs as expected if mesh extends along X axis or Z axis. Performs unexpectedly (similar to Taper mode) if mesh extends along Y axis\n\nStart with new 'general' scene.\nSelect default cube\nAdd 'Array' modifier with values for relative (or constant) offset as: X=2, Y=0, Z=2 (so it extends along X and Z axis)\nSet 'Count' to 6 to have 6 cubes along the X axis\nAdd 'Simple Deform' modifier\nSelect 'Bend' mode\nDefault values for Bend mode will be Axis: X and Angle: 45\nMesh will bend as expected around X axis - each cube is rotated around a vector from origin along X axis keeping the expected shape\n\n\nChange Axis to Z\nMesh will bend as expected around Z axis - each cube is rotated around a vector from origin along Z axis keeping the expected shape\n\n\nChange Axis to Y\nMesh rotates along vector from origin along Y axis, but tapers. \n\n\nThis behaviour is very similar to how the Taper mode works\n\n\nPlaying with the angle values for each axis will clearly illustrate the issue. Changing angles on X and Z axes bends as expected. Changing angles on Y axis tapers and stretches.\n\nI've seen similar reports here that may be talking about the same thing, but they've been closed down as expected but unintuitive behaviour. I hope this shows that this is more likely a bug rather than simply unintuitive, as bending on both other axes works as expected.\n\nThanks all.\n\n[bend_X.blend](bend_X.blend)\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", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\n\n", "Freestyle - marked freestyle edges do not work on objects with the boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: Unknown\n\nEdges marked as freestyle do not work on objects with the boolean modifier\n\n\n1. Create cube object, add some edge loops and mark any edge as **\"Freestyle Edge\"**2. Create a second cube, and use it as a \"cutter\" using the**\"Boolean\"** modifier\n3. Activate **\"Freestyle\"**and check the**\"Edge Markt\"** in the \"Line Set\" area\n4. Make a render - the edge marked as **\"Freestyle Edge\"** will not be visible\n\n\nFile in attachment.\nThank you\n\n[Boolean Freestyle bug.blend](Boolean_Freestyle_bug.blend)\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" ]

[ "[SOLVED] Only XYZ Euler is working in Blender 2.93.5\nOperating system: Windows 10\nGraphics card: Not important in relation to this bug\n\nBroken: 2.93.5\nWorked: I think it worked with 2.8\n\nIn gimbal rotation mode only the XYZ Euler works from the list of rotation modes. \n\n\n1: Default startup\n2: Choose \"Gimbal\" on the Transform Orientation-list\n3: In the Sidebar-menu (N), under View, choose \"ZXY Euler\" (the dropdown menu under Rotation).\n4: Now, when rotating the Cube it still acts as if rotated with the XYZ Euler.\n```\n The Z-axis controls Y and X. Y controls X. X controls nothing.\n```\n5: If any other rotation mode is selected in the Sidebar-menu the object is still rotated as if by the XYZ Euler.\n\n{[F11626642](Nyt_Projekt_-_2021-10-30T224631.905.png)}\n\nPlease help me by fixing this issue :) " ]

[ "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", "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", "Wrong tangent space when using GPU subdivisions\nOperating system: Linux-5.18.0-1-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.08\n\nBroken: version: 3.3.0 Alpha\nWorked: N/A\n\n\nThe tangent space is calculated wrongly when using GPU subdivisions: it appears as if it is calculated for the base mesh instead of being calculated at the limit surface.\n\n\nOpen the attache file, and toggle \"GPU subdivisions\" in the preferences.\n\n|CPU subdivisions|GPU subdivisions|\n| -- | -- |\n||\n\n[gpu_subdiv_tangent.blend](gpu_subdiv_tangent.blend)\n", "UV map inconsistency after bevel modifier\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nMesh position in edit mode affects how bevel processes UV map\n\nIn attached file translate selected part of mesh along world Z axis -> UV is changing position\n[bevel_uv_issue.blend](bevel_uv_issue.blend)", "Incorrect and Confusing Units for String to Curves Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\n\nIncorrect and Confusing Units for String to Curves Node, depending on Scene / Units\n\nIf Scene / Units is set to Metric this node looks like this:\n\n{[F13984816](image.png),width=100%}\nCharacter spacing is shown in meters, and that is so odd that it might as well be shown in \"number of chickens\". Our current Character Spacing is already done strangely enough. This value is divided by 2 then 0.5f is subtracted from it. That value is a portion of the font's em square that is added to each character. So a value of **1 means no change** to character spacing. 0 means that 0.5 of an em is subtracted from each one. That \"1\" means default is bad enough, but much worse to show it as one meter. \n\nAt minimum we should show this as unitless. Better would be to not do the division and shifting and therefore show \"0\" as default and add \"em\" as unit. This would match with CSS letter-spacing.\n\nWord spacing is similar, but is a factor multiplied against each character's advance. So again, \"1\" means normal, 0 means that a space has no width, a 2 means a space is twice as wide. No relation to grid size. So showing \"1 meter\" is pretty bad.\n\nThis also should be unitless. Ideal would be to change it from a factor to a absolute value added to the width of space characters. That way it can also be \"0\" by default and show \"em\" as units. This would match with CSS word-spacing.\n\nFor even more oddness, this what it looks like in Imperial\n\n{[F13984832](image.png),width=100%}\n\nAs in normal and default character width and normal word spacing are shown as \"3.28 inches\"?\n\n", "Boolean modifier assigns wrong material\nOperating system: win10\nGraphics card: 1050 ti\n\nBroken: 3.4 alpha\nWorked: 3.3.2\n\nMaterial transferred during boolean operation is not the one assigned to target geometry.\n\n[boolean_material_update_problem.blend](boolean_material_update_problem.blend)\nOpen attached file or:\n\n - Create some boolean difference situation with modifier\n - Add two materials to target, assign first to geometry and put it on second slot -> modifier owner slice has wrong material\n\n\n", "Grease pencil strokes are incorrectly blended with geometry in draw mode (depending on 'Fade Inactive Geometry' setting)\nOperating system: Win 10\nGraphics card: ATI Radeon 5700\n\nBroken: (example: 2.92b, 213f8*, master, 2021-01-28, as found on the splash screen)\n\n\nnote: this is due to `Fade Inactive Geometry` being ON\n\nWhen drawing grease pencil strokes with a black material the rendering style changes when...\n\n - ...switching between draw-mode and edit mode, or\n - ... toggling the overlay button in draw mode (even will all overlay options disabled).\n\n\nThis leads to noticeable rendering artifacts while drawing. Please consider the following screenshots:\n\noverlays on:\n\n\noverlay off:\n\n\nSome assumptions:\n- I assume that the blend modes are not correctly set and thus interfere with the MSAA.\n- The white artifacts are especially pronounced for thin strokes of all opacities. Increasing the thickness factor slightly decreases the problem.\n\nLoad the following blender file\n[stroke-test.blend](stroke-test.blend)\n\nStep by step:\n1. Start blender\n2. Create Cube\n3. Create Grease Pencil\n4. Add new material for grease pencil and change to black\n5. Draw strokes (with different opacities)\n6. Switch between Draw and Object mode or toggle Overlay-Toggle\n", "Multi-segment bevel doesn't follow edgeloop below certain width.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Beta\nWorked: NA (repro in 2.80)\n\n\nWhen using a multi-segmented bevel below a certain width the existing edgeloop flow is not respected. It will 'snap' to follow the existing edgeloop once you reach a certain width. \n\nChanging the unit scale does not affect the issue. However, scaling up the object and applying scale will avoid the issue as the bevel width with the issue is so insignificant.\n\n\n\n[bevel_issue.blend](bevel_issue.blend)\n\n\n - Load bevel_issue.blend\n - Enter the Right Orthographic (X+) preset viewpoint\n - In outliner select bevel object from the scene collection and enter edit mode (edge)\n - Select the two edges marked sharp\n - Use the bevel tool and set segments to 4\n - Observe that a bevel width < 1.6mm results in a slight upwards bowing of the mid-ring loops inside the bevel, whereas a larger bevel follows the existing orientation of the edgeloop.", "MacOS, Metal: Banding artefacts in viewport when using curves in color management\nOperating system: macOS-13.2.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro Vega 64 1.2\nScreen: iMac 27 inch Retina 30bit\n\nBroken: version: 3.5.0\nWorked: same version with openGL viewport API\n\nIn the \"wanderer\" demo file you get white lines in the bright parts of the scene. They are visible in rendered view as well as in the final render (but only inside blender). \nWhen \"Use Curves\" in \"Color Management\" is turned off, they dissapear. \nWhen switching back to openGL api everything looks ok.\n\nOpen the demo file wanderer wanderer.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", " Freestyle renders extra lines\n%%%--- Operating System, Graphics card ---\n1st PC: Win7 64bit & Quattro 2000\n2nd PC: Win7 64bit & Nvidia 560ti\n\n\n\n - Blender version with error, and version that worked ---\n2.68a\n\n - Short description of error ---\nFreestyle produces lines through objects as they are transparent\nI build a moving staircase and some lines of the glass roof appear \"randomly\" through the walls.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\n\nI just created objects + render. %%%", "Incorrect Fresnel layer weight shading on backfacing geometry\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\n\nFresnel layer weight creates a sharp boundary instead of a smooth falloff when viewed on backfacing geometry.\nIn this example there are 2 hemispheres with the same material, but the left one has inverted face normals.\n\n\n[fresnel bug.blend](fresnel_bug.blend)\n", "modifier offset slider step value being driven by the mouse looses one order of magnitude worth of accuracy when units are metric vs none\nwin 10\n2080ti\n\nBroken: 2.80+\n\nSince blender 2.8 has switched to real world units the modifier slider step(when driven by the mouse) value has lost one order of magnitude worth of accuracy, 0.001 instead of 0.0001 \nIt is possible to switch the unit system back to none to get the higher accuracy. \nThey should be consistent and both work to the higher level of accuracy as this level is essential when working on real work scale small items e.g. a watch\n\n\n- with scene unit type set to \"metric\" add a bevel modifier the standard cube\n- press shift while clicking and dragging the bevel modifier offset slider and notice how the smallest amount possible to move is 0.001 m\n- switch scene unit type to \"none\"\n- press shift and click drag the modifier offset slider and notice the smallest amount possible to move is 0.0001 m\n", "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", "Normal arrows float out of subdivided curve\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 17)\n\n\nWhen curve subdivided, normals (arrows) still floats on their old unsubdivided positions. \nLooks like a bug/flaw.\n\n[2020-05-22_12-36-40.mp4](2020-05-22_12-36-40.mp4)\n\n[отлипшие нормали.blend](отлипшие_нормали.blend)\n\n" ]

[ "Measurements are being drawn incorrectly if one end is off screen\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.82 (sub 3)\n\n[Short video illustrating the problem](mrcge)\n\n- Use the measure tool to measure for example one edge of the default cube.\n- Now move your view in between the two points. The line should now point in the wrong direction\n\nHere's the default file with a measurement already added:\n\n[measuretoolbug.blend](measuretoolbug.blend)\n\n(this is a duplicate of #71629)\n" ]

[ "Experiment: Compositor meta data to support different workflows.\nTo test a new workflow at the blender institute we want to use the same meta data as stored in the input file.\nThe compositor already has the ability to keep the meta data when using cryptomatte which we want to use.\nThis is just an experiment and not intended to land in blender master ATM.\n\n\nMetadata for single layered textures are stored as `ImBuf.metadata` (Properties)\nI expect that in `void OutputSingleLayerOperation::deinit_execution` we could fill them with information that we get from COM_MetaData.\nWe should then also fill the meta data in `ImageOperation`.", "Batch Rename: Numbering support\nCurrently batch renaming relies on Blender to number duplicates.\n\nNumbering could be supported:\n\nExample: a chain of finger bones. These would usually be named `Index.01.L`, `Index.02.L`, `Index.03.L` and so forth.\n\nFor numbering to work usefully we would want a way to sort items before they're numbered (by their current alphabetical order, hierarchy, location... possibly others).\n\nThis needs some design to think of how to expose this to users usefully, see suggestion: a5b1231de7#244815", "Smoke domain emission render has blocks using View Layer Indirect Only \nOperating system: Windows 10 Home 10.0.183363\nGraphics card: Nvida RTX 2080 super\n\nBroken: 5e04548500\n\n\nWhen setting the volume object (smoke domain) into Indirect Only, the render doesn't seem correct (the black blocks show up).\n\n- Play the animation to bake the 5 frames.\n- Render any of the 5 frames to see blocks in the image. \n\n\n[indirect_only_volume.blend](indirect_only_volume.blend)\n\n\nThanks\n", "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", "Lots of animation-related operators do not check if the data is editable or not\nMany animation-related operators do not do any check whether the data-block they operate on is linked, liboverride or fully local data. This seems to affect in particular operations from the 3DView (like key insertions), and in the NLA (like adding new tracks, duplicating strips, etc.).\n\nE.g. one can insert keyframes on a linked object (ie create animdata for that linked object, a new local action, and assign that local action to the linked object!).\n\nRelated to issue reported in #98686 (Cant rename local NLA tracks within a local library override data-block.).", "UV: select similar enhancements\nAdd support for UV Select similar:\n\n* Islands / Faces / Edges, crossing UDIM boundary\n* Islands / Faces texel density\n\nThanks @BlenderBob !\n\n", "TIFF 8bit always saved and loaded as unassociated alpha\nOperating system: Linux amd64 Debian Buster\nGraphics card: NA\n\nBroken: All\nWorked: Possibly way back.\n\nBlender can handle own TIFFs\n\nTIFF handling in Blender has been forever been broken for a number of reasons.\n\nBy default TIFFs encode associated alpha. Sadly, Blender had a hack that tried to \"preserve\" background pixels, coupled with saving with extrasamples set to unassociated alpha. The result is that Blender can't properly load it's own files.", "Support MinGW\nWe have some patches in MINGW-packages to make blender build on MinGW.\nWe already have it for Windows ARM64.\nIs it OK to upstream those patches?", "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.", "Expand asset drag & drop support to more cases\nUsers expect a number of use-cases for asset drag & drop to work. Dropping an asset means appending it currently, but what happens then varies.\n\nThe following drag & drop operations should be supported:\n\n| | Asset Type | Drop Action | Notes \n| ---- | ----| ---- | ---- | ----\n| General UI | | | |\n| ---- |\n| {icon square-o} | Any | Dropping onto data-block selector: Assign data-block if applicable | \n| {icon square-o} | Scene | Change to dragged in scene | \n| 3D View | | | |\n| ---- |\n| {icon check-square-o} | Object | Add Object in Object mode | \n| {icon square-o} | Object | Add mesh (or strokes, curves, meta-ball element, ...) in edit mode (to the active object?). | Append in edit mode not supported. Postponed for now.\n| {icon check-square-o} | Object-data | Adds object in object mode using appended object-data | \n| {icon square-o} | Object-data | In edit mode: Same as dropping object in edit mode | Append in edit mode not supported. Postponed for now.\n| Node Editor | | | \n| ---- |\n| {icon check-square-o} | Node Group | Create Node Group node | \n| {icon check-square-o} | Image | Create Texture/Image node | \n| Geometry Nodes | | | |\n| {icon check-square-o} | Object | Create Object Info node | \n| {icon check-square-o} | Collection | Create Collection Info node | \n| {icon check-square-o} | Texture | Create Attribute Sample Texture node | \n| Compositor | | | |\n| {icon check-square-o} | Masks | Create Mask node | \n| Outliner | | | |\n| ---- |\n| {icon square-o} | Any | Assign to drop target (e.g. assign dragged material to object under cursor on drop) | \n| Text Editor | | | |\n| ---- |\n| {icon square-o} | Text | Change to dropped text | \n| UV/Image Editor | | | |\n| ---- |\n| {icon square-o} | Image | Change to dropped image | \n| Dopesheet | | | |\n| ---- |\n| {icon square-o} | Action/Pose | Change to dropped action (if the context mode allows it, e.g. in Action Editor mode) | \n| NLA | | | |\n| ---- |\n| {icon square-o} | Action/Pose | TBD | \n| VSE | | | |\n| ---- |\n| {icon square-o} | Media | Add strip for media type (image, video, sound) | \n| Movie Clip Editor | | | |\n| ---- |\n| {icon square-o} | Video/Image/Clip | Add clip for media type and change to it | \n\nNote that drag & drop support for assets also brings drag & drop support for local data-blocks. So for example by adding drag & drop support for node group assets, dragging a node group from the Outliner to a Node Editor is also added.", "Pose Library: Collection pop-up when creating new poses in Action Editor\nWhen creating poses from the Action Editor it should be explicit to which catalog the new asset should be added.\n\nBy default the Unassigned option should be highlighted, so users can post-pone this decision for later, similar to when marking data-blocks as assets.\n\nThis is part of #103265.\n\n---\n\nSome initial code snippets for anyone interested on tackling this: [P3408](P3408.txt)", "Pack to box region in uv editor\n- Additional property option to the pack islands operator. \n- scales down uv's to fit the selected box\n- Uses new UV editor widget, similar to “render region” in the 3D Viewport, which is activated by the shortcut CTRL+B (deactivate with shortcut CTRL+ALT+B)\n- This feature could also be very useful for the **Unwrap** operator. Let me know if we need a separate task for that\n```\n\n```\n\n\n\n\n**Starting point**\n\nSelected UV islands should be packed into the “box region” that is “drawn” by the user.\n\n\n\n**Desired result**\n\nSelected UV islands are packed to the “box region” that was “drawn” by the user\n\n", "Add option to re-use or duplicate data for the Current File asset library\nAgreed on this alternative to [D12752: Asset Browser: Hide Import Types menu for \"Current File\" asset library](D12752). Currently dragging in data from the *Current File* asset library always reuses the existing ID. The option to duplicate the data could be quite useful and make it explicit what dragging in the asset will do.", "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?", "Adding new hook while in Edit mode breaks when trying to undo/redo the operator\nWin7 (32bit)\n\nBroken: 2.78a\n\n\n- Add Path from Curve menu, add new Armature\n- Assign Bone to control point as Hook\n- Blank Hook modifier appears along with real one\n\nScreencast: [screencast0001-0250.mp4](screencast0001-0250.mp4)\n" ]

[ "Handle Data Dependencies\nWhen dragging in an asset that depends on other data-blocks or files, these dependencies should be handled in a clear way.\n\n* - [x] Indirect datablocks get appended. *-- This is done now, including re-using of heavy indirect data-blocks (794c2828af) and proper scene instantiation (df9120b365)*\n* - [ ] External files can use pack, append, then unpack (into e.g. textures/ folder next to .blend) *-- In progress, [D12423](D12423).*" ]

[ "Grease pencil: unstable offset height (surface drawing)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\nWhen I use perspective camera, and try to drad on surface with GP, offset is unstable and depends on distance from camera.\n\nTest File:\n[#94735.blend](T94735.blend)\n[2022-01-08_10-23-37.mp4](2022-01-08_10-23-37.mp4)\n", "Mesh edit, Shift+V vertex slide adjustment produces unexpected result\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nInstead adjustment movement with slider i have broken shape:\n[2021-04-30_15-00-38.mp4](2021-04-30_15-00-38.mp4)\n\n", "Driven values do not change with units\nOperating system: Windows-10-10.0.20206-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\nWorked: No working versions (at least >= 2.79)\n\nWhen creating a driver from an unlabeled value, pasting it into a field that accepts units of measurement will always use meters rather than the Scene unit.\nThis means that for a scene using inches, a driver with a value of 1 will translate to approx. 39.\nWhile this prevents things from changing when units change, this is not ideal as exactly re-converting in an expression is impossible.\n(It is highly unlikely someone working specifically in inches will want to input their values in meters.)\n\n- Create a new project, and change the units. (in this case, to Inches)\n- Copy a new driver from an unlabeled value. (ex. array count)\n- Paste the driver into a field with a unit label. (ex. constant offset value)\n\n[#80649.blend](T80649.blend)", "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", "Curve \"solidify\" modifier glitch\nOperating system: Windows 7\nGraphics card: GT750M\n\nBroken: 2.80, 2019-02-28\nWorked:\n\nWhen applying a \"Solidify\" modifier to a bezier curve shape (or imported SVG), it creates random height vector points, creating strange triangles. This can be fixed by simply selecting the errored vector point then selecting one of the transform value (in my case it was Y) in the panel and either pushing enter (keeping the same value) or unselecting the vector point.\n\n\nAttached blend file with imported SVG.\n\n", "Subtype for input value nodes\n\nThe user may be at a loss when entering a rotation radians value into some built-in node, copies it into the input value node, and now these are degrees.\nThe explicit way of specifying the sub type must be an option for all value input nodes that it can have.\nThe type list option should be available in the N-Panel so as not to clutter up the node space.\n\n", "Adding vertices when Basis Shapekey is active prevents changes to the Basis from affecting other keys\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.1.0\nWorked: (Unknown, bug exists at least as far back as 2.79b)\n\nAs requested by @ideasman42, this is a report of the following shapekey bug:\n\nWhen vertices are added to a mesh with shapekeys when the **Basis Shapekey is selected**, any changes made to the Basis key will **NOT** propagate to other keys.\n\nHOWEVER, if vertices are added when any key **OTHER** than the Basis is selected (ie. Key1), and then the Basis key is edited, any changes to the Basis **WILL** correctly propagate to other keys.\n\nADDITIONALLY, if vertices are added when the Basis Shapekey is selected, **BUT** Edit mode is first **EXITED** then **RE-ENTERED** before any vertex manipulation is made to the Basis key, then any changes to the Basis **WILL** correctly propagate to other keys.\n\nAll three scenarios below (based on a new empty project) are demonstrated in **[this example video HERE ](v7YUb_9H2Ec)**.\n\n**1.** Add a cube, add 2 shapekeys. With the \"Basis\" key selected, enter Edit mode and add loop cuts. Move the vertices. Select \"Key1\" and notice the changes to the \"Basis\" key have **NOT** affected Key1. **This is the only scenario where the bug exists.**\n\n**2.** Add a cube, add 2 shapekeys. With the \"Key1\" key selected, enter Edit mode and add loop cuts. Now select the \"Basis\" key. Move the vertices. Select \"Key1\" again and notice the changes to the Basis key have affected Key1 as expected. **This is one workaround.**\n\n**3.** Add a cube, add 2 shapekeys. With the \"Basis\" key selected, enter Edit mode and add loop cuts. Now **EXIT** Edit mode and **RE-ENTER**. Move the vertices. Select \"Key1\" and notice the changes to the Basis key have affected Key1 as expected. **This is a second workaround.**\n\n*P.S. Apologies for the very late report. The last 3 weeks have been heavily pre-occupied with music production. And I'm super thrilled that #44415 made it into the 3.1 release. Thanks so much to @ideasman42 and all the talented Blender devs for making this happen!* :-)\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", "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.", "Copying in edit-mode copies the entire object, not the selection\nthere is an issue occurs when a part of (mesh) is copyed in the edit mode \nwhat happens when copying one part of a (mesh) and pasting it\nyou suppose to get this part only pasted ,but instead you get the whole (mesh) pasted\n\nfor examble if you have a cube model with a single face selected in the edit mode \nif you copyed then pasted it the result is the whole cube modele is pasted rather than the single face \n \n \n\n", "Changing dimension on multiple objects no-longer works\nOperating system: Windows\n**working version:**\n2.79b\n**Last known *working* version:**\nblender-2.80.0 Beta (dec 2018)\nHash: e4dbfe0a98c1\nBransh blender2.7\n2.80.39\n**Earliest known *broken* version**\nblender-2.80.0 Beta (april 2019)\nHash: 480a09a92f7f\nBransh blender2.7\n2.80.60→2.83.2→2.90.0 Alpha\nManipulating the values in ‘`3d view`→`n-panel`→`dimensions:`' with ‘alt-key’ held down and dragging the mouse cursor will no-longer affect all the selected objects, only the parent.\n(feature still present for '`Location`', '`Rotation`', '`Scale`'.)\n\n1. Duplicate the default cube and move it so both cubes are visible.\n2. select both cubes and go to ‘`3d view`→`n-panel`→`Dimensions:`'\n3. With both cubes selected, hold down the alt-key and start manipulate the value by dragging your cursor in one of the three fields for 'Dimensions'\n\n**PS.** feature did not have the same affect as just scaling the objects, (see animated gif bellow)\n\n[dimbug.blend](dimbug.blend)\n", "Changing the Orientation of Modifiers\nCurrently, LineArt is created in 3D space, however, the Modifiers can be oriented incorrectly.\n\nIn this example, the Noise Modifier is moving the Grease Pencil points on the Normal but not up and down on Z. There is currently no way to change it.\n\n[Noise - Position.mp4](Noise_-_Position.mp4)\n\nThis is a request for a way to change the orientation of the Modifiers.", "Imported SVG dimensions are incorrect after scaling and undo\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2070\n\nBroken: 2.93.1\nWorked: 2.80 also has this issue, the older versions are not working on my computer.\n\nImported SVG dimensions are incorrect after scaling and undo. After toggling edit mode this issue can't be reproduced anymore.\n\nSeems to be caused by `BKE_nurb_minmax` because `use_radius` is true\n\n\n\n- Import svg file (as curve, not GP)\n- Open side panel > Item tab, note initial dimensions\n- Scale imported object\n- Undo scale\nDimensions are incorrect.", "3D Texturing: When changing the texture resolution, the pixel data isn't recreated\n* Start painting\n* Change image resolution\n* Continue painting.\n\nWe have a safe guard for this, but it doesn't seem to work anymore.\n", "Grid in rendered orthogonal views does not adapt to displacement\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.92.0 Alpha\nWorked: unknown\n\nWhen in rendered view, in an orthogonal view, the grid does not adapt to displacement, giving some strange looking results.\n\nAdd displacement to an object. Go to rendered view, orthogonal. Grid does not adapt to the new object shape, see screenshot.\n\n" ]

[ "Measurement error while scaling objects\nI'm not sure if it's a bug or not but ... Namely when I want to increase the cube with one coordinate (S + Y) and press 4 I get some weird results. As can be seen in the picture, it is not possible that all the coordinates are the same, and the error can already be seen in the picture.\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", "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", "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n", "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.", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "blender crash itself while importing a dae (collide) file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nBroken: version: 2.82 and all versions in between then and now\nWorked: n/a\n\nHi, I'm using blender version 3.3 on a windows 10 downloaded on steam.\n\nwhen i try to import dae files, blender crashes itself and shuts down\n(this only happens with some dae files, not all and the ones who crash are not to big ).\n\nI tried to search with powershell to find the problem and I got this:\n\nError: EXCEPTION_ACCESS_VIOLATION\n[bgr_darryls_ship_ground.dae](bgr_darryls_ship_ground.dae)\n\n```\nThe gh->hashfp function pointer is NULL (hasn't been initialized yet)\n\nblender.exe!ghash_keyhash(const GHash * gh, const void * key) Line 133\tC\nblender.exe!ghash_lookup_entry(const GHash * gh, const void * key) Line 411\tC\nblender.exe!BLI_ghash_lookup(const GHash * gh, const void * key) Line 736\tC\nblender.exe!BKE_armature_find_bone_name(bArmature * arm, const unsigned char * name) Line 601\tC\nblender.exe!ArmatureImporter::create_armature_bones(Main * bmain, std::vector<Object *,std::allocator<Object *>> & arm_objs) Line 478\tC++\nblender.exe!ArmatureImporter::make_armatures(bContext * C, std::vector<Object *,std::allocator<Object *>> & objects_to_scale) Line 826\tC++\nblender.exe!DocumentImporter::finish() Line 228\tC++\n[External Code]\t\nblender.exe!DocumentImporter::import() Line 127\tC++\n```\n", "Cycles 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)", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "Crash 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.", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n", "Blender 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", "inset and bevel edits crashing blender 3.x\nThreadripper 1950x 128 gb ram 2tb SSD (home)\nNVIDA 3080 updated to latest drivers\n\nIntel i7 64 gb ram 2 tb SSD (work)\nAMD 6900xt updated to latest drivers\n\n\nHappens on all 3.x versions of blender.\n\nIssue happens on both my home PC (the thread ripper) and my work PC.\n\nStart editing default cube add bevels, insets place some cuts... crashes within a couple of minutes. Happens in all display modes.. mesh, solid, renders. Happens with a smooth display mesh and hard edges. Super frustrating need to save just before doing any of these procedures on any modeling task. Always update video drivers which probably cant be the issue because two different families of video cards in two different machines have the same issue. Been doing this ever since I updated to Blender 3. I assume it's a plugin I installed because I can't imagine why this would happen on two completely different computers. Is there a dump file or something I can send? Here is a video of a typical crash. No dialog box... just blender vanishes in the the middle of editing.\n\n", "Blender 3.5.1 + Mac + Metal + Crash\nOperating system: MONTEREY 12.6.3\nGraphics card: AMD Radeon Pro 5500 XT 8 GB\n\nBroken: Blender 3.5.1\nWorked: Blender 3.4.1\n\nBlender 3.4.1 will render a given scene with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" in 1 min 58 sec\n\nBlender 3.5 and 3.5.1 will crash on the same scene set on \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" - \nIt has to be run with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"CP\" and now takes 5 min 53 sec.\n\nI have lost computing power with the latest versions.\n\nJust run the file with GPU BACKEND turned on and \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\"\n\nI could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send\n\n" ]

[ "crash when i open snow character rig\nOperating system: Windows-10-10.0.19042 64 Bits\nGraphics card: AMD Radeon(TM) R7 M360 ATI Technologies Inc. 4.5.13399 Core Profile Context 0\n\nBroken: version: 3.1.2\nWorked: (the newest version of Blender that worked as expected)\nsnow character rig blender stopped and got crashed\n\nNo crash with other characters like rain and mike\nI tried many times to load factory settings but didn't work this problem I faced only with the snow character rig\nI attached a screen record file maybe help you to understand the problem that I faced a few days \nand thanks \n\n[26.05.2022_06.44.03_REC.mp4](26.05.2022_06.44.03_REC.mp4)\n\n\nthanks \n\n" ]

[ "Second windows ignores tablet input under Gnome-Shell/Wayland\nOperating system: Linux-5.18.6-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 550 / 550 Series (polaris12, LLVM 14.0.0, DRM 3.46, 5.18.6-200.fc36.x86_64) AMD 4.6 (Core Profile) Mesa 22.1.2\n\nBroken: version: 3.5.1\nWorked: 3.3.1\n\nAny secondary window doesn't register input from pen tablet\n\nOpen a \"new file window\" and see as the tablet input stops being registered by blender on that window\n\nTested on multiple computers with the same os and different pen tablets.\nOn a closer inspection, I found an aestethic difference between 3.3.1  secondary windows and 3.5.1 ones .\n\n", "Mantaflow liquid collisions not working properly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.90.1\n\nUnless a liquid collision effector's Surface Thickness is set to at least 0.5 or set to \"Is Planar\" it is not used.\n\nI reference two examples for liquid and smoke+fire [examples ]] and there are several issues logged in [[ https:*blender.stackexchange.com/search?q=liquid+collision | Blender stackexchange ]], along with my [[ 111042 | investigation ](http:*optionpeer.com/jimtpersonal/collisions.zip).\n\nA collision effector is ignored unless Surface Thickness is set to at least 0.5 or set to \"Is Planar\". However as [docs ](effector.html) state Surface Thickness is \"Additional area around the effector\".\n\nIn my first example \"liquid collision.blend\" the results (show in \"liquid collision.png\") shows how the extra Surface Thickness effects the liquid that becomes more confined in the container, whereas setting it to less than 0.5 will cause the liquid to fall through the container.\n\nThe same is true in the \"muzzle*.blend\" file where the flash & smoke comes through the collision object unless Surface Thickness is set (incorrectly) to at least 0.5\n\n[liquid collision.blend](liquid_collision.blend)\n[muzzle flash no projectile.blend](muzzle_flash_no_projectile.blend)\n", "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. ", "There is a delay when dragging the value sliders while using a Wacom pen.\nOperating system: Windows 10\n\n\nBroken: Blender 3.0\n\n\n\nTrying to drag value input sliders always has an initial friction which makes value dragging not an instant interaction. I do not get this initial friction when I use a mouse instead. \n\nPlease see the movie below. As you can see the values start changing just a little bit after dragging starts with the pen. You cant see the mouse pointer in the recording but you can see that the value box activated then the value changing starts happening.\n\nThis issue happens with all of the value boxes, not just the transform inputs as in the movie.\n\n\n[pzJM3EGql3.mp4](pzJM3EGql3.mp4)\n\n\n\nMake sure you are using a Wacom pen with Windows Ink (although Wintab does not seem to make a diff)\n\nAdd a basic object\n\nOpen the transform panel\n\nTry to slide the values in the boxes.\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", "No space mouse support in --debug mode\nOperating system: macOS 12.6.7\nGraphics card: Apple M1 Max GPU\n\nBroken: 3.6.1\n\nConnexion Space Mouse does not work if Blender is launched with --debug.\nNormal launch works.\nIs this related to #93170 ?\n\nLaunch Blender with --debug\nTry to use Space Mouse\n\n", "(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.", "Unify Interpolation In Vertex Paint And Sculpt Mode\nVertex paint squares colors when it interpolates, while the paint tools in sculpt mode do not. This should really be made consistent across both modes. \n\n\n", "Affects only origins does not work for Point Cloud, Curves, Text objects\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nAffects only origins does not work for Point Cloud, (new hair) Curves and Text objects.\n\n- Add Point Cloud (experimental), Curves or Text object\n- Set Affect Only: Origins\n- Try to move\n\n[AffectOnlyOrigin.mp4](AffectOnlyOrigin.mp4)", "The walk mode is stuck when it is enabled while using a tablet pen\nOperating system: Windows 10\n\n\nBroken: 3.0.0\n\n\nThe walk navigation mode goes does not trigger right away when it is used with a Wacom tablet in Windows Ink mode. The Win ink is set both in Blender and the Wacom properties.\n\nHere I enable the walk mode, but it does not move at all until I lightly move the mouse. After that it works.\n[ClvNCLQx0H.mp4](ClvNCLQx0H.mp4)\n\nUse a Wacom pen \nEnable Windows Ink in Wacom panel and in Blender\nEnable Walk navigation", "Holdout material no export in PDF\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.57\n\nBroken: version: 2.93.0\nWorked: (newest version of Blender that worked as expected)[story bug.blend](story_bug.blend)\n\n\n\n", "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", "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", " Alpha channel of Tint Modifier don't Work with Fill material but work with stroke material.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nhi, it's been a while i didn't make a report for a bug, :) , well i'm back.\nthe Tint Modifier work well with `Stroke `material for every color channel R,G,B,A , but for Fill material we have problem with Alpha channel that don't work at all.\nthe first video show stroke works well with ALpha channel :\n[2022-10-16 13-12-36.mp4](2022-10-16_13-12-36.mp4)\nthe file\n[aplha color of tint modifier work well with stroke material.blend](aplha_color_of_tint_modifier_work_well_with_stroke_material.blend)\nsecont video show the problem with FILL material and alpha channel:\n[2022-10-16 13-14-27.mp4](2022-10-16_13-14-27.mp4)\nthe file\n[aplha color of tint modifier don't work with fill material.blend](aplha_color_of_tint_modifier_don_t_work_with_fill_material.blend)\nhope to get fixed.thank you for reading it\n\n", "Pen input UI/UX issues\nThis task keeps track of the UI/UX related design issues in all Blender mode that don't work as intended or can greatly improved with pen input devices. \nIf we consider that most pen input devices have at least one button in the pen, this will mostly include feature that rely on mouse wheel events. \n\n\n## Edit mode\n\n- ##Number of Cuts## of loop cut and slide can't be controlled during modal operation, needs to be adjusted with the redo panel.\n- Proportional editing size can only be adjusted incrementally with keyboard shortcuts instead of with pen gestures (like brushes in all modes)" ]

[ "Pen pressure not working \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.23\n\nBroken: version: 2.91.0\n\n\n\nTablet that does not work with the pen pressure function, Huion H420\nThe tablet itself was detected by the program, everything works fine, except for sculpting and texture paint.\n\nHope you can easily fix this! Thanks for the great program)) " ]

[ "Crash when using OCIO v2\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0 Release Candidate\n\nWhen I used OCIO v2 config file and used Cycles for rendering with Optix, it worked for viewport rendering. But if I pressed F12 for final render, Blender 3.0 crashed when the render was finsihing.\nI tried with a few scenes even if the Blender default scene still crashed. Then I tried rendering with CPU, it still crashed.\nI also tried in Blender 2.93.5. It crashed again even if the render didn't start.\nI downloaded the OCIO v2 config file from ocio_v2_demo.html.\n\nWhen I used OCIO v1.2 config file, Blender worked perfectly.\n\n[test-ocio2.txt](test-ocio2.txt)\n- Set the OCIO environment variable to the location of the test-ocio2.txt config file.\n- Start blender and set Cycles as the render engine\n- F12\n\n-----\nOCIO v2 Config\n{[F12676993](image.png) size=full}\n\nBlender 3.0 crash video\n[Crash.mp4](Crash.mp4)\n", "(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", "Optix - Out of GPU memory in RTX 4090 but not in RTX 3090/3080\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.3.7\n\n\nI'm getting \"System is out of GPU memory\" while rendering in blender 3.3.1/3.3.7 optix with RTX 4090, but the same scene rendering fine in RTX 3090 and RTX 3080 in same system (Ryzen9 7950X, 128GB RAM). Tried updating to latest nvidia studio drivers( 535.96) as well as downgraded ( 531.61) still no luck. This issues not happening for small scenes with render time in optix less than 15mins. But for complex shot with render time over 30 mins giving out of GPU memory but render happening fine in 12GB 3080 and 24GB 3090 cards\n\n", "Using subdiv modifier affects normal baking performace of all objects in scene\nOperating system: Windows 10\nGraphics card: GTX 1080Ti\n\nBroken: version: 2.83 (sub 10)\nWorked: Never (2.8+)\n\n[#60428.blend](T60428.blend)\n- Open file\n- Press bake, watch memory usage\n# Remove subsurf modifier on `door_frame_low.001` object and repeat step 2\n\nBaking is much quicker and doesn't require too much RAM\n", "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)", "Point Cloud - Missing Particles when Rendering with Cuda on Linux\nOperating system: Linux-5.13.0-35-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.1.0\n\nWhen rendering large amounts of particles with CUDA on Linux, there appear to be some random patches of particles missing. This does not occur when using the OptiX rendering backend or CPU rendering backend. This problem **does not** occur on Windows for any rendering backend, i.e. the same render has been confirmed to work on Windows with the CUDA backend.\n\n1. Open the attached .blend file.\n2. Render with Cycles and CUDA backend on linux. *Note: It might be necessary to render the same scene multiple times if the error does not occur on the first render, or to switch the render device back and forth.*\n3. See the attached image for an example screenshot of the problem\n\n(alternative)\n1. \n - create a plane object and create 1000 edge loops in x and y direction so that the object has roughly 1 million vertices.\n - add \"Mesh to Points\" geometry node with radius 0.001\n2. Render with Cycles and CUDA backend on linux. *Note: It might be necessary to render the same scene multiple times if the error does not occur on the first render, or to switch the render device back and forth.*\n3. See the attached image for an example screenshot of the problem\n\n.blend File:\n[particles_problem.blend](particles_problem.blend)\n\nImage of the Problem:\n", "Cycles rendered 3DViewport massive performance drop, using lights with node groups. --Intel MacOS--\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 4.0.0 Alpha\n\nSee screenrecording video! \nWhen switching to a light with nodegroups in Cycles rendered 3DView, performance drops a big time. (~50%).\n\n1. Open the performance.blend file with Intel MacOS blender 4.0, switch to cycles rendered 3DView, select the cube and rotate the view.\n2. Then switch to the caustic light and try to rotate the view again.", "Cycles takes very long to cancel a render\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.2.0\nWorked: 2.93\n\nEver since Cycles was upgraded to Cycles X whenever I render a scene with a high Max sample count and cancel the render mid-render it always takes very long (up to a few minutes) until the render actually stops.\nThe time it takes to until the render stops seems to be proportional to both scene complexity and Max sample count.\nAt the start of rendering the samples first go up at small increments and later go up at greater increments. The greater the increments between sample count updates the longer it takes to stop the render.\nChecking Task manager shows that after hitting `cancel render` it does keep using the GPU, therefore keep rendering, until it finally stops.\nDuring the time between hitting `cancel render` and Cycles actually stopping the render the entirety of Blender becomes completely unresponsive.\n\nThis is only a problem when actually rendering the scene. Viewport render doesn't seem have this issue.\n\nTest file:\n[untitled.blend](untitled.blend)\n\nHit render and wait a little until the rate samples go up slows down. The hit `cancel render`.\n\nThank you and have a great day!", "Cycles X material preview using 100% of cpu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nUsing cycles X, opening the material preview causes my computer to lag and drop in FPS\n\nCreate a new material and open the material preview with cycles x\n\nFor a new scene with default cube and default material, preview render completes in about 5 seconds.\nWith Beckmann glass it's ~10 seconds.\nWith Multiscatter GGX Glass, ~35 seconds.\n\n(Size of preview render: 134x150px)\n", "Extremely frequent crashing when using the compositor. Especially when using the glare node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I believe it was far more stable before the realtime compositor implementation. (Blender 3.3-ish)\n\nBlender crashes extremely frequently when using the compositor on my system, especially when the glare node is being used at all. Does not seem related to vram or system specs, and looking through logs has not come up with any errors - it just closes.\n\nAdjust compositor glare node values with the viewer enabled. It seems to crash within a minute of doing so, usually sooner.\n\n", "Object rotation increases render time more than 10 times.\nTested with windows 7 64bit and windows 10 64bit.\nCPU ryzen 5 1600\nGPU GTX 780\nRAM 8GB GDDR4\n(bug appears on other computers too)\n\ntested with 2.79 and 2.8\nWorked: (optional)\n\nIf I rotate object for about 45 degrees around Z axis render time increases more than 10 times.\nBut in preview mode there is no difference in render time before and after rotation.[test.blend](test.blend)\njust rotate the object on attached blend file around Z axis about 45 degrees and compare render times before and after.\n10seconds for 2000 samples before rotation and about 10 minutes after.\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n", "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", "No responding open .blend file reuse mesh many times\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: blender-3.0.0-alpha+master.32cc9ff03746-windows.amd64-release (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: None (newest version of Blender that worked as expected)\n\n.blend file can download here\n21082\n\nI use bpy build a scene reuse some mesh many times. reuse around 64 times can work smoothly, only 0.4 second to build and open immediately. 128 times build 0.9 seconds and open will take a while. 256 times build 3.17 seconds and cannot open(no responding, not error). \n\n```\n collection = bpy.data.collections.new('matrices')\n bpy.data.collections['meshes'].children.link(collection)\n count = 0\n for mat in self.matrices:\n obj = bpy.data.objects.new(mesh.name, mesh)\n collection.objects.link(obj)\n mat_bpy = matrix_translate_to_bpy(mat)\n obj.matrix_world = mathutils.Matrix([mat_bpy[:4], mat_bpy[4:8], mat_bpy[8:12], mat_bpy[12:16]])\n obj.data.materials.append(materials[get_material_key(self.material)])\n count += 1\n if count > 256:break\n```\n\n", "Eevee: Occasional render glitches when using attribute node\nOperating system: Linux, specifically KUbuntu with X11\nGraphics card: RTX 3080 (Driver Version: 530.30.02, CUDA Version: 12.1)\n\nBroken: 2.93 - 4.0.0 Alpha, 2023-06-29, f47eed749eaf\nWorked: 2.92 (as available on Steam)\n\nUsing an attribute in an Eevee material causes occasional but severe render glitches. This does not happen consistently on any particular frame. It does not happen when rendering from the command line with `--background`.\n\nTo reproduce, render an animation with the attached Blender file. One in every 50 frames or so are corrupted. Occasionally it gets most of the way through the animation before ever producing a bad frame.\n\nThis file is basically the startup file with two changes:\n1. An attribute node with the name set to \"Color\" is plugged into the base color on the default material.\n2. The sample count is lowered to one. (The issue persists without this, but with a higher sample count, some samples glitch and others do not. The final image is a mix of the glitched and regular samples.)\n\nI have ensured that this is not a problem with my particular Blender settings by deleting everything in `~/.config/blender/4.0/config` and selecting \"Save New Settings\" in the splash screen before opening and rendering the file in the 4.0.0 alpha.\n\nNormal frame:\n\n\nCorrupted frame (as rendered in 2.93, some other versions simply display a transparent hole where the cube was without affecting the background):\n\n\n", "Cycles: Changing certain settings with `Persistent Data` enabled can lead to extremely long initialization times on re-render\nOperating system: Linux-5.15.0-1-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken version: 3.1.0 Alpha\nBroken version: 2.93.6\nWorked: Unsure\n\nWhen changing certain settings on some objects while having `Persistent Data` on in Cycles, can lead to extremely long initialization times on re-renders. For example I may have a particle count set to `10,000,000` and I render the scene for the first time. It takes roughly 2 minutes. Re-rendering the scene only takes 10 seconds because of the `Persistent Data` option. However, if I then **decrease** the particle count to `1,000,000`, the render takes a really long time to start (I waited 15 minutes before giving up)\n\n1. Change the render engine to Cycles.\n2. Change render settings such that the render is quick (lower sample count, turn off denoising, reduce the resolution).\n3. Enable `Persistent Data` in the `Render Properties -> Performance` section of the `Properties editor`\n4. Create a hair particle system with lots of objects. I did this by creating a plane, giving it a hair particle system set to count `10,000,000` and set it to \"render as\" a Suzanne object\n5. Render the scene. Take note of roughly how long it takes for the render to initialize. Roughly 2 minutes for me.\n6. Render the scene again. (I'm not sure why but this steps seems to be necessary)\n7. Reduce the particle count on the plane. I reduced it to `1,000,000`.\n8. Render the scene again. Notice how the render takes a really long time to start. (I gave up after waiting 15 minutes.)\n\nHere is a file that does step 1-4 for you:\n[Persistent Data Long Intialization Time.blend](Persistent_Data_Long_Intialization_Time.blend)\n\n**NOTE:** This is not an out of memory issue, at least from what I can tell. Blender gets nowhere close to using the entirety of my RAM (64GB) or VRAM (24GB) during tests using CPU or GPU for testing." ]

[ "Cycles Optix rendering slows down on second tile\nOperating system:Windows 10\nGraphics card: 1x Nvidia RTX 2080 Ti\n\nBroken: Blender 2.82a\nWorked: every previous version\n\nWhen I render on Optix sometimes (50% times) rendering goes extremely slow after rendering the first tile of render\n\nThis is happening to me only on hudge scenes like 1,44GB. And this is not happening every time but quite often ( 50% of times )\nTo Explain that let's just assume that we have an interior scene which has nothing special in it ( I know that optix is not working with AO shader and branched path tracing)\n 1. I hit render and first tile is rendering really fast and when I'm checking how my card is vorking cuda usage looks like this:\n\n2. But after rendering first tile, second goest extremely slow and my cuda usage looks like this\n\nand expected time of rendering goes from 1 hour up to 15 hours or even 20 hours\n\nI know that you might say that not every tile is rendering with the same speed but that is not an issue. When I restart PC or sometimes when I restart blender or sometimes when I prerender scene for something like 1 minute with material override option enabled render goes in the correct way. What I mean by that is that:\n 1. I hit render (same camera same samples and all other settings) \n 2. Render goes with almost same fast speed on every tile and full render is acomplished after 1 hour. My cuda usage looks like this: \n\n As I wrote before this happens to me only on complicated hudge scenes but my work consits only those type of scenes ( I'm interior designer)\nI have this problem since the first release of blender with optix rendering. I,ve also checked tenperatures on my GPU and nothing goes above 66 degrees.\nHere is my file but it is quite large 1,44 GB:\n[poznań restauracja zmiany evee zmiany ewa textury small.blend](poznań_restauracja_zmiany_evee_zmiany_ewa_textury_small.blend)\n \nFor me it is hude deal if my render goes 1 hour or 15 hours so pls help me :)\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", "Inset faces and Bevel Edge command has bugged interaction with Undo command and shape keys\nOperating system: Windows-7,10\n\nBroken: version: 2.83 (sub 2)\nBroken: version: 2.82 (sub 6)\n\n\nIn edit mode, while selecting a shape key, the Inset operation (I) followed by any other operation (Translating vertices or extruding or whatever), followed by an Undo (Ctrl-Z) command causes the shape key selector to hop to the \"basis\" shape key. This also occurs when using the `Bevel` command.\n\nFrom Default Startup:\n1. Create two shape keys: \"Basis\" and \"Key 1\"on Default Cube. Selection will be on \"Key 1\"\n2. Go into edit mode\n3. Inset a face on any of the existing faces with \"I\"\n5. Do ANY other operation or operations, such as moving a vertex or extruding. The bug occurs with any number of operations done after the Inset command.\n6. Undo (Ctrl-Z)\n7. Observe Shape key information as the undo command causes the selection to switch from \"Key 1\" to \"Basis\".\n8. Keep `Undoing` until you `Undo` the `Inset` operation.\n9. Notice that the shape key selection jumps back to \"Key 1\" as you `Undo` the `Inset`. \n", "shift+key with option click\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7262\n\nBroken: version: 2.90.0 Alpha\n\n[problem with a key set to 'CLICK' and with shift=True]\n\nIf I do a shortcut with e.g: km.keymap_items.new('wm.call_panel', 'S', 'CLICK', shift=True)\nI need to press and hold Shift and then press and release S. \nI mean if you do a click on a key without shift or ctrl or alt, the option is respected. but adding a Shift for example the property is not working the same anymore.\napparently in the programing of this click option the presence or not of another key has not been considered.\nthe interest of a click as it is explained in the blender help is when you add another key with the same shortcut but with the option 'CLICK_DRAG'\n\n\n", "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 ", "Wayland: Unable to access window position, finding the window under the cursor doesn't work\nWayland can't access window positions. From what I can tell this is an intentional limitation and there aren't ways to access this information.\n\nThis means functions such as `WM_window_find_under_cursor` doesn't work.\n\nFrom the user perspective the following functionality wont work.\n\n- \"Swap Areas\" / `SCREEN_OT_area_swap` isn't able to swap areas with another window.\n- Some \"Eyedropper\" functions such as `datadropper_win_area_find` wont be able to access other windows.\n- Dragging items between windows doesn't work (see `wm_event_cursor_other_windows`).\n\nCurrently `GHOST_SupportsWindowPosition()` has been added to prevent other windows being found when they shouldn't be.\n\n\n---\n\nNOTE: there is a proposed solution that might allow Blender to restore the positions of windows saved in a file: see: 18\n", "Can't type tilde (~) in text editing mode - Blender enters fly/walk navigation immediately\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\nOS Language: Brazilian Portuguese\nKeyboard layout: United States (international)\n\nBroken: version: 2.90.0\nWorked: don't know\n\nUsing the `ENG` layout the tilde (~) is in this position on the keyboard:\n\n\nIt can be entered by pressing {key Shift `}.\nHowever, this is the shortcut of another operator:\n\n\nThis conflict causes the `VIEW3D_OT_navigate` operator to run instead of the `FONT_OT_text_insert`.\nPressing {key Shift `} (grave accent) enters into fly/walk navigation even when in text editing mode. This makes it impossible to type letters with tilde (i.e. \"**ã**\") directly into Blender.\nThe workaround for now is typing the text I need in another program and then pasting into Blender.\nThis is quite annoying, specially for someone who speaks another language, or has the tilde in his name, even if one uses the English user interface.\nThis bug might be related to #66607.\n\n\n - Open Blender with a new file.\n - Add a text object.\n - Enter text mode ({key TAB}).\n - Press {key Shift `}\n\nThis enters the fly/walk navigation mode immediately, instead of registering the tilde deadkey.\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", "Bisect Tool Snap does not Work\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.1\n\nWhen using the bisect tool and dragging the yellow arrow, snapping does not work when holding the CTRL key despite it being an option in the context tool bar. With the rotate gizmo it works fine. \n\n1. Add for example Suzanne.\n2. Select the whole mesh.\n3. Use the bisect tool.\n4. Try first the rotate gizmo and hold Ctrl, snapping works fine.\n5. Now use the yellow arrow instead, no snapping at all regardless of the snapping settings.", "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", "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.", "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)]", "depsgraph.view_layer.name driver expression doesn't work correctly\nOperating system: Windows 11\nGraphics card: Geforce RTX 3090\n\nBroken: 3.3.5 LTS\nBroken: 3.5\n\nI use a driver expression to control modifiers visibility or shader values depending on a view layer name. If the needed view layer is active, then values change. All works well when switching viewlayers manually inside the viewport of my scene. But as soon as I render the scene, the expression is ignored and nothing happen.\n\n* Open attached file\n* Change view layer few times\n\nDriver will change only once. This also doesn't work when rendering.\n\n", "Splitting two modifier keys between two input devices doesn't work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.0\n\n\nPressing modifier keys from two keyboard device doesn't correctly register in blender.\n\n\n- Have two physical \"Keyboard\" device that both have modifier keys\n- Press Ctrl on keyboard 1 and Alt on keyboard 2\n- Blender doesn't recognize that both Ctrl and Alt are pressed.\n\n-----\n\nOriginal description:\n\nHi - I have modifier keys (shift, alt ctrl) assigned on mouse and keyboard and razer keypad. \nI use alt to select edge/face loops without issue. \nIf I press shift+alt on keyboard then I can select as many loops as I like. Same if I press shift+alt both on mouse. \nHowever, if I use modifier keys combined between deviced (shift on keyboard and alt assigned on mouse, or vice versa) then it lets me add only one additional loop to selection only. \nI initially thought it was accessory issue, but Its true with my default keyboard, razer keypad, logitech G600 and Razer Naga mouse, I suspect the issue is within blender. \n\nIn summary combining modifier keys between keyboard/mouse doesn't seem to work, atleast with loop selections. Any advice? Thanks\n", "Double click is recognized even when the first click is consumed to close a menu\nOperating system: Windows 10\n\nBroken: 2.80 release, 2.81 5e5cf9ea9f7\nWorked: (optional)\n\nWhen clicking on a workspace name to close the splash screen, the second click gets treated as double click if it occurs fast enough. As a result instead of switching to the workspace, the workspace name switches into text edit mode.\n\nIt happens with other menus too, with wheel menus even when the first click is selecting an option at same time.\n\nObject names in the outliner do switch into text edit mode too.\n\n - Open Blender or make splash screen visible.\n - Double click on the name of a worskpace or object\n\nResult: Workspace (or object) name is in edit mode.\n\n**Or**\n\n - Move the default cube away from the 3D cursor\n - Shift + S to open Snap menu (wheel)\n # Double click on a workspace name while \"Selection to Cursor\" is highlighted\n\nResult: Selection moved to cursor and workspace name is in edit mode.", "Keep Alt Key not work in the F-Curve properties\nwin10 64bit, gtx1060\n\nBroken: 2.79a 8928d99270f\nWorked: (optional)\n\nKeep alt key for multiple objects not work in F-curve property ( N panel )\n\nOpen my .blend file, when I select multiple curves and keep alt key to twice the Interpolation or Easing option, it's just worked in one cure,not for all selected, if this is bug, please fix, it very useful for lots curves, else I must one by one to change those, thanks.\n\n\n\n[bug.blend](bug.blend)" ]

[ "Alt+Wheel mouse doesn't work in \"Loop Cut & Slide\" operator (and in Slide operators) to change the control edge with (E)Even option\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.4549\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIn the \"Loop Cut & Slide (Ctrl+R)\" operator (Edit Mode), and in any other Slide operators, the shortcut \"Alt+Wheel mouse\" doesn't work for change the \"control edge\" with the (E)Even option active.\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", "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", " EXCEPTION_ACCESS_VIOLATION when entering Edit Mode\nOperating system: Windows 10 1903 (18362.239)\nGraphics card: Intel HD Graphics 4000\n\n***Broken:***\nBlender 2.80 (sub 75) / 2019-07-29 09:44 AM Windows / Stable\nBlender 2.81 (sub 1), branch: master, commit date: 2019-08-13 11:31, hash: 6f9cbbc8ec4f\n***Worked:***\nBlender 2.79 (copied mesh over through copybuffer.blend)\n\n\nWhen entering edit mode of a specific object Blender crashes with EXCEPTION_ACCESS_VIOLATION. Logs and example .blend provided.\n\nThe issue shouldn't be in my GPU, since the same issue persists even with Software Rendering.\n\n1. Open up example file\n[window_broken.blend](window_broken.blend)\n\n2. Select `window_panes` and enter Edit Mode\n3. Get EXCEPTION_ACCESS_VIOLATION\n\n**Logs (2.80 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n**Logs (2.81 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "Blender Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\nOperating system: Windows 10 - 22H2\nGraphics card: 3090ti 31.0.15.3667\n\nBroken: (3.5, 3.5.1, 3.6.1)\nWorked: None\n\nBlender Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\n\nI have a volumetric setup in the scene. To show up as haze on the horizon. Error only occurs when Volumetric is active.\n\nEnsure the WorldSphere is enabled for render and just render animation for 1279. \nIt will do 1 - 10 frames before throws the error attached. \n\nFile is too big for the attacher, please get blend file from google drive link.\n\nview?usp=drive_link\n\nSimplified: view?usp=drive_link\n\n", "Crash when selecting object on Mac\nOperating system: macOS-12.5.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.3.0\n\nSystem crash trying to open einar_hair.blend file\n\nDownload einar_hair.blend fle from ?asset=6072\nSelect any object.\n\nBlender will crash. Also hair is not visible. It's possible, that OS will crash as well. ", "[ Linux/ Wayland ] Cannot use evee with nvidia\nOperating System: Arch Linux \nKDE Plasma Version: 5.27.7\nKDE Frameworks Version: 5.108.0\nQt Version: 5.15.10\nKernel Version: 6.4.10-arch1-1 (64-bit)\nGraphics Platform: Wayland\nProcessors: 8 × Intel® Core™ i5-9300H CPU @ 2.40GHz\nMemory: 15.3 GiB of RAM\nGraphics Processor: Mesa Intel® UHD Graphics 630 + Nvidia GTX 1660 ti \n\n\nBroken: Blender 3.6 (in wayland session) \nWorked: Works in X11 session with nvidia prime.\n\nIn x11 i can use blender evee with nvidia-prime but in wayland i cannot use blender evee with nvidia prime. The blender window \ndoesn't open at all. \n\nI have two graphics card, one integrated intel & another discrete graphics card nvidia. \nCycles works fine with nvidia in wayland session but when i try to use evee it uses integrated graphics instead of \nnvidia card. \n\n\n1. Login to wayland session.\n2. Open blender with nvidia-prime to run the program with nvidia. ( $ prime-run blender )\n3. Try to render using evee\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.", "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", "Mem leak when rendering on GPU\nOperating system: Windows 10 20H2 Build 19042.985\nGraphics card: Gigabyte RTX 30870\n\nBroken: 2.92 - 3.0\n\n\nRender 2.92 splash screen on GPU 60337d495677e942564cce76\n\nOn CPU, memory usage was 18GB, on GPU it went to 60GB and I had to terminate the process.", "Hair Dynamics: cannot generate a valid particle cache\nOperating system: 4.20.12-gentoo Linux\nGraphics card: Radeon(TM) Pro WX9100 (VEGA10, DRM 3.27.0, 4.20.12-gentoo, LLVM 6.0.1)\n\nBroken: 2.80 (sub 48) commit hash: bf9904ec8018 Build: 2019-03-13 01:14:16 Linux Release branch: blender2.7\n\nWorked: (optional) 2.79b commit hash and date unknown; compiled from Gentoo repository\n\nFails to make a valid particle cache when rendering a dynamic hair system via Cntl + F12. Hair particle motion appears compromised after the first frame. see video clip **dyn_on.mkv**.\n\n**Require**\nA .blend file with a mesh object that has a hair particle system defined on it. Hair dynamics is turned on in the particle system properties panel. The file should have been previously saved without a cache. Blend file **dyn_on.blend** provided for this requirement. \n\n1. Open **dyn_on.blend**\n2. Cntl + F12 to render animation (implicitly build in-memory cache)\n3. Observe:\n```\n a. Cache indicator on timeline shows only 1 or 2 valid initial frames; remaining 248 - 249 frames are invalid.\n b. Hair particles exhibit only limited rotational dynamics. They do not follow the surface of the sphere (i.e., they appear \"unanchored\"), nor do they seem affected by gravity. See **dyn_on.mkv** video clip.\n c. After the last frame has been rendered, click on the rewind control in the timeline. The cache section in the Particles properties reports the state of the cache: \"1 frames in memory (216 KB), not exact since frame 0\"\n```\n\n**Workaround**\n1. Bake particle dynamics first or\n2. Run the animation through in the 3D viewport to create an in-memory or on disk cache before rendering.\n\nRendering with an in-memory, on-disk, or with baked dynamics appears to generate an unaffected animation. See **dyn_on_cache.mkv** video clip.\n\n**Notes:**\n1. Examples rendered in Cycles, but EEVEE and Workbench rendering does not change behavior.\n2. Hair particles rendered with a collection of simple mesh geometry in the examples, but rendering with single mesh objects or rendering hair paths does not change behavior.\n3. Running in single thread mode (-t 1 on command line) does not change behavior.\n4. Rendering via CPU or GPU does not change behavior.\n5. Problem seems specific to hair particle systems. Emitter particle systems without pre-computed caches can be rendered with Cntl + F12; the cache seems fully valid in the time line, dynamics of falling emitter particles do not seem unusual and the cache section in the Particles properties reports that there are 250 valid frames in memory at the conclusion of the animation.\n\n**Related:**\n#62439 describes a failure in particle updates which seems very similar in appearance exhibited by particles in video clip **dyn_on.mkv.**\n\n[dyn_on_cache.mkv](dyn_on_cache.mkv) - dyn_on_cache.mkv\n[dyn_on.mkv](dyn_on.mkv) - dyn_on.mkv\n[dyn_on.blend](dyn_on.blend) - dyn_on.blend\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)", "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", "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", "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", "bevel modifier shading error\nOperating system: Windows-10-10.0.18362-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\nHarden Normals option inside the Bevel Modifier, generates shading error.\n\nOpen the file to check it.\n\n\n[bevel.blend](bevel.blend)" ]

[ "Cycles render does not render hair when using GPU rendering\n**Windows 10 Pro**\nWindows 10 Pro x64 Nvidia Geforce GTX 750 ti\n\n**2.75a**\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n**GPU rendering fails when hair are being rendered**\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Bake All Dynamics doesn't work when baking particle hair\nMacBook Pro, NVIDIA GeForce GT 750M, Intel Iris Pro\nMac OS 10.12.6\n\nBroken: Blender 2.79 Hash: 5bd8ac9\n\nHitting the Bake All Dynamics to bake out particle hair doesn't do anything.\n\nLoad the attached file.\nSelect the sphere.\nGo to the particle panel.\nUnder Cache, click Bake All Dynamics.\nNothing happens.[sph.blend](sph.blend)", "Dissolving edge doesn't work as expected\nOperating system: Windows 10\nGraphics card: RTX 2070 SUPER\n\nBroken: 3.2.1\nWorked: not sure\n\n\nDissolving edges doesn't work as expected.\n\n\n\n\n\n[untitled.blend](untitled.blend)", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "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", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "Particle don't emit curves/text in 3.0 beta \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nCaused by b9febb54a4.\n\nParticle don't emit TEXT\n\nNo particles text from 3.0 [Particle_Text_NOT_Working.blend](Particle_Text_NOT_Working.blend)\n", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script", "Boolean Modifier not working \nOperating system: Windows \nGraphics card: Nvidia Geforce GTX 770\n\nBroken: 2.93.4\nWorked: 2.90\n\nIf one tries to apply the boolean modifier \"Difference\" it does nothing. In previous version it functions.\n\n1. Download the Blender File from above \n2. There a 3 objects in the collections. The objects are in the positive xy-quardant. (Sorry that they are not centered)\n3. If one tries to apply the modifier on the Frame object there is no error message but the frame object doesnt get modified.\n\nGreetings Philip \n\nTest File:\n[#71360.blend](T71360.blend)", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "Blender 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", "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 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", "With ThinkPad keyboards Zoom does not work with the trackpoint and middle button\nOperating system: Linux ubuntu 22.04\nGraphics card: Intel HD4600 + NVidia GT730M\n\nBroken: 3.4.1\nWorked: Works correctly until Blender version 3.3.1\n\n\nIn previous versions of blender moving the trackpoint and pressing the center button of the trackpack on thinkpad keyboards blender zooms in and out. In version 3.4.1 it no longer does. In 3.4.1 rotates the wiev. Does not work with or without 3er button emulation. In previus versions it works correctly, does zoom in and out. \n\nBased on the default startup or an attached .blend file (as simple as possible).\nStart blender move the track point while cicking the middle button on the trackpad.\nUntil blender 3.5 it does zoom, in 3.4.1 rotates the view. (I think in some alpha 3.4 it works but not in 3.4.1)", "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" ]

[ "Blender 3.0\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\nBlender 3.0\n\nBlender goes to Not Responding. I must go to task manager and end blender.\n\nThis only happens with this file, not with a factory reload file or other files.\n\nScene Properties, Audio, press Update Animation Cache, button goes blue and stays blue. When you press anything else, you get ‘Not Responding’.\nUsing 3 SPEAKERS but even muted this happens.\nHave 3 speaking parts and trying to make mouth animations sync with audio (Bake sound to f-curves).\n[Chamiaholom.blend](Chamiaholom.blend)\n\nBy the way I do not know how to find this task again. Maybe you can send an E-mail to me at guccumatz@yahoolcom to tell me how to find it. Thank you. Regards,\nRoberto Collins Lazo\n\nHey, I found the problem. I was not waiting long enough before pressing something else. Perhaps because the file is big it takes longer to update.\n\nThanks. You can close this." ]

[ "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 Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\nOperating system: Windows 10 - 22H2\nGraphics card: 3090ti 31.0.15.3667\n\nBroken: (3.5, 3.5.1, 3.6.1)\nWorked: None\n\nBlender Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\n\nI have a volumetric setup in the scene. To show up as haze on the horizon. Error only occurs when Volumetric is active.\n\nEnsure the WorldSphere is enabled for render and just render animation for 1279. \nIt will do 1 - 10 frames before throws the error attached. \n\nFile is too big for the attacher, please get blend file from google drive link.\n\nview?usp=drive_link\n\nSimplified: view?usp=drive_link\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).", "gpu module in CustomRenderEngine causes segfault\nOperating system: Linux-5.4.2-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.7\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nUsing gpu module in CustomRenderEngine render function causes segfault\n\n- Open attached blendfile\n- Run the python script from text editor\n - it is based on the example bpy.types.RenderEngine.html\n - only difference is, importing gpu module and doing a gpu.matrix.push_pop() in the render function\n - also added faulthandler to see where it crashes\n- change render engine to custom\n- hit f12 (blender crashes)\n\nIs the GPU module not suited for use in CustomRenderEngine ?\nAlso testet drawing a gpu.types.GPUBatch to a framebuffer object without doing matrix.push_pop(), it also caused a segfault. The matrix thing is just the simplest case to reproduce.\n\n[CustomRenderBug.blend](CustomRenderBug.blend)\n\n", "2.93 EEVEE viewport worse performance on iGPU\nOperating system: W10 20H2\nGraphics card: i5-8250U - IGPU UHD Graphics 620\n\nBroken: 2.93 release (windows store)\nWorked: 2.92 release (windows store)\n\n\nWith the new update i'm getting worse performance in EEVEE viewport, in the 2.92 version i had 18 fps, while in the new 2.93 i'm getting 8 fps\n\nScene has 1.200.000 tris\n\nScene has 40 mb \n\n[castle_of_maldrak.blend](castle_of_maldrak.blend)", "GPUOffScreen example give strange \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.1.2\n\n\n\n1. copy the code from here gpu.html#rendering-the-3d-view-into-a-texture\n2. run it \n\n", "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", "4090 has problem with texture in render preview\nOperating system: Windows 11\nGraphics card: Nvidia Geforce 4090\n\nBroken: (3.4 and 3.5.1)\nWorked: none.\n\n**Short description of error** \nThis only started recently, has been fine up till today. My preferences are set to use both the CPU (AMD Threadripper 32) and the GPU (geforce 4090) in OptiX (or CUDA, doesnt seem to matter). Once the file opens, material preview works fine. (refer to \"materialpreview.png\") but when i click render preview (refer to renderprevier.png) all i see is my rig. Anything with a texture is a similar dark grey as the default blender background. I can move the camera around fine, but no textures are visible. If i click material preview again to switch back, blender freezes and must \"end task\" in task manager. If i turn off the GPU assistance and only have the CPU enabled, everything works as it should. \n\nYesterday i updated to latest windows 11 update. I also updated my gameready drivers for my 4090. When the issue started, i thought it might have something to do with gameready drivers so switched to Studio drivers. This did not fix it. \nAssuming that these updates may have broken my file, i rolled back windows 11 drivers to most recent previous version, and did the same with the nvidia studio drivers (uninstalled 5.35.... installed 5.31). This fixed nothing.\n\nI would love to know why my GPU can't be used with Blender suddenly. Games work fine. Furmark 3d app works fine, no issues. Heat is fine. Very frustrating to have such expensive gear suddenly stop working.\n\n", "Cycles HIP binaries disabled due to compiler bugs\n### Tasks\n\n- [x] Enable on Windows (#107098)\n- [x] Enable on Linux (#107662)\n- [ ] Enable Radeon VII (gfx906)\n\n### Background\n\nThere are known bugs in HIP compiler that are causing random build failures when making changes to the Cycles kernel. This is preventing developers from efficiently making improvements to Cycles.\n\nCycles AMD GPU rendering were disabled in Blender 3.6 alpha, so that ongoing work like Principled v2 is not blocked. Additionally light tree sampling is not available for HIP in Blender 3.5. We hope this can be resolved later on in the 3.6 release cycle.\n\nRelevant FIXME's in LLVM amdgpu backend (in fact I suspect we hit the same ones back when we were using OpenCL).\nSIRegisterInfo.cpp#L221\nSIRegisterInfo.cpp#L296\n\nMost recent issues:\n#104085 (#104720 )\n#104669\n#104097\nD16714", "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", "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 when rendering animations (GPU Subdivision ON, OFF is fine)\nSystem Information\nOperating system: WIndows 11 22H2\nGraphics card: Nvidia GeForce RTX 4080\n\nBlender Version\nBroken: 3.4.1, 3.5, 3.6\n\nForce closes when rendering animation after a number of frames and when opening larger blend files. Happens with all files. All drivers up to date and tested memory with no issues. Worked without issue for 6 months, crashing started 1 week ago.\n\nRendering animation with GPU Subdivision unchecked did not trigger a crash", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "closest_point_on_mesh() freezes Blender when called from a driver\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: 2.79\n\nCalling closest_point_on_mesh() from within a driver causes Blender to freeze.\n\n[test2.blend](test2.blend)\nOpen the file allowing scripts -> Freeze", "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" ]

[ "Blender 2.80 does not recognize my graphics card for GPU render in Cycles (and it should).\nOperating system: Linux-5.1.8-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 550 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 Beta Linux 64 bit - July 19, 23:05:03 - c2e8e249acf9\nWorked: Blender **2.79b** (blender-2.79b-linux-glibc219-x86_64)\n\n\nIn official Blender 2.79b I can see my graphics card and use it for GPU rendering with CUDA... In newer versions it doesn't work anymore. Blender just says \"No compatible GPUs found for path tracing. Cycles will render on the CPU\"... this has been happening for months now in newer versions than the official 2.79b, I just hadn't the time to report it until now, sorry.\n\nP.S.: I've checked the \"list\" of supported GPUs for Blender 2.80 and my GPU should still work. ( supported-gpus-in-blender-2-80/ )" ]

[ "Rigidbody doesn't work when you change motion blur steps in eevee\nOperating system:debian buster\nGraphics card:nvidia gtx 1070\n\nBroken: (example: 2.90, 0330d1df29c0, master, 2020-08-31, as found on the splash screen)\nWorked: Never\n\nRendering unbaked rigidbody simulation in eevee with motion blur with 2 or more steps will cause simulation to stop working.\n\n[#80388.blend](T80388.blend)\n- Open file\n- Check if rigidbody simulation works\n- Render image\n- Check if rigidbody simulation works\nIt doesn't work anymore.", "EEVEE-Next Volume Rendering\nUnified volume rendering will first be ported before adding any other feature. Fixing the flickering and object bounds are still major targets for the 4.0 release but are considered nice to have and could be made during Bcon2\n\nHere is a breakdown of the tasks:\n- [x] Needs compute shader based pipeline for world and geometry.\n- [x] #107176 Port current unified volume rendering as-is using compute shaders.\n#### Milestone: Volume Rendering minimum-viable-product for 4.0 release.\n\n- [ ] Correct bounds.\n- [ ] Fix flickering by changing the sampling scheme.\n#### Milestone: Extended feature for 4.0\n\n#### Extended targets\n- [ ] Support shadow casting onto opaque surfaces.\n- [ ] Support irradiance.\n- [ ] Support in bake.\n- [ ] Support per pixel volumes.\n- [x] Optimize by skipping unseen tiles.\n", "Cycles: GPU Optix kernel loading with Bevel/Ambient Node.\nXMGNEO17 Laptop AMD Ryzen9 5900HK Radion.\nOperating system: Windows 11 Home. 21H2\nGraphics card: Nvidia Geforce RTX 3080 Laptop GPU. 16 GB VRAM.\n\nBlender 3.2-3.4 show the error. Blender 3.1 and before not.\n\nThe error happens when ever an Ambient Occlusion or Bevel Node is used and connected in a shader and GPU option OPTIX is enabled for rendering in Cycles. It does not happen with CUDA or CPU.\nBlender will start render process and stops with the line: Preparing for rendering, this can take time.. etc. At that point the UI is still working, but will freeze after trying to cancel rendering. Blender can only be forced to shut down. Scene changes are lost. \n\nThe but is very simple to reproduce:\n1. Open Blender and apply a shader to the cube. \n2. Add a bevel/Ambient node to the shader and connect it to any input. Doesn't really matter which.\n3. Enable Optix in the preferences and set cycles as render. Make sure its set to use GPU.\n4. Switch viewport to preview render.\n5. Blende will stop preparing the scene and won't move further. Its UI is still reacting until trying to stop the process.", "Image sequence render just stops on Cycles on MacOS Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Ultra 1.2\n\nBroken: version: 3.5.0\nWorked: none, tried 2.93, 3.3\n\nafter about 100 or so frames render just stops, Blender is still responsive, its not frozen or crashed, render bar just sits at %0. I'm doing motion tracking to get some kitbashed 3d elements into the scene. Plays fine in Eevee in the viewport. This is the error I get: CommandBuffer Failed: cycles_metal_shader_eval_displace. Attached ram usage for last 24 hours, I still have plenty of ram!\n\nI've closed the file and retried, several times, never got a render all the way through.\n", "Cycles: Bump node doesn't generate anything in certain conditions\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.3.0\nWorked: all versions from 2.79 to 3.4.0 alpha are affected, there is no working build\n\nI'm trying to generate a normal map using Bump node and color output of the env map as height map, it doesn't work on Cycles while it works on Eevee. Seems like the \"reflection\" output of Texture coordinate node is broken, but it works fine when I'm using another outputs though\n\nOpen the project, then click on viewport Rendered mode button - it'll start Cycles which for some reason can't generate bump map, then switch to Material preview mode - it'll start eevee which works as expected\n[bug_report.blend](bug_report.blend)\n\nEdit: typos and bad english grammar fixed, I believe", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "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 hangs due to deadlock caused by two registered draw handlers\nOperating system: Only happens on Linux (Ubuntu 22.04)\n\nBroken: 3.2.2\nWorked: unknown\n\n\nWhen my addon is used together with the addon [\"node minimap\" ](1366781), Blender hangs/freezes completely under certain conditions (details below).\nTo close Blender in this state, not even Ctrl+C is enough, it is necessary to close the parent terminal from which Blender was started.\n\n\n[addons.zip](addons.zip)\n\n[test.blend](test.blend)\n\n- Install the two addons \"node minimap\" and \"test addon\" from the attached zip file.\n- Enable both addons (search for \"node\" in the addon list to find both).\n- Open the blend file.\n- Convert the editor on the lower left to a Shader Editor.\n# Blender will immediately hang.\n\n\n", "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", "Subdiv hangs blender\n**System Information** DESKTOP-HR30UII\nOperating system:Windows 11 Home Single Language\nGraphics card:2GB NVIDIA GRAPHICS DRIVER\n\n\nBroken: Blender Version 3.5\nWorked: ?\n\nBLENDER 3.5 KEEPS NOT RESPONDING WHILE I USE MODIFIERS \n\nON BLENDER ADD MESH AND ADD MODIFIERS TO SUBDIVISION SURFACE THEN CHANGING THE VALUE OF LEVELS VIEWPORT VALUE ABOVE 4 .THEN ONWARDS BLENDER COMPLETELY STOPS WORKING AND I NEED TO RESTART IT AGAIN\n\n", "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)", "blender3.4 alpha new eevee a rendering on the flashback\nOperating system:windows10 21h1\nGraphics card: amd 6800xt （22.7.1 driver opengl doubled the performance of a version)\n\nBroken: blender-3.4.0-alpha+master.ca172677b1a7-windows.amd64-release\nWorked: There is no version that can be tested\n\n\nScene any scene including cube, whether window rendering or f12, directly exit the software.", "EEVEE viewport rendering loop bug when using walk or fly navigation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nWorked: As far as I know, this bug was always in Blender\n\nEEVEE viewport rendering loop bug when using walk or fly navigation:\nwhile using fly or walk navigation and staying still, the sampling always just jumps back to 0 when finished sampling and just starts sampling over and over again thus creating an irritating loop of constant resampling\n\n1. Use EEVEE\n2. For the purpose of this example, change the scene filter size to 50px so that the effect is easily noticeable \n3. Press shift + ` to go to walk navigation (fly navigation has this bug too)\n4. Stay still so that the viewport could start sampling to the specified amount\n\nNotice when the sample amount reaches the specified viewport samples amount, rendering starts again as in if you have moved\n\n[EEVEE viewport navigation loop bug.blend](EEVEE_viewport_navigation_loop_bug.blend)\n\n\n\n\n\n", "EEVEE doesn't take collection visibility in account with collection instances\nOperating system: Arch Linux and Windows 10\nGraphics card: Intel UHD 620 and NVIDIA GTX 1060 Super\n\nBroken: `3.1 Alpha 43b0ff3054ba`; `3.0 Beta fb0ea94c6303`; `LTS 2.83.19`\nWorked: \n\nWhen baking (cubemaps or irradiance) with visibility collection set, it will ignore collection instances.\n\nTo explain, I've prepared the following screenshot, hopefully it will explain the situation well.\n\n\n\nAs you can see, the cubemap has visibility collection set to *Collection*, where a *Plane, Cube and an instance of Real* are present, however in the cubemap only the *Plane and Cube* are visible, while the instance is left out.\n\nAs a reference, this is how it should've looked like (this was after instances were made real):\n\n\n\n1. Open the appended file\n2. In render settings, under indirect lighting: *Delete Lighting Cache* and *Bake Cubemap Only*\n3. Switch to Renderered view\n4. Observe the missing floating instance of Real\n[eevee_visibility.blend](eevee_visibility.blend)", "EEVEE and Workbench missing animatable properties\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n\nWorking-ish*:\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release) \nBroken:\t\t\t`blender-2.80-f6cb5f54494e-windows64` (official release) and later\n\n\nEEVEE and Workbench's render properties (`Properties Editor --> Render Properties`) are, for the most part, not animatable.\nThis is in contrast to Cycles which, *for the most part*, has all settings set to be animatable.\nBack in 2.79b the OpenGL \"Workbench\" Render options were supported:\n\n\n\nSome of the panels like Film, Simplify and Colour Management (which exist in all render engines) work as expected from 2.7X to 2.8X." ]

[ "Eevee render freezes the windows while it's rendering\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7\nWorked: (optional)\n\n\nRender anything with eevee completely freeze Blender window. Just open Render with default lights&cube scene , press F12 to render and the blender window is froze (unrespond, cant click nor do anything) until the task is finished. Cycle works fine.\nJust upgraded my GPU so not sure if this is a hardware issue.\n" ]

[ "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "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", "Copy Rotation Constraint - adding rotations causes unexpected behaviour\nOperating system: Windows\nGraphics card: GTX 1650 Max-Q`\n\nBroken: v2.81a, v2.81, v2.82\n\nWhen adding a Copy Rotation constraint to an object, the `Add` mode seems to not work correctly\n(or at least how I would expect it to work). For example, setting the rotation of the object to (x,x,x) and\nthe target to (-x, -x, -x) does not consistently result in having no net effect. The value for which this *stops* \nworking is x >= 54.\n\n1 - Add an object, give it a rotation of (80, 80, 80), Euler XYZ (default)\n2 - Add an empty, give it a rotation of (-80, -80, -80)\n3 - Add a Copy rotation constraint on the object, and set the target to empty\n\nThe included `bug.blend` file contains an animation that goes over the values of x as described in the\nabove example from 0-100. The problem can be seen around halfway through the animation at the\ncritical value above.\n\n**Result**\nObject seems to have a weird rotation, which is not the expected outcome. The same happens\nwhen only one of the axes is rotated more, and also when they don't necessarily add up to 0.\n\nThis has been tested on multiple Windows machines.\n\n[bug.blend](bug.blend)\n\n\n\n\n\n\n\n\n", "Collection linking + library override doesn't allow to transform object inside\nBroken: version: 3.6.0\n\n\nLinking this collection and then creating a Library Override on it doesn't allow to move the \"Gear\" object inside such collection.\n\n- Download [Test.blend](attachment)\n- Open Blender and link the collection \"Collection\" from Test.blend\n- In the Outliner right click on the imported collection and do Library Override > Make > Selected and Content\n\n", "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)", "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", "Armature modifier slows down any transforms on an object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 2.92.0\n\nHaving the armature modifer on an object with a slightly high polycount slows down any transformations (move, scale, rotation) done to it in the viewport.\nEven with the modifier disabled in view still slows down its movement.\nThis slowdown is very impactful to the smooth playback framerate of projects.\n\nHere's a video of the steps (I started out in the default scene and deleted all the starting objects)\n0Bgx_1JEouc\n\n- Make a high poly mesh (Eg. Suzanne subdivided 5 times)\n- Add Modifier: Armature\n- Transform the high poly object (Mode, rotate ...) and note the delay in fps", "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", "Behavior for mathutils.Vector.rotation_difference when vectors are aligned\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001\n\nBroken: version: 2.93.0 Alpha\nWorked: Never? (tested on 2.79)\n\n```\nimport bpy\nfrom mathutils import Vector\n\nvector_a = Vector((0.0,-1.0,0.0))\nvector_b = Vector((0.0, 1.01,0.0))\nquat = vector_a.rotation_difference(vector_b)\n\nobj = bpy.context.object\nobj.rotation_quaternion = quat\n```\nIn the `rotation_difference` method shown in the script above, when the angle between two vectors is 180° or close, the resulting Quaternion, although pointing in the correct direction, also rotates on another axis.\n\n- Open attached file\n- Run script\nNote that the object did not rotate exactly 180° on one axis\n[rotation_difference_bug.blend](rotation_difference_bug.blend)\n\n", "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", "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)", "Causing other objects to be named .001 doesn't immediately update the Viewport Name Display\nI found this in 3.0.0 but happens the same in 3.1.0.\n\nWhen you turn on Viewport Name Display:\n\n\nAnd then you rename a new object the same as object that was already in the scene:\n\n\nThe name of the original doesn't update until you somehow \"touch\" the object by moving it, entering Edit Mode etc.\n\nIt doesn't get fixed by simply affecting something else.\n\nIn the .blend you need to select the object with name \"Plane.001\" and rename it to \"Plane\" then the object on the left stays named as Plane until you somehow affect it.\n[Bug-ViewportDisplayName.blend](Bug-ViewportDisplayName.blend)", "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)", "Array modifier is crazy, when using \"object offset\" pointed to empty, which is parented to curve\nOperating system: Mac OS Catalina 10.15.4 (latest)\nGraphics card: Intel HD 6000\n\nBroken: 2.83 beta as of 8-th of May\n\nArray modifier is crazy, when using \"object offset\" pointed to empty, which is parented to curve. And when the CURVE CONVERTED TO MESH -- it just destroys scale of object!\n\n1) Open .blend\n[plants.blend](plants.blend)\n2) Try to move empty -- everything works fine\n3) Select \"empty\" and \"petals\" (with shift) then parent them (Ctrl + P -- to object) to \"bezier curve\"\n4) Select bezier curve and \"convert to mesh\"\n5) Now try to move empty\n\nBefore:\n\nAfter:\n", "Gizmo shifting to different value after release with tablet input.\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\nWorked: 2.79 (haven't tested this extensively)\n\nWhen using a tablet to manipulate objects, the gizmo will often pop to a different location. A similar thing happens in the dopesheet when moving the playhead, it will pop to a different (usually very close) frame. I assume this is due to how the tablet input is being interpreted but after exploring and changing every setting I can find, the problem still persists to a certain degree. \n\nBasically, just select an object, choose the rotate tool (not the r shortcut) and use a tablet to rotate on an axis. I've attempted to record this issue in the attached video. [tablet issue.mp4](tablet_issue.mp4)\n\n" ]

[ "rotation bug\n{[F6216668](blenderbug.blend)}Operating system: Windows 7\nGraphics card: gtx 1070\n\n2.79b \n\n\nHello! \n\nThere is a problem in blender. \n\nSometimes if you rotate an object, and set apply \"rotation and scale\" , the dimensions of object will be changed strangely. \n\nI made a gif, that will help understanding the problem. Also, i attached the blend file.\n\n- [ ](Ph5syOI0IO6CK9pOM9)\n\nThank you!" ]

[ "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)", "Weight Paint Vertex Selection Display issue\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: never really, more on that below\n\nWhen in weight paint mode with\n* vertex selection enabled\n* show wire enabled\n\nedges will not be drawn within the selection\n\n\n**The odd part**\nClicking in an empty space will get the wires to show again, but keep the vertices selected. \nThat's a behaviour that has changed from 3.1.2 to 3.2.2\nPreviously it deselected the vertices but didn't draw the edges\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n* Open the attached blender file\n* you can see that edges are not drawn between selected vertices\n* click in an empty space (important to click, not click drag)\n* vertices stay selected but wires are drawn\n\n", "Texture paint in viewport is not using the color space of the image.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.2.1 30.0.14023.7007\n\nBroken: version: 3.2.0 Alpha\n\nIf you paint a noncolor texture like a normal map, painting it directly in the 2D image correcly uses the non-color space, but painting in the viewport doesn't.\n\n\n- With any non-color texture, try to paint both in viewport and in the 2D image\n[2022-02-15 10-34-07.mp4](2022-02-15_10-34-07.mp4)\n\nAditional note: This seems to happens when you sample from the 2D image. By contrast, if you sample the color from the 3D view, you can correctly paint on it, BUT in the 2D viewer the color becomes brighter.", "Error with paint curves and drawing with mouse buttons\n[system-info.txt](system-info.txt)\n\nBroken: blender-2.80.0-git.cc600de6695a-windows64 (and probably above)\n\nWhen using paint curves, they don't draw upon clicking the right mouse button if specified as the button to select with in the preferences. But they do if you set the mouse button to select with to be the left one. So if you have selected the LMB in the preferences then you can draw the paint curve (I don't mean creating the curve) with the LMB, but if you have chosen it to be the RMB then it doesn't work when pressing the RMB, neither does the LMB. (Also, the UI button for drawing the curve in the stroke panel does not work. But you can draw it when you type draw curve in the search panel)\n \nGo to the *Sculpting* screen layout and create a paint curve on an object (if it helps, I used the the normal *Draw* brush). Open the *Stroke* panel in the *Properties Editor* and set the *Stroke Method* to *Curve*. If you have chosen the left mouse button in the *Keymap* section in the *Blender Preferences* under *Select With:* , then everything works fine. You can draw the paint curve on the object by doing a left click after creating it by doing multiple Ctrl-RMB clicks. But if you now set the mouse button with which you want to select to *Right*, then you can create the paint curve with Ctrl-LMB clicks, but when you try to sculpt/draw the paint curve with either the left mouse button or the right mouse button, none of them work. (And again, if you try to draw the paint curve with the *Draw Curve* UI button in the *Stroke* panel, it will also do nothing but turn blue because you clicked on it...)", "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", "Animation workspace: Switching between tabs causes viewport to change\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0\nWorked: Not sure\n\nChanging between the Texture Paint tab and Animation tab causes the Animation viewport to take on properties of the Texture Paint viewport. If this is working as expected it's not ideal.\n\nOpen a new General 3D project. (Or use attached blend)\nSelect the Animation tab. The viewport should look normal.\nNow go to the Texture Paint tab.\nGo back to the Animation tab.\nThe viewport has taken on the properties of the Texture Paint tab.\n\n(A similar issue with the UV editor and Animation tab also occurs.)\n\n[TexPaintToAnimationTab.blend](TexPaintToAnimationTab.blend)\n\n\n", "Vertex Paint bug with Falloff Angle\nBroken: 2.79.x, Win32 & Mac\n\nSee video below.\n\nTo reproduce, set Falloff Angle to 45, and paint (one continuous stroke)\nwith the brush radius approximately equal to the object.\n\nAll by default (2D Falloff and Accumulate is OFF).\n\n[vertex-paint-falloff-angle-bug.blend](vertex-paint-falloff-angle-bug.blend)\n\n---\n\nSmall brush size is ok:\n\n\nIncreased size produces artifacts:\n\n\n---\n\n[vertex-paint-falloff-angle-bug.mp4](vertex-paint-falloff-angle-bug.mp4)", "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", "Sculpting - Switching stroke method with a shortcut causes a freeze\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1\n\nWhen using E shortcut in sculpt mode to change stroke method of the brush, there is a ~5-10 second freeze every time.\nHowever, when you do the same thing from the brush UI, the switch is silky smooth. See the video for example\n\n1. Open attached file\n2. Switch to sculpt mode\n3. Do a few strokes, press E - blender will freeze for about 10 seconds\n4. Do a few strokes again, this time change stroke method from UI - no freezes here\n\nVideo:\n[blender_am0pkp0Cwy.mp4](blender_am0pkp0Cwy.mp4)\nExample File:\n[sculptbug.blend](sculptbug.blend)\n\n", "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)", "System Hangs while Interacting with the Viewport\nOperating system: Manjaro KDE Plasma\nGraphics card: Intel HD Graphics (Cherry Trail) Atom X7-Z8700\n\nBroken: 3.5.0, 3.4.0, 3.4.1\nWorked: 3.3.2 (Haven't tried newer versions in the 3.3.x series)\n\nBlender causes the entire system to hang periodically while performing any task. Simply rotating the camera or zooming in or out results in the system freezing for minutes at a time. The mouse cursor responds to mouse and touchpad movement, but the system does not respond to mouse button clicks or keyboard input for long periods of time. Neither Blender nor the desktop respond.\n\nWhen rotating, moving or zooming the camera text overlays in the viewport flicker, sometimes the entire viewport flickers, then the system hangs. There are no errors or warnings printed to the terminal\n\nDoesn't appear to be related to a specific file. The issue is present in all blend files and when starting with the default setup.\n\n", "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", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should.", "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)", "Grease Pencil: various issues\n*Note: this tasks can be split up once we get feedback on issues, for now this is to discuss changes to make.*\n\n----\n\n\n- Brush pixels are not pixels,\n```\nshouldn't we use a meaningful value?\n(pixels or blender units).\n```\n\n- Grease pencil brushes have material pointers which are globally overwritten.\n\n```\nWhen you set a material, all brushes are looped over and have their material values clobbered.\n```\n\n```\nWhy have a material attached to the brush at all? This could be a scene level setting (or at least not stored per-brush).\n```\n\n```\nSee: `BKE_brush_update_material` called by rna `rna_Brush_material_update` when setting any material.\n```\n\n- Grease pencil sculpt uses it's own brush system,\n```\nis there a good reason for this?\n```\n\n```\nSince these brushes are fairly advanced (pressure & curve mapping options)\nwouldn't it be better to use the existing brush system?\n```\n\n *Note: while particle system for eg: has 'simple' brush types like this, grease-pencil sculpt brushes are more advanced and duplicate more of what we have for regular brushes used elsewhere.* \n\n- Grease pencil weight brush seems to have no way to paint a weight value (only add weight).\n\n```\nAs with mesh weight paint we should be able to paint a weight.\n```\n\n- In edit-mode, vertex selection exists but is hidden by default (0.0 opacity).\n\n```\nShouldn't they be visible?\n```\n\n----\n\n### Lower Priority\n\n- Internally grease pencil sculp is called:\n\n - grease pencil edit (`GP_BrushEdit_Settings`, `GP_EditBrush_Data`, `GP_BRUSHEDIT_FLAG_APPLY_UV`)\n\n```\nThis is highly confusing since we have grease pencil edit-mode, can't we rename these `GP_Sculpt*`. ?\n```\n\n - grease pencil paint (`GPENCIL_OT_brush_paint`)\n\n```\nPaint is easily confused with draw, seems this is for sculpt/weight painting." ]

[ "Graphics Tablet Lag when in Texture Paint mode in Blender 3.0\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 466.27\n\nBroken: version: 3.0.0\nWorked: (2.92 and earlier)\n\n[Texture paint mode lags when using a graphics tablet, not the case with a mouse.]\n\n[Create a new blender scene, delete the default cube and create a new sphere, unwrap the sphere, switch to paint mode and create a default 1024px by 1024px texture paint slot. Try texturing with a graphics tablet, and it will lag. It will not lag if texturing with a mouse]\n\n| **Blender** | **Brand** | **Model** | **OS** | **Device Driver** | **State** |\n| -- | -- | -- | -- | -- | -- |\n| Blender-3.5.0-e0ef5f360222 | Wacom | Intuos Pro M | Windows-10-10.0.19044.0 SP0| 6.4.0-11 | Working |\n" ]

[ "Bridge Faces missing from menus\nOperating system: Linux-5.3.0-29-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.48.02\n\nBroken: version: 2.83 (sub 4)\n\nThe \"Bride Faces\" operator for edit mode is currently only accessible in the context menu when in face selection mode.\nI would expect it to also appear in the faces menu (Ctrl + F or in the header) since Bridge Edges is also accessible in the edges menu.\n\n\n\n\n\n", "Menu Editor for Quick Favorites\nCurrently users can only manage menu items in the quick-favorites menu by adding/removing items.\n\nThis task proposes to: \n\n- Create a generic menu editor in the user preferences.\n\n - Add/remove menu items\n - Re-ordering menu items.\n - Operators options should be able to be changed or unset - as we have with the keymap editor.\n\n**Implementation**\n\n- This could share UI code with the keymap editor for adjusting operator settings, since internally they are very similar.\n- We may support multiple kinds of menus, besides \"Quick Favorites\", internally there is support for this. Even if this isn't exposed to users initially.\n\n```\nThis would be useful for declaring user defined toolbars for example.\n```\n\n**User Interface**\nHere's how the UI could be organized: \n\n{[F8282863](Screenshot_2020-01-17_at_11.08.58.png), size=full}", "Multi-Object Properties Editing\nIn Blender, we want to make it easier to set values for multiple objects, bones, strips, keys and other items at once. \n\nCurrently you can do this in limited circumstances, but you have to right-click on a value after you've changed it and pick Copy to Selected from the menu or hold Alt while editing values. This not only slow, but also very hidden, and the Alt-key conflicts with Emulate 3 Button Mouse. Lastly, it isn't clear at all to users which values work for multi-editing, and which values don't.\n\nHere's how we would like to solve it:\n\n\n## Selection vs Active\n\nThe concept of ***active*** in Blender means that we only show properties and only affect the active object or item. However, if we want to better support multi-item editing, we must start by making it so the Properties reflects the ***selection*** rather than the ***active*** item, of which there can only be one. Going forward, by default the Properties will be set to reflect the selection instead. This could be controlled in the Properties like so:\n\n{[F8363009](Screenshot_2020-02-22_at_17.34.54.png), size=full}\n*(The search box is added here to reflect how the Properties will be updated when that item is also added, but is a separate feature)*\n\nIf set to ***Active***, the Properties will continue to function as it does today, only showing properties for the active item.\n\n## When there are multiple selected items\n\nWhen the user has selected multiple items, a few things change:\n\nInstead of showing the name of the object at the top, Blender tells the user how many items are selected:\n\n\nIn the list of tabs, only properties sections are shown that are common among the selected items. For example, if you select a text and a mesh object, we don't show Modifier, Mesh or Curve Properties, since these properties only exist on a subset of the selected objects:\n\n\nThis rule also goes for individual panels. Here, both a Sun and Spot light are selected, and we only see properties that are shared between them. A note at the bottom clarifies that you are only seeing the shared subset:\n\n{[F8364914](Screenshot_2020-02-23_at_18.49.33.png), size=full}\n\n## When values differ\nWhen multiple items are selected, Blender will compare values to check if they are the same, or if they are different. If they differ, we change the way properties are displayed, like so:\n\n{[F8363037](Screenshot_2020-02-22_at_17.52.51.png), size=full}\n\n\n\n## Manipulating values across multiple items\n\n\n\nFor simply setting a value to be the same. you would simply type a new value, hit Return, and that value is then propagated to the selection.\n\nFor manipulating numbers and sliders relatively, you can just drag on them (like Alt-dragging today), or type the character '=', so the user can type '= -3' to subtract 3 from the value on all selected items.", "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)", "VSE: Animated sound volume not working when referencing scene\nOperating system: Arch Linux\nGraphics card: AMD with Mesa driver\n\nBroken: 2.81 Alpha, ab519b91b2c4, master, 2019-10-04 22:33\n\nI have multiple scenes in one .blend file using the sequencer. In the first scene (\"ReferencedScene\") I have a sound strip with an animated volume. Playing that scene adjusts the volume as expected. In another scene (\"MAIN\"), I added the \"ReferencedScene\" to the Sequencer. Playing the \"MAIN\" scene does NOT adjust the volume of the sound in \"ReferencedScene\". Instead, the volume level stays constant.\n\nI expected that the animated volume of the \"ReferencedScene\" is the same for direct play back as well as when referenced in the \"MAIN\" scene.\n\n\n- Open the attached file.\n- Play back \"ReferencedScene\" with \"Space\"\n- Hear the volume of the sound fade to 0.0 and back to 1.0 again\n- Switch to \"MAIN\" scene\n- Play back \"MAIN\" scene with \"Space\"\n- Hear constant volume of sound from \"ReferencedScene\"\n\n[vse-sound-volume-bug.blend](vse-sound-volume-bug.blend)\n", "Auto Render doesnt work with scene animations\n{[F8575831](autorender.gif)}Operating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0 Beta\n\nIt should render when the scene animation updates. In general auto render also seems a bit unreliable. eg. Sometimes I turn it off and it keeps rendering, and it doesn't render even if some changes are made to the scene. Anyway in this case it doesn't update when there're scene animations.\n\nFrom startup:\n1. Set \"Use nodes\" in compositor\n2. Turn on \"Auto render\"\n3. Animate default cube (I used rotate here)\n4. Scrub timeline\nIt doesn't auto render with new changes.\n\nWith attached blend:\n- Scrub timeline\n\n[autorender_animation.blend](autorender_animation.blend)\n\n\n", "Different results for select_all option in local view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0\n\nWhen having one of two object in local view the {key A} works different than the command\n```\nimport bpy\nbpy.ops.object.select_all(action='SELECT')\n```\neven though the output in the bottom left window in the scripting tab is the same.\n\n[Based on the attached .blend file]\n1. Select *Cube*\n2. Go in local view\n3. Press {key A} to select **only**the *Cube* because of the local view\n4. Deselect everything\n5. Run the command:\n\n```\nimport bpy\nbpy.ops.object.select_all(action='SELECT')\n```\nBut now you have the *Cube***and** *Cube.001* selected even though you used the same command. The output in the bottom left window in the scripting tab is the same. Shouldn't you select in both times the exact same objects?\n\n[selectAll.blend](selectAll.blend)\n\n", "Splitting strips will change image output\nOperating system: Windows 8\nGraphics card: 550Ti\n\nBlender Version\nBroken: 2.93.0 Beta\nWorked: Not sure\n\nSplitting strips with \"hard\" method will change image output.\n\nAdd movie or image sequence to VSE\nSplit strip by pressing Shift + K\n\nImage will change\n\n", "Proportional editing doesn't work with loop slide\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.2 Release Candidate\n\n\n[2021-07-06 19-47-45.mp4](2021-07-06_19-47-45.mp4)\n", "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", "Outliner toggle animatability\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release)\nBroken: \t\t\tBlender 2.80-2.82 (official releases)\t\t\n\n\nThe animatability of objects, collection (layers) etc... are not available as they were in 2.7X \n\n| 2.7X UI (friendly) | Data | 2.8X UI (friendly) | Data |\n| -- | -- | -- | -- |\n| Exclude Render Layers from having any influence | `bpy.context.scene.render.layers[\"RenderLayer\"].layers_exclude- [x]` | Exclude from View | `bpy.context.scene.exclude` |\n| Restrict Viewport Selection | `bpy.data.objects[\"In Collection 02\"].hide_select = False` | Disable Selection | `bpy.data.collections.hide_select` |\n| ZMask Scene Layer for solid faces | `bpy.context.scene.render.layers[\"RenderLayer\"].layers_zmask[10] = False` | Holdout | `bpy.context.scene.holdout` |\n| ? (new property) | ? (new property) | Indirect Only | `bpy.context.scene.indirect_only` |\nThese properties will be printed on the info editor.\n\nTo show what I mean, I've created a .blend in 2.79b with all the things listed above.\n\n[2.79_Demo.blend](2.79_Demo.blend)\n\nOpen the .blend file in 2.79b and ues the functionality:\n\n - Restricted Viewport Selection in curtin frames\n\n - Masking until frame 4\n\n - Layer excluded completely until frame 9\n\nNone of this works in the listed broken versions... and there is seemingly no mention in the release notes of this being designed not to function anymore.\n\n___\nI'm not sure, nor can I think, of a reason why you can't animate these and other properties collection wide.\nExample: **All** these toggle are not animatable:\n\nI don't know that would constitute a bug as there's nothing to compare the functionality to. *I'm sure it just hasn't been added (yet).*", "Timeline showing key-frames for trackers all the time.\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIn the Layout view, the timeline normally shows only the keyframes for the selected item. When I add do some motion tracking in the movie clip editor and create the scene. Switching back to layout view, the timeline now shows a keyframe on every frame even if I have no objects to select. I can't find a way to hide the keyframes from the timeline either. If I expand the timeline and twirl down the summary, I see lots of trackers with keyframes.\n\n\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.", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "Disabled Selectability: it is still possible to enter other modes (The new Switch Objects operator, py API, ...) - should this be prevented?\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\n\nAfter trying the new Switch Objects operator in Sculpt Mode and Edit Mode, I noticed that the operator completely ignores if an object has Disable Selection active or not in the Outliner.\n[Desktop 2020.09.19 - 22.58.16.01.mp4](Desktop_2020.09.19_-_22.58.16.01.mp4)\n\n1. Have two separate objects in your scene. Go into Sculpt Mode or Edit Mode with one object.\n2. Use Disable Selection in the Outliner on the object you are not selecting in Sculpt Mode/Edit Mode.\n3. Click on the object that uses Disable Selection. You will be able to select it regardless." ]

[ "scene sub-option not appear in video sequence editor\nOperating system : Windows 10\ngraphics card : Radeon(TM) RX 460 Graphics\n\n\nBroken: 2.79 build 2018-03-20 \nin blender ver. 2.79a works properly.\n\n\nIn the 'video sequence editor'. When you click on the menu bar, option **add,** another menu with options appears, one of them is scene, it allows you to choose between the different scenes of the project because if exist only one scene, not show options, if there are several scenes show all but the current scene.\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", "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", "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", "Blender hangs due to deadlock caused by two registered draw handlers\nOperating system: Only happens on Linux (Ubuntu 22.04)\n\nBroken: 3.2.2\nWorked: unknown\n\n\nWhen my addon is used together with the addon [\"node minimap\" ](1366781), Blender hangs/freezes completely under certain conditions (details below).\nTo close Blender in this state, not even Ctrl+C is enough, it is necessary to close the parent terminal from which Blender was started.\n\n\n[addons.zip](addons.zip)\n\n[test.blend](test.blend)\n\n- Install the two addons \"node minimap\" and \"test addon\" from the attached zip file.\n- Enable both addons (search for \"node\" in the addon list to find both).\n- Open the blend file.\n- Convert the editor on the lower left to a Shader Editor.\n# Blender will immediately hang.\n\n\n", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "Rendering animation freezes with particle system\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.91.2\nWorked: 2.83LTS (not sure, this is said in most of the comments)\n\nI am trying to render out an animation based on the CGBoost Blender Launchpad Tutorial. Every time I try to render, it will render around 50-400 frames and then it will just stop rendering new frames. My CPU usage goes straight up to 100% when that happens and my GPU usage drops down to 0%. The Blender UI is still responsive, it is just that the render seems to get stuck on a frame. If I cancel the render, then Blender becomes totally unresponsive and I have to force quit via the Task Manager.\n\nIssue happens in both EEVEE and Cycles\n\n**Workarounds (picked up from comments)**\n- Render animation from command line\n- Check lock interface: {nav Render > Lock interface}\n\n1. Open attached Blend file \n2. Press Ctrl-F12 to render out animation.\n3. Wait for render to freeze on a frame. This can happen within the first few frames or after 400-500 frames. It seems random.\n4. Examine CPU and GPU usage.\n\n[Blender Launchpad.blend](Blender_Launchpad.blend)\n[ING BG.blend](ING_BG.blend) (File provided by @Megaseppl: #85267#1122053)", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "`user_remap` fails silently when object is in edit mode\nBlender 3.6\n\nWay to reproduce:\n1) Create new empty blender project\n2) Select cube\n3) Enter edit mode\n4) Run the code below\n\nResults - mesh wasn't replaced and no errors occured. Expected - to either mesh to change or get some warning/error.\n\n```python\nimport bmesh\nimport bpy\n\nobj = bpy.context.active_object\n\ndata = bpy.data.meshes.new('test')\nbm = bmesh.new()\nbmesh.ops.create_monkey(bm)\nbm.to_mesh(data)\nbm.free()\n\nobj.data.user_remap(data)\nassert obj.data == data\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", "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", "If the user changes the OS terminal to one that cannot be hidden by its clients, then blender cannot hide it\nOperating system: Win11 (also probably true on Win10)\nGraphics card: 3090\n\nBroken: 3.1\nWorked: probably N/A\n\nWhen Windows Terminal is set as the default terminal Blender will launch under it, but can't hide it - the terminal will always be visible and Window>Toggle System Console doesn't work.\n\nUpdated from Harleys comment - since Blender can't work with Windows Terminal and it breaks the use model and menu choice, change this to a request to have Blender only use the old style Windows terminal regardless of the default terminal. \n\nWindows Terminal is a Microsoft replacement for the default cmd window, supporting tabs, settings and other advanced features. \n\n - Install Windows Terminal (Microsoft Store or otherwise)\n - Open it, on the tab bar click the down arrow\n - Click Settings in the menu (or just hit Ctrl-,)\n - Set Default terminal application to Windows Terminal\n - Close, start blender which launches from a Windows Terminal\n - Close the terminal and Blender quits\n - Toggle System Console doesn't work either\n```\n\n```\n\n", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Error message and unable to edit a skeleton when using a library override armature\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: No idea.\n\nBlender generates an error when you attempt to enter edit mode on a library overriden armature. There's no description of what the error is or if there is some extra step to make it work. Hopefully this isn't one of those, \"works as intended issues,\" because then there's no way to make multiple characters share an updateable base rig.\n\n\n- Add an armature, enter edit mode, extrude out a few bones.\n- Save the file and open a new scene.\n- Link in the armature you just created.\n- Make the armature a library override.\n- Try to enter edit mode. Should get an error.\n\n", "Shader not working on Mac blender 3.5 - works in Windows\nOperating system: macOS-13.3-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0\n\nI have been trying to install the Weight Paint Tools paid addon weight_paint_tools?layout=profile&recommended_by=library\n\nThis worked fine for years, up till 3.5, now it crashes upon activation. The developer has attempted to update it for metal, but it still wont work. He's sent me a simplified script that he says should work without errors.. but still errors out. See attached blend file.\n\nRun the script\n\n\nRun the script\n\n" ]

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

[ "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", "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 crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Cycles 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)", "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", "Vertex paint mode breaks permanently under certain conditions (Global undo involved)\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 3.6.0 Alpha\n\nCaused by 575ade22d4de (vertex paint now does `SCULPT_undo_push_begin_ex` in wpaint_invoke [which leads to `BKE_undosys_step_push` using sculpt undo])\n\nVertex paint mode breaks permanently under certain conditions\n\n- turn OFF Global undo in Preferences\n- enter vertex paint mode\n- make two strokes\n- Undo (prior to 575ade22d4de nothing was undone, now stroke is actually undone)\n- Undo again (this now takes you out of vertexpaint mode into object mode prior to 575ade22d4de you would never leave vertexpaint mode)\n- enter vertex paint mode\n- painting is not possible anymore (strokes have no effect)\n- this is also true for other objects\n\n", "Array/Skin-Modifier-Combo causes crash\nOperating system: Linux Mint 19\nGraphics card: GT630\n\nBroken:\n2.80 (sub 39), branch: blender2.8, commit date: 2018-12-20 23:46, hash: 7a26e930a8c0\n\n\nPlease try to toggle the \"visibility\" of the skin modifier in my simple file. It crashes instantly and repeatingly:\n[Procedural leaves feathered1.blend](Procedural_leaves_feathered1.blend)\n", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script", "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)", "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", "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", "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", "Crash on render on some of the frames\nOperating system: Linux-4.4.0-154-generic-x86_64-with-debian-stretch-sid 64 Bits\n8x Tesla V100 SXM2 NVLINK Accelerator Cards\nDual XEON Scalable 4208 CPUs\n192 GB RAM\n\nBroken: version: 2.82 (sub 7)\nI also tested recent 2.83 build\n\nBlender crash when it renders scene frames from 346-639, the rest of the frames are fine.\nIt crashes for CPU anf GPU as well.\n\nIn order to render above frames I workaround the assert:\n\n```\n--- a/intern/cycles/kernel/kernel_compat_cpu.h\n+++ b/intern/cycles/kernel/kernel_compat_cpu.h\n@@ -74,8 +74,10 @@ CCL_NAMESPACE_BEGIN\n template<typename T> struct texture {\n ccl_always_inline const T &fetch(int index)\n {\n- kernel_assert(index >= 0 && index < width);\n- return data[index];\n+ //kernel_assert(index >= 0 && index < width);\n+ if (index < 0) return data[0];\n+ else if (index >= width) return data[width];{F8410049}\n+ else return data[index];\n }\n #if defined(__KERNEL_AVX__) || defined(__KERNEL_AVX2__)\n /* Reads 256 bytes but indexes in blocks of 128 bytes to maintain\n```\n\nThe scene is complex and I couldn't make it very simply and narrow the problem.\nPlease find the scene attached.\n\n[animation_002_02_part01.blend](animation_002_02_part01.blend)\n\n1. Open Blender 2.82\n2. Open attached scene\n3. Set frame 346, start render (F12)\n4. After one minute or so it will crash\n\n\n", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Crash when switching from solid to rendered view\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\n\nI have a scene about 1.7GB in size with 4K textures but renders in 2K using simplify, blender crashes when I open the file > hit F12 and render the scene then close the render windows and switch to render view > it starts compiling then blender closes, in the past it would show out of memory this report: \n\n105522#issuecomment-904934 \n\nThis issue happens only when persistent Data is active\n\nunfortunately I can't share the file at the moment. \n\n\n\n\n" ]

[ "Blender crashes on opening texture paint\nWindows 7 professional 64 bits - NVIda Gforce 8400 GS (Also tested on my acer aspire laptop running windows 8.1 with the same result: crash)\n\nBlender version:2.72 (both 32 and 64 bits)\n\nWorked: 2.71\n\nBlender crashes (without any error message) when going into texture paint mode\n\nShortest way to reproduce: open up blender and from the startscreen with the cube go from object mode to texture mode and voila: no blender (-: " ]

[ "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", "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)", "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", "Seemingly no way to remap \"use tool\" button?\nBroken: 2.80+\nWorked: 2.79\n\nSee 599\n\nThere doesn't seem to be a way to remap or disable the button which activates the tools selected by the buttons found in the T panel. Sometimes this button conflicts with the 2.7x keymap. For example, in the node editor, left tweak *always* applies the selected tool (box select by default), which prevents all the 2.7x Left Tweak shortcuts from working\n\n\n[27_28_keymap.blend](27_28_keymap.blend)\n\n1. Open the file with --factory-startup\n2. Go to the keymap section in the preferences\n3. Select the 27X preset\n4. Try to use the Shift+Left Tweak shortcut to add a reroute node\n5. Box select will be invoked instead", "Regression from 3.3: Invalid button mapping on SpaceMouse Enterprise (256f:c633)\nButton mapping on this device is now completely scrambled. For example pressing \"Shift\" deletes selected object, \"Lock rotation\" is interpreted as play/pause, \"Button 6\" rotates camera 90deg CCW and \"1\" brings up the menu. Other buttons do not seem to register.\n\n\nBus 003 Device 013: ID 256f:c633 3Dconnexion SpaceMouse Enterprise\n\nTested on macOS Ventura and Ubuntu 22.04\n\nIn blender 3.3.2 on Linux and macOS, some buttons function correctly:\n - Shift\n - Ctrl\n - Alt\n - Rotate\n - Top\n - Front\n - Right\n\n Basically all other keys in 3.3.2 bring up the on-screen menu.\n\n\nTested versions: 3.4, 3.5 and 3.6.\n\nOperating system: macOS-14.0-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\nWorked: 3.3.2\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.", "Improve keyboard usage for menu search popup\nNA\n\nBroken: example: 2.78\nWorked: >new feature request<\n\nwhen spacebar search menu popups and user start writing the required command, only down-arrow keyboard shortcut are allowed to select the required command, starting from first item on top.\nIt will be very useful and faster if also up-arrow can be usable to select the last item in the list (so starting from bottom).\nSee image as reference: green arrow show the required feature, red one is the only one actually working.\n\n\nnot an error, only UI usage improvement :)\n", "Lasso Select Broken if Select key is changed from Default Left to Right\nOperating system: Windows 10 (Home)\nGraphics card: Nvidia 1070 \n\n**Blender Version** \nBroken: 2.90.0 (Steam)\nWorked: Not sure, Has been like this since before 2.79b\n\nWhen the default select mode is changed from Left to Right Mouse button Lasso Select no longer works with Tweak + RMB Any. \n\nSplash Screen Change on initial set up or Select button or Edit - Preferences - KeyMap - Select With Mouse Button\n\nAffected: any View Mode that has the Lasso option. (Edit mode, Object Mode, Grease Pencil, etc)\n\n\nSee attached MP4.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nStart Blender and use Start up Cube. [BlendBug_2.mp4](BlendBug_2.mp4)\n\nTemporary fix if the Select key is changed from Left to Right Mouse Button is to walk through the KeyBindings and set anything that uses Lasso to Tweak Right and anything that was using Tweak Left to Tweak Right where Lasso is was changed. ", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "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", "The SHIFT key, mapped on my graphic tablet is not working in Blender 2.80\nOperating system: Windows 10\nGraphics card: NVidia GeForce GTX 1070\n\nBroken: 2.80 25-12-2018\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nI own a Huion NEW 1060 PLUS 8192 graphics tablet. One of my keys is mapped as SHIFT, but Blender doesn't recognize it at all. As one of the pen keys is mapped as the Middle Mouse Button.\nAnother key on the tablet is mapped as CTRL, another as ALT etc. and they all work with the MMB on the pen, but the SHIFT key is not recognizable to Blender. I can zoom, I can rotate, I can change views but i cannot pan nor select multiple objects. Basically, everything that is connected to the SHIFT key is dead.\nBlender recognizes the keyboard SHIFT key, as well as a mapped SHIFT shortcut on the mouse, but not on the tablet.\nAll around the OS and in Rhino, Photoshop, Illustrator, the Shift key from my tablet is working perfectly, but inside Blender no.\n\nOh, and this is the first time I'm trying 2.8. \nEverything works fine in 2.79.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "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>", "Trackpad stops working for a while\nOperating system: MacOS 12.6.5\nGraphics card: AMD Radeon Pro 5500M\n\nBroken: 3.6.2\nWorked: don't know\n\n\nSometimes, Blender stops responding to trackpad gestures such as two-finger scroll or pinch zoom. This is not just in the viewport but everywhere - I can't scroll menus or the node view, for example.\n\nThe UI is otherwise responsive when this happens - I can scroll menus by dragging the slider at the edge, just not with a two-finger scroll.\n\nIf I go and do something else in another app for a few minutes, it usually fixes itself.\n\nThis happens sporadically and I don't have a reliable way to reproduce it, but it seems to happen often after I render an image - after the image has rendered, I try to use pinch-zoom to look more closely and find I can't. I am not sure if it happens in other situations as well - if it does I will update this report.\n\n\nI'm afraid that I can't reproduce this reliably - it just happens every now and then, in any .blend file. I am happy to take any advice on how to look for a way to reproduce it.\n\n", "The version over 3.5 (3.6 and 3.6.2) crashes for me after using control of view.\nOperating system: Linux-6.2.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics 650 (Kaby Lake GT3e) (KBL GT3) Intel 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: 3.6 and 3.6.2\nWorked: version: 3.5.0\n\n\nI have quite simple scene: 1 table, 1 chair. I change selection from chair to table f.x., then deselection or I make zoom out, the screen freezes, Blender proposes me to closing because not responding\n\n", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\n\n" ]

[ "Shortcut keys become unusable in the middle of using blender\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 3.1.2\n\n\n\n" ]

[ "The light and smoke is not rendering in 3.4\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.3 with motion blur off.\n\nThe light and smoke is not rendering in 3.4\n\n\n\n\n**Steps to reproduce**\n[other other.blend](other_other.blend)\n\n- Open file\n- Bake smoke domain\n# Render image\n\n\n\n\n\n\n", "3D Texturing: Limit Eevee samples to 1 during paint stroke.\nGhosting effects appear when painting. We should limit the number of samples to improve the performance and reduce the ghosting effect.", "Improve volume render passes\nCycles volumes mostly do not write to render passes currently. Given the transparency it's not always useful or meaning to do this, but we can do better.\n\nA few known issues:\n- [ ] Cryptomatte is not written for volumes. We could accumulate cryptomatte contributions of objects while ray-marching.\n- [ ] Mist is not written, which causes the background value to be used when the volume is opaque. More useful would be to either write it based on the volume position weight by transparency, or to write mist for the object behind. (#91280)\n- [ ] There is no Volume Color pass currently, equivalent to the Diffuse/Glossy/Transmission Color passes. We do now write albedo for denoising, a similar thing could be added for volumes but it's unclear if this is useful for compositing in practice, especially with overlapping volumes.\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.", "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.", "Eevee volume shader on imported VDB influences other volumetrics density (specified density attribute makes a difference)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\nI've noticed for a while now that if I bring in a vdb file, to a scene that already has fog via a large cube with principled volume shader applied, once I either import the vdb or, if it's hidden and I unhide it, the scene fog via the large cube will suddenly turn off. There's no way to get it back other than to reload the scene/restart Blender.\n\nMake a scene, envelop it in a large cube, apply principled volume shader. Something like 0.025 density or thereabouts. Whatever is thick enough to see the scene and appreciate the fog is there.\nImport a vdb file and apply a volume shader to it. The main fog should disappear. \nThen try putting the fog on the cube up to 1.0 density and you'll notice you get fog back, but, it's not as dense as it should be, even at 1.0 density. \n\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", "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)", "Smoke darkening/miscoloration with multiple inflow objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nHaving 2 or more inflow objects in a smoke simulation, each with its own smoke color, causes darkening and other hue color glitches, even when the two smokes don't mix. At first I thought this was maybe an intended effect, like burning smoke, but with just one flow object the smoke comes out with a proper uniform color.\n\nOpen this file, select the domain and bake the smoke sim to see the darkening, you can see it better in Cycles. You can move the object \"model2\" out of the Flows collection and rebake again with just one Flow object, and see the color to compare\n\nThe attached images use a saturation node on the shader to exagerate the color so you guys can see it more clearly\n\n[BUGREPORT_smoke.blend](BUGREPORT_smoke.blend)\n\n\n\n", "Light Nodetree support\nWhen rendering shadowmaps, we could run a postprocess shader (using the depth texture to retreive position) to output a Mono or Poly-chromatic intensity texture.\n\nThis would enable the use of custom light shaders and IES light profiles.\n\nThis will have to use another sampler since the shadow texture use another format.\n\nEstimate : 2 weeks", "I have glitch when i turn on my Motion blur with a shape keys animate\nHello, \n\nOperating system: Darwin-19.4.0-x86_64-i38{[F8688055](Capture_d_e_cran_2020-07-12_a__01.21.11.png)}\n\n{[F8688058](Capture_d_e_cran_2020-07-12_a__01.21.11.png)}6-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.90.0 Alpha\n\nI tried with Eevee i don't have the problem only with cycles. \nIs only when i render animation or image. I can't see this glitch on viewport.\nI tried with blender version on mac and window and multiples different graphics card but the problem is still append.\nWith or without modifiers or movement of camera still in. \n\n\n\n\nOpen blender with love.\nMake a beautiful animation with shape keys.\nTurn on motion blur.\nProblem when i render :( \nClose blender but with love to help. :D \n\nThanks you \n\npacpac\n\n{[F8688074](Capture_d_e_cran_2020-07-12_a__13.46.43.png), size=full}\n\n\n\n\n\n", "2x RTX 3090 Bugg\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84 x2\n\nBroken: version: 3.0.0\n\n[PHello so u just got my secound rtx 3090 card its and msi geforce, got the gigabyte rtx 3090 before so now i have 2 cards. When rendering with optix denoising in the viewport i get a light bleed even if i have no lights on. \n\nWhen i open a file from 2.92 and open it in 3.0 and hit viewport render and only have one card active it works fine, if i activate both cards it crashes everytime. ]\n\n[When rendering with optix denoising in the viewport i get a light bleed even if i have no lights on. \n\nWhen i open a file (kate) from 2.92 and open it in 3.0 and hit viewport render and only have one card active it works fine, if i activate both cards it crashes everytime. using optix denoiser ]\n\n\n[Kate.blend](Kate.blend)\n\n", "Workbench: Add shadeless to material viewport display properties.\nFeature requested by Heist project.\n\nShadeless is a slider that effectively blends between flat shading and material shading.\nOnly used when shading mode is set to material.\n\nIt is used to make details more visible during layout/previs phase.\n\nIn blender internal this was a toggle, but it is specifically requested to be a factor slider.\n\nNOTE: Check current workbench material if it can be encoded in the current struct, or could easilly be added. Also check if we require new (G-)buffers for this, ot if it can be encoded to somehow..\n", "EEVEE Cryptomatte Processing Performance\nCurrent implementation uses a single core. During implementation it was always kept in mind that we should do the processing in a threaded way. It should also be possible to render the next sample during the integration of the previous sample in the accumulation buffer.\n\nAnother solution would be to do the sorting on the GPU using compute shaders. [D10913: GPU: Compute Pipeline.](D10913)", "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" ]

[ "How\nCan someone please explain it to me how they got Miami Gain Effect in this Blender File here? cloud.blender.org/p/gallery/57e5084f0fcf294119c5055c, I cannot open it because its encrypted with hidden python codes. I just wanna know the light effects (Miami Gain), thank you. \n\nMaybe break encryption so you get how they did light effects on final render?" ]

[ "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", "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", "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)", "QuadriFlow Remesh Crash\nOperating system:iMac (Retina 5K, 27-inch, 2020)\nGraphics card:AMD Radeon Pro 5700 8 GB\nRam: 96 GB 2133 MHz DDR4\n\nBroken: 3.6.0, 3.5.0 Beta and 3.2.1\nWorked: N/A\n\n\nDear all\n\nI found that the QuadriFlow Remesh will crash when i try to remesh (40K) from also most 900K faces. I tested on 30K and so on. The only sucessful try is down to 500 faces.\n\n\nHere is the model for your reference which is modified after 3D print addon (cannot QuadriFlow if not) from the orignal question below and i also record a 1:30min video for reference as well ( YR6oPpNbKis )\n\nModel file: view?usp=share_link\n\nPlease check. Many thanks\n\nOrignal Question: mesh-doesnt-follow-the-armature", "alpha does not contribute to adaptive sampling noise treshold\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\nWorked: i dont think it ever worked\n\nwhen rendering with adaptive sampling enabled, the noise treshold does not seem to be affected by a noisy alpha channel.\n\nthis is most visible on shadow catchers: since their rgb is always black, they are always rendered with \"Min Samples\", as soon as adaptive sampling is enabled.\neven though the alpha channel is still very noisy, it stops rendering additional samples.\n\n[shadowCatcherNoise.blend](shadowCatcherNoise.blend)\n- open file\n- render samples at 64-512 samples\n- when adaptive sampling is enabled, the shadow will remain very noisy. when adaptive sampling is disabled, the shadow will be smooth\n\n", "Mantaflow: emit smoke from particles can't inherit velocity.\nOperating system: windows 10\nGraphics card:\n\nBroken: 2.92\nWorked: 2.83\n\nEmit smoke from particles can't inherit velocity.\n[volume speed bug.blend](volume_speed_bug.blend)\n\n\n2.90.0\n\n\n2.91\n", "Mantaflow simulation is asymmetric even without the influence of any force\nRunning a Mantaflow smoke simulation with a symmetric flow object and no external forces or internal turbulence will produce a readily noticeable asymmetry that looks like a wind force being applied.\n\nAs can be seen, the smoke is biased in the positive direction and the velocity visualizations shows the direction to be intrinsic to the simulation.\n\n\n\n\n\n- Delete everything except the default cube.\n- Add quick smoke to a the default cube.\n- Run the simulation.", "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)", "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", "Noise nodes with high detail and lacunarity values outputs erratic values\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked: ?\n\nLacunarity option was exposed with 0702c24a36. Not sure if that commit caused or exposed this issue because I don't think there was a way to change lacunarity value at user-level before that. Maybe the latter since Musgrave and Voronoi textures seem to have similar issues with high values.\n\nNoise node with high detail and lacunarity values outputs erratic values (values outside of the expected range, nan, inf) in Geometry Nodes. It seems there's no issue in Shader nodes until you give them very high values (ex: detail 15.0, lacunarity: 500.0) but I'm not sure.\n\nNotice that even with the Normalize option enabled it outputs values higher than 1.0 (see the spreadsheet).\n\n\n\n\nTest file: [noise_node_values.blend](attachment)\n\nIt seems this happens when combination of detail and lacunarity values are high.\n\nThe easiest way to trigger the error is set both values very high. It will probably outputs all nan values.\n\n### Detail: 10.0, Roughness: 1.0, Lacunarity: 10.0, Normalize enabled\n\n\n\nWith not so high values, it usually outputs values outside of the range.\n\n### Detail: 6.5, Roughness: 1.0, Lacunarity: 7.5, Normalize enabled\n\n\n\n", "Regression: mantaflow Domain \"Guides\" (velocity source) not working \nOperating system: Windows 11 Pro\nProcessor 12th Gen Intel(R) Core(TM) i9-12900K \nGraphics card: asus dual geforce rtx 3060 12gb gddr6\nRAM:32.0 GB \n\nnot worked: (3.1.2)\nWorked: (2.82.7)\n\nTo simulate the spraying of water fluid, I use the Guide Domain tool so that the water particles react with the smoke coming out of the flow and the spraying mode was simulated, but this simulation does not work in version 3.1.2, but in version 2. 82.7 works properly\nIs this a bug?\nPlease watch the videos\n[3.1.2 not work.mp4](3.1.2_not_work.mp4)\n[2.82 work.mp4](2.82_work.mp4)\n\nfile:[3.1.blend](3.1.blend)", "BMesh.free causes crash under curtain conditions\nOperating system: Linux-5.16.16-200.fc35.x86_64-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.0 Alpha\n```\nall 3.x versions are broken, 3.0.0 sometimes works\n```\nWorked: 2.93.8 LTS\nOn Fedora also some 2.91 versions have been affected, according to rebuild agains newer pythons.\nReported on redhat bugzilla: show_bug.cgi?id=1872980\n\n[blender.crash.txt](blender.crash.txt)\nUsing my python addon blender crashes on _PyEval_EvalFrameDefault or _Py_Dealloc.\n\nUnable to describe simple steps to reproduce. This happens using my python addon, but if a bug is in addon, still shouldn't crash blender but throw an python traceback.\nWhen I delete line describen in crash log's backtrace, then another row is marked as a problem, so unable to identify exactly what's happening.\nPlease, let me know, if you need more information.\n\n----\n\nEdit, run this script with the following command line arguments: [boxmaker_crash_single_script.py](boxmaker_crash_single_script.py)\n`blender -b --factory-startup --python boxmaker_crash_single_script.py`\n", "smoke effects flicker in domain when start frame is set to later than animation start frame\nOperating system: Windows 11\nGraphics card: nvidia geforce rtx 2060\n\nBroken: 3.5.0\nWorked: n/a; never worked since 2.9 at the earliest\n\nWhen smoke domain start frame is set to a value later than animation start frame, smoke effects will flicker inside that domain until the start frame is reached.\n\n`Object Mode` > `Add` > `Cube`, `Sphere`, or any other solid 3d object found in the `Tab` > `Quick Effects` > `Quick Smoke` > Under physics properties with smoke domain selected, set start frame to any value greater than the animation's Start frame > see error for self.\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```", "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 when trying to bake \"Noise\" with Adaptive Domain using Mantaflow\nOperating system: Windows 10 Pro\nGraphics card: Nvidia GeForce RTX 2080 Ti\n\nBroken: 2.90.0 Alpha, 5a13f682ee5f, 2020-07-02 22:21\nWorked: 2.83.1\n\n\nBlender crashes when trying to bake \"Noise\" with Adaptive Domain active using Mantaflow.\n\nOn a new scene, after adding \"Quick smoke\" effect to default cube I activated Adaptive Domain and Noise. I also switched Cache Type to Modular. Than I baked my simulation and tried to bake Noise but Blender crashed at 0%. Everything works when Adaptive Domain is turned off." ]

[ "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)", "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)", "Mantaflow grid visible in spray, foam and bubbles particles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nSpray, foam and bubbles particles take the shape of the grid when simulated.\n\n[mantaflow_bug.blend](mantaflow_bug.blend)\n- Open the file\n- Bake\n- Display spray, foam or bubbles particles\nFoam and bubble particles are very blocky and unnatural\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", "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", "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", "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", "Mesh to Volume crash on small geometry\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nIn some cases with small geometries, the `Mesh to Volume` node ends up consuming a lot of memory and resulting in a crash.\n\nThis was identified when running the background rendering script for the attached production file.\n\nWith the production file, on the 23rd frame (Every time), I got the crash. It does it from the command line OR from the software itself. From the command line, it shows me the information for the last frame (23), then goes into the error message. I copied it below, and the .crash.txt file is attached.\n\n```\nCurrent Frame= 23  Axon Length um=60,  n Soma Mito=15,  n Proximal Mito=3,  n MidNeurite Mito=1,  n Distal Mito=3,  Mito Avg LW Ratio=1.33,  Mito Size=0.36,\nError   : UNKNOWN EXCEPTION\nAddress : 0x00007FFF45F2FE7C\nModule  : KERNELBASE.dll\nThread  : 00003638\nWriting: C:\\Users\\Owner\\AppData\\Local\\Temp\\NeuroMito 823 03b.crash.txt\n```\n\n- Open attached file [mesh_to_volume_crash.blend](https://projects.blender.orgattachment)\n- Reduce the size of primitive geometry to `0.8`\n\n---\n**Steps for the production file**\nThe .Blend file refers to the attached .CSV file. To run it, you just have to change the folder in the script to wherever you saved the .csv file. I used this command to run it from command line, or just run the script to start the rendering.\n\n\"c:\\Program Files\\Blender Foundation\\Blender 3.4\\blender.exe\" -b \"S:\\Phys\\NeuroMito 823 03b.blend\" --python-exit-code 1 --python-text \"Render01\"\n\nThank you as always for your work on this amazing program. I am sure it is something about the way I am using geometry nodes or scripting that is causing this.\n\n", "Mantaflow simulation stops and crashes at the end of the bake (or when closing blender): The CG solver diverged, residual norm > 1e30, stopping.\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nCrash baking fluid simulation.\n\n\nOpen the file and bake all its frames (or only frame 181 to 183).\n\n[beach.blend](beach.blend)\n\n```\nTraceback (most recent call last):\n File \"<string>\", line 1, in <module>\n File \"<string>\", line 169, in bake_fluid_data_5\n File \"<string>\", line 164, in bake_fluid_process_data_5\n File \"<string>\", line 136, in liquid_adaptive_step_5\n File \"<string>\", line 221, in liquid_step_5\nRuntimeError: GridCg::iterate: The CG solver diverged, residual norm > 1e30, stopping.\nError raised in extern/mantaflow/preprocessed/conjugategrad.cpp:562\n(...)\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in extern/mantaflow/preprocessed/fluidsolver.cpp:33\nAborted (core dumped)\n```\n\nComplete output: [P2568](P2568.txt)", "Regression: mantaflow Domain \"Guides\" (velocity source) not working \nOperating system: Windows 11 Pro\nProcessor 12th Gen Intel(R) Core(TM) i9-12900K \nGraphics card: asus dual geforce rtx 3060 12gb gddr6\nRAM:32.0 GB \n\nnot worked: (3.1.2)\nWorked: (2.82.7)\n\nTo simulate the spraying of water fluid, I use the Guide Domain tool so that the water particles react with the smoke coming out of the flow and the spraying mode was simulated, but this simulation does not work in version 3.1.2, but in version 2. 82.7 works properly\nIs this a bug?\nPlease watch the videos\n[3.1.2 not work.mp4](3.1.2_not_work.mp4)\n[2.82 work.mp4](2.82_work.mp4)\n\nfile:[3.1.blend](3.1.blend)", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Mantaflow emitter sometimes creates smoke of wrong color (blue and green channels swapped)\nOperating system: Arch Linux, kernel 6.0.2, but this also reproduced on Win 10\nGraphics card: [AMD/ATI] Hawaii PRO [Radeon R9 290/390] (according to lspci)\n\nBroken: 3.2.0, 3.3.1, 3.4.0\nWorked: not tested yet\n\nThis bug involves mantaflow smoke simulations with an animated emitter color.\nUnder some conditions, the emitted smoke has the wrong color. This manifests in the \"solid\" viewport shading as well as in the shader when the color is read from the Volume Info node.\n\nSpecifically, in the attached blend, when baking the fluid simulation with a domain resolution of 128, the colors are wrong. When baking with a resolution of only 64, the colors appear correct.\nWhen the colors are wrong, it seems that the blue and green channels are swapped.\n\nHere is a screenshot: The emitter color changes every 50 frames, in the order red, green, blue.\nAt the current frame, the correct emitter color would be blue, as shown in the Properties Panel, while the actual emitted smoke color is green.\nNote how the emitter plane itself is covered in smoke of the correct color.\n\n\n\nAlthough this can be worked around in the shader, it seems especially problematic that the bug depends on the domain resolutions (and possibly other factors).\n\n\n - Open the attached blend file and bake the fluid simulation without changing the resolution.\n - Observe how the smoke colors are wrong: blue and green channels are swapped\n - Free bake, change domain resolution to 64 and bake again.\n - Observe how the colors are correct now.\n\n[mantaflow_rgb_bug.blend](mantaflow_rgb_bug.blend)", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "Blender 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)", "Mantaflow: Noise doesn't follow smoke\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 650 Ti\nProcessor: Intel® Core™ i7-3770\n\nBroken: Blender 2.90\nWorked: Blender 2.81\n\nAfter enabling \"Noise\", the Wavelet turbulence doesn't follow the smoke. It seems to only mildly adapt to certain movements; but, unlike in 2.81 it doesn't get \"dragged\" by the velocity of the smoke.\n[NoiseDifference-C.mp4](NoiseDifference-C.mp4)\n\n**Exact steps to reproduce the error**\nIn any smoke simulation (preferably one where smoke is being constantly emitted), enable \"Noise\" and bake.\n\n2.9 Project file: [2.9 Example.blend](2.9_Example.blend)\n\n2.81 Project file for comparison: [2.81 Example.blend](2.81_Example.blend)" ]

[ "Mantaflow Adaptive Domain & Noise Crash\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.87\nCPU: Ryzen 9 3950X\n\nBroken: version: 2.90.0 Alpha\nWorked: 2.83.1\n\nBlender crashes, when baking smoke with adaptive domain and then baking noise.\nOnly occurs with modular cache and adaptive domain.\n\n\n* Factory startup\n* Quick smoke on Default Cube\n* Check Adaptive Domain\n* Set cache to Modular\n* Bake Data\n* Enable Noise\n* Bake Noise\n\nOr open this .blend and click Bake Noise. Baked smoke cache included.\n[bake_noise.zip](bake_noise.zip)" ]

[ "Ctest: Crash in cycles_image_colorspace_cpu\nOperating system: Windows\nGraphics card: Irrelevant\n\nBroken: current master (c32c6a5f85) \nWorked: Unknown\n\n\nDuring testing of [D10212: Cmake/deps: Update OSL to 1.11.10.0](D10212) I noticed a single test failing... once... by repeating the test over and over I got it to misbehave once every 5-45 minutes , so... that's not gonna be super fun to track down.\n\nI attached 3 stack traces which all point to the same location, a null check there just mask the issue, personally I'd take a crash over a random bad frame being output. \n\n\n`ctest -C Release -VV -R cycles_image_colorspace_cpu --repeat-until-fail 9999 -O Fail.log`\n\n\n[image_non_color.crash.txt](image_non_color.crash.txt)\n\n[image_log_osl.crash.txt](image_log_osl.crash.txt)\n\n[image_alpha_blend.crash.txt](image_alpha_blend.crash.txt)\n\nI mentioned this on chat earlier today, but tracking ticket is probably nicer cc: @brecht ", "\"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", "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)", "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)", "Quick Smoke crash guide February 3, 2023\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.5.0 Alpha\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\n[image.png](image.png)\n[image.png](image.png)\n[Blender-2023-02-03-113746.ips](Blender-2023-02-03-113746.ips)\nTest File: [3.5.zip](3.5.zip)\n```\nCall Stack: Main thread\n__psynch_cvwait\n_pthread_cond_wait\ntake_gil\nPyEval_RestoreThread\nPyGILState_Ensure\npy_timer_execute\nBLI_timer_execute\nwm_event_do_notifiers\nWM_main\nmain\nstart```", "Access violation when running multiple quick liquid bakes (Python API)\nOperating system: Windows 10\n\nBroken: 3.3 alpha, 3.3, 3.4 alpha, 3.4\nWorked: Not any recent releases\n\nSeems related to T98427 , but the fix for that issue did not fix this.\nAccess violation when running multiple quick liquid bakes\n\n```lines=18\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF9DE2B9224\nException Module : python310.dll\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x0000000000000008\n\n\nStack trace:\npython310.dll :0x00007FF9DE2B9220 PyDict_GetItem_KnownHash\npython310.dll :0x00007FF9DE2CF200 PyFrame_GetBack\npython310.dll :0x00007FF9DE430410 PyRun_FileExFlags\npython310.dll :0x00007FF9DE430410 PyRun_FileExFlags\npython310.dll :0x00007FF9DE430270 PyRun_StringFlags\nblender.exe :0x00007FF64D0F4E60 MANTA::runPythonString\nblender.exe :0x00007FF64D0DAF70 MANTA::~MANTA\nblender.exe :0x00007FF64D0DB340 MANTA::`vector deleting destructor'\nblender.exe :0x00007FF6484EB4D0 BKE_fluid_modifier_freeDomain\nblender.exe :0x00007FF6484EB4A0 BKE_fluid_modifier_free\nblender.exe :0x00007FF648274A00 BKE_modifier_free_ex\nblender.exe :0x00007FF648488760 BKE_object_free_modifiers\nblender.exe :0x00007FF6484834A0 object_free_data\nblender.exe :0x00007FF6487EB890 blender::deg::deg_free_copy_on_write_datablock\nblender.exe :0x00007FF6487ECA40 blender::deg::IDNode::destroy\nblender.exe :0x00007FF6487E1F70 blender::deg::Depsgraph::clear_id_nodes\nblender.exe :0x00007FF6487E21E0 DEG_graph_free\nblender.exe :0x00007FF64D64FA80 BLI_ghash_free\nblender.exe :0x00007FF648450510 scene_free_data\nblender.exe :0x00007FF64846F120 BKE_id_free_ex\nblender.exe :0x00007FF64826E980 BKE_main_free\nblender.exe :0x00007FF6482628F0 BKE_blender_free\nblender.exe :0x00007FF6486F1AB0 WM_exit_ex\nblender.exe :0x00007FF6486F1A60 WM_exit\nblender.exe :0x00007FF6477F1260 main\nblender.exe :0x00007FF64D8788C0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThreads:\nThread : 00004eb4\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000051dc\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004114\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004ab8\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000033dc\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005b3c\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000044b0\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000033f0\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000031f8\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004aa4\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000049b8\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\nblender.exe :0x00007FF64E410730 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF64E40FF40 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF6479B3A10 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005340\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00002654\nntdll.dll :0x00007FFA49C90780 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA49C42680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004c64\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000024a4\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005664\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 000048c4\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00005b4c\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 00004eb0\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nThread : 0000446c\nntdll.dll :0x00007FFA49C8CDB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA47831A40 WaitForSingleObjectEx\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA373BD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA473D1B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA48397020 BaseThreadInitThunk\nntdll.dll :0x00007FFA49C42630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF647680000 3.3.0.0 blender.exe C:\\Users\\ecl25031\\blender-3.3.0-alpha+master.4c3b984b3daa-windows.amd64-release\\blender.pdb \n0x00007FFA49BF0000 10.0.19041.1741 ntdll.dll \n0x00007FFA48380000 10.0.19041.1741 KERNEL32.DLL \n0x00007FFA47810000 10.0.19041.1741 KERNELBASE.dll \n0x00007FFA48E00000 10.0.19041.546 WS2_32.dll \n0x00007FFA499D0000 10.0.19041.1706 RPCRT4.dll \n0x00007FFA47C50000 10.0.19041.1503 USER32.dll \n0x00007FFA47B10000 10.0.19041.1766 win32u.dll \n0x00007FFA373B0000 tbb.dll \n0x00007FFA48790000 10.0.19041.1620 GDI32.dll \n0x00007FFA2BF10000 tbbmalloc.dll \n0x00007FFA47B40000 10.0.19041.1706 gdi32full.dll \n0x00007FFA47310000 10.0.19041.789 msvcp_win.dll \n0x00007FFA473B0000 10.0.19041.789 ucrtbase.dll \n0x00007FFA48EA0000 10.0.19041.1682 ADVAPI32.dll \n0x00007FFA48440000 7.0.19041.546 msvcrt.dll \n0x00007FFA486F0000 10.0.19041.1586 sechost.dll \n0x00007FFA49040000 10.0.19041.1741 SHELL32.dll \n0x00007FFA48F50000 10.0.19041.1706 SHLWAPI.dll \n0x00007FFA2FB80000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFA477C0000 10.0.19041.1620 CFGMGR32.dll \n0x00007FFA15BF0000 14.29.30139.0 MSVCP140.dll \n0x00007FFA43A40000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFA47AE0000 10.0.19041.1023 bcrypt.dll \n0x00007FFA485C0000 10.0.19041.1202 ole32.dll \n0x00007FFA35C50000 10.0.19041.867 dbghelp.dll \n0x00007FFA48A40000 10.0.19041.1741 combase.dll \n0x00007FFA49870000 10.0.19041.546 PSAPI.DLL \n0x00007FFA49B00000 10.0.19041.1741 shcore.dll \n0x00007FFA484E0000 10.0.19041.546 IMM32.dll \n0x00007FFA03B30000 10.0.19041.1741 OPENGL32.dll \n0x00007FF9D3660000 9.0.0.0 openvdb.dll \n0x00007FF9D19D0000 59.18.100.0 avcodec-59.dll \n0x00007FF9F78D0000 59.16.100.0 avformat-59.dll \n0x00007FFA2D720000 59.4.100.0 avdevice-59.dll \n0x00007FF9F8750000 57.17.100.0 avutil-57.dll \n0x00007FFA48970000 10.0.19041.985 OLEAUT32.dll \n0x00007FF9FBCC0000 1.21.1.0 OpenAL32.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFA0FA30000 6.4.100.0 swscale-6.dll \n0x00007FF9F7770000 2.0.20.0 SDL2.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFA41050000 libgmpxx.dll \n0x00007FFA47F10000 10.0.19041.1741 SETUPAPI.dll \n0x00007FFA40FF0000 tbbmalloc_proxy.dll \n0x00007FF9DE1A0000 3.10.2150.1013 python310.dll \n0x00007FFA30660000 6.10.19041.1110 COMCTL32.dll \n0x00007FFA2AB80000 10.0.19041.1 AVIFIL32.dll \n0x00007FFA415D0000 10.0.19041.546 VERSION.dll \n0x00007FFA44B10000 10.0.19041.746 dwmapi.dll \n0x00007FFA2A530000 10.0.19041.1741 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFA29450000 4.3.100.0 swresample-4.dll \n0x00007FFA3D230000 10.0.19041.546 Secur32.dll \n0x00007FFA2EAF0000 10.0.19041.1 AVICAP32.dll \n0x00007FFA39CA0000 10.0.19041.546 WINMM.dll \n0x00007FFA28820000 10.0.19041.1 MSACM32.dll \n0x00007FFA291F0000 10.0.19041.1 MSVFW32.dll \n0x00007FFA37020000 10.0.19041.1 winmmbase.dll \n0x00007FFA47200000 10.0.19041.1586 SSPICLI.DLL \n0x00007FFA45AD0000 10.0.19041.546 kernel.appcore.dll \n0x00007FFA452E0000 10.0.19041.1741 windows.storage.dll \n0x00007FFA46D70000 10.0.19041.1682 Wldp.dll \n0x00007FFA47250000 10.0.19041.844 profapi.dll \n0x00007FFA47610000 10.0.19041.1415 bcryptPrimitives.dll \n0x00007FFA48510000 2001.12.10941.16384 clbcatq.dll \n0x00007FFA3FB50000 10.0.19041.1503 MMDevApi.dll \n0x00007FFA470C0000 10.0.19041.1620 DEVOBJ.dll \n0x00007FFA3FC00000 10.0.19041.1741 AUDIOSES.DLL \n0x00007FFA468E0000 10.0.19041.546 powrprof.dll \n0x00007FFA46750000 UMPDC.dll \n0x00007FFA44880000 10.0.19041.1620 uxtheme.dll \n0x00007FFA2D140000 10.0.19041.1566 MPR.dll \n0x00007FFA415E0000 10.0.19041.546 drprov.dll \n0x00007FFA45F70000 10.0.19041.546 WINSTA.dll \n0x00007FFA2ED10000 10.0.19041.1566 ntlanman.dll \n0x00007FFA2EB50000 10.0.19041.546 davclnt.dll \n0x00007FFA22F70000 10.0.19041.546 DAVHLPR.dll \n0x00007FFA46500000 10.0.19041.1645 wkscli.dll \n0x00007FFA27030000 10.0.19041.546 cscapi.dll \n0x00007FFA467B0000 10.0.19041.546 netutils.dll \n0x00007FFA46CC0000 10.0.19041.546 CRYPTSP.dll \n0x00007FFA462D0000 10.0.19041.1052 rsaenh.dll \n0x00007FFA46CE0000 10.0.19041.546 CRYPTBASE.dll \n0x000002627AAF0000 3.10.2150.1013 python3.DLL \n0x00007FFA2CA10000 3.10.2150.1013 _bz2.pyd \n0x00007FFA28ED0000 3.10.2150.1013 _lzma.pyd \n0x00007FFA2C980000 3.10.2150.1013 _socket.pyd \n0x00007FFA46770000 10.0.19041.546 IPHLPAPI.DLL \n0x00007FFA40E90000 3.10.2150.1013 select.pyd \n\n# Python backtrace\n\n```\n\nPut this ins a file called test.py\n```\n\nimport bpy\n\nCUBE = bpy.data.objects[\"Cube\"]\nCUBE.select_set(True)\nbpy.ops.object.quick_liquid()\nbpy.ops.fluid.bake_all()\n\nbpy.ops.object.select_all(action='DESELECT') \nmesh = bpy.data.meshes.new('Basic_Cube')\nCUBE2 = bpy.data.objects.new(\"Cube2\", mesh)\nCUBE2 = bpy.data.objects[\"Cube2\"]\nbpy.context.scene.collection.objects.link(CUBE2)\nCUBE2.select_set(True) \nbpy.ops.object.quick_liquid()\nbpy.ops.fluid.bake_all()\n```\n\nthen, in terminal, run:\n\n```\nblender -b --python test.py \n```", "Cycles regression testing for GPU devices\n**Background**\n\nThe Cycles automated regression tests so far only ran on the CPU.\n\nWith some environment flags it was possible to execute a script that runs them on other devices, but this is cumbersome. The goal of this task is to add a CMake option to enable running the regression tests on GPU devices in addition to CPU devices.\n\nThe reference images are currently only valid for CPU rendering. Keeping differeing reference images updated will have to wait until we have CI infrastructure for testing GPU rendering. For now we can do a few things:\n* Do nothing and manually check when tests fail\n* Increase difference thresholds for tests that only differ a little\n* Disable failing tests for GPU testing\n\n**Status**\n\n- [x] CYCLES_TEST_DEVICES option to specify devices to test\n- [x] Blacklist failing CUDA tests\n- [x] Blacklist failing OPTIX tests\n- [ ] Verify HIP tests are working\n- [ ] Enable GPU testing on the buildbot", "Broken edge lines with boolean and freestyle\nOperating system: Linux-5.0.7-200.fc29.x86_64-x86_64-with-fedora-29-Twenty_Nine 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\n\nBroken: version: 2.80 (sub 58)\nWorked: (optional)\n\n\nI'm seeing two different issues:\n(1) There is a broken line in the edge (see attached render). Rotating the object for a different angle, changing the boolean by moving one of the cylinders, etc. still causes broken lines, sometimes on multiple edges. Also, using the simple surface (without the toon shading setup of Shader-to-RGB and gradient) still causes the broken line. \n(2) The second possible issue is that while Eeevee renders correctly otherwise, Cycles also has the broken line and in addition seems to be rendering incorrectly for the toon shade effect - i.e., all solid color vs. multiple colors expected, see attached render. \n\nCreate a cube and two cylinders. Add two boolean modifiers to the cube to subtract the two cylinders. Add a toon shading setup (shader to RGB and gradient) and free style to render lines for edges. Render with Eevee and Cycles (see above). File attached. [sekhar-04-20.blend](sekhar-04-20.blend)\n\n", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "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)", "Rigify: Assert on 2 of the Action space types\nOperating system: Linux-6.4.6-gentoo-x86_64-Intel-R-_Core-TM-_i9-9900K_CPU_@_3.60GHz-with-glibc2.37 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.86.05\n\nBroken: version: 4.0.0 Alpha\n\n\nI believe only the 'World' and 'Local' space types are meant to be supported. The other ones will result in errors.\nThe asserts seems to support a 3rd space type, which is \"TRANSFORM\", but that's wrong too; The Action Constraint seems to support only World, Local, and Custom Space.\n\nAnd in the context of Rigify, I don't think supporting Custom Space is necessary, so just World and Local should be enough.\n\nOriginally reported as a CloudRig issue [here](89).\n\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "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)", "Point Cloud - Missing Particles when Rendering with Cuda on Linux\nOperating system: Linux-5.13.0-35-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.1.0\n\nWhen rendering large amounts of particles with CUDA on Linux, there appear to be some random patches of particles missing. This does not occur when using the OptiX rendering backend or CPU rendering backend. This problem **does not** occur on Windows for any rendering backend, i.e. the same render has been confirmed to work on Windows with the CUDA backend.\n\n1. Open the attached .blend file.\n2. Render with Cycles and CUDA backend on linux. *Note: It might be necessary to render the same scene multiple times if the error does not occur on the first render, or to switch the render device back and forth.*\n3. See the attached image for an example screenshot of the problem\n\n(alternative)\n1. \n - create a plane object and create 1000 edge loops in x and y direction so that the object has roughly 1 million vertices.\n - add \"Mesh to Points\" geometry node with radius 0.001\n2. Render with Cycles and CUDA backend on linux. *Note: It might be necessary to render the same scene multiple times if the error does not occur on the first render, or to switch the render device back and forth.*\n3. See the attached image for an example screenshot of the problem\n\n.blend File:\n[particles_problem.blend](particles_problem.blend)\n\nImage of the Problem:\n" ]

[ "OpenCL Cycles Render Fail\nOperating system: Win 10\nGraphics card: AMD R7 265\n\nBroken:2.80 Beta\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\nCompiling OpenCL program split\nOpenCL build failed with error CL_BUILD_PROGRAM_FAILURE, errors in console.\nOpenCL program split build output: \"source\\kernel/kernel_volume.h\", line 394: error: expression must have\n```\n pointer-to-struct-or-union type\n if(rand < pdf->x) {\n ^\n```\n\n\"source\\kernel/kernel_volume.h\", line 397: error: expression must have\n```\n pointer-to-struct-or-union type\n else if(rand < pdf->x + pdf->y) {\n ^\n```\n\n\"source\\kernel/kernel_volume.h\", line 397: error: expression must have\n```\n pointer-to-struct-or-union type\n else if(rand < pdf->x + pdf->y) {\n ^\n```\n\n3 errors detected in the compilation of \"C:\\Users\\Karthik\\AppData\\Local\\Temp\\OCL9568T4.cl\".\nFrontend phase failed compilation.\n\nSplit kernel error: failed to load kernel_path_init\nError: Split kernel error: failed to load kernel_path_init\nCompiling OpenCL program split\nOpenCL build failed with error CL_BUILD_PROGRAM_FAILURE, errors in console.\nOpenCL program split build output: \"source\\kernel/kernel_volume.h\", line 394: error: expression must have\n```\n pointer-to-struct-or-union type\n if(rand < pdf->x) {\n ^\n```\n\n\"source\\kernel/kernel_volume.h\", line 397: error: expression must have\n```\n pointer-to-struct-or-union type\n else if(rand < pdf->x + pdf->y) {\n ^\n```\n\n\"source\\kernel/kernel_volume.h\", line 397: error: expression must have\n```\n pointer-to-struct-or-union type\n else if(rand < pdf->x + pdf->y) {\n ^\n```\n\n3 errors detected in the compilation of \"C:\\Users\\Karthik\\AppData\\Local\\Temp\\OCL9568T4.cl\".\nFrontend phase failed compilation.\n\nSplit kernel error: failed to load kernel_path_init\nError: Split kernel error: failed to load kernel_path_init\n\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Creating meshes after removing previous meshes result in an BKE_object_data_is_in_editmode error\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2\n\nBroken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca3055776, type: release\nWorked: version: 2.93.7, branch: master, commit date: 2021-12-14 16:35, hash: a5b7f9dc9011, type: release\n\nCreating a big amount of blenddata meshes and linking them to a collection works the first time without any exceptions.\nThe second time that you execute the script below, this will be output to the terminal.\n```\nCode marked as unreachable has been executed. Please report this as a bug.\nError found at C:\\Users\\blender\\git\\blender-v300\\blender.git\\source\\blender\\blenkernel\\intern\\object.cc:1970 in BKE_object_data_is_in_editmode.\n```\nThis doesn't happen if you don't delete all the meshes in bpy.data.meshes, which I would like to do since bpy.data.meshes is being bloated with old meshes. \nThe addon I'm writing needs bpy.data.meshes to be empty at the start of execution for performance reasons.\n\n- Run this python script in a new blender project multiple times (for two times is probably enough)\nEventually you will get the BKE_object_data_is_in_editmode error.\n\n```\nimport bpy\n\nfor i in bpy.data.meshes:\n bpy.data.meshes.remove(i)\n\nfor _ in range(3000):\n mesh = bpy.data.meshes.new('mesh')\n basic_mesh = bpy.data.objects.new(\"mesh\", mesh)\n bpy.context.collection.objects.link(basic_mesh)\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", "Video Editing (outline on the border)\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\nSome images with an alpha channel have grey outline when scaled up and different bicubic or bilinear interpolation is used.\n\nIssue is visible immediately after opening .blend file\n[#86861.zip](T86861.zip)", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "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", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\n\n", "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)", "GPU Subdivision: Wrong objects statistics information\nWindows 10\ni7-4790\n16 GB RAM\nRTX 2070\n\nBlender v3.4.1 (Steam)\n\nWrong objects statistics information in object mode when GPU Subdivision is enabled\n\n- Open `Rat.blend` file\n- Enable GPU subdivision\n- Rotate/move the bone\n- Switch to object mode (notice the viewport statistics)\n\n\n\n", "Sporadic boolean issues\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.2.0\nWorked: 3.0\n\nMeshes using the boolean modifier sporadically break in Blender 3.2.0, while they still worked in 3.0.\nThis would result in meshes that lack faces or even crash Blender\n\n\nUnfortunately I wasn't able to isolate the cause of the issue, as it seems to occur sporadically and randomly. What I have noticed is that sometimes meshes that were fine suddenly break once you enter exit edit mode.\n\n", "Blender 2.92 crashing when editing fractured mesh\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.80.02\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.91.0\n- 2.90.1\n- 2.83.10\nWorked: ?\n\nI have used cell fracture to fracture a UV sphere. I did separate the parts using P. I tried to edit a part and it is where the crash happens.\n\n\n```lines\n/home/yves/Downloads/blender291/blender(BLI_system_backtrace+0x20) [0x84ba490]\n/home/yves/Downloads/blender291/blender() [0xe5293a]\n/lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7fa720a5e210]\n/home/yves/Downloads/blender291/blender(DRW_mesh_batch_cache_create_requested+0x5a9) [0x1364e89]\n/home/yves/Downloads/blender291/blender() [0x1311158]\n/home/yves/Downloads/blender291/blender(DRW_draw_render_loop_ex+0x35d) [0x131232d]\n/home/yves/Downloads/blender291/blender(view3d_main_region_draw+0x8f) [0x1afb15f]\n/home/yves/Downloads/blender291/blender(ED_region_do_draw+0x7e1) [0x16b43f1]\n/home/yves/Downloads/blender291/blender(wm_draw_update+0x52e) [0x11c181e]\n/home/yves/Downloads/blender291/blender(WM_main+0x30) [0x11bf740]\n/home/yves/Downloads/blender291/blender(main+0x30d) [0xd8d12d]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7fa720a3f0b3]\n/home/yves/Downloads/blender291/blender() [0xe4f0b3]\n```\n\n{F9530087}\n\n{F9530088}\n\n- Open the attached file and select `Sphere_cell.055`.\n- Try to switch to edit mode.\n\n\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)", "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.", "Subsurface modifier new \"OpenSubdiv\" method Issue\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 53), \nbranch: blender2.7, \ncommit date: 2019-03-31 21:52, \nhash: `b936d7b16c`\nWorked: (optional)\n\n\nIssues with the new \"OpenSubdiv\" modifier method.\n\n- Add a simple plane mesh in Blender 2.8\n- UV unwrap it\n- Import a texture and apply it to your plane\n- Add a Subsurf modifier \n\nHere is the issue in details.\nI was doing some texture work on High-poly models, and when I applied the textures to my model, they were deformed in places.\n\n\n\n\nI later learned that the method used in Subsurface modifiers was changed :\n\n\nWould there be any way to bring back the old method ?\nbecause this is going to break a LOT of my models.\n\n", "Dae parsing issue\nOperating system:Windows 10\nGraphics card: NVidia gforce GTX660\n\n 2.79\n\n\nIt is a common error, when trying to upload an object to Second-life or Opensim, to be unable to upload a model,created in Blender, due to a \"DAE parsing issue\"\nThis object is one that is effected.\n\n[lowpol.blend](lowpol.blend)\nExport as .DAE file and upload to Opensim or Second-life", "\"Input Pending\" for Loop Cut and Slide when called from menu.\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 1660Ti\n\nBroken: 3.3.2\nWorked: 2.93\n\n**Caused by:** da2ba402689d7ed752b0b37ad49dce1a5851cc77\n\n**Reproducing the error:**\n\n- Ctrl+R on default cube edit mode, regardless of selection mode, loop cut slide works as usual.\n- Use search menu or header->edge menu and select loop cut slide, header bar only shows \"Input Pending\", if pressed left mouse, then operator runs correctly. If pressed right mouse, then operator is cancelled.\n\n\n\n" ]

[ "[BUG] Mesh bug when move in edit mode.\nOperating system: Windows 10 (64 bits)\nGraphics card: AMD Radeon HD 6570 2gb(last driver support)\nOthers: I5 2320, 8gb ram\n\nBroken: 2.81-a\n\nAn image of any mesh is separating the hit box when moving in edit mode.\n\nCreate a mesh (cube / plane) and move in edit mode\n\n\n\n[a4a20c3d-9d99-4165-ab4e-4b887ee5aa86.webm](a4a20c3d-9d99-4165-ab4e-4b887ee5aa86.webm)\n\n**.blend**\n[blender-erro.blend](blender-erro.blend)" ]

[ "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", "\"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", "NaN pixels in Normal Pass\nOperating system: Linux-3.10.0-1127.10.1.el7.x86_64-x86_64-with-centos-7.8.2003-Core 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.83.0\nWorked: (Unknown)\n\nI produced a template based rendering solution and am experiencing occasion nan pixels in the normal pass output. Nan pixels are occurring in both CPU and GPU renders on a number of different hardware configurations.\n\nI've stripped down one of the files that exhibit the issue, see nan pixel at x162, y78 of normal pass.\nChanging visibility of the lights collection, specifically the 'LightArea', removes the pixel. Changing render resolution, sample seed, or adaptive sampling, can remove bad pixels.\nDisconnecting the normal map node on the geometry object's material removes the pixel. Providing input to that node, both textures and noise, has no effect on the pixel.\nChanging the transform on the rendered geometry removes the nan, regardless of whether the pixels occur on transparent background.\n\n[nan_pixel_isolated.blend](nan_pixel_isolated.blend)", "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.", "VSE: 'Clear fade' function clears every opacity/volume keyframe and resets non-default baseline value\nOperating system: Linux-5.4.0-84-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\nThe 'Clear fade' function used on either a visual or audio strip does not only clear the start/end fade(s), but any other set opacity/volume keyframes as well. It will also reset the baseline value to 1, even if the fades in the strip clearly operate on a baseline set to other than 1.\n\n[clear-fade-function-clears-internal-value-changes-and-does-not-preserve-non-default-baseline-value.blend](clear-fade-function-clears-internal-value-changes-and-does-not-preserve-non-default-baseline-value.blend)\n(NOTE: In blend file, choose 'Clear fade' from the context menu for the top strip)\n\n- Add sound or visual strip\n- Change opacity/volume to 0.5\n- Choose 'Fade in and out' from the context menu, and note that the changed 0.5 baseline has been respected\n- Add a manual keyframe change/fluctuation somewhere in the middle of the strip\n- Choose 'Clear fade' from the context menu\n- Notice that all keyframes including the middle ones are now gone, as well as the 0.5 baseline value (replaced by default 1.0)\n\nIt is not expected that any fades apart from in and out will be cleared. In particular, it is quite common to have volume keyframes toyed with throughout the strip, so I do think targeting just the ins and outs is useful, certainly much more so than destroying all the keyframes (which one can achieve by choosing \"Clear keyframes\" directly on the property).\n\nAlso all the options to add fades are for adding fade-ins and fade-outs, so it's expected that the \"Clear fade\" will remove fade ins/outs as well. Either way, the description should be made clearer to reflect what will really happen.\n\nA user-set, non-default baseline should also be preserved, if it clearly exists.", "Compositor refresh on every 3D view edit and blocks UI\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.80 (sub 74)\n\nAdjust operator panel for selection operations is greyed out after every operation. When you move cursor out of the input field it's active again. It happens only when compositor is opened and \"Use Nodes\" is selected. See video:\n[Desktop 2019.06.19 - 12.22.31.02.avi](Desktop_2019.06.19_-_12.22.31.02.avi)\n\n - Open attached file: [select_compositor_bug.blend](select_compositor_bug.blend)\n - Use Select > Checker deselect\n # Go to adjust operator panel and change one value. Menu will be greyed out until you move cursor out of input field.\nIt's the same with other selection operations like \"Select Similar\" or \"Select Sharp Edges\".", "depsgraph.view_layer.name driver expression doesn't work correctly\nOperating system: Windows 11\nGraphics card: Geforce RTX 3090\n\nBroken: 3.3.5 LTS\nBroken: 3.5\n\nI use a driver expression to control modifiers visibility or shader values depending on a view layer name. If the needed view layer is active, then values change. All works well when switching viewlayers manually inside the viewport of my scene. But as soon as I render the scene, the expression is ignored and nothing happen.\n\n* Open attached file\n* Change view layer few times\n\nDriver will change only once. This also doesn't work when rendering.\n\n", "Edit mode. Wire become non-selectable dependent on resolution (regression)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n", "Dynamic paint waves: Viewport render and main Render looks very different.\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.82 (sub 7)\nWorked: Never\n\nIn render dynamic paint do notproduce waves as it do in viewport.\n\nViewport:\n[viewport.mp4](viewport.mp4)\n\nRender\n[render.mp4](render.mp4)\n\nFile:\n[DinamicTestPaint.blend](DinamicTestPaint.blend)\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", "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.", "'Reset to Default Value' sets any property on a node to 0\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nIn shader editor gamma default is 1 when I do the hover over setting and press backspace to reset the default it goes to 0.0\nSame with hue/saturation/value.. and probably more.\nThe one with hue is pretty annoying as it has specific default settings .\nSame deal with groups - I set the defaults, it doesn't default .. goes to 0\n\n- in any node editor hover over any setting and press backspace to reset to default value.\nIt defaults to 0 instead of 1 or whatever it's default was in shader editor..\n\n", "Default Value for Viewport Display Color's Alpha Wrong.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.92.0 Alpha\nAlso tested on 2.83.8 and same problem.\nWorked: It do not think this has ever worked\n\nWhen reverting to the Default Value for Viewport Display Color the alpha gets down to 0.8 making the object semi transparent.\n\nOpen up a new scene.\nSelect the cube.\nGo to the materials tab.\nScroll down to \"Viewport Display\"\nRight Click on \"Color\"\n\"Reset to Default Value\"\nResult: RGB values go back to the default, but Alpha goes to 0.8\n\n\nThank you so much !", "VSE: adding scene stripe resets animation of colour stripe with mask\nOperating system: Linux-5.13.0-41-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.41.0, 5.13.0-41-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.3.8 (git-813ee839be)\n\nBroken: version: 3.1.2\nWorked: none tested\n\nI have added a colour channel and applied a mask to it. I have created and animated a clock as UI element.\nWhen I add the clock as scene stripe to the scene with the masked colour stripe, the mask of the colour strip is not applied correctly.\n\nI have no idea what really causes the issue or how I could reproduce it. See the attached blend file and video files.\n\n**Notes**\n- When the clock strip is muted in the VSE overview, the problem does no longer exist. So I guess it's some weird interaction between the mask and the scene strip\n- The bug can be solved when you create a new scene and add the colour strip as scene strip and on top of that the clock strip. It works, but performance is incredibly bad.\n\n**Files**\n - The actual output: [bug 01.mp4](bug_01.mp4)\n - How it should look like: [bug 02.mp4](bug_02.mp4)\n - blend file: [bug.blend](bug.blend)", "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\"" ]

[ "Cycles Regression: Changing \"Start Samples\" in denoiser resets viewport render\nOperating system: Linux-5.14.0-3-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.29.05\n\nBroken version: 3.0.0 Alpha\nWorked: Prior to Cycles-X merge\n\nChanging the `Start Samples` value for the viewport denoiser resets the viewport rendering. This did not happen prior to the Cycles-X merge.\n\n1. Create a scene that has noticeable amounts of noise in Cycles.\n2. Enable viewport denoising.\n3. Enter rendered viewport mode.\n4. Change the `Start Samples` value of the viewport denoiser. You will notice that viewport rendering will reset back to 1 sample. This did not happen prior to the Cycles-X merge." ]

[ "Geometry Nodes: 3D Viewport Overlay Statistics don't respect Viewer Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.4.0 Alpha\n\n\nThe geometry output by the preview node is not taken into account by the overlay scene statistics:\n[2022-09-30 11-35-43.mp4](2022-09-30_11-35-43.mp4)\n", "Curve to Mesh node causes other objects to edge split when not shaded smooth\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nWhen using a Curve to Mesh node, it causes other objects joined to it to be read with each face as a separate mesh island by Cycles (using the Random per Island socket of the Geometry node in shaders). This only happens while using Flat shading AND the Curve to Mesh is plugging into the first position of the Join Geometry node. In any other order it will not happen.\nAlso happens with more mesh objects as long as the Curve to Mesh object is the first on in the Join node.\n\nThe edges aren't actually split, it just seems to be Cycles that thinks they're individual mesh islands.\n\nAdd a grid node and join it to a curve going through a Curve to Mesh node.\nEnsure the Curve to Mesh is the first connection into the Join Geo node.\nAssign a material to the grid and in the shader, view the Random Per Island output of the Geometry node.\n\n[2021-11-06 18-08-29.mp4](2021-11-06_18-08-29.mp4)\n\n[Mesh Island Bug.blend](Mesh_Island_Bug.blend)", "Warning messages should propagate to nodegroups\n[nodegrou-warning-outside.blend](nodegrou-warning-outside.blend)\n\nThe warning happens in the node inside the nodegroup. However it does not show in the nodegroup itself:\n\n{[F10231869](image.png), size=full}", "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", "Node group inputs and outputs have incorrect \"name\" property\nOperating system: Linux-5.8.0-44-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.42.0, 5.8.0-44-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.2.0-devel\n\nBroken: version: 2.93.7 3.01 3.1 3.2\n\nWhen adding new Input or Output Sockets in the Group Node Properties Tab, the selected Input or Output Socket name is duplicated.\nTwo issues:\n- - [x] the socket name is not unique (this can get problematic since entries in node.outputs are name based)\n- - [x] design question: should the new name default to either \"Input\" or \"Output\"?\nShould Default to Input or Output. ( Only Defaults to Input or Output if there are no Sockets except the Default ones )\n\nIn the Node Editor add Input or Output Sockets to a nodegroup in the sidebar, change the name and try adding more Inputs or Outputs, the System will assign the name of the selected sockets. \n\nSeems like there are muliple functions handling new sockets\n- `make_socket_interface` [in affect when adding a new socket through the UI] gives a unique identifier (but copies the name exactly -- no uniqueness)\n- `nodeAddSocket` or `make_socket` take care of making the name unique as well\n\n{[F12842289](image.png) size=full}\n\n{[F12842292](image.png) size=full}\n\nref #91826 (just to show that unique names are important).\n", "Applying bevel modifer changes vertex group\nOperating system: Linux-5.4.0-120-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\nWorked: unknown\n\nApplying bevel modifier changes vertex group\n\n- Create a cube\n- Subdivide\n- Assign a vertex next to an edge that would be affected by an bevel to a vertex group\n- Add a bevel modifier\n- Apply bevel modifier\n- -> the vertex group is changed\n\nThe vertex group is only changed by applying the bevel modifier.\nAn active bevel modifier dont modifiy the vertex group which can be checked with an modifier that uses a vertex group placed after the bevel modifier.\n\nExample:\nUsed vertex group before apply bevel modifier\n\n\nVertices in group\n\n\nUsed vertex group after apply bevel modifier\n\n\nVertices in group after applying bevel modifier\n\n\nSimple example\n[bevel_modifier_apply_bug.blend](bevel_modifier_apply_bug.blend)\n\nComplex example\n[steam_traveller17.blend](steam_traveller17.blend)", "Redo Panel changes the state of the last active Vertex Group\nOperating system: macOS-12.4-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.4.0 Alpha\n\nActivating a certain Vertex Group before calling the Smooth Vertex Weights (or another weight paint operator) won't necessarly respect the choices even when the Subset Active Group is enabled. As soon as you interact with the pop-up operator's parameters seems Blender will pick up another Vertex Group instead of the current activated one.\n\nVideo:\n[WightPaint-SmoothOperator-Bug.mp4](WightPaint-SmoothOperator-Bug.mp4)\n\nSample file:\n[Smooth-Operator_Bug.blend](Smooth-Operator_Bug.blend)\n\n\n1. Paint some vertex groups on your mesh.\n2. Click on one of your groups to set it active.\n3. Call the Operator from Weight Paint > Weights > Smooth\n4. Set operator's Submenu to Active Group\n\n*Note that is might switches to another Vertex Group as soon as you interact with the pop-up's operator parameters.\n_ \nWorkaround: after setting the desired Vertex Group active, you must perform another action like clicking with you brush on an empty area of the 3D view. This way it will respect the active Vertex Group selected.\nIt seems some kind of residue living in the memory of undo buffer. I don't know... could you please investigate?\n\nThanks you!\n\n", "Renaming Vertex Group Breaks Modifier's Vertex Group Reference\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: Never (2.79+)\n\nChanging name of the vertex group breaks modifier's vertex group reference.\nSame issue has been reported 6 years ago: [#41876](T41876). If it's still a \"known limitation\" or \"to do\", it might be a good idea to tag it with new/proper labels.\n\n1- Launch default Blender.\n2- Create a vertex group to the cube and assign a face.\n3- Create a modifier with vertex group option (Mask modifier for example) and select the vertex group that we just created.\n4- Rename the vertex group and notice that breaks the modifier referencing to that vertex group.\n\n[#74726.blend](T74726.blend)\n", "Geometry Nodes: Mesh Boolean-Union node anamoly when boolean does not alter input mesh\nBroken: Current main.\nWorked: Never.\n\nI was trying to see if the simulation node group would get rid of internal geometry by incrementally using the **Mesh Boolean-Union** node in the **Simulation node group** but it **seems to delete some outer geometry instead.** \n\n## Without Simulation Nodes:\n| Operating as expected without Mesh Boolean Union node enabled (**creates internal geometry see red arrow**) | Operating as expected with Mesh Boolean Union node enabled (**no internal geometry**) |\n| -- | -- |\n|  |  |\n\n## With Simulation Nodes:\n\n| Description | Show |\n| -- | -- |\n| Operating as expected without Mesh Boolean Union node enabled (creates internal geometry see red arrow) |  |\n| Not Operating as expected with Mesh Boolean Union node enabled (no internal geometry but missing outer geometry) |  |\n| It should look something like this (no internal geometry but it should have \"external\" geometry also see red arrow |  |\n\nThe reason I'm trying to use the boolean mesh-union node within the simulation node group is because on some large meshes the boolean mesh-union node will fail or crash blender. \n105652#issuecomment-931240\n\nMy logic is if you have to finish an entire pie in one sitting (think of a pie eating contest) it's easier to cut them up into little pieces and eat them one at a time. **So I'm incrementally running the boolean mesh-union node on smaller pieces in the simulation node group to get rid of internal geometry therefore it's less likely to crash / fail like it does trying to do this all at once on larger meshes.**\n\nSee attached blend file: [cube repeat.blend](https://projects.blender.orgattachment)", "After swapping the basis shape key to another one, the former basis key still affects the new one\n2.91.0\n\nWhat I try to do: I would like to make a later created shape key the basis one. \nI can do it with moving it to the top, and setting the former basis key's \"Relative To\" setting to this new basis one.\nIt works as expected until I'd like to make further changes in the old basis key (now just a regular shape key)\nIt affects the current basis, where - by definition - there's no \"relative to\" setting, so it shouldn't be affected by anything.\n\nI noticed that it does work as expected if I'm using the \"shape key in edit mode\" option - BUT it only behaves well until I come back to object mode. Then the new basis key instantaneously gets all the modifications I just made on the old basis.\n\nThe steps are below on an image with descriptions, but I attached the blend file too. Just change the shape key called \"starting basis\" and check what happens with the real basis one.\n\n\n[shapekey_error.blend](shapekey_error.blend)\n\nNote: there was one time when I created a shape key pair where this whole thing worked as intended. But out of (literally) 6 tries, only one worked and I couldn't pinpoint what I did differently in that case.", "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", "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", "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", "Some areas do not use modified (by geometry nodes) curve\nOperating system: Windows 10 - Probably irrelevant.\n\nBroken: 3.0.0 (not checked earlier versions).\nWorked: (none)\n\nThe Curve modifier on mesh objects does NOT use the modified version of a curve\n\nSee attached blend file for easy example: [bug - curve with modifier.blend](bug_-_curve_with_modifier.blend)\nExample screenshot of that blender: \nThe thin line is the curve, which has geometry nodes modifying it.\nThe thick (square) line is the mesh, which targets the curve but doesn't use the modified version.\n\n - Add BezierCurve, with a few points.\n - BezierCurve: Add geometry nodes (or any other modifier, like wave or whatever) that changes the curve.\n - BezierCurve: (for visibility) add geometry.\n - Add Cube .1m \n - Cube: Add Array modifier and Curve modifier, targeting the BezierCurve\n\n**Expected result**: Mesh follows modified curve.\n**Actual result**: Mesh follows original (unmodified) curve.\n\nThe blender file shows this very easily, the modified curve is round, the mesh is in the \"old location\" that the curve would have without the modifier on the curve.\n\n\nYes, this is a duplicate of: 93702/ - Where apparently there is confusion on what the issue is. I could not find a way to un-archive a ticket.\n\n\n**Areas Affected**\n- Curve modifier\n- Spline IK", "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)" ]

[ "Regression: \"Store Named Attribute\" node affects all vertex groups after than the one specified. \nOperating system: Arch Linux w/ Linux-5.18.10-zen1-1-zen-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.57\n\nBroken: version: 3.3.0\nWorked: 3.2.1\nCaused by 12bde317f4\n\nSeems to be related to #99787 \nModifying a vertex group with the \"Store Named Attribute\" node affects all groups after that one.\n\n - Add many one vertex groups to a mesh.\n - Assign some weight to the vertex groups to make the issue more clear.\n - Add a \"Store Named Attribute\" node to a geometry nodes group on the object.\n - Set the target attribute to a vertex group near the top of list in the properties panel.\n # Note that the vertex group's weights of groups after the targeted group have been shifted up on in the list.\n\n\n[NoArmature.blend](NoArmature.blend)\n[Peek 2022-07-17 04-01.webm](Peek_2022-07-17_04-01.webm)" ]

[ "Blender crashes when merging mesh.vertices with a python script\nOperating system: Pop_OS 20.04\nGraphics card: Intel 4th Generation Core Proc \n\n\nBroken: 2.82a\n\n\nLink to stackoverflow question:\n\nblender-crashes-when-merging-mesh-vertices-with-a-python-script\n\nI have reuploaded the question here because I think It could be an error with blender code rather than mine. The steps to reproduce the crash would be creating an icosphere mesh, setting the max_distance variable to 0.3 and just moving nodes nearby to other ones and clicking run_script then. At some point it will close and save an ico.crash.txt. I have attached mine.\n\n[ico.crash.txt](ico.crash.txt)\n\n[#88022.blend](T88022.blend)\n\n[#88022.webm](T88022.webm)", "Blender 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)", "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", "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. -----------------------------------------------------------", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "Regression: Crash when sculpting shape keys in 3.6.2 release\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: 3.5 did not crash, I'm told.\n\n**Description**\nA user in a Discord community shared a file which was crashing for them while in Sculpt mode. I could reproduce the crash, so I simplified the file and found repro steps.\n<video src=\"attachment\" title=\"2023-09-14 00-35-34.mp4\" controls></video>\n\nAs you can see, it takes a few seconds of aggressively dragging the shape key value to get the crash to occur.\nAnother way to get the crash is to just make sculpt brush strokes. I found the shape key slider dragging easier, but I could get it to crash with sculpt strokes too, which was the original complaint from the user.\nMaybe worth noting that, as far as I can tell, if the shape key is not this extreme in its effect, then it seems even harder or impossible to produce the crash.\n\n- File: [Vessa_clean5.blend](attachment)\n- Make sure you're in sculpt mode (I don't think it can crash otherwise)\n- Drag the shape key value around for several seconds, or make a few dozen sculpt strokes\n- Should crash eventually.\n\n", "Cloth simulation collision differs between viewport and render when collider is hidden\nOperating system: Fedora Linux\nGraphics card: AMD\n\nBroken: 3.3.0 - 3.6.1\nWorked: \n\nCloth simulation collision differs between viewport and render when collider is hidden in both.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n- create a cloth that will collide with the default cube\n- hide the default cube in both render and viewport\n- press play\n- the cloth will collide with the hidden default cube\n- press pause\n- go to frame 1\n- enter and exit edit mode on the cloth mesh to reset the cloth simulation cache\n- render the animation\n- the cloth will not collide with the hidden default cube\n\nAdditionally:\n\n- If you play with cube hidden, up to when cloth collided the cube, and render animation, the animation will be like: cloth collided the cube, and after the cache runs out, it starts falling as if the cube has not been there.\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", "GPencil: Blender crash when file open\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.0 Beta\n\nAs soon as I open attached file Blender crashes. Attached also crash log file.\n\n- Open attached file\n- Change radius (say 0.6)\n- Save file\n- reopen it (Crash)\n[#102930.blend](T102930.blend)", "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", "Dyntopo detail size drawing with Shift + D seems broken\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: At least a few alpha versions ago\n\nDyntopo size control with Shift + D seems broken.\nThe first time I tried, the gizmo simply froze and the Resolution value didn't change after mouse movement.\nAfter installing the latest GeForce Studio Driver — version 457.30 — I tried again. The gizmo casts infinite lines, but I noticed that the Resolution value does change after mouse movement.\n\n1. Enter Sculpt Mode.\n2. Activate Dyntopo.\n3. Switch to Constant Detail mode.\n4. Press Shift + D.", "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", "Crush while baking a cloth simulation\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.2\n\nI was performing the baking of a cloth simulation. During the initial and subsequent baking attempts, everything worked fine. However, when I tried to re-bake the simulation after moving the cursor in the timeline, the program crashes. I tries to bake that cloth in previous versions. It didn't work as well\n\nTo trigger the crash, you simply need to move the cursor in the timeline and then initiate the baking process.\n\nUnfortunately, i cannot add the file (size is 200mb and i can't make it smaller ), so than i added the crash txt file and a link to the file on google drive\nview?usp=sharing\nThank you!\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)", "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" ]

[ "Regression: Crash with dyntopo when cursor moved over object \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.4, 3.5.0 Alpha\nWorked: 3.3\nCaused by d7cfb6ac71\n\nCrash to desktop when cursor moved over either default cube or plane when in dyntopo sculpt mode. \nThis does not happen with objects such as UV sphere or monkey.\nGPU subdivision on/off has no effect.\n\n- With default cube, open sculpt mode\n- Turn on dyntopo\n- Move cursor over surface of object if doesn't crash, try to move quickly over object\n" ]

[ "Window title shows unsaved indicator while loading\nOperating system: Linux-4.15.0-45-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: May 18 2021, hash: `1f9eb7e2c6`\n\nWhile Blender loads a file, the window title shows the unsaved indicator: `Blender* [/path/to/blend]`.\n\n- Create a .blend file which takes long to load. A simple example involves creating huge amounts of geometry with Array modifier, then applying the modifier.\n- Open the startup file (ctrl+N) so the window title is cleared (makes it easier to see what changes, but not required).\n- Open the .blend you created earlier, you will see the unsaved indicator in the title until loading finished.\n\n", "Crash guide during render complete August 29, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.44\n\nBroken: version: 3.3.0 Beta\n\nBlender 3.3 Beta crash guide during render August 29, 2022\n\n\nNot matter all version 3.0 to 3.4 keep me crash. Do not use Windows. Only for Macintosh.\n\n\n\n[Blender-2022-08-29-092340.ips](Blender-2022-08-29-092340.ips)\n\n[Armor wear 1.0.0.blend](Armor_wear_1.0.0.blend)\n\n\n\nT100328\n@Nurb2Kea\nRender 600 (complete render cause crash guide)\n", "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", "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)", "Collada export crashes (when relative \"//\" is in `Preferences` > `File Paths` > `Temporary Files`)\nOperating system: macOS 12.1\nGraphics card: M1 MBP\n\nBroken: 3.0 with the attached userpref.blend\nBroken: 2.93.8\nBroken: 2.83.19\n\n\n\nfrom factory-startup:\n\n- - [x] type `//` in `Preferences` > `File Paths` > `Temporary Files`\n- - [x] `Export` > `Collada`\n- crash\n\nnote: in a debug build, the following assert is hit after step [1]\n```\n./bin/blender(BLI_system_backtrace+0x26) [0xf4a5f1b]\n./bin/blender(_BLI_assert_print_backtrace+0x16) [0xf344596]\n./bin/blender(BLI_exists+0x2a) [0xf497c6c]\n./bin/blender(BLI_is_dir+0x18) [0xf497d21]\n./bin/blender() [0x3c2a38d]\n./bin/blender(BKE_tempdir_init+0x27) [0x3c2a5e2]\n./bin/blender() [0x4c1ec17]\n./bin/blender() [0x4a2e592]\n./bin/blender(RNA_property_update+0x50) [0x4a2e7ca]\n./bin/blender() [0x55d728b]\n./bin/blender() [0x55f3b4a]\n./bin/blender() [0x435810e]\n./bin/blender() [0x435e018]\n./bin/blender() [0x435e5cc]\n./bin/blender(wm_event_do_handlers+0x7a0) [0x435fd81]\n./bin/blender(WM_main+0x30) [0x4351d2e]\n./bin/blender() [0x3c236af]\n/lib64/libc.so.6(+0x2d590) [0x7fb0c4842590]\n/lib64/libc.so.6(__libc_start_main+0x89) [0x7fb0c4842649]\n./bin/blender(_start+0x25) [0x3c23095]\nBLI_assert failed: source/blender/blenlib/intern/storage.c:348, BLI_exists(), at '!BLI_path_is_rel(path)'\n```", "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)", "Cycles Render with Intel UHD GPU Crashes\nOperating system: macOS Ventura 13.0.1\nGraphics card: Intel UHD Graphics 630 (built-in), AMD Radeon RX 6800 (eGPU)\n\nBroken: 3.4.0 (downloaded from the Blender website)\nWorked: the last 3.3.1\n\nIt is impossible to render in Cycles with the Intel GPU enabled: Blender crashes\n\nOn a Mac Mini 2018 (Intel) with 6-core i7 CPU and 32GB of RAM, with Stage Manager enabled, open Blender, load a file, then in the Preferences, enable only the Intel GPU (uncheck the eGPU), and start rendering. Note: unless it is the first attempt (that involves the loading of the kernels), unchecking the eGPU may not even be necessary.\nWhen the preliminary steps are finished (such as the BVH building, importance map, and so on), Blender will crash before the rendering proper starts (before anything appears in the render result output).\nThe subsequent error dump will look as follows: \n\nThe full dump is below:\n\n```lines\n-------------------------------------\nTranslated Report (Full Report Below)\n-------------------------------------\n\nProcess: Blender [4086]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.4.0 (3.4.0 2022-12-07)\nCode Type: X86-64 (Native)\nParent Process: launchd [1]\nUser ID: 501\n\nDate/Time: 2022-12-09 13:00:26.8303 +1000\nOS Version: macOS 13.0.1 (22A400)\nReport Version: 12\nBridge OS Version: 7.0 (20P420)\nAnonymous UUID: DA7E5727-A75F-6765-C417-804DFCD4552C\n\n\nTime Awake Since Boot: 5000 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 35\n\nException Type: EXC_CRASH (SIGABRT)\nException Codes: 0x0000000000000000, 0x0000000000000000\n\nID Vend/Dev\n8488 73bf1002\nSeconds Ago ID Type\n 5000.0 8488 Attach\n\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t 0x7ff8140160ce __semwait_signal + 10\n1 libsystem_c.dylib \t 0x7ff813f2ab4a nanosleep + 196\n2 libsystem_c.dylib \t 0x7ff813f2aa80 usleep + 53\n3 Blender \t 0x1069dd928 WM_main + 24\n4 Blender \t 0x106262b8e main + 878\n5 dyld \t 0x7ff813d21310 start + 2432\n\nThread 1:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff813ed2efb _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff813ed33d7 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x1120ad1d2 IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 Blender \t 0x1120abcce void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 13:: caulk.messenger.shared:17\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 caulk \t 0x7ff81d7598f8 caulk::mach::semaphore::wait_or_error() + 16\n2 caulk \t 0x7ff81d73f664 caulk::concurrent::details::worker_thread::run() + 36\n3 caulk \t 0x7ff81d73f328 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 41\n4 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n5 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 17:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 18:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 25:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t 0x7ff8140136a2 mach_msg2_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff81402167d mach_msg2_internal + 82\n2 libsystem_kernel.dylib \t 0x7ff81401a71a mach_msg_overwrite + 723\n3 libsystem_kernel.dylib \t 0x7ff814013989 mach_msg + 19\n4 CoreAudio \t 0x7ff81635f8a5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n5 CoreAudio \t 0x7ff8162384c1 HALC_ProxyIOContext::IOWorkLoop() + 3783\n6 CoreAudio \t 0x7ff816237029 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63\n7 CoreAudio \t 0x7ff8163be630 HALB_IOThread::Entry(void*) + 72\n8 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n9 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libopenblas64_.0.dylib \t 0x136d5a49f blas_thread_server + 207\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 31:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t 0x7ff8140136a2 mach_msg2_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff81402167d mach_msg2_internal + 82\n2 libsystem_kernel.dylib \t 0x7ff81401a71a mach_msg_overwrite + 723\n3 libsystem_kernel.dylib \t 0x7ff814013989 mach_msg + 19\n4 CoreFoundation \t 0x7ff81412cd0e __CFRunLoopServiceMachPort + 145\n5 CoreFoundation \t 0x7ff81412b77a __CFRunLoopRun + 1360\n6 CoreFoundation \t 0x7ff81412abb0 CFRunLoopRunSpecific + 560\n7 AppKit \t 0x7ff8173ad696 _NSEventThread + 132\n8 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n9 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108d23ba5 ccl::Session::wait() + 101\n4 Blender \t 0x1081da316 ccl::BlenderSession::render(BL::Depsgraph&) + 3526\n5 Blender \t 0x1081d10e0 ccl::render_func(_object*, _object*) + 176\n6 Blender \t 0x112141552 cfunction_call + 130\n7 Blender \t 0x1120fa1b5 _PyObject_MakeTpCall + 373\n8 Blender \t 0x1121efcce call_function + 974\n9 Blender \t 0x1121eca4a _PyEval_EvalFrameDefault + 30570\n10 Blender \t 0x1121e51b1 _PyEval_Vector + 145\n11 Blender \t 0x1121efaaf call_function + 431\n12 Blender \t 0x1121eca4a _PyEval_EvalFrameDefault + 30570\n13 Blender \t 0x1121e51b1 _PyEval_Vector + 145\n14 Blender \t 0x106f00225 bpy_class_call + 1029\n15 Blender \t 0x106e433d1 engine_render + 113\n16 Blender \t 0x1079cb58c engine_render_view_layer(Render*, RenderEngine*, ViewLayer*, bool, bool) + 572\n17 Blender \t 0x1079cb0ca RE_engine_render + 954\n18 Blender \t 0x1079d097e do_render_full_pipeline(Render*) + 334\n19 Blender \t 0x1079d0566 RE_RenderFrame + 406\n20 Blender \t 0x108178e8f render_startjob(void*, short*, short*, float*) + 127\n21 Blender \t 0x1069f92f8 do_job_thread + 40\n22 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n23 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 34:\n0 libsystem_kernel.dylib \t 0x7ff81401361e semaphore_wait_trap + 10\n1 Blender \t 0x1069d3e08 tbb::internal::rml::private_worker::run() + 104\n2 Blender \t 0x1069d3d99 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 35 Crashed:\n0 libsystem_kernel.dylib \t 0x7ff81401a30e __pthread_kill + 10\n1 libsystem_pthread.dylib \t 0x7ff814051f7b pthread_kill + 263\n2 libsystem_c.dylib \t 0x7ff813f9bd3f __abort + 139\n3 libsystem_c.dylib \t 0x7ff813f9bcb4 abort + 138\n4 libsystem_c.dylib \t 0x7ff813f9afbe __assert_rtn + 314\n5 Metal \t 0x7ff81d6acf32 MTLReportFailure.cold.1 + 43\n6 Metal \t 0x7ff81d687df9 MTLReportFailure + 529\n7 Metal \t 0x7ff81d5913ba -[_MTLCommandBuffer addCompletedHandler:] + 87\n8 Blender \t 0x10827ac38 ccl::MetalDeviceQueue::enqueue(ccl::DeviceKernel, int, ccl::DeviceKernelArguments const&) + 3352\n9 Blender \t 0x108dc338b ccl::ShaderEval::eval_gpu(ccl::Device*, ccl::ShaderEvalType, ccl::device_vector<ccl::KernelShaderEvalInput>&, ccl::device_vector<float>&, long long) + 267\n10 Blender \t 0x108dc2d48 std::__1::__function::__func<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0, std::__1::allocator<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0>, void (ccl::Device*)>::operator()(ccl::Device*&&) + 680\n11 Blender \t 0x10823c8af ccl::Device::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 31\n12 Blender \t 0x108246740 ccl::MultiDevice::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 64\n13 Blender \t 0x108dc296a ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&) + 154\n14 Blender \t 0x108c2a79f ccl::GeometryManager::displace(ccl::Device*, ccl::Scene*, ccl::Mesh*, ccl::Progress&) + 511\n15 Blender \t 0x108bb4769 ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 3305\n16 Blender \t 0x108c51111 ccl::Scene::device_update(ccl::Device*, ccl::Progress&) + 1745\n17 Blender \t 0x108c52d73 ccl::Scene::update(ccl::Progress&) + 163\n18 Blender \t 0x108d246e3 ccl::Session::run_update_for_next_iteration() + 1395\n19 Blender \t 0x108d23c74 ccl::Session::run_main_render_loop() + 100\n20 Blender \t 0x108d24c13 ccl::Session::thread_render() + 259\n21 Blender \t 0x108d228c8 ccl::Session::thread_run() + 168\n22 Blender \t 0x10db3e413 ccl::thread::run(void*) + 19\n23 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n24 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\nThread 39:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 40:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 41:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 42:\n0 libsystem_kernel.dylib \t 0x7ff8140161fe __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t 0x7ff8140527e1 _pthread_cond_wait + 1243\n2 libc++.1.dylib \t 0x7ff813faec32 std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18\n3 Blender \t 0x108271985 ccl::ShaderCache::compile_thread_func(int) + 165\n4 Blender \t 0x108274dfd void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*) + 45\n5 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n\nThread 43:\n0 libsystem_pthread.dylib \t 0x7ff81404dc58 start_wqthread + 0\n\n\nThread 35 crashed with X86 Thread State (64-bit):\n```\nrax: 0x0000000000000000 rbx: 0x000070001368d000 rcx: 0x000070001368a7c8 rdx: 0x0000000000000000\nrdi: 0x000000000002c707 rsi: 0x0000000000000006 rbp: 0x000070001368a7f0 rsp: 0x000070001368a7c8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x000070001368d000 r11: 0x0000000000000246\nr12: 0x000000000002c707 r13: 0x000000012feea028 r14: 0x0000000000000006 r15: 0x0000000000000016\nrip: 0x00007ff81401a30e rfl: 0x0000000000000246 cr2: 0x000000012feea000\n\n```\nLogical CPU: 0\nError Code: 0x02000148 \nTrap Number: 133\n\n\nBinary Images:\n 0x7ff814012000 - 0x7ff81404bff7 libsystem_kernel.dylib (*) <0c2fd2c9-777c-3355-b70f-7b1b6e9d1b0b> /usr/lib/system/libsystem_kernel.dylib\n 0x7ff813f1a000 - 0x7ff813fa2fff libsystem_c.dylib (*) <5efaf10b-2ec1-32ed-b077-80125e552c8d> /usr/lib/system/libsystem_c.dylib\n 0x1060c2000 - 0x116badfff org.blenderfoundation.blender (3.4.0) <de78ac19-6469-3e44-ab08-627697965862> /Applications/Blender.app/Contents/MacOS/Blender\n 0x7ff813d1b000 - 0x7ff813daf54f dyld (*) <28fd2071-57f3-3873-87bf-e4f674a82de6> /usr/lib/dyld\n 0x7ff813ed0000 - 0x7ff813f16ff3 libdispatch.dylib (*) <817339a1-d03e-3e54-9c47-acacf69f6193> /usr/lib/system/libdispatch.dylib\n 0x7ff81404c000 - 0x7ff814057ff7 libsystem_pthread.dylib (*) <13b5e252-77d1-31e1-888d-1c5f4426ea87> /usr/lib/system/libsystem_pthread.dylib\n 0x7ff81d73d000 - 0x7ff81d762fff com.apple.audio.caulk (1.0) <43ed8c13-59df-3c8d-b4d2-aee44e4939b9> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7ff816060000 - 0x7ff81675affd com.apple.audio.CoreAudio (5.0) <e9f27094-01cb-337a-8530-0cab0e2cc96d> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x136a29000 - 0x13a6b4fff libopenblas64_.0.dylib (*) <10431d8f-5e3b-3bbc-abd5-81f6a73a5269> /Applications/Blender.app/Contents/Resources/3.4/python/lib/python3.10/site-packages/numpy/.dylibs/libopenblas64_.0.dylib\n 0x7ff8140ae000 - 0x7ff814546fff com.apple.CoreFoundation (6.9) <dbc459f3-81bb-398a-8f74-3f7392392bb7> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7ff81720f000 - 0x7ff818213ff6 com.apple.AppKit (6.9) <817d572e-eb8c-3999-b7a0-68e1c4b47266> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7ff813fa3000 - 0x7ff813ffbff3 libc++.1.dylib (*) <06015868-b157-3745-889b-69e23c5034fd> /usr/lib/libc++.1.dylib\n 0x7ff81d570000 - 0x7ff81d73cffb com.apple.Metal (306.2.4) <4ac8bfa1-153f-3c2d-8f98-6831b7c643f8> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n\nExternal Modification Summary:\n```\nCalls made by other processes targeting this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\nCalls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\nCalls made by all processes on this machine:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n```\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\nWritable regions: Total=47.1G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=47.1G(100%)\n\n```\n VIRTUAL REGION \n```\nREGION TYPE SIZE COUNT (non-coalesced) \n**=======**\nAccelerate framework 256K 2 \nActivity Tracing 256K 1 \nCG backing stores 960K 4 \nCG image 228K 14 \nColorSync 228K 25 \nCoreAnimation 64K 14 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreUI image data 636K 9 \nFoundation 16K 1 \nIOAccelerator 12.8G 547 \nIOKit 148K 10 \nIOSurface 58.3M 8 \nKernel Alloc Once 8K 1 \nMALLOC 32.1G 1445 \nMALLOC guard page 48K 9 \nMALLOC_LARGE (reserved) 383.9M 11 reserved VM address space (unallocated)\nMALLOC_MEDIUM (reserved) 496.0M 10 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 176K 44 \nStack 69.8M 44 \nVM_ALLOCATE 158.7M 96 \nVM_ALLOCATE (reserved) 224.0M 3 reserved VM address space (unallocated)\n__CTF 756 1 \n__DATA 59.9M 642 \n__DATA_CONST 51.3M 373 \n__DATA_DIRTY 1753K 211 \n__FONT_DATA 2352 1 \n__GLSLBUILTINS 5174K 1 \n__LINKEDIT 274.5M 70 \n__OBJC_RO 65.1M 1 \n__OBJC_RW 1982K 2 \n__TEXT 989.1M 651 \ndyld private memory 512K 3 \nmapped file 298.9M 95 \nshared memory 447.1M 580 \n**=======**\nTOTAL 48.8G 4936 \nTOTAL, minus reserved VM space 47.4G 4936 \n\n\n\n-----------\nFull Report\n-----------\n\n{\"app_name\":\"Blender\",\"timestamp\":\"2022-12-09 13:00:27.00 +1000\",\"app_version\":\"3.4.0\",\"slice_uuid\":\"de78ac19-6469-3e44-ab08-627697965862\",\"build_version\":\"3.4.0 2022-12-07\",\"platform\":1,\"bundleID\":\"org.blenderfoundation.blender\",\"share_with_app_devs\":0,\"is_first_party\":0,\"bug_type\":\"309\",\"os_version\":\"macOS 13.0.1 (22A400)\",\"roots_installed\":0,\"name\":\"Blender\",\"incident_id\":\"C005C7B8-C72E-4093-B4F1-FAE90C2561DF\"}\n{\n```\n\"uptime\" : 5000,\n\"procRole\" : \"Foreground\",\n\"version\" : 2,\n\"userID\" : 501,\n\"deployVersion\" : 210,\n\"modelCode\" : \"Macmini8,1\",\n\"coalitionID\" : 1400,\n\"osVersion\" : {\n \"train\" : \"macOS 13.0.1\",\n \"build\" : \"22A400\",\n \"releaseType\" : \"User\"\n},\n\"captureTime\" : \"2022-12-09 13:00:26.8303 +1000\",\n\"incident\" : \"C005C7B8-C72E-4093-B4F1-FAE90C2561DF\",\n\"pid\" : 4086,\n\"cpuType\" : \"X86-64\",\n\"roots_installed\" : 0,\n\"bug_type\" : \"309\",\n\"procLaunch\" : \"2022-12-09 12:58:58.0017 +1000\",\n\"procStartAbsTime\" : 4965752889748,\n\"procExitAbsTime\" : 5054490072306,\n\"procName\" : \"Blender\",\n\"procPath\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n\"bundleInfo\" : {\"CFBundleShortVersionString\":\"3.4.0\",\"CFBundleVersion\":\"3.4.0 2022-12-07\",\"CFBundleIdentifier\":\"org.blenderfoundation.blender\"},\n\"storeInfo\" : {\"deviceIdentifierForVendor\":\"94D4C7AA-42A4-5C3F-8C08-A3A0F4499D46\",\"thirdParty\":true},\n\"parentProc\" : \"launchd\",\n\"parentPid\" : 1,\n\"coalitionName\" : \"org.blenderfoundation.blender\",\n\"crashReporterKey\" : \"DA7E5727-A75F-6765-C417-804DFCD4552C\",\n\"bridgeVersion\" : {\"build\":\"20P420\",\"train\":\"7.0\"},\n\"sip\" : \"enabled\",\n\"externalGPUInfo\" : \"ID Vend\\/Dev\\n8488 73bf1002\\nSeconds Ago ID Type\\n 5000.0 8488 Attach\\n\",\n\"exception\" : {\"codes\":\"0x0000000000000000, 0x0000000000000000\",\"rawCodes\":[0,0],\"type\":\"EXC_CRASH\",\"signal\":\"SIGABRT\"},\n\"extMods\" : {\"caller\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"system\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"targeted\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"warnings\":0},\n\"faultingThread\" : 35,\n\"threads\" : [{\"id\":64792,\"queue\":\"com.apple.main-thread\",\"frames\":[{\"imageOffset\":16590,\"symbol\":\"__semwait_signal\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":68426,\"symbol\":\"nanosleep\",\"symbolLocation\":196,\"imageIndex\":1},{\"imageOffset\":68224,\"symbol\":\"usleep\",\"symbolLocation\":53,\"imageIndex\":1},{\"imageOffset\":9550120,\"symbol\":\"WM_main\",\"symbolLocation\":24,\"imageIndex\":2},{\"imageOffset\":1706894,\"symbol\":\"main\",\"symbolLocation\":878,\"imageIndex\":2},{\"imageOffset\":25360,\"symbol\":\"start\",\"symbolLocation\":2432,\"imageIndex\":3}]},{\"id\":64803,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64804,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64805,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64806,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64807,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64808,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64809,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64810,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64811,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64812,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64813,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64814,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":12027,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":4},{\"imageOffset\":13271,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":4},{\"imageOffset\":201241042,\"symbol\":\"IlmThread_3_1::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":50,\"imageIndex\":2},{\"imageOffset\":201235662,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_3_1::Thread::*)(), IlmThread_3_1::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64817,\"name\":\"caulk.messenger.shared:17\",\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":116984,\"symbol\":\"caulk::mach::semaphore::wait_or_error()\",\"symbolLocation\":16,\"imageIndex\":6},{\"imageOffset\":9828,\"symbol\":\"caulk::concurrent::details::worker_thread::run()\",\"symbolLocation\":36,\"imageIndex\":6},{\"imageOffset\":9000,\"symbol\":\"void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*)\",\"symbolLocation\":41,\"imageIndex\":6},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64872,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64873,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64874,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64875,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64876,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64877,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64878,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64879,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64880,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64881,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64882,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64883,\"name\":\"com.apple.audio.IOThread.client\",\"frames\":[{\"imageOffset\":5794,\"symbol\":\"mach_msg2_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":63101,\"symbol\":\"mach_msg2_internal\",\"symbolLocation\":82,\"imageIndex\":0},{\"imageOffset\":34586,\"symbol\":\"mach_msg_overwrite\",\"symbolLocation\":723,\"imageIndex\":0},{\"imageOffset\":6537,\"symbol\":\"mach_msg\",\"symbolLocation\":19,\"imageIndex\":0},{\"imageOffset\":3143845,\"symbol\":\"HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int)\",\"symbolLocation\":111,\"imageIndex\":7},{\"imageOffset\":1934529,\"symbol\":\"HALC_ProxyIOContext::IOWorkLoop()\",\"symbolLocation\":3783,\"imageIndex\":7},{\"imageOffset\":1929257,\"symbol\":\"invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)\",\"symbolLocation\":63,\"imageIndex\":7},{\"imageOffset\":3532336,\"symbol\":\"HALB_IOThread::Entry(void*)\",\"symbolLocation\":72,\"imageIndex\":7},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64909,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64910,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64911,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64912,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64913,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":3347615,\"symbol\":\"blas_thread_server\",\"symbolLocation\":207,\"imageIndex\":8},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":64992,\"name\":\"com.apple.NSEventThread\",\"frames\":[{\"imageOffset\":5794,\"symbol\":\"mach_msg2_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":63101,\"symbol\":\"mach_msg2_internal\",\"symbolLocation\":82,\"imageIndex\":0},{\"imageOffset\":34586,\"symbol\":\"mach_msg_overwrite\",\"symbolLocation\":723,\"imageIndex\":0},{\"imageOffset\":6537,\"symbol\":\"mach_msg\",\"symbolLocation\":19,\"imageIndex\":0},{\"imageOffset\":519438,\"symbol\":\"__CFRunLoopServiceMachPort\",\"symbolLocation\":145,\"imageIndex\":9},{\"imageOffset\":513914,\"symbol\":\"__CFRunLoopRun\",\"symbolLocation\":1360,\"imageIndex\":9},{\"imageOffset\":510896,\"symbol\":\"CFRunLoopRunSpecific\",\"symbolLocation\":560,\"imageIndex\":9},{\"imageOffset\":1697430,\"symbol\":\"_NSEventThread\",\"symbolLocation\":132,\"imageIndex\":10},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65215,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":46537637,\"symbol\":\"ccl::Session::wait()\",\"symbolLocation\":101,\"imageIndex\":2},{\"imageOffset\":34702102,\"symbol\":\"ccl::BlenderSession::render(BL::Depsgraph&)\",\"symbolLocation\":3526,\"imageIndex\":2},{\"imageOffset\":34664672,\"symbol\":\"ccl::render_func(_object*, _object*)\",\"symbolLocation\":176,\"imageIndex\":2},{\"imageOffset\":201848146,\"symbol\":\"cfunction_call\",\"symbolLocation\":130,\"imageIndex\":2},{\"imageOffset\":201556405,\"symbol\":\"_PyObject_MakeTpCall\",\"symbolLocation\":373,\"imageIndex\":2},{\"imageOffset\":202562766,\"symbol\":\"call_function\",\"symbolLocation\":974,\"imageIndex\":2},{\"imageOffset\":202549834,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30570,\"imageIndex\":2},{\"imageOffset\":202518961,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":2},{\"imageOffset\":202562223,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":2},{\"imageOffset\":202549834,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30570,\"imageIndex\":2},{\"imageOffset\":202518961,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":2},{\"imageOffset\":14934565,\"symbol\":\"bpy_class_call\",\"symbolLocation\":1029,\"imageIndex\":2},{\"imageOffset\":14160849,\"symbol\":\"engine_render\",\"symbolLocation\":113,\"imageIndex\":2},{\"imageOffset\":26252684,\"symbol\":\"engine_render_view_layer(Render*, RenderEngine*, ViewLayer*, bool, bool)\",\"symbolLocation\":572,\"imageIndex\":2},{\"imageOffset\":26251466,\"symbol\":\"RE_engine_render\",\"symbolLocation\":954,\"imageIndex\":2},{\"imageOffset\":26274174,\"symbol\":\"do_render_full_pipeline(Render*)\",\"symbolLocation\":334,\"imageIndex\":2},{\"imageOffset\":26273126,\"symbol\":\"RE_RenderFrame\",\"symbolLocation\":406,\"imageIndex\":2},{\"imageOffset\":34303631,\"symbol\":\"render_startjob(void*, short*, short*, float*)\",\"symbolLocation\":127,\"imageIndex\":2},{\"imageOffset\":9663224,\"symbol\":\"do_job_thread\",\"symbolLocation\":40,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65354,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65355,\"frames\":[{\"imageOffset\":5662,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":9510408,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":104,\"imageIndex\":2},{\"imageOffset\":9510297,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"triggered\":true,\"id\":65357,\"threadState\":{\"r13\":{\"value\":5099135016},\"rax\":{\"value\":0},\"rflags\":{\"value\":582},\"cpu\":{\"value\":0},\"r14\":{\"value\":6},\"rsi\":{\"value\":6},\"r8\":{\"value\":0},\"cr2\":{\"value\":5099134976},\"rdx\":{\"value\":0},\"r10\":{\"value\":123145627947008},\"r9\":{\"value\":10000000},\"r15\":{\"value\":22},\"rbx\":{\"value\":123145627947008},\"trap\":{\"value\":133},\"err\":{\"value\":33554760},\"r11\":{\"value\":582},\"rip\":{\"value\":140703464268558,\"matchesCrashFrame\":1},\"rbp\":{\"value\":123145627936752},\"rsp\":{\"value\":123145627936712},\"r12\":{\"value\":182023},\"rcx\":{\"value\":123145627936712},\"flavor\":\"x86_THREAD_STATE\",\"rdi\":{\"value\":182023}},\"frames\":[{\"imageOffset\":33550,\"symbol\":\"__pthread_kill\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":24443,\"symbol\":\"pthread_kill\",\"symbolLocation\":263,\"imageIndex\":5},{\"imageOffset\":531775,\"symbol\":\"__abort\",\"symbolLocation\":139,\"imageIndex\":1},{\"imageOffset\":531636,\"symbol\":\"abort\",\"symbolLocation\":138,\"imageIndex\":1},{\"imageOffset\":528318,\"symbol\":\"__assert_rtn\",\"symbolLocation\":314,\"imageIndex\":1},{\"imageOffset\":1298226,\"symbol\":\"MTLReportFailure.cold.1\",\"symbolLocation\":43,\"imageIndex\":12},{\"imageOffset\":1146361,\"symbol\":\"MTLReportFailure\",\"symbolLocation\":529,\"imageIndex\":12},{\"imageOffset\":136122,\"symbol\":\"-[_MTLCommandBuffer addCompletedHandler:]\",\"symbolLocation\":87,\"imageIndex\":12},{\"imageOffset\":35359800,\"symbol\":\"ccl::MetalDeviceQueue::enqueue(ccl::DeviceKernel, int, ccl::DeviceKernelArguments const&)\",\"symbolLocation\":3352,\"imageIndex\":2},{\"imageOffset\":47190923,\"symbol\":\"ccl::ShaderEval::eval_gpu(ccl::Device*, ccl::ShaderEvalType, ccl::device_vector<ccl::KernelShaderEvalInput>&, ccl::device_vector<float>&, long long)\",\"symbolLocation\":267,\"imageIndex\":2},{\"imageOffset\":47189320,\"symbol\":\"std::__1::__function::__func<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0, std::__1::allocator<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0>, void (ccl::Device*)>::operator()(ccl::Device*&&)\",\"symbolLocation\":680,\"imageIndex\":2},{\"imageOffset\":35104943,\"symbol\":\"ccl::Device::foreach_device(std::__1::function<void (ccl::Device*)> const&)\",\"symbolLocation\":31,\"imageIndex\":2},{\"imageOffset\":35145536,\"symbol\":\"ccl::MultiDevice::foreach_device(std::__1::function<void (ccl::Device*)> const&)\",\"symbolLocation\":64,\"imageIndex\":2},{\"imageOffset\":47188330,\"symbol\":\"ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)\",\"symbolLocation\":154,\"imageIndex\":2},{\"imageOffset\":45516703,\"symbol\":\"ccl::GeometryManager::displace(ccl::Device*, ccl::Scene*, ccl::Mesh*, ccl::Progress&)\",\"symbolLocation\":511,\"imageIndex\":2},{\"imageOffset\":45033321,\"symbol\":\"ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&)\",\"symbolLocation\":3305,\"imageIndex\":2},{\"imageOffset\":45674769,\"symbol\":\"ccl::Scene::device_update(ccl::Device*, ccl::Progress&)\",\"symbolLocation\":1745,\"imageIndex\":2},{\"imageOffset\":45682035,\"symbol\":\"ccl::Scene::update(ccl::Progress&)\",\"symbolLocation\":163,\"imageIndex\":2},{\"imageOffset\":46540515,\"symbol\":\"ccl::Session::run_update_for_next_iteration()\",\"symbolLocation\":1395,\"imageIndex\":2},{\"imageOffset\":46537844,\"symbol\":\"ccl::Session::run_main_render_loop()\",\"symbolLocation\":100,\"imageIndex\":2},{\"imageOffset\":46541843,\"symbol\":\"ccl::Session::thread_render()\",\"symbolLocation\":259,\"imageIndex\":2},{\"imageOffset\":46532808,\"symbol\":\"ccl::Session::thread_run()\",\"symbolLocation\":168,\"imageIndex\":2},{\"imageOffset\":128435219,\"symbol\":\"ccl::thread::run(void*)\",\"symbolLocation\":19,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65398,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]},{\"id\":65417,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]},{\"id\":65494,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]},{\"id\":65525,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65526,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65529,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65530,\"frames\":[{\"imageOffset\":16894,\"symbol\":\"__psynch_cvwait\",\"symbolLocation\":10,\"imageIndex\":0},{\"imageOffset\":26593,\"symbol\":\"_pthread_cond_wait\",\"symbolLocation\":1243,\"imageIndex\":5},{\"imageOffset\":48178,\"symbol\":\"std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&)\",\"symbolLocation\":18,\"imageIndex\":11},{\"imageOffset\":35322245,\"symbol\":\"ccl::ShaderCache::compile_thread_func(int)\",\"symbolLocation\":165,\"imageIndex\":2},{\"imageOffset\":35335677,\"symbol\":\"void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, ccl::ShaderCache::load_kernel(ccl::DeviceKernel, ccl::MetalDevice*, ccl::MetalPipelineType)::$_1> >(void*)\",\"symbolLocation\":45,\"imageIndex\":2},{\"imageOffset\":25177,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":5},{\"imageOffset\":7291,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":5}]},{\"id\":65535,\"frames\":[{\"imageOffset\":7256,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":5}]}],\n\"usedImages\" : [\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703464235008,\n \"size\" : 237560,\n \"uuid\" : \"0c2fd2c9-777c-3355-b70f-7b1b6e9d1b0b\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_kernel.dylib\",\n \"name\" : \"libsystem_kernel.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703463219200,\n \"size\" : 561152,\n \"uuid\" : \"5efaf10b-2ec1-32ed-b077-80125e552c8d\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_c.dylib\",\n \"name\" : \"libsystem_c.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4396425216,\n \"CFBundleShortVersionString\" : \"3.4.0\",\n \"CFBundleIdentifier\" : \"org.blenderfoundation.blender\",\n \"size\" : 279887872,\n \"uuid\" : \"de78ac19-6469-3e44-ab08-627697965862\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"name\" : \"Blender\",\n \"CFBundleVersion\" : \"3.4.0 2022-12-07\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703461126144,\n \"size\" : 607568,\n \"uuid\" : \"28fd2071-57f3-3873-87bf-e4f674a82de6\",\n \"path\" : \"\\/usr\\/lib\\/dyld\",\n \"name\" : \"dyld\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703462916096,\n \"size\" : 290804,\n \"uuid\" : \"817339a1-d03e-3e54-9c47-acacf69f6193\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libdispatch.dylib\",\n \"name\" : \"libdispatch.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703464472576,\n \"size\" : 49144,\n \"uuid\" : \"13b5e252-77d1-31e1-888d-1c5f4426ea87\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_pthread.dylib\",\n \"name\" : \"libsystem_pthread.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703622746112,\n \"CFBundleShortVersionString\" : \"1.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.caulk\",\n \"size\" : 155648,\n \"uuid\" : \"43ed8c13-59df-3c8d-b4d2-aee44e4939b9\",\n \"path\" : \"\\/System\\/Library\\/PrivateFrameworks\\/caulk.framework\\/Versions\\/A\\/caulk\",\n \"name\" : \"caulk\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703498108928,\n \"CFBundleShortVersionString\" : \"5.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.CoreAudio\",\n \"size\" : 7319550,\n \"uuid\" : \"e9f27094-01cb-337a-8530-0cab0e2cc96d\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreAudio.framework\\/Versions\\/A\\/CoreAudio\",\n \"name\" : \"CoreAudio\",\n \"CFBundleVersion\" : \"5.0\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 5211590656,\n \"size\" : 63488000,\n \"uuid\" : \"10431d8f-5e3b-3bbc-abd5-81f6a73a5269\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/Resources\\/3.4\\/python\\/lib\\/python3.10\\/site-packages\\/numpy\\/.dylibs\\/libopenblas64_.0.dylib\",\n \"name\" : \"libopenblas64_.0.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64h\",\n \"base\" : 140703464873984,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.CoreFoundation\",\n \"size\" : 4820992,\n \"uuid\" : \"dbc459f3-81bb-398a-8f74-3f7392392bb7\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreFoundation.framework\\/Versions\\/A\\/CoreFoundation\",\n \"name\" : \"CoreFoundation\",\n \"CFBundleVersion\" : \"1953.1\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703516651520,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.AppKit\",\n \"size\" : 16797687,\n \"uuid\" : \"817d572e-eb8c-3999-b7a0-68e1c4b47266\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/AppKit.framework\\/Versions\\/C\\/AppKit\",\n \"name\" : \"AppKit\",\n \"CFBundleVersion\" : \"2299\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703463780352,\n \"size\" : 364532,\n \"uuid\" : \"06015868-b157-3745-889b-69e23c5034fd\",\n \"path\" : \"\\/usr\\/lib\\/libc++.1.dylib\",\n \"name\" : \"libc++.1.dylib\"\n},\n{\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703620857856,\n \"CFBundleShortVersionString\" : \"306.2.4\",\n \"CFBundleIdentifier\" : \"com.apple.Metal\",\n \"size\" : 1888252,\n \"uuid\" : \"4ac8bfa1-153f-3c2d-8f98-6831b7c643f8\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/Metal.framework\\/Versions\\/A\\/Metal\",\n \"name\" : \"Metal\",\n \"CFBundleVersion\" : \"306.2.4\"\n}\n```\n],\n```\n\"sharedCache\" : {\n\"base\" : 140703460519936,\n\"size\" : 21474836480,\n\"uuid\" : \"840e528a-0c70-3c6a-b7b4-4f05f32ccc51\"\n```\n},\n```\n\"vmSummary\" : \"ReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\\nWritable regions: Total=47.1G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=47.1G(100%)\\n\\n VIRTUAL REGION \\nREGION TYPE SIZE COUNT (non-coalesced) \\n=========== ======= ======= \\nAccelerate framework 256K 2 \\nActivity Tracing 256K 1 \\nCG backing stores 960K 4 \\nCG image 228K 14 \\nColorSync 228K 25 \\nCoreAnimation 64K 14 \\nCoreGraphics 12K 2 \\nCoreImage 4K 1 \\nCoreUI image data 636K 9 \\nFoundation 16K 1 \\nIOAccelerator 12.8G 547 \\nIOKit 148K 10 \\nIOSurface 58.3M 8 \\nKernel Alloc Once 8K 1 \\nMALLOC 32.1G 1445 \\nMALLOC guard page 48K 9 \\nMALLOC_LARGE (reserved) 383.9M 11 reserved VM address space (unallocated)\\nMALLOC_MEDIUM (reserved) 496.0M 10 reserved VM address space (unallocated)\\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\\nOpenGL GLSL 256K 3 \\nSTACK GUARD 176K 44 \\nStack 69.8M 44 \\nVM_ALLOCATE 158.7M 96 \\nVM_ALLOCATE (reserved) 224.0M 3 reserved VM address space (unallocated)\\n__CTF 756 1 \\n__DATA 59.9M 642 \\n__DATA_CONST 51.3M 373 \\n__DATA_DIRTY 1753K 211 \\n__FONT_DATA 2352 1 \\n__GLSLBUILTINS 5174K 1 \\n__LINKEDIT 274.5M 70 \\n__OBJC_RO 65.1M 1 \\n__OBJC_RW 1982K 2 \\n__TEXT 989.1M 651 \\ndyld private memory 512K 3 \\nmapped file 298.9M 95 \\nshared memory 447.1M 580 \\n=========== ======= ======= \\nTOTAL 48.8G 4936 \\nTOTAL, minus reserved VM space 47.4G 4936 \\n\",\n\"legacyInfo\" : {\n\"threadTriggered\" : {\n```\n\n```\n}\n```\n},\n```\n\"trialInfo\" : {\n\"rollouts\" : [\n {\n \"rolloutId\" : \"5fb4245a1bbfe8005e33a1e1\",\n \"factorPackIds\" : {\n```\n\n```\n },\n \"deploymentId\" : 240000021\n },\n {\n \"rolloutId\" : \"62b4513af75dc926494899c6\",\n \"factorPackIds\" : {\n \"COREOS_ICD\" : \"62fbe3cfa9a700130f60b3ea\"\n },\n \"deploymentId\" : 240000014\n }\n],\n\"experiments\" : [\n```\n\n```\n]\n```\n}\n}\n\nModel: Macmini8,1, BootROM 1916.40.8.0.0 (iBridge: 20.16.420.0.0,0), 6 processors, 6-Core Intel Core i7, 3.2 GHz, 32 GB, SMC \nGraphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In\nDisplay: ASUS VG32V, 2560 x 1440 (QHD/WQHD - Wide Quad High Definition), Main, MirrorOff, Online\nGraphics: AMD Radeon RX 6800, AMD Radeon RX 6800, PCIe, 16 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, HMA82GS6CJR8N-VK\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, HMA82GS6CJR8N-VK\nAirPort: spairport_wireless_card_type_wifi (0x14E4, 0x7BF), wl0: Sep 14 2022 18:10:05 version 9.30.489.3.32.5.84 FWID 01-31bf0e8d\nBluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports\nNetwork Service: Ethernet, Ethernet, en0\nNetwork Service: Wi-Fi, AirPort, en1\nPCI Card: pci8086,15f0, USB eXtensible Host Controller, Thunderbolt@13,0,0\nPCI Card: pci144d,a808, NVM Express Controller, Thunderbolt@73,0,0\nPCI Card: AMD Radeon RX 6800, gpu-controller, Thunderbolt@12,0,0\nPCI Card: pci1002,ab28, Audio Device, Thunderbolt@12,0,1\nPCI Card: pci1002,73a6, USB eXtensible Host Controller, Thunderbolt@12,0,2\nPCI Card: pci1002,73a4, Unknown, Thunderbolt@12,0,3\nUSB Device: USB31Bus\nUSB Device: USB31Bus\nUSB Device: USB3.1 Hub\nUSB Device: USB3.1 Hub\nUSB Device: USB2.0 Hub\nUSB Device: Microsoft® LifeCam HD-3000\nUSB Device: USB2.0 Hub\nUSB Device: Matias RGB Backlit Wired Keyboard\nUSB Device: USB2.1 Hub\nUSB Device: USB Storage\nUSB Device: Dell MS116 USB Optical Mouse\nUSB Device: T2Bus\nUSB Device: Headset\nUSB Device: Apple #2 Controller\nThunderbolt Bus: Mac mini, Apple Inc., 47.5\nThunderbolt Device: Node Titan, AKiTiO, 1, 50.1\nThunderbolt Device: Portable SSD X5, SAMSUNG ELECTRONICS CO., LTD, 3, 35.1\nThunderbolt Bus: Mac mini, Apple Inc., 47.5\n```\n\nCrashing Thread:\n```\nThread 35 Crashed:\n0 libsystem_kernel.dylib \t 0x7ff81401a30e __pthread_kill + 10\n1 libsystem_pthread.dylib \t 0x7ff814051f7b pthread_kill + 263\n2 libsystem_c.dylib \t 0x7ff813f9bd3f __abort + 139\n3 libsystem_c.dylib \t 0x7ff813f9bcb4 abort + 138\n4 libsystem_c.dylib \t 0x7ff813f9afbe __assert_rtn + 314\n5 Metal \t 0x7ff81d6acf32 MTLReportFailure.cold.1 + 43\n6 Metal \t 0x7ff81d687df9 MTLReportFailure + 529\n7 Metal \t 0x7ff81d5913ba -[_MTLCommandBuffer addCompletedHandler:] + 87\n8 Blender \t 0x10827ac38 ccl::MetalDeviceQueue::enqueue(ccl::DeviceKernel, int, ccl::DeviceKernelArguments const&) + 3352\n9 Blender \t 0x108dc338b ccl::ShaderEval::eval_gpu(ccl::Device*, ccl::ShaderEvalType, ccl::device_vector<ccl::KernelShaderEvalInput>&, ccl::device_vector<float>&, long long) + 267\n10 Blender \t 0x108dc2d48 std::__1::__function::__func<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0, std::__1::allocator<ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&)::$_0>, void (ccl::Device*)>::operator()(ccl::Device*&&) + 680\n11 Blender \t 0x10823c8af ccl::Device::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 31\n12 Blender \t 0x108246740 ccl::MultiDevice::foreach_device(std::__1::function<void (ccl::Device*)> const&) + 64\n13 Blender \t 0x108dc296a ccl::ShaderEval::eval(ccl::ShaderEvalType, int, int, std::__1::function<int (ccl::device_vector<ccl::KernelShaderEvalInput>&)> const&, std::__1::function<void (ccl::device_vector<float>&)> const&) + 154\n14 Blender \t 0x108c2a79f ccl::GeometryManager::displace(ccl::Device*, ccl::Scene*, ccl::Mesh*, ccl::Progress&) + 511\n15 Blender \t 0x108bb4769 ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 3305\n16 Blender \t 0x108c51111 ccl::Scene::device_update(ccl::Device*, ccl::Progress&) + 1745\n17 Blender \t 0x108c52d73 ccl::Scene::update(ccl::Progress&) + 163\n18 Blender \t 0x108d246e3 ccl::Session::run_update_for_next_iteration() + 1395\n19 Blender \t 0x108d23c74 ccl::Session::run_main_render_loop() + 100\n20 Blender \t 0x108d24c13 ccl::Session::thread_render() + 259\n21 Blender \t 0x108d228c8 ccl::Session::thread_run() + 168\n22 Blender \t 0x10db3e413 ccl::thread::run(void*) + 19\n23 libsystem_pthread.dylib \t 0x7ff814052259 _pthread_start + 125\n24 libsystem_pthread.dylib \t 0x7ff81404dc7b thread_start + 15\n```", "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)", "VSE video strips with audio get packed into the .blend file when auto-packing enabled, leading to crashes with large amounts of videos\nOperating system: Windows 8.1\n\nBroken: 2.80, 2019-04-09\nWorked: 2.79\n\nBlender will try to pack all video/audio files in the vse into the .blend file if \"File>External Data>Automatically Pack Into .blend\" is enabled. This is terrible default behavior since it can very easily lead to blender attempting to save huge multi-gb files.\nIn addition to this, if you have more gb of files than you have ram, blender will crash when you enable auto-pack... really easy to do since a single video can easily be over 32gb.\n\nSome notes:\nBlender seems to only decide to do this for video files that have an audio track, even if the audio track is no longer loaded into the timeline.\nThere are no options to pack/unpack a video track. If the audio track is removed, the file will still attempt to be packed, but it cannot be unpacked.\n\nCreate a new 'Video Editing' file.\nLoad several gb of videos with audio into the vse timeline.\nSelect \"File>External Data>Automatically Pack Into .blend\"\nSave the file...\n", "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)", "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", "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", "Cycle gpu rendering crashes randomly\nOperating system: Win11\nGraphics card: Nvidia RTX 3070 Ti\n\nbroken: all 3.0 versions\n\nRenders keep crashing randomly when I’m using my gpu with cycles, I updated my drivers, my memory use is okay, I tried to not use denoiser, lower my samples, resolution etc but nothing works, sometimes it render 10 frames sometimes 100 but it can't render my whole animation without crashing (also for animations with low poly count and small textures tiles) \nDon't know how to read the crash log file.\n\n", "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", "Persistent data –> Out of GPU memory (macOS)\nOperating system: MacOS 12.6.6\nGraphics card: M1\n\nBroken: 3.6.1\n\nIf \"Persistent data\" checkbox is on, after a couple of frames rendering, Blender is quits or just says \"Out of GPU memory\" (a MacOS bugreport and screenshots are attached)\n\nIf I turn OFF persistent data switcher, animation rendering is working fine. It seems, the data is persistent, but the BVH loading happens on all frames, so the memory filling up.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "App automaticaly closing when auto saving the app or exporting any file\n{[F9801258](new_doc_shoe__15548_autosave_13928_autosave.crash.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel 4.5.0 - Build 26.20.100.8141\n\nBroken: version: 2.91.2\n\n\n\n" ]

[ "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "bake hair dynamics issues\nOperating system: wind 10\nGraphics card: gtx 1070\n\nBroken: blender-2.80-79f67acccb36-win64\nWorked: idk\n\nunable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.\n\n", "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", "Memory leak while rendering with particle hair?\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\nSystem Memory: 32 GB\n\nBroken: version: 3.4.0\nWorked: Could not find any which made a difference (tried 3.4.1, 3.3, 3.2, and 2.83)\n\nHi\nI've been having a problem where, while rendering in cycles, a blend file appears to be causing system memory usage to increase every frame. It does seem to plateau eventually, but the memory committed remains high even after the rendering is finished or stopped.\n\nI tried to simplify things down as much as possible, it's just the mesh and the object with several particle hair systems.\n\nRender the sample blend file.\nOriginal (240 MB)\nSample.blend?dl=0\nCompressed (54 MB)\nSample.zip?dl=0\nOr\n-Create new blend file\n-Set to render using cycles (gpu using optix)\n-Append \"Sample\" collection from attached blend file\n-Render", "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 with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "Crash when rending animation w/simple physics sim\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: Spinning beach ball in 3.1 Alpha\n\nWhen selecting \"Render Animation\", the Rendering window starts to draw, and then the app crashes.\n\n\nFile attached. Just load and Select Render Animation.[simple-physics-crash.blend](simple-physics-crash.blend)\n\n", "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)", "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", "Hair particles: cannot delete hair particles in particle edit mode until you comb it\nOperating system: Linux-3.10.0-957.10.1.el7.x86_64-x86_64-with-centos-7.6.1810-Core 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.81 (sub 4)\nWorked: 2.79\n\nYou cannot delete all (hit a) hair particles until you comb them. Even more, if you select one hair or several and hit delete, they disappear, but if you then select all the rest and hit delete, all the particles deleted come back.\n\n\n- Open this blend file: [#69487-hair-delete-279.blend](T69487-hair-delete-279.blend)\n- Press {key X} and choose Particles\n\nIn current Blender (2.82 alpha @ 756b9acaf5) hairs get deselected but are not deleted. In 2.79b the hairs are deleted.\n\n**Original steps to reproduce:**\n\nCreate a new hair particle system\nGo into particle edit mode\nSelect all, hit X delete particles -> nothing happens\nDeselect all\nSelect a couple, hit X -> the selected hairs will disappear\nSelect all, hit X -> all the hairs come back visible again\n\nThere's a hair particle system newly created in the attached file.\n[hair_particles_delete_bug.blend](hair_particles_delete_bug.blend)", "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)", "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", "Hairs not rendered in cycles when edit mode or particle edit mode is active\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\nWorked: unknown\n\nWith the attached file, when you render with F12 while edit mode or particle edit mode is active in the viewport, the hairs are not rendered. In Eevee this does not occur.\n\nOpen attached file, select the bezier curve\nPress f12 to render while in object mode -> hairs are rendered\nSwitch to edit mode or particle edit mode and press F12 -> hairs are not rendered\n\n[Feather hair bug.blend](Feather_hair_bug.blend)\n\n", "Blender full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "Crash on Changing Repeat value to -1 in Corrective Smooth modifier\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 2.93.5\n\nNot Responding when I change the Repeat value to -1\n\n{[F11810617](image.png), size=full}\n\n" ]

[ "CRASH - Blender crashes on trying to use 'Hair' particle \nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro `[D300](D300)` OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.93.0 Alpha\n\n\nBlender crashes on trying to use 'Hair' particle \n\n- Select an object\n- Go to its particle properties\n- Add a particle system by clicking the + symbol\n- Select 'Hair' ( blender crashes)\n\n\nPlease see the attached .Blend file and screen grab\n\n[donut.blend](donut.blend)\n\n\n\n" ]

[ "bake hair dynamics issues\nOperating system: wind 10\nGraphics card: gtx 1070\n\nBroken: blender-2.80-79f67acccb36-win64\nWorked: idk\n\nunable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.\n\n", "Particle System switching between Emitter/Hair \"Viewport Display\" sticks to Hair-Viewport-Display-Settings\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.92.0 Alpha\n\nIn the particle system, when you change the particle type form Emitter to Hair and then back to Emitter , the \"Viewport Display\" panel does not change back accordingly - it remains as if the Hair-type emitter is still present.\n\nit would be just as easy to create a new particle system with the right settings, to remedy this situation\n\n- create a particle system on a object\n- Observe the properties of the \"Viewport Display\" panel\n- change the particle type form Emitter to Hair (properties have changed accordingly)\n- change it back to emitter\nViewport Display won't show Options Particles have, instead it will show Hair Options like \"Strand Steps\"\n\n", "Crash and assert hit when converting empty hair to mesh\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\n\nBroken: 3.5, 3.6\nWorked: never? (conversion for \"Curves\" is added in 3.5 release)\n\nCrash triggers when converting empty hair object to mesh due null pointer access and\nassert hit at `BLI_assert(mesh_src->id.tag & LIB_TAG_NO_MAIN)` and `BLI_assert(mesh_dst == ob->data)`\n\n- Open default scene\n- Select default cube and Add empty hair object\n- Convert to > Mesh\n\n```\n \tblender.exe!_BLI_assert_abort() Line 47\tC\n>\tblender.exe!BKE_mesh_nomain_to_mesh(Mesh * mesh_src, Mesh * mesh_dst, Object * ob) Line 1113\tC++\n \tblender.exe!object_convert_exec(bContext * C, wmOperator * op) Line 3397\tC++\n \tblender.exe!wm_operator_invoke(bContext * C, wmOperatorType * ot, const wmEvent * event, PointerRNA * properties, ReportList * reports, const bool poll_only, bool use_last_properties) Line 1539\tC++\n \tblender.exe!wm_operator_call_internal(bContext * C, wmOperatorType * ot, PointerRNA * properties, ReportList * reports, const wmOperatorCallContext context, const bool poll_only, const wmEvent * event) Line 1727\tC++\n \tblender.exe!WM_operator_name_call_ptr(bContext * C, wmOperatorType * ot, wmOperatorCallContext context, PointerRNA * properties, const wmEvent * event) Line 1776\tC++\n \tblender.exe!WM_operator_name_call_ptr_with_depends_on_cursor(bContext * C, wmOperatorType * ot, wmOperatorCallContext opcontext, PointerRNA * properties, const wmEvent * event, const char * drawstr) Line 1969\tC++\n \tblender.exe!ui_apply_but_funcs_after(bContext * C) Line 1029\tC++\n \tblender.exe!ui_popup_handler(bContext * C, const wmEvent * event, void * userdata) Line 11541\tC++\n \tblender.exe!wm_handler_ui_call(bContext * C, wmEventHandler_UI * handler, const wmEvent * event, const bool always_pass) Line 814\tC++\n \tblender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3305\tC++\n \tblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3422\tC++\n \tblender.exe!wm_event_do_handlers(bContext * C) Line 4044\tC++\n \tblender.exe!WM_main(bContext * C) Line 649\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 597\tC\n```\n\n", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "Hair from 2.79 messed up in 2.8 (modifiers prior to PSys and partially broken without 'Use Modifer Stack')\nOperating system:\nGraphics card:\n\nBroken: blender-2.80.0-git.dd3f5186260e-windows64\nWorked: 2.79b release\n\nHair particles made in blender 2.79 get messed up, when opend in 2.8. The hairs are pulled in direction of objects origin:\n\n\n[hairbug.blend](hairbug.blend)\n\nopen attached file in 2.80 (and in 2.79, to compare)\n\n---\nIt is maybe is related to T59587 .. i am not sure.", "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", "Simulation issues with new hair object converted to legacy particle hair\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nSimulation of particle hair system (legacy) which was converted from new hair object has issues. Hair does not seem to be attached to surface and has weird movement.\n\nI understand that this issue relates legacy particle system, which at some point will be removed. But as of this time, it is the only way to have hair physics simulation in blender. And it would be great to have this ability with converted hair object until it gets its own simulation capabilities.\n\n- Create sphere.\n- Create hair particle system on it.\n- Enable hair physics, play simulation, observe.\n- Convert hair particle system to new hair object.\n- Delete old hair particle system on sphere\n- Assign sphere as hair surface on new hair object properties, assign sphere uvmap as hair surface uvmap\n- Select new hair object and convert it to legacy particle system.\n- Disable new hair object in viewport\n- Select sphere again -> particle system -> Hair dynamics\n- Press play and observe\n\nTest file (First 6 steps included):\n[#101621.blend](T101621.blend)", "Blender crashes with certain geometries (e.g. tweaked Jiggly Pudding simulation demo file)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 4.0.0 Alpha\nWorked: Unsure\n\nWith certain geometries, Blender will freeze then crash. I have included a demonstration in the video attached below:\n<video src=\"attachment\" title=\"Jiggly Pudding Crash.mp4\" controls></video>\n\n1. Download the Jiggly Pudding demo from demo-files/\n2. Follow the steps outlined in the video attached above. The steps in the video are as follows:\n a. Open the Jiggly Pudding file.\n b. Select the Pudding and open a geometry node editor.\n c. Inside the Simulation zone there is a node with the title \"Scale\". Change the Scale from 0.85 to 10 or something higher.\n d. Open a 3D viewport (if you haven't already) and press play in the time line.\n e. Blender will freeze and crash.\n\n", "Cycles can not render parent particle hair, while Eevee can.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.0\nWorked: I duno\n\n\nIn Eevee, parent particles are successfully rendered both in viewport and final render.\n\n\nHowever, Cycles fail to render the parent particles both in viewport and final render.\n\nA sample Blender file has been attached below.\n\n", "Bake All Dynamics doesn't work when baking particle hair\nMacBook Pro, NVIDIA GeForce GT 750M, Intel Iris Pro\nMac OS 10.12.6\n\nBroken: Blender 2.79 Hash: 5bd8ac9\n\nHitting the Bake All Dynamics to bake out particle hair doesn't do anything.\n\nLoad the attached file.\nSelect the sphere.\nGo to the particle panel.\nUnder Cache, click Bake All Dynamics.\nNothing happens.[sph.blend](sph.blend)", "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)", "Adding texture to particle emission density breaks particle simulation\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nPlease see attached file, after adding cloud texture and enabling Density in Texture influences, the simulated particles either stick to the surface or fly of into infinity as a group. \n\nOpen attached file and play animation, note some particles either sticking or a large group of particles incorrectly flying of.[particle_system_broken.blend](particle_system_broken.blend)\n\n", "Crash with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "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)", "Hair object - Node types design\nIMPORTANT: Please note that this document is subject to change and will most likely not represent the final product of the new hair object in Blender\n\n## Hair object - Node types design\n---\n## Reference links\n\n\nHair object - project description\nT68981\nHair object design\nT78606\n\nCommissioner: @DanielBystedt d.bystedt@gmail.com, dbystedt\nProject leader: @sebbas \nProject members: @ideasman42, @lichtwerk\n\n\n\n[Thread on devtalk ]] about scattering objects by [[ https:*devtalk.blender.org/u/BD3D/summary | BD3D ](https:*devtalk.blender.org/t/future-particle-hair-nodes-discussion-and-everything-wrong-with-hair-particles/9576/5) (eg Instances)\n\n---\n## NOTES\n\n- Please note that all mockups are rather simplified at the moment. For example the sphere in most images will never be a part of the actual hair curves geometry. Attributes are visualized with black/white color etc.\n- Sockets are colored by using @JacquesLucke simulation editor in the daily builds of blender as a reference.\n---\n## NODE GRAPH - EXAMPLES\n\n**Example 1**\nOpen image in new tab to view details\n{[F8679279](node_graph_example_1.jpg), height = 500}\n\n---\n## NODES - DATA FLOW\n\n\n - Node: Input\n - Type: Data flow\n\n\n**Input type (Upper drop down menu)**\n- Guide curves\n - that exists in current hair object\n\n- Alembic\n - Read (potentially) animated curves from alembic. List from .abc in blender file\n\n- Object\n - Object that exists in blender file. Used for geo masking or instancing object per hair\n\n- Collection content\n - Objects that exists in a collection in the blender file. Used for scattering random objects on surface. Random object in collection used per hair “instance”\n\n- Collection\n - That exists in blender file. Used for scattering objects on surface. The result of the entire collection is used per hair \"instance\"\n\n{[F8673998](image.png), height = 400}\n\n\nExample of input node where **Input type** = Alembic\n{[F8674005](image.png), height = 400}\n\n---\n\n - Node: Delete\n - Type: Data flow\n\nDeletes vertices if attribute value in socket **Fac** is higher than 0.5. Avoid \"floating\" hairs where the root is missing.\n\n**Note on Fac**\nVisualisation of input mask. In a node tree this is represented by nodes of course (for example image texture)\n\n{[F8674022](image.png), height = 400}\n\n\n---\n\n - Node: Split\n - Type: Data flow\n\nSplits hair curves into two separate \"groups\". A hair curve can only belong to one group or the other (i.e. avoid hair curves that are split from root to tip)\n\n**Note on Fac**\nVisualisation of input mask. In a node tree this is represented by nodes of course (for example image texture)\n\n{[F8658118](image.png), height = 400}\n\n\n---\n\n - Node: Merge\n - Type: Data flow\n\nmerge two inputs of hair curves to one output. It would also be nice to allow merge for instanced geo\n\n{[F8658184](image.png), height = 400}\n\n---\n\n - Node: Switch\n - Type: Data flow\n\nHair 1 or 2 is selected as hair output via drop down menu. This could just as well be a slider, radio button etc\n\n{[F8658187](image.png), height = 400}\n\n---\n\n - Node: Hair curves output\n - Type: Data flow\n\nhair curves output to viewport and render. Multiple outputs can exist in the node graph, but only one can be active (just like in the shader editor)\n\n{[F8674220](image.png), height = 400}\n---\n\n - Node: Object output\n - Type: Data flow\n\nOutput node for instances (rocks, trees etc) and deformed instances (game hair, feathers). \n\nIMPORTANT: I would love developer input regarding if this is the best way to handle instances and deformed instances. \"Deformed instances\" might not be the best term, but I hope you understand what I mean.\n\n{[F8674235](image.png), height = 400}\n\n---\n\n## NODES - CREATE\n\n---\n\n - Node: Scatter hair\n - Type: Create\n\n**Influence radius (float)**\nControls of how wide radius the input hair controls the direction/interpolation of the output hair. It also scatter hair within the area of the input hair roots. Using this could turn the children=simple type of hair useless\n\n**Vertices (integer)**\nVertex count per hair curves\n\n**Relax iteration (integer)**\nRelaxes the distrubution of root vertecies. In the current implementation of hair, the distribution is pretty uneven. Possibly skip input if it complicates coding (eg if sampling from texture etc is hard to implement)\n\n**Density (float)**\nSets the density of the hair curves\n\n**Length (float)**\nLength shoud also be represented by an individual node. For simpler node networks it could be nice to have length included in the scatter hair node. Mostly because it's convenient.\n\n**Width (float)**\nSets the width of the hair curves\n\n{[F8674432](image.png), height = 400}\n\n---\n - Node: Resample\n - Type: Create\n\n**Vertex amount (upper drop down menu)**\n- Count\n - Amount of vertices per hair curve is decided depending on the value in the variable **Fac**\n- Length \n - Amount of vertices per hair curve is decided depending on distance in object space between each vertex/sample. Distance is set in the variable **Fac**\n\n**Fac**\nFloat value used for variable **vertex amount**. When **vertex amount** = Count, then round off to lower integer (eg floor(Fac))\n\n**Resample method**\nWhen upsampling a low res hair curve it is useful to have the result as a smooth curve. \n- Nurbs\n- Linear\n\n{[F8663697](image.png), height = 400}\n---\n - Node: Instance\n - Type: Create\n\n**Instance node socket (left side)**\nAccepts input node with type\n- Object\n- Collection content\n- Collection\n\n**Deform**\n- False: the instanced objects are not deformed\n- True: The instanced objects are deformed along the shape of each hair curve\n\n**Object up (1:st drop down menu)**\nDecides which axis (in object space) of the source object that should be treated as object up (pointing in the direction of the hair curve tip vertex)\n- +X\n- -X\n- +Y\n- -Y\n- +Z\n- -Z\n\n**Object front (2:nd drop down menu)**\nDecides which axis (in object space) of the source object that should be treated as object front. \n\n**Front aim vector (3:d drop down menu)**\nDecides which vector that \"Object front\" should aim. \n- Tangent (Cross product calculated from position of root vertex and second vertex)\n- +X\n- -X\n- +Y\n- -Y\n- +Z\n- -Z\n\n**Tilt**\n- If Deform = True: Rotate **per component (vertex)** along axis of vector between root and tip hair vertex. \n- If Deform = False: Rotate **per hair curve** along axis of vector between root and tip hair vertex. \n\nNOTE: The word \"Tilt\" is used, since it is already used for curves in Blender\n\nNon deforming example. Instanced objects up vector are aligned from root to tip. Used for trees, rocks etc\n{[F8674511](image.png), height = 400}\n\n\nDeforming example. Used for game hair, feathers etc\n{[F8674541](image.png), height = 400}\n\n\n---\n\n## NODES - DEFORM\n\n---\n\n - Node: Deform\n - Type: Create\n\n**Direction**\nAlong the direction of the hair (per segment/vertex)\n\n**Normal**\nInherited/Transfered from the growth mesh\n\nRead more about transferred normals from growth mesh to guide curves here #78606 (Hair object - design proposal)\n\n\n{[F8658219](image.png), height = 400}\n\n---\n\n - Node: Frizz\n - Type: Create\n\n{[F8658223](image.png), height = 400}\n\n---\n - Node: Rotate\n - Type: Deform\n\n\n{[F8658230](rotate_hair.gif), height = 200}\n{[F8658225](image.png), height = 400}\n\n---\n\n - Node: Curl\n - Type: Deform\n\n{[F8658233](image.png), height = 400}\n\n---\n\n - Node: Length\n - Type: Deform\n\nCut/Extend\nCut = shorter, extend = grow along vector between last two vertices at the tip\n\nScale\nScale per hair from hair root vertex\n\n{[F8658235](image.png), height = 400}\n\n---\n\n - Node: Clump\n - Type: Deform\n\n**Fac**\nAmount of clumping. The user can edit the attribute that is connected to this socket in order to clump more/less at the root/tip of the hair curves.\n\n**Frequency**\nThe primarily clump frequencey/size\n\n**Fractal iterations (integer)**\nCreating smaller (recursive) clumps per clump so that clumping does not look as uniform\n\n{[F8674575](image.png), height = 400}\n\n---\n\n\n - Node: Width\n - Type: Deform\n\nWidth is also controllable through the UI of the hair object (outside of node network) and act as a multiplier to the width inside of the node network. There should be separate width for viewport and render\n\n{[F8663656](image.png), height = 400}\n\n---\n\n - Node: Shrinkwrap\n - Type: Deform\n\nThis node is very useful for creating the look of wet hair\n\n**Object**\nShrinkwrap target. Collection or geometrical object. See the node **Input** in the **data flow** section\n\n**Fac**\nThe amount/blend of whrinkwrap deform\n\n{[F8674660](image.png), height = 400}\n\n\n---\n\n - Node: Smooth\n - Type: Deform\n\n**Smooth vector (upper drop down menu)**\n- Hair tip vector\n- Normal vector\n\n**Curve length (lower drop down menu)**\n- Keep length\n- Lock tip\n\n\nLower drop down menu\n\n**normal vector + keep length**\nIn this example the vector that the hair smooths/conforms to is the normal direction from the growth mesh surface. The length of the original hair curve is kept as it is smoothed\n{[F8663673](normal_vector___keep_length.gif), height = 200}\n\n**Hair tip vector + lock tip**\nIn this example the vector that the hair smooths/conforms to is the vector from the root to the tip of the hair curve (pre smooth). The length of the hair curve is shortened so that the tip of the hair stays in place. \n{[F8663674](Hair_tip_vector___lock_tip.gif), height = 200}\n\n**Iterations (integer)**\nSmoothing iterations\n\n{[F8674688](image.png), height = 400}\n\n---\n\n - Node: Simulation influence\n - Type: Deform?\n\nIMPORTANT: Update after feedback from @JacquesLucke. Feel free to give further feedback\n\nReference to a simulation network where the actual simulation happens. The simulation network simulates the hair and the new position per hair curve vertex is output from the right socket. It is useful to simulate a sparse set of hair curves and then use a **scatter hair** node after in order to generate more hair curves that are conformed to the shape of the sparse set of simulated hair curves.\n\n**Simulation network** (top drop down menu)\nLink to a node network with simulation setup\n\n{[F8674704](image.png), height = 400}\n\n---\n## NODES - ATTRIBUTE\n\nAttributes on hair objects are created in the hair object UI, much like vertex groups on mesh objects. Perhaps these attributes could be picked up during shading in the future? See #78606 (Hair object - design proposal) for more info\n\n---\n\n - Node: Object weight transfer\n - Type: Attribute\n\n**Input weight (top drop down menu)**\nGets value of vertex weight from input object(s). Useful for dynamic weights controlled by modifiers. Input can be a mesh object (see **Input** node in the *Data flow** section in this document. \n\n{[F8674777](image.png), height = 400}\n\n---\n\n\n - Node: UV transfer\n - Type: Attribute\n\nI've been thinking about how to solve multiple uv sets in conjunction with the generation of hair curves. This node is one solution and is rather flexible, since we can sample uv's from any object. Another route would be to decide that we only source the uv's from the growth mesh. Feel free to give input regarding what would be the easiest in terms of development/coding. \n\n{[F8674782](image.png), height = 400}\n\n---\n\n - Node: Hair root proximity\n - Type: Attribute\n\nThe hair root proximity node is very useful when scattering ground vegetation with the **Instance** node. The root mask can be used to make sure that bushes should not grow close to trees for instance.\n\n\n**Radius**\nThe radius in object space of the mask produced from each root vertex of the hair curves\n\n{[F8674896](image.png), height = 400}\n---\n\n - Node: Attribute get\n - Type: Attribute\n\nWhenever the user needs to remap an attribute (multiply, add, clamp etc) she/he can break out the attribute with an **attribute get** node, do operations and then use a **attribute set** node to write it to the hair curves later in the node graph\n\n{[F8674889](image.png), height = 400}\n\n---\n\n - Node: Attribute set\n - Type: Attribute\n\nWhenever the user needs to remap an attribute (multiply, add, clamp etc) she/he can break out the attribute with an **attribute get** node, do operations and then use a **attribute set** node to write it to the hair curves later in the node graph. Usually the attribute is used right after the node, so it's convenient with a ouput socket with Factor.\n\n{[F8679290](image.png), height = 400}\n\n---\n - Node: Geometry intersection\n - Type: Attribute\n\nNOTE: I will add further visual examples to how this works later\n\n**Position (Top drop down menu)**\n- Inside\n - Masks the hair curve vertices that positioned **inside** of the geometry object. \n- Outside\n - Masks the hair curve vertices that positioned **outside** of the geometry object.\n\n\n**Hair component(Bottom drop down menu)**\n- Root\n - For each hair curve: if hair curve root is positioned inside/outside (depending on the variable **Position**), all of the vertices per hair is masked\n- Vertex\n - For each hair curve: If a vertex is positioned inside/outside (depending on the variable **Position**), that vertex and all of the vertices with higher index number per hair curve (\"child vertices\") will get a value of 1 for the hair curve attribute that is specified in the node.\n\n{[F8674898](image.png), height = 400}\n\n---\n## USEFUL NODES FROM THE SHADING EDITOR\n\nAlmost all nodes in the shading editor would be very useful for creating masks for hair. It would be nice to reuse so the functionality is instantly recognized by the user. I need input from developers such as @sebbas if it's even possible to use existing nodes from shading editor.\n\nShading editor nodes is evaluated after the hair is deformed and we will likely want to evaluate these nodes BEFORE the final deformation of the hair. This could cause issues and I'm not sure it's possible to work around it somehow. Seems tedious to rewrite so many nodes.\n\nA lot of these nodes would require an object/geometry input socket in order to define the source (such as \n- Vertex Color\n- Attribute\n- Texture Coordinate\n\n{[F8663900](image.png), height = 700}\n\n\n" ]

[ "Crash - Blender crashes when applying hair from particle properties\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D300](D300) OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.91.0\n\nBlender crashes when I apply the hair particle to any object \n\n- Select any object\n- Click on particle properties\n- Add a particle system by clicking the + symbol\n- Click on hair ( blender crashes )\n\n\nPls see attached files\n\n[donut.blend](donut.blend)\n\n\n\n" ]

[ "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Trackpad scrolling is too sensitive in Text Editor\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.6.1\nWorked: never\n\n\nIf you scroll very slowly, nothing happens, deltas that give an offset of less than one line/character are simply discarded and not accumulated. The minimum possible scrolling is too fast, this jumps several lines at once and it's impossible to stop at the desired one.\n\nOne of the possible solutions can be seen here: D9552. This makes the scroll speed match the speed in other Blender editors, and other macOS applications as well.\n\nAnother solution could be to use a smooth scroll like with the MMB.\n\n", "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", "Grease Pencil Blur makes a tight white line beteween to diferent GP Objects.\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 516.94\n\nBroken: version: 3.6.0 Alpha\n\nWhen I use Blur effects on a GP object, it makes a tight white line between to different GP Objects. But, depends on which angle you look at, and this bug disappears.\n\n\njust added a blur effect on a grease pencil on render preview mod.\n\n", "Grease Pencil: Radius property misses blue slider background to visualize the percentage between soft min and max\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.81\n\nBroken: 2.80 -> 2.92.0 Alpha\nWorked: I believe it's been like this since initial GPencil implementation\n\nIn the GPencil editor the slider number button for \"Radius\" located in the topbar does not draw a percentage fill as is done in other editors such as Vertex Paint, Sculpt, Texture Paint and Weight Paint. \n\nStart blender with default settings\nAdd->Grease Pencil ->Blank\nSelect the Grease Pencil Object if not already selected\nSwitch from Object mode to Draw mode\nNote that the \"Radius\" topbar slider does not contain a fill color as does the \"Strength\" topbar slider \n\n[GreasePencilRadiusSliders.mov](GreasePencilRadiusSliders.mov)\n\nI've created [D9948](D9948) as a potential fix", "Ctrl+Click for Nurbs Surfaces\nWith Meshes and Curves, you can select a point, press Ctrl+LMB, and the point is extruded to the mouse.\n\nThis however does not work for Nurbs, even though you can extrude a point, Ctrl+LMB does not work.\n\nTry:\n- Add -> surface -> nurbs curve\n- Enter editmode\n- Select an end-point\n- Ctrl+Click... *nothing happens*\n\nThe same works for a curve or a mesh.\n\nThis could be split into 2 tasks\n- Get Ctrl+Click working for single nurbs curves.\n- Get Ctrl+Click working for nurbs surfaces (using the extrude code), This should extrude and place the newly extruded vertices at the mouse position, as is done with mesh data.", "Grease Pencil: Line Art › Light Contour causes crash\nOperating system: macOS-11.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.21\n\nBroken: version: 3.6.0 Alpha\nAlso reproduced with 3.5 and 3.4.1\n\nWhile using the Grease Pencil Line Art modifier, enabling the Light Contour feature causes a crash. The problem does not appear with a very simple scene, so a certain amount of geometry may be needed, hence the 6mb sample file. While trying to reproduce with smaller scenes, I sometimes had to toggle the Light Contour checkbox on and off a few times to trigger the crash, and the number of toggles actually varied from one launch to the next.\n\n1. Open provided file, GP crash.blend\n2. Select Grease Pencil object and expand its Line Art modifier\n3. Click Light Contour checkbox to enable it\n\nThis reliably causes a crash on my Intel Mac\n\n", "The Tool Selector Window close one time every two times, when opened too closed to the bottom border of the screen\nOperating system: Windows 10\nGraphics card: GTX 1080\n\nBroken: 2.80\nWorked: (optional)\n\nThe Tool Window, open and close immediately, choosing the tool under the mouse cursor, if the tool window is opened too close from the bottom of the screen.\n\n1) In Edit > Preferences > Keymap, set the \"Space Bar action\" to \"Tools\"\n2) On the 3D viewport, place your mouse cursor in the top area of the viewport\n3) press the spacebar, the tool menu open without any problem, and you can choose a tool with a shortcut key (for example press B to choose the Box selection)\n4) You can repeat that several times in a row without any problems.\n5) Now move your mouse cursor much more closer to the bottom border of the screen, so that you know that the tool window will have to be shifted upward to be displayed correctly.\n6) Press the spacebar a first time. This is ok, you can select your tool\n7) Now press the spacebar a second time. This time, the tool window open and intermediately closed, and the tool selected is the one that is under your mouse cursor.\n8) Press the spacebar again: the tool window open normally\n9) Press the spacebar again: the bug reappear\n10) Now on, every one time over two, the bug appear.\n\n**Expected behavior**\nThe Tool Window should open and stay opened consistently, no matter where the mouse cursor is placed on the screen, when the spacebar is pressed.", "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", "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).", "NLA: Active Strip State lost when dragging Strip between tracks\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: Never Worked\n\nClicking on a strip and dragging or G dragging the Strip on the timeline on the same Track and then hitting TAB to enter tweak mode is working, but if I do the same thing but drag it to another TRACK then hit TAB I get an error\n\nOpen my example Blend file and select the \"Click and Drag Me to the Drag Strip Here track\" STRIP and drag it to \"Click and Drag Me to the Drag Strip Here track\" then hit the TAB key to enter tweak mode, you should see an error as shown in the image. \n\"No active strip(s) to enter tweak mode on\n\"\n\n\n\n", "The tools panel suddenly disappears in engraving mode.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro K620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\n\nBroken: version: 2.93.0\n\n\n\n\nIn the engraving mode, use the blank key to call the tools panel may suddenly disappear.\n\nMy native language text↓↓↓↓\n\n在雕刻模式，使用空白鍵呼叫　tools 面板會有突然消失的可能。\n\n\n\n\n\n1. Set KeyMap>Spacebar Action>Tools\n2. Select any object and enter sculpt mode.\n3. Press the blank key to call the tools panel. At this time, the panel will suddenly disappear. (Error generation)\n4. Move the mouse arbitrarily\n5. Press the space button again to call the tools panel. At this time, the panel will suddenly disappear. (Error occurs again)\n\nOther additional tests:\n\n1. The panel disappears (when an error occurs), do not move the mouse, press the blank key again, and it will appear normally\n\n2. When it appears normally, as long as you move the mouse and press the blank key, an error will occur, but there is one exception, which is simply moving the mouse horizontally so that the panel appears in the second position, the selected brush and slide The overlapping position of the mouse is exactly the same as the last time, the error will not occur (image)\n\n3. In the object mode, everything is normal, I think it should be operated like the object mode.\n\nMy native language text↓↓↓↓\n\n1.設定 KeyMap >Spacebar Action>Tools\n2.選擇任意物體，進入sculpt模式。\n3.按空白鍵呼叫tools面板。這時候面板會突然消失。(錯誤產生)\n4.任意移動滑鼠\n5.再次按空白鍵呼叫tools面板。這時候面板會突然消失。(再次錯誤產生)\n\n其他額外測試 :\n\n1.面板消失(錯誤產生時)，滑鼠不要動，再按一次空白鍵，就可以正常出現\n\n2.當正常出現後，只要有移動滑鼠，再按空白鍵就會發生錯誤，但有一個時候例外，就是單純水平移動滑鼠，讓第二個位置出現面板時，選取的筆刷與滑鼠重疊的位置和上一次一模一樣，錯誤就不會發生 (圖片)\n\n3.在物體模式，一切正常，我認為應該操作起來要像物體模式這樣。\n\n\n\n", "Info log popup on the status bar displays large messages incorrectly\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.0\nWorked: Probably never\n\n\nWhen a large report is submitted to the info log, the pop-up message indicator displays an enormous empty space. Ideally, this should display a truncated amount of text from the first line of the report.\n\n\n\nIn addition, it appears as though it is attempting to display the newline (`\\n`) character (I wrote out `\"Foo\\nBar\"` to the log).\n\n\n\n[lorum.mp4](lorum.mp4)\n[infobug.blend](infobug.blend)", "Problem with stop animation when View Viewport Render Animation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.17\n\nBroken: version: 3.5.0\n\nThere is big gap and Problem with **stop** animation when View -> Viewport Render Animation is started in blender, eg. when it's selected accidentally and as alternative to View -> Viewport Render Image.\n\nTry to stop this animation. By me when I made this mistake not found solution other by kill blender process, cos stop button not was available or \"x\" btn like render (in case render view updating each image on Evee rendering process).\nNo imagine some big project and situation that user must waiting to finish, and he is not sure about saved file and blender is hanged due this process.\n\n", "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" ]

[ "Regression: Annotation lines doesn't start where clicked\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\nI'm using a Wacom tablet but also happens with mouse, just to a lesser extent for some reason.\n\nBroken: version: 3.2.0\nWorked: 3.1\n\nLooks like this is caused by b8960267dd\n\nwhenever I try drawing a line with the annotate tool or in grease pencil draw mode, the first end of the line never starts on the place I click.\n\nwith annotate line tool selected, try to draw a line from one point to another, the line won't start appearing right away and leaves a gap.\n\n[2022-07-03-09-21-46_Trim.mp4](2022-07-03-09-21-46_Trim.mp4)" ]

[ "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", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "gpu module in CustomRenderEngine causes segfault\nOperating system: Linux-5.4.2-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.7\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nUsing gpu module in CustomRenderEngine render function causes segfault\n\n- Open attached blendfile\n- Run the python script from text editor\n - it is based on the example bpy.types.RenderEngine.html\n - only difference is, importing gpu module and doing a gpu.matrix.push_pop() in the render function\n - also added faulthandler to see where it crashes\n- change render engine to custom\n- hit f12 (blender crashes)\n\nIs the GPU module not suited for use in CustomRenderEngine ?\nAlso testet drawing a gpu.types.GPUBatch to a framebuffer object without doing matrix.push_pop(), it also caused a segfault. The matrix thing is just the simplest case to reproduce.\n\n[CustomRenderBug.blend](CustomRenderBug.blend)\n\n", "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", "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", "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", "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", "Blender Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\nOperating system: Windows 10 - 22H2\nGraphics card: 3090ti 31.0.15.3667\n\nBroken: (3.5, 3.5.1, 3.6.1)\nWorked: None\n\nBlender Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\n\nI have a volumetric setup in the scene. To show up as haze on the horizon. Error only occurs when Volumetric is active.\n\nEnsure the WorldSphere is enabled for render and just render animation for 1279. \nIt will do 1 - 10 frames before throws the error attached. \n\nFile is too big for the attacher, please get blend file from google drive link.\n\nview?usp=drive_link\n\nSimplified: view?usp=drive_link\n\n", "gpu.types.GPUOffScreen together with gpu.state.depth_test_set causes blender ui to be unresponsive\n(reporting from different os, those are copied from system-info.txt generated by blender)\nOperating system: Windows-10-10.0.19043-SP0\nGraphics card: GeForce GTX 760/PCIe/SSE2, 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: cc66d1020c3b, type: release\nWorked: ?\n\n`gpu.types.GPUOffScreen` together with `gpu.state.depth_test_set` causes blender ui to be unresponsive, nothing can be clicked, blender have to be killed. if `gpu.state.depth_test_set` is set to `'NONE'` after drawing is finished, problem goes away. this happens on windows, on mac it works.\n\nexample code is from: gpu.html#copy-offscreen-rendering-result-back-to-ram with marked modifications\n\n- Open text editor in default scene\n- Paste and run the attached code\n```\nimport bpy\nimport gpu\nimport random\nfrom mathutils import Matrix\nfrom gpu_extras.presets import draw_circle_2d\n\nIMAGE_NAME = \"Generated Image\"\nWIDTH = 512\nHEIGHT = 512\nRING_AMOUNT = 10\n\n\noffscreen = gpu.types.GPUOffScreen(WIDTH, HEIGHT)\n\nwith offscreen.bind():\n fb = gpu.state.active_framebuffer_get()\n fb.clear(color=(0.0, 0.0, 0.0, 0.0))\n \n # one line added here ----------------------------------------------------\n gpu.state.depth_test_set('LESS_EQUAL')\n # ------------------------------------------------------------------------\n\n with gpu.matrix.push_pop():\n # reset matrices -> use normalized device coordinates [-1, 1]\n gpu.matrix.load_matrix(Matrix.Identity(4))\n gpu.matrix.load_projection_matrix(Matrix.Identity(4))\n\n for i in range(RING_AMOUNT):\n draw_circle_2d(\n (random.uniform(-1, 1), random.uniform(-1, 1)),\n (1, 1, 1, 1), random.uniform(0.1, 1),\n segments=20,\n )\n \n - and one line here ------------------------------------------------------\n - gpu.state.depth_test_set('NONE')\n # ------------------------------------------------------------------------\n\n buffer = fb.read_color(0, 0, WIDTH, HEIGHT, 4, 0, 'UBYTE')\n\noffscreen.free()\n\n\nif not IMAGE_NAME in bpy.data.images:\n bpy.data.images.new(IMAGE_NAME, WIDTH, HEIGHT)\nimage = bpy.data.images[IMAGE_NAME]\nimage.scale(WIDTH, HEIGHT)\n\nbuffer.dimensions = WIDTH * HEIGHT * 4\nimage.pixels = [v / 255 for v in buffer]\n```\n\n", "Cycles GPU/CPU render difference with more than 64 transparent bounces and coplanar faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\n\n\nWhen using particle plane with transparency ( to fake volume scatter ), we have a color mismatch between CPU and GPU rendering. \n\n\n see attach file\n\n\n\n[cpu_gpu_issue.blend](cpu_gpu_issue.blend)\n \n", "Edge quality of uv export\nWindows 10\nGtx 1060\n\nBlender 2.8 - February 28 ( d7d180bd3d8d )\n\ndifference looks huge between blender 2.79 and blender 2.8\n\nPlease note: check image in full view.\n\n\n\n\n\nthanks.", "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "Crash on Mac when starting with `--debug-gpu` flag\nOperating system: Mac OS Ventura 13.1\nGraphics card: Apple M1 Max\n[system-info.txt](system-info.txt)\n\nBroken: 3.4.1\nWorked: 3.3.2\n\nBlender won't start on a Mac when starting with `--debug-gpu` flag.\nThe terminal output is this:\n\n```\n/Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\nRead prefs: /Users/vollstock/Library/Application Support/Blender/3.4/config/userpref.blend\nWARN (gpu.debug): source/blender/gpu/opengl/gl_debug.cc:165 init_gl_callbacks: Failed to hook OpenGL debug callback. Use fallback debug layer.\nzsh: segmentation fault /Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\n```\n\n\nStart with the flag\n\n```\n/Applications/Blender.app/Contents/MacOS/Blender --debug-gpu\n```", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n" ]

[ "Error with GTX 750 Ti Cycles not working\nMAC OS SIERA 10.12.1\nNvididia driver .367.15.10.15.f03\nCUDA drivers 8.0.63\n\nBroken: 2.78b\nWorked: 2.78a\n\nCycles not running always get errors on GPU GTX 750ti. On All previous versions of blender it worked like charm. CPU rendering ok, but GPU no\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Multiresolution sculpting broken after change in base geometry\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.1.2 30.0.14023.3004\n\nBroken: version: 3.1.0 Beta\n\nThe file was created at 3.1.0, but the model in 3.0.1 also has the same problem.\n\nafter deleting edges from a loop and recreating them in a different arrangement, some parts of the model cannot be sculpted with multiresolution on.\n\n\nIn a model with multiresolution, I deleted and recreated some edges of the topology and this broke the sculpt mode of the multiresolution: \n- In the sculpt mode, whenever I was getting close from the model, it simply dissappeared, reapearing after zooming out.\n- When hovering the mouse over some areas of the model, doesn't change the brush gizmo, and I can't sculpt on those areas neither.\n- If there is a area that you can interact/sculpting, by doing it the areas that you were unable to sculpt will become sculptable again.\n- In the areas that you can sculpt, the brush gizmo rotation doesn't match the surface sometimes.\n- baking normals from this multiresolution causes blender to crash\n\nI splited the model in some parts trying to remove the defective part, but this only changed the areas the bug was occuring, and I also tried to re-sort the vertices of the model, which had the same effect\n\nIn this video, the upper part of the leg is sculptable, but the rest of the leg is not \n[2022-02-06 14-33-33.mp4](2022-02-06_14-33-33.mp4)\n\nThis model is from a commission so I had to fair the upper part of it\n[broken multires.blend](broken_multires.blend)\n\n", "Curves don't have 'All Edges' option for wireframe\nBroken: 2.80\n\nMesh objects have the toggle for its viewport display wireframe to render all edges, but curve objects don't.\n\n\nOpen the attached file and look for the 'All Edges' option.\n[Wiref.blend](Wiref.blend)\n", "Generated Texture Coordinate Node In Shader Creates Broken Pattern Upon Applying Subdivision After Armature Modifier \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.1\nWorked: Blender 3.2\n\nWhen I use the Generated value of a Texture Coordinate node, and have a modifier stack with an Armature above and a Subdivision below, it creates a really weird result [broke.blend](broke.blend)\n\n\n - Check the .blend file and simply activate the Subdivision modifier on the model\n\n\n\n\n", "Alembic Instances are Duplicates instead of References\nWhen importing alembic files, Blender creates duplicates of the geometry data instead of references. Additionally, each instance is an object instead of a dupli group which would consume far less memory?\nAlembic is outputted from Houdini. [pigs_packedTransforms.abc](pigs_packedTransforms.abc)\n\nThis behaviour is exhibited by 2.79rc2. ", "Sculpt: mask cut and fill can`t hold tubes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\nBug or limitation/flaw?\n[untitled.blend](untitled.blend)\n[2020-01-17_19-12-26.mp4](2020-01-17_19-12-26.mp4)", "\"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", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "Particle Instance from interpolated children works unexpected\nOperating system: win10 74bit\n\nBroken: 2.8, 2.79b\n\n\"Children\" option works good only with \"Along path\". Otherwise it just duplicates extra geometry where parent particles are located. \n\nOpen file and enable \"Children\" option, see how poly count is changed without visual appearance. Then check both \"Children\" and \"Along Path\" to see the difference.\n[Particle_instance_child.blend](Particle_instance_child.blend)", "Joining curves overrides other materials\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.92.0\n\nJoining two or more curve objects together will result in the curves being assigned the active object's material rather than keeping the material assigned to their points. \n\nOpen the below file:\n[curve_material_bug.blend](curve_material_bug.blend)\nUse Ctrl+J to join the two curves together. \n\n", "Unique generic attribute names can break armature binding process\nOperating system: N/A\nGraphics card: N/A\n\nBroken: Current main (48950ff934de4)\nWorked: 3.6 (before extending unique names to vgroup as 'virtual' part of generic attributes)\n\nRelated to/caused by !109910.\n\nParenting (binding) a mesh to an armature is broken if other existing generic attributes are already using some of the bones' names.\n\nSee also 31073\n\nStarting with default cube from default startup file:\n\n1. Add (or rename) a generic attribute to `Bone` (e.g. a UVMap).\n2. Create a default, one bone armature.\n3. Parent the cube to the armature, with one of the vgroup creation options (e.g. automatic weights).\n4. The newly created vgroup is named `Bone.001`, and the bone does not deform the cube object at all.\n\nFinal result: [armature_bones_generic_attributes_name_collision.blend](attachment)\n\n--------------------\n\nNote: this is a very dumb, but also very good example of the kind of issues that name uniqueness is going to cause in existing code and workflows.\n\n", "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", "Outliner selection not working correctly after undoing object deletion\nOperating system: Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (LLVM 13.0.1, DRM 2.50, 5.17.15-1-MANJARO) AMD 4.5 (Core Profile) Mesa 22.1.2\n\nBroken: 2.91.2, 3.2.0, version: 3.3.0 Alpha\nWorked: prior to b077de086e\n\nAn object that is linked in another collection can usually be removed from just that collection by using unlink, while using delete removes it from both collections. But if you delete the object and undo, unlink does delete the object in both collections. \nRenaming the cube or creating a new object \"breaks\" the cubes apart so they can be selected/unlinked individually again.\n\nIn the default scene,\n- create a new collection\n- in the outliner, ctrl-drag the default cube object to that collection to link it\n- delete the cube\n- undo\n- in the outliner, it is now impossible to select the cube in the new collection separately and using unlink will delete both cubes", "Unlinked/deleted objects reappear, when deleted at startup in a python script (i.e. ./blender --python delete.py)\nDebian 7.4 64bit, also occurs on OSX\n\nBroken: 2.63, 2.69.0\n\n\nUnder certain conditions objects which have been unlinked from a scene do reappear.\n\n\n\n\n - Start blender with `./blender --python delete.py` (see below for the script) (blender just shows an empty scene)\n - Once the GUI is loaded, do: **Add -> Mesh -> Plane**\n # Immediately afterwards hit **F6** and adjust one Property of the newly added object (e.g. the radius)\n\nResult: the objects from the start scene (camera, lamp, cube) reappear.\n\n**Doesn't occur when...**\n - ... A second Mesh is inserted before hitting **F6** to change its properties\n - ... The script is executed in the Blender Editor (and not at startup with option `--python`)\n\n\n**Python script `delete.py`**\n\t\n\n\n\n```\n import bpy\n \n```\n - IMPORTANT: run as: ./blender --python delete.py\n - once blender started, here is what I did in Blender GUI:\n - - add a new mesh (Add -> Mesh -> Plane)\n - - Hit F6 immediately afterwards and modify radius\n # Result: Blender start scene (cube, light & camera) is visible again\n```\n \n```\n # the described bahaviour and result is the same for deleteScene1() - deleteScene3()\n```\n \n def deleteScene1():\n bpy.ops.object.select_all(action='SELECT')\n bpy.ops.object.delete()\n \n def deleteScene2():\n bpy.ops.object.select_by_type(type='MESH')\n bpy.ops.object.delete()\n bpy.ops.object.select_by_type(type='LAMP')\n bpy.ops.object.delete()\n bpy.ops.object.select_by_type(type='CAMERA')\n bpy.ops.object.delete()\n \n def deleteScene3():\n scn = bpy.context.scene\n for obj in scn.objects:\n scn.objects.unlink(obj)\n \n```\n - deleteScene1()\n - deleteScene2()\n```\n deleteScene3()\n\n```\n\n\n\n", "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", "Remove unavailable sockets and links\nYes. Finally, hiding some interface elements will not have business functionality and a bunch of complications in the code.\n\n**More about the problem:**\nThe hide (in interface) and unavailable (for processing) sockets is now used to hide the visible (used) list of sockets.\nThis has consequences:\n1. All sockets exist all the time.\n2. Links to them still exist.\n3. It is not possible to create new sockets without code complexity (previously, for node groups new sockets are created manually in some code places).\nAnd this brings a lot of complexity to the code.\nJust examples: [D16784](D16784), [D16772](D16772), 2b4cb893e7, ...\nAnd trubbls for python users: #103395 (Node: Incorrect node socket indexing when connecting with python)\n\n**The main task:**\nAt the moment, this problem can be solved in several parts :\n1. Different sockets for different node configurations:\n a. Group nodes create their sockets based on node tree declaration: [D16850](D16850).\n b. Individual nodes create a statically assigned set of sockets depending on the state of the node: [D17081](D17081).\n c. Nodes for working with multiple data layers (shaders, compositor): based on scene data or some other data. There may be subtleties here. Example task: #70802.\n d. Physics Nodes: Based on what data should be stored in the simulation.\n2. Support for multiple types on a socket as generic socket type:\n a. Argument list of supported types for socket declaration.\n c. Type of socket declaration, that mean evaluation-time type of socket based on context (similar to template node groups)\n\nAlso, since the constant deletion and creation of sockets has its consequences, some behavior needs to be recreated. Now it will have more control, which in theory should improve usability:\n1. Simulating data storage for a temporarily remote socket [D17136](D17136) :\n a. It is possible to store data of node group sockets.\n b. Value conversions when changing the group socket type.\n2. Handling implicitly deleted links for their possible return to their original place.\n\n**Code cleanups:**\n1. The result of a complete switching to explicit processing of real sockets may be the complete removal of visibility flags for sockets. Or at least move them to the category of deprecated.\n2. As well as the complete removal of the code that processes them." ]

[ "Proxy controls break when appending in scenes to new file\nWindows 7 Home Premium X64 service pack 1\nIntel i7 920 @ 2.67 Ghz\n9 GB ram\nNvidia GeForce GTX 760 4 GB ram driver version 340.52 directX11\n\nBroken: 2.75a c27589e date: 2015-07-07 14:56 and 2.76b f337fea date: 2015-11-03 10:56\nWorked: 2.74 000dfc0 date: 2015-03-31 13:39\n\n**Proxy controls break when appending in scenes to new file**\n\nSteps\nAttached zip file is a basic rigged prop consisting of 1 cube, an armature with one bone named ctl.god.c and a circle representing the bone shape. All in a group named grp.name\n\nPreparation\n\n - In a fresh blend file name a scene shot.001\n - Link in the grp.name group from the zip file\n - Create a proxy of ctl.god.c\n - Create a second scene file with option \"link object data\". Call this scene shot.002\n - Create a UV_sphere, select it and create a group called grp.ball\n - You should now have a file with 2 scenes ( shots )and two groups. Both scenes have the cube rig linked in , shot.002 has a ball that is in grp.ball\n # Save the file as test_master_shot_2.74.blend\n\n( Old behavior ) Create a fresh file in blender 2.74 \n\n - Append in scene \"shot.001\" & \"shot.002\". This should bring in the group grp.name with the scenes.\n - In shot.001 , grab the ctl.god.c control and move it in pose mode. The armature should work as expected. Hit control Z and it should go back to origin.\n # Go to shot.002, Notice there is no grp.ball group. Group is missing from append ( This is a problem going back to version 2.74 at least )\n\n( New Broken Behavior ) Create a fresh blend file in blender 2.75a or 2.76b \n\n - Repeat previous append steps from version 2.74\n - In these versions of blender you get a double of the proxy controls when you move the ctl.god.c control in pose mode\n # Hitting control Z to undo movement completely breaks the control leaving two versions. This seems to be a problem with appended scenes \n\nAlso notice the grp.ball group is still missing from the appended file. It also doesn't seem to matter if you build the test_master_shot_2.74.blend file in 2.75a od 2.76b. It still breaks. \n\n\n\n" ]

[ "With enabled Modifier On Cage option crashes on entering Edit Mode if in Render Viewport Shading\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nIn Eevee, in Render Viewport Shading, an object having a Geometry Nodes modifier with enabled On Cage Modifier Result, that affects a UV Attribute which is used in Shader, crashes upon entering Edit Mode.\n\n - Set Viewport Shading Mode to Render\n - Enter Edit Mode ->Crash\n[displace-preview.blend](displace-preview.blend)", "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", "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", "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.", "Applying Skin Modifier to square loop object and in edit mode braking the loop makes prob\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: AMD Radeon HD 8400 / R3 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1065.0\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nSkin modifier disturbs the geometry form one corner on braking the loop form one corner of closed loop (of square shape). Although in this case the angles are 90% but it's will make prob...\n\n\n\n\n", "The time limit isn't working when rendering multiple tiles.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.0.0 Alpha\nWorked:\n\nThe time limit isn't working when rendering. \nHere are my settings \n\n\nEnable time limit and render an image\n\n\n\n", "Modifier are still evaluated even when not required.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.0.0\nWorked: never\n\nModifiers are evaluated, even when blank, for example a lattice modifier without any lattice, would still make depth graph calculation or something like that, that make each action (select, move, rotate, etc.) verry slower.\n\nCreate/ import a large object (60M poly mesh for example).\nAdd lattice modifier, let all option blank. \nDisable viewport visibility of this modifier.\nTry to move/rotate/scale the object in the viewport, the performance is really low.\n\nIn order to transform your mesh, you need to remove all modifiers, and add then back once transform is convenient.\n", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "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", "Blender continuosly freezes when transforming an object\nOperating system: Ubuntu 20.04.4 LTS\nGraphics card: ntel Corporation Skylake GT2 [HD Graphics 520] (rev 07)\n\nBroken: 3.1.2\n\n\nBlender continuosly freezes when transforming an object.\n\nCreate a General project (With the default cube). Scale the cube in every direction. Continue doing this and it the app will freeze. The debug log is filled with the following message:\n\n\n> INFO (gpu.debug): Notification : memory mapping a busy \"miptree\" BO stalled and took 0.039 ms.\n\n\n\n\n", "Bevel modifier with many segments sometimes generates spikes\nOperating system: Linux-5.3.0-53-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.8\n\nBroken: version: 2.83.0\n\nif a bevel modifier and a mirror modifier are added to an object,\na render error appears only in the mirrored object, depending on the number of bevel segments chosen.\nin the file appended, the glitch disappears as soon as the bevel modifier is applied.\n\n- Open attached file\n- increase or decrease the number of bevel segments until the error occurs.\nIt should be visible in the attached .blend file (the spike)\n\n[bevel_spikes.blend](bevel_spikes.blend)\n\n", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "Non animatable properties\nBroken: version: 3.3.0 Alpha\n\nWorking on refreshing the in-built AnimAll addon by adding the latest properties supported in Blender.\n@ideasman42 asked me to file a task\n\nCertain properties are missing animation capabilities:\n\n - Lattice Vertex Groups\n - Mesh Vertex Creases", "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", "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!" ]

[ "Blender 3.1 Crash; Ico Sphere\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070\n\n**Blender Version** 3.1\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n**Short description of error** When I \n\n**Exact steps for others to reproduce the error** When I subdivide and ico sphere, Blender freezes for 8 - 1- seconds. Then when I try to add a Subdivide Surface modifier, Blender freezes and shuts down.\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Rendering: Engine specific passes show up in other render engines render result\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: Blender 2.83.18, Blender 2.93.6, Blender 3.2.1, Blender 3.4\n\nPasses that were enabled for Cycles show up for eevee/workbench even if they should not.\n\n1. Fresh start-up\n2. Switch to Cycles\n3. Enable all render passes\n4. Switch to Eevee/Workbench\n5. Disable all render passes except `Combined`\n6. Render the image\n7. Notice `Vector`, `Position`, `UV`, etc. in the Pass dropdown\n\nAlternative:\n1. Fresh start-up\n2. Enable all render passes\n3. Switch to Workbench\n4. Render the image\n5. Notice `Vector`, `Position`, `UV`, etc. in the Pass dropdown\n\n[T100319_eevee.blend](T100319_eevee.blend)\n\n[T100319_workbench.blend](T100319_workbench.blend)\n", "Some particles are not being rendered during the first render\nOperating system: Windows 10\nGraphics card: I tried on two different computers with different GPUs - Nvidia RTX3070 and Mobile Nvidia RTX2060, same behaviour.\n\nBroken: 2.93.6, 3.0.0 Release Candidate, 3.1.0 Alpha\n\n\nBlender is not rendering some particles (in my case this is a grass) during the first render.\nIt does after re-rendering the scene, but this is quite confusing and inconvenient, especially in the moments when I have to resume render of animation.\nApparently this only happens when we add a force field to control the particles.\n\nOn top of this, 3x does not render trees (particles).\n\nOpen the blend file and press F12 to render. You should have similar result as on the screenshot:\n\n\n\nRender again, and the grass will appear:\n\n\n\nI attach results also from 3.0:\n\n\n\n\n\nand 3.1:\n\n\n\n\n\n- Open attached file\n- Render (F12) - See the particles issue\n- Render again - Now it is ok\n\n[turbulence_particle_eevee_bug.blend](turbulence_particle_eevee_bug.blend)\n\n---\nOriginal File:\nBecause file is big (260M) I have decided to share the link: view?usp=sharing <- if you would prefer me to upload it anyway here, please just let me know.", "Motion blur artifacts on certain frames EEVEE\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nMotion blur on error appears on same certain frames.\n\nblend attached Error appears on frames : 49 , 60, 85, 95, 103, 119,130\n\n[blur test.blend](blur_test.blend)\nnormal frame \n\nerror frame \n\nvideo with error frames [0001-0300.mp4](0001-0300.mp4)\n\n", "Sculpting using EEVEE\nThis keeps track of the patches and tasks needed for improving sculpting with EEVEE/Lookdev enabled\n\n[D8558](D8558) Fix EEVEE not using the PBVH for rendering in Sculpt Mode\n[D8564](D8564) Sculpt: Use Simplified Materials option\n[D8566](D8566) LookDev: Lock HDRI rotation to View", "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", "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", "Baking vertex colors does not respect alpha with \"Diffuse\" selected but respects alpha with \"Direct + Indirect\" also selected\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.2.1\n\nI believe this is a bug: when baking vertex colors, the alpha channel is included ONLY if \"Direct + Indirect + Color\" are all enabled, but then lighting gets baked in as well which is often not intended.\nThis leads to the situation that It doesn't look like there's a way right now to bake just color + alpha to a Color Attribute with alpha channel.\n\n- open the attached blend file: [BugDiffuseAlphaVertexBake.blend](BugDiffuseAlphaVertexBake.blend)\n- select the Cube\n- switch viewport to Eevee\n- make sure Render Engine is set to Cycles so things can be baked\n- in the Bake tab, click \"Bake\" with Bake Type=Diffuse and Contributions=[Color]\n- note the result doesn't have an alpha channel in vertex colors, it's just black\n\n- now, enable \"Direct\" + \"Indirect\" and Bake again\n- note the result has aloha channel BUT now looks incorrect as only diffuse was intended to be baked...\n\n\n- also note that neither \"Color + Direct\" nor \"Color + Indirect\" result in an alpha channel\n- both \"Direct\" only and \"Indirect\" only result in alpha channels but then the color can't be baked.", "Shader to RGB node is ignoring shading and just using color socket data directly\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.4\n\n\nIf you have a Shader that is converted with the Shader to RGB node, and then the resulting Color is plugged into another shader node and rendered, the output of Eevee's Color pass for that shader shows color plugged to socket of shader that is converted to RGB. In example file it is pure white, when you would expect to see the converted shader to RGB.\n\nProblem exists with Diffuse, Glossy, and Emission shaders and passes with the exception that an Emission converted to RGB going into another Emission will show up properly in the emission pass.\n\nSee Node graph in attached image, or attached file.\n\n\n[shader_to_rgb_eevee_pass.blend](shader_to_rgb_eevee_pass.blend)", "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", "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", "3D Texturing: Limit Eevee samples to 1 during paint stroke.\nGhosting effects appear when painting. We should limit the number of samples to improve the performance and reduce the ghosting effect.", "Cycles: Tex Coord node plugged directly in a world shader does not affect diffuse rays\nI tested and it's not supported in 2.79 so this maybe a corner case that has long been standing.\n\nThis happens also in final render.\n\n[cycles_diffuse_ray_issue.blend](cycles_diffuse_ray_issue.blend) \n- Open given file and switch to rendered view.\n- Connect the 2nd checker color socket to another of the dysfunctional texco socket.\n- Only glossy rays can now see the texco of the environment.\n\nThe issue seems to happen if the coordinate is plugged straight to the background or emission node. If the output is mixed it does work (default state of the file).\n\nMixed, working:\n\n\nNot mixed, broken:\n", "Slow EEVEE timeline scrubbing when using Scene World material\nOperating system: Arch Linux\nGraphics card: Intel UHD 620 (`iris` with `INTEL_DEBUG=reemit`)\n\nBroken: `0781c22ceedc`, `2.90`\nWorked: \n\n\nScrubbing through the timeline on an empty scene is slow when viewing through EEVEE and Scene World enabled, even though the node graph for it is a simple Background Shader node.\n\nThis also happens when *nothing* is connected to World's material output.\n\n[slow_scrub.mp4](slow_scrub.mp4)\n\nYou can see in the first part of the video, when using LookDev and have Scene World disabled, the scrubbing is relatively fluid and very close to the cursor. After enabling Scene World you can see that the scrubbing is lagging behind the cursor.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Create a new scene\n2. Delete everything (not really necessary)\n3. Try scrubbing the timeline without Scene World in LookDev\n4. Try scrubbing the timeline *with* Scene World in LookDev\n5. Notice that the latter is less responsive\n\n**Note**\n\nI have only experienced this on this GPU (probably due to its low-performance), however I still feel this is a weird bug.", "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", "Blender crashes with Noise Texture Node + Hair Particle System + Eevee\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 480 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: 8dc95f61f3\nBroken: version: 2.92.0\nBroken: version: 2.91.2\nWorked: version: 2.83.12\n\nBlender 2.92 with AMD crashes with **Noise Texture Node**and **Hair Particle System** with render engine Eevee.\nWith Blender 2.91.2 with AMD it doesn't crash but colors are incorrect.\n\nWith 8dc95f61f3 with Intel GPU, there's no crash but colors are incorrect in the same way as in AMD - 2.91.2.\n\n1. Open attached .blend file\n2. Viewport shading to: Render \n3. Play animation by tapping space bar\n\n[particle_loop.blend](particle_loop.blend)\n[blender_2_92_crash.txt](blender_2_92_crash.txt)\n\n**Blender 2.92**\n[blender_2_92.mp4](blender_2_92.mp4)\n\n**Blender 2.91**\n[blender_2_91_2.mp4](blender_2_91_2.mp4)\n\n**Blender 2.83.12**\n[blender_2_83_12.mp4](blender_2_83_12.mp4)" ]

[ "All Lights Are Green In Eevee, Fine In Cycles.\n\nOperating system: Ubuntu Linux\n\n\nBroken: Blender 2.81\n\n\nWhen I add lighting to a scene, all lights are green. This is in the Eevee render engine. The lights work fine in Cycles though.\n\n\n\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.", "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)", "Outliner: Sorting not working for some types in Scene display mode\nBroken: Current master\nWorked: Never\n\n\nSorting elements in the outliner only works for objects. Scenes, collections, and other types are not sorted.\n\n<img src=\"https://projects.blender.orgattachment\">", " Alpha channel of Tint Modifier don't Work with Fill material but work with stroke material.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nhi, it's been a while i didn't make a report for a bug, :) , well i'm back.\nthe Tint Modifier work well with `Stroke `material for every color channel R,G,B,A , but for Fill material we have problem with Alpha channel that don't work at all.\nthe first video show stroke works well with ALpha channel :\n[2022-10-16 13-12-36.mp4](2022-10-16_13-12-36.mp4)\nthe file\n[aplha color of tint modifier work well with stroke material.blend](aplha_color_of_tint_modifier_work_well_with_stroke_material.blend)\nsecont video show the problem with FILL material and alpha channel:\n[2022-10-16 13-14-27.mp4](2022-10-16_13-14-27.mp4)\nthe file\n[aplha color of tint modifier don't work with fill material.blend](aplha_color_of_tint_modifier_don_t_work_with_fill_material.blend)\nhope to get fixed.thank you for reading it\n\n", "Object Info node random output doesn't work properly\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13399 Core Profile Context 0\n\nBroken: version: 3.6.2\nWorked:\n\n**Short description of error and steps for others to reproduce the error**\nI have a scene with many collection instances of a collection containing a car and its wheels. The car has a material on it with its base color being controlled by an object info node's random output:\n[![enter image description here][1]][1]\n\nEverything looks good as long as I am in material preview with the overlays turned off:\n[![enter image description here][2]][2]\n\nBut with the overlays turned on(or sometimes the other way around) or if rendered using the EEVEE render engine, all the cars will have the same color.\n[![enter image description here][3]][3]\n\nHere is the .blend file:\n4whyzTYK#LYLMOGpAT3VvUi4j73Jg63W2p8sG_HRQ8L3E_A107z0\n\n [1]: Api9y.png\n [2]: XZ0Gz.png\n [3]: OeeZJ.jpg\n\n", "When changing the node type in material, sockets of different node types are reused\nOperating system: MacOS\nGraphics card: Apple M1\n\nBroken: main\nWorked: don't know\n\nShader nodes that have the same input sockets can have different default values.\nBut if you switch between shader nodes in the material interface, then the default values will first of all be copied from pre-existing socket of a node of a different type. Because of this, default values may not be used and may look strange.\n\nIn the default scene, assign Glass BSDF material to the default cube, and check the \"Roughness\" field. Now assign another material without \"Roughness\", such as Hair BSDF, then assign Glass BSDF material again and check the \"Roughness\" field.\n\n", "The Hair Particles interprets the color from the newer vertex domain and float color types wrong\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.0\n\nI am trying to modify hair color using color attribute (called as vertex color in previous versions). But hair particles simply ignores the color attribute. I just plugged in a musgrave texture and that works as expected but color attribute does not. I have attached a screenshot for a better understanding.\n\n\n\n\n", "Shader Image Mapping Issue\nOperating system: Mac OSX High Sierra\nGraphics card: NVIDiA GeForce\n\nBroken: (example: 2.92 Master 02948a2cab44\nWorked: N/A\n\nIt seems the mapped image is not applying to an object that's linked by Object Data\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[repro2.blend](repro2.blend)\n\nIn this file, just going in and out of editmode causes the the (rendered) UVs to not be consistent (they appear fine in the UV Editor):\n\n\n\n\n\n\n---\nOriginal report:\n[modular.blend](modular.blend)\n\nLook at the image reference in the shader for the second to last vehicle. All other vehicles with similar bodies are linked and are following the map except the second to last object. After linking the body of that vehicle, the object appears to follow the map until you render the image. ", "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", "Smear tool painting vertex colors corrupts color info: part 2\nvertex colors get corrupted under certain blend mode combinations. 3.0.1 master.\n\nusing the smear tool over blue colors introduce green, magenta, yellow, gray and orange not present inside the blue ranges.\n\npainting with blue results in grays instead. \n\ni had this problem in 3.2 alpha using sculpt vertex colors, but when i got back to a project in 3.0.1 it happened with vanilla vertex colors tool. \n\nincluded a file this time\n\n[vertex colors bug.blend](vertex_colors_bug.blend)\n\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1\nWorked: (newest version of Blender that worked as expected) 2.93\n\nSmear tool painting vertex colors corrupts color info\n\nuse paint brush with blue color. paints gray instead.\nuse smear brush. it should smear blues and not oranges and greens.\n", "EEVEE: Material update does not trigger shadowmap update\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nModify procedural does not update real time in view port shading in EEVEE \n\nJust a cookie with procedural noise in front of a point light in EEVEE (remove hdri if it's missing), I could not see changes while modify noise texture, also with viewer\n\nAttached blend file and video\n[studio-light-v1.blend](studio-light-v1.blend)\n[studio-procedural-gobo.mp4](studio-procedural-gobo.mp4)\n", "Cycles: transparent object has black line where it intersect with other objects\nOperating system: Windows-10-10.0.18363 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 461.40\n\nBroken: 2.91.2\n\n\nWhen rendering transparent objects that intersect with other objects, black lines will appear on the intersecting area.\n\n1. Open a default scene.\n2. Add a plane to the scene.\n3. Rotate the plane a little.\n4. Move the plane up to make it intersect with the top face of the default cube.\n5. Make sure the view or camera view is very close to the intersecting area and lower the Clip Start value to 0.00001\n6. Set the renderer to Cycles and render the view.\n\n\n\n[Cycles_Black_Line_Transparency.blend](Cycles_Black_Line_Transparency.blend)", "Non animatable properties\nBroken: version: 3.3.0 Alpha\n\nWorking on refreshing the in-built AnimAll addon by adding the latest properties supported in Blender.\n@ideasman42 asked me to file a task\n\nCertain properties are missing animation capabilities:\n\n - Lattice Vertex Groups\n - Mesh Vertex Creases", "Retopology Overlay Color Location\nA user noted that the overlay can be difficult to see when using random object colors: 15\n\nOne solution would be to move the color from the theme to the workspace, and expose it in the overlays popover.\nI think that just exposing the color isn't enough, because editing a preference outside of the preferences window does not autosave.\nMeaning that if you change the color in the popover, save your project, and restart Blender, the color would be back to default.", "Cannot disable shadows if an object is set to holdout.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: Confirmed on Version 3.4 to version: 3.5.0\nWorked: Never (Goes as far as 3.0, since the addition of the \"Object Properties -> Visibility -> Holdout\"option)\n\nCannot control an objects shadow visibility if the object is set to holdout. Having a shadow on a holdout object does not work as expected, especially when trying to use the holdout object as a 3d mask.\n\n\n- Set scene renderer to Eevee.\n- Create an object, set \"Shadow Mode\" to none in the material shader of said object.\n- The object will no longer have a shadow, as expected. \n- Set the object to holdout via \"Object Properties -> Visibility -> Holdout\" option, and the shadow reappears. Can not turn off shadow as long as this option is on.\n - However, if use Holdout shader in the nodes and connect it directly to the Surface output, no shadow will appear (this matches expectation).\n\nAdded a file that directly shows the issue." ]

[ "materials not appling to object \nOperating system: Windows 10\nGraphics card: NVIDIA GeForce MX230\n\nBroken:3.3.1\nWorked: 2.90 or before\n\nwhen the object is selected in the move or rotation mode it is splashing some color rays  and the object is not accepting any color and when I assign to select the color from material properties they are assigned as black. \n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Object properties In-front doesn't work in viewport shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nObject properties In-front doesn't work in viewport shading\nAll the other options works in Object properties/viewport display, except for In-front \n\n\n- Open attached file\n- Go to Viewport Shading\n[lookdev_in_front_bug.blend](lookdev_in_front_bug.blend)\n", "Metal Viewport \n**Status:** `?` Initial stages of development\n\n---\n\n**Description**\nBringing Metal support to the Blender viewport for optimal performance on macOS. This will be implemented as a new GPU Backend within Blender's GPU Module.\n\n**GHOST**\n\n* - [x] Encapsulate use of OpenGL within GHOST_ContextCGL\n* - [x] Add support for Metal Backend to GHOST_ContextCGL\n* - [ ] EDR (Extended Dynamic Range) support for GHOST swapchain\n\n**EEVEE Next - Workbench Next - Overlay Next**\n\nInitial bring-up\n\n* - [ ] Add support for 2D Texture Atomics via Buffer + Implement metal path\n* - [ ] Add support for virtual frame buffers (No attachments, but specified dimensions, currently allocating temporary texture for enablement). \n* - [ ] EEVEE + GPU Unit tests 100% pastorate\n* - [ ] EEVEE irradiance cache baking - Metal support\n* - [ ] EEVEE Next shadows - Metal support\n\nOptimisation + Later:\n\n* - [ ] Optimize compute kernel workgroup sizes for all passes\n* - [ ] Investigate kernels wherein threadgroup size requirement exceeds optimal sizing heuristic. Aim to avoid using maxTotalThreadsPerThreadgroup.\n* - [ ] Ensure resource usage is optimal (compression etc)\n\n**GPU Module METAL Backend**\n * - [x] MTL_backend\n * - [x] MTL_batch\n * - [x] -> Metal indirect draw support\n * - [x] MTL_capabilities\n * - [x] MTL_command_buffer\n * - [x] MTL_context\n * - [x] MTL_debug\n * - [x] MTL_drawlist\n * - [x] MTL_element\n * - [x] MTL_extensions (via backend)\n * - [x] MTL_framebuffer\n * - [x] MTL_immediate\n * - [x] MTL_memory_manager\n * - [x] MTL_query\n * - [x] MTL_shader\n * - [x] MTL_shader_interface\n * - [x] MTL_state\n * - [x] MTL_storage_buf\n * - [x] MTL_texture\n * - [x] MTL_uniformbuffer\n * - [x] MTL_vertex_buffer\n * - [x] Compute support for Metal\n\nMore items to be added as necessary.\n\n**GPU Feature coverage**\n\nA number of features available in Blender require API functionality which is either not directly available in the Metal API, such as geometry shaders, or requires a higher degree of explicitness from the high-level renderer. These tasks represent non-invasive changes required to enable full Metal support:\n\n * - [x] GPU - Geometry shader workflow alternative\n * - [x] GPU - Multi-layered rendering support in Vertex Shader\n * - [x] GPU - Shading language translation layer from GLSL to MSL (Metal Shading Language).\n * - [x] GPU - Alternatives for unsupported GPU Primitive types: `GPU_PRIM_TRI_FAN`/`GPU_PRIM_LINE_LOOP` (mtlprimitivetype?language=objc)\n * - [x] GPU - Shader uniform struct alignment validation for Metal (`GPU_uniformbuf_create_from_list`)\n * - [x] GPU - Shader barycentric support in Metal.\n * - [x] GPU - default depth format support checks (Apple Silicon does not support `GPU_DEPTH24_STENCIL8`)\n * - [x] GPU - Lightweight GLSL shader requirements for MSL compatibility.\n * - [ ] GPU - Extended Dynamic Range (EDR) support for OCIO shaders and GPUViewport.\n * - [x] DRW/GPU/COM - Support for Realtime compositor (T99210)\n * - [ ] #104025 Offline Metal shader compilation - Startup compilation time and system caching.\n * - [ ] Metal/DRW - EEVEE/Material PSO (Pipeline State Object) parallel compilation.\n\n> Shader libraries compile (Front-end compilation) in parallel while displaying the default EEVEE material. For Metal (and likely Vulkan too), PSO compilation (backend/low-level compilation) happens on demand, depending on the current render pipeline state in combination with a given shader, and this can take time, introducing stalls and stutters, such as when an object is first selected and the select-engine/depth-only permutation is generated for that particular mesh.\n>\n> Ideally we would want to avoid these one-off PSO stalls, which for OpenGL, are generally hidden behind driver processing. Propose a few options:\n> - Option to add a \"default/fallback shader to a **GPUShader** such that if it needs a fresh PSO, and a default shader/fallback is provided, it can instead bind that shader for the draw. In essence, continue using the EEVEE default material, if PSO compilation is needed, not only when the shader library is compiling.\n> - Shader PSO cache warming: Generate the render pipeline state configurations/permutations up-front to allow background parallel PSO compilation. This could be done by performing a dry-run of Blender and packaging a data-file containing the serialized input structure for the PSO compilation function, and performing background warming after start-up, using this data. This avoids the need to manually specify the configs.\n> - Prepare certain configurations up-front in background by performing dummy renders in different states, and skipping draws which trigger a PSO compilation. This allows the dynamic render state to be set, without performing rendering.\n\n\n * - [x] Metal viewport/Metal Cycles shader compiler load distribution manager. \n\n> As both backends use Metal, there is only a fixed pool of shader compilation threads available. A mechanism should be in place to ensure compilation is not stalled, which could cause the viewport to become unresponsive for synchronous shader compilations. e.g. PSO backend compilations.\n\n```\n\n```\n * - [x] Python -- Use of OpenGL within Python API - Ensure safe fallback (T103863)\n * - [x] Cycles - Live viewport display -- Currently uses OpenGL directly\n\n---\n\n**Relevant links**:\n* `-` Metal-Shading-Language-Specification.pdf\n* `-` metal/\n* `-` Metal-Feature-Set-Tables.pdf", "Blender 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\n", "Regression: object.local_view_get and object.visible_in_viewport_get() always returns False\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.0.0\nBroken: 2.81\nWorked: 2.80\n\nCaused by 1954723635\n\nobject.local_view_get() and object.visible_in_viewport_get() always returns False\n\n1. Set Viewport in Local View.\n2. Get 3D view space, that's in the local view, (in my case C.workspace.screens- [x].areas- [x].spaces[0])\n3. Get local view state by command C.object.local_view_get. Observe that the result is False, but the object is in local view.\n4. Remove object from local View by command C.object.local_view_set. Observe that the object is hidden now.\n5. Get local view state by command C.object.local_view_get. Observe that the result is False, as expected.\n\n{[F12823064](image.png), size=full}\n\nobject.visible_in_viewport_get() have same behavior.", "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", "Viewport view resets after navigating within the Camera view\nOperating system: Pop!_Os 20.04\nGraphics card: Nvidia GTX 1080ti\n\nBroken: 3.0 Beta, 7a5b8cb20284, master, 2021-11- 05, 2.83, 2.79... etc\nWorked: Has never worked\n\nWhen navigating in camera view, if the user goes back to Viewport view it will reset the Viewport back to the world origin\n\n- New File\n- Add Camera\n- Navigate anywhere in Viewport view\n- Go into Camera view\n- Navigate again inside Camera view (use walk navigation)\n- Go back into Viewport view\n- Viewport will reset back to world origin\n\nNOTE: this only happens if you navigate inside the camera, if you go back to Viewport view using the middle mouse button it wont happen\n\n| Blender 3.0 | 2.83.16 | 2.79 |\n| -- | -- | -- |\n| [Peek 2021-11-07 04-54.mp4](Peek_2021-11-07_04-54.mp4) | [Peek 2021-11-07 05-05.mp4](Peek_2021-11-07_05-05.mp4) | [Peek 2021-11-07 05-09.mp4](Peek_2021-11-07_05-09.mp4) |\n", "EEVEE: Reduce viewport render time by only render needed draw passes.\nCurrently all material + effect passes are rendered even when eventually they aren't needed. This can happen when viewing a render pass in the viewport. For example:\n* Mist\n* AO\n* Shadow\n* AOV (after [D7010](D7010) has been comitted)\n* etc\n\nWe should see how we can optimize the rendering pipeline so that only the passes that are needed are drawn. This would lead to a more responsive viewport in these cases.", "OptiX denoiser creates dark artifacts in viewport when used with 2 GPUs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.3.1\n\nThe OptiX denoiser creates several black sectors in the viewport. The smaller the area to be cleaned the more visible the error is.\nThis is only present when I have my 2 GPUs activated at the same time (3070 and 2060s). And it works normally when I enable only one of them.\n\n\n\n1. Activate both GPUs in preferences (OptiX or CUDA)\n2. Select Cycles render > GPU\n3. Activate viewport denoise and select OptiX.\n4. In viewport (Ctrl + B) set a small render region.\n[Based on the default startup]\n\n", "depsgraph.view_layer.name driver expression doesn't work correctly\nOperating system: Windows 11\nGraphics card: Geforce RTX 3090\n\nBroken: 3.3.5 LTS\nBroken: 3.5\n\nI use a driver expression to control modifiers visibility or shader values depending on a view layer name. If the needed view layer is active, then values change. All works well when switching viewlayers manually inside the viewport of my scene. But as soon as I render the scene, the expression is ignored and nothing happen.\n\n* Open attached file\n* Change view layer few times\n\nDriver will change only once. This also doesn't work when rendering.\n\n", "EEVEE: Volumetric simulation show ghosting in playback\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: ALL versions up to and including version: 2.91.0 Alpha\n\n\n\nHere's the video of the problem, as can be seen, I have to stop playback to clear the viewport vdb data from the previous frames. Left is EEVEE viewport, right is solid mode (so you can see what the eevee viewport should be displaying:\n\nIt isn't related to EEVEE volume optimisation as I have tried reducing the number of voxels displayed and also reducing the volume samples, viewport samples, and turning off the denoiser. \n\nlatest gpu driver and blender version, resetting blender to factory defaults doesn't help.\n\n[2020-08-20 04-22-55.mp4](2020-08-20_04-22-55.mp4)\n\nHere's the blend file:\n\n[vdb playback bug.rar](vdb_playback_bug.rar)\n```\n\n```\nP.S, the fps is Extremely slow compared to other 3d apps I've tested this sim in (with shading). Is this due to all of the surplus vdb data not being cleared? Perhaps there needs to be an option to cache to RAM if reading from disk is the cause?\n", "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(", "Black and white pixels appearing in render and viewport when rendering with HIP in Cycles (Blender 3.1.2)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 21.Q4 30.0.14011.2006\n\nBroken: version: 3.1.2\n\n\nViewport and render displayed Black and white pixels in places that should not be black or white when rendering using HIP. On the attached image, the mushroom shows it best and is a hotspot for these broken pixels. Switching to CPU rendering fixed the issue. \n\n*Open attached blend file\n*Set rendering to 'HIP' in preferences, switch to GPU compute for rendering\n*In rendered view in the viewport, there will be black + white error pixels. The more samples are used, the more of these pixels are visible.\n*Rendering the image has the same result. \n[TheWetland.blend](TheWetland.blend)\n\n\n\n", "GPU: Workarounds and Device Features checks becoming obsolete\nBlender 4.0 bumped its OpenGL version from 3.3 Core profile to 4.3 Core profile. Some workarounds and optional device features were added to the GPU Backend in order to emulate features that were not available on all platforms.\n\nThis issue contains a list of features, workarounds that we should revisit.\n\n* `shader_draw_parameters` In Vulkan these seems to be supported even on low end devices (displayreport.php?id=23923#features_core_11) we might want to consider making this a requirement, although it is not required by vulkan.\n* `compute_shader_support` is required for workbench-next\n* `shader_storage_buffer_objects_support` is required (#112572)\n* `shader_image_load_store_support` is required. \n* `clear_viewport_workaround` should be solved by the editor, not by the gpu backend. IIRC the VSE has fixed this some months ago.\n* remove `--debug-gpu-disable-ssbo` as SSBO's are required. (#112571)\n\n", "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", "Default Value for Viewport Display Color's Alpha Wrong.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.92.0 Alpha\nAlso tested on 2.83.8 and same problem.\nWorked: It do not think this has ever worked\n\nWhen reverting to the Default Value for Viewport Display Color the alpha gets down to 0.8 making the object semi transparent.\n\nOpen up a new scene.\nSelect the cube.\nGo to the materials tab.\nScroll down to \"Viewport Display\"\nRight Click on \"Color\"\n\"Reset to Default Value\"\nResult: RGB values go back to the default, but Alpha goes to 0.8\n\n\nThank you so much !" ]

[ "Viewport lags since 451.77-desktop-win10-64bit drivers.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\n\n\n\n\ni need a newest drivers for other 3D softwares but blender has a LAGS viewport since 451.77-desktop-win10-64bit drivers.\nold 442.19-desktop-win10-64bit working good!!!!!!!!!!!!!!!!!\n", "Viewport lag while navigation\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: 2.90.1\n\n[The viewport of the blender lag and everything has become slow after a windows update.]\n\n[New blend file > default Cube > Rotate around in the viewport]\n[{[F8994692](Viewport_lag.blend)}]\n\n" ]

[ "Resetting default value does not work in popovers or menus\nOperating system: Windows 10, 64 bits, \nGraphics card: Nvidia GTX 1080 8 gb, Nvidia GTX1070 8 gb\n\nBroken:\nblender-2.81.0-git.ce2368cf69f5-windows64\n\nWorked: (optional)\n\nResetting options in the context menu (right click) of things like brush stroke strength, Autosmooth, plane offset and other parameters does not work at all, but does work through active Tool side panes and top bar. Probably it should work everywhere? If I'm working full screen I would want to be able to reset it in the context menu with my stylus as I sculpt.\n\n\n\n1 Create any mesh\n2 Enable Sculpt mode\n3 Select any brush\n4 Right click to invoke context menu\n5 Try resetting any of the parameter to default values\n", "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", "New geometry nodes viewer overlay makes mesh edit mode overlays invisible\nOperating system: Linux-5.19.10-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha, current master\n\n\n| {[F13588717](image.png) size=full} | {[F13588720](image.png) size=full} |\n| -- | -- |\n", "Fake Dependency Cycle: 'Disable in Viewport' depends on 'Disable in Renders'\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.2.2\n\nDriving hide_render from hide_viewport causes a dependency cycle\nwhile the error occurs on all objects, the driver does seem to work on some objects, but not others. In the default scene for example, the driver works with the camera, but not the cube or the light\n\n- in the outliner, edit the filter to display the `Disable in Viewport` option.\n- Right click the `Disable in Viewports` icon on any given object\n- Copy as New Driver\n- Right click the `Disable in Render` icon of the same object\n- Paste Driver\n[render visibility driver issue.blend](render_visibility_driver_issue.blend)\n\n", "Drag-to-toggle visible/selectable/renderable in the Group view.\nWindows 64\n\nBroken: 2.70a\n\nThe drag-to-toggle visible/selectable/renderable in the Outliner does not work in the Groups view.\n", "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-", "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.", "Outliner: Data API view can expand non expandable properties\nThe Data API view in the outliner let you click on the (invisble) expand arrow on non expandable properties.\n\nThis result in the property value to become invisible. You can click to bring it back, so I think it's only a display issue.\nNot all properties seems to be affected.\n\nBefore:\n\nAfter:\n", "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)", "Grease Pencil Onion Skin visible when disabled\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\nbroken 2.93.5 - 3.1\n\nGrease Pencil Onion Skins should not be visible in the Viewport when disabled in Viewport Overlay settings, or when Viewport Overlays are turned off. Nevertheless, they still appear in Wireframe View.\n[GP_onion_skin_bug.blend](GP_onion_skin_bug.blend)\n - Create a GP animation with Onion Skinning (example attached)\n - Disable Onion Skins in Viewport Overlay settings\n # Change Viewport Shading Method to Wireframe. The onion skins show up again!\n\n\n", "Sculpting/Painting on invisible objects\nOperating system: Linux-6.5.2-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.2-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-b492f73f87)\n\nBroken: version: 4.0.0 Alpha\nWorked: ---\n\nThis is an inconsistency that I noticed when toggling between collections of objects while working on an asset. It's most likely not a regression.\n\nIn edit mode it's impossible to operate on the selection if the object is currently hidden. This is very helpful to prevent mistakes and as feedback that you might be editing the wrong object atm.\n\nWhile in sculpt mode or any of the painting modes this is not the case. If the object is currently hidden while in sculpt or weight paint mode, it is possible to use the brushes on the geometry.\n\nIdeally any operation should be prevented if the object is hidden.\n\n1. Enter edit mode.\n2. Select everything.\n3. Hide the object or collection in the outliner.\n4. Try to move or otherwise edit the selected geometry.\n5. Show the object again (No edits should have happened).\n6. Enter sculpt mode and hid the object/collection again.\n7. Use a brush on the hidden object.\n8. Show the object/collection (See the edits that have been done).\n\n", "Collections.hide_viewport needs Visibility user interface\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\n[Collection.hide_viewport ](bpy.types.Collection.html#bpy.types.Collection.hide_viewport) disables a Collection without a Visibility user interface: an inconsistency with Objects.\n\nObjects whose visibility have been disabled by Python can be re-enabled from the Visibility panel:\n```\ncube = bpy.data.objects.get(\"Cube\")\ncube.hide_viewport = True\n```\n\n\nCollections do not:\n```\nimport bpy\ncoll = bpy.data.collections.get(\"Collection\")\ncoll.hide_viewport = True\n```\n\n\nIn order to re-enable a collection disabled using `hide_viewport`, the user must context-click the Collection > Visibility > Enable in Viewports which is very confusing and inconsistent with Objects.", "Artifacts around shadow catcher object\nOperating system: Win 10 PRO 19041.1348\nGraphics card: GTX 1080\n\nBroken: Official 3.0\nWorked: 2.9 lts\n\n{[F12718649](image.png),size = full}\n[头图制作B.blend](头图制作B.blend)\n\nLine is faintly visible at Y=472px height.\n\nThis doesn't happen when Denoise node Prefilter is set to Accurate, but when opening older files, Fast option is used by default.\n", "Mask paint is invisible in Sculpt Mode.\nOperating system:Mac OS 12.3.1\nGraphics card: 24-core GPU (?)\n\n**Blender Version** 3.2.1\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nThe mask in sculpt mode is invisible. I have the overlay turned on and I don't have any unapplied modifiers. I also don't have any physics or particle systems turned on. \n\nThank you for your help.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "weird viewport visual glitch\nOperating system: Windows 11 64 bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti Gaming X Trio\n\nBroken: version: 3.3.1\nWorked: cant bother sorry\n\nits like the position of the viewport has an offset relative to the orientation of the camera, and the viewport has a set size and cant change.\n\nfirst go to the layout workspace and have an animation playing (must have an animation playing for the bug to happen), then create a new viewport by sliding it like im doing in the video. then change the viewport into rendering mode like im doing in the video and when you resize the viewport, it has a set size and cant be changed and the position of all parts have an offset according to the position and orientation of the camera.\n\n" ]

[ "Topbar glitch when the Status Bar is hidden due to the process bar display\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: 2.81a, 2.82a, 2.83.0, 2.90, 2.93.3, 3.1.0\nWorked: not found\n\nIf the Status Bar is hidden, when you invoke a process that displays a progress bar, it causes a glitch.\n\nThis has something to do with the fact that the *arena* is divided into *regions*, so for example,\nthis works fine when `template_running_jobs()` is moved from `draw_right()` to `draw_left()`.\n\n\n- Hide the Status Bar\n- Press F12\n\n{[F8577145](topbar-glitch.png), size=full}\n\n[topbar-glitch.mov](topbar-glitch.mov)\n\n\n- Hide the Status Bar\n- Invoke the File Browser with File > Import or Add > Image > Background.\n\n{[F10340167](bug.mp4), layout=link}", "Header Bar in the Layout View collapses suddenly\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 466.27 (2 times)\n\nBroken: version: 3.0.0\n\nHeader Bar in the Layout View collapses suddenly (to avoid confusion it is the top bar with the tabs for File, Edit, Render, etc ...). It collapses to about 1/3th of the original and required height making the bar unusable till expanded to original height again. This can be done by hovering the mouse over the top border of the collapsed bar and dragging it upwards. \n\nThe reproduction again seems difficult. This error appeared in the beta version of 3.0 and still is there in the official release 3.0. I had this error twice after saving the file with the \"Save As\" menu .\n\n\n", "Blender window occasionally crops top menu bar making it inaccessible\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.2.2\n\nFor the past year I occasionally experience an issue where the Blender file interface window will suddenly crop the top menu bar; usually occurs when the window is maximized. The top menu bar then becomes disabled until I un-maximize and then re-maximize the window.\n\nSometimes un-maximizing and then re-maximizing the window doesn't fix the issue and the window becomes frozen. The only solution then is to exit the file by hitting the Ctrl+Q hotkeys.\n\nCan't reproduce on demand. Typically happens with larger projects where there are multiple linked assets\n\n\n\n[console_window.txt](console_window.txt)\n\n\n", "Topbar Glitch On Save\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.5\n\nIf you disable the status bar and then save your file, the Topbar glitches out (at least on my system) and is covered with a gray bar preventing you from accessing anything on it until you click the dividing line between the topbar and an underlying editor. Minimize the program and adjusting the window will also dismiss the glitch. This happens for me on the master branch as well as 3.0 beta and 3.1 alpha.\n\n1. From a vanilla install of Blender, without adjusting any settings.\n2. Open Blender. Go to Window and uncheck \"Show Status Bar\".\n3. Press File and \"Save As\" then press \"Save As\" again to confirm the save.\n4. The topbar glitches out and is covered with a gray bar.\n[Based on the default startup]\n\nNote, a display menu tab seems to appear on the gray bar that covers up the topbar when this happens.\n" ]

[ "Error message and unable to edit a skeleton when using a library override armature\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.0\nWorked: No idea.\n\nBlender generates an error when you attempt to enter edit mode on a library overriden armature. There's no description of what the error is or if there is some extra step to make it work. Hopefully this isn't one of those, \"works as intended issues,\" because then there's no way to make multiple characters share an updateable base rig.\n\n\n- Add an armature, enter edit mode, extrude out a few bones.\n- Save the file and open a new scene.\n- Link in the armature you just created.\n- Make the armature a library override.\n- Try to enter edit mode. Should get an error.\n\n", "\"RENDER_OT_render\" called with \"EXEC_DEFAULT\" freezes Blender with Eevee motion blur enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\n\nbpy.ops.render.render() called without 'INVOKE_DEFAULT' from the Python Console or script freezes Blender when Eevee motion blur is enabled.\nAnd the same issue is in the 2.91 Alpha version.\n\n----\n\n- Open Blender\n- Make sure context scene render engine is Eevee\n- Turn on motion blur\n- Open Python console\n- type in bpy.ops.render.render() and hit enter\n\n----\n\n*Edit* (added method that doesn't activate via Python).\n\n**Exact steps to reproduce the error without activating from Python.**\n- Open Blender\n- Make sure context scene render engine is Eevee\n- Turn on motion blur\n- Run this script in the text editor\n\n\n```\nimport bpy\ndef menu_func_import(self, context):\n layout = self.layout\n layout.operator_context = 'EXEC_DEFAULT'\n layout.operator(\"render.render\", text=\"Blocking Render\")\nbpy.types.TOPBAR_MT_render.append(menu_func_import)\n```\n\n- Run \"Render -> Blocking Render\" from the top-bar.", "Motion blur artifacts on certain frames EEVEE\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nMotion blur on error appears on same certain frames.\n\nblend attached Error appears on frames : 49 , 60, 85, 95, 103, 119,130\n\n[blur test.blend](blur_test.blend)\nnormal frame \n\nerror frame \n\nvideo with error frames [0001-0300.mp4](0001-0300.mp4)\n\n", "Crash when rendering animation\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\n\n\nI was rendering a simple camera animation overnight, Blender crashed about 2/3rd the way through. Here's the crash log.\n", "Crash on render on some of the frames\nOperating system: Linux-4.4.0-154-generic-x86_64-with-debian-stretch-sid 64 Bits\n8x Tesla V100 SXM2 NVLINK Accelerator Cards\nDual XEON Scalable 4208 CPUs\n192 GB RAM\n\nBroken: version: 2.82 (sub 7)\nI also tested recent 2.83 build\n\nBlender crash when it renders scene frames from 346-639, the rest of the frames are fine.\nIt crashes for CPU anf GPU as well.\n\nIn order to render above frames I workaround the assert:\n\n```\n--- a/intern/cycles/kernel/kernel_compat_cpu.h\n+++ b/intern/cycles/kernel/kernel_compat_cpu.h\n@@ -74,8 +74,10 @@ CCL_NAMESPACE_BEGIN\n template<typename T> struct texture {\n ccl_always_inline const T &fetch(int index)\n {\n- kernel_assert(index >= 0 && index < width);\n- return data[index];\n+ //kernel_assert(index >= 0 && index < width);\n+ if (index < 0) return data[0];\n+ else if (index >= width) return data[width];{F8410049}\n+ else return data[index];\n }\n #if defined(__KERNEL_AVX__) || defined(__KERNEL_AVX2__)\n /* Reads 256 bytes but indexes in blocks of 128 bytes to maintain\n```\n\nThe scene is complex and I couldn't make it very simply and narrow the problem.\nPlease find the scene attached.\n\n[animation_002_02_part01.blend](animation_002_02_part01.blend)\n\n1. Open Blender 2.82\n2. Open attached scene\n3. Set frame 346, start render (F12)\n4. After one minute or so it will crash\n\n\n", "Extremely frequent crashing when using the compositor. Especially when using the glare node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I believe it was far more stable before the realtime compositor implementation. (Blender 3.3-ish)\n\nBlender crashes extremely frequently when using the compositor on my system, especially when the glare node is being used at all. Does not seem related to vram or system specs, and looking through logs has not come up with any errors - it just closes.\n\nAdjust compositor glare node values with the viewer enabled. It seems to crash within a minute of doing so, usually sooner.\n\n", "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", "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", "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", "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", "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)", "Using python handlers introduces artifacts with EEVEE motion blur\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Beta\n\n\nRendered image has \"wrong\" motion blur\n\n0. Open attached .blend file\n[motion_blur.blend](motion_blur.blend)\n1. It contains a script, which sets the cube position via a follow path constraint based on the current frame:\n\n2. Set motion blur steps to 1, render:\n\n3. Set motion blur steps to 8, render:\n\n", "Blender 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", "Evee Render crashes [2.80] Beta\nOperating system: Win10\nGraphics card: 980ti\n32GB memory\nSSD\n\nBroken:\n2.80 2019-02-10\n\nHard disk storage overflow occurring\n\nParticle simulations\n\n1000's particles\nover 10's of thousands frames\n\nIt seems Evee renderer is built around rendering baking viewport to file, in certain situations auto saving a large temporary baked file leads to a system running out of memory when the file exceeds available storage with large bakes.\n\nAutosaves with large bakes to any available memory on this, this can be replicated with high memory commit states.\n\nI also suspect when the memory commit exceeds the remaining memory on the computer, saving attempts to write to disk and subsequently crashes a number of background programs whose telemetry attempts to use disk space to hash the reports.\nThe target file attempting to be saved is corrupted if it is being overwritten.\nI haven't confirmed whether the project file or autosave file corrupts in the process of saving, but it is very easy to lose a project and or backup when the bake commit is disproportion large to available memory on the machine.\n\nautosave : Enabled (default 2min)", "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" ]

[ "Eevee Render crash with Motion Blur and Overscan\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nCaused by 1d49293b80\n\nBlender crashes when rendering with motion blur enabled.\n\n- Open default file\n- Enable Motion Blur\n- Enable Overscan ({nav Render Properties > Film > Overscan})\n- Render Image\n[Eevee Motion Blur Crash.blend](Eevee_Motion_Blur_Crash.blend)\n\n" ]

[ "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "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", "Cycles regression testing for GPU devices\n**Background**\n\nThe Cycles automated regression tests so far only ran on the CPU.\n\nWith some environment flags it was possible to execute a script that runs them on other devices, but this is cumbersome. The goal of this task is to add a CMake option to enable running the regression tests on GPU devices in addition to CPU devices.\n\nThe reference images are currently only valid for CPU rendering. Keeping differeing reference images updated will have to wait until we have CI infrastructure for testing GPU rendering. For now we can do a few things:\n* Do nothing and manually check when tests fail\n* Increase difference thresholds for tests that only differ a little\n* Disable failing tests for GPU testing\n\n**Status**\n\n- [x] CYCLES_TEST_DEVICES option to specify devices to test\n- [x] Blacklist failing CUDA tests\n- [x] Blacklist failing OPTIX tests\n- [ ] Verify HIP tests are working\n- [ ] Enable GPU testing on the buildbot", "OptiX Denoiser crashes OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\nCPU: AMD Ryzen 7 1700\nRAM: 32 GB\n\nBroken: version: 2.90.0 Alpha\nWorked: unknown\n\nWhen the Viewport OptiX Denoiser is activated it crashes with the following error *\"OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources(denoiser, rect_size.x, rect_size.y, &sizes) (device_optix.cpp:850)\"*\n\nBased in the Startup File, (Reseted to Factory Settings and userpref.blend deleted):\n1. In Preference->System set Cycles Render Devices to \"CUDA\"\n2. Set render engine to \"Cycles\"\n3. Set device to \"GPU Compute\"\n4. Set Viewport Denoiser to \"Fastest (Optix)\" or \"OptiX\"\n5. Set Viewport Shading to \"Rendered\"\nERROR *(View screenshot)*\n\nOnce the error has ocurred I can't render with CUDA, even on a new file. To be able to render with CUDA I must close Blender and open it again. *View System Console Output*\n\n**Additional Info**\n\n- The error doesn't happen if the Cycles Render Devices is set to \"OptiX\"\n- This error doesn't happen in my laptop (i7 7700HQ, GTX 1050, 16GB RAM)\n- In a more complex scene blender tries to load the render kernels for a long time before throwing the error\n\n\n[system console Output.txt](system_console_Output.txt)\n[system-info.txt](system-info.txt)\n\n\n\n", "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "GPencil: W shortcut in Draw mode not working and displays error\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.1\n\nThe W shortcut used to display the Context menu, the same summoned with RMB, but it's not working & displaying this error message:\n```\nTool 'builtin.select_box' not found for space 'VIEW_3D'\n```\nOpen a new 2D Animation file and press W.\n\n", "Reliable GPU hang on common Intel cards (Linux)\nOperating system: Linux Fedora 32\nGraphics card: UHD Graphics 620 (rev 07) Intel\n\nBroken: 2.80.x, 2.90.0-x\n\n\n\nBlender crashes the computer, freezing, dmesg command shows a GPU Hang error.\n\n\nOnly with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here)\n\nOpen the given blend file [F8892221](gpuhangtest.blend) (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs.\n\nI followed the dmesg output that says to create an issue on freedesktop gitlab: 2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender.\n\nThe problem started from 2.80 if I'm not wrong, not with others earlier versions.\n\n", "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", "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", "Startup.blend file is not loaded on startup if userpref.blend does not exist.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 26.20.100.7000\n\nBroken: version: 2.81 (sub 3)\nWorked: (optional)\n\nStartup.blend file is not loaded on startup if userpref.blend does not exist.\n\n- Remove userpref.blend file from it's usual location\n- Start blender\n- Dismiss splash screen by clicking on 3D viewport\n- Make some change to the file (move the cube)\n- Save as startup file\n- Close Blender\n# Open blender\n\nStartup file is not loaded", "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", "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", "GPUOffScreen example give strange \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.1.2\n\n\n\n1. copy the code from here gpu.html#rendering-the-3d-view-into-a-texture\n2. run it \n\n", "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", "OptiX denoiser creates dark artifacts in viewport when used with 2 GPUs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.3.1\n\nThe OptiX denoiser creates several black sectors in the viewport. The smaller the area to be cleaned the more visible the error is.\nThis is only present when I have my 2 GPUs activated at the same time (3070 and 2060s). And it works normally when I enable only one of them.\n\n\n\n1. Activate both GPUs in preferences (OptiX or CUDA)\n2. Select Cycles render > GPU\n3. Activate viewport denoise and select OptiX.\n4. In viewport (Ctrl + B) set a small render region.\n[Based on the default startup]\n\n" ]

[ "Error: Launch in CUDA queue copy_from_device (integrator_intersect_closest)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Quadro K2100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.91\n\nBroken: version: 3.3.0\n\nWith the Blender 3.3.0 splash .blend file, on rendering with CUDA GPU I get the following error, nothing is displayed on screen.\n\nError: Launch in CUDA queue copy_from_device (integrator_intersect_closest)\n\nThis was using nvidia driver 425.91.\n\nI also tested with 3.3.1, same issue.\n\nWith the 3.4 beta, it displayed the start of an image and then failed with the same error.\n\nI have since upgraded to a newer driver, 426.78, and that fails with a different error, That's nothing rendered and error:\n\nError: Launch failed in CUDA queue copy_from_device (integrator_shade_surface_raytrace integrator_sorted_paths_array integrator_compact_shadow_states prefix_sum)\n\n\n\n1. Load the blender_3_3_lts_splash_by_piotr_krynski.blend file.\n2. Set settings to CUDA GPU\n3. F12\n\n" ]

[ "AutoDepth ignores texture transparency\nOperating system: Win 10 64-bit\nGraphics card: 980 Ti\n\nBroken: 2.93.4 LTS, 3.0 alpha (including current latest build)\nWorked: 2.79\n\nWhen navigating using mouse with auto-depth enabled, the full-transparent parts of textures should be ignored when picking the depth.\nThis worked correctly in 2.79, but 2.93 and the latest 3.0 alpha seem to ignore this.\n\n\nEnable Auto-Depth, create an object, assign it a material with some full-transparent texture, then try to zoom / pan using mouse with the cursor on it.\n[autodepth-transparent-issue.blend](autodepth-transparent-issue.blend)", "3D Cursor don´t take into actcount the face orenration with keyboard shortcut ( Shift + RClick)\nversion: 2.80 (sub 51), branch: blender2.7, commit date: 2019-03-25 00:55, hash: 07f6be87a97e, type: Release\nbuild date: 24/03/2019, 18:03\nplatform: Windows\n\n3D Cursor don´t take into account the Geometry orentation (topbar options ) with keyboard shortcut\n\n- Open blender and select 3D cursor tool\n- Set \"Geometry\" in the topbar 3D Cursor options\n- Use Shift + RClick to set your 3D cursor on top of default cube\n\nResult:\n\n3D Cursor don´t take into actcount the face orenration \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.", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822", "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", "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)", "Painting on pixel-textures do not allow to paint some faces\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: \n- 2.92.0\n- 2.91.0\n- 2.90.1\n\n\nI can paint one face but can`t do it with another, and third one transfer color to wrong place of texture.\n[2020-12-21_11-51-55.mp4](2020-12-21_11-51-55.mp4)\n\nHere the file\n[1pxTexturePaint.blend](1pxTexturePaint.blend)\n", "Multires Unsubdivide freezes Blender with hidden geoemtry\nOperating system: Linux-5.15.0-41-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.3.0 Alpha\n\nIn the Multiresolution modifier the buttons \"Unsubdivide\" and \"Rebuild Subdivisions\" do a similar operation.\nWhen having any faces in edit/sculpt mode hidden though, using any of these operators will freeze Blender.\n\n- Subdivide Cube a couple times\n- Apply modifier\n- In edit mode, hide some faces\n- Add multires modifier (Don't add any more subdivisions)\n- Use \"Unsubdivide\" or \"Rebuild Subdivisions\" \n\n[#99887.blend](T99887.blend)", "Multires spikes\nOperating system:\nGraphics card:\n\nBroken: Blender 3.00\nWorked:\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Sculpt while having multires modifier on\n2. Move \"sculpt\" level up and down\n3. Go into edit mode? I am not sure if I did do this, but I read that some people did do it to cause the artifact to appear. \n4. Artifact appear\n5. Unable to fix, without restarting [Handle safeguard v2.blend](Handle_safeguard_v2.blend)\n\nI can read online that this seems to have been a bug for long, but I couldn't find a fix. \n\nCan I use multires on my objects? What exactly caused this, and how can I fix it? \n\n", "Improve Interior Face Selection Method #2\nOperating system: Win 10 Pro\nGraphics card: nVidia GeForce GTX 1070ti\n\nBroken: tested in 2.80 stable and 2.81-dcad1eb03ccc\n\n\nIn Edit Mode Select -> Select all by Trait -> Interior Faces does not select all expected Faces.\n\n\nIn the attached blend file try to select the interior faces by trait and nothing happens. The object was created by moving a default cyclinder and UV sphere into each other and merging the vertices at the spheres equator by distance. After the merge the top face of the cylinder is selected by trait as expected while the lower faces of the sphere are not.\n\n[interior_faces_bug.blend](interior_faces_bug.blend)", "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", "unsubdivide of Multires bug\n**Blender Version**2.91\n\nI try to use unsubdivide of Multires function in blender ,but the result is error.So I test in Zbrush with same modle, it work rightly.\n\nThe thing is,I want sculpt with tank top with no thickness,and add thick ness at last.So I first sculpt with Multires (3 level subdivide),and apply it,and I loop cut the edge with 7 loop cut.After that I add Multires,and use unsubdivide,the result go wrong.\n\nI use the same modle in Zbrush,it work rightly.[unsubdivide error.zip](unsubdivide_error.zip)", "select interior faces doesn't support some kinds of interior geometry\nwin 7 pro\n\nBroken: (example: 2.76.1 bfdb420)\nWorked: (optional)\n\nwhen you try to check if there are some interior faces, from menu you select interior faces in face mode. but it does not show them. you only can do this by select non manifold in egde mode and then find the wrong ones. \nwhen you open file, there is black frame where interior faces are. change to face mode, then select interior faces from menu. nothing happens. change to egde mode and select non manifold, and there are 2 interior faces which were not selected earlier.\n[interior faces_bug.blend](interior_faces_bug.blend)\n", "Data Transfer modifier works only for Byte Color & Face Corner color attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.2.0\n\nIf a target color attribute Domain is *Vertex* or it's Data Type is *Color*, the data are not transferred.\n\n[data-transfer-color-attr-bug.blend](data-transfer-color-attr-bug.blend)\nYou can see in the attached .blend that the Data Transfer modifier is set correctly, but the Col attribute isn't updated.\nAfter doing Convert Attribute -> Domain: *Face Corner*, Data Type: *Byte Color*, it starts to work correctly.\n\n\n", " Render Face Sets and Mask as contour lines\nFace Sets were added to control the visibility of all paint modes and currently, they are rendered as colors (which is the easiest way to debug them and work with them from sculpt mode). This won't work for vertex paint and texture paint (and any other mode that works with color), so a different rendering needs to be implemented that does not affect the color of the surface as an option these painting modes. \n\nIf possible, this should be implemented for the current sculpt mask (add an option to render it as a contour line, similar to the lasso selection) as the same mask implementation and rendering will also be used for vertex paint." ]

[ "Mesh Boundary and Face Sets Boundary automasking not working in sculpt mode with Multires\nOperating system: Linux-5.3.0-59-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.59\n\nBroken: version: 2.90.0 Alpha\n\nWhen sculpting on an objects multiresolution modifier subdivision levels, the automasking options \"Mesh Boundary\" & \"Face Sets Boundary\" are not working.\n\n" ]

[ "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Geometry Node: Input Color node: Custom color and value color is the same property\nOperating system: Linux-5.15.0-60-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.4.1\nWorked: Never.\n\n\nCustom color and value color is the same property. Impossible to set custom color to node, always edited value color.\n\n1. Create Geometry Node tree.\n2. Create `Input Color` node\n3. In `N` panel, `Node` page:\n a. Enable `Custom Color` button.\n b. Try to change custom color.", "LightGroups & big render resolution results in Hardware failure & macOS crash incl. reboot\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15\n\n**Blender VersionS**\nBroken: version: 3.2.0 Alpha\nBroken: version: 3.2.0 Alpha\n\n\n(GPU only)\nI usually render with a resolution of 5120x2048 on 50% as check resolution. \nWhen I scale it up with the slider to 100% and render I get a stripe pattern as we seen in other bugreports related to M1 Mac's.\nThen when I try double the resolution on 50% I get the same.\n\nThe crash of macOS with a hardware failure and reboot happened when I tried my final resolution 10240x2048 on 100%. (blender calculated a sec. and when the render via GPU only started it hanged for two sec. and then completely crashed)\nTo be honest, a crash like this I never had with 3 imac's the last 6 years. Only with a hackintosh not related to blender...\n\nDespite the fact of the total crash, I decided not to try to reproduce the total crash,\nBUT...\nthe stripes I could with the resolution I used. \n- Open attached file\n- Render once in 50% from 5120x2048,\n- and then render on 100%, or try the higher resolution.\n\n(The scene was: just a plane, monkey and 3 lights, to check the lightgroups and compositing options (worked all fine, exept the render...))\n(see attached blendfile)\n\nSo just 3 pointlights, each into a one of the 3 lightgroups a plane, monkey...(something to get lit),\nresolution 5120x2048 on 50% and render. Then render on 100% and you should get stripes.\n\n`***When there, just delete the lightgroups under Scene -> View Layer Tab and the stripes are gone.***`\nOperating system: (INTEL) macOS-12.3.1-x86_64-i386-64bit 64 Bits \nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15\n[untitled.blend](untitled.blend)\n", "Particle Texture influence broken when using two particle system on the same object\nOperating system: Ubuntu 18.04\nGraphics card: GeForce 970GTX\n\nBroken: 2.90.1\nWorked: Never (2.8+)\n\n\nWhen using two particles system on the same object with an influencing texture, one particle system has a wrong influence (e.g. Particle System shrink to quickly)\n\nBlend File: [particle_texture_bug.blend](particle_texture_bug.blend)\n\n0. Set the animation start and end to 100 - 200\n1. Create an Emitter and a Particle Object\n2. Add a Particle System to the Emitter and use the Particle Object for rendering\n3. Set the Start and End to 100 - 200\n4. Give the Particle System a Blend Texture that influences the size with \"Strand/Particle\" as Coordinates\n5. Add another System and Duplicate the previous one to get the exact same setting\n6. Change the Start and End of the new System to 0 - 100\n7. Bake all Dynamics\n8. Render Frame 199 and compare to rendering of 101. The particles in 199 are tiny in comparison (or invisible). They should look near identical\n\nOptional: \n9. Remove the 0-100 Particle and Redo Baking\n10. Frame 199 now has normal sized particles\n", "Pointness gives a white spots on a small objects \nWin10, gtx 1070\nBroken: 2.79,2.79a,2.79b\n\nPointness gives a white spots on a small objects (a few cm objects)\nIn the image below, you can see how the `Pointless` output is affected by the local size:\n\n\nThe leftmost object shows the smallest one, the middle one is of intermediate size and the one on the right has not been scaled.\n\n\n - Open: [pointess_scale_bug.blend](pointess_scale_bug.blend)\n", "Properties don't update focus when copy/paste an object\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1, 3.1.2\nWorked: I don't know\n\nIf you **Copy/Paste** object with **Ctrl+C**, **Ctrl+V** the Property window will still have focus on the old object (although a new one is selected).\nIn this case, the **Duplicate** operation works correctly, the focus is on the new object (the one that is selected).\nReproduce on **Scene objects** and on **Nodes** in node editor. I think there are many more places.\n\n[filename700.mp4](filename700.mp4)\n[filename704.mp4](filename704.mp4)\n\nIn node editor\n1) Select any node.\n2) Copy and paste node with Ctrl+C/Ctrl+V.\n3) Change any properties, you can see that you are changing the previous object, although a new one is selected.\n\n", "Object Info node random output doesn't work properly\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13399 Core Profile Context 0\n\nBroken: version: 3.6.2\nWorked:\n\n**Short description of error and steps for others to reproduce the error**\nI have a scene with many collection instances of a collection containing a car and its wheels. The car has a material on it with its base color being controlled by an object info node's random output:\n[![enter image description here][1]][1]\n\nEverything looks good as long as I am in material preview with the overlays turned off:\n[![enter image description here][2]][2]\n\nBut with the overlays turned on(or sometimes the other way around) or if rendered using the EEVEE render engine, all the cars will have the same color.\n[![enter image description here][3]][3]\n\nHere is the .blend file:\n4whyzTYK#LYLMOGpAT3VvUi4j73Jg63W2p8sG_HRQ8L3E_A107z0\n\n [1]: Api9y.png\n [2]: XZ0Gz.png\n [3]: OeeZJ.jpg\n\n", "closest_point_on_mesh() freezes Blender when called from a driver\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: 2.79\n\nCalling closest_point_on_mesh() from within a driver causes Blender to freeze.\n\n[test2.blend](test2.blend)\nOpen the file allowing scripts -> Freeze", "Some particle hairs that emitted from the vertices do not rotate with the armature.\nOperating system:MacOS\nGraphics card:Radeon Pro\n\nBroken: 2.93.2\n\n\nSome particle hairs that emitted from the vertices do not rotate with the armature.\n\n\n\n\n\n\n\n\n\n[Hair Rotation bug.blend](Hair_Rotation_bug.blend)\n\nSimple example wit a cube:\n[#89749.blend](T89749.blend)\n\nIssue only happens when emitting from Vertices (emitting from faces is fine)", "Optix Viewport Denoiser Makes Objects Glow When Using High Exposure Even When There is no Light in the Scene\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nThe latest build added the feature to let non-RTX GPUs use the denoiser, so I tested it on my scene right away. However, the objects in the scene start glowing when the denoiser starts working. The scene was lit using the Physical Lights feature that the Photographer 3 addon has provided, which offers units like Lumen and Candela, etc. And since physically correct light values can sometimes be very dim (like a candle = 1 candela), sometimes be very bright (like the Sun at noon 111,000 lux), Photographer offers real life camera's settings for modifying the exposure in the color management in the render settings to adjust the overall brightness. And in my scene, I used a candle, which is very dim. Therefore the exposure has been set very high. It has been fine until the denoiser came. \n\nBased on the default startup\n1. Delete the default point light\n2. Turn the World Background Strength to 0\n3. Turn the Exposure in the Render Settings under Color Management to 10\n4. Change the render engine to Cycles\n5. Turn on render view, you should see nothing but complete darkness\n6. Turn on the Optix Viewport denoiser\n7. Wait for a while and see the default cube glowing\n\nI don't know if this is a bug or not, if it is not, please at least get some work around. Like making the denoiser refresh when the exposure changes or something?\n\n", "Regression: Particle mirror broken for particular mirrored mesh.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2. also version: 3.3.0 hash: `8d9d5da13706`\nWorked: 3.0.0, commit hash: `8b44b756d850db38ab4d83513682f2012d88a3f4` from branch 3.0.1 to be exact.\n\nCaused by 02ab4ad991\n\nParticle hair x-mirror results in hair going in all directions instead of being properly mirrored, see the following screenshot: \n\n1. Start from the attached blend file which has an emitter sourced from a base model and mirrored by applying a mirror modifier. I could not reproduce the issue from scratch with simpler geometry and I might have reconnected the hair at some point .\n2. Go into particle edit mode on the `Eyebrows_Particle` object.\n3. Enable x-mirror in the top-right `Options` menu.\n4. Observe that the particles change directions.\n\nHere is what it looks like when it's working in the same particle edit mode with x-mirror enabled. The exact commit that introduced the issue is: `77694b571f5bd297ea7228b30f591ebbd333e0ea`.\n\n\n\n[mirror_bug.blend](mirror_bug.blend)\n\n[repro.blend](repro.blend)\n- open file\n- `Particle` > `Mirror`\n- observe wrong mirroring", "Rigidbody doesn't work when you change motion blur steps in eevee\nOperating system:debian buster\nGraphics card:nvidia gtx 1070\n\nBroken: (example: 2.90, 0330d1df29c0, master, 2020-08-31, as found on the splash screen)\nWorked: Never\n\nRendering unbaked rigidbody simulation in eevee with motion blur with 2 or more steps will cause simulation to stop working.\n\n[#80388.blend](T80388.blend)\n- Open file\n- Check if rigidbody simulation works\n- Render image\n- Check if rigidbody simulation works\nIt doesn't work anymore.", "Diffuse Direct, Indirect Bake to Vertex Color Artefacts\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nWorked: This has never worked properly (At least in my experience)\n\nWhen baking Diffuse light to vertex color, black triangles and random dark spots appear in vertex color. This effect is more apparent with:\n- Area lights.\n- Emissive surfaces.\n- Lights with very high power.\n\n1. Create geometry and give each a byte_color vertex color channel.\n2. Place area lights in scene with high power.\n3. Bake diffuse direct and indirect to color attribute.\n\nSee .blend of my project attached. In the file i've already baked the emissive light to vertex color where you can see the artefacts. Switch to cycles live render view to see the correct output. I think the tiled texture may have something to do with it. I've added a tiled texture and packed it in the example.\n\n", "4.0A producing specular reflections of area lights on diffuse surfaces, 3.6.1 doesn't behave this way.\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.1 & 4.0 Alpha\n\nArea lights in 4.0 Alpha producing specular reflections on diffuse only (specular = 0) surfaces in 4.0.\n\nI tried to report this discrepancy to the developer forum but can't seem to post it there, so I figured maybe whoever monitors this could help. \n\nIn 3.6.1, if a material has no specular component, area lights only produce diffuse illumination. But in the 4.0 alpha (build downloaded 8/14), the area light produces a specular reflection. I don't know if this is a new intentional development thing, or if it's somehow related to the light linking feature.\n\n", "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)" ]

[ "point light won't emit light after duplicate of 128 (render eevee)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[i need 265 lights in one of my scene but point light won't emit light after 127 light the starting from 128 won't emit light ]\n\nopen?id=1BlbieX2ksslRDUud59HUcqvseRhEHwl8\n\n" ]

[ "Blender File Browser Freezes if folder includes an not reachable Alias | MacOS\nOperating system: 13.5.2 (22G91)\nMachine: Apple Macbook Pro M2 Max\n\n3.6.2 - This has been happening before, I'm just reporting it now.\n\nWe have been using an Alias of our flamenco root folder called \"_flamenco\" on our Desktops for a while now. This error is NOT connected to flamenco issues, but I figured I add this for completeness.\n\nAlias is at:\n`/Users/USERACCOUNT/Desktop/\n`\nAlias points to:\n`/Volumes/Files/_flamenco\n`\n\nThis Files server is only reachable in local – physical – network, so if no cable is attached to the machine the connection can not be established.\n\nEvery time I select the Blender File Browser and open the Desktop folder, Blender will hang, freeze or crash. We had quite the trouble figuring out what is happening as we thought it would be connected to the actual contents of the other elements in the folder.\n\nI wonder if it is necessary to evaluate the source of the alias at that stage, or if this can be postponed until I click on the Alias.\n\n\nNo special blend file is needed to recreate this bug.\n\n1. Create Alias to an imaginary/not connected resource to the Desktop\n2. Open default Blender install\n3. File -> Open.. -> \n4. The Blender File Browser will open\n4. The Blender File Browser will still look responsive (hovering over buttons still works) but the next interaction will trigger a freeze\n4. User clicks on anything\n5. The file Browser and Blender will freeze, either for a very long time >3minutes or crash completly\n\n", "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", "Old todos (to be checked)\nNOTE: this is a direct dump of Install-OS (without cherrypicking the valid items)\n\n- [ ] Add code to detect drives to change (usb connected, disconnected)\n- [ ] RNA library needlessly rebuilds every time in visual studio.\n- [ ] Blender doesn't recognize .lnk shortcuts or hidden files.\n- [ ] Symbolic links are not supported #37619.\n- [ ] NTFS junctions are not supported #52080.", "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 randomly crash without reason in 'glDrawElementsInstancedBaseVertex' (in 'OVERLAY_wireframe_draw' or 'workbench_draw_sample')\n|Operating system:|macOS-10.14.6-x86_64-i386-64bit 64 Bits|@MaciejSobolewski\n| -- | -- | -- |\n||macOS Big Sur 11.1 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4|@RonMartin\n||Darwin-18.7.0-x86_64-i386-64bit 64 Bits|@aayerbe\n||Darwin-20.3.0-x86_64-i386-64bit 64 Bits|@Chyiik\n||Mac OS X 10.14.6 (18G7016)|@sahrul\n||macOS 11.2.3 (20D91)|@fahr\n||macOS-10.14.6-x86_64-i386-64bit 64 Bits|@didi404\n---\n|Graphics card:|AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.23|@MaciejSobolewski\n| -- | -- | -- |\n||Intel UHD Graphics 630 1536 MB|@RonMartin\n||Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.25|@aayerbe\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15|@Chyiik\n||Intel Iris Plus Graphics 640|@sahrul\n||AMD FirePro [D700](D700)|@fahr\n||AMD Radeon Pro 570X|@didi404\n\nBroken: 2.91, 2.92, 2.93.0 Alpha, commit date: 2021-04-01 21:49\nWorked: 2.81, 2.90\n\nBlender crashes randomly on Mac OS\nIt can crash randomly after startup even if we do nothing like this example.\n\nIt has also been reported that it happens often when try to save the file after several minutes of work (#86565).\n\nCrash Log 1:\n```lines=25\nProcess: Blender [6485]\nPath: /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\nIdentifier: Blender\nVersion: 2.93.0 (2.93.0 2021-04-01)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [6485]\nUser ID: 501\n\nDate/Time: 2021-04-03 13:43:19.501 +0200\nOS Version: Mac OS X 10.14.6 (18G8022)\nReport Version: 12\nBridge OS Version: 3.0 (14Y906)\nAnonymous UUID: 5527B0F5-C330-CDA4-B73E-9CB133041D4E\n\nSleep/Wake UUID: DBADD923-7C0B-4D5E-AEFC-935ECD0B12BA\n\nTime Awake Since Boot: 850000 seconds\nTime Since Wake: 1600 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000e2c\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [6485]\n\nVM Regions Near 0xe2c:\n--> \n __TEXT 000000010cad1000-0000000118885000 [189.7M] r-x/r-x SM=COW /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff3cfe28b5 gleRunVertexSubmitImmediate + 6085\n1 GLEngine \t0x00007fff3cf4c29c glDrawElementsInstancedBaseVertex_GL3Exec + 681\n2 libGL.dylib \t0x00007fff3c2fcd02 glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x000000010d27bf05 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010d27b68c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x000000010d27afdf DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x000000010d2d2819 OVERLAY_wireframe_draw + 41\n7 org.blenderfoundation.blender \t0x000000010d2c2499 OVERLAY_draw_scene + 393\n8 org.blenderfoundation.blender \t0x000000010d2724fa drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x000000010d274643 drw_draw_depth_loop_impl + 1299\n10 org.blenderfoundation.blender \t0x000000010db9670f ED_view3d_depth_override + 239\n11 org.blenderfoundation.blender \t0x000000010dbbe460 ED_view3d_autodist + 48\n12 org.blenderfoundation.blender \t0x000000010db9dc9a ED_view3d_cursor3d_position + 234\n13 org.blenderfoundation.blender \t0x000000010db9dd80 ED_view3d_cursor3d_position_rotation + 144\n14 org.blenderfoundation.blender \t0x000000010db9e417 ED_view3d_cursor3d_update + 279\n15 org.blenderfoundation.blender \t0x000000010db9e7f1 view3d_cursor3d_invoke + 145\n16 org.blenderfoundation.blender \t0x000000010d152629 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x000000010d153bd8 wm_handler_operator_call + 648\n18 org.blenderfoundation.blender \t0x000000010d1531c4 wm_handlers_do_intern + 1588\n19 org.blenderfoundation.blender \t0x000000010d14ec16 wm_handlers_do + 774\n20 org.blenderfoundation.blender \t0x000000010d14e2de wm_event_do_handlers + 2862\n21 org.blenderfoundation.blender \t0x000000010d146b80 WM_main + 32\n22 org.blenderfoundation.blender \t0x000000010cc3691b main + 907\n23 libdyld.dylib \t0x00007fff5f1f93d5 start + 1\n\n(...)\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000e2c rbx: 0x0000000000000011 rcx: 0x00007fff3cfe28b5 rdx: 0x00007fff3cfe3ec8\n rdi: 0x0000000000000004 rsi: 0x0000000000c00000 rbp: 0x00007ffee312d230 rsp: 0x00007ffee312d090\n r8: 0x0000000000000211 r9: 0x00006000055d9f50 r10: 0x000000000000108c r11: 0x0000000000000001\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000108c00049800\n rip: 0x00007fff3cfe28b5 rfl: 0x0000000000010213 cr2: 0x0000000000000e2c\n \nLogical CPU: 4\nError Code: 0x00000004\nTrap Number: 14\n\n\nBinary Images:\n 0x10cad1000 - 0x118884fdf +org.blenderfoundation.blender (2.93.0 - 2.93.0 2021-04-01) <76DA024A-23A9-360A-9B4D-17E1FFF3C70F> /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n 0x11f240000 - 0x11f2acffb +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender 2.93/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x11f81a000 - 0x11f9affff com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x121431000 - 0x121435ffb com.apple.audio.AppleHDAHALPlugIn (282.54 - 282.54) <207D25F0-B094-3569-AA6D-09B4EDD72861> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x123231000 - 0x123234ff7 +_opcode.cpython-39-darwin.so (0) <B301C79A-62B7-387B-8FF2-1AA125557218> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x123241000 - 0x12325eff3 +libRprSupport64.dylib (0) <E10A8DBC-2DAE-3C5D-A670-E95122180BDF> /Users/USER/Library/Application Support/Blender/*/libRprSupport64.dylib\n 0x123a67000 - 0x123a6affb +_lsprof.cpython-39-darwin.so (0) <390A27D2-FE66-3D62-9D0D-EC24BDD4185E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x123c6f000 - 0x123c72047 libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib\n 0x124d05000 - 0x124dceff7 com.apple.AMDRadeonX4000GLDriver (2.11.23 - 2.1.1) <C9BBA305-1222-3D05-A096-DF3485CAA6D1> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver\n 0x12a338000 - 0x12a4eaffb +libRadeonProRender64.dylib (0) <7857C60D-5962-34B2-9946-AA62FB25A0FC> /Users/USER/Library/Application Support/Blender/*/libRadeonProRender64.dylib\n 0x12b156000 - 0x12b159fff +_heapq.cpython-39-darwin.so (0) <39FBF3FE-B287-3DE1-9C22-E65F7DE3FBD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x12b32f000 - 0x12b33aff3 +math.cpython-39-darwin.so (0) <B182812A-68AA-35BD-A8E8-D26E6BDB8C3F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12b4cf000 - 0x12b53970f dyld (655.1.1) <EA5BF483-08FB-31C9-B31E-C0D0FD94FE89> /usr/lib/dyld\n 0x12c854000 - 0x12cb0b80f +_ssl.cpython-39-darwin.so (0) <9E0B733D-CC78-37AF-9E27-8D058929365F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x12cbdc000 - 0x12cbebff7 +_socket.cpython-39-darwin.so (0) <B1F1427E-EC5E-35BF-8595-3AB7F81B8BFA> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x12cc3c000 - 0x12cc43fff +select.cpython-39-darwin.so (0) <9F931F33-6B72-314B-9365-C443F0E411CE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x12cc50000 - 0x12cc57fff +array.cpython-39-darwin.so (0) <C6EAB41B-E104-3EF6-923E-5279F64BB2AE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x12cc68000 - 0x12cc6fff7 +_struct.cpython-39-darwin.so (0) <80252227-C14A-3C4F-974E-3F540EDA92B5> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12cc80000 - 0x12cc87ff7 +binascii.cpython-39-darwin.so (0) <804000F0-C103-3525-88BB-176B163AC5A4> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12cd14000 - 0x12cd17fff +_bisect.cpython-39-darwin.so (0) <C55FDD46-701F-3112-80AC-1514BA077D76> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12cd24000 - 0x12cd27ff3 +_random.cpython-39-darwin.so (0) <17F6835A-5316-353E-89E2-28FA2C7310B6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12cd34000 - 0x12cd3bff3 +_sha512.cpython-39-darwin.so (0) <FE9A114B-3EB9-331D-9CB2-3F71DA53B2FB> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12cd88000 - 0x12cd97ff7 +_datetime.cpython-39-darwin.so (0) <DD77ED03-5D10-32E9-A860-DEBFE5951394> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x12ce6c000 - 0x12d08b0f7 +_hashlib.cpython-39-darwin.so (0) <4EADD130-4A3F-3A9C-BFD5-5226CC3B80BC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x12d12c000 - 0x12d133ff3 +_blake2.cpython-39-darwin.so (0) <47823C31-458F-31C3-939B-3E51CAFB21E9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x12d140000 - 0x12d143fff +_queue.cpython-39-darwin.so (0) <B6BD974A-932F-3126-8B07-332D5C1005B1> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x12d150000 - 0x12d167ff3 +zlib.cpython-39-darwin.so (0) <1357BDA0-EBFF-328F-8CF8-2BAAF0777C3E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12d2d6000 - 0x12d2edff3 +_bz2.cpython-39-darwin.so (0) <F5BE8D18-E1D6-3C23-B906-AB09DBF0FFBF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12d2fa000 - 0x12d329ff3 +_lzma.cpython-39-darwin.so (0) <6D9DCFA1-0480-302F-8AD2-8B32FD3377EE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12d33a000 - 0x12d33dff7 +grp.cpython-39-darwin.so (0) <DCF6B520-1F6E-3ADF-B061-CE405DC2CB4B> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12d3d9000 - 0x12d3e0fff +_json.cpython-39-darwin.so (0) <ACB3C18C-E080-3C95-8420-DAE93E2D5E99> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12d43f000 - 0x12d442ffb +_scproxy.cpython-39-darwin.so (0) <50CE8674-D618-32A2-9E79-A89350AE9BA9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x12d48f000 - 0x12d59aff7 +unicodedata.cpython-39-darwin.so (0) <B1C10C25-AADB-3554-8EA4-2D8EDBA913C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x12d6cd000 - 0x12d710ff7 +_decimal.cpython-39-darwin.so (0) <DB2C2DBC-0CAC-396C-9DC6-F473D0ED9DD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x12d731000 - 0x12d734ffb +_statistics.cpython-39-darwin.so (0) <1FC5B98C-DFF6-34A6-B0BB-817D49440624> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x12d881000 - 0x12d884ff3 +_posixsubprocess.cpython-39-darwin.so (0) <A047F4C3-E223-3AAB-9298-1E5E46906ADD> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x12db66000 - 0x12dedbfe7 +_multiarray_umath.cpython-39-darwin.so (0) <495E23F2-DD86-34BE-85F2-D8B8FA1CFDFE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12e003000 - 0x131baab4f +libopenblas.0.dylib (0) <03CB01A7-1E7B-3A87-B36F-CD619D546D98> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x131e47000 - 0x131f5eff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x131fcd000 - 0x132003fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x132017000 - 0x13202cff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x14a03c000 - 0x14a053ffb +_pickle.cpython-39-darwin.so (0) <3559C80E-CFDA-3F33-B6ED-B469333FB0C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x14a0b2000 - 0x14a0bfff7 +_multiarray_tests.cpython-39-darwin.so (0) <AE0DCAB5-64AB-3F7D-B12A-60B9B9E919FF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x14a116000 - 0x14a131f4f +_ctypes.cpython-39-darwin.so (0) <61595129-0907-3B76-BAD5-E83E12232E92> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x14a1ce000 - 0x14a1cfffb +lapack_lite.cpython-39-darwin.so (0) <ED8E8882-7728-3AFC-B16E-AD65D26C95CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x14a1d7000 - 0x14a1f0ffb +_umath_linalg.cpython-39-darwin.so (0) <C031BBC1-676E-3561-971A-817DB290B4CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x14a2c4000 - 0x14a2d5fff +_pocketfft_internal.cpython-39-darwin.so (0) <F874775F-892F-3E6D-AB44-13585A46F440> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x14a31e000 - 0x14a38ffff +mtrand.cpython-39-darwin.so (0) <26C3326C-CD5C-3EB6-ADC1-1501DEFF4824> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x14a3ea000 - 0x14a408ffb +bit_generator.cpython-39-darwin.so (0) <0AA58188-F7BE-3259-B73D-F73A44D18892> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x14a429000 - 0x14a45eff3 +_common.cpython-39-darwin.so (0) <A5274DC2-1EDF-3596-810F-949AFC3280AF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x14a47b000 - 0x14a4d1ffb +_bounded_integers.cpython-39-darwin.so (0) <C5EA861D-2A70-3753-B812-574045E67644> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x14a4f8000 - 0x14a506ffb +_mt19937.cpython-39-darwin.so (0) <317BAC67-09BA-3FCD-951A-1F8665EB2AB2> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x14a517000 - 0x14a523ff3 +_philox.cpython-39-darwin.so (0) <E0D66351-2EA3-3CAC-92B8-9BDD75A35465> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x14a533000 - 0x14a53dff7 +_pcg64.cpython-39-darwin.so (0) <97A10DFD-6916-3251-84B1-FCCF8D908E08> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x14a54c000 - 0x14a553fff +_sfc64.cpython-39-darwin.so (0) <4A390EEB-7105-3235-85B2-4C8D98B3587C> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x14a560000 - 0x14a5e6ffb +_generator.cpython-39-darwin.so (0) <D25A4A84-E711-357E-9925-2B76BD03BAB0> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x152b16000 - 0x152b9aff7 +core.so (0) <90E3783C-EA48-3E8D-98E7-E2465548F8C7> /Users/USER/*/core.so\n 0x152e28000 - 0x152e2fff7 +_csv.cpython-39-darwin.so (0) <A88064E5-CC97-3CD9-9422-3148889BB740> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_csv.cpython-39-darwin.so\n 0x7fff27936000 - 0x7fff27c8ffff com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff27c92000 - 0x7fff27d9efff com.apple.AMDMTLBronzeDriver (2.11.23 - 2.1.1) <69902D3A-0267-3D14-9820-D65016305FCC> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver\n 0x7fff27d9f000 - 0x7fff28744ff3 ATIRadeonX4000SCLib.dylib (2.11.23) <CC649A6F-573C-30F6-AC1B-8F0850D85B87> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib\n 0x7fff2caac000 - 0x7fff2d880ff7 com.apple.driver.AppleIntelSKLGraphicsGLDriver (12.10.25 - 12.1.0) <9AE3588C-F533-3A5D-9E4B-602ACEA5493C> /System/Library/Extensions/AppleIntelSKLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsGLDriver\n 0x7fff2d881000 - 0x7fff2dbb2ff7 com.apple.driver.AppleIntelSKLGraphicsMTLDriver (12.10.25 - 12.1.0) <8889F99C-A463-3299-8DE8-ED06FF6A6735> /System/Library/Extensions/AppleIntelSKLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsMTLDriver\n 0x7fff2f5b8000 - 0x7fff2f5b8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2f5b9000 - 0x7fff2f5cfff7 libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2f5d0000 - 0x7fff2fc69fef com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2fc6a000 - 0x7fff2fee3ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2fee4000 - 0x7fff2ff56ffb libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2ff57000 - 0x7fff30300ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff30301000 - 0x7fff30316feb libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff30317000 - 0x7fff3031cff3 libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff3031d000 - 0x7fff30399ff3 libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff3039a000 - 0x7fff303adfe3 libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff303ae000 - 0x7fff30595ff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff30596000 - 0x7fff30649ff7 libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff3064a000 - 0x7fff3064afff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff307ec000 - 0x7fff315a1ffb com.apple.AppKit (6.9 - 1671.60.109) <F3BB6BCD-F2DF-36E7-8F20-FEC419671841> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff315f3000 - 0x7fff315f3fff com.apple.ApplicationServices (50.1 - 50.1) <7BDB78C7-9021-3B29-823A-1FFDB9F79602> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff315f4000 - 0x7fff3165ffff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff316f8000 - 0x7fff3180fff7 libFontParser.dylib (228.6.2.10) <B0B7AF1F-2342-3A95-A7E6-629FC032D4B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff31810000 - 0x7fff31852fff libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff318ac000 - 0x7fff318defff libTrueTypeScaler.dylib (228.6.2.10) <5FE48A9A-8329-3B0D-9A99-DEAC708F8334> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff31943000 - 0x7fff31947ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff319e2000 - 0x7fff31a34ff7 com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff31a35000 - 0x7fff31a44fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff31a45000 - 0x7fff31a8eff7 com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff31a8f000 - 0x7fff31ac8ff7 com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff31ac9000 - 0x7fff31ad5fff com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff31ad6000 - 0x7fff31d4dfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff31d4f000 - 0x7fff31d4ffff com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff320a8000 - 0x7fff3244afff com.apple.CFNetwork (978.5 - 978.5) <06BB192E-0302-3AE9-B229-A9B15AD4CBF4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff3245f000 - 0x7fff3245ffff com.apple.Carbon (158 - 158) <B955D7C0-ACA6-33EB-9527-1598288532A6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff32460000 - 0x7fff32463ffb com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff32464000 - 0x7fff3275bfff com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff3275c000 - 0x7fff3275fff3 com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32760000 - 0x7fff32765ff7 com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff32766000 - 0x7fff327fbff3 com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff327fc000 - 0x7fff32814ff7 com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff32834000 - 0x7fff32835ff7 com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff32836000 - 0x7fff32838ff7 com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff32839000 - 0x7fff3283fff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff32961000 - 0x7fff32961fff com.apple.Cocoa (6.11 - 23) <987A526D-6FD8-345E-9265-4D8067B337D1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff3296f000 - 0x7fff32abeff7 com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff32c4a000 - 0x7fff32cd0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E6E4A58D-9BAE-30B1-856E-E1332B98E9ED> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff32d34000 - 0x7fff32d5effb com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff32d5f000 - 0x7fff330e4fef com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff330e5000 - 0x7fff331d5ff7 com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff331d6000 - 0x7fff3361bfff com.apple.CoreFoundation (6.9 - 1575.401) <4D6EA727-F7B9-398A-9B0B-4A30802E49BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff3361d000 - 0x7fff33cadfe7 com.apple.CoreGraphics (2.0 - 1265.11) <71E7056D-6AA5-324A-A5B8-9CD35772D87B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff33caf000 - 0x7fff33fcffff com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff342cc000 - 0x7fff343d0fff com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3442d000 - 0x7fff3442dfff com.apple.CoreServices (946 - 946) <8423F2AB-74CB-3BBD-A66E-ED93DE2363C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3442e000 - 0x7fff344aaff7 com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff344ab000 - 0x7fff34782fff com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff34783000 - 0x7fff347cbff7 com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff347cc000 - 0x7fff347d4ffb com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff347d5000 - 0x7fff34986ff7 com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff34987000 - 0x7fff34a25ff7 com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff34a26000 - 0x7fff34a70ff7 com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff34a71000 - 0x7fff34ad8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff34ad9000 - 0x7fff34afaff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff34e05000 - 0x7fff34f67ff7 com.apple.CoreText (352.0 - 584.26.3.6) <47B18B6F-C53C-357A-8EBA-A2CD340018E6> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff34f68000 - 0x7fff34fa8ff3 com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff34fa9000 - 0x7fff35038fff com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff3528f000 - 0x7fff35294ffb com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff35458000 - 0x7fff3545aff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <205B0C3E-4E8D-3347-A993-469F06ABBFF9> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff3545b000 - 0x7fff35808ffb com.apple.Foundation (6.9 - 1575.401) <546CCD67-0069-369A-8E6A-37FB5DD64AA1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff35877000 - 0x7fff358a6ffb com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff359a6000 - 0x7fff35ab0fff com.apple.Bluetooth (6.0.14 - 6.0.14d12) <0904E4FC-DE05-3B78-BD49-832A5AC2967D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff35b13000 - 0x7fff35ba2fff com.apple.framework.IOKit (2.0.2 - 1483.260.5) <6D560570-9AEB-3046-96B7-12AC1D145C3D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff35ba4000 - 0x7fff35bb3ffb com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff35c07000 - 0x7fff35d94fe7 com.apple.ImageIO.framework (3.3.0 - 1850.2.11) <5F5F7C36-2A20-3CFE-ACAC-53633B0F2F0A> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff35d95000 - 0x7fff35d99ffb libGIF.dylib (1850.2.12) <060E927C-DFA7-33A7-98E3-F9699D734A8E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff35d9a000 - 0x7fff35e76ff7 libJP2.dylib (1850.2.12) <CEC4FF68-7522-3430-B03D-37648FEB450E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff35e77000 - 0x7fff35e9cfeb libJPEG.dylib (1850.2.12) <F7A6A6EC-24B6-3C45-813F-B2FFA3980B49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff36172000 - 0x7fff36198feb libPng.dylib (1850.2.12) <B816B90B-2454-31D8-AD34-1489B6350C70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff36199000 - 0x7fff3619bffb libRadiance.dylib (1850.2.12) <1A67ED5D-00BC-301D-8515-CEDFFE994F2B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff3619c000 - 0x7fff361e9ff3 libTIFF.dylib (1850.2.12) <3FB9D8DC-1D7B-324C-ADE6-DDC794FD2B43> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3735c000 - 0x7fff37375fff com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3762f000 - 0x7fff37639fff com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff376e9000 - 0x7fff37d8ffff com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff37d91000 - 0x7fff37e39ff7 com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff37e55000 - 0x7fff37e74ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff37e75000 - 0x7fff37ef1fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff37ef2000 - 0x7fff37f19fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff37f1a000 - 0x7fff38045ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff38046000 - 0x7fff38060fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff38061000 - 0x7fff38062ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff38e66000 - 0x7fff38e72ff7 com.apple.NetFS (6.0 - 4.0) <1C8237D6-731D-3E32-8BD5-B92A33D08A30> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff391d5000 - 0x7fff391f8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <2EE5236C-775B-36B1-97A8-DEE5FB80F5B5> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff3b907000 - 0x7fff3b90ffe3 libcldcpuengine.dylib (2.11) <AAE49359-EB53-3FD4-ADBF-C60498BD0B34> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff3b910000 - 0x7fff3b967ff7 com.apple.opencl (2.15.3 - 2.15.3) <2F6B796C-901C-33AF-8B12-F3522DA05218> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3b968000 - 0x7fff3b983ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3b984000 - 0x7fff3b98fffb com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff3c2df000 - 0x7fff3c2e1fff libCVMSPluginSupport.dylib (17.7.3) <700B3323-3404-3848-91D2-99EFC7E2634A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff3c2e2000 - 0x7fff3c2e7ff3 libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff3c2e8000 - 0x7fff3c2ecfff libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff3c2ed000 - 0x7fff3c2f5ff7 libGFXShared.dylib (17.7.3) <26BA051E-1113-3022-A46A-1F69E7CFA787> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff3c2f6000 - 0x7fff3c301fff libGL.dylib (17.7.3) <16C56C55-327F-395F-810C-C360F7DE9063> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff3c302000 - 0x7fff3c33cfef libGLImage.dylib (17.7.3) <F68F1268-5AD1-3D2E-A255-0BD442A24F4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff3c33d000 - 0x7fff3c4afff7 libGLProgrammability.dylib (17.7.3) <92DDEDA1-5E95-36A9-9D2E-A725541B2F93> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff3c4b0000 - 0x7fff3c4eefff libGLU.dylib (17.7.3) <D83871DF-B7DD-3DFD-8D5C-0BA359AC1BF2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff3ce8b000 - 0x7fff3ce9affb com.apple.opengl (17.7.3 - 17.7.3) <62E4CB29-51CA-387E-90BF-F58213D56D62> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff3ce9b000 - 0x7fff3d032ff7 GLEngine (17.7.3) <8C9F33DD-7C81-3D45-80F7-A7D6A877993A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff3d033000 - 0x7fff3d05cff3 GLRendererFloat (17.7.3) <2B5F700E-9E9B-3543-BC35-949279CB24FF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3dca4000 - 0x7fff3defbff7 com.apple.QuartzCore (1.11 - 701.14) <B37B1291-4977-34D2-B3F0-509FB3DB5090> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3e733000 - 0x7fff3ea33ff7 com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3ea34000 - 0x7fff3eac0fff com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3eaf2000 - 0x7fff3eaf6fff com.apple.xpc.ServiceManagement (1.0 - 1) <5055F807-1DD4-3F97-A2A6-4537F51A5736> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3ee8f000 - 0x7fff3eefcfff com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3f15b000 - 0x7fff3f4bcfff com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff42138000 - 0x7fff421ddfff com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff42bf2000 - 0x7fff42bf3ff7 com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff431f6000 - 0x7fff43222ff7 com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff4334a000 - 0x7fff43359fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff43455000 - 0x7fff43460fff com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff434a1000 - 0x7fff434eaff3 com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff4373e000 - 0x7fff43760fff com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff43824000 - 0x7fff43874ff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <FB127E63-853B-3F00-BE2A-12B4BF6FED33> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff438bf000 - 0x7fff438d3ffb com.apple.AssertionServices (1.0 - 1) <456E507A-4561-3628-9FBE-173ACE7429D8> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43ca2000 - 0x7fff43d8eff7 com.apple.AuthKit (1.0 - 1) <2765ABE9-54F2-3E45-8A93-1261E251B90D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43f50000 - 0x7fff43f58fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43f59000 - 0x7fff43feefff com.apple.backup.framework (1.10.7 - ???) <5243C2BC-0159-3DBB-9FAB-22EA01E58052> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff43fef000 - 0x7fff4405cff3 com.apple.BaseBoard (360.28 - 360.28) <68FA8044-F3CD-3BC6-9DAB-27DACF52BFC0> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff44ebc000 - 0x7fff44f0bff7 com.apple.ChunkingLibrary (201 - 201) <DFE16C42-24E6-386F-AC50-0058F61980A2> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff45cc9000 - 0x7fff45cd2ffb com.apple.CommonAuth (4.0 - 2.0) <93335CB6-ABEB-3EC7-A040-8A667F40D5F3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff4616b000 - 0x7fff4654efef com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff4654f000 - 0x7fff4657dff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff469ab000 - 0x7fff469bcff7 com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff46f66000 - 0x7fff46fccff7 com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff47279000 - 0x7fff47281ff7 com.apple.CorePhoneNumbers (1.0 - 1) <11F97C7E-C183-305F-8E6C-9B374F50E26B> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff473fd000 - 0x7fff4742eff3 com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff477f5000 - 0x7fff47879fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff47909000 - 0x7fff47a34ff7 com.apple.coreui (2.1 - 499.10) <A80F4B09-F940-346F-A9DF-4EFADD9220A8> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff47a35000 - 0x7fff47bd5fff com.apple.CoreUtils (5.9 - 590.16) <BF9A990D-24C0-3633-A753-F19F4DFCA663> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff47c29000 - 0x7fff47c8cff7 com.apple.framework.CoreWiFi (13.0 - 1375.2) <7E9CC352-BB06-3C97-A51F-6A35F09EBA16> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff47c8d000 - 0x7fff47c9eff3 com.apple.CrashReporterSupport (10.13 - 938.29) <8A66F5D5-87D1-31C9-BEAE-86E0735F4E92> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff47d2e000 - 0x7fff47d3dfff com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff47d3e000 - 0x7fff47d42ff7 com.apple.DSExternalDisplay (3.1 - 380) <787B9748-B120-3453-B8FE-61D9E363A9E0> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff47dc3000 - 0x7fff47e38ffb com.apple.datadetectorscore (7.0 - 590.27) <06FB1A07-7AE6-3ADD-8E7E-41955FAB38E8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff47e84000 - 0x7fff47ec1ff7 com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff47ec2000 - 0x7fff47ffdff7 com.apple.desktopservices (1.13.6 - ???) <7536F3F3-90F1-3D1C-9249-91B809FE5328> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff48f44000 - 0x7fff4935ffff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4cc13000 - 0x7fff4cc14fff libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4e2a8000 - 0x7fff4e2b3ff7 libGPUSupportMercury.dylib (17.7.3) <121E8765-3C03-32AB-903E-6B1DD9A4FD4A> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff4e2b4000 - 0x7fff4e2b9fff com.apple.GPUWrangler (3.50.16 - 3.50.16) <1156CF8C-729B-3173-B3CC-00BB17156BCC> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4e647000 - 0x7fff4e66bff3 com.apple.GenerationalStorage (2.0 - 285.101) <84C2E52C-F2C6-3FF8-87E5-3C88A40D3881> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff4f0c5000 - 0x7fff4f0d4fff com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4f23a000 - 0x7fff4f2aeffb com.apple.Heimdal (4.0 - 2.0) <D97FCF19-EAD6-3E2F-BE88-F817E45CAE96> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff505af000 - 0x7fff505b8fff com.apple.IOAccelMemoryInfo (1.0 - 1) <32F6778F-3EB5-36A3-8AF8-55B37A44AC0C> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff505b9000 - 0x7fff505c0ffb com.apple.IOAccelerator (404.15 - 404.15) <06D2C96E-1CF5-3199-A234-9033934D78BF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff505c4000 - 0x7fff505dcfff com.apple.IOPresentment (1.0 - 42.6) <D2BA3A78-21C6-37B8-9F8F-9EC0F30F953F> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff50984000 - 0x7fff509b1ff7 com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff50c44000 - 0x7fff50c56ff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <D5DDE47A-E922-3166-BD7F-E7C3DF360DD9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff50c71000 - 0x7fff50d4cff7 com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff50d4d000 - 0x7fff50d89ff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff50d90000 - 0x7fff50d95fff com.apple.LinguisticData (1.0 - 238.25) <F529B961-098C-3E4C-A3E9-9DA9BFA1B3F0> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff515b4000 - 0x7fff515b7fff com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff51a8b000 - 0x7fff51ab3ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.58) <23E8580B-19C0-3E4F-A9FE-368DA80EAA6F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff51ab4000 - 0x7fff51b41ff7 com.apple.gpusw.MetalTools (1.0 - 1) <9B542958-6363-3041-A265-EC7AC7BD7A43> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff51b58000 - 0x7fff51b71ffb com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff51d3d000 - 0x7fff51d58ffb com.apple.MobileKeyBag (2.0 - 1.0) <39337CBB-1D39-3DDC-A998-591194C76523> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff51de1000 - 0x7fff51e0bffb com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <42A23EC9-64A7-31C7-BF33-DF4412ED8A3F> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff52047000 - 0x7fff52051fff com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff528b3000 - 0x7fff52904ff3 com.apple.OTSVG (1.0 - ???) <CB2F1DBE-0313-30CB-A95F-2FE75E0A089E> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff53a9d000 - 0x7fff53aacff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff5593e000 - 0x7fff5595cff7 com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff55af4000 - 0x7fff55b44fff com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff55ca2000 - 0x7fff55cc4fff com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff574ce000 - 0x7fff575ecfff com.apple.Sharing (1288.62.5 - 1288.62.5) <BB647030-839A-3271-B205-D4325346DD3B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff58401000 - 0x7fff586b0fff com.apple.SkyLight (1.600.0 - 340.55) <1F737945-E242-3F03-A7D6-1A5955AB1298> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff58e54000 - 0x7fff58e60fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff594ff000 - 0x7fff5953bff3 com.apple.StreamingZip (1.0 - 1) <046FAD5C-E0C5-3013-B1FE-24C018A0DDCF> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff595b1000 - 0x7fff5963cfc7 com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff59b22000 - 0x7fff59b2effb com.apple.TCC (1.0 - 1) <E3691073-7284-35E4-94F3-16587A7F380F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff59d94000 - 0x7fff59e5cff3 com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff59f12000 - 0x7fff59f13fff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <15DF9C73-54E4-3C41-BCF4-378338C55FB4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff59f19000 - 0x7fff5a0d1ffb com.apple.UIFoundation (1.0 - 551.5) <A0FDC3A4-45C6-3C87-B77F-7DC394374C08> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff5ad4d000 - 0x7fff5ae26fff com.apple.ViewBridge (406 - 406) <3CC6AE31-2CD7-30CA-982C-47EF242EFA30> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff5b5fe000 - 0x7fff5b601fff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5ba02000 - 0x7fff5ba04ffb com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff5ba05000 - 0x7fff5ba1afff com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff5bcce000 - 0x7fff5bd02fff libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib\n 0x7fff5bd05000 - 0x7fff5bd0fff7 libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff5bd9d000 - 0x7fff5bd9effb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff5bdd5000 - 0x7fff5c02cff3 libFosl_dynamic.dylib (18.3.4) <1B5DD4E2-8AE0-315E-829E-D5BFCD264EA8> /usr/lib/libFosl_dynamic.dylib\n 0x7fff5c07d000 - 0x7fff5c09cfff libMobileGestalt.dylib (645.270.1) <99A06C8A-97D6-383D-862C-F453BABB48A4> /usr/lib/libMobileGestalt.dylib\n 0x7fff5c09d000 - 0x7fff5c09dfff libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff5c1dd000 - 0x7fff5c1deffb libSystem.B.dylib (1252.250.1) <C7A55258-8EB2-3202-82B5-AA56E53EE2DA> /usr/lib/libSystem.B.dylib\n 0x7fff5c25a000 - 0x7fff5c25bfff libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib\n 0x7fff5c26d000 - 0x7fff5c283ffb libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib\n 0x7fff5c284000 - 0x7fff5c2adffb libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib\n 0x7fff5c2ae000 - 0x7fff5c32dfff libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib\n 0x7fff5c331000 - 0x7fff5c331ff3 libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib\n 0x7fff5c403000 - 0x7fff5c413ffb libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib\n 0x7fff5c414000 - 0x7fff5c421fff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib\n 0x7fff5c422000 - 0x7fff5c475ff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib\n 0x7fff5c476000 - 0x7fff5c48bff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib\n 0x7fff5c48c000 - 0x7fff5c48cff3 libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib\n 0x7fff5c48d000 - 0x7fff5c49dffb libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib\n 0x7fff5c49e000 - 0x7fff5c4b6ffb libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib\n 0x7fff5c72b000 - 0x7fff5c741fff libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib\n 0x7fff5c742000 - 0x7fff5c743ff3 libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff5c8e1000 - 0x7fff5c9d9ff7 libcrypto.35.dylib (22.260.1) <91C3D71A-4D1D-331D-89CC-67863DF10574> /usr/lib/libcrypto.35.dylib\n 0x7fff5cbef000 - 0x7fff5cc45ff3 libcups.2.dylib (462.16) <E82021D0-36AD-3FB7-AE47-A03A6947C7D0> /usr/lib/libcups.2.dylib\n 0x7fff5cd79000 - 0x7fff5cd79fff libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib\n 0x7fff5cdab000 - 0x7fff5cdb0ff7 libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib\n 0x7fff5cdb1000 - 0x7fff5cdb6ff7 libheimdal-asn1.dylib (520.270.1) <73F60D6F-76F8-35EF-9C86-9A81225EE4BE> /usr/lib/libheimdal-asn1.dylib\n 0x7fff5cde1000 - 0x7fff5ced1fff libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib\n 0x7fff5ced2000 - 0x7fff5d133ffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib\n 0x7fff5d180000 - 0x7fff5d181fff liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib\n 0x7fff5d182000 - 0x7fff5d19aff3 liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib\n 0x7fff5d1b2000 - 0x7fff5d256ff7 libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5d257000 - 0x7fff5d45bfff libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib\n 0x7fff5d633000 - 0x7fff5d984ff7 libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib\n 0x7fff5da16000 - 0x7fff5e19bfdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib\n 0x7fff5e1ad000 - 0x7fff5e1b1ffb libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib\n 0x7fff5e1b4000 - 0x7fff5e1e9fff libpcap.A.dylib (79.250.3) <97B8CE1B-3EF6-3443-95EF-5659733139C9> /usr/lib/libpcap.A.dylib\n 0x7fff5e302000 - 0x7fff5e31affb libresolv.9.dylib (65.200.3) <1FB0982D-84D9-36E0-B3D8-C808891EFF50> /usr/lib/libresolv.9.dylib\n 0x7fff5e36b000 - 0x7fff5e36cff7 libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib\n 0x7fff5e36d000 - 0x7fff5e54afff libsqlite3.dylib (274.26) <6404BA3B-BCA4-301F-B2FE-8776105A2AA3> /usr/lib/libsqlite3.dylib\n 0x7fff5e763000 - 0x7fff5e766ff7 libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib\n 0x7fff5e767000 - 0x7fff5e774fff libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib\n 0x7fff5e779000 - 0x7fff5e85cfff libxml2.2.dylib (32.19) <E07AB10E-E2E6-33F2-8550-C24A0EB8FEAC> /usr/lib/libxml2.2.dylib\n 0x7fff5e85d000 - 0x7fff5e885ff3 libxslt.1.dylib (16.7.1) <4A5CB7D5-50F8-36BF-8A80-D526C57EB5D9> /usr/lib/libxslt.1.dylib\n 0x7fff5e886000 - 0x7fff5e898ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib\n 0x7fff5f07c000 - 0x7fff5f080ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib\n 0x7fff5f081000 - 0x7fff5f08bff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5f08c000 - 0x7fff5f093ff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5f094000 - 0x7fff5f09dff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib\n 0x7fff5f09e000 - 0x7fff5f122fc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5f1a9000 - 0x7fff5f1e2ff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib\n 0x7fff5f1e3000 - 0x7fff5f20fff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib\n 0x7fff5f210000 - 0x7fff5f210ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib\n 0x7fff5f211000 - 0x7fff5f21dff3 libkxld.dylib (4903.278.56) <A3FF22FA-4AD4-3FF3-9891-B34482DC8572> /usr/lib/system/libkxld.dylib\n 0x7fff5f21e000 - 0x7fff5f21eff7 liblaunch.dylib (1336.261.6) <1F0EEC6F-4D08-38E6-ACF9-6E44D328931F> /usr/lib/system/liblaunch.dylib\n 0x7fff5f21f000 - 0x7fff5f224fff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib\n 0x7fff5f225000 - 0x7fff5f227ff7 libquarantine.dylib (86.270.1) <3F36A3D6-9606-3D90-B520-809BAEF981C3> /usr/lib/system/libquarantine.dylib\n 0x7fff5f228000 - 0x7fff5f229ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib\n 0x7fff5f22a000 - 0x7fff5f241ff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5f242000 - 0x7fff5f242ff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5f243000 - 0x7fff5f2cafff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib\n 0x7fff5f2cb000 - 0x7fff5f2ceffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5f2cf000 - 0x7fff5f2d2ff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5f2d3000 - 0x7fff5f2d9fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5f2da000 - 0x7fff5f2e0ffb libsystem_dnssd.dylib (878.270.3) <D5352ABD-0311-3327-8E64-93F29EB19BF1> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5f2e1000 - 0x7fff5f32cffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib\n 0x7fff5f32d000 - 0x7fff5f355ff7 libsystem_kernel.dylib (4903.278.56) <5B0F1BF0-E2F4-3753-87B6-6F91C594F59E> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5f356000 - 0x7fff5f3a1ff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib\n 0x7fff5f3a2000 - 0x7fff5f3ccfff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5f3cd000 - 0x7fff5f3d7ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5f3d8000 - 0x7fff5f3dffff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5f3e0000 - 0x7fff5f3e9fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5f3ea000 - 0x7fff5f3f4ff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5f3f5000 - 0x7fff5f3f8ff7 libsystem_sandbox.dylib (851.270.5) <20D11F30-783F-3A56-9BD2-6CF38C049332> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5f3f9000 - 0x7fff5f3fbff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5f3fc000 - 0x7fff5f403ff3 libsystem_symptoms.dylib (820.267.2) <0DA60956-0403-3456-9D6A-11F2DB9E3819> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5f404000 - 0x7fff5f419ff7 libsystem_trace.dylib (906.260.3) <5B6FAE61-EF5C-381F-B71B-9B6F6428FEE2> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5f41b000 - 0x7fff5f420ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib\n 0x7fff5f421000 - 0x7fff5f450fff libxpc.dylib (1336.261.6) <522FA3AF-D3B1-3283-8EF4-8B17CB237B65> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 1047\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 76643460\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=750.3M resident=0K(0%) swapped_out_or_unallocated=750.3M(100%)\nWritable regions: Total=1.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.9G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 3 \nActivity Tracing 256K 1 \nCG backing stores 1320K 2 \nCG image 380K 11 \nCoreAnimation 328K 10 \nCoreGraphics 8K 1 \nCoreImage 32K 4 \nCoreUI image data 704K 8 \nCoreUI image file 540K 5 \nFoundation 4K 1 \nImage IO 256K 1 \nKernel Alloc Once 8K 1 \nMALLOC 868.0M 567 \nMALLOC guard page 32K 7 \nMALLOC_LARGE (reserved) 128K 1 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nMemory Tag 242 12K 1 \nMemory Tag 249 192K 2 \nOpenGL GLSL 256K 3 \nSTACK GUARD 92K 23 \nStack 36.7M 23 \nVM_ALLOCATE 524.9M 572 \nVM_ALLOCATE (reserved) 128.0M 2 reserved VM address space (unallocated)\n__DATA 120.0M 333 \n__DATA_CONST 20K 1 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 283.5M 85 \n__TEXT 467.0M 320 \n__UNICODE 564K 1 \nmapped file 79.5M 26 \nshared memory 4276K 12 \n=========== ======= ======= \nTOTAL 2.8G 2030 \nTOTAL, minus reserved VM space 2.3G 2030 \n\nModel: MacBookPro13,3, BootROM 429.80.1.0.0, 4 processors, Intel Core i7, 2,9 GHz, 16 GB, SMC 2.38f7\nGraphics: kHW_AMDRadeonPro460Item, AMD Radeon Pro 460, spdisplays_pcie_device, 4 GB\nGraphics: kHW_IntelHDGraphics530Item, Intel HD Graphics 530, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nMemory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)\nBluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.0 Bus\nUSB Device: Wacom Wireless Receiver\nUSB Device: iBridge\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\n```\n\nCrash Log 2:\n```lines=25\nProcess: Blender [4923]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.92.0 (2.92.0 2021-02-25)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [4923]\nUser ID: 501\n\nDate/Time: 2021-03-14 13:37:52.807 +0100\nOS Version: macOS 11.2.3 (20D91)\nReport Version: 12\nBridge OS Version: 5.2 (18P4347)\nAnonymous UUID: B5FE06B1-F2A1-95FF-0593-1738C46F37D4\n\nSleep/Wake UUID: CBAA4D96-6C0A-4683-B5C6-D788FF799225\n\nTime Awake Since Boot: 65000 seconds\nTime Since Wake: 5700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000024\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [4923]\n\nVM Regions Near 0x24:\n--> \n __TEXT 10016f000-10ab5b000 [169.9M] r-x/r-x SM=COW /Applications/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff6cc64690 gleRunVertexSubmitImmediate + 5632\n1 GLEngine \t0x00007fff6cbeb197 glDrawElementsInstancedBaseVertex_GL3Exec + 807\n2 libGL.dylib \t0x00007fff6cb323cf glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x0000000100808ec5 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010080864c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x0000000100807f9f DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x0000000100832048 workbench_draw_sample + 344\n7 org.blenderfoundation.blender \t0x000000010083229c workbench_draw_scene + 76\n8 org.blenderfoundation.blender \t0x00000001007ff33a drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x00000001007fde5d DRW_draw_render_loop_ex + 1565\n10 org.blenderfoundation.blender \t0x00000001007ff5db DRW_draw_render_loop_offscreen + 155\n11 org.blenderfoundation.blender \t0x000000010111d058 ED_view3d_draw_offscreen + 808\n12 org.blenderfoundation.blender \t0x000000010111d834 ED_view3d_draw_offscreen_imbuf + 692\n13 org.blenderfoundation.blender \t0x000000010111db64 ED_view3d_draw_offscreen_imbuf_simple + 628\n14 org.blenderfoundation.blender \t0x00000001006e6876 wm_save_as_mainfile_exec + 1974\n15 org.blenderfoundation.blender \t0x00000001006e6cb1 wm_save_mainfile_invoke + 289\n16 org.blenderfoundation.blender \t0x00000001006e0bd9 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x00000001006e216c wm_handler_operator_call + 636\n18 org.blenderfoundation.blender \t0x00000001006e1836 wm_handlers_do_intern + 1782\n19 org.blenderfoundation.blender \t0x00000001006dcdbf wm_handlers_do + 31\n20 org.blenderfoundation.blender \t0x00000001006dca1d wm_event_do_handlers + 3373\n21 org.blenderfoundation.blender \t0x00000001006d5360 WM_main + 32\n22 org.blenderfoundation.blender \t0x00000001002b3b8b main + 907\n23 libdyld.dylib \t0x00007fff203ca621 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 17:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff284ad92a caulk::mach::semaphore::wait_or_error() + 16\n2 com.apple.audio.caulk \t0x00007fff2849a6e6 caulk::semaphore::timed_wait(double) + 110\n3 com.apple.audio.caulk \t0x00007fff2849a634 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff2849a3c0 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 18:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff21e9edd5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff21d3a467 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 3435\n4 com.apple.audio.CoreAudio \t0x00007fff21eddf2a HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 34:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff204a7bf7 __CFRunLoopServiceMachPort + 316\n3 com.apple.CoreFoundation \t0x00007fff204a62ca __CFRunLoopRun + 1315\n4 com.apple.CoreFoundation \t0x00007fff204a56ce CFRunLoopRunSpecific + 563\n5 com.apple.AppKit \t0x00007fff22e4b7c6 _NSEventThread + 124\n6 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n7 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 35:: Dispatch queue: com.apple.opengl.cvmDoWork\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 libdispatch.dylib \t0x00007fff2021a776 _dispatch_mach_send_and_wait_for_reply + 518\n3 libdispatch.dylib \t0x00007fff2021ab6e dispatch_mach_send_with_result_and_wait_for_reply + 50\n4 libxpc.dylib \t0x00007fff200f11ac xpc_connection_send_message_with_reply_sync + 238\n5 libCoreVMClient.dylib \t0x00007fff6c90670a cvms_element_build_and_get_internal + 229\n6 libCoreVMClient.dylib \t0x00007fff6c90660e cvms_element_build_from_source + 169\n7 libCVMSPluginSupport.dylib \t0x00007fff6c91bf14 cvm_deferred_build_modular(void*) + 422\n8 libdispatch.dylib \t0x00007fff202047c7 _dispatch_client_callout + 8\n9 libdispatch.dylib \t0x00007fff2020a5fe _dispatch_lane_serial_drain + 606\n10 libdispatch.dylib \t0x00007fff2020b0cb _dispatch_lane_invoke + 375\n11 libdispatch.dylib \t0x00007fff20214c5d _dispatch_workloop_worker_thread + 819\n12 libsystem_pthread.dylib \t0x00007fff203ac499 _pthread_wqthread + 314\n13 libsystem_pthread.dylib \t0x00007fff203ab467 start_wqthread + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 39:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 40:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000024 rbx: 0x00000c3300041000 rcx: 0x00007fff6cc64690 rdx: 0x00007fff6cc65ae8\n rdi: 0x0000000000000006 rsi: 0x0000000000000000 rbp: 0x00007ffeefa8dce0 rsp: 0x00007ffeefa8db50\n r8: 0x0000000000000001 r9: 0x0000600003844bf0 r10: 0x0000000000000001 r11: 0x0000000186600082\n r12: 0x0000000000000000 r13: 0x0000000000000003 r14: 0x0000000000000000 r15: 0x00000c3300041000\n rip: 0x00007fff6cc64690 rfl: 0x0000000000010217 cr2: 0x0000000000000024\n \nLogical CPU: 0\nError Code: 0x00000004 (no mapping for user data read)\nTrap Number: 14\n\nThread 0 instruction stream:\n ff 48 8b 8d 28 ff ff ff-48 8b 44 01 08 e9 b6 f7 .H..(...H.D.....\n ff ff 85 d2 0f 84 84 00-00 00 49 89 fd be 00 00 ..........I.....\n 80 38 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 40 00 .8f...........@.\n 89 d7 8d 14 3f 81 c6 00-00 80 ff f7 c7 00 02 00 ....?...........\n 00 74 ed 81 e2 fe 03 00-00 4c 89 ef 4c 8b ad 08 .t.......L..L...\n ff ff ff eb 4d c1 e6 0d-81 c6 00 00 00 38 eb 42 ....M........8.B\n [8b]08 89 8d 30 ff ff ff-8b 48 04 89 8d 34 ff ff ....0....H...4..\t<==\n ff e9 bc f9 ff ff 8b 08-89 8d 30 ff ff ff 8b 48 ..........0....H\n 04 89 8d 34 ff ff ff 8b-48 08 89 8d 38 ff ff ff ...4....H...8...\n 8b 40 0c 89 85 3c ff ff-ff e9 42 05 00 00 31 f6 .@...<....B...1.\n 31 d2 c1 e2 0d 09 f2 09-ca 89 95 30 ff ff ff 41 1..........0...A\n 83 fd 02 0f 82 e0 03 00-00 0f b7 70 02 89 f1 c1 ...........p....\n \nThread 0 last branch register state not available.\n\n\nBinary Images:\n 0x10016f000 - 0x10ab5afff +org.blenderfoundation.blender (2.92.0 - 2.92.0 2021-02-25) <F92572D3-A6D1-3A9C-9F23-72D19FC8242A> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11191c000 - 0x111988fff +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x1186b5000 - 0x118818fff com.apple.audio.units.Components (1.14 - 1.14) <8C3B07AD-A96B-383A-94DC-902CCE4CD511> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11886d000 - 0x11887cfff libobjc-trampolines.dylib (818.2) <29187EF9-2BD6-3ABF-8088-DE708721B612> /usr/lib/libobjc-trampolines.dylib\n 0x118c6b000 - 0x118d06fff dyld (832.7.3) <0D4EA85F-7E30-338B-9215-314A5A5539B6> /usr/lib/dyld\n 0x118d83000 - 0x119332fff com.apple.audio.AudioDSPComponents (1.0 - 1) <1A7FCA3F-190C-32F0-A48D-1524A11B0910> /System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP\n 0x119963000 - 0x119ce2fff com.apple.AMDRadeonX6000MTLDriver (4.2.15 - 4.0.2) <56DBFC8D-9ABB-34AE-873F-CAF3E6A184D5> /System/Library/Extensions/AMDRadeonX6000MTLDriver.bundle/Contents/MacOS/AMDRadeonX6000MTLDriver\n 0x11a0ab000 - 0x11a1fefff com.apple.AMDRadeonX6000GLDriver (4.2.15 - 4.0.2) <6A663F3B-05F2-35F1-9832-C0E3645C7E08> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/AMDRadeonX6000GLDriver\n 0x127eb0000 - 0x127eb1fff +_heapq.cpython-37m-darwin.so (0) <20086BF0-0130-3463-B824-F98C6D51BE39> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x1280ba000 - 0x1280bffff +math.cpython-37m-darwin.so (0) <F76ADA60-2AAA-34A7-BB31-26405F501673> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x128fe4000 - 0x128fe7fff com.apple.CloudDocsFileProvider (1.0 - 726.1) <AB47EF12-834C-3720-BEE5-22E11638BFB7> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x128ff8000 - 0x128ffbfff com.apple.FileProviderOverride (326.3 - 326.3) <54B6F621-7F46-3223-A227-C0757EB3F900> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x12900c000 - 0x129027fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1350.2.10) <EDD7E1EC-AB15-3496-9A57-237C9D3A2CEB> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff200e4000 - 0x7fff200e5fff libsystem_blocks.dylib (78) <E644CAA0-65B7-36E4-8041-520F3301F3DB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff200e6000 - 0x7fff2011bfff libxpc.dylib (2038.80.3) <70F26262-01AA-3CEC-9FAD-2701D24096F0> /usr/lib/system/libxpc.dylib\n 0x7fff2011c000 - 0x7fff20133fff libsystem_trace.dylib (1277.80.2) <87FEF600-48D9-31C9-B8FC-D5249B2AE95D> /usr/lib/system/libsystem_trace.dylib\n 0x7fff20134000 - 0x7fff201d3fff libcorecrypto.dylib (1000.80.5) <1EB11CFB-ABD7-36DD-97C7-C112A6601416> /usr/lib/system/libcorecrypto.dylib\n 0x7fff201d4000 - 0x7fff20200fff libsystem_malloc.dylib (317.40.8) <A498D1EF-E43D-310C-84E8-9C0AADA0C475> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff20201000 - 0x7fff20245fff libdispatch.dylib (1271.40.12) <AD988EEA-1A2F-3404-9A6E-390FC2504223> /usr/lib/system/libdispatch.dylib\n 0x7fff20246000 - 0x7fff2027efff libobjc.A.dylib (818.2) <EB6B543F-D42C-3FB2-A2EC-43407C5F80D3> /usr/lib/libobjc.A.dylib\n 0x7fff2027f000 - 0x7fff20281fff libsystem_featureflags.dylib (28.60.1) <9CECB43A-094E-3CA9-B730-24DEA1A6DE05> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff20282000 - 0x7fff2030afff libsystem_c.dylib (1439.40.11) <4AF71812-4099-3E96-B271-1F259491A2B2> /usr/lib/system/libsystem_c.dylib\n 0x7fff2030b000 - 0x7fff20360fff libc++.1.dylib (904.4) <B217D905-4F9C-3DE0-8844-88FAA3C2C851> /usr/lib/libc++.1.dylib\n 0x7fff20361000 - 0x7fff20379fff libc++abi.dylib (904.4) <3C9FE530-3CD2-3A64-8A36-70816AEBDF0D> /usr/lib/libc++abi.dylib\n 0x7fff2037a000 - 0x7fff203a8fff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff203a9000 - 0x7fff203b4fff libsystem_pthread.dylib (454.80.2) <B989DF6C-ADFE-3AF9-9C91-07D2521F9E47> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff203b5000 - 0x7fff203effff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib\n 0x7fff203f0000 - 0x7fff203f9fff libsystem_platform.dylib (254.80.2) <1C3E1A0A-92A8-3CDE-B622-8940B43A5DF2> /usr/lib/system/libsystem_platform.dylib\n 0x7fff203fa000 - 0x7fff20425fff libsystem_info.dylib (542.40.3) <0C96CFE8-71F5-3335-8423-581BC3DE5846> /usr/lib/system/libsystem_info.dylib\n 0x7fff20426000 - 0x7fff208c1fff com.apple.CoreFoundation (6.9 - 1774.101) <2A0E160E-9EE6-3B23-8832-6979A16EC250> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff208c2000 - 0x7fff20af1fff com.apple.LaunchServices (1122.11 - 1122.11) <9ACD5692-3B92-3E6E-8B24-56ADCC911556> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff20af2000 - 0x7fff20bc5fff com.apple.gpusw.MetalTools (1.0 - 1) <B1FDD261-7707-3E20-A6C2-99D9AF46356B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff20bc6000 - 0x7fff20e29fff libBLAS.dylib (1336.40.1) <92702864-A5C6-3E22-86F6-DB329532674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff20e2a000 - 0x7fff20e77fff com.apple.Lexicon-framework (1.0 - 86.1) <2F429EBD-1BD2-3057-B760-8A81546DBD6F> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff20e78000 - 0x7fff20ee6fff libSparse.dylib (106) <B889DE4E-7356-3CC8-A13E-68D15E2024DF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff20ee7000 - 0x7fff20f64fff com.apple.SystemConfiguration (1.20 - 1.20) <3518EA0E-C32D-32CC-81B9-0F3C83B6430C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff20f65000 - 0x7fff20f9afff libCRFSuite.dylib (50) <970D1F7B-5DBD-355F-80D8-C820AA1626D2> /usr/lib/libCRFSuite.dylib\n 0x7fff20f9b000 - 0x7fff211d2fff libmecabra.dylib (929.1.1) <102A0AD8-D119-340B-B652-B75F0AAB1C7E> /usr/lib/libmecabra.dylib\n 0x7fff211d3000 - 0x7fff21536fff com.apple.Foundation (6.9 - 1774.101) <8D9081B3-3F6A-31A0-9B20-1AE5CD8DD747> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff21537000 - 0x7fff21623fff com.apple.LanguageModeling (1.0 - 247.1) <1A05BCD7-232F-3950-936D-EC0F95BA3FB0> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff21624000 - 0x7fff2175afff com.apple.CoreDisplay (231.3 - 231.3) <6DD6A260-800F-3284-842C-8E4CB9EA47FF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2175b000 - 0x7fff219d1fff com.apple.audio.AudioToolboxCore (1.0 - 1180.25) <DEE2C5BA-BFD1-349F-A10A-B10717BA8F7C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff219d2000 - 0x7fff21bbafff com.apple.CoreText (677.3.0.4 - 677.3.0.4) <9A8DC9A0-1A80-3A26-ACA0-A245D3FFF921> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff21bbb000 - 0x7fff2225ffff com.apple.audio.CoreAudio (5.0 - 5.0) <801E2D1E-7EA5-37DA-8F44-B6D7DD3CE5B9> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff22260000 - 0x7fff225b1fff com.apple.security (7.0 - 59754.80.3) <B377D7C7-EDB6-3737-B492-E9872F4C6469> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff225b2000 - 0x7fff22813fff libicucore.A.dylib (66109) <8F8D8A8B-4EE0-3C09-9F45-725A1FBDD38C> /usr/lib/libicucore.A.dylib\n 0x7fff22814000 - 0x7fff2281dfff libsystem_darwin.dylib (1439.40.11) <E016D8F7-C87F-36F8-B8A0-6A61B8E4BACB> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff2281e000 - 0x7fff22b05fff com.apple.CoreServices.CarbonCore (1307 - 1307) <B857EADF-D517-34E8-8053-34C0E6695250> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff22b06000 - 0x7fff22b44fff com.apple.CoreServicesInternal (476 - 476) <0DA95074-B315-3B84-B8A3-BAEDC4471A2C> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff22b45000 - 0x7fff22b7ffff com.apple.CSStore (1122.11 - 1122.11) <89992991-8538-380B-B2B8-4EA997CBFDBE> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff22b80000 - 0x7fff22c2efff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <49AC0177-35A3-3C96-AD9D-3E59923C4761> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff22c2f000 - 0x7fff22c3afff libsystem_notify.dylib (279.40.4) <B2BF20C7-448A-3FBD-A2F5-AB7618D173F6> /usr/lib/system/libsystem_notify.dylib\n 0x7fff22c3b000 - 0x7fff22c86fff libsandbox.1.dylib (1441.60.4) <591F41F3-1FE9-354F-A1F9-BC0CC73333DA> /usr/lib/libsandbox.1.dylib\n 0x7fff22c87000 - 0x7fff239e9fff com.apple.AppKit (6.9 - 2022.30.122) <EA4B3536-A5AF-3E5D-A8E3-A3F795F34F05> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff239ea000 - 0x7fff23c3efff com.apple.UIFoundation (1.0 - 727.3) <5A905085-B5EB-3F71-A663-200428E7A5F4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff23c3f000 - 0x7fff23c51fff com.apple.UniformTypeIdentifiers (633.0.2 - 633.0.2) <2AAE247F-1BA0-3E42-A07B-CBE413747B30> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers\n 0x7fff23c52000 - 0x7fff23ddcfff com.apple.desktopservices (1.18 - 1346.3.1) <2144B85E-A433-3F9E-A25D-E8F9D7B6D175> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff23ddd000 - 0x7fff23deffff com.apple.metadata.SpotlightLinguistics (1.0 - 1) <7FC34645-4185-3382-8813-9780C822BB15> /System/Library/PrivateFrameworks/SpotlightLinguistics.framework/Versions/A/SpotlightLinguistics\n 0x7fff240a9000 - 0x7fff246ecfff libnetwork.dylib (2288.80.2) <A3F1E999-6D61-32D7-B3F7-67832CEA53CD> /usr/lib/libnetwork.dylib\n 0x7fff246ed000 - 0x7fff24b8afff com.apple.CFNetwork (1220.1 - 1220.1) <04A917FB-DBFB-3432-BA4C-5B860990A420> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff24b8b000 - 0x7fff24b99fff libsystem_networkextension.dylib (1295.80.3) <5213D866-7D0E-3FD9-8E1A-03C0E39CEC44> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff24b9a000 - 0x7fff24b9afff libenergytrace.dylib (22) <33A9FBF3-A2D3-3ECE-9370-B0ADDE3896DE> /usr/lib/libenergytrace.dylib\n 0x7fff24b9b000 - 0x7fff24bf6fff libMobileGestalt.dylib (978.80.1) <C4C7A5DC-C3AD-374D-902A-B6DED14FBB67> /usr/lib/libMobileGestalt.dylib\n 0x7fff24bf7000 - 0x7fff24c0dfff libsystem_asl.dylib (385) <5B48071E-85EB-33B0-AE9B-127AEB398AEC> /usr/lib/system/libsystem_asl.dylib\n 0x7fff24c0e000 - 0x7fff24c25fff com.apple.TCC (1.0 - 1) <2F48471B-68F3-3017-8B18-BEDD4ED5853F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff24c26000 - 0x7fff24f8cfff com.apple.SkyLight (1.600.0 - 570.7) <8034EAA7-787C-3A3E-A301-FF90376F247D> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff24f8d000 - 0x7fff25620fff com.apple.CoreGraphics (2.0 - 1463.3.2) <29845645-F6F2-34E0-AC0D-C659773C78ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff25621000 - 0x7fff25717fff com.apple.ColorSync (4.13.0 - 3473.3.1) <A67D9B0A-E9FB-325A-873B-032DAF45C112> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff25718000 - 0x7fff25773fff com.apple.HIServices (1.22 - 714) <780B2B09-80A6-32C8-B9E5-024988196E00> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff25b1f000 - 0x7fff25f3dfff com.apple.CoreData (120 - 1044.3) <7BE9684B-4439-3008-A2A7-4093BBCA180A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff25f3e000 - 0x7fff25f54fff com.apple.ProtocolBuffer (1 - 285.23.11.29.1) <58CD91DC-64A9-3A97-AE41-6EA30308D617> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff25f55000 - 0x7fff26114fff libsqlite3.dylib (321.1) <ACCC6A4C-3257-38A4-8AFB-BA73D906205B> /usr/lib/libsqlite3.dylib\n 0x7fff26115000 - 0x7fff26191fff com.apple.Accounts (113 - 113) <BCB8494A-A340-30A1-928C-9B53E953328D> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff26192000 - 0x7fff261aafff com.apple.commonutilities (8.0 - 900) <8C96D016-2B40-39C0-A51C-9CF687AE7218> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff261ab000 - 0x7fff2622cfff com.apple.BaseBoard (526 - 526) <3A964BB6-7AB8-3B5D-BAF6-40F56D2BA393> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff2622d000 - 0x7fff26278fff com.apple.RunningBoardServices (1.0 - 505.80.1) <4B9FFFB3-310F-350A-BEBB-AB779BD3F405> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff26279000 - 0x7fff262eefff com.apple.AE (918.0.1 - 918.0.1) <9B6B42DB-8768-343B-B10E-A9A5710280CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff262ef000 - 0x7fff262f5fff libdns_services.dylib (1310.80.1) <97EB5DFD-BB41-3834-BF09-1F597D84F324> /usr/lib/libdns_services.dylib\n 0x7fff262f6000 - 0x7fff262fdfff libsystem_symptoms.dylib (1431.40.36) <BC85B46C-02EE-31FF-861D-F0DE01E8F6CF> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff262fe000 - 0x7fff26482fff com.apple.Network (1.0 - 1) <75C2713C-F0D8-32BA-A839-17A2AE49A061> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff26483000 - 0x7fff264a7fff com.apple.analyticsd (1.0 - 1) <4FFF906A-FE79-38F9-B777-AE878A0C99F1> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff264a8000 - 0x7fff264aafff libDiagnosticMessagesClient.dylib (112) <20EDB261-69C7-3E4A-8C00-878814186A62> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff264ab000 - 0x7fff264f7fff com.apple.spotlight.metadata.utilities (1.0 - 2150.7.5) <FB7BF527-2D95-3E82-AAD8-D42B33DAC0F0> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff264f8000 - 0x7fff26592fff com.apple.Metadata (10.7.0 - 2150.7.5) <49187239-597B-31A1-8895-8AA265C818C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff26593000 - 0x7fff26599fff com.apple.DiskArbitration (2.7 - 2.7) <ACFCD23E-05DF-3F96-BCFA-E294AAAFD2CE> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2659a000 - 0x7fff26c40fff com.apple.vImage (8.1 - 544.2) <3EBF95E1-30EB-3162-A9D4-B97BE581B69F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff26c41000 - 0x7fff26f0bfff com.apple.QuartzCore (1.11 - 926.8) <04D8759B-1119-3E37-B922-32BDECB7C5D2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff26f0c000 - 0x7fff26f4dfff libFontRegistry.dylib (309) <9E9329F6-7384-3C7F-83E7-D52CD7FFBC09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff26f4e000 - 0x7fff2708ffff com.apple.coreui (2.1 - 690) <6DB427BB-44CA-3002-A3FF-77F0FEFC2A51> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff27090000 - 0x7fff2717bfff com.apple.ViewBridge (551.3 - 551.3) <9F31CEDB-5B8A-3BAE-A638-E9F352EF4E87> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff2717c000 - 0x7fff27187fff com.apple.PerformanceAnalysis (1.275 - 275) <2E5E666D-EE93-3949-8C76-692FA748D129> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff27188000 - 0x7fff27197fff com.apple.OpenDirectory (11.2 - 230.40.1) <333A7F2E-0F3E-37F1-9E1B-69996F5084D2> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff27198000 - 0x7fff271b7fff com.apple.CFOpenDirectory (11.2 - 230.40.1) <25F138F8-9E55-3749-8271-0FDB275C3E2C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff271b8000 - 0x7fff271c0fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <6B70B98B-BCC5-3FBE-A6B5-CD0696AA055A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff271c1000 - 0x7fff271e5fff com.apple.coreservices.SharedFileList (144 - 144) <C861FAD6-D3A5-302C-88AE-B2813F7201A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff271e6000 - 0x7fff271e8fff libapp_launch_measurement.dylib (14.1) <2BBB708C-4D91-364E-ABD0-39BF198688A6> /usr/lib/libapp_launch_measurement.dylib\n 0x7fff271e9000 - 0x7fff27231fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <7A2E42E6-3AF2-3ECB-8A16-5C4AC41206EE> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout\n 0x7fff27232000 - 0x7fff27314fff libxml2.2.dylib (34.9) <E0BF29C7-869B-3DD5-82AE-F36E6398091A> /usr/lib/libxml2.2.dylib\n 0x7fff27315000 - 0x7fff27361fff com.apple.CoreVideo (1.8 - 408.4) <50857F8D-C7CC-3609-B0DB-FC3C7382243B> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff27362000 - 0x7fff27364fff com.apple.loginsupport (1.0 - 1) <B149BCAF-854C-3820-809D-15C6077FFB8B> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff27365000 - 0x7fff2738dfff com.apple.aps.framework (4.0 - 4.0) <D86ED827-F22D-3A52-B055-251478B29AE1> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService\n 0x7fff2738e000 - 0x7fff273abfff com.apple.UserManagement (1.0 - 1) <B6B35079-3860-384F-B7A2-584192BAAE70> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff273ac000 - 0x7fff2754bfff com.apple.cloudkit.CloudKit (970 - 970) <58BD254C-AAF1-3CC5-AAB7-2EF0A70BA033> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit\n 0x7fff2754c000 - 0x7fff275cefff com.apple.CloudDocs (1.0 - 726.1) <EDBE33B4-1629-3323-902F-F6DABE66D552> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff282c8000 - 0x7fff28345fff com.apple.corelocation (2420.12.16 - 2420.12.16) <8BD49018-78D4-3A81-88AD-47DE1A8E3BFE> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation\n 0x7fff28346000 - 0x7fff28356fff libsystem_containermanager.dylib (318.80.2) <6F08275F-B912-3D8E-9D74-4845158AE4F3> /usr/lib/system/libsystem_containermanager.dylib\n 0x7fff28357000 - 0x7fff28368fff com.apple.IOSurface (289.3 - 289.3) <029C5E16-2E04-3E98-BE25-CC8BAE5E3D19> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff28369000 - 0x7fff28371fff com.apple.IOAccelerator (439.52 - 439.52) <41EDF102-E1B5-3FBA-A74A-6C583CAA5D24> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff28372000 - 0x7fff28497fff com.apple.Metal (244.32.7 - 244.32.7) <829B9C4D-2DB6-38C9-9FE8-E6544FB3BDCC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff28498000 - 0x7fff284b4fff com.apple.audio.caulk (1.0 - 70) <3FFEB564-C7CC-3F3E-B193-3F4E7B7C6764> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff284b5000 - 0x7fff2859efff com.apple.CoreMedia (1.0 - 2765.6.4.2) <8E50C806-C6A2-3B96-B3D2-DA1FFC73D2A8> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2859f000 - 0x7fff286fbfff libFontParser.dylib (305.3.0.1) <2CD3B3C9-7022-34DD-BF53-D48D79DEF726> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff286fc000 - 0x7fff289fbfff com.apple.HIToolbox (2.1.1 - 1061.2) <82B316E1-E47F-334D-8C33-DB1B7E8A4F71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff289fc000 - 0x7fff28a0ffff com.apple.framework.DFRFoundation (1.0 - 265) <4B26DB42-BFDD-3B0D-8966-3D0926A3A5B7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff28a10000 - 0x7fff28a13fff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <D279B67B-7108-3A16-93E5-5A429B898DAA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff28a14000 - 0x7fff28a3dfff com.apple.CoreSVG (1.0 - 149) <D88B5A7D-F9F7-36C2-A346-87D7163605A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff28a3e000 - 0x7fff28c78fff com.apple.ImageIO (3.3.0 - 2130.3.5) <3558ABA9-6522-36A8-A49D-8641A9D7FCE1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff28c79000 - 0x7fff28ff6fff com.apple.CoreImage (16.2.0 - 1130.1) <29BE82F7-93BE-336A-AF66-9DD3F48B8565> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff28ff7000 - 0x7fff29052fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <287C79B5-4E13-3DF6-BDC4-439EC621E010> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff29053000 - 0x7fff29056fff libsystem_configuration.dylib (1109.60.2) <4917D824-4DE8-32CC-9ED2-1FBF371FEB9F> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff29057000 - 0x7fff2905bfff libsystem_sandbox.dylib (1441.60.4) <5F7F3DD1-4B38-310C-AA8F-19FF1B0F5276> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff2905c000 - 0x7fff2905dfff com.apple.AggregateDictionary (1.0 - 1) <E6C1A91D-4ADE-33CB-AA47-2F573811BFD9> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff2905e000 - 0x7fff29061fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4F8A1D06-3EFF-3174-BE9C-C4B70A3EA290> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff29062000 - 0x7fff29063fff liblangid.dylib (136) <E8044658-AE79-3930-A902-07A38BB22382> /usr/lib/liblangid.dylib\n 0x7fff29064000 - 0x7fff29104fff com.apple.CoreNLP (1.0 - 245.1) <6C49B26B-CB39-3504-AD5E-9C3333FFE086> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff29105000 - 0x7fff2910bfff com.apple.LinguisticData (1.0 - 399) <B059FF7F-731A-38F1-884A-588C6C8CA7F2> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff2910c000 - 0x7fff297c9fff libBNNS.dylib (288.80.1) <C5CD30D8-114B-3104-9020-E5C05E68CEE8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff297ca000 - 0x7fff2999dfff libvDSP.dylib (760.40.6) <4CCEE561-A72B-33BC-B9F9-77A6CF2E7AF0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2999e000 - 0x7fff299b0fff com.apple.CoreEmoji (1.0 - 128) <D43F3FFA-6692-3D56-ACBA-DDA40C566DDE> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff299b1000 - 0x7fff299bbfff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <B15E9DA1-1C81-3ECF-94C7-FD137AD6C5E2> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer\n 0x7fff299bc000 - 0x7fff29a8efff com.apple.framework.CoreWLAN (16.0 - 1657) <35927D28-3324-3CAB-9255-276A7022EADC> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff29a8f000 - 0x7fff29c8efff com.apple.CoreUtils (6.5 - 650.6) <184C48A4-7F66-395B-81DB-DAA1641383CF> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff29c8f000 - 0x7fff29cb1fff com.apple.MobileKeyBag (2.0 - 1.0) <0F83FED4-709A-37A0-9E04-EFFD71CB1272> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff29cb2000 - 0x7fff29cc2fff com.apple.AssertionServices (1.0 - 505.80.1) <A00B802D-7BB8-3F6B-A79D-E9697F7D0ABB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff29cc3000 - 0x7fff29d4ffff com.apple.securityfoundation (6.0 - 55240.40.4) <72AC63B1-0B72-394F-97E8-BA9B114DD0A9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff29d50000 - 0x7fff29d59fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <EC15118E-62BD-3C24-A880-3B9B74318B0B> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff29d5a000 - 0x7fff29d5efff com.apple.xpc.ServiceManagement (1.0 - 1) <FD031028-B702-3909-B2AF-3916404DD4A8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff29d5f000 - 0x7fff29d61fff libquarantine.dylib (119.40.2) <40D35D75-524B-3DA6-8159-E7E0FA66F5BC> /usr/lib/system/libquarantine.dylib\n 0x7fff29d62000 - 0x7fff29d6dfff libCheckFix.dylib (31) <74E17BB2-1A3C-3574-92DD-63ABE39E3FF9> /usr/lib/libCheckFix.dylib\n 0x7fff29d6e000 - 0x7fff29d85fff libcoretls.dylib (169) <B33BEF87-3275-356D-9815-D0E94122D2EB> /usr/lib/libcoretls.dylib\n 0x7fff29d86000 - 0x7fff29d96fff libbsm.0.dylib (68.40.1) <D71EF121-D4B0-306E-9843-9FAFD558E3A4> /usr/lib/libbsm.0.dylib\n 0x7fff29d97000 - 0x7fff29de0fff libmecab.dylib (929.1.1) <1F424683-4213-3594-9BF5-EFCCCDAA83A5> /usr/lib/libmecab.dylib\n 0x7fff29de1000 - 0x7fff29de6fff libgermantok.dylib (24) <E40EFA11-E95C-36D1-A8BE-8CA5B1DD179D> /usr/lib/libgermantok.dylib\n 0x7fff29de7000 - 0x7fff29dfcfff libLinearAlgebra.dylib (1336.40.1) <0D017F3F-6FD6-38DB-AA14-A64523A4D093> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff29dfd000 - 0x7fff2a024fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <8FA469B3-48BE-315B-B3A0-C868CD541608> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff2a025000 - 0x7fff2a074fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <613BB6F1-3588-3E25-B523-059022FBE56E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff2a075000 - 0x7fff2a1bcfff com.apple.MLCompute (1.0 - 1) <01B968D9-A464-3667-8B8E-C99AEBA1FF79> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute\n 0x7fff2a1bd000 - 0x7fff2a1f3fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <B988D5F6-4E54-335D-A654-12C74FD668EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff2a1f4000 - 0x7fff2a231fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <51ECDE6B-39F8-3BAB-ADC1-84C958F40A3F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff2a232000 - 0x7fff2a2c2fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <D009508B-DCDF-3421-B1CB-40FDF4A68E93> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff2a2c3000 - 0x7fff2a2d2fff com.apple.AppleFSCompression (125 - 1.0) <879A04AA-F9A1-3640-A9EF-F5D0813C852A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff2a2d3000 - 0x7fff2a2e0fff libbz2.1.0.dylib (44) <E163D5F9-E202-3A53-817B-8BC40B9293C0> /usr/lib/libbz2.1.0.dylib\n 0x7fff2a2e1000 - 0x7fff2a2e5fff libsystem_coreservices.dylib (127) <529A0663-A936-309C-9318-1B04B7F70658> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff2a2e6000 - 0x7fff2a313fff com.apple.CoreServices.OSServices (1122.11 - 1122.11) <8D30829B-426E-361E-B2A9-5850F1E5513D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2a314000 - 0x7fff2a445fff com.apple.AuthKit (1.0 - 1) <4A9B2D94-7AB0-3417-8D4E-A9C6C31C31D4> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff2a4e9000 - 0x7fff2a4fbfff libz.1.dylib (76) <6E2BD7A3-DC55-3183-BBF7-3AC367BC1834> /usr/lib/libz.1.dylib\n 0x7fff2a4fc000 - 0x7fff2a543fff libsystem_m.dylib (3186.40.2) <DD26CC5C-AFF6-305F-A567-14909DD57163> /usr/lib/system/libsystem_m.dylib\n 0x7fff2a544000 - 0x7fff2a544fff libcharset.1.dylib (59) <D14F9D24-693A-37F0-8F92-D260248EB282> /usr/lib/libcharset.1.dylib\n 0x7fff2a545000 - 0x7fff2a54afff libmacho.dylib (973.4) <C2584BC4-497B-3170-ADDF-21B8E10B4DFD> /usr/lib/system/libmacho.dylib\n 0x7fff2a54b000 - 0x7fff2a566fff libkxld.dylib (7195.81.3) <DE05C188-D9FE-30DC-8299-DF3DC9F837A5> /usr/lib/system/libkxld.dylib\n 0x7fff2a567000 - 0x7fff2a572fff libcommonCrypto.dylib (60178.40.2) <822A29CE-BF54-35AD-BB15-8FAECB800C7D> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff2a573000 - 0x7fff2a57dfff libunwind.dylib (200.10) <1D0A4B4A-4370-3548-8DC1-42A7B4BD45D3> /usr/lib/system/libunwind.dylib\n 0x7fff2a57e000 - 0x7fff2a585fff liboah.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/liboah.dylib\n 0x7fff2a586000 - 0x7fff2a590fff libcopyfile.dylib (173.40.2) <39DBE613-135B-3AFE-A6AF-7898A37F70C2> /usr/lib/system/libcopyfile.dylib\n 0x7fff2a591000 - 0x7fff2a598fff libcompiler_rt.dylib (102.2) <62EE1D14-5ED7-3CEC-81C0-9C93833641F1> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff2a599000 - 0x7fff2a59bfff libsystem_collections.dylib (1439.40.11) <C53D5E0C-0C4F-3B35-A24B-E0D7101A3F95> /usr/lib/system/libsystem_collections.dylib\n 0x7fff2a59c000 - 0x7fff2a59efff libsystem_secinit.dylib (87.60.1) <E05E35BC-1BAB-365B-8BEE-D774189EFD3B> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff2a59f000 - 0x7fff2a5a1fff libremovefile.dylib (49.40.3) <5CC12A16-82CB-32F0-9040-72CFC88A48DF> /usr/lib/system/libremovefile.dylib\n 0x7fff2a5a2000 - 0x7fff2a5a2fff libkeymgr.dylib (31) <803F6AED-99D5-3CCF-B0FA-361BCF14C8C0> /usr/lib/system/libkeymgr.dylib\n 0x7fff2a5a3000 - 0x7fff2a5aafff libsystem_dnssd.dylib (1310.80.1) <E0A0CAB3-6779-3C83-AC67-046CFE69F9C2> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff2a5ab000 - 0x7fff2a5b0fff libcache.dylib (83) <1A98B064-8FED-39CF-BB2E-5BDA1EF5B65A> /usr/lib/system/libcache.dylib\n 0x7fff2a5b1000 - 0x7fff2a5b2fff libSystem.B.dylib (1292.60.1) <83503CE0-32B1-36DB-A4F0-3CC6B7BCF50A> /usr/lib/libSystem.B.dylib\n 0x7fff2a5b3000 - 0x7fff2a5b6fff libfakelink.dylib (3) <D939A124-9FD5-37A2-B03B-72E98CBC98FE> /usr/lib/libfakelink.dylib\n 0x7fff2a5b7000 - 0x7fff2a5b7fff com.apple.SoftLinking (1.0 - 1) <EF2AC5FF-B98D-3252-ABA8-2FC721CBA942> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking\n 0x7fff2a5b8000 - 0x7fff2a5effff libpcap.A.dylib (98.40.1) <DE5787F8-D011-3E71-8323-936B35976D9E> /usr/lib/libpcap.A.dylib\n 0x7fff2a5f0000 - 0x7fff2a6e0fff libiconv.2.dylib (59) <AD10ECF4-E137-3152-9612-7EC548D919E8> /usr/lib/libiconv.2.dylib\n 0x7fff2a6e1000 - 0x7fff2a6f2fff libcmph.dylib (8) <A5D1EBB3-70A1-3ECA-A3C7-E97FBAD36ECF> /usr/lib/libcmph.dylib\n 0x7fff2a6f3000 - 0x7fff2a764fff libarchive.2.dylib (83.40.4) <9061C767-43FD-3483-9C48-73973AF82DC1> /usr/lib/libarchive.2.dylib\n 0x7fff2a765000 - 0x7fff2a7ccfff com.apple.SearchKit (1.4.1 - 1.4.1) <6243D4C0-3572-30A6-889A-B8690A5EAC24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2a7cd000 - 0x7fff2a7cefff libThaiTokenizer.dylib (3) <47CDE3EE-60AB-38CE-9494-5CC047CACA7F> /usr/lib/libThaiTokenizer.dylib\n 0x7fff2a7cf000 - 0x7fff2a7f6fff com.apple.applesauce (1.0 - 16.26) <4A637FE0-A740-32F0-AE70-4593F6DF1573> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff2a7f7000 - 0x7fff2a80efff libapple_nghttp2.dylib (1.41) <A2F6DE8D-2B38-3669-A16E-E1BD54108F24> /usr/lib/libapple_nghttp2.dylib\n 0x7fff2a80f000 - 0x7fff2a821fff libSparseBLAS.dylib (1336.40.1) <FC45F7FD-6B10-3F8D-A553-F57C757F6717> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a822000 - 0x7fff2a823fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F37DBCE9-20CD-33D4-806B-93B326E08422> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff2a824000 - 0x7fff2a828fff libpam.2.dylib (28.40.1) <FA3308D0-E7B4-3A2C-AE39-0E085F6CDEE0> /usr/lib/libpam.2.dylib\n 0x7fff2a829000 - 0x7fff2a841fff libcompression.dylib (96.40.6) <9C42DB2C-0A6D-38CE-BB8D-899A9B34B695> /usr/lib/libcompression.dylib\n 0x7fff2a842000 - 0x7fff2a847fff libQuadrature.dylib (7) <55EE1866-623B-3C10-91FB-C8B06EB83995> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a848000 - 0x7fff2abe4fff libLAPACK.dylib (1336.40.1) <2F92E8CD-396D-3665-88EB-41A4E1A9CB31> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2abe5000 - 0x7fff2ac33fff com.apple.DictionaryServices (1.2 - 341) <5D0B1BB2-995B-32EB-AE75-F5F27127ACAF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ac34000 - 0x7fff2ac4cfff liblzma.5.dylib (16) <168D84A7-8E54-361E-9161-B661D96C0C9A> /usr/lib/liblzma.5.dylib\n 0x7fff2ac4d000 - 0x7fff2ac4efff libcoretls_cfhelpers.dylib (169) <80AF345B-1989-3C88-AEF4-8FF18A366A9C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff2ac4f000 - 0x7fff2ad49fff com.apple.APFS (1677.81.1 - 1677.81.1) <E48CCAAC-34B5-377E-8E5D-06CDBD411C2F> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff2ad4a000 - 0x7fff2ad57fff libxar.1.dylib (452) <FAA7B36E-21EC-3ADF-AA6A-E3742737CA3A> /usr/lib/libxar.1.dylib\n 0x7fff2ad58000 - 0x7fff2ad5bfff libutil.dylib (58.40.2) <0A268749-08E7-3551-8969-442210651CCA> /usr/lib/libutil.dylib\n 0x7fff2ad5c000 - 0x7fff2ad84fff libxslt.1.dylib (17.3) <1C5219FB-B504-3658-B23B-2C45A3BA28F1> /usr/lib/libxslt.1.dylib\n 0x7fff2ad85000 - 0x7fff2ad8ffff libChineseTokenizer.dylib (37) <718400BF-9911-3CB6-8CCE-4C2D7C35D80A> /usr/lib/libChineseTokenizer.dylib\n 0x7fff2ad90000 - 0x7fff2ae4efff libvMisc.dylib (760.40.6) <9D11FCFC-6C30-32B6-864B-9CC3ED7D1143> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ae4f000 - 0x7fff2aee7fff libate.dylib (3.0.4) <42707DFB-86A4-3F56-A5AF-E6DAA7E49DC7> /usr/lib/libate.dylib\n 0x7fff2aee8000 - 0x7fff2aeeffff libIOReport.dylib (64) <8DEEA01D-B715-340A-900E-B448AB22720E> /usr/lib/libIOReport.dylib\n 0x7fff2aef0000 - 0x7fff2af1efff com.apple.CrashReporterSupport (10.13 - 15047.1) <EA306EDB-2A02-3FB6-8812-F5EAA337AEE6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff2b00b000 - 0x7fff2b012fff libMatch.1.dylib (38) <DE8B7844-BFB2-3E3E-9FD0-1C9AD1DC1736> /usr/lib/libMatch.1.dylib\n 0x7fff2b013000 - 0x7fff2b09efff libCoreStorage.dylib (554) <044E6815-6340-31D5-BEE9-760C354E92A3> /usr/lib/libCoreStorage.dylib\n 0x7fff2b09f000 - 0x7fff2b0f2fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <E3BE877B-1C78-3ABF-8C41-66FE9B6971C7> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff2b0f3000 - 0x7fff2b10cfff libexpat.1.dylib (26) <1D978F91-674E-3A44-8A93-773C7E3E513C> /usr/lib/libexpat.1.dylib\n 0x7fff2b10d000 - 0x7fff2b116fff libheimdal-asn1.dylib (597.80.1) <8F6CD867-FB45-375D-82C1-E0AE79558C8C> /usr/lib/libheimdal-asn1.dylib\n 0x7fff2b117000 - 0x7fff2b12bfff com.apple.IconFoundation (479.3 - 479.3) <3563C4B4-ABF6-3DE0-8381-D3667DFE2B80> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation\n 0x7fff2b12c000 - 0x7fff2b199fff com.apple.IconServices (479.3 - 479.3) <B6859735-701D-307E-8061-298BA2296E47> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff2b19a000 - 0x7fff2b237fff com.apple.MediaExperience (1.0 - 1) <14E84D66-28B8-390E-A499-9F24B7628EC7> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff2b238000 - 0x7fff2b261fff com.apple.persistentconnection (1.0 - 1.0) <B3FE85C5-8034-38D5-8566-5317B49ECF61> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff2b262000 - 0x7fff2b270fff com.apple.GraphVisualizer (1.0 - 100.1) <A7393BC4-4441-31B5-BB15-5A5A70738BEC> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff2b271000 - 0x7fff2b68cfff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <23CD0C8A-E300-3E28-BD5B-DDCDA4521C54> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff2b68d000 - 0x7fff2b6d7fff com.apple.OTSVG (1.0 - 677.3.0.4) <827396F3-F3A7-3A4F-BE7F-171077501137> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff2b6d8000 - 0x7fff2b6defff com.apple.xpc.AppServerSupport (1.0 - 2038.80.3) <C78E9D22-5110-349B-AF8E-6BA893A20214> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport\n 0x7fff2b6df000 - 0x7fff2b6f0fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <F0974976-30C0-35EB-92F1-B4CF1E974F11> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff2b6f1000 - 0x7fff2b6f3fff libspindump.dylib (295.1) <3B4701CB-8F66-3E50-A38A-BEEC992AAC31> /usr/lib/libspindump.dylib\n 0x7fff2b6f4000 - 0x7fff2b7b4fff com.apple.Heimdal (4.0 - 2.0) <69768234-4F4F-3AB6-B116-4AE249E6417A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff2b7b5000 - 0x7fff2b7cffff com.apple.login (3.0 - 3.0) <B9BEC3A1-688C-3999-B705-2D50B8756E62> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff2b94f000 - 0x7fff2b952fff libodfde.dylib (26) <47160F56-2A36-3147-B721-279BE2F8B4A6> /usr/lib/libodfde.dylib\n 0x7fff2b953000 - 0x7fff2b9bdfff com.apple.bom (14.0 - 233) <F4B7C353-8A65-3B54-9E01-2C93CB3F55A3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff2b9be000 - 0x7fff2ba08fff com.apple.AppleJPEG (1.0 - 1) <7F3819DE-BCE7-32B7-BB33-10C1DB2BA512> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff2ba09000 - 0x7fff2bae7fff libJP2.dylib (2130.3.5) <2DFE6642-4309-30BD-A402-F93E28F1F065> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff2bae8000 - 0x7fff2baebfff com.apple.WatchdogClient.framework (1.0 - 98.80.2) <C257C950-F430-3762-BC72-15D314D99556> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff2baec000 - 0x7fff2bb1ffff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <4243F7DC-7EB9-3750-BE36-527B0BADF36C> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff2bb20000 - 0x7fff2bc72fff com.apple.VideoToolbox (1.0 - 2765.6.4.2) <425BDD2D-6C26-3D09-AD9F-942EA387B2A4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff2bc73000 - 0x7fff2bca5fff libAudioToolboxUtility.dylib (1180.25) <83DBFA98-F85B-3B63-B58F-C9989BAC9611> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff2bca6000 - 0x7fff2bcccfff libPng.dylib (2130.3.5) <9046A7B7-6C31-32C5-B610-6AEA6F6B2D48> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff2bccd000 - 0x7fff2bd2cfff libTIFF.dylib (2130.3.5) <CAAF5746-3171-38B1-9722-8CB9B650C627> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff2bd2d000 - 0x7fff2bd49fff com.apple.IOPresentment (54 - 37) <5AD7B6E0-1744-3C8D-8A95-FE425DEA005C> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff2bd4a000 - 0x7fff2bd50fff com.apple.GPUWrangler (6.2.2 - 6.2.2) <60363868-111B-36CF-9CDF-2643DF82002D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff2bd51000 - 0x7fff2bd54fff libRadiance.dylib (2130.3.5) <71EBA416-A317-380A-984A-F6B0A0695A65> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff2bd55000 - 0x7fff2bd5afff com.apple.DSExternalDisplay (3.1 - 380) <010F8260-BC46-361E-BE59-540F765EFE74> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff2bd5b000 - 0x7fff2bd7ffff libJPEG.dylib (2130.3.5) <4BFCC012-7CDD-320D-845D-E475243D3ECE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff2bd80000 - 0x7fff2bdaffff com.apple.ATSUI (1.0 - 1) <6C45783D-CF90-3F11-BA86-92D31A9B68CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2bdb0000 - 0x7fff2bdb4fff libGIF.dylib (2130.3.5) <0C91C2A9-5D71-3042-A0D2-AA8F1F09012E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff2bdb5000 - 0x7fff2bdbefff com.apple.CMCaptureCore (1.0 - 80.20.5) <2B7E468B-D901-3EA9-85CF-82FD753785BD> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore\n 0x7fff2bdbf000 - 0x7fff2be06fff com.apple.print.framework.PrintCore (16 - 531) <DB939B2B-D47D-3035-8C02-01006D21C5A7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2be07000 - 0x7fff2bed3fff com.apple.TextureIO (3.10.9 - 3.10.9) <50BA07A4-02E8-38EE-B0B9-B12C277B563B> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff2bed4000 - 0x7fff2bedcfff com.apple.InternationalSupport (1.0 - 60) <DE997943-6AD5-32DA-B48E-78170C1EAA7B> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff2bedd000 - 0x7fff2bf58fff com.apple.datadetectorscore (8.0 - 674) <A4EBFF22-F861-321A-AF28-1DB8ECB9A4FF> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff2bf59000 - 0x7fff2bfb7fff com.apple.UserActivity (435 - 435) <12250395-D660-3CC1-81DB-565340F2651B> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity\n 0x7fff2bfb8000 - 0x7fff2c723fff com.apple.MediaToolbox (1.0 - 2765.6.4.2) <C8645EA0-643D-38CF-AA88-3253339192B1> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff2cbdd000 - 0x7fff2cc05fff com.apple.locationsupport (2420.12.16 - 2420.12.16) <63AB1284-8E33-3E9D-A857-9370F492B343> /System/Library/PrivateFrameworks/LocationSupport.framework/Versions/A/LocationSupport\n 0x7fff2cc06000 - 0x7fff2cc37fff libSessionUtility.dylib (76.7) <6AAD02A0-9590-3CED-9568-36E05C59AA2B> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff2cc38000 - 0x7fff2cd68fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <8E53C25F-9FE2-372E-8374-6A598D72C4C1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2cd69000 - 0x7fff2cdd0fff com.apple.audio.AudioSession (1.0 - 76.7) <F696F4EC-9344-3C85-941E-6E5EF5CEF585> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff2cdd1000 - 0x7fff2cde3fff libAudioStatistics.dylib (25.4) <303533DD-D001-3CE8-A5A4-EC29F464FC3A> /usr/lib/libAudioStatistics.dylib\n 0x7fff2cde4000 - 0x7fff2cdf3fff com.apple.speech.synthesis.framework (9.0.51.2 - 9.0.51.2) <14F3382B-2B8E-31E5-8C73-73F0B8DD05F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2cdf4000 - 0x7fff2ce5ffff com.apple.ApplicationServices.ATS (377 - 516) <3DD60168-A0F3-3388-8DDE-69F81280AE91> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2ce60000 - 0x7fff2ce78fff libresolv.9.dylib (68) <7B043B4A-71CE-3F6E-91F0-CBBED47A9EA9> /usr/lib/libresolv.9.dylib\n 0x7fff2ce79000 - 0x7fff2ce8cfff libsasl2.2.dylib (214) <7EE1EE13-9D86-3612-A6BC-3E6B5D578267> /usr/lib/libsasl2.2.dylib\n 0x7fff2cfab000 - 0x7fff2d08afff libSMC.dylib (20) <B207FDFF-8D80-3800-B968-03C718FFBF3F> /usr/lib/libSMC.dylib\n 0x7fff2d08b000 - 0x7fff2d0eafff libcups.2.dylib (494.1) <CDF6F483-017E-3DED-B107-C50FC3CADD65> /usr/lib/libcups.2.dylib\n 0x7fff2d0eb000 - 0x7fff2d0fafff com.apple.LangAnalysis (1.7.0 - 254) <14703020-3124-3C62-A9DB-6DD28024CD42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d0fb000 - 0x7fff2d105fff com.apple.NetAuth (6.2 - 6.2) <D40BF56F-DF5F-3ECB-AAC2-FE6F13E9D120> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff2d106000 - 0x7fff2d10dfff com.apple.ColorSyncLegacy (4.13.0 - 1) <F3AEB77A-456F-3F9F-98CC-3E29ABAF5D0C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d10e000 - 0x7fff2d119fff com.apple.QD (4.0 - 416) <F65D0944-C775-33FB-A345-C046789667B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d11a000 - 0x7fff2d788fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <6A293E4C-1E2D-36DA-B416-FBED7286CD6E> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff2d789000 - 0x7fff2d795fff com.apple.perfdata (1.0 - 67.40.1) <A9D2E8CD-9D74-304E-BD99-A7704F3CD38B> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata\n 0x7fff2d796000 - 0x7fff2d7a4fff libperfcheck.dylib (41) <5AFDC5C6-EBB6-33E4-9215-1AACE6C6F6EE> /usr/lib/libperfcheck.dylib\n 0x7fff2d7a5000 - 0x7fff2d7b4fff com.apple.Kerberos (3.0 - 1) <02FFA3CA-F8AF-3211-9159-36BC29612650> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff2d7b5000 - 0x7fff2d804fff com.apple.GSS (4.0 - 2.0) <5D06022E-C963-390A-9487-90BD1B61BC20> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff2d805000 - 0x7fff2d815fff com.apple.CommonAuth (4.0 - 2.0) <C4418557-FA52-3B80-804F-2BC7AF760FD6> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff2d816000 - 0x7fff2d83cfff com.apple.MobileAssets (1.0 - 659.60.1) <62F25002-C547-3C6C-87D1-0824DD058C82> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff2d86a000 - 0x7fff2d88cfff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F4B051F-BC33-3880-81B2-5C62DABFF02D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff2d88d000 - 0x7fff2d895fff com.apple.CorePhoneNumbers (1.0 - 1) <AA493452-21D3-3EC6-953C-42DBF75F4EB9> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff2d9ea000 - 0x7fff2d9eafff liblaunch.dylib (2038.80.3) <C7C51322-8491-3B78-9CFA-2B4753662BCF> /usr/lib/system/liblaunch.dylib\n 0x7fff2e1e5000 - 0x7fff2e32cfff com.apple.Sharing (1579 - 1579) <4925CAB3-09C0-373C-A5D3-9BB5FF025A4F> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff2e32d000 - 0x7fff2e44dfff com.apple.Bluetooth (8.0.3 - 8.0.3d9) <C6FFFDA7-CD91-339A-8529-7D094338949D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff2e44e000 - 0x7fff2e462fff com.apple.AppContainer (4.0 - 509.60.2) <F294CD92-94FA-3D7D-9E59-AA5544504264> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff2e463000 - 0x7fff2e466fff com.apple.SecCodeWrapper (4.0 - 509.60.2) <1BEC89D6-6AC8-36C2-89AE-41662D14DC50> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff2e467000 - 0x7fff2e4c0fff com.apple.ProtectedCloudStorage (1.0 - 1) <88EF8B12-617E-316C-9036-18357E27BC0A> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff2e714000 - 0x7fff2fc0afff com.apple.GeoServices (1.0 - 1757.23.11.29.3) <72B73209-98B3-3E90-8D5D-B69C81784E5D> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices\n 0x7fff2fc0b000 - 0x7fff2fc16fff com.apple.DirectoryService.Framework (11.2 - 230.40.1) <4DB85BA3-9323-304B-BDC3-6E13B9AAA1C2> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff2fc17000 - 0x7fff2fc42fff com.apple.RemoteViewServices (2.0 - 163) <661A448B-2901-33CD-B13C-362D61AFD998> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff2fc43000 - 0x7fff2fc52fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <B24969AE-43BA-36C2-80F9-2CBBC3F63CC8> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff2fc53000 - 0x7fff2fc5afff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <8C33ECFF-2FBF-30FF-87EA-32A508860543> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2fe9e000 - 0x7fff2fe9efff libsystem_product_info_filter.dylib (8.40.1) <20310EE6-2C3F-361A-9ECA-4223AFC03B65> /usr/lib/system/libsystem_product_info_filter.dylib\n 0x7fff2ff79000 - 0x7fff2ff79fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <8CD6F55A-8E4F-3653-A367-427D0ED3DD16> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ffa0000 - 0x7fff2ffa0fff com.apple.CoreServices (1122.11 - 1122.11) <E59859C6-7221-3324-BB58-F910B2199959> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3026e000 - 0x7fff3026efff com.apple.Accelerate (1.11 - Accelerate 1.11) <2423F0F6-A3A4-37AB-971E-FCFC7645D282> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff302af000 - 0x7fff302bafff com.apple.MediaAccessibility (1.0 - 130) <264B30DF-646A-30EC-98B6-20429E9718CB> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff302bb000 - 0x7fff302dafff com.apple.networking.AlgosScoreFramework (1.0 - 1) <8713D2A4-ECB6-3B96-BE39-F47851EEF900> /System/Library/PrivateFrameworks/AlgosScoreFramework.framework/Versions/A/AlgosScoreFramework\n 0x7fff302db000 - 0x7fff302dffff com.apple.AppleSRP (5.0 - 1) <3BF95CAF-2EC5-393A-95B7-429C0C5F8F13> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff302e0000 - 0x7fff302ebfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D73E7719-09C8-30E6-B92D-AFC1BB356D92> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff302ec000 - 0x7fff30323fff com.apple.framework.SystemAdministration (1.0 - 1.0) <9275DC16-B898-326A-B6AD-6CDF34F0CF77> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff30ae5000 - 0x7fff30b47fff com.apple.CoreBluetooth (1.0 - 1) <B88DEE8B-6268-36BA-BF6C-088F3BD8C652> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff30b48000 - 0x7fff30b51fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <83B5E330-D786-34D2-AEE6-6F7B34D6FE9C> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff30b52000 - 0x7fff30b65fff com.apple.PowerLog (1.0 - 1) <3A076F54-AE8C-3550-8262-5655B5026489> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff30b66000 - 0x7fff30b72fff com.apple.AppleIDAuthSupport (1.0 - 1) <964BA0DB-E86E-3F81-BB82-CC27184B6D20> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff30b73000 - 0x7fff30c1bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <2B9AA549-63FD-36BB-AE05-ABD5DAC41279> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff30c1c000 - 0x7fff30c4ffff com.apple.MediaKit (16 - 927.40.2) <D1056292-E38F-313F-B202-EFD871195729> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff30c50000 - 0x7fff30d3bfff com.apple.DiskManagement (14.0 - 1733.80.1) <9281E3F8-EAFE-3367-B7D5-23687AA6EB70> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff30d3c000 - 0x7fff310f6fff com.apple.CoreAUC (322.2.0 - 322.2.0) <DAE981E0-5FED-39FD-8443-BD91D6957901> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff310f7000 - 0x7fff310fafff com.apple.Mangrove (1.0 - 25) <61919815-50C9-3358-836F-B81ED66CCD84> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff310fb000 - 0x7fff31128fff com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B123866C-3945-37E7-92EF-BE36AEDD620D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff31129000 - 0x7fff31249fff com.apple.FileProvider (326.3 - 326.3) <C5007E6E-897B-308F-B173-4F5C6BF3968D> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff3124a000 - 0x7fff3126dfff com.apple.GenerationalStorage (2.0 - 322) <974A1465-7AA4-347E-8606-CF35160FFA92> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff31ac0000 - 0x7fff31afffff com.apple.AppleVPAFramework (3.21.1 - 3.21.1) <4E96F781-3689-3086-9DF3-60F20487FB9E> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA\n 0x7fff31bd0000 - 0x7fff31c0cfff com.apple.DebugSymbols (195.1 - 195.1) <12A5A6E2-6C84-3FCA-9927-8B9E241C607F> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff31c0d000 - 0x7fff31ccafff com.apple.CoreSymbolication (12.2 - 64541.4) <F1A41B4E-671A-335E-8AE0-B99688F255C8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff31ccb000 - 0x7fff31cd4fff com.apple.CoreTime (284) <D80E792D-33D1-3D07-B39F-F0A1A7F74E24> /System/Library/PrivateFrameworks/CoreTime.framework/Versions/A/CoreTime\n 0x7fff32b61000 - 0x7fff32bc4fff com.apple.framework.Apple80211 (17.0 - 1728) <A62689A7-7C22-33B3-90FA-730E4AAEE5B5> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff32bc5000 - 0x7fff32d17fff com.apple.CoreWiFi (3.0 - 341) <F3D8F158-611A-3A5E-9F1D-E5FC273A4C74> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff32d31000 - 0x7fff32d68fff com.apple.LDAPFramework (2.4.28 - 194.5) <246874E6-4FD1-35A5-A039-4141999D8CD6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff32d69000 - 0x7fff32d6afff com.apple.TrustEvaluationAgent (2.0 - 35) <6FEF60A0-F80F-34E3-8845-FEEC92840920> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff32d6b000 - 0x7fff32e6efff libcrypto.44.dylib (56.60.2) <7D8D4B1B-625D-3D00-A626-C21AFEE0462E> /usr/lib/libcrypto.44.dylib\n 0x7fff32e6f000 - 0x7fff32e9cfff libssl.46.dylib (56.60.2) <E02ED3C9-4956-39C4-AF0A-B541EEDD3F1B> /usr/lib/libssl.46.dylib\n 0x7fff32e9d000 - 0x7fff32f4cfff com.apple.DiskImagesFramework (595.40.1 - 595.40.1) <3139EC22-A8F2-3F26-8953-7961C97E7CEF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff32f84000 - 0x7fff32f93fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.80.3) <78AF1606-37D8-3424-92AE-071A9F43AA0F> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery\n 0x7fff32f94000 - 0x7fff32fabfff com.apple.xpc.RemoteXPC (1.0 - 2038.80.3) <C4BFF5FC-FC9C-3161-9612-7070EDAE9989> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC\n 0x7fff32ff3000 - 0x7fff32ff6fff com.apple.help (1.3.8 - 71) <6074D81C-4507-35A6-88D7-D82309F81587> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32ff7000 - 0x7fff32ffefff com.apple.EFILogin (2.0 - 2) <B06CCD1C-A4D1-34D2-89C5-0DB69FE65234> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff32fff000 - 0x7fff3300afff libcsfde.dylib (554) <9CDB9580-DD1C-347E-91C5-6D92D96F52F5> /usr/lib/libcsfde.dylib\n 0x7fff3300b000 - 0x7fff33070fff libcurl.4.dylib (121.40.2) <77010EA9-4AD1-3F4A-B3EF-2FFE739FB349> /usr/lib/libcurl.4.dylib\n 0x7fff33071000 - 0x7fff33078fff com.apple.LoginUICore (4.0 - 4.0) <7225326A-7704-362D-B64E-4ABF4A221F88> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff33238000 - 0x7fff33238fff com.apple.ApplicationServices (48 - 50) <42B48E32-1918-3178-8DE0-E8126B9EC088> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff33539000 - 0x7fff33539fff libHeimdalProxy.dylib (79) <85526E13-1E48-377A-A700-EE3F5648A6E3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff335ec000 - 0x7fff335ecfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <8CF768B8-836B-3DA8-9F0A-8CF840348202> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff33611000 - 0x7fff33653fff com.apple.StreamingZip (1.0 - 1) <157C7AC0-9F73-3FF5-A276-54EC3CAE958A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff33696000 - 0x7fff3369bfff com.apple.PushKit (1.0 - 1) <4D0A6539-611C-3B9C-A67D-D45CDEEC8CDC> /System/Library/Frameworks/PushKit.framework/Versions/A/PushKit\n 0x7fff3369c000 - 0x7fff336d2fff com.apple.C2 (1.3 - 569) <817D8F9D-1801-3E6D-846A-7002174B59CB> /System/Library/PrivateFrameworks/C2.framework/Versions/A/C2\n 0x7fff33705000 - 0x7fff33f12fff com.apple.vision.EspressoFramework (1.0 - 256.2.2) <70E23334-A179-3671-A930-A7AB9EC77BDD> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso\n 0x7fff33f13000 - 0x7fff33f2afff com.apple.ANEServices (4.52 - 4.52) <50EF6199-93EF-3227-B64A-313BC1DF41AE> /System/Library/PrivateFrameworks/ANEServices.framework/Versions/A/ANEServices\n 0x7fff342c7000 - 0x7fff3458afff com.apple.spotlight.index (10.7.0 - 2150.7.5) <0056D8F9-D6CF-3586-974C-80902DF8952A> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff345a3000 - 0x7fff345f3fff com.apple.ChunkingLibrary (334 - 334) <CBEBDC8A-CCE4-3A21-915C-D2F3FB20B900> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff34ebf000 - 0x7fff34ed5fff com.apple.CoreML.AppleNeuralEngine (1.0 - 1) <A2E78405-4382-3A23-8638-56E1A5D14543> /System/Library/PrivateFrameworks/AppleNeuralEngine.framework/Versions/A/AppleNeuralEngine\n 0x7fff3503b000 - 0x7fff3503efff com.apple.Cocoa (6.11 - 23) <B0F6AF8E-B85C-3C5C-9812-9CD8BC07ADB2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff36482000 - 0x7fff3649dfff com.apple.openscripting (1.7 - 190) <E3815884-A406-3CF6-82C1-BEDC772A9081> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff3649e000 - 0x7fff364a1fff com.apple.securityhi (9.0 - 55008) <F7E1C957-65AF-39E5-8BBA-9D7C7C9D30B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff364a2000 - 0x7fff364a5fff com.apple.ink.framework (10.15 - 227) <E3D118A5-7A62-3893-ADAC-E0A9F45314C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff364a6000 - 0x7fff364a9fff com.apple.CommonPanels (1.2.6 - 101) <F46676FA-60F3-30CC-BF48-F5BB6E66E576> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff364aa000 - 0x7fff364b1fff com.apple.ImageCapture (1708.1 - 1708.1) <AC709D2F-7C16-3645-BB20-19DD1414E210> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff3949f000 - 0x7fff394a2fff com.apple.OSAServicesClient (1.0 - 1) <201350F5-56C4-3342-AD10-4BE20772C52B> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/OSAServicesClient\n 0x7fff3c090000 - 0x7fff3c24bfff libFosl_dynamic.dylib (200) <83EE0261-E5F6-3607-8897-B03B2B954B15> /usr/lib/libFosl_dynamic.dylib\n 0x7fff3d1a8000 - 0x7fff3d1abfff com.apple.print.framework.Print (15 - 271) <F3F40AFD-1743-34E6-8BD3-6A577E3BD590> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff3d1ac000 - 0x7fff3d1affff com.apple.Carbon (160 - 164) <7395C7E9-AE3B-3547-8773-4F3A70B241AA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff3d434000 - 0x7fff3d453fff com.apple.private.SystemPolicy (1.0 - 1) <29F5E3FE-CF12-3242-9FD3-4950DA38E4D0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy\n 0x7fff3d600000 - 0x7fff3d61dfff com.apple.sidecar-core (1.0 - 228) <78195DB7-D409-3B46-B8C8-3B70538D3CDC> /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore\n 0x7fff3dd7d000 - 0x7fff3dd88fff com.apple.MallocStackLogging (1.0 - 1) <507894FA-6738-372B-9A10-C38AFC9DA079> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/MallocStackLogging\n 0x7fff3dd9e000 - 0x7fff3ddb0fff libmis.dylib (274.60.2) <6C720DC2-E50E-3A8D-8494-F8C007DF8DF4> /usr/lib/libmis.dylib\n 0x7fff3ddb1000 - 0x7fff3ddb4fff com.apple.gpusw.GPURawCounter (17.3 - 12.0) <070CF9B7-EE89-39F3-B0F6-26D4974AD3A8> /System/Library/PrivateFrameworks/GPURawCounter.framework/Versions/A/GPURawCounter\n 0x7fff3e2c0000 - 0x7fff3e2d1fff com.apple.sidecar-ui (1.0 - 228) <E0B4A84C-7E8D-338B-8269-DAA5AE1ED094> /System/Library/PrivateFrameworks/SidecarUI.framework/Versions/A/SidecarUI\n 0x7fff4153a000 - 0x7fff41569fff libncurses.5.4.dylib (57) <CAD79205-84C0-3731-AED8-EDEF51ACC872> /usr/lib/libncurses.5.4.dylib\n 0x7fff4156a000 - 0x7fff41573fff com.apple.IOAccelMemoryInfo (1.0 - 1) <544B95BE-810E-3D94-AEB1-D5C117D946D7> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff419aa000 - 0x7fff419c8fff libCGInterfaces.dylib (544.2) <2BC461CE-B7FA-33F3-A36B-64F54FB371B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff43fb8000 - 0x7fff44231fff com.apple.RawCamera.bundle (9.10.0 - 1430) <3E7403EB-156C-36C7-93AD-1356447D5310> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff46cb9000 - 0x7fff46cc4fff libGPUSupportMercury.dylib (18.1.1) <1321060E-8F56-3917-8F4D-510A4DB45798> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff48327000 - 0x7fff48376fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <CADD88A2-87A8-3879-8759-D3C112A6844F> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics\n 0x7fff4c3d2000 - 0x7fff4c3d5fff com.apple.FinderSyncPriv (1.3 - 1350.2.10) <121C1E64-B0BE-389F-A35D-DD44D84129E8> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff522ff000 - 0x7fff52391fff com.apple.Symbolication (12.2 - 64541.7.1) <FA39B702-6E08-3F11-953F-5EC1EFB993BB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff564d5000 - 0x7fff564d8fff com.apple.ForceFeedback (1.0.6 - 1.0.6) <8782199E-5556-3FB6-87E8-03472B480BAA> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff5eada000 - 0x7fff5ef6afff com.apple.driver.AppleIntelKBLGraphicsMTLDriver (16.1.12 - 16.0.1) <2B7EEE40-F4BD-32CD-B5A3-51F67B57AA69> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver\n 0x7fff5ef6b000 - 0x7fff5f97efff libSC.dylib (4.2.15) <86667FD2-E9BB-39FE-82E9-7B1F0230A922> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib\n 0x7fff5fcc7000 - 0x7fff60caafff com.apple.driver.AppleIntelKBLGraphicsGLDriver (16.1.12 - 16.0.1) <7E0C9E81-E41B-3D24-AB0B-84295B61FADF> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver\n 0x7fff6a490000 - 0x7fff6a494fff libmetal_timestamp.dylib (31001.161) <DF0A6F36-E486-3656-A6F2-9BA9A0CF2159> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libmetal_timestamp.dylib\n 0x7fff6c8fe000 - 0x7fff6c904fff libCoreFSCache.dylib (177.22) <44489BD1-3963-35DF-86F1-DE95778AC0DB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff6c905000 - 0x7fff6c909fff libCoreVMClient.dylib (177.22) <989F6CBF-CCEF-340D-9CB5-EC4133707040> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff6c90a000 - 0x7fff6c919fff com.apple.opengl (18.1.1 - 18.1.1) <F70AF1B3-D17A-3A0E-A8AC-9D45C5B52BA9> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff6c91a000 - 0x7fff6c91cfff libCVMSPluginSupport.dylib (18.1.1) <AF77D964-9A4C-3690-AF62-4E05825DC9BF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff6c91d000 - 0x7fff6c925fff libGFXShared.dylib (18.1.1) <45A1FFDC-03B7-3D64-AFAF-16D321B53D28> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff6c926000 - 0x7fff6c959fff libGLImage.dylib (18.1.1) <16D10CE1-C2A1-3E24-A617-766CB6E9133C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff6c95a000 - 0x7fff6c996fff libGLU.dylib (18.1.1) <F0DD35B5-3692-3BE5-AD3D-4F6B237EF6AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff6c997000 - 0x7fff6cb2bfff libGLProgrammability.dylib (18.1.1) <F8A8DACC-1932-3DEF-A269-396E4981B4D0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff6cb2c000 - 0x7fff6cb36fff libGL.dylib (18.1.1) <68ABAADE-2DB4-3412-9F36-CA1AEAC8E9F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff6cb37000 - 0x7fff6ccb2fff GLEngine (18.1.1) <2C9F1F38-F0CA-3416-9A6E-C0E3F40C3AAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff6ccb3000 - 0x7fff6ccdcfff GLRendererFloat (18.1.1) <A66AB383-EE4C-325C-8115-78F2B3FFECC7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff6df6d000 - 0x7fff6dfc5fff com.apple.opencl (4.5 - 4.5) <40B70A3B-D981-3E4A-9BEC-F22EF84118F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff6eee8000 - 0x7fff6ef37fff ATIRadeonX6000SCLib.dylib (4.2.15) <E3B416D3-3876-3218-A68F-A745B103F160> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/ATIRadeonX6000SCLib.dylib\n 0x7fff6f857000 - 0x7fff6f879fff com.apple.audio.OpenAL (1.8 - 1.8) <43D5D99A-39C3-30F3-BB9E-5B83EEA9DAFD> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff78132000 - 0x7fff78139fff libRosetta.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/libRosetta.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 4\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 55959\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)\nWritable regions: Total=8.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8.8G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 4 \nActivity Tracing 256K 1 \nCG backing stores 3456K 6 \nCG image 1180K 10 \nCoreAnimation 84K 9 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreServices 36K 1 \nCoreUI image data 904K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 6.8G 341 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.5G 16 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 164K 41 \nStack 73.8M 42 \nVM_ALLOCATE 92.1M 777 \n__CTF 759 1 \n__DATA 89.4M 371 \n__DATA_CONST 17.6M 215 \n__DATA_DIRTY 918K 116 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 545.7M 25 \n__OBJC_RO 60.5M 1 \n__OBJC_RW 2449K 2 \n__TEXT 461.6M 370 \n__UNICODE 588K 1 \nmapped file 260.7M 39 \nshared memory 40K 4 \n=========== ======= ======= \nTOTAL 10.2G 2421 \nTOTAL, minus reserved VM space 8.3G 2421 \n\nModel: MacBookPro16,1, BootROM 1554.80.3.0.0 (iBridge: 18.16.14347.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC \nGraphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin\nGraphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 11 2020 17:01:15 version 9.30.440.2.32.5.61 FWID 01-1d69e4b4\nBluetooth: Version 8.0.3d9, 3 services, 25 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.1 Bus\nUSB Device: USB Receiver\nUSB Device: Apple T2 Bus\nUSB Device: Composite Device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```\n\n- Random\n", "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Blender hangs due to deadlock caused by two registered draw handlers\nOperating system: Only happens on Linux (Ubuntu 22.04)\n\nBroken: 3.2.2\nWorked: unknown\n\n\nWhen my addon is used together with the addon [\"node minimap\" ](1366781), Blender hangs/freezes completely under certain conditions (details below).\nTo close Blender in this state, not even Ctrl+C is enough, it is necessary to close the parent terminal from which Blender was started.\n\n\n[addons.zip](addons.zip)\n\n[test.blend](test.blend)\n\n- Install the two addons \"node minimap\" and \"test addon\" from the attached zip file.\n- Enable both addons (search for \"node\" in the addon list to find both).\n- Open the blend file.\n- Convert the editor on the lower left to a Shader Editor.\n# Blender will immediately hang.\n\n\n", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "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", "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>", "Impossible to run Modal operator with simultaneously open props dialog (Blender crashes)\nOperating system: Linux-5.15.4-x86_64-AMD_Ryzen_3_PRO_4350G_with_Radeon_Graphics-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.42.0, 5.15.4, LLVM 13.0.0) AMD 4.6 (Core Profile) Mesa 21.2.6\n\nBroken: version: 2.93.0\n2.93.6, 2.93.7, 3.0.0 and 3.1.0 all are broken.\nWorked: (don't know)\n\nBlender crashes while trying to display operator properties dialog (invoke_props_dialog) and add\nthe same operator as the modal handler (modal_handler_add(self))\nI think it's the same problem as in the (closed) task blender/blender-addons#48196\n\nTry to invoke corresponding operator and then to return {'FINISHED'} or {'CANCELLED'} from the modal() handler.\nThen blender crashes after pressing ESC or closing dialog.\n\nSample code:\n\n```\nimport bpy\n\nclass TEST(bpy.types.Operator):\n bl_idname = \"test.modal\"\n bl_label = \"test invoke props + modal\"\n\n test: bpy.props.StringProperty(\n name=\"test\",\n description=\"test\",\n default=''\n )\n \n def draw(self, context):\n col = self.layout.column(align=True)\n col.prop(self, \"test\")\n\n def invoke(self, context, event):\n context.window_manager.invoke_props_dialog(self)\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n \n def execute(self, context):\n return {'FINISHED'}\n\n def modal(self, context, event):\n if event.type in {'ESC'}:\n return {'CANCELLED'}\n return {'PASS_THROUGH'}\n\ndef register():\n bpy.utils.register_class(TEST)\n\n\ndef unregister():\n bpy.utils.unregister_class(TEST)\n\nif __name__ == \"__main__\":\n register()\n```\n\nI think that impossibility of creating modal operators which can simultaneously have open properties\ndialog for on-the-fly corrections lead to endless tries to create custom bgl-rendered UIs which is just\nan unneeded overhead.\n\nPlease, review the mentioned bug, AFAIK it was already fixed but somehow reappeared upstream...\n", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "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", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "CMD terminal stays open after opening blender\nOperating system: Windows-10-10.0.25247-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\n\nI'm not sure why it';s happening but it's not happening for 3.3 version\n\n\n\n" ]

[ "Blender won't open \nOperating system:\nGraphics card: GTX 1050\n\n**2.79b**\nBroken: may 5 2019\nWorked: may 4 2019\n\n**every time I try to open my blender application the command window opens, then the actual software opens for a second with a grey screen then it closes**\n\n**I simply opened the software on the hardware listed above**\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Show error messages in the info editor\nFollowup task to #83237", "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```", "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", "IDproperty subtype can cause Blender UI to throw exception\nOperating system: Win 10\nGraphics card:\n\nBroken: example: 3.3.1 LTS, b292cfe5a936, master, 2022-10-04\n\nAfter editing an IDproperty subtype through python interface, the blender GUI becomes broken when trying to edit the property\n\nobject.id_properties_ui(\"prop\").update(subtype = ***) will accept NONE', 'FILE_PATH', 'DIR_PATH', 'FILE_NAME', 'BYTE_STRING', 'PASSWORD', 'PIXEL', 'UNSIGNED', 'PERCENTAGE', 'FACTOR', 'ANGLE', 'TIME', 'TIME_ABSOLUTE', 'DISTANCE', 'DISTANCE_CAMERA', 'POWER', 'TEMPERATURE', 'COLOR', 'TRANSLATION', 'DIRECTION', 'VELOCITY', 'ACCELERATION', 'MATRIX', 'EULER', 'QUATERNION', 'AXISANGLE', 'XYZ', 'XYZ_LENGTH', 'COLOR_GAMMA', 'COORDINATES', 'LAYER', 'LAYER_MEMBER'\n\nBut anything other than 'NONE', 'COLOR', 'COLOR_GAMMA', 'EULER', 'QUATERNION' causes Blender UI to throw exception when editing the property.\n\n- open [bug.blend](bug.blend)\n- see the Cube's custom object ID property \"prop\" and that it's editable through the 'gear' button.\n- Change the type to `Float Array`\n- run the included script in text editor or run `bpy.data.objects[\"Cube\"].id_properties_ui(\"prop\").update(subtype='ANGLE')` in python console\n- see the property again in UI and try to edit it.", "Proposal: allow exporting of image annotations\nIt seems essential to me that Blender allows images with annotations to be saved with those annotations in the file.\nProbably as a flag in the file browser, perhaps disabled by default?", "Alembic animation import missing dynamically spawned objects\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.3.1\nWorked: ?\n\n\nHi ! :) I'm trying to import a rigid body sim from houdini, where smalls spheres are spawning during time by wave, the first wave appear in the viewport but the other no. BUT blender still recognize them because i can see the other objects in the Object Path in MeshSequenceCache. The video i attached explain the probleme well. Someone know how to make the other object appearing ? Thanks :D\n\n?\n\n", "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", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "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", "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", "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", "Subdiv hangs blender\n**System Information** DESKTOP-HR30UII\nOperating system:Windows 11 Home Single Language\nGraphics card:2GB NVIDIA GRAPHICS DRIVER\n\n\nBroken: Blender Version 3.5\nWorked: ?\n\nBLENDER 3.5 KEEPS NOT RESPONDING WHILE I USE MODIFIERS \n\nON BLENDER ADD MESH AND ADD MODIFIERS TO SUBDIVISION SURFACE THEN CHANGING THE VALUE OF LEVELS VIEWPORT VALUE ABOVE 4 .THEN ONWARDS BLENDER COMPLETELY STOPS WORKING AND I NEED TO RESTART IT AGAIN\n\n", "Segmentation fault when selecting context.area.type before applying operator (scripting)\nOS: Ubuntu 16.04.4 LTS\nHW: Dell XPS 9550 notebook, using Intel HD GPU (nvidia deactivted)\n\nBroken: 2.83\n\nExecuting the operator `bpy.ops.transform.translate` causes a crash if `bpy.context.area.type` is set manually before.\nCrash in `setTransformViewMatrices` because `t->ar->regiondata` is `NULL`\n\nRunning the following script causes the crash:\n```\nimport bpy\nimport bmesh\n\n# Create object\nbpy.ops.mesh.primitive_plane_add(size=1, enter_editmode=False, location=(0, 0, 0))\n\n# Enter edit mode\nbpy.context.area.type = 'VIEW_3D' # If this is not set, crash does not occur\nbpy.ops.object.mode_set(mode='EDIT', toggle=False)\n\n# Modify vertices\nmesh = bmesh.from_edit_mesh(bpy.context.active_object.data)\nmesh.verts.ensure_lookup_table()\nmesh.verts[0].select = True\n\n# Next call causes crash:\nbpy.ops.transform.translate(value=(0, 0, 1), constraint_axis=(False, False, True),\n mirror=False, use_proportional_edit=True,\n proportional_edit_falloff='SHARP')\n```\n", "Improve performance for Render Engines Addons\n**Status:** Ideas from this thread: 7 to improve speed and ease for external render engines to work with Blender\n\n---\n\n**Team**\n**Commissioner:** @brecht \n**Project leader:** @BrianSavery \n**Project members:** `-` *Optional other developers, can be in multiple projects at once.*\n\n**Description**\n**Big picture:** There are certain issues external renderers working with Blender have that Cycles does not due to it's access to the blender C data structures. Render Engine Addons have to work through the Python API and thus have limited performance. This \"TODO\" will include various subtasks for improving the render engine interface.\n\n**Use cases**: Or possible things that could be improved\n* Faster reading of mesh vertices (as numpy array?)\n* Faster reading of hair or paritcles rather than using particle_system.co_hair(...)\n* Pre-load image data so that image.pixels.foreach_get() is not blocking. (see 9)\n* Detecting deleted objects? \n\n**Branch**: `-` *Existing patches or branches.*\n\n---\n\n**Relevant links**:\n* `-` 19251/", "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" ]

[ "TraceBack Error Report.\nOperating system: Windows\nGraphics card: \n\nBroken: All versions of Blender Including Blender 3.1, 2.79\n\nThe error says : Traceback error.\nI am not able to Import any Obj file.\nPlease help me fix this issue.\n\n\nscreenshot : 👇\n\n\nMy obj file : 👇\n[gaming keyboard.obj](gaming_keyboard.obj)\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", "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", "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", "Particle Edit mode for non hair particles - point select mode crash\nOperating system: Linux-5.6.0-050600-lowlatency-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 3)\n\nBlender crashes when entering into the Particule Edit mode\n\n- Delete all objects from the default scene\n- Create a plane\n- Add a particle system\n- Set end frame to 50\n- Bake the particle system\n- Switch to the Particle Edit mode\n- Select Point select mode\n\n- > Crash\n\n[blender.crash.txt](blender.crash.txt)\n\n\n", "Blender 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", "Crash when rending animation w/simple physics sim\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: Spinning beach ball in 3.1 Alpha\n\nWhen selecting \"Render Animation\", the Rendering window starts to draw, and then the app crashes.\n\n\nFile attached. Just load and Select Render Animation.[simple-physics-crash.blend](simple-physics-crash.blend)\n\n", "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", "Particle Edit mode for non hair particles - 2 Crashes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n\nParticle Edit: 2 Crashes\n\nParticle Edit: 2 Crashes\n\n- Open the blender file and click on the buttons \"Particle select and display point\"\n- Crash 1 (Screenshot)\n\n- Open the blender file and click on the tool \"Weight\" and click into the particles\n- Crash 2 (Screenshot)\n\n- Also had a crash with \"Puff\" \n- file not included\n\n- There are some tools that do nothing while others work\n- User gets no feedback / error message but give no feedback\n\n\n\n[2019-05-19-particle-edit-crash.blend](2019-05-19-particle-edit-crash.blend)\n\n", "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", "Old blend file corrupts to crash blender, I guess\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 20.11.2 27.20.14540.4003\n\nBroken: version: 3.0.0\n\nCrashes here and there. RN I witness crush form select/deselect. help plz ;c\n\nI do, tho, have installed two PROBABLY outdated addons BUT in new file crash doesn't seem to happen.\n\nThe problem is - Idk exact steps, but overall it takes to select/deselect all/smth at all few times\n\nSteps\n- Open the provided .blend below\n- Enter edit mode on the main SN4K3Mesh\n- Select-All, De-Select-All (Repeat)\n\n[#94213-asan.txt](T94213-asan.txt)\n\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF715993808\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF71599380C\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n\n[SN4K3.blend](SN4K3.blend)\n\n[SN4K3.crash.txt](SN4K3.crash.txt)", "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", "Sculpt mode - program crash: brush smooth + graphics tablet\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.30\n\nBroken: version: 3.6.0\n\nUnless explicitly specified in \"preferences > input > tablet > tablet API > wintab or windows ink\", it crashes when using smooth brush. If I use the \"automatically\" setting.\nFor the bug to recur, the brush must take a force or size parameter from the pressure force on the graphics tablet. If I use the mouse, the error does not occur.\nThis error is repeated in any scene and with any object. I created a cube, remesh it and used a smooth brush in sculpt mode. Blender crashes to completion.\n\ngraphics tablet: xp-pen star 06\n\n", "Crash 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", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Cycles 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" ]

[ "Crash when selecting high density imported scan model\nThis is a duplicate of #47537 due to me meaning to attach the .blend file but neglecting to do so.\n[Palmyra.blend](Palmyra.blend)\n\nWindows 10\nNVIDIA GeForce 960M\n\nBroken: 2.77 test2\nWorked: 2.76\n\nDownloaded a model of a scan from browser as an obj. Imported the obj into blender. When I right click to select Blender immediately crashes. The same process in 2.76 does not result in a crash.\n\nRight click on the model\n" ]

[ "3D Viewport: Jump, when mouse crosses a window corner\nOperating system: Windows 10, 64bit\nGraphics card: none (CPU)\n\nBroken: (v 2.82a) and also (v 2.83 Alpha, Date 2020-03-18 17:16, Hash c9c08dc7c873)\nWorked: Never\n\nPossibly any operation in 3D Viewport jumps, if the mouse pointer crosses a corner (not only an edge) of the 3D Viewport window.\n\nTypical scenario: I have zoomed in a lot to edit a detail, and I'm moving an object to the screen center using the `Move the view` tool. If my mouse cursor crosses the 3D Viewport window corner, the object jumps out of sight (disappears).\n\n- Start Blender\n- Choose 2D Animation on the splash screen (-> 2D Animation starts in camera view and draw mode)\n- Zoom out as far as possible (-> you'll see things jump, and not just dissapear)\n- Enable Display Cursor (-> seeing the cursor makes it easier to intentionally hit the corner) \n- Press the `Move the view` tool to move the camera view.\n- Drag the cursor across the window corner with reasonable speed (-> fast to easier hit the corner, slow to distinguish a jump from jerky mouse movement) \n- It's not quite easy to exactly hit the window corner. I correct my motion, if I see the cursor pass in the top left or bottom right corner. With practice, I get a jump about every 10th time, I pass the corner. \n- If a jump occurs, the (fully zoomed out) camera view suddenly jumps to one of the edges of the window.\n\nNote:\nThis happens to me not only with `draw mode`, `camera view` and `Move the view` tool, but likely with any mode, view and tool of the 3D Viewport, that sometimes makes me cross the window corner. I did observe it using\n- Move the view tool\n- Zoom in/out the view tool\n- G-key command to move things\nin\n- camera view\n- 3d view\n- draw mode\n- edit mode\n- maybe object mode\n", "Vertex paint: polygon selection in X-ray mode do not select back faces\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\n\n\nI suppose it is a bug, because , box selection + x-ray have differend behavior in edit mode.\nPlease check. Bug or flaw?\n[2020-01-23_08-12-52.mp4](2020-01-23_08-12-52.mp4)\n[vertex paint polygon selection.blend](vertex_paint_polygon_selection.blend)", "Selected object color is weird in wireframe mode if the object color isn't single.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0 Alpha\n\nOutline overlay seems to be drawn under wireframe.\n\n[#91619.blend](T91619.blend)\n\nImmediately visible in provided file.", "Regression: Curve wire line not displayed in wireframe display mode when it has evaluated mesh/point/volume\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 3.2.0 Alpha\nWorked: 2.93\n\nCaused by b9febb54a4\n\nThe original curve line for curves is not displayed in wireframe display mode.\nThis change only applies when the curve is changed during evaluation, for example, when it is replaced by an evaluated \"tube\" mesh, or points, or a volume, etc.\nThis is very similar to #96138 (Regression: Curve wire line not displayed in edit mode when it has evaluated mesh/point/volume), but for objectmode.\n\n- create a curve\n- in the curve properties, give it a bit of extrude\n- enable viewport shading wireframe OR\n- enable object Viewport Display properties > Wireframe\n\n3.0+\n\n2.93\n\n\n", "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 ", "pixelated Artifacts displayed in 3D view port on the wire frame with 'Outline Selected' On or 'smooth wires overlay' turn on.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.42.01.221031\n\nBroken: version: 3.5.1\n\nPixelated Artifacts are displayed on the selected object's wire frame in the 3D view port, in object mode when viewed through the camera with 'Outline Selected' turned On. The grid floor also has pixelated artifacts on it's wire frame in both edit and object mode when viewed through the camera and 'smooth wires' overlay is turned on in preferences -> view port -> quality. When you rotate the view and it brakes from the camera view the artifacts disappear.\n\nIn 3D view turn on 'Outline Selected' On and or in preferences -> View port -> quality turn on 'smooth wires' overlay.\nBased on the attached .blend file (as simple as possible)\n\n", "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", "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", "Using viewport visibility as a driver doesn't work without constantly updating it in the driver property\nBroken: version 2.93\nWorked: Never (2.8+)\n\n\nUsing viewport visibility as a driver from another object doesn't works unless you constantly hit \"update dependencies\" it in the driver property.\n \n \nFor this, i used the cube's visibility as a driver on the shape key of the sphere.\n[The not working file.blend](The_not_working_file.blend)\nIn the outliner, enable the viewport visibility for the cube, then disable it again. The shape key doesnt update unless you go into the driver property and hit the update dependency button.\n\n\n\n[The working one.blend](The_working_one.blend)\nThis is what i was hoping it would do. The only way I could use viewport visibility as a driver is to use a custom property on that object then use the custom property as a proxy.\n\nIs there a reason why it dont update if you use visibility as a driver from another object or is that a bug?\n\n**Steps to reproduce**\n[The not working file.blend](The_not_working_file.blend)\n\n- Open file\n- Click on Disable in Viewports icon on Cube object in outliner\nSphere shape should be change, but it doesn't", "GPU Subdivision: Wrong objects statistics information\nWindows 10\ni7-4790\n16 GB RAM\nRTX 2070\n\nBlender v3.4.1 (Steam)\n\nWrong objects statistics information in object mode when GPU Subdivision is enabled\n\n- Open `Rat.blend` file\n- Enable GPU subdivision\n- Rotate/move the bone\n- Switch to object mode (notice the viewport statistics)\n\n\n\n", "Orbit around selection not working with modifers in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nWhen \"orbit around selection\" is turned on in the preferences the viewport usually rotates around the selected object - for example a selected vertex.\nIf the objects geometry is influenced by a modifier, though, the viewport does not rotate around the modifieds position of the vertex but still around the original position of the vertex. This can be very limiting, esspecially when using heavily deformed meshes which is often the case when using lattices.\n\n1. Preferences -> Navigation -> check \"Orbit Around Selection\"\n2. create Cube\n3. put simple Deform Modifier on Object\n4. In the modifier next to the Camera and Viewport Display icons press the \"Edit Mode\" icon and the \"On Cage\" icons. (see image)\n5. Select a single vertex of the Cube and rotate the viewport\n6. The viewport does not rotate around the vertex.\n\n\n\n\n", "Wireframe not visible with X-ray in weight paint mode.\nOperating system: Win10\nGraphics card: GTX 1070\n\nBroken: 3.0.0\nWorked: 2.93.6\n\nWireframe on other side of mesh can't be seen through faces when x-ray is enabled.\n\n[#94704.blend](T94704.blend)", "interior rim edges not drawn for wireframe of subdiv + optimal-display\nOperating system: linux\nGraphics card: nvidia RTX 2060\n\nBroken: 3.3.1\nWorked: ?\n\ninterior rim edges not drawn for wireframe of subdiv + optimal-display\n\n(see attached .blend file)\n\nThis is not a bug, just maybe a short-coming.\n\nobject with topological hole (\"Box\")\nviewport_shading = wireframe\nviewport xray = off\nmodifier subdivision surface: - [x] optimal_display\n... inner-boundary of near \"hand-hole\" is not drawn.\n... inner-boundary of near-side rim is not drawn.\n\n[test045_subdivOptDisplay.blend](test045_subdivOptDisplay.blend)\n[system-info.txt](system-info.txt)\n", "\"Loop Cut and Slide\" requires to click anywhere first (different from loop cut)\nOperating system: Windows 10 64bits\nGraphics card: RTX 3070\n\nBroken: Blender 3.1\nWorked: Blender 2.93.6\n\nBehavior changed in f8b51f702c\n\n\nCalling for \"Loop Cut and Slide\" won't start previewing the possible cuts until a first left click is made anywhere on the viewport. This behavior is different from the \"Loop Cut\". It is a very small thing, but it is getting anoying.\n\n - Enter edit mode on the default cube.\n - Search and activate the operator \"Loop Cut\". It will show possible cuts immediately.\n - Search and activate the operator \"Loop Cut and Slide\". It won't show any possible cut until a left click.\n\n[2022-03-21 16-25-50.mkv](2022-03-21_16-25-50.mkv)", "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." ]

[ "Selection does not allways work in 3D-view, wireframe mode\nOperating system: WIN10Pro\nGraphics card: NVIDIA GeForce 980\n\nBroken:\n2.80 (sub 45), branch: master, commit date: 2019-02-22 22:26, hash: 779860d34e26, type: Release\nWorked: (optional)\n\nObject are not allways detected if selected by mouse in wireframe mode\n\nIn defaut 3D-view, add some more objects scattered along X-axis.\nChage view angle so thet object are partially covered by each other.\nSwitch to wireframe (transparent or not) mode, and try to select object by cliking different points on object.\n[system-info.txt](system-info.txt)\n[Selection_problem.blend](Selection_problem.blend)" ]

[ "Can not selection Armature in MacOS Backend Metal.\nOperating system: Macbook pro 14\nGraphics card: Apple M2\n\n3.6.2\n\n\n\nCan not selection wire Armature in MacOS Backend Metal.\n\nrecorded video\n\nview?usp=sharing\n\nWhen Macos' Backend is set to Metal and the Armature object Viewport Display is wire, objects cannot be selected in bone areas other than the root bone at the location of the origin point.\n\n- Open attached .blend file\n- Try to select any bone in wireframe mode", "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", "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", "Select Interior Faces is not working\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nWorked: \n\nthe operator \"select > select all by trait > interior faces\" is not working at all. Honestly I've never used this operator, so I'm not sure of how it should behave, but it doesn't do anything even with the simplest geometry. I tested it in 3.5 and 4.0 Alpha; I can't test it on other releases at the moment because of company installation restriction\n\nthe file attached is just a cube inside another cube in the same object\n\n", "Curves don't have 'All Edges' option for wireframe\nBroken: 2.80\n\nMesh objects have the toggle for its viewport display wireframe to render all edges, but curve objects don't.\n\n\nOpen the attached file and look for the 'All Edges' option.\n[Wiref.blend](Wiref.blend)\n", "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", "Cycles does not respect Object->Holdout option.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0\nWorked: Never (Goes as far back as 3.0 where the object->holdout option is added)\n\n\nCycles does not respect Object->Holdout option.\n\n\n- Open the provided file.\n- Press render.\n- The plane which is set as \"holdout\" doesn't mask the image.\n - Expected: the region of the plane should be zero alpha.\n", "Loop deselect doesn't work in 3 button emulation mode\nOperating system: Windows 7\nGraphics card: irrelevant\n\nBroken: 2.80, 9a8b6d51c12, 2018-12-11 01:35, Branch: blender2.8\n\nWith three button emulation and left click select on in user preferences, no methods for deselecting edge loops work.\n", "Shadow catcher punching holes through objects below it\nOperating system: **Windows 10 Home (Unregistered)**\nGraphics card: AMD **Radeon RX Vega 11 (Integrated. CPU: 2400G)**\n\nBroken: **2.91.2**\nWorked: **None**\n\nThe shadow catcher punches holes through any objects that are below it. I think this is intentional but I don't see any option to toggle it. I remember it working before, could be a hardware issue since I was using a different machine at that time (2nd Gen i3)\n\n\nAdd a shadow catcher and a plane below it to the default scene. Choose Cycles Render and enter rendered view.\n[SCBug.blend](SCBug.blend)", "No (selection) tool in Image editor mask mode (Left-click and drag selection doesn't work)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nLeft-click and drag selection doesn't work in Image editor -> Viewer Node -> Mask mode\n\nCreate a mask in the Image Editor and try to select it with left-click and drag selection\n\n\n", "Add In Front/Visible option to lasso and box mask tools\nCurrently Box Mask and Lasso Mask create the mask through the object, which is not useful in some cases. There should be an in front option to change this behavior. \n\nImplementing this by checking the vertex normal and view direction is trivial, but it won't work as expected on models with occluded vertices facing toward the view. We should evaluate if it is possible to implement vertex occlusion test in sculpt mode. If it is not, then we can use the vertex normal implementation. ", "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.", "VSE's selection not centred to images\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.1.0 Alpha\nWorked: Never\n\nWhen zooming in enough to a selected image's corner, it can be seen that the selection box (white rectangle) reaches outside the image itself. It also happens with a scaled down \"color\" strip.\n\n- Open a \"Video Editing\" workspace and add a \"Color\" strip\n- Scale it down and zoom to a corner\n- To better notice the issue, play with the resolution of the Preview (in Properties)\n\n\nNotes & thoughts:\n- The selection box (white box) is unresponsive to \"aspect ratio\" changes (in Properties)\n- The drifting of the image is somewhat annoying, and sticking the selection box to the image wouldn't fix this.\nSince I don't know how pixel alignment works in the preview, I'm not sure about this, but it may work to instead drift the canvas, leaving the image put like the selection box currently does. So sticking the image TO the selection box.", "Mirror select doesn't select appropriate vertices where there are overlapping verts\nOperating system: Windows 10 Pro\nGraphics card: GTX 1070 + GT710 for extra outputs\n\nBroken: 2019-03-10 22:28\nHash 6fd11a21f5c5\n\n\nCtrl-Shift-M (or using the menu to select mirrored) doesn't select all mirrored verts where there are overlapping verts.\n\n\n[63Stingray.zip](63Stingray.zip)\n\nOpen blend file, hopefully it'll already be in edit mode with the appropriate vertices selected.\n\nShould look like this;\n\n\nFrom there select mirrored from either the select menu, or Ctrl-Shift-M, doesn't matter, and enable the following settings;\n\n\n\nObserve incomplete selection;\n\n\n\nThe area's of incomplete selection are here, where the overlapping underbody verts are in the same location as the verts for the body;\n\n\n\n", "Sculpt: Grid overlay for Grab active point do not work.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nThis seems to be issue only with Nvidia GPUs on windows.\n\nBroken: version: 3.0.0 Alpha\n\n\nGrid overlay for Grab active point do not work.\n[2021-07-18_18-56-46.mp4](2021-07-18_18-56-46.mp4)\n\n\n**Steps to reproduce**\n[#89942.blend](T89942.blend)\n\n- Open file\n- Check if wireframe overlay is drawn under cursor\n\nWhat fixes this is to have any transform gizmo visible while using brush, then it works until Blender is restarted.\n\n\nFrom #92703:\n\n> This was proposed on the blenderartists thread, I have no idea if it works or if it could broke the preview on the AMD cards\n>  \n> If you know how to compile you can fix it by erasing ! from the line 1157 : if (!depth_test) {\n> to read like so: if (depth_test) {\n\n\n" ]

[ "Selecting object in 3D-view does not allways work in wireframe mode\nOperating system: WIN10Pro\nGraphics card: NVIDIA GeForce GTX 980\n\nBroken:\n2.80 (sub 45), branch: master, commit date: 2019-02-22 22:26, hash: 779860d34e26, type: Release\nWorked: (optional)\n\nObject selection by mouse does not detect problem allways\n\nIn default view live default cube in place and greate some other objects along X-axis.\nSwitch to wireframe (transparent or not) mode and try to select object." ]

[ "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\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", "GPU texture baking with large tile size fails\nOperating system: Windows 10\nGraphics card: Vega56\n\nBroken: 2.90.1\nWorked: 2.83.8\nNot sure if this was a particular commit (or if libraries changed at that time) but this broke between 51ac411ce8 and 5c5a638b57\n\nI was trying to bake 8k emissive map but it doesnt work so i was searching for some error about hour a then try to make 4k emissive map and everything worked jsut fine with same settings, only thing i change was resolution of image from 8k to 4k. After this i try again bake 8k emissive but doesnt work image was empty so this must be some sort of bug.\nBased on the default startup or an attached .blend file (as simple as possible).\n[bug.blend](bug.blend)\n\nThis file has its tile size at 8192x8192.\nWith a tile size of 4096x4096 it works fine.", "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "Setting/editing keyframes on multiple characters in pose mode doesn't work for Whole Character and Whole Character(selected Bones Only) options.\nOperating system: Windows 10 Home Edition\nGraphics card: GeForce RTX 2080\n\nBroken: 3.1.0 Master Build\nWorked: never\n\nSetting/editing keyframes on multiple characters in pose mode at the same time only affects the Active Character's Keys on certain insert key options.\nIdeally the insert key options work consistently for all selected characters bones.\n\n - Add two character skeletons to a new scene (Shift+a > Armature > single bone)\n - Select the first bone then Shift+Select the second one.\n - Switch to pose mode\n - hit \"a\" to select all. You should have both bones highlighted\n # hit \"i\" to insert a keyframe.\n - # if you choose Whole Character or Whole character \"Selected bones only\" it will only set a key on the bones for the Active Character.\n - # if you choose any other option it sets keys on both characters.\n\n\n\n\n\n\n**Additional comments:**\nIdeally Whole character would key all characters currently in pose mode.\nand Whole Character (Select bones only) would Key any currently selected bones regardless of which character they belong to.\n\nThe current functionality is confusing, if it is intended, the label should read \"Active Character\" and \"Active Character(selected Bones only)\"\n\nHowever when a user chooses to have multiple characters in pose mode it is because they are trying to pose and key them at the same time without having to switch back and forth with every adjustment. So having the ability to key multiple whole characters, or a random selection of bones belonging to multiple characters would be useful.\n\nThat said keying rotation/translation/scale&custom properties gets me what I need so this is not a blocker but it is something that could be improved for clarity as it will frustrate many animators unaware of this inconsistent behavior for the last two options.\nI was relying on \"Whole character\" and \"whole character (Selected bones only)\" to essentially key everything until I had to do multiple characters and I got confused for a while why my animations were looking janky until a dug into it.", "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", "Hidden Particle paths draw solid [2.79 draws them half transparent]\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 15)\nWorked: (optional)\n\nComparison of particle hiding Blender 2.81 beta and 2.79. I wrote earlier that the particles are not hiding, and this is so fixed?\n\n", "Multi-Object (Weight) Painting\nMulti-object weight painting would be extremely useful when rigging characters with clothing pieces that are separate objects. If a character has a shirt and a jacket, they both have to be weight painted identically, but separately.\n\nThe objects could be combined, but that would mean they must share a modifier stack, which is not always an option. We could also paint one then transfer the weights, but that only works between very similar objects. So we are stuck with meticulously weight painting both clothing pieces, while making sure the weights match between them.\n\nWith multi-object weight paint, the same brush strokes could affect both meshes, so they would be a lot easier to keep in sync.\n\nThe bare minimum functionality that I would consider useful:\n- Be able to select an armature then several meshes that are rigged to it, and enter weight paint mode\n- Selecting a bone activates the relevant vertex group on all meshes\n- Brush strokes affect all meshes\n- Can switch to multi-object edit mode\n- Geometry masking features work\n\nIn my personal workflow, supporting multiple armatures is not important.\nIf anyone thinks this is important, please comment with a use case example.\n\nAdditional functionality that would be nice to have:\n- Indicating active object in the 3D View. So far this hasn't been necessary, since it was always just one object.\n- Changing the active object without leaving weight paint mode. Symmetry settings are stored on the mesh, so this would be needed to be able to access those.\n- All of the above for Vertex and Texture Paint :)\n\nI tried to keep wall of text to a minimum, I hope this is not too bad @ideasman42 :)", "Rigid body bugs\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.21\n\nBroken: version: 2.93.1\n\nSimulation somehow broken for small (less than 1 cm) or light (less then 100 grams) objects. In first example below object stay still between bouncing and small shivering. And that is just one example. Another examples are – reaching speed of light instantly (one frame), partial simulation when one object (or some objects) acts like it suppose to, but others act completely inadequate, two or three similar parts in one simulation (example 2). I tried different options but nothing helped. \"Substeps per frame\" and \"Solver iterations\" seems not working because there are no actual changes with different values or simulation just goes nuts.\n\n[r_body-bug.blend](r_body-bug.blend)\n[r_body-bug2.blend](r_body-bug2.blend)\n", "Particle Texture influence broken when using two particle system on the same object\nOperating system: Ubuntu 18.04\nGraphics card: GeForce 970GTX\n\nBroken: 2.90.1\nWorked: Never (2.8+)\n\n\nWhen using two particles system on the same object with an influencing texture, one particle system has a wrong influence (e.g. Particle System shrink to quickly)\n\nBlend File: [particle_texture_bug.blend](particle_texture_bug.blend)\n\n0. Set the animation start and end to 100 - 200\n1. Create an Emitter and a Particle Object\n2. Add a Particle System to the Emitter and use the Particle Object for rendering\n3. Set the Start and End to 100 - 200\n4. Give the Particle System a Blend Texture that influences the size with \"Strand/Particle\" as Coordinates\n5. Add another System and Duplicate the previous one to get the exact same setting\n6. Change the Start and End of the new System to 0 - 100\n7. Bake all Dynamics\n8. Render Frame 199 and compare to rendering of 101. The particles in 199 are tiny in comparison (or invisible). They should look near identical\n\nOptional: \n9. Remove the 0-100 Particle and Redo Baking\n10. Frame 199 now has normal sized particles\n", "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "not possible to make multiple fabrics with different properties collide\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.15\n\nBroken: version: 3.1.0\nWorked: n\n\n1. By default, it is not possible to make multiple fabrics collide\n2. Use \"jion\" to combine multiple fabrics to generate collision, but it will lose different cloth properties at per object.\n3. Adding collision modifier while using fabric modifier will lead to very unexpected results.\n\nI have created a simple example to reproduce this problem.\n\n - > open the file\n [test_some_cloth.blend](test_some_cloth.blend)\n- > paly animation.\n\n", "Particle simulations dont generate valid disk caches\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 2.93.1\n\nand I tried on the blender-2.83 LTS and it has the same issue.\n\nBlender stops simulating particle systems. if I'm baking them it just puts noting in the bake if I'm rendering without baking first if doesn't do anything except make my fans run full blast.\n\ncreate a bunch of particle sims. Use I used the script in the blend to do it.\nrun bake all dynamics. Only the first few of them actually generate anything.\n\nOf don't bake and just try to render. It freeze.\n\n[bugReportFireworks.blend](bugReportFireworks.blend)", "Vertex Paint bug with Falloff Angle\nBroken: 2.79.x, Win32 & Mac\n\nSee video below.\n\nTo reproduce, set Falloff Angle to 45, and paint (one continuous stroke)\nwith the brush radius approximately equal to the object.\n\nAll by default (2D Falloff and Accumulate is OFF).\n\n[vertex-paint-falloff-angle-bug.blend](vertex-paint-falloff-angle-bug.blend)\n\n---\n\nSmall brush size is ok:\n\n\nIncreased size produces artifacts:\n\n\n---\n\n[vertex-paint-falloff-angle-bug.mp4](vertex-paint-falloff-angle-bug.mp4)" ]

[ "Problems Baking Dynamic Paint with two canvases on one object (Blender 2.80)\nOperating system: Win 10\nGraphics card: GTX 1080Ti\n\nBroken: blender 2.8 2019-04-17 Hash: b46245470f79 \n\n\n\nOnly one Dynamic Paint canvas is cached!! When you have several (e.g. weight and paint) only the results of one is shown (last baked). \n\nIn addition, I found DynPaint Baking only Bake 1 frame and stops. when you delete Bake and bake again, it should work. \n\nFollow my description to understand the issue \n\n\n```\n New BlendFile\n keep the cube, add DynPaint Brush \n add Sphere (or what you like), \n add one Canvas (for now), set to weight, add vertex group as output, (limit frame range for shorter Baking time)\n add Edge split angle = 0\n add Smooth, Factor 0.99, repeat 9, use created Vertex Group \n```\n\n```\n animate cube that it brushes the sphere \n```\n\n```\n bake DynPaint ---> should replay fine \n delete bake \n add a second canvas and Bake the first canvas again (typically it shows \"1 frame on disk\" first; delete Bake, and Bake again and it shows expected number of frames)--> only the final result will be visible over the whole frame range or no effect. \n \n```\n\n - following worked only on first glance, but its actually not working when you wane continue working or render---------\n```\n work around I found to make it work (probably a hint for you)\n Delete both canvas caches \n Bake the second one first (Bake and delete until frames on disk is the expected value)\n Bake the first canvas \n```\n - > now it should be as expect\n ----------------------------------------------------------------------------\n```\n \n \n```\n\nPS:\nIn addition also Cache to Bake also seems affected... but its probably all the same issue otherwise I'll check and report :-) \n\nthx for your work!!! \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nDynPaintTest.blend?dl=0" ]

[ "Ray Visibility (glossy, diffuse, transmission) on light sources generate a different result when using hit by the BSDF or next-event estimation \nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nWhen changing/disabling the ray visibilities on a light source (glossy, diffuse, or transmission), the result becomes\ninconsistent when using only BSDF sampling, next-event estimation, or MIS between both.\n\nThe reason for that is that the contribution of a light source is completely neglected when the type of the BSDF closure used for sampling the direction is disabled on the light source.\nDuring next-event estimation, on the other hand, the light source ALWAYS contributes. Only the BSDF evaluation components multiplied with the light contribution differ [ eg. instead: L*glossy + L*diffuse -> L*diffuse if glossy is deactivated].\n \nThe example shows a scene with one big rectangular light at the ceiling, where glossy rays are disabled on. \nAs you can see, the BSDF image is darker compared to MIS, and the NEE version is a little bit brighter.\n\n\nThe MIS image is more or less a blended version of BSDF and NEE.\nBecause both BSDF and NEE do not converge to the same result, the MIS one is inconsistent/biased.\nSince the blending factors/mis weights depend on the sampling strategies, the result changes when using path guiding or the light tree.\nThis makes these optimized strategies unpredictable and can confuse the artists.\nIn the worst case, they report bugs on for the light tree and path guiding.\n\nA WIP fix is proposed in [D16965](D16965)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Motion blur artifacts on certain frames EEVEE\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nMotion blur on error appears on same certain frames.\n\nblend attached Error appears on frames : 49 , 60, 85, 95, 103, 119,130\n\n[blur test.blend](blur_test.blend)\nnormal frame \n\nerror frame \n\nvideo with error frames [0001-0300.mp4](0001-0300.mp4)\n\n", "Stereo Panorama in EEVEE\nStereo panorama is challenging on its own since we need to support slice rendering.\nNo plans to support this in the viewport, but at least for rendering.\n\nTo be tackled after #68991.", "VDB sequences are rendered blocky here and there ( issues with Volume Displacement Modifier )\nOperating system: Windows 10 \nGraphics card: RTX 2070 CUDA\n\nBroken: blender-3.0.0-alpha+master.ef5a362a5b24-windows.amd64-release.zip\n\n\nBlender renders these blocky frames here and there during the actual render. The VDBs seem to be fine, the same botched render frames look fine in the viewport render. These anomolies are happening only during the actual render. See the attached image (middle right image) for what is happening please.\n\nThe same sequence renders without any issues in Houdini.\n\n(Cycles)\n\n\n\n\nHere is an actual movie render (with Eevee) that shows how horrible this issue is.\n[borkedframes_0001-0200.mp4](borkedframes_0001-0200.mp4)\n\n\n[#88966.blend](T88966.blend)\n[steam.4.0001.vdb](steam.4.0001.vdb)\n\n- Open .blend file\n- Render sequence with CUDA\n\nIssue should appear within 30 frames\n", "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", "Animated curves flickers when Motion Blur and Persistent Data are enabled\nIf there is an animated curve and Motion Blur + Persistent Data are enabled, the curves will randomly appear and disappear. Here is a simplified file that reproduces the issue on master. Render the animation an notice how the curves flicker.\n\n[curvesAnimatedCyclesIssue.blend](curvesAnimatedCyclesIssue.blend)\n\n### Original Report\n\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nDisplay Graphics card: Radeon RX 580 Series 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\nCUDA enabled Graphics card: NVIDIA GeForce GTX 1650 Driver version. DCH 472.12\nCPU: Ryzen 7 2700 (16 threads, 8 cores) \n\n\nBroken: version: 3.2.0\n\n**Description of error**\nObjects disappear from what seems to be random frames close to the beginning of keyframed object transformations in renders produced with Cycles (only).\nThis appears to be the same bug as archived [#40313 ](T40313).\n\n\n\nBug is more prevalent in blender version: 3.1.2 however is still present.\nRender Examples:\n3.1: \n[3.1 build.mkv](3.1_build.mkv)\n3.2: \n[3.2 build.mkv](3.2_build.mkv)\n\nThis Project was using AnimAll addon to animate some of the objects featuring the glitch, these appare to be the only ones still glitching in 3.2. However testing this Addon in a controlled environment does not feature this behaviour, which might suggest its cause is elsewhere, but might be aggravated by animating individual vertices. \n\n* Open Attached Blend file\n* Render Animation in Cycles using files settings.\n\nThis render was made using GPU Compute with CUDA and CPU enabled in system preferences.\nEdit: works on CPU only also. Updated .Blend file with packed textures.\n\nFile removed now simplified is available\n", "Auto perspective sometimes fails\n**System Information** \nOperating system: Windows 10\nGraphics card: 3070\n\nBroken: 3.2.0 and 3.2.1\nWorked: 3.1\n\nAuto perspective setting doesn't work in this case: if you are in camera view or any side view and then you are switching to another side view you have this smooth transition animation between views. If during this animation you press middle mouse button (rotation) to go from side view it doesn't change to perspective. Moreover it \"shifts\" viewport like it was aligned to a bad quad. \n\n1. Turn on auto perspective.\n2. Go to top view.\n3. Change top view to any other side view.\n4. During smooth transition between view press middle mouse button and rotate the viewport.\n5. Now viewport is shifted and stays in orthographic instead perspective.", "Add rotation offset in array modifier\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nIt would be really helpful to have the possibility to use a rotation offset in the array modifier. It is already possible to set this up, with a separate object as rotation offset, but it is time consuming to set up and requires the user to convert from degrees to radians in case the user want to set up a driver for rotation based on the \"count\" property in the array modifier. Duplicating geometry with the array modifier like this is useful if you intend to deform it with a lattice or welding vertices for example. \n\nThe goal is to have a very simple implementation. If complex rotation and translation is needed, using a separate object as offset is a better approach\n\nSee video below for what I'm trying to achieve\n\n[rotation offset.mp4](rotation_offset.mp4)\n\n---\nMockup for additional modifier panel.\nPossibly it could be a \"Factor slider\" per axis instead. \nIf \"X Factor\" == 0.5, the max spin in the X axis would only be 180 degrees\nf \"X Factor\" == 1, the max spin in the X axis would be 360 degrees\n\n\n\n\n\n", "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", "Transform node with bicubic filtering distorts image\nWin 7 64bit\n\nBroken: 2.79\n\nWith untouched settings every other option gives proper \"difference\" result, except Bicubic.\n\n\nOpen file, switch between filtering options and see difference from source image.\n[Bicubic_scale.blend](Bicubic_scale.blend)", "Motion Blur weird artifacts when rendering MeshSequenceCache USD\nOperating system: Windows 11\nGraphics card: RTX 2080 Ti\n\nBroken: 3.6 LTS, but it also seem to happen in older versions\n\n\nI'm getting some weird artifacts when rendering a USD mesh cache with motion blur enabled.\n\nI've exported the mesh from maya 2023 using the Arnold USD export method. \n\nWhat i've tried:\n\n- Disable Auto Smooth Normals and removing every Subdivision Surface Modifier.\n- Trying to change the position of the motion blur from Center to Start or End\n\nThe problem persist.\n\nExport a high res mesh animation from Maya using Arnold USD as export option.\n\nImport it in Blender and try to render the sequence with Motion Blur activated.\n\nBlend file Link : view?usp=sharing \n", "Scaled up images are incorrectly interpolated\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\n\nScaling up strips will result in sharp edge on left and bottom side. This is caused by discarder when `IMB_TRANSFORM_MODE_CROP_SRC` is used\nAdditionally image is not centered correctly. which is caused by incorrect `uv_start` coordinate\n\nPatch [D13124](D13124) resolves incorrect image coordinate. Also uses `IMB_TRANSFORM_MODE_REGULAR` if no cropping is used, but with cropping image will still have sharp edge issue.\n\n\n\n[#103980.blend](T103980.blend)\n\nIssue visible immediately when file is opened\n", "GN +motion blur =bi-direction\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\n\n\n[Мошкара.blend](Мошкара.blend)\n\n", "3.5 Alpha: OSL GPU \"Displacement and Bump\" broken / not implemented\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\nIf displacement maps are used via OSL the result differs from what we get as an image node\n\n\nThis is how the displacement looks like via an image node:\n\n\nAnd this when loaded via OSL OPTIX:\n\n\n\nDemo file:\n[displacement.zip](displacement.zip)\n\nDon't forget to adjust the image path in the OSL file to test:\n\n\n@pmoursnv\nThis is a follow up to #104240 \n\n\n\n", "Coordinate Lines distorted in perspective view\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel Inc. 4.1 INTEL-16.4.5\n\nBroken: version: 2.93.0\nWorked: ? Didn't recognize phenomenon before\n\nIn object/perspective view, the XY-coordinate axes indicators are displayed distorted when I work with one of my .blend files. The issue is not visible if I work\na) in User Orthographic view\nb) with a new file\n\nNote: In Orthographic view the meshes look distorted\n\n\nOpen attached BLEND-File, go to Default view, 3D Viewport, Object Mode, User Perspective\n\nBLEND-File: [HITRAP_BeamlineUnten.blend](HITRAP_BeamlineUnten.blend)\nScreenshot \n\nsimple test file:\n[#89192.blend](T89192.blend)" ]

[ "Render has distortion with stereo, panoramic and motion blur\nOperating system: Linux-5.4.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Ivybridge Mobile Intel Open Source Technology Center 4.2 (Core Profile) Mesa 19.2.6\n\nBroken: version: 2.81 (sub 16)\nWorked: Worked well in GUI mode.\n\nWhen batch render the 3D 360 scene, object with follow path modifier and motion blur enabled, the \"R\" eye image contains distorted object\n\n\n[3D_360.blend](3D_360.blend)\n\n0) Set render engine to \"Cycles\"\n1) set [Stenography] option ON, select [Stereo 3D]\n2) set camera to Panoramic, type Equirectangular\n3) Add object to scene\n4) Add curve to scene (circle for example)\n5) Add constrain [Follow Path]\n6) Add key frames with different offset values to make it move along the path\n7) Enable [Motion Blur] in \"Render properties\"\n8) Save the file and quit blender\n9) Run the rendering in batch mode (for example):\n$ blender -b scene.blend -f 1\n\n10) Examine saved image for _R eye.\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", "Bake diffuse causes exits the program and core dump\nOperating system: Ubuntu 20.04.1\nGraphics card: Sapphire RX 5700 XT with latest drivers 20.45\n\nBroken: 2.83.10, 2.83.9, 2.83,8, 2.90.1\nWorked: \n\nI have cube with simple material. When I hit bake (diffuse), Blender exits immediately.\nInfo from terminal: \n\"Memory access fault by GPU node-1 (Agent handle: 0x7f9faac09b00) on address 0x7f9e1782c000. Reason: Page not present or supervisor privilege.\n./apps.sh: line 34: 84735 Aborted (core dumped) /home/karol/port_apps/blender-2.83.10-linux64/blender\"\n\n", "Multiple Smoke Flow Colors Rendering Black when Flow Behavior is set to Geometry\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 670/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.83.1\nWorked: 2.81 -- N/A, newer versions use fluid settings, but the old smoke sim worked as it should\n\nBaking a smoke domain multiple smoke flow objects with flow set to \"geometry\" and each set to a color results in all of the smoke rendering black.\n\nCreate a smoke domain on any object and place two smoke flow objects inside the domain. Set the smoke color of the smoke flow objects to any color, and the flow behavior to \"geometry\" vs \"inflow\" or \"outflow\". Change the material on the domain object to a material without a surface bsdf but with a volume bsdf whose color is set to the color output of an attribute node with the Name property set to \"color\". Bake the sim and render, and you should observe that all smoke is black, as opposed to the colors set on the flow objects. This works correctly when the flow behavior is set to inflow (except on the first frame), so I'm guessing this has something to do with the initialization of the smoke.\n\n[smoke_multi_color_bug.blend](smoke_multi_color_bug.blend)", "Blender crashing while baking Smoke Domain\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.0 & 3.2.0 Alpha\nWorked: NA\n\n\nBlender Crashes while baking smoke domain\n\n- open Project \n- Select smooth domain from outliner\n- {nav Physic properties > Bake All} (crash between frame 60 & 70)\n\n\n\n\n", "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", "Baking workflow revamp\n*(This design doc is work in progress)*\n\n### Goal\nBaking is hard to use and requires one map to be baked at a time. Each time configuring appropriate settings and selecting the right objects and shader nodes.\n\nBlender should natively have a baking workflow that is more efficient and powerful.\n\n### Existing Work\n\nMultiple add-ons exist to make this workflow easier.\n\nA patch for object-based baking and long discussion about various other options is here:\n[D3203: Baking system overhaul: Move baking settings from render settings into BakePasses](D3203)\n\n### Use Cases\n\n* Baking a set of maps for game assets.\n**Typically includes maps like base color, metallic, roughness, normal map, AO.** The assets may use complex procedural texture nodes, multiple blended shader nodes and multiple materials, all to be baked down to a single set of maps and material that the game engine understands.\n**Exporters like FBX or glTF would typically want to export this baked material representation.** Efficiently re-baking objects, inspecting the results in the viewport, and applying the same settings to other assets is important.\n* Baking to optimize rendering\n**Some part of a shading network may be baked down for more efficient rendering, either as a viewport approximation or final render. Maybe a complex procedural texture, static background or ray-traced AO/curvature.** Light maps may also be considered part of this, though I personally would not recommend to use them for Cycles or Eevee and not focus on this use case.\n* One-off bakes\n**Examples may be to create a base to start texture or vertex painting, to use in geometry nodes, etc.** The current workflow is reasonably well suited to this, but automatic creation of images or vertex color layers and preview of the result would be helpful.\n** Perhaps best integrated as an operator/tool in paint or edit modes.\n* Other\n**Light map baking for export: how important is this still in modern game engines?** Baking as a part of a geometry nodes network?\n**Baking to transfer attributes between objects: use Data Transfer modifier instead?** ... ?\n\n### Proposal\n\nThere is not a single workflow that is ideal for all uses cases. I suggest to have two workflows that I think will handle the most important ones well, and can work for others with some extra effort. The Bake panel in the scene render properties would be removed.\n\n**One-Off Bakes**\n\n* New operator to quickly bake to images or attribute\n* Operator pops up a dialog, with choice for bake type and relevant settings\n* No settings stored in the scene. Only operator properties, remembered for the next operator execution\n* Operator creates new images or attribute if none exists, or bake to active one\n* Likely exposed in vertex, sculpt, texture paint mode, and in the vertex colors panel\n* No selected to active baking support here\n\n**Material Based Bakes**\n\n* New Bake Texture shader node\n**Bake type and relevant settings** One bake type is an input socket with arbitrary shader nodes plugged in\n**Image or attribute to bake to** Bake/Clear button\n* New Material datablock settings\n**Bake panel in material properties shader node editor, visible when there are any Bake Texture nodes** Bake/Clear button for the entire material\n**Collection property for \"selected to active\" baking, no use of selection state.** Any other shared settings\n\nWith this system, it's possible to create a reusable shader node group for a baked material, or manually add a few Bake Texture nodes for specific cases.\n\nA big advantage of this approach is that the baked result is also immediately previewable in the viewport and usable in the final render. No need to set up bake settings in one place, and a preview shader node setup in another place.\n\nMore details to be worked out\n* Likely need an Image socket type, to make shader node groups really reusable?\n* How to handle baking multiple materials into one, special material slot that all materials bake into? \n** Potentially confusing to have two ways to bake, using either this special slot or as part of regular material slot\n* Precise workflow to clear bakes and decide if baked/unbaked is show in viewport and render\n\n### Python API\n\nWe expect add-ons will continue to be needed for more advanced use cases and automation. Currently these use the Bake operator, but a lower level Python API function could be added, which does not rely on selection state, but rather accepts specific objects, materials, attributes, etc.\n\n### Missing Features\n\n* Metallic, Base Color and possibly other types\n* Packing bakes into specific channels, and multiple maps into one image or attribute", "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", "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", "Use after Free (according to asan) while baking.\nOperating system: Linux-5.4.0-90-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked:Don't know\n\nWhen pressing 'bake' in the attached (simple) blend file blender crashes when compiled with address sanitizer. Strangely only when in the UV-editor workspace, and not in the shading workspace.\n\n\n- build blender in debugmode with developer options\n- open the attached .blend\n- press bake\n\n\n[printuvs.blend](printuvs.blend)\n\nOr else from default startup:\n- build blender in debugmode with developer options\n- add a noise texture + colorramp to the base color input of the default material\n- add an image texture (sized 128x128) to the material and make it active\n- switch to uv editor workspace\n- switch renderer to cycles\n- open bake tab, choose diffuse bake\n- press bake\n\nASAN output:\n```\n\n==30632==ERROR: AddressSanitizer: heap-use-after-free on address 0x613000566c90 at pc 0x000006232e48 bp 0x7fff79d57550 sp 0x7fff79d57540\nREAD of size 4 at 0x613000566c90 thread T0\n - 0 0x6232e47 in paint_object_is_rendered_transparent /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_paint.c:52\n - 1 0x62333f5 in OVERLAY_paint_init /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_paint.c:75\n - 2 0x61e20f1 in OVERLAY_engine_init /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_engine.c:138\n - 3 0x60336a7 in drw_engines_init /home/martijn/progs/blender-git/blender/source/blender/draw/intern/draw_manager.c:1037\n - 4 0x60394be in DRW_draw_render_loop_ex /home/martijn/progs/blender-git/blender/source/blender/draw/intern/draw_manager.c:1641\n - 5 0x6038abd in DRW_draw_view /home/martijn/progs/blender-git/blender/source/blender/draw/intern/draw_manager.c:1571\n - 6 0xadf0436 in view3d_draw_view /home/martijn/progs/blender-git/blender/source/blender/editors/space_view3d/view3d_draw.c:1573\n - 7 0xadf05bf in view3d_main_region_draw /home/martijn/progs/blender-git/blender/source/blender/editors/space_view3d/view3d_draw.c:1595\n - 8 0x7f2353c in ED_region_do_draw /home/martijn/progs/blender-git/blender/source/blender/editors/screen/area.c:564\n - 9 0x53d6339 in wm_draw_window_offscreen /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_draw.c:730\n - 10 0x53d7569 in wm_draw_window /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_draw.c:880\n - 11 0x53d89d8 in wm_draw_update /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_draw.c:1081\n - 12 0x53c5120 in WM_main /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm.c:658\n - 13 0x34c4239 in main /home/martijn/progs/blender-git/blender/source/creator/creator.c:558\n - 14 0x7f41af1ae0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n - 15 0x34c35bd in _start (/mnt/fast/martijn/progs/blender-git/build_linux_debug/bin/blender+0x34c35bd)\n\n0x613000566c90 is located 208 bytes inside of 360-byte region [0x613000566bc0,0x613000566d28)\nfreed by thread T20 here:\n - 0 0x7f41af9ef1c7 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:123\n - 1 0x1bb10832 in MEM_lockfree_freeN /home/martijn/progs/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:130\n - 2 0x5f86383 in blender::deg::IDNode::destroy() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/node/deg_node_id.cc:143\n - 3 0x5e21387 in clear_id_nodes_conditional<blender::deg::Depsgraph::clear_id_nodes()::<lambda(ID_Type)> > /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:162\n - 4 0x5e1e4c0 in blender::deg::Depsgraph::clear_id_nodes() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:173\n - 5 0x5e1cdf8 in blender::deg::Depsgraph::~Depsgraph() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:89\n - 6 0x5e20080 in DEG_graph_free /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:325\n - 7 0x9ca04e1 in bake /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1608\n - 8 0x9ca3d40 in bake_startjob /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1775\n - 9 0x5461946 in do_job_thread /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:393\n - 10 0x1bae287e in tslot_thread_start /home/martijn/progs/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 11 0x7f41af920608 in start_thread /build/glibc-YbNSs7/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread T20 here:\n - 0 0x7f41af9ef6f7 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154\n - 1 0x1bb10f20 in MEM_lockfree_callocN /home/martijn/progs/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:236\n - 2 0x370cccf in BKE_libblock_alloc_notest /home/martijn/progs/blender-git/blender/source/blender/blenkernel/intern/lib_id.c:1095\n - 3 0x5f84eff in blender::deg::IDNode::init_copy_on_write(ID*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/node/deg_node_id.cc:114\n - 4 0x5e1e02c in blender::deg::Depsgraph::add_id_node(ID*, ID*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:127\n - 5 0x5fa14e5 in blender::deg::DepsgraphNodeBuilder::add_id_node(ID*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:178\n - 6 0x5fcd141 in blender::deg::DepsgraphNodeBuilder::build_material(Material*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1797\n - 7 0x5fcdee5 in blender::deg::DepsgraphNodeBuilder::build_materials(Material**, int) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1819\n - 8 0x5fb47b3 in blender::deg::DepsgraphNodeBuilder::build_object_data(Object*, bool) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:941\n - 9 0x5fb0010 in blender::deg::DepsgraphNodeBuilder::build_object(int, Object*, blender::deg::eDepsNode_LinkedState_Type, bool) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:787\n - 10 0x601516d in blender::deg::DepsgraphNodeBuilder::build_view_layer(Scene*, ViewLayer*, blender::deg::eDepsNode_LinkedState_Type) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes_view_layer.cc:117\n - 11 0x5f19f8e in blender::deg::ViewLayerBuilderPipeline::build_nodes(blender::deg::DepsgraphNodeBuilder&) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/pipeline_view_layer.cc:35\n - 12 0x5f06808 in blender::deg::AbstractBuilderPipeline::build_step_nodes() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/pipeline.cc:72\n - 13 0x5f058af in blender::deg::AbstractBuilderPipeline::build() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/pipeline.cc:51\n - 14 0x5e2ff1d in DEG_graph_build_from_view_layer /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph_build.cc:259\n - 15 0x9c9c19e in bake /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1236\n - 16 0x9ca3d40 in bake_startjob /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1775\n - 17 0x5461946 in do_job_thread /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:393\n - 18 0x1bae287e in tslot_thread_start /home/martijn/progs/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7f41af920608 in start_thread /build/glibc-YbNSs7/glibc-2.31/nptl/pthread_create.c:477\n\nThread T20 created by T0 here:\n - 0 0x7f41af996a65 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216\n - 1 0x1bae2aa8 in BLI_threadpool_insert /home/martijn/progs/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x546296a in WM_jobs_start /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:488\n - 3 0x9ca69f8 in bake_invoke /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1938\n - 4 0x53e6d36 in wm_operator_invoke /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1347\n - 5 0x53e8c9e in wm_operator_call_internal /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1554\n - 6 0x53e8ef9 in WM_operator_name_call_ptr /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1602\n - 7 0x53ea323 in WM_operator_name_call_ptr_with_depends_on_cursor /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1790\n - 8 0xa4d665e in ui_apply_but_funcs_after /home/martijn/progs/blender-git/blender/source/blender/editors/interface/interface_handlers.c:1030\n - 9 0xa565bfd in ui_handler_region_menu /home/martijn/progs/blender-git/blender/source/blender/editors/interface/interface_handlers.c:11435\n - 10 0x53e0497 in wm_handler_ui_call /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:690\n - 11 0x53f88dc in wm_handlers_do_intern /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3052\n - 12 0x53f99d3 in wm_handlers_do /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3166\n - 13 0x53ffb0e in wm_event_do_handlers /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3656\n - 14 0x53c5108 in WM_main /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm.c:652\n - 15 0x34c4239 in main /home/martijn/progs/blender-git/blender/source/creator/creator.c:558\n #16 0x7f41af1ae0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_paint.c:52 in paint_object_is_rendered_transparent\nShadow bytes around the buggy address:\n 0x0c26800a4d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4d70: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd\n 0x0c26800a4d80: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n=>0x0c26800a4d90: fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4da0: fd fd fd fd fd fa fa fa fa fa fa fa fa fa fa fa\n 0x0c26800a4db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4dc0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4de0: fa fa fa fa fa fa fa fa 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 Shadow gap: cc\n==30632==ABORTING\n```\n\n\n", "Object Data Properties, Normals, Auto Smooth Angle not working in Sculpt\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.4.1\n\nNormals, Auto Smooth Angle not working in Sculpt, is this an bug or why is this not working?\n[2023.01.14-21.18.36.mp4](2023.01.14-21.18.36.mp4)\n\n1. On default cube set Shade Smooth.\n2. Object Data Properties -> Normals -> ON.\n3. Go to sculpt mode\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)", "Rendering animation using \"Generate\" type modifiers after animated displacement texture crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.83.10\n\nIf 2 high poly (~100k faces per obj) objects in modifiers properties have after Displacement modifier (with animated texture) \"Generate\" type modifiers (I've tried Boolean and Decimate), Blender cant run Animation render (but still can run Image render). \nCrash happens on 2.9 and higher. I've tested this on 2.83.10 LTS (from steam) and everything worked fine there.\nCrashes with Decimate a little bit hard to recreate. So I will go with steps for \"Boolean crash\"\n\n- create Cude, Empty and Icosphere\n- Add Subdivision mod. to Cube: set it to \"Simple\" and 7 levels\n- Add Displacement mod. to Cube and set texture (Clouds) coordinates to object - Empty\n- Add Boolean mod. (difference) and select object Icosphere\n- Select Cude with Icosphere and duplicate them\n- Save and press Render Animation\n[bug.blend](bug.blend)\n[bug.crash.txt](bug.crash.txt)\n\n```lines\n## 3883==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500034ec08 at pc 0x000016fc795d bp 0x7fffc19dd6c0 sp 0x7fffc19dd6b0\nREAD of size 8 at 0x61500034ec08 thread #15\n - 0 0x16fc795c in blender::gpu::GLBatch::verts_(int) const /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112\n - 1 0x17013501 in blender::gpu::GLVertArray::update_bindings(unsigned int, GPUBatch const*, blender::gpu::ShaderInterface const*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_array.cc:124\n - 2 0x16fa900b in blender::gpu::GLVaoCache::vao_get(GPUBatch*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:273\n - 3 0x16fa84d8 in blender::gpu::GLVaoCache::base_instance_vao_get(GPUBatch*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:234\n - 4 0x16fa9d3e in blender::gpu::GLBatch::bind(int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:317\n - 5 0x16fa9f3f in blender::gpu::GLBatch::draw(int, int, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:328\n - 6 0x16eca2be in GPU_batch_draw_advanced /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_batch.cc:282\n - 7 0x16fc1207 in blender::gpu::GLDrawList::append(GPUBatch*, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_drawlist.cc:122\n - 8 0x16efa9f5 in GPU_draw_list_append /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_drawlist.cc:52\n - 9 0x5978acc in draw_indirect_call /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:598\n - 10 0x5978acc in draw_call_batching_flush /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:795\n - 11 0x597c5f0 in draw_call_batching_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:891\n - 12 0x597eae7 in draw_shgroup /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1056\n - 13 0x597f89f in drw_draw_pass_ex /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1113\n - 14 0x597fe50 in DRW_draw_pass /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1153\n - 15 0x5c51bc0 in EEVEE_velocity_resolve /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:466\n - 16 0x5c5202b in EEVEE_draw_effects /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:486\n - 17 0x5a21f42 in EEVEE_render_draw /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_render.c:671\n - 18 0x59b1dbc in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:559\n - 19 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 20 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 21 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 22 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 23 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 24 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 25 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 26 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 27 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 28 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 29 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 30 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n - 31 0x7ffff6f46292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)\n\n0x61500034ec08 is located 8 bytes inside of 512-byte region [0x61500034ec00,0x61500034ee00)\nfreed by thread #15 here:\n - 0 0x7ffff76927cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)\n - 1 0x18e0eab0 in MEM_lockfree_freeN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:129\n - 2 0x16ef56c6 in blender::gpu::GLVertBuf::operator delete(void*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x17018021 in blender::gpu::GLVertBuf::~GLVertBuf() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:35\n - 4 0x16f8bb19 in blender::gpu::VertBuf::reference_remove() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer_private.hh:94\n - 5 0x16f877f5 in GPU_vertbuf_discard /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:161\n - 6 0x5a0eab8 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:449\n - 7 0x59b1bef in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:542\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread #15 here:\n - 0 0x7ffff7692bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)\n - 1 0x18e0f510 in MEM_lockfree_mallocN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:276\n - 2 0x16ef5676 in blender::gpu::GLVertBuf::operator new(unsigned long) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x16ef70a2 in blender::gpu::GLBackend::vertbuf_alloc() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_backend.hh:121\n - 4 0x16f85d10 in blender::gpu::VertBuf::duplicate() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:77\n - 5 0x16f8750d in GPU_vertbuf_duplicate /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:149\n - 6 0x5a0ee06 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:467\n - 7 0x59b1953 in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:507\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\nThread #15 created by T0 here:\n - 0 0x7ffff75bf805 in pthread_create (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)\n - 1 0x18de42b9 in BLI_threadpool_insert /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x4fee516 in WM_jobs_start /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:484\n - 3 0xd7b88bd in screen_render_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:1041\n - 4 0x4f8f3ba in wm_operator_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1293\n - 5 0x4f912f2 in wm_operator_call_internal /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1500\n - 6 0x4f91551 in WM_operator_name_call_ptr /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1548\n - 7 0x90f1c95 in ui_apply_but_funcs_after /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:932\n - 8 0x917b8d0 in ui_handler_region_menu /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:10809\n - 9 0x4f88a9b in wm_handler_ui_call /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:636\n - 10 0x4f9ec36 in wm_handlers_do_intern /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2757\n - 11 0x4f9fc78 in wm_handlers_do /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2865\n - 12 0x4fa537f in wm_event_do_handlers /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3288\n - 13 0x4f732cf in WM_main /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm.c:635\n - 14 0x34f58fa in main /home/dev/01-data/01-git/blender-git/blender/source/creator/creator.c:522\n - 15 0x7ffff6e4b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112 in blender::gpu::GLBatch::verts_(int) const\nShadow bytes around the buggy address:\n 0x0c2a80061d30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa\n 0x0c2a80061d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n# >0x0c2a80061d80: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061da0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c2a80061dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n```\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07 \nHeap left redzone: fa\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb\nShadow gap: cc\n```\n", "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", "EEVEE baking\n", "Cleanup: Explicit Colors\nAnnotating colors in `BLI_color.hh` with the goal that it becomes more clear in the code what color and alpha association is used.\n\nSee proposal-explicit-colors/\n\n- Changes to BLI_color.h + migration of existing code (Function + Geometry nodes): [D10978: Blenlib: Explicit Colors.](D10978)\n- Compostor: Is already CPP and some operations use color space conversions.\n- Color picker: There is an effort to move more UI code to CPP Color picker is one that would benefit in readability.\n- Draw manager: Although this is in limited places.\n- Blenkernel: blenkernel (colorband, gpencil, image_gen, studiolight) seems like small tweaks.\n" ]

[ "Crash when baking to vertex colors while \"Normals-> Auto Smooth\" is enabled.\nOperating system: Linux-5.8.0-53-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 2000 (SNB GT1) Intel Open Source Technology Center 3.3 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0\nWorked: 2.92\n\nCaused by 85be72c1cc\n\nSelecting 'Bake' with Output->Target set to 'Vertex Colors' crashes blender when \"Normals-> Auto Smooth\" is enabled.\n\nFrom a new scene:\n1 - Set render engine to Cycles\n2 - Create new vertex colors on 'Object Data Properties' for the default cube.\n3 - Enable Normals->Auto Smooth on the cube.\n3 - Set Bake->Output->Target to 'Vertex Colors'\n4 - With the cube selected, press bake.\n\n\nFrom blender file:\n1 - With the cube selected, press bake.\n[bug.blend](bug.blend)\n\n" ]

[ "Blender crashes with Noise Texture Node + Hair Particle System + Eevee\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 480 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: 8dc95f61f3\nBroken: version: 2.92.0\nBroken: version: 2.91.2\nWorked: version: 2.83.12\n\nBlender 2.92 with AMD crashes with **Noise Texture Node**and **Hair Particle System** with render engine Eevee.\nWith Blender 2.91.2 with AMD it doesn't crash but colors are incorrect.\n\nWith 8dc95f61f3 with Intel GPU, there's no crash but colors are incorrect in the same way as in AMD - 2.91.2.\n\n1. Open attached .blend file\n2. Viewport shading to: Render \n3. Play animation by tapping space bar\n\n[particle_loop.blend](particle_loop.blend)\n[blender_2_92_crash.txt](blender_2_92_crash.txt)\n\n**Blender 2.92**\n[blender_2_92.mp4](blender_2_92.mp4)\n\n**Blender 2.91**\n[blender_2_91_2.mp4](blender_2_91_2.mp4)\n\n**Blender 2.83.12**\n[blender_2_83_12.mp4](blender_2_83_12.mp4)", "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)", "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`.", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "Correct link is shown as invalid\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIn the composer, after some actions, the link is displayed as incorrect, although there is no reason for this.\n\n**Exact steps for others to reproduce the error** \n\n0. Factory settings file (optional).\n1. Switch render engine to Cycles.\n2. Enable any `Scene > ViewLayer > Passes`. For example, this would be `... > Data > UV`.\n3. Enable the compositing nodes and connect the new socket to the \"Composite\" node.\n4. Switch render engine to Eevee.\n5. Make a Render.\n6. Switch render engine to Cycles.\n\n\n\n", "blender3.4 alpha new eevee a rendering on the flashback\nOperating system:windows10 21h1\nGraphics card: amd 6800xt （22.7.1 driver opengl doubled the performance of a version)\n\nBroken: blender-3.4.0-alpha+master.ca172677b1a7-windows.amd64-release\nWorked: There is no version that can be tested\n\n\nScene any scene including cube, whether window rendering or f12, directly exit the software.", "EEVEE AOV of full transparency is bad compared to Cycles\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4\n\nAOV of full transparent shader is barely noticeable. Cycles works fine.\n\n\n[eevee_aov_transparent.blend](eevee_aov_transparent.blend)\nFor default scene:\n\n - Set fully transparent shader (alpha clip or hashed) and add AOV layer for it\n - Render EEVEE -> AOV layer is bad\n\n", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)", "Crash 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)", "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", "EEVEE doesn't take collection visibility in account with collection instances\nOperating system: Arch Linux and Windows 10\nGraphics card: Intel UHD 620 and NVIDIA GTX 1060 Super\n\nBroken: `3.1 Alpha 43b0ff3054ba`; `3.0 Beta fb0ea94c6303`; `LTS 2.83.19`\nWorked: \n\nWhen baking (cubemaps or irradiance) with visibility collection set, it will ignore collection instances.\n\nTo explain, I've prepared the following screenshot, hopefully it will explain the situation well.\n\n\n\nAs you can see, the cubemap has visibility collection set to *Collection*, where a *Plane, Cube and an instance of Real* are present, however in the cubemap only the *Plane and Cube* are visible, while the instance is left out.\n\nAs a reference, this is how it should've looked like (this was after instances were made real):\n\n\n\n1. Open the appended file\n2. In render settings, under indirect lighting: *Delete Lighting Cache* and *Bake Cubemap Only*\n3. Switch to Renderered view\n4. Observe the missing floating instance of Real\n[eevee_visibility.blend](eevee_visibility.blend)", "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).", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)" ]

[ "Blender EEVEE crashes while baking indirect lighting\nOperating system: Windows 10 1803\nGraphics card: RX 570\n\nBroken: (example: 2.80, f606f588455e, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen opening previous project in this Blender 2.8 f606f588455e beta build, while baking indirect lighting Blender gets crash and bring to the desktop. This was working correctly till 15/05/2019 build after that problem started.\n\nBased on the default startup or an attac{[F7055128](Blender_2.8_Crashes.mp4)}hed .blend file (as simple as possible).", "Blender 2.8 - Bake Indirect Lighting or Cubemap stuck in a loop and sometimes crash with Auto Bake selected.\nOperating system: Windows 7 64-bit\nGraphics card: GeForce GTX 1060 6GB\n\nBroken: blender-2.80, 99d4321feff6-win64 2019-03-29\nWorked: (optional)\n\nIf Auto Bake is selected, clicking \"Bake Indirect Lighting\" or \"Bake Cubemap only\", it never finishes with the calculation. It looks like it starts over and over in a loop. \nPerhaps it's an unrelated issue but I notice the progress bar does not show up while this is going on unless I move mouse cursor around over the bottom info bar or other UI elements. \nI can only exit the loop if I uncheck Auto Bake again. During my earlier tests it sometimes made blender crash/close after a while, but that has not happened for me anymore today.\n\nOpen attached blend file.\nChoose Rendered view mode.\nMake sure Auto Bake is ticked.\nClick \"Bake Cubemap Only\" button.\nObserve how the reflection under the sphere fade in and out as if it recalculates over and over.\n[autobake_bug.blend](autobake_bug.blend)" ]

[ "Blender 2.8 and 2.81 (ab519b91b2c4) has high chance of crashing when using Python to create a new node-tree link.\nOperating system: Windows 10 (x64) v1903 Build 18362.356\nGraphics card: Nvidia GeForce GTX 1060 6GB\nCPU: Intel Core i5 7600K\n\nBroken: 2.81-ab519b91b2c4 **AND** 2.80 release\n\nCreating a new node-tree link via Python sometimes causes Blender to crash with the error \"EXCEPTION_ACCESS_VIOLATION\".\nI have attached a .blend file that will cause the crash, just by clicking \"Run Script\" once or twice. \nWhen I found the bug, I spent some time making the script as small as possible while still causing the crash, so the script is less than 30 lines.\n\nI also installed Blender 2.81-ab519b91b2c4 on a Windows 10 laptop that had never seen Blender before, and the bug was present on there too, so I'm confident the issue isn't specifically due to my hardware.\nI've also included blender_debug_output.txt and blender_system_info.txt, generated by the blender_debug_log.cmd file included in the Blender 2.81 download.\n\n1) Open the attached .blend file.\n2) Click \"Run Script\" in the bottom right of the text editor pane.\n3) Repeat 2 until crash (should only take 1 or 2 tries)\n\n[Crashy crash.blend](Crashy_crash.blend)\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Texture Node editor --->creating image , then use created image as input node in texture node editor \nwin 10 \namd radeon \nintel i5\n\n Blender 2.8\n3d8cbb534f82\n\n\n First of all ,this is specifically about the \"texture node editor set to brush for creating an image , then using the created image as an image input in the (brush ) node editor , and again paiting in the SAME image ...\nIt totally makes sens that blender crashes because it is trying to create an image where the brush is that image itself , thus creating a feedback loop \n\n\nSteps to reproduce crash\n\n\n- Create plane \n- Go to the shader editor and create an image texture node \n- Create a new file , let's call this one ''crash'' and route it the shader's colour input \n- Go to the 'texture node editor and from the dropdown select 'brush''\n- Click the 'new tab' and enable úse nodes , by default we are presented with the checker pattern \n- go to the image editor and draw something , we are presented with a checker pattern \n- Now go back to the texture node editor'' and select ímage 'from the input nodes and route it to the tout\n- Select çrash 'as image \n- Now paint something in the image editor \n\nCrash \n\nIn the provided file , everything is already set up , al you have to do is paint in the image editor , and then route the module labeled çrash'to the output of the texture node editor [feedback crash .blend](feedback_crash_.blend)\n\n ", "Segmentation fault when selecting context.area.type before applying operator (scripting)\nOS: Ubuntu 16.04.4 LTS\nHW: Dell XPS 9550 notebook, using Intel HD GPU (nvidia deactivted)\n\nBroken: 2.83\n\nExecuting the operator `bpy.ops.transform.translate` causes a crash if `bpy.context.area.type` is set manually before.\nCrash in `setTransformViewMatrices` because `t->ar->regiondata` is `NULL`\n\nRunning the following script causes the crash:\n```\nimport bpy\nimport bmesh\n\n# Create object\nbpy.ops.mesh.primitive_plane_add(size=1, enter_editmode=False, location=(0, 0, 0))\n\n# Enter edit mode\nbpy.context.area.type = 'VIEW_3D' # If this is not set, crash does not occur\nbpy.ops.object.mode_set(mode='EDIT', toggle=False)\n\n# Modify vertices\nmesh = bmesh.from_edit_mesh(bpy.context.active_object.data)\nmesh.verts.ensure_lookup_table()\nmesh.verts[0].select = True\n\n# Next call causes crash:\nbpy.ops.transform.translate(value=(0, 0, 1), constraint_axis=(False, False, True),\n mirror=False, use_proportional_edit=True,\n proportional_edit_falloff='SHARP')\n```\n", "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", "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", "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.", "Dae parsing issue\nOperating system:Windows 10\nGraphics card: NVidia gforce GTX660\n\n 2.79\n\n\nIt is a common error, when trying to upload an object to Second-life or Opensim, to be unable to upload a model,created in Blender, due to a \"DAE parsing issue\"\nThis object is one that is effected.\n\n[lowpol.blend](lowpol.blend)\nExport as .DAE file and upload to Opensim or Second-life", "Blender 2.90.1 crashes after rendering the first few frames of animation.\n**System Information** \nOperating system: windows 10 64 bit\nGraphics card: Nvidia GeForce GTX 1650\n\nBroken: (2.90.1 3e85bb34d0d7; master)\nWorked(didn't): (only tried on 2.8.3 and did not work at all)\n\nWhen I try to render the animation, after about 50 or so frames(varies randomly), blender crashes with no alerts or anything that tells me what the error is, it simply closes.\nI've rendered another project, and that did indeed render, so I'm left confused why this short animation would cause a crash.\n\nEdit: I disabled motion blur, and it rendered fine. However, I would really like to know why blender won't render if motion blur is enabled. The renderer is Eevee and while my laptop isn't a super computer, it should be able to handle it. Thank you all in advance!\n\n- Open attached file\n- render the animation\n[cube-loop-tut-V1.0.blend](cube-loop-tut-V1.0.blend)", "Crash 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", "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 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.", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Blender 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" ]

[ "ERROR EXCEPTION_ACCESS_VIOLATION IN WINDOWS 10 (64BIT)\nOperating system: Windows 10 Pro\nGraphics card: Integrated Radeon(tm) HD Graphics\n\nBroken: # Blender 2.91.0, Commit date: 2020-11-25 08:34, Hash 0f45cab862b8\nWorked: None. I just downloaded Blender for the first time and it just crashed.\n\nWell, I downloaded Blender, installed it, opened it, and it just crashed after showing a code screen for a few miliseconds\n\nOpen Blender\n\nI have a .txt which I think is a kind of bug report: [blender.crash.txt](blender.crash.txt)" ]

[ "iMac CRASH through Blender 3.6.0 ASSET.\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.6.0 Alpha\n\niMac CRASH through Blender 3.6.0 ASSET.\n\nMacOS 13.4\nBlender cause bad memory leak through ASSET open.\ndemo-files/\n\nClick ( Cube Diorama )\nthen\nOpen Cube Diorama.alend\ncause bad memory leak cause iMac crash.\n\n\nSee my youtube. A2d0Wu8ig-w", "Local view mode is not exited correctly when closing New Windows\nOperating system: Mac OS*\nGraphics card: Macbook pro M1 MAX, 64G ram\n\n**Blender Version** 3.41 (same issues found in 3.2)\nBroken: Local view doesn't work(/)\nWorked: \n\nit's hard to say when it will happened, I used MacBook with two monitors, (one is Mac Studio, an other one is iPad Pro), when I duplicate a new windows to my second screen, like to iPad for sculpting, some times, local view function(hot key\"/\") doesn't work and show 'no more than 16 local views\" error. I met this error 3times from version 3.2 to 3.41\n\n\n\n\n- Repeat the following 16 times\n - Open a new `Window`->`New Window`\n - Go into Local view in the new 3d viewport that appears\n - Close the window while still inside local view\n- Attempt to go into local view 1 more time\n- Observe failure\n\nThe issue is that local view mode is not exited when those temporary New windows are closed. Blender continues to think that those local views are still in use and runs out of available space for any new ones.\n\n[test.blend](test.blend)\n\n", "Blender 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 viewport render doesn't resize if an animation is playing.\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple `M1` Pro Apple 4.1 Metal - 83\n\nBroken version: 3.5.0 Alpha\nBroken version: 3.3.1\n\nIf a .blend file contains a animation, and the animation is playing, and you're in the Cycles rendered viewport mode, then the viewport resolution/size will not update as you adjust it's size.\n\n1. Create a scene that has a colour that differs from the standard background colour of the 3D viewport.\n2. Animate something in the scene (E.G. Animate the movement of an object)\n3. Change the render engine to Cycles (This issue only appears in Cycles for me.)\n4. Enter the rendered viewport mode so you're now seeing a Cycles viewport.\n5. Start playing the animation.\n6. While the animation is playing, start adjusting the size of the 3D viewport editor and notice how the Cycles rendered view isn't updating with the change in size. This is the issue. Once you stop playing the animation, it will update.\n\nHere is a video demonstrating the issue:\n\n[Cycles preview doesn't resize.mp4](Cycles_preview_doesn_t_resize.mp4)\n", "Smoke simulation silently fails in Sync to Audio or Frame Dropping playback\nSmoke simulation silently fails in Sync to Audio or Frame Dropping playback\n\n---\n\n**Original Report:**\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 3.1.2\nWorked: Never (tried 2.93, 2.83)\n\nThe smoke simulation does not simulate beyond the first frame in this particular file. Any smoke simulation added or appended from other files stops working as well.\n\nHowever, everything works fine in new files on the same system & hardware.\n\n[smoke simulation issue.blend](smoke_simulation_issue.blend). \n\nOpen the blend file, move the smoke domain to clear the old cache.\nHit play and the smoke is not moving. Other physics (rigid body, particles) are working fine.\n\nDelete everything, add a cube, add the quick smoke effect, and the same happens.\n\n", "Mantaflow: charge force field crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen I try to add the charge force field and play the simulation the blender 3.0.0 Alpha crashes\n\nMake a simple water simulation and add the charge force field\n**Crash seems to happen only in release builds**\n\n[#92110.blend](T92110.blend)", "Crash 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", "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)", "Eevee incorrect motion blur Mantaflow liquid\n\nOperating system: Windows 7 Pro 64-bit\nGraphics card: Nvidia GeForce GTX 1060 6-gig\n\nBroken: 2.90.0 Alpha - 2020-07-03 - hash cad98923d006\nWorked: ---\n\n\nEevee motion blur not correctly applied to mesh of Mantaflow liquid sim.\nCube in scene is correctly blurred.\nMantaflow appears to show only start/end positions with some sort of strange (zoomed?) artifacts in between.\n\n\n\n**Steps to reproduce**\n[Eevee motion blur bug.blend](Eevee_motion_blur_bug.blend)\n\n- Open file\n- Bake simulation\n- Render", "Mantaflow Noise Smear (OpenVDB cache)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen you add the noise effect to any gas simulation (that uses the OpenVDB cache type) it creates a smearing effect. It only adds to the simulation and it never deletes itself.\n\n**Video explanation** base simulation | with noise enabled | overlayed\n\n[Noise_Smear.mp4](Noise_Smear.mp4)\n\n[Noise_Smear_2.mp4](Noise_Smear_2.mp4)\n\n\n - Create any kind of Mantaflow gas simulation (if the emitter moves it is the most noticeable)\n - Leave the cache type to OpenVDB (With UniCache it works properly)\n - Enable [Noise ](noise.html#bpy-types-fluiddomainsettings-use-noise)\n - Bake the simulation\n\n\nTest File:\n[Noise_smear_bug.blend](Noise_smear_bug.blend)\n", "Move cache visualization to draw overlay\nCurrenlty the cache visualization isn't updated during playback, only when the screen is redrawn.\nThis needs an optimization of the drawing of the cache lines.", "Shadow catcher issue with Cycles Standalone\nOperating system: Win10\nGraphics card: 2070 super\n\nN/A Cycles standalone\n\nShadow catcher is not working properly\n\nI've modified the XML parser of Cycles standalone to read shadow_catcher tag as well as create a new sample, derived from scene_monkey.xml, that uses a plane with shadow catcher enabled.\n\nNotice that the shadow is not visible on the output (you can use something like in the commandline \"scene_monkey_shadow.xml --samples 128 -output Temp.png --background\" \n\n[shadow_catcher_issue.zip](shadow_catcher_issue.zip)", "SpaceView3D.draw_handler_add with PRE_VIEW draw type does not result in visible draws\nOperating system: MacOS 11.6.3, Ubuntu 18.04 LTS (issue exists in both)\nGraphics card: Intel UHD 630, Nvidia Quadro RTX 400 (issue exists in both)\n\nBroken: 2.93 LTS, latest master (b626edd751d64b269da12ef8e774ced2836c3c9e)\nBroken: 2.83.0\nWorked: 2.82\n\nBroke between good 189e96ba68 and bad d95e9c7cf8\n\n1. Startup Blender\n2. Go to scripting tab and create a new script\n3. Copy \"Triangle with custom shader\" code from: gpu.html\n4. Change draw_type param in draw_handler_add from\n```\n'POST_VIEW'\n```\nto\n\n```\n'PRE_VIEW'\n```\n5. Run script.\n\nExpected behavior:\nThe drawn triangle is visible.\n\nActual behavior:\nThe drawn triangle is not visible.\n", "Disk Cache combined with Cache Step does not work\nOperating system:\nGraphics card:\n\nBroken: blender-2.80.0-git.8d95dcd87dbb-windows64\nWorked: Blender 2.79 b f4dc9f9d68b\n\nBaking a particle system with *Disk Cache* checked and *Cache Step* set to greater than 1 results in the baking failing.\nNo error is reported, but the bake is obviously corrupt.\nIt worked in 2.79.\n\n[bake.zip](bake.zip)\n1. Extract the archive and open the *.blend* file. (in 2.80)\n2. Playback works at this point. (Particles fall down from the plane.)\n3. Click *Delete Cache* and then *Bake*.\n4. Try playback again. It's not incorrect. (Particles appear at the bottom and don't move. If you check the cache folder, you will see it cached every second frame---instead of every 10th as configured, except for the first step.)", "Surface tension is not working\nOperating system:Windows-10-10.0.19041-SP0 64Bits\nGraphics card:NVIDIA GeForce RTX 2080/PCIe/SSE2\n\nBroken:3.1.0 Alpha, branch: K-Cycles, commit date: 2022-01-16 15:45, hash: 164a13275cf8\nWorked: \n\nIn mantaflow fluid simulation, change the value of 'surface tension' does not work at all, My cpu is Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz, i tried different version of blender, it didn't work either\n[surface1.blend](surface1.blend)" ]

[ "Mantaflow \"Replay\" cache not working as expected\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 660M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.24 355.11.10.50.10.103\n\nBroken: version: 2.83 (sub 11)\n\n\nThe replay/live preview and modular and final in the mantaflow fluid simulator won’t work for me. I tried deleting the cache folder and making a new one and changing some settings in the mantaflow simulator and changing them back to try to clear the cache but that still didn’t work. Someone on the cg cookie forum said it might be an operating system specific bug.\n\nopen blend file and select replay/live preview beside cache type and press play in the timeline or select modular and press bake data or select final and press bake all and press play in the timeline nothing will show up for both of these cache types \n\n[Mantaflow.blend](Mantaflow.blend)\n\n[video of problem.mp4](video_of_problem.mp4)\n\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", "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)", "Alembic: Camera properties (focal length, focus distance, ...) animation not importing\nMacOS 10.13.3\n\nBroken: 2.79 5bd8ac9\n\n\n\nWhen importing camera in FBX or ABC file (exported from Nuke), the animation of focal length is not importing. It's being set to a constant value according to frame 1. Other values are imported correctly.\nIf I reimport to Nuke, the focal length is correctly animated.\n\nCamera files attached.[camera.fbx](camera.fbx)\n\n[camera.abc](camera.abc)\n", "FPS problem (movie import)\nOperating system: Windows 10\nGraphics card: rtx 2070\n\nBroken: \nWorked: Blender 3.5.1 \n\nWhen I import a 30 fps video in blender (in \"movie clip editor\"), this video will be interpreted as 120 fps per blender, making motion tracking impossible.\n\nimporting a 30fps video in movie clip editor\n\n", "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)", "Camera Background image is appearing greyish in 3D Viewport \nOperating system: Windows 10\nGraphics card: Nvidia GTX 1080Ti\n\n**Blender Version** 3.2.1\nBroken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac9e\nWorked: \n\nCamera Background image is appearing greyish in deep black area in 3D Viewport but showing completely normal in Image editor section and renders. \nEven after turning on \"View as Render\", problem is still there.\n \nOpen the attached blend file.[Blender BG Bug Report.blend](Blender_BG_Bug_Report.blend)", "Draw: Move to 32bit reversed depth buffer\nAs of now, Blender solely uses depth buffer with 24bit normalized integer format which is unideal in many ways. It is nowadays recommended to use reversed-Z depth buffer with 32bit floating point depth format. The immediate benefit would be less Z fighting in scenes with much higher scale.\n\nBoth `GPU_DEPTH32F_STENCIL8` and `GPU_DEPTH_COMPONENT32F` are supported by all backend and platforms. However the Opengl default depth range is not giving any benefits even if we do the switch to reversed-Z. The way to change it is only available through `glClipControl` which is only available in OpenGL 4.5. This is above the planned GL minimum version for Blender 4.0 (Opengl 3.4) so this task need to be tackled either when we bump the OpenGL version to 4.5 or when remove the GL backend in favor of the Vulkan and Metal backend.\n\nThis would affect a lot of areas:\n- [ ] Depth picking algorithm needs to remap the depth.\n- [ ] Rendered depth pass needs to remap the depth.\n- [ ] Projection Matrix Computation need to output 0..1 depth range instead of current -1..1 range.\n- [ ] All Algorithms / Shaders sampling the depth buffer need to change their assumptions.\n- [ ] All depth tests done on the reversed Z buffer need to be reversed.\n\nReferences:\nvisualizing-depth-precision/\n\n", "Collada Import Skeleton animations Y and Z axis are swapped\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 550 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nImport the attached Collada file.\nAnimation shows rotation in Z direction with a twisting motion.\nThe collada file has rotation in the Y direction which should appear as a bending motion.\n[BendCylinderY.zip](BendCylinderY.zip)", "Viewport x-ray shading slider flipped\nOperating system: Linux-4.15.0-66201911071317-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nViewport x-ray shading slider flipped\n\nI think this is ment to work the other way round, isn't it?\n", "Mirror Pose: Custom center of symmetry\nAs it is now, the Mirror Pose operator works through a rig/root bone center, which is of limited use when the character has moved away from that center while animating. The center of Mirror Pose should be selected on a per armature basis and should be available in linked/proxied armatures for the animators to change never at rigging stage, so i would potentially display it only in pose mode in the tool bar or under the pose options..\n\n- In the armature, you could have a bone selector box, where you can pick the mirror bone and axis.\n- If nothing is selected then it defaults back to the current behaviour.\n\nNote that this design task is for poses only, and not other places, like sculpting, where mirroring is used.\n", "Non Uniform Scaling possible when Camera is parented\nOperating system: Win 10\nGraphics card: Geforce 2070\n\nBroken: 2.82-3.2\n\n\nIf you parent a Camera to an Object and scale the parent non uniformly, the Camera View gets scaled and distorted too.\n\n\nCreate an Empty, parent the Camera to an Empty, scale the Empty. The Camera View gets distorted.\n\n[blender_camera_scaling_bug.blend](blender_camera_scaling_bug.blend)", "Scene Proxies in the Video Sequence Editor\nWindows 7 Ultimate, 64-bit, 32GB, 5960x, Nvidia Quadro FX 1800 (Primary) & GeForce 9800 GTX+ (Secondary)\n\nBroken: (2.79a) Official builds\nWorked: (2.79) Official builds\n\n\nTo cut a long story short @ideasman42 disabled Scene proxies in the Video Sequence Editor because:\n\n> In #54048#485268, @ideasman42 wrote:\n> Looked into this and for now **building proxies doesn't support anything besides movie, so disabling support for this.**\n> \n> 6535f668b4\n\n\n*This shocked me, have I been using Blender wrong?* Because I've been happily doing this for months.\n\nI don't quite understand the rationale behind the removal of is.\n\nThe main problem for me is that I have projects (made in 2.79 and earlier) that rely on scene proxies and when opening them up in 2.79a viewing or creating them doesn't work.\n\nNow there *are* issues with Scene Proxies most notably the aforementioned (#54048) one and it can be really bad:\n\n[0001-2565.mkv](0001-2565.mkv)\nand\n**Other proxy issues**\n - Skipping frames whilst rendering.\n - Properties side panel scrolls up after changing proxy location in the File Explorer.\n - Overwrite don't have the same behaviour as Overwrite does in the render setting (in the properties editor)\n - and [inconsistent functionality ](F2418236).\n\nBut I've always treated this as an incomplete feature, (same way I treat NetRender, it's somewhat stable but is inconsistent. e.g. blender/blender-addons#52502) throwing in a bug report due to just crashing (#53792) and have been fine.\n\nBut now with the update, the [Proxy/Timecode Panel ](proxy.html) is still there and does nothing. and as I said in my query to @ideasman42's decision to disable this:\n\n> In #54048#485618, @ChristopherAnderssarian wrote:\n> So, @ideasman42 does this invalidate my bug report? #53792\n> Also, is it a good idea to disable this considering the Proxy/Timecode Panel option still there (or are you still working on this)?\n> \n> With no information or feedback in the Blender Manual or when trying to create proxies (nothing happens), `you are going to get users confused on a essential feature that worked` (works fine in cycles for me (not the file names the crashing)) in 2.79 `and now doesn't with no apparent reason why. `\n\n___\n\n> In 6535f668b4, @ideasman42 wrote:\n>>...generating proxies currently only works for movies...\n\n*No... they don't. They worked for Scenes before. (and they work for images for that matter)*\n>>...cancel until other types of sequence strips are supported...\n\n*What do you mean by this? That it's officially 'supported', documented?* \n___\n\nNow that I've been trying to research around a bit, is this an incomplete feature or has it slowly gotten broken in time?\nThere's #43857 which uses a scene proxy. So there must be other uses who uses this right? Or was this just an example?\nI would love to use this with Eevee; having the proxies rendered in no time and my GPU not getting taxed.\n___\n\nWhat I think to be good next steps:\n\n - Having the functionality back as it was before.\n - An open task to deal with the *Other proxy issues.*\n___\n\nZipped folder with a working Blender file and proxy:\nTested in Ubuntu VM both 2.79 and 2.79a with reproducible behaviour.^\nTested on a separate laptop with both 2.79 and 2.79a with reproducible behaviour.^\n(Note: In my Ubuntu VM I had to toggle Textured Solid button in the Scene Preview/Render Panel to get the proxy showing in 2.79.)\n(^ Reproducible behaviour being: fully working in 2.79 and not working at all in 2.79a)\n[Blender_VSE_Testing_Scene_Proxy.zip](Blender_VSE_Testing_Scene_Proxy.zip)\n\n\nI'm sure this was just a misunderstanding.\nYours,\nA passionate Blender user", "Camera projection mapping for brush texture\n**Status:** Task design and engineer plan review\n\n---\n\n**Team**\n**Code Review:** @Jeroen-Bakker @ideasman42\n**Project leader:** @ivpe \n**Project members:** @ssh4 \n\n\n**Preamble**\n\nGoal of this project are add code support and tools for Camera Projection Painting to Blender.\nSuch workflows used in 3D CG from early days for matte painting, 3D and video integration, etc.\nIn all workflows most logical UX is projection preview as it seen from camera and projection preview overlay on 3D model or scene that visible from any point.\n\nWhen matte painting is one of oldest workflows. Last years we can see huge progress in 3D scanning/Photogrammetry methods, that now one of main parts of 3D assets or scenes creation process. And in same time a lot of artists use photo modeling workflows with photo or video data as a source for textures.\nAnd again, most logical and fast way to work with textures for that models is using 3D paint feature directly in 3D app, instead of use external 3D painters or 2D editors to work with UVed textures.\n\n-----------------\n\n**Who can use it**\n\nThis project improvements in used UX from 3D assets creators, Photogrammetrists (3D scanners) and VFX/Matte painters point of view.\nFor that we made a list of current limitations and propose improvements for wide type of 3D CG users.\n\n* 3D assets creators:\n\nProbably one of biggest group. Standard photo modeling workflow use photo or images as a backgrounds. Final model UVed in human readable form and textures are making with standard for 2D editors or texture painter's workflows with using layers, masks, etc.\n\nPaint tool that can allow project image or photo from specific camera view can speedup time for mock-ups iterations in works with clients and art/creative directors. Due to real-time preview of results in 3D. In same moment using real photo, especially in architectural models limiting possible source of images. Due to lens distortions in all photo, required additional attention to used only high-quality professional photo equipment. Or applying undistortion to all sources before using them for texturing. And when using video in that moment required lot of additional disk space to store that temporary data.\n\nIf 3D assets are low-polygon than this also required creation of “proxy” objects with higher polygons count, because current Blender UV Projection give visible distortions on textures if used low-poly mesh or mesh with n-gons.\n\n* 3D sculptors:\n\nAnother and also big group of 3D content creators. And if in early CG days that was mostly artists that working with organic shapes or characters. In current time a lot of artists doing hard-surface modeling in 3D sculpting editors.\nThat group of artists also need the way to project photo data to textures and using paint editor in same app, speedup sketching or work in progress iterations.\n\nAll models made in that workflows in time of work can have complicated and non-optimized UVs. And using external 2D editors or texture painters not usable until model are retopologized and UVed in human readable form.\nCurrent Blender UV projection have less issues with such meshes. But polygons count already have a big impact on CPU time required for work. Computing new UV Projection from new camera/view for 5-10 million poly meshes already far from real-time.\n\nThis user group also have demand on works with photo or video sources, and lens distortion in source data required to use of undistorted images.\n\n* Photogrammetry and 3D scanning:\n\nLast years one of most growing groups of 3D content creators. That group work with a huge poly count meshes. And it more narrows to 3D sculpting by used workflows in post-processing scan data. With one but important difference, 3D scans are often monolith or split to chunks 3D meshes. And in the middle of process this meshes have completely non optimized UV's with thousands UV islands made by UV parametrization algorithms optimized for speed and works with thousands or even hundreds of millions polygons meshes.\n\nPhotogrammetry with all its power have a limitations in used algorithms due to a huge amount of data used in time of creation of 3D meshes and their texturing. And photogrammetry user not always have way to easily control process of choosing best source for texture in specific part of model. And result texture can use source data from image (camera) with worse depth of field or changed environment lights.\n\nLot of clients of 3D scan studios prefer to work with raw meshes and original textures to be sure that all possible details from 3D scan was used in most efficient way for their project.\nBut photogrammetrist still need fast way to quickly fix raw mesh and raw texture from specific image (specific camera) with better details, or correct light, etc.\n\nAs with 3D sculptors, mesh polygon count is more than enough to avoid UV projection deformations on textures. But used polygon count around 10-20 million of polygons in raw mesh is not a rare use case for high-quality high-resolution 3D scan.\n\nOne of biggest differences for other groups, is an image (camera count) used for 3D model and texture creation. 50-60 images/cameras are average small photogrammetry scan.\nBig or precise scans can easily have 1000 or even 10000 images with 8K or bigger resolution.\nGood point that using all these images/cameras for final texture is not a mandatory. But workflow that allow quickly switching between images/cameras are big time saver.\n\nAnd as soon as source for 3D model and texture are real photo, that always have lens distortions. But if other groups probably can work with some small distortions. Photogrammetry due to it high precision required using mathematically correct lens distortion models. That allow precise copy of source texture from scanned objects with sub millimeter resolution.\n\nUsed image count and size of this images required a lot of disc space for any additional temporary files like undistorted images.\nSo support for using lens undistortion in projection painting “must have” feature.\n\n* Matte painting/VFX:\nThat group can combine workflows and issues from all groups mentioned above. But in addition, this group often work with video sources. That mean this can be hundreds or thousands of frames that also can have real lens distortions or even rolling shutter issue (visible as a skew image deformation).\n3D models can be a combination of low-polygon models or blocks or n-gons for quickly build different distance planes on scene.\nAnd all of this in production or sketching time required quick integration with projection mapping painting.\n\n----------------\n\n**Current Blender workflow limitations and issues**\n\nSummarizing the above limitations of Blender:\n\nBlender currently has a way to do camera projection painting, with \"Clone\" brush and \"UV Project\" modifier. This method is enough labor intensive on the part of the user experience, requires to choose a lot of options even just to change camera from which projection act, which negatively affects the speed of the workflow. The main disadvantage of this method is the requirement for the density of the geometry. Low poly models (for example, after retopology) will have unnecessary distortions when drawing. Also, an extra step in this process is the export undistorted images/movie clips, because datasets can be large enough to create a lot of unnecessary files. It is also desirable to have control over brightness/contrast, ect, this method do not allow this.\n\n-----------------\n\n**User workflow expectations**\n\nThe ultimate goal of this project is to build a workflow that eliminates these shortcomings:\n\n**Scene setup**\nAssumed that the user has a scene with mesh objects, created by himself or imported from third-party software. There are also a number of cameras and original images/movie clips.\n- Automatically attach images/movie clips to specific cameras, they have similar names in any software. It should also be possible to do this manually.\n- Distortion parameters can be obtained through Movie Tracking Solver, but it should be possible to set parameters separately.\n\n**Canvas texture correction/painting process**\nAssumed that user is in Texture Paint Mode.\n- Select a camera. It is assumed that when you select a camera, the corresponding image/movie clip will also be selected for painting.\n- Paint. It is assumed that texture projection will occur from the camera with distortion correction according to the distortion parameters.\n\nMore globally, a major refactoring of the Texture Paint module is needed (like this one [#73935 ](T73935)), all users expect smooth workflow with high-polygon objects and high-resolution images/movie clips.\nAlso, an important part is to give the user a visual representation in the viewport of exactly how the texture will project on the object and from which camera the projection is act (the most obvious is to project from the active camera of the scene).\n\n------------------\n\n**Suggestions**\n\nHere described only a suggestions, each of them can be an open question.\n\n- For both \"Movie Tracking\" and \"Texture Paint\" modules image/movie clip as well as distortion parameters should be part of a particular camera (That should be coordinated with Movie Tracking module). About the Brush Management project. The described workflows have a tight relationship with a specific scene and objects in it, hence from the point the user's view of the photogrammetrist or VFX artist, it is expected that the work done by him at the scene setup stage will be saved specifically for this scene and objects in it. Therefore, it is important to understand that the camera with which the projection is act, its distortion parameters should not have relations with a specific brush. Since the dataset of images/movie clips can be large and also associated with specific cameras of a specific scene, it is also cannot relate to the brush.\n- Automate the process of attaching images/movie clips to specific cameras. This is most often possible by the name matching of the camera and the image/movie clip file.\n- Add \"Camera\" brush texture projection mode. It should use data (image/movie clip) from the active scene camera for the brush texture and also to determine the current parameters of the distortion.\n- Refactoring the brush preview. At the moment it is not informative and has limited presentation of the end result (for example, for \"3D\" texture map mode it's not presented for many years). In the context of this project the preview should be an overlay that takes into account the geometry of the object and gives an actual representation at any view.\n\n**All this but more visually**\nPreviously, we (@ssh4, @ivpe) did it as an addon, it was more photogrammetry-oriented so UI/UX should be different in some cases. In this short video described basic principles of workflow with large dataset of raw (distorted) images, viewport preview. Non-commercial scene is used.\n[Camera Projection Mapping.mov](Camera_Projection_Mapping.mov)\n\n-------------------\n**Work plan**\n> This section will proceed only after final design is ready:\n\n- ...\n\n**Open questions**\nOpen questions according to the suggestions below. Everyone can have their own opinion, so we need a general solution to be approved by everyone. Therefore, I leave a link to the original post, as well as its summary. After design document update some suggestions are included into it and some are still questionable:\n\n- [Original post by]] @brecht [[ https:*developer.blender.org/T81662#1038426 | Original post by](https:*developer.blender.org/T81662#1037146) @Sergey Where to store the distortion parameters of images/movie clips as well as the relationship between a specific camera with a specific image as given the current Movie Tracking design and in the case of its modification to more unified?\n- [Original post by](T81662#1037214) @brecht In case if camera store image or movie clip as background image. Should we have option for automation switch brush texture image / movie enabled by default? Or it should be the only way? \n- [Original post by](T81662#1046815) @sebastian_k Camera background image is enough for visual preview or it should be shader based?\n- [Original post by](T81662#1046815) @sebastian_k VFX scenes has already set background movie clips on cameras. It can be used for any workflow as well, I think. In terms of current project - to store image or movie clip relative to specific camera. But if we have more than one background image on single camera? In this case background images/movies are blended. The oldest principle: \"You get what you see\" should work here too. So how can we handle this? In my opinion the simple way - remove list of background images and leave only one. As I remember in older releases (< 2.8x) we had this as a list to use from different view angles (from left, right, top, camera). So, I think it is more Blender's design questionable too.\n- [Original post by](T81662#1047507) @ssh4 should be camera intrinsics animated for support videos that captured using zoom lenses as well as using optical or sensor stabilization?\n\n- Refactoring of the Texture Paint mode. Is it planned and is it worth counting on help in its implementation?\n- ...\n\n**Relevant links**:\nA small research on YouTube about current limitations:\n[CGMatter: Blender 2.8 Panorama stitching projection painting (part 2)](s_x62z1T9tk?t=467)\n[CGMatter: 2D To 3D](nWCWtojeM14)\n[CGMatter: Realistic 3D? EASY](uWkKV0HxwFQ?t=919)\n[IanHubert: Wild Tricks for Greenscreen in Blender](RxD6H3ri8RI?t=131)\n\nPrevious implementation using UV-projection method in separate boost-module:\n[Camera projection painter addon](watch?v=lasdJIIAv70&t=13s)\nIndustry-compatible lens distortion models:\n[Brown-Conrady]], [[ https:*developer.blender.org/D7484 | Nuke ](https:*developer.blender.org/D9037)", "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)", "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" ]

[ "FBX Export-Camera mirror inverted\nWindows 7 Prof, 6 GB Ram, Ati Radeon HD 5750\n\nBlender 2.73 RC\n\nThe Blend File:\n\n[CameraFBXExportBug.blend](CameraFBXExportBug.blend)\n\nA Screenshot:\n\n\n\n\nA Simple Scene I exportet to Cinema 4D to test Compositing Features, but importet Camera aims into opposite direction and is mirror-inverted.\n" ]

[ "Different results for select_all option in local view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0\n\nWhen having one of two object in local view the {key A} works different than the command\n```\nimport bpy\nbpy.ops.object.select_all(action='SELECT')\n```\neven though the output in the bottom left window in the scripting tab is the same.\n\n[Based on the attached .blend file]\n1. Select *Cube*\n2. Go in local view\n3. Press {key A} to select **only**the *Cube* because of the local view\n4. Deselect everything\n5. Run the command:\n\n```\nimport bpy\nbpy.ops.object.select_all(action='SELECT')\n```\nBut now you have the *Cube***and** *Cube.001* selected even though you used the same command. The output in the bottom left window in the scripting tab is the same. Shouldn't you select in both times the exact same objects?\n\n[selectAll.blend](selectAll.blend)\n\n", "`Materials` tab not opened at the first time running the script\nOperating system: macOS 10.14.2 (18C54)\nGraphics card: Intel Iris Plus Graphics 640 1536 MB\n\nBroken: (example: 2.80, 89207DF7222A, master, 2019-05-27, as found on the splash screen)\n\n`Materials` tab not open at the first time running the script in attached .blend file\n\n\n* Open the attached .blend file\n* Click `Run Script` the first time\n* It just opens the `Object` tab\n* Click `Run Script` the second time\n* It then opens the `Materials` tab\n\nIt should open Materials tab at the first time clicking `Run Script`\n\n[bug_001.blend](bug_001.blend)", "Cycles GPU crash when switching to Rendered 3DViewport --MacOS 13.1--\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.5.0 Alpha (works fine)\n\nInstant crash of blender when switching to rendered 3DView.\n\nCompile latest 3.5 version as of 2022-12-18 20:06, hash: `50c7eb14f4`\nopen empty scene provided below and switch to rendered 3DView.\n[gpu.blend](gpu.blend)\n\n\nxcode 14.1\nlatest brew updates\n(cycles-cache & build-darwin folders deleted before compiling )\n\nPS: When switching to CPU there is no crash. Only GPU !", "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.", "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)", "The 3d cursor looks very dim on AMD cards with the Mesa driver.\nOperating system: Gentoo Linux\nGraphics card: AMD Vega64\n\nBroken: All current Blender versions (2.93 to 3.5)\n\nThe 3D cursor in the viewport seems to be drawn with transparency.\nHowever this is only an issue on AMD cards it seems.\nIt started happening 4-5 months ago, so this is most certainly a driver issue.\n\nOpen the default cube scene and observe that the 3D cursor looks very dim:\n", "Keyframes with stereoscopy button doesn't work in animation, individual frame works\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.90 (sub 0)\nWorked: never, tested 2.75a (when Stereoscopy was introduced) and 2.79\n\nWhole animation is render with stereoscopy ignoring on/off animation keyframes. \n\nwith stereoscopy \"on\" insert a keyframe on it, move few frames and turn off stereoscopy and insert a keyframe. While rendering animation (my setup is FFmpeg with mp4 coding) all frames are rendered as stereoscopic. I attached an example file with render result. I was expecting to have half of this animation as stereoscopic and half normal. Originally I discovered it in a situation where I was swapping cameras (binding to video marker). \n\nOpen file, render frames 39-40-41 individually.\nin viewport change set frame to 39\nRender animation (5 frames)\nin viewport, set frame to 41, \nRender animation \nnotice difference in the two. \n[T76353Stereoscopy.blend](T76353Stereoscopy.blend)\n\n[bug reportstereoscopy.blend0001-0250.mkv](bug_reportstereoscopy.blend0001-0250.mkv)\n", "Grease Pencil drawing next to objects using 3D cursor and View mode previews \nOperating system: \nGraphics card:\n [system-info.txt](system-info.txt)\nBroken: Blender 2.92.0 Alpha - November 12, 10:10:02- bc090387ace9 - macOS 64 bit\nand blender-2.91.0-b99faa0f567f-macOS\nWorked: (blender-2.90.1-macOS)\n\nDrawing with the Grease pencil near objects sketches out and glitches through the object geometry and randomly offsets from the curser point when using a 3D cursor as the stroke placement and View as the drawing plane. The simple step by step video attached below best explains it. Note: this is not the case when starting the file in 2D Animation mode only when adding a grease pencil to a general 3D scene. Also, This problem did not exist with version 2.90.1\n\nSee the short video and blender files of the easiest set up to show the bug.\n\n[Grease Pencil Bug.mp4](Grease_Pencil_Bug.mp4)\n\n[Grease pencil Bug-latest build.blend](Grease_pencil_Bug-latest_build.blend)\n\n[Grease pencil Bug.blend](Grease_pencil_Bug.blend)\n", "Make Instances Real doesn't work for geometry instances\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0\n\nWhen I want to make instances real on object that has geometry nodes, blender create duplicate of whole mesh, togather with instances, on each place (point) where single instance mesh should be. I have attached screenshots and test scene that reproduces the bug. \n\nOpen .blend file I sent you, hover with mouse over 4 instaced spheres, and pres ctrl+A... select make instances real. You will see that geometry nodes instances are not created properly (whole geometry is duplicated on each geometry node point).\n\nSimilar thing happens when instancing collections, and trying to make them real - the parent relationship/hiararchy is not working. So there is a bug there also.[geom_nodes_bug.zip](geom_nodes_bug.zip)\n\n\n\n\n", "problem Blender 4.0 in a mac mini\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\n\nI'm trying to get Blender 4.0 (Alpha) running on a Mac Mini running OS Ventura 13.14.1(c). When the cube appears (by default) it is not surrounded by the yellow paint and cannot be selected with the left mouse button or the pointer of the digital tablet either. It can only be selected in the outliner\n\n\n", "Collada: export when editing multiple objects does not pick up all changes\nOperating system: Linux\nGraphics card: Intel Integrated\n\nBroken: 3.0, 2.93\nWorked:\n\nWhen editing multiple meshes, if you export to Collada from edit mode, only the changes to the active object will be picked up; the other objects export as if they had not been edited.\n\n1. Create two cubes. Select them, go to edit mode, and change both of them. In my case, the cube on the right was the active object.\n```\n {F12749887}\n```\n2. Without exiting edit mode, export to .dae.\n3. Open a blank file and import the .dae. Observe that only the active cube was exported correctly.\n```\n{F12749891}", "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.", "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.", "Keep Alt Key not work in the F-Curve properties\nwin10 64bit, gtx1060\n\nBroken: 2.79a 8928d99270f\nWorked: (optional)\n\nKeep alt key for multiple objects not work in F-curve property ( N panel )\n\nOpen my .blend file, when I select multiple curves and keep alt key to twice the Interpolation or Easing option, it's just worked in one cure,not for all selected, if this is bug, please fix, it very useful for lots curves, else I must one by one to change those, thanks.\n\n\n\n[bug.blend](bug.blend)", "Rigid body bugs\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.21\n\nBroken: version: 2.93.1\n\nSimulation somehow broken for small (less than 1 cm) or light (less then 100 grams) objects. In first example below object stay still between bouncing and small shivering. And that is just one example. Another examples are – reaching speed of light instantly (one frame), partial simulation when one object (or some objects) acts like it suppose to, but others act completely inadequate, two or three similar parts in one simulation (example 2). I tried different options but nothing helped. \"Substeps per frame\" and \"Solver iterations\" seems not working because there are no actual changes with different values or simulation just goes nuts.\n\n[r_body-bug.blend](r_body-bug.blend)\n[r_body-bug2.blend](r_body-bug2.blend)\n" ]

[ "3DConnexion Mouse not working in new Blender instance\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon VII OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 5)\nWorked: (optional)\n\n3dconnexion mouse works only in one instance of Blender\n\nIf I open 2nd instance of Blender 3d mouse does not work in it, only in the original file. This behaviour is same in official 2.8. I have tested this in Rhino for Mac. There Mouse works in both instances, which ever is active of course.\n" ]

[ "Update Tweak Tool behaviour on Right Click Select\nThis has been a long running known issue for the Active Tools when using right click select.\n\n## Issue\nOn RCS, the Tweak Tool in the toolbar is placing the 3D Cursor instead of tweaking elements.\nThis duplicates the behaviour of the Cursor Tool (right next to it in the toolbar).\n\nThe reason for this seemed to be that right click & drag is already using the tweak action.\nIf the Tweak Tool would tweak with left & right click then there is no way of setting the 3D cursor anymore.\n\nBut the Tweak Tool doesn't require the 3D cursor. And this workaround is breaking the tweak tools purpose.\n\n## Solution\n\nThe Tweak Tool needs to tweak with left click & drag.\nThis can be it's own keymap item in the preferences under the Tweak Tool.\nRight click & drag can still use the default tweak action in the preferences.\n\nThe benefits are:\n- The Tweak Tool can be used without a drag threshold with left click & drag, if the option \"Alt Cursor Access\" enabled in the preferences\n- There is a functional distinction between the Tweak Tool and the Cursor Tool.", "Adding a reference image with the name \"Front\" changes the width.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\n[When I add a reference image it is slightly being widened on the x axis if the file name is named as Front.jpg. If I name it Frontt or anything the size is correct. I was using a very well aligned picture which is why I could see it's not the right size, using the grab and z axis shortcut was showing the axis not at the center of the reference image.]\n\n[Shift+A > Image > Reference > select an image named Front.jpg > Left click image > G + Z > see the z axis not being at the center. ]\n\n", "Shading or Lighting Discrepancy issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nSo I’ve been having this problem since working in 2.8 and I don’t have a clue what could be causing this issue but I went and stripped down a project as simple as possible trying to isolate the root cause. It seems its a mesh that has an emissive material and when I disconnect the node or hide the mesh the problem disappears. Weird thing is that the brighter version is when hiding mesh number 2. I am attaching the file.\n\nYou will see how the tone changes. This never happened to me after so many years using Blender until now already in a few projects in 2.8. \n\n- Open attached file.\n- Render once using slot 1.\n- Hide mesh 2 or disconnect the emissive node.\n- Render again using slot 2.\n# Toggle with J\n\nNotice the different lighting between each result.\n\n[Shading Issue - Simplied.blend](Shading_Issue_-_Simplied.blend)", "Minor image editor left click values bug\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen inspecting an Openexr image file with sRGB color space it gives incorrect raw values.\n\n\nOpen any external Openexr image in the image editor\nLeft click to inspect values\nSwitch to sRGB color space\nLeft click to inspect values\nThe image editor will now display incorrect values for RGB (not color managed) next to XY\n\nDon't ask me why I inspect an Openexr with sRGB color space, but here is just to let you know this bug exists.\n\nThank you and have a great day!\n", "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.", "Contradictory labels in UI. Naming of boolean properties sometimes positive, sometimes negative.\nOperating system: Any\nGraphics card: Any\n\nBroken:\nBlender 2.80.74 aka rc2\n\nInconsistency in naming leads to contradictory info.\n\n- Open Blender\n- Select an object on the scene (add one if you have nothing...)\n- Go to Object properties panel\n- Scroll down to Visibility\n- Hover \"Show in Renders\"\n- A pop-up info label reads \"Globally disable in renders\", so now you're not sure what happens if you check the box\n- Check the box\n- Open the Info Editor, the last line will read \"bpy.context.object.hide_render = True\"\n\nSo now we have three different nomenclatures for the same thing. Two that are contradictory within the UI and one that is the opposite naming of what's in the UI.\n\nInstead of having properties named \"show_name\" and some others \"hide_viewport\", all such boolean properties could be named \"show_function\" or \"enable_function\" so that you don't have to negate the negation as in hide_viewport = False\n\nSince Blender 2.8 is a breaking release, it is the time when you can implement coherent naming. After that, it's going to be much more difficult.\n\nOf course that's by far not a priority since it doesn't break Blender.", "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", "OpenColorIO-Config-ACES 0.2.0 breaks in sRGB view transform\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nI tested the newest OCIO v2 config from Github (v0.2.0)\nin Blender 3.2 Alpha. It was first time I tried that.\nI had to change the OCIO 2.1 version to 2.0 to make it actually work in Blender. I was assured that this shouldn't be a problem.\n\nI rendered a test scene and saw some strange shading errors with the default sRGB view transform.\nSelecting a different view transform like Rec.709 fixes the issue.\n\nI posted about the issue on my blog ?page_id=5517 and on ACESCentral.com \n4354\n\nThe rendered EXR file is fine of course. The problem only occurs in the render view or when I try to export the rendered image.\nJPG works fine, PNG breaks in a different way and creates a strangely bright image.\n\n[Blender_32alpha_OCIOv2_sRGB_bug.blend](Blender_32alpha_OCIOv2_sRGB_bug.blend)\n\n\n\n\n\n\nI also tested the same .blend file on a new M1Max MBP. There I cannot replicate the error.", "Auto perspective sometimes fails\n**System Information** \nOperating system: Windows 10\nGraphics card: 3070\n\nBroken: 3.2.0 and 3.2.1\nWorked: 3.1\n\nAuto perspective setting doesn't work in this case: if you are in camera view or any side view and then you are switching to another side view you have this smooth transition animation between views. If during this animation you press middle mouse button (rotation) to go from side view it doesn't change to perspective. Moreover it \"shifts\" viewport like it was aligned to a bad quad. \n\n1. Turn on auto perspective.\n2. Go to top view.\n3. Change top view to any other side view.\n4. During smooth transition between view press middle mouse button and rotate the viewport.\n5. Now viewport is shifted and stays in orthographic instead perspective.", "Allow OpenGL image drawing in UI colour space\nSince 7ad802cf3a images are stored with premultiplied alpha and in scene linear space. This produces the wrong colours when used for drawing UI elements.\n\nExample from the Blender Cloud texture browser, with the post-7ad802cf3a drawing on the left and the expected colours on the right:\n\n\n\n@brecht proposed adding a new shader that can be used from Python and that draws the textures in the correct colour space.\n", "Mesh Mirror Node\n{[F9914997](mirror.png) size=500}\n\n**Changes and simplifications in comparison to the modifier:**\n\n1. It reflects on an arbitrary plane which is defined by position and rotation.\n\n2. It shows a gizmo that visualizes the reflection plane.\n\n3. Merge by distance operation can be done by a separate node.\n\n**Open Questions:**\n\n1. Will we handle UV data in this node or a separate one?\n\n2. How to handle the Bisect option. Having Bisect as separate node makes sense, but to use it in combination with the mirror node would require to some effort to get them lined up correctly e.g. using at least the same plane for both nodes.", "Normal Map gets inverted in Edit mode\nOperating system: Linux-5.3.0-7642-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 13)\n\nFor some reason having material shading enabled and entering edit mode inverts the normal map.\n[2020-04-14 14-01-54.mp4](2020-04-14_14-01-54.mp4)\n\n1. Open the file [bug.blend](bug.blend)\n2. Enable Material Preview\n3. Switch between Edit mode and object mode\n\n", "Mesh cache Modifier cant unselect Flip axis once selected \nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nin Mesh cache Modifier i cant unselect X,Y,Z Flip axis once selected ..it can only be interchanged\n\n\n\n", "Subdivide smooth is not symmetric\nWindows 8\nGeforce GTX 665 M\n\nBroken: Blender 2.96.0 r60995\n\n\nOn a 3 vertex line with the center vertex with greater y like that :\n\n\nIf I use subdividee smooth the result is not symmetric, I haven't set any random property.\n \n\n1./ Use subdivide smooth on the attached blend file, I have put the result that I get and the original\n[subdivide_smooth_bug.blend](subdivide_smooth_bug.blend)", "Inconsistency: Vector math node flips large list of options/operations.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.1.2\n\nWhen direction of opening changes, direction/order of list changes too.\n\n[2022-04-12_09-48-55.mp4](2022-04-12_09-48-55.mp4)\nIt is fun, it was the same in 2.79. But there was very short list with 1 column And it wasn`t so annoying. \nNow, with 2 columns the order should be fixed same way as in Math node.\nBecause user remember the relative position of option too. Not just «how far from start»\nAlso the same flipping exists for other lists, like Transfer Attributes node. But as I said, for one short column it is not the issue at all\n" ]

[ "Right and Left Views ... swapped\nWindows 8.1, 64 bit\nnVidia GT 740\n\nBroken: 2.77 (all I have memory of)\nWorked: none that I recall\n\nThe Right and Left Views are swapped.\nThe **Right** side of the scene appears in the **Left** View and vice-versa\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nTrying to set the reference images for a mesh, I always have to assign the **Left** reference image to the **Right** view and vice-versa.\nThis is really annoying.\n\nHere are some screenshots and a test file (no references, I used Text labels, to limit the file size)\n\n**Front View** (so far so good)\n\n\n**Left View** (it shows the **right** side of the scene)\n\n\n**Right View** (it shows the **left** side of the scene)\n\n\nThe blend file\n[LR Reference.blend](LR_Reference.blend)" ]

[ "OpenImageDenoise crash / computer restart\nOperating system: Windows 10 (x64)\nGraphics card: GTX970\n\nVersion 3.0.0\n\n\n**Finish rendering when Denoise processing should take place, the computer restarts. This happens with the Cycles rendering on the GPU, when the \"Use nodes\" checkbox is checked in the \"Composting\", and the \"Denoising Data\" checkbox is unchecked on the right panel. Regardless of the scene, be it a simple cube or a complex scene like 512 or 1024 samples, the PC always reboots at the end.**\n\n\nПод конец рендера когда должно происходить обработка Denoise, происходит перезагрузка компьютера. Происходит это с рендером Cycles на GPU, когда в \"Composting\" включена галочка \"Use nodes\", а на панели с права отключить галочку \"Denoising Data\". Независимо от сцены, будь то простой куб или сложная сцена, например 512 или 1024 семпла, всегда в конце происходит перезагрузка ПК. \n\n\n\n**I attach a screenshot of the settings and the scene file itself.**\n\n\nПрикрепляю скриншот настроек и сам файл сцены.\n\n[Bug.blend](Bug.blend)\n\n", "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.", "Asset Browser: Material preview with black background when Cycles is disabled\nBroken: version: 3.0.0, 3.4.0\nWorked: Never\n\nWhen a scene was saved with Cycles but I disable the Cycles add-on the material previews get a black background.\n\n* Disable Cycles add-on.\n* Click on any (e.g., the Yellow) material asset and update its preview.\n[black_preview.blend](black_preview.blend)\n", "Realtime compositor: Texture node output textures with artifacts\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nTexture node support was introduced in 151a53110c\n\nIn realtime compositor, Texture node outputs textures with artifacts.\n\n\n\nIt happens with most procedural textures I tested. This does not happen when a custom image is used, or when Blend texture is connected from the Value output (instead of the Color output) of the node. (With other textures it happens with both outputs.)\n\nThis does not happen when running Blender with a single thread (`blender -t 1`)\n\nFile for quick test: [TextureNodeTest.blend](attachment)\n\n", "Displacement Animation works only with keyframed node present\nOperating system: Linux-5.4.0-107-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.1.2\nBroken: version: 3.2.0 Alpha\nWorked: unkown\n\nDisplacement Animation works only with a keyframed node present, even if it is not connected!\nI was trying to animate displacement using the object color, finding that it doesn't work.\nWhen trying a keyframed mapping node instead I found that it works but even if the node is not connected!\n\n - Open the attached blender file, switch to render mode and play the animation\n - The displacement will be animated.\n - Now delete the not connected mapping node or clear its keyframes.\n - The displacement will not be animated anymore. Even though I would expect it to be animated by the object color.\n\n[displace-test-1-1.blend](displace-test-1-1.blend) \n\n[displace-test-1-1.mp4](displace-test-1-1.mp4)\n", "Dither affects 'File Output' image even when \"save as render\" is disabled \nThe dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when \"save as render\" is disabled, when disabled it should not touch the output image, when \"save as render\" is enabled it makes sense to dither.\n\n\nnoise in output file\n\n\n- Open attached file\n- Optionally change the Dither in {nav Output Properties > Post Processing}\n- hit render\nIt will generate an image in the directory pointed to by the node `File Output`.\nNote that Dither also affects this image.\nMaybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data.\n\n[gradient.blend](gradient.blend)", "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. ", "Cycles: transparent object has black line where it intersect with other objects\nOperating system: Windows-10-10.0.18363 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 461.40\n\nBroken: 2.91.2\n\n\nWhen rendering transparent objects that intersect with other objects, black lines will appear on the intersecting area.\n\n1. Open a default scene.\n2. Add a plane to the scene.\n3. Rotate the plane a little.\n4. Move the plane up to make it intersect with the top face of the default cube.\n5. Make sure the view or camera view is very close to the intersecting area and lower the Clip Start value to 0.00001\n6. Set the renderer to Cycles and render the view.\n\n\n\n[Cycles_Black_Line_Transparency.blend](Cycles_Black_Line_Transparency.blend)", "Blending Factor Slider in Image Editors not working\nOperating system: Linux-5.15.0-50-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.61.05\n\nBroken: version: 3.4.0 Alpha\n\nThe \"Blending Factor\" slider in the Mask Display options doesn't work (= the image outside the masked area stays black).\n\n\n\nThe same display option works as expected in the Movie Clip Editor's mask mode.\n\n- Open Blender\n- Press F11 to open an Image Editor\n- Open an existing image or create a new e.g. a Color Grid\n- Switch the Image Editor to mask mode and draw a closed shape.\n- Go to the Mask Display menu and select the \"Overlay\" option and set it to \"Combined\"\n- Move the Blending Factor slider -> Nothing happens.", "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", "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", "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", "Cycles: Tex Coord node plugged directly in a world shader does not affect diffuse rays\nI tested and it's not supported in 2.79 so this maybe a corner case that has long been standing.\n\nThis happens also in final render.\n\n[cycles_diffuse_ray_issue.blend](cycles_diffuse_ray_issue.blend) \n- Open given file and switch to rendered view.\n- Connect the 2nd checker color socket to another of the dysfunctional texco socket.\n- Only glossy rays can now see the texco of the environment.\n\nThe issue seems to happen if the coordinate is plugged straight to the background or emission node. If the output is mixed it does work (default state of the file).\n\nMixed, working:\n\n\nNot mixed, broken:\n", "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", "Denoising passes are darkened when denoising is enabled for multi-device rendering\n## Simplified Report\n\nDenoising passes like Albedo and Normal are darkened when denoising is enabled when rendering using multiple devices.\nThis is most likely because the passes are scaled in-place during denoising and then scaled again in the pixel accessor.\n\n## Original report\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.3.0\nWorked: 3.2.2\n\nWhen rendering a scene using Cycles with the Denoise option enabled, the Denoising Normal and Denoising Albedo passes don't render correctly, the images correspondent to those passes are much darker than they should be.\n\n1. Open attached file or\n - Open Blender.\n - Delete the default cube.\n - Add an icosphere and set it shade smooth.\n - With the icosphere selected, go to the Shading workspace and add a material to it.\n - In Principled BSDF of the icosphere's material, go to base color and add a color (any color other than black, white or gray).\n - Go to Render Properties and select Cycles as render engine and GPU as Device.\n - In the Render section of the Render Properties, disable Denoise (it is enabled by default).\n - Go to View Layer Properties.\n - In the View Layer Properties, go to Passes section, Data sub-section and enable Denoising Data.\n - Go to the Compositing workspace and enable Use Nodes.\n2. Render the image (Press F12).\n3. In the Render Layers node, visualize the Denoising Normal and Denoising Albedo outputs (Ctrl+Shift+LeftClick with the Node Wrangler Add-on enabled).\n4. In the `Properties Editor` Go to {nav Sampling > Render} and re-enable `Denoise`.\n5. Render the image again (Press F12 or use the small buttom at the bottom right of the Render Layers node).\n6. Repeat step 3.\n\nBy comparing the images from step 3 and step 6, the difference is clear, the images from step 6 (Cycles' denoise enabled) are much darker than they should be;\nI tested with a more complex scene and noticed that the darker images do remove noise when used with the Denoise node in the compositor, so it may not be a big problem for Blender, but it may affect someone using other softwares in a pipeline, unfortunally, I can not tested it because I don't have acess to external compositing softwares, I only use Blender.\n\nThank you, have a nice day :).\n\n[#101071.blend](T101071.blend)" ]

[ "Denoise Node produces black image in 2.83.0\nOperating system: Linux-5.6.15-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83.0\nWorked: version 2.82.0\n\nAfter update to version 2.83 the denoise Node, in Compositing tab produces only black images.\nTried many scenes, even simple ones. In version 2.82 worked fine.\n\nAfter default start, change render Engine to cycles, and\nenable denoising data in View Layer Properties.\nThen add the denoise node in Compositing tab, connect all of the denoising data, and hit render.\n\n", "Blender Denoise node in Compositing results in black image\nOperating system: Linux-5.6.15-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nDenoising with the Denoise node in Compositing outputs a black image\n\n- Create new Blender project\n- Switch to Cycles renderer\n- Go to compositing, enable \"Use Nodes\", attach a \"Denoise\" node between \"Render Layers\" and \"Composite\" node\n(saving this will produce [denoise_black_image_bug.blend](denoise_black_image_bug.blend))\n- Render: this will render as normal until it reaches the Compositing stage where the entire image turns black\n\nI cannot seem to reproduce this on another machine running Pop!_OS 20.04, so this may be an environment-specific or hardware-specific issue.", "AI Denoiser Error in Compositor\nOperating system: Linux-5.4.43-1-lts-x86_64-with-glibc2.29 64 Bits\nGraphics card: Quadro K1000M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83.0\nWorked: 2.82a\n\nWhen I use denoiser node in compositor the rendered image appears to be black.\nThen I download 2.82a.zip and run, the issue doesn't happen.\n\nI never use AI Denoiser before I update to 2.83. But after watching 2.83 release, I stumble across this video watch?v=Pw-OxOHHu5I and wanted to try out AI Denoiser. But surprisingly, I got this error, trying to rerender a couple of times, and download 2.82a to test it out, and it worked with 2.82a but not 2.83.... xD\n[KOOMPI E13.blend](KOOMPI_E13.blend)\n\nThanks! Have fun!\n\n", "Denoise node returns a black image\nOperating system: Arch Linux 5.6.15-arch1-1\nGraphics card: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) (I render on CPU!!!)\n\nBroken: 2.83\nWorked: 2.82a\n\nDenoise node in the compositor returns a black image. Similar to [#76668](T76668) but occurs at any resolution and using Blender 2.83. The denoise node works fine using Blender 2.82a.\n\n- Open Blender with default cube\n- Render engine: Cycles\n- Device: CPU\n- go to Compositing tab -> use Nodes\n- insert Denoise node\n- render image -> black image\n\n\n[bug.blend](bug.blend)" ]

[ "Some Cycles nodes are active when muted (RGB To BW, Math, vector Math, Separate RGB)\nWin10 64bit\n\nBroken: 2.79\n\nRGB To BW node is active when muted\n\nOpen file and render\n[RGB_BW.blend](RGB_BW.blend)\n\n", "Freestyle doesn't render hair\nOperating system: Win10 64bit\nGraphics card: gtx1050ti\n\nBroken: 2.8-155c62b070a9\nWorked: 2.79b\n\nRender file with Cycles in 2.79b and 2.8. In 2.8 only mesh is outlined.\n[free.blend](free.blend)", "Soft Body collides with Rigid Body in their initial position of the animation\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.1\n\nI have an animation with a Rigid Body (blue balloon in the blend file) which collides with some Rigid Body (the letters H and T in the blend file).\n\nWhen you play the animation in the blend file, notice that the blue Soft Body balloon bounces on the Rigid Body objects (the letters H and T), but it does so in the INITIAL position of these letters. It's clearly visible from frame 38 and onwards.\n\nI wouldn't expect the blue Soft Body balloon to bounche on the Rigid Body letters before it's actually hits them.\n\nOpen the attached blend file, go to Layout tab, and play the animation.\n[TextBug.blend](TextBug.blend)", "Greasepencil effect error\nOperating system:windows10\nGraphics card:GTX1060\n\nBroken: 2.93\n\n\n\nIf Greasepencil enters a 3D object\n\n1, A small part of the BLUR effect will overflow and the join part will be a little transparent\n2.The FILP effect will lose part of the image\n3.The RIM effect will change as the 3D object changes.\n4.The shadow effect overlays 3D objects and is partially missing\n5.The wavedristution effect will overwrite the 3D object in horizontal mode.Vertical is normal\n6.The swirl effect will lose some of its effect and will overwrite the 3D object\n\n[rim.blend](rim.blend)", "Geometry Nodes fouling up motion blur\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.1.0\nWorked: N/A\n\nGeometry Nodes applied to a spline which affect its shape over time do not blur when Motion Blur is enabled.\n\nLoad attached simple file. Render frame zero. There is no blur at all. Render frame 1, *everything* is blurred, despite only part of the spline is in motion. It would appear the entire spline is blurred according to how the base object is moving, not how the spline is deformed as a result of the applied Geometry Nodes.\n\nNote that same file loaded into 3.3.1 causes Blender to crash (GPU rendering only - it's a stack corruption bug in the nVidia driver, but 3.1 doesn't cause a problem). I previously reported that crash but it was rejected due to possibly being related to the Photographer add-on, which I have uninstalled. It still crashes.[Motion Blur Bug.blend](Motion_Blur_Bug.blend)", "Physics: The default value for Format Volumes is nothing...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.4\n\nThe default value for Format Volumes is nothing...\nBlender will stop working if you try to let the Animation play. EDIT: Can no longer reproduce with Blender 3.0\n\nDo a Backspace (to reset to default) on \"Format Volume\"\n![2021-09-09 09_15_29-Blender_ [C__Users_raimund.klink_Downloads_adaptive bug2.blend].png](2021-09-09_09_15_29-Blender___C__Users_raimund.klink_Downloads_adaptive_bug2.blend_.png)\n[happy_little_bug.blend](happy_little_bug.blend)\n\n", "Support for USD PointInstancer\nOperating system: Win10\nGraphics card: GTX 1660 Ti\n\nBroken: 3.1\n\nAfter loading a USD file with type particleInstancer attached with spheres as child, Blender failed to draw the points as spheres. Instead, the displayed object in the layout window is just a singular point at the origin. Example file attached.[example_sim_granular.zip](example_sim_granular.zip)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Kill Particles does not make them really dead\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 2.93.6\nWorked: -\n\nIf you give a mesh a physics property of collision and check the \"Kill Particles\" Checkbox, they are not becoming dead, they just stop moving. If you add a Particle Instance to another object and only show dead, the dead objects show correctly in viewport but not in render (eevee/cycles).\n\nI created a plane, put it about 10m higher and turned it 180° on x axis. Then i added a particle system to that plane with default settings. I added another plane and scaled it up a few times and applied all transforms. I then added a collision physics property with \"Kill Particles\" enabled to that plan. Now i added an Icosphere, scaled it down, applied all transforms and added the Particle Instance modifier. As Object i chose the first created plane and only left show dead active. After baking the Particle system, you see in viewport the Icosphere as soon as the particles hit the Plane with the collison physics property. But if you then want to render the image they are gone.\n\nWith the attached .blend file you just have to click bake in the particle system properties of the ParticleEmitter object and you should see the dead ParticleInstance object at Frame 40. But if you render the image then they are gone.[ParticlesNotDead.blend](ParticlesNotDead.blend)", "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", "cycles stalls with hair particles in viewport\nOperating system: Windows 10 home version 21H1 OSBUILD 19043.1415\nGraphics card: no card\n\nBroken: 3.0.0\nWorked: prior to 3.0.0\n\n\n[CUBE HAIR packed.blend](CUBE_HAIR_packed.blend)\n\ncycles stalls in viewport with hair particles, final render does not work\n\n\n1. Change the render engine to Cycles\n2. Create the material shown below (The parameter surrounded in red have been modified on the Principled BSDF)\n\n3. Give the material created above to a mesh object.\n4. On that same mesh object, add a hair particle system.\n5. Enter the rendered viewport. And take note of the slow rendertimes.\n6. \"Restart\" the render by doing something like **one** of these steps:\n - Move, scale, or rotate an object\n - Click on a material in the 'Material Properties' tab of the `Properties editor`\n - Adjust a material property in the world material or the object material\n - And probably others\n7. Notice the viewport render is now much faster.\n\n> Original Steps to reproduce\n> click display render preview in viewport, observe cycles stalling, then click on 'material' in layout panel, now observe cycles picking up and running at fast pace, then try final render, observe that it does not proceed", "Subsurface scatering does not indirectly affect diffuse.\nHello,\nI've noticed an oddity: materials with SSS are considered totally opaque, but only for the diffuse aspect, but remain visible for glossy surfaces ;\n\n\n\n\nIt looks like a limitation, but it doesn't seem to be listed anywhere :\n\n-0df9b2c715\n-sss.html\n\nMaterials, such as ivory, jade, marble, rubber or skin, will produce variable results.\n\nIf this is a limitation, it's strange that it's only on the diffuse component and not the glossy one.\n\nSo it looks like a bug.\n\nThanks for reading, and sorry about my bad English.\n\n\nOperating system: Windows 11\nGraphics card: nvidia 2080ti\n\nBroken: 3.6\nWorked: none ?\n\n\nLoad SssPasstrought.blend , render\n\n", "Fire does not render if flow object had disabled Show in Renders\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional)\n\nFire does not render if flow object had disabled Show in Renders\n\n[F_F_I_R.blend](F_F_I_R.blend)\n\n- Open file\n- Bake domain cache\n- Render\n", "Quick Liquid has no effect until playback loops back on the start frame\nOperating system: Linux-5.9.16-100.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: latest master\nWorked: Never\n\nThe quick liquid effect appears not to work until the playback loops back over the start frame\n\n- New file\n- Set the frame to something that's not the first, i.e. frame 80\n- Quick Liquid operator on default cube\n- I can see why it wouldn't work at this point, but it feels broken on the user level\n- See only two wireframes, no particles\n- Play the animation until it loops back past 250 to the first frame\n- Particles are now visible\n", "Bake All Dynamics doesn't work when baking particle hair\nMacBook Pro, NVIDIA GeForce GT 750M, Intel Iris Pro\nMac OS 10.12.6\n\nBroken: Blender 2.79 Hash: 5bd8ac9\n\nHitting the Bake All Dynamics to bake out particle hair doesn't do anything.\n\nLoad the attached file.\nSelect the sphere.\nGo to the particle panel.\nUnder Cache, click Bake All Dynamics.\nNothing happens.[sph.blend](sph.blend)", "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" ]

[ "wave modifier is not involved in physics\nOperating system: windows\nGraphics card: GTX 1660\n\nBlender Version 3.1\n\n\nwhen running a simulation of a wave on a surface, it does not participate in physics (the rigid body is set correctly), the wave does not affect objects in any way" ]

[ "Crash when deleting one rigidbody from constraint during simulation\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\nBroken: master branch\nWorked: Don't know if it ever worked\n\nDeleting one rigidbody that is part of a constraint during simulation causes a crash.\n\n**Steps to Reproduce**\n- Add two cubes to a scene. Add a rigidbody to both cubes.\n- Add an empty object to the scene. Add a fixed rigidbody constraint to the cube. Set the cubes as the first and second object in the constraint.\n- Play the simulation for a few frames and then pause the simulation.\n- Delete either cube, then continue playing the simulation.\n- Crash", "Crash on forcing laptop to sleep when rendering animation\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\nCpu AMD Ryzen 7 4800h\n\nBroken: version: 3.3.1\nWorked: Maybe never? (able to reproduce in 2.83)\n\nblender crash when I wake up my laptop , I lost my unsaved file\n\n- Open .blend file\n- Start render animation\n- Force laptop to sleep {nav Start -> Power -> Sleep}\n[test1.blend](test1.blend)\n[test1.crash.txt](test1.crash.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n", "Outliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.5, 2.90, 2.91 ce0bcd5fb\nWorked: Never (2.79 has the same problem)\n\nOutliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\n\n[T79961_repro.blend](T79961_repro.blend)\n- Open file\n- Cube should be in editmode\n- In the Outliner (should be in Data API mode):\n - navigate to Meshes > Cube > Skin Vertices > expand the dot as well\n - crash", "Blender crashes when using bpy.ops.view3d.view_orbit with a custom context\nOperating system: Linux-5.15.11-arch2-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.42.0, 5.15.11-arch2-1, LLVM 13.0.0) AMD 4.6 (Core Profile) Mesa 21.3.2\n\nAlso tested on WIndows:\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14756 Core Profile Context 20.40.32 27.20.14032.8\n\nBroken (Linux): version: 3.0.0\nBroken (Windows): version: 3.0.0\nWorked: Never, the crash happens in 2.7 and 2.6 doesn't seem to support the override thing (I haven't tested subversions)\n\nBlender crashes when using `bpy.ops.view3d.view_orbit` with a custom context\n\nRun this in the Python console:\n```\narea = [n for n in bpy.context.screen.areas if n.type == \"VIEW_3D\"][0]\noverride = bpy.context.copy()\noverride['area'] = area\nbpy.ops.view3d.view_orbit(override, type='ORBITLEFT')\n```\n\n[blender.crash.txt](blender.crash.txt)", "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", "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", "Remeshing object with subdivision modifier hangs Blender\nOperating system: macOS 10.14.6\nGraphics card:\n\nBroken: All versions of Blender but tested on Version 2.93.0 (2.93.0 2021-02-25) & Version 2.92.0 (2.92.0 2021-02-25)\nWorked: ?\n\nRemeshing object with subdivision modifier hangs Blender\n1 Add a subdivision modifier to the default cube, set it to 2 or more.\n2 Jump into Sculpt mode and remesh with default voxel settings, it should work fine.\n3 Undo the last remesh and now change the voxel size to 0.002 m and remesh again, it hangs.\n\n\nDo step 1 again, this time apply subdivision modifier and then try to remesh with voxel size of 0.002 m, it should work\n\n\n\n", "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)", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "Blender 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", "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", "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", "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", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "Applying negative scale inverts multires displacement\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.82a, 2.90 Alpha (542ff416e274)\nWorked: 2.79b\n\nWhen multires-sculpting an object, then mirroring it on any axis and then applying the scale, the multires displacement inverts - turning inside out. Flipping normals (either before or after applying scale) doesn't help.\nIn 2.79b, multires data is retained correctly after applying scale, although normals need to be flipped afterwards.\n\n1. Pick the default cube, add a multires modifier to it.\n2. Subdivide a bit for good measure, sculpt something.\n3. In object mode, mirror the object on any axis.\n4. Apply scale.\n5. Observe the sculpt turning inside out." ]

[ "blender crashes when using multires modifier in sculpt mode\nOperating system: Linux-5.3.0-46-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 13)\nWorked: (blender-2.83-2ec6eca518ef-linux64)\n\n[blender crashes when adding subdivision in multires modifier and go to sculpt mode]\n\n[start blender add multires to default cube subdivide 2 times go to sculpt mode.]\n[Based on the default startup]\n\n", "Crash when trying to sculpt geometry in Multires modifier\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.83 (sub 13)\n\nProgram crashes when trying to edit multiresolution with sculpt mode. If Multiresolution modifier is applied, however, the program will not crash when going to sculpt mode afterwards.\n\nStart a new file, make a cube, select it and add a multiresolution modifier, subdivide 2 times on the multires modifier then go into sculpt mode and the program crashes.\n\n[Crash cube.blend](Crash_cube.blend)\n\nThis is a gyazo gif of the steps I took:\nc8c5e2ac49cb09f8db75fde6f326587b\n\nThe file is a simple cube. The modifier is added and all you do is go into sculpt mode for the crash.\n\nThank you!\n\n", "crash sculpt mode in multires modify\nOperating system: win 10, Ryzen 3900x 64G ram\nGraphics card: Nvidia 980ti \n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) \n2.83 2020/04/16 15:38 Hash:8cb10c124efe\n\n\n\nCrash when entering Sculpt mode with multires modify enabled..", "Blender Crash when you switch to sculpt mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD FirePro W9100 ATI Technologies Inc. 4.5.13587 Core Profile Context FireGL 17.1.1 26.20.14001.39003\n\nBroken: version: 2.83 (sub 13)\n\nBlender crash when you switch to sculpt mode with a multiresolution modifier.\n\n- select cube\n- add multiresolution modifier\n- subdivide a couple of times\n- switch to sculpt mode\n- blender crash\n\n", "When using Multires in Object mode then back to Sculpt mode Blender Crash.\nOperating system: win 10 64bit \nGraphics card: GTX 960ti\n\nBroken: (2.83 , master, 2020-04-17 and 2020-04-16) both build Broken\n(2.9 , alpha , 2020-04-17 and 2020-04-16) both build Broken\nWorked: 2.82a\n\nWhen using Multires in Object mode then back to Sculpt mode Blender Crash .\n\nUsing Multires in Object mode, subd to 3-4 level > enter Sculpt Mode > Crash\nIn Sculpt Mode using Multires, subd to 3-4 level > to Object Mode and back in Sculpt Mode > Crash\n", "Subdivide Multires into Object Mode crash Blender by switching to Sculpt Mode.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.90 (sub 0)\n\nFrom Sculp mode you can add the Multires modifier and subdivide the mesh without problem, but if it is added from Object Mode, it means that Blender will close unexpectedly, when going to Scuplt Mode.\n\nAdd Multires to the original cube.\nSubdivide a couple of times.\nEnter Scupt Mode.[2020-04-16 07-33-38.mp4](2020-04-16_07-33-38.mp4)\n\n\n\n\n\n\n\n", "Crash when switching to sculpt mode with multiresolution modifier is enabled\nOperating system: Windows 10\nGraphics card: NIVIDIA GeForce RTX 2060\n\nBroken: Version: 2.83 (sub 13), branch: master, commit date: 2020-04-17 20:03, hash: 76b3aac802f9\n*Also Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503*\nWorked: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd76f\n\nBlender crashes when switching to sculpt mode when multiresolution mod with at least 1 level of subdivision is active on that object ***(A)***You can enable multiresolution mod when already in sculpt mode without it crashing however if you exit sculpt mode and return to sculpt mode it will crash***(B)***Multiresolution mod with no subivisions ***will not*** reproduce the crash\n\n***A***\n1: With a new scene add multiresolution mod to default cube (or any new mesh object you create) \n2: Subdivide your mesh in the multiresolution modifier with Either versions of division (Catmull-Clark or Simple)\n3: switch to sculpt mode *Crash*\n***B***\n1: With a new scene go into sculpt mode with default cube (or any new mesh object you create) \n2: Add multiresolution modifier to active object while in sculpt mode and Subdivide your mesh in the multiresolution modifier (note no crash occurs)\n3: switch out of sculpt mode and then back into sculpt mode *Crash*\n", "Entering Sculpt mode after using Multires Subdivide crashes Blender\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 13)\nWorked: Build from April 10th still worked\n\nEntering Sculpt mode after using Multires Subdivide crashes Blender.\n\n1. Add Multires modifier to the default cube\n2. Click Subdivide\n3. Switch into Sculpt mode\n\n", "A Multiresolution modifier created in object mode crashes Blender\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90 (sub 0)\n\nWhen I add the multiresolution modifier in object mode and switch to sculpt mode Blender crashes.\nIf the multireasolution modifier is created while in sculpt mode it works fine until you go back to object mode and again into sculpt mode.\n\n1. Open Blender\n2. Add a new mesh object\n3. Give the object the multiresolution modifier while in object mode and subdivide it a bit\n4. Go into sculpt mode\n5. Crash\n\n[Multires_crash.mp4](Multires_crash.mp4)\n\n", "Instant crash when using the Multiresolution Modifier and switch to Sculpting\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.83 (sub 13)\n\n\n\nAdd the Multiresolution Modifier to the standard cube\nSubdivide 3 or 4 times\nswitch to Sculpting layout or into Sculpt mode\n# > Crash\n\n\n" ]

[ "Crash when deleting ViewLayer while rendering\nOperating system: Linux-5.4.0-66-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.92.0\n\nA crash will happen when deleting a ViewLayer while rendering stills or animations, for any render_display_type\n\n- In the default scene, add a new ViewLayer\n- Set the renderer to Cycles so that you can see the render progress. In Eevee you could set up a little animation to get the same problem.\n- Start a normal render\n- While Blender is still rendering, delete the new ViewLayer that you just added and that was being in use when the render process was called\n- A crash happens with a Segfault, even after some time.\n\nThis problem looks to me as just an unhandled context change, because I noticed that if you delete the current scene or the current camera used while rendering animations, those context changes are appropriately handled and the render process is effectively stopped without a crash.\n", "Tweak tool deselects previously selected items.\nOperating system: Windows\nGraphics card: 1060\n\nBroken: All 2.8 versions\n\nTweak tool deselects previously selected items.\n\n\n", "Better Rigidbody and Constraint Memory Management\nHere is a general diagram of the relevant pieces of the `Object` and `RigidBodyWorld` models\n\n\n\n\n**Problem Scenarios:**\n1. There is an empty with the constraint. Two objects with rigidbodies are linked to the constraint.\n\n - Deleting one of the objects.\n - Deleting the empty with the constraint.\n\t\n\n 2. There is an object with a rigidbody and it has the constraint on it. There is another object linked to the constraint.\n - Deleting the other object.\n - Deleting the object with the constraint.\n\t\n\n**Scenario 1.A:**\nEmpty - Has constraint.\nObject1 - First object in constraint\nObject2 - Second object in constraint.\nPlay simulation for a few frames. Pause simulation. Delete Object2 from scene.\n[Test1a.blend](Test1a.blend)\n\t\n**Problem**\nFor Object2, its btRigidBody has a pointer to the btTypedConstraint. When deleting the btRigidBody, we tell the btTypedConstraint to `removeConstraintRef()`.\nThis however just marks Object2's btRigidBody as not colliding with Object1's btRigidBody, it does not remove the btRigidBody from the btTypedConstraint.\nThe memory for Object2's btRigidBody gets deleted, and btTypedConstraint now contains junk memory that crashes when attempting to run the simulation for the scene RigidBodyWorld.\nFrom looking at the header of btTypedConstraint, it seems like the intent is to never swap out the rigid bodies or change them after the creation of the constraint.\nSo we need to ensure that when an object gets removed from the scene, the btTypedConstraint gets removed from the btDiscreteDynamicsWorld for the scene.\t\n(This also happens when both objects are set in the rigidbody constraint, the simulation is played for a few frames and then paused, and then UNDO takes the object out of the constraint.)\n\n**Scenario 1.B:**\nEmpty - Has constraint.\nObject1 - First object in constraint\nObject2 - Second object in constraint.\nPlay simulation for a few frames. Pause simulation. Delete Empty from scene.\nDidn't cause any crashes that I could find\n\t\n**Scenario 2.A:**\nObject1 - Has constraint.\nObject2 - Second object in constraint.\nPlay simulation for a few frames. Pause simulation. Delete Object2 from scene.\n\n**Problem:**\nEssentially the same as **1.A**\n\t\n**Scenario 2.B:**\nObject1 - Has constraint.\nObject2 - Second object in constraint.\nPlay simulation for a few frames. Pause simulation. Hit Ctrl-Z to undo and move back to start of simulation. \n[Test2b.blend](Test2b.blend)\n\nWhen hitting UNDO, we iterate throught the objects in the scene to delete and recreate them in the previous state.\nWhen deleting, if Object1 is deleted first, that has the constraint on it, we delete the physics object and the constraint.\nEach btRigidBody contains an array of pointers to constraints that it is in. When deleting the physics body, we need to ensure that it is removed from all constraints.\nWe remove the constraint from Object1's btRigidBody, and then delete the btTypedConstraint.\nHowever Object2's btRigidBody still has a pointer to the btTypedConstraint. When deleting the btRigidBody, we attempt to remove it from the btTypedConstraint,\nbut the memory has already been freed, so we get a crash.\n\n\nThese are the most obvious issues with the current implementation, though it is not exhaustive. There are further problems with memory getting corrupted between undoing and rebuilding the simulation that I could not pin down so specifically, but I think these are representative of what the issues boil down to. \nThe crux of the issue is that when deleting any physics object, it needs to know about all the constraints it is in and all the other objects that are related to it in the physics simulation. And if it is in a constraint, but doesn't actually own the constraint, there's no way to find the other objects and relationships it cares about. This also leads to the order-of-processing issues depending on which objects get deleted first when undoing/rebuilding a simulation.\n\n\n**Resolution Ideas**\nMy suggestion is to no longer free `ob->rigidbody_object` or `ob->rigidbody_constraint` directly from an `Object`.\nThe Scene's `RigidBodyWorld` should be responsible for handling removal of all rigidbody related data.\n - It should contain a map from `Object` -> `Set<RigidBodyCon>` so when any Object is being removed the RBW has a link to any related constraints. An object could be in multiple constraints, hence the `Set<RigidBodyCon>`. In theory we could loop through all constraints in the scene to find which constraints an object is in, but this would obviously have a performance impact on a scene with a lot of constraints.\n - When an object is being removed/deleted, the RBW will remove any btTypedConstraint that references it from the btDiscreteDynamicsWorld.\n - It can also remove the btTypedConstraint from any other objects in the constraint so it no longer has a junk pointer.\n\nCreate a hashmap on the `RigidBodyWorld` data structure to contain a map of Objects to the constraints they are in.\n\n```\n /** (blender::Map<Object *, blender::Set<RigidBodyCon>>) */\n void *object_rbc_map;\n```\n\nWhen rigidbodies or constraints are going to be added to/removed from the scene, ensure that the RigidBodyWorld is responsible for deleting all relevant physics objects and constraints, rather than deleting them from the Object directly. \n\nFor **Scenario 1.A/2.A:** the RBW would ensure that if a `btRigidBody` is removed from a `btTypedConstraint`, the `btTypedConstraint` should get removed from the `btDiscreteDynamicsWorld`.\n\nFor **Scenario 2.B:** the RBW would ensure that when deleting a constraint, all objects in the constraint have the `btTypedConstraint` removed from their `btRigidBody`.", "Memory leak with a combination of vertex groups and particle systems\nOperating system: Windows-10-10.0.19043-SP0 64 Bits, **This seems to happen only on Windows.**\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.1\nWorked: no one worked\n\n[system-info.txt](system-info.txt)\n\nThis is not an error but a memory leak bug. The ram is filled more and more at each render. I simplified the file as max as possible. When you remove the 20 copied particule systems, no bug anymore or when you remove all the vertex group, the bug also disappear. But when there is this combinaison of particule system and vertex group there is the memory leak. Note => I duplicated the particule system to see faster ram growth\n\n[Memory leak the animal.blend](Memory_leak_the_animal.blend)\nOpen the file \nrender image repeatedly.\nBlender will use all available memory.\nDoes not happen when rendering animation.", "Mantaflow rendering unstable (when using multiple fluid domains)\nOperating system: Ubuntu 18.04\nGraphics card: Radeon R9 FURY\n\nBroken: 2.83.5\nWorked: none\n\nMantaflow seems unstable during rendering of 6 simultaneous domains and it relates to the cycles AA samples.\nThe error it shows:\n```\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in /home/sources/buildbot-worker-linux_centos7/linux_lts_283/blender.git/extern/mantaflow/preprocessed/fluidsolver.cpp:33\n```\n\n1. Open the example file [mantaflow-render-test.blend](mantaflow-render-test.blend)\n2. Bake the domains one-by-one\n3. Run the `Render Animation`\n4. It's quite a random, so could take some time\n5. on ~160 frame the blender will fail and close with the next error:\n```\nSaved: '/home/user/tmp/mantaflow-render-test-scene/out/0161.png'\n Time: 00:03.10 (Saving: 00:00.08)\n\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in /home/sources/buildbot-worker-linux_centos7/linux_lts_283/blender.git/extern/mantaflow/preprocessed/fluidsolver.cpp:33\n```\n```\nSaved: '/home/user/tmp/mantaflow-render-test-scene/out/0051.png'\n Time: 00:01.78 (Saving: 00:00.09)\n\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in /home/sources/buildbot-worker-linux_centos7/linux_lts_283/blender.git/extern/mantaflow/preprocessed/fluidsolver.cpp:33\n```", "Data lost to a severe crash was auto-recovered and forcefully overrid data that was saved to disk even tho no recovery options were used\nOperating system: Windows 11\nGraphics card: Gigabyte Windforce RTX 2060 OC Super 6GB\n\nBroken: (steam 3.4.x-3.6.2)\nWorked: ()\n\nnote: this is not related to the recovery or auto recovery systems but about pre-crash data being used from ram instead of reading saved data from disk\n\nnote 2: i verified it's old data as it happened with a mask this time and the vertex ids it was assigned after the crash corresponded to the ones that the mask was assigned to after the bug, but was improperly recovered as ids changed due to changes to the mesh, and unmasking those vertices caused them to be moved a random locations as the shapekey they where assigned to did not exist anymore\n\nAfter a severe crash that was not induced by hardware crashes(ie: out of memory/vram, ran out of pagefile memory etc)\nbut from an error internal to blender, even tho data and changes where saved to disk, blender auto recovered data that was not saved and lost to a crash, and it possibly corresponded to a block of ram that was not freed reported by blender in the cmd window;\nafter the unprompted recovery the data even tho it was corrupted it forcefully overrid the data that was saved to disk upon load\n\nthis error seems to recover all kinds of data, it restored a sculpt mask that had been corrupted and was after deleted and saved the file to disk as not having said mask, to even internal textures/texture paint, and changes to properties\n\ni came to this correlation as this type of forceful recovery seems to specifically happen before the ram drops in utilization after a save and a sizable chunk of ram sometimes in the gigabytes is reported as not freed upon closure from the crash\n\nthis also seems to cause blender to not generate crash.log files\n\n\n\nimportant: blender has to terminate from an internal system and not the OS, as even tho blocks of ram still weren't freed windows took care of it in the cases of hardware related crashes causing this error to not happen\n\n\n\nobtain a crash from any of blender's systems not the OS(import, sculpt mask, operators/geometry nodes with faulty input seem to be the most reliable)\n\nif the file is still saving and completes but the ram has not yet been cleared and a crash happens there is a very high chance the old data will be used instead of the data saved to disk\n\n**regarding a blend file:**\nthere is no way for me to provide a blend file as it's dependent on data that is left in the ram by the crash and happened the same way regardless of file, and would require me to find a reliable way to crash blender in this specific conditions, which is out of my knowledge.\n\n", "Cloth simulation randomly breaks down when scrubbing timeline\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1\n\nWhen scrubbing the timeline , the cloth simulation may cause the mesh to become distorted even with the existence of cache. The video below will show a quick way to break the simulation, however, I first stumbled upon the problem when I set the keys for the bones.\n\n[2022-07-22 15-48-43.mp4](2022-07-22_15-48-43.mp4)\n\n1. Create cloth simulation.\n2. Scrub the timeline. After some time, a situation will arise where the mesh will be distorted.", "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", "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", "Film -> Pixel Filter settings are not used when baking textures\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.5.0\n\n\nPixel Filter settings are not used when Baking a Texture, changing them does not effect Baking in any way. The width seems to be fixed at a value of around 0.1\nHad a quick look at the github and I'm guessing they aren't passed to the render when Baking.\n\n\nRender any texture with sub pixel details to a texture, see attached file as example\n\n- Enable viewport render preview\n- Adjust Film->Pixel Filter value, it's effective\n- Bake the texture\n- No matter how you adjust Film->Pixel Filter value, it's not effective on the baked result\n", "gpu module in CustomRenderEngine causes segfault\nOperating system: Linux-5.4.2-arch1-1-x86_64-with-glibc2.29 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.7\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nUsing gpu module in CustomRenderEngine render function causes segfault\n\n- Open attached blendfile\n- Run the python script from text editor\n - it is based on the example bpy.types.RenderEngine.html\n - only difference is, importing gpu module and doing a gpu.matrix.push_pop() in the render function\n - also added faulthandler to see where it crashes\n- change render engine to custom\n- hit f12 (blender crashes)\n\nIs the GPU module not suited for use in CustomRenderEngine ?\nAlso testet drawing a gpu.types.GPUBatch to a framebuffer object without doing matrix.push_pop(), it also caused a segfault. The matrix thing is just the simplest case to reproduce.\n\n[CustomRenderBug.blend](CustomRenderBug.blend)\n\n", "VSE video strips with audio get packed into the .blend file when auto-packing enabled, leading to crashes with large amounts of videos\nOperating system: Windows 8.1\n\nBroken: 2.80, 2019-04-09\nWorked: 2.79\n\nBlender will try to pack all video/audio files in the vse into the .blend file if \"File>External Data>Automatically Pack Into .blend\" is enabled. This is terrible default behavior since it can very easily lead to blender attempting to save huge multi-gb files.\nIn addition to this, if you have more gb of files than you have ram, blender will crash when you enable auto-pack... really easy to do since a single video can easily be over 32gb.\n\nSome notes:\nBlender seems to only decide to do this for video files that have an audio track, even if the audio track is no longer loaded into the timeline.\nThere are no options to pack/unpack a video track. If the audio track is removed, the file will still attempt to be packed, but it cannot be unpacked.\n\nCreate a new 'Video Editing' file.\nLoad several gb of videos with audio into the vse timeline.\nSelect \"File>External Data>Automatically Pack Into .blend\"\nSave the file...\n", "Cycles: adaptive sampling improvements\n- [x] Optimize PMJ pattern generation, and generate more samples\n- [x] Solve issues with combined CPU and GPU not using the same amount of samples. Possibly by using a higher adaptive step for both CPU and GPU.\n- [x] Render multiple small times at the same time for GPU, to allow adaptive sampling to stop and match CPU without too much performance impact.\n- [x] Denoising can detect patterns due to adaptive sampling only working per tile. (#79190)\n\n- [ ] Detect errors in larger windows or using some hierarchical methods, as the simple 3x3 window fails for noisy scenes \n- [ ] Analyze different error metrics, and consider adding some user control over this", "Scene strip to cache/prefetching\nOperating system: windows 10\nGraphics card: rtx2060\n\nv2.83.0\n\n\n32:22 - 36:00\nwatch?v=MW-wn9htHFM\n\nI posted a question for \"blender today\" where Pablo Vazquez and @dfelinto reviewed what I was talking about, and at the end, they mentioned to report it as a bug. i put the time stamps for the video above. my original post read: \"i was wondering how to load a scene strip to cache (like prefetch it) in the vse. currently i have to scroll over the clip multiple times, because pressing play and letting it play doesn't load the whole thing to cache.\"\n\njust to reiterate, I am talking about *scene* strips. I'm not sure if this is actually a bug or a feature request, but considering that they were messing around with it and told me to report it as a bug, that's all i wanted to do. thank you!", "Excessive RAM usage with instances that have emission material\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 471.41\n\nBroken: version: 2.93.3\n\nInstances with a material that contains emission use a massive amount of memory compared with those without emission.\n\nRender a scene with a number of instances (geometry nodes) that have an Emission BSDF on them and the memory usage will be significantly more than with a Diffuse BSDF.\n\nExample scene with 10000 instances of a 250k tri mesh:\n[EmissionMemory.blend](EmissionMemory.blend)\n\nDiffuse material:\n0:25, Mem: 44.7M\n\nEmission material:\n3:52, Mem: 41376.8M\n\n\n" ]

[ "2D filters RAM consumption.\nI think the 2D filters may be using more ram that they should. Even on a simple scene, like the startup scene, the memory usage keeps going up. And this memory is not freed after the game engine stops. I tested with a custom 2D filter, what made me think that maybe were my filter bugging stuff in some crazy way, but then i tested it with blender's standards filters, and the problem still happens." ]

[ " Greasepencil Hue/Saturation modifier\nOperating system:windows 10\nGraphics card:GTX 1060\n\nBroken:2.93beta\n\nHue/Saturation modifier can not take effect on fill-gradient", "Node Socket Name Change results in Cycles Material Rendering Black (name is also identifier, should be read-only?)\nWindows 10\nIntel Core i7-5820k 4.1GHz\n2x Nvidia GTX 970\n\nBroken: 2.79 5bd8ac9\n\nIf you change the name of a Node Socket (not the socket's identifier) of a Cycles Shader Node during execution of a python script, Cycles will render the Material black. \n\nDownload the blend file below:\n[socket_naming_bug.blend](socket_naming_bug.blend)\n\nRun the code in the text editor. \nSwitch to viewport preview.\n\nTo fix the problem, simply reset the two nodes, or add a new Material Output Node and a new Principled Node to the Node Tree. Connect the new nodes together and delete the old ones. \n", "USDZ IO - Occlusion Texture gets stripped\nOperating system: Windows 11\nGraphics card: RTX 3090\n\nBroken: (3.60, 6daa3f6b8a9b)\nWorked: NA\n\n\nWhen importing a sample USDZ file it imports correctly but has no Occlusion applied on the shader. When exporting back out to USDZ the Occlusion map is not included inside the USDZ anymore. \n\nWhen checking the original file (extract the usdz via a 7zip) it does have the AO texture inside the directory.\n\n1. Download sample USDZ file from Apple: Rock.usdz\n2. Import USDZ into Blender\n3. Go to Shading Tab\n4. Export USDZ from Blender\n5. Extract USDZ file via 7zip to check for embedded textures\n6. The directory only contains color and normal maps\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)", "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.", "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)", "Hotkeys conflict between Shader Nodes, Compositing Nodes, GeoNodes and Texture Node Editor.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\nI have hotkeys on frequently used nodes in shader editor. When I switch to Compositing, first of all I have hotkeys already assigned to similar nodes (I did it in shader editor, but they are automatically assigned in compositing). Secondly, I get an error in Compositing - Not a shader or geometry node tree.\n\n1) Apply the \"I\" button to the \"Invert\" node in the shader editor\n2) Switch to Compositing or Texture Node Editor\n3) Call the invert node with the I button\n\nYou get the following error \n```\nPython: Traceback (most recent call last):\n\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 138, in invoke\n result = self.execute(context)\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 129, in execute\n self.create_node(context)\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 92, in create_node\n node = tree.nodes.new(type=node_type)\n\nRuntimeError: Error: Cannot add node of type ShaderNodeInvert to node tree 'Geometry Nodes'\n\nNot a shader node tree\n\nlocation: <unknown location>:-1\n```\nbandicam_2021-11-26_16-53-56-020.mp4\nNode_Conflict.blend\n\n", "Geometry Nodes: HSV color circle has incorrect position\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\n*Input > Constant > Color* shows incorrect position compared to numerical edit or shader editor.\n\nOpen file, compare node representation of a color with position, when you numerically edit input color\n\n", "Sculpt: Grid overlay for Grab active point do not work.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nThis seems to be issue only with Nvidia GPUs on windows.\n\nBroken: version: 3.0.0 Alpha\n\n\nGrid overlay for Grab active point do not work.\n[2021-07-18_18-56-46.mp4](2021-07-18_18-56-46.mp4)\n\n\n**Steps to reproduce**\n[#89942.blend](T89942.blend)\n\n- Open file\n- Check if wireframe overlay is drawn under cursor\n\nWhat fixes this is to have any transform gizmo visible while using brush, then it works until Blender is restarted.\n\n\nFrom #92703:\n\n> This was proposed on the blenderartists thread, I have no idea if it works or if it could broke the preview on the AMD cards\n>  \n> If you know how to compile you can fix it by erasing ! from the line 1157 : if (!depth_test) {\n> to read like so: if (depth_test) {\n\n\n", "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", "Camera texture coordinate output in orthographic view is different from orthographic camera\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\n\nTexture coordinate camera output does not give expected results in the z component when viewing through the viewport in orthographic mode\n\nTexture coordinate camera output does not give expected results in the z component when viewing through the viewport in orthographic mode.\nTo see this seperate the z component and the problems will be directly visible.\nThis issue does not appear when viewing through a camera.\n\nTest file:\n[Camera_test.blend](Camera_test.blend)\n\nThank you and have a nice day!\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)", "Generated texture coordinates incorrect on file load in presence of modifiers\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.82 (sub 7)\nAlso broken: 2.83 alpha, hash f6d5a9551380\n\nGenerated texture coordinates are using modified vertex position on file load, apparently until those modifiers are edited, for rendered preview (only). Actual rendering appears to use generated texture coordinates from unmodified vertex position.\n\nHere's a file with a candy stripe material using generated texture coordinates, with a simple deform/twist modifier:\n\n[gentest.blend](gentest.blend)\n\nOpen it up, don't change anything, and switch to a rendered preview:\n\n\n\nRender and compare:\n\n\n\nEditing the twist angle on the modifier updates the generated coords to work appropriately, and can be considered a work-around, but it's painful to do this on every file load, for every deformed object using generated texture coordinates.\n", "Image Texture shader node with Box projection outputs extreme values when mesh has unusual normals\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0\nWorked: can't test in other versions, since they can't open .blend files saved with Blender 3.0\n\nIf you open the attached file, you will see a mesh that's black everywhere except for some *very* bright pixels (the Bloom effect makes this glitch very pronounced).\nThe material is just an Image Texture node connected to BSDF's color, using Box projection and a completely black texture. Theoretically, it should only output interpolations between the colors of the source texture, but that's definitely not the case here.\nOn its own, the mesh doesn't exhibit the glitch, but some modifiers (such as Displace or Wave) make it manifest for certain combinations of parameters. I suspect that the mesh has some unusual normals or face orientations that the modifiers amplify into even weirder normals, which in turn cause trouble in Image Texture's Box projection.\n[shiny glitch blender3.blend](shiny_glitch_blender3.blend)\n\nOpen the attached file, wait for shaders to compile.", "Looks like an eevee limitations with UV maps and attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\nWhen working with multiple UVs and attributes, eevee disables some normal/bump maps.\nThere is an error in the console:\n```\nGPU_material_compile: Attribute \"nor\" overlap one or more index from another attribute. Note that mat4 takes up 4 indices. While merging eevee_legacy_material_surface_frag_opaque\n```\nIn 3.4, the shader cannot compile at all (pink texture).\n\nThis is not documented anywhere and it is not clear to me how it works, because until I connect nodes with attributes in Base Color, all normals are displayed.\n\n1. Open .blend file.\n2. Turn on the eevee render.\n3. Look, all normals are displayed.\n4. Connect nodes with attributes to Base Color.\n5. One normal map is missing. An error appeared in the console.\n\n" ]

[ "Texture Coordinate node not working\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken:\n- version: 3.3.0 Alpha\n- version: 3.2.0 Beta\nWorked: version: 3.1.2 Release\nThe `Texture Coordinate` node doesn't work in alpha and beta versions of Blender.\n\n1. Open Blender\n2. Open a shading window\n3. Remove all nodes besides the `Material Output` node from the cube's material\n4. Add a `Texture Coordinate` node and connect any output into the `Surface` input from the `Material Output`\nAs one can see, in 3.1.2 the cube is colored based on the coordinates outputted by the `Texture Coordinate` whereas in 3.2.0 and 3.3.0 it displays as bright pink, indicating a missing texture.\n", "Regression: Material Preview Not Displaying Textures\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0 Beta\nCaused by 281bcc1c1d\n\nMaterial Preview Not Displaying Textures, instead displaying pink missing texture color, (Vanilla blender) no change in settings or addons\n\n- Open default scene\n- Switch to shading workspace\n- Add image texture node (and connect it to color input of `Principled BSDF` node\n- select image texture node and create new image or open the existing one from the drive\n\nFile with all steps included\n[#97827.blend](T97827.blend)", "Eevee & Material Preview Not Compiling Basic Shader With Texture with RTX 3090ti (Always Pink) \n[system-info_3.2.0.txt](system-info_3.2.0.txt)\nOperating system: Windows 10 Pro\nGraphics card: RTX 3090 ti\n\nBroken: 3.2.0 Beta\nWorked: 3.0.0 - 3.1.2\n\nIf we add an image texture to the Base Color input of a Principled BSDF node, the material will become pink, along with an error being printed to the launching terminal. . \n\nThis only seems to happen in Eevee and the Material Preview modes, the object renders out appropriately in Cycles. \n\n\n\n\n\n1. Open a Shader Node view\n2. Create a new material\n3. Create an Image Texture node.\n4. Connect the Color Output pin to the Base Color Input pin of the Principled BSDF node\n5. Change viewport mode to Material Preview, or Rendered and the object will appear to be pink", "[Eevee / Viewport] Normal Maps Broken\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0 Alpha\nWorked: Worked a day or two ago.\n\nAttaching a normal map from an image texture breaks to the pink unrecognized / missing texture.\n\n1. Create Cube.\n2. Go to Material Preview\n3. Add New Material.\n4. Plug in Normal Map node with an Image Texture input.\n5. Pink.\n\n\n\n" ]

[ "Wrong status bar keymap for release confirms and right click select\nOperating system: Manjaro x64\nGraphics card: HD5770\n\nBroken:\n2.80, 81ea815dcb6, blender2.8, 2018-12-12\nWorked: 2.79b\n\nWhen grabbing something(object, vertex, etc) by right clicking on it and then releasing/clicking on the same button the action is not performed, object doesn't return to its initial position. \nHowever if you use G or a Tool to grab instead of mice click Cancel by Right clicking option works.\n\nRight click on a Cube(in 2.79 thats enough to start moving an object but not here here you have to hold the button) AND HOLD the button\nDrag mice somewhere to move the Cube\nRight Click again to Cancel movement\nNothing happens.\n[blender_bug-2018-12-13_22.18.53.mkv](blender_bug-2018-12-13_22.18.53.mkv)\nI'm also attaching video file for it to be more clear.", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at greenstoneleaf@gmail.com\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Crash when rendering animations (GPU Subdivision ON, OFF is fine)\nSystem Information\nOperating system: WIndows 11 22H2\nGraphics card: Nvidia GeForce RTX 4080\n\nBlender Version\nBroken: 3.4.1, 3.5, 3.6\n\nForce closes when rendering animation after a number of frames and when opening larger blend files. Happens with all files. All drivers up to date and tested memory with no issues. Worked without issue for 6 months, crashing started 1 week ago.\n\nRendering animation with GPU Subdivision unchecked did not trigger a crash", "Lasso Select Broken if Select key is changed from Default Left to Right\nOperating system: Windows 10 (Home)\nGraphics card: Nvidia 1070 \n\n**Blender Version** \nBroken: 2.90.0 (Steam)\nWorked: Not sure, Has been like this since before 2.79b\n\nWhen the default select mode is changed from Left to Right Mouse button Lasso Select no longer works with Tweak + RMB Any. \n\nSplash Screen Change on initial set up or Select button or Edit - Preferences - KeyMap - Select With Mouse Button\n\nAffected: any View Mode that has the Lasso option. (Edit mode, Object Mode, Grease Pencil, etc)\n\n\nSee attached MP4.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nStart Blender and use Start up Cube. [BlendBug_2.mp4](BlendBug_2.mp4)\n\nTemporary fix if the Select key is changed from Left to Right Mouse Button is to walk through the KeyBindings and set anything that uses Lasso to Tweak Right and anything that was using Tweak Left to Tweak Right where Lasso is was changed. ", "Smoke domain emission render has blocks using View Layer Indirect Only \nOperating system: Windows 10 Home 10.0.183363\nGraphics card: Nvida RTX 2080 super\n\nBroken: 5e04548500\n\n\nWhen setting the volume object (smoke domain) into Indirect Only, the render doesn't seem correct (the black blocks show up).\n\n- Play the animation to bake the 5 frames.\n- Render any of the 5 frames to see blocks in the image. \n\n\n[indirect_only_volume.blend](indirect_only_volume.blend)\n\n\nThanks\n", "[Mantaflow] Fluid volume loss with moving obstacle.\nOperating system: Linux-5.8.0-33-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.92.0 Alpha\n\nThe fluid suffers a loss of volume when a container obstacle moves.\n[MF_MovingObstacle_BUG.mp4](MF_MovingObstacle_BUG.mp4)\n\nThe attached file contains a setup that demonstrates the issue. Just hit play and wath at the moment that the bowl moves the fluid inside simply starts to disappear...\n\n[MF_MovingObstacle_BUG.blend](MF_MovingObstacle_BUG.blend)", "Smoke: \"changing Flow Type\" does not affect already computed frames.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Beta, f903e3a3fd003e5295f7aea35710a77b2e74f846\n\nAfter \"Quick Smoke\" changing \"Flow Type\" for already computed frames has no effect.\n\nNew Scene, delete cube and add Suzanne (optional probably).\nSelect object, F3, \"smoke\" enter on \"Quick Smoke\".\nPress space bar to play the scene, you should see smoke rising around the object.\nPress space bar again to stop the sim around say frame 150.\nIn the Physics Properties, change the Flow Type from Smoke to Smoke+Fire or Fire.\nPress space bar to resume the playback.\n\nObserve that new frames not previously computed will reflect the new Flow Type, but when it wraps around to the previously computed frames it only shows the original \"Smoke\" flow type. \n\nIf you save the scene and re-load it, then the currently selected flow type will affect the scene correctly from frame 1.\n\nSo when changing \"Flow Type\" it does not clear frames that have been computed/cached under the previous value. \n\nI looked for some place to explicitly clear that cache without any luck but maybe I just didn't fine it. Since reloading the scene resets the now incorrect frames, it seems to me that changing the Flow Type should immediately invalidate any now-obsolete frames that were computed using the old setting.", "Graph Editor Expand/Collapse Channels collapsing happens on all hierarchy levels at once [Outliner doesnt do this, expanding is also one step at a time]\nOperating system: Mac 10.15\nGraphics card: \n\nBroken: 2.90.0\nWorked: never\n\n(This might be considered a feature request, it would be consistent with the Outliner though)\nIn the Graph Editor when working on the left panel and use '+'/'-' keys on Numpad, the '+' is working well, it opens the collapse levels one each time, but the '-' is collapse all the level in one time. It is not convenient when having lots of things in this panel.\n\n[Screen Recording 2020-09-13 at 22.22.54.mov](Screen_Recording_2020-09-13_at_22.22.54.mov)", "Adding noise to smoke simulation causes colors to change dramatically\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0\nWorked: Not since mantaflow introduced in 2.82, worked with \"high res\" back in in 2.8\n\nWhen creating a quick smoke simulation with default settings (except changing the \"smoke color\" on the emitter object to purple. Adding Noise will make the smoke above the emitter turn yellow while the rest stays purple\n\n.blend has been attached with this reproduction.\n1. Delete everything from default scene.\n2. Add ico sphere.\n3. Select sphere, \"quick smoke\".\n4. Set sphere smoke color to purple.\n5. Enable noise in domain properties.\n6. Add area light to light up the smoke sim.\n7. Add \"color\" attribute to principled volume in the default domain node set up.\n\n", "mantaflow instability on high timesteps\nmacOS 10.14\nIntel HD 6000\n\nBroken ce64cfd6edc2a0ec0aabfd4daaa5f655763cc74b, 2.83.12\n\n**error**\n\n[11110001-0070.mp4](11110001-0070.mp4)\n\n- Add quick liquid to default cube.\n- Set minimum and maximum timesteps to 100.\n- Bake up to frame 70 and watch the liquid explode.", "The flame of the Mantaflow Domains disappears when you make an append of the baked object.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nWhen simulating fire with Mantaflow, although the fire is baked and is correctly represented in the scene in which it was created, it disappears when an append of the domain is performed in a new scene.\n\nOpen the default scene.\nSelect the cube.\nWith Object / Quick Effects, create smoke.\nSelect the Flow Cube and in Flow Type activate Fire + Smoke.\nIn the Domain Cache activate Data File Format = OpenVDB.\nSimulate and bake the animation.\nSave the file\nOpen a new file.\nMake an append of the Domain.\nThe problem persists in the different render engines.\n[2020-02-12 21-06-54.mp4](2020-02-12_21-06-54.mp4)\n", "No fluid particles created when switching from gas to liquid\nOperating system: Linux-5.4.0-40-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.90.0 Alpha\nWorked:2.83 sometimes shows the same behaviour, and sometimes it works (???) however in 2.90.0 I can consistently reproduce this.[logs.zip](logs.zip)\n\nWhen 'manually' creating a fluid sim, no particles are created, while when using 'quick liquid' it does work as expected.\nChanging the cache to an empty directory correctly initializes the particles.\n\n- default startup\n- switch to wireframe view\n- duplicate startup cube\n- scale duplicate x 2\n- select original cube. go to physics properties. check liquid.\n- choose 'type = flow' in fluid panel\n- choose 'flow type = liquid' in the fluid settings panel, leave the rest of the settings as is.\n- select larger cube\n- go to physics properties, check fluid\n- check 'type = domain'\n- check 'domain type = fluid'\n\nNo particles are created inside the small cube. \n\nGoing to the cache settings and selecting a different (empty!) cache folder solves it makes it create particles.\n\nWhen I set MANTA::with_debug to 1 and I compare a run between 'quick fluid' and 'manual fluid' the first obvious difference is that has_data is 1 in the 'manual' fluid run.\n\nCould it be that erasing the cache for the unused gas cachedata fails somehow?\n\nAttached are two console outputs , one from quick fluid and one using the manual steps above (except that I used a different scale factor for the domain in these runs) \n\n\n(edit: removed embedded text files and added them as a zip)\n(edit2: cleared up some mixup with the bugreport I originally wrote for 2.83)\n(edit fix small typo)", "Blender Mantaflow gas fire and smoke simulation - Adaptive Domain moves problem!\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nTHE SAME BEHAVIOUR FOR Blender versions 3.3.1 and 3.4.1.\n\n\nIf Noise is ON then:\nsometimes Adaptive Domain position jumps between two consecutive frames and smoke jumps too.\n\nAdaptive Domain jumps problem\n(even if Domain is static - must be much larger)\n\nsometimes Adaptive Domain position jumps between two consecutive frames and smoke jumps too which is noticeable for the viewer and not acceptable.\n\nSee \"Adaptive Domain jump - Noise ON OFF.png\"… the camp fire simulation according to the book \"Learn Blender Simulations the Right Way\".\n\nIf Noise OFF, OK! Seems Noise OFF is solution to these problems but then smoke does not look good. Or Adaptive Domain OFF but then render time is soaring.\n\nBlend files without simulation data (too big) in \"AD boundary jumps\" directory shows the problem, in my simulation data most remarkable jump was between frames 353 and 354.\n\nuploaded files \"AD moves problems.7z\"\n\n\n- Open file QuickSmoke4.blend\n- Bake data + noise\n- Check next frame (353 -> 354)\n\nDomain will move.\n", "Prevent catalogs from closing after droping\nThis isn't just confusing and unexpected, but also causes the tree to shrink which is visually quite disruptive. So a catalog should keep its state on drop.\n\nThink this needs to be or should be implemented on the tree-view API level, because I expect other tree-views will want item drag & drop support for reordering as well.", "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" ]

[ "Quick explode crash\nOperating system: Microsoft Windows-10 home -10.0.17763 64 Bits\nGraphics card: Intel(R) Core (TM) i3-3217U CPU @ 1,80GHz, 1801 Mhz , 2 Core(s), 4 Logical Processor 10.0.17763 Build 17763\n\n\nBroken: version: 2.80 (sub 74), blender-2.80.0-git.e73647bf5b44-windows64\nWorked: (optional)\n\n\n[quick explode is closing the blender down]\n\n\n[In the drop down objects box choosing Quick effects then quick explode it is closing the blender down. However I have checked all other quick effects with no problems, working for fur, smoke or fluid.]\n\n\n" ]

[ "Bake All Dynamics doesn't include all when Lifetime of particle system gets animated\nOperating system: Windows 10\nGraphics card: Quattro\n\nBroken: 2.91.0\nWorked: \n\nWhen the lifetime setting of a particle system gets changed during an animation of the emitter and the animation gets baked, the number of frames are not aligned to the changed lifetime. \n\nInitial lifetime of 100 will be changed during the animation to 500. Number of frames after bake is the frame end setting of the particle system plus the initial life time setting - in this case 100.\n\n- Open attached file or (Based on the default startup):\n - Set number of frames to 1.000\n - Create a sphere - size .1\n - Enter keyframe on frame 0 for location x,y,z\n - Move sphere on x-axis to +10\n - Enter keyframe on frame 250 for location x,y,z\n - Add particle system to the sphere, 1.000 pieces, start frame 1, end frame 250, lifetime 100\n - Add keyframe for lifetime on frame 1 and frame 49 with lifetime value 100\n - Add keyframe for lifetime on frame 50 with a lifetime value of 500\n\n- Bake all Dynamics\nYou will see 351 frames in memory and not 751 as expected\nAlthough the error is the same, rendering of animation does still work in Blender 2.83.5 but not in Blender 2.91.0 anymore\n **WORKAROUND:** Set keyframe for lifetime on frame 0 with lifetime value 500 \n[LiveTimeTest_002.blend](LiveTimeTest_002.blend)\n\n\n\n", "Particle hair simulation not working\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.93.4\nWorked: unknown\n\nI modeled particle-hair and try to make it dynamic, for whatever reason I cannot make it to work and sometimes Blender crashes.\n\n[Test.blend](Test.blend)\n\n[Test.crash.txt](Test.crash.txt) \n\nIf I try another simple particle-hair system on the-same object it does work. \n\nTry to get the hair in attached file to simulate.", "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)", "Clicking \"Bake All Dynamics\" causing various crashes.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\n\nUsing \"Bake All Dynamics\" is beyond finicky and crashes Blender in many different use cases. Many little \"tricks\" are needed to make it work. I am using Disk Cache for all below situations, but I believe the crashes happen with or without this.\n\nSituations where it crashes:\nClicking \"Bake All Dynamics\" within the Cloth cache settings. It seems it's required to click \"Bake All Dynamics\" button within the context of the Rigid Body system, or else it crashes instantly.\n\nClicking \"Bake All Dynamics\" in the context of hair dynamics seems to do nothing. Same goes for \"Update All to Frame\"\n\nIf a rigid body simulation has been baked, clicking \"Delete All Bakes\", then clicking \"Bake All Dynamics\" immediately will also crash blender. The only workaround for this is to \"move\" an object even if using a zero value, before clicking \"Bake All Dynamics\" again. This prevents the crash. \n\n\nCreate a Rigid Body Sim, create a Cloth Sim. Check \"Disk Cache\" as an option. Try the various methods listed above.\n\n", "Mantaflow simulation stops and crashes at the end of the bake (or when closing blender): The CG solver diverged, residual norm > 1e30, stopping.\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nCrash baking fluid simulation.\n\n\nOpen the file and bake all its frames (or only frame 181 to 183).\n\n[beach.blend](beach.blend)\n\n```\nTraceback (most recent call last):\n File \"<string>\", line 1, in <module>\n File \"<string>\", line 169, in bake_fluid_data_5\n File \"<string>\", line 164, in bake_fluid_process_data_5\n File \"<string>\", line 136, in liquid_adaptive_step_5\n File \"<string>\", line 221, in liquid_step_5\nRuntimeError: GridCg::iterate: The CG solver diverged, residual norm > 1e30, stopping.\nError raised in extern/mantaflow/preprocessed/conjugategrad.cpp:562\n(...)\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in extern/mantaflow/preprocessed/fluidsolver.cpp:33\nAborted (core dumped)\n```\n\nComplete output: [P2568](P2568.txt)", "[Mantaflow] Generating a huge number of particles as substeps increase\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7560D ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008\n\nBroken: version: 2.90.1\n\nThe number of particles increases as the number of substeps increases.\n\nBake the liquid from this scene.\n[substeps_bug.blend](substeps_bug.blend)\nYou will see the following:\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", "Crashing while viewing animation in Cycles\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.4.0\n\nWill crash seconds after playing animation in viewport when Cycles is selected and in render view. Both CPU and GPU crash. Does not crash when removing the Subdivision Surface Modifier so polycount may be a factor? This is a brand new Apple M1 Max computer from BestBuy with nothing else installed. Also tried initializing a render to video file and crashed as well. (Note: This is an error strictly with Apple M1 computers as I have tested it on an Apple intel MacBook Pro and it works just fine.) Thank you and happy holidays!\n\n1. Load file. It is a mesh plane with default cloth and subdivision modifiers acting on a wind force.\n2. Make sure Cycles is selected as Render Engine.\n3. Select Viewport Shading to Rendered (to view cycles render)\n4. Push play. Will crash or freeze seconds after play.\n\n[Cloth_Cycles_Crash.blend](Cloth_Cycles_Crash.blend)\n\n[Blender 3.4 Crash Report 12.13.22.rtf](Blender_3.4_Crash_Report_12.13.22.rtf)\n[Blender 3.5 Crash Report 12.14.22.rtf](Blender_3.5_Crash_Report_12.14.22.rtf)", "Particle Edits not being deleted from blend data after 'Delete Edit', filesize bloat\nBroken: blender-2.80.0-git.03bd024c077d-windows64\n\nAfter deleting a particle edit, the filesize remains the same.\nFor particle systems with large amount of particles, this leads to massive filesize bloat that cannot easily be reversed.\nThe only way around it is to delete the Particle System and add it again with the same Particle Settings, but this is troublesome because particle settings relating to the object (ie, vertex groups and materials) need to be setup again in the particle settings.\n\n- Create particle system (eg, hair)\n- set particle amount to something large like 300,000\n- in particle edit mode make some changes\n- save, observe filesize (around 100mb)\n- Delete Edit from particle system panel\n- save, observe filesize (doesn't reduce)", "Particle Edit mode for non hair particles - Not working\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)\nWorked: can not find one\n\n\nCan not edit a baked particle simulation's particle paths in Particle Edit mode\n\n\n- Delete all object from the original scene\n- Create a plane\n- Add a particle system. For the sake of testing with 20 particles,\n- Bake the simulation (not in disk)\n- Switch to Particle Edit mode\n- Select Point select mode\n\n- > There is no particle path in the view-port to be edited.[path not showing in particule edit .blend](path_not_showing_in_particule_edit_.blend)\n", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Crash 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)", "Particle system bug with texture influence\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: N/A.\n\nParticle system caching issue. \n\n1. Make a particle system with collider that kills particle. Add a cloud texture to influence it's density.\n2. Now bake.\n3. Now later when you increase or decrease size of the particle. the cache breaks. \n4. Some particle is starting to stay on collide serve instead of killing . And some particle floats around.", "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" ]

[ "Hair Dynamics: entering particle edit mode with baked cache crashes blender\nOperating system: Windows 10 64-Bit\nGraphics card: Nvidia GeForce GTX 1080Ti\n\nBroken: cef41d0144e\n\nSwitching to particle edit mode on an object with baked hair dynamics crashes blender. I'm not sure when or why you'd actually want to do that, but it shouldn't cause a crash.\n\nOpen the provided .blend file and switch to particle edit mode. Otherwise you can recreate the MWE:\n\n - Add a particle system to the an object\n - Activate hair dynamics\n - Bake the physics\n - Switch to particle edit mode \n\n[mwe.blend](mwe.blend)\n" ]

[ "Trackpad scrolling is too sensitive in Text Editor\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101\n\nBroken: version: 3.6.1\nWorked: never\n\n\nIf you scroll very slowly, nothing happens, deltas that give an offset of less than one line/character are simply discarded and not accumulated. The minimum possible scrolling is too fast, this jumps several lines at once and it's impossible to stop at the desired one.\n\nOne of the possible solutions can be seen here: D9552. This makes the scroll speed match the speed in other Blender editors, and other macOS applications as well.\n\nAnother solution could be to use a smooth scroll like with the MMB.\n\n", "Interlaced 3D Viewport swaps eyes when creating new window\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro [P1000](SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.56\n\nBroken: version: 2.91.0\n\nI am using a Zalman Trimon passive 3D monitor which uses Blender's interlaced 3D mode to display stereoscopic 3D. Everything works well in the 3D Viewport until I either create a new window or resize a nearby window. The original 3D Viewport pane suddenly swaps the left and right eyes and never goes back to the original configuration. It appears that dragging an adjacent window triggers the 3D Viewport to be vertically offset by one line, which causes the left eye image to become the right eye image and vice versa.\n\nSee this video for a demonstration (use the password \"blender\" without quotes): x7yf3cg\n\n- Open the default Blender file.\n- In the Properties editor, go to the Output Properties tab, check Stereoscopy and make sure Stereo 3D is picked as the option.\n- Go to Window -> Set Stereo 3D.\n- Set Display Mode to Interlace. Leave Interlace Type set to Row Interleaved. Leave Swap Left/Right unchecked.\n- Look at any object in the 3D Viewport through a 3D monitor that can interpret interlaced rows. Take note if the object is in positive parallax (the object is deep within the screen) or if the object is in negative parallax (the object is sticking out of the screen).\n- Create a new 3D Viewport pane by dragging the lower right hand corner of the current 3D Viewport up.\n- Note that the original 3D Viewport pane has swapped the left and right eyes (i.e. if the object was in positive parallax, it's now in negative parallax and vice versa), but the 3D Viewport pane you just created has the expected views for the left and right eyes.\n\n[swapped_eyes.blend](swapped_eyes.blend)\n", "Lag reading viewport depth buffer in LookDev mode\nOperating system: macOS Sierra version 10.12.6\nGraphics card: Radeon Pro 55 2048 MB\n\nBroken: ( 2.80 )\nWorked: (optional) ( 2.80, 3325b19ee7fd, branch: blender 2.7, 2019-06-06 )\n\n\nIn LookDev mode, zooming is extremely choppy. This topic was adressed earlier and dismissed a hardware issue. But the problem did not exist in an earlier version, suggesting it probably could be a software related issue. Check the video beneath.\n\nBased on the default startup or an attached .blend file.\n\n[devlook slow zooming.mp4](devlook_slow_zooming.mp4)", "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "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", "Flip the Render\nI proposed this idea to Campbell via email and he said it sounded reasonable enough to add here...\n\nThe idea: In the image editor, when the Rendered Result is displayed, pressing F will flip the render horizontally. This is a common action that many digital painters use in Photoshop to refresh their eyes and see new flaws in their work.\n\nSome notes:\n - It will should only work in the Rendered Result, not on regular images\n - All tools that normally work in Rendered Result, should work here as well. (rendered border, sampling image color, painting)\n - Only Flip X. I've tried Flipping Y before, but I haven't found it to be that helpful in the artistic process. Could be added later though if people want it?\n - Should apply the Flip state to all Slots. Eg. If flipped in Slot 1, when you change to slot 2 it will also be flipped. If you turn Flip off in Slot 2, it will also be off in Slot 1 and all slots.\n - To remove the potential confusion for users who flipped it by accidentally pressing F but don't know the hotkey, a new button should display in the toolbar. Here: ", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "Multi-Object-Mode: EditMesh Vert/Edge Slide (transform) incorrect orientation for non active objects\nVert/Edge slide calculates the closest edge, then a screen space vector to move the cursor along to perform the slide.\n\nThis currently is only correct for the active object.\n\nIt's possible to have multiple objects rotated differently so the slide vector will be wrong on some objects.\n\nNote that performing vert/edge slide on multiple loops (while supported) is not all that common.", "Can't scrub timeline with alt + pan trackpad gesture\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.105\nMacOS 10.13.6 + Apple Magic Mouse\n\nBroken: version: 2.83 (sub 15)\nWorked: never ?\n\nWhen using a Magic Mouse it's not possible to navigate the timeline using the \"ALT+scroll\" default shortcut.\nCorrect behaviour is seen in **[this ](watch?v=o19U-yPGdyY&feature=youtu.be&t=84)** official Blender video.\n\nThis shortcut is in : User Preferences > Keymap > \"Frame Offset\".\nYou'll see it's actually **two instances** of the same shortcut :\n- one to scroll forward (ALT + Wheel Down) >> `screen.frame_offset = +1`\n- another to rewind (ALT + Wheel Up) >> `screen.frame_offset = -1`\n\nThis is a problem because the Magic Mouse is actually seen as a trackpad, therefore we have to use the \"Mouse/Trackpad Pan\" event.\nUnfortunately if you do that you are only able to scroll one way, because this shorcut entry doesn't \"see\" the scrool as bidirectional.\n\nProposed fix : add a new shortcut entry, like it's been done for \"Zoom View\" and \"Pan View\" for example.\n{[F8515046](MagicMouse_timeline_scroll.jpg), size=full}\n\nOn a Mac, using a Magic Mouse :\nopen Blender, in the viewport try to do ALT+scroll > it doesn't scroll the timeline.\n\n\n", "Mistranslated Modifier Option on MacOS using Logitech Mouse\nOperating system: MacOS 12.6\nHardware: Mac Studio M1\nBlender Version: 3.3.0\n\nI use a Logitech M500s corded mouse (FW 53.00.0011) and I programmed the 4th and 5th buttons (on the side) using Logi Options (version 9.70.29) to Modifiers, Shift on one, and either Ctrl or Cmd (I have not settled on which is better) on the other. This has worked fine on all my software until Blender.\n\nAlso, since the Middle button on the mouse is critical in Blender, and since the M500s defaults to side scrolling (which I never use) when you tilt the wheel and these activate way too easily, I re-programmed both the tilts to emulate a Middle mouse button click. I left the normal wheel scrolling untouched. This allows me to click or tilt the wheel to get a Middle mouse click without worrying if I hit it correctly. This has worked great in Blender, both the normal scrolling and middle mouse clicks work as expected.\n\nWhat does not work in Blender is my using buttons 4 and 5 as modifiers when I combine them with other mouse actions. I was getting unexpected results, so I used Keymap to find out what was happening, and discovered the following:\n\nPressing button 4 (or 5) alone works: I see the appropriate \"Ctrl\" (or \"Shift\") appear but it does not map, of course, as I am only providing a modifier. I see the same effect on the status bar when I press the buttons in the editors. I see the guides correctly change for each modifier press.\n\nPressing button 4 (or 5) with a keyboard key works: Blender correctly maps the appropriate modifier (Shift, etc.) with the selected key. Same happens in the editors, e.g. when I use the modified mouse button for \"Shift\" and hit \"A\" on the keyboard, the Add menu pops up correctly.\n\nPressing button 4 (or 5) with mouse Left or Right buttons fails: Blender maps the appropriate modifier (Shift, etc.) but with button 4 (or 5) instead of with the pressed Left or Right button. If Blender is doing this elsewhere, it would explain why I am not getting expected results in the Editors.\n\nPressing button 4 (or 5) with a Middle mouse button (any as programmed) fails: Blender maps the appropriate modifier (Shift, etc.) but with \"Wheel Up\" instead of with the Middle button. Again, this could explain my unexpected results in the Editors.\n\nBy the way, when I press button 4 (or 5) and move the wheel, I get the same map, the appropriate modifier with the appropriate \"Wheel\" direction, although I can get \"Wheel Down\" with the actual wheel.\n\nAlso, when I press a Middle mouse button alone (any three): Blender correctly maps the Middle mouse button as pressed. As it does with any other mouse action except the buttons modified to be Modifiers.\n\nI tested for this problem on my Windows 11 system. Different mouse, G502, and different options software (G Hub vice Logi Options) but same Modifier settings (Shift and Ctrl) for buttons 4 and 5. It worked fine on my Windows system.", "Sculpt mode -> Curve Stroke causes Undo to behave differently\nOperating system: Windows 10 x64\nGraphics card: Nvidia 980 GTX\n\nBroken: v 2.82 Alpha, 10-12-2019\n\nIf Brush stroke is set to Curve and some sculpt detail is added (Ctrl + Left Click), (Ctrl + Z) or Undo does not work. Instead of Undo for the sculpt detail, the curve control points are removed.\n\n1. Start with default cube and add Multi-Res modifier, subdivide a couple of times.\n2. Go to sculpt mode and with the SculptDraw brush set the stroke to Curve.\n3. Draw a curve using (Ctrl + Right Click) to add some control points.\n4. Add sculpt details using Ctrl + Left Click. \n5. Press Ctrl + Z. Instead of removing the details the control points of the curve will be removed first. \n6. Press Ctrl + Z repeatedly. When the last control point remains then the sculpt detail will be removed.", "Undo doesn't work with paint mask selection (texture paint vs. vertex/weightpaint)\nOperating system: Linux-5.2.10-arch1-1-ARCH-x86_64-with-arch 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.32.0, 5.2.10-arch1-1-ARCH, LLVM 8.0.1) X.Org 4.5 (Core Profile) Mesa 19.1.5\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nUndo does not work with paint mask selections. The expected behavior here is that undo should work as in other selection modes.\n\nClick on texture paint.\nSelect single image and create a texture.\nTurn on paint masking, and then select the \"select box\" tool.\nclick on a face on the cube to select it.\nPress ctrl-z.", "mouse scroll zoom freeze in first attempt \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.0.0 Alpha\n\nHello , i tried new version for blender 2.92 and found that whenever i rotate my object or do pan, immediate after that zoom in and zoom our \"with mouse scroll\" not working for some fraction of second. it freez for one scroll motion. Otherwise working fine with \"alt+MMB\" \nAlso i tried this same thing with version3.0.0 but same thing happened. Don't remember about the previous version. \n\nalso i checked my mouse with other 3d software but it worked fine there. so mouse is not causing errors i hope. \n\nopen fresh blend file\nrotate camera/view with MMB\nimmediate after rotating the camera/view scroll in or our. It will miss for sure. \n\nbut the speed for rotating and zoom in our should be fast. it worked in slow manner. \n\n\nThanks in advance, \n", "error in custom view3d.move Keymap Setting\nOperating system: Windows11\nGraphics card: It doesn't matter\n\nBroken: up to 3.5.1\n\n\n\nBecause I often use the 2D features in Blender, and the pan view function in Blender is not very convenient (requires using Shift + MMB), I made the settings as shown in the picture to add a new pan view keymap to Spacebar + LMB. In the normal object mode, I can indeed pan the view by using the new shortcut, but once I switch to any other mode, this shortcut key will be disabled. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822" ]

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

[ "Unexpected behavior when applying Geometry Nodes modifier on top of the Multires.\nThis is a more comprehensive report on a bug that was recently posted and closed [HERE ](T97603)\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1+\n\nApplying Geometry Nodes on top of the Multires modifier does not give expected results. Multires is an exception from the \"Applying a modifier will apply it as if it was first in the stack\" rule, when a modifier is applied on top of the Multires, the mesh changes will be applied to the currently visible subdivision level. Quick video below.\n[Multires GNodes Bug.mp4](Multires_GNodes_Bug.mp4)\nAnd the Example .blend file > [Multires GN Bug.blend](Multires_GN_Bug.blend)\n\nHow should applying the Geometry Nodes behave ? When the Geometry Nodes modifier doesn't change the vertex count and simply deforms the mesh, it should behave just like any other modifier, see example video with the Shrinkwrap modifier. \nSo what when Geometry Nodes does change the vertex count ? I say we keep the same behavior that solidify modifier has, it skips Multires and applies it as it would be first in the stack. While of course this will bring broken results, this is a already an existing behavior so i think it would be completely fine.\n\nSeries of images presenting how applying a Solidify modifier on top of Multires behaves. (Intended behavior)\n\n\n\n\n\n\n\n", "Changing \"Disable in Viewports\" of a viewlayer-disabled collection would affect animation playback speed\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.6.1\n\nDisabled objects are affecting animation playback when the armature is placed in a collection.\n\n\n- Download and open \"Buggy_easier.blend\"\n- Play animation, it goes smoothly.\n- Click the \"Disable in Viewports\" button (the little screen button) for \"Collection\" which is disabled in view layer.\n - Animation plays much slower due to evaluation happening in that collection.\n - If instead, you click the little screen button for \"Collection For Extra Cubes (DISABLED)\" (which is also disabled in view layer), playback proceeds normally.\n\n------------\n\nOriginal description:\n\nI have attached two blend files. \n\nNot_Buggy_Blend\nThe objects are parented to the armature. The armature is placed directly in view layer (without any collections).\nAll Cubes use \"auto smooth\" and contain 20k+ polygons.\nThe first Cube is enabled.\nThe other cubes are disabled. These cubes are also shrinked wrapped to the first cube. \nMy animation playback is 60 fps.\n\nBuggy_Blend\nSame setup as in Not_Buggy_Blend. The only difference is that the armature is now placed in a collection, and the disabled cubes are also placed in a collection.\nPlayback is poor.\nMy animation playback is 15 fps.\n\n", "Geometry nodes. Viewer node data late update (delete node and undo)\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**Short Description**\nSpread Sheet editor is not updating when I undo the action of viewer node deletion\n\n**Steps to Reproduce**\n- Open .blend file\n- Delete viewer node\n- undo (You will not see any data in the spreadsheet until click on the viewer node or hovering mouse over spreadsheet)\n\n[#94641.blend](T94641.blend)\n[2022-01-04_20-09-05.mp4](2022-01-04_20-09-05.mp4)\n", "Geometry Attributes panel in Edit Mode (design pending)\nThis task is going to adding a unified panel for editing attributes of the selected element by value in edit mode. It makes users able to pass arbitrary per-element data to geometry nodes, opening up more possibilities for procedural modeling.\n\nAll data types (int, color etc.) should be supported. \nDomain supports should match selection modes in edit mode (eg. no face corner support for meshes). \n\n## Basic\nAttributes on the active element is listed in the side panel. \nItems are grouped by domain.\n\n\n## Multiple Selection\nfor float types (float, vector, 2d vector): \n* Show a mean value computed from all selected elements. \n* Button offsets values of all selected elements.\nfor other types: \n* If an active element with a matching domain exists, show the value of it.\n* Button only affects the value of the active element.\nFill operators are provided for batch editing. It fills current button value into all selected elements.\n\n", "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)", "UV: Modified Edges UV overlay don't show on generated Mesh from Geometry Nodes\nBroken: version: 3.6.0\n\n\"Modified Edges\" UV Option does not work when there is Join Node or primitives is used to generate geometry.\n\nIn setup like this, where we generate UVs in GN, and have \"Modified Edges\" overlay work correctly.\n\n\n\nWhen we generate geometry eg. by using Join Node, or Primitives. Overlay no longer works (even in UV sync mode where all UVs should be shown)\n\n\n\n\nI'm not sure if its desired behavior because eg. some setup do work when we modify and not generate new geometry.\n\n\n--\n\n(that's the overlay if someone is not aware of its existence :p)\n\n\n- Open attached .blend file. (Note that the UV for \"Modified Edges\" is showing as expected)\n- Unmute `Join Geometry` node. (UV for \"Modified Edges\" no longer appears)", "Rebuilding subdivisions with multiresolution deletes vertex groups\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.0, 3.1.2\nWorked: version: 2.93.9\n\nRebuilding subdivisions with multiresolution deletes vertex groups. In 2.93LTS it preserves the vertex groups.\n\n[MultiresRebuildSubdivsYeetsUrVertGroups.blend](MultiresRebuildSubdivsYeetsUrVertGroups.blend)\n0. On version 2.93 parent object with automatic weights to generate vertex groups\n1. Apply multiresolution modifier\n2. Verify rig still works and vertex groups are still intact\n3. Add new multiresolution modifier\n4. Rebuild subdivisions in the multiresolution modifier\n5. Verify rig doesn't work anymore and vertex groups are gone (in Blender 2.93 rig still works)\n\n", "Poor performance for \"Remove duplicate vertices\" for some models\n**System Information** \nOperating system: Windows 10 (but happens on Linux too)\nGraphics card: NVIDIA GeForce GTX 970 (but happens w/ no gfx card too)\n\nBroken: 2.91.0 Beta of 2020-10-26 17:29, hash edf4378c442a (master)\nWorked: unknown\n\n\"Merge vertices\" becomes very slow if glTF object is imported with vertices already merged\n\n\n* Start blender, remove all default objects\n* Import the attached glTF with:\n * Merge Vertices: Turned on\n * Shading: `Smooth Shading`\n* Select Model Group > Mesh Group > Mesh_0\n* Enter Edit mode\n* right-click Merge Vertices > By Distance\n* repeat the above process, but leave Merge Vertices turned off during import\nor\n- Open attached .blend file\n- Go to edit mode on the object named `Mesh_0_slow`\n- right-click Merge Vertices > By Distance\n- Try the same with the object named `Mesh_0_fast`\n\nNote the first time taken: for me it's around 30 sec, which is quite slow\nNote the second time taken for `Merge Vertices > By Distance` is only a second or so\n\nI speculate that this could be because this particular glTF object is reusing some buffers (the 60 meshes are just transformed copies of Mesh_0), so the merge may be doing more work than necessary, but I haven't dug into it.\n\nIn my application, I'm looping over all meshes in the scene and removing duplicate verts, so in my case I'm spending the 30 sec per mesh 60 times for a total of 30 min of processing time! Of course I shouldn't need to do that with Merge Vertices turned on, but I have other imported objects and it's all scripted so it's hard to know which ones to merge vs. not.\n\n[merge_by_distance_bug.blend](merge_by_distance_bug.blend)\n[test-molecule-1.glb](test-molecule-1.glb)\n\n", "Geometry Nodes modifier input: Show More descriptive names in the dopesheet\nRight now animated geometry nodes modifier properties get an infamous label such as \"Input_2\". It should instead show the name that is shown in the UI, just like the other (non-geometry nodes) modifier properties.\n\n{[F13048799](image.png), size=full}\n\n[modifier.blend](modifier.blend)\n\nA proposed solution by @HooglyBoogly + @JulianEisel is to introduce \"labels\" to the UI data of ID Custom Properties.\n\n*This doesn't touch the Python API.*", "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", "Copy Datablock button has different behaviour in Graph as Modifier\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.3.0\n\nThe button to duplicate the current node tree works as such in the node graph but on the modifier, it creates a new node tree.\nIn other areas of Blender (eg materials) the same button duplicates current datablock.\n\n\n\nAdd a new geometry node tree\nAdd a node\nClick the Copy Node group button in graph and see graph is duplicated\nClick the Copy Node group button in modifier and see graph is replaced\n[2022-09-15 11-14-53.mp4](2022-09-15_11-14-53.mp4)\n", "Merging vertices keeps vertex groups from one vertex, discards others\n[merge_vgroup_bug.webm](merge_vgroup_bug.webm)\nBroken: 2.80, d3870471edd7, 2019-02-12\n\nWhen merging vertices (either directly or using \"Remove Doubles\"), vertex groups are only inherited from one vertex and the others are discarded (effectively at random). Expected behavior is that all vertex groups assigned to the vertices to be merged will be inherited.\n\nDoing the same but with materials instead of vertex groups results in expected behavior (all materials assigned to the vertices to be merged are inherited), so I guess there's a case to be made for consistency.\n\n - Open the attached .blend file\n - Note that the vertex group \"top_group\" contains all top vertices and \"bottom_group\" contains all bottom vertices\n - Select all vertices\n - Remove Doubles\n # Note that the merged vertices only inherited vertex groups from either \"top_group\" or \"bottom_group\", instead of both\n[merge_vgroup_bug.blend](merge_vgroup_bug.blend)", "Delete Geometry node face mode behaves unexpectedly when used after Join Geometry\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.2.1\nWorked: N/A (problem exists on 3.1.2)\n\n\nNot sure if this is by design, but I find that the following behaviour unexpected:\n\n- By itself, a Mesh Line output connected to Delete Geometry + Geometry Proximity node using Face mode won't delete anything.\n- However, when such a Mesh Line is joined with a Grid primitive, then Delete Geometry + Geometry Proximity in Face mode will cause all of Mesh Line to be deleted, regardless of distances.\n\n\n\n\n\n\n\n\n- Download the blend and observe Mesh Line is preserved.\n- Unmute Grid node link to Join Geometry, and observe Mesh Line is now gone.\n\n[line-deletion.blend](line-deletion.blend)\n", "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", "Texture nodes CPU evaluation design\nFor #54656, we need CPU evaluation of a subset of shader nodes that form the texture nodes.\n\nPrototype under development in [D15160](D15160).\n\n**Overview**\n\nThe plan is to make this a subset of geometry nodes that can be evaluated using the same mechanisms. Texture nodes can be though of as a geometry nodes field, and when evaluated in the context of geometry nodes they are.\n\nHowever they can also be evaluated outside of a geometry node tree. In particular, they can be evaluated on:\n* Geometry domains vertex, edge, face, corner, for geometry nodes and baking of textures to attributes. Possibly also sculpting and vertex color painting.\n* Geometry surface, for image texture baking and painting.\n* 2D or 3D space not attached to any geometry. For brushes, 2D image painting, physics effectors.\n\nTo support the last two cases in the geometry nodes infrastructure (but not the geometry node evaluation itself), a new field context named `TextureFieldContext` is added. This represents a continuous texture space, that may be mapped to a geometry surface or not. It has one domain, `ATTR_DOMAIN_TEXTURE`.\n\n**Compilation and Execution**\n\nThe texture nodes compilaton and evaluation mechanism uses much of the same infrastructure as geometry nodes, but is separate to be usable in different contexts. It's meant to be possible to execute texture nodes efficiently many times, for example paint brushes are multi-threaded and each thread may execute the nodes multiple times. This is unlike geometry nodes where multiple threads may cooperate to execute nodes once.\n\nThe current compilation mechanism is as follows:\n* Multi-function nodes are compiled into a `MFProcedure`, which bundles multiple multi-functions into one for execution. Geometry nodes do not currently use this mechanism, but it is designed for this type of evaluation. This is rather inefficient currently for individual points, but should get more efficient when evaluated in big batches.\n* Remaining nodes are input nodes, and execute `geometry_node_execute` as part of compilation, which then outputs fields and values. The execution context for these nodes is limited, unlike geometry nodes there is no geometry, object or depsgraph.\n* For evaluation, fields are converted into `GVArray` using the provided geometry.\n\nWe could consider making geometry available and to the compilation and caching the compilation per geometry, though it's not clear there will be nodes that need this. Alternatively we may cache just the `GVArray` per geometry.\n\n**Fields**\n\nInput nodes return fields, which are then turned into `GVArray` for evaluation. For the texture domain, this is a virtual array that interpolates attributes. There may be some possibility here to share code with data transfer field nodes, or nodes that distribute points and curves on surfaces and inherit attributes.\n\nShader nodes need additional fields that are not currently in geometry nodes:\n* Generated / Rest Position / Orco\n* Normal, taking into account face smooth flag and custom normals\n* UV maps (planned to become available as float2 attributes)\n* Active render UV map and color layer\n* Tangent\n* Pointiness (Cavity)\n* Random Per Island\n\nIt's unclear to me what the best way to specify these as fields is, if we should add additional builtin atttribute names or `GeometryFieldInput`. Some of these like Pointiness would also make sense to cache as attributes, and make available to external renderers.\n\nOne constraint is that it must be efficient to evaluate only a small subset of the domain. For many field inputs and operations this works, but there are some that will compute a data array for the entire domain. This can be enforced by just not making such nodes available as texture nodes, or caching the data array on the geometry.\n\nFor sculpt and paint modes, there is a question if and how we can make all these attributes available. The challenge is that it has different mesh data structures (bmesh and multires grids), which are not supported by geometry nodes. Additionally, recomputing for example tangents and pointiness as the geometry changes during a brush stroke would be inefficient, especially if it's for the entire mesh and not just the edited subset.\n\n**Batched Processing**\n\nFields and multi-functions are not optimized for evaluating one point at a time, there is too much overhead. That means we want to process texture evaluations in batches, and all (non-legacy) code that uses textures should be refactored.\n\nFor geometry nodes, modifiers and 2D brushes this is most likely straightforward. However for 3D brushes, particles and effectors it will be more complicated.\n\nThere is currently a mechanism to single evaluations possible while code is being converted. However this is rather inefficient, with quite a bit of overhead in `MFProcedure` execution. It may be possible to do some optimizations there for legacy code that we may not be able to easily convert to batches.\n\n**Node Graph Transforms**\n\nTo support sockets like Image datablocks, and to automatically insert Texture Coordinate or UV Map nodes for textures coordinate sockets, we need to transform the node graph. The texture node layering will also need to do significant node graph transformations. In order to share code with Cycles and other external engines, it may be best to do this as part of node tree localization.\n\n**Relation to Other Node Systems**\n\nThere are many node evaluation systems in Blender, and the question is if we can somehow share this implementation with anything else. I don't think the CPU evaluation can be directly shared, but will make the old texture nodes evaluation obsolete at least. The GPU implementation can probably be largely shared with shader nodes, and that implementation could be refactored to use DerivedNodeTree for consistency and to simplify that code." ]

[ "Delete geometry node performance regression writing to multiple vertex groups in 3.1\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.1.0\nWorked: 3.0.1 and older\n\nCaused by f5e5a0987a\n\nUsing a combination of Delete Geometry node along side the Armature modifier makes the node run slower and slower the more vertex groups armature is using. The difference is an immense drop from 144fps back to 8fps using the same .blend file in 3.0.1 and 3.1\n\n[Delete Geometry + Armature 3.0.1.blend](Delete_Geometry___Armature_3.0.1.blend)\n\n[Delete Geometry + Armature 3.1.blend](Delete_Geometry___Armature_3.1.blend)\n\n**.blend file overview**\n\n\nI would argue that this bug is a high priority issue and makes a lot of the character animation workflows impossible to use in 3.1 .\nDelete Geometry Node has been a replacement for the Mask Modifier ever since Geometry Nodes was introduced, it is a crucial part of a lot workflows. \n\n\n\n**More information if needed :**\n\n- Order of the modifiers does not matter\n- Vertex groups on the mesh have to be used by the armature for it to take an affect, however the vertex group used to delete the geometry is not being used by the Armature\n- The issue seems to be that the Node is now checking every single vertex group instead of the single attribute given to it\n- The more vertex groups used by the armature the worse the performance\n\n\n\n" ]

[ "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "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", "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)", "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", "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", "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", "Incorrect combined texture baking with subsurface material\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nBaking result is different from what I have seen in render and has strange artifacts.\n\n\nOpen attached file and run combined baking with default settings.\n[test_bake_2_79.blend](test_bake_2_79.blend)", "Blender crashes: OpenVDB math::Transform::read throws exception. \nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.2\n\nBlender keeps crashing.\n\nI have a project were I created an animation of modified arrays. Everytime I play it it crashes\n\nCrash report: P1536\n\ncrashed thread: \n```\n\tThread 35 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff726c733a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff72783e60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff7264e8a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff7264e817 abort + 135\n4 libc++abi.dylib \t0x00007fff6f8ae458 abort_message + 231\n5 libc++abi.dylib \t0x00007fff6f89f8bf demangling_terminate_handler() + 262\n6 libobjc.A.dylib \t0x00007fff713da5b1 _objc_terminate() + 104\n7 libc++abi.dylib \t0x00007fff6f8ad887 std::__terminate(void (*)()) + 8\n8 libc++abi.dylib \t0x00007fff6f8b01a2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27\n9 libc++abi.dylib \t0x00007fff6f8b0169 __cxa_throw + 113\n10 org.blenderfoundation.blender \t0x0000000110291c61 openvdb::v7_0::math::Transform::read(std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 4801\n11 org.blenderfoundation.blender \t0x000000011026082b openvdb::v7_0::io::Archive::readGrid(std::__1::shared_ptr<openvdb::v7_0::GridBase>, openvdb::v7_0::io::GridDescriptor const&, std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 1787\n12 org.blenderfoundation.blender \t0x0000000110286589 openvdb::v7_0::io::File::Impl::unarchive(openvdb::v7_0::io::File const&, std::__1::shared_ptr<openvdb::v7_0::GridBase>&, openvdb::v7_0::io::GridDescriptor const&, openvdb::v7_0::io::File::Impl::NoBBox) + 57\n13 org.blenderfoundation.blender \t0x0000000110282c91 openvdb::v7_0::io::File::readGridByName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, openvdb::v7_0::math::BBox<openvdb::v7_0::math::Vec3<double> > const&) + 465\n14 org.blenderfoundation.blender \t0x0000000110282ab6 openvdb::v7_0::io::File::readGrid(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 54\n15 org.blenderfoundation.blender \t0x00000001128a2cc9 MANTA::updateGridFromVDB(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 361\n16 org.blenderfoundation.blender \t0x0000000112890985 MANTA::updateGridFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 869\n17 org.blenderfoundation.blender \t0x0000000112890cee MANTA::updateNoiseStructures(FluidModifierData*, int) + 558\n18 org.blenderfoundation.blender \t0x000000011287e2b5 manta_update_noise_structures + 21\n19 org.blenderfoundation.blender \t0x000000010df34cd0 BKE_fluid_modifier_processDomain + 3168\n20 org.blenderfoundation.blender \t0x000000010df316ce BKE_fluid_modifier_do + 142\n21 org.blenderfoundation.blender \t0x000000010e3ad4f6 applyModifier + 54\n22 org.blenderfoundation.blender \t0x000000010dea5b0a mesh_calc_modifiers + 2778\n23 org.blenderfoundation.blender \t0x000000010dea4d6b mesh_build_data + 123\n24 org.blenderfoundation.blender \t0x000000010dea4035 makeDerivedMesh + 133\n25 org.blenderfoundation.blender \t0x000000010dfe1281 BKE_object_handle_data_update + 1089\n26 org.blenderfoundation.blender \t0x000000010dfe1704 BKE_object_eval_uber_data + 52\n27 org.blenderfoundation.blender \t0x000000010e9f36ba DEG::(anonymous namespace)::deg_task_run_func(TaskPool*, void*, int) + 138\n28 org.blenderfoundation.blender \t0x00000001142cadbc task_scheduler_thread_run(void*) + 364\n29 libsystem_pthread.dylib \t0x00007fff72784109 _pthread_start + 148\n30 libsystem_pthread.dylib \t0x00007fff7277fb8b thread_start + 15\n```\n", "Crash when rendering (Apple M2)\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: version: 3.6.2\n\n[Rendering with GPU (metal) works fine without fire simulation, with fire simulation the render crashes, while rendering in the viewport is no problem.]\n\n\n", "Crash clicking on Material Preview\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nSometime, clicking on Material Preview button (Eevee) Blender 2.92 crashes without a reason.\nSee file and log attached\nThank you\n[Rocks_Pack.crash.txt](Rocks_Pack.crash.txt)\n\n-\n\n[Rocks_Pack.blend](Rocks_Pack.blend)", "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", "Multiresolution - Crash when Linear Subdivision level is above 1\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.91.0\nWorked: Never? (2.90 and 2.92 dailies seem to crash on this one as well)\nWhen using multiresolution modifier on this part of my model and using linear subdivision level above 1, Blender crashes.\nThis does not happen with other subdivision methods, as shown in video.\nI've also tried to make this mesh manifold, but Blender crashed either way.\n\n\n1. Open attached Blend file\n2. Add multiresolution modifier to a mesh\n3. Press on \"linear\" button twice\n\n[Crash_SampleFile.blend](Crash_SampleFile.blend)\n\n[MultiresCrash0001-2375.mp4](MultiresCrash0001-2375.mp4)\n\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "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", "Cycles: principled BSDF volume scattering\nThe idea is to add another \"subsurface scattering\" method, to specify the inside of the object.\n\nThe parameters for SSS are designed to specify an average color at the surface, and then absorption and scattering parameters are derived from that. Such parameters make less sense for thinner volumes, like absorption and scattering inside glass, ice or ocean water. Further, SSS uses a diffuse BSDF at the entry point which is not suitable for such effects.\n\nThe parameters for this would be similar to principled volume, likely:\n* Density\n* Scattering Color\n* Absorption Color\n* Anisotropy\n\nThe scattering implementation could be shared with random walk, for efficient handling of many scattering events. However this does mean no handling of internal objects, so potentially there could be an option for both, or some automatic optimization to handle both cases efficiently.\n\nFor handling refraction the entry point, in general this is tricky as there will be volume caustics with a glossy refraction. A possibility would be to make the surface transparent and ignore any refraction, or to use some blurring through filter glossy." ]

[ "Crash when subsurface pass is enabled in Eevee\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Radeon(TM) RX 460 Graphics ATI Technologies Inc. 4.5.13506 Core Profile Context 23.20.15017.3010\n\n\nBroken: version: 2.80 (sub 53)\n\n\nCrash when subsurface pass is enabled in Eevee.\n\n1. Enable Subsurface Scattering in Render tab\n2. Enable Subsurface Direct or Subsurface Color in View Layer tab\n3. Set Subsurface socket in Principled BSDF to 1\n4. Hit F12\n\n", "Cursed blend file crashes on F12 render unless SSS is turned off.\nOperating system: Windows 10, v1607\nGraphics card: GTX 1070\n\nBroken: 2.80, 009dbc2bc9fb\n\n**How I got this file**\nI was working on a project (which I cannot share the original files of) and at some point it started crashing on F12 render. The last thing I remember doing before this started happening was baking cloth physics and binding Mesh Deform and Surface Deform modifiers.\n\nIn an attempt to troubleshoot the error, I deleted every object except my character's eyeballs, which used SSS. Disabling SSS in the project prevents the crash. Appending the eyes into a fresh file also would not crash. I then just deleted the eyes as well and spawned a cube and a brand new material on it with SSS, and it still crashes. If I re-create said cube with said material in a fresh file, it works fine. So it's just this file that something is up with. I thought it could be useful to share.\n\nUnsure if relevant, but I began working on this project in 2.80, d986b04bd302. That version had an issue with Mesh Deform binding, so I switched to the latest version yesterday, and it only started crashing today.\n\n- Download blend\n- Press F12\n- Hope it's not just my PC that it happens on.\n[sss_crash.blend](sss_crash.blend)" ]

[ "Viewport Tools Settings panel appears after reload\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\n- 2.92 - 2.8x\nWorked: Never\n\nI don't know, if this is intended. I unchecked Header in a viewport and everything disappeared. But after reloading file, \"Tools Settings\" panel was still present, even though Header is unchecked.\n\n- Uncheck Header\n- Save file and close Blender\n- Open Blender and load that file \n\nThe header itself is still hidden, but the tool settings are back.\nTo hide the tool settings again, the header must be re-enabled and disabled.", "CMD terminal stays open after opening blender\nOperating system: Windows-10-10.0.25247-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\n\nI'm not sure why it';s happening but it's not happening for 3.3 version\n\n\n\n", "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)", "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 ", "Hiding Armature in Outliner while in Pose Mode, leaves viewport without ability to select or exit the Pose Mode.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0\n\nWhen Armature is hidden via Outliner in Pose Mode, the selection, active object, and the Mode remains on that armature, not allowing to select anything anymore. Same happens with Meshes and Edit Mode, but one is still able to exit the Edit Mode. I assume it's likely that one either shouldn't be able to hide the object one is in Edit/Pose mode with, or the Mode probably should be exited upon hiding it's object. Or, at least, switching the Mode off shouldn't be disabled if the object is considered still active/selected.\n\n[armature.blend](armature.blend)\n - Select Bone,\n - Press Disable in Viewports for Armature object in Outliner,\n - > Can't select other objects in viewport now, or exit the pose mode.", "Cache folder determination of `thumbs.c#get_thumb_dir` should be migrated to use `BKE_appdir_folder_caches`\nthumbs.c uses its own logic to find out where to place the thumbnails. \nThis should be done by the central logic that was created for the asset indexing.\nBKE_appdir_folder_caches()\n\nThis task should be updated with the thumbsnails storages standards", "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", "In some Constraints, only one Custom Space selection box appears when there should be multiple \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 3.1.2\nWorked: 2.83 (When the custom space option hasn't been added)\n\nIn some constraints such as copy location/rotation, there are two \"space\" selection boxes. However, only one custom space target selection box appears when both of them are selected as \"custom space\".\n\n1. Open Blender, add a copy location constraint to the default cube\n2. Set both the \"target\" and the \"owner\" to \"custom space\"\nOnly one custom space target selection box appears, where there should be two.\n\n\n", "Touch on Gizmos can return invalid cursor coordinates\nversion: 2.80 (sub 39), branch: blender2.7, commit date: 2018-12-23 21:42, hash: e5e885d0ecb9, type: Release\nbuild date: 23/12/2018, 17:14\nplatform: Windows\n\n\nWhen using a pen, as in a Microsoft Surface or similar device, using the camera Gizmos and moving the pen outside the 3D viewport seems to return null/invalid coordinates, and it breaks. They can ONLY be used inside the 3D viewport. It's an absolute deal breaker for touch screen users (Surface, Wacom, etc)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nAny default .blender. On a touch device using a stylus pen, click on a Gizmo (axis, zoom, or drag) and move the pen outside the 3D viewport.\n\n\nWhen using a regular mouse the cursor gets hidden and it works as intended.", "Support for binding additional keys\nThere are keys which aren't included in Blender's keymap.\n\nHowever it doesn't make sense for us to include all possible keys, as there are many which don't make sense (system-wake, calculator, eject, brightness-up, ... [see a full list ](keycodes)).\n\nRecently we have added some keys which can be useful.\n\n- Application key (used for context menu)\n- F20-24 (for users to have keyboards with additional F-Keys).\n\nThis task is to keep track of other possible additions to the keymap.\n\nOpen Topics:\n\n- How to handle non US keymaps?\n - We could support binding raw keycodes *(so we don't need to expand our fixed table of keys to include keys from all keyboard layouts).*\n - We could support keyboard layouts, which all include the US keymap, extending on it for keys it doesn't include. This could be selected as a preference.", "Blender 3.5: Cursor warping usable on windows remote desktop (RDP)\nOperating system: Windows 10 21H1 19043.2130\nGraphics card: GTX1650 4GB\n\nBroken: 3.5.0 Alpha, hash: 508fd044b44a\nWorked: 3.4.1, hash: ef9ca44dee7f\n\nI'm using Blender through Windows Remote Desktop (RDP) for quite a long time.\nNow in the new alpha 3.5 the Blender UI acts weird and non controllable anymore when using mouse middle click to pan viewport or left clicking into number fields to drag values up or down.\n\nAt this point for me Version 3.5 alpha is not usable anymore through an RDP connection - which is quite important for me! - while at least in Blender Version 3.4.1 everything worked fine!\n\n- Open blender from a Windows computer on another Windows computer via remote session\n- use {key MMB} to pan viewport or {key LMB} into number fields to drag values up or down.\n\n\n", "Regression Tests: Run-Time Check Failure #3 - The variable 'ls' is being used without being initialized.\nOperating system: Windows 10 21H2 Build 19044.1645\nGraphics card: Nvidia GT 610\nRenderer: GeForce GT 610/PCIe/SSE2\nVersion: 4.5.0 NVIDIA 391.35\n\nBroken: (example: 3.20 Alpha, 180163c4e448, private branch without changes, 2022-04-14)\n\nBuilding RUN_TESTS in Visual Studio will fail on certain tests.\n\n\nTo check for yourself run the following commad from a cli in your build directory:\n\n```\nctest -R cycles_light_cpu -C debug --debug\n```\n\nA part of the tests will pass, but some will fail. An error window will appear, saying: \"Run-Time Check Failure #3 - The variable 'ls' is being used without being initialized.\"\n\nTo manually check out this failure, take a look at the debug output and check which .blend file is loaded and if the test fails.\n\nI choose following file to load into blender.\n```\n\\lib\\tests\\render\\light\\spot_light.blend\n```\nNext hit F12 to render this test file. \n\n**Location in source**\nThe bug is located in shade_volume.h Line 947. ls.P is passed as a parameter there\n\n**Setup**\nAll testing was done in the DEBUG-x64 target in VS.\nBug still exists in 7484f274dcdc\n", "Improve communication of auto-save behavior by adding dialog box to \"Load Factory Preferences/Settings\"\n*Adding this task based on a discussion about improving usability to auto-save preferences when loading factory settings.*\n\nCurrently when loading factory settings, the preferences don't auto-save, even though loading the factory settings enables the auto-save option.\n\nThe rationale here is that we want to allow users to temporarily load factory settings without it overwriting their own preferences.\n\nIn this case explicitly saving needs to be done to overwrite their preferences.\n\nThis task is not to re-open the design discussion, for some context on the topic see other discussions.\n\nFor reference, discussion on this topic:\n- [D4863](D4863) - Preferences UI patch for Save/Revert/Reset\n- [D5236](D5236) - Remove option for disabling the override when factory settings are loaded\n- #66675 - Tooltip urgently needed for Preferences editor button to avoid user data loss with factory-defaults.\n- 4a5e046c92 UI: remove button to enable auto-save after load factory preferences\n\n----\n\nBased on discussion with @JulienKaspar, @dr.sybren & @WilliamReynish - we agree the current logic isn't well communicated to the user,\nsince loading factory settings puts Blender in a state where auto-save is checked but ignored.\n\nThis could be mitigated using a dialog which lets the user know what happens when loading factory settings.\n\nSuggested text:\n\n> Loading factory preferences won't automatically save your preferences on exit.\n> To overwrite your current preferences you must manually save the preferences. \n\n\n\n", "Custom property in workspace \"Layout\" can not be added to driver\nOperating system: Linux-4.10.0-28-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Ivybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 17.0.7\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\n\n\n\nWhen adding custom property in any workspace can't use it in any drivers. It works with object's custom property world's custom property, but not in workspaces.\nI think it's a bug.\n\nThank's in advance.\n\n\n\n\n\n\n[workspace_custom_property_drivers.blend](workspace_custom_property_drivers.blend)", "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" ]

[ "Windows Store Blender 3.2 version config folder not in appdata\\roaming folder\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 512.96\n\nBroken: version: 3.2.0\n\n\nNo config folder for Blender downloaded from the windows store in c:\\users\\user\\appdata\\roaming\\blender\\blender foundation\\\n\n\n\nYet, the system console says it is reading it from that location.\n\nWhen I download a zip version of Blender 3.2 from blender.org and open it, it starts as if I don't have any configuration for 3.2\n\nTherefore, it seems that with the Windows Store version, even though the console is saying that the config folder is in the correct place above, it must be somewhere else.\n\n" ]

[ "Remove 'Use Nodes'\nWhen using Cycles and editing materials, the user is presented with a button called Use Nodes. This is confusing and adds an extra step before being able to set up materials.\n\nIt might be nicer to simply have the material use nodes always. Materials without nodes doesn't even really make sense when using Cycles as they are central to material editing and creation.\n\n", "Meshes with the remesh modifier disappear when they are edited at the same time\n**System Information** :\nOperating system :Windows10, CPU:3950X\nDisplayCard: RTX4000\n\n **Blender version**: \nBlender:2.92\n\nWhen editing multiple objects in edit mode, if you edit more than one at the same time, some modifiers (such as remesh) cause the meshes to disappear.\n[2021-04-13 07-02-23.mp4](2021-04-13_07-02-23.mp4)\n\n- Open attached file\n- In edit mode select the face of an object\n- Scale (modifier updates correctly)\n- Deselect all and select the face of the other object\n- Scale (modifier updates correctly)\n- Select both faces\n- Scale (Meshes disappear)\n\n[UNTD_SIMPLIFIED.blend](UNTD_SIMPLIFIED.blend)\n\n---\n**Original description:**\n\nI added a lot of modifiers to these two objects.\n\nSelect one. Edit mode scale is fine. \n\nSelect two edit modes scale will disappear\n\nTest file : \n[UNTD.blend](UNTD.blend)", "Loop deselect doesn't work in 3 button emulation mode\nOperating system: Windows 7\nGraphics card: irrelevant\n\nBroken: 2.80, 9a8b6d51c12, 2018-12-11 01:35, Branch: blender2.8\n\nWith three button emulation and left click select on in user preferences, no methods for deselecting edge loops work.\n", "Can't undo the keyframe change in edit mode\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.15\n\nBroken: version: 3.1.2\n\nWhile in edit mode, when you hit Undo in the graph editor after moving a keyframe, the graph doesn't change.\n\n- Animate anything using a couple of keyframes.\n- Change to edit mode in viewport\n- Switch timeline to the graph editor (not necessary, you can keep timeline as it is)\n- Select a keyframe and move it\n# Hit undo\n\nResult: The graph editor stays the same\n\nExpected: The move you just made in the graph editor should be the only thing being undone!\n\nTest file with first four steps included\n[#97700.blend](T97700.blend)", "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", "Exiting 'Start Editing Stached Action' mode with tab or selecting 'Stop Tweaking Strip Action' results in the channel mute button having no effect\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5600M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.22\n\nBroken: version: 2.93.5\n\n[Edit_Stashed Action_NLA_Bug.blend](Edit_Stashed_Action_NLA_Bug.blend)\nIf you either choose 'Start Editing Stashed action' or press Shift + tab, then you enter edit mode, but if you press tab or select 'Stop tweaking Strip action' it seems like you've returned to the NLA, but the strip mute button has no effect. Moving the strip behaves as expected. Going back into stash edit mode and exiting via the menu 'Stop editing stashed action' or Shift + Tab will get back to the NLA with the mute button behaving correctly\n\n\n\nOpen the attached blendfile, note that the NLA strip is muted and has no effect. Either right click on the NLA strip and select 'Start Editing Stashed action'. Press tab or right click on the strip and select 'Stop tweaking Strip action'. See that now the strip is active even though the channel is muted. \n\n\n", "Modifiers added in edit mode are undone out of order if you go back to object mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 13)\nWorked: Never (2.8+)\n\nModifiers added in edit mode are undone out of order if you go back to object mode and then start undoing.\n\nAffects both old and new undo system. There's often mentions of edit<->object transitions being problematic but just in passing; I think this is a long standing issue. Just wanted to note it down as I test out the undo systems.\n\nHoping the new undo system can account for this now.\n\n- Default scene\n- Go to edit mode on the default cube\n- Add any modifier (bevel, subdivision, etc.)\n- Add any loop cut 1\n- Add another loop cut 2\n\n- Go to object mode\n- Undo --> Modifier is removed first (out of order)\n- Undo --> Loop cut 2 is removed\n- Undo --> Loop cut 1 is removed\n\n\n", "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", "Redo panel disappears during edits in Tweak tool\nOperating system: Win10 x64\nGraphics card: Nvidia 1070\n\n**Blender Version** \nblender-2.80.0-git.26d5a3625ed-windows64\n\nThe info panel for move disappears in edit mode if tweak mode is in action. This does not seem to happen if one uses \"g\" for grab instead.\n\n\n- Enable left click select, optionally select all toggles\n\n- In your space bar menu turn the select mode (W) on\n\n- Create a mesh and move into edit mode \n\n- Start grab and drag of verts and watch the move info panel at the left bottom\n\n- Now try the same thing with selecting a vertex then press \"g\" to move.\n\n", "Video Editing: Undo kills Rebuilding Proxy when it wasn't the last command\nOperating system: Windows 10\nGraphics card: GTX 960\n\nBroken: 2.92\n\nVideo Editing: Undo kills Rebuilding Proxy when it wasn't the last command:\n1. add the video file to the timeline\n2. click Rebuild Proxy and Timecode Indices\n3. rebuilding proxy process should start\n4. split the strip\n5. click Undo\n6. the rebuilding proxy process breaks", "Make saving of `quit.blend` on exit optional\n### Description & Scope of Problem\n\nEvery time Blender quits, when it has something on the undo stack, it will write the current \"undo file\" to `${TEMPDIR}/quit.blend` ([manual](open_save.html#last-session)).\n\nSaving `quit.blend` can take a while when the file is large. While the file is being written, Blender's UI is gray and unresponsive.\n\nThe problem is not pressing, as usually it takes considerably longer to load the files in the first place. I've asked some artists at the Blender Studio and they didn't really consider the delay when quitting Blender a practical issue. Still, it gets somewhat in the way of quickly testing things with various production blend files, so it could be seen as an issue for developers more than for artists.\n\n### Possible Solutions & Impact\n\n**Simplest solution:**\n\nAs a solution we could introduce a user preference \"Save Recovery File\" that is enabled by default. Disabling this option would:\n- Avoid writing `quit.blend`.\n- Remove the \"File ‣ Recover ‣ Last Session\" menu item.\n- Remove the \"Recover Last Session\" button from the splash screen.\n\n**Alternative solution:**\n\nThe \"Recover Last Session\" operator does not poll the filesystem from its poll function. This means that the operator is available even when the file `${TEMPDIR}/quit.blend` does not exist. Changing this, such that the operator is disabled when `quit.blend` does not exists, means that the above solution would not have to remove the recovery operators when \"Save Recovery File\" is disabled. The operators would auto-detect whether a recovery file is available at all.\n\nThe upside of this solution is that it makes the \"Recover Last Session\" operator appear more reliable, as it refuses to work when it knows it cannot do its job. This would be an improvement regardless of the \"Save Recovery File\" status.\n\nThe downside is that an old `quit.blend` might be lingering around after \"Save Recovery File\" has been disabled. This means that it could appear as if you could still recover, but it would load an older file. This could be avoided by removing `quit.blend` when disabling \"Save Recovery File\", but I'm not a big fan of Blender explicitly removing files that are meant to recover from human error.\n\n### Discussion Topics\n\nThis task is meant to discuss the following:\n\n- Do we want to make it possible to quit without writing `quit.blend` at all?\n- If so, which of the solutions is preferred? Or is there another way to deal with this that's even better?\n- Do we want this as a general option, or something that's enabled only when \"Developer Extras\" are enabled?\n", "Crash when multiple materials are assigned to a mesh\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.1 Release Candidate\nWorked: unknown (I haven't opened the .blend file in versions older than 3.2. It is broken in 3.2)\n\nWhen two materials are assigned to the mesh, random faces disappear and reappear when switching between Object and Edit modes. After switching back and forth several times, Blender crashes. In some instances it took significantly more switches from Edit mode to Object mode and back before Blender crashed. In some of these instances, Blender appeared to create new faces with one or more vertices at the object's origin.\n\nWhen transforming any vertex, edge, or face, Blender quickly generates new faces with at least one vertex at the object origin and crashed shortly thereafter.\n\nI posted a 30-second video of the issue (including two crashes) here: strange_face_artifacts_causing_crashes/\n\nThankfully, I have not reproduced this issue in any other .blend file.\n\n1) Open the attached file, \"Crash - random faces.blend\" and you will see the mesh has a number of holes in it.\n2) Press tab and the missing faces will reappear but other faces will disappear. Pressing tab additional times eventually results in Blender crashing.\n3) Select any vertex, edge, or face and transform the selected element using G, S, or R and new faces will appear. Blender will quickly crash.\n4) Reducing the number of material slots to one appears to fix the problem (all faces are visible as normal) but it reappears as soon as a material is assigned to the second slot.\n\nThank you very much for your time.\n\n[Crash - random face orientation.blend](Crash_-_random_face_orientation.blend)\n", "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)", "paint.sample_color operator options no longer accessible by default due to undo flag removal\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.2.0\nWorked: 3.1.2\n\nThe undo flag for `paint.sample_color` was removed in rB511a08585d2934b38e7d3de447752686b5f0e15b, this means that the 'redo toolbar panel' no longer pops up after sampling color with the default keybinding of 'S'. Previously, users could change the default settings through the 'redo toolbar panel', without it, I don't think the \"Sample Merged\" and \"Add to Palette\" options are accessible to users by default any more.\n\nI'm not sure if this should be considered a bug or an API change, but for the latter, I think there should at least be some other way to access these options through the UI or default keybindings without requiring users to create new keybindings with these options specifically enabled/disabled.\n\n'redo toolbar panel': \n\n1. Enter Texture Paint mode\n2. Hit `S` (default keybinding of `paint.sample_color`)\n3. No 'redo toolbar panel' appears to allow for changing operator options\n\n", "Undo, Sculpt mode options reverts back with wrong order and simultaneously\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 2.93.1\n\n\n\nTo reproduce:\nWith sphere\n1. Go to sculpt mode\n2. Make a stroke\n3. Change an option (remesh/options)\n4. Make another stroke\n5. Press Undo or {key Ctrl+Z} twice \n\nExpected: one stroke and one option change will be rolled back.\nActually: option wasn`t reverted, but both strokes do.\n\n6. change few options\n7. Press Undo: you will go back to object mode and all options from the Remesh panel will be reverted.\n\n[2021-07-29_11-11-37.mp4](2021-07-29_11-11-37.mp4)\n\n\n" ]

[ "Undo material color and mode change at the same time.\nBroken: 3.0\n\nUndo two steps at the same time. Material color and mode change in one undo.\n\ntab to edit mode\nadd a new material slot\nclick (+ new) for new material\nchange the material base color\nchange to face select mode\nselect a face \nassign the second material slot to that face\nchange viewport to material preview\nchange to object mode \nundo\nboth the base color and mode will change at the same undo", "While on edit mode, the undo system does not work on nodes\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.1.0\n\nif you enter edit mode in an object, if you edit the nodes(I tested in both geometry and shader) and then try to undo, the undo does nothing even tho its reported that you went back in the undo history\n\n\nfrom startup file:\n- add a geometry node to an object\n- add a node to this object\n- move the node you just added and ctrl+z in object mode\n- go to edit mode, move the node and try undo without leaving the edit mode.\n[2022-03-15 12-14-59.mp4](2022-03-15_12-14-59.mp4)", "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", "Undo in Curve Edit Mode doesn't work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0\n\nWhen working with Curve Objects in Edit Mode, modifications in Object Data Properties are not undoable\n\nAdd a curve object, enter Edit Mode, change \"Resolution Preview U\" in Object Data Properties tab, press Ctrl+Z ->nothing happens\nIt looks that some parameters are undoable ex: switching 2D/3D or the ones under \"Active Spline\"\n[Based on the default startup]\n\n" ]

[ "New geometry nodes viewer overlay makes mesh edit mode overlays invisible\nOperating system: Linux-5.19.10-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.4.0 Alpha, current master\n\n\n| {[F13588717](image.png) size=full} | {[F13588720](image.png) size=full} |\n| -- | -- |\n", "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)", "Some particles do not appear in the render when the 'Vector' pass is enabled\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: 3.2.2 - 3.3.1\nWorked: 2.79\n\nParticles in Render don't match particles in viewport. Some particles do not appear. When they move very fast the issue is more visible.\nIt happens when we enable the pass `Vector`\n\n- Open attached file or:\n - In the default scene (with the Cube), add a Plane\n - Add a ParticleSettings toe the plane\n - In {nav Particle Properties > Render} set `Render As` to `Object`\n - For the `Instance Object` choose the Cube\n - In {nav Particle Properties > Field Weights} set `Gravity` to `0.0`\n - Optionally bake for cache\n - Set `Render Engine` to `Cycles`\n - In {nav View Layer Properties > Passes > Data} enable `Vector`\n - Move Cube out of camera view\n- Choose a frame in the middle and render\nNote that the particles closest to the plane disappear\n\n[particles displaced.blend](particles_displaced.blend)\n\n", "Random Per Island does not work on instances\nOperating system: Linux-6.0.5-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\n\nMaterials which use the \"Random Per Island\" geometry attribute do not work correctly on instances generated via geometry nodes.\nI am not sure if this is actually a bug, because maybe the attribute is only intended to work for meshes. But I think as an artist you would expect it to work?\n\nIn the following video I have a cube with an array modifier applied to it. I then added a geometry nodes modifier after the array modifier which instances cubes on the array of cubes.\n[2022-10-29 13-56-24.mp4](2022-10-29_13-56-24.mp4)\n\n[random_per_island_instances.blend](random_per_island_instances.blend)\n\n", "Object properties In-front doesn't work in viewport shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nObject properties In-front doesn't work in viewport shading\nAll the other options works in Object properties/viewport display, except for In-front \n\n\n- Open attached file\n- Go to Viewport Shading\n[lookdev_in_front_bug.blend](lookdev_in_front_bug.blend)\n", "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", "Line Art doesn't exclude object's instanced by geo node\nOperating system: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.3.1\nBroken: version: 3.5.0 Alpha\n\nCollection Line Art includes instances that are distribute my geometry nodes, even if that object is not within the Line Art target collection.\n\n\n[Line_art_Geo_Nodes_instance_bug.blend](Line_art_Geo_Nodes_instance_bug.blend)\n**Exact steps for others to reproduce with example file**\n1. Open Attached File \n2. Observe Line Art is on objects outside target collection\n\n**Exact steps for others to reproduce the error from Startup**\n1. Distribute Objects from a collection with Geo-Nodes\n2. Create a second collection with a Line Art Target Object only\n3. Add Collection Line Art and target collection from step 2\n4. Line Art will be drawn on Geo-Nodes instanced objects\n\n\n\n", "Generated cordinates from instancer\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\nDocs says, that it should work, but do not give any example.\nGenerated from instancer gives -0.5 value on all instances and points.\nI expect to have correct vector field, the same as instancer have.\n\n{[F9500816](59614942.png) size = full}\n[from instancer.blend](from_instancer.blend)\n\n[2020-12-10_23-36-48.mp4](2020-12-10_23-36-48.mp4)", "Point Instance node doesn't instance meta objects.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\nBroken: version: 2.93.0 Alpha\n\nFor Geo Nodes, Point Instance node doesn't work (doesn't copy) meta objects (like metaball). \n\nI used a very basic setup. The original input and output nodes plus one point instance node. I selected the object to be a meatball. Nothing happens! I selected any other object (non-meta). The object is instanced. Geo nodes were added to the default cube. \n", "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. ", "Geometry Node: Sculpt mode doesn't cause update due to editing\n## SIMPLE REPORT:\n\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\nWorked: Never\n\n\nObjects with geometry nodes do not update if dependent on the object that is currently being sculpted.\n\n[2023-01-14 13-13-37.mp4](2023-01-14_13-13-37.mp4)\n\n\n1. Duplicete default cube.\n2. Add Geometry Node tree on copy, add `Object Info`, choose other one cube, connect geometry to group output.\n3. Select other one cube, go to sculpt mode, do anything.\nCube with geometry node does not according to sculpted one\n\n## USER REPORT:\n\nOperating system: Windows 10 Pro\nGraphics card: Geforece RTX 2080\n\nBroken: 3.4.1 Stable\nWorked: not sure\n\n\nGeometry nodes network is not updating when in sculpt mode. It's updating fine when in edit mode.\n\nI have nodes basically adding differences in point positions from one mesh to another -\n\n\n\n\n[sculpt_mode_update.blend](sculpt_mode_update.blend)\n\n\n\n\n\n- Create an object(=A) and add a geometry nodes modifier\n\n- Duplicate the object(=B), and use it's object info in the first objects geometry node\n\n- Connect object B geometry, position and ID into a sample index node, sampling a vector on a point\n\n- Subtract the vector coming from the sample index from object A's position\n\n- Connect the result to the offset\n\n- Try moving verts on object B in edit mode and see object A updating\n\n- Try moving verts on object B in sculpt mode. Object A is only updating when switching from sculpt mode back to object mode.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Disabling collection in the outliner does not entirely disable all the calculations connected with that collection\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\n\nBroken: version: 3.2.1\nWorked: 2.79\n\nIf you have a collection with some armature (*say \"Character\" collection*) and some other collection that has objects linked to that armature (say \"Character's Clothes\") and there are some heavy models there (*lots of modifiers, faces, etc.*), then the armature performance would be abysmal until you completely delete that collection from the Scene.\n\nBased on an attached .blend file.\n 1) Move any armature's bones with \"Sides\" collection **ENABLED**\n 2) Observe lag\n 3) **Disable**\"Sides\" collection\n 4) Move any armature's bones\n 5) Observe lag\n 6) **Delete Hierarchy** \"Sides\" collection\n 7) Move any armature's bones\n 8) There would be no lag\n\nWhich means that after you disable collection in the Outliner, the calculations that are connected to that collection's objects are not entirely disabled like it was with Layers in 2.79. So, if the objects in the second collection are really compute-intensive, the whole scene is going to lag.\n\nI have attached a blend file and a video of this happening.\n[lag_example.blend](lag_example.blend)\n[blender_vp_lag.mp4](blender_vp_lag.mp4)", "`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.", "Particle Instance from interpolated children works unexpected\nOperating system: win10 74bit\n\nBroken: 2.8, 2.79b\n\n\"Children\" option works good only with \"Along path\". Otherwise it just duplicates extra geometry where parent particles are located. \n\nOpen file and enable \"Children\" option, see how poly count is changed without visual appearance. Then check both \"Children\" and \"Along Path\" to see the difference.\n[Particle_instance_child.blend](Particle_instance_child.blend)", "Inconsistent Limitations of Instances in Geometry Nodes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nIt's not clear what operations can or can't be done to an instance, eg. Extrude and Scale Element, Dual Mesh, Triangulate etc all work fine but Set Position doesn't. \n\nSorry for the complex file but I wanted to leave in all the nodes I'd been through before realising that I was working an Instance still.\nThe Set Position node was the first one in that line that gave me any indication that I was still on an instance.\n\n[12 Marching Squares.blend](12_Marching_Squares.blend)\n" ]

[ "Overlay setting \"Fade Inactive Geometry\" does not work with instance collections.\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.91.0 Beta\n\nOverlay setting \"Fade Inactive Geometry\" does not work with instance collections. Instance Collections are allways 100% visible.\n\nMake a scene with an object and add an instance collection of an object. Go to editmode and actovate \"Fade Inactive Geometry\". The Instance collections does not fade.\n\n", "No fading for instanced objects, when I use edit or sculpt modes\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 3.0.0 Alpha\n\n\nInstannce collection with objects, go to sculpt mode for another object. \nAnd instanced collection will not be shaded. Same as duplivertices.\n\n\n\n[shade.blend](shade.blend)\n[2021-05-08_21-55-49.mp4](2021-05-08_21-55-49.mp4)\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!", " 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)", "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", "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", "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)", "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", "stack_overflow exception while rendering with viewport render on\nOperating system: win10\nGraphics card: 2070super\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 2.83.4, 2.91 6fe609d4c3\n\n\nwhen pressing f12 in render mode, blender crashes,\nwhen pressing render in solid mode, blender doesnt crash\n\n[blender_debug_output.txt](blender_debug_output.txt)\n```\nError : EXCEPTION_STACK_OVERFLOW\nAddress : 0x00007FFF42963FDB\nModule : C:\\Windows\\system32\\DriverStore\\FileRepository\\nv_dispsi.inf_amd64_6af46268c19e4980\\nvcuda64.dll\n```\n[2.blend](2.blend) \n1. switch to render mode\n2. press f12 & watch task manager.\n3. blender will close", "Shader not working on Mac blender 3.5 - works in Windows\nOperating system: macOS-13.3-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0\n\nI have been trying to install the Weight Paint Tools paid addon weight_paint_tools?layout=profile&recommended_by=library\n\nThis worked fine for years, up till 3.5, now it crashes upon activation. The developer has attempted to update it for metal, but it still wont work. He's sent me a simplified script that he says should work without errors.. but still errors out. See attached blend file.\n\nRun the script\n\n\nRun the script\n\n", "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.", "Debug information not generated upon crash.\nOperating system: Arch Linux 6.4.12-arch1-1\nGraphics card: AMD ATI Radeon 680M\n\nBroken: 3.6.2\nWorked: Could not determine (tried up to 3.5.1, which does not work without a full system downgrade)\n\nBlender crashes immediately upon launch.\n\nLaunching from the command line, I get this:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\nThe contents of /tmp/blender.crash.txt are this:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nPassing the --debug-all flag, I get no errors. I attached the output of this command as a text file.\n\nWhile Blender crashing on startup is not in and of itself an issue worthy of reporting, the lack of any debug information immediately makes the problem impossible to tackle independently. I have no idea what my next steps should be here.\n\nLaunch blender.\n\n", "Blender crashes when using bpy.ops.view3d.view_orbit with a custom context\nOperating system: Linux-5.15.11-arch2-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.42.0, 5.15.11-arch2-1, LLVM 13.0.0) AMD 4.6 (Core Profile) Mesa 21.3.2\n\nAlso tested on WIndows:\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14756 Core Profile Context 20.40.32 27.20.14032.8\n\nBroken (Linux): version: 3.0.0\nBroken (Windows): version: 3.0.0\nWorked: Never, the crash happens in 2.7 and 2.6 doesn't seem to support the override thing (I haven't tested subversions)\n\nBlender crashes when using `bpy.ops.view3d.view_orbit` with a custom context\n\nRun this in the Python console:\n```\narea = [n for n in bpy.context.screen.areas if n.type == \"VIEW_3D\"][0]\noverride = bpy.context.copy()\noverride['area'] = area\nbpy.ops.view3d.view_orbit(override, type='ORBITLEFT')\n```\n\n[blender.crash.txt](blender.crash.txt)", "Metal Backend causes UV editing to glitch out, crash Blender\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.5.1, 3.6.3, 4.0 alpha\n\nTrying to do UV editing with the Metal backend causes unexpected UI behavior. Islands will glitch out, disappear, randomly stretch and contort, or Blender will crash entirely. It makes Metal useless for work and requires a switch to OpenGL to have expected performance. This happens on my M1 Air, M1 Pro MacBook Pro, and M1 Max Mac Studio. They all had to be switched back to OpenGL.\n\n<video src=\"attachment\" title=\"error.mov\" controls></video>\n<video src=\"attachment\" title=\"Screen Recording 2023-09-09 at 5.50.49 PM.mov\" controls></video>\n\n- Open the included Blender file with Metal backend\n- Make sure the 3D viewport has either Material Preview or Rendered View enabled.\n- Start UV editing on the `Azumi` object (go to Object Mode > Select the Azumi object > go to UV Editing Workspace)\n- Zoom, pan, scale, rotate...\n\nIt'll happen eventually.\n\nEDIT: This issue seems to stem from having multiple UV Maps on the model somehow. If the additional UV Maps are removed, the issue stops occurring.\n\nEDIT 2: Further digging seems to show that it specifically has to do with the texture atlas expression swapping using the UV Map and Mapping Nodes in the \"Colors.001\" material. Clearing the field in the UV Map node also immediately resolves the issue.\n\nI've attached two screen recordings of some of the behavior, as well as the error log when Blender crashed, and the file I'm working with.\n\nEDIT 3: Uploaded a simple test file with just a cube using the same material setup as my character file. It exhibits the exact same behavior.", "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", "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?", "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)" ]

[ "Blender Crashes while adding materials \ntried to add materials it crashes\nadded all details needed please do the needfull\n\n\n\n\n\n\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)" ]

[ "Transform: Tilt values in curves are not transformed\n2.8, 2.81\n\nWhen mirroring curves, tilt values are not mirrored.\n\nIn edit mode, MIRROR(or SCALE -1) dose not change tilt values.\nSo I can not get mirrored result (bebel geometry).\n\n(In object mode, I can get mirrored 2 curves by MIRROR(or SCALE -1),\nBut JOIN the two curves results not mirrored tilt effect.)\n\nOpen:\n[mirrored_curve.blend](mirrored_curve.blend)\n* The file contains 2 splines. One is a scaled duplicate of the other.\n* Note that the tilt of the corresponding point remains the same on both splines.", "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", "Disable selection operators in sculpt mode\nA small task to improve keymap changes from #105298\n\nSelect operators can be used in sculpt mode, even though they have no effect:\n\n- `view3d.select_circle`\n- `view3d.select_box`\n- `view3d.select_lass`\n\nEspecially due to recent keymap cleanups, the circle select operator can be called with the shortcut `C`. These operators need to be disabled while in that mode to prevent this.\n\n", "API: Drawing artifact when drawing inside Gizmo and blend mode is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0 Release Candidate\n\nDrawing artifact when drawing inside Gizmo.draw and blend mode is enabled.\nLook at the line across each graphic/rectangle.\n\n\n[GizmoDrawingIssueBlendAlpha.blend](GizmoDrawingIssueBlendAlpha.blend)\n1. Open the provided .blend file.\n2. Run the script\n3. Look at the simple rectangle and the transparent line across the rectangle\n4. Now try again but remove both 'gpu.state.blend_set' lines\n5. Rectangle is ok\n\nNote: the same drawing code from a [draw callback ](bpy.types.Space.html?highlight=draw_handler#bpy.types.Space.draw_handler_add) works fine without artifact.\n", "Proposal: improve functionality of Randomise Transform\nI personally find the way Randomise Transform works to be a bit confusing. The problem goes for all modes (location, rotation, scale) but it is most noticeable when randomising scale.\n\nIf I understand it correctly, setting the number to 1.15 would set the boundaries for the randomisation to 0.85 - 1.15, which is not very clear in this UI. It gets worse when I set it to a number below 1 - is it still the maximum? What's the minimum then?\n\nI would like to propose the following design for this: work with actual, defined boundaries - minimum and maximum values.\n\n\n*Though it's not really a huge issue in the location and rotation modes, I would extend it there for consistency.*\n\nWhile not exactly easier on the eyes than the current UI, I feel this offers more control and predictability than using one number that the user has to imagine going in both directions of the axis. And when scaling, no-idea-where.", "Circle Select Tool improvements\n## Issue\n\nThe current problem with the Circle Select Tool is that it is very inconvenient to change the brush size. In the modal operator equivalent (Shortcut C) it's just about pressing + and - or using the scrollwheel but this is not an option for the Tool. Generally there are no shortcuts for Tools before they are initiated. If the settings need to be changed then this needs to happen in the Tool Settings in the header or sidebar.\nBut changing the radius via that slider in the settings is awkward and appears visually glitchy since it's intersecting with the UI itself.\n\n\n\n## Proposals\n\nSo how can this be fixed. Ideally the solution should be as straight forward as possible without reshuffling the keymap. But it is very important that this is a general solution that can also be used for other brush-like Tools in the future (like proposed retopology tools that also rely on a brush radius)\n\n**1. More integrated modal shortcuts**\n\nOnce a Tool is initiated (usually by click & dragging) it uses the modal operator. This means that when using the Circle Select Tool and click & dragging, the radius can be changed with the mouse wheel & the + and - keys. \nThe current issue with this is that the Gizmo drawing is conflicting with the Tool Radius and that any changes to the radius are not updated in the tool settings.\nKeeping these 2 more in sync would be one solution or at least a great added feature.\n\n\n\nIt should be updated to the way the annotate eraser tool works but with more accessible shortcuts for radius changes if the mouse wheel is not an option (pen users)\n\n**2. Include Brush Tools in more modes**\n\nAnother solution is to redesign the Circle Select Tool (and any tools, present or future, that work similarly) as a brush like in sculpt mode or the painting modes.\nThis means that when the Tool is active it does have a set of shortcuts that can change the tool settings before the tool is initiated.\n\n**Conflicts**\n\nAlmost all are already taken like the typical F for brush size changes. It's not clear what shortcut can be used. \nAlso any shortcut that would be available must then be exclusively used for those brush tools to avoid any conflicts. \n\n**Solutions**\n\n1. Find or make an available shortcut for brush tools radius. But this shortcut then needs to be left exclusive of those tools.\n2. Override needed shortcuts when brush tool is used (In this case F for the radius). This does introduce difficulties and extra tool switching in edit mode though. \n3. Reuse the shortcut C that is used for the Circle Select Tool to change the radius once the tool is active. This will be awkward and incompatible with future tools that will work similar though.\n\n## Open Topics\n\n- Can it be achieved to use both solutions to improve brush like tools?\n- Are there possibly other ways of solving the conflicts in proposal 2?\n- For proposal 1, what shortcuts could be better for adjusting the brush size? + & - are on the numpad and the brackets are too far to the right and on for example German keyboard layouts not very accessible.", "Spin Tool Todo\n\n## Spin/Lathe\n * - [x] {icon circle color=red} Should allow dragging to change amount \n * - [x] {icon circle color=yellow} We should add the new gizmo design\n * - [x] The gizmo should respect the Scene orientation\n * - [x] {icon circle color=yellow} Just like the transform gizmos, dragging anywhere performs a spin along the view (just like now), but dragging on the manipulator performs a spin on that axis \n * - [x] {icon circle color=yellow} Just like the transform gizmos, the manipulator should be visible immediately, not only *after* the initial spin operation.\n * - [ ] The gizmo should respect the Scene Pivot Point. Currently it's hardcoded to always use the 3D Cursor as a pivot. It may often be useful to spin around Active Element, for example. \n\nUpdated Gizmo design, here:\n\nWhen enabling the Spin tool, we present an option in the Tool Settings for the X, Y or Z axis.\n\n1: Before executing the Spin tool, the user is presented with a widget like so:\n\n\n\nThis looks like the Extrude widget, but is curved, and shows a dotted line to the 3D Cursor, to indicate the center point.\n\nWhen the user hovers over this line, we see the entire circle visualized, like so:\n\n\n\nAfter the initial spin step, the user is then able to adjust the result using the gizmo, like so:\n\n\n\n - The Angle can be adjusted with the large disk. \n - The axis can be adjusted with the rotation handles. \n - The center can be adjusted using the arrows\n - To start a new spin operation, the user can use the + button, consistent with the Extrude tool, or select a different element.", "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", "Spin / Screw Adjust Last Operation: using the slider after having reset the axis will constantly pop up `Invalid/unset axis` [hard to escape]\nWindows 10\nNvidia mx 150\n\nBlender 2.9\n\nBlender starts to loose control in some functions when i press make some values to \"Zero\".\n\n1. Make a plane. goto edit mode and select face.\n2. Press \"Alt+E\" and select \"Spin\" option.\n3. Goto Last action menu, hover over the axis X value and press \"Backspace\" to make all values to zero. Error popup `Invalid/unset axis` comes up (which is correct)\n3. note here that Backspace seems broken [or intentionally disabled in recent builds], so it might be neccessary to set axis to zero \"by hand\"\n4. Now try to change the spin \"Steps\" using the slider (arrow keys are OK) and it will \"hang\" (as in: Error popup will follow the mouse) and you will have to hit ESC multiple times or force close blender.\n\n[#81042.webm](T81042.webm)", "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", "Scaled Rigid Body causes issue (moving origin or mesh breaks collision, double transforms on negative scale)\nOperating system: Ubuntu 18.04 LTS\nGraphics card: Intel HD 4000\n\nBroken: 3.0\nBroken: 2.90.1\nWorked: I don't know if this works with any other version, I created the file using 2.90.1.\n\n\nSee the attached .blend file. This file contains two errors with Rigid body simulation. I'm filing both errors in one bug because these may be related (both happen in one example simulation).\n\nError 1: object origin distance from another object changes interaction between objects\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that \"Ball\" is attached to the chain.\n3. Stop the animation and jump to first frame.\n4. Select object \"Ball\" and from menu Object - set Origin - Origin to Center of Mass (Volume)\n5. Play the animation to verify that \"Ball\" is no longer attached to the chain.\n\nError 2: Rigid body type \"Active\" changes orientation of the object\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that chain is attached to the object \"Cube\".\n3. Stop the animation and jump to first frame.\n4. Change \"Cube\" Physics properties - Rigid body - Type: Active and Settings: Dynamic\n5. Play the animation and notice that Cube is now rotated 180 degress around the X axis. Obviously this results in chain no longer connected to the cube as expected and chain and Ball drop directly down during the animation.\n\nExample .blend file (cannot simplify more because Blender seems to be unstable with this file):\n[physics-test.blend](physics-test.blend)\n\n**Additional information**\nIt seems that I can work around Error 1 by selecting all items and applying \"Rotation & Scale\". I think this should not be required to get two objects to interact during simulation so I'm reporting the problematic file as-is. I cannot figure out the reason nor workaround for Error 2.\n\n$ apt policy blender\nblender:\n```\nInstalled: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nCandidate: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nVersion table:\n```\n *** 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0 500\n 500 ubuntu bionic/main amd64 Packages\n", "Asset drag & drop snapping: Limitations\nLimitations for the drag & drop snapping implemented in the `asset-browser-snap-dragging` branch.\n\n* - [x] The bounding box drawing uses bounding box based snapping, actually dropping the object uses the origin. (279f271a0a)\n* - [ ] No way to select an up-axis (e.g. for putting frames on a wall).\n* - [ ] No way to rotate the object while or after dragging.\n* - [ ] Rotation of the dragged object is not applied.\n* - [ ] Snapping uses rotation of the snapped to object.\n* - [ ] Snapping uses normals of the snapped to surface, which are often flipped. Should probably work in both positive and negative normal direction?\n* - [ ] Not implemented for collections yet.", "Automatic Weights not working if part of mesh has negative scale\nOperating system: Windows 10 Pro\nGraphics card: NVIDIA GTX 960\n\nBroken: 3.1.0\nWorked: Never (2.8+)\n\n\nWhen part of a character mesh is given a negative scale in Edit mode, parenting to an armature with Automatic Weights no longer seems to work correctly. Applying scales does not help either as the scaling is done in Edit mode.\n\nI realise there are other ways to mirror part of a mesh rather than negative scale, however myself and one of my students have now both lost hours to this issue before I finally found out what seemed to be causing it.\n\n**How to recreate the bug**\n1. Open the file \"Block Man Example.blend\".\n2. Select the Cube mesh.\n3. Go into Edit mode.\n4. Select an entire arm or leg (I used Select Linked).\n5. Set the scale to -1 on the x-axis. (S, X,-1).\n6. Return to Object mode.\n7. Select the Cube mesh, then holding shift, select the Armature as well.\n8. Press Ctrl+P to parent, choosing With Automatic Weights.\n9. Select the Armature and go into pose mode.\n10. Try rotating the bones around the arm or leg which had been scaled.\n11. You see the mesh does not follow the bone as you would expect.\n\nFile: [Block Man Example.blend](Block_Man_Example.blend)", "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", "Unnecessary Proportional editing in Sculpt Mode.\nOperating system: Windows-10-10.0.1709 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 and 2.82 (sub 1)\nWorked: (optional)\n\nthis is probably not a bug but more of a design since Sculpt mode now has regular transform tools.\n\nI accidentally found out that if you enable Proportional editing then going to Sculpt mode the Transform tools will show Proportional editing & it's hotkeys in the Status bar.\n\n * Enable Proportional editing in Object mode.\n * Enter Sculpt mode.\n * Use any tool of the Transform tools.\n" ]

[ "Transform gizmo: Scale handles and rotation handles overlap\nWhen using the Transform gizmo, sometimes the scale handles and rotation handles overlap. This happens often in the side view. The problem is that it makes it almost impossible to use the scale handles then. I think we should always evaluate the scale handle input first, because the rotation handle goes around the whole object anyway:\n\n\n\nThere are also cases where the rotation circles will be in front of the move-arrows. So we should apply this to both the scale and move handles. " ]

[ "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", "Looks like an eevee limitations with UV maps and attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\nWhen working with multiple UVs and attributes, eevee disables some normal/bump maps.\nThere is an error in the console:\n```\nGPU_material_compile: Attribute \"nor\" overlap one or more index from another attribute. Note that mat4 takes up 4 indices. While merging eevee_legacy_material_surface_frag_opaque\n```\nIn 3.4, the shader cannot compile at all (pink texture).\n\nThis is not documented anywhere and it is not clear to me how it works, because until I connect nodes with attributes in Base Color, all normals are displayed.\n\n1. Open .blend file.\n2. Turn on the eevee render.\n3. Look, all normals are displayed.\n4. Connect nodes with attributes to Base Color.\n5. One normal map is missing. An error appeared in the console.\n\n", "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", "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", "Blender 3.0.0 breaks compatibility of rigs with the previous version\nOperating system: Windows 11 Pro 21H2\nGraphics card: Nvidia RTX 3070\n\nBroken: 3.0.0\nWorked: 2.93.6\nBlender 3.0.0 breaks compatibility of rigs with the previous version.\n\n1. Open Agent 327 shot 10_03_B-agent_dodges animation file (10_03_B.anim.blend)\n2. Observe that the rigs are completely broken\n\n\n", "Geometry Node in World Shaderworkspace does not output the same coordinates in Eevee like in Cycles.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.0.0 Alpha\nWorked: None same in 2.83\n\nGeometry Node works differently for Cycles and Eevee in the World Shader Tab, The Coordinates are distorted with Eevee. Im not sure if this is as expected.\n\n1 Goto Shading Workspace\n2 Enable Viewport Shading and enable World Background\n3 Add Geometry Node.\n4 Connect either Position, Normal, True Normal or Incoming to Background Shader.\n5 Switch between Eevee and Cycles to see the difference.\n\nOn the other hand, the Normal output of the Texture Coordinate Node is exactly the same in both render engines.[Geometry Shader in World Bug.blend](Geometry_Shader_in_World_Bug.blend)", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "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)", "Geometry Node: Viewer output for instance domain ignore if value nearest to 0.01\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4, 3.5\n\nGeometry Node: Viewer output for instance domain ignore if value nearest to 0.01\n\nIf you explicitly specify the instance domain, then with a value nearest to 0.01, the viewer will ignore the value input\n\n[2022-11-11 23-41-29.mp4](2022-11-11_23-41-29.mp4)\n\n\n- Put some intance to Viewer\n- Connect Float Value to Viewer set to instance domain\n- Test various floats (0.01 and 0.3)\n\nOr in attached file switch between couple of Viewer nodes\n[gn_viewer_value.blend](gn_viewer_value.blend)", "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", "Extremely frequent crashing when using the compositor. Especially when using the glare node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I believe it was far more stable before the realtime compositor implementation. (Blender 3.3-ish)\n\nBlender crashes extremely frequently when using the compositor on my system, especially when the glare node is being used at all. Does not seem related to vram or system specs, and looking through logs has not come up with any errors - it just closes.\n\nAdjust compositor glare node values with the viewer enabled. It seems to crash within a minute of doing so, usually sooner.\n\n", "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", "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.", "Improvement ideas for using Driver Context Properties to access scene custom properties\nThe #105132 pull request introduces access to properties of the current scene and view layer via an implicit rather explicit reference.\n\nThe existing implementation is perfectly fine for built-in properties, but I have some additional ideas aimed at making it easier and more convenient to allow scene-global custom settings via custom properties.\n\nBasically, since the properties have to be added by the user, it would be convenient to support the case when it doesn't exist. It also may be nice to allow setting overrides at several different levels of abstraction.\n\nThus:\n\n* Allow an optional default value that would be returned by the variable if the referenced property doesn't exist, instead of failing with an error.\n\n* Allow fallback from Layer to Scene, and then World: one World can be used by multiple Scenes, which can have multiple Layers.\n\nSince this all only makes sense for *custom* properties, maybe it can be a new mode specifically aimed at them, e.g. some kind of \"Layer/Scene/World Custom Property\", which has options for the custom property name (without the `[\"...\"]` quoting), channel index (for vectors), and default value.\n\nThese are things missing for the new driver things to fully cover the features of the View Layer mode of the Attribute material node.", "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" ]

[ "WORL ENVIRNONMENT INFINITE FOCUS \n{[F13629455](BUG_WORLD_ENVIRONMENT.blend)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.2.2\n\n**The world environment seems to have a focus on inifte.**\n\n\n*Unable to reproduce it, nor to fix it\n\n\n" ]

[ "Regression Tests: Run-Time Check Failure #3 - The variable 'ls' is being used without being initialized.\nOperating system: Windows 10 21H2 Build 19044.1645\nGraphics card: Nvidia GT 610\nRenderer: GeForce GT 610/PCIe/SSE2\nVersion: 4.5.0 NVIDIA 391.35\n\nBroken: (example: 3.20 Alpha, 180163c4e448, private branch without changes, 2022-04-14)\n\nBuilding RUN_TESTS in Visual Studio will fail on certain tests.\n\n\nTo check for yourself run the following commad from a cli in your build directory:\n\n```\nctest -R cycles_light_cpu -C debug --debug\n```\n\nA part of the tests will pass, but some will fail. An error window will appear, saying: \"Run-Time Check Failure #3 - The variable 'ls' is being used without being initialized.\"\n\nTo manually check out this failure, take a look at the debug output and check which .blend file is loaded and if the test fails.\n\nI choose following file to load into blender.\n```\n\\lib\\tests\\render\\light\\spot_light.blend\n```\nNext hit F12 to render this test file. \n\n**Location in source**\nThe bug is located in shade_volume.h Line 947. ls.P is passed as a parameter there\n\n**Setup**\nAll testing was done in the DEBUG-x64 target in VS.\nBug still exists in 7484f274dcdc\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)", "Exact Boolean (Union & Self Intersections -- to remove inside geometry) bad performance/memory footprint\nOperating system: Linux-5.15.0-67-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.2.6\n\nBroken: version: 3.5.0 Beta\n\nI have a group of nodes that gets rid of internal geometry by creating a \"mold\" of an object.\n\nBut it crashes on some meshes and not on other meshes and the crash doesn't give any real information why.\n\nIs there a work around for this?\nNodes works with certain meshes and crashes with others.\n\nWorking mesh and blend file.\n\n**Left side shows internal / overlapping geometry and Right side is free of this after using node network.**\n\n\n\n[doesn't crash.blend](attachment)\n\n\nCashes when I **click the switch node to enable it** (**see red arrow**).\nCrashes in 3.4.1 and 3.5.\n\n\n\n\n\n[this one crashes.blend](attachment)\n\nCrash text files attached below\n\n\nIs there a work around for this?\n\n", "Guardedalloc test failure with ASan enabled builds.\nOperating system: macos 10.14\n\ne21f1136c2dc95ba78b871955e2679b74e42e223\n\n[guardedalloc.txt ASan test failure](guardedalloc.txt_ASan_test_failure)\n\nBuild blender with ASan.\nRunning `ctest -C Debug -R Overflow -VV` will show two test failures with the attached message.\n`LockFreeAllocatorTest.LockfreeIntegerOverflow` and `GuardedAllocatorTest.GuardedIntegerOverflow`\n\nA workaround is in [D9844](D9844).\nAnother implementation of the workaround is in [D9844](D9844)#255346\nAlso see comment by Sergey [D9844](D9844)#250637\nChange in tests is in [D10719](D10719).\n", "Regression: Sculpt mode Annotation tool cursor conflict\nOperating system: Win 10\n\nBroken: 2.91, 3.4\nWorked: 2.90\nCaused by b9e4696641\n\nThe Annotation tool in sculpt mode is not using it's proper cursor. It's using the regular sculpting cursor instead.\nWhen you start drawing, the original cursor shows up on top of the regular sculpting cursor. \nThe end result is two cursors displaying at the same time and the original one flickering sometimes...\n\nTry to use the Annotation tool in sculpt mode....\n\nHere 2.90 (working fine)\n\n\nHere 2.91 (broken)\n\n", "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.", "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. ", "How to handle difference in sinf/cosf for M1\nAs discovered in 104513 , it appears that the single-precision floating point trig functions are producing slightly different results on apple silicon CPUs (M1, M2) compared with x86_64 CPUs, for certain inputs.\ne.g.\n```\n sinf(0.8960554599761962890625) = 0.780868828296661376953125 <- output on x86_64\n sinf(0.8960554599761962890625) = 0.78086888790130615234375 <- output on Apple M1 and M2\n```\n\nThis is a design task to help understand this problem, track solutions and mitigations.\n\nSee for example, 0eba9e41bff97659bdb5e51ba814d3e5dd150b43\n\n", "Boolean modifier artifacts\nOperating system: macOS-12.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.54\n\nBroken: version: 3.3.0 Alpha\n\nDifference on Brush Boolean is error code and lot bug.\nSee youtube tell you.JaCQrMN0quk\n\n**Steps to reproduce**\n- Open .blend file\n- Move target object over the object which has boolean modifier on it\n\n[3D print baby tall chair belt.blend](3D_print_baby_tall_chair_belt.blend)\n", "Mesh Boolean and Bounding Box node joined together make lose the UVs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.5.0\n\nApparently, joining 2 branches of geometry node that contain a Mesh Boolean node and a Bounding Box node make the UV gone. On image attached, the cube on the left with the voronoid is the original cube and on the right it's the same cube with the Geometry node turned on. Maybe other node combination recreate this issue.\nWhen inspecting the branches independently the UV are still working but stop working when adding the Join Geometry.\n\n- Have an object with texture applied. \n- Have a geometry node modifier assigned.\n- The geometry node consists of a Mesh Boolean node joined with a Bounding box node. (I used a transformed node to move the bounding box away and see our object)\n\n", "Segfault when encountering exception with props dialog open.\nOperating system: Linux\nGraphics card: Intel\n\n\nBroken: 2.92, 2.93.0\n\n\nWhen an `Exception` is raised in the `.invoke()` method of an operator while a props dialog is open, Blender does a segfault:\n\n`Unhandled exception thrown: read access violation. op->type was nullptr.`\n```\n>\tblender.exe!ui_layout_operator_properties_only_booleans(const bContext * C, wmWindowManager * wm, wmOperator * op, int layout_flags) Line 2517\tC\n\n \tblender.exe!uiTemplateOperatorPropertyButs(const bContext * C, uiLayout * layout, wmOperator * op, eButLabelAlign label_align, short flag) Line 2560\tC\n \tblender.exe!wm_block_dialog_create(bContext * C, ARegion * region, void * userData) Line 1391\tC\n \tblender.exe!ui_popup_block_refresh(bContext * C, uiPopupBlockHandle * handle, ARegion * butregion, uiBut * but) Line 586\tC\n \tblender.exe!ui_block_region_refresh(const bContext * C, ARegion * region) Line 399\tC\n \tblender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 754\tC\n \tblender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 867\tC\n \tblender.exe!wm_draw_update(bContext * C) Line 1066\tC\n \tblender.exe!WM_main(bContext * C) Line 654\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 523\tC\n```\n\n\n[#88929.blend](T88929.blend)\n\n- Open file\n- Run script", "Spreadout enum in pie menu gives strange result\nWin7x64GTX660m\n\nBroken: 2.73\nWorked: (optional)\n\nIf \"select similar\" operator is launched from a pie, items are arranged in a weird fashion (happens only in vertex and edge mode), overlapping one another and showing index numbers such as 167.\n\nFrom file, just click run in text editor (replaced example operator in text editor's pie menu template with *pie.operator_enum(\"mesh.select_similar\", \"type\")*).\n\n[overlappingPies.blend](overlappingPies.blend)", "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 on applying boolean modifier\nOperating system: Linux Fedora V35\nGraphics card: Nvidia 3070TI\n\nBlender 3.1.2 and Blender 3.2.0 both crash\n\nI created a mesh object, then used boolean modifier to create a hollow center. I applied the modifier. When I go into edit to clean it up, it crashes.\n\napply the boolean modifier to the mesh \"Bottom\" with object \"Plug\" in the included blend file using all defaults. Enter edit mode and see the mesh is badly corrupted.\n\n[part7.blend](part7.blend)\n[printReady1.blend](printReady1.blend)", "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" ]

[ "ctest: bmesh_boolean test fails on x86\nOperating system: Windows X86 + Linux X86\nGraphics card: N/A\n\nBroken: Latest Master 32 bit\nWorked: Latest Master 64 bit\n\n\nthe bmesh_boolean test fails on both windows and linux on 32 bit builds. \n\n**Additional information**\n\nThe reported memleak doesn't seem to trigger on the x64 builds. \n\n```\nBlender 2.80 (sub 72) (hash f18373a9ab1a built Sun 05/26/2019 12:09 AM)\nfound bundled python: D:\\a\\1\\build_windows_Full_x86_vc15_Release\\bin\\Release\\2.80\\python\nRead blend: D:/a/1/s/../lib/tests/modeling/bool_regression.blend\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nInfo: Deleted 1 object(s)\nError: Not freed memory blocks: 3, total unfreed memory 0.002487 MB\nD:/a/1/s/../lib/tests/modeling/bool_regression.blend\\run_tests:4: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses\nTraceback (most recent call last):\n File \"D:/a/1/s/../lib/tests/modeling/bool_regression.blend\\run_tests\", line 38, in <module>\nSystemExit: 1\nRun test: intersect_boolean(operation=\"UNION\") on Cubecube selecting F 0 1 2 3 4 5\nSuccess\nInfo: Deleted 1 object(s)\nRun test: intersect_boolean(operation=\"INTERSECT\") on Cubecube selecting F 0 1 2 3 4 5\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRun test: intersect_boolean(operation=\"DIFFERENCE\") on Cubecube selecting F 0 1 2 3 4 5\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRun test: intersect(separate_mode=\"CUT\") on Cubecube selecting F 0 1 2 3 4 5\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRun test: intersect(separate_mode=\"ALL\") on Cubecube selecting F 0 1 2 3 4 5\nFail Edge Mismatch\nInfo: Deleted 1 object(s)\nRun test: intersect(separate_mode=\"NONE\") on Cubecube selecting F 0 1 2 3 4 5\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRun test: intersect(mode=\"SELECT\" separate_mode=\"NONE\") on Cubecube selecting F 0 1 2 3 4 5 6 7 8 9 10 11\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRun test: intersect_boolean(operation=\"UNION\") on Cubecone selecting F 6 7 8 9 10\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRun test: intersect_boolean(operation=\"UNION\") on Cubecones selecting F 0 1 2 3 4 5\nFail Loop Vert Mismatch In Poly Test\nInfo: Deleted 1 object(s)\nRan 9 tests, 8 failed\nTests Failed\n```\n\nrun the bmesh_boolean test or load bool_regression.blend manually and click run script. " ]