Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "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", "Assert in debug for dyntopo sculpt\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: Today main.\n\nSee attached stack trace file.\n\nIn debug:\n1. Sculp mode.\n2. Enable Dyntopo option.\n3. Do something.\nSee the crash.\n\n", "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.", "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 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)", "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>", "Dicrepency between requested mesh data layer and eval mesh data layer\nWhile fixing #91838 it became apparent that the data layers requested by `mesh_cd_calc_used_gpu_layers` differs from the ones when creating the batches. Which lead in this case to a crash.\n\nThe fix was just a workaround and fixing this would mean to have the same layers at request time. Or maybe, not assuming they will be available during batch creation.", "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", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "Crash when 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```", "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", "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 Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "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", "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)" ]

[ "I Cant Open Blender\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFA06A37B78\nModule : atig6pxx.dll\nThread : 00002e74\nSwitching to fully guarded memory allocator.\nBlender 2.90.1\nBuild: 2020-09-23 08:36:20 Windows Release\nargv- [x] = C:\\Program Files\\Blender Foundation\\Blender 2.90\\\\blender\nargv- [x] = --debug\nargv- [x] = --debug-cycles\nargv- [x] = --python-expr\nargv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\\Users\\Owner\\AppData\\Local\\Temp\\blender\\debug_logs\\blender_system_info.txt')\nread file \n```\nVersion 280 sub 39 date unknown hash unknown\n```\nWriting: C:\\Users\\Owner\\AppData\\Local\\Temp\\blender.crash.txt" ]

[ "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", "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)", "Discrepancy between CPU and GPU rendering/material behaviour\nOperating system: macOS 13\nGraphics card: AMD W6800X Duo MPX module\n\nBroken: 3.3.1 (latest full release)\n\nI bought some assets which render with weird artefacts with the GPU, but work fine with CPU.\n\nThe assets are made by Bproduction (Florian Benedetto) on Blender Market. They are trees and vegetation models, which can be used individually or with Scatter 5.3. Simply put: they render properly with the CPU (Mac Pro, 24-core Intel), but render with horrible artefacts using the dual GPU. This doesn't happen with any other assets or materials I have.\n\nThe images below show the issue. I believe it's something to do with the material setup, but in any case it should render properly under both systems. Maybe it's an issue with macOS drivers?\n\n\n\n", "Theme > Shader Editor, Sidebar > Alpha value does not work\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A3000 12GB Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.1\n\nIn side of the Shader editor, if you want to change the color works correctly, but if you want to change the Alpha value, is not working.\n\nGo to Preferences > Themes > Node editor > Theme space > Region Background\n\n", "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", "Sorted Collection info Instance - update problem\nAs showed in the gif, there's an update problem in the spreadsheet, somehow the name get updated when an user change the name in the outliner, but the order stay the same, sending another update signal (refresh the collection picker or edit mode toggle) is needed to refresh the order. \n\n\n\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n", "State of hidden geometry not synced between edit mode and vertex paint/weight paint mode\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\nWhen vertex selection (or face selection) is used in either vertex paint or weightpaint mode the state of hidden geometry is not synchronized but overwritten by some specific state on this object. That makes it impossible to paint on using vertex selection. Joining the mesh into a new object did not fix the issue.\n[hidden_geo-2021-04-29_20.57.11.mp4](hidden_geo-2021-04-29_20.57.11.mp4)\n\nSee file:\n[hidden_geo.blend](hidden_geo.blend)\n\n", "Improve support for Rotate and Pinch trackpad gestures\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\nAt the moment, zooming with the Pinch gesture is too slow, requiring several full gestures to zoom in on details. When using the Rotate gesture, the rotation angle does not match the rotation of the fingers. Both gestures do not allow tiny changes with slow finger movements, due to rounding/conversions of values in the code.\n\nThe current code converts 'magnification' and 'rotation' values (float) to delta values (int). It would be more correct to use 'magnification' and 'rotation' values directly, without rounding when converting to delta.\n\nThere's an old macOS patch to start with: D8521", "\"Sync visible range\" does not affect other windows.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.2.0\nWorked: Unknown\n\nThe \"Sync Visible Range\" options in timeline does not affect the timeline on other windows.\n\n\n # Open the Blender 3.2.0\n\n # Load the default startup file. (File > De`f`aults > `L`oad Factory Settings)\n\n # Open a new window by going to \"Window > `N`ew Window\".\n\n # Change the \"Editor type\" in the new window to a timeline.\n\n # Enable the \"Sync visible Range\" options in the timeline of both Windows. (View > Sync Visible Range)\n\n # Move a timeline in the horizontal axis.\n\n**Actual Result**\nNotice that the timelines are not synchronized with each other.\n\n**Expected Result**\nThe timeline are synchronized in both Windows.\n\n**Notes**\n- This issue has not been tested on previous Blender version.\n- Timeline in the same windows sync as expected.\n- This issue occurs with any editor type in the \"animation\" category. I.E every timeline type.", "(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.", "Audio Scrubbing bug\nOperating system: Windows 10 64-bit\nGraphics card: RTX 2070 Super\n\nBroken: (2.90, 2.91, 2.92 Alpha, 3.0)\n\nEnabling \"Audio Scrubbing\" with \"AV-sync, Frame Dropping, and No Sync\" causes an issue with animations in the 3D Viewport and Timeline \n(AV-sync issue)\n1. Open a default Blender file.\n2. Create basic animation with any mesh, just something to show keyframe movement. Frames 1 - 250 should be enough for this procedure.\n3. In the timeline window, click \"Playback\" and switch \"Audio\" to \"AV-sync\" and enable \"Scrubbing\". A sound file is **not** needed for this step.\n4. Hit spacebar. The timeline cursor and animation should move as intended.\n5. Hit spacebar again to stop the timeline cursor and animation.\n6. Now the tricky part! Move the timeline cursor in any direction on the timeline, then **instantly** hit spacebar again. It may take a few tries but when it does work, the animation and the timeline cursor will not move. Yet, the \"FPS counter\" in the top left corner and the \"Anim Player\" icon will stay visible as if the animation is playing.\n7. Press spacebar to stop the \"ghost\" animation.\n\n(Frame Dropping and No Sync issue)\n1. Using the same file from above, add a sound clip in the \"Video Sequence\" editor.\n2. In the timeline window, click \"Playback\" and switch \"Audio\" to either \"Frame Dropping\" or \"No Sync\" and enable \"Scrubbing\". A sound file **is** needed for this step.\n3. Hit spacebar. The timeline cursor, animation, and sound should play as intended.\n4. Hit spacebar again to stop the timeline cursor and animation.\n5. Same as before, move the timeline cursor in any direction on the timeline, then **instantly** hit spacebar again. It may take a few tries but when it does work, the animation and timeline cursor will move but the sound will not play.\n6. Hit spacebar to stop the animation.\n\nWith both examples above, issues only popped up when \"Scrubbing\" was enabled. Disabling it did not produce the same results.\n\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 when delete linked object in scenes outliner\nOperating system: Windows 10\n\nBroken: 3.6, 3.5, 3.3 LTS, 2.93 LTS\nBroken: 2.91.0\nWorked: 2.90.1\n\nCaused by b0741e1dcbc5e4549e95745b1f1b501f8cd33add\n\nBlender is crash when delete linked object in scenes outliner\n\n1. Open start scene\n2. Create new scene \"Scene.001\"\n3. Click on Cube, Ctrl+L, Link objects to scene \"Scene.001\"\n4. In Outliner switch to \"Scenes\"\n5. Select \"Cube\" object in Scenes Outliner in \"Scene.001\"\n6. Move cursor to Outliner, press key \"X\" or \"Delete\"\n7. Blender is crashing\n\n", "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" ]

[ "Turning off Sync with Outliner does not to work\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Plus Graphics 645 Intel Inc. 4.1 INTEL-14.7.8\n\nBroken: version: 3.5.0 Alpha\n\nTurning off the 'Sync with Outliner' by setting it to 'Never' does not work:\n\nHere selected a Camera within the outliner:\n\n\nTurning the 'Sync with Outliner' to Never,\nThen selected the Cube within the Outliner and the Properties tab changed to Cube although the sync option is set to 'Never':\n\n\nWhat exactly this 'Sync with Outliner' is doing please?" ]

[ "Particles cache ignores animated lifetime\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0\nWorked: not sure if it worked after 2.80, maybe it worked in 2.79, but I'm not sure.\n\nIf you animate the lifetime and bake the particles everything in the same blender session everything works correctly, no matter if you bake them to disk or to memory.\nWhen you save the file, and open the file again the particle cache is broken and it's loading all the animation with the lifetime present in the first frame, no matter if it's a disk cache or a memory cache.\n\n\nBlende file: [test.blend](test.blend)\n\nSteps to reproduce:\n\nYou can watch the video I did or follow this steps:\n\nVideo:[particle_lifetime_an_bug.mp4](particle_lifetime_an_bug.mp4)\n\n1.- Open the attached blend file with Blender 2.90 release\n2.- Clean the cache if there is one, change some parameter like particle count (don't touch particle lifetime, it's animated)\n3.- Bake the animation, and you will see the correct result\n4.- create a new file\n5.- reload our test file\n6.- you will see how the cache is not behaving correctly and it's ignoring the animated lifetime\n\nIt's impossible to trustworthy bake particles without this working, because not even the disk cache is working\n\n\n", "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", "Particles not visible in render\nOperating system: Windows 10 Home 21H1 v. 19043.1466\nGraphics card: PowerColor RX 6600 XT OC\nCPU: AMD Ryzen 7 2700 Pro\n\nBroken: version: 3.0.0 LTS\nWorked: 2.93\n\n**Short description of the error**\nWhile rendering Spring demo with Blender 3.0, the grass is missing for some reason, only flowers is left\n\n**Exact steps to reproduce:**\n\n1. Download and run Blender 3.0 LTS: download/\n2. Download and open Spring demo (Blender 2.8): 5d2607ee6b3001d49bab798a\n3. Render as-is (this impacts both CPU and GPU rendering)\n\nPossibly this can be fixed by manipulating the original file's node system, I just want to know if this is a bug or just some hair/particle systems are no longer supported.\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", "Empty Hair object in sculpt mode, set select mode control points has wrong tooltip, doesn't show hotkey, adds new hotkey to wrong section\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\n\nThe new empty hair object has in sculpt mode two selection methods. Control Points and Curves. The Curves selection method displays the proper tooltip, including the hotkey.\n\nThe Control Point selection method shows a short tooltip called Use Sculpt Selection, doesn't display the existing hotkey for it. And when you try to add your own hotkey, then the new hotkey gets added in the global Windows section, as a context toggle instead of the proper operator.\n\n\n- Add a empty hair object to the default cube\n- Switch to sculpt mode\n- Watch the tooltip for the selection methods in the header\n- Add your own shortcut\n\n\n\n\n\n\n\n\n\n\n\n\n", "Hair: changing children related settings in objectmode dont show when switching to particle editmode\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83.7\nWorked: 2.79\n\nWhen I change additional options like Clumping, children not updates and their update stuck for edit mode for any try except 1st. \nDemonstration and details:\n[2020-10-15_01-46-01.mp4](2020-10-15_01-46-01.mp4)\n\n#69000 (Hair: changing children related settings not updating in particle editmode) is very much related", "Hair particles: 'Use modifier Stack' option removes all hair if particles have been added or removed in particle editmode\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)\n\nUse modifier stack checkbox deletes all the hair particles if they were created with the add hair brush and combed (not necessary), even if there are no modifiers before the particle system. This also happens if particles have been deleted (X) in particle editmode.\nAnd there is no way to get those hairs back. It can really destroy all your work on grooming.\nBy the way, that check box becomes inactive in 2.79 after grooming, but it's active for some reason.\n\nCreate a hair particle system.\nGo into particle edit mode.\nDelete all the hairs (by the way, you won't be able to do that until you comb it, may be a second bug).\nAdd some hairs via add hair brush (you can add hair without deleting on the previous step, the bug will occur anyway).\nGo back to object mode.\nCheck the use modifier stack checkbox.\nAll the hairs disappear!\n\nThe attached file has all that done except the very last step.\n\n[hair_use_modifier_stack_bug.blend](hair_use_modifier_stack_bug.blend)", "Having too much hair particles creates visual glitches\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: not really sure, but it may have been in blender for some time\n\nHair strips gets a really bad distortion once they reach a certain threshold of number, children and \"additional subdivisions\"\n\n\nUsing a ball with 2 subdivisions:\n\n| 1 | Furball with hair strips, 0 additional Subdivisions, 20000 particles and 80 interpolated children |  |\n| -- | -- | -- |\n| 2 | Furball with hair strips, 1 additional Subdivisions, 20000 particles and 80 interpolated children |  |\n| 3 | Furball with hair strips, 1 additional Subdivisions, 20000 particles and 60 interpolated children |  |\n| 4 | Furball with hair strips, 1 additional Subdivisions, 18000 particles and 60 interpolated children |  |\n| 5 | Furball with hair strands, 1 additional Subdivisions, 18000 particles and 60 interpolated children (hair gets scrambled where the glitch is happening) |  |\n| 6 | Furball with the exact same configuration as the first glitchless one, but with 3 Strand steps on Viewport Display instead of 2 |  |\n\nSo it seems like a mix of a lot of segments and a lot of particles create those glitches.\n\nThe file bellow contains the furball with the second configuration\n[furball.blend](furball.blend)\n", "Particles \"Numbered\" Incorrectly When Generation Time is Influenced by Texture\nSee attached - probably not relevant.\n\nBroken: 2.90 - see attached\n\nA keyed particle system sends particles from one particle system to another particle system. Normally the ordering is respected: the first-generated particle in one system gets sent to the first-generated particle in the second system, same for the second-generated particle, and so forth. This does not work though if a texture is used to generate a particle system. Various visual effects rely on the ordering being respected.\n\nCreate a plane mesh. Add a particle system to it, physics none, starting at time 1 and ending at time 10 with 10 particles. Add a blend texture so the particles are generated from one side to another. Add a second particle system on a second object. Now create a keyed particle system on the second object going from the first particle system to the second particle system, starting at time 15 and ending at time 24 with 10 particles. Display its particles in a distinct way (e.g., as red spheres). Step through the simulation frame by frame. Note the order that the particles appear on the plane mesh (first particle system). Then at frames 15, 16 and 17 note the order in which the keyed particles appear. They appear in a different order, whereas, if a texture is not used but the random seed is used, the keyed particles will be created in the same order that they were created in the first particle system regardless of the chosen random seed.\n\n[system-info.txt](system-info.txt)\n[Particle Numbering Bug.blend](Particle_Numbering_Bug.blend)", "Hair Curves: Invalid surface UV attachment\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060 Super\n\nBroken: 3.6.1\nWorked: N/A\n\nWhen using 'Interpolate Hair Curves' and 'Deform Curves on Surface', a small amount of curves can appear that have a \"Invalid surface UV attachment\", causing these curves to be unable to pose. They are left as floating particles which is a big issue for final renders with posed characters/objects. \nFurthermore, if the surface mesh is subdivided, more curves appear that do not pose with the mesh correctly and instead stay in rest position, however these are not considered an \"invalid surface UV attachment\", and thus cannot be removed with the 'hair attachment info' node's selection. There is no way to clear these \"valid\" invalid curves, they stay floating. \n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n- The provided file contains a posed mesh, moved slightly to the right, to show that one particle is left floating in the air.\n- Open the provided file, and render the image.\n\nThe problem should appear in the render as a single floating particle.\nNow check the geometry nodes setup and see that we have deleted the supposedly invalid curves, but one remains yet floating in the air far from the posed mesh.\n\n**Notes about the file**\n- A simple small surface, posed with an armature slightly to the right to show that some curves are not moving with the mesh correctly\n- A regular UV map made with smart uv pack, no overlaps, udims or islands outside the bounds.\n- The hair curves object was made by converting a hair particle system object to curves, and then used \"snap to nearest surface\" on hair sculpt mode to attach it to the surface\n- Which hairs are bugged depends on the 'intepolate hair curves' node's seed, for example on seed 2 this \"valid\" invalid curve appears, but not on some other seeds, and more appear on other seeds, completely randomly\n\n\n**Further notes after experimenting**\n- I suspect this is related to seams, as the problem seems to happen more often close to seams on the subdivided mesh, and better UV maps result in the bug happening less, but still happening. I added more seams to the simple mesh in hopes of the bug appearing more often. \n- Problem seems to happen more often if you use the boundary smooth option on the subdivision modifier; still happens if option is disabled but less.\n\n\n", "Hair particles roots moving when using curl kink type and simple children\nOperating system:Windows 10\nGraphics card: Nvidia RTX\n\nBroken: 3.0+\n\n\n\nWhen you use particle hair with simple children and you try to add the curl kink. The roots move with the amplitude. The only thing that keeps the roots in their place is to turn on the clumping. This doesn't happen when you use the interpolated children\n\nI don't know if it's a bug (most likely) but it is extremely frustrating\n\n Take a look at the video.I've added the file just in case\n \n Thanks\n\n", "Sequencer doesn't reflect source range in strip display correctly\nWindows 7\n\nBroken: 2.78 Release\n\nWhen the length of a render source is modified, the display in the strip display doesn't show it. The info 'Original frame range' is correct though.\n\n1. From the default scene, create a 'link object data' copy (although i guess the type doesn't matter)\n2. Go back to scene 'Scene' and set the end frame to 100\n3. Go to scene 'Scene.001', open sequence editor and add scene 'Scene'. It will now show a strip of 100 frames length.\n4. Go back to scene 'Scene' and change the end frame to 50\n5. Go back to scene 'Scene.001' \nThe Sequence Editor will still show a green bar 100 frames long, although the info in the properties panel tells the correct info: Original frame range 1-50 (50).\nMore importantly, you can drag the right grabber of the strip to the right and it will still paint 100 frames green and the rest grey/transparent, although the 100 frames don't have any meaning no more - it was just the length it was created with. You can also unlink the strip from the original scene and relink it again, it will still paint 100 frames green/valid.\n\nMaybe this is a bug, an oversight, maybe even intentional, I don't know. \nI don't think a .blend file is necessary in this case, but I will upload one, if desired. \n", "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.", "Hair object - design proposal\n\nIMPORTANT: Please note that this document is subject to change and will most likely not represent the final product of the new hair object in Blender\n\n---\n\n**Reference links**\n\nHair object - project description\n#68981 (New curves object type)\nHair object - node design\n#78515 (Hair object - Node types design)\n\n---\n## Hair object design\n\n**Guide curves**\nThis is a list of guides in the hair object. \"myGuides\" in image example. On the same hair object there can be multiple guide curves (\"eyebrows\", \"hair\", \"eyelashes\" etc). Guide curves are the curves are what the user grooms with the particle brush. The guide curves are sourced into the node tree graph via an input node.\n\n**Growth mesh**\nThis is the mesh that the guide curves are attached to.\n\n**Node tree**\nThis is a slot that referers to the node tree containing the nodes for creating and deforming the instanced hair curves. See design task #78515 (Hair object - Node types design) for more info regarding hair object node design\n\n**Hair simulation properties**\nI don’t currently have a strong opinion about where to place simulation related controls/UI. Perhaps this could be integrated somehow with particle nodes? See example of **simulation influence node** in #78515 (Hair object - Node types design). We should check with @JacquesLucke, since he is working on particle nodes and physics.\n\n|||\n| -- | -- |\n\n\n\n---\n## Alembic cache\n\nReading curves from alembic file as hair is supposed to be implemented as noted in the project description #68981 . I've been going back and forth regarding if I think alembic settings should be placed in the Hair object UI or in the Input node in the node network. I ended up with the conclusion that alembic settings should be placed in the hair object node networks **input node**.\n\n\n{[F8664085](image.png), height = 400}\n\n\n---\n**Notes on guide curves geometry data**\n\nThis is likely relatable to \nT76659\n\nDeformed instances\nImagine the blue poly strip on the image to the left is a deformed instance along a guide curve. The goal is to have it conform to the normal of the surface of the growth mesh (head geometry). This type of workflow is important for creating hair for real time rendering (e.g games) or feathers for offline rendering\n\n{[F8664030](image.png), height = 400}\n\n\n\nSometimes the sampled normals from the surface is too noisy (ear area) and needs to be averaged based on neighboring guide curve vertex normals. The smoothing should propably be done with an operator that is triggered by the user.\n\n{[F8664033](image.png), height = 400}\n\n\n**Normal per guide curve vertex**\nTransfer normal vector from growth mesh surface (CYAN) to guide curve vertices. This normal vector is not used for shading, but for aligning tilt/twist of instances to the growth mesh surface. This is very important for creating hair cards for real time graphics/games.\n\nGuide curve vertices that does not get a ray hit from growth mesh surface can inherit normal vector from the closest guide curve vertex that got a ray hit (YELLOW). We could also use this normal vector to displace the guide curves along the normal of the growth mesh surface with the deform node that is described in the Hair object node design T78515\n\nIf transferring normal vectors from the growth mesh is slow, perhaps it’s a good idea to transfer normals with an operator that is run by the user when desired. I guess it’s important to note that we would not want normal transfer to happen post simulation\n\nIt seems likely that this task is related to storing custom data on hair vertices: #76659 (Geometry Attributes Design)\n\n\n\n---\n**Direction per guide curve vertex**\nAnother important vector to use would be the direction of the guide curve. The direction of the last guide curve vertex will need to be inherited from its closest neighbor. The direction could be used by the tilt for deformed instances and also, the deform node that is described here: #78515 (Hair object - Node types design)\n\n\n\n\n---\n## Tangent per guide curve vertex\n\nThe cross product of the transferred surface normal and guide curve direction would result in a tangent. One potential problem is that the transferred surface normal and guide curve direction could sometimes be almost aligned (eg when hair is pointing along the surface normal). I’m not sure how big of a problem that could be. In case the tangent is zero, perhaps it should just get some arbitrary vector? Perhaps pointing along the X-axis?\n\nThe tangent can be used by the deform node that is described here: #78515 (Hair object - Node types design)\n\n\n\n---\n\n## Operators\n\nIMPORTANT: Nodes are to be developed first, so operators will not be a first priority\n\n**select random**\nexisting operator that is extremely useful while grooming. Selects random hair/points \n\n\n**transfer normals from growth mesh**\nTransfer growth mesh normals to guide curves. Vertecies that does not get a ray hit to growth mesh should inherit from closest guide curve vertex on same guide curve. Normals on guide curves can be useful for aligning instanced mesh. Very important for real time hair (eg hair cards) or feathers in off line rendering\n\n\n\n\n\n**smooth guide curve normals**\nsometimes growth mesh normals might be pointing in a lot of different directions (close to an ear for example). Then smoothing out normals can be useful. This is very simililair to **smooth curve tilt** for curves\n\n{[F8664672](image.png), height = 150}\n\n\n\n**create guide curves from curves**\nUseful for interoperability between other softwares. I think it would be useful to rearrange vertex order per guide curve so that vertex index 0 is closest to growth mesh surface. Only the two ends of the curve needs to be sampled to determine which is closer to the growth mesh. This would be very useful for converting hair using old hair system to the new hair system\n\n{[F8664681](image.png), height = 400}\n\n**resample guide curves**\nBased on current selection. Change number of vertices per guide curve. Vertices should always be equally spaced. When going from a low amount of vertices to a higher amount, it might be needed to \"change curvature\" in order to avoid linear interpolation between each new vertex. The current operator **Rekey** does a very good job, but doesn't solve issues where hair vertices that is not evenly spaced per hair.\n\n{[F8664686](image.png), height = 200}\n\n**Create curves from hair nodes**\nConvert current hair node setup to curves. Useful for interoperability with other softwares. Current operator hides in the **particle system modifier**\n\n{[F8664691](image.png), height= 300}}\n\n\n**Tilt normal**\nTilt normal on selected guide curve vertices. Very similair to tilt operator for curves\n\n{[F8664702](image.png), height= 200}\n\n**select by length**\nusable for deleting/pruning very small hairs. Small hairs can sometimes be accidentally too short by using the \"cut brush\"\n\n{[F8664699](image.png), height= 200}\n\n\n**smooth length**\nsmooth length on selected guide curves by sampling surrounding guide curves. This is useful for making sure there are no guide curves that are shorter or longer than they should be\n\n{[F8664705](image.png), height = 200}\n", "Hair particles: rekeying, cut tool, subdividing do not interpolate existing weights (breaking simulation)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 51)\nWorked: (optional)\nJust click once sometimes work right\n\n\nThis bug happen in both 2.79 and 2.8\nClick and drag the hair cut tool mess up the vertices position, especially after subdividing one or 2 segments of the hair. After the hair is messed up, it can't be fixed using rekey command.\nDragging the cut tool on a hair that is not subdivided also cause the problem, but not as severely, the vertices become unevenly positioned.\n\n\nCreate a hair system on the default cube, set the emission number to 1.\nGo to particle edit mode, subdivide one or 2 segments of the hair.\nUse the cut tool, click and drag from the tip of the hair.\nThe hair is now completely messed up.\n" ]

[ "Hair particles; The display percentage parameter breaks after a render is done\nOS - Windows 10 64 bit; CPU - Third-gen i7; GPU - ATI HD 7xxx; RAM - 24 gigs\n\nBroken: Blender hash 3b5dec4 (March 22 build from the buildbot).\nWorked: Unknown\n\nThe display percentage parameter (in the particle panels) breaks after rendering (so if you set it to show only 1 percent of the amount of particles in your hair particle system, exiting out of the render window will show 100 percent of the particles instead (which means a major slowdown for really large systems)). Clicking the parameter field again and clicking out of it will lower the visible count back to 1 percent.\n\nI will also note that this bug *only* affects hair particles (when you have the particle mode set to \"emitter\" the parameter works like it should at all times).\n\nOpen the .blend file and notice that only a few hair particles are visible, then render the scene. When the scene is done rendering, exit back to the 3D view and notice that every particle is visible despite what the display percentage suggests.\n\n**.blend**\n[HairParticlesBug.blend](HairParticlesBug.blend)\n\nThis has annoyed me for a while at least, I hope it can be fixed.\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", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\n\n", "Large soft shadows converge to an incorrect result in EEVEE viewport.\nOperating system: Linux-5.16.0-3-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.54\n\nBroken version: 3.2.0 Alpha\nBroken version: 3.1\nBroken version: 3.0\nBroken version: 2.93\nBroken version: 2.92\nBroken version: 2.91\nBroken version: 2.90\nBroken version: 2.83\nBroken version: 2.82\nBroken version: 2.81\nBroken version: 2.80\n\nWhen rendering large soft shadows in the EEVEE viewport, it converges to an incorrect result at high sample counts. Here are some examples:\n||||\n| -- | -- | -- |\n|EEVEE viewport - 512 samples (\"Mostly Normal\")|EEVEE viewport - 16,384 samples (\"Broken\")|EEVEE final render (`F12`) - 16,384 Samples (To be used for comparison)|\n\n1. Start with the default scene.\n2. Add a ground plane. ({nav Add > Plane} then scale it up and shift it below the cube)\n3. Select the default light and change it's radius to `2m`\n4. Render the scene in EEVEE to a high sample count in the viewport. This can be done by setting the `EEVEE viewport sample count` to something like 16,384 and letting it process. \n5. Render the same scene in EEVEE with a final render (`F12`) and the same sample count and compare it to the viewport result. Notice that it's very different.\n\nNote: Soft shadows is enabled by default in EEVEE in modern versions of Blender. But depending on your defaults, you might have to enable it. It's in {nav Render Properties Editor > Shadows > Soft Shadows}", "Remesh Voxel Size can be much to small by default (leading to crashes). 'Edit Voxel Size' operator can have wrong range\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\nProcessor: AMD Ryzen 7 3800x 8-Core Processor 3.90 GHz\n\nBroken: version: 2.90.0 Alpha\n(Also with Blender 2.83 BETA)\n\nSelecting the \"Remesh\" modifier, selected \"Voxel\", Voxel size below \"0.01m\" = PC Crash. Needed to restart the PC.\n\n1. Start Blender.\n2. Let the default Cube alive and add the \"Remesh\" modifier.\n3. Make the \"Voxel Size\" below \"0.01m\".\n4. Did it crashed?\n(Found out in my Blender Project, but I tested it then in a default Scene. Same thing happened.)\n\n(Why I set the Voxel Size below \"0.01m\"?\nIt happens accidentally, when I have it like \"0.42m\", but I hold my left click and slide it to the left, so I accidentally go below \"0.01m\".)\n\n{[F8619727](image.png), size = full}\n\nGood Luck!\n", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n", "Render animation cycles-x bug March 11, 2022\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nRender count from 1 to 1200 frames\n\n\nBlender 3.2.0 Alpha within Cycles-x\nPush the 'Command + F12\" and render animation cause bug between start to end (855 - 1200 frames)\n\nBlender and video file: [Blender 3-2-0 by Kent Davis March 11 2022.zip](Blender_3-2-0_by_Kent_Davis_March_11_2022.zip)\n\n\n\n\n\n\n\nRadeon Pro 575:\n\n```\nChipset Model:\tRadeon Pro 575\nType:\tGPU\nBus:\tPCIe\nPCIe Lane Width:\tx16\nVRAM (Total):\t4 GB\nVendor:\tAMD (0x1002)\nDevice ID:\t0x67df\nRevision ID:\t0x00c4\nROM Revision:\t113-D000AA-931\nVBIOS Version:\t113-D0001A1P-025\nEFI Driver Version:\t01.00.931\nMetal Family:\tSupported, Metal GPUFamily macOS 2\nDisplays:\n```\niMac:\n```\nDisplay Type:\tBuilt-In Retina LCD\nResolution:\tRetina 5K (5120 x 2880)\nFramebuffer Depth:\t30-Bit Color (ARGB2101010)\nMain Display:\tYes\nMirror:\tOff\nOnline:\tYes\nAutomatically Adjust Brightness:\tNo\nConnection Type:\tInternal\n```\n\n", "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", "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", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "Metal Viewport flickering on interaction\nOperating system: Mac OS Monterey, Version 12.6.2\nGraphics card: Apple M1 Max, Mac Book Pro 16 inch 64 GB, LG Ultra Fine Display as secondary monitor\n\nBroken: 3.5.1 release candidate\nWorked: 3.4 with Open GL does not have these issues\n\n\nWhen interacting in the viewport say moving a camera the viewport flickers. Also when adjusting shaders in a cycles window the viewport also flickers depending on the speed of the interaction. Evee viewport does not have this issue, but solid render does\n\nBased on supplied file Look through camera and split the viewport in two. Left side has cycles rendering turned on. Change the default renderer from Eevee to Cycles and change to GPU compute. Rotate camera with the empty and cycles view on left flickers. Next select cube and change the shader colour from pink to any other colour you like. Again viewport flickers like crazy.\n\n", "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)", "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", "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", "USD: Crash when loading the Intel Moore Lane demo asset (related to Color Attributes)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nBroken: version: 4.0.0 Alpha\nWorked: version: 4.0.0 Alpha\n\nCrashes during import of the Intel 4004 Moore Lane asset. Seemingly related to Color Attribute processing though the stack traces for the crash are not related.\n\n- Download the \"4004 Moore Lane v 1.1.0\" asset: 4004-moore-lane/\n- Attempt to import the `USD\\4004MooreLane_III_03_ASWF.usd` file with default settings --> observe crash\n- Attempt to import the same file but with the \"Color Attributes\" option unselected --> works\n\nOddly, the crashing stack occurs inside tbbmalloc and while seemingly dealing with mesh normals...\n```\n...\ntbbmalloc.dll!00007ffd7fa29f4e()\tUnknown\nblender.exe!MEM_lockfree_mallocN_aligned(unsigned __int64 len, unsigned __int64 alignment, const unsigned char * str) Line 310\tC\n[Inline Frame] blender.exe!blender::GuardedAllocator::allocate(unsigned __int64) Line 47\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::allocate(__int64) Line 425\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::get_buffer_for_size(__int64) Line 419\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::{ctor}(__int64) Line 122\tC++\nblender.exe!blender::bke::mesh::mesh_normals_loop_custom_set(blender::Span<blender::VecBase<float,3>> positions, blender::Span<blender::VecBase<int,2>> edges, const blender::offset_indices::OffsetIndices<int> faces, blender::Span<int> corner_verts, blender::Span<int> corner_edges, blender::Span<blender::VecBase<float,3>> vert_normals, blender::Span<blender::VecBase<float,3>> face_normals, const bool * sharp_faces, const bool use_vertices, blender::MutableSpan<blender::VecBase<float,3>> r_custom_loop_normals, blender::MutableSpan<bool> sharp_edges, blender::MutableSpan<blender::VecBase<short,2>> r_clnors_data) Line 1368\tC++\nblender.exe!blender::bke::mesh::mesh_set_custom_normals(Mesh * mesh, float[3] * r_custom_nors, const bool use_vertices) Line 1642\tC++\nblender.exe!blender::io::usd::USDMeshReader::process_normals_face_varying(Mesh * mesh) Line 797\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh_sample(blender::io::usd::ImportSettings * settings, Mesh * mesh, double motionSampleTime, bool new_mesh) Line 853\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh(Mesh * existing_mesh, USDMeshReadParams params, const char * * __formal) Line 1094\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_object_data(Main * bmain, double motionSampleTime) Line 249\tC++\nblender.exe!blender::io::usd::import_startjob(void * customdata, bool * stop, bool * do_update, float * progress) Line 288\tC++\n\n```\n\n", "Crash when moving to Shading workspace\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.17.5 355.10.05.45f01\n\n|Broken:|version: 2.83.0, commit date: 2020-06-03,|hash: `211b6c29f7`\n| -- | -- | -- |\n||version: 2.90, commit date: June 08,|hash: `9f7d84b656`\n|Worked:|version: 2.82|-\n\nWhen I open Blender, without changing anything in the default scene, if I move to the 'Shading' workspace my system freezes for a few seconds and crashes (it closes).\n\n- Default startup scene\n- click on 'Shading' workspace from the top bar\n" ]

[ "Crash at playing viewport shading animation after resizing 3D viewport editor\nmacOS 10.14, Intel HD 6000\n\nbroken; 8dc95f61f3dff4e5686c2a278bd44db714065b20\n[system-info.txt](system-info.txt)\n```\n- 0 in 0x162ad5cf8 ()\n- 1 in glDrawElementsInstancedBaseVertex_ACC_GL3Exec ()\n- 2 in glDrawElementsInstancedBaseVertex ()\n- 3 in blender::gpu::GLBatch::draw(int, int, int, int) at source/blender/gpu/opengl/gl_batch.cc:331\n- 4 in ::GPU_batch_draw_advanced(GPUBatch *, int, int, int, int) at source/blender/gpu/intern/gpu_batch.cc:282\n- 5 in draw_geometry_execute [inlined] at source/blender/draw/intern/draw_manager_exec.c:584\n- 6 in draw_call_single_do at source/blender/draw/intern/draw_manager_exec.c:831\n- 7 in draw_shgroup at source/blender/draw/intern/draw_manager_exec.c:1002\n- 8 in drw_draw_pass_ex at source/blender/draw/intern/draw_manager_exec.c:1113\n- 9 in DRW_draw_pass at source/blender/draw/intern/draw_manager_exec.c:1153\n- 10 in eevee_draw_scene at source/blender/draw/engines/eevee/eevee_engine.c:297\n- 11 in drw_engines_draw_scene at source/blender/draw/intern/draw_manager.c:1136\n- 12 in DRW_draw_render_loop_ex at source/blender/draw/intern/draw_manager.c:1637\n- 13 in DRW_draw_view at source/blender/draw/intern/draw_manager.c:1513\n- 14 in view3d_draw_view at source/blender/editors/space_view3d/view3d_draw.c:1565\n- 15 in view3d_main_region_draw at source/blender/editors/space_view3d/view3d_draw.c:1587\n- 16 in ED_region_do_draw at source/blender/editors/screen/area.c:558\n- 17 in wm_draw_window_offscreen at source/blender/windowmanager/intern/wm_draw.c:724\n- 18 in wm_draw_window at source/blender/windowmanager/intern/wm_draw.c:864\n- 19 in wm_draw_update at source/blender/windowmanager/intern/wm_draw.c:1065\n- 20 in WM_main at source/blender/windowmanager/intern/wm.c:653\n- 21 in main at source/creator/creator.c:519\n- 22 in start ()\n- 23 in start ()\n```\n\n\nSteps:\n\nOpen the given file\nChange viewport shading to material preview\nHit space bar to play animation for 5-10 frames. Pause it.\nResize the 3D viewport editor. I did by grabbing it from viewport - outliner divider.\nShift + left arrow to set current frame to 1\nhit space bar again\nCrash\n\n[particle_loop.blend](particle_loop.blend) from #86194 (Blender crashes with Noise Texture Node + Hair Particle System + Eevee)" ]

[ "Adjust modifier values when using \"Apply scale\"\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nWhen using \"Apply scale\", the modifier values are not adjusted if the object scale is not [1,1,1]. I would like to suggest that the operator \"Apply scale\" iterates through all modifiers of the selected objects and adjusts all values related to scale\n\nFor example\nBevel modifier - Amount\nDisplace - Strength\nData transfer - max distance, ray radius\nUV project - Scale X, Scale Y, \netc\n\n---\n\nCurrent behaviour\n{[F9849514](image.png), height = 700}\n\n---\n\nDesired behaviour\n{[F9849529](image.png), height = 700}\n\n---\n\nsuggested Operator mockup\n\n{[F9852183](image.png), height = 300}", "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)", "Regression: Blender 3.1 UI editor resize /border dragging performance\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\nWorked: 3.0.1\n\nCaused by {6738ecb64e8b6d0c1f5a79f1e63f468b4138de19}\n\nResizing UI editor panels in Blender 3.1 is significantly slower (framerate) and laggier than it was in 3.0. This is not related to the UV Editor performance regression as it happens even when there's no UV editor displayed in the given workspace. \n\nHere's a video of the issue, recorded at 60FPS and slowed down to 50% so the issue is more apparent: watch?v=a0wzLgkf6mk\n\n1. Open blender with a new empty file \n2. Drag the top of the Timeline Editor UI area around\nResult: The UI redraw framerate and input response (lag) are worse than in Blender 3.0\nExpected: The UI redraw framerate and input response (lag) are same or better than in Blender 3.0\n\n", "UI of Dropdown Menus : long list of EnumProperty Items (ColorSpace, Language, RemapUser ID) is partially hidden\nHi all !\nHere is a UI glitch in Dropdown Menus happening with long list of items.\n\nOriginally, this report was about the Language select list in the Preferences window but it actually occurs with every long Dropdown Menu lists.\nThis problem appears every time the Dropdown Menu is bigger than the window it is displayed inside.\n\n\nOperating system: Linux-5.3.0-2-amd64-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.4\nDisplay resolution : Full HD 1920x1080px\n\nBroken: version: 2.82 (sub 3)\n\nOpening the Preferences window (or any small sized Blender window) with Factory Settings defaults and changing the translation language (or choosing any other option in a long Dropdown Menu) displays a \"bigger than expected\" dialog that is partially hidden by the side of the window in a 1920x1080 pixels screen. The user has then to resize the Preferences window to fit, not a big problem per se but would be better if defaults were better.\nThat is because the list of supported languages is becoming quite big, specially the \"starting\" ones.\nBlender already has a few big list dialogs (e.g. the Editor Type or the Add Modifier) but those are generally dispayed correctly within the Blender window (almost full-screen).\nThat is not the case of the Preferences window.\n\nThree possibilities to solve this:\n- reordering the list so it stays into the Preferences window (e.g. \"In Progress\" below \"Complete\")\n- allowing the list to go beyond the borders of the Preferences window (do not know if technically feasible)\n- resize a bit the whole Preferences window to fit\n- redesign how Dropdown Menus behave, allowing for easy scrolling and search\n \n see illustrations below\n Thanks a lot ! =D\n\n\n\n\n\n", "Move the transform info away from the header, into the viewport.\nCurrently, when you transform any item in Blender, we take over the header while the transform is happening:\n\n\n\nThis makes for a vey flashing/blinking UI, where both the header and the viewport gizmo disappears and re-appears in a jarring way. \n\nInstead, the header and viewport gizmos should stay untouched, and the transform info can be moved to the viewport along the bottom.", "Sculpt Mode Simplify Tool\n * - [ ] {icon circle color=red} This tool should be renamed to 'Detail' because it can both add or remove detail. 'Simplify' is not a good name here\n * - [ ] {icon circle color=red} This tool only works when Dyntopo is enabled. Hide this tool when Dyntopo is disabled, otherwise we are displaying a tool that simply doesn't work.\n * - [ ] {icon circle color=yellow} The main tool setting for this tool is the Detail Size property in the Dyntopo popover. However, this is not easy to know, and cumbersome to change. We should add this property to the main tool settings in the top bar and Tool Settings Properties for this tool. ", "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.", "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", "Edit Dyntopo Detail Size: Add resolution value for visual feedback\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\n## Issue\n\nWhen using the `sculpt.dyntopo_detail_size_edit` on `R` while Dyntopo is set to 'Constant' or 'Manual' Detailing in the dyntopo settings, \nit can easily happen that the overlay doesn't show the wires that indicate the resolution.\nThis happens when the value is much higher than the current brush size, like when working on a very small object.\n\n\n\n## Suggestion\n\nIt would be give better feedback to the user that this is happening by displaying the 'Resolution' value\n- in the header\n- in the viewport itself, like with `object.voxel_size_edit` on the same shortcut.\n\nThe first solution would be the easiest and most consistent with other operators.\nThe second solution is also very welcome but would need the text to be placed outside of the brush cursor (Perhaps even dynamically placed depending on the availible viewport space).\n\n\n\n", "GPU Hair Rendering Bug - \"Glitter\" with particular Root to Tip sizes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIn a perfect storm of GPU rendering + Hair with Radius Root size smaller or equal to the Tip size, bright white \"cards\" appear at the tips of some hair strands. \n*Switching to CPU rendering, the anomalies go away.*\n\nAlso, making the Root size Large and the Tip size small reduces the cards, but they are still there.\n\n\n\n\n[Hair Render Bug.zip](Hair_Render_Bug.zip)\n\n\n\nOpen the attached file in Blender 2.80\nSwitch to the Camera view if not already there\nRender (should be set to *Cycles using GPU*)\nSwitch to *Cycles using CPU* rendering\nRender\n\nOptionally:\n\nSelect the hair object (eyebrows)\nGo to the particle tab\nUnder Hair Shape, change the Radius Root to, say, 0.45 and the Tip to 0.1\nRender using GPU - cards are still there but are much smaller.\n\n", "Image Editor in Mask mode: Toolbar broken \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nImage Editor in Mask mode: Toolbar broken \n\n- Open the Image Editor\n- Change the UI mode to Mask.\n- Add a new mask.\n- Toggle Toolbar(T).\nNotice that the Adjust Last Operation pop up i moving but no Toolbar becomes visible.\n{[F11089235](mask.gif),size=full}\n\n\n", "File Browser Window Size Change\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n//Small display: 1280 x 1024 pixels\nBig display: 3840 x 2160 pixels -- Windows UI scaling set to 150%//\n\nBroken: version: 2.83 (sub 15)\nWorked: Never.\n\nWhen opening window of File Browser from a low resolution Monitor (resolutions listed in System Information), it appears, on high resolution display, with smaller size than before. When you close and reopen it again this way it gets even smaller.\n\n1) On your secondary (small display) open shader editor.\n2) shift+a an \"Image Texture\"\n3) Click on \"open\" to open image file\n4) A File Browser pops up on the big display\n5) Close the File Browser\n6) Repeat step 3)\n7) The File Browser window appears again, but this time smaller.\n\n8) If you repeat steps 3) and 5), the File Browser window gets smaller and smaller.\n\n", "modifier offset slider step value being driven by the mouse looses one order of magnitude worth of accuracy when units are metric vs none\nwin 10\n2080ti\n\nBroken: 2.80+\n\nSince blender 2.8 has switched to real world units the modifier slider step(when driven by the mouse) value has lost one order of magnitude worth of accuracy, 0.001 instead of 0.0001 \nIt is possible to switch the unit system back to none to get the higher accuracy. \nThey should be consistent and both work to the higher level of accuracy as this level is essential when working on real work scale small items e.g. a watch\n\n\n- with scene unit type set to \"metric\" add a bevel modifier the standard cube\n- press shift while clicking and dragging the bevel modifier offset slider and notice how the smallest amount possible to move is 0.001 m\n- switch scene unit type to \"none\"\n- press shift and click drag the modifier offset slider and notice the smallest amount possible to move is 0.0001 m\n", "[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)", "Empty object property \"Size\" should be \"Radius\"\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.0\n\n- Mesh Cube is 1 meters wide when set its \"Size\" to 1 meters when creating\n- Empty Cube is 2 meters wide when set its \"Radius\" to 1 meter when creating.\n- However the property tab for the empty cube shows \"Size\" as 1 when it really supposed to mean \"Radius\".\n\n- Add a Mesh Cube with size 1 meter\n- Add an Empty Cube with size 1 meter\n- Compare the size. The size of Empty Cube is 2 Meters when set to 1 meter\n\n" ]

[ "Affect origins indicator gizmo is not affected by unit scale\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.2\nWorked: never\n\nThe gizmo used to indicate affect origin feature of transform tool is enabled does not change with different unit scale. This makes the gizmo invisibly tiny when using unit scale of 0.01, which is mandatory for Unreal Engine export capability, as described here: scene_scale.mp4\n\n1. In a new .blend file, set unit scale to 0.01\n2. Create a new cube. Newly created cube should be sized appropriately for new unit scale.\n3. Select new cube, Activate move tool, and activate \"Origins\" Affect Only option.\nResult: The gizmo to indicate Affect Only Origins feature is enabled is invisibly tiny and requires extreme zoom in:\n\nExpected: The Affect Only Origins indicator gizmo scale changes appropriately with different unit scales.\n" ]

[ "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", "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)", "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", "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", "Geometry-node object-info rotation&scale outputs values are False if scale is negative \nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0\n\nthe object info rotation & scale values are false if the scale of the sampled object is negative \nsee video, where i compare with simple drivers of the object transforms\n\n[dffdsdfdsfsfd.mp4](dffdsdfdsfsfd.mp4)\n[buggy transforms.blend](buggy_transforms.blend)\n\n", "Breaking change? Curve point tilt default orientation rotated by 90°\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\nWorked: 2.80\n\nThe default orientation (0°) of curve points has changed by 90°. If the curve is used for another object's curve modifier, the result between Blender 2.80 is different to newer versions (reproduced with 2.81...3.6). This is a change that I did not find listed in the release notes, so this is either a bug or by design. In any case, it's a breaking change.\n\n2.80 vs 3.6:\n\n\n\n1. Open the attached project in Blender 2.80 and in 3.6\n2. If you compare the two, you see that the normal orientation is different, consequently the result of the curve modifier affecting the mesh is different.\n\nAfter migrating a bigger project this causes several issues that would need to be fixed. Or Blender needs to be fixed.\nThis is an old issue, so I hope it's not a duplicate. Didn't find it.\nThank you.\n\n", "linking spring character breaks the nose!\nOperating system: Linux-6.3.8-zen1-1-zen-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.0 Beta / 4.0.0 alpha\nWorked:\n\nwhen reloading (opening) saved file of linked spring character, her nose is broken.This does happen only in linking, appending is working fine.\n\n1. Launch blender `./blender --factory-startup`\n1. File -> Link -> CH-spring (collection)\n1. Object -> Library Override -> Make\n1. Save the file\n1. File -> Revert\n\nas I said before, if you go append in the second step `File -> Append -> CH-spring (collection)`, the model works correctly!\n\nEdit: The model is a Blender Studio character [here]()", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "TexBlendNode Python property tooltip incorrect\nBlender 2.8 \n\nI can not change the Progression or the Flip Axis for the Tex Blend Node with python. \n\nIt returns with an error that says \" no attribute use_flip_axis\". I thought this was my fault so I reached out for help on the Stack Exchange> [here ](how-do-i-change-the-blend-node-to-vertical?)\n\nThey think this is a bug or missing API?.. I checked online but could not see this bug reported so I thought I would let you guys know.\n\nI have used a rotate node to work around the problem but I am sure you guys would be able to fix this issue with ease.\n\n[#69973.blend](T69973.blend)", "Blender 3.2 crash when extracting mesh draw cache\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0\nWorked: 3.1\n\nBlender 3.2 constantly crash on heavy load.\n\nI have loaded my scene that has a lot of particles. tried to playback the timeline. after maximum 3 frames, Blender just closes without any error messages.\n[HourglassBuildUp-JUNE30.blend](HourglassBuildUp-JUNE30.blend)\n\n", "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", "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)", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n", "Curves sculpting collision with surface.\n", "Scale and rotate using individual origins as the transform pivot point is useless on poly and NURBS spline types\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.1.0 Alpha\n\nWith Bezier curves, using scale resizes the handles for each control point, but with paths and meshes converted into curves does nothing since they don't have handles. It would have been more useful if it used the median point for each isolated spline instead. That is what I expected it would do." ]

[ "Regression: Crash when using Rotation Output of Curve To Points node (node_geo_curve_to_points.cc)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro K3100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 426.78\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.5.0 Alpha\nCaused by 2ffd08e952\n\nWhen connecting the Rotation output of an active Curve To Points node (or opening a file with such a connection), Blender crashes.\n\n- Create a new project\n- add a Geonodes modifier to the default cube\n- Insert a Curve Primitive node, connect it to a Curve To Points node\n- Connect that to the geometry output\n# Then connect the Rotation output of the node to any active node that will evaluate it (Set Position, Group Output, etc.)\nFirst 4 steps included:\n[#103747.blend](T103747.blend)" ]

[ "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)", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "EEVEE: Crash if computation is too heavy for the system (TDR issue)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nAny time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[NebulaV2.blend](NebulaV2.blend)", "Blender crashes: OpenVDB math::Transform::read throws exception. \nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.2\n\nBlender keeps crashing.\n\nI have a project were I created an animation of modified arrays. Everytime I play it it crashes\n\nCrash report: P1536\n\ncrashed thread: \n```\n\tThread 35 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff726c733a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff72783e60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff7264e8a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff7264e817 abort + 135\n4 libc++abi.dylib \t0x00007fff6f8ae458 abort_message + 231\n5 libc++abi.dylib \t0x00007fff6f89f8bf demangling_terminate_handler() + 262\n6 libobjc.A.dylib \t0x00007fff713da5b1 _objc_terminate() + 104\n7 libc++abi.dylib \t0x00007fff6f8ad887 std::__terminate(void (*)()) + 8\n8 libc++abi.dylib \t0x00007fff6f8b01a2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27\n9 libc++abi.dylib \t0x00007fff6f8b0169 __cxa_throw + 113\n10 org.blenderfoundation.blender \t0x0000000110291c61 openvdb::v7_0::math::Transform::read(std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 4801\n11 org.blenderfoundation.blender \t0x000000011026082b openvdb::v7_0::io::Archive::readGrid(std::__1::shared_ptr<openvdb::v7_0::GridBase>, openvdb::v7_0::io::GridDescriptor const&, std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 1787\n12 org.blenderfoundation.blender \t0x0000000110286589 openvdb::v7_0::io::File::Impl::unarchive(openvdb::v7_0::io::File const&, std::__1::shared_ptr<openvdb::v7_0::GridBase>&, openvdb::v7_0::io::GridDescriptor const&, openvdb::v7_0::io::File::Impl::NoBBox) + 57\n13 org.blenderfoundation.blender \t0x0000000110282c91 openvdb::v7_0::io::File::readGridByName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, openvdb::v7_0::math::BBox<openvdb::v7_0::math::Vec3<double> > const&) + 465\n14 org.blenderfoundation.blender \t0x0000000110282ab6 openvdb::v7_0::io::File::readGrid(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 54\n15 org.blenderfoundation.blender \t0x00000001128a2cc9 MANTA::updateGridFromVDB(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 361\n16 org.blenderfoundation.blender \t0x0000000112890985 MANTA::updateGridFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 869\n17 org.blenderfoundation.blender \t0x0000000112890cee MANTA::updateNoiseStructures(FluidModifierData*, int) + 558\n18 org.blenderfoundation.blender \t0x000000011287e2b5 manta_update_noise_structures + 21\n19 org.blenderfoundation.blender \t0x000000010df34cd0 BKE_fluid_modifier_processDomain + 3168\n20 org.blenderfoundation.blender \t0x000000010df316ce BKE_fluid_modifier_do + 142\n21 org.blenderfoundation.blender \t0x000000010e3ad4f6 applyModifier + 54\n22 org.blenderfoundation.blender \t0x000000010dea5b0a mesh_calc_modifiers + 2778\n23 org.blenderfoundation.blender \t0x000000010dea4d6b mesh_build_data + 123\n24 org.blenderfoundation.blender \t0x000000010dea4035 makeDerivedMesh + 133\n25 org.blenderfoundation.blender \t0x000000010dfe1281 BKE_object_handle_data_update + 1089\n26 org.blenderfoundation.blender \t0x000000010dfe1704 BKE_object_eval_uber_data + 52\n27 org.blenderfoundation.blender \t0x000000010e9f36ba DEG::(anonymous namespace)::deg_task_run_func(TaskPool*, void*, int) + 138\n28 org.blenderfoundation.blender \t0x00000001142cadbc task_scheduler_thread_run(void*) + 364\n29 libsystem_pthread.dylib \t0x00007fff72784109 _pthread_start + 148\n30 libsystem_pthread.dylib \t0x00007fff7277fb8b thread_start + 15\n```\n", "EEVEE: 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", "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", "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", "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", "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", "bevel (Miter Outer) + mirror modifier gives inconsistent result.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\n\nMirror + Bevel modifier sometimes give some inconsistent result when using the \"Miter Outer\" options.\n\nOpen the file to see the error.\nThank you\n\n\n[bevel.blend](bevel.blend)\n\n\n\n\n\n", "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "Crash 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)", "Problems due to leftover Nvidia drivers\nOperating system: Windows 11 Home\nGraphics card: Intel Arc a770 16gb Limited Edition (latest drivers)\n\nBroken: (Blender 3.3, 3.5 and 4.0) Trying to work out if it is just my GPU that is the issues\n\n\nBlender 3.5.1 will not allow me to access editor preferences, and won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 3.3 allows me to access editor preferences, but still won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 4.0 allows for editor preferences, same issue with Cycles. Eevee works fine.\n\nBy not allowing me to access editor preferences or Cycles I mean it crashes.\n\nI have tried to converse with Intel engineers with a video of the crashes but they seem incompetent with knowing how to enable GPU rendering in their own tests.\n\n", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "Crash 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" ]

[ "Bevel/Triangulate modifier causes crash in edit mode\nBroken: 6add652c38\nWorked: 6add652c38~\n\n\nBevel modifier or Triangulate modifier causes crash when switching to edit mode. Only happens when \"Display modifier in edit mode\" setting is enabled.\nAlso happens when a 'subdivision surface' modifier is above an 'edge split' modifier in the modifier stack and both have \"Display modifier in edit mode\" enabled.\n\nAdd a bevel modifier to default cube and enter edit mode.", "2.8 Crashes after adding bevel modifier to default cube and switching to Edit mode\nWindows 10 64-bit/ nVidia 1060 GTX (see also system information file)[system-info.txt](system-info.txt)\n\nBroken: blender-2.80.0-git.efa3389b83e-windows64\n\n2.8 Crashes after adding bevel modifier to default cube and switching to Edit mode\n\nOpen Blender 2.8. The default cube is selected - add a bevel modifier. Then press TAB. Blender crashes on my machine. See debug.log for more information [debug.log](debug.log)\n", "Crash when in edit mode and a 'subdivision surface' modifier is above an 'edge split' modifier\nWindows 10 64bit\nRadeon RX 470 Graphics\n\nversion: 2.80 (sub 27), branch: blender2.8 hash: 8e3a680ebe3\n\nInstant crash when in edit mode and a 'subdivision surface' modifier is above an 'edge split' modifier in the modifier stack.", "Crash when trying to edit a mesh with Bevel Modifier added\nSystem info:\n[system-info.txt](system-info.txt)\nBlend file:\n[Crash.blend](Crash.blend)\n\nOpen Blender, add mesh Cube, add Bevel Modifier, Edit --> Crash.\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", "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", "Clicking on a pie menu item doesn't work when holding the pie menu key.\nOperating system: Windows 10\n\nBroken: 2.79, 2.92\n\nClicking on a pie menu item doesn't work when holding the pie menu key. This is a problem because sometimes the pie menu key release isn't detected by blender and then the it locks the UI.\n\n1. On the 3D Viewport hold Z for the shading pie menu.\n2. While still holding Z try clicking on the pie menu items. Doesn't work.\n3. While still holding Z, left click on Windows's Taskbar then release z.\nAfter that, clicking on the pie menu items doesn't work even though the user isn't holding the pie menu key anymore, blender still considers that the key is held. Then Blender gets locked to the user unless he knows to press esc or right click. The solution is making the pie menu clickable even when the pie menu key is held.", "Symmetry in sculpt mode weird behavior with mask and face set\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.90.0 Alpha\nWorked: --\n\nWhen sculpting a non-symetric object with symmetry on, using shift+a or shift+w creates a weird behavior\n\n\n\n[bug.blend](bug.blend)\n- Open the file above.\n- use shift+a in the second finger like this:\n\n- Turn symmetry off and try it again:\n\n\nThe origin is far off those two fingers and also all the transformations are applied, so I don't think its an expected behavior,\n\n\nBesides, it doesn't happen when you try using brushes on the mesh. \n\n", "Transform cursor (patch included)\nRecently LMB-Drag was made to move the cursor *(edit, this has since been reverted)*.\n\nHowever this just moves the cursor under the mouse,\n\nit _could_ be useful to use transform here, it allows.\n\n- Drag, XKey to lock to an axis\n- ... Shift+Y to constrain to a plane.\n- ... Hold Ctrl to snap (snap to verts for example is handy)\n- ... Shift for more precise placement...\n... most other transform keys.\n\n\nOne reservation I have about this, is that you probably would often want to be able to snap to vertices and edges, and not have to depend on the current snap options in the 3d view header.\n\nSo we could override the snap options that transform uses.... but this seems a bit crappy too, since you may want to snap to faces in some cases, or even snap to grid.\n\nAs an alternative, we could just not bother attempting to integrate this with transform, and add snapping to the current modal operator (similar to how we have with the Ruler operator, which shares low level code with transform snapping)\nBut in that case we miss the axis constraints which seem like they would be nice to support.\n\n\nHere is a test patch to show how it works: [P87](P87.txt)\nNote, it crashes if you try to scale and its hard coded to LMB for cursor place, so its mostly a proof of concept.", "Gaomon Pen Tablet Stops Functioning\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 / HD 7900 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.3.1\nWorked: Not sure, not since 3.0 at least. \n\nUsing Gaomon pen tablet (M10K with latest drivers, 16.0.0.37)\nPen tablet stops functioning under various circumstances.\nPen stops functioning only in Blender. When Blender is not active window, pen resumes function. Pen will not function again inside Blender until all instances of Blender are completely closed and reopened. Starting a new empty scene from file menu does not fix it. Interestingly, only the motion itself is disabled - the buttons on the pen and tablet will still work (right clicking with the pen still opens the context menu, hotkeys still perform function, ect).\n\nPerhaps unrelated, might be a different bug, but after rotating the camera with the pen middle-mouse, any attempt to rotate with the mouse middle-mouse button does so in clunky steps, instead of smoothly. Alt-tabbing to a different window then alt-tabbing back fixes this and makes it smooth again.\n\nThree tested things so far that break the tablet:\n\n - Subdividing an Object\nUsing the subdivision modifier is the most consistent, and breaks the tablet with lower face count of 23,000. \n\n - Raising Face Count Too High\nWithout using subdivision, extruding and loopcutting a cube enough times breaks the tablet at around 120,000 faces\n\n - Enabling a hidden Collection\nEnabling a disabled collection with more than one object. This doesn't always happen. Collection tested has 3 objects (even when hidden in viewport) with no modifiers and face count below 20,000\n\nSimply loading a save with one of the above already saved also breaks the pen function, making progress impossible. \n\n\n[TabletBug post failure.blend](TabletBug_post_failure.blend)\n\nSimply loading \"TabletBugPostFailure.blend\" produces error. Pen will not move cursor at all.\n\n[TabletBug Pre failure.blend](TabletBug_Pre_failure.blend)\n\nAfter loading \"TabletBugPreFailure.blend\", add a subdivision modifier to the rounded cube object. Pen will move cursor before subdivision, but will not move after the modifier is added.\n\n[Tablet Bug character file.blend](Tablet_Bug_character_file.blend)\n\nAfter loading \"TabletBugCharacterFile.blend\", add a subdivision modifier to the character \"body\" object. Pen stops functioning\n", "Texture paint Backface culling option does not work if symmetry is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.1\nWorked: never since implemented in e2d60d180ed8 afaict\n\nWhile in the texture paint mode, the backface culling option of the brush is sometimes ignored, allowing painting onto backfaces. It only seems to affect certain objects. I could not discern why. See the attached blend file.\n\n1. Open attached blend file.\n2. Paint on the backfaces of the mesh; observe bug.\n3. Select cube\n4. Paint on the backfaces of the cube; observe no bug.\n\n", "UI: activate_init doesn't work with Int and Float type properties\nOperating system: Windows & Linux\n\nBroken: 3.2\nWorked: Unknown\n\nUsing activate_init to allow users to directly edit a property doesn't seem to work when the property is of type IntProperty or FloatProperty.\n\n1. Open the attached script in blenders text editor\n2. Run the script\n3. Go to the 3d viewport\n4. Ensure an object is selected/active\n5. Run the simple operator, either through the menu or operator search\n6. Notice that the property in the popup is not directly editable\n\n[test_activate_init.py](test_activate_init.py)", "Poly Build Tool: Editing poly build keymap causes poly build tool to not work properly\nWindows 10\nGeForce GTX 1080\n\nv2.81 Alpha\nDate: 2019-09-10 15:07\nHash: 8f55794c0e80\n\nWith a default blender open, edit the poly build keymap. The tool doesn't work properly with the new key assignment. \n\nFor example, switch 'face at cursor move' to shift + left mouse, and 'poly build delete at cursor' to ctrl + left mouse.", "Click-and-Drag the Cursor with Snapping enabled and an Active Object selected missplaces the Cursor\nOperating system: Linux-5.2.9-125.current-x86_64-with-glibc2.9 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\nWorked: None so far\n\n\nDragging the cursor and snapping it to a Vertex while having the Target set to Active makes the cursor snap to a point in space that is directly related to where you start your *click-and-drag* instruction in reference to the selected object's origin. \n\n1) Change snapping to Vertex, Edge or Face\n2) Change snapping target to Active\n3) Set active tool to Cursor\n4) Activate snapping during transform\n5) Select default cube\n6) Drag Cursor over cube\n\n**Important notes**\n\n- If you deselect everything it works, but while there's an object selected the snapping won't work.\n\n- The problem also happens in Edit Mode, but only if there's an object selected in Object Mode. If you deselect everything in Object Mode and then go back to Edit Mode it works as intended.\n\n- As far as I can tell the _offset_ of the snapping is directly related to where you start your click-and-drag in regards to the Objects Origin.\n\n- There's a BlenderArtist Topic in which some have tested the behavior in Blender 2.81: 1177897\n\n- I recorded a video showing the problem: [blender_bug_report_complete.mkv](blender_bug_report_complete.mkv)\n\n- I also uploaded the blend file I used to record the video: [bug_report_cursor_snapping.blend](bug_report_cursor_snapping.blend)", "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 ). ", "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", "Sculpting laggy and weak from some directions.\nOperating system: Windows 10\nGraphics card: Nvidia GTX 970\n\nBroken: 3.6.1\nWorked:Never(2.80+)\n\nWhen i try to sculpt from from below, using radius unit: scene, sculptings get laggy and the stroke is weak.\n\nI'm trying to sculpt stones for a wall in place.\nThe sculpting works fine if i first move the stone i'm working on to the scene origin. This adds a lot of work as i want to for example put bevels on all objects first, then go on with cracks and other features!\n\nTo reproduce:\nOpen file, sculpt from top and bottom\n\nFile is default sculpt template with sphere moved up by 5 and using scene radius.\n\n", "Cursor warping not supported on Remote Session\nOperating system: Linux-3.10.0-1160.59.1.el7.x86_64-x86_64-with-glibc2.17 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.2\nNever worked on previous Blender Version as far as I am aware\n\nMouse wrapping (seem in `Walk Navigation` for example) in Remote Sessions is unusable.\nAs Unreal had a similar issue that was fixed, I was wondering if that was something that could be fixed for Blender as well.\nIt happens both on Linux and Windows.\n\nInfo from the Remote tech used and possible issue:\nrelative_mouse_support/\nInfo on Unreal Problem and Solution:\n141157\n\n- Under a Remote session, go to View > Navigation > Walk Navigation to activate the tool.\n- panning and tilting around,\nthe camera will lag a lot and get out of control by over-panning/tilting\n\nThanks a lot :)\n\n", "Enable pen tilt support by default\nThis task keeps track of the tested devices in order to enable pen tilt support by default.\nThe reason this feature was committed as experimental was because it is not clear what devices and OS configurations are supported and what devices we are planning to support. \nRight now the feature can be enabled in alpha builds as a experimental feature and used in some sculpt tools (draw sharp, scrape, clay strips...). \n\n\nWorking:\n- Wacom Cintiq Pro 16 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Manjaro 19 GNOME \n- Wacom Intuos Pro M - Ubuntu 20.04\n- Wacom Intuos Pro M - Pop OS 20.04\n- Wacom Intuos Pro M - Windows 11\n\n- XP-Pen Artist 13.3 Pro - Windows 10\n- XP-Pen Artist 15.6 Pro - Windows 10\n\n\n\nNot working:\n- Wacom Mobilestudio Pro 16 - Windows 10 (y tilt axis is inverted)\n- Huion Kamvas 13 - Windows 10 (y tilt axis is inverted)\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)." ]

[ "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", "Particles from multiple systems disappear when all Physics Type are None.\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.81a\n\nWhen selecting a Particle System, all particles of the object disappear.\nImages showing before and after:\n\n\n\n- In the default cube add two particle systems.\n- Set the `Frame End` of both to 1 for better observation.\n- In the `Physics` tab of both choose `Physics Type` `None`.\n- Select any of the particle systems, note that the particles disappear.\n\nAttached file contains an example of multiple particle system on one object:\n[LP_grass.blend](LP_grass.blend)\n\nThis has to be the first file you open with the application.\nIf you open blender and enable the eevee material preview for example with the default cube and open the example file afterwards it works.", "Particles reset their position when using time stretching\nMinimal reproduction steps:\n- Add a particle system to the default cube and make it renderable.\n- Set the old time stretching setting to 20 and leave the new at 100.\n- Play the animation until frame 90 and render.\n- Find that the particles are sticking on the object as opposed to their correct position in the viewport.\n- Render again. They now have their correct position.\n- Play another 5 frames.\n- Render again, they are now sticking to the object again.\n\n[timeStretchingBadRender.blend](timeStretchingBadRender.blend)\n\n**Original Report**\n\nHello,\n\ni am using blender-3.1.0-linux-x64 and working on particles with time stretching but the viewport display is correct.\n\nattached is the blend file. [experiment with text.blend](experiment_with_text.blend) \n\nproblem seen in cpu/gpu/cycles/evee.\n\nregards,\nYaju", "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", "Baked Particles are rendered incorrectly on frame 0 and below\nOperating system: Windows 10\nGraphics card: Geforce RTX 3070\n\nBroken: Blender 3.3.5, 3.3.8 ,3.3.7, 3.6\nWorked: Unknown\n\nWhen rendering baked particles systems that have a baked frame on Frame 0 (or below) particles are rendered incorrectly.\nParticles are rendered on the emitter instead of their correct position.\n\n\n- Open the attached blend file (Note: Particles are now displayed incorrectly even in Viewport on Frame 0)\n- Skip 2 Frames ahead in Timeline\n- Go back to Frame 0 (Note: Particles are now displayed as expected)\n- Render Frame 0, Note: Particles are rendered on the surface of the emitter, which is different from what can be observed in the viewport.\n\n", "Particle Viewport display options don't reset properly when changing particle type\nOperating system: Windows-10-10.0.19044-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\n\nViewport Display panel options don't reset properly when changing the particle type from Emitter to Hair and back to Emitter again.\n\n1. New default scene.\n2. Add particle system to cube.\n3. Go to the Viewport Display panel for the particle system and notice options.\n4. Change the particle system type from Emitter to Hair.\n5. Options under Viewport Display panel change accordingly.\n6. Change the particle system type back from Hair to Emitter.\nOptions under Viewport Display panel are those for Hair and not Emitter.\n\n\n\n", "Converting hair don't work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: -\n\nUsing any of the conversion options in {nav Obejct > Convert}:\n1. Converting the new hair curves systems to any other type don't work, \n2. Converting the new hair curves systems to `Curves` removes the `Surface Deform` modifier\n\n- add a mesh and add the `Empty Hair` curves\n- go to sculpt mode for the hair system\n- add some hair and optionally start to sculpt the the hair with the Comb brush\n- go to object mode\n- press {key F3} or go to {nav Obejct > Convert} and try convert the hair to any other type.\nNoting will hapen unless you convert it to `Curves`, but the `Surface Deform` modifier will disapper.\n\n[Test Hair2.blend](Test_Hair2.blend)\n\nthis files has the old and new hair system for teating, and the old has a tool the new don't have, vutting the size of the hair. I don't know if that is a missing tool or by design, but I real hope that can be added later.\n\nkeep up the grate work :-)", "Can't Animate Texture Mapping Offset For Particle Hair\nWindow 7 64bit 8gb\nnvidia 660\n\nBroken: 2.72 RC\nWorked: I thought this was possible all the way back into the 2.4 series.\n\nAdd a single keyframe to particle texture mapping coordinates.\nMove to another frame and type a new number in the *Offset* mapping field and it will jump back to the number of the first keyframe.\nIn this state there is no way to animate the*Offset*. Even if I insert the same value at the new time location and edit the value in the graph editor the system still refuses to use the *Offset*information for the particle system hair density.\n\nOpen the Attached BLEND file and type a new number in the *X Offset* field.\nThe system refuses to accept the input and resets to the keyframe value.\n\nNOTE: This seems to only be a problem in the *Offset* and *Size* properties for Mapping. You will also see in the BLEND file that I have successfully keyframed the R value of the RGB without experiencing the same problem.\n\n[27_sequin_star_curtain_1a.blend](27_sequin_star_curtain_1a.blend)\n", "Connected Only option of Proportional Editing in Particle Edit mode doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nConnected Only option of Proportional Editing in Particle Edit mode doesn't work\nWhen you try to edit a single hair curve, Proportional Editing affects the nearest curves as well, whether the Connected Only option is enabled or not.\n\n", "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)", "API returns wrong particle position\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.90.0\n\n\nHello, \n\nMy team and I are working on a game prototype with Godot and Blender. We use Blender as our DCC of course but also as the level editor. I'm responsible of the export tool to Godot. One critical point is the vegetation generation and to do so we use Blender hair particle system to place instances of grass onto the terrain. We use a Black and White map to drive the density of the growing areas. Nothing fancy here, It is just a particle system with a texture plugged to the density channel.\n\nI then have a python script that loops through each particle and export its world position and rotation into a json file. \n\nTo better understand the problem, here what I have in Blender : \n\n\n\nNotice how there are no particle on the mud part of the trail, thanks to the density mask in the particle system settings. \n\nHowever, when I loop trough the particles and export to godot , I have this result in the editor : \n\n\n\nThe terrain is covered in particles ! \n\nAnd if I deactivate the mask in Blender, I get exactly the same as in godot with my importer : \n\n\n\nThis simply means, that when I looped through the evaluated particle system in python, it didn't take into account the given mask\n\nTo access the particle system I have : \n\n\n\n```\n result = []\n objects = get_all_objects_in_collection([], col)\n degp = context.evaluated_depsgraph_get()\n for obj in objects:\n if obj.type != 'MESH':\n continue\n for particle_system in obj.evaluated_get(degp).particle_systems:\n result.append(get_particle_system_info(particle_system))\n```\n\nand :\n\n\n```\ndef get_particle_system_info(particle_system):\n \"\"\"Return a dictionary containing particle system and all\n particles and children particles position and rotation\"\"\"\n system = {}\n system['name'] = particle_system.settings.name\n system['mesh_collection'] = particle_system.settings.instance_collection\n system['scale'] = particle_system.settings.particle_size\n system['scale_random'] = particle_system.settings.size_random\n system['particles'] = []\n\n for part in particle_system.particles:\n pa_dict = {}\n pa_dict['location'] = swizzle_yup_location(part.location)\n pa_dict['rotation'] = swizzle_yup_rotation(part.rotation)\n system['particles'].append(pa_dict)\n return system\n```\n\n\nLoad the attached blend file, and run the script. It contains a simple particle system with an image texture as density map with only the top right corner in white. \nThe script outputs the particle positions and by default we easily see that particle position is correct, with only particles found on the top right corner. \n\nNow, change the particle system drawing from Path to Collection and run the script again. Now the API returns all particles, even the ones we don't want....\nFurthermore the position given by the api is the tip of the particle and not the root, which is not really a bug but not really intuitive value. \n\nThanks a lot,\n\nHenri\n\n[bug particles.blend](bug_particles.blend) \n\n\nFurther findings:\n- each time the Render As type is changed, the evaluated objects particlesystem particle count increases\n\nAs a workaround, iterating depsgraph object instances is a much more reliable way of getting object instances for export (see also bpy.types.Depsgraph.html#dependency-graph-iterate-over-all-object-instances)\n\n\n```\nimport bpy\n\ndegp = bpy.context.evaluated_depsgraph_get()\nobj = bpy.data.objects['Plane']\nobj_evaluated = obj.evaluated_get(degp)\n\ninstance_count = 0\nfor object_instance in degp.object_instances:\n # This is an object which is being instanced.\n obj = object_instance.object\n - `is_instance` denotes whether the object is coming from instances (as an opposite of\n - being an emitting object. )\n if object_instance.is_instance and object_instance.parent == obj_evaluated:\n - Instanced will additionally have fields like uv, random_id and others which are\n - specific for instances. See Python API for DepsgraphObjectInstance for details,\n print(f\"Instance of {obj.name} {object_instance.parent} at {object_instance.matrix_world}\")\n instance_count += 1\n\nprint(instance_count)\n```\n\n", "Particles cache ignores animated lifetime\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0\nWorked: not sure if it worked after 2.80, maybe it worked in 2.79, but I'm not sure.\n\nIf you animate the lifetime and bake the particles everything in the same blender session everything works correctly, no matter if you bake them to disk or to memory.\nWhen you save the file, and open the file again the particle cache is broken and it's loading all the animation with the lifetime present in the first frame, no matter if it's a disk cache or a memory cache.\n\n\nBlende file: [test.blend](test.blend)\n\nSteps to reproduce:\n\nYou can watch the video I did or follow this steps:\n\nVideo:[particle_lifetime_an_bug.mp4](particle_lifetime_an_bug.mp4)\n\n1.- Open the attached blend file with Blender 2.90 release\n2.- Clean the cache if there is one, change some parameter like particle count (don't touch particle lifetime, it's animated)\n3.- Bake the animation, and you will see the correct result\n4.- create a new file\n5.- reload our test file\n6.- you will see how the cache is not behaving correctly and it's ignoring the animated lifetime\n\nIt's impossible to trustworthy bake particles without this working, because not even the disk cache is working\n\n\n", "Particle hair with density influenced by texture is (partially) invisible with cycles CUDA backend\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.0.0 up to latest (version: 3.3.0 Alpha)\nWorked: 2.9.3 (from memory since these blend files can no longer be opened)\n\nThe particle hair in the given example file does not show up properly when switching to rendered preview using GPU compute and CUDA specifically. Switching to Optix, or CPU render makes the hair appear shaded. With not showing up properly I mean that the grid lines behind the hair does get obscured (only very faintly visible in the screenshots), but they are clearly not shaded. Disabling texture density influence also makes the hair appear in the GPU compute and CUDA combination.\n\nI understand that the particle system is deprecated, but figured I might as well report this issue so it does hopefully not occur in the replacement.\n\n 1. Open the attached blend file. \n\n [hair_invisible.blend](hair_invisible.blend)\n 2. Make sure that CUDA is used as the GPU compute backend, and that the device is set to GPU compute.\n 3. Switch to rendered view.\n 4. Observe that the hair is only obscuring the grid lines, but not shaded. Next there are several possibilities.\n\n 5. Switch to CPU backend for cycles and observe that the hair appears.\n 7. Or, disable texture density influence and observe that the hair appears.\n\n 8. Reduce the children to 23 and observe that some part of the hair appears within some bounding box. Further reducing the children makes it appear and disappear occasionally until everything appears (as above) at 9 children.\n\n", "Physics different between rigid body and particle system\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.1.0\n\nInconsistent of physics behavior between particle and rigid body with same mass when affected by force-field.\n\n1. Turn off gravity.\n2. 1kg Cube with Rigid Body.\n3. A Particle system with the setting, scale: 1, mass: 1kg, and only emit one particle.\n4. Add a force field with strength of 10/-10.\n5. Play and see the difference.\n\nThe behavior in Particle System is 100x faster than normal rigid body. Is this expected?\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" ]

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

[ "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)", "Crashes when working with pose mode (rigidbodies involved)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.0.1\nWorked: 2.8\n\nFrequent random crashes.\n\nJust animate bones. It may even crash at undo. One day it's okay, another it crashes 20 times a day.\n[debug_logs.zip](debug_logs.zip)\n", "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", "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 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", "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 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 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", "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 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", "Crash when moving to Shading workspace\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.17.5 355.10.05.45f01\n\n|Broken:|version: 2.83.0, commit date: 2020-06-03,|hash: `211b6c29f7`\n| -- | -- | -- |\n||version: 2.90, commit date: June 08,|hash: `9f7d84b656`\n|Worked:|version: 2.82|-\n\nWhen I open Blender, without changing anything in the default scene, if I move to the 'Shading' workspace my system freezes for a few seconds and crashes (it closes).\n\n- Default startup scene\n- click on 'Shading' workspace from the top bar\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Blender Crashes 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", "Quick edit image buffer is saved as 8bit image\n%%%--- Operating System, Graphics card ---\nNvidia 750gtx, Windows7 64\n\n - Blender version with error, and version that worked ---\n2.66\n\n - Short description of error ---\nWhen painting textures it is common to export the current camera buffer to an editing applicationn and bring bacvk adn reapply as project in Blender and other apps. Blender provides this functionality as \"quick edit\" in the texture painting panel. It is all great however the buffer seems to be saved as 8bit which renders the integrity of an highbit (16/32) images. I believe that the quick edit buffer bit depth should be saved as the original image bit depth. As of right now the fidelity of an high bit image is compromised with 8 bit image buffers.\n\nI use Photoshop for image editing so this is not an image editing app mistake, as in that would be with Gimp since it has no support for anything else besode 8bit images.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nAdd a 32 bit image to your model for texture painting\nopen texturing mode\nclick quick edit on the texturing pane\nIt should open up your editing application for quick painting.\n\nYou can also try the blend file I attached.\n\n%%%", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n" ]

[ "Blender Crashes after pressing the right mouse button on the VSE Preview\nOperating system: Windows 8.1\nGraphics card: GTX 1080\n\nBroken: (Blender 2.80 Beta, 2019-03-29)\nWorked: (optional)\n\nBlender Crashes after pressing the right mouse button on the VSE Preview\n[Media1.mp4](Media1.mp4)", "crash with RMB in Video Sequencer / Preview area\nOperating system: Win 7 64 bits or Ubuntu 18.10\nGraphics card: Intel HD Graphics 4400\n\nBroken: 2.80 Beta, 337eb8c1de4c, 2019-03-26\n\nCrash\n\nOpen the Video Sequencer editor.\nSelect the Preview or Sequencer/Preview view type.\nIn the Preview area, click with RMB (right mouse button).\n- > Segmentation fault", "Crash >> Clicking the Preview window of the Video Sequencer\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 51)\n\n\nIn the Video Sequencer window,, just click the Preview area.\nThe area where the images/videos/etc are visually displayed.\nThe strips area slides like normal but clicking the image area just crashes Blender.\n\nNote: (Action mouse click) \nLeft Click in right-click default\nRight Click in left-click default" ]

[ "Dynamic Asset Catalogs\nDynamic catalogs support is a missing part of the asset catalog design. Essentially, they are custom filter settings that are stored and displayed for fast access. The author of an asset library could set them up and have them stored inside the library. However the user of the asset library should also be able to create own dynamic catalogs, and have them stored as part of the preferences.\n\nAlso see: #asset-navigation-organization", "hard to see the warnging messages in the \"XSI\" theme\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0\n\nhard to see the warnging messages in the \"XSI\" theme\n\n\n\n", "Proposal: New Bone Color Presets\n\n\n| | Edge Shapes Deselected | Edge Shapes Selected | Polygon Shapes Deselected| Polygon Shapes Selected | Theme UI |\n|---|---|---|---|---|---|\n| Before |  |  |  |  |  |\n| After |  |  |  |  |  |\n\nMost rigs are forced to use Custom Colors very often, because not enough of the preset colors feel nice to use. This is a shame, because Custom Colors cannot be customized on a user-level, via the theme settings. I think if the Preset Colors were better, Custom Colors wouldn't even be necessary; The 20 slots that we have are plenty enough to cover the entire color wheel with distinct enough colors. At that point, even if you wanted to add a custom color, you'd be hard pressed to find a color that isn't very similar to one of the presets.\n\n### Issues with current bone color presets:\n- Slots 16-20 are blank, immediately not useful.\n- Most colors are too dark, and do not contrast well against Blender's default viewport background color, which is a dark gray in the case of all shipped themes.\n\n### The colors in this proposal:\n- Base colors are much brighter, with a minimum value of 0.75.\n- Colors are spread out sort of evenly across the color wheel.\n- Hues are fairly similar to the old ones, so the color language of existing rigs that used presets shouldn't change much.\n- Proposal is for **ALL themes**. Previously, lighter and darker themes had slightly different presets, but they all had the issues described above. The Modo theme had the additional issue of no visual distinction between selected and active bones.\n\nThe file I used to create the screenshots, with the script to place bones based on their theme color, and to output the code for the [PR](112639): [bone_colors.blend](attachment)\n\n### Questions: \n- Are the colors... good?\n- Should we re-order the presets by hue?\n - Pro: Helps avoid cases where you assign 2 colors that were far from each other in the preset list, but are actually quite similar, so you don't get the contrast you were hoping for.\n - Con: Would make existing rigs using the old presets look very different, potentially with less distinct colors (although still much brighter!).\n- Anti-Versioning: Julian Eisel tells me `do_versions_theme()` can be used to force reset theme colors, but I may need some help with that part.", "Suggestion: Move UI List filter buttons to the top\n**Motivation**\n\n* It's unusual to have filtering settings below the items. Usually you have the filter settings before the items you're searching in, inside and outside of Blender.\n* Since the list extends to the bottom, it's may be more likely that the lower boundary of the list is scrolled out of view than the upper one.\n* While entering a filter string, the number of visible items changes and the filter settings may jump around.\n* For the Asset View UI template, used for pose libraries, we enlarge the UI list so all items fit into the list, to avoid a scrolling view inside a scrolling view (rows are taller there, making this an issue). There is lots of scrolling still, especially to switch from the search button to the other settings: \n\n**Proposal**\nProposal is to simply move the filter options to the top of the list.\nScreenshots of a quick implementation ([P2100](P2100.txt)):\n|  |  | |\n| -- | -- | -- |\n|  |  |  |\n\n**Downsides**\n* Takes slightly more space than the previous solution, which combined the triangle to expand the filter settings with the grip button.\n* It does feel a bit odd at first :) But I think you get used to it quickly.\n* If the list is at the top of the layout, its upper edge may still tend to be scrolled out of view. E.g. in the material properties.\n* Aesthetically not too great? The little triangle kinda fails to indicate what it's there for.", "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\">", "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", "Node Group usability tasks for Node assets\n* Enum socket\n* Custom warnings and errors\n* Panels / Sub-panels\n* Dynamic UI changes\n* Surface choice for inputs in modifiers\n\n", "COLORSPACE SELECTOR: Group box fails to show all possible colour transforms\nDebian Stretch\n\nTrunk\n\nTrial against ACES 1.0.3 set won't show all possible colour transforms when choosing via the UV Image Editor\n\nLoad the ACES 1.0.3 configuration from the official repository. Try to change the colour transform on a loaded image.\n\n\n", "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", "Node Operators: Show node group inputs in redo panel\n_No response_\n\n", "Regression: panels in the properties panel lose their place when scrolling one of the other property panels.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.4.0 Alpha\nBroken: 2.91\nWorked: 2.90\n\nThis is caused by 940b239ad4\n\nWhen we scroll down in any panel and switch to another panel then changing back to previous panel will reset its position (i.e. to the top)\n\n\n[2022-10-18 22-54-24.mp4](2022-10-18_22-54-24.mp4)\n\n", "Inconsistent naming for modes in the undo history menu\nBroken: 3.4 alpha\n\nIn the undo history panel, the \"Object mode\" entry is registered with the name of previous modes. Switch from sculpt mode to Object mode will create an undo step with \"Sculpt Mode\" name\n\nAs for the other modes entries, they have no naming standard. Some entries have \"Toggle\" written before, some have \"Toggle\" after, some don't have \"Toggle\". Also they all have \"Mode\" written except for texture paint. \nThe entries are as follows:\n\n\"Texture Paint Toggle\"\n\"Weight Paint Mode\"\n\"Vertex Paint Mode\"\n\"Toggle Edit Mode\"\n\"Sculpt Mode\"\n\nBased on the default startup;\nChange modes; \nCheck \"Edit -> Undo History\" menu.\n", "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", "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", "\"New Image\" UI improvement\nNOTE: This design is still under discussion and is incomplete.\n\n# Current Issue\n\nThe UI for image creation in Blender doesn't make it very easy to pick an optimal resolution and could be improved for usability.\n\n\nExperienced Blender users might know that you can:\n- Drag over both fields to edit both at the same time\n- Type `*` or `/` to multiply or divide the resolutions to keep standard resolutions\n\n# Proposal\n\nWe need to make these options more obvious and readily available:\n- Add a dropdown for common resolutions (128,256,512,1024,2048,...)\n- Add a toggle to either keep image square. When disabled choose resolution for both dimensions.\n- Add an option to type in a custom resolution\n\nThis still needs mockups and further discussion." ]

[ "Tool settings panel location in the UI\n**Issue Description:**\n\nThe redo panel is actually global but only in the 3D view. Additionally it takes up a lot of space, doesn't really fit well in its current location and generally could use a redesign.\n\n**No Design Decisions Yet:**\n\nThis has turned out to be a fairly big task and will likely go along with a bigger redesign. It's not going to be decided on immediately but we can have some further brainstorming or design work here, even if it's likely this will not be implemented in the next few months.\n\n**Proposed Solutions:**\n\nSee the comments for various proposals.\n\nPut titles in the same line as the setting, much like in the Properties Editor\n" ]

[ "GeometryNodes: Attributes in shader not visible in Eevee \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\n\nWhen an attribute is used in the shader editor, it will render in Cycles but not Eevee. \n\nHave an attribute in a shader as a render output with the Eevee render engine enabled. \n\n[Possible Attribute Bug.blend](Possible_Attribute_Bug.blend)\n\n", "Metaball particles are handled inconsistently in Geometry Nodes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.7.1.220725\n\nBroken: version: 3.4.0 Alpha\nWorked: (n/a)\n\nMetaball rendered via particles are handled inconsistently in Geometry Nodes. It seems only mesh related nodes are generally working well with them.\n\nI wasn't sure about reporting this as a bug, because I assume that compatibility with the particle system is probably not intended use case. I guess ability to access metaball particles at all is an unintended bonus from eaa87101cd5a? I'd argue that if this can be easily \"fixed\" it will open up some interesting use cases before actual simulation/physics nodes arrive, but this is a borderline feature request and I guess developers will decide if this is worth to look at at this point.\n\n\n[MetaballParticles.blend](MetaballParticles.blend)\n[MetaballParticles.mp4](MetaballParticles.mp4)", "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?", "Cycles: Normal Edit modifier after displace modifier does not with motion blur (Eevee seems fine)\nTried on multiple systems\n\nBlender 3.0 (And the previous beta builds)\n\nThe normal edit mode will not work with motion blur enabled\n\nSee attached file - Using a NormalEdit modifier looks correct in viewport then fails at render time if motion blur is used in combination with the attached Geometry Nodes tree that is displacing the main geometry over time. \nWith the node tree disabled the NormalEdit modifier works even with motion blur.\n\n**Viewport Result:**\n\n\n**Rendered Result:**\n\n\n\n**Demo file:**\n[Bug (1).blend](Bug__1_.blend)\n[#93700 Cycles Normals Motion Blur Displace.blend](T93700_Cycles_Normals_Motion_Blur_Displace.blend)", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n", "Bevel modifier/tool expands vertex groups into surrounding geometry\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nWhen beveling geometry with avertex group assigned, some of the surrounding vertices are added to that group after beveling. This creates a lot of problems when deforming a mesh in Geometry Nodes based on vertex groups.\n\n\n\n - Assign part of the mesh to a vertex group.\n - Bevel entire mesh either with a modifier or a bevel tool.\n\n\n", "Cannot render GeoNodes instanced collection without having original collection also rendered\nA collection is created and two planes shaped as diamonds are added. A separate plane is created and geometry nodes is used as a modifier instancing multiple copies of the diamond collection. When rendering only the geometry node instances are to be rendered but the original collection also renders. If the camera icon in the outliner is changed to black for the original collection or the diamonds then the whole scene is rendered black. The geonode plane with a white (on) camera icon should render all items generated by that modifier and the original diamonds with the camera black (off) should not be rendering.\n[B30beta renders too much.blend](B30beta_renders_too_much.blend)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Beta\n\n\n\n", "Geometry node group input for \"Single Value Only\"\nAdd a new \"Single Value Only\" option to node group inputs, only for geometry nodes.\n\nThis would hard-code the non-field status of that input, and remove the \"Use attribute\" toggle in modifier and tool inputs.\n\n", "GN: Delete Geometry node hides edges in some cases\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.2.0 Alpha\n\nHard to describe this one more abstract..\n\nI start with a mesh line primitive (0,0,0) (0,1,0) and extrude it **n** times along **x** to get a grid.\nNow I try to delete all points with a distance from the **y** axis greater than **d** \nWhenever **d** lies between the first and the last extrusion, the edges of the starting primitive are not displayed.\nIt shows up in the spreadsheet however and reappears if I apply the modifier and tab into edit mode and back \n\n[2022-02-05 19-27-50.mp4](2022-02-05_19-27-50.mp4)\n[del_geo_node.blend](del_geo_node.blend)\n\n", "Geometry Nodes: Viewer overlay disappears when enabling In Front\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nWhen enabling \"In Front\" in the Viewport Display options of an object, which currently has a geometry nodes viewer overlay, that overlay disappears.\n\n| Viewer object: `In Front`: OFF | Viewer object: `In Front`: ON |\n| -- | -- |\n|  |  |\n\n1. Open the attached file in 3.4 or newer versions.\n2. Make sure the viewer node is enabled in the geometry nodes of `Plane.001`.\n3. Under Viewport Display, toggle `In Front` for `Plane.001`.\n\n[bug_report.blend](bug_report.blend)\n", "Shader Editor header always shows active slot info even when pinned\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version:**3.5.0 Alpha**\nWorked: Never\n\nShader Editor's header, where the slot number and material name dropdowns are displayed, keeps showing the active/selected slot info even when it's pinned to another one. \nEditor shows the correct nodetree, so the issue is limited to the header, not the whole editor.\n\nFor comparison, issue is not present for the Geometry Nodes editor.\n\n\n\n- Have two materials present on an object\n- Open two Shader Editors, pin one of them\n- Select the other slot, the pinned editor's header will also show the newly selected slot's name, when it shouldn't\n\n[BUG_pinned shader editor.blend](BUG_pinned_shader_editor.blend)\n", "Add Active Camera geometry node\nSince geometry nodes is always processed in the context of a scene (at least it is now), there is typically a single camera object that's currently used for rendering. It can be useful to extract information from it, and the first step is just being able to access its transform.\n\nVQ2W/\n\nAdd a node that outputs the active camera object. Users can then use the object info node to retrieve data about the object's transform. The task includes investigating and adding dependencies between the two objects so that geometry nodes reevaluates when the active camera is moved. That is done in `process_nodes_for_depsgraph`.\n\n", "Geometry Nodes: Color mix nodes don't effect the alpha\nOperating system:\nGraphics card:\n\nBroken: 3.4.1\n\nwhenever I try doing any math with colors, the alpha isn't affected when I use the color mix node in any blend mode. \n\n1. Open blender geometry nodes.\n2. Add 2 combine color, color or whatever node with different different values for the alpha's.\n3. Use a mix color node with any operation like add, subtract etc.\n4. See that the alpha didn't change (use the spreadsheet or the hover over).", "Bezier Splines: Support different interpolation options\nBezier splines have the option of different interpolation methods between control points.\nTo achieve feature parity with the old curve implementation, these should be supported\nfor geometry nodes curves as well.\n\n{[F11838239](image.png) size=full}\n\nBecause of the generalized way attributes are handled in geometry nodes, supporting\na different interpolation method for the `tilt` and `radius` is much more complicated,\nand would require special cases in many areas of the code. I propose merging the two\noptions, so a spline can only have one interpolation method that applies to all attributes.\nIf one wants to interpolate tilt and radius differently, it would always be possible by changing\nthe interpolation mode procedurally and capturing the result as an anonymous attribute.\n\nMeeting notes: 21733", "Image syncing between Editors via active image canvas \nThis is related to [D16811](D16811) and similar improvements.\n\n## Issue\n\nThe purpose of this design is to avoid unintended syncing of images between the image editor, 3D viewport and shader editor.\nThe syncing is currently tied to the last active image texture node in the material. But since this is triggered with selection it leads to many accidents.\nThis has lead users to avoid using the syncing all together by pinning images and not using the \"Material\" texture selection in the 3D viewport.\n\n## Solution\n\nThe goal is to make the syncing an explicit action by\n- Using the active texture paint slot/canvas, instead of the last active image texture node\n- Indicating the active image canvas on any image texture node that uses it with an icon (Eye icon for example)\n- Changing the active image canvas in the node editor via an explicit action (Clicking the icon)\n- For faster use, add a shortcut (like double clicking on an image texture node) to make the image canvas active\n- For reference, add a context menu entry with the used shortcut\n\n\n\nThis also affects other areas where currently the active image texture node is being used:\n\n- General Image editor display\n- 3D viewport solid shading with color set to Texture\n- Baking target texture\n- UV editing image aspect ratio\n\nThis wouldn't contradict current cases of icons in the top-right corner.\n\n" ]

[ "UI: Give all node editors a different view state\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.23\n\nBroken: version: 3.2.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: N/A\n\nCurrently when you switch between node editors, the view position and zoom doesn't change.\n\nFor example, say you have a Geometry Nodes graph with the view panned to the left because your geometry nodes are to the left.\nIf you switch to the Shader Editor, now you have to pan to the right to see your Shader nodes.\n\nThis is really painful if all nodes have a different position, and sometimes you can't see nodes at all.\n\n1. Open Geometry Node graph\n2. Select all nodes and drag them to the left\n3. Pan the view to the left (using middle mouse button)\n4. Switch to Shader Editor\n5. You can't see any nodes\n\nMany times I've completely lost track of where I put my nodes due to this problem." ]

[ "mask animation is not undoable\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4454\n\n\nBroken: tested 2.79, 2.80\nWorked: non\n\n\nmask animation is not undoable\n\ncreate a mask and make an animation keyframe\npress ctl+Z or edit->undo : nothing happens!\n", "Grease Pencil - A corrupt Sculpt > Push brush is created when undoing a mode change\nOperating system: Darwin-19.5.0-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: 2.90.0 Alpha\n\nA corrupt Push brush is created when I undo a Draw -> Sculpt mode change.\n\n* File > New > 2D animation\n* Change from draw to sculpt mode\n\n* Edit > Undo (the mode changes back to draw mode)\n* Change again to sculpt mode as before\n* A new corrupt Push brush has appeared called F Push (instead of F Push Stroke), and is selected. It has no thumbnail. It is missing the usual UI elements of the Push brush, like strength. See screenshot.\n \n\n", "Texture Paint: Wrong active Texture Slot\nOperating system:win10\nGraphics card:GTX 740m\n\nBroken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, build date: 2021-02-25, 09:31:14, hash: 02948a2cab\n\nVpqy7BmMKaA\n\n- Open attached file or:\n - Go to \"texture painting mode\" (in default workspace)･\n - Create 2 base color textures\n - Open Shader Editor\n- In the Shader Editor, select non -active texture (\"Material Base Color 2\")\n- in the View 3D, paint texture\n- Nothing happen in visual.\n- The other texture slot is changed instead of current active texture.\n[tex_slot_problem.blend](tex_slot_problem.blend)\n\n", "Creating a new image texture in shader editor does not appear among the texture slots\nWindows 10 Pro 64bit, AMD Ryzen 5 2600, 16Gb RAM\nNVidia GTX 1060 6Gb\n\nWindows 10 Pro 64bit, AMD Ryzen 5 1600, 8Gb RAM\nNVidia GTX 1050Ti 4 Gb\n\nBlender 2.8 Beta 91a155833e59\n\nIf you are texture painting in one window and you modify the shader by adding/removing an image texture to it in another, it won't appear/disappear from the texture slot list until you change to edit mode (or anything else) and back. Another issue is that this way you can paint onto an image texture that is no more connected to the shader and it doesn't disappear even if you do the \"edit mode and back\" (TAB x2) trick.\n\nSteps: Add an image texture to the shader in the attached file, connect to the roughness for example, create a new texture for. It won't be in the texture slots list. Now TAB x2 in the 3D view, slot appears. Paint on it, delete the node from the shader. It is still in the list. TAB x2. It is no more in the list, but the 3D view still shows the texture.\n\n[test1.zip](test1.zip)", "Dynamic Paint With UNDO [Control Z] Crash Blender\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen Press Control Z While In Weight Paint (EDIT MODE), Blender Crash\n\nBased on the default startup or an attached .blend file (as simple as possible).\n[weight-paint-v1.blend](weight-paint-v1.blend)\n1. Open the provided .blend file\n2. Start playback and enter Weight Paint mode\n3. Paint and then undo (Control + Z)\n4. Blender crashes after a while,\n\nHere is video to show case KUUbxSnwmbE", "Physics menu - Dynamic Paint breaks the menu layout\nOperating system: Linux-5.4.92-050492-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.3.3 - kisak-mesa PPA\n\nBroken: version: 2.91.2 , 2.93 Alpha 699b2d98553f \n\nIt is quite simple, Dynamic paint causes the menu to become one column instead of sticking to two as shown in the video.\n\nOpen up a new file, go to Physics Properties tab, click on Dynamic paint.\n\n[Based on the default startup, no need to provide a file]\n\n[blender-dynamic-paint-menu-bug.mp4](blender-dynamic-paint-menu-bug.mp4)", "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", "Undo/Redo if Sculpt Mode toggle doesn't have Undo History produces Draw Brush in Sculpt Mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha\n\nUndo/Redo if Sculpt Mode toggle doesn't have Undo history produces Draw Brush in Sculpt Mode\n\nCreate new 2D animation project\nInstall the following addon, which binds a \"gpencil.sculptmode_toggle\" with no Undo history to \"LEFT_CTRL\" and \"ed.undo\" to \"D\" \n[no_undo_sculpt.py](no_undo_sculpt.py)\nDraw lines in paint mode\nHold \"LEFT_CTRL\" to switch to sculpt mode, press \"Z\" to undo\nDraw brush is now in Sculpt Mode\nAlso affects redo if you use \"D\" to undo and not switch to Sculpt Mode, use \"CTRL+SHIFT+Z\" to redo\nWhile in this state, pressing \"TAB\" to switch modes produces \"Unable to execute 'Strokes Sculpt Mode Toggle', error changing modes\"\nPressing \"TAB\" again switches to Object Mode\n[2021-04-08 16-51-03-00.00.00.000-00.00.28.016.mp4](2021-04-08_16-51-03-00.00.00.000-00.00.28.016.mp4)", "Edge/Vert Slide fail to properly \"redo\"\nCurrently vertex & edge-slide use the mouse input to calculate which edge to slide, the direction to slide, and the **Even** toggle is set at runtime.\n\nUsing operator redo is not re-running with the same options, so redoing the action fails.\n\nWe could simply disable redo with this operator, however being able to toggle **Correct UV** is important.\n\nAdding this report to merge in duplicates, since there are various reports on this, which all have the same root-cause.", "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", "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", "Grease pencil. Artefacts at beginning of strokes\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: 3.0.0 Alpha\n\nGrease pencil strokes drawn with a stylus have unwanted artefacts at their beginning. Especially noticeable at high radius settings. Related to this, the start of a stroke is often narrower than the artist's intention.\n\n\n\n* Open new document, 2d animation\n* Set brush strength to 1 (not using pressure)\n* Set brush radius to 200 (using pressure)\n* draw several lines with a stylus\n* zoom in to inspect the start of the lines. There are artefacts, a 'lumpy' line close to the beginning of the stoke (see screenshot)\n\n**Notes**\nWhen you draw with deformable physical natural media (e.g. a paint brush, felt-tip) adding pressure increases the size of the mark, even when the tip is not moving over the paper. Other drawing programs also work this way. Currently blender doesn't work this way.\n\nI looked at the source code (gpencil_paint.c). Here's what i think is going wrong with the grease pencil strokes:\n\nWhen the pressure difference between two close adjacent vertices is large this can cause ugly 'lumps' in the line.\n\nCurrently, stylus pressure can be very different between the first and second vertex recorded in a grease pencil stroke. This is because there can be a large time difference between the recording of the two points; The first vertex stores a record of the pressure only at the moment the stylus first touches the tablet, subsequent changes of pressure before the stylus begins to move across the tablet are not recorded in the stroke. Only after the stylus starts moving is the second point recorded with the current pressure.\n\n**Proposed solution**\nAny time the stationary stylus tip is touching the tablet, the drawing routine polls the changing tablet pressure continuously. When the detected pressure is higher than the pressure of the last recorded point, the pressure of the last recorded point is overwritten by the newly detected (higher) pressure. This way, the pressure of the first and second points in a stroke is much more likely to be similar, the width of the start of the line will more closely match the artists intention, and the likelihood of artefacts is reduced.", "Texture paint Backface culling option does not work if symmetry is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.1\nWorked: never since implemented in e2d60d180ed8 afaict\n\nWhile in the texture paint mode, the backface culling option of the brush is sometimes ignored, allowing painting onto backfaces. It only seems to affect certain objects. I could not discern why. See the attached blend file.\n\n1. Open attached blend file.\n2. Paint on the backfaces of the mesh; observe bug.\n3. Select cube\n4. Paint on the backfaces of the cube; observe no bug.\n\n", "Render glitches on cycles when 'Motion Blur' and 'Use Limit Surface' are turned on. \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\nAlso broken in: 2.93.0 Alpha, branch: master, commit date: 2021-03-20 21:00, hash: 9ca67c47a152, type: Release\nbuild date: 2021-03-20, 23:00:48\nWorked: unknown. This file was created within 2.92\n\nWhen rendering this file I get (for me) random glitches in the render, when Motion Blur is active in Cycles.\nIn the attached file you can see this in for example frames 13,46,77 and 153 (amongst others) for the figure on the left and in frames 57,65 and 82 for the figure on the right.\nTurning off motion blur makes the glitches go away. It happens - for me - both with CPU only and with GPU renders.\n\nThe only objects - as far as I can tell - that produce these glitches are the two 'jasjes' with the material called 'overhemd'. (changing 'overhemd' to a different color also changes the glitches to that same color) Apart from the very obvious triangular glitches, you can also see some sort of wrinkly render errors near the ties on the shirt that only appear when the glitch is visible.\n\nFrame (13) with a glitch: \nFrame (14) without a glitch: \n\nThe objects started out as duplicates of each other.\n\n- Open attached file\n- Render frame 153 (or any of these: 13, 46, 77)\n\nI'm sorry the file is as large as it is, but I haven't had this happen in other renders/files yet, so I couldn't reproduce with another file.\nPlease let me know if you prefer to get Dropbox links instead of an actual upload.\n\n[Statler_en_Waldorf_animatie_013.blend](Statler_en_Waldorf_animatie_013.blend)", "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" ]

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

[ "Invert Masking behaviour for Sculpt/Paint Mode\nThis is a design related to the implementation of Paint Mode.\nIt outlines the possibility to invert the behavior & visualization of masks.\n**Current** = Masked vertices cannot be edited\n**Proposed** = Masks & Selections are the same -> They can be edited.\n\n# Current Issues\n\nThere are a few different issues that exist the with current way of how masks work.\n\n### An Inverted Workflow\n\nA typical workflow issue when using masks is that users mask a section of their mesh and then invert the mask.\nIn a lot of cases the areas you mask are the ones you DO want to edit.\nMasking is very much designed with this workflow in mind. But this leads to using `Invert` on the mask potentially hundreds of times per day.\n\n### Syncing Selections across Modes\n\nFor the implementation of Paint Mode it will be very beneficial to start syncing selections between various modes. \nSo if a selection is made in Edit Mode it will also appear as masked in Sculpt/Paint Mode (This would likely be a direct conversion every time you switch modes)\nThis will be less confusing and disconnected if both the selection in Edit Mode and the mask in Sculpt/Paint Mode are areas you CAN affect.\n\n### Masks vs Selections\n\nA current plan for the implementation of Paint Mode and the new Curves object type is to use \"Selections\". \nThe use case for sculpt mode masks and selections is essentially the same: \n**You define a temporary area that should be affected by your operations.**\n\nThe issue is that \"Masks\" also refer to the concept of for example creating an attribute (like a vertex group or color attribute)\n or a grayscale image texture and using it as a factor for shader/geometry nodes. The use case here is quite different:\n**You save an area for repeated use in materials and procedural networks.**\nFor example layering textures.\n\nReplacing the current concept of sculpt mode masks with selections would avoid confusion and make the use case of selections and masks very clear.\n\n# Proposal\n\n### Selection instead of Masking\n\nWe need to test the following behavior:\n- Rename \"Mask\" to \"Selection\" or \"Selection Mask\"\n- Unselected areas are darkened with an overlay\n- Selected areas are affected by brushes & other operations\n\nThere are use cases that are important to keep in mind with this change:\n- When entering sculpt mode, everything should already be selected.\n- Previous workflows (Mask brush) to create a deselected area and should still be accessible.\n\nOther areas of Blender will still refer to \"Masks\" like a Texture Mask in the brush settings, mask nodes, grease pencil layer masks and motion tracking masks.\n\n### Offer a preference to use the old behavior\n\nThere should be an option in the preferences to invert the selection behavior globally in sculpt/paint mode and get the old behavior back.\nTo what extend the inverted behavior would be done needs to be tested.", "Inconsistent pressure behavior between the size and the strength in the sculpt mode\nOperating system: Win 11, Wacom Intuos Pro\n\nBroken: c1beaea80f97\n\n\n\nThis bug report was requested by @JulienKaspar.t.\n\nThe strength pressure feels totally flat once the size pressure is disabled. This behavior is really inconsistent across brushes. I am using the Clay brush below but most brushes have this issue, so it is not limited to the Clay brush.\n\nHere I am demonstrating it with the Clay brush. The brush feels ok when both the pressure and the strength is enabled, there is enough pressure variety and consistency.\n\n[blender_CXuVDMlgac.mp4](blender_CXuVDMlgac.mp4)\n\nI am disabling the size pressure in the video below and the strength feels like there is hardly any pressure control. It almost feels like it is not even responding to the pen pressure. I am using the exact same pressure as in above video with my Wacom pen.\n\n[blender_sd6OpRGCHX.mp4](blender_sd6OpRGCHX.mp4)\n\n\n\nAdd a dense mesh\n\nEnter into the ssculpt mode\n\nSelect the Clay brush\n\nMake sure the brush utilizes the size and the strength pressure.\n\nUse pressure to draw over the surface.\n\nDisable the size pressure control\n\nObserve how the strength behaves \n\nIncrease the strength beyond 1 to see the issue better.", "Bone weights dont normalize from assign automatic from bones\nOperating system: windows 10\nGraphics card: gtx 1660\n\nBroken: 3.0.1\nWorked: doesn't\n\nvert weights go past the value of 1\n\n- Open attached file (there will be 2 meshes with their own bone chains', labeled \"before assign automatic from bones\" and \"after assign automatic from bones\")\n- Select the \"Armature\" object and then its Mesh\n- Got to Weight Paint mode\n- select bones with no weights,\n- {nav Weights > Assign Automatic from Bones}\nor\n- spawn any mesh,\n- then a bone,\n- apply all transforms to both, \n- select mesh and then armature,\n- ctrl P > automatic weights,\n- armature edit mode,\n- subdivide the bone to create a chain of 3, \n- select armature then mesh,\n- weight paint mode,\n- select bones with no weights,\n- {nav Weights > Assign Automatic from Bones}\n\n[Bone weights dont normalize from assign automatic from bones.blend](Bone_weights_dont_normalize_from_assign_automatic_from_bones.blend)\n", " Elastic deform brush won't work with lower scene unit scale.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 14)\n\n Elastic deform brush won't work with lower scene unit scale.\n\n*Set scene units to Metric, scale to 0.01m\n*Scale the cube by 100 to compensate, apply all transforms\n*Enter sculpt mode\n*Use the elastic transform brush with the options **Grab, Twist or Scale**, the others appear to work", "Dynamic Paint evaluated even when disabled\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.3.1\nWorked: (Unknown)\n\nAfter disabling the Viewport Display and Render options for both the Canvas and the Brush in the Dynamic Paint settings, the system continues to be evaluated during timeline playback, resulting in a very low frame rate. The only way to fix this is to completely delete the **Dynamic Paint modifier** from **both** the Canvas **AND** the Brush. This is not ideal, as settings need to be tweaked in between testing an animation, so the system **should be properly bypassed** when the Viewport Display and Render options are disabled.\n\nThanks very much for looking into this!\n\n**[exact steps needed to reproduce the issue]**\n\nPlease see example .blend file. The landscape mesh is used as a proximity brush to paint \"shoreline\" interaction onto an animated canvas. The project exhibits the same low frame rate even when the Dynamic Paint modifiers have their Visibility and Render settings disabled. Only by completely deleting the modifiers, does the the frame rate return to normal.\n\n\n\n[DYNAMIC PAINT TEST FILE.blend](DYNAMIC_PAINT_TEST_FILE.blend)\n\n", "FaceMaps Phase 1: bone selection & bone display\nThe first phase of integrating the FaceMaps feature, is to make it work as an alternative way of displaying and selecting bones. \n\nThe user sets it up this way:\n\n\n - For each bone, we will have a display option called 'Face Map'. The user can enable it for all the bones he/she wants to use it\n - When enabled, it looks for Face Maps with the same name as the bone.\n\nThat's it. Users can then manipulate their rigs just like today, but bones will look as if you are selecting and manipulating the mesh itself.\n", "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)", "Enable pen tilt support by default\nThis task keeps track of the tested devices in order to enable pen tilt support by default.\nThe reason this feature was committed as experimental was because it is not clear what devices and OS configurations are supported and what devices we are planning to support. \nRight now the feature can be enabled in alpha builds as a experimental feature and used in some sculpt tools (draw sharp, scrape, clay strips...). \n\n\nWorking:\n- Wacom Cintiq Pro 16 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Manjaro 19 GNOME \n- Wacom Intuos Pro M - Ubuntu 20.04\n- Wacom Intuos Pro M - Pop OS 20.04\n- Wacom Intuos Pro M - Windows 11\n\n- XP-Pen Artist 13.3 Pro - Windows 10\n- XP-Pen Artist 15.6 Pro - Windows 10\n\n\n\nNot working:\n- Wacom Mobilestudio Pro 16 - Windows 10 (y tilt axis is inverted)\n- Huion Kamvas 13 - Windows 10 (y tilt axis is inverted)\n", "Grease Pencil: various issues\n*Note: this tasks can be split up once we get feedback on issues, for now this is to discuss changes to make.*\n\n----\n\n\n- Brush pixels are not pixels,\n```\nshouldn't we use a meaningful value?\n(pixels or blender units).\n```\n\n- Grease pencil brushes have material pointers which are globally overwritten.\n\n```\nWhen you set a material, all brushes are looped over and have their material values clobbered.\n```\n\n```\nWhy have a material attached to the brush at all? This could be a scene level setting (or at least not stored per-brush).\n```\n\n```\nSee: `BKE_brush_update_material` called by rna `rna_Brush_material_update` when setting any material.\n```\n\n- Grease pencil sculpt uses it's own brush system,\n```\nis there a good reason for this?\n```\n\n```\nSince these brushes are fairly advanced (pressure & curve mapping options)\nwouldn't it be better to use the existing brush system?\n```\n\n *Note: while particle system for eg: has 'simple' brush types like this, grease-pencil sculpt brushes are more advanced and duplicate more of what we have for regular brushes used elsewhere.* \n\n- Grease pencil weight brush seems to have no way to paint a weight value (only add weight).\n\n```\nAs with mesh weight paint we should be able to paint a weight.\n```\n\n- In edit-mode, vertex selection exists but is hidden by default (0.0 opacity).\n\n```\nShouldn't they be visible?\n```\n\n----\n\n### Lower Priority\n\n- Internally grease pencil sculp is called:\n\n - grease pencil edit (`GP_BrushEdit_Settings`, `GP_EditBrush_Data`, `GP_BRUSHEDIT_FLAG_APPLY_UV`)\n\n```\nThis is highly confusing since we have grease pencil edit-mode, can't we rename these `GP_Sculpt*`. ?\n```\n\n - grease pencil paint (`GPENCIL_OT_brush_paint`)\n\n```\nPaint is easily confused with draw, seems this is for sculpt/weight painting.", "Weight paint mode can show influences of non selected vertexgroups (if weight is controlled by multiple dynamic paint brushes)\nOperating system: Linux-4.15.0-147-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.1\n\nWeight paint mode can show influences of non selected vertexgroups (if weight is controlled by multiple dynamic paint brushes)\n\n[PBdynamicPaint_check.blend](PBdynamicPaint_check.blend)\n\n- open .blend\n- go to weightpaint mode\n- play animation\n- in the mesh properties, change from one vertexgroup to the other back and forth\n- influence of one group is (partially) still visible when switching to the other\n\n", "Blender 2.90/ 2.91 Sculpt Vertex Paint - Stencil not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta, branch: master, commit date: blender-2.90.0-0e280b96ca82-windows64\nWorked: I think this last work in 2.83.2 or 2.83.1\n\nSculpt Vertex Paint - Stencil not working\n\n\n[BlenderBug.blend](BlenderBug.blend)\n\nAdded colored image to texture\nChange texture mapping to stencil\nImage is coming out as black and white on the screen and image is not being transferred on the object.\n\nI have tried changing Blender Mode and Color Space but it didn't work.\n\nAlso I am not sure if this suppose to happen but the image for stencil disappears when I tick Color Ramp under Color in Texture Panel.\n\n", "Gradient weight tool confusing (using previous tool brush)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nGradient Tool in its current state is not very user friendly:\n\n- generally this accesses previously selected tools brush as it doesnt have its own brush (so it looks like it has its own settings for strength/weight, but those are from an 'alien' brush) when `Unified Weight` is turned ON (default) the tool actually works with the `Unified Weight` (set on some other brush, e.g. the Draw Brush), but doesnt present you with that value in the UI (bug!)\n- when `Unified Weight` is turned OFF you are actually tweaking the weight setting of the previously selected tools brush (the 'alien' one) -- this causes confusion (it doesnt affect e.g. `Blur`, `Average` or `Smear` since these dont have weight capabilities)\n- this is even worse when tweaking the Strength, you are actually tweaking the weight setting of the previously selected tools brush (the 'alien' one), this affects `Blur`, `Average` or `Smear` (and Unified Strength is OFF by default!)\n\nSo not sure how to solve the issue with the \"tweaking setting of a seemingly unrelated brush\" issue, what I think we should do though is at least have the values in the UI respect Unified Weight / Unified Strength since this is what the tool will use internally...\n\nSo the main issue is fixed in f38c54d56e: Fix Vertex weight gradient tool show wrong weight/strength values in the UI.\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", "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", "Operator macros [e.g. ARMATURE_OT_duplicate_move] have non-functional 'Proportional editing' option in Adjust Last Operation panel\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nDuplicating a bone in edit mode. In the Adjust Last Operation panel there is a proportional edit checkbox. Which can't be activated.\n\n\nOpen Blender\nCreate armature\nSwitch to Edit Mode\nDuplicate the bone\nIn Adjust Last Operation panel try to activate Proportional editing.\n\n\n\n" ]

[ "\"Double Symmetry\" in Weight Painting\n### Situation\nCurrently there are two types of X-axis symmetry available in weight paint mode. Let's refer to these by their current python API names.\n- `use_mirror_vertex_group_x` uses old symmetry code which relies on finding vertices on the opposite side of the mesh from the vertices affected by the brush stroke. This supports vertex group name mirroring, and is therefore the more useful option when trying to weight paint symmetrical characters.\n- `use_mirror_x` uses new code which is shared across all painting modes, and mirrors the actual brush stroke, hence works even on asymmetrical meshes. Also supports Y and Z axis symmetry as well as Radial. However, this does not support vertex group name mirroring, which is essential for weight painting.\n\n### Problems\n- Currently, it's possible to have both of these options enabled at the same time. The resulting behaviour in this case is catastrophic, as two totally separate symmetry implementations run at the same time.\n- This will happen frequently, because you could easily forget to toggle `use_mirror_x` off when switching from another mode's symmetrical workflow into weight paint mode. You must toggle it every time you change modes.\n- Weight operators like Smooth Vertex Weights is only symmetrical when `use_mirror_x` is enabled.\n\n**<Solution 1 & 2 have been removed from here as they are no longer relevant.>**\n\n**Update and Solution 3:**\n\n- `use_mirror_vertex_group_x` is grayed out until `use_mirror_x` is enabled.\n- If both of the above options are enabled, Blender will use the \"old\" symmetry implementation, meaning that Y, Z and Radial symmetry become grayed out.\n- This prevents the new and old symmetry implementations from both being active at the same time.\n- As long as you keep `use_mirror_vertex_group_x` enabled, you won't have to worry about changing symmetry settings when switching between weight paint mode and sculpt/edit mode.\n- You would only ever disable `use_mirror_vertex_group_x` if you need Y, Z or Radial symmetry, which is fairly rare.\n- You can not have Y, Z or Radial symmetry at the same time as vertex group name aware X symmetry. This is not a new limitation, this wasn't possible in the past either.\n\nAdding vertex group name awareness to the \"new symmetry\" would be a bigger undertaking with threading headaches, but hopefully something that can happen in the future.\n\nCC @angavrilov @dr.sybren @jpbouza-4 @PabloDobarro @BassamKurdali in case I missed anything :)" ]

[ "UI: Image/UV Editor\nThe UI of the Image and UV Editor can be improved.\n\n* Move smooth edges option to user pref\n* Move overlays to an overlay popover\n\n\n\n\n* Move display settings to a popover\n* Change the Pixel Coordinates toggle into an enum to choose between Pixels or Normalized\n\n\n* Slightly re-arrange the header:\n\n* Move th UV Vertex panel away from the Image Sidebar category and into Item, and include Coordinates option here too:\n\n", "Material Preview (EEVEE) can cause access violations when switching to edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.3\nWorked: N/A\n\nSwitching to edit mode with material preview (EEVEE) enabled results in a crash \n(Log from my machine produced with the joined blender file also joined to this report)\n\nusing the file joined in this report:\n- Open the scene\n- Select \"Circle.039\"\n- Switch to material preview\n- Attempt to enter edit mode on \"Circle.039\"\n\n", "Displacement distorts textures\nOperating system: Windows 10\nGraphics card: RTX 3060Ti \n\nBroken: 3.6.0\nWorked: Never\n\nAll textures are distorted where displacement texture is greater than 0.\n\nWhen you plugin displacement as 'bump only' the box projected textures glitch out and start to stretch.\nSee attached file.\n", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "UVEditor: Add developer option to show vertex, edge and poly indexes.\nSimilar to the 3d viewport we should add option to show the vertex, edge and poly indexes to the uv editor.\n\nWithout I have looked to close to the current code-base this should be possible by adding the option to the UVEditor overlay and some tweaks in the overlay engine. \n\nCurrent work-around is to use a split screen.\n\n", "Cycles: Volumes in the world shader behave strangle with some textures\n**System Information:**\nOperating system: Linux-5.14.0-1-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01\n\nBroken: version: 3.0.0 Alpha, and every version between master at 2.81 (That is how far I tested).\nWorked: Unsure\n\n**Short description of error:**\nWhen using certain procedural textures in the volume output of the world shader in Cycles, you get unexpected results.\n\n**Exact steps for others to reproduce the error:**\n1. Create a scene in Cycles.\n2. Change to the rendered viewport.\n3. Open a shader editor and change to the `World` shader and delete the `Background` node.\n4. In the `World Shader`add a `Magic Texture` node and connect one of the outputs to the `Volume` socket on the `World Output` node.\n5. You will noticed that in the viewport you can see the `Magic Texture` is projecting light onto objects in the scene, but you can't see the `Magic Texture` directly.\n6. Place a `Color Ramp` node between the `Magic Texture` and the `World Output` nodes. Now you can see the `Magic Texture` in the viewport.\n\nAnother test:\n1. Create a scene in Cycles.\n2. Change to the rendered viewport.\n3. Open a shader editor and change to the `World` shader and delete the `Background` node.\n4. Add a `Noise Texture` node and connect an output to the `Volume` socket on the `World Output` node.\n5. Notice that you can see the impact the `Noise Texture` is having on the scene, but you can't see the `Noise Texture`\n6. Place a `Color Ramp` between the `Noise Texture` and the `World Output` nodes. You still can't see the `Nosie Texture` in the scene.\n7. Place a `Volume Scatter` node in the `World Shader`, connecting the output to the `Volume` socket on the `World Output` node and connect the output of the `Color Ramp` node to the `Density` input of the `Volume Scatter` node. You can now see the noise texture in the volume if you have a light in your scene.\n8. Select the left most handle (the handle that is black) in the `Color Ramp` node and drag it closer to the position `0.5`. You will see the results you expect until you reach the position `0.5` where the volume will seem to disappear from your scene. Yet when you look at objects in the scene, the light reaching them is still affected by a volume shader you can't see.\n\nHere's a video demonstrating this:\n[Volumetrics not visibile in viewport in certain sitautions.mp4](Volumetrics_not_visibile_in_viewport_in_certain_sitautions.mp4)", "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.", "Mask modifier slow when one of its properties is animated/driven\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\nBroken: version: 2.81 (sub 1)\n\nWhen one of mask properties is animated/driven, it drops performance excessively, the less it hides. \n\n[2019-08-16 10-23-30.mp4](2019-08-16_10-23-30.mp4)\n\n1. Open attached file;\n2. Play animation to see the fps;\n3. Add a keyframe (I key) to the `Display modifier in viewport`.\n\n[maskman.blend](maskman.blend)", "compositor performance issue when larger empty area surrounding the image\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: much faster in 2.93\n\ncompositor performance is severely degraded if there is a larger empty area surrounding the pixels. Also becomes more and more sluggish the longer it plays back, despite it only updating a single image block. Task manager doesn't show any increase in memory usage as it becomes slower.\n\n<video src=\"attachment\" controls></video>\n\nGet an image sequence to playback in the compositor's backdrop, either with a image sequence node, or by updating a single image via python and calling render.render to force the playhead to wait for the compositor to finish calculating. Try playing back with the compositor contracted and expanded. See video for demonstration.\n\nIssue affects the tiled, full frame, and gpu compositor modes. Also happens when experimental compositor is disabled completely in the preferences.\n\nExample video attached.\n\n", "Viewport don`t updated, when UDIM tiles is created\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6.1\n\n[video](-PMixtP5f3c)\n\n- Create a model where the UVs are spread across several UDIM tiles\n- Create a UDIM texture and use it within the material -- but do not create all the tiles necessary to cover the UVs\n- Go into Material Preview mode in the Viewport -- pink sections of the model should appear\n- Create a UDIM tile to cover the UVs\n- The Viewport will not be updated until some interaction occurs (the bug; an update can be triggered by orbiting the viewport or making a selection for example)", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "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", "Quick edit image buffer is saved as 8bit image\n%%%--- Operating System, Graphics card ---\nNvidia 750gtx, Windows7 64\n\n - Blender version with error, and version that worked ---\n2.66\n\n - Short description of error ---\nWhen painting textures it is common to export the current camera buffer to an editing applicationn and bring bacvk adn reapply as project in Blender and other apps. Blender provides this functionality as \"quick edit\" in the texture painting panel. It is all great however the buffer seems to be saved as 8bit which renders the integrity of an highbit (16/32) images. I believe that the quick edit buffer bit depth should be saved as the original image bit depth. As of right now the fidelity of an high bit image is compromised with 8 bit image buffers.\n\nI use Photoshop for image editing so this is not an image editing app mistake, as in that would be with Gimp since it has no support for anything else besode 8bit images.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\nAdd a 32 bit image to your model for texture painting\nopen texturing mode\nclick quick edit on the texturing pane\nIt should open up your editing application for quick painting.\n\nYou can also try the blend file I attached.\n\n%%%", "How to keep asset viewer options and the search field in view?\n\n\nIt's annoying that animators have to scroll up all the time to access these (or down for the search field).", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks" ]

[ "Poor performance when UV editing with many areas/editors open at once\nTo demonstrate: [vy92NCyTgC.mp4](vy92NCyTgC.mp4)\n\nThe areas/editors doesnt necessarily need to be image viewers, but could be of any editor type. Even types such as the sequencer or preferences window.\n\nIdeally only areas/editors that actually would *need* to be updated should *be* updated when editing the UV layout. Editors like the 3D viewport and other UV editors. I also think there should be some kind of \"lazy update\" functionality to avoid poor performance in the window that you are working if you have multiple UV editors open (so that other UV editors can be updated less frequently to maintain better performance in the active editor/area - it would probably also be a good idea to prioritize the 3D viewport for situations where you want real-time feedback there as well).\n\nTowards the end of the video I also show my \"view\" settings where \"Update automatically\" and \"Adjust Last Operation\" is probably most interesting.\n\n**The issue appears only when the texture size limit is set to anything but off in the viewport preferences pane:**\n", "Viewport Texture Size Limit causes lags when uv editing with textured viewport on the side\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.4 Release Candidate\nBroken: 2.92\nWorked: 2.91\n\nCaused by df0bce3f7d\n\nVery bad performance on uv editing with viewport with textures\n\nthis can be reproduced simply but here is a quick one:\n1) get a project (here I tested Fox Splash that you can find blender cloud) very important to use a project as I could not reproduce it on anything simple as a cube\n2) add a UV editing workspace\n\n3) turn on textures in viewport \n\n4) try to edit the uvs of the head of the fox\nIt lags very hard all of blender goes heavy lag\n5) getting rid of viewport or the texture option in viewport solves it but it did not happen on older version of blender (I tested and 2.90 works fine)\n\n\n" ]

[ "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n", "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", "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.", "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", "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 2.91 crashes when enabling Archipack addon\nOperating system: Linux-5.8.0-23-generic-x86_64-with-debian-bullseye-sid 64 Bits\nUbuntu 20.10 Groovy Gorilla (development branch)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (KBL GT2) Intel 4.6 (Core Profile) Mesa 20.2.0\n\nBroken: version: 2.91.0 Alpha\n\nBlender crashes after enabling Archipack addon. Terminal says 'Aborted (core dumped).' Also, Blender doesn't record a crash.txt (that I can find). \n\nStart Blender>Edit>Preferences>Addons>Enable Archipack addon.\n\n[CoreDump.mp4](CoreDump.mp4)\n", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Crash 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", "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?", "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", "Rigify crash in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.2.230315\n\nBroken: version: 3.5.0\n\nWhen I orbit the view in edit mode, the program crashes after a few seconds. Especially around the hands and face.\nIn version 3.1.2 it does not happen to me, it does happen in 3.3.0 and 3.5.\nTried to clean and reinstall, update drivers, save file in 3.1.2 and open in new versions, but the bug persists.\n\nSorry for bothering you, I hope you have a good day.-\n\n\ncreate human metarig, go to edit mode, orbit the view. Orbiting around hands seems to crash faster.\n\n", "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", "Rigidbody crash undoing while animation plays (which was started at frame 1 or below)\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[animation_john2.blend](animation_john2.blend)\n\nOperating system: Windows 10\nGraphics card: Nvidia 2070 Super\n\nWorked: -\n\nBlender crashes when object is rotated to a steep vertical angle and animation player is run.\n\nFor animation_john2.blend\n- Play Animation\n- Select a bone (could be any other operator as well I think)\n- Undo (this will also jump back to frame 0 -- where we started -- which is the important part, starting animation at frame 2 or higher does not result in the crash)\n- Redo\n\nRepeat until crash. Occurs between 2-5 repeats.\n\nAlso occurs at other similar high angles.", "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" ]

[ "Camera causes Blender to crash when hitting render (Eevee and Cycles).\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 72)\nWorked: 2.80 (sub 71)\n\n\nI've had this project for a few months now which breaks on this version if I try to render it. \nThis has something to do with the scene's camera because if I make a new camera, it seems to work fine.\nI have absolutely no clue why this happens though. I tried my best to figure out what causes it but I honestly just have no clue.\nThe console says \"EXCEPTION_ACCESS_VIOLATION\". Full console screenshot below.\n\n\n\nOpen the blender file (Assets were removed) and hit F12 or the render button.\nShould crash instantly.\n\nAttempt to make another camera and render. Should be able to render it fine.\n\nBlend file: [BuggedCamera.blend](BuggedCamera.blend)", "Crash when Rendering (F12)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 399.24\n\n\nBroken: version: 2.80 (sub 71)\nWorked: (optional)\n\n\nCrash when Rendering (F12)\n\nOpen blender, open my file then crash when Rendering (F12)\n[immeuble en fete v3.blend](immeuble_en_fete_v3.blend)\n\n" ]

[ "Tweak tool doesn't drag the point\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.6.0 Beta\n\nThe tweak tool is broken. It doesn't tweak a point.\n\n\nChhose the Tweak tool and try dragging a point.\n\n", "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "Set parent (keep transform without inverse) has no effect on scale\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Alpha\n\n\nSet parent (keep transform without inverse) has no effect on scale. End result is different if use Set parent (without inverse)\n\n[parent_scale.mp4](parent_scale.mp4)\n", "Can't resize node in visible bounds\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\n\nWhen trying to resize a node, the node cannot be resized if the mouse is precisely on the edge of the node\n\nAdd any node in shader o geometry node editor and try to resize the node with the cursor in the border line of the node\n<video src=\"attachment\" title=\"2023-07-11 14-28-46.mp4\" controls></video>\n\n", "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", "Broken simulation nodes cache indicator in timeline\nOperating system: ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6 Beta\n\nWhen Simuation nodes caching is disabled, indicator from timeline is not disappear, and behaves incorrectly:\n1. Under the widget of the current frame there is a piece of the indicator \n2. when moving the current frame to the left, a piece of the indicator remains in place, and after the operation is terminated, it returns under the widget of the current frame\n[2023-05-20 17-30-40.mp4](attachment)\n\n1. Open blend file\n2. perform the operations specified in the description\n\n", "Keyframing Corner pinning in compositing is inconsistent\nOperating system: windows 10\nGraphics card: Nvidia geforce GTX 1050 Ti\n\nBroken: 3.3.0\n\n\nWhen using the background X symbols to drag and drop corners with corner pinning, only the topmost value of each vector is keyframed\nExample image(wanted to edit a meme):\n\n\n- Open attached file\n- Single Render to Update Compositor\n- Move the Corner Pins\nor\n- Arrange nodes as seen.\n```\n{F13601679}\n```\n- Select the corner pin node\n- Try to keyframe the location of the second image/video, using auto keyframes and the background viewport manipulators.\nOnly the topmost (X) value gets keyframed\n\n[Corner pin.blend](Corner_pin.blend)\n", "Cursor's icon doesn't update correctly when going from panel to scene\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.2.0 Alpha\nWorked: Never (introduced/discovered with new design for 2.8 series)\n\nThe cursor icon doesn't update properly when returning it to the scene fast enough after tweaking in panels, and on it's way passing over text panels.\n\n- Go edit mode and select a vertice/edge/face to activate the transform panel\n- Place the cursor in the panel where its icon displays the OS default one\n- Move the cursor fast enough onto the scene. On its way pass over text panels.\n- The cursor icon is the default's one, not the cross as it should.\nSee the .gif for visual explanation:\n", "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", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "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", "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", "Refactor: Replace socket declaration system for (Geometry) Nodes Panels\nThis is an internal refactor, follow up of #108897\n\n", "Add Object Tool, Resolve UI Issues & Polish\nThis task is to track the add-object tool.\n\n- - [x] Resolve behavior when axis aligned, see: #57210 (currently creates very large object). Done 1501c3adad\n- - [ ] Review design changes proposed by @DanielBystedt #57210#1010083", "Custom Nodes customizable Header for the Node Editor\nHi\n\nThis is a follow up from my closed design task:\n 104066\n\nAs @brecht suggested the best way will be to create a dedicated function that every addon can use to customize the header. \n\nI'm going to investigate if it can be donein `release/scripts/modules/bpy_types.py`.\n\nI hope I can get it done this time. \n\nCheers, \nDavid\n\n" ]

[ "Annotations do not scale in the Shader Editor with the Resolution Scale or Windows Display Scaling\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.13\n\nBroken: version: 2.83.3\nWorked: Couldn't find one. Tried 2.90 beta too.\n\nAnnotations made in the Shader Editor do not scale with the interface, either with the Preferences resolution scaling or with Windows Display scaling. This is problematic when reviewing annotations made on a computer using a different screen scale as notes do not line up.\n\nGo to Shader Editor - Add default material/nodes for scale reference.\nT - for left toolbar. Select Annotation tool.\nAdd annotation to the screen, e.g. draw around a node.\nOn the Menu > Edit > Preferences > Interface \nChange the resolution scale.\nNodes will scale. The annotation marks will not.\n\nSame behaviour is observed by changing the Windows Scaling % in the Windows Display 'Scale & Layout' menu.\n\n\n\n" ]

[ "Boolean Modifier is evaluated if an object linked to the cutter object is link-duplicated\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.91.0\n\n\nSuppose ObjectA has a boolean modifier, the target object of which is CutterA. CutterA shares the same mesh datablock as CutterB. If CutterB is link-duplicated (Alt-D), ObjectA 's boolean modifier is re-evaluated. In large technical scenes with many linked cutters this means Blender frequently stalls, re-evaluating *every boolean in the scene every time you duplicate a cutter.*\n\nExpected behaviour: boolean modifier should only be evaluated if the cutter object datablocks *change*, and adding a user to a datablock should not count as a change.\n\n", "Cryptomatte: Are instanced objects handled correctly.\nIt is unclear what the current logic is and if it is desired. This task is there to investigate and propose a solution and implement it.", "Generative modifiers (solidify, mirror) draw face normals from original face (wrong direction)\n@Baszczer information\nOperating system: Ubuntu 20.04\nGraphics card: Radeon Pro WX 7100\n\n@Alaska information\nOperating system: Linux-5.4.0-7629-generic-x86_64-with-debian-bullseye\nGraphics card: GTX 1050Ti 440.82\n\nBroken: 2.83 (2020-05-26 22:42) `f772a4b8fa`, 2.90 (2020-05-26 20:02) `eb5422828a`\nWorked: 2.82a\n\n**Short description of error:**\nThe viewpoint overlay for displaying faces normals in edit mode for faces that are part of a solidify modifier will always point in the direction of the face normal being solidified with Blender 2.83 and 2.90.\n\n\n2.82a\n\n\n2.83/2.90\n\n**Exact steps for others to reproduce the error:**\n1. Open Blender.\n2. Add a plane.\n3. Give the plane a solidify modifier.\n4. In the modifier panel, enable the \"On cage\" option for the solidify modifier.\n5. Enter edit mode on the plane. \n6. In the viewport overlays enable the \"Display normals\" option for faces. \n\n[#77090 - Solidify Normals.blend](T77090_-_Solidify_Normals.blend)\n\nIn 2.82a, this will be have as expected. The normal lines will be perpendicular to the faces of the solidifies plane. In 2.83, all the normal lines align with the normal line of the face being solidified.\n\nVideo because I feel like I'm having a hard time explaining this in words:\n[2020-05-27 22-55-31.mp4](2020-05-27_22-55-31.mp4)", "Eyedropper picker Afected by retopology overlay\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: \n\nBroken: version: 4.0.0 Alpha\n\n\nUsing the Eyedropper Data-Block wouldn't pick visible objects if edit mode and retopology overlay are active\n\n1. Enter edit mode with the default cube.\n2. Activate retopology overlay\n3. Enter in the view tab in the n-panel\n4. Use the Eyedropper Data-Block and you won't be able to pick the object, only if you are at the origin of the object.\n\n", "Alembic design notes\n# Terminology\n\n* ABC = Alembic file (because extension is .abc)\n* DNA = Blender’s data structure\n\n# Current Functionality\n\nImporting meshes from ABC can result in multiple cases. For each imported object:\n* No object animation, no mesh deformation: mesh is imported into DNA as regular mesh object, after that no more link with ABC.\n* With object animation: as above, but with constraint that streams transformations from ABC to DNA.\n* With mesh deformation: as first case, but with modifier that streams mesh data from ABC to DNA, possibly even removing and reconstructing the entire mesh.\n\n\nOther functionality:\n* Materials are buggy (materials should be mapped by name, but we don’t seem to save those to ABC).\n* Curves are supported and loaded as Blender curves (but miss certain properties such as extrustion, etc.).\n* Particles in ABC are loaded as vertex-only mesh.\n* Camera animation is partially supported (transforms, but not camera properties such as zoom/DoF)\n\n\nCurrently easy to do:\n* Static mesh exchange between other software and Blender (because of point 1 above)\n* Adding constraints/modifiers on top of ABC import.\n* Removing extraneous objects.\n* Assigning and editing materials (but on data level may be troublesome).\n* Adding hair/particle systems (it may not work well, but it’s easy to add).\n\n\nCurrently hard or impossible to do:\n* Keeping Blender in sync with ABC (automatically importing added objects, etc.)\n* Knowing (from user perspective) which objects are from ABC and which are from Blender.\n* Performing actions for all imported objects (such as setting a consistent time offset)\n* Offsetting objects in space.\n* Flipping between “real” objects and cached versions.\n* Reliably add hair/particle system, groom, and bake to ABC again.\n\n\n# Tech meeting with Sybren, Sergey, and Campbell\nFeatures discussed:\n* Data streaming can be implemented in same way as dupli-lists / dupli-groups:\n * Loaded ABC is represented as dupli-object. This allows us to generate the meshes / curves from ABC without saving them to the blend file. It also allows the artist to spatially offset the ABC.\n * Dupli-object has option to indicate which sub-hierarchy is loaded. This allows artists to select a subset of objects in the ABC, for example loading an animated character but not the environment or cameras.\n * Dupli-object is stored as `DNAAlembicHierarchy` struct in DNA.\n * Objects from ABC are shown in outliner as collection, similar as currently done with dupli-group.\n * Besides being able to disable the entire collection (currently possible), it should be possible to disable individual objects (not yet possible). This allows, for example, to load an animated Agent 327 from ABC and remove/hide his watch.\n * The collection could contain options to indicate which sub-hierarchy it represents, and a time offset for animations.\n * Alembic XForm hierarchies are loaded as hierarchy of Empties, possibly as their own subgraph in the depsgraph.\n * Open question: how to interact with the objects, how to create static overrides or otherwise “make local”.\n* [Material](abcm.html) names are loaded from ABC\n * Currently Blender doesn’t even properly store material names to ABC at all.\n * The creator of the ABC is responsible for assigning materials to objects / data. The name of these materials should be saved to the ABC.\n * When loading an ABC the materials are looked up by name (if there are duplicates from different libraries, pick arbitrary one).\n * An artist should be able to choose which material names in the ABC map to which Blender materials.\n * It might be nice to have a button “Generate Missing Materials”, which automatically creates correctly-named materials and assigns them to the meshes/objects.\n* Objects loaded from ABC should be handled as “linked from library”, with the ABC as “virtual library”. Interaction between objects from ABC and Blender should be discussed (for example when merging two meshes, one from ABC and one from Blender).\n* Hair: It may be possible to load an animated mesh from ABC, add a hair system, groom it, and save to another ABC. This poses problems with ABC allowing meshes to arbitrarily change topology (and thus also vertex and face order) from one frame to the next. Possible solutions lie in reconnecting the hair system after loading the ABC (for example by using UV coordinates instead of vertex/face indices) or disallowing mesh changes completely after adding hair (this option won’t be liked by artists). We should check with artists in the industry to see which workflows are actually in use.\n* Motion blur: object motion blur is already there. Deformation motion blur should work when the mesh doesn’t change topology. Otherwise it can work if we save & load velocities.\n\n\n# Interface Mockup\n\n\n\n\n\n# Future Work\nPossible directions that we may implement in the future, and may be nice to know about in advance to at least not make completely impossible with current design choices. The basic idea behind this feature is *fixups on top of cached data*.\n\n\n## Sculpt on top of ABC mesh\nHere Hjalti takes the role of the animator, and Andy that of the shader/lighter/look developer.\n1. Hjalti animates character, exports to ABC.\n2. Andy loads ABC, tweaks materials and environment.\n3. Andy locally changes the ABC-streamed mesh (e.g. not changing topology, but for a number of frames change, say, the position of the hand).\n4. Andy saves those changes to another ABC file that acts as a 2nd layer of mesh data.\nSteps 2-4 can be repeated, generating multiple layers of ABC files that eventually are all merged into a single animated character in Blender (this merging of data from different ABC files is supported by ABC itself).\n\n\n# Open Questions\n\n- How to interact with instanced objects from ABC.\n- How to allow modifiers to be stacked on top of imported ABC meshes/curves.\n\n\n# Development Targets\nTBD which is part of Code Quest, or postponed to later. Should be discussed with artists for final decision on what to build & how.\n\n\n1. Rework ABC importer to produce `DNAAlembicHierarchy` structs instead of directly creating new objects/meshes/curves/cameras.\n2. Allow enable/disable of individual objects in ABC dupli-group.\n3. Create & link Collection for ABC.\n4. Fix material name saving.\n5. Create system for material linking.\n6. Implement switching collection between ‘cached’ and ‘live’.\n7. User Interaction between ABC-backed and non-ABC-backed objects (for example trying to join two of those, or trying to parent a Blender object to an ABC object or vice versa)\n8. Make the hair system work.\n9. Test motion blur to clarify what works and what doesn’t (and implement/fix the latter if desired).", "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)", "Apply scale normal flipping\nThe apply transforms operator in blender can apply negative scaling to an object.\nHowever there is two ways to do this. If you scale your model with a negative\nvalue in editmode, you get flipped normals. This is because the vertex order in the\nfaces is preserved and that is what determines the normal. In object mode however,\nthere is a flag in the render engines to flip the normals back, if they are flipped due\nto negative scale. This inconsistency creates the problem with the apply transforms\noperator. The following image shows on top the behavior in editmode and at the\nbottom the behavior in object mode.\n\n\n\nOf course both behaviors have their reasoning to exist.\n\nOne reason for the rendering flag to exist is, that instances of the same object can\nbe mirrored without causing normal problems. Obviously there is no other solution\nto that, since the underlying mesh is the same for all instances, so the render engine\nhas to handle negative scales.\n\nOn the other hand, in editmode you don't want to change the loop order for all your faces\nif you are just scaling. It makes much more sense for editmode scaling to just change\nvertex coordinates. That means you need to fix the normals manually.\n\n\nThe apply operator can only be called in object mode. From object mode the current\nbehaviour looks as if it was flipping the normals. Actually it is just applying the\ntransform \"in editmode\", which looses the negative scale information for rendering.\nThis looks like a bug to some users and is confusing for new users. Users have actually\nrequested this to be changed:\n\n4Zdbbc/\n\nI also heard this request on the BCON22.\n\nHowever the question arises, do we add another option or do we just always flip the\nnormals to make it consistent with rendering? Another question is what happens to\naddons which are using this operator if the operator gets changed in this way?\nHow many addons are actually using apply scale on negatively scaled objects?\nDo those addons fix the normals by flipping them manually?\n\nThere is already a patch available to add this normal flipping without an option:\n\nD16382", "Geometry nodes material index attribute not working correctly on generated/instanced geometry\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.93.0 Alpha\nFYI, the history on this:\nprior to 1a81d268a1 this was working in editmode (but not objectmode)\nafter 1a81d268a1 no material was shown in the viewport at all\nthen with 6583fb67c6 we had first material showing again, but setting index was not working in either objectmode nor editmode\n\nchanging the material_index attribute does not seem to have an effect on created/instanced data, even though the material index seems to change accurately in the spreadsheet and the material slots are set to `Object` type. What is especially strange about this is that the issue does not persist for cycles rendering.\n[geo-nodes_material_index_bug-2021-04-09_12.25.49.mp4](geo-nodes_material_index_bug-2021-04-09_12.25.49.mp4)\n(same for geometry generated with a primitive node)\n\nOriginal file:\n[geo-nodes_material_index_viewport.blend](geo-nodes_material_index_viewport.blend)\n\nUpdated to fields:\n[geo-nodes_material_index_viewport.blend](geo-nodes_material_index_viewport.blend)\n\n", "'Custom Split Normals' generated by the Boolean modifier does not match the normals of the object\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\nIf the object used as operand in the Boolean modifier has `Custom Split Normals` (either through the `WeightedNormal` modifier or manually added) the resulting object will have a \"broken\" `Custom Split Normal`.\nThis kind of works with objects which do not have any `Custom Split Normals` (so only shade flat and shade smooth, no weighted normals etc.) (although it also has it's problems. See #95913 (Strange shading behaviour when using boolean modifier))\nWhen `Custom Split Normals` are involved, the modifier uses the `Custom Split Normals` of the operand object on the target object to determine the shading on the affected areas.\n\n- Open attached file. (The left example has only shade smooth on the boolean object and on the right example the boolean object has a weighted normal modifier on the modifier stack).\nThe issue still persists even if you delete the weighted normals modifier on the target object in the right example.\n[Test_file2.blend](Test_file2.blend)\n\n---\nAnother example:\n[Test_file.blend](Test_file.blend)\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", "Solidify Modifier wrong solidification normals in some cases\nOperating system: Windows 11\nGraphics card: ATX4000\n\nBroken: 3.5.0\n\nIn some corner cases, the Solidify modifier uses wrong solidification normals.\n\nWith the \"Faces linked only by one vertex.obj\" object, where some faces are sharing only one vertex and no edge, the solidification behaves as if ignoring that shared vertex.\n\nWith the \"Triangulated mesh wrong solidification.obj\" object the vertex in coordinates (-1, 1, -1) does not solidify properly, while the exact same mesh, but not triangulated (\"Triangulated mesh right solidification.obj\" object) solidifies right.\n\n", " Verts/Faces instantiation recursion: child items reappear if they are collection instances\nOperating system: kubuntu\nGraphics card: nvidia\n\nBroken: 2.82a - 2.90.1\nWorked: I don't think it did in the 2.8 series\n\n\nThe lower plane is the face-instancer of a blue sphere, and a collection instance that consists only of the peg (the one to the right). When the plane gets instantiated, the sphere is hidden (as expected) but the collection instance of the peg appears.\n\n\n\n\n\n[instantiating-a-collection-vs-object.blend](instantiating-a-collection-vs-object.blend)", "lattice modifier doens't keep original shape at rotation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: 3.6\nWorked: never?\n\nweird behavior of lattice modifier after rotation of 90 degree ()\n\n- Add a lattice modifier on object\n- Pick a curvature mode between bspline, catmull, cardinall - all behave the same\n- Select lattice object, switch to edit mode\n- Select all points of lattice, rotate lattice at 90 degree & I have this weird behavior where lattice doesn't keep original shape - screen will show better\n\n\n\n\n", "API returns wrong particle position\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.90.0\n\n\nHello, \n\nMy team and I are working on a game prototype with Godot and Blender. We use Blender as our DCC of course but also as the level editor. I'm responsible of the export tool to Godot. One critical point is the vegetation generation and to do so we use Blender hair particle system to place instances of grass onto the terrain. We use a Black and White map to drive the density of the growing areas. Nothing fancy here, It is just a particle system with a texture plugged to the density channel.\n\nI then have a python script that loops through each particle and export its world position and rotation into a json file. \n\nTo better understand the problem, here what I have in Blender : \n\n\n\nNotice how there are no particle on the mud part of the trail, thanks to the density mask in the particle system settings. \n\nHowever, when I loop trough the particles and export to godot , I have this result in the editor : \n\n\n\nThe terrain is covered in particles ! \n\nAnd if I deactivate the mask in Blender, I get exactly the same as in godot with my importer : \n\n\n\nThis simply means, that when I looped through the evaluated particle system in python, it didn't take into account the given mask\n\nTo access the particle system I have : \n\n\n\n```\n result = []\n objects = get_all_objects_in_collection([], col)\n degp = context.evaluated_depsgraph_get()\n for obj in objects:\n if obj.type != 'MESH':\n continue\n for particle_system in obj.evaluated_get(degp).particle_systems:\n result.append(get_particle_system_info(particle_system))\n```\n\nand :\n\n\n```\ndef get_particle_system_info(particle_system):\n \"\"\"Return a dictionary containing particle system and all\n particles and children particles position and rotation\"\"\"\n system = {}\n system['name'] = particle_system.settings.name\n system['mesh_collection'] = particle_system.settings.instance_collection\n system['scale'] = particle_system.settings.particle_size\n system['scale_random'] = particle_system.settings.size_random\n system['particles'] = []\n\n for part in particle_system.particles:\n pa_dict = {}\n pa_dict['location'] = swizzle_yup_location(part.location)\n pa_dict['rotation'] = swizzle_yup_rotation(part.rotation)\n system['particles'].append(pa_dict)\n return system\n```\n\n\nLoad the attached blend file, and run the script. It contains a simple particle system with an image texture as density map with only the top right corner in white. \nThe script outputs the particle positions and by default we easily see that particle position is correct, with only particles found on the top right corner. \n\nNow, change the particle system drawing from Path to Collection and run the script again. Now the API returns all particles, even the ones we don't want....\nFurthermore the position given by the api is the tip of the particle and not the root, which is not really a bug but not really intuitive value. \n\nThanks a lot,\n\nHenri\n\n[bug particles.blend](bug_particles.blend) \n\n\nFurther findings:\n- each time the Render As type is changed, the evaluated objects particlesystem particle count increases\n\nAs a workaround, iterating depsgraph object instances is a much more reliable way of getting object instances for export (see also bpy.types.Depsgraph.html#dependency-graph-iterate-over-all-object-instances)\n\n\n```\nimport bpy\n\ndegp = bpy.context.evaluated_depsgraph_get()\nobj = bpy.data.objects['Plane']\nobj_evaluated = obj.evaluated_get(degp)\n\ninstance_count = 0\nfor object_instance in degp.object_instances:\n # This is an object which is being instanced.\n obj = object_instance.object\n - `is_instance` denotes whether the object is coming from instances (as an opposite of\n - being an emitting object. )\n if object_instance.is_instance and object_instance.parent == obj_evaluated:\n - Instanced will additionally have fields like uv, random_id and others which are\n - specific for instances. See Python API for DepsgraphObjectInstance for details,\n print(f\"Instance of {obj.name} {object_instance.parent} at {object_instance.matrix_world}\")\n instance_count += 1\n\nprint(instance_count)\n```\n\n", "Curves with curve modifiers are not translated to mesh correctly and can't be used as a target for constraints and modifiers predictably\nOperating system: W10\nGraphics card: GTX 1080TI\n\nBroken: 2.80-d966c2f0c2ad-win64\nWorked: 2.79 master build\n\nIf you ctrl+a and press \"visual geometry to mesh\" on a curve that has a curve modifier, the resulting mesh you're getting is as if you didn't have that curve modifier at all. This was not the behaviour in 2.79b. Also, if you assign any constraints or assign this curve as a modifier for objects, you'll have it deformed as if the deforming curve doesn't have the curve modifier.\n\nCtrl+a on the bezier curve in this sample file\n[sample.blend](sample.blend)" ]

[ "PyAPI: Object.ray_cast returns wrong face indices with some modifier combinations\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: AMD Radeon HD 6900 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1062.1003\n\nBroken: version: 2.82 (sub 3)\nWorked: (optional)\n\nWith some modifier combinations, Object.ray_cast returns face indices that don't match the indices the object would have if the modifiers were applied or when using Object.evaluated_get. I tested this also in 2.79 and it doesn't work there either.\n\nAttached is a blend file which includes a slightly modified version of the operator_modal_view3d_raycast.py template. It now prints the indices into the console. I included two different test scenarios just in case.\n\nNote, the only changes in the code are the debug print on line 63 and the change to execute the operator only on mouse press on line 84.\n\n1. Open the attached blend file\n2. Open System Console\n3. Run the \"operator_modal_view3d_raycast.py\" script\n\nCase 1:\n4. Select \"Bevel + Decimate\" object\n5. See that the Decimate modifier's face count is 24\n6. Search for \"RayCast View Operator\" and press Enter\n7. Click on the object's faces and check the printed indices inside the Console\n8. Confirm that they go above 23\n\nCase 2:\n4. Enable Developer Extras in Preferences > Interface\n5. Select \"Boolean + Bevel Applied\" object\n6. Switch into edit mode\n7. Inside Viewport Overlays popover, enable indices\n8. Select the top face and check the index\n9. Switch into object mode\n10. Search for \"RayCast View Operator\" and press Enter\n11. Click on \"Boolean + Bevel\" object's top face and check the printed index inside the Console\n12. Confirm that it doesn't match the index of the object which has the modifiers applied\n\n[ray_cast_debug.blend](ray_cast_debug.blend)\n\n" ]

[ "Quick Smoke crash guide February 3, 2023\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.5.0 Alpha\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\n[image.png](image.png)\n[image.png](image.png)\n[Blender-2023-02-03-113746.ips](Blender-2023-02-03-113746.ips)\nTest File: [3.5.zip](3.5.zip)\n```\nCall Stack: Main thread\n__psynch_cvwait\n_pthread_cond_wait\ntake_gil\nPyEval_RestoreThread\nPyGILState_Ensure\npy_timer_execute\nBLI_timer_execute\nwm_event_do_notifiers\nWM_main\nmain\nstart```", "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)", "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.", "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", "Cache-folder name makes fluid simulation not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nCache-folder name makes fluid simulation not working. My blend file (with fluid cache data) was in a folder named badeværelse and the fluid sim didn't work. Changed the folders name to badevaerelse and it worked.\n\nMake folder called \"æ\" (possibly \"ø\" and \"å\" too)\nMake a blend file inside it and try to bake liquid sim and use the folder as cache directory for the fluid physics\nSee how no particles appear when you press bake\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", "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)", "v2.79 - Particle System \"Current Cache to Bake\" Not Work\nWindows 10 Enterprise 64-bit\nNvidia GeForce GTX1080Ti\n\nBroken: v2.79（5bd8ac9）\nWorked: (optional)\n\nAfter previewed and cached the simulation, I cannot read back the cached files after hitting \"Current Cache to Bake\", instead I have to hit the \"Bake\" button to bake it all again(spend the same amount of time as the first time caching it). This way I can read back the baked files and use on any new objects. However It would be nice if \"Current Cache to Bake\" works so I can save some time on every simulation I have already cached.\n\n1. Create a simple mesh(e.g. a plane).\n2. Add a new particle system.\n3. Set up a simple simulation(e.g. set normal velocity to 40 to simulate a fountain).\n4. Go to Cache tab, check Disk Cache, double click the cache and give a simple name(e.g. 001).\n5. Put timeline indicator to frame 0 and hit play, and then it will cache the simulation on a new folder next to your .blend file.\n6. After it is cached, hit \"Current Cache to Bake\".\n7. In the same Cache tab, check \"external\", locate the file path, and leave the cache file name as \"001\"(as you named it). Leave the Index Number to 0.\n8. It shall now indicate that \"2 Points are Found!\"(where you shall have 1000 points by default). If you hit play it will only play 2 out of the 1000 particles you have cached.\n9. Now return to Step 6, hit the \"Bake\" button instead of \"Current Cache to Bake\", the progress bar will show and it will take the same amount of time as your first time played(cached) the simulation.\n10. After baked, repeat Step 7, you should get \"1000 Points Found!\" now.\n", "Crash after Disk Cache Particle bake while set to render as path\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\nsame results on daily 3.1 build\n\nBlender crashes after finishing baking the particles to disk.\nThen proceeds to delete the baked files upon reopening the file. \n(don't know if the deletion is intended behaviour or not, but it stops you from being able to salvage the bake unless you rename / duplicate the cache folder beforehand)\n\nSeems to only happen with disk cache bake and not baking to memory. \nChanging the 'render as' setting to anything but 'path' seems to stop the crashing.\n\nOpen file, bake the particle system\n[Particle Bake to DiskCache Crash.blend](Particle_Bake_to_DiskCache_Crash.blend)", "Remove DerivedMesh: Multi-res Baking\nCurrently multi-res baking uses DerivedMesh because of it's access to internals of the evaluated ccgdm derived mesh.\n\nSee: `MultiresBakerJobData` use of `DerivedMesh`.", "Can't bake to external textures (Python)\nHello, when trying to bake an object to an external texture, Blender seems to ignore the \"save_mode\" and bakes the texture to an internal buffer. I've tried two ways:\n\n```\nimport bpy\n\n# Bake selected objects\nfor obj in filter(lambda x: x.type == 'MESH', bpy.data.objects):\n\t\n\tprint('Selected: ' + obj.name)\n\t\n\t# Select current object\n\tbpy.ops.object.select_all(action='DESELECT')\n\tobj.select = True\n\tbpy.context.scene.objects.active = obj\n\t\n\t# Bake\n\tbpy.ops.object.bake(type='COMBINED', save_mode='EXTERNAL', filepath='E:\\\\baked.png', use_automatic_name=True, width=512, height=512)\n\t\n\t- Other version, doesn't work either\n\t- bpy.ops.object.bake(filepath=\"//baked.png\", save_mode='EXTERNAL')\n```\n\nAnd also setting the parameters in a different way:\n```\nbpy.context.scene.render.bake.filepath = 'E:\\\\baked.png'\nbpy.context.scene.render.bake.save_mode = 'EXTERNAL'\nbpy.context.scene.render.bake.use_split_materials = False\n```\n\nAlways, the execution of the previous code returns the following and does not create an image file:\n```\nSelected: Cube\nInfo: Baking map saved to internal image, save it externally or pack it\nSelected: Floor\nInfo: Baking map saved to internal image, save it externally or pack it\n```\n\nTried with different paths and parameters for the bake funcion, also creating image nodes and selecting / deselecting them in the node editor for the material.\n\nAlso, I found someone who had the same problem as me, and found no solution:\n676562\n\n\nFind attached a blend file: [Bake.blend](Bake.blend)\nIt's a simple cycles scene with a cube and a floor, Cycles renderer. It bakes correctly to textures (internal buffer).\n\n - Open the blend file or create your own scene\n - Run the code written above\n - Blender won't create a bake file, in the console you'll see \"Baking map saved to internal image, save it externally or pack it\"\n\n\nWindows 10, nVidia Quadro K5100M\n\nBroken: 2.79b f4dc9f9d68b, 2.77a abf6f08\n\nThank you", "Error de progama\nno me aparece el modo vèrtice\n\n", "Unsubdivide and rebuild subdivisions from multires.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.1\n\nModel with multires applied doesnt works with unsubdivide option or rebuild subdivisions.\nI´ve applied the modifier, cleaned the data blocks but persist...\nThere is something strange in the mesh because it works with the default cube...\n\n- Open attached .blend file\n- In the Multires modifier, click in Subdivide\n- Apply modifier\n- Add multiresolution modifier again\n- Click in Unsubdivide\n\n> No valid subdivisions found to rebuild a lower level\n\n[UnsubdivideMultires.blend](attachment)\n\n", "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", "EEVEE baking\n" ]

[ "Multiple UDIM tiles are not baked\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\nBroken: version: 3.0.0\n\nDalai Felinto asked me to report this as a bug via blender.chat\n\nWhen trying to bake to an object with uv's outside of UDIM 1001 (outside 0-1 space), only the pixels in UDIM 1001 (inside 0-1 space) is baked. This happens even when the target texture contains multiple UDIM tiles\n________________________________________\nText objects that I try to bake to a plane with 2 UDIM tiles.\n\n________________________________________\nExpected result\n\n________________________________________\nActual result\n\n\n________________________________________\n\n1. Open the attached .blend\n[bake to udims.blend](bake_to_udims.blend)\n2. Press \"fill tile\" in the uv editor\n\n3. Select the text objects and then the mesh object \"bake target\"\n4. Press bake in the render properties \n```\nbpy.ops.object.bake(type='EMIT')\n```\n5. You should now be able to see an incorrect bake result in the uv ediors image\n\n\n" ]

[ "Cycles: Persistent Data option make Point Cloud position is dirty for transformed objects\nOperating system: Linux-6.2.6-76060206-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.105.17\n\nBroken: Curent main.\nWorked: Never (3.0+).\n\nIf you turn on `Persistent Data` in cycles render settings, and change some object position properties, point cloud objects gonna be incorrect positions have on render.\n\n| Shifted point cloud. Expected. | Second result with persistent data option. |\n| -- | -- |\n|  |  |\n\n1. Create Point Cloud object.\n2. Turn ON `Persistent Data`.\n3. Try to render.\nEverything is okay.\n4. Open N-panel. Just click on point cloud position properties. No need to really change something.\n5. Try render again.\n\n", "Redo panel does not work for the 3d cursor\nUbuntu 18.04\n\nBroken: 7d38654\n\nRedo panel for moving the 3d cursor does not work as expected.\n\nStart moving the 3d cursor and then change the value in the redo panel.\n\n\n\nMy guess is that this happens because the 3d cursor is not effected by the normal undo.", "NLA: Change the shortcut key (TAB) to \"Start Tweaking Strips Actions (Full Stack)\" from Start Tweaking Strips Actions (Lower Stack)\nAs discussed in the Animation Module meetings:\n\nCurrently\nMenu: Edit ‣ Start Tweaking Strips Actions (Lower Stack)\nShortcut:\nTab\n\nShould be changed to and remove the Shortcut from (Lower Stack)\nEdit ‣ Start Tweaking Strips Actions (Full Stack)\nShortcut:\nTab\n\nediting.html#bpy-ops-nla-tweakmode-enter\n\nNow that the Full stack tweak mode has had the quaternion rotation keyframe bug fixed, we should update the default short cut to the improved full stack editing mode. This will help with user discovery of the new and requested feature as well as help stop visually confusing animators when working with animation layer workflow in the NLA. The current default of Lower Stack causes a visual change/jump/soloing of the action being edited and looses context of what you are trying to animate.\n\n", "Sculpt Mode - Face Set FK, mirror X is wrong when Scale/Translate using Pose brush with Lock Rotation When Scaling\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\nBroken: 2.92, 3.5.0 Alpha\nWorked: Never.\n\n\n- Change to pose brush.\n- Change brush deformation mode to Scale/Translate.\n- Enable brush Lock Rotation When Scaling.\n- Try to pose the hand.\n- The other hand is flipped.\n\n\n\n\n\nThis is the file I'm using:\n\n[20221205_model_human_sculting_pose_brush_using_facecets_0001.blend](20221205_model_human_sculting_pose_brush_using_facecets_0001.blend)\n", "Set parent to > Keep transform without inverse. - Don't work with animation.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.2\n\nSet parent to > Object ( Keep transform without inverse. ). Doesnt keep transform with animation\nThe child jump to another positions like the \"keep transform\" of the operation didn't worked.\n\n\nYou can watch the video below.\n<video src=\"attachment\" title=\"Blender 2023-09-13 08-53-20_edit.mp4\" controls></video>\n\nExact steps needed to reproduce the issue. Based on the default startup .blend file.\n1. open blender 3.6.2 lts\n2. select the cube. press g. move the cube. \n3. maj + a. add mesh > torus. \n4. select the torus. frame 1. object propertie. press i to create keyframe at xyz position\n5. move to frame 40. press G. move torus. press i to create keyframe at xyz position\n6. select the torus and the cube. The cube must be the active object. press Ctrl + P > parent without inverse and keep transform.\n7. move the timeline cursor. The position of the torus jump to another location\n\n", "Mirror threshold too high, values less than 0.00002 are snapped to center\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.83.3\nWorked: 2.79b\n\nBlender 2.8x has a bug that forces it to snap to the YZ plane with a value less than 0.00002.\nThe above is occurring with the snap off.\nThe bug occurs even if the vertex's X coordinate is moved to more than 0.00002.\nDuplicating the object does not eliminate the bug.\n\n3D Viewport / Edit Mode.\nCreate an object with the following vertices:\n```\nObject-1 = {\n Vertex-A x = 0.00002, y = 0.00005, z = 0.0\n Vertex-a x = -0.00002, y = 0.00005, z = 0.0\n Vertex-B x = 0.000019, y = -0.00005, z = 0.0\n Vertex-b x = -0.000019, y = -0.00005, z = 0.0\n}\n```\n3D Viewport / Edit Mode / Tool / Options / Mirror X [enable].\n3D Viewport / Edit Mode / Snap [disable].\nSelect Vertex-A and Vertex-B.\nMove Vertex-A and Vertex-B.\nBlender 2.8x has a bug that forces it to snap to the YZ plane with a value less than 0.00002.\n\n3D Viewport / Object Mode.\nDuplicate the Object-1 to obtain the Object-2.\n3D Viewport / Edit Mode.\nMirror the vertices of object 2 as if they were object 1. This causes the same problem.\n\nEnlarge the Object-2 sideways.\nMirror the vertices of Object-2. The same problem still occurs. The problem occurs even if the Vertex-B x-coordinate is greater than 0.00002 after magnification.\n\n\n[X-Mirror_bug.blend](X-Mirror_bug.blend)\nThe objects in the X-Mirror_bug.blend file are very small, so zoom in on the view to the maximum size.\n\n\nThis is a 2.79b file with the X-Mirror working correctly:\n[X-Mirror_2.79b.blend](X-Mirror_2.79b.blend)\n\n\nThe difference in x-mirror behavior between 2.8x and 2.79b is shown in the following video:\n[Blender 2.8x BUG_X-Mirror.mp4](Blender_2.8x_BUG_X-Mirror.mp4)\n\n[Blender 2.79b X-Mirror.mp4](Blender_2.79b_X-Mirror.mp4)\n\n\nIf it is unintentionally aligned to the YZ plane like 2.8x, it will not be possible to edit it (if this behavior is a specification, it will be useful if you can implement it as a function separate from the mirror, align it to the YZ plane, and set a threshold to align).\n\n**When importing model data from the outside and editing a mirror, all vertices with an X coordinate of less than 0.00002 are already implicitly aligned to the YZ plane, so editing with an X mirror is no longer possible at all. Hence, until this bug is fixed, edits involving X mirrors should use 2.79b.**\n", "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)", "Multi-object-Mode: EditMode transform properties\nEdit-mode buttons currently only show median values for the active edit-object.\n\nThe Mean Crease value of the N panel doesn't work for multiple objects:\nHere i have 2 objects selected\n\nIn Edit Mode changing the Mean Crease value does change its effect only on the selected object:\n", "VSE: Frame Overlay incorrectly applies Transform to reference frame, ignores keyframes\nOperating system: Ubuntu 20.04.2\nGraphics card: AMD® Verde\n\nBroken: 2.93.3\nWorked: don't know\n\nWhile Frame Overlay is active and set to \"Reference\" or \"Rectange\", the video sequencer applies transformations to the reference frame even when that frame has a different transformation keyframed. The expected behaviour is that the reference frame looks exactly as it does when that particular frame is active.\n\n - Open attached file [vseoverlaytransform.blend](vseoverlaytransform.blend)\n - Note that Frame Overlay is active and Overlay Type set to \"Reference\"\n - Alter the Rotation parametre of the text strip\n - Note that the displayed frame transforms as you change the value\n - Disable Frame Overlay and jump to the first frame\n - Note that the transformation parametre has a keyframe at 0 deg, but the displayed text is still rotated\n - Press Ctrl-R (Refresh All) and note that the text jumps back into its unrotated state\n\n", "NLA: Animated Influence/Time Property Sliders Unresponsive\nTask: #76549 (NLA Strip influence slider doesn't respond to autokey correctly.)\n\n**Source of Problem**: (anim_sys.c) *nlastrip_evaluate_controls() -> animsys_evaluate_fcurves()*: I believe the issue is due to NLA evaluation, where the animated strip properties are evaluated and flushed at the same time the action strip channels are evaluated. Since autokeying doesn't insert a keyframe as the value changes, that's probably why the slider is unresponsive. \n\n**Solution**: Perhaps we should separate (despgraph-wise) NLA strip animated property evaluation from when we evaluate the NLA system for general animation? Animated strip properties would only be evaluated and flushed on frame change or when the whole frame needs refreshed. Then normal non-NLA animation evaluation will just read the strip properties as is. This would allow the slider be responsive. It also allows the user to change these properties and view their changes without having to keyframe, just like any other Blender animated property. \n\n**Potential Problems with Solution:** What do we do when strip influence is animated and the user changes it (without keying) then inserts keys on character bones. When we remap the keyframes, should we re-evaluate and use the strip's animated influence? Or should the new keys be remapped using the unkeyed strip time?", "Wrong undo/redo sequence with direct transform change (via Item/transform panel or addon)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 2.93.1\n\n\nUndo operation is not working properly with `Copy attributes addon`.\n[refer the video to understand the situation better]\n\n\n**Exact steps to Reproduce the error**\n\n[2021-07-28_13-59-32.mp4](2021-07-28_13-59-32.mp4)\n\n**To reproduce**\n- 0. Make sphere, go to sculpt mode.\n- 1. Draw «1» on sphere\n- 2. Change location via item panel\n- 3. Draw «3» on the sphere\n- 4. Undo actions with {key Ctrl+Z}: undo order is broken\n\n---\n\n**Exact steps to Reproduce the error (Addon Case)**\n\n- Open .blend file\n- Enable Copy attributes addon\n- Select both mesh objects\n- Do {key Ctrl C} -> `Copy Locations`\n- Switch to edit mode\n- Perform some changes to the mesh\n- Switch to object mode\n- Perform undo operation.\n\n[Notice that the undo operation ignores all the steps from edit mode and directly switches the mesh to the initial position]\n\n\n[2021-07-27_13-33-38.mp4](2021-07-27_13-33-38.mp4)\n\nTest File:\n[#90234.blend](T90234.blend)", "Pie Menus initiated by tweak events will disable the mouse button used in the tweak event. Works fine for regular menus, operators.\nWindows 10\ngeForce GTXTitan\n\nBroken: blender-2.77.0-git.94e18c5-AMD64\nWorked: (optional)\n\nI've set up some UI shortcuts that use 'tweak' events (or directional gestures) for various pie menus, regular menus, and operators. This work fine for regular menus and operators. After calling a pie, however, the tweak button defined in the input editor (left, right, middle, action) becomes unusable. \n\n1) Open User Prefs, select the add-ons tab, and enable Official Pie menu addon\n2) Select the 'Input' tab in User Prefs, and in the keymap filter (set to name), type the the word 'pie' without quotes\n3) The first filtered pie is 'Frames'. change the hotkey as follows: \nClick the event mapping dropdown (its set to keyboard by default), and change to Tweak. two new options appear next to it: 'Left', and 'Any'.\nChange the type of event, or leave it as 'Left' \nChange 'Any' to a direction.\nSelect a modifier key such as Shift\n\n4) go to the 3d view and execute the new shortcut you set up. The playback options should appear in the pie menu but are not selectable. Hitting the escape key will get out of the pie, but the defined tweak button is not usable.\n\nNOTE: If you use the default right click select, you can still place the cursor, but can't trigger the shortcut again. If left click select is set, then normal tweak events like moving selected objects are also not possible.\n\nNOTE: Toggling Object/Edit mode will make the button usable again.", "Wrong property changing `matrix_world` and destructive undo via RMB.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken:\nversion: 3.6.1\nversion: 4.0.0 Alpha\nWorked: never\n\nReturning to the original state during editing (or canceling) does not give the result that was when editing was started.\n<video src=\"attachment\" title=\"2023-08-16 21-40-53.mp4\" controls></video>\n\n1. Copy script and run\n```python\nimport bpy\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Test Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n col = self.layout.column()\n ob = context.object\n col.prop(ob,'name')\n col.prop(ob,'matrix_world')\n\nif __name__==\"__main__\":\n bpy.utils.register_class(Panel)\n```\n2. Quickly change the scale value for the object matrix.\n3. Press Right mouse button.\n\n", "Apply scale on armature breaks position of child elements with relationship 'Bone'\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.1\nAlso Broken: blender-2.93.4-candidate+v293.7ec351c0d531-windows.amd64-release\nWorked: Never (2.80+)\n\nIf I have an armature with non (1,1,1) scale and if I create an object that is parented to one of the armature bones, applying the scale to the armature moves the object.\n\nIf I then select my arrow/cube and remove the 'Parent Bone', it is aligned correctly again, if I then put the 'Parent Bone' bone back, the arrow/cube is moved to a completely new position.\n\nI can also see the following error in terminal when I unparent the bone (I don't think this is relevant and clearing the bone always prints this, but just in case)\n\n```\nadd_relation(Bone Parent) - Could not find op_from (ComponentKey(OBArmature, BONE))\nadd_relation(Bone Parent) - Failed, but op_to (ComponentKey(OBEmpty, TRANSFORM)) was ok\nERROR (bke.object): C:\\Users\\blender\\git\\blender-v293\\blender.git\\source\\blender\\blenkernel\\intern\\object.c:3330 ob_parbone: Object Empty with Bone parent: bone doesn't exist\n```\nMy theory is that Blender is trying to reposition the object without taking the bone parent into consideration.\n\nI've recorded a small video to illustrate: watch?v=BGNckTOfBQQ\n\nI was also able to create a script that fixes the position by detaching the parent and reattaching with keep_transform (also note the commented out line)\n\n\n```\nimport bpy\n\nprint ('Bone fixer')\nfor obj in bpy.data.objects:\n if (obj.parent_type == 'BONE' and obj.parent_bone):\n bpy.ops.object.select_all(action='DESELECT')\n \n print (f'Parent={obj.parent} parent_={obj.parent_type} parent_bone={obj.parent_bone}')\n print (obj.name, obj.scale, obj.location, obj.rotation_euler)\n \n # obj.parent_bone = obj.parent_bone # This line should not have any effect but it does move the object to a new position\n\n parent_bone = obj.parent_bone\n obj.parent_bone = '' # We are now correctly positioned but not parented \n\n obj.select_set(state=True)\n obj.parent.select_set(state=True)\n obj.parent.data.bones[parent_bone].select = True\n bpy.ops.object.parent_set(type='BONE', keep_transform=True)\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n[test.blend](test.blend)\n\n1. Create armature ('Armature') and set a non 1,1,1 scale\n2. Add bones to armature\n3. Create a new object (I tried empty/arrow or cube)\n4. Set relationship on the cube as parent = 'Armature', Parent Type = Bone, Parent Bone = 'Bone.X' (last bone in the sample file)\n(^ Already done in sample file)\n5. Select armature and \"Apply scale\"\n\nExpected - the empty remains at the 'end' of the bone\nObserved - the empty is moved to a new location (I am unsure what is the logic)\n\n\n\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" ]

[ "move only parent or origin doesn't work with global transform input or snap to cursor.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Quadro P5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nMaybe this isn't a bug, maybe more of a feature request?\nwhen using the new option to only move parent, it only works with the move command not if you use the global transform input or snap to cursor command.\n\nmake two objects. make one of the objects a parent of the other. \nset the option for transform to only affect parents and choose the parent object.\nIf you move the object with ´g´ shortcut everything works fine. If you try to use shift+s to snap to 3d cursor it will move both parent and children even if it should not. \nthis is the same for origin. \nIt would be much better if it was possible to snap to cursor and still only affect the parent/origin.\nI almost forgot, it doesn't work with global transform inputs either. see my attached gif.\n\n\n" ]

[ "Preferences: `Interface Font` doesn't open path set in `File Paths`\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.67\n\nBroken: version: 3.3.0\nWorked: never\n\nWhen hitting the folder icon button to open the file browser to select an interface font, it does not open the path set for fonts under Preferences > File Paths.\n\n1. Set folder path for fonts\n\n2. Open file browser under Preferences > Interface > Text rendering\n\n\n", "Cycles: CUDA takes ages to render what takes seconds on CPU and OPTIX (it also needs way more RAM)\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1, 2.93, 2.92\nWorked: I think it was always the case\n\nThe dino demo file (Splash Blender 2.92 60337d495677e942564cce76) takes with CUDA (BVH2) way longer to build the scene than CPU (Embree).\nIt also needs a lot more RAM. \nCa. 100GB of RAM\n\n\n```\nCUDA (BVH2)\nFra:1 Mem:1175.90M (Peak 51547.35M) | Time:21:52.48 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0001.png'\n Time: 21:53.12 (Saving: 00:00.63)\nOptix (Embree)\nFra:2 Mem:1176.06M (Peak 14002.25M) | Time:00:36.55 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0002.png'\n Time: 00:37.16 (Saving: 00:00.60)\nCPU (Embree)\nFra:1 Mem:1175.90M (Peak 14007.17M) | Time:01:08.57 | Compositing | De-initializing execution\nSaved: 'C:\\tmp\\0001.png'\n Time: 01:09.21 (Saving: 00:00.63)\n```\n1. Open the scene\n2. Set it to one sample (disable denoising)\n3. Render with CPU, CUDA and OPTIX to compare.\n", "Dynamic Asset Catalogs\nDynamic catalogs support is a missing part of the asset catalog design. Essentially, they are custom filter settings that are stored and displayed for fast access. The author of an asset library could set them up and have them stored inside the library. However the user of the asset library should also be able to create own dynamic catalogs, and have them stored as part of the preferences.\n\nAlso see: #asset-navigation-organization", "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.", "Poor performance in Timeline, Dope Sheet, etc when at the top of the editor.\nOperating system: Linux-5.3.0-7648-generic-x86_64-with-Ubuntu-19.10-eoan 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.79, 2.83, 2.90.0 Alpha\nWorked: unknown, possibly never.\n\nSeems like some animation files cause really poor performance in Dope sheet when trying to scroll on top of it. Scrolling down and making the top section not visible seems to fix the performance. \nI presume the editors draw keyframes for channels on top of each other without checking if the key already exists.\n[2020-07-16 17-54-48.mp4](2020-07-16_17-54-48.mp4)\n\n1. Open attached file\n[slow.blend](slow.blend)\n2. Try to click around on timeline, dope sheet editor.\n3. Open the key dropdown in dope sheet and scroll down. Notice how performance goes back to normal.\n\n", "Baking diffuse color takes a lot of time in version 3.0\nOperating system: Windows 10 64bits\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: 3.0, 3.0.1, 3.1\nWorked: 2.93.8\n\nIt takes longer time to complete bake diffuse color in version 3.0 compared to 2.93\n\n\n\n[Bake 2.93.blend](Bake_2.93.blend)\n\n[Slow_Bake 3.0.blend](Slow_Bake_3.0.blend)\n", "Blender editing performance with many datablocks\nEditing scenes with many datablocks can be slow, for example adding, deleting or duplicating many objects.\n\nAdding or deleting a single object has time complexity O(N), where N is the number of objects. This is due to unique name tests, looping over all datablocks to clear all pointers, and other operations that require accessing many datablocks. In general all such operations must become O(log(N)) or O(1), along with possible access of just the other datablocks linking to it.\n\nUndo push (#60695) and dependency graph rebuild are also O(N). We are not trying to improve those as part of this task, and note these can be run once after making many edits.\n\nPractical steps to reduce time complexity would be:\n\n* Store two-way links for all (non-COW) data-blocks, so that iterating over all datablocks that link to a given datablock is fast. There are transient data structures for this, but it should become permanent. Every `id_us_min()` and `id_us_plus()` should be turned into an operation that sets the datablock pointer and creates a link in the other direction as well.\n* Extend or modify datablock lists in `Main` to support quick testing for duplicate names.\n* Change view layer collection syncing to not require looping over all objects.", "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)", "Slower frame-change with many objects in the scenes collection\nWhen objects are in the scenes collection (instead of a sub-collection), changing frames using left/right keys is slower.\n\nThere is also a slowdown when animation playback restarts.\n\nThis occurs in 3.5x `ab63fe9eab8fd01d4a763199442987191d105c55` and 3.4x release.\n\nTo reproduce the problem:\n\n- With a new file paste the script inlined at the bottom of the report into a text editor and run it.\n- Press Spacebar in the 3D viewport to play back animation.\n- Note the FPS (~13.1 FPS here).\n\n- Start again, doing the previous steps with `USE_SCENE_COLLECTION = True` in the script.\n- Note the FPS is much lower (~3.46 FPS here).\n\n---\n\n#### Explanation\n\n- This is an issue I ran into when investigating why objects in collections were being re-populated during animation playback in some files, see !104553.\n- The cause of the problem is the scene is tagged by the depsgraph (see: `ANIMPLAY_FLAG_JUMPED`). _(note: the jumped flag is set when changing frame via arrow keys & when the animation restarts)._\n- When `ANIMPLAY_FLAG_JUMPED` is set `scene` is tagged with `ID_RECALC_FRAME_CHANGE`.\n- This causes the scene to be copied (see `blender::deg::deg_update_copy_on_write_datablock`).\n- The `scene->master_collection` is copied (non recursively).\n\n - When `scene->master_collection` contains many objects, copying has a noticeable performance penalty.\n - When it only contains some collections, the problem isn't noticeable.\n\n#### Other Notes\n\n- This is mainly noticeable when loading files pre 2.8x which load objects directly into `scene->master_collection`.\n- This report mentions animation playback speed because it's easily measurable, however many other operations trigger this (left/right arrow keys to change frames, every update when dragging scene number buttons \"Sampling\" (Render or Viewport) for e.g.).\n- In the test script the start and end frames are the same to so the playback is continually restarting to accentuate the problem and match the slowdown from changing frames via arrow keys.\n\n---\n\nThis script adds many objects to the factory settings file, hides them, adds some keyframes to the Light and sets the 3D viewport full-screen, ready for animation playback.\n\n\n```python\nimport bpy\n\nUSE_SCENE_COLLECTION = False\nOBJECT_NUMBER = 20_000\n\ndef objects_create(object_num):\n objects = []\n new = bpy.data.objects.new\n for i in range(object_num):\n objects.append(new(hex(i), None))\n return objects\n\n\ndef objects_collection_link(collection, objects):\n link = collection.objects.link\n for ob in objects:\n link(ob)\n\n\ndef main():\n from bpy import context\n\n bpy.ops.wm.read_homefile(use_factory_startup=True)\n\n if USE_SCENE_COLLECTION:\n collection = context.scene.collection\n else:\n collection = context.collection\n\n # Keyframe the lamps location, this is important as without this\n # the scene is not considered \"animated\".\n ob_lamp = bpy.data.objects[\"Light\"]\n ob_lamp.keyframe_insert(\"location\", frame=1)\n\n # The short frame range shows the problem most,\n # as this tags the scene to be tagged to update on frame-change.\n context.scene.frame_start = 1\n context.scene.frame_end = 1\n \n # Attempt max FPS.\n context.scene.render.fps = 1000\n\n objects = objects_create(OBJECT_NUMBER)\n objects_collection_link(collection, objects)\n \n # Hide everything, except the lamp.\n bpy.ops.object.select_all(action='SELECT')\n window = bpy.data.window_managers[0].windows[0]\n area = next(area for area in window.screen.areas if area.type == 'VIEW_3D')\n \n # Hide needs an 3D viewport (but select doesn't, hrm..).\n with context.temp_override(window=window, area=area):\n bpy.ops.object.hide_view_set(unselected=False)\n ob_lamp.hide_set(False)\n \n # Fullscreen 3D view (rule out slowdown from drawing other areas).\n with context.temp_override(window=window, area=area):\n bpy.ops.screen.screen_full_area()\n \n\nif __name__ == \"__main__\":\n main()\n```\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", "Regression: Texture slots thumbnails in Texture painting mode are missing\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\nCaused by 8b7cd1ed2a\n\nTexture slots thumbnails in Texture painting mode are missing\n\nIn Texture Paint mode, create texture, begin to paint, save texture and blender file. In the active tools panel>Texture Slots, the texture appears as a generic icon and its name, in 2.90 there was a thumbnail of the created texture instead of a generic icon.\n\n\nimages for reference:\n\n\n", "No preview icon in the material list\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 536.40\n\nBroken: version: 3.6.1\nWorked: (unknown)\n\nI noticed that for this material in the list it is not previewed, but in the \"Preview\" panel the preview is correct.\nThis is a simple setup of mixing 2 shaders using the \"Alpha\" attribute as a factor.\nThis situation makes it difficult to work when only using the drop-down list of materials in various situations..\n\nThx.\n\n", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "Lag on moving mesh elements in edit mode with skin modifier\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: 3.4.0\nWorked: nothing\n\nIn edit mode if object has a skin modifier and visibility of modifier is set for edit mode, a performance drop is seen on moving mesh elements in edit mode\n\n- Open attached file\n- Switch to edit mode\n- Select all vertices and move them\n[untitled.blend](untitled.blend)", "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" ]

[ "Extremely slow preview icon loading\nOperating system: Linux-4.15.0-54-generic-x86_64-with-Ubuntu-18.04-bionic 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 410.48\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nLoading preview collections is extremely slow. \n\nAny add-on which uses preview_collections to load previews grinds to a halt. I've tried Extreme PBR2.0 and Easy HDRI. I reverted the following two patches and the problem seemed to go away:\n\n9656ad91a39e496ce15233d049dccdf6721a89c2 (HEAD -> test) Revert \"Previews: delay icon preview renders a bit for smoother interaction\"\n390ca39cc50b506c49db23f33efa21be570f6ed9 Revert \"Fix #66230: delay in the material preview panel after recent changes\"\n\n\n" ]

[ "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\n\n", "compositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: (4.0 alpha from a few weeks ago not sure of version as deleted now)\n\nCompositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.\n\n1. Open a new blend file.\n2. Go to the compositor.\n3. Drag in the image file attached below.\n4. Connect the resulting image node's 0_Image output to a viewer node and turn on the backdrop.\n5. Image will be shown.\n6. Now place a blur node between the image node and the viewer node.\n7. Set the x and y values of the blur node to 1 and the size to 1.\n8. Image will blur.\n9. Now change the blur mode to fast gaussian.\n10. Image will go completely black.\n\n[test-image](https://projects.blender.orgattachment)", "Pixel Smearing in Compositor when using image node (image node lacks interpolation setting [in comparison to texture nodes])\nOperating system: Windows 10\nGraphics card: NVIDIA Quadro RTX 4000\n\nBroken: 2.79b , v2.83.8\nWorked: none known\n\nWhen an image is brought into the compositor and mixed with the scene, the result can be \"half pixel smeared\" depending on the even/odd pixel relationship between the image and the scene. It appears that some interpolation is happening on the image node's result in order to reconcile it with the center of the scene size, but this is undesirable as it breaks images that are intended to be pixel-perfect. \n\nAttached is a very simple, lightweight example .blend file (2.8) that contains 4 small example images (these images have dimensions 16x16 pixels, 15x16, 16x15, and 15x15).\nThese images exist as image nodes in the compositor.\nRender the scene, and then move the viewer node to the various outputs indicated to see how the resulting images have been smeared.[PixelError.blend](PixelError.blend)\nWhen these images are mixed with the scene, the resulting pixels from the small images will be smeared if there is a mismatch between the even-ness and odd-ness of the number of pixels in the image, and the number of pixels in the scene.", "No visible mesh on Viewport Screenshot in sculpt mode with Multires\nOperating system: Linux-6.2.11-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.36 64 Bits, X11 UI\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhat the title says.\n\n- Add a cube\n- Enter sculpt mode\n- Add a multiresolution modifier and subdivide\n- Use the operator: Header -> View -> \"Viewport Render Image\"\n\n", "Autoscroll not working in lists that can be text searched (template_ID), works in others (e.g. template_node_view)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.4.0\n\nUnlike other similar places in Blender, the Scenes list does not autoscroll when hovering the mouse over one of the direction triangle icons.\n\n\n\n\n", "`bpy.context.space_data.overlay.grid_scale` returns inconsistent view3D grid scale in multi-view\nOperating system: win 10\nGraphics card: RTX 3090\n\nBroken: This was observed in 3.5 alpha but I don't think that is relevant \nWorked: N/A\n\n`bpy.context.space_data.overlay.grid_scale` does not apply to multi-view functionally, and any interaction with the 3D navigation sphere only effects the main window portion of multi-view.\n\nSee attached video for a demonstration of some of the odd behavior.\nSee attached blend to reproduce the error.\n\nEnter multi-grid view: **ctrl+alt+q** (mismatched transform grid) The main window is top right.\nClick any axis sphere in any 3D view that isn't the top right quadrant, only the main window transforms.\nYou will also notice that the main window also inherits the grid scale of the multi-view windows.\n\nPlaces to look maybe? [A](overlay_grid.cc#L86) [B](space_view3d)\n\n", "Applying mirror modifier doesn't work with mesh-deform data\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Beta\n\napply the mirror modifier while is used with the multiresolution produces artifacts.\n\nopen the attached file and apply the mirror modifier.\n\nThank you\n\n\n\n[multires_err.blend](multires_err.blend)\n\n", "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty.", "File Output nodes output gets overwritten by \"standard\" output (if the same filename is used)\nI have a scene with simple animation. \nI'm rendering muilti-layer open exr with an composite output node with the passes as in them. \nThe standard file 5 year old output bug is still here, where your file saves twice, once from the main file output tab and again on your composite output, normally I don't care whatever, it will just overwrite and I'll end up with one file. \n\nAfter setting up my render output with all the layers I want, normally I just let the overwrite button on regular output be set and it's fine. However all my passes in the exr file were changed to VeiwLayer.(pass), and I'm missing passes like image and alpha or others I might composite into the composite output node. \n\nMy work around is to make the file name something different than my composite output vs the normal file output name. \nBut now I'm saving twice and having to deal with deleting 100s of gigs of junk EXR files from the main file output tab. \n\nIf you render one frame from the file I uploaded, then drop it into a compositor like nuke, fusion or cough cough AE, you'll see the passes are different. \nP.S. You can kill the textures, sorry I didn't pack them for size sake\n\nThank you\n\nblender 3.6 \nFile SYS - (although it seems to be the case on multiple machines, so I thinks it's just an overlook bug): \nryzen 9 5950x\n128 gigs ddr4\nrtx 4090\n\nAnd \nM1max 64 gig integrated\n\n", "Grease pencil scale issue\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0\n\n\nGrease pencil seems to deteriorate as the scale of a camera increases\n\nIn the attached file I created a door object with a central thinner panel. I then created an orthographic camera at ortho scale 1 in plan view and set the near clipping plan to about the middle of the door in the Z axis. I added a Grease pencil scene Lineart object an placed it in it's own collection to aid turning it on and off and set the style thickness to 1 in the modifier tab. The resulting lineart works fine. I then duplicated the camera and changed its orthographic scale to 2 which also works fine. I repeated this at orthographic scale 3 and again at 4 where the resulting lineart starts to break down. at orthographic scale 20 the issue is very apparent. If I am working on a large scale scene I obviously need to have my orthographic scale high. Please advise if there is a way of increasing the orthographic scale without losing the line art quality.\nThanks\n[Greasepencil_scale_bug01.blend](Greasepencil_scale_bug01.blend)\n\n\n\n\n", "MetaData of multilayer EXR not shown in UV/Image editor\nversion 2.74 (sub 5), branch b'master', commit date b'2015-05-28' b'20:10', hash b'3511e2d', b'Release'\nbuild date: b'2015-05-29', b'04:10:03'\nplatform: b'Linux:64bit'\nMetaData not stored into EXR (multilayer)\n\n\nLoad a rendered openEXR-multilayer into image editor, check \"Draw Metadata\" and nothing info appear.\n\nWorks fine with \"plain\" OpenEXR\n\nDaniel\n", "Different extrude operations use the scale of the object differently\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.4.0, 2.93\nWorked: - never?\n\nThe four different extrude operations (avaliable on the Alt+E menu) can take or not the scale of the object in consideration when applying the command.\nThe screenshot below, in which all objects were originally simple planes scaled by 2 (in object mode), shows the difference between the operations when trying to extrude it by 1 meter.\n\nAs shown, the \"Extrude Faces Along Normals\" and \"Extrude Individual Faces\" use the scale of the object, resulting in a 2 meter extrusion, which is not the intended value of 1 meter.\nGiven that most actions in edit mode don't take the scale of the object into consideration, I believe these two operations cited above are a bug.\n\n- Using a plane, scale it by 2 (or any number different than 1) and copy it 4 times.\n- In each plane, extrude it by the same amount (i.e. 1 meter), using a different extrude operation given by the Alt+E menu.\n- You should notice the \"Extrude Faces Along Normals\" and \"Extrude Individual Faces\" operations will interfere on the extrusion amount given.\n\nThe result should be the same as the screenshot above and can be checked in the file below:\n[Extrusion Bug Report.blend](Extrusion_Bug_Report.blend)", "Unable to output pictures correctly when rendering version 3.2 demo with 65536*65536 resolution\nOperating system:win11 -workstationedition\nGraphics card:4090\n\nBroken: 3.4.0 release\nWorked: \n\nUnable to output pictures correctly when rendering version 3.2 demo with 65536 * 65536 resolution.\nWhen nearly 4 hours of rendering ends, blender does not work any picture out, as the picture atteched. And the image attribute say this image is 32768 * 32768.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nusing the dome file for blender3.2\n\n", "Image.save_render saves OpenEXR Multilayer as a regular OpenEXR with no layers\nOperating system: Windows 10\nGraphics card: (2x) NVIDIA GeForce GTX 1070\n\nBroken: (2.80 release)\n\nWhen exporting a **Multilayer OpenEXR** file using Blender's Python API and the [bpy.types.Image.save_render ](bpy.types.Image.html?highlight=save_render#bpy.types.Image.save_render) function, the image is exported as a **regular OpenEXR** file with neither layers nor passes.\nThis is NOT an issue with the way Blender reads Multilayer OpenEXR files because exploring the EXR files with other software yields missing layers and passes as well.\n\n1. Download and open the attached .blend at the bottom of this file (openexr_bug_24_10_19.blend)\n2. Note that there are multiple passes being rendered (Combined, Z, Mist, etc.) and there are also multiple layers being rendered (View Layer and Composite)\n2. Click \"Run Script\" in the text editor. This script will render an image, configure its output settings to be a Multilayer OpenEXR, then write it to the same directory that the Blender file is in.\n3. Import the exported OpenEXR (named \"script_output.exr\") into Blender's compositor either by clicking and dragging it in, or by opening it in an image node\n4. Note that the image is missing the extra layers that should be included (Normal, AO, Mist, etc.)\n\nIt may be useful to note that if you actually tear apart the exported OpenEXR file, the only channels included are 'R', 'G', 'B', and 'A'.\n\n**Expected behavior, for comparison**\n1. In the Image Editor with the rendered image, select Image > Save As and save it somewhere using the settings detailed in the script (Multilayer OpenEXR, RGBA, 32-bit depth, No Codec)\n2. Import the saved OpenEXR in Blender's compositor either by clicking and dragging it in, or by opening it in an image node\n3. Observe how there is an additional \"Layer\" option in the image node, and depending on the layer that is selected, different passes appear as outputs from the node\n\nIt may be useful to note that if you tear apart this OpenEXR file, the channels included are: 'Composite.Combined.R', 'Composite.Combined.G', 'Composite.Combined.B', ... all the way through all of the image layers and passes.\n\n**Included Files**\n[openexr_bug_24_10_19.blend](openexr_bug_24_10_19.blend)\n", "OpenEXR can't be used to save results during the render process\nOperating system: XUbuntu 20.04\nGraphics card: Not applicable\n\nBroken: Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nWorked: Blender 2.93.7\n\nSeems OpenEXR now can't be used to save intermediate results during rendering using Cycles. The other formats (like PNG) seems works just fine. Blender starting v3 just crashing if you trying to save as single or multi-layer EXR. When the render is completed the `save_render` function is working correctly.\n\nThis bug doesn't allow to prepare the proper distributed preview for user outside of Blender UI (EXR needed to merge multiple preview samples from the remote workers).\n\nThe default cube blender scene is just enough to reproduce. Please switch to script console and paste the next code:\n```\nbpy.context.scene.render.engine = 'CYCLES'\nbpy.context.scene.render.image_settings.file_format = 'OPEN_EXR' # OPEN_EXR_MULTILAYER here will fail too, but PNG for example will work just fine.\nbpy.context.scene.cycles.use_adaptive_sampling = False\nbpy.context.scene.cycles.samples = 512\n\nbpy.ops.render.render('INVOKE_DEFAULT', use_viewport=True)\n\nimport time\ntime.sleep(2)\nbpy.data.images['Render Result'].save_render('_preview.exr')\n\n### Crash will be right here ###\n\nimport os\nprint(\"Preview file exists:\", os.path.exists('_preview.exr'))\n```\n\nCrash report: [blender.crash.txt](blender.crash.txt)\n" ]

[ "Pixels and resolution not for multilayer EXR and Render Result\nCentOS - GTX 1070\n\n2.79\n\nPixels and resolution are not available with multilayer EXR or Render Result images.\n\nimport bpy\ndata = bpy.data\nimage = data.images['Render result or multilayer EXR']\nprint(image.pixels) # length is 0\nprint(image.resolution) # return always Vector((0.0, 0.0))\n\nIt is working with regular EXR file.\n", "image pixels unavailable from python if multilayer EXR\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\n\nDesperately need the ability to modify multilayer exr files from python so I can implement some machine learning functionality into an addon. Although Blender uses the OpenEXR module, no python bindings are shipped with blender, and when using image.load(), the image pixels are blank/unavailable from python when loading in multilayer EXRs.\n\n\nGo to the python console and type:\n```\nimg = bpy.data.images.load('PATH TO MULTILAYER EXR')\nfor i in img.pixels:\n print(i)\n\n```\n\nI'm a financial supporter of the Blender development via the development fund, but mostly from addon sales. Could someone do what's necessary to make it possible to read and write to multilayer EXR's from python? Perhaps adding the python bindings for the OpenEXR already in use by Blender would be possible? It would open up a whole host of possibilities in the absence of any ability to modify render result pixels pre-file write.\n\n\n" ]

[ "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}", "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)", "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", "Preset icon overlaps panel header text\nOperating system: Mac 10.9.5\nGraphics card: Macbookpro NVIDIA GeForce GT 750M 2048 MB\n\nBlender 2.8 downloaded today\n\nIn movie editor\nthe text tracking settings is somehow mixed up with a button.\nI can sent a pic if you want.\n\nI am a amateur and English is not my first language, so i'm very sorry if i've wasted your time.\n\nGreetz \nLes", "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.", "CYCLES: Surfaces inside volumes are Not Lit or Shadowed by the volume if the volume is not visible to Camera Rays\nLinux Mint Mate\nGTX 1050\n\n\nBlender 2.81 Alpha\n2019-09-27 22:44\nHash: 1c1a3198af9d\n\n\nDiscovered while trying to catch shadows from volumes on surfaces for compositing.\n\nSurfaces inside of volume meshes are not shaded (lit/shadowed) by the volume if the volume is invisible to camera rays\n(checkbox in Object Properties -> Visibility -> Ray Visibility -> Camera)\nAs far as i can tell this also affects Holdout.\n\n\n\n\nCurrent workaround: make sure volume IS visible to camera rays, and instead bypass it in the volume shader using the Camera Ray socket on the Light Path node\n\n\nTo Reproduce:\n\nOpen attached .blend , press render\nNote the missing shadow/light where the volume cubes intersect the default cube.\n\nI have in the .blend also included the \"expected behaviour\" by using the workaround, switch the Scene from \"Bug\" to \"Workaround\" and press render again.\nNote the shadow/light now covers the default cube properly.", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Blender Interface Does Not Respect Windows Colour Profiles\nOperating system: Windows 10 Home 1909\nGraphics card: Nvidia GTX 1080\n\nBroken: 2.83.0 on Windows\nWorked: 2.83.0 on OSX\n\nBlender's interface shows incorrect colours on high colour gamut monitors in Windows 10. Any monitor over 100% sRGB is showing colours to be incorrectly vibrant in every panel, including image viewer, 3D view and compositing.\nThis is believed to be due to Blender failing to reference the OS's installed ICC/ICM profile, or the interface entirely lacking any colour management that respects monitor profiles.\nSince OSX has system-wide colour management, this issue is not apparent. Windows does not have system-wide colour management, and apps must perform their own referencing of the installed ICC/ICM profile.\n\nOpen Blender on a high-gamut monitor in Windows 10. Compare to sRGB 100% monitor or OSX.\nError initially produced on a Dell UP2516D high-gamut monitor.", "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", "Dual monitor issue\nOperating system: macOS-13.2.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.5.0\n\nUsing a new Mac Mini Pro with single monitor (Apple Studio Display), Blender 3.5 is very fast.\nAdd in a second Studio display and the interface becomes 'clunky', contextual menus take sometimes 2 or 3 seconds to appear, playback is jerky. \n\nTried various settings in preferences but no change. Unplugging the second monitor returns good performance...\n\nUodate:\nSetting 'GPU Backend' to 'OpenGL' improves things a little...\n\nUpdate-2:\nVersion 3.4.1 seems to have similar issues\n\nUpdate-3\nI seem to have solved some of the issue..\nThe Apple Studio Displays have 4 input ports, one Thunderbolt port and 3 USB-C ports.\nThe external display was plugged into one of the USB-C ports.\nSwapping input to the Thunbderbolt port seems to speed things up.\nStill a lot of lag on contextual menu pop-up,and selection box drag out.\n\nUpdate-4\nSo it tried reducing the Blender window to 1/4 screen, Blender becomes smooth again.\n\nI then methodically made it bigger and bigger until the latency suddenly reappears.\n\nProvided I leave around 15mm of gap around the edge of the Blender window with the desktop peeking around the edge, Blender stays very smooth.\n\nPull it a bit further out and the latency returns.\n\nIt can’t cope with absolute full screen, knock it back 5% smaller and it’s fine.\n\nWeird!!\n\n\n\n", "Material setting \"show_transparent_back\" (Show Backface) gives weird results\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nMy materials are messed up by having blend mode set to \"Alpha Blend\" and \"Show Backface\" set true.\n(The checkbox for \"Show Backface\" pops up if a materials blend mode is set to Alpha Blend\")\n\nIs this normal behaviour?\nThe intend here was to see every side of the cube with a bit of transparency.\n\n[ShowTransparentBackBug.blend](ShowTransparentBackBug.blend)\n1. Add a Cube (subdivide a few times) and give it a material\n2. Go to material settings and set the materials...\n- Blend mode to \"Alpha Blend\"\n- Backface Culling to False\n- Show Backface to True", "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", "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.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.", "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(" ]

[ "MacOS interface bug\nHi! \nI'm very new to Blender, but as soon as I've installed it on my MacOS 10.13.3 High Sierra, the interface of the whole application seems to appear with a bug. \nAll buttons and menus are sliced in half from top left to bottom right, with some one part transparent one opaque. Every single button and menu seems to be that way which makes it unintelligibly and confusing, impossible to work with. \nWhat can be wrong? \nBlender version 2.90\nScreenshot: \n\nThank you in advance for your help.\n\nHardware specs: Macbook Pro (13-inch Late 2011) 2.4 GHz Intel Core i5 \n8 GB DDR3,\nIntel HD Graphics 3000 512 MB \n", "Issues in Blender 2.91 using a MacBook Pro 2011 with High Sierra\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel HD Graphics 3000 OpenGL Engine Intel Inc. 3.3 INTEL-10.4.14\n\nBroken: version: 2.91.2\n\nThe problems it presents are the following:\n- When starting Blender, it takes about 2 minutes without showing anything (it seems very strange to me because I have an SSD and in the computer I used before, a HDD, it did not take more than 15 seconds)\n- ALL the interface is shown corrupted with a diagonal line that cuts the text box, showing half. I already tried changing the language. It does not work.\n- The interface is very lageada, no matter what you are doing (so it is not that the mac \"does not run\")\n- In Eeve, the shadows are very dark, and sometimes they turn to different colors, blue or green. If I activate the bloom they glow. This does not happen in Cycles, only in Eeve.\nTest with various versions of Blender over 2.8. In all of them the same problems are presented, except in 2.80. In this version the shadows are displayed correctly and the interface is fluid, but the text and boxes still have the problem of the diagonal line. I would greatly appreciate any help.\n\n\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", "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.", "Outliner Floating window Drag & Drop to Geometry Nodes editor not working\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: I don't know if it ever worked\n\nDragging and dropping objects from the outliner to the geometry node editor is not working\n\nFloat outliner to be its own window\ndrag and drop an object from the node editor to the geometry nodes\ndoesn't work.\n\n", "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.", "Outliner displays non existing Screens.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.3 26.20.13001.18009\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nOutliner displays non existing Screens.\n\nThey exist in default blender workspace, however opening any editor in separate window with Shift and closing that window will create same thing, they wont be removed after saving and reopening file either.\n\n\n", "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).", "Graph Editor Expand/Collapse Channels collapsing issue\nOperating system: Linux-5.8.4-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: never\n\nOnce Collapse/Expand Channels operator has been used with the All option turned OFF, then the All is turned ON again for Collapse, a following Expand Channels operation will not work anymore\n\n[#80753.blend](T80753.blend)\n- Open above .blend\n- `Collapse Channels`, in the `Redo Last Operation` panel turn OFF `All`\n- `Expand Channels`, in the `Redo Last Operation` panel turn OFF `All`\n- `Collapse Channels` again, in the `Redo Last Operation` panel turn ON `All` again\n- `Expand Channels` will not expand to selected channel anymore\n[T80753_bug.webm](T80753_bug.webm)\n\n", "Blender Crash by doing 2d animations\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 500 Intel 4.5.0 - Build 31.0.101.2111\n\nBroken: version: 3.6.0\n\nWhenever I draw with a line, circle, arc, curve, interpolate, and box tool, my drawings disappear and reappear and then it suddenly crash.\n- 2D animation Draw Mode\n[\nPlease describe the exact steps needed to reproduce the issue]\n\n", "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", "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)", "Linking/Moving collection to another scene messes with the object visibility.\nOperating system: Windows 11\nGraphics card:\n\n**Blender Version** \nBroken: 9719fd696488\n\n\n\nThere is no reason the object visibility should not be carried over when the collection is moved or linked to another scene.\n\n\n[blender_HRo7zHHvN3.mp4](blender_HRo7zHHvN3.mp4)\n\nload the attached .blend\n\nselect the TEST collection in scene.A\n\nleft click drag onto scene.B while holding ctrl to link the collection instead of moving it. Moving the collection has the same affect\n\nopen scene.B and check the visibility\n\n\n\n[tests_06122022_1933_13.zip](tests_06122022_1933_13.zip)\n", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Disabling Collections in the Outliner filters overlaps the Mode Column icons with the expansion arrows\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIf you disable the \"Collections\" filter in the Outliner, the space of the Mode Column disappears even if the \"Show Mode Column\" filter is enabled, and the icons of the Edit Mode Column overlap with the object expansion arrows.\n\nAdd any mesh object, disable the Collections filter in the Outliner, enter edit mode.\n", "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", "Node Panels Polishing\n- [ ] Support A to expand/collapse panels.\n- [ ] Support Ctrl+click to isolate panel.\n- [ ] Support dragging all panels to collapse/expand them.\n- [ ] Use the horizontal padding vertically:\n\nBefore:\n\n\n\nAfter:\n\n\n\n---\n\n- [ ] Don't space out socketes when hiding the node\n\n\n- [ ] Bug, hide panel when all its sockets are hidden with Ctrl+H\n\n" ]

[ "I can´t collapse the collections\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 880M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 13)\nWorked: (optional)\n\nThe colecctions do not collapse\n\nOpen blender, create a collection and a few more inside of the first one, and the collapse arrow dont works\n[collections do not collapse.blend](collections_do_not_collapse.blend)\n\n\n\n" ]

[ "VSE: No simultaneous strip snapping on left & right side [and right side favoured]\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\n{[F10300365](no-dual-strip-snapping.png),size=full}\nA strip in VSE cannot snap at left and right ends simultaneously. Annoying when the end that does not snap is the end that you're wanting to know the orientation of (especially when you're zoomed out and can't tell by eye). \n\nFurther to this, the right side snap will always prefer over the left. It seems it just searches the right side first, and if it snaps it just doesn't check the left side at all. I would find it very odd if dual snapping isn't intended, but if somehow there is no plan to add it in the near future, at least the behaviour should not prefer one side - like maybe prefer the side based on the direction the strip is dragged or something (snap first to the side of the direction the strip is heading?).\n\n[strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred.blend](strips-do-not-snap-at-both-ends-simultaneously-and-right-side-is-preferred.blend)\n- Open the blend file, and drag colour strip along x-axis\n- Only the right end will snap, despite both ends clearly lining up with the metastrips\nNOTE: There is a reason I used a metastrip as the snap-to strips here, as there is another snapping bug I will be filing soon (and I didn't want that bug to mess up the behaviour in this one).\n", "No field in theme editor for \"World\" channel in NLA editor window\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.1 Release Candidate\n\nThere doesn't seem to be any way to edit the colour of the \"World\" channel in the NLA editor, it's always the default pale grey/blue with no way to change it as far as I can see in the Themes preferences.\n\n\nIn Blender Preferences - Themes tab - Nonlinear Animation dropdown - there is no colour picker for the World channel.\n", "Transform Node Messes Up Alpha Channel Manipulation\nArch Linux\nNvidia 750ti\n\nBroken: 2.79 (Tried 2.8 as well and I have the same issue)\n\nAs referenced here:\n4\n\nWhen I take an image in the compositor and scale it up 2x or whatever and then separate the RGBA and dilate/erode the alpha and use that to set the alpha on the image, it only works within the size of the original image and not the scaled up image. Also even if I use the R, G, or B, it still only uses the size of the original image and not that of the scaled up one.\n\n\n\nCropped if I try to mess with the alpha after a transform.\n\n\nUncropped if I mute my changes to the alpha.\n\n\nAlso I believe that if you scale down\n\n[dilatecropissue.blend](dilatecropissue.blend)\n", "Crash 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", "Render with negative color values results in broken .hdr file (possible underflow error)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.3\nWorked: ?\n\nWhen rendering an HDR image that contains negative color values (for example from a world shader with negative values), the saved .hdr file has visual artifacts and does not look correct at all when opened in any external software (e.g. RenderDoc, any online HDR viewer, or even as input for [cmft](cmft) for creating SH coefficients for irradiance).\n\nWhen clamping the shader's output values to [0, 1] (or any other number > 1 instead of 1), the .hdr file looks correct, so my guess is that there is an underflow error somewhere that leads to invalid values in the HDR file. As far as I'm informed, radiance HDR files don't contain negative lighting information, so the output should be automatically clamped to non-negative values.\n\n**Render without clamped values:**\n\n\n**Render with values clamped to above 0:**\n\n\nPlease note that the displayed render output in Blender looks the same in both cases, this issue is about the exported file.\n\nExample file:\n[HDR_negative_values.blend](HDR_negative_values.blend)\nRender the image and save as `Radiance HDR`.\n\nThe incorrect .hdr file:\n[test.hdr](test.hdr)\n\n", "NLA: Action Track Hold Forward Inconsistency\nBug Report: #66946 (NLA strip unexpectedly auto-switching from Hold to Hold Forward)\n\n**Problem:** For the Action Track (non pushed action), extrapolation `None` and `Hold` is respected but `Hold_Forward` is not. It's a source of confusion. \n\n**Solution:** [Originally proposed by angavrilov]]. We treat extrapolation `Hold_Forward` as bounded on the left and infinite on the right.*FModifiers note:*It's important to note that the Action Track does not evaluate the same as normal strips which is [[https:*developer.blender.org/T66946#723602 |intentional](https:*developer.blender.org/T66946#724251). FModifiers will affect the track's boundaries so keyframes don't necessarily define the Action Track's evaluation bounds. So adding a default cyclic modifier to channels effectively makes the Action Track's evaluation bounds infinite. Even extrapolation `None` in this case appears to not work properly. This behavior is still intentional even though it appears broken. The user-side solution is to restrict the modifier's frame range. ", "Node frame grid alignment issue\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nNode frames shift contents out of grid alignment when transformed.\nMy understanding is that the frame borders are not multiples of the grid spacing, so whenever the frame is transformed and snapped to the grid, its contents are yanked out of alignment with the grid. Moving the contents back into alignment on their own works, but any further transforming the encompassing frame will yank them out again. Perhaps making the frame border an exact multiple of a grid unit could fix this.\n\n1. Try moving the convex hull node. Observe that it stays aligned with the grid\n2. Try moving the frame around it. Observe that it snaps to the grid, and the convex hull node is now unaligned with the grid\n\n", "Geometry Nodes Inputs `is_animatable` Property Incorrectly Returns False\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0 Alpha\n\nGeometry Nodes inputs' context menus ([WM_MT_button_context ](bpy.types.Menu.html#extending-the-button-context-menu)) incorrectly show the inputs' `is_animatable` property as `False` when the property does accept keyframes (see screenshot, attached).\n\n\n - Open the attached .blend file (attached, below)\n - Run the script in the Text Editor\n - Right-click the Input property of the Cube's Geometry Nodes Modifier\n - Open the System Console to see the `is_animatable` property of `context.button_prop` is `False`\n[is_animatable.blend](is_animatable.blend)", "Autoscroll not working in lists that can be text searched (template_ID), works in others (e.g. template_node_view)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.4.0\n\nUnlike other similar places in Blender, the Scenes list does not autoscroll when hovering the mouse over one of the direction triangle icons.\n\n\n\n\n", "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "Impossible to move with G key an object scale to 0 and parent to an empty\nOperating system: Windows 7\nGraphics card: GTX 780\n\nBroken: 3.5.1\nWorked: \n\nWhen an object is parented to an empty, and this object is scale to 0, you cannot move it anymore with the G key. But you can move it in the transform menu location.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open blend.\n2. Try to move object with G key.\n3. It is possible with Transfom menu.\n\nThanks a lot !\ndono", "Greasepencil operators (e.g.bpy.ops.gpencil.stroke_join) fail when running outside the 3Dview\nOperating system: Linux, pop-os 20.04\n\nBroken: 2.91.0 Alpha\n\nbpy.ops.gpencil.stroke_join operator fails ( but returns {'FINISHED'} without error ) when executed from a python script or the build-in python interpreter.\n\nThe operator works fine from the GUI\n[Bug_reproduce.mp4](Bug_reproduce.mp4)", "Update animation operators for previously hidden redo panel contents\nWith the changes in [D14960](D14960), many operators that had previously hidden options are showing their redo panel.\nThis applies to the timeline editor, dopesheet (all modes) and NLA editor.\n\nI tested all operators in each editor to find out which ones need changes. The following list is complete, meaning that any operator that is not listed here works as expected when tweaked:\n\n# Dopesheet\n\n- - [ ] Transform\n - Hide W axis\n - Not sure how to do this for `transform.transform` with `TIME_TRANSLATE`\n- - [x] Box Select\n - Hide redo panel (it never shows in 3d view)\n- - [x] `select_column`\n - Hide mode selector (the modes are very distinct from each other, and don't make sense to be changed by the user)\n- - [ ] `leftright`\n - Hide the \"Check if Select Left or Right\" mode\n - Does not seem like you can hide enum entries, so this may have to be split into a separate property\n\n# Markers\n\n- - [x] Holding select (rightclick)\n - Hide redo panel\n- - [x] Move\n - Hide tweak checkbox\n- - [x] Select before/after\n - Capitalize parameter names\n- - [x] Box Select (see Dopesheet)\n\n# NLA Editor\n\n- - [x] Duplicate\n - [D15086](D15086) fixed the issues related to the duplicate operator\n- - [x] Push Down Action\n - Hide redo panel (seems to be an internal property not worth changing)\n- - [ ] Transform (see Dopesheet)\n - Additionally, the Proportional Editing property can not be toggled (probably since the NLA editor does not have this option at all), so the checkbox should be hidden\n- - [x] Box Select (see Dopesheet)\n- - [ ] `leftright` (see Dopesheet)\n\n# Graph Editor\n\nWhile not affected by the above patch, it's still worth touching up, since the original patch that added its redo panel [D6286](D6286) did not change related operators either.\n\n- - [x] Box Select\n - While we should hide redo panel for consistency, the \"Select Curves\" option may be interesting to toggle? But at the same time, it currently does not update, so needs to be fixed.\n- - [x] `select_column` (see Dopesheet)\n- - [ ] `leftright` (see Dopesheet)\n\n---\n\nA lot of operators would benefit from functional changes, now that the user can adjust their parameters not only through different menu items, but also by tweaking the settings in the redo panel.\nThis could be tracked as an additional to do task.", "'Flipped' in Graph Editor Redo Panel for Paste Keyframes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\nWorked: N/A\n\nWhen copying and pasting keyframes in the Graph Editor, the Redo panel has an option called 'Paste Flipped.' This is a highly-specific and confusing option.\n\n - Create an F-Curve with keyframes\n - Graph Editor Key Menu > Copy Keyframes\n - Graph Editor Key Menu > Paste Keyframes\n - Open Redo Panel\n # Enable and disable 'Flipped'\n\n**More Info**\nThe 'Flipped' option's description says that it pastes keyframes from mirrored bones if they exist. That is not at all my initial expectation of 'Flipped' in this context. I would expect the F-Curves to either be flipped on the X-axis or Y-axis in the Graph Editor. I would also expect 'Flipped' to work with all pasted keyframes: not just those of mirrored bones.\n\n\n\nFix: D14328", "GPencil: Add multiframe support to Move to Layer\n" ]

[ "Regression: The start frame of NLA tracks can not be negative.\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2070\n\nBroken: 3.3.0, branch: master, commit date: 2022-09-06 15:39\nWorked: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22\n\nCaused by bd00324c26\n\nTracks start frame can not be negative. I the track is moved left, as soon as its left bound reach frame 0, it stays stuck here and the right bound is shrunk down.\n\n- create a simple animation on an object\n- put this action as a track in the NLA editor\n- try to move this track to the left, past frame 0\n\nWorking version (3.2)\n\n\nBug (3.3)\n\n\nTest File\n[nla_track.blend](nla_track.blend)\n\nThis seems linked to this upgrade : rBbd00324c264c\n" ]

[ "Cycles fully transparent shader is brighter when a Clear Coat shader is behind it\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0 Alpha\nWorked: Never Worked\n\nWhen doing Decals, we often use alpha channel to define transparent area. However, I found when the Object's base color is above hsl(h,s,0.01), who's under the Decal, then the decal's transparent area will affect the underneath object's shading.\nMy test configuration is that 2048 viewport samples alongwith light bounces param all been set to 64.\nThe BUG is easier to notice when the background object is light grey, and the light is quite dimmed(or just turn down the exposure in colormangement to observe.)\n\n\n\n\n\nPlease open the attached Blend file to test.\n[Transparent shading BUG.blend](Transparent_shading_BUG.blend)\n\n", "Blender 3.6's window has 1/4 content area, 3/4 transparent area under Linux\nOperating system: Arch-based Linux, kernel 6.3.7-arch1-1\nGraphics card: Intel Arc A779\n\nBroken: blender-3.6.0-beta+v36.2ef27684c56c-linux.x86_64-release, but has happened with all 3.6 daily builds so far.\nWorked: 3.5.1, the latest version.\n\nThe content area is 1/4 of the window size when the window is first open. 3/4 of the window is transparent.\nGnome 44.2, Wayland, fractional scaling enabled (100%, 175%), dual monitors (1920x1200, 4K).\n\n\n\n\nRun Blender 3.6\n\n", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "EEVEE Holdout missing screen space reflections\nOperating system: windows 10\nGraphics card: rtx 2070 super\n\nBroken: 2.8.5\n\nscreen space reflections are not applied to an object from environment that has been held out using holdout button on collection. since the stuff is still there when holdout is applied to background, screen space should still be applied to objects that are not held out.\n\nhere is an example:\n\n\n\n[holdout ssr.blend](holdout_ssr.blend)", "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)", "Bump Map and Normal Map causes flat shading.\nOperating system: windows 10 1903\nGraphics card: 1080ti * 2\n\nBroken: 2.82.7 stable versioin\n\nThis issue appears both on eevee and cycles.\nWhile using smooth shading, simply add a bump map and the shading lookes flattened.\n\n\nThis problem will occur on a high poly model if the camera is close enough.\n\n\nBevel the cube with several segments and simply plug a bump map to the normal port of the shader node.\n\n[smooth shading issue.blend](smooth_shading_issue.blend)", "EEVEE-Next: Known Issues\nThis task lists the minor missing features that are known for not yet working with EEVEE-Next.\n\nPriority of each task needs to be assessed and assigned.\n\n# LookDev\n- [ ] camera world alignement isn't working.\n- [ ] blur background isn't working.\n- [ ] diffuse contribution isn't taken into account.\n\n# Shadow\n- [ ] big performance bottleneck caused by rendering method\n\n# Hardware support\n- [ ] Metal backend doesn't support shadow rendering and GI baking yet", "HDRI Preview Spheres appear in surface reflections\n\n\nBroken: version: 2.82 (sub 7)\nMaster\n\nWhen using material shading and overlays in the viewport, the gizmo at the bottom-left corner (sphere displaying the environment map used for preview) is reflected by shiny surfaces in the 3D world, despite technically being a part of the UI. Using the icon to show / hide overlays affects this, the reflection also disappears when overlays are hidden.\n\nShould work in any setup, if there are issues replicating this let me know and I'll extract the relevant part from my project's blend file. Just add a plane, lower its material roughness so it's shiny, move the view upward so the overlays appear under it, and you should see the strange reflection.\n\n\n\n[HDRI_reflected_in_viewport.blend](HDRI_reflected_in_viewport.blend)", "Cycles: tapering hair transparency fails in '3D Curves' mode [regression] (probably caused by embree)\nOperating system: Ubuntu 20 LTS and MacOS Mojave\nGraphics card: Quadro p2000\n\nBroken: 2.92 and latest 2.93.0 alpha 5f1f233dc97de34f6be0f51edd3cbf2d8247fbda\nWorked: 2.82a and 2.83.4\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nSetting a transparent BSDF shader to hair in 3D curves mode yields a visible error where parts of the hair are black.\nThis issue is visible in the viewport and at render time. It affects both CPU and GPU rendering.\n\nIn ribbons mode, transparency works almost as expected. I noticed that when hair strands overlap and they have transparency, they are not transparent but they take the background opaque color instead, so the hair strands below are \"covered\" with background color.\n\nembree\n\nbefore embree\n\n\n[#86500.blend](T86500.blend)\nOpen file and switch to rendered view\n\n---\n\nOriginal report:\n\nInitial setup in viewport: a cube with 20 hair strands:\n\n\nRender in version 2.83.4:\n\n\nRender in version 2.92+\n\n\n\nAttached is a .blend file example (so that you don't need to reproduce the steps below). [transparent_hair_curves_issue.blend](transparent_hair_curves_issue.blend)\nIf you run it on Blender 2.82a, rendering should show only a cube. Blender 2.92+ will show the issue.\n\nSteps:\n- Open a new default blender scene with a cube\n- Choose Cycles renderer\n- Under Render Properties > Hair, select 3D Curves\n- Add a hair particle system to it\n- Lower particle count to 10\n- Set segments to 5\n- Enable Hair Dynamics, play the timeline for a while until hair bends\n- Go to simulated frame 30 (just an example)\n- Scroll down in psys panel to Render, enable b-spline with steps 2\n- In Timing, set start to 0.361 (just for testing purpose)\n- In Hair Shape, set Diameter Root 0.5, Tip 1, Radius Scale 1.00\n- Render in viewport or to an image (same result)", "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)", "Visible density seen inside an overlapping volume with zero density value (Cycles)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.5.1\nWorked: Not tested on other versions.\n\nVisible density seen inside an overlapping volume with zero value (Cycles)\n\n\n**Steps to reproduce**\nOpen file and render. \nThe TestVolume_AllTransparent_Large_Test_1 object has 0 density, but it is visible in render\n\nNote: There are 3 different test collections that may or may not be result of same issue. More info [here](107418#issuecomment-931613)", "Black outlines around animated Objects when Scrubbing/Playback.\nOperating system: Windows 10 64 Bits\nGraphics card: GTX 1080 TI.\n\nBroken: version: 2.83.8 hash: 7c027f9480a9\nWorked: version: 2.83.4 hash: `abb7364912` (commit date: 2020-02-23 23:00)\n\nThere are some weird black outlines popping out during anim playback or scrubbing. \n\n***P**\n{[F8400153](spot.jpg) size = full}\n\n\n* open the file\n* If it is not already set, set viewport shading to material preview (that's where you can easily spot them)\n* playback the animation or quickly move the object\n\nThe black outlines will appear but the moment you stop they'll disappear, so you can screen capture the moment to check their existence ***P**.\n\n[Black.blend](Black.blend)\n", "Volumes look much much different in master compared to 2.79b\nWindows 10 pro x64\nGTX 970\nThread Ripper 1950x\n\n\n\nBasic volume shader with noise texture from build bot today doesnt look the same as 2.79b\n\n\n\n[untitled.blend](untitled.blend)\n", "Shader color affects Shadow Pass in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.1.0\n\nShadow Pass is not working as it should in Cycles. It somhow works much better in EEvEE (altough other problems arise).\n\nEasiest setup is just adding a plane, a sphere and setup cycles as a render engine.\nActivate **Shadow Pass** (not the Shadow Catcher Pass).\nDo an image render and everything works, more or less, as expected. So you get as a result a Black and White image (right side) where black is shadow and white is none:\n\n\nBut, as soon as you texture the objects with any image you get the darkest areas of those images in the Shadow pass (something like if one of the rgb channels is leaking to the final image):\n\n\nI have already tested it in Blender 2.83, 2.93, 3.1, 3.2 and 3.3 alpha and I have got always the same behaviour... so no idea if it ever worked or not as it should do. Right now it is absolutelly useless as you can't compose it without textures afecting the masked shadow.\n\nAs I said I already tested in EEvEE and it works better:\n\nBut another problem arises, tesselation of the objects aren't smoothed, like if it is not using Smooth Shade setting at all.\n\n\nI attach a scene that reproduces the problem: [Shadow_Pass_3.1_Packed.blend](Shadow_Pass_3.1_Packed.blend)\n\nAs a last detailed behaviour, in the scene I'm actually working, I nottice that some Specularity and Diffuse are also \"leaking\" to the Shadow Pass:\n\n\nI hope it can be fixed.\n\nOf course, If I can somehow workaround it let me know as it would be of much help as I didn't found, yet, a way to overpass the trouble other than creating a new scene with untextured materials.\n\nThanks in advance, and cheers!\nIgnasi.\n\n", "Black Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0\n\nBlack Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field, if Shader Color is not pure white (similar problem with Layer Weight)\n\n**Exact steps for others to reproduce the error**\n- Open attached file (Just a simple box (can be a plane) with Transparent BSDF. Camera' distance or depth of focus influences the result. Attached pictures in Image Editor from a real case).\n- Press F12 to render\n[transprarent_shader_artifacts_with_camera_DOF1.blend](transprarent_shader_artifacts_with_camera_DOF1.blend)\n\n\n" ]

[ "Volumetric lighting leaking in eevee\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.11014\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nVolumetric lighting is visible through thin geometry if a light is placed close to it. Effect is especially bad if the light is inside an object. In this example there is a spot light inside the cube on the left. Both object have a simple opaque material.\n \n" ]

[ "Flashing vertices on screen updates\nWindows 10 Home, version 1909, 64-bit\n| Graphics card: | Author:\n| -- | -- |\n| GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 | @Code_Craft_Plugin\n| GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89 | @MontagueMGM\n\nBroken: 2.83.0 - 2.83.10 (still broken as of latest 2.92.0 alpha experimental build acbda123ad08)\nWorked: 2.82.7\n\nVertices flash when the screen is updating. Only on my desktop using a GTX 780, not my laptop using an i7-1065G7 (Intel Iris Plus)\n\nCreate an Ico Sphere with subdivisions set to 6. It happens at levels 5 and 7 as well, but not nearly as noticeable. It seems related to a specific vertex count, rather than proportional to the number of vertices.\n\n[Blender 2021-01-12 02-13-49.mp4](Blender_2021-01-12_02-13-49.mp4)", "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", "Bevel modifier profile direction depends on edge/face order\n[2021-04-18 01-18-54.mp4](2021-04-18_01-18-54.mp4)\n\n[01.blend](01.blend)\n\n\n\nIt is recommended that the Solidify modifier reorder the faces. \n\nThis is the problem I encountered when I was making a column. I thought it was bug. \n\nIt was later found that after the Solidify modifier, the Bevel direction is controlled by the face order, and the Bevel modifier has no option for the face order.", "State of hidden geometry not synced between edit mode and vertex paint/weight paint mode\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\nWhen vertex selection (or face selection) is used in either vertex paint or weightpaint mode the state of hidden geometry is not synchronized but overwritten by some specific state on this object. That makes it impossible to paint on using vertex selection. Joining the mesh into a new object did not fix the issue.\n[hidden_geo-2021-04-29_20.57.11.mp4](hidden_geo-2021-04-29_20.57.11.mp4)\n\nSee file:\n[hidden_geo.blend](hidden_geo.blend)\n\n", "Stitch tool only works on separate islands\nHello,\n\nIn my opinion the biggest issue with UVs in blender right now is the stitch tool.\n\nIn its current state you are unable to stitch edges that belong to the same UV island. It will only function if you are stitching two different UV islands together. \n\nThe only way to sew edges together that belong to the same island is to either change your seams and unfold the UV island again or manually go through each UV point and merge them one by one.\n\nI propose that we have full control over the stitch tool and remove this limitation. If the selected edges have the capability to be stitched, the tool should function as expected regardless if the selected edges belong to the same UV island or not.\n\nThanks to the Devs for all your efforts.\n\n", "Using \"Rebuild Subdivisions\" in Multires modifier on hires mesh returns an error: Not valid subdivisions found to rebuild lower levels\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 3.0.0\nWorked: IDK, first time user\n\nUsing \"Rebuild Subdivisions\" in Multires modifier on hires mesh returns an error: Not valid subdivisions found to rebuild lower levels\n[Head_Subdiv_Error.blend](Head_Subdiv_Error.blend)\n1. In the attached file add Multires modifier to the Head mesh\n2. Click Rebuild Subdivisions\n3. An error should be reproduced.\n\n", "GPU: Design topic for displaying outline for instances\nSee 2 for discussion on devtalk\nWe might have technical reasons, but we don't need to distract users with drawing an outline around each instance.\n\nDesign topic could be should we group the outlines per original object (when using multiple objects to instance) or should we outline the object that creates the instances (eg contains the node group).\n\nPersonally I think we should have a single outline for an object. Not taking into account that it draws instances or not.\n", "Surface Deform Modifier invokes \"Invalid surface UVs\" error when applied to Hair\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 770 Intel 4.5.0 - Build 31.0.101.3959\n\nBroken: version: 3.5.1\n\nWhen adding Fur to the mesh in the example file, the Surface Deform modifier produces the error message \"Invalid surface UVs on x curves\". This also appears related the rippling visibility of the hair an animation (see also [#109285](109285#issuecomment-965921))\n\n\n1. Load the attached file and press play\n2. Note the \"Invalid surface UVs on x curves\" error in the Surface Deform modifier\n3. Stop the playback, and note that the figure in the error corresponds with the appearance of hairs on the surface\n4. Select the Body object and Add > Curve > Fur\n5. Observe the same error in the newly added Surface Deform modifier\n\n", "Remeshing object with subdivision modifier hangs Blender\nOperating system: macOS 10.14.6\nGraphics card:\n\nBroken: All versions of Blender but tested on Version 2.93.0 (2.93.0 2021-02-25) & Version 2.92.0 (2.92.0 2021-02-25)\nWorked: ?\n\nRemeshing object with subdivision modifier hangs Blender\n1 Add a subdivision modifier to the default cube, set it to 2 or more.\n2 Jump into Sculpt mode and remesh with default voxel settings, it should work fine.\n3 Undo the last remesh and now change the voxel size to 0.002 m and remesh again, it hangs.\n\n\nDo step 1 again, this time apply subdivision modifier and then try to remesh with voxel size of 0.002 m, it should work\n\n\n\n", "Wireframe modifier strange behaviour\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.2\n\nStrange behaviour from wireframe modifier\n\n\nTook a plane and subdivided, added a wireframe modifier, unsubdivided. Some corner vertices are pushed to the edge of scene.\n[Based on the default startup or an attached .blend file (as simple as possible)][Wireframe.BugReport.blend](Wireframe.BugReport.blend)\n\n", "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "OSL on the GPU displays all black for Voronoi Distance > Bump Height\nSystem:\nWindows 11\nRTX3090Ti gpu\n\nBump output is pitch black when using Voronoi (Distance) output into Bump Height. Colorramp in between does not fix it. Noise output into Bump Height works fine.\n(Blender 3.5 in cycles)\n\nedit: more useful info + screenshot + isolated blend file\n\nRunning OSL on the CPU works fine, only the new GPU support seems affected.", "Symmetry on sculpt mode won't work with auto masking topology enabled\nOperating system: Windows-11\nGraphics card:Quadro RTX 3000/PCIe/SSE2\n\nBroken: Blender 3.5.0\nWorked: N/A\n\nSymmetry on sculpt mode won't work with auto masking topology enabled.\n\n\n- Have a mesh that has two disconnected parts across a symmetry axis.\n- Enter sculpt mode, turn on \"Advanced -> Topology\" (topology auto masking).\n- Turn on X symmetry for sculpting brushes.\n- Sculpt on one part of the mesh, the opposite side doesn't change.\n", "Some mesh operations (e.g. smooth, randomize) are not using mirror modifier mirror object transform correctly for clipping\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.0.1 Release Candidate\n\nWhen using mirror modify with clipping, Smooth Vertices ignore clipping and smoothing all, and this is no options\n\n\nTools to check:\n`Transform` > `Randomize`: does not clip (even without mirror object usage)\n`Transform` > `Warp`: does not clip (even without mirror object usage)\n`MESH_OT_vertices_smooth`\n\nnote: all of the above are not part of the transform system (randomize is even written in python), so it might be a bit cumbersome to implement", "Ngon with more edge crash blender when using Multires/Subdivision Modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha, 2.93.2, \nWorked: None\n\nPlease check the video, it shows the difference when blender deal will small ngon(edge < 10) and large ngon (~=600).\nI think it should take over aleast 5000 points ngon(for some svg file)\n[2021-08-15 17-50-41.mp4](2021-08-15_17-50-41.mp4)\n\nCreat a ngon with more than 600 points\nextrude it and add Subdivision Modifier\ncrash\n[test.blend](test.blend)\n" ]

[ "GPU subdivision does not support wireframe subdivision (no faces)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.1.0 Alpha\n\nNormally you can subdivide a wire mesh. For example a square with no filling face to create a sort of circle.\nIt appears the GPU subdivision code doesn't support this case yet\n\n[Subsurf Wire.blend](Subsurf_Wire.blend)\nWith GPU Subdivision OFF it will look like this\n\nBut with GPU Subdivision enabled it turns back to a square\n" ]

[ "Stereoscopic - right side has incorrect render (Eevee)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.93.4\nWorked: unknown\n\nStereoscopic creates an incorrect image for the rendered Right side (Eevee).\nThe right side seems to be a mix of the correct render and a render with low samples (1?). This is clear on the soft shadows and AO.\n \nIt can only be resolved by enabling Screen Space Reflections, which isn't always desirable obviously. \n\nOpen attached blend file and render. \nCompare left and right render.\n\n[stereoscopic_rightSide_difference.blend](stereoscopic_rightSide_difference.blend)\n", "Booleans causing shadow artifacts in solid render mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 3.0.0 Alpha\nWorked: Unknown\n\nI built up a random shape using a bunch of booleans via the box cutter addon.\nThis seems to have introduced artifacts when the shape is viewed from certain angles.\n\nThe artifacts remain when applying all the modifiers. I also tried to reset various edge data like bevel weight and crease without any effect.\nAdding a triangulate modifier however cleans it up, so maybe something about the automatic triangulation is off.\n\nI compared the output with the stable release: It also shows artifacts but they look slightly different, at least with my current configuration.\n\nv.2.93.1\n\n\nv.3.0.0 (see version info above)\n\n\nIn motion from another angle, showing convergence on a point and something that looks like an [even/odd fill rule](Even%E2%80%93odd_rule) of a shape being used to draw the shadow:\n[streaks.mp4](streaks.mp4)\n\n\nI cannot offer concrete steps; my default file also has certain settings already applied.\nHere is the file that may help show the issue: [shadow-streaks.blend](shadow-streaks.blend)\n", "Blender 2.81 — Shadow glitches with Workbench render-engine (in viewport and same at render)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.81 (sub 9)\n\n\nBroken shadows \"traced path\" glithc effect in the air in places where geomety have \"complex area\" (when you use shadows from Workbrench render and same in viewport).\n[Screenshot ](l2ZRNEjhzLYbl2.jpg)\nHere is on [video ](#!0OoB2I7R!h1qq3DB20nOOgoxoYw9QT_kyoZO-a-1C7OSqRifExcs) uou can see it. Sorry for broken english.\n\n\nDon't know how to reproduce it step by step, so I've put the file here: \n[broken.blend](broken.blend)\n\n\n", "In eevee, shading disappears when SSS is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: -\n\nShading disappears in Eevee if one object is located on another object and both have Subsurface enabled\n\nWhen an object has no shading, it looks unrealistic and wrong.\nTo get around this bug, I render two images and connect them in the compositor.\n\nMaybe it is possible to somehow enable these shading without a second render?\nSSS is needed for both objects.\n\nBall Subsurface On (0.02)\n\nBall Subsurface Off (0.0)\n\n\n.Blend file\n[bugshafowsubsurface.blend](bugshafowsubsurface.blend)\n", "Fade Inactive Geometry: Objects with the same stored mode are not faded\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 3.0.0 Alpha\n\nIt is possible to keep objects in a certain mode even if they are not active. \nThe \"Fade Inactive\" Geometry\" overlay is supposed to fade out any object that is not affected by the currently active object in any mode that is not object mode.\nUnfortunately if any object in the scene is also in the same mode, even if it is not active or affected by the currently active object, it will not be greyed out.\n\n In this example image 2 quad-spheres are not greyed out. The left one is active and can be sculpted on. The right one is not active or selected but is also currently in sculpt mode. \n\n- Disable \"Lock Object Modes\" in Topbar -> Edit\n- Duplicate an object multiple times to have more than 1\n- Select one and switch to (for example) vertex paint mode\n- Select another object in the 3D viewport or via the outliner without exiting the mode of the active object\n- Switch into the vertex paint mode\n- The other object is not greyed out \n\n", "Eevee: Soft shadows causing flickering in animation and temporal AA in scenes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.80\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nEevee soft shadows in objects with thin reflections causes flickering in animation and temporal AA in still images. This type reflections common in interior Arch Viz.\n\nScene 1 example of flickering of soft shadows in animation. I have remove all light probes and effects to focus only light and shadows. Open attach file \"Scene1_AA_eevee.blend\".\nRender the animation with Soft Shadows ON. Then Render animation with Soft Shadows OFF.\n[Scene1_AA_eevee.blend](Scene1_AA_eevee.blend)\n\nAnimation with Soft Shadows ON. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_eevee.mp4](Scene1_AA_eevee.mp4)\n\nAnimation with Soft Shadows OFF. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_No_SShadow_eevee.mp4](Scene1_AA_No_SShadow_eevee.mp4)\n\nAnimation in Cycles for comparison. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_cycles.mp4](Scene1_AA_cycles.mp4)\n\n******************************************************************************************************\nScene 2 example of temporal anti-aliasing cause by soft shadows. I have simplify the scene 2 to focus only light and shadows. Open attach file \"Scene2_AA_eevee.blend\".\nRender Image with Soft Shadows ON. Then Render Image with Soft Shadows OFF.\n[Scene2_AA_eevee.blend](Scene2_AA_eevee.blend)\n\nRender image with Soft Shadows ON. Make sure to view at full size. Notice the temporal AA on the edges on horizontal counter, vertical counter, oven handle and oven racks.\n\n\nRender image with Soft Shadows OFF. Make sure to view at full size. Notice the temporal AA is gone.\n\n\nRender image with Cycles for comparison. Make sure to view at full size.\n\n\n", "Volume render bug in view layer indirect only.\nOperating system: windows 10\nGraphics card: RTX 2080 supper\nCPU: AMD ryzen7 2700\n\nBroken: 2.92.0\nWorked: no\n\nOutliner \"Indirect Only\" option does not work well with volumes, as inner shadows are ignored.\n\n\nSurface material with indirect only can work.\n\n- Open attached file\n- Display Render Preview in any of the viewports\n(Make sure the \"Indirect Only\" option in the outliner is enabled).\n[renderlayer bug.blend](renderlayer_bug.blend)", "EEVEE Volume draw distance broken with emission shader\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.4\nWorked: none\n\nWhen using an Emission shader as Volume shader in EEVEE, draw distances smaller than 100 produce unecpected behaviour.\nUsing Principled Volume works fine as long as Density is not 0, if it is 0 the behavior breaks in the same way.\n\n- Open attached blend (Cube with emission shader as Volume)\n- Change Volumetrics End distance to 70m\n- Zoom in and out in EEVEE viewport, the cube does disappear at a distance range inbetween the set clipping range\n[eevee_volume_drawdistance_bug.mp4](eevee_volume_drawdistance_bug.mp4)\n[eevee_volume_drawdistance_bug.blend](eevee_volume_drawdistance_bug.blend)\n\n", "Shading Problem in Eevee in Top Orthonographic View When the Scale is not Applie Yet\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\nWorked: Never\n\nThere is a strange shading problem in Eevee that happens when the object is scaled and the scale is not applied yet. The light needs to be at certain angle to make it appear. The problem also has to do with the topology of the mesh, it is hard to notice with just one face (though still there as you can see it flickers when you scale it), but it becomes obvious when subdivided.\n\n\nBased on the attached .blend file \nOpen my .blend file, you can see there is a circle and a light in the scene. You can see the problem by turn on render view. The light is placed at certain angle to make the problem show. \nThe circle was created using the below steps:\n\n(0. delete or hide my circle)\n1. Shift A and add a circle\n2. Lower left corner menu, the fill type choose Ngon\n3. Scale it up a little, don't apply the scale, and you can see it flickers during the scaling process\n4. Edit mode, hit the a key to choose all, hit the i key to inset the circle, and then inset it again, and see it has to do with the topology\n5. Object mode, ctrl a apply the scale, the problem is gone, it has to do with the scaling.\n[Orthonographic Top View Shading Problem.blend](Orthonographic_Top_View_Shading_Problem.blend)\n\n", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "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", "Regression: Passepartout Flickers when using Solid Viewport Shading and Background > Viewport\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: 2.93, 3.5\nWorked: 2.83\n\nThe Passepartout flickers with every Viewport interaction when using Solid Viewport Shading and the Background set to Viewport\n\n1. Create a 2D Animation workspace\n2. Zoom out to see the Passepartout\n3. Switch to Solid Viewport Shading and set the Background to Viewport\n\nIn this screencast, the Passepartout flickers with every Viewport interaction when using Solid Viewport Shading and the Background set to Viewport. In the video, it stops flickers when switching to World, however it is doing now. It does stop when using Material Preview Shading.\n\n[Passepartout.mp4](Passepartout.mp4)\n", "Regression: Screen Space Reflections on EEVEE render shaders with roughness a minimum regardless the value or map in the shader\nOperating system: Linux Manjaro \nGraphics card: Geforce 590\n\nBroken: 3.2 and succeeding versions\nWorked: 3.1\n@Tyson-Marchuk found the first bad commit: 80859a6cb2\nAlso mentioned the potential fix: #102423#1459379\n\nScreen Space Reflections on EEVEE render materials incorrectly\nThe shaders roughness valuue or map are ignored and all shaders are render \n| 3.3.1 (SSR off) | Broken: 3.3.1 (SSR on) | Worked: 3.1.0 (SSR on) |\n| -- | -- | -- |\n|  |  |  |\n\nThe problem became evident in a scene with medium or high roughness by enabling the Screen Space Reflactions\n\n[SSR.blend](SSR.blend)", "Auto smooth smooths triangulated faces despite faces beeing set to flat shading/EEVEE smooths faces when it shouldn't\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.1.0\n\nWhen using cycles after enabling auto smooth it smooths the faces after triangulation despite setting faces to flat shading, meaning that a quad will still have flat shading compared to it's neighbors but instead of showing 2 flat tris it will show 1 smoothed quad.\nWhen using EEVEE it always smooths the faces after triangulation despite setting faces to flat shading even if auto smooth is turned off, so depending on whether or not this is intentional behvior, the title might also be \"triaglulated faces not smoothed correctly in cycles when auto smooth disabled.\"\n\nTest file:\n[Test.blend](Test.blend)\n\n2 almost identical Suzannes. Both are set to shade flat, but the left one has auto smooth enabled while the right one does not.\nNote that the triangulation is not visible for the left suzanne.\nSwitching to EEVEE shows that the triangulation is not visible for either of them.\n\nThank you and have a great day!", "Shader color affects Shadow Pass in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.1.0\n\nShadow Pass is not working as it should in Cycles. It somhow works much better in EEvEE (altough other problems arise).\n\nEasiest setup is just adding a plane, a sphere and setup cycles as a render engine.\nActivate **Shadow Pass** (not the Shadow Catcher Pass).\nDo an image render and everything works, more or less, as expected. So you get as a result a Black and White image (right side) where black is shadow and white is none:\n\n\nBut, as soon as you texture the objects with any image you get the darkest areas of those images in the Shadow pass (something like if one of the rgb channels is leaking to the final image):\n\n\nI have already tested it in Blender 2.83, 2.93, 3.1, 3.2 and 3.3 alpha and I have got always the same behaviour... so no idea if it ever worked or not as it should do. Right now it is absolutelly useless as you can't compose it without textures afecting the masked shadow.\n\nAs I said I already tested in EEvEE and it works better:\n\nBut another problem arises, tesselation of the objects aren't smoothed, like if it is not using Smooth Shade setting at all.\n\n\nI attach a scene that reproduces the problem: [Shadow_Pass_3.1_Packed.blend](Shadow_Pass_3.1_Packed.blend)\n\nAs a last detailed behaviour, in the scene I'm actually working, I nottice that some Specularity and Diffuse are also \"leaking\" to the Shadow Pass:\n\n\nI hope it can be fixed.\n\nOf course, If I can somehow workaround it let me know as it would be of much help as I didn't found, yet, a way to overpass the trouble other than creating a new scene with untextured materials.\n\nThanks in advance, and cheers!\nIgnasi.\n\n" ]

[ "Blender 2.9 shadow bug for toon outline, shadow does not show under the sun lamp\nOperating system: Windows 10\nGraphics card: NVIDIA Geforce GTX 1070\n\nBroken: 2.90.0 & 2.90.1\nWorked: 2.83.5\n\nI opened my file created in 2.8 in 2.9 and all the shadow disappeared on my file that has a toon shader with outline (simple toon outline created by solidify the object and inverse the normal).\n\n\n- If you open up my attached file with 2.9, there is no shadow in viewport shading mode, but if you open up the file in 2.8, there is shadow.\n\n- In 2.9 if you delete the outline material or change the material's shadow mode to opaque, the shadow will appear since it's the solidify outline is casting shadow, but outline is not suppose to cast shadow and when the geometry is more complex, the shadow could look weird.\n2.9  2.8 \n\n- Even if you delete the solidify modification in 2.9 the shadow still does not show up, only if you delete the outline material (or any material that has shadow set to none) then the shadow will appear. \n\n- On top of this if you create something with 2 materials and has the second material set shadow to none, then the object will have no shadow (so it has nothing to do with solidify). It seems like the second material's shadow mode is dictating the first one? I am not sure about this.\n\n- One weird thing is that if you have a object that is without the problem material near or intersect with the ones that does have the material, it will make the shadow appear, but if you drag it away enough from the other objects, the shadow will slowly disappear. You can try this in the scene that is attached, turn on the object named \"Plane\", shadow will appear, but drag it away from the other 2 objects, the shadow will shrink and disappear after a certain distance.\n\n- On more thing, this only happens with sun lamp, not other lights, weirdly.\n\nHopefully you guys can fix this problem soon, thank you!\n\n[Blender2.9Problem.blend](Blender2.9Problem.blend)" ]

[ "Polishing the Painting Experience\nThere are a few tasks that would enhance the texture painting pipeline that could be prioritized before advanced features like layered textures is even considered.\n\n## Existing Painting System\n\n### Small Tasks (e.g., bug fixing)\n- [ ] Graphics Tablet Lag when in Texture Paint mode in Blender 3.0 #93796\n- [ ] Undo bugs\n - [ ] Undo eliminates brush texture #88592\n - [ ] Texture paint undo can changes texture slot #62520\n - [ ] Texture Paint mode tools swap when exiting maximized area #98014\n- [ ] Color space support for texture painting #95797\n- [ ] Sync Image Sequence options (Frames, Start Frame, Offset, Cyclic, Auto Refresh) #109769\n- [ ] Texture paint: Bleedind around thin cuts do not fill texture #106066\n- [ ] Add support for \"Channels\" to the Images & Color Attributes #108404\n- [ ] 8/16 bit textures have different strength behavior (premultiplied problems) #101436\n- [ ] UDIM bugs [need report]\n- [ ] 3D mirroring in Image Editor\n- [ ] Other bugs (by Daniel Bystedt) [need report]\n\n### Bigger Tasks (e.g., re-designs) - need design\n- [ ] Image syncing between Editors via active image canvas #103636\n- [ ] Multi-object painting\n- [ ] Multi-object uv editing\n- [ ] Support \"viewport\" face sets in Image Editor\n- [ ] Square brush\n\n## 3D Brush\n\nRelated to #96225\n\n### 3D brush vital\n- [ ] Color sampling\n- [ ] Erase blend mode\n- [ ] Affect only visible (Show/Hide)\n- [ ] Affect Alpha option\n- [ ] Masking\n- [ ] (2D) Fill operation\n\n### 3D brush additional\n- [ ] Feature parity\n - [ ] Blur & Smear brushes\n - [ ] Clone brush\n - [ ] Sync masks and edit mode selection\n - [ ] Paint modified geometry instead of base mesh\n - [ ] Missing brush settings\n - [ ] Stencil masking\n- [ ] Image editor syncing\n- [ ] Dedicated paint mode\n- [ ] Performance\n\n", "Grease Pencil: 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.", "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:", "Dynamic Paint With UNDO [Control Z] Crash Blender\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen Press Control Z While In Weight Paint (EDIT MODE), Blender Crash\n\nBased on the default startup or an attached .blend file (as simple as possible).\n[weight-paint-v1.blend](weight-paint-v1.blend)\n1. Open the provided .blend file\n2. Start playback and enter Weight Paint mode\n3. Paint and then undo (Control + Z)\n4. Blender crashes after a while,\n\nHere is video to show case KUUbxSnwmbE", "Hair children are jumping around on skinned mesh\nOperating system: Windows 10\nGraphics card: AMD\n\n**Blender Version\nBroken: 3.5, 3.6\nWorked: 3.4\n\nProblem:\nWhen I use hair with interpolated children on a skinned/ rigged mesh, the hair folicles jump around /change position wildly when i move the bones. For example: When I rotate the arm of my rigged character up or down, the hair all over his body jumps around randomly from (rendered) frame to frame. This problem did not exist in version 3.4, everything works fine in 3.4. It appeared in 3.5 and 3.6.\n\n\n- Make a mesh and some bones.\n- Skin the mesh with automatic weights.\n- Add hair and children (interpolated).\n- now move the bones and check the _rendered_ images. The hair will jump around wildly on the mesh.\n\n", "Improved way to display weight painting colors\nWeight group colors in vertices blend between their neighbors by going through the entire range of values between the 2 points\n\n\nFor example if a vertex has a 1.0 (red) value and one of it's neighbors has a 0.0 (blue) value, the face will show a rainbow interpolation going trough orange, yellow, green, cyan and finally blue\n\n\nIn certain situations where each of the vertices of a face have different values (like 1.0, 0.5, 0.75, 0.0) it will create weird intersections in the middle that look like there is a vertex there that doesn't exist\n\n\nThe problem is even worst when the wireframe is not displayed and we only see gradients of colors indicating vertex values that do not exist\n\n\nThe solution is to fix the color blending mode to simply **mix** between the 2 neighboring colors. This way it is very clear that vertices have values of 1.0, 0.75 and 0.5 and nothing in between.\n", "Weight paint issue with brush Accumulate option\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\n\nWhen use weight paint with option Accumulate, turn on symmetry, artifacts appear on the axis of symmetry\n[test.blend](test.blend)\n\n\n[EnrLS0nY4n.mp4](EnrLS0nY4n.mp4)\n", "All bone drivers selected when reselecting bone\nWindows 8.1\nGTX 580\n\nBroken: 2.77, 2.77a\nWorked: It seems any version before 2.77\n\nVisual explanation:\n\n\nBasically, all created drivers for a bone will be selected instead of the last active one when the bone is selected.\nVery annoying problem that wasn't there before (Had to redo drivers several times because I didn't realize the last active driver isn't the active one anymore).", "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.", "Texture paint: Bleedind around thin cuts do not fill texture\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.6.0 Alpha\nWorked: never?\n\n\n1. Wider distance allow to overlap color\n2. closer distance between faces do not\n3. closer distance between islands allow to overflow to neighbour island…\n\n\n[bleeding test.blend](attachment)\nopen file, try to paint as seen in the [video 2023-03-24_05-09-32.mp4](attachment)\n\n", "Unable to select certain vertices (regression from 2.79)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nSome vertices are impossible to select.\n\nAt first I thought it was because the vertices formed a concave area (see first file) but then I hit a second concave case (see second file).\n\n\nWithout rotating or zooming the view try to select one of the marked vertices in both files.\n[Select1.blend](Select1.blend)\n[Select2.blend](Select2.blend)\n\n----\n\n2.79 worked in this case, open this file in 2.79 to test.\n\n[Select1(1)_279.blend](Select1_1__279.blend)", "blender 3.4 and 3.5 hangs during compositing when rendering an animation\nOperating system: Linux-5.4.0-132-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.4.0 Beta\n\nwhen rendering a longer animation the beta and alpha versions tend to hang on the \"initializing execution\" part of the compositing. No compositing happens on the render in the render window, you see frame n while the playhead already is a frame n+1.\n\nWhen rendering the same animation it happens randomly after 5 frames or after 150 frames, but mostly with 200+ samples and at least HD resolution, smaller res and less samples went through mostly. I compared the same animation file with 3.3.1 and it just worked and the very same file with 3.4 got stuck.\n\n", "Texturing with anchored type stroke\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.51.06\n\nBroken: version: 2.91.0 Alpha\n\nTexture paint with stroke set to anchored while using texture significantly slows down blender up to non responsive state and crash while paint texture is larger than 2k.\n\n[Texture pain stroke ty[e anchored.blend](Texture_pain_stroke_ty_e_anchored.blend)\n", "GPencil: Texture Image Alpha pass through grease pencil strokes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.1\n\nContext: Using texture image to make some kind of 2d fur on top of a GPencil Object\n\nThe Image Texture used to make some fur is mostly transparent and the brush used to make the colored part is a texture paint brush with Cloud Mask (it was made entirely in Blender with Blender tools).\n\nWhen on top of the GPencil object, the part of the Image Texture that is only half transparent(between 99%-1% transparent), makes the GPencil color disappear, even when moving the center point behind the one of the fur images.\n\nOn the contrary, when on top of another Image Texture (imported to be used as camera mapping), the Image Texture of the fur doesn't impact the transparency of that one.\nNotice that the Image texture boundary, even from the imported one, has problems with clipping and always makes a white line appear.\n\n- Open attached .blend file\n- Zoom in and out to notice the alpha transparency influencing the GP object\n\nThanks for your help!\n\n\n\n\n\n\n\n[bug_alpha.blend](bug_alpha.blend)", "Texture Paint Fill Tool is broken with partial strength on Float/Linear Textures\nOperating system: Linux-4.15.0-55-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130\n\nBroken: version: 2.92.0 Alpha\nalso 2.79, 2.80, 2.81, 2.83.5, 2.90.1\nWorked: probably never?\n\nTexture Paint Fill Tool behaves strangely with partial strength (0-1 exclusive) when painting on float/linear textures. It appears as though strength were ignored when filling over a black image, but doing so over a non-black image shows some weird interaction.\n\nNote that the Texture Paint Draw Tool behaves correctly, so I guess the fix is for fill to just do what draw does.\n\n(minor note: working with colour spaces is difficult and I figured there's a chance the problem is just me not understanding it/doing it wrong, but I think the fact that the draw tool does work as expected has me covered.)\n\n**Video demonstration:**\n(I've fast-forwarded unimportant parts)\n\n0:14 - Non-float image. Draw tool with strength=1.0, then 0.1, then fill tool with strength=0.1. Behaves as expected.\n0:43 - float image. Same test. Draw behaviour with low strength appears correct. Fill behaviour is incorrect.\n\n[BlenderFloatFillBug.mp4](BlenderFloatFillBug.mp4)\n\n\nFrom default startup:\n1. enter texture paint workspace\n2. properties editor -> tool settings, set texture slots mode to single image, make new image with 32 bit float.\n3. set tool to fill, set strength to any value below 1, except 0.\n4. click cube to fill black texture with white paint. Expected: some shade of grey. Result: full-bright white.\n\n**Results of tests with various shades/strengths**:\n\n- all performed in 3d viewport\n- each test performed on empty black image\n- input/output are HSV values\n- 0.7354 being middle grey\n- output value is sampled from viewport with eyedropper\n- fill 2nd click is result after two clicks of fill\n\n| in | strength | draw output | fill output | fill 2nd click\n| -- | -- | -- | -- | -- |\n| 0.01 | 0.01 | 0.0001 | 0.01 | 0.0199 |\n|| 0.1 | 0.001 | 0.01 | 0.019 |\n|| 0.5 | 0.005 | 0.01 | 0.015 |\n| 0.1 | 0.01 | 0.001294 | 0.099998 | 0.15143 |\n|| 0.1 | 0.012949 | 0.099998 | 0.14752 |\n|| 0.5 | 0.061102 | 0.099998 | 0.128549 |\n| 0.5 | 0.01 | 0.027639 | 0.49997 | 0.684261 |\n|| 0.1 | 0.157658 | 0.49997 | 0.670251 |\n|| 0.5 | 0.36078 | 0.49997 | 0.602086 |\n| 0.7354 | 0.01 | 0.060985 | 0.735162 | 0.998114 |\n|| 0.1 | 0.247814 | 0.735162 | 0.97771 |\n|| 0.5 | 0.537175 | 0.735162 | 0.880889 |\n| 0.99 | 0.01 | 0.098344 | 0.99001 | 0.999924 |\n|| 0.1 | 0.345314 | 0.99001 | 0.999924 |\n|| 0.5 | 0.727916 | 0.99001 | 0.999924 |\n| 1 | 0.01 | 0.099802 | 0.999924 | 0.999924 |\n|| 0.1 | 0.349084 | 0.999924 | 0.999924 |\n|| 0.5 | 0.735271 | 0.999924 | 0.999924 |\n\nNotice:\n- the first click of the fill tool always gives the same result regardless of strength.\n- the second click makes the image brighter than the colour we're filling with, which doesn't make sense.\n- the second click gives lower values for higher strengths, when you'd expect the opposite.\n\n\n**Another demonstration:**\n\n- left: black texture painted with grey values 0.1 .. 1.0.\n- right: then filled with middle grey 0.7354 with strength 0.5.\n\n\n\nNotice:\n- every shade becomes brighter (or remains ~1.0), even those greater than 0.7354 that should darken (move towards middle grey)." ]

[ "BONES WONT WEIGHT PAINT!\nOperating system: Ryzen 9\nGraphics card: AMD radeon 5\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (newest version of Blender that worked as expected) 3.1 ANDDDDDD before it was 2.79\n\nI have under 5,300 bones for hair cards. After painting half of my skulpt in weight paint, my rig stops working and wont weight paint or select bones. they are thin basic planes that I am weight painting. not sure why it stops after a certain amount of bones. \n\n\nmore than half my rig was weight painted. \nBased on the default startup or an attached .blend file (as simple as possible).\n\nPLEASE FIX BONES AND WEIGHT PAINT!" ]

[ "Snap move doesn't work with Spin tool\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.47\n\nBroken: version: 3.3.1\n\nSnapping doesn't work with transform gizmo in spin tool\n\n- Open .blend file\n- use spin tool\n- Move with transform gizmo and try to snap with ctrl key (works though for rotation)\n[#102198.blend](T102198.blend)", "Geometry Nodes: writing attributes (from procedurally created geometry) to vertex groups not working\nOperating system: macOS Monterey 12.4\nGraphics card: RX 6800 XT\n\nBroken: 3.1 & newer\nWorked: 3.0.1\n\n\nIn Blender 3.0.1, it was possible to write attributes from procedurally created geometry (created by geometry nodes) to vertex groups, as long as the \"Group Input\" node was joined with the procedural geometry. However, no version newer than 3.0.1 seems to have this capability. From what I understand, this may have been done intentionally in anticipation of attributes replacing vertex groups entirely... but it seems odd to kill this feature before that transition is complete, so I'm reporting this as a bug.\n\n\nOpen the attached .blend file in Blender 3.0.1:\n[geonodes_attrib_to_vgroup.blend](geonodes_attrib_to_vgroup.blend)\nThis file contains a geonodes setup where half of a procedurally generated grid is extruded using a solidify modifier. The \"geonodes\" object should look exactly the same as the \"Expected Result\" object. \n\nNext, open the file in Blender 3.3 (or 3.1, or 3.2) and notice how the \"Expected Result\" object no longer matches the \"geonodes\" object.\n", "Joining meshes or realizing instances in geometry nodes removes custom normals data\nOperating system: macOS Big Sur 11.5.2\nGraphics card: Apple M1\n\nBroken: 2.93 and 3.0 Alpha\n\n\nUsing the collection info node in geometry nodes destroys custom normals data when the geometry node modifier is applied (or when the project is exported).\n\n\nApply the geometry node modifier on the \"Dummy\" object in the attached blender project. I've also included a video that shows the issue.[collection_info_test.blend](collection_info_test.blend)\n\n[collection_info_bug.mov](collection_info_bug.mov)", "python display_shape don't work in GeometryNodeTree\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.1.0 Alpha\n\nWhen adding a custom node with custom socket to the GeometryNodeTree you can't alter the display_shape of the socket and the bpy.types.NodeSocketFloat or any socket type doesn't matter when connecting nodes it always stay red.\n\n\nAttached a blend file with the script for quick testing\n[tst.blend](tst.blend)\n\nThis is not a problem in the Shader or Compositing editors:\n\n", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg", "Applying geometry nodes modifier create an empty material slot for no reason\nOperating system: W10\n\n3.4.1\n\nApplying geometry nodes modifier create an extra empty material slot for no reason.\n\n| Geometry node tree | Applyed mesh |\n| -- | -- |\n|  |  |\n\n1. Create an object\n2. Add a GN modifier\n3. Create some geometry inside GN and assign a material to it (or don't)\n4. Apply the modifier, you'll get an empty material slot on the object.\n\n", "GeometryNodes: Attributes in shader not visible in Eevee \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\n\nWhen an attribute is used in the shader editor, it will render in Cycles but not Eevee. \n\nHave an attribute in a shader as a render output with the Eevee render engine enabled. \n\n[Possible Attribute Bug.blend](Possible_Attribute_Bug.blend)\n\n", "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", "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", "Circle select does not select all vertices within the same pixel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.90.1\n\nSelecting closely-arranged vertices with circle select tool doesn't consistently select all vertices.\n\nCreate plane geometry with three vertices located close together (e.g., the end of a sword or a blade of grass). Type 'C' to use the circle select tool and select the vertices. Zoom in to verify that all vertices have been selected. De-select vertices. Change zoom level. Repeat selection. Repeat verification. See animated GIF, attached, using simple .blend file, attached.\n\n\n\n[C3DE_Ch4_L12a.blend](C3DE_Ch4_L12a.blend)\n\n", "Node frame grid alignment issue\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nNode frames shift contents out of grid alignment when transformed.\nMy understanding is that the frame borders are not multiples of the grid spacing, so whenever the frame is transformed and snapped to the grid, its contents are yanked out of alignment with the grid. Moving the contents back into alignment on their own works, but any further transforming the encompassing frame will yank them out again. Perhaps making the frame border an exact multiple of a grid unit could fix this.\n\n1. Try moving the convex hull node. Observe that it stays aligned with the grid\n2. Try moving the frame around it. Observe that it snaps to the grid, and the convex hull node is now unaligned with the grid\n\n", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "3D cursor doesn't precisely follow mouse pointer when Transform Pivot Point is Active Element\nOperating system: Fedora Linux (Wayland)\nGraphics card: AMD\n\nBroken: at least from 2.93 to 4.0 all broken\nWorked: never?\n\nWhen moving the 3D cursor, it's moved distance is multiplied by some value depending on the view orientation. \n\n\n- Move the default cube and rotate the viewport orientation\n- Select Active Element as the Transform Pivot Point\n- Move the 3D-Cursor with shift+RMB\n\n", "Can't resize node in visible bounds\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\n\nWhen trying to resize a node, the node cannot be resized if the mouse is precisely on the edge of the node\n\nAdd any node in shader o geometry node editor and try to resize the node with the cursor in the border line of the node\n<video src=\"attachment\" title=\"2023-07-11 14-28-46.mp4\" controls></video>\n\n", "Grease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\n\n\nBroken: version: 3.3.0 Alpha\n\n\nWorked: Blender 3.2 \n\n\n\n\nGrease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\n\n\n\n\n - New scene.\n - Keep the cube.\n - Don't delete it.\n - Add an empty Grease Pencil Object.\n - Don't delete the cube.\n - Add a Line Art Modifier to the Grease Pencil Object,\n - Switch Source to Object, and select the cube.\n - Assign the default layer and material.\n - You should be seeing something like this\n\n\n\n - Add geometry nodes nodes to the cube.\n - yes keep the damn cube.\n - here is the simplest setup that involves instances that I could think of\n\n\n\n - as you can see in the viewport the grease pencil line art has dissapeared completely.\n\n\nThanks for looking into it.\n\n" ]

[ "Geometry Nodes editor, nodes click and drag area broken in Blender 3.2 Beta\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.23.04 30.0.13023.4001\n\nBroken: version: 3.2.0 Beta\nWorked: Working in 3.1 and older\n\nGeometry Nodes editor, nodes click and drag area different compare to blender 3.1 and the shader editor. \nCan't click and drag on Output socket row and socket text.\n\n\n\nIn red highlighted areas where you can click and drag the nodes \n\n\n", "Regression: Click Dragging on Socket Labels does not register\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\nWorked: Definitely 3.1. (I think I noticed the error only in the last 3-4 days)\nCaused by 484a914647\n\nClick dragging nodes in the node editor does not register when clicking over a socket label.\nIn geo nodes. Doesn't seem to happen in Shaders.\n\n - Add a new node tree.\n - Add several nodes.\n - Click and drag on different nodes that are not currently active.\n - Sometimes the click won't drag the node (specifically on sockets)\n\nor \n - Add new GN tree\n - select group input node\n # Click & drag somewhere around socket label of Group output node\n[2022-04-16 18-27-05.mp4](2022-04-16_18-27-05.mp4)", "Moving/tweaking multiple selected nodes my clicking and dragging only moves 'active' node\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.0 Alpha\nWorked: 3.1.1\n\nIf you have multiple nodes selected in the node editor (geomertynodes, shader, composite) and you want to move them by clicking and dragging, it only moves the node you clicked on, not all selected nodes (how it used to work in 3.1)\n\nDon't know if this is intended since, there was some work done on the tweak in the past days to unify it with the tweak in 3D viewport, where it always used to work like this.\n\n - Add a new Geometrynodes tree to the default cube\n - Add multiple nodes into the tree (don't need to be connected)\n - Select multiple nodes (with the selection tool of your choice, box, lasso, 'A' on the keyboard)\n - Try to move the nodes by clicking and dragging on one of the selected nodes\n # Have a nice day :)\n[Tweak_multiNode.mp4](Tweak_multiNode.mp4)" ]

[ "smaller startup.blend\nNot sure if this is technically a bug, but...\n\nI notice that `startup.blend` includes 64 blocks of type `MTex` that don’t seem to be referenced anywhere. Loading the startup file into Blender and then saving it without making any changes removes these blocks.\n\nEnclosed [startup.blend](startup.blend) is a copy of `startup.blend` from the current Blender source tree after processing through my experimental [blendhack ](blendhack) script to remove the unreferenced blocks. I also saved it with 32-bit rather than 64-bit pointers, which knocks about another 50K off the size.\n\nI also note the potential for information leaks in the current procedure for saving `.blend` files; for example, fixed-length fields containing null-terminated strings retain traces of previous values after the terminating null. And the saving of in-memory addresses can give hints about the configuration of the system on which the file was saved.", "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.", "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.", "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", "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", "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", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\n\n", "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", "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", "HIP related bugs\nThere are multiple bug reports following the release of 3.6 on the stability and the consistency of HIP, combine them here for easier access:\n\n- #109415 Geometry appears to be tearing up\n- #109417 #110459 Crashes\n- #109418 #109421 Material appears to be white\n- #109477 #110841 crash with RT enable\n- #109521 HIP binary kemel for this graphics card compute capability (9.0) not found.\n- #109553 \"Out of memory\" when HIP is on but fine when off.\n - ~~#110126 Under-reporting memory usage on windows+AMD, could be the same cause as the above one.~~ Mis-categrization, This one does not have HIP enabled.\n- #109562 libamdhip64.so library location/install issue\n- #109811 Linux crash with `HSA_STATUS_ERROR_INVALID_ISA: The instruction set architecture is invalid.`\n- #110392 #111198 Crash on driver `AMD Adrenaline 23.7.1` and `23.7.2` but fine on `AMD Adrenaline 23.5.2`.\n- #111546 Crash on `23.8.1` with `Radeon RX 6800XT`\n- #111569 Crash on `23.7.2.230718`\n- #111685 5700xt `22.20.27.09.230330` hangs (not sure if this is real crash yet)\n- #112177 \"Instant crash on high polygon\", User pref erroneously shows two identical AMD cards instead of one.\n- #112608 6950 XT (navi21, LLVM 16.0.6, DRM 3.54, 6.5.3-300.fc39.x86_64) crash without backtrace, Fedora Linux 39", "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).", "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", "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", "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", "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\n\n" ]

[ "Closing startup\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 21.10.2 30.0.13025.5005\n\nBroken: version: 2.93.5\nClosing all the time opening please fix this\n\nFlikkering closing on startup not opening\n\n\n\n" ]

[ "Cycles render artifacts relating scene scale\nOperating system: Windows 10\nGraphics card: tested multiple graphics cards with same issue\n\nBroken: 2.83.6 (file originally made in 2.79 and had the same issue)\n\nThere exists in the blend file data only two objects - the camera and a simple plane. Yet when rendering, the result does not match the viewport and there seems to be another ghost object appearing in the scene.\n\nBased on the following startup file: [strange-error.blend](strange-error.blend)\n\n1. Switch to rendered view in the viewport. This is how things should look.\n2. Now render the current frame at frame 97. Notice the strange ghosting effect in the center of the frame.", "Eevee: Soft shadows causing flickering in animation and temporal AA in scenes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.80\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nEevee soft shadows in objects with thin reflections causes flickering in animation and temporal AA in still images. This type reflections common in interior Arch Viz.\n\nScene 1 example of flickering of soft shadows in animation. I have remove all light probes and effects to focus only light and shadows. Open attach file \"Scene1_AA_eevee.blend\".\nRender the animation with Soft Shadows ON. Then Render animation with Soft Shadows OFF.\n[Scene1_AA_eevee.blend](Scene1_AA_eevee.blend)\n\nAnimation with Soft Shadows ON. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_eevee.mp4](Scene1_AA_eevee.mp4)\n\nAnimation with Soft Shadows OFF. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_No_SShadow_eevee.mp4](Scene1_AA_No_SShadow_eevee.mp4)\n\nAnimation in Cycles for comparison. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_cycles.mp4](Scene1_AA_cycles.mp4)\n\n******************************************************************************************************\nScene 2 example of temporal anti-aliasing cause by soft shadows. I have simplify the scene 2 to focus only light and shadows. Open attach file \"Scene2_AA_eevee.blend\".\nRender Image with Soft Shadows ON. Then Render Image with Soft Shadows OFF.\n[Scene2_AA_eevee.blend](Scene2_AA_eevee.blend)\n\nRender image with Soft Shadows ON. Make sure to view at full size. Notice the temporal AA on the edges on horizontal counter, vertical counter, oven handle and oven racks.\n\n\nRender image with Soft Shadows OFF. Make sure to view at full size. Notice the temporal AA is gone.\n\n\nRender image with Cycles for comparison. Make sure to view at full size.\n\n\n", "Running multiple instances of Cycles HIP ends in segfault\nOperating system: Windows 10\nGraphics card: 2x Radeon W6800 32GB\n\nBroken: 3.0.0, 3788003cdaeb, master, 2021-11-30\nWorked: Never\n\nWhen I have 2 instances of Cycles rendering using HIP at the same time on a particular production scene, one instance will crash with the following error: \n\n\n```\n...\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.57 | Mem:1469.81M, Peak:1469.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Furniture_Roughness.png\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.70 | Mem:1533.81M, Peak:1533.81M | Scene, View Layer | Updating Images | Loading Metal02_nrm.jpg\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.73 | Mem:1569.81M, Peak:1569.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Objects_normal.png\nFra:441 Mem:9030.99M (Peak 9030.99M) | Time:00:21.73 | Mem:1570.69M, Peak:1570.69M | Scene, View Layer | Updating Images | Loading Tires_rough.png\nMalloc returns null: len=37748736 in Cycles Aligned Alloc, total 1149156740\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFED98C853D\nModule : amdhip64.dll\nThread : 00000734\n\n```\nI was unable to reproduce it in a simple scene or any commonly available demo scenes such as classroom or Barbarshop. And unfortunately I cannot share the particular scene that's causing the issue. But the scale of the scene that's crashing should easily fit onto the GPU vram three times.\n\nI've attached the crash report. If more info is needed I will try to create a dummy scene that show the same behavior.\n\n[Anim-A-Garage.crash.txt](Anim-A-Garage.crash.txt)", "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.", "Normal Baking Inconsistence\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.0 Alpha\nWorked: unknown\n\nNormal baking result is different from original.\nAs below, a texture is baked to be used as normal map. Using \"Normal\" bake type the result is inconsistent with the original normal. A baking result using \"Emit\" type is used for comparison.\n\nDiffuse shader :\n[Correct (Diffuse).mp4](Correct__Diffuse_.mp4)\n[Incorrect (Diffuse).mp4](Incorrect__Diffuse_.mp4)\n\"Emit\" bake type has identical result to the original one, while \"Normal\" bake type has a little dimmer color.\n\nGlossy shader :\n[Correct (Glossy).mp4](Correct__Glossy_.mp4)\n[Incorrect (Glossy).mp4](Incorrect__Glossy_.mp4)\nDue to image resolution, the result of \"Emit\" type has acceptable differences at the edges of the squares. The result of \"Normal\" type has areas that shouldn't be brighter/dimmer (check from multiple view angles in the file below).\n\n[Bug Report.7z](Bug_Report.7z)\n\n\n - This is the node setup to generate the texture : \nThese nodes simulate the kind of texture that will connect into \"Normal Map\" node so that it can also be baked using \"Emit\" type.\n\n\n\n - Use the \"Material Output\" nodes to view the differences : \n\n\n\n - If re-bake, use 16-bit color depth can help to get the similar result from original nodes.", "panormic camera inverts the vector pass when rendering with Cycles.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.3.0 Alpha\n\n\nOpen below blend file and go to the compositor. For convenience I've included the rendered exr vector sequence, but you can recreate by rendering the animation with the pano cam and then the standard cam if you like. The panoramic/fisheye cycles render has inverted the vector pass data, whilst the standard/perspective cam is correct. \n\n[fisheye vector pass bug.zip](fisheye_vector_pass_bug.zip)\n\n", "Make \"offset edge loop\" slide evenly\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)\n\n\n\n[2019-09-17_15-04-45.mp4](2019-09-17_15-04-45.mp4)\n\nJust repeat the video example\n", "Can't Animate Texture Mapping Offset For Particle Hair\nWindow 7 64bit 8gb\nnvidia 660\n\nBroken: 2.72 RC\nWorked: I thought this was possible all the way back into the 2.4 series.\n\nAdd a single keyframe to particle texture mapping coordinates.\nMove to another frame and type a new number in the *Offset* mapping field and it will jump back to the number of the first keyframe.\nIn this state there is no way to animate the*Offset*. Even if I insert the same value at the new time location and edit the value in the graph editor the system still refuses to use the *Offset*information for the particle system hair density.\n\nOpen the Attached BLEND file and type a new number in the *X Offset* field.\nThe system refuses to accept the input and resets to the keyframe value.\n\nNOTE: This seems to only be a problem in the *Offset* and *Size* properties for Mapping. You will also see in the BLEND file that I have successfully keyframed the R value of the RGB without experiencing the same problem.\n\n[27_sequin_star_curtain_1a.blend](27_sequin_star_curtain_1a.blend)\n", "Eevee: UV map tangent forces first UV layer when in edit mode\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: 3.3.0 Alpha\nWorked: unknown\n\nWhen entering edit mode Eevee seems to always use the first UV layer for the tangent information, even when another UV layer is specified.\nI thought maybe it would fallback to the UV layer set to `active render`, but that doesn't seem to be the case.\n[UV_tangent_edit_mode_eevee-2022-07-07_14.16.48.mp4](UV_tangent_edit_mode_eevee-2022-07-07_14.16.48.mp4)\n\n[UV_tangent_edit_mode_eevee.blend](UV_tangent_edit_mode_eevee.blend)\nFrom file:\n- toggle edit mode and object mode\n\nFrom scratch:\n- create second UV layer on default object\n- rotate UVs\n- create shader with tangent map of second UV map\n- toggle edit mode and object mode\n\n", "VSE image sequence playback order is sensitive to file sort order in file picker\nOperating system: NixOS 20.09 (Nightingale) x86_64 \nGraphics card: NVIDIA GeForce 940MX \n\nBroken: since at least 2.91.0 as of , still broken on 2.93.1 Release Candidate, 7edbe463d2d9 (splash screen doesn't give more detailed info)\n\n\nImage sequences added to the VSE play in the order the files are displayed in the file picker. (Reverse order plays sequence backwards and sort by size plays the sequence in an order depending on file sizes) Since at least 2.92.0 as of https:*download.blender.org/release/Blender2.92/ this plays frames in reverse order by default (the default display and sorting parameters seem to have been changed) Seems similar to https:*developer.blender.org/T73930\n\nPick Video Editing from the splash screen, hit Shift A to add an image sequence, navigate to folder and select everything with A. Sort files by size and/or in reverse. Import frames and play sequence.\n\nI believe this to be a bug and not intended behavior. Thanks for taking a look and have a nice day.", "Motion blur artifacts on certain frames EEVEE\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0 Alpha\nWorked: not sure\n\nMotion blur on error appears on same certain frames.\n\nblend attached Error appears on frames : 49 , 60, 85, 95, 103, 119,130\n\n[blur test.blend](blur_test.blend)\nnormal frame \n\nerror frame \n\nvideo with error frames [0001-0300.mp4](0001-0300.mp4)\n\n", "EEVEE 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", "In eevee, shading disappears when SSS is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0\nWorked: -\n\nShading disappears in Eevee if one object is located on another object and both have Subsurface enabled\n\nWhen an object has no shading, it looks unrealistic and wrong.\nTo get around this bug, I render two images and connect them in the compositor.\n\nMaybe it is possible to somehow enable these shading without a second render?\nSSS is needed for both objects.\n\nBall Subsurface On (0.02)\n\nBall Subsurface Off (0.0)\n\n\n.Blend file\n[bugshafowsubsurface.blend](bugshafowsubsurface.blend)\n", "Eevee: Unknown bug when just create first shader \nStep to reproduce an issue (or bug?):\n1. Run latest Blender v3.4alpha (Experimental build) with Eevee Next integrated.\n2. Create scene with just one Cube.\n3. Go to Properties > Material panel > Create New material.\n4. Boom! Blender shut down imidetily.", "Line Art isn't updating active camera\nOperating system: GNU/Linux mint 19\nGraphics card: gforce RTX 2060\n\nBroken: 2.93.4 \n\nLine Art isn't updating active camera when it's changed in a 'Scene' strip (VSE)\n\n\n- Create a scene, a camera and a LineArt object.\n- Now, create a 2nd camera (Cam.001) (not the active one)\n- Create an empty scene in order to be used for video creation.\n- In `Video Sequencer`, add a Scene strip and choose the Cam.001 camera ->it changes ok, but lineart goes dependent on the first one.\n\nTest File:\n[#91971.blend](T91971.blend)" ]

[ "EeVee/Workbench: image sequence offset doesn't have the expected behavior (as seen in Cycles)\nOperating system: Linux and Windows\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116 / Radeon (TM) RX 480 Graphics\n\nBroken: version: 2.80rc1\nWorked: (optional)\n\nA camera with an \"offset\" Background Image sequence causes an object texture with \"Window\" texture coordinates to be offset as well, but only in EeVee (not Cycles)\n\nImage sequence:\n[images.tar](images.tar)\nBlend File:\n[imageSequenceTest.blend](imageSequenceTest.blend)\n\n* Download the attached images and .blend file.\n* Decompact the images in the same directory as the .blend file but within a folder named `images/`.\n* Open attached file.\n* Switch the selection between the mesh and camera to compare image sequence settings in the mesh material and camera background. (Must be the same).\n* Forward some frames, note that the images are synchronized.\n* In any of the image settings (for example the background), change the offset and forward or backward some frames.\n* In Eevee and Workbench it makes no difference other than not finding some images in the sequence.\n* In Cycles it works correctly.\n\nThis can be observed causing an issue at ~13:35 in this video: 8irtcgc8GqE?t=814\n...In that tutorial video, the instructor is removing a large tracking marker using \"Window\" texture coordinates. At ~13:35 he switches from EeVee to Cycles to do the texture baking on to the overlay plane.\n\nThe image sequence on the textured plane aligns perfectly with the duplicate background image sequence when the renderer is set to EeVee, but when he switches to Cycles, it is misaligned. ~~Strangely, though, I don't think the camera object is using an \"offset\" in that case, so perhaps the bug (if it is one) goes deeper than I have supposed.~~ [update: turns out he did set an offset, though I'm not clear if it was already in place at the timestamp in that video.]\n\n**Another way to reproduce the bug:**\n* open blender with fresh/clean profile directory\n* delete default cube, add a plane, create a new material\n* in shader editor, delete BSDF node, add Image Texture node, connect Color output to Surface input of Material Output node\n* add Texture Coordinate node, connect Window output to Image Texture \"Vector\" input\n* in Texture Node, open provided image sequence, then enable \"Cyclic\" and \"Auto Refresh\"\n* select main camera; in Properties -> Camera pane, enable Background Images, click \"Add Image\" and then \"Open\" the same image sequence as before; Change Alpha to 1.0\n* assume camera view with numpad-0, change to rendered mode (EeVee, by default)\n* observe that the background image and the plane texture are in sync, as expected, even when changing frames\n* change render mode to Cycles, and observe the same\n* select camera object in outliner; in Properties->Camera->Background Images, change the Offset to 1\n* observe that in Cycles, the plane texture and background textures are offset by 1 frame\n* observe that in EeVee, they are not: the plane adopts the offset of the camera background image", "Randomized \"Start Frame\" of Image Sequence gives different result in Eevee and in Cycles\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 555 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nI have bunch of objects, each with unique Material, and each one has the same Image Sequence, with randomized Start Frame. Rendering it using Cycles gives the correct result.\n\n\n\n\n\n\n\n\n\nRendering in Eevee however, gives wrong result, each one is the same.\n\n\n\n\n1. Import Image Plane, sequence of images, for example from here:\nfree-vfx-image-sequences-flipbooks/\n\n2. Make duplicates of the plane. We want each plane to have the sequence running at different start frame, cyclic is turned on.\n\n3. I know the fact that we need to have each single user Material. Sometimes I think we need single user Image Texture too.\n\n4. However, I realized Cycles only need single user Material and can use the same Image Texture. Eevee does not work however, hence I am questioning whether this is a bug, or a known limitation.\n\n", "EEVEE image sequence frame offset not working [in multiple image texture nodes having the same image datablock]\nOperating system: WIN 10\nGraphics card: RTX 2070\n\nBroken: 2.81 date 2019-09-08\nWorked: none\n\nif I use one video texture in different materials, I only change the frame offset of the texture node\n- CYCLES: work as expected ( image is offset in time)\n- EEVEE: all materials use the same frame of the video texture\n\n\n\n\n\n[test_offset_blender-02.zip](test_offset_blender-02.zip)\n\n\nset viewport to \"rendered\" mode. just switch from EEVEE to CYCLES to see the difference (the number displayed on the texture is the frame number of the texture)" ]

[ "GizmoGroup with setup_keymap() doesn't work if addon is enabled by default\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: all versions so far\nWorked: never\n\nIf an addon is enabled by default, any of its GizmoGroup with setup_keymap() classmethod won't react to user input (if they are registered in the register() function). However, if they are registered during the normal operation (i.e. after Blender initializes and draws the first frame), the problem does not appear.\n\n1. Install the attached addon.\n2. Enable the addon (it's called \"!Gizmo test!\").\n3. Save Blender preferences.\n4. Close Blender.\n5. Open Blender.\n6. Select a camera and try dragging the circular gizmo. The gizmo won't react to the input.\n7. Disable the addon, then enable it again.\n8. Select a camera and try dragging the circular gizmo. Now it will rotate the camera.\n[gizmo_test.py](gizmo_test.py)", "Changes to a PropertyGroup in the preferences of an addon do not trigger the flag indicating changes to save\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\nUser preferences and add-on preferences are normally auto-saved when Blender exits, and it is triggered when the user modifies preferences data through the UI.\nBut there appears to be a bug that prevents this from happening when the preference data is defined inside of a property group.\n[2020-01-08 16-39-50.mp4](2020-01-08_16-39-50.mp4)\n\n- Install the simplified addon attached - (simple script that adds/draws two preference variables for an add-on: One directly inside of a class derived from `bpy.types.AddonPreferences`, and one inside of a class derived from `bpy.types.PropertyGroup`)\n- In the addon UI, modify any the group preferences - (neither value will be saved on exit)\n- In the addon UI, modify the root preference - (dirty flag or auto-save will be triggered)\nA similar issue occurs when preference values are programmatically altered (auto-save is not triggered), but I'm not sure if this is a bug, or lack of a feature.\n[user_pref_addon.py](user_pref_addon.py)", "Not updating links when deleting node group sockets\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.0\nWorked: never!\n\nRemoving NodeSocketInterface sockets from groups removes sockets from NodeGroupInput, and if they were connected to a multi-input, its connection point move higher and leave the connection place with the socket.\n<video src=\"attachment\" title=\"2023-04-20 07-25-38.mp4\" controls></video>\n\n1. Сreate many geometry sockets for the group\n2. Add \"Node Group Input\" node\n3. Add \"Join Geometry\" node\n4. Connect all geometry sockets from \"Node Group Input\" to \"Join Geometry\" multi-input\n5. Use the N panel to remove geometry inputs from last to first\n", "Menu label does not update after \"Remove Shortcut\" from context menu\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: all\n\nAfter \"Remove Shortcut\", the menu label is not updated properly.\nJust for a moment, but it's noticeable.\n\n**Only in the case when the \"Remove Shortcut\" menu item (mouse cursor actually)\nis located above the deleted item or above separator.**\n\n", "Pinning Bones/Constraint Tabs in Properties Editor doesn't work\nBroken: 2.76 - master (1283c66)\nWorked: Unknown\n\nThe context pinning functionality in the Properties Editor doesn't work for Bones and Constraints. There may be a few others too that I haven't noticed yet, but these are the biggest ones.\n", "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", "Mirror Paste for pose bones also copies custom properties\nBroken: 2.80, 02581a7ef819\n\nI'm making a rig where I store some custom properties in my face bones which I make use of with a script.\n\nWhen using Ctrl+C to copy a pose, then Ctrl+Shift+V to Mirror-Paste, the values of the custom properties of the copied pose bone(s) get pasted into the opposite bone **if** said opposite bone had custom properties with the same name.\n\n[mirror_paste_pastes_custom_props.blend](mirror_paste_pastes_custom_props.blend)\n- Download attached blend\n- Note that left_bone has a property called \"prop\" and its value is the string \"left bone's info\"\n- Note that right_bone has a property called \"prop\" and its value is the string \"right bone's info\"\n- press Ctrl+C then Ctrl+Shift+V\n- right_bone['prop'] now reads \"left bone's info\".\n\nOne might argue that this is an intended feature, but then the operator should be called \"Copy Pose and Properties\" not \"Copy Pose\"! :P (Realistically, \"Copy Properties\" could be added into the Copy Attributes addon.)\n\n**Workarounds**\nThe bone-specific custom properties can be stored in the edit_bones but this is problematic since edit_bones can only be accessed when the skeleton is in edit mode.\nAlternatively, the custom properties names can be pre/suffixed with the bone's name, which is ofc pretty redundant, but it prevents the bug since the property names will no longer match.", "Hair: changing children related settings in objectmode dont show when switching to particle editmode\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83.7\nWorked: 2.79\n\nWhen I change additional options like Clumping, children not updates and their update stuck for edit mode for any try except 1st. \nDemonstration and details:\n[2020-10-15_01-46-01.mp4](2020-10-15_01-46-01.mp4)\n\n#69000 (Hair: changing children related settings not updating in particle editmode) is very much related", "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", "Scaling in edit mode with individual origins and snapping activated is broken\nWin7 x64\n\nBroken: 2.76\n\nFollowing #39161. Scaling in edit mode works well with \"median\" as pivot point but with \"individual origins\" it breaks.\n\n\nIn attached file:\nScale and choose a vertex with \"ctrl\" pressed, cube seems to disappear.\nTo compare, press \"G\" and choose a vertex for snap, the cube's center is moved as a cube (also individual origins could make all selected verts move to that position making a point instead of a cube?) to that vertex.\nScale with \"median\" as pivot, it works\n[bug scale individual origins.blend](bug_scale_individual_origins.blend)\n\nSo maybe to make it consistent, make \"individual origins behave like median.\n", "Modifying Basis shape key .co via script in Object mode desyncs from mesh vertices causing new from_mix=False shape keys to revert script changes\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 471.11\n\nBroken: 2.79.0, 2.80.75, 2.93.7, 3.0.0, 3.2.0, 3.3.0 Alpha (branch: master, commit date: 2022-06-07 18:08, hash: 173a15bcda) (I have not tested any versions older than 2.79.0)\nWorked:\n\nModifying the Basis shape key of a mesh via script in Object mode does not update the mesh vertices to match the changes to the Basis shape key.\nWhen creating a new shape key with `from_mix=False`, the newly created shape key matches the positions of the mesh vertices instead of the Basis shape key, making the new shape key effectively undo the modifications via script.\nThis is confusing because there is no way to tell through the UI that the mesh vertices and Basis shape key have become desynchronised due to a script.\nFixing the desynchronised state is at least fairly simple, going into Edit mode and back out to Object mode will cause the mesh vertices to update to match the basis shape key, fixing the desync (of course, the script could also be modified to propagate the changes to the mesh vertices too).\nI'm unsure if the issue here should be considered the desync between basis shape key and mesh vertices, the behaviour of creating new shape keys with `from_mix=False` or a fault with the script for not also updating the mesh vertices, causing the desync in the first place.\n\n- Add a shape key to the default Cube so that the Cube now has a Basis shape key\n- Modify any of the .co of the Basis shape key's .data while remaining in Object mode by using a script or the Python console, e.g. `bpy.context.object.data.shape_keys.reference_key.data- [x].co.x += 1`\n- Add a new shape key to the default Cube with `from_mix=False` (either the UI, the operator used by the UI or the shape_key_add method of the Cube Object)\n- The newly created shape key will match the original cube shape instead of the basis shape key shape, so when activated (value -> 1.0) it will revert the mesh's shape back to the original cube shape\nAlternative steps to reproduce only the desync without creating a new shape key with `from_mix=False`:\n- Add a shape key to the default Cube so that the Cube now has a Basis shape key\n- Modify any of the .co of the Basis shape key's .data while remaining in Object mode by using a script or the Python console, e.g. `bpy.context.object.data.shape_keys.reference_key.data- [x].co.x += 1`\n- Remove the basis shape key from the Cube such that it no longer has any shape keys, the mesh will revert back to the original cube shape when doing so\n - If you were to instead go into Edit mode and back out to Object mode before removing the Basis shape key (thus fixing the desync), the Cube will remain in the shape of the Basis shape key when the Basis shape key is removed.\n\nModifying the Basis shape's .co via foreach_set('co', my_co_array) has the same issues, but note that it does not update the visuals of the cube in the 3D view immediately so it can appear as if it has done nothing until something else causes the visuals to update e.g.\n```me = bpy.context.object.data\nme.shape_keys.reference_key.data.foreach_set('co', [0,] * 3 * len(me.vertices))```\n\nIn both of these sets of steps, you can instead modify the .co of the mesh vertices to achieve the same issue, but with a reversed effect.\n\n----\nIf you select the default Cube as the active object, the following script will run through the first set of reproduction steps, creating shape keys with both `from_mix=True` and `from_mix=False` and printing whether they match the basis and if not, printing whether they instead match the mesh vertices:\n```import bpy\n\ndef cos_equal(shape_data_or_vertices1, shape_data_or_vertices2):\n```\n for data1, data2 in zip(shape_data_or_vertices1, shape_data_or_vertices2):\n if data1.co != data2.co:\n return False\n return True\n \n```\n\ncube = bpy.context.object\nme = cube.data\n\n# Remove all shape keys if the script has been run previously\nif me.shape_keys:\n```\n bpy.ops.object.shape_key_remove(all=True)\n```\n\nprint(\"\\nTesting shape keys in {}:\".format(bpy.app.version))\n\nbasis_shape = cube.shape_key_add(name='Basis')\n\nassert me.shape_keys.reference_key == basis_shape\n\n# Newly created Basis shape key should match the mesh vertices\nfor v, b in zip(me.vertices, basis_shape.data):\n```\n assert v.co == b.co\n```\n\n# Modify the basis shape key via script in some way\nbasis_shape.data- [x].co.x += 1\nprint(\"Modified basis shape key via script\")\n\nif cos_equal(me.vertices, basis_shape.data):\n```\n print(\"Basis shape key matches mesh vertices\")\n```\nelse:\n```\n print(\"Basis shape key does not match mesh vertices, there is desync!\")\n```\n\n# Create new shape key, from mix, using the shape_key_add funtion\nnew_shape_from_mix = cube.shape_key_add(name='from_mix=True', from_mix=True)\n\nassert new_shape_from_mix.relative_key == basis_shape\n\nif cos_equal(basis_shape.data, new_shape_from_mix.data):\n```\n print(\"from_mix=True matches basis shape key\")\n```\nelse:\n```\n print(\"from_mix=True does not match basis shape key!\")\n```\n # Compare against the mesh vertices instead\n```\n if cos_equal(me.vertices, new_shape_from_mix.data):\n print(\" from_mix=True matches mesh vertices\")\n else:\n print(\" from_mix=True does not match mesh vertices\")\n```\n\n# New shape key, not from mix, created using the shape_key_add funtion\nnew_shape = cube.shape_key_add(name='from_mix=False', from_mix=False)\n\nassert new_shape.relative_key == basis_shape\n\nif cos_equal(basis_shape.data, new_shape.data):\n```\n print(\"from_mix=False matches basis shape key\")\n```\nelse:\n```\n print(\"from_mix=False does not match basis shape key!\")\n```\n # Compare against the mesh vertices instead\n```\n if cos_equal(me.vertices, new_shape.data):\n print(\" from_mix=False matches mesh vertices\")\n else:\n print(\" from_mix=False does not match mesh vertices\")\n```\n```\nExample script output in the System console:\n```Testing shape keys in (3, 0, 0):\nModified basis shape key via script\nBasis shape key does not match mesh vertices, there is desync!\nfrom_mix=True matches basis shape key\nfrom_mix=False does not match basis shape key!\n```\nfrom_mix=False matches mesh vertices```", "catalog_simple_name doesn't refresh when renaming catalog\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 531.79\n\nBroken: version: 3.6.1\n\n\n`asset_data.catalog_simple_name` doesn't refresh when renaming catalog.\n\n- create an asset and move it to a catalog\n- Call `D.collections[\"xxx\"].asset_data.catalog_simple_name` in python console (gives the right result)\n- But if you rename the catalog, `.catalog_simple_name` hasn't updated. It still outputs the old catalog name.\n\n", "Mirror UI in does not update immediately when a shortcut is assigning \nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.2.0\nWorked: for sculpt mode it used to work in blender 2.80-2.92, broke in blender 2.93 and up. \n\nAssigning a shortcut to the mirror widget in any mode does not immediately trigger a ui update when pressed.\n\n- Enter sculpt or any other mode\n- Assign shortcut to the mirror x widget, v for example since its unassigned by default \nUI does not update immediately when pressing the shortcut, mouse cursor need to hover over the ui to trigger the update, this used to work in 2.80-2.92, but since 2.93 and up the ui does not refresh after pressing the shortcut. \nVideo of the issue:\n[Blender 2022-07-02 14_30_21_Trim_Trim.mp4](Blender_2022-07-02_14_30_21_Trim_Trim.mp4)", "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.", "Switch View Node does not get updated when clicking `update views` button\nOperating system: MacOS Ventura 13.4\nGraphics card: M2 Max\n[system-info.txt](attachment)\n\nBroken: 3.6 LTS\n\n## Not sure if it is a bug, or it is just my misunderstanding.\nSwitch View Node does not get updated when clicking `update views` button. (I expect that there should be a new input socket `RenderView`)\n\n\n1. Add a switch view node and (optinally connect it into the node tree)\n2. Check stereoscopy and add a view.\n3. click the `update views` button in the side panel.\n\n<video src=\"attachment\" title=\"Screen Recording 2023-07-09 at 5.10.54 PM.mov\" controls></video>\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" ]

[ "Particle System Orientation Axis set incorrectly after file load\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1070\n\nBroken:\n2.82 Beta, 507a331f0182, blender2.8, 2020-01-27\n\nAfter undoing any change, every particle system in the scene resets its orientation axis. To fix this, you have to manually change the orientation axis to something else and back again. There may be other situations where the particle orientation gets reset, but this one is easily reproducible.\n\n1. Open the attached file\n2. Set the ParticleSettings>Rotation>Orientation Axis to Global Z\n3. Shift-A and add a cube (or any change at all to the scene)\n4. Ctrl-Z\nThe particles are not longer aligned on the global z-axis. \n\nAlternatively, it also breaks if you:\n1. Open the attached file\n2. Set the ParticleSettings>Rotation>Orientation Axis to Global Z\n3. Save the file\n4. Close and reopen the file\n\n[ParticleBug.blend](ParticleBug.blend)\n", "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)", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)", "Particle Emitter - Particles collisions not accurate\nOperating system: Linux-5.11.0-40-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha\nWorked: This has been an ongoing problem since starting with Blender from 2.8\n\n\nParticles are not respecting collision system in every case.\n\n- Create plane and add particle system\n- Give emitted particles a positive or zero gravity value in field weights\n- Add wind force field running roughly parallel to plane.\n- Add turbulence.\n- Add collision system to plane\n\nExpected behaviour is for the particles to bounce off the plane as they are emitted in a positive Z direction and blown by turbulence against the plane. Instead they often break through. In the past this has meant that particles are bypassing the collision system such that emitted bubbles break through the hull of a submarine, and in my current case, half my sand particles to be hidden from view in a desert scene.\n\nNote attached file which shows the behaviour. Watch the simulation side on and particles can clear be seen breaking through the mesh.\n\n[Sand Wind Test.zip](Sand_Wind_Test.zip)\n\n\n\n", "Particle system baking messes particle dietime (that in turn messes up particle textures)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.0\n\nIf texture with color ramp is used for animating particle size through lifetime, in ~10 last frames of simulation all particles PERMANENTLY getting smaller until totally disappear lol, and it occurs only if using BAKE.\nthis is not animation, this is 100% bug, looks like particle size animation is applied to WHOLE particle system respectively/relatively to all scene timeline, and is overriding every single particle age at the end of timeline.\n\nFile uploaded.\nParticle systems in blender are SOOOO broken, the way how it works is so facepalmable, particularly \"bake\" and \"textures\".\nlooks like in my case they met lol\n", "Hair particles rendered as an object do not follow parent object when the parent object is falling under gravity as a rigid body when animating\nOperating system: Microsoft Windows 10 Home, Version 10.0.18362 Build 18362\nGraphics card: GeForce GTX 1080\n\nversion: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4caf4, type: Release\nbuild date: 2020-03-12, 15:41:08\nplatform: Windows\n\nI have an issue where i have a cube mesh, I create hair particles, and set the hair to render as an object, say a cylinder. I then enable rigid body physics for the cube. I also have a passive plane below the cube. When I run an animation, the cube falls as if under gravity and stops at the plane, but the cylinder particles remain in their original position?\n\nIf I add soft body physics to the cube and order the soft body physics before the particle settings, then the cylinders fall, but lag behind the cube. The cube falls through the plane below, but the cylinders are stopped by the plane?\n\nWith soft body added (to top of stack). Particles do fall but have a lower acceleration rate, and the cube no longer detects the floor and passes through the plane?!\n\nThanks!!\n\nSee attached blend file [StackExchangeParticleProblem-001.blend](StackExchangeParticleProblem-001.blend)", "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", "Hairs & custom normals\nOperating system: Linux 5.10.0-5-amd64 #1 SMP Debian 5.10.26-1\nGraphics card: Radeon RX 560 Series\n\nBroken: 2.92 (from snap)\nWorked: not known\n\n\nHairs does not consider edited ‘custom normals’ and still use ‘face normals’.\n\nLook at attached screenshot.\n\n[test_normals.blend](test_normals.blend)\n", "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)", "Duplicating hair particles from one file to another is not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0\nWorked: I don't know. And at least, v3.2.1 is also affected.\n\nFor Eevee rendering, duplicating the hair particles within the same file is working as expected, because the duplication and the original hair look exactly the same. \nHowever, duplicating the hair particles from one file to another is not working for Eevee rendering, because they do not look identical. \nMoreover, under the Eevee rendering, the duplicated hair can no longer be controlled by the particle system. (In comparison, Cycles rendering is not affected by this problem.)\n\nThe video to reproduce the error:\n[Duplicate hair under Eevee.mkv](Duplicate_hair_under_Eevee.mkv)\n\n**Steps to reproduce**\n[eevee hair test3.blend](eevee_hair_test3.blend)\n\n- Open file\n- Copy objects `LLonglash` and `LLonglash.001`\n- Open new file\n- Paste objects\n# Inspect hair shape\n\n", "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)", "Grid particles emitted from a volume behave strangely\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0\n\nWhen a particle system emitted from a volume uses grid distribution, many resolutions behave strangely for complex objects.\n\nStart with this .blend file: [grid bug.blend](grid_bug.blend) \n1. In the .blend, I modified an ANT landscape to make a manifold solid. I added a grid-distributed particle system emitting from its volume and displayed the particles as objects.\n2. Currently the emission > source > resolution == 36 and things look fine.\n3. Modify the resolution to be 35.\n4. You will see rows of particles that do not conform to the volume to an *extreme* degree.", "Parent with child containing particle emitter can't be moved on frame 1 keyframe\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Alpha\n\nEmpty in provided .blend file cannot be moved on frame 1 when it has a keyframe on frame 1. It can be moved on any other frame with or without a keyframe on that frame, or on frame 1 if it doesn't have a keyframe.\n\nSelect the Empty in the provided .blend file, and attempt to move it with `g`, transform sliders, etc. It will not move.\n\n[move_bug.blend](move_bug.blend)\n\nI'm not sure how I got my .blend file in this state, as my best effort at making a seemingly identical set of objects does not reproduce it. I'm guessing someone will have to inspect the internal state of these objects to find something amiss.\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", "\"Long Hair\" children pulled to world origin when using Texture (2.93.4 regression)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.4\nWorked: 2.93.3\n\nMy particle hair system works as expected in 2.91+ up to 2.93.3:\n\n\nIn 2.93.4, the children are pulled towards world (not object) origin:\n\n\nThis appears to only happen IF a texture is used to affect Density AND \"Long Hair\" is checked.\n\n\n\n1. Move default cube away from origin\n2. Add particle system\n3. Enable interpolated children\n4. Check \"Long Hair\"\n5. Add a Texture (even a cloud texture works)\n6. Enable Density influence\n\n\n\nBlend file with error:\n\n[Bug3.blend](Bug3.blend)\n" ]

[ "When changing particle type from Emitter to Hair and then back to Emitter, effect is missing\nWindows 10, GTX 1070\n\nBroken: Blender 2.8 Alpha 2, 0c8b0771f26\n\nWhen you change the Particle type from Emitter to Hair, and then back to Emitter, the effect is missing.\n\n1) Start a new scene\n2) Select the default cube\n3) Open the Particle panel\n4) Click New\n\nPlay the animation. and you'll see particles emitting from the cube\n\n5) Change the Particle type to Hair\n6) Change the Particle type back to Emitter\n\nPlay the animation. The particles aren't emitting from the cube\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", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "AlembicObjectPath has a fixed-size char[]\nAlembicObjectPath (see `DNA_cachefile_types.h`) has a fixed-size char- [ ] buffer. \n\n> In 3128600a8a#142412, @LazyDodo wrote:\n> if the object path can be arbitrarily large it's gonna be a matter of time before someone comes with a file with 4097 byte object path, why not just allocate the ram you need? \n\n\nI think that's a good idea, and that's what this task is for.\n", "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", "Crash opening file using Clump Curves on Particle Children \n****\n\nversion: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d49d, type: Release\nbuild date: 2019-12-04, 14:30:40\nplatform: Windows\n\n***********************************************************\n\nWhen I worked on a project using particles, after a short break I wasn´t able to reopen the project. The project crashed right after opening. When starting Blender from console the only error I could find was:\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF706DC271E\n\nno Blender log file was written!\n\nEven in debug mode there were no more hints but his one. I opened the project in an Ubuntu VM and it also crashed there. No chance to recover the file.\n\n\nUsing Particle following a nurbspath with Force Field \"Curve\".\nParticles rendered as objects.\nUsed Simple Children.\nWhen ticking the box: Use Clump Curve it crashes.\n\nEither Blender crashes right after ticking the box or when reopen the project. The latter then means that I´m not able to recover my work at all.\nI might have to do with particles already baked or not. Not sure. \n\n[T72763_crash_log.txt](T72763_crash_log.txt)\n\nfile written from c2a37867f2 that crashes on file read:\n[#72763.blend](T72763.blend)\nfile written from 2.79b that crashes on file read:\n[T72763_279.blend](T72763_279.blend)", "BLENDER DISPLAYS INCORRECT NUMBER OF VERTICES, TRIANGLES AND FACES IN VIEWPORT\nOperating system: Windows 11 Pro 10.0.22621 Build 22621\nGraphics card: NVIDIA RTX 2070 SUPER\n\nBroken: 3.5.1\nWorked: Do not recall, however, I first posted this issue in the Blender 3D Artists FB Page on Sept. 8, 2022.\n\nIn the 3D VIEWPORT, with STATISTICS turned on, Blender 3.5.1 (and many previous versions) randomly show the incorrect number of VERTICES, FACES and TRIANGLES ( most often it is something like 10 or 20 BILLION). This SAME error occurs OVER and OVER during my repeated \"daily\" blender usage. I estimate that I have seen it now at least 30 times since I first reported it. I CANNOT SAY WHICH ACTION TRIGGERS IT. Many others have acknowledged that they have seen the same thing. It is very annoying because I OFTEN have large scenes and TRULY need to know how large my scene is, but often cannot. SOMETIMES restarting blender helps, but then it happens again within the newly opened session.\n\nIT IS POSSIBLE that this only happens with fairly large scenes, but since my scenes are usually very large, I cannot say for sure.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nThe blender files where I KNOW it has definitely happened are too large, detailed and proprietary. Sorry, I cannot provide. If I happen to see it in smaller, unimportant blender file, I shall add it to this bug.\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.", "Normal map support in Cycles standalone\nWindows 8.1 64-bit\n\n**Cycles Version**\nd553b8de7180\n\n\nIn the latest version available in the Cycles standalone repository, commit d553b8de7180, using a normal map node in a shader graph will cause Cycles to crash. This behavior was not present in release 1.7.0 but has been added since then.\n\nThis looks to be caused by an improperly initialized member variable in the ccl::NormalMapNode type. Upon creating an object of type NormalMapNode, the ustring named 'attribute' is initialized such that attribute.c_str() will return a nullptr.\n\nCycles crashes when the nullptr used to construct a std::string in NormalMapNode::attributes in this bit:\n\n```\t\n\t\telse {\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent\").c_str()));\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent_sign\").c_str()));\n\t\t}\n```\n\n\nI have attached a simple cycles standalone scene that triggers this error here: [sample_scene.xml](sample_scene.xml)", "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).", "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", "Curve to Mesh node creates wrong face orientation with cyclic profile curve\nOperating system: Linux-6.1.26-x86_64-with-glibc2.37 64 Bits\nGraphics card: AMD Radeon RX 6800 XT (navi21, LLVM 15.0.7, DRM 3.49, 6.1.26) AMD 4.6 (Core Profile) Mesa 23.0.3\n\nBroken: version: 3.5.1, branch: Unknown, commit date: Unknown Unknown, hash: `Unknown`\nWorked:\n\nThe `Curve to Mesh` geometry node creates incorrect face orientation when using a cyclic `Profile Curve`. This bug only happens with cyclic profile curves, non-cyclic profile curves work correctly.\n\nInside of the attached `.blend` file there are two identical curves. The left curve uses the curve `Bevel` option. The right curve uses the `Curve to Mesh` geometry node.\n\nThey should produce the same results, but they don't.\n\nThe `Profile` curve is just a standard `Add` -> `Curve` -> `Circle`.\n\n1. Open the attached `.blend` file.\n2. Notice that the curve on the left has the correct face orientation.\n3. Notice that the curve on the right has the wrong face orientation.\n\n", "Segfault pasting stale driver.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\nDrives copied and pasted with significant change in file data in between can trigger segfaults. \n\n```\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nblender(BLI_system_backtrace+0x34) [0x55dfd70fd084]\nblender(+0xe151bd) [0x55dfd4bd41bd]\n/usr/lib/libc.so.6(+0x3cf80) [0x7f9b26870f80]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder26build_object_data_geometryEP6Objectb+0x170) [0x55dfd7000380]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder17build_object_dataEP6Objectb+0x54) [0x55dfd6ffb4b4]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x1d3) [0x55dfd6ffe2c3]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder22build_driver_variablesEP2IDP6FCurve+0x77) [0x55dfd6ffad87]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder14build_animdataEP2ID+0x1f9) [0x55dfd6ffe8b9]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x228) [0x55dfd6ffe318]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder16build_view_layerEP5SceneP9ViewLayerNS0_26eDepsNode_LinkedState_TypeE+0xb2) [0x55dfd7003892]\nblender(_ZN7blender3deg23AbstractBuilderPipeline16build_step_nodesEv+0x76) [0x55dfd6fea296]\nblender(_ZN7blender3deg23AbstractBuilderPipeline5buildEv+0x42) [0x55dfd6fea4b2]\nblender(DEG_graph_build_from_view_layer+0x33) [0x55dfd6fd24e3]\nblender(+0xef501a) [0x55dfd4cb401a]\nblender(wm_event_do_depsgraph+0xc5) [0x55dfd4f59245]\nblender(wm_event_do_refresh_wm_and_depsgraph+0x92) [0x55dfd4f593b2]\nblender(wm_event_do_notifiers+0x36a) [0x55dfd4f6055a]\nblender(WM_main+0x2b) [0x55dfd4f5532b]\nblender(main+0x367) [0x55dfd4b9da67]\n/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f9b2685bb25]\nblender(_start+0x2e) [0x55dfd4bd056e]\n\n# Python backtrace\n```\n\n\n* Add a custom property to the Scene.\n\n* Right click on its value field, and run \"Copy as New Driver\".\n\n* Run `CTRL`+`N` or \"File\" —> \"New\" —> \"General\".\n\n* Right click on any value field, and run \"Paste Driver\".", "Crashing/unexpected results while rendering custom Node-defined volumetric materials\nOperating system: Linux-5.6.0-2-amd64-x86_64-with-glibc2.29 64 Bits\nGraphics card: AMD Radeon (TM) RX 470 Graphics (POLARIS10, DRM 3.36.0, 5.6.0-2-amd64, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.7\n\nBroken: version: 2.91.0 Alpha\nWorked: Never\n\nWhen rendering the attached .blend file, Blender frequently crashes or at the very least fails to render properly. It seems to be something to do with the materials I've defined for Evee to use.\n\n\n[#79682.blend](T79682.blend)\n- Open file\n- Render animation", "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", "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" ]

[ "Exporting curves to Alembic crashes other software when reading\nwindows 8 64bit\n\nBroken: 2.77.3 1fe9d67\nWorked: (optional)\n\nThe curve import to others software will be report error, even cause crash\n\n[test.zip](test.zip)\n\nDownload the test file and import to maya, or houdini, the some curve type will make report error or cause crash.\n\nblender to blender:\n\n\nNurbs into Maya:\n![}V5$~AO7B5KW]A)O2AKY1_7.png](_V5__AO7B5KW_A_O2AKY1_7.png)\n\nPoly or Bezier into Maya:\n!- [x]R`2QT$~35E}7KPE{`UK`E.png](V_R_2QT__35E_7KPE__UK_E.png)\n\n![46HZM]9SDG3%`}OFX$V}F8P.jpg](46HZM_9SDG3___OFX_V_F8P.jpg)\n\nHave test with maya 16, maya 17 and houdini 15" ]

[ "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", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "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 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", "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)", " 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)", "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.", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "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)", "Lost hotkey with save preset\n2.80\n\n\nI finally can replicate problem from 2.7x and it is still problem in 2.80. When you change some combination of hotkeys and save it to the preset. You lose some of them. On my GIF example Numpad 1 dissapear.\n\nSometimes it come back after restart Blender, but sometimes it is just gone.\n\n\n\n", "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", "Error de progama\nno me aparece el modo vèrtice\n\n", "OSL on the GPU displays all black for Voronoi Distance > Bump Height\nSystem:\nWindows 11\nRTX3090Ti gpu\n\nBump output is pitch black when using Voronoi (Distance) output into Bump Height. Colorramp in between does not fix it. Noise output into Bump Height works fine.\n(Blender 3.5 in cycles)\n\nedit: more useful info + screenshot + isolated blend file\n\nRunning OSL on the CPU works fine, only the new GPU support seems affected.", "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", "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 to desktop on launch\nasus strix 1080ti, windows 10 64bit latest updates for everything\n\nBroken: latest release on steam\n\nCTD on launch. Will flash a cmd as well as a grey window for a second.\nLaunch\n" ]

[ "Performance bottleneck with many nested nodes\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.2.0 Alpha\n\nSeems like *Domain Size* performance drops if using nested groups.\n \nIn attached file mute *Float to Integer* node (yellow color) and look how *Domain Size*'s executing time is drastically increasing.\n[domain_size_performance.blend](domain_size_performance.blend)", "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "Crash 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", "Blender crashes after rendering a few frames of an animation\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nI've never had this kind of problem - Blender crashes randomly after rendering a few frames of the animation. The only \"new\" thing I'm doing is I started using geometry nodes in this scene. I have plenty of VRAM left, shouldn't be a GPU issue. Tried both in 3.4 and 3.5\n\n\n", "Blender 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)", "Regression: Shape Keys Causing Vertices to Explode Periodically\nOperating system: Windows 10 Home\nGraphics card: NVIDIA GeForce RTX 3090\n\nBroken: 3.6.2\nWorked: 3.4\n\nI have animated shape keys for a character as well as shape keys for a boat to create dynamic movement. I rendered out a short scene of the boat on the water and vertices would randomly explode every couple of frames (as seen in the photos added). I had just keyframed the movement with the shape keys and if I delete all of those keyframes the exploded vertices disappear. I appended the same file into Blender 3.4 and rendered out frames with no issues whatsoever.\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "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", "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", "Programmatically creating a link involving a blank group input/output socket causes a UAF\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 3.0.0 Alpha\nAlso occurs in the 2.93.1 debug build\n\nGroup Input and Group Output nodes have blank sockets that can be used to automatically create a new group input or group output by plugging them into something. Trying to do this via `NodeTree.links.new()` causes a use-after-free in a debug build.\n\n1. Open the attached file\n2. Run the script\n3. AddressSanitizer causes a crash\n\n[group-socket-uaf.blend](group-socket-uaf.blend)\n\nAddressSanitizer output: [P2214](P2214.txt)\n\nEverything works as expected in a release build: a new group input or group output is correctly created.\n\nThis also happens if you try to directly create an output or input on the Group Input / Group Output sockets, but it happens in a different place: [P2215](P2215.txt) . I can spin that out into a separate task if needed.\n\nCreating inputs or outputs on the *node group* (which I'm pretty sure is what you're supposed to be doing) works fine.", "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n", "Crash when renaming a world in a timer and dragging a world in the asset browser\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.4.0 Alpha\nWorked: Don't know, tested back to 3.1, and still got the crash\n\nWhen a python timer renames a world, and the user is dragging a world *from another file* in the asset browser, blender will crash. (doesn't happen if the world is from the current file)\n\nI also tested this on materials, and it didn't cause a crash, so I assume that it's limited to just worlds.\n\n[world renaming crash.blend](world_renaming_crash.blend)\n* Open the attached blend file, and run the script in the text editor.\n* That will start a timer that will run once a second for ten seconds, and will rename a world data-block each time.\n* During those ten seconds, in the asset browser window, start dragging a world asset that originates from another file.\n* Blender should crash.\n\n[2022-10-23 15-49-18.mp4](2022-10-23_15-49-18.mp4)\n\nThanks a lot!", "use-after-free crash after setting scene's render.engine inside custom render engine context\nOperating system: Ubuntu 20.04.2LTS\n\nBroken: 2.93.0 Beta, branch: master, commit date: 2021-05-19 10:14, hash: a294670bacb1, type: release\nAlso Broken: 0efb627bbd3ac3e53afb95591ae4e244bd1f8af4\n\nBlender crashes when setting some scene's render.engine property inside `__init__` or the `view_update` context of a custom render engine to a different one than the custom engine.\n\n[T88404_asan_report.txt](T88404_asan_report.txt)\n**Code to reproduce the error**\n```\nimport bpy\nimport bgl\n\nclass CustomRenderEngine(bpy.types.RenderEngine):\n bl_idname = \"CUSTOM\"\n bl_label = \"Custom\"\n bl_use_preview = True\n \n def __init__(self):\n return\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def __del__(self):\n pass\n\n def view_update(self, context, depsgraph):\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def view_draw(self, context, depsgraph):\n pass\n\ndef get_panels():\n exclude_panels = {\n 'VIEWLAYER_PT_filter',\n 'VIEWLAYER_PT_layer_passes',\n }\n\n panels = []\n for panel in bpy.types.Panel.__subclasses__():\n if hasattr(panel, 'COMPAT_ENGINES') and 'BLENDER_RENDER' in panel.COMPAT_ENGINES:\n if panel.__name__ not in exclude_panels:\n panels.append(panel)\n\n return panels\n\n\ndef register():\n bpy.utils.register_class(CustomRenderEngine)\n\n for panel in get_panels():\n panel.COMPAT_ENGINES.add('CUSTOM')\n\n\ndef unregister():\n bpy.utils.unregister_class(CustomRenderEngine)\n\n for panel in get_panels():\n if 'CUSTOM' in panel.COMPAT_ENGINES:\n panel.COMPAT_ENGINES.remove('CUSTOM')\n\nif __name__ == \"__main__\":\n register()\n```\n\n1) Copy code from above into a new script file inside of Blender\n2) Run the script\n3) Select \"Custom\" as Render Engine inside Render Properties\n4) Select \"Material Preview\" as display method in the viewport.\n\n[crash.blend](crash.blend)\n\nCrash log:\n```\n# Blender 2.93.0, Commit date: 2021-05-19 10:14, Hash a294670bacb1\nEngine 'CUSTOM' not available for scene 'Scene' (an add-on may need to be installed or enabled) # Error\nbpy.ops.text.run_script() # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xa63c950]\n./blender() [0xf6082a]\n/lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f7ce17be210]\n./blender(GPU_framebuffer_blit+0x2f) [0x8664faf]\n./blender() [0x1485fc3]\n./blender() [0x14597fe]\n./blender(DRW_draw_render_loop_ex+0x242) [0x1459a72]\n./blender(view3d_main_region_draw+0x8f) [0x1d3570f]\n./blender(ED_region_do_draw+0x851) [0x189c771]\n./blender(wm_draw_update+0x52e) [0x130cc9e]\n./blender(WM_main+0x30) [0x130aa20]\n./blender(main+0x319) [0xe881c9]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f7ce179f0b3]\n./blender() [0xf5d1bc]\n\n# Python backtrace\n```", "Crash When Adding Hair Subdivision upon Viewer node\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\n\n\nAdding hair subdivision will cause crash immediately when you are using viewer node to visualize field values in the viewport.\nNote no crash will occur if the viewer node is inactive.\n\n[Hair Crash.crash.txt](Hair_Crash.crash.txt)\n\n1. select default cube\n2. shift+A to add empty hair\n3. in the node tree add viewer node.\n4. Crash if adding subdivision\n[Hair Crash.blend](Hair_Crash.blend)" ]

[ "Regression: Crash on deleting the multi-level hierarchy\nOperating system:MacOS Monterey 12.3.1\nGraphics card: M1 Max\n\nBroken: 3.4.1\nWorked: 3.3\n\nDeleting a hierarchy crashes blender when there is more than one level of hierarchy. \n\nMake three cubes.\n1. Parent Cube1 to Cube2 (keep transform).\n2. Parent those to Cube3 (keep transform). So there are 3 levels of hierarchy, each with one cube. \n3. Right-click in outliner and select \"Delete Hierarchy\".\nBlender instantly crashes every time\n\nWorkaround: It works to \"Select Hierarchy\" then choose \"Delete\". The crash only happens when choosing \"Delete Hierarchy\" \n\n---------------\n\nHere is a testing .blend file with some relatively more complex relationships: " ]

[ "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.", "Speakers cannot be muted or unmuted via the API (bpy.data.speakers.muted is broken)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0\nWorked: 2.79b\n\n1. Add a speaker object\n2. Add a sound to the speaker.\n3. Play the animation, you should hear the sound playing.\n4. Open the console and run bpy.data.speakers[\"Speaker\"].muted = True\n5. Play the animation, you will still hear the sound playing, even though the UI has been updated to add a checkmark to the box next to \"Mute\" in the speaker data.\n\nMuting the speaker via the UI works normally.\n\n[#94627-speaker-mute-depsgraph.blend](T94627-speaker-mute-depsgraph.blend)", "Denoising + negative lamps = black and white artifacts\nOS X Sierra 10.12.6,\nNVIDIA GeForce GT 750M 2048 MB\nIntel Iris Pro 1536 MB\n\nBroken: 2.79\n\nSimple scene with negative lights gives bad artefacts with denoising enabled.\n\nJust render the attached .blend file.\n\nAttachments are:\n* Denoised image with artefacts\n* Non-denoised image without artefacts\n* .blend file\n\n  [denoising.blend](denoising.blend)", "Optix: Motion Blur seems to glitch out while rendering\n\nOperating system: Windows 11 Pro 22H2 22621.525\n\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\n\nBroken: version: 3.3.2 LTS / 3.5.0 Alpha (Broken in both)\n\n\nHaving motion blur on while rendering with Optix seems to not work as expected in this scene. It renders out with artifacts (Alpha / black squares). Things work fine **when you turn off motion blur or switch to Cuda**.\n\n \n\n**Steps to reproduce the bug:**\nOpen the attached fine and render frame #82 with Optix enabled.\n\n[Keyframe remove 1_010.blend](Keyframe_remove_1_010.blend)\n", "Tooltips doesn't display when play animation\nOperating system: Linux-4.15.0-64-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 12)\nWorked: 2.8\n\nTooltips doesn't display when play animation, work otherwise\n\nDefault startup:\n \n* Play animation\n* Tooltips doesn't show \n\n", "Black outlines around animated Objects when Scrubbing/Playback.\nOperating system: Windows 10 64 Bits\nGraphics card: GTX 1080 TI.\n\nBroken: version: 2.83.8 hash: 7c027f9480a9\nWorked: version: 2.83.4 hash: `abb7364912` (commit date: 2020-02-23 23:00)\n\nThere are some weird black outlines popping out during anim playback or scrubbing. \n\n***P**\n{[F8400153](spot.jpg) size = full}\n\n\n* open the file\n* If it is not already set, set viewport shading to material preview (that's where you can easily spot them)\n* playback the animation or quickly move the object\n\nThe black outlines will appear but the moment you stop they'll disappear, so you can screen capture the moment to check their existence ***P**.\n\n[Black.blend](Black.blend)\n", "Sound strips don't change length when sound file is changed\nOperating system: Windows 10\nGraphics card: Nvidia MX150\n\nBroken: 2.91 and 2.92 Alpha\n\n**Steps to reproduce**\nAdd sound, change file to another one with different length.\n\nStrip length is not updated.", "Blender 3.2.1 / 3.4 - Cycles - Persistant Data and Motion Blur artifacts on GPU\nOperating system: Windows 10, Ubuntu 21.04\nGraphics card: GTX 1080, RTX 3080\n\nBroken: 3.2.1, b5e92c3dfe\nWorked: 2.79\n\nPersistant data is bugs out during renders sometimes.\n\n1. Open attached blend file in Blender 3.2.1\n2. Press f12\n3. Press right on the keyboard (frame 771)\n4. Press f12\n5. Press right on the keyboard (frame 772)\n6. Press f12\n7. Notice how its not as expected.\n8. Press f12 without framing forward\n9. Notice how it is fine\n\ngood\n\nbad\n\n\nThis means when rendering animations, it can produce frames which bad, which then require more re-renders.\n\nWindows and Linux have both been tested and results are the same.\n\nTested CUDA, Optix and both have issues. CPU renders fine. \n\nDisabling Persistant Data renders fine.\n[bug.blend](bug.blend)\n\nNOTE: We had #95475, #96822 already for Persistent Data and Motion Blur issues (these should be fixed), I can repro this case though.\n\nEDIT:\nAs another task #100729 has been merged into this file, there is another test file [BUG.blend](BUG.blend)\n", "Creating new folder in File View disables \"select all\"\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 5)\n\nThis seem to happen only when 'Select All Toggles' is enabled.\n\n - Enable **Select All Toggles** in **Preferences** > **Keymap**\n - Open **File View** (can be open or save menu)\n - Pressing \"**a**\" should toggle selection of all elements (you need some files in the folder for that).\n - Create new folder.\n - Type in a name\n - Now pressing \"**a**\" does nothing. Using box select should fix it.\n[file_view_select_all_bug.blend](file_view_select_all_bug.blend)", "compositor performance issue when larger empty area surrounding the image\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: much faster in 2.93\n\ncompositor performance is severely degraded if there is a larger empty area surrounding the pixels. Also becomes more and more sluggish the longer it plays back, despite it only updating a single image block. Task manager doesn't show any increase in memory usage as it becomes slower.\n\n<video src=\"attachment\" controls></video>\n\nGet an image sequence to playback in the compositor's backdrop, either with a image sequence node, or by updating a single image via python and calling render.render to force the playhead to wait for the compositor to finish calculating. Try playing back with the compositor contracted and expanded. See video for demonstration.\n\nIssue affects the tiled, full frame, and gpu compositor modes. Also happens when experimental compositor is disabled completely in the preferences.\n\nExample video attached.\n\n", "Compositor doesn't render if VSE contains strips\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.0.0 Alpha\n\nCompositor doesn't render if VSE contains strips.\nIn some cases user may want to have for example sound strip to play sound while compositing. This can cause only VSE to be used for rendering.\n\nAdd color strip to VSE, in compositor check Use Nodes and render.", "FFMpeg color offset\nOperating system: Win7x64, Ubuntu18x64\n2.80 beta\n\nFiles encoded through FFMpeg.h264 in Blender show up with a consistent color space offset (warmer and different gamma) in other software/players/viewers, but are viewed \"as saved\" if opened in Blender. At the same time h264 files produced in other software are open in Blender with no noticeable color shift, but re-rendering them through Blender introduces it.\nSame content rendered into other formats, like PNG, does not have such effect.\nAt first I thought those are my codecs on a windows machine, but the output/behavior is the same on Ubuntu.\n\nGiven that the h264 files produced elsewhere are open in Blender without matching \"negative\" color offset (at least one I could see), could it be that FFMpeg in Blenders is set up to default to some particular color space for encoding?\n\n[cc-test.zip](cc-test.zip)\nOpen, render animation, compare to what is in the source image in any other software.\n\nEdit:\nTrying to reproduce the issue on command line ffmpeg it was found present unless some flags are used.\nFlags:\n- vf scale=out_color_matrix=bt709\nare needed for other programs to read colors identical to png.\nPlus these:\n- color_primaries 1 -color_trc 1 -colorspace 1\nare needed to make Blender recognize the converted colors again properly.\n", "Blender card only showing a default cube when open even the file size is 100 mb\nI am working on a blender file on my pc . The file size is almost 100mb . I saved the file. But when i opened it again the file is just showing a single default cube. No layers no anything. Just default interface. My file was just having the room interface . It consists of some free models also which i downloaded from the internet. Like free 3d website like sketchfab. \nThis thing happened with me 1 week ago. But then i made the file again and get my pc hard disk and windows changed. And now it happened with me again. I dont know what to do. Please tell me what to do to recover my file and to prevent this issue next time.\n\ni was able to recover it through .blender1 format but still i know this will happen again. please guide me on this, i have not added anything in my addons also \n\nblender 3.6 version \ngraphic card 750 Ti \nWindows 10 \nnew hardrive of 250 gb\n\n", "Inaccuracy in 'Info' editor\nThis bug is difficult to describe specifically, since I have no idea of *all* of the affected properties. All I noticed is that *some* are reported inaccurately (i.e. the reported rna path does not exist or does not point to the changed property).\n\nA few I found are on the View Layer tab in the Properties editor:\n`bpy.context.scene.view_layers- [x].cycles.denoising_store_passes` is reported as `bpy.context.scene.denoising_store_passes`\n`bpy.context.scene.view_layers- [x].cycles.pass_debug_render_time` is reported as `bpy.context.scene.pass_debug_render_time`\n`bpy.context.scene.view_layers- [x].cycles.use_pass_volume_direct` is reported as `bpy.context.scene.use_pass_volume_direct`\n`bpy.context.scene.view_layers- [x].cycles.use_pass_volume_indirect` is reported as `bpy.context.scene.use_pass_volume_indirect`\nPlus all of the Cryptomatte and Denoising properties.\n\nI have no idea how the Info editor receives this information, but it looks as if the message is partially hard-coded and not up to date?", "VSE Linked external scene with audio with input Sequencer only works if the scene is NOT also linked with input Camera\nOperating system: Linux-4.9.0-9-amd64-x86_64-with-debian-9.9 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 13.0.6\n\nBroken: version: 2.81 (sub 3)\nWorked: Haven't yet tried other versions.\n\nVSE: Linking external scene with audio with input Sequencer only works if the scene is NOT also linked with input Camera.\n\n1. Create file A with Scene-A and add audio to it on the VSE.\n2. Create file B\n3. From the VSE in file B, link the Scene-A from file A. Set it's input to \"Sequencer\". On file B, playing the strip will correctly play the sound from Scene-A.\n3. Duplicate (or re-instance) Scene-A on the VSE sequencer. If the Input is still \"Sequencer\", both clips will play the audio, as expected.\n4. Switch one of the Scene-A instances to use the Camera as input. \n\nExpected behaviour: \n\nWe should be able to both see the Camera strip and hear the Sequence strip for Scene-A\n\nActual behaviour:\n\nFor all the strips of Scene-A that are set to Input \"Sequencer\", the audio will stop playing.\n\nNote: I've determined that it is not that the audio crashes: other clips with sound on the sequencer keep playing normally.\n\nNote: If I delete the strip with Input Camera and leave only the input Sequencer strips, the problem will not go away, unless I save the file like this and \"revert\" to it.\n\nI cannot find a suitable work-around. In the video that I'm producing I need to edit local sound effects on the shot sequence, and incorporate it on the larger edit.\nI cannot, therefore, both see and hear my sequence on the host sequencer.\n\n\nIf a workaround is possible (that is not reconstruct and re-import the sounds on the original scene) I'd be a happy man :-)\nThanks!\n\n\n" ]

[ "Audio SDL: Video editor Sound muted without muting it\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79b\n\n\nAudio playback not making any sound\n\nadd a image strip and then a mp4 video file or only the mp4 file, it just doesn't sound at all by any means\n[filenotworking.blend](filenotworking.blend)\n" ]

[ "Self-referencing driver works in viewport, but not in render.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional) 2.79b\n\nRotation property of object is updated in viewport, but not in render.\nIf run same script in 2.79 - all works fine both in viewport and render.\n\n```\ndef rotator():\n var1=bpy.data.objects[\"Suzanne\"].rotation_euler.z\n var3=bpy.data.scenes[\"Scene\"].render.fps\n\n new_value=var1+math.radians(var3)\n\n return new_value\n```\n\n\n[Script_bug_2.8.2.blend](Script_bug_2.8.2.blend)\n\n- run the file Script_bug_2.8.2 ('Run script', 'Update Dependecies')\n- play in the viewport - the animation works correctly\n- render (Ctrl + F12) - the animation does not work;\n\nViewport:\n[bug_video_render0001-0050.mkv](bug_video_render0001-0050.mkv)\n\nRender:\n[bug_video_render_20001-0050.mkv](bug_video_render_20001-0050.mkv)\n\n2.79 file:\n[Script_work_2.79.blend](Script_work_2.79.blend)\n\n", "Regression: Unable to move camera/area light with gizmo (intel GPU)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 30.0.101.1122\n\nBroken: version: 3.2.0, 3.3\nWorked: 3.1\nCaused by 5045968f24\n\ni cant move my camera using move tool or tranform tool on left side bar\n\n- select camera\n- Choose move or transform tool\n- Move camera with gizmo (won't be able to move)\n\n[bug camera.blend](bug_camera.blend)\n[blender 3.2.mkv](blender_3.2.mkv)", "GPencil: Randomize brush's 'Position' attribute doesn't work when camera is too close to Grease Pencil object\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.93, 3.1.0\nWorked: N/A\n\nExact steps to reproduce the error:\n\n- Open file\n- try to use Randomize brush\n- Strength and Thickness work, but not Position \n- Switch to the other camera that's farther away from the GP object, and randomizing the position works fine.\n\n[randomize_not_working_close_NEW.blend](randomize_not_working_close_NEW.blend)\n\n\nwatch?v=4pTrEm5HqVU", "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", "Grease Pencil Outline Modifier not showing with duplicated camera in outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.33\n\nBroken: version: 3.4.0 Alpha\n\nThe outline modifier of a grease pencil is not showing with a camera that gots duplicated in the outliner\n\n\n- Remove the default cube\n- In the outliner copy and paste the default camera\n- Remove the first camera\n- Add a grease pencil stroke\n- Add a Outline modifier to it\n\nThe outline will not show.\n\nThis bug is related to this report. I am just not sure if it is two different causes and cases, or the same. T102373\n\n\n\n[2022-11-09 10-30-57.mp4](2022-11-09_10-30-57.mp4)\n\n\n\n", "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", "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", "Parented camera not animated when switching view with markers and collection is disabled\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.5.0 Alpha\nBroken: version: 3.4.1\nBroken: version: 2.83.9\nWorked: probably never\n\nIn a scene with multiple cameras and markers used to switch between them, if the collection containing the cameras is disabled (hidden with the monitor icon) and the cameras have an animated parent, only the camera active at the start of playback will be animated. The animation works fine when the collection is shown.\n\n\n\n\n\n[bug_report_marker_cam_anim.blend](bug_report_marker_cam_anim.blend)\n- Open the attached blend file\n\n- Play the animation\n - The result is staggered because only one camera is animated\n- Show the Cams collection and play\n - The result is smooth because both cameras are animated—this is the expected behaviour.\n\nWhen the collection is hidden:\n\n\nWhen the collection is shown:\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.", "Animation. Keyframes. Copy - move to the current frame.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\n[Animation. Keyframes. Copy - move to the current frame for replacing the previous one. If you copy keyframes and move them to the current frame it won't work properly. All will seem good but the last frame will play an animation relay on the previous parameters. ]\n\n\n[bug.blend](bug.blend)\n\n\n\n", "Allow View Navigation within Modal Operators\nExcept when there's a good reason to block navigation (such as modal transforms) all modal operators should allow user to navigate the viewport. This includes panning, rotating, zooming, and changing to direct view (top, front, side, etc).\n\nFor example, neither Box Select or Circle Select allow viewport navigation. This severely limits the tools use, often requiring the user to activate the operator multiple times from different angles. \n\n**Operators that need navigation events passed through**:\n - Circle Select\n - Box Select\n - Mesh Bisect\n - Mesh Loopcut and Slide\n", "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.", "Camera rotation is inverted when camera is upside down in \"fly navigation\" mode\nOperating system: Linux-4.15.0-46-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken version:\n\n\n - 2.80 (sub 51)\n - similar behavior on 2.79\n\n\nLeft-right rotation of camera in \"Fly navigation\" is inverted when camera is upside down and \"upright Z axis\" is off. This effect can be seen even if camera is slightly upside down (for example if you look in X-axis direction and rotate around Y-axis more than 90 degrees). Changing \"upright Z axis\" to ON fixes this issue even if camera is still upside down. Changing it back to OFF produces problem again. If \"upright Z axis\" is kept ON all the time, you can rotate camera UP to bring it upside down to see that problem only happens when \"upright Z axis\" is off.\n\nI believe this is bug, because it is counterintuitive and different from behavior in same situation when \"upright Z axis\" is ON.\n\n**Exact steps for others to reproduce the error (blender 2.8, default shortcuts)**\n\n - Open any blender scene.\n - Press F3 to open search dialog.\n - Search \"*Fly Navigation*\" and press Enter.\n - Press Z to turn off \"Upright Z axis\".\n - Rotate camera upside down (for example move cursor above rectangle in center of screen until camera is upside down).\n - Place cursor left of rectangle in center of screen. Camera should rotate left, but it rotates right. Alternatively, place cursor right of rectangle in center of screen.\n", "Collection usability\n- [ ] Viewport UI\n- [ ] Shortcuts to toggle visibility?\n[ ] . . .\n\nNeed a clear design on what to do.", "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" ]

[ "controlling camera movement with keyframes\nOperating system: Windows 10 Pro 10.0.16299 Build 16299\nGraphics card: NVIDIA GeForce GTX 1070\n\nBroken:\n(example: 2.80, a205493426b blender2.8, 2018-12-03, as found on the splash screen)\nWorked: (optional)\n\nCamera keyframe malfunction\n\nI don't know if this is a bug or not, but I'm having all kinds of problems getting the camera keyframes to behave like they did in 2.79 or lower. When I set keyframes and then move the camera and try to set a new keyframe, the camera frequentlly pops back to the prior location and rotation.\n\nI thought it had something to do with the check box next to the \"lock/unlock\" icon on the dope sheet that controls the F-curve, but unchecking it yields inconsistent results.\n\nI cannot figure out how to make it work correctly all the time.\n\nI feel like maybe I'm missing something that should be obvious.[Negative result_280.blend](Negative_result_280.blend) I haven't been able to find an answer on any of the forums.\nBased on the default startup or an attached .blend file (as simple as possible).", "Camera Location, keyframe Bug\nOperating system: Win 10 64 bit\nGraphics card: 2xGTX 1080 Ti\n\nBroken:\n2.80, 2018-12-03, a205493426b\nWorked: (optional)\n\nWhen camera location keyframed beyond timeline(or sometimes in) can't change keyframed values from 1st keyframe.\n\n\nCreate camera, set view to camera, add keyframe, change position on timeline, move camera in location tab - its looking like view is still only outframe of camera is moving and changing visual od depth. After release for ex OY location it will back to value from first keyframe. If description will be not enough I can provide video.", "Camera animation error\nOperating system: Mac OS High Sierra\nGraphics card: Radeon Pro 580 8 GB\n\n2.80 Beta (11 29 2018)\n\nCamera animation error\n \n\nBased on the default startup or an attached .blend file (as simple as possible).\nAnimating a camera from camera view (0) with \"lock camera to view\" checked. I moved the camera to start position and inserted LocRot keyframes then moved down the timeline to move the camera to its second position and it does not move.\nA yellow rectangle that looks like it represents the edges of the camera view moves around, but it does not affect the actual camera view." ]

[ "boolean node in geometry nodes seems to work wrong\nOperating system: macOS-11.2.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15\n\nBroken: version: 3.0.0 Alpha\n\n\n\nI have made this node tree in geometry nodes and i am getting this result, which - for me - looks like a bug.\n\n", "Decimate modifier gives different result on every evaluation\nOperating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06\n\nBroken: version: 3.2.2, 3.3 latest\nBroken: 3.1.2\nWorked: 3.1.0\nWorked: 2.93.8\n\nCaused by fb2cb0324a\n\nA mesh with decimate modifier gets topology rebuilt on each frame of Cycles render. Notice that a new cones object on the right is not broken.\nThere's something wrong with the left object. I checked every property I could think of.\n[0001-0250.mp4](0001-0250.mp4)\n[decimate_bug.blend](decimate_bug.blend)\n\nOpen the file. Render a sequence.\n\n", "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", "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", "Boolean Modifier is evaluated if an object linked to the cutter object is link-duplicated\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.91.0\n\n\nSuppose ObjectA has a boolean modifier, the target object of which is CutterA. CutterA shares the same mesh datablock as CutterB. If CutterB is link-duplicated (Alt-D), ObjectA 's boolean modifier is re-evaluated. In large technical scenes with many linked cutters this means Blender frequently stalls, re-evaluating *every boolean in the scene every time you duplicate a cutter.*\n\nExpected behaviour: boolean modifier should only be evaluated if the cutter object datablocks *change*, and adding a user to a datablock should not count as a change.\n\n", "Applying Data Transfer Modifier - only the active Shape Key is taken into account\nOperating system: Win 10 x64\nGraphics card: 3080 TI\n\nBroken: 3.3.2, 86abbf717691, master, 2022-11-28\nWorked: ??\n\nWhen applying data transfer modifier to an object (to transfer vertex groups), it only takes into account the selected shape key, not all others too.\n\nExample:\n\nDownload test Blend:\n[datatransfer_shapekeys.blend](datatransfer_shapekeys.blend)\n\nThis is the cube's vertex group:\n\n\nPlane is moved down by shape key \"Key 1\". All looks good in the viewport, this is how the vertex group should look when you apply it:\n\n\nBut if the 'Basis' shape key is selected instead of 'Key 1' when you apply the modifier, it ignores Key 1.\n\n\nSee how the position of the vertex weight is off as compared to the first picture, as if Key 1 were disabled.\n\n\nBut if you were to have Key 1 selected when you apply the modifier, it works as expected:\n\n\nThis is troublesome with objects that have many shape keys, all with different influences on the affected area. When you apply the modifier, it should take into account every active shape key.\n\nThis gets even less predictable if you have multiple shapekeys besides the `Basis` shapekey.\nHere I have two (both with 0.5 weight).\nYou get different results selecting `Key 1` or `Key 2` and none look like what you had in the viewport:\n[datatransfer_shapekeys_multiple.blend](datatransfer_shapekeys_multiple.blend)", "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", "Bump node bump converges to different result than displacement bump\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\nUsing the same height map in combination with the bump node gives a different result than using the displacement node with bump only.\n\n\nWhen switching between the bump and displacement node one can notice a visible brightness difference in parts of the shape.\nWhat is perplexing however is that upon inspecting the normals used in rendering (switch render pass to normals), they are identical.\nSo the problem probably doesn't lie in how the shading normals are calculated but rather how cycles uses these.\n\n- Open attached file\n- Disconnect the displacement Map and connect the Bump Node to the `Principled BSFD` Node\nNotice the difference, (one receives less light)\n[test.blend](test.blend)\n\n\nThank you and have a great day!\n\n", "Ghost / False Node inputs\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.1, 3.2, 3.3\n\nWhen the output type of a node changes:\n\nVector Math multiply (vector output) ----> Vector Math distance (float output)\n\nIt causes the node that has the changing type as it's input to be in a bugged state.\n\n* Open .blend file\n[ghost_inputs.blend](ghost_inputs.blend)\n* Change the multiply to distance (easiest one I could think of)\n* The other math node will be in a messed up state\n\n* You can even drag from the ghost input and you will be able to see that Blender thinks it is still connected.\nThanks!", "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)", "Regression: Surface Deform modifier bind to object with different viewport/render subdiv level will be buggy when rendering\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.3.0 Alpha\nWorked: version: 3.2.0\n\nIf object A has a subdiv modifier with different level for viewport/render, and object B has a SurfaceDeform modifier that bind to A.\n\nWhen A is deforming in viewport, B will also deform normally in viewport. However in rendered result, B will become chaotic. Clearly the 'bind' option in B's SurfaceDeform modifier remembers A's vertices that subdived for levels of viewport setting, but when rendering, A will be subdived for levels of render setting, and have a different number of vertices, making B's bind invalid.\n\nAny other modifiers with bind option, e.g. MeshDeform, may also suffer from this.\n\nI wonder if this can be fixed. Two possible solutions:\n1. for every subdiv step, add additional vertices at the end of original vertices. So the original vertices will remain index unchanged, and the bind may work as well.\n2. When rendering, check if render subdiv level != viewport subdiv level, and always use viewport subdiv level for binding of any other modifiers. The render subdiv level should only affect render visual effect. Maybe an option for this can present in subdiv modifier, if this change may introduce incompatibility issues.\n\nFollowing above information, reproduce should be easy. However, an example .blend file is provided.\n1. open example.blend. This file contains a surface with subdiv level 2/5 for viewport/render and a torus with SurfaceDeform bind to it.\n2. F12/render and see the torus go bad.\n\n", "Cloth Filter Doesn't respect collision outer surface thickness\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 511.65\n\nBroken: version: 3.2.0 Alpha 991781c8eabe\nWorked: 3.2.0 Alpha 52be06301257\n\nI don't know if this is feature was supposed to work or not but when using Cloth filter with collision on, then adjusting the collision object outer thickness, doesn't seem to have any effect on the cloth object, the cloth object still penetrates the collision object\n\n\n\n\n[#96124.blend](T96124.blend)\n\n- Open file\n- Sculpt plane so it intersects with cube\n\nNo deformation will happen.\n\n", "Geometry Nodes Mesh Boolean unexpected difference result\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 83\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nGeometry Nodes Mesh Boolean Difference does not work as expected.\nNode setup:\n\n\nUnexpected boolean difference:\n\n\n- Open the attached .blend file\n- Press G to move the selected Cube.001 and the small cubes will flicker.\n# At certain positions of Cube.001 some of the small cubes will disappear when they should not.\nThanks!\n[test06.blend](test06.blend)\n", "Regression: Image Editor Texture Draw Stops Updating\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0 (probably introduced by {f663a1dc09}?)\nWorked: 3.0\n\nthis was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues -- @lichtwerk)\n\nImage on Image Editor -> Paint does not update when being drawn on at certain close view levels until the viewport is moved \n\nLoad default scene\nSwitch to Texture Paint tab\nCreate new image\nZoom in 7 or 8 times (for reference I am using a scroll wheel that has steps)\nDraw on the image\nIt will sometimes update fine, sometimes stop updating when it passes over a what looks like a UV boundry, that extends off the screen\n\nSee gif where I added a material to it\nSorry if this has already been reported, haven't been able to find a public bug tracker\n[image_paint_bug.blend](image_paint_bug.blend)\n\nThis is the file I (-- @lichtwerk) used on linux to bisect/reproduce on a 1920x1080 display (since this seems to depend on monitor/zoom etc):\n[image_paint_bug_repro.blend](image_paint_bug_repro.blend) ", "context override for bpy.ops.view3d.view_selected doesn't work\nBlender 3.6\n\nTried to override currently selected items and run `bpy.ops.view3d.view_selected` (default blender operator binded on \"Numpad .\" by default) and it doesn't work. If I select objects manually with `obj.select_set(True)` it works.\n\nI've compared context's dict produced by `bpy.context.copy()` - the only difference between the context after `.select_set` were `selected_objects`, `selected_ids`, `selected_editable_objects` and I've overidden them.\n\nWay to reprodiuce:\n1) Open default blender scene.\n2) Make sure nothing is selected and move camera away.\n3) Run the code below - nothing happens\n4) Uncomment first two lines of code - operator works.\n\n```python\nimport bpy\n\n#for obj in bpy.data.objects:\n# obj.select_set(True)\n \nfor area in bpy.context.screen.areas:\n if area.type == 'VIEW_3D':\n for region in area.regions:\n if region.type == 'WINDOW':\n override = {\n 'area': area, \n 'region': region\n }\n override['selected_objects'] = bpy.context.view_layer.objects[:]\n override['selected_ids'] = bpy.context.view_layer.objects[:]\n override['selected_editable_objects'] = bpy.context.view_layer.objects[:]\n with bpy.context.temp_override(**override):\n bpy.ops.view3d.view_selected()\n # print(bpy.context.copy())\n```\n\n" ]

[ "Boolean Modifier loses material on newly generated surface in \"exact\" mode\nOperating system: Windows 11\nGraphics card: Intel\n\nBroken: (3.2.2)\nWorked: (2.79b, or if you open a file with a boolean from 2.79b in 3.2.2)\n\nWhen using the bool modifier to make a cake cut of an object(ie. Show the texture through the object hole procedurally continuing) in \"exact\" mode, the cut region is not shaded, instead of shaded with the textured material. It only shades correctly in \"fast\" mode. \nThis happens if you create the Booleans and textures in 3.2.2 from scratch.\nIf you do the same thing in 2.79b, the texture properly shades in cycles in either carve or bmesh mode. If you save the 2.79b file and open it in 3.2.2, suddenly the Boolean shading works in either mode.\nUse BoolTool to create a brush bool difference of two cubes.\nShade the cut cube with principled shader, plug a noise texture into the color.\nswitch the bool method to exact.\nThe cut section (or merged) will not have any texture.\nThis works in either EEVEE or Cycles.[Boolean error 3.2.2.blend](Boolean_error_3.2.2.blend)\n\n[Boolean works 2.79.blend](Boolean_works_2.79.blend)\n\n[system-info.txt](system-info.txt)", "Regression: Boolean Difference modifier - material of hole created by hidden object different for fast and exact\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.2.1\nWorked: 3.1\n\nCaused by a2d59b2dac\n\nWhen using Boolean difference modifier with hidden objects, the material depends on whether the fast or exact solver has been used. With \"Exact\" the material is that of the hidden object. With \"Fast\" the material is that of the original object. \n\nCreate object, say cube A. Material colour Blue. \nCreate second object, say cylinder B, partially inside cube. Material colour Red. \nCreate third object, say sphere C, partially inside cube A. Material colour Green. \nCreated boolean difference modifier acting on A with B as object using Fast solver.\nCreated boolean difference modifier acting on A with C as object using Exact solver.\nHide objects B and C from viewport and Render. \n\nThe hole created from Object B inherits colour from object A. \nThe hole created from Object C inherits its colour from object C. \n\nThe same issue is present in EEVEE and cycles. \n\nThis behaviour is inconsistent and different from Blender 3.1. \n\nPreviously the hole always inherited the colour from the original object A. \n\n[Boolean hidden object colour.blend](Boolean_hidden_object_colour.blend)\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)", "python display_shape don't work in GeometryNodeTree\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.1.0 Alpha\n\nWhen adding a custom node with custom socket to the GeometryNodeTree you can't alter the display_shape of the socket and the bpy.types.NodeSocketFloat or any socket type doesn't matter when connecting nodes it always stay red.\n\n\nAttached a blend file with the script for quick testing\n[tst.blend](tst.blend)\n\nThis is not a problem in the Shader or Compositing editors:\n\n", "Node Tools Overview\n## Background\nWith node group assets becoming more prevalent and geometry nodes becoming essential\nfor manipulating geometry in Blender, we want to add the ability to implement operators\nwith geometry node groups.\n\nRelevant node groups would need a geometry input and output, and could have other inputs (and possibly outputs), with similar mappings as the geometry nodes modifier.\n\nAdditionally, specific inputs could be marked as editable modally, for example, a \"Factor\" input could be controlled by moving the mouse cursor left or right.\n\nThe specific data design still needs to be settled on (i.e. is the node group an operator, or does an operator reference a node group?).\n\n## Design\n- The node group itself is the operator asset\n- Geometry nodes gets new input nodes\n\t- Selection\n\t- Mouse coordinates\n - View transform\n - 3D cursor location\n - etc.\n- Geometry node groups with these input nodes can only be used as operators\n\t- This design is similar to the shared node groups between shader and geometry nodes, for example.\n- The group outputs are used to adjust the output geometry\n\t- The geometry output will adjust the \"active\" geometry\n - We _might_ need to store a specific mapping for outputs, but relying on the name is a start\n- The project is \"completely finished\" when any existing edit mode operator could be implemented with nodes\n\n## Implementation\n\n_Organized by priority in each category_\n\n### 4.0 Targets\n\n_Changes needed to move the feature out of experimental and enable it in the release_\n\n- [x] Initial basic feature for curves sculpt mode e4cc91a6113f14418b5d8f2a0aace252dc3949d8\n- [x] Allow controlling which modes assets are available in fd9d22ba57d75b278a0350492c5eab2d39d39070\n- [x] Update 3D view menus dynamically (avoid need to restart Blender) cc83951951efc28411960d950435224e8d06606c\n- [ ] Make object info node geometry output work properly\n- [x] #111529 Show menus for unassigned node group assets d2d4de8c710c4e8e648a86f904e6436133664836\n- [x] Tool specific nodes\n - [x] Selection input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Set selection e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] 3D cursor e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n - [x] Sculpt face sets input e3e6fb8ecf8252344e9bfc9dc255bf7f722aa5f0\n- [ ] Node group inputs displayed in the redo panel\n - [x] Initial input drawing bc393c403325c956ec4e83eeb072a9bdb2e7824d\n - [x] Display node group name in panel title f0467b4615b366f34f0daae81ef717c342e8f520 ee1ee584ded3b76fdd9b661244274af850b08fa9\n - [ ] Add attribute search\n - [x] Don't draw redo panel when there are no inputs c59d998ce524e37c2449694602fb6d57b6d292fa\n- [x] #111523 Improved default traits b4dc16f32d92a2fbc140abfe6eb438ff11b5d5e8\n- [ ] #111524 Finalize trait popover locations\n- [ ] Add support for evaluating output attributes\n- [x] Shortcut support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [x] Quick favorite support 65591b2c8cc83b024bc0a283bae1bbeb7ee85132\n- [ ] #111526 Filter data-block selector based on tool/modifier option #112389\n- [ ] Publish the user manual\n\n### Polishing\n\n_Not necessarily required for a release in main_\n\n- [ ] Show visual difference for tool nodes in modifier context\n- [ ] Show visual difference for viewer and simulation nodes in tool context\n- [ ] Resolve flickering in asset browser when using redo panel\n- [ ] Warnings in node editor header\n - [ ] When node group is not an asset (with button to mark as asset) #110813\n - [ ] When the node group is not marked as a tool #110813\n - [ ] When asset is not in a catalog (and not in a menu) #110813\n\n### Milestone 2\n\n_The second phase of the project, after the fundamentals are working well_\n\n- [ ] Option to show settings in popup before operation starts\n- [ ] Tool specific nodes\n - [ ] Sculpt \"soft selection\" input and set\n - [ ] View transform\n - [ ] Mouse position\n - [ ] Deformed (\"cage\") positions\n- [ ] Modal operator support\n- [ ] \"Wait for cursor\" option\n- [ ] Store operator properties for the next execution\n\n\n## Use Cases and Ideas\n- [ ] Mesh sculpt \"face set extract\"\n- [ ] Mesh sculpt \"mask extract\"\n- [ ] Lasso selection operator", "GeoNodes: Getting animated/driven Curve Radius doesn't work if curve has shape key\nOperating system: Linux-6.2.2-gentoo-x86_64-Intel-R-_Core-TM-_i9-9900K_CPU_@_3.60GHz-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.6.0 Alpha\nWorked: Likely never\n\nThis is a pretty specific set-up on the old Curves, so I'm not sure if it's something that needs to be fixed or if this datablock is getting replaced anyways, but I thought it would at least be good to be aware of.\n\nIf a curve has a shape key, the GeoNodes \"Radius\" node seems to fail to return the correct radius value.\n\nI don't know for sure if this is really a GeoNodes issue, though, because from my testing, the way the Radius value works with shape keys just seems pretty weird. It makes a fair amount of sense until the Radius value gets a driver. At that point, the shape key seems to take on whatever value the Radius had when leaving edit mode.\n\n- File: [radius_driver_not_working.blend](attachment)\n- Scale the bone; The curve point's radius is hooked up to be driven by the bone's scale, and the sphere is created by GeoNodes based on that curve point's radius. So, when you scale the bone, the sphere gets bigger.\n- Add 2 shape keys to the curve\n- Scale the bone again; Sphere doesn't scale any more.\n\nFor my use case, I don't actually need shape keys on my curve, so this won't be an issue for me at all, I just ran into it because I happened to have a temporary shape key on there and I thought I would report it.\n\n", "Cycles XML, light node does not react to transform\nCycles XML, light node does not react to transform (it was ok before migration to graph/node* node parsing). Let me know if this is a bug or it is by design.\n\nSee attached sample XML.\n\n```\n<cycles>\n<transform translate=\"0 0 -4\"><camera type=\"perspective\" /></transform>\n<integrator max_volume_bounce=\"0\" method=\"branched_path\" sample_all_lights_direct=\"true\" sample_all_lights_indirect=\"true\"/>\n<background heterogeneous_volume=\"false\" volume_sampling_method=\"equiangular\" ><scatter_volume name=\"scatter\" color=\"0.8, 0.8, 0.8\" density=\"0.3\" /><connect from=\"scatter volume\" to=\"output volume\" /></background>\n<shader name=\"point_shader\"><emission name=\"emission\" color=\"0.8 0.1 0.1\" strength=\"100\" /><connect from=\"emission emission\" to=\"output surface\" /></shader>\n\n<state shader=\"point_shader\"><light type=\"point\" co=\"0 0 0\" size=\"0.01\" /></state>\n\n<!-- Light does not react to transform node -->\n<transform translate=\"0 0.5 0.0\">\n\t<state shader=\"point_shader\"><light type=\"point\" co=\"0 0 0\" size=\"0.01\" /></state>\n</transform>\n\n</cycles>\n```", "Cycles: point cloud geometry improvements\n[D9887: Cycles: pointcloud geometry type](D9887)\n\nImprovements:\n- [x] Point Info node with radius, position, random\n- [ ] Backfaces are ignored (like curves), which means e.g. volumes inside points don't work.\n- [ ] Render as normal or ray oriented disc (see [D9887](D9887)#289012, [P2125](P2125.txt))\n- [ ] Baked shadow transparency support like hair? But must be optional since texturing alpha across the sphere/disc is useful.", "Geometry instances cannot mix with other instancing\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\nWorked: 3.0 alpha\n\n\n\n[cant scatter.blend](cant_scatter.blend)\n[2021-11-02 19-08-07.mp4](2021-11-02_19-08-07.mp4)\n\n", "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}", "Create geometry nodes modifier when selecting an existing one in the editor\nSelecting an already existing geometry nodes tree in the editor on an object without a modifier should automatically create a nodes modifier. This is in parallel to the behaviour of selecting a material without a material slot.\n", "bump node ignores height input (with certain inouts used as mapping vectors in the tree, seems to require `SOCKET_OUT_POINT`as opposed to `SOCKET_OUT_NORMAL`)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\n\nbump node does not react to data.\n\n[bump bug.blend](bump_bug.blend)\n\n\n\n\n\n\n\n\nFor Cylces, the following seem to be the working inputs (the ones that trigger the availability of requirements for the bump node):\n- Geometry node\n - Position\n - Parametric\n - all others dont trigger the requirements (derrivatives?)\n- Texture Coordinate node\n - Generated\n - UV\n - Object\n - Camera\n - Window\n - all others dont trigger the requirements (derrivatives?)", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Support warnings for field input nodes\nField input nodes evaluate in a context, but currently they give no warning if they do not support\na particular context. The initial goal is to add a warning like \"Input node does not support geometry type: Mesh\" on the spline parameter node in the following situation:\n\n{[F12738459](image.png) size=full}\n\n### Implementation\nA potential implementation isn't clear.\nIt seems there needs to be a way to keep track of which node (`bNode`, `NodeRef`, `DNode`, etc.) the field input node came from.\nThen the field evaluation system should have a way to collect errors and return them to the caller. Or maybe the caller can pass a\n\"logger\" class to the field evaluation system. That generalization could allow more specific breakdowns of node timing in the future.", "Support all attributes in the non-point cloud attribute list\nSee #87827.\n\n* position\n* UVMaps\n* Vertex groups\n(...)\n\nTechnical design discussion: #88460", "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", "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" ]

[ "Problem with a node in geomerty nodes\nOperating system:\nGraphics card:\n\nHello,\nI have a problem with a node in geomerty nodes.\n\nthe ROTATE INSTANCES node no longer works when I use it in the geometry nodes.\nThere is in the upper right corner of the node window, an icon with the letter (I).\n\n\nThe problem occurred when using BLENDER version 3.1.\nSo I downloaded version 3.2, but nothing.\n\nHow can I do to solve the problem?\n\nThanks in advance." ]

[ "Drawing of pose markers does not take NLA time mapping into account\nOperating system: Linux-5.11.0-49-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.2.0 Alpha, branch: `master`, hash: `d6e7241237`\nWorked: don't think it ever workerd\n\nShifting an Action on the NLA, then going into tweak mode to edit it, shows the keyframes shifted in the animation editors. The action's pose markers are still in their absolute position.\n\n\n\nThe pose markers should align with the 2nd, 3rd, and 4th keyframe.\n\n- Open the attached file, look at the pose markers.\n- Drag the action in the NLA editor, and see the keys moving while the pose markers stay put.\n\n[[D14176](D14176)-select-markers.blend](https://archive.blender.org/developer/F13001132/D14176-select-markers.blend)\n\n**Context & Relevance**\n\nThese \"pose\" markers originated from the old, now obsolete, pose library. However, regardless of the status of that library, I've heard the desire to have Action-scoped markers (so independent of scene time), and the pose markers would fit that need quite well. The only thing that has to be done to make this a reality is a rename (from \"pose marker\" to \"action marker\") and some UI cleanup. Fixing this bug is a good start.\n\nMarked as low-prio because the new purpose for pose markers isn't that official yet.\n\n**Note:** Be sure to test the `marker.select_leftright` operator as well (f1ae6952a8) after addressing this issue.\n", "Animation Editors: Modifier keys cancel out dragging handles \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.4.0 Alpha\n\nIn recent releases db4313610cab was implemented and the animation editors are still not adapted to this behaviour. This fix allows the use to press any keyboard key, like `Shift` or `X`, etc, before the drag threshold of the current action is reached, and it will cause the operator to execute.\n\nFor example: Click and hold on a move gizmo in object mode. Either drag 3 pixels to start the operation and then press `X` and hold `Shift` to slowly move along the x axis.\nOR immediately press `X` and hold `Shift` without reaching the drag threshold of 3 pixels to already start the operator.\n\nBefore this fix, any pressed keys would cancel the click & drag and prevent the operator from running.\nThis is still the case with the graph and dopesheet editors.\n\n- Create a simple animation to the default cube\n- click and drag on the keyframes or handles in the animation editors\n- Now click and hold them, hold `Shift`, and then continue to drag. Nothing happens.", "NLA: Animated Influence/Time Property Sliders Unresponsive\nTask: #76549 (NLA Strip influence slider doesn't respond to autokey correctly.)\n\n**Source of Problem**: (anim_sys.c) *nlastrip_evaluate_controls() -> animsys_evaluate_fcurves()*: I believe the issue is due to NLA evaluation, where the animated strip properties are evaluated and flushed at the same time the action strip channels are evaluated. Since autokeying doesn't insert a keyframe as the value changes, that's probably why the slider is unresponsive. \n\n**Solution**: Perhaps we should separate (despgraph-wise) NLA strip animated property evaluation from when we evaluate the NLA system for general animation? Animated strip properties would only be evaluated and flushed on frame change or when the whole frame needs refreshed. Then normal non-NLA animation evaluation will just read the strip properties as is. This would allow the slider be responsive. It also allows the user to change these properties and view their changes without having to keyframe, just like any other Blender animated property. \n\n**Potential Problems with Solution:** What do we do when strip influence is animated and the user changes it (without keying) then inserts keys on character bones. When we remap the keyframes, should we re-evaluate and use the strip's animated influence? Or should the new keys be remapped using the unkeyed strip time?", "splitting an nla track prevents adding new keyframes outside of the clips bounds in tweak mode\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\nWorked: unsure\n\nsplitting an nla track prevents adding new keyframes outside of the clips bounds in tweak mode\n\nadd armature\nanimate\npush down\nsplit clip\ntweak clip\nmove playhead beyond clips bounds\nattempt to add keyframe\n\nvideo attached.\n\nThanks.\n\n", "Animation: Exiting NLA tweak mode on empty action corrupts entire NLA track\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3060 Ti\n\nBroken: 3.3.0, 3.5.0\nWorked: Unknown\n\n\nWhen tweaking a strip on the NLA, if the user deletes all the keyframes of the action being tweaked, when the user exits tweak mode, all other NLA strips on that track will be moved in an unexpected and undesirable way.\n\n[tweakbug.mp4](tweakbug.mp4)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open the attached .blend file\n2. Delete the keyframes on the track being tweaked.\n3. Exit tweak mode by pressing Tab.\n4. Observe that the NLA strips have been moved.\n\n[tweakbug.blend](tweakbug.blend)", "Clipped text labels intermittently missing ellipses by Float properties\nBroken: 3.4\nWorked: -\n\nThere are no ellipses by node group parameters in all editors by unhidden values \n\n[2022-09-02 16-57-07.mp4](2022-09-02_16-57-07.mp4) \n\n- Open attached file\n[missing_ellipsis_bug.blend](missing_ellipsis_bug.blend)", "Resizing Outliner and Properties editor windows makes the outliner view go up if its long enough.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nResizing Outliner and Properties editor windows makes the outliner view go up if its long enough.\n\n\n - Make the scene have enough objects in it so you need to scroll down to see the end in the outliner.\n - Resize the Outliner/Properties windows while you are not seeing the top of the list of objects in the outliner.\n\nTest File:\n[#89056.blend](T89056.blend)\n", "Generic Rigid Body Constraint Bug\nOperating system: Windows 10\nGraphics card: Radeon RX 470\n\nBroken: 2.83.0\nWorked: Unknown if it ever worked\n\nAngle limit not only doesn't work but causes weird neverending twitching back and forth\nUPDATE:\nTwitching happens for both cases when both rigid bodies are active and when one of them is passive.\n[M0DJ38oWQo.mp4](M0DJ38oWQo.mp4)\n\n1. Add 2 rigid bodies, 1 active, 1 passive animated\n2. Position them active on top, passive on the bottom\n3. Add an empty in between them, add a rigid body constraint to it, select the 2 rigid bodies in its settings, uncheck disable collisions.\n4. Change the joint type to Generic, limit location to 0-0 on each axis.\n5. Play. Now it works, once you select the passive RB and move it it should behave normal.\n6. Undo. Check angle limit on Z and choose some angle range (I had it set to -30 to 30).\n7. Play. Move the passive RB and watch it breaking.\n", "Cyclic Strip Time not work with non-zero Action Clip Start Frame\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.3\nWorked: ???\n\nCyclic Strip Time not work with Action Clip\n\nI attached .blend to show this bug.\nThe track called \"Ok\" works with the \"Cyclic Strip Time\" check mark correctly.\nThe track called \"Bug\" works with the \"Cyclic Strip Time\" check mark incorrectly.\n\nIn the track \"Ok\", there are two keys, at 0 and 10 frames.\nIn the track \"Bug\", the same two keys, but for 43 and 53 frames. In the Action Clip, I set the values Frame Start =43 and End = 53.\nI expect that the \"Bug\" track will perform the same actions as the \"Ok\" track, but this does not happen.\nI think this is a mistake.\n[BugCST.blend](BugCST.blend)\n", "VSE: Operators missing cache invalidation\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.1.0 Alpha\n\n\nThese things were also reported in: #90415 but not fixed yet. Invalidate cache = restart prefetch frames. \n\nScene Strips:\n - 3D View object changes in referenced Scene strip need to invalidate cache.\n - Changing the Post Processing setting in the referenced scene in a scene strip needs to invalidate cache.\n - Changes in Compositor need to invalidate cache.\n\nText Strips:\n - Doesn't update while entering text, but do when changing Wrap Width.\n\nSnap Strips to Current Frame:\n - Is not caching from the Playhead position. It actually makes prefetch caching stop. And it will only start again if Show Cache is disabled and reenabled. \n\n\nModifiers:\n - Curves doesn't update Preview while dragging curve points, only on release.\n\nUnmute Strips:\n - Need to invalidate cache.\n\nBtw. caching still needs to work when reverse playing and also needs to keep some frames cached on the left side of the playhead for quick reverse playing. There might be an old report open for this, but I can't remember.\n\n\n", "Visual bug when using strenght tool in 3D space left for Tool Panel\nOperating system: Windows 10 64Bit\nGraphics card: Nvidia GTX 960M\n\nBroken: 2.80 RC\n\nVisual bug in Sculpt mode, Vertex Paint, Weight paint and Texture paint\n\n1. Go to Texture Paint mode\n2. Set strength tool to 1.0 (shift F)\n3. Use strenght tool hotkey (Shift F) in the narrow 3D space left for the Tool Panel\n\n", "Area light resize gizmo (amongst other gizmos) missing undo step?\nOperating system: Arch Linux\nGraphics card: GTX Titan\n\nBroken: 2.81.3 (232049dd9408)\n\n\nSeems an area light resize in the 3D view is not registered with the undo system. \n\n\n1. Add an area light to the scene\n2. Grab and move somewhere else\n3. Change size with widget\n4. Ctrl-Z\n5. The light is now back at the origin with the default size\n\nNote that when changing the size using the properties panel an undo *will* work correctly, i.e. only change back the size.\n\nThis seems true for a couple of Gizmos [not adding an undo step -- or at least not working correctly / as expected]\nThese are the ones I quickly checked:\n- Camera Focal Length\n- Area Light size\n- Spot Size\n- Wind Force Field Strength\n- Reference Image size\n- Compositor Backdrop\n- Reference image size and move\n", "UV Editing move/scale/rotate tool, add option to respect pins\nFor Live Unwrap to work correctly, the move/scale/rotate etc tools all allow the user to move the *pinned* UVs, while the live unwrap algorithm moves all the other UVs in a nice manner.\n\nHowever, without Live Unwrap, the \"Pin\" concept could be extended to actually Pin the UVs in place.\n\nThis is a feature request to add an option to actually Pin the Pinned UVs when using the move tool, with an additional option to respect the falloff parameters around the pinned UVs as well as the user selection.\n\nFrom a design perspective, this should probably consider the \"Grab\" Sculpt tool and the generic Transform tool as well.\n\n", "Application handler not executed when video sequencer contains a strip\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.4\n\nA registered handler for frame_change_post does not get executed while rendering an animation when there is a strip present in the video sequencer.\n\n1. Open the example file and turn on the system console\n2. Execute the example script present in the file\n3. Render an animation, note how you can see the handler getting called before each rendered frame in the console\n4. Add a strip to the video sequencer (for example a solid color)\n5. Render another animation, note how this time the handler doesn't get called per frame anymore\n6. Remove the strip again\n7. Render once more, note how it works again as expected\n\n**Example file**\n[bug_example.blend](bug_example.blend)\n", "UI: In Preferences, Invisible Execute Region in Nav_bar, blocks resize of area.\nBroken: 957b4547ae, 6b082278d1\nWorked: never?\n\nWhen you try to resize preferences, you grab the execute region edge instead(Only for nav_bar side).\nThe default state, has the area open but invisible. Blocking resize.\n\nSeparate preference window, does not have a problem.\n\n[2019-05-10 09-01-29.mkv](2019-05-10_09-01-29.mkv)" ]

[ "NLA: Fix Dragging Strips\nNOTE: test the patches for Solution1 temp-[D10103](https://archive.blender.org/developer/D10103)-nla_support_strip_overlap_during_transform/temp-[D10103](D10103)-nla_support_strip_overlap_during_transform-blender-2.92.0-5065c0e6d5bc-windows64.zip\n\nThis is no longer true, we would rather remove them and improve the interaction with HOLD type ****Update design since transition strips should be kept.****\nTodo: Add concrete examples where transitions are useful in the ideal case (where strips animate through the transition).\n___\nReport: #82195 (NLA tracks won't pass through actions or locked tracks)\n\n**Summary:** The ideal solution is to get rid of transition strip types. They're useless. Let strips overlap. When they do, they get blended in order like an upper strip. Then we don't have to restrict movement.\n\n___\n\nBehavior can be found in: (transform_convert_nla.c) *recalcData_nla()*\n**Problem**: The core intent of the function is to prevent moved strips from overlapping other strips. The restriction is reasonable since NLA evaluation is undefined in this case. However, the implementation prevents the ability to move a strip to its destination even if it wouldn't result in overlap. \n\nWhen moving strips:\n* You cannot move a strip through a locked track, even if not the intended final destination.\n\n* You cannot move a strip past another in the same track, even if the intended final destination would not result in overlap.\n\n* You cannot move a strip into through or into a track if doing so results in overlap. \n\n* Vertically moving strips, when there are no more nla tracks, leads to strips being vertically compressed. This breaks the animation when strip extrapolation is important.\n\n___\n**Solution1:** (Simpler solution) We only apply the restriction on the final strip location. If the strip cannot be placed without overlap, then we either cancel the move operation (not ideal) or notify the user (show the strip as red?) without cancelling.\n\n[D10101: Cleanup: Nla: Refactor nla.c functions](D10101) (independent patch) Does a little bit of refactoring which [D10103](D10103) relies on.\n[D10102: NLA: Strip Post-transform Horizontal Shuffle](D10102) (independent patch) Adds support for horizontal shuffling so users can horizontally drag strips past eachother.\n[D10103: NLA: Strip Post-transform Vertical Shuffle and Auto-Grow Track List](D10103) (depends on prior patches) Adds support for vertical shuffling so users can vertically drag strips into a new track even if it results in overlap or the user moves the strip into a locked track.\n\nPatches have been made for this solution since it's simpler and faster to implement. Overlap support can still be worked on but is a lower priority and still has design problems to figure out.\n___\n**Solution2:** (Ideal solution, but would take longer to implement) We change NLA evaluation to work properly when strips overlap. Then we can completely remove the restriction and let the animator freely move strips. \n \n**Patch1: Completely remove transition types**\nWe can simplify NLA evaluation here a bit. NLA transitions are problematic and ineffective. *Transition strip types should be completely removed.* They do a lerp between the previous strip's last pose and next strip's first pose. Generally in animation, lerping 2 poses is a problem you fix, not something you ever want. Support-wise, transitions are a bit broken anyways (see [D9711](D9711) and [D9713](D9713))\n\n**Patch2: Implement new behavior when strips overlap**\nInstead of an explicit transition strip type, we'll let action and meta strips support a new transition behavior. When two strips overlap, we simply blend the next strip as if it was an upper strip. That's the core idea. \"Transitioning\" strips of the same track would used for convenience and organization. This would simplify the keyframe remapping math. In [D8296](D8296), I couldn't figure out the math to properly invert through transitions between a Quaternion Combine strip and a Quaternion Replace (or any non-Combine) strip. With the new behavior, keyframing through transitions is simplified to inverting through any other strip. \n\n**Patch3: Re-add support for holding poses through the transition**\nThough, as is, both strips are always animated through the transition. We don't have the ability to hold one strip's boundary pose while the other animates through the transition. I propose a few new strip properties: `hold_left_duration` (unit: scene frame), `hold_right_duration`. The influence over these regions can be automatically calculated when strips overlap. Or they can be keyed into shape using the existing influence fcurve. As an example of these new properties, we'll have two strips that only overlap over this held duration. \n*Note. I'm having second thoughts on the properties. Yes, there should be support for holding poses through the transition. But the problem is how these properties are anchored relative to the strip bounds and what's most convenient. I want to avoid problems like the ones we already have with nla strip frame_start/end being tightly related to the action clips frame_start/end, scale and repeat values. This leads to unintuitive strip frame_start/end changes.*\n\n**Patch4: Finally loosen strip dragging logic (only relies on patch2)**\nWe can completely remove the dragging restriction and let the animator freely move and overlap strips.\n \n___\n\n(Pretend the two strips are in the same row/track. I did not draw them that way because I'm not sure how the UI should look. This also isn't a suggestion for how the UI should render)\n\nThis results in *nearly*the same result as old Transition clips. Only *nearly*, because the old implementation would first blend the prev strip with the lower NLA stack, then blend the next strip with the lower NLA stack, then lerp the two. The new behavior holds the previous strip's last pose over the light green area. The next strip's first pose is held over the pink area. The influence of the next strip increases linearly. \n___\n\nThis holds the previous strip's last pose. The next strip animates as it's blended.\n___\n\n\nAnother possibility.\n___\n\n**Problematic UI case**: I'm not sure what the proper UI should look like when one strip completely overlaps. The animator can always just move the strip out above as a work around. Logically, it would evaluate fine. It would just be a UI issue. What if N strips overlap? It still all works out. We blend the strips in the order of their start frame. What if all strips are on the same start frame? That case won't be properly supported and considered undefined (as in we won't fix it). The animator can and should fix it themselves. \n__\n\n**Alternative WorkAround:** Add operators that can be used as workarounds.\n* ([RCS]())Send strip to the end of the active strip or track, with options to handle overlap properly. \n\n___\nPatches:\n\n**(Abandoned)Patch set 1: Removal of transitions** \n*Note: I'm not sure how file versioning should be handled? I haven't removed the strip type NLASTRIP_TYPE_TRANSITION yet. I'm not sure if the enum should remain so it can be used for file versioning to either delete transitions or convert them to the new behavior (after Patch set 3).*\n[D9702: Nla Transitions Obselete: remove ui icon](D9702)\n[D9703: Nla Transitions Obselete: Nla Stack no longer evaluates Transitions](D9703)\n[D9704: Nla Transitions Obselete: Remove Operator Add Transition](D9704) \n[D9705: Nla Transitions Obselete: Remove themed drawing](D9705) \n[D9706: Nla Transitions Obselete: Remove default naming case](D9706) \n[D9707: Nla Transitions Obselete: Special case for adjacent strip deletion](D9707) \n[D9708: Nla Transitions Obselete: Adjacent strip overlap resolution](D9708) \n[D9709: Nla Transitions Obselete: nlastrip_get_frame()](D9709) \n[D9710: Nla Transitions Obselete: RNA strip frame_start/end set functions](D9710) \n[D9711: Nla Transitions Obselete: Transform, redundant check](D9711) \n[D9712: Nla Transitions Obselete: Transform, Cancelling](D9712) \n[D9713: Nla Transitions Obselete: Transform, broken strip exceed resolution](D9713) \n[D9714: Nla Transitions Obselete: Loose comments](D9714)\n**Abandon Reason:** I misunderstood why transitions were limited. Yes, their current implementation only supports single pose transitions. But they would be more useful if the strips animated through the transition. Alexander Gavrilov suggested we keep transitions for their branched evaluation behavior.\n" ]

[ "Sculpt mode: Pose/Cloth gizmos/cursors remain visible when switching to other tools \nOperating system: Win 10\n\nBroken: blender-2.92.0-165b4f85ec23-windows64\nWorked: 2.90\n\nThe gizmos/cursors of tools like Pose and Cloth remain visible when switching to other tools that shouldn't have cursor... which wasn't the case in 2.90...\n\n[2020-10-24_21-16-50.mp4](2020-10-24_21-16-50.mp4)", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)", "Mask Opacity keyframes not visible anywhere.\nUbuntu 14.04 64x\nnVidia GT620\n\nBroken: 2.78a\n\nKeyframes in LayerMask \"Opacity\" or \"Invert the mask B/W\" can be created. These keyframes exist in an existing Action (can be seen in Outliner - Actions and has datapath), but they don't appear in DopeSheet - DopeSheet nor DopeSheet - Mask. They can't be modified as the other keyframes. Nor changing its type (keyframe, interpolation, handle).\n\n- Open this file: [101-mask-keyframes.blend](101-mask-keyframes.blend)\n- Check the MaskLayer Opacity animation by going from 10 to 20 and back. Keyframes are visible only in the slider (as yellow slider).\n- The same with \"Invert the mask B/W\". Frame 30 and 40 have keyframes.\n\nEDIT: file uploaded.", "Animating hide_viewport propertie deselect objects\nOperating system: Linux-4.15.0-20-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.87.01\n\nBroken: version: 2.81 (sub 16)\n\nWhen animating the \"*hide_viewport*\" propertie of an object it deselect it, this was not the case in 2.79.\nNot only the selection is lost but this make the user unable to use filters \"*Selected only*\" in combination with \"*Display hidden*\" like you could do in 2.79\n\n{[F7930271](losing_selection_and_only_select_filter.gif), size=full}\n\nAnimate the hide_viewport visibility of an object, in graph editor toggle on *Selected only* and *Display hidden*. Select the object and then scrub in/out the animated hide range, object gets deselected.\nExample blend : [animated_display_on_cube.blend](animated_display_on_cube.blend)\n\nSomeone also mentionned it in blender stack exchange with gifs to compare 2.79 and 2.8+ behavior : hiding-object-in-2-80-via-animated-disable-in-viewport-loses-selection\n\n\nThank you !\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 ", "Statistic doesn't update if object deleted due to object data deletion with RMB\nBroken: version: 3.0.0\nBroken: version: 2.80 (sub 75)\nWorked: unsure (didn't find scene statistics in 2.79...)\n\nScene statistic (both in footer and 3D viewport) does not update correctly if object data is deleted with RMB\n\n1. Open default scene.\n2. Make sure you enable scene statistic either in 3D viewport or footer.\n3. In outliner unroll object to show it's object data, i.e. default cude.\n4. Click on object data, i.e. cube mesh, with RMB and delete it.\nObject will be deleted since it doesn't have mesh/camera/light object data. Notice that scene statistic is not updated (number of objects, vertices, selected status etc.). To update it you can select any object or click on outliner (doesn't matter on object or not).\n\nThat works correctly if object is not deleted, i.e. adding subdivision modifier (statistic will update) and then deleting it with RMB in outliner (statistic updated again).", "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", "Mode locked and crash if objects become disabled in viewport while not in object mode\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: didn't crash but showed an error message in 2.91.2\n\nObjects that are in a mode which is not Edit Mode nor Object Mode, will lock the mode setting (so the mode options are greyed out and unusable) if they get disabled in the viewport. Hiding will not cause the this bug, it needs to be disabled in viewport using that display icon in the outliner, not the eye.\n\nThe solution for this is probably to make the disable in viewport action switch the mode to object mode if the active objects gets removed (much like delete from outliner). Another solution would be to still allow the mode switch.\n\nMuch worse though! Blender crashes sometimes when it gets into this state. I can reliably crash blender as described below.\n\nGo into weightpaint mode of the default cube and disable it in the viewport using the outliner (you need to enable the option first). Now you are stuck and have to enable it in the viewport first to be able to edit anything.\n\nNow restart blender etc. and try this:\n1. Go into Vertex Paint Mode of the default cube\n2. Hit Tab to go into Edit Mode\n3. Disable the cube in the viewport using the outliner as above\n4. Hit Tab to switch out of Edit Mode -> Crash", "Right clicking on 3D Viewport Header not working as expected\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 and older)\n\n\nIf you Right click on empty space of 3D Viewport Header it will not bring Header Menu for disabling or enabling Header. it was possible in version 3.6\nThere are just 2 options to bring menu:\n1- Right click very close to Header items but not inside items(it's really hard to reach)\n2- disable region overlap (many prefer not to turn it off)\n\nI know it is now available to see and select objects through header but I think old right click should back to header because:\n1- constancy( when you right click on all other editor's header that menu will pop up)\n2- beginner friendly (imagine someone new to blender or blender 4 wants to hide header and he does not know new region toggle pie menu so it is hard to hide it)\n\n", "Sculpt Mode Border Mask Tool Todo\n## Sculpt Mode Border Mask Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from mask, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools", "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", "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.", "Regression: 3.0.0: The curve is not hidden in the Viewport if there is a Bevel value\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: 3.0.0 `d046a1f2fa `\nWorked: 3.0.0 `1275ce61b1`\n\nHiding the curve display in the viewport as an object does not work\n\nIf you add a curve to the scene and try to hide its display and the ability to select in View Object Types, then hiding works.\nIf you add a profile for a curve or Bevel, then hiding does not work. In this form, the curve is hidden only when it is done as a hide mesh.\nPerhaps this is the correct behavior.\n\n[2022-12-28 16-39-53.mp4](2022-12-28_16-39-53.mp4)\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", "File browser buttons disappear on undo in another window\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- All versions since the new file browser was introduced are affected by this\nWorked: Never\n\nI've tried to save file with CTRL+S and by accident pressed my LMB on a viewport. Because of that mistake, I pasted object in my scene, instead of pasting file name in \"Blender File View\" window. So I tapped CTRL+Z (while still being active in a viewport) and whole panel with buttons \"Save file\", \"Cancel\" in \"Blender File View\" window disappeared. I've tested this on a completely new empty blender file. Pressing on a viewport didn't recreate that effect (probably, because nothing was there). But pressing on outliner or timeline have the same issue.\n\n- Open Blender\n- CTRL+S\n- Press LMB on an Outliner\n- CTRL+Z\n\n[UI bug.blend](UI_bug.blend)" ]

[ "Alt + H does not work for 2.79 files\nOperating system: Linux-5.2.3-1-default-x86_64-with-glibc2.9 64 Bits\nGraphics card: Mesa DRI Intel(R) Ivybridge Mobile Intel Open Source Technology Center 4.2 (Core Profile) Mesa 19.1.3\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nOpen file with Blender 2.8, Alt +H does not make visible hidden Monkey.\nIt work in Outliner.\n\n\n[hide_with _279.blend](hide_with__279.blend)\n\n" ]

[ "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "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", "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", "Mesh Attributes Python API Is Buggy\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3070\n\nBroken: 2.93 & 3.3\nWorked: \n\nAccessing geometry attributes via python causes internal errors and mismatched pointers.\n\n\n```\n- Blender 3.3.0 bug\n- 1) Open new file w/ default cube\n- 2) Paste this script into the scripting tab\n- 3) Make sure the cube is selected and run this script\n\nimport bpy\n\nme = bpy.context.active_object.data\n\nfva = me.attributes.new('float_vector_attribute', 'FLOAT_VECTOR', 'CORNER')\n\nprint(f'fva : {fva}.data_type = {fva.data_type}')\n\nfca = me.attributes.new('float_color_attribute', 'FLOAT_COLOR', 'CORNER')\n\nprint(f'fva (again): {fva}.data_type = {fva.data_type}') # output will be wrong\nprint(f'fca : {fca}.data_type = {fca.data_type}')\n\nme.calc_normals_split() # causes next line to crash\n\nfva.data[0].vector = (1, 2, 3) # only crashes the first time the script is run\n\n```", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "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", "Steam Blender doesnt open Saved Files\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\n\nSaved Files from Steams Blender do not open and require me to have a normal Blender file downloaded separately.\n\nSave a file from the Blender downloaded from Steam, then try to open it normally. The PC will say it cannot find a suitable software to open it in. The problem will be fixed if I have a separate Blender downloaded. (I need the steam to count the time I spend on it)\nBased on the normal Startup of Blender, I have not added or changed anything.\n\nThank you very much, and all the best.\nTake care.\n\n", "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", "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)", "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", "API's new context.property causing immediate Blender access violation crash.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked: N/A\n\ncertain properties cause immediate access violation when using the new context.property which was introduced recently. See: 6ba0346797f43cd73eb1003ce65a62b8409203fb and 107280\n\n\n\n1. open attached blend file makins sure 'load ui' is ticked in the file open options.\n2. click the play button on the script editor to register the shortcut key\n3. hover the mouse over the font size in the text editor's font size property\n \n4. press tab\n5. immediate access violation is triggered in the poll function on line 28.\n\n", "Crash when sculpting with a texture, deleting the image of the texture and exiting sculpt mode\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: version: 3.4, 3.5, 3.6\nBroken: version: 3.3.3\nBroken: 3.1.0\nWorked: 3.0.1\nWorked: 2.93 LTS\n\nCaused by 9111ea78ac\n\nBlender crashes when a texture image is deleted and you exit sculpt mode.\n\nYou can test it inside the attached blend file. I basically just attached an image to a sculpting brush.\n\n1. Open the blend file below\n2. draw on the surface of the sphere\n3. delete the image inside the outliner\n4. exit sculpt mode\n\nCrash occurs because `item->image->runtime.cache_mutex` is null inside `BKE_image_pool_free`\n```\nStack trace:\nblender.exe :0x00007FF713D04C10 pthread_mutex_lock\nblender.exe :0x00007FF70E6EE880 BKE_image_pool_free\nblender.exe :0x00007FF70E6B5CF0 BKE_sculptsession_free\nblender.exe :0x00007FF70F1B67A0 ED_object_sculptmode_exit_ex\nblender.exe :0x00007FF70F1B85F0 sculpt_mode_toggle_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\nblender.exe :0x00007FF70E9528D0 wm_operator_call_internal\nblender.exe :0x00007FF70E955880 WM_operator_name_call_ptr\nblender.exe :0x00007FF70F171800 ED_object_mode_set_ex\nblender.exe :0x00007FF70F148710 object_mode_set_exec\nblender.exe :0x00007FF70E953220 wm_operator_invoke\n```", " 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)", "Crash when updating image pixel data through python API\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.0, 2.90\nWorked: N/A\n\nBlender crashes with apparent memory corruption, when image pixel data and previous are updated frequently with python script.\nStack traces give no obvious answer, i have seen it happen in depsgraph eval, node graph code, imbuf, etc.\n\n*Note: i could not reproduce this issue in debug mode so far, only release or RelWithDebInfo seems to work.*\n\n 1. Open attacehd file\n - Run the script\n - Make sure the scene properties are visible (it seems to only crash when displaying image previews).\n - Grab the default cube and wiggle it around to force depsgraph updates.\n - If it doesn't want to crash, re-open Blender, it seems to be quite random.\n\nI'm using a node group to access image data blocks, so they can be displayed in a panel as pointers. The code generates data to replace the image pixels as well as the preview.\nI have also tried running a timer and deferring pixel updates using a queue as suggested [here ](bpy.app.timers.html#use-a-timer-to-react-to-events-in-another-thread), just in case the depsgraph post update is somehow not safe, but this doesn't change anything substantially. The bug happens in both cases.\n\n[crashtest.blend](crashtest.blend)", "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" ]

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

[ "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", "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)", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Particle collisions aren't simulated before frame zero for negative frame simulations\nBroken: 2.79, 2.81\nWorked: (optional)\n\nMaking particles simulation start from negative frames don't allow for those particles to have collisions with meshes. Unless I set the initial frame to be negative.\n\n\nOpen the file and look at the already baked simulation. The first particles went through while the later ones collide perfectly. You can also rebake the cache and see the same result\n\n[ParticleBug.blend](ParticleBug.blend)\n\n**Known workaround**\nChange initial frame to match the first simulated frame before baking the simulation.\n\n", "Particles \"Numbered\" Incorrectly When Generation Time is Influenced by Texture\nSee attached - probably not relevant.\n\nBroken: 2.90 - see attached\n\nA keyed particle system sends particles from one particle system to another particle system. Normally the ordering is respected: the first-generated particle in one system gets sent to the first-generated particle in the second system, same for the second-generated particle, and so forth. This does not work though if a texture is used to generate a particle system. Various visual effects rely on the ordering being respected.\n\nCreate a plane mesh. Add a particle system to it, physics none, starting at time 1 and ending at time 10 with 10 particles. Add a blend texture so the particles are generated from one side to another. Add a second particle system on a second object. Now create a keyed particle system on the second object going from the first particle system to the second particle system, starting at time 15 and ending at time 24 with 10 particles. Display its particles in a distinct way (e.g., as red spheres). Step through the simulation frame by frame. Note the order that the particles appear on the plane mesh (first particle system). Then at frames 15, 16 and 17 note the order in which the keyed particles appear. They appear in a different order, whereas, if a texture is not used but the random seed is used, the keyed particles will be created in the same order that they were created in the first particle system regardless of the chosen random seed.\n\n[system-info.txt](system-info.txt)\n[Particle Numbering Bug.blend](Particle_Numbering_Bug.blend)", "Boolean Exact Mode failing\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: 3.5.0 - 3.6.0\nWorked: Unknown.\n\nIn the attached `v8 bug daily.blend` file, an object mysteriously vanishes at frame 36, then reappears in frame 37. Changing various minor things makes the problem go away.\n\nThat file uses a simple armature to animate the rotation of the \"Rotor\" object. \n\nIf you change the end frame of the animation from 60 to 61 and move the last keyframe from frame 61 to frame 62--i.e., stretch out the animation just a little bit--the problem goes away.\n\n- Open the [Boolean_exact_difference__bug.blend](attachment) file\n- Enable the boolean modifier\nor \n- Open the [v8 bug daily 03b.blend](107388#:~:text=Save-,v8%20bug%20daily%2003b.blend,-1006%20KiB) file\n- Go to frame 36", "Sun light shadows in Eevee disappear when emitter particles become very distant from the camera.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken version: 3.4.0 Alpha, branch: master, commit date: 2022-10-27 21:09, hash: 454dd3f7f0a3\nBroken: version: 3.3.1\nWorked: unknown\n\nIn Eevee, the sun light shadow is effectively disabled when particles(and perhaps other objects) become very distant.\n\n\nIn the attached test file, if the viewport shading is set to rendered and the timeline is scrubbed to frame 10, you can observe the sun light is no longer casting shadows, as if they've been disabled. In this scene, some particles shoot off very fast and far into the distance which seems to cause the shadow bounds/volume to become unreasonably large. Alternatively, at frame 10, you can toggle the visibility of the emitter object named 'Particle Emitter with drag - BROKEN' and watch the shadows turn on/off. The value set in the sun light shadow->cascade shadow map->max distance setting seems to have no effect. It doesn't seem like that max distance parameter does anything, or that particles aren't getting filtered by that value.\n\n[Particle Drag and Sun Shadow Bug.blend](Particle_Drag_and_Sun_Shadow_Bug.blend)\n\nMore info available in the text editor of the attached blend file, item #3. Thanks!\n\n\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", "Particles cache ignores animated lifetime\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0\nWorked: not sure if it worked after 2.80, maybe it worked in 2.79, but I'm not sure.\n\nIf you animate the lifetime and bake the particles everything in the same blender session everything works correctly, no matter if you bake them to disk or to memory.\nWhen you save the file, and open the file again the particle cache is broken and it's loading all the animation with the lifetime present in the first frame, no matter if it's a disk cache or a memory cache.\n\n\nBlende file: [test.blend](test.blend)\n\nSteps to reproduce:\n\nYou can watch the video I did or follow this steps:\n\nVideo:[particle_lifetime_an_bug.mp4](particle_lifetime_an_bug.mp4)\n\n1.- Open the attached blend file with Blender 2.90 release\n2.- Clean the cache if there is one, change some parameter like particle count (don't touch particle lifetime, it's animated)\n3.- Bake the animation, and you will see the correct result\n4.- create a new file\n5.- reload our test file\n6.- you will see how the cache is not behaving correctly and it's ignoring the animated lifetime\n\nIt's impossible to trustworthy bake particles without this working, because not even the disk cache is working\n\n\n", "Hair particles: 'Use modifier Stack' option removes all hair if particles have been added or removed in particle editmode\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)\n\nUse modifier stack checkbox deletes all the hair particles if they were created with the add hair brush and combed (not necessary), even if there are no modifiers before the particle system. This also happens if particles have been deleted (X) in particle editmode.\nAnd there is no way to get those hairs back. It can really destroy all your work on grooming.\nBy the way, that check box becomes inactive in 2.79 after grooming, but it's active for some reason.\n\nCreate a hair particle system.\nGo into particle edit mode.\nDelete all the hairs (by the way, you won't be able to do that until you comb it, may be a second bug).\nAdd some hairs via add hair brush (you can add hair without deleting on the previous step, the bug will occur anyway).\nGo back to object mode.\nCheck the use modifier stack checkbox.\nAll the hairs disappear!\n\nThe attached file has all that done except the very last step.\n\n[hair_use_modifier_stack_bug.blend](hair_use_modifier_stack_bug.blend)", "Child Of vertex group fails when controled by Particle System\nWin10 64bit\n\nBroken: 2.79\n\nChild Of constraint fails on rotation from PS\n\nOpen file, play animation on every layer\n\nFirst layer: *Empty* with *Child Of* constraint is controled by Plane's transform animation -> works OK\nSecond layer: *Empties* with *Child Of* are controled by Plane's *Particle System* (via *Explode*) -> Location is maintained, but **rotation is non-synchronized**\nThird layer (example of how previous case is expected to work): Empties parented to *3 vertices* are controled by same PS - OK\n[Child_Of_test.blend](Child_Of_test.blend)\n", "Metaball properties do not update during animation playback\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.8, 2.9\nWorked: 2.79\n\nMetaball particles do not update during animation playback when their location, radius, stiffness and other properties are animated within one object (when one metaball object has multiple particles). I'm not the only one who have this problem: 2-8-metaball-animation-viewport-metasurface-doesnt-update\n\n1. Create one Metaball object, enter Edit Mode and insert keyframe to its location, radius, stiffness, hide or other properties.\n2. Change the frame, move the metaball or change its property and insert another keyframe. Notice that if you will try to use Autokey, it won't work and just show corresponding parameter in orange.\n3. Play animation.\n\nIn 2.79 you will be able to see your particle being updated in real time.\nIn 2.8 and 2.9 you will only see particle's radius circle moving (or property checkbox changing its status) but not the particle itself. ", "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", "Links persist invisibly after their source sockets are removed\nBroken: Probably forever (e.g. 3.0, 3.1)\nWorked: N/A\n\nIf the output socket of a node is removed, the input socket it was connected to does not show a button to input a value. It acts like it's still connected.\n\n**Detailed replication**\n1. Go into the Shader Editor\n2. Create the *Voronoi Texture* node and a *Math* node\n3. Set the *Voronoi Texture* node to 4D, and plug its new W output into the *Math* node\n4. Set the *Voronoi Texture* node to 3D. Observe that the input on the *Math* node still acts like it's connected\n5. Click and drag from that input on the *Math* node. A bogus wire will appear from the *Voronoi Texture* node, coming from where the W output used to be.\n\nYou can then plug this wire into another socket. It will disappear again once you let go. If you set the *Voronoi Texture* node back to 4D, the wires will re-appear.\n\nVideo example:\n\n[XwBMq60aMI.mp4](XwBMq60aMI.mp4)\n\n**Another example:**\n\n{[F13079601](free-socket.blend), size=full}\n\nIn this case you can even save the file in this state where you can't see or edit the value of the node until you disconnect it.\n\n", "Particle Edit Breaks After Selecting a Mesh with Cloth Physics\nOperating system: macOS 10.13.6\nGraphics card: NVIDIA GeForce GT 650M 1024 MB\n\nBroken: at least 2.82 up to 2.92 experimental (I suspect it never worked since 2.80)\nWorked: 2.79\n\nParticle edit behaves like object edit mode, but the UI shows \"Particle Edit\" being active.\n- There is no circle typical for the comb tool around the mouse cursor.\n- No additional key points to select or black hair strands are rendered.\n- Instead of e.g. combing you will move the object around once you drag with the mouse.\nBasically everything except for the UI stays in \"Object Mode\".\n\nEffect On (broken):\n\n\nEffect Off (works as expected):\n\n\nBased on the default startup:\n1. Go to \"Particle Properties\"\n2. Add a particle system\n3. Set its type to \"Hair\"\n4. Add a second particle system\n5. Set its type to \"Hair\" too\n6. Add a new mesh e.g. \"Plane\"\n7. Go to \"Physics Properties\"\n8. Add \"Cloth\" physics\n9. Select the original \"Cube\" again\n10. Switch mode to \"Particle Edit\"\n\nWays to reverse the effect (make \"Particle Edit\" work properly again):\n- Either: Make a new file and append both objects of the old file\n- Or: Delete one of the particle systems on the \"Cube\" and undo the operation\n\nEven after reversing it you can restore the effect by selecting the \"Plane\" once.\nAt least two particle systems are required for the effect.\n\nThe effect can even be saved and stays the same after loading from the file again.\nThus I was able to create two files one with the effect and one without.\nThe file without the effect is a little bigger in size.\n\n[EffectOn.blend](EffectOn.blend)\n\n[EffectOff.blend](EffectOff.blend)\n\nIt took me a whole day to find the cause and boil it down so far.\nHope it helps and that it can be fixed with the provided info." ]

[ "Metaballs particles with drag force disapearing\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.33.01\n\nBroken: version: 2.83.2\nWorked: Never (2.8+)\n\nHi Guys,\n\nas you could see in the atachment file, the metaballs instances particles disapears on certains frames ...\nThere is no problem when Drag Force is not applied\n\nThanks in advance for your help !\nYour Software is amazing !! We love it !\n\n[MetaballsParticlesBug.blend](MetaballsParticlesBug.blend)\n\n- Open file\n- Play animation" ]

[ "Issues with HDRIs and render result pixel values that exceed half float limits\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n(Also tested in latest 3.3 Alpha)\n\nSome lookdev HDRI's give the scene a colored tint, that also does not disappear after lowering the strength\n\nI imported this HDRI to preview lighting in my Eevee scene: lenong_2\n\nAt first, this looks okay in blender:\n\n\nBut after lowering the strength, you will notice that there is a yellow light that should not be there, as well as a white spot from where the sun used to be, even if strength=0\n\n\nI found a workaround by adjusting the exposure of the HDRi in advance by -1 in affinity photo. This makes the image only a tiny bit darker, but the end result is as you would expect it.\nNo yellow light, no sun.\n\n\nI tried this with another HDRi from HDRIhaven (from another creator, this one specifically ehingen_hillside) and the issue also existed there. \n\nHere is the blend file for testing:\n[HDRI_Test.blend](HDRI_Test.blend)\nAnd the HDRI fixed by me\n[lenong_2_1k_fixed.hdr](lenong_2_1k_fixed.hdr)", "After updating the video card drivers to 20.11.2, interface artifacts appeared.\n{[F9329300](Снимок_экрана_2020-11-19_212921.png)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 590 Series ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.83.9\n\nMultiple artifacts can appear [see merged reports and see below]\n\n\n|  |||\n| -- | -- | -- |\n\nAfter updating the video card drivers to 20.11.2, interface artifacts appeared\nPossible workaround: downgrade GPU driver\n\nWe had more user state that enabling Render Properties > Performance > High Quality Normals avoids the drawing issues with Eevee.", "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", "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", "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", "Vertex paint + x-ray + polygon selection mode = weird shading\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\n\nFor me it looks like this\n\n\n\n[vertex paint x-ray strange shading.blend](vertex_paint_x-ray_strange_shading.blend)", "Cycles GPU CUDA rendering high number of points seems broken in LTS (main is fine, request for backport)\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.3.3\nWorked: latest 3.5 alpha\n\nRendering point \"clouds\" with Cycles - CUDA seems to make some chunks of points disapear randomly\nThis looks like this has been fixed in 3.5, but i didn't find when. Can this be fix in LTS ?\n\nDelete the default cube and add a plane\nAdd a Geonode Modifier on that plane\nDistribute Points on Faces > Density : 250'000\nSet Point Radius > 0.0025 (for convenience)\n \nSwitch to Cycles, GPU\nSwitch the render device to CUDA\n\nResults with :\n\n|  CPU |  CUDA |  OPTIX\n| -- | -- | -- |\n\n\n\nBug is visible in both viewport shading and Render.\n\n", "\"No Render\" volume of space with motion blur and GPU render\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.27\n\nBroken: version: 3.4.1\nWorked: N/A\n\nThere appears to be a volume of virtual space where objects do not render.\n\nLoad attached file. Set render frame to 110 and render the scene. Note the progress it makes as the large cube slowly vanishes with each render pass, while the smaller thin cube only partially renders. Set the frame to 50 and it renders fine. The problem starts with frame 106 and gets progressively worse for the large cube, while it seems to somewhat recover for the thin cube in later frames.\n\nThe problem does not repro with CPU rendering, and did not repro with my older graphics card way back when I first made this scene (GeForce 1080Ti). It repros with GPU rendering on both 3.4.1 and 3.1.0. It does not repro with motion blur disabled (hence the viewport render is also fine).\n[GPU Motion Blur Bug.blend](GPU_Motion_Blur_Bug.blend)\n", "Incorrect VRAM quantity in the Status Bar ( GNU/Linux AMDGPU )\nHello, first bug report :)\nA minor bug about the VRAM displayed in the status bar in my GNU/Linux AMDGPU system.\n\nOperating system: Linux-5.4.0-7642-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.35.0, 5.4.0-7642-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 2.90.1\nBroken: 2.91.0 alpha\nWorked: No\n\nDisplayed VRAM quantity in the status bar is wrong: 16 GB instead of 8 GB.\n\nIn a similar system enable the Video Monitor option to show the GPU usage in the status bar.\nUploaded an image and system info file:\n\n[system-info.txt](system-info.txt)", "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", "Blender performance under Linux is flakey ( on my system? )\nHi,\n\nI was hesitant to report this, because I don't really know if it is a bug or if something is wrong with my system, but I've tried almost every trick I know to get it working right and something is still not as it should be.\n\nWhen running Blender on Linux and doing some sculpting, the system begins to lag. It will take a couple of seconds for the cursor to keep up with the mouse and generally everything runs slowly. This is with a simple scene with one object and 600.000 faces, when trying to quit Blender it will hang for about two to three minutes pegging one CPU at 100%. Switch from object to sculpt mode also takes quite a while. \n\nWhen running the exact same file on my Windows installation ( dual boot ) everything is snappy and behaves like it should. On my Linux installation I have a VM that has a GPU passed through to it and that also works as it should ( same file ), this has made me startup the VM within Linux and use that for sculpting because it is much faster, which is a bit weird.\n\nAMD ThreadRipper 1950X\nAsrock Taichi \n32GB RAM\nGeforce 1080GTX TI\nGeforce 1080GTX\nnvme boot drive ( Windows and Linux each have their own drive, the VM resides on the Linux drive )\n\nWindows VM:\n6 cores\n8GB RAM\nVirtio harddisk\nAbove mentioned Geforce 1080GTX passed through using KVM,.\n\nSoftware:\nWindows 10 FCU ( VM )\nWindows 10 ( Dual boot )\nKUbuntu 17.10 Tried drivers: Nouveau, Nvidia 384, 390, 396.\nUbuntu 17.10 ( fresh install different drive )\n\nFor Linux I've tried kernels: 4.13 up to 4.14. \nOn Windows: Blender 279a both for the VM and the dualboot\nLinux: Blender 279a, 279b, the latest built of 279 of April 24 and Blender 280 also April 24. \n\nSculpting lags in Linux, Windows is fine on the same hardware.\n\nOn Linux just open the file, do some sculpting and it begins to lag, try to close Blender and one CPU will be pegged for 100% for about 4 minutes. On Windows sculpt some, everything is snappy close Blender without saving ( it prompts ) but closes immediately.\nI've included the file ( compressed with 7zip )[Dolphin.7z](Dolphin.7z)\n", "OSL on the GPU displays all black for Voronoi Distance > Bump Height\nSystem:\nWindows 11\nRTX3090Ti gpu\n\nBump output is pitch black when using Voronoi (Distance) output into Bump Height. Colorramp in between does not fix it. Noise output into Bump Height works fine.\n(Blender 3.5 in cycles)\n\nedit: more useful info + screenshot + isolated blend file\n\nRunning OSL on the CPU works fine, only the new GPU support seems affected.", "Intel GPU: switching between applications when in full screen mode causes glitches or screen flickering\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 530 Intel 4.5.0 - Build 30.0.101.1340\n\nBroken: version: 3.1.2\n\nWhen in Fullscreen, switching to other program and then returning to blender, glitch(black screen or something else) occurs suddenly and disappears.\nThis is not critical bug, but it would be good if it is fixed.\n\n\n- Open default blender file\n- {nav Window > Toggle Window full screen}\n- Switch to another application and again back to Blender", "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", "Bump node bump converges to different result than displacement bump\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\nUsing the same height map in combination with the bump node gives a different result than using the displacement node with bump only.\n\n\nWhen switching between the bump and displacement node one can notice a visible brightness difference in parts of the shape.\nWhat is perplexing however is that upon inspecting the normals used in rendering (switch render pass to normals), they are identical.\nSo the problem probably doesn't lie in how the shading normals are calculated but rather how cycles uses these.\n\n- Open attached file\n- Disconnect the displacement Map and connect the Bump Node to the `Principled BSFD` Node\nNotice the difference, (one receives less light)\n[test.blend](test.blend)\n\n\nThank you and have a great day!\n\n" ]

[ "Cycles GPU rendering produces a different result than CPU\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.3 26.20.13025.1004 (PowerColor 8GB)\n\nversion: 2.80 (sub 75)\n\nOpenCL Cycles GPU rendering produces a different result. There differences in reflections and lightness/darkness.\nSome tiles seem to be correct to the CPU result.\n\nRender the attached scene with CPU, then switch render slots and render with GPU to compare difference.\n\n\n\n\n\n[cycles GPU issue.blend](cycles_GPU_issue.blend)\n\nI am aware of a past issue on Mac OS that appears similar, but this is on Windows." ]

[ "GPencil: lines on surface quality difference between F12 and viewport render\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.83.0\nWorked: I don't think it ever worked\n\nThere's a difference in GPencil line quality between viewport render and F12. The GPencil lines are drawn on top of a 3d surface. The difference in quality seems to be the level of intersecting.\n\nBlend file has GPencil lines drawn over a 3d surface.\n1) render viewport in rendered viewport shading\n2) render with F12 and compare both renders\n[GP_on_3D_ViewportVsF12.blend](GP_on_3D_ViewportVsF12.blend)\n\n", "Alpha bug on Principaled BSDF with GPU\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA RTX A2000 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.92\n\nBroken: version: 3.2.1\n\nDecreasing alpha makes material black in the Principaled BSDF shader when using GPU compared to CPU \n\n\n\n - Decrease \"Alpha\" on the Principaled BSDF shader\n - Change to device to either \"GPU Compute\" or \"CPU\" \n - Adjust alpha value to discern difference if not apparent when switching Device property\n\n\n**Notes**\nCPU appears to work correctly with this value, it's only on GPU on my machine that causes alpha to make the material black. Bug appears in rendered images too and not just viewport, and is present in both CUDA and Optix. \n\nMake my alpha 0% if duplicate.\n\n[Blender GPU Alpha Bug.blend](Blender_GPU_Alpha_Bug.blend)", "Black render artifact with CPU+GPU rendering in viewport\nWindows 7 Pro\nNvidia Quadro P6000\nIntel Xeon E5-2690 v4\n\nBroken: daily builds 2.79 since at least 25.10.2017.\nWorked: -\n\nIf I enable combined CPU+GPU rendering, a black rectangle shows up on one of my objects. It shows up in viewport rendering, and also in the final render. This seems to be independent of the material used. I have provided a stripped down version of the scene where it is still visible. This time only in the viewport, the final render works for this simplified scene. \n\nThe artifact seems to be \"locked in space\", I can move or rotate the object away, so that it disappears. In some rotation angles it is not a black rectangle, but dense black lines. \nWhat is also interesting is that the surface of the object in not only black, but partly transparent. I have put a lamp and a cube inside the object in the demo scene, these should not be visible from outside, but they are.\n\n- Open file. In the render settings GPU compute should be turned on, and in the user preferences CUDA should have both the CPU and GPU selected.\n- Turn on viewport rendering. --> black box visible.\n- Then switch to CPU rendering. No more black box.\n\n[black_artifact_bug3.blend](black_artifact_bug3.blend)\n\n", "USD import: investigate texture color space conversion issue\n\n@brurpo Reported the following issue:\n\n> When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb.\n> Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space.\n> Is there a workaround for this, or is this planned?\n\n\nI'll be looking into this.\n\n\n", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "Cycles HIPRT device \n### Known Issues\n\n- [ ] The BVH builder doesn't efficiently handle degenerate triangles. For certain contents this might lead to performance slowdown or crash. We currently have a fix in HIP RT SDK to handle the crash, but the change is not yet part of our driver distribution.\n- [x] Soft shadow on hair doesn't look right in certain cases. This seems to be a regression. Images from previous test results of the same scenes look correct. We are working to find the regression point. \n- [x] Objects with motion blur are not rendered correctly. This is also a regression, and we have a rough idea of the change that broke motion blur.\n- [ ] Shadow linking not working (probably similar fixed as was needed for Metal #112012)\n- [ ] No Linux support\n\n### Background\n\nHIPRT enables hardware ray tracing on AMD cards utilizing HIPRT SDK. \n\nHIPRT SDK allows the developer to build the bvh on the GPU with different methods and trade-offs. It also allows for user defined primitives and intersection. The device side of the SDK provides traversal functions. In order to compile the kernels using traversal, the kernels must be compiled through the runtime compiler function that HIPRT SDK supplies. \n\nHIPRTDevice and HIPRTDeviceQueue, derived from HIP, implement new functions or override existing functions to enable HIP ray tracing on the host. side.\n", "Normal Baking Inconsistence\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.0 Alpha\nWorked: unknown\n\nNormal baking result is different from original.\nAs below, a texture is baked to be used as normal map. Using \"Normal\" bake type the result is inconsistent with the original normal. A baking result using \"Emit\" type is used for comparison.\n\nDiffuse shader :\n[Correct (Diffuse).mp4](Correct__Diffuse_.mp4)\n[Incorrect (Diffuse).mp4](Incorrect__Diffuse_.mp4)\n\"Emit\" bake type has identical result to the original one, while \"Normal\" bake type has a little dimmer color.\n\nGlossy shader :\n[Correct (Glossy).mp4](Correct__Glossy_.mp4)\n[Incorrect (Glossy).mp4](Incorrect__Glossy_.mp4)\nDue to image resolution, the result of \"Emit\" type has acceptable differences at the edges of the squares. The result of \"Normal\" type has areas that shouldn't be brighter/dimmer (check from multiple view angles in the file below).\n\n[Bug Report.7z](Bug_Report.7z)\n\n\n - This is the node setup to generate the texture : \nThese nodes simulate the kind of texture that will connect into \"Normal Map\" node so that it can also be baked using \"Emit\" type.\n\n\n\n - Use the \"Material Output\" nodes to view the differences : \n\n\n\n - If re-bake, use 16-bit color depth can help to get the similar result from original nodes.", "Overlapping objects of different sizes with volumetric materials render incorrectly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.83.4\nWorked: 2.82a\n\n\nTwo cubes, both principled volume, one large one small, smaller cube inside larger cube. \n\nThe area inside the smaller cube from the view perspective renders differently than outside with a hard edge where the mesh ends, the effect is much easier to see with a texture controlling the volume density of the large cube. Looks to me like an issue with blender using different step sizes for different objects. Definitely not an issue with not enough transparency/volume light bounces, already tried that.\n\nOnly happens with cycles\n\nOpen blend file\nSwitch to rendered view\nToggle visibility of big volume and/or small volume in outliner to see difference\nExtra notes in shader nodes for big volume and small volume's materials\n\n[overlapping volumes hard edge bug.blend](overlapping_volumes_hard_edge_bug.blend)", "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", "Light of 'Area' type lamp presents artifacts when placed at great distances\nOperating system: macOS-13.4.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: versions: 3.1 to 4.0a \n\nArtefact's appearing with bigger Arean Light distances and spread angle 0.1 to 20~ \n(Like for space scenes with bigger distance Area lights for better sun effects...)\n\nJust open one of the files or follow the image below to set up the light.\n\n", "Baked Normal Map Is Not Equal To The Original Normal Map.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.Q4.221025\n\nBroken: version: 2.93.2\n\nThe problem that after I bake the normal it appears different than the original\n,Is this a bug ? , and why it appears different .\n\n1. Open blender\n2. Go to the shading window\n3. Select The cube \n4. Add normal map image connect it to the normal map after you add it , Then to the BSDF node \n5. create image to bake to it and select it \n6. bake the normal and see the result\n\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", "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", "Cycles: GPU Performance\n**Memory usage**\n\n- [x] Auto detect good integrator state size depending on GPU (hardcoded to 1 million now)\n- [ ] Reduce size of IntegratorState\n - [x] Don't store float4 as float3\n - [x] Don't allocate memory for unused features (volumes, sss, denoising, light passes)\n - [x] Dynamic volume stack size depending on scene contents ([D12925](D12925))\n - [ ] Overlap SSS parameters with other memory\n - [ ] Compress some floats as half float\n - [ ] Reduce bits for integers where possible\n - [ ] Can diffuse/glossy/transmission bounces be limited to 255?\n\n- [ ] SoA\n - [ ] Individual arrays for XYZ components of float3?\n - [ ] Pack together 8bit/16bit values into 32bit?\n\n- [ ] Reduce size of ShaderData\n - [ ] Compute some differentials on the fly?\n - [ ] Read some data directly from ray/intersection?\n - [x] Don't copy matrix if motion blur is disabled\n\n- [ ] Reduce kernel local memory\n - [ ] Dynamically allocate closures based on used shaders\n - [ ] Dynamically allocate SVM stack based on used shaders\n - [ ] Check if SVM stack is allocated multiple times\n - [ ] Check on deduplicating ShaderData instances\n - [ ] Check for other unknown sources of memory usage\n - [x] Use either `shade_surface` or `shade_surface_raytrace` for reserving memory\n\n**Kernel Size**\n\n- [x] Replace megakernel used for last few samples? Only helps about 10% with viewport render, barely with batch render. But makes OptiX runtime compilation slow.\n- [x] Make `svm_eval_nodes` a templated function and specialize it for\n - [x] Background\n - [x] Lights\n - [x] Shadows\n - [x] Shader-raytracing\n - [x] Volumes\n- [x] Avoid shader ray-tracing for AO pass ([D12900](D12900))\n- [x] Verify if more specialization is possible in `svm_eval_nodes` (seems not)\n- [ ] Deduplicate shader evaluation call in `shade_background`\n\n**Scheduling**\n\n- [x] Make shadow paths fully independent so they do not block main path kernels ([D12889](D12889))\n- [x] Accurately count number of available paths for scheduling additional work tiles\n- [x] Compact shadow paths similar to main paths ([D12944](D12944))\n- [x] Consider adding scrambling distance in advanced options ([D12318](D12318))\n- [x] Compact path states for coherence\n- [ ] Tweak tile size for better coherence\n- [ ] Tweak work tiles or pixel order to improve coherence (many small tiles, Z-order, ..)\n- [ ] Try other shader sorting techniques (but will be more expensive than bucket sort)\n - [ ] Take into account object ID\n - [ ] Take into account random number for BSDF/BSSRDF selection?\n- [ ] Overlapped kernel execution\n - [ ] Use multiple independent GPU queueus? (so far was found to be 15% slower)\n - [ ] Use multiple GPU queues to schedule different kernels?\n- [ ] Optimize active index, sorting and prefix sum kernels\n - [ ] Parallelize prefix_sum\n - [ ] Build active/sorted index array for specific based on another array indicating active paths for all kernels, especially when number of paths is small\n- [ ] Try pushing (part of) integrator state in queues rather than persistent location, for more coherent memory access\n - [ ] Check potential performance benefit by coalescing state\n - [ ] Shadow paths\n - [ ] Main path\n- [ ] Cancelling renders and updates can be slow due to the occupancy heuristic that schedules more samples. Find a way to reduce this problem.\n- [ ] Shader sorting and locality balancing ([D15331](D15331))\n - [ ] Find better heuristics for scenes with many shaders\n - [x] Use for GPU devices other than Metal\n- [ ] Shader sorting by node graph similarity, to find coherence if e.g. the graph only has different image textures\n\n**Display**\n\n- [x] For final render, let Cycles draw the image instead of copying pixels to Blender\n - [x] Render pass support\n\n**Render Algorithms**\n\n- [x] Use native OptiX curve primitive for thick hair\n- [x] Transparent shadows: can we terminate OptiX rays earlier when enough hits are found? ([D12524](D12524))\n- [x] Transparent shadows: tune max hits for performance / memory usage\n- [ ] Detect constant transparent shadows for triangles and avoid recording intersection and evaluating shader entirely\n- [ ] Detect transparent shadows that are purely an image texture lookup and perform it in the hit kernel\n- [ ] For volume stack init, implement volume all intersection that writes directly into the stack\n\n**Tuning**\n\n- [ ] Automatically increase integrator state size depending on available memory\n- [ ] Tweak kernel compilation parameters (num threads per block, max registers)\n - [ ] Different parameters per kernel?", "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" ]

[ "GPU+CPU Strange results\nOperating system: Windows 7 x64\nGraphics card: Radeon Pro Duo Polaris\nCPUs: Xeon E5 2660 v3 (Dual Socket)\n\nBroken: 2.80 Official\nWorked: (optional)\n\nWhen rendering project night rendering with cpu+gpu, the gpu renders brighter than cpu. Also, rendering results between gpu and cpu standalone give different results as well. gpu is brighter. Probably user error. If this is too much to look at, I understand.\n\n\nOpen attached file and render. Scene is set up to go. Sorry, not simple file. Because I do not know what is the issue. The anomaly is most noticeable on the image on the right hand side of the rendering.\n\nAttached are some images that show what is happening on my end. Plus a finished GPU only rendered result.\n\n\n\n[CPU_GPU_Problem.zip](CPU_GPU_Problem.zip)\n\n\n\n\n\n\n\n\n\n\n\n" ]

[ "Grease Pencil problem (especially soft pencil) \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n\nSince couple version of Blender I cannot use a soft pencil (mainly) brush in Grease Pencil 2D animation mode. The issue depends on how much You zoom. When You zoom in and use same size it's not visible. When You zoom out and draw with same size dots are visible. \nIt's behavior is very strange now and produces bad results (visible dotted lines or other which are visible on attached file. Some of these issues occur when the brush is small (line type set as dots). This is much more more visible when stroke stabilization is on. The bug was not there about 2 years ago and I was able to use the soft pencil without such problems. When line type is set to line the pencil stroke has strange contour around and when self overlap is off it produces artifacts on edges. \n\n\n\nJust choose a soft pencil and make it small. Check it with stroke stabilization as well. Then change the line type to line with self overlap on and off. \n\n", "GP transparent layer doesn't blend with background object \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\nI have a foreground grease pencil object, and a background grease pencil object (yellow blob).\nThe foreground object contains a layer set to 0 opacity.\nWhere this layer overlaps the background object in the viewport, the background object is invisible.\nExpected behaviour: the visibility of the background grease pencil object isn't affected by transparent layers in a foreground object.\n\n\n\n\n\n[#89286.blend](T89286.blend)\n\nForeground object \"makes hole\" in background, doesn't blend. Rotate viewport camera, suddenly it blends correctly.\nWhen foreground location is set to 0,0,0 it blends correctly too.", "Grease Pencil: Eraser Brush ends on maximum radius\nOperating system: Linux-5.4.0-89-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.1.0 Alpha\nWorked: never\n\nWhen using the eraser brush in draw mode of grease pencil objects you can notice that when you stop your stroke, the brush radius will end on the maximum radius.\nThis has the effect of users erasing something carefully when using pressure sensitivity for the radius, but then erasing everything within the max radius anyway once they end the stroke.\n\nThis effect is most noticeable if you use the \"Eraser Point\" brush in the eraser tool with \"Use Pressure\" enabled.\n\n", "Workspace tabs click-dragging only works when starting from current tab.\nSystem Information\nOperating system: Windows 10\nGraphics card: Geforce GTX 1070\n\nBlender Version\nBroken: 2.80 2019-02-20 20:10\n\nShort description of error\nClick-dragging on tabs works fine in the Preference's tabs now, but fails to work on the Workspace tabs *unless*you start from the current one (so to rephrase, for clarity: if you start on one that's not the currently selected one, it will simply not go through the tabs)\n\n- Create workspace (either duplicate or append) so there's more than one\n- Click on one of the workspaces that isn't currently displayed\n- Drag left and right, you'll notice nothing happens.\n- Click on the currently selected workspace's tab\n- drag left and right: this should switch between workspaces as you pass over their tabs", "Geometry Nodes: writing attributes (from procedurally created geometry) to vertex groups not working\nOperating system: macOS Monterey 12.4\nGraphics card: RX 6800 XT\n\nBroken: 3.1 & newer\nWorked: 3.0.1\n\n\nIn Blender 3.0.1, it was possible to write attributes from procedurally created geometry (created by geometry nodes) to vertex groups, as long as the \"Group Input\" node was joined with the procedural geometry. However, no version newer than 3.0.1 seems to have this capability. From what I understand, this may have been done intentionally in anticipation of attributes replacing vertex groups entirely... but it seems odd to kill this feature before that transition is complete, so I'm reporting this as a bug.\n\n\nOpen the attached .blend file in Blender 3.0.1:\n[geonodes_attrib_to_vgroup.blend](geonodes_attrib_to_vgroup.blend)\nThis file contains a geonodes setup where half of a procedurally generated grid is extruded using a solidify modifier. The \"geonodes\" object should look exactly the same as the \"Expected Result\" object. \n\nNext, open the file in Blender 3.3 (or 3.1, or 3.2) and notice how the \"Expected Result\" object no longer matches the \"geonodes\" object.\n", "GP kills bloom\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: 3.6.3 Release Candidate\nWorked: \n\nWhen you have mesh objects emitting in front of grease pencil objects, bloom doesn't work there.\n\n\n", "Line art modifier clips with object on (MBP 16\")\nOperating system: macOS Big Sur\nGraphics card: 5500M \n\nBroken: 2.93.0 LTS\nWorked: -\n\nLine art modifier (grease pencil) seems to clip into / z-fighting the object. \n\n\nJust add a new line art modifier, possibly a mac problem?\n\nTest File:\n[line_sample.blend](line_sample.blend)", "Grease Pencil Proportional Edit \"Connected Only\" fails to delimit unconnected strokes if they are selected\nVersion 2.80 rc3 (Linux 54)\n\n[GP_proportional_edit_bug.blend](GP_proportional_edit_bug.blend)\n\nHow to reproduce:\n\n - Open attached file, remain in edit mode.\n - Note the proportional edit settings and selected stroke vertices.\n # Move around the whole blue stroke, along with one vertex at the tip of the black stroke.\n\nObserve how the black stroke is affected by the selected vertices of the blue stroke, even though the two strokes are not connected and are on different layers. This is not the expected behavior of the \"Connected Only\" setting. The strokes should only be affected by their own vertices, but as long as any vertex of either stroke is selected, they will affect each other as though the \"Connected Only\" setting is ignored!", "Grease Pencil is lit by World's Viewport Display Color, not by the actual World Color\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.93.0\n\nGrease Pencil Objects change their color in Rendered Viewport Shading Mode and on the final render according to World's Viewport Display Color, not by actual World's Surface Color.\n\nOpen a new scene.\nDelete the cube and light.\nAdd Grease Pencil Monkey object.\nSwitch shading mode to \"Rendered\".\nIn the \"Properties\" area find \"World Properties\" and expand \"Viewport Display\" settings.\nPlay with the color value. In the viewport you'll see Monkey changing color according to your experiments.\nBlack color will bring drawing to complete hopeless darkness.\nTry to render the image with tinted monkey in frame. You'll see the effect takes it's place on render as well.\nNow play with World's Surface color. It doesn't do anything.", "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", "Decentralize .blend I/O for grease pencil modifiers.\nThis is a follow up task for #76372.\n\nFor normal modifiers this has been done already. Have a look at `ModifierTypeInfo.blendWrite` and `ModifierTypeInfo.blendRead` for more details.", "Grease Pencil: Visual glitches in viewport when using guides \nOperating system: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.82a\n\n\nWhen using one of the guides that enable the drawing of straight lines, visual glitches in the viewport appear.\n\n\n - Open Blender with the 2D Animation template\n - Enable Guides\n - Use \"Parallel\" guides\n - Start drawing a horizontal line -> move the cursor perpendicular to the tip of the stroke (up or down; not too fast)\n\n\n\n\n\n", "Grease Pencil drawing only show up when pen is lifted from tablet\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800S ATI Technologies Inc. 4.5.14802 Core Profile Context 21.40.64.30 30.0.14064.30001\n\nBroken: version: 3.6.1\n\n\nGrease Pencil is not the same as before. When I press down to draw something with the pen, it won't show up- until after I lift my pen up from the tablet and then it shows what I drew. This is bad because I can't draw if I can't see what mark I made. It only shows up after and ruins the workflow.\n\n\nI open up Blender, the updated version: 3.6.1. I click: 2d animation to start. Then I click pen as my grease pencil drawing tool. I draw something on the canvas. I press down to draw a shape. Nothing shows up as I press down on the canvas. I lift my pen off the tablet and then I see what I 'drew'. A horrible squiggle line because I cannot see what I'm drawing as I'm drawing. I did not have this problem with the past version of blender that I had: Blender 3.3.1. \n\n~Karina\n\n", "Snapping: Make 'Absolute Grid Snapping' a new Snap Mode\nHaving `Absolute Grid Snapping` as an option for `Increment` does not seem ideal.\n\nIncremental Snapping means to snap to values that increment the current position.\n\nGrid Snapping means snap to grid.\n\nHaving `Grid Snapping` as an option also limits its use because `Increment` does not use a pivot or base point for transformation.", "Grease Pencil: Add eyedropper to palette popup\nInspired by this [idea]() by gakutada.\n\n## The Issue\nThe color picker popup in Grease Pencil is missing the eyedropper button:\n\n\nThat is present in regular color pickers:\n\n\nEven though holding the `E` key with the mouse over the color swatch works fine:\n<video src=\"attachment\" title=\"gpencil_palette_colorpicker.mp4\" controls></video>\n\n## The Solution\n\nAdd the operator to the popup. Aligned to the right-side so it's similar to the regular color popup.\n\n\n" ]

[ "Snap support for Grease Pencil objects\n**Description**\n**Big picture:** Make it possible for the snap options: `Vertices, Edges and Face`, to work on Grease Pencil objects\n\n**Use cases**:\n* Precisely positioning a Grease Pencil object on a Mesh in the 3DView\n* More flexibility in positioning the 3D Cursor\n\n**Design:**\n* Will work in conjunction with 3DView's snap system (no new interface required)\n\n**Engineer plan:**\n* Since Grease Pencil objects can be 3D, a BVHTree system may have to be implemented to snap to faces and occlusion test.\n* Another option is to work with a depth buffer." ]

[ "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Fractured object crashes Render\nOperating system: macOS-13.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.10.12\n\nBroken: version: 3.4.1\n\nRendering image crashes Blender\n\nThe attached file is the output of a fractured cube using RBDLabs, nothing else. It's a series of 965 simple static meshes. When displaying rendered shading in viewport, all is well. When doing Render > Render Image, then Blender crashes. Happens on my Mac M1 and Mac Intel, on Blender 3.3.4, 3.4.1, 3.5 and 3.6 alpha. If I delete the 115 last cells or the 134 first ones, then the render will properly happen. Thanks !\n\n", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)", "Blender crashes when using temp_override on 'UV' area with transform.translate, transform.resize\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.3.5\nBroken: version: 3.4.1\nBroken: version: 3.5.0\nWorked: none\n\nWhen executing `transform.resize` or `transform.translate` with `context.temp_override(area=uv_area)` Blender crashes. This happens when the area.ui_type is UV, with VIEW_3D is works fine.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF72DEF3C80\nModule : blender.exe\nThread : 000009dc\n```\nthe complete crash file is attached\n\n1. create a new Text and paste the below code into the text (the attached file issue.blend can also be used)\n```py\nimport bpy \ncontext = bpy.context\narea = context.area\narea.ui_type = \"UV\"\nwith context.temp_override(area=area):\n bpy.ops.transform.resize(value=(0.5, 0.5, 0.5), orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n bpy.ops.transform.translate(value=(0.25, -0.25, 0), orient_axis_ortho='X', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n```\n2. run this text, Blender will now crash\n\n**Note**: not using `temp_override()` and executing these operators in the current context with the ui_type set to UV works fine. Like this: \n```py\nimport bpy \ncontext = bpy.context\narea = context.area\narea.ui_type = \"UV\"\nbpy.ops.transform.resize(value=(0.5, 0.5, 0.5), orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\nbpy.ops.transform.translate(value=(0.25, -0.25, 0), orient_axis_ortho='X', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n```\n\n", "Crash on applying boolean modifier\nOperating system: Linux Fedora V35\nGraphics card: Nvidia 3070TI\n\nBlender 3.1.2 and Blender 3.2.0 both crash\n\nI created a mesh object, then used boolean modifier to create a hollow center. I applied the modifier. When I go into edit to clean it up, it crashes.\n\napply the boolean modifier to the mesh \"Bottom\" with object \"Plug\" in the included blend file using all defaults. Enter edit mode and see the mesh is badly corrupted.\n\n[part7.blend](part7.blend)\n[printReady1.blend](printReady1.blend)", "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", "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", "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", "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", "Hard crash while resizing packed multichannel EXR\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nWorked: unknown\n\nTrying to resize this particular image crashes blender instantly. There's 2 unusual things about the image, not sure if they're relevant\n\n\n - it's a packed multichannel EXR\n - it has some very large values (it's an SDF, so some values are like 9999) \n\n\n\n # Load the file\n[image_resize_crash_004.blend](image_resize_crash_004.blend)\n - Resize the image\n - Crash!\n```\n\n```\nSee video:\n\n[Blender image resize crash 2022-12-08 15-41-15.mp4](Blender_image_resize_crash_2022-12-08_15-41-15.mp4)\n\n\n", "Crash on deleting driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken: (\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\n)\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. I don't know where that driver on Location X came from. The original didn't have one. I then wanted to delete that driver. After deleting it and moving the current frame blender crashed.\n\n- Load attached file\n- Delete driver of 'Location X'\n- Press Cursor keys Left/Right a few times till crash.\n[crash.blend](crash.blend)", "Region overlap crashes when interacting with action zones\nEnable region overlap user preference.\n\nIn the default 3D viewport, press NKey, then drag on the corner widget. -> Blender crashes.\n\nAttached asan output: [region_overlap_azone.txt](region_overlap_azone.txt), [region_overlap_azone_2020_01_28_update.txt](region_overlap_azone_2020_01_28_update.txt) (found while investigating #46764).\n\nUpdated asan output\n\n\n----\n\nNote: Blender internals aren't well suited of handling regions being manipulated like this while the rest of Blender is being used. We could either prevent interaction during the fade, or disable it since its not really needed.", "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.", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n" ]

[ "Created Vertex > Edit Mode > Subdivision Surface > On Cage = Blender Crash\nOperating system: Windows-11 22000.675 21H2 64 Bit\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e369187, type: release\nWorked: 3.2.0\n\nI'm studying blender and trying to learn it. Then when I press On Cage in Blender 3D, Blender 3D will crash by itself. I has been to uploaded the video and .blend files to reproduce this bug for developer.\n\nIn video reproduce steps and .blend files is here:\n[2022-06-14 14-57-47.mp4](2022-06-14_14-57-47.mp4)\n[modifiercrash.blend](modifiercrash.blend)", "Blender Crashes on turning on \"On Cage\" on subdivision surface modifier (Intermittent)\nOperating system: Windows 10\nGraphics card: Nvidia Geforce 2060 6Gb\n\nBroken: 3.2\nWorked: 3.0\n\nWhen turning on the On Cage option with only vertex's and no mesh it used to not be an issue, This now crashes blender. \n[Roadster18.blend](Roadster18.blend)\n\n[Video of reproduction steps ](722224899)", "subdivion modifier crash on cage mode (EDIT MODE)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0\n\n\n\n----------------------\n1. create circle\n2. edit mode\n3. add subdivision surface\n4. turn on ON CAGE\n# crash\n[crash_EDITMODE ONCAGE.blend](crash_EDITMODE_ONCAGE.blend)\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", "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.", "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", "Area light resize gizmo (amongst other gizmos) missing undo step?\nOperating system: Arch Linux\nGraphics card: GTX Titan\n\nBroken: 2.81.3 (232049dd9408)\n\n\nSeems an area light resize in the 3D view is not registered with the undo system. \n\n\n1. Add an area light to the scene\n2. Grab and move somewhere else\n3. Change size with widget\n4. Ctrl-Z\n5. The light is now back at the origin with the default size\n\nNote that when changing the size using the properties panel an undo *will* work correctly, i.e. only change back the size.\n\nThis seems true for a couple of Gizmos [not adding an undo step -- or at least not working correctly / as expected]\nThese are the ones I quickly checked:\n- Camera Focal Length\n- Area Light size\n- Spot Size\n- Wind Force Field Strength\n- Reference Image size\n- Compositor Backdrop\n- Reference image size and move\n", "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", "Randomize Transform + Affect Only Origins, not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nRandomize Transform not working as expected with Affect Only = origin. Whole object is transformed rather than just origin.\n\nin the 3d view port go Options > Affect Only and tick Origins\nselect default cube\nTransform the cube using Object>Transform>Randomize Transform\n\nCube moves/rotates/scales when I'd expect only the origin to be affected\n\n", "Click-and-Drag the Cursor with Snapping enabled and an Active Object selected missplaces the Cursor\nOperating system: Linux-5.2.9-125.current-x86_64-with-glibc2.9 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\nWorked: None so far\n\n\nDragging the cursor and snapping it to a Vertex while having the Target set to Active makes the cursor snap to a point in space that is directly related to where you start your *click-and-drag* instruction in reference to the selected object's origin. \n\n1) Change snapping to Vertex, Edge or Face\n2) Change snapping target to Active\n3) Set active tool to Cursor\n4) Activate snapping during transform\n5) Select default cube\n6) Drag Cursor over cube\n\n**Important notes**\n\n- If you deselect everything it works, but while there's an object selected the snapping won't work.\n\n- The problem also happens in Edit Mode, but only if there's an object selected in Object Mode. If you deselect everything in Object Mode and then go back to Edit Mode it works as intended.\n\n- As far as I can tell the _offset_ of the snapping is directly related to where you start your click-and-drag in regards to the Objects Origin.\n\n- There's a BlenderArtist Topic in which some have tested the behavior in Blender 2.81: 1177897\n\n- I recorded a video showing the problem: [blender_bug_report_complete.mkv](blender_bug_report_complete.mkv)\n\n- I also uploaded the blend file I used to record the video: [bug_report_cursor_snapping.blend](bug_report_cursor_snapping.blend)", "Autosmooth + Custom Normals is slow\nOperating system: Windows 10\nGraphics card: Nvidia mx230\n\nBroken:\nmaster\n\n\nUsing autosmooth and custom normals at the same time is slow, even in situations where you wouldn't\nexpect normal calculation to happen (like moving an object in object mode).\n\n\n[normal_autosmooth_slow.blend](normal_autosmooth_slow.blend)\n\n - Load the .blend file. Move the object around, it should be slow. \n - Either disable autosmooth, or clear custom split normals.\n # Moving the object should now be a lot faster\n\n", "Slower frame-change with many objects in the scenes collection\nWhen objects are in the scenes collection (instead of a sub-collection), changing frames using left/right keys is slower.\n\nThere is also a slowdown when animation playback restarts.\n\nThis occurs in 3.5x `ab63fe9eab8fd01d4a763199442987191d105c55` and 3.4x release.\n\nTo reproduce the problem:\n\n- With a new file paste the script inlined at the bottom of the report into a text editor and run it.\n- Press Spacebar in the 3D viewport to play back animation.\n- Note the FPS (~13.1 FPS here).\n\n- Start again, doing the previous steps with `USE_SCENE_COLLECTION = True` in the script.\n- Note the FPS is much lower (~3.46 FPS here).\n\n---\n\n#### Explanation\n\n- This is an issue I ran into when investigating why objects in collections were being re-populated during animation playback in some files, see !104553.\n- The cause of the problem is the scene is tagged by the depsgraph (see: `ANIMPLAY_FLAG_JUMPED`). _(note: the jumped flag is set when changing frame via arrow keys & when the animation restarts)._\n- When `ANIMPLAY_FLAG_JUMPED` is set `scene` is tagged with `ID_RECALC_FRAME_CHANGE`.\n- This causes the scene to be copied (see `blender::deg::deg_update_copy_on_write_datablock`).\n- The `scene->master_collection` is copied (non recursively).\n\n - When `scene->master_collection` contains many objects, copying has a noticeable performance penalty.\n - When it only contains some collections, the problem isn't noticeable.\n\n#### Other Notes\n\n- This is mainly noticeable when loading files pre 2.8x which load objects directly into `scene->master_collection`.\n- This report mentions animation playback speed because it's easily measurable, however many other operations trigger this (left/right arrow keys to change frames, every update when dragging scene number buttons \"Sampling\" (Render or Viewport) for e.g.).\n- In the test script the start and end frames are the same to so the playback is continually restarting to accentuate the problem and match the slowdown from changing frames via arrow keys.\n\n---\n\nThis script adds many objects to the factory settings file, hides them, adds some keyframes to the Light and sets the 3D viewport full-screen, ready for animation playback.\n\n\n```python\nimport bpy\n\nUSE_SCENE_COLLECTION = False\nOBJECT_NUMBER = 20_000\n\ndef objects_create(object_num):\n objects = []\n new = bpy.data.objects.new\n for i in range(object_num):\n objects.append(new(hex(i), None))\n return objects\n\n\ndef objects_collection_link(collection, objects):\n link = collection.objects.link\n for ob in objects:\n link(ob)\n\n\ndef main():\n from bpy import context\n\n bpy.ops.wm.read_homefile(use_factory_startup=True)\n\n if USE_SCENE_COLLECTION:\n collection = context.scene.collection\n else:\n collection = context.collection\n\n # Keyframe the lamps location, this is important as without this\n # the scene is not considered \"animated\".\n ob_lamp = bpy.data.objects[\"Light\"]\n ob_lamp.keyframe_insert(\"location\", frame=1)\n\n # The short frame range shows the problem most,\n # as this tags the scene to be tagged to update on frame-change.\n context.scene.frame_start = 1\n context.scene.frame_end = 1\n \n # Attempt max FPS.\n context.scene.render.fps = 1000\n\n objects = objects_create(OBJECT_NUMBER)\n objects_collection_link(collection, objects)\n \n # Hide everything, except the lamp.\n bpy.ops.object.select_all(action='SELECT')\n window = bpy.data.window_managers[0].windows[0]\n area = next(area for area in window.screen.areas if area.type == 'VIEW_3D')\n \n # Hide needs an 3D viewport (but select doesn't, hrm..).\n with context.temp_override(window=window, area=area):\n bpy.ops.object.hide_view_set(unselected=False)\n ob_lamp.hide_set(False)\n \n # Fullscreen 3D view (rule out slowdown from drawing other areas).\n with context.temp_override(window=window, area=area):\n bpy.ops.screen.screen_full_area()\n \n\nif __name__ == \"__main__\":\n main()\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)", " Elastic deform brush won't work with lower scene unit scale.\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 14)\n\n Elastic deform brush won't work with lower scene unit scale.\n\n*Set scene units to Metric, scale to 0.01m\n*Scale the cube by 100 to compensate, apply all transforms\n*Enter sculpt mode\n*Use the elastic transform brush with the options **Grab, Twist or Scale**, the others appear to work", "Gizmos do not appear when editing normals via the rotate or point to target functions\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 24.20.100.6292\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nWhen editing normals using the \"rotate\" or \"point to target\" options in the Alt-N normal menu, no gizmo appears to control these functions using the mouse. This behavior isn't consistent with the behavior [shown in this video ](Rqsgrg_SVME?t=123).\n\n\n # Open new \"General\" file\n\n # (Optional: Enable normal visualization gizmos)\n\n # Select cube and go into edit mode\n\n # Select a face and open the Alt-N normal editing menu\n\n # Choose the \"rotate\" or \"look at target\" options\n\n - Gizmo for mouse does not appear\n", "Child object rotates after parenting with 'Keep Transform Without Inverse'\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83.1\n\nBroken: version: 3.6.0\nWorked: introduced with 'Keep Transform Without Inverse' in 3.2\n\nAfter parenting with 'Keep Transform Without Inverse' the child object is slightly rotated and even the location can be off in relation to the parent object.\nPlease see the attached video and the blend file.\n\nNote, that the scene units in the blend file are set to centimetres. Working with smaller units pronounces the effect of the location values. But for the rotation the scene units have no effect.\n\nThe problem seems to be related to rounding errors in the transform matrix multiplication code.\n\nOther observations:\n\n- There is no rotation when the object gets parented with 'Keep Transform' (but this way the transformation values don't represent the relative values to the parent object)\n- When the object is parented with 'Keep Transform' and then 'Clear Parent Inverse' is executed the unwanted rotation will appear.\n- The larger the Euler rotation of the parent object is the more dramatic the location values appear distorted (as in the sample blend file).\n- Using Quaternion rotation doesn't yield as extreme results since the individual quaternion values cannot be set as high as when using Euler angles.\n- The same effect can be observed when parenting the object to a bone.\n- When trying to replicate the issue in other 3D Applications the parenting does not produce unwanted rotations or faulty relative positional values in relation to the parent object.\n\nThe problem is not directly noticable, other than fractional values are introduced to the rotation as well as the location. But when the object is large the far-away edges will get shifted in a more visible way.\n\nParent an object to another which has rotation values. The resulting offset is small and therefore is only pronounced when zooming in at a larger distance from the origin.\n\n", "Skewed Rotation Bug - Using snap invert with align rotation on skews the rotation of the Mesh\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.73\n\nBroken: version: 3.1.2\n\nWith align rotation enabled from the snapping menu, snapping an object to another using *snap invert (pressing the ctrl button)* works normally until you move your cursor before clicking ctrl to snap. In other words, moving your mouse cursor and snapping skews the rotation for the next time you try to snap again. In the steps below, I'll be snapping to *face* with *median* selected, but the bug is also there with *edge mode*, and even *center* and *active*.\n\n* From the snapping menu, select *Face mode*, and choose to snap with the *median*, and only turn on *align rotation.* Do not turn on *snap during transform (the magnet)*, we will use *ctrl* to snap onto the mesh using *snap invert.*\n* Do not delete the default cube. Instead, create a cylinder, and move it away from the cube, and scale it down. We will be snapping the cylinder onto one of the cube's faces to demonstrate this bug, so you can enter side view if you'd like.\n* Click the cylinder, and enter *edit mode.* Press 'A' to select all vertices. Click 'G' to enter Transform mode, and try not to move your cursor.\n* Click ctrl to snap the cylinder onto the cube using *snap invert*. Next, click the RMB to cancel the transformation.\n* Click 'G' to enter Transform mode again. Next, move your cursor a notable distance to the side of the cube's face. Click ctrl to snap the cylinder onto the cube's face. Again, click the RMB to cancel the transformation.\n* Finally, click 'G' again, and click ctrl to snap the cylinder onto the cube's face, and notice that the rotation has been skewed.\n* (Bonus info, not needed) To return to your original snap rotation, you have to cancel the transformation and enter it again to snap, even multiple times. \n\n1) Here's a screenshot of the skewed rotation\n\n\n2) Since this is a bit more difficult to reproduce, I have provided a video on how to exactly reproduce this bug: [Video](xw4vYG9MOIA)\n\n3) Finally, here's the blend file:\n[Skewed_rotation_bug.blend](Skewed_rotation_bug.blend)\n\nP.S. I would also appreciate it if you can mention how align rotation works in edit mode.\n\nThank you so much for you work. Very much appreciated!!", "Regression: Visual bug when using the object gizmos\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\nCaused by 917a972b56\n\nDifferently from using the transform tools in the toolbar, when activating the object gizmos that stay visible also with the select tools, a strange bug occurs that the e.g. moving the object on an axis keeps a grey axis where it was before, the gizmo is always present (differently again from using the transform tools), and if you switch from this to the transform tools to the selection with gizmo again, it messes the origin of the object.\n[2021-09-20 14-59-52.mp4](2021-09-20_14-59-52.mp4)\n\n\nI'm pretty sure that this is caused by the recent change of keeping the viewport gizmo visible when doing these operations.\n\nUse the select tool in the toolbar, activate on or more object gizmos that stay always visible, do a transform operation.\n[Based on the default startup]\n\n" ]

[ "Slow Response Rotation Gizmo in edit mode\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nTrackball with 512 dpi - 2048 dpi, Logitech MX ERGO.\n380 x 2160 resolution monitor.\n\nBroken: version: 3.1.1 Release Candidate\n\nThe response from the rotation gizmo is slow, the problem is present in any mesh for this we use the simplest mesh (cube) the problem is in the 3.1 and 3,1.1 RC. In the version 3.0.1 the response is immediate. Another gizmos are not affected. \n|[blender1.mov](blender1.mov)\n| -- |\n\nApparently related to #96435 (Regression: very long input delay when dragging some gizmos handles in macOS)\n\nIn a black file.\n1.- Add a cube. \n2.- Edit mode, vertex mode.\n3.- Select rotation gizmo and select the complete mesh.\n4.- Rotate the mesh using the gizmo, the response is slow sometimes it shows the spinning ball.", "Regression: very long input delay when dragging some gizmos handles in macOS\n|Operating system:|macOS-12.1-x86_64-i386-64bit 64 Bits|@WilliamReynish\n| -- | -- | -- |\n||macOS-12.3-x86_64-i386-64bit 64 Bits|@p1x3l\n||macOS 12.2.1|@veily\n\n|Graphics card:|AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.101|@WilliamReynish\n| -- | -- | -- |\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.101|@p1x3l\n||AMD Readon RX 6900 XT 16GB|@veily\n\n> In #96435#1346701, @Sergey wrote:\n> I can reproduce this issue on Mac Pro 2019 AMD W6800X, but NOT on MacBook with Intel Iris GPU.\n\n\nBroken: 3.1.1 Release Candidate\nWorked: 3.1.0\n\nWhen dragging some gizmo handles, the user has to drag the mouse cursor over a huge distance before the drag is registered as an input. That is even if the drag threshold is set to the minimum level. Used to work normally in 3.1 and earlier releases. This makes using the gizmos extremely slow and unresponsive.\n|[blender1.mov](blender1.mov)|[Screen Recording 2022-03-14 at 13.14.54.mov](Screen_Recording_2022-03-14_at_13.14.54.mov)\n| -- | -- |\n\n - Switch to the Scale tool\n - Pull either of the colored axis handles\n - You have to pull them extremely far before it start to actually scale at all.\n\nSome gizmo handles work better, such as the move gizmo handles. Not sure why there is such a difference.\n\nSee the below video recording. As you can see, drag threshold is set to the minimum amount here, and you can see the cursor traveling very far before it starts to scale" ]

[ "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 when duplicating and \"Use Clump Curve\" is turned on for hair particles\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 497.09\n\nBroken: version: 3.1.0 Beta\n\nA crash occurs when a curve guide force field is applied and \"Use Clump Curve\" is turned on. Doing this then duplicating the object crashes Blender.\n[blender_puASiznJH9.mp4](blender_puASiznJH9.mp4)\n\nFrom Default Start up\n1. Create Hair particle on cube\n2. Create curve, and add \"Curve Guide\" force field\n3. In Hair particle settings, turn on \"Children: Simple\" and \"Use Clump Curve\"\n4. Attempt to duplicate cube. It should crash here\n\nFrom attached:\nJust turn on \"Use Clump curve\" then duplicate. \n[haircrash.blend](haircrash.blend) \n\n\n\n\n\n", "Crash when playing animation in rendered view (cycles)\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0, 3.5\nWorked: unknown\n\nPlaying animations in cycles rendered view frequently crash blender. With the attached file I consistently get a crash within 1-2 minutes of starting the animation.\n\nThe crashes do not occur when running the intel version through rosetta. They occur much faster/more often when using the CPU than when using the GPU.\n\nOpen attached file\nSwitch to rendered view (Crashes with and without Metal preference)\nPress spacebar to play\n\n[Boat boating.blend](Boat_boating.blend)\n[Animation crash.txt](Animation_crash.txt)\n```\nThread 17 Crashed:\n0 Blender \t 0x10319354c tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 340\n1 Blender \t 0x103193644 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 588\n2 Blender \t 0x103192c60 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 184\n3 Blender \t 0x103183300 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252\n4 Blender \t 0x10318c3b8 tbb::internal::market::process(rml::job&) + 40\n5 Blender \t 0x10318d6b0 tbb::internal::rml::private_worker::run() + 288\n6 Blender \t 0x10318d584 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n7 libsystem_pthread.dylib \t 0x1b39cd4ec _pthread_start + 148\n8 libsystem_pthread.dylib \t 0x1b39c82d0 thread_start + 8```", "Click-and-Drag the Cursor with Snapping enabled and an Active Object selected missplaces the Cursor\nOperating system: Linux-5.2.9-125.current-x86_64-with-glibc2.9 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\nWorked: None so far\n\n\nDragging the cursor and snapping it to a Vertex while having the Target set to Active makes the cursor snap to a point in space that is directly related to where you start your *click-and-drag* instruction in reference to the selected object's origin. \n\n1) Change snapping to Vertex, Edge or Face\n2) Change snapping target to Active\n3) Set active tool to Cursor\n4) Activate snapping during transform\n5) Select default cube\n6) Drag Cursor over cube\n\n**Important notes**\n\n- If you deselect everything it works, but while there's an object selected the snapping won't work.\n\n- The problem also happens in Edit Mode, but only if there's an object selected in Object Mode. If you deselect everything in Object Mode and then go back to Edit Mode it works as intended.\n\n- As far as I can tell the _offset_ of the snapping is directly related to where you start your click-and-drag in regards to the Objects Origin.\n\n- There's a BlenderArtist Topic in which some have tested the behavior in Blender 2.81: 1177897\n\n- I recorded a video showing the problem: [blender_bug_report_complete.mkv](blender_bug_report_complete.mkv)\n\n- I also uploaded the blend file I used to record the video: [bug_report_cursor_snapping.blend](bug_report_cursor_snapping.blend)", "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", "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", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Blender crashes after rendering a few frames of an animation\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nI've never had this kind of problem - Blender crashes randomly after rendering a few frames of the animation. The only \"new\" thing I'm doing is I started using geometry nodes in this scene. I have plenty of VRAM left, shouldn't be a GPU issue. Tried both in 3.4 and 3.5\n\n\n", "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```", "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", "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", "\"Object Custom Properties\" Drivers don't work while Object Custom Properties are created with simple script.\n\n\n\n\n\n\n\n\n\n\n\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Beta\n\n\"Object Custom Properties\" Drivers don't work while Object Custom Properties are created with simple script.\n\n1. Open Blender.\n2. Select the Default Cube.\n3. Run this code via Text Editor (it creates one Object Custom Property to Cube, and one Object Custom Property to Camera):\n\n\n```\nimport bpy\n\nob = bpy.context.active_object\n\nprop_name1 = ob.name + \"_Property\"\nob[prop_name1] = 0.0\nob.id_properties_ensure() # Make sure the manager is updated\nproperty_manager = ob.id_properties_ui(prop_name1)\nproperty_manager.update(min=0.0, max=1.0, soft_min=0.0, soft_max=1.0)\n\ncamera = bpy.context.scene.objects['Camera']\n\nprop_name2 = ob.name + \"_Property\"\ncamera[prop_name2] = 0.0\ncamera.id_properties_ensure() # Make sure the manager is updated\nproperty_manager = camera.id_properties_ui(prop_name2)\nproperty_manager.update(min=0.0, max=1.0, soft_min=0.0, soft_max=1.0)\n```\n4. Select Camera.\n5. Right Click on created Camera's Object Property \"Cube_Property\" and Left Click on \"Copy as New Driver\".\n6. Select Cube.\n7. Right Click on created Cube's Object Property \"Cube_Property\" and Left Click on \"Paste Driver\".\n8. Value is not drivered / updated. Unless you edit driver, click in Data Path Textbox or Name Textbox, click Enter - now everything works great, but... i didn't change anything there.\n\n", "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", "Linking/Moving collection to another scene messes with the object visibility.\nOperating system: Windows 11\nGraphics card:\n\n**Blender Version** \nBroken: 9719fd696488\n\n\n\nThere is no reason the object visibility should not be carried over when the collection is moved or linked to another scene.\n\n\n[blender_HRo7zHHvN3.mp4](blender_HRo7zHHvN3.mp4)\n\nload the attached .blend\n\nselect the TEST collection in scene.A\n\nleft click drag onto scene.B while holding ctrl to link the collection instead of moving it. Moving the collection has the same affect\n\nopen scene.B and check the visibility\n\n\n\n[tests_06122022_1933_13.zip](tests_06122022_1933_13.zip)\n" ]

[ "crush by moving a object\nOperating system: windows 10\nGraphics card: Radeon RX 580 Series\n\nBroken: (Broken in the newest Blender Version as well as in the old blender Versions)\n\n**When I moving (clicking and moving with g) object \"cube 17\" the Programm crashes. When I look at the task manager I see, that the gpu is fully occupied {[F8948235](Armbrust_Low_work.blend)}**\n\nBased on the default startup or an attached .blend file (as simple as possible)." ]

[ "Links persist invisibly after their source sockets are removed\nBroken: Probably forever (e.g. 3.0, 3.1)\nWorked: N/A\n\nIf the output socket of a node is removed, the input socket it was connected to does not show a button to input a value. It acts like it's still connected.\n\n**Detailed replication**\n1. Go into the Shader Editor\n2. Create the *Voronoi Texture* node and a *Math* node\n3. Set the *Voronoi Texture* node to 4D, and plug its new W output into the *Math* node\n4. Set the *Voronoi Texture* node to 3D. Observe that the input on the *Math* node still acts like it's connected\n5. Click and drag from that input on the *Math* node. A bogus wire will appear from the *Voronoi Texture* node, coming from where the W output used to be.\n\nYou can then plug this wire into another socket. It will disappear again once you let go. If you set the *Voronoi Texture* node back to 4D, the wires will re-appear.\n\nVideo example:\n\n[XwBMq60aMI.mp4](XwBMq60aMI.mp4)\n\n**Another example:**\n\n{[F13079601](free-socket.blend), size=full}\n\nIn this case you can even save the file in this state where you can't see or edit the value of the node until you disconnect it.\n\n", "Asset Brower Header Position won't stay on bottom\nOperating system: Linux-4.15.0-159-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.1.0\n\nLike for other editors, you can flip the header of the Asset Browser to the bottom. \nHowever, this will not persist when Header position is set to \"bottom\" in preferences tab\n\n* Change Header position to \"Bottom\" {nav Edit > Preferences > Interface > Editor > Header Position}\n* change the Asset Browser header position to bottom: RMB on header -> select `Flip to Bottom`\n* save the file (as a new or as a startup file)\n* restart Blender, and the header will be on top again \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 ", "Improve unclear/broken File Browser User Preferences\nThe current File Browser settings are a mess and/or don't work.\n\n# Problems\n\n## 1) \"Show Hidden\" space parameter conflicts with user preference\nWhether to show hidden files is determined by a per-space flag, which is automatically saved (see `PARAMS_FLAGS_REMEMBERED`). But this flag also tries to get initialized with the userpref flag `USER_HIDE_DOT`.\nThe former **overrides** the latter, meaning the option does nothing when using temporary windows (which is factory default).\n\n## 2) Hidden Data-Blocks is confusing (and broken)\nFor those who don't know, this is a feature which hides dot-prefixed data-blocks not only from file browser, but also when searching in any ID selector.\nHowever, for the file browser, it's (confusingly) not tied to this user preference, but to the \"Show Hidden\" flag of the editor (the tooltip of which does not mention data-blocks at all)!\nAdditionally, this feature does not work in the file browser on Windows due to an `#ifndef WIN32`.\n\n## 3) Unnecessary \"Filter Files\" user preference\nSince the file browser already has the capability to remember its settings (see point 1), it seems reasonable to remove the explicit user preference and use `PARAMS_FLAGS_REMEMBERED`.\n\n## 4) \"Show Recent/System Locations\" are hard to discover\nOther editors (e.g. status bar sections, or Navigation Bar of the preferences editor) allow configuring directly in the editor, either via right click or in the editor's header.\nThese two file browser settings are only found in the preferences.\n\n---\n\n# Proposed Solutions\n\n## 1+2) Cut \"Show Hidden Files/Data-Blocks\" preference in half\n[D14650](D14650)\n- Rename the preference to \"Show Hidden Data-Blocks\" and put it into e.g. the Editing user preferences section.\n - Moving this setting makes it clear it doesn't only affect file browser, but also ID selectors.\n- Consequently, this user preference will no longer affect the \"Show Hidden\" flag of file browsers (this is already handled via `PARAMS_FLAGS_REMEMBERED` anyway).\n- For file browser, show dot-prefixed data-blocks if either this user preference is set *or* the file browser show hidden flag is set.\n - Update the tooltip of the file browser flag, to clarify that data-blocks can also be hidden.\n- Fix hidden data-blocks for file browser not working on Windows.\n\n## 3) Remember \"Filter Files\" automatically\n[D14650](D14650) (can be split into another commit, since it doesn't strictly belong to this patch)\n- Remove \"Filter Files\" user preference and corresponding userpref UI flag `USER_FILTERFILEEXTS`.\n- Instead remember the flag via `PARAMS_FLAGS_REMEMBERED`, making this completely transparent to the user.\n\n## 4) Add \"Show Recent/System Locations\" to file browser\n[D14649](D14649)\n- Include in either the right click menu, or the header menu, options to toggle these two user preferences.\n - It might be worth storing them as per-editor parameters at this point, though I personally don't see much of a desire to have these differ per editor.", "Dopesheet Display Hidden doesn't work property combined with Only Selected.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 75)\nWorked: Version 2.79b\n\n\nIn version 2.79 with the \"Selection Only\" option active in the dope sheet screen, after animating the appearance or disappearance of the object, you had the possibility to edit the keyframes, now it is possible only if the Only Selected option is deactivated, it is rather uncomfortable compared to the previous one because that option is useful to avoid having a max dopesheet window and to avoid errors in complex animations.\n\nFrame 1:\nTurn off the object then Animate Disable in viewport,\nFrame 2:\nTurn on the object and animate Disable in viewport.\nOpen dopesheet window, Click Selection only and Display Hidden option at frame 2, go to frame 1 the frames disappear.\n\n[Dopesheet_280.blend](Dopesheet_280.blend)\n[Dopesheet_279b.blend](Dopesheet_279b.blend)\n\n\n", "Hidden Face Set Boundaries unmasked after inverting the mask on Multires Modifier\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\n\nHidden face sets are not affected by changes in the mesh, colors or mask. So when inverting a mask, the hidden face sets will keep their state of masking intact.\nOn a mesh without a multires modifier it will keep the mask sharp between the face sets but when using a multires modifier it will smooth past what is hidden and what is shown.\nThe mask should remain sharp and accurate.\n\nIn this example I am hiding a face set (Shift + H) and inverting the mask (A) to compare the result on the left (no multires) to the right (with multires).\n[2020-07-27 13-54-29.mp4](2020-07-27_13-54-29.mp4)\n\n[bug.blend](bug.blend)\n\n- Open file\n- Hide center face set (green)\n- Draw mask somewhere on mesh that is visible\n- Invert mask\n# Show all face sets\nRepeat steps 2-4 for another object and compare results.", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n ", "Disabling/enabling in viewport a sub collection doesn't make the instances of the collection disabled/enabled unless you save and re-open the file\nOperating system: Windows 10 Pro 64-bit (10.0, Build 18363)\nGraphics card: NVIDIA GeForce 920M (Laptop)\n\nBroken: v2.83.13 Beta, 2020-04-21\n\nIf you disable/enable in viewport a sub collection of Collection then the instances of the parent collection \"Collection\" is not disabled/enabled in viewport unless you save and re-open the file.\n\n**Wanted result**\nThe wanted result is exactly like when you save and re-open the file, because for example if you enable/disable the cube which is child of child of Collection, then the instance of cube is enable/disabled. And just like that, SubCollection is child of Collection and if it's enable/disabled then the instance should be enabled/disabled too.\n\n\n[SubCollection_ViewportEnableDisable_refresh_bug.blend](SubCollection_ViewportEnableDisable_refresh_bug.blend)\n1. Open the provided file.\n2. Disable in viewport the collection named \"**SubCollection**\" to unreveal it in viewport. Now the two collection instances \"Instance of '**Collection**' (1) & (2)\" are not hidden.\n3. Save the file.\n4. Press Ctrl+N and click General.\n5. Reopen the same file. Now the two collection instances before are hidden, but before they were not hidden, it's a bug about refreshing.\n6. Enable in viewport the collection named \"**SubCollection**\" to reveal it in viewport. Now the two collection instances \"Instance of '**Collection**' (1) & (2)\" are not shown.\n7. Save the file.\n8. Press Ctrl+N and click General.\n9. Reopen the same file. Now the two collection instances before are shown, but before they were not shown, it's a bug about refreshing.\n\n**Steps for others to explain the logic of the viewport visibility of Collection and Collection Instance, this is not a bug, it's a useful feature that you should keep**\n- Don't forget to enable the \"SubCollection\" if you didn't do it yet, you've already save and re-open the file.\n- Disable in viewport the collection named \"**Collection**\" to unreveal it (not SubCollection). Now the two collection instances \"Instance of '**SubCollection**' (1) & (2)\" are not hidden. Now Enable back the \"Collection\", the enablement of the 2 collection instances \"Instance of 'SubCollection' (1) & (2)\" don't depend on the viewport enablement of the collection named \"Collection\".\n\n**Description of the last steps**\nIt's very useful when you build a model in a .blend file at the origin (0, 0, 0), and its collection name is \"_MODEL_\", and you want to place a collection instance of it at other location (not origin), and you want to disable the model at the origin by disabling the parent collection of the collection named \"_MODEL_\", and you want to keep enabled (visible) the collection instances.\n\n\n**People will adapt the non-logic bug but they will see weird things**\nThis is a big problem because if people don't know the bug then they think that it's the logic of viewport enablement of collection instances, and all their projects depend on that, but once they save and close and then re-open the file, they will see weird things.", "Blender 3.6's window has 1/4 content area, 3/4 transparent area under Linux\nOperating system: Arch-based Linux, kernel 6.3.7-arch1-1\nGraphics card: Intel Arc A779\n\nBroken: blender-3.6.0-beta+v36.2ef27684c56c-linux.x86_64-release, but has happened with all 3.6 daily builds so far.\nWorked: 3.5.1, the latest version.\n\nThe content area is 1/4 of the window size when the window is first open. 3/4 of the window is transparent.\nGnome 44.2, Wayland, fractional scaling enabled (100%, 175%), dual monitors (1920x1200, 4K).\n\n\n\n\nRun Blender 3.6\n\n", "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-", "\"View\" settings not refreshing when going out of camera view\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.80 (sub 74)\n\nNot a big bug, but I'm reporting anyway.\n - Open file:\n[viewport_camera_settings_bug.blend](viewport_camera_settings_bug.blend)\n - Use middle mouse button to go out of camera view. Simple click should be enough.\n - Some of the settings in \"View\" will be greyed out until hovered over with mouse cursor:\n\n\n", "Using View Navigation in Camera View Causes Viewport View to Focus on World Origin\nOperating system: Windows-10 64 Bits\nGraphics card: GeForce GTX 1070 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: Never (2.79+)\n\nUsing view navigation (Shift+\") in camera view (Numpad 0) causes to lose the previous viewport view (Numpad 0 again) and it focuses world origin. \n\n1- Launch default Blender.\n2- Change your view to anywhere (For example zoom in to a vertex of the cube).\n3- Go in camera view (Numpad 0), use view navigation (Shift+\") and right click to cancel it (you can change view with left click as well, it doesn't matter).\n4- Go in viewport view (hit Numpad 0 again), notice that your previous view changed (it now focuses world origin)\n\nBelow gif demonstrates the issue:\n\nView navigation that I used:\n\n\n", "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", "Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.4.0 Alpha\nBroken: 2.92.0\nWorked: 2.91.2\n\nBisecting gives 0f95f51361 as the culprit commit\n\nif the armature viewport mode is set to \"in front\" it doesn't properly update when the overlays are turned off and on\n[Peek 2022-11-01 05-35.mp4](Peek_2022-11-01_05-35.mp4)\n\n1-add an armature\n2-set the \"viewport display\" to in front\n3-turn off and on overlays\n4-if you can confirm the bug the armature should appear after changing anything in the 3d view to update as in the video, move rotate or zoom \n\n", "Particle Viewport display options don't reset properly when changing particle type\nOperating system: Windows-10-10.0.19044-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\n\nViewport Display panel options don't reset properly when changing the particle type from Emitter to Hair and back to Emitter again.\n\n1. New default scene.\n2. Add particle system to cube.\n3. Go to the Viewport Display panel for the particle system and notice options.\n4. Change the particle system type from Emitter to Hair.\n5. Options under Viewport Display panel change accordingly.\n6. Change the particle system type back from Hair to Emitter.\nOptions under Viewport Display panel are those for Hair and not Emitter.\n\n\n\n" ]

[ "Header showing again after hiding it and rebooting blender\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 512.15\n\nBroken: version: 3.3.0 Alpha\n\nAfter hiding the header from the 3d viewport, saving and relaunching the saved file, the header is back again but with tool setting only, when it's supposed to be hided.\n\n1- Launch blender\n2- Right click on the header and uncheck \"show header\", all the header is now hided.\n\n\n\n\n3- Save the file and re launching blender and load the saved file\n4- Tool header is now visible\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", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "lineart bake w/ object keyframes + camera binds = crash\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.4.1\n\nA crash (instant program exit) happens when trying to bake line art with *both* keyframes on object visibility *and* cameras bound to a frame in the timeline.\n\n1. Open the attached blend file. Select the Line Art modifier, and click \"Bake Line Art\". The baking starts, gets to frame 7 (the one after the TriAllFree bound camera) and crashes.\n2. Open the attached blend file. Delete the camera binding marker on frame 6. Select the Line Art modifier, and click \"Bake Line Art\". The baking starts, gets to frame 7 (the one after where the TriAllFree bound camera was) and crashes.\n3. Open the attached blend file. Delete the camera binding marker on frame 6. Save the file to a new filename. **Exit blender**. Open the blend file with the new filename. Select the Line Art modifier, and click \"Bake Line Art\". The baking completes with no issue.\n4. Open the original attached blend file (not the new one without the camera bind). Delete the timeline channel on the Suzanne model that changes the render visibility. Select the Line Art modifier, and click \"Bake Line Art\". The baking completes with no issue.\n\nTested with daily builds of 3.4.1, 3.5.0 beta, and 3.6.0 alpha. Issue still present in all cases.\n\n", "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", "Frequent crashes when performing minor adjustments with rigid body constraints\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel Inc. 4.1 INTEL-16.5.2\n\nBroken: version: 3.0.0 Alpha\n\nWith a simple rigid body setup (see attached file), there are frequent crashes when doing simple adjustments such as moving the constraint around, rotating it, starting/stopping the animation, undoing some steps. There is not a single scenario leading to a crash, but performing a combination of these actions in succesion consistently leads to a crash (segmentation fault) within about 30-60s.\n\n[Rigid body crash.blend](Rigid_body_crash.blend)\n[Rigid body crash.txt](Rigid_body_crash.txt)\n\nI closed #91025 because I thought it was fixed, but it turns out the crashes still occur. I have found one reproducible way to get the crash:\n- With factory preferences, open attached blend file.\n- Press spacebar to start the animation\n- Press command-Z to undo and then shift + left arrow to restart at the first frame\n- Repeat the last step (command + z and then shift + left arrow) a few times\n- Blender will crash usually after repeating 2-3 times, sometimes a few more.\n", "Crash after Disk Cache Particle bake while set to render as path\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\nsame results on daily 3.1 build\n\nBlender crashes after finishing baking the particles to disk.\nThen proceeds to delete the baked files upon reopening the file. \n(don't know if the deletion is intended behaviour or not, but it stops you from being able to salvage the bake unless you rename / duplicate the cache folder beforehand)\n\nSeems to only happen with disk cache bake and not baking to memory. \nChanging the 'render as' setting to anything but 'path' seems to stop the crashing.\n\nOpen file, bake the particle system\n[Particle Bake to DiskCache Crash.blend](Particle_Bake_to_DiskCache_Crash.blend)", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\n\n", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "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)", "Set as Background crashes blender instantly.\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080 Ti and RTX 3060\n\nBroken: 3.62\n\nI'm trying to do object tracking. Have tracked an object and clicked Solve Object Motion, then when I click on Set as Background Blender crashes instantly. Trying to load in a 400 frame 1920x1080 png sequence. Blender also crashes if I try to load the background image sequence via the camera properties (Background Images > Add Image).\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "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)", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "Crash (Seg Fault) When Rendering Grease Pencil Stroke on Render Farm\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.1\n\nOur render farm of 70 iMacs has been running for 3 years through the 2.7x series up till 2.81a.\nWhen we switched to 2.83 last week it started crashing consistently when rendering Grease Pencil strokes.\nThe crash occurs when using Blender to do command line rendering via an SSH session on a machine without the user physically logged in. (Crashes on Mac and Linux)\n\nCommand Line Rendering on my own machine works fine.\nCommand Line Rendering on a remote machine via SSH works fine if I'm also logged into that machine.\nBut as soon as I log out of the machine so that the SSH session is the only active user on the machine, then the error shows up.\n\nI tested this on 2.81a and the error (below) shows up there too, but in 2.81a it doesn't also lead to the Segmentation Fault that crashes Blender.\nIt's only in 2.83 (and 2.83.1) that the error is followed by the Seg Fault 11\n\n\n**_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.\nWriting: /var/folders/jk/7b488ncn6c13t515bnt6q_8w68xcj1/T/test.crash.txt\nSegmentation fault: 11**\n\non Linux the error message is slightly different, but still a crash:\nUnable to open a display\nAborted (core dumped)\n\nContents of test.crash.txt (from the Mac crash)\n# Blender 2.83.1, Commit date: 2020-06-25 09:47, Hash 8289fc688b3e\n\n# backtrace\n0 Blender 0x00000001079eb9d7 BLI_system_backtrace + 55\n1 Blender 0x000000010159ddb8 sig_handle_crash + 392\n2 libsystem_platform.dylib 0x00007fff5db5fb3d _sigtramp + 29\n3 ??? 0x00007f8594802010 0x0 + 140211698802704\n4 Blender 0x0000000101a39da2 DRW_opengl_context_create + 66\n5 Blender 0x00000001018f47d5 WM_init_opengl + 37\n6 Blender 0x0000000101a374ff DRW_render_gpencil + 127\n7 Blender 0x0000000105de5ef4 RE_engine_render + 1156\n8 Blender 0x0000000105df06d3 do_render_all_options + 387\n9 Blender 0x0000000105df2a14 RE_RenderAnim + 2260\n10 Blender 0x000000010159c9dd arg_handle_render_animation + 141\n11 Blender 0x000000010797880d BLI_argsParse + 173\n12 Blender 0x000000010159a497 main + 855\n13 libdyld.dylib 0x00007fff5d974ed9 start + 1\n14 ??? 0x000000000000000a 0x0 + 10\n\n\n\n1) Make a new default file.\n2) Delete the Cube\n3) Add->Grease Pencil->Monkey\n4) Save as test.blend\n5) Copy test.blend onto a remote machine\n6) Make sure the machine is at the login prompt (showing the username password boxes).\n7) ssh into the remote machine\n8) command line render one frame from test.blend something like:\nBlender -b /test.blend -s 1 -e 1 -a\n\n", "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" ]

[ "Blender crashes if you add a motion path to the bones\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nBlender crashes if you add motion path to the bones or trying to recalculate the existing one. Motion paths with objects works just fine.\n\nAdd an armature single bone, set a couple of keyframes for it in the pose mode\npress 'W' -> Calculate motion paths -> press OK button. \n", "Blender crash when use motion paths\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\n\nBlender crash when use motion paths\n\n- Open Crash.blend\n- Select one bone and calculate motion paths\n- Blender crash\n\n[Crash.blend](Crash.blend)\n\n\n" ]

[ "Color > Multiply doesn't multiply alpha channels\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) 3.6.2\n\nThe Color > Multiply section in a video sequencer strip no longer multiplies the alpha channel when that feature is pretty important for creating outlines using the glow effect. Perhaps adding an option whether to multiply alpha or not would be beneficial?\n\nStart up blender 4.0.0\nSwitch to Video Editing workspace\nAdd a white color strip with 0.1 opacity\nAdjust the Color > Multiply value and notice how it doesn't affect alpha anymore\n\n", "Blender Interface Does Not Respect Windows Colour Profiles\nOperating system: Windows 10 Home 1909\nGraphics card: Nvidia GTX 1080\n\nBroken: 2.83.0 on Windows\nWorked: 2.83.0 on OSX\n\nBlender's interface shows incorrect colours on high colour gamut monitors in Windows 10. Any monitor over 100% sRGB is showing colours to be incorrectly vibrant in every panel, including image viewer, 3D view and compositing.\nThis is believed to be due to Blender failing to reference the OS's installed ICC/ICM profile, or the interface entirely lacking any colour management that respects monitor profiles.\nSince OSX has system-wide colour management, this issue is not apparent. Windows does not have system-wide colour management, and apps must perform their own referencing of the installed ICC/ICM profile.\n\nOpen Blender on a high-gamut monitor in Windows 10. Compare to sRGB 100% monitor or OSX.\nError initially produced on a Dell UP2516D high-gamut monitor.", "Line Art isn't updating active camera\nOperating system: GNU/Linux mint 19\nGraphics card: gforce RTX 2060\n\nBroken: 2.93.4 \n\nLine Art isn't updating active camera when it's changed in a 'Scene' strip (VSE)\n\n\n- Create a scene, a camera and a LineArt object.\n- Now, create a 2nd camera (Cam.001) (not the active one)\n- Create an empty scene in order to be used for video creation.\n- In `Video Sequencer`, add a Scene strip and choose the Cam.001 camera ->it changes ok, but lineart goes dependent on the first one.\n\nTest File:\n[#91971.blend](T91971.blend)", "LookDev: Add option to set the background color\nTheme, World, Viewport.\n", "Invisible color picker in the preferences menu\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\n\n**Short description of error**\nDepending on your position in the preferences menu the colour picker becomes invisible\n\nDepending on your position in the themes menu (preferences/themes), the colour picker may be above or under the setting you want to change, but there is a specific position in which the colour picker becomes invisible. This bug only occurs if there are multiple settings above, at least one submenu open and you edit one of the settings in the middle. E.g. \"Inner\" and \"Inner selected\" in the user interface section. The colour picker is not only invisible but also not functioning. The \"RGB\" and \"HSV\" sliders work as well as the \"HEX\" section.\nClosing the picker and scrolling down the page, only by a single line (up or down) fixes the glitch, also resizing the window works. \n\nBased on the default startup\n\n", "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", "No color drag'n'drop in Viewport Shading popover\nOperating system: Linux Mint\nGraphics card:\n\nBroken:2.81-a856c5eccffb-linux-glibc217-x86_64\n\n\nNo color drag'n'drop in 3d view solid (and wireframe) shader options dropdown.\n\nOpen default scene,\nclick on solid shading,\nopen the shader options dropdown,\nunder \"Color\" choose [Single],\nunder \"Background\" choose [Viewport],\ntry to drag the color of one to the other.\n\nAlso not works in wireframe shading dropdown.\n\n", "VSE: Alpha Over + Convert to float changes the color of the top layer\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 600 Intel 4.5.0 - Build 27.20.100.8853\n\nBroken: version: 2.92.0 Alpha\n\nAdd two color strips - not black, and change compositing of the top strip to Alpha Over. Toggle 'Convert to float' under color while pressing arrow left/right to update the preview. The top layver will now change color, it's a regression and a bug. \n\n", "UI: Color picker lightness/value changes Hue and Saturation (only in Preferences > Themes?)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.6\n\nThe color jumps erratically by adjusting the lightness value, worse the closer to black\nSeems to converge towards specific colors (see video).\nDoesn't seem like node colors are affected.\n\n1. Open a theme setting.\n2. Adjust the lightness value.\n[ZVj8uWcUpy.mp4](ZVj8uWcUpy.mp4)\n", "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.", "Default Particle System colourization in Particle Edit Mode (Hair) doesn't follow theme wire/verts settings\nArch Linux + GTX 780ti\n\n\nAll versions since 2.5alpha. Currently using Blender v2.79 8ef39d5c882\n\n\n * Choose a dark Blender UI theme (Dark 3Dview background)\n * Working in `Particle Edit Mode` with different different particle systems (PS) the currently selected hair PS wire/verts colours are set to *black* instead. This is ok with light `3DView` (opengl) backgrounds. With black or dark themes or blender scenes the user can't see particle paths.\n * Adding more than one PS shows all unselected PS colours just fine using their set material colour. That is not what this bug report is about. Here the focus is on wire/vertices default colourization for the **currently selected** PS.\n * It looks like selecting the first PS uses black as default wire/verts colour. While selecting all other PS they use theme wire colour somehow, but changing `User settings -> Themes -> 3D View -> Wire/Wire Edit` colour has no impact?!\n\n\n**Side effects**\n * Switching `Particles->Render->Emitter` brings viewport PS colourization \"back\" somehow. Broken, but unselected PS are showing their material colour. randomly (?)\n * Working with three hair PS and playing with Emitter influences only some unselected PS (random)?\n\n\n**Current Workaround**\nWhile editing (Particle Edit mode) the current PS just *select all* and then use the brush to edit them. \n\n\n * Use the attacked blend file [PS.blend](PS.blend)\n * and play around while switching between `PS Red/Green` in `Particle Edit Mode` and randomly switch `Emitter` on/off.\n\n\n**Suggested Result**\nThe currently selected hair PS follows theme wire/verts colourization. All unselected PS are using their material diffuse/base colour.\n\n**PS**\nI added a cloned PS, too. Which was cloned from the Red one `ParticleSystem Green (cloned Red)`. Switching its visibility brings all PS material back.\n\n**Possibly Related Sources**\n* Blender Artists: [How Do I Change Hair Colour In Particle Edit Mode?](showthread.php?320868-How-Do-I-Change-Hair-Colour-In-Particle-Edit-Mode)\n", "Color management is broken in the Sequencer\nOperating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1\n\n\nBroken: version: 2.80 (sub 74)\nWorked: earlier build of 2.80 (hash: d62a749fcf48) and 2.79\n\nWeird things happens when changing the color management settings in the VSE:\n- wrong color display\n- make sound\n\nWith a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.\nAlso, changing this setting does not apply the change directly, the VSE has to be refreshed.\n\nAnother issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.\n", "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", "Sample color add to palette, works for mouse click but not key press only\nOperating system: Windows 10 64-bit\nGraphics card: NVIDIA GeForce GTX 960M\n\nBroken: 2.80 2019-02-05 23:34\nWorked: (optional)\n\nUsing the **sample color** tool, **add to palette** option does not work properly.\n\n1. Press S+LMB with cursor on any color. The option **add to palette** is checked automatically(at the tool properties panel at the bottom left) and the color is actually added to the palette(tool properties bar at the top > brush).\n2. Press S with cursor on any other color(do not click). The option **add to palette** is still checked(because it remembers the last operation). new color is extracted and is now the foreground color. However it does not add the new color to the palette. Strange.\n3. Press S with cursor on any other colors(do not click). It behaves the same. **Add to palette** is checked but is not working.\n\n**Extra bug**\n1. Press S with cursor on any color(do not click). The option **add to palette** is not checked automatically.\n2. Try to enable the checkbox **add to palette**.\n3. Blender crashes.\n\nMaybe the solution is just to get rid of the checkbox **add to palette**.\nS is sampling color to foreground color, S+LMB is sampling color to palette. Why would we need the checkbox?\nIt is also possible to add the color to palette after sampling(to foreground color). This option doesn't seem necessary to me...\n\n[bug-samplecolortool-addtopalette.blend](bug-samplecolortool-addtopalette.blend)", "Color picker value not working as expected\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha, 2.92 doesn't work either.\nWorked: 2.91 official release\n\nWhen I enter 0, 0 , 0. 5 in the HSV-values expecting a 50% grey ,but the grey I get is way too bright. It's more like 70% grey. The value slider also indicate this brighter value and not half way the black and white gradient as you'd expect it.\nThe saturation value exhibits the same kind of problem a 0, 0.5, 0.5 HSV-value is not as saturated as one would expect.\n\nfirst noticed this in the 2.92 official release and and checked, as advised, the latest version (the above mentioned 2.93 alpha) to see if it was resolved. The last time the color picker worked as expected was in 2.91.\n\nMakes inputing specific colors values pretty much a nightmare.\n\nopen blender, change color pretty much anywhere you can change color. \n\nattached screenshots:\n\n\n\n\n\n\nThanks, have a nice day. (Pablo made me say it! 'cause apparently humans are checking XD)\n" ]

[ "Color management not affecting the viewport when Scene Lights and Scene World are unchecked\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX Vega ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.90.0\nWorked: never?\n\nExposure, Gamma and Curves will not affect viewport if \"Scene Lights\" and \"Scene World\" are unchecked.\nHappens on Eevee and Cycles.\n\n1. Set properties>Color Management>Exposure to -10\n2. Change viewport to material preview or rendered\n3. Make sure \"Scene Lights\" and \"Scene World\" are unchecked\nScene isn't dark when it should be.\nChecking any of those will show the scene on the correct exposure.\n\n\n" ]

[ "Face overlay still not resolve.\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\nWorked: 3.4.1\n\nDepth offset in Metal overlay is much larger than seen in OpenGL\n| OpenGL | Metal |\n|---|---|\n|  |  |\n\n\n- Open attached .blend file\n\n", "Dynamic Paint sub-steps doesn't work with particles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.0 Alpha\n\nWhen using a particle system as a dynamic paint brush, the sub-steps setting of the canvas doesn't work. The sub-steps appear to work as intended with all other brush types. Whether the painting is done with vertex or texture maps doesn't seem to have an impact on the bug.\n\n* Open attached .blend\n* Bake the dynamic paint cache with a sub-steps value > 0\n* The result shows no sub-steps\n[Bug2.blend](Bug2.blend)\n", "Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.0\nWorked: --\n\nLow resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to \"closest\" in the material shader.\n\nfeature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.\n\nplace object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. \n\ntextures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from \"linear\"(or whichever is set to default) to \"closest\"\n\nWe have 4 materials each having individual Image Texture nodes (but all using the same image).\n\nIf you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.\n\n", "Workbench: Shadow Bug\nOperating system: MacOS Catalina\nGraphics card: Intel Iris Pro 1536 MB\n\nBroken: 2.83\n\nWhen trying to add a shadow, all screen \"cracks\" into different-shadow pieces\n\n\n\nViewport Shading> \"checkbox\" Shadow ", "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", "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", "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", "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", "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", "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n", "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", "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", "3D Connexion Space Mouse Pro - Blender 2.82a on macOS\nmacOS Catalina 10.15.4 (19E287)\n3D Connexion 3dWare10 10.6.5\n\nBlender 2.82a\n\n\nThe mouse appears to almost match the 3D Connexion training app in terms of movement when in object/edit mode but it would appear that none of the buttons & especially the MENU do not work. \n\nI have installed the 3D Connexion drivers a second and third time with firewall and anti-virus off and the problem with these mice seem to persist. \n\n>> This has been edited by another but im wondering if there is some resource file missing where keys are mapped, either this is a 3D Connexion plug in or something to do with Blender?\n\n\nI've seen these tasks; It's still a problem for me. \n#67686 (NDOF mouse not working in code signed macOS builds)\n#67971 (3D Connexion Space Mouse Enterprise Custom Buttons 1-10 Not working in Blender 2.8 (macOS))", "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.", "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" ]

[ "Texture paint overlay opacity no longer work\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\nWhile in texture paint, the texture always appear at 100% opacity regardless of the opacity setting in the overlay menu. Even when turn off the overlay, the texture remains at 100%.\nSwitch to look dev mode makes the texture disappear entirely.\n\nSet material and a texture for the default cube, switch to texture paint. The texture will appear regardless of opacity setting." ]

[ "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", "Closing quotes get replaced by unit names in driver expressions.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.91, 2.92\n\n\nWhen the scene unit system is set to `'IMPERIAL'`, the closing quotes of any driver expression that includes string literals will be replaced with the text strings of either `in` or `ft`.\n\nE.G. `SomeObj[\"SomeProp\"]` turns into `SomeObj[\"SomePropin]`. `SomeObj['SomeProp']` turns into `SomeObj['SomePropft]`.\n\nThe replacement happens when the driver expression is *edited* for the first time from the input field for the property which it drives. It does not happen immediately when the expression is first input, so the driver works fin until it's been edited, and it does not seem to happen when the driver is either viewed or modified from the driver editor pane.\n\n \n\n\nSet `C.scene.unit_settings.system` to `'IMPERIAL'`, then create a driver with a string literal expression and try to edit it from its driven value's input field.\n\nOr download the attached file, and click on either of the two driven channels in the active object's location transform in the 3D Viewport Sidebar:\n\n[DriverCorruption.blend](DriverCorruption.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.", "Pinning Bones/Constraint Tabs in Properties Editor doesn't work\nBroken: 2.76 - master (1283c66)\nWorked: Unknown\n\nThe context pinning functionality in the Properties Editor doesn't work for Bones and Constraints. There may be a few others too that I haven't noticed yet, but these are the biggest ones.\n", "Unable to fix broken linked IDs when renamed in libfile\nWindows 10\nWindows 7 x64\n\nWorked: 2.82\nBroken: 2.83.0\n\nCant rename linked collection. Error: Cannot edit external library data\n\nDefault Blender setup (first file lets call it assets.blend)\nCreate a collection and name it \"Test\" \nCreate a cube and move it to \"Test\" collection\nSave the file\n\nCreate another file (lets call it level.blend)\nLink the \"test\" collection from the assets.blend\nCheck all linking options before hiting link\nSave the file\n\nNow open assets.blend again and rename \"Test\" collection to \"Cube\"\nAnd save it again.\n\nOpen level.blend\nA message appears that link is broken\nGo to Outliner and change Display mode to Blender File\nNow go down to the linked collection\nDouble click broken collection to rename it\nError message appears \"Cannot edit external library data\"\n\nRenaming linked collections works fine in 2.82\n", "Undo in Armature Edit Mode does not undo Custom Properties\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.5 Beta\n\nUndo in Armature Edit Mode does not undo changes to Armature Custom Properties\n\n- [optionally] In default scene delete all objects\n- Add an \"Armature\" object\n- Go to `Edit Mode`\n- In `Object Data Properties` add a `Custom Property`\n- Change the value of the property (to for example `0.0`) in order to add an Undo step\n- Try undo (`Ctrl+Z`)\n\nThe step is not undone in edit mode.\nInterestingly, changes to the Custom Properties of Bones are correctly undone in Edit mode.\nThis makes it seem that changes to Armature Custom Properties were perhaps missed in the Armature Edit Mode Undo Context.\n\n---\n**Original Report**\n[Video](3RZNWd5tRQI)\nNote when changing the **head size** in the redo panel, you can observe how the number of elements in in the Collection Property `bones_for_delete` grows.\n\n1. Execute the script generate_rig.py from the file, if you do not have automatic script execution enabled\n2. After execution, the Generate Rig panel will appear in the Rig category\n3. Select Empty.021 first, then Armature.001. Switch to armature editing mode, and click Generate Rig on the panel\n4. The bones will appear, and also the text on the panel will notify that there are elements in bones_for_delete. After that, you can scroll the **head size** on the redo panel, or simply undo the operator. the label in the panel will notify you that the number of items will not change\n\n", "Uncontrolled vertex movement in symmetric editing\nOperating system: Windows 7\nGraphics card: AMD Radeeon `R9` 200 Series\n\nBroken: version: 2.82 (sub 7), type: Release; build date: 2020-02-13, 01:56:46\nWorked: (optional)\n\nWhen symmetrical editing about the X axis with proportional editing of an almost symmetric object, model changes are detected in places where editing was not performed. \n\nMoreover, these changes occur asymmetrically. For example, in a key with a changed shape of the legs of a human model, a significant asymmetric change in the neck region with a shift of the line of symmetry itself was found. So it is with most other shape keys. Thus, the symmetry of the entire model is violated, which entails other undesirable consequences. These problems cannot be solved programmatically or manually, and the data on the coordinates of the vertices strangely diverge from the observed form.\n\n[#74340.blend](T74340.blend)\n\n- Open file\n- Move selected vertex\n# vertices in unconnected mesh on mirror side will move\n\nModel Genesis 8 exported from DAZ Studio in Base Resolution .obj file and imported to Blender.\nHMiU6BYcl2E\n", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)\nOperating system: Linux-5.15.0-52-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.4.0 Alpha\nBroken: 2.92.0\nWorked: 2.91.2\n\nBisecting gives 0f95f51361 as the culprit commit\n\nif the armature viewport mode is set to \"in front\" it doesn't properly update when the overlays are turned off and on\n[Peek 2022-11-01 05-35.mp4](Peek_2022-11-01_05-35.mp4)\n\n1-add an armature\n2-set the \"viewport display\" to in front\n3-turn off and on overlays\n4-if you can confirm the bug the armature should appear after changing anything in the 3d view to update as in the video, move rotate or zoom \n\n", "XYZ symmetry options: unclear release notes\nThe 2.91 release notes for 5502517c3c are lacking, both in clarity of the description and the discoverability of that change for the people it impacts.\n\n- The change is described in the Sculpting section, under \"[Sculpting Workflow with multiple objects](Sculpt#Sculpting_Workflow_with_multiple_objects)\". However, it is much broader than just that. Since this change also impacts weight painting, it is relevant to riggers as well. It should be described in a place such that riggers can find it.\n- The only description is \"XYZ symmetry is now a per mesh settings which is shared between all painting and editing modes\". This doesn't convey what this change means practically, it doesn't show the changes in the UI, and doesn't tell riggers how they have to change their workflow to account for this change.\n\nAs a side-note, the #animation_rigging module should have been involved in design task #79785 and the review of [D8587](D8587), since this change impacts workflow of riggers. Instead, it went completely under the radar.\n", "Toggling mesh symmetry (X, Y or Z) by shortcut doesn't refresh its icons\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.0.0\n\nIf I assign a shortcut to enable symmetry on X axis in the tool settings > symmetry, symmetry works when sculpting and the X icon turn on/off accordingly.\nThe full path is bpy.data.meshes[\"Cube.001\"].use_mirror_x.\nIf I assign a shortcut to enable symmetry on X axis in the viewport, symmetry works when sculpting, but the X icon turn on/off only when mouse leave the viewport, like it needs a refresh.\nThe full path is bpy.data.objects[\"Cube.001\"].use_mesh_mirror_x\n\nOther than that it seems the two icons don't talk each other on the fly: if I turn off X in viewport, X in settings is still on and it will be off only when mouse goes over it.\nIf it's not fixable, my suggestion is to take down the three XYZ icons in viewport and just leave the butterfly icon with the actual drop down menu, in my opinion it's more important seeing there's the \"ghost brush\" on the other side, rather than having a not working icon or substitute them with the three icons from settings.\nThank you\n\n- with the default Cube go to Edit, Paint or Sculpt mode\n- Assign a shortcut to one of the mesh symmetry axis\n- press the shortcut\nSymmetry is enabled but the icon doesn't show it.\n", "Batch Renaming Subdivided Bones Bug\nOperating system: Windows 10\nGraphics card: GTX 1660\n\nBroken: 3.0\nWorked: hasn't\n\nbatch naming subdivided bones messes with names\n- Open .blend file\n- Switch to edit mode\n- ctrl f2 to batch rename, change objects to bones, type to set name, method to new, name to anything, click ok.\nthe order for the bone names gets reversed. \nif you did individual subdivisions for a bone, the names get scrambled\n\nreference: LlLCkwp\n\nthe \"fix\" was to tab out into object mode before batch naming the subdivided chain.\n\nTest File:\n[#94090.blend](T94090.blend)", "Bevel modifier - Clamp Overlap broken\nWindows 10\n\nBroken: 2.79.0-git.43a6cf1-windows64\nWorked: 2.79 RC2\n\n\n\nSee attached blend file.[clamp.blend](clamp.blend)", "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.", "Changing driven rigidbody constraint value does not invalidate cache\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nChanging driven rigidbody constraint value does not invalidate cache.\n\n[0385-5151.avi](0385-5151.avi)\n\n[#83561.blend](T83561.blend)\n\n- Open file\n- Change Y location of Empty.006 - pinned in upper editor. This should change velocity of motor of Empty.005\nThis should invalidate rigidbody cache, but it doesn't\n\n[T83561_simplified.blend](T83561_simplified.blend)\n" ]

[ "Flip names working just on one side \nWindows 10\n\nBroken: all versions (2.49b - 2.78a)\n\nFlipping names .L with .R creates a .R.001 name\n\nThe bones in the file are named Bone.R and Bone.L\nSelect them in edit mode, press W > Flip Names \nInstead of just switching sides, the new bone names are Bone.L and Bone.R.001\n\n[flipnames.blend](flipnames.blend)\n" ]

[ "Crash after Disk Cache Particle bake while set to render as path\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\nsame results on daily 3.1 build\n\nBlender crashes after finishing baking the particles to disk.\nThen proceeds to delete the baked files upon reopening the file. \n(don't know if the deletion is intended behaviour or not, but it stops you from being able to salvage the bake unless you rename / duplicate the cache folder beforehand)\n\nSeems to only happen with disk cache bake and not baking to memory. \nChanging the 'render as' setting to anything but 'path' seems to stop the crashing.\n\nOpen file, bake the particle system\n[Particle Bake to DiskCache Crash.blend](Particle_Bake_to_DiskCache_Crash.blend)", "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)", "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", "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)", "Cycles: point cloud geometry improvements\n[D9887: Cycles: pointcloud geometry type](D9887)\n\nImprovements:\n- [x] Point Info node with radius, position, random\n- [ ] Backfaces are ignored (like curves), which means e.g. volumes inside points don't work.\n- [ ] Render as normal or ray oriented disc (see [D9887](D9887)#289012, [P2125](P2125.txt))\n- [ ] Baked shadow transparency support like hair? But must be optional since texturing alpha across the sphere/disc is useful.", "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 by doing 2d animations\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 500 Intel 4.5.0 - Build 31.0.101.2111\n\nBroken: version: 3.6.0\n\nWhenever I draw with a line, circle, arc, curve, interpolate, and box tool, my drawings disappear and reappear and then it suddenly crash.\n- 2D animation Draw Mode\n[\nPlease describe the exact steps needed to reproduce the issue]\n\n", "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", "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", "Intermittent Segfault When Programmatically Creating Node Group\nThere have been intermittent crashes plaguing some of my addons. I think I have narrowed it down to creating node groups using the Python API. Specifically, to connecting something to a new node output.\n\nEnclosed [ldo_node_crash.py](ldo_node_crash.py) is a simple script that seems to reliably reproduce the problem for me; I hope it does for you, too. Open it in, or paste it into, Blender’s text editor, and run with ALT-P. I set the loop to run for 10 iterations, but for me, so far, it has always crashed before that.\n\nI am currently normally running Blender 2.82 on Debian Unstable AMD64; I tried a Blender build from the latest master branch, and the crash happens there, too. The backtrace looks like this:\n\n```\nblender-build-latest-debug/bin/blender(BLI_system_backtrace+0x26) [0x8257e79]\nblender-build-latest-debug/bin/blender() [0x2a09cfc]\nblender-build-latest-debug/bin/blender() [0x2a09efc]\n/lib/x86_64-linux-gnu/libc.so.6(+0x3b7e0) [0x7f5c97ff07e0]\nblender-build-latest-debug/bin/blender() [0x3919d1c]\nblender-build-latest-debug/bin/blender() [0x3919e13]\nblender-build-latest-debug/bin/blender(node_connected_to_output+0xf6) [0x391a0a6]\nblender-build-latest-debug/bin/blender(ED_node_tag_update_nodetree+0x41) [0x390df93]\nblender-build-latest-debug/bin/blender() [0x321f7c6]\nblender-build-latest-debug/bin/blender(NodeLinks_new_call+0x98) [0x323b5c9]\nblender-build-latest-debug/bin/blender(RNA_function_call+0x47) [0x3159a88]\nblender-build-latest-debug/bin/blender() [0x334374e]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyObject_FastCallKeywords+0xd7) [0x7f5c9890c887]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(+0x6dfc3) [0x7f5c9871bfc3]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x68a2) [0x7f5c98722c42]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x92d) [0x7f5c988443dd]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(PyEval_EvalCodeEx+0x3e) [0x7f5c9884465e]\n/usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0(PyEval_EvalCode+0x1b) [0x7f5c98844e8b]\nblender-build-latest-debug/bin/blender() [0x333463c]\nblender-build-latest-debug/bin/blender(BPY_execute_text+0x39) [0x33348cc]\nblender-build-latest-debug/bin/blender() [0x3969d26]\nblender-build-latest-debug/bin/blender() [0x3969dfb]\nblender-build-latest-debug/bin/blender() [0x2ce7313]\n```", "Geometry Nodes: Simulation and Repeat nodes is work though they are muted\nBroken: version: 4.0.0 Alpha\nWorked: Never.\n\n\n\n1. Geometry Nodes tree:\n a. Add Simulations nodes.\n b. Mute both.\n2. Play animation.\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 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)", "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", "Geometry Nodes: Point Grid Primitive (3D)\n**Relevance**\n----\n\nUse-case would involve filling/instantiating geometry in a volume with uniform spacing between instances. Other volume based use-cases could also be relevant and are mentioned in #85898.\n\n\n------\n**Alternatives**\n\nGrid node can be used to resolve many use cases but current implementation is limited: \n\n - Generates a surface (mesh).\n - Only able to generate a 2D point grid. \n\nA node for creating a 3D point lattice is then both a generalization of the grid node (to 3D) and would address limitations in the intention of the grid node to generate a surface. For a surface, generating a single point or line becomes a degenerate case and the current the grid node does not support these cases. While this is being addressed in [D11772](D11772), the task also spawned a discussions which highlighted possible relevance for a including a general node for creating 3D point grids.\n\nOther options would be to include geometry instantiation in the 'Point Instantiate' node, will eventually be realized but would not rule out relevance of a 3D grid primitive.\n\n\n------\n**Related Tasks**\n\n#85898 [D11810](D11810) [D11772](D11772)\n\n\n------\n**Limitations of the proposed solution(s)**\n\nRisk of node pollution, there already exists multiple geometric primitives.\nRisk of overlap with #85898 (abandoned state).\n\n\n**Design Proposals**\n-----\n\nOne could approach this issue in multiple ways, relevant designs would be to either to facilitate math operation workflows, extend the current grid node, add a 'point grid' primitive, or a node for distributing/scattering points within a box.\n\n----\n**Construct Point Cloud primitive using math operations**\n\nConstruct PointCloud using a vector [field](60) (view over a Nx3 array).\n\n\n\nMockup notes:\n * Linspace and SparseGrid (== np.meshgrid(sparse=True)) are equivalent to iterators, they do not allocate any data buffer and has memory complexity of O(1).\n * Actual realization of how to generate 3D vectors for the PointCloud can vary.\n * Mode to convert geometry instead may or may not be relevant (i.e. position attribute from a mesh can be passed instead). \n\n\n**Pros**\n\n* Use 'Field' input to construct PointCloud(s).\n* Adaptible method, math blocks can be used to generate different shapes.\n* Users expect custom layers to be copied with the geometry.\n * Performing operations on data buffers (interchangeable with iterators) avoids association to geometry.\n * Users expect all attributes to be copied with geometry, facilitating workflow using math operations is therefor preferable and makes an explicit PointGrid node superfluous.\n\n**Cons**\n\n* Slightly reduced performance for the unique case.\n* Not as intuitive (a 3D grid is not simple to use however).\n\n\n----\n**Extending the grid node**\n\n\n\n*Option could be to replace 2D/3D with Mesh/Points, where Points option generates PointCloud geometry (in 3D). \n\n**Pros**\n\n * Consistency, a single node for generating grids.\n\n**Cons**\n \n * Node is intended to generate a mesh/surface. No other mesh primitive generates only verts (include edges for a 3D mesh grid?).\n * Generates unnecessary faces and edges when used to instance geometry, these do however provide familiar visual geometry to debug the node tree. \n\n----\n**Point Grid/Lattice primitive**\n\nA new node generating a 3D point grid. \n\n\n\n\n**Pros**\n\n * Generates PointCloud objects (no PointCloud primitive exist).\n * Point clouds do provide visual information similar to a mesh.\n * No unnecessary geometry when used with the Point Instancing node (minor optimization). \n\n**Cons**\n\n * A new primitive node with a similar, but distinct, behavior as the grid node.\n\n-----\n**Point Scatter/Point distribute volume**\n\nEssentially the same as proposed in #85898, but would implement the 'Geometry Volume' approach rather then to use volume objects. \n\nDid not make a mockup for this, would involve option of either Count/Density to determine the number of points to scatter within the box, and size of the box. \n\n**Pros**\n\n * Adaptable approach, could include options such as 'Grid'/'Lattice', 'Uniform', 'Normal', and ?.\n * Generates a PointCloud.\n\n**Cons**\n\n * Might be unintuitive for many users, extending the Grid node to include a 3D option might still be relevant.\n * Partial overlap with #85898. \n * Implementation complexity (generated geometry should ~match the density function.).\n * Similar behavior can be achieved by randomly displacing a point grid.\n\n" ]

[ "Point Density causes Crash\nOperating system: Windows 10, 64 bit, Version 10.0.17134 Build 17134\nGraphics card: 4x Radeon VII, Driver Version 19.5.2\nProcessor: Threadripper 2990WX 32-Core on X399 Chipset (Gigabyte Designare Motherboard rev 1.0)\nRAM: G.Skill Snyper 64GB (4x 16GB), 3200MhZ\n\n\nBroken: 2.80, c13e10a7404d\nWorked: Don't know, it's the first time I try using Point density in Blender 2.8\n\nWhen Cycles Viewport preview is active, Blender tends to crash whenever I change settings in the Point Density Node.\n\n- Make Start-Cube a Volume Scatter Material, don't plug anything into the Surface Output\n- Add Sphere, scale it down a bit\n- Add Point density node in the Cubes material and set it to Object Vertices\n- Set Sphere as Target Object in the point density node\n- Activate rendered preview with Cycles engine\n- Play around with the settings in the Point Density node, it won't take long until Blender crashes", "Cycles Volume-SCatter shader crashes when changing frame in preview\nOperating system: Windows 10 64bit\nGraphics card: Nvidia GTX950 OC\n\nBroken: 2.80, 1b839e85e142, 2019-04-06\n\nCycles preview crashed when changing the frame in the timeline and usign a volume scatter shader.\nIts verry semilar to previous bugs but its a way newer blender version so I reported it anyway.\n\nIt gives this error :\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7033BF42E\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7033BF42E\n\n\n**Exact steps for others to reproduce the error**[randomSmoke.blend](randomSmoke.blend)\nPlay the animation, stop\ngo in rendered view\nchange the frame (1 or 2 times) by clicking the timeline\n - > blender should crash" ]

[ "Bevel Vertex selection stops after for planar geometry\nOperating system: Windows 10\nGraphics card: NVIDIA Geforce GTX 1060 3 GB\n\n2.83.2\nBevel Vertex does not maintain the selection for planar objects. For other objects the selection is transferred onto the verts created from the Bevel.\n\nCreate a plane, circle, or any planar object/ \nIn edit mode, Bevel any amount of vertices (ctrl+shift+B) on a plane, circle, or any other type of planar geometry and try to bevel any number of the corners.", "F12 Rendering from edit mode makes multires ineffective\nOperating system: Linux Mint 19.2\nGraphics card: GTX 1660\n\nBroken: 3.0\nBroken: 2.92\nBroken: 2.80\nWorked: 2.79\n\nWhen {key F12} rendering from editmode, multires modifier is ignored.\n\n\n[throne upload.blend](throne_upload.blend)\n\n- Open file\n- you should be in editmode\n- {key F12} render, notice the multires modifier is not in effect\n- go to objectmode\n- {key F12} render again, notice the multires modifier is now in effect\n\nExpected behavior: multires should be applied in {key F12} renders no matter what mode you are in\n\n\nOriginal report:\n\nI've included a file{[F10150774](throne_upload.blend)} which demonstrates the problem, in Eevee or Cycles (on GPU and CPU). I removed all other materials and meshes (the file size was initially around 200 MB+, which isn't helping here); but you may need to add a light to see it more clearly. Rendering with the viewport in object mode provides the displacements (there are two of them); rendering from edit mode removes those displacements. (This could in theory ruin an animation if someone's unaware!)\n\nBy the Unix philosophy, the 3D viewport and the render are two entirely separate tasks, aren't they? I don't think they should affect one another in a stateful way.\n\nCurrent workaround is to consistently render from object mode. I have no idea what other viewport modes might do to the render, but it's worth looking into.", "Knife Tool produces bad geometry in certain cases (disconnected edges/vertices, overlapping faces)\nif i use tools knife i see this bug.\n\n\n\n", "Solidify cause wrong vertex selection in edit mode\nLinux-4.19.0-12-amd64-x86_64-with-debian-10.6 64 Bits\nMesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6\n\nWindows 10-10.0.19041 SP0 64Bit\nGeForce 9600 GT PCIe SSE2 Nvidia Corporation\nRadeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.83.2\nBroken: version: 2.90.1\nBroken: version: 2.91.0 Beta\nWorked: unknown\n\nIn 3d viewport, vertex selection, solid mode, X-Ray off, you cannot predict what you are selecting when using solidify:\nBlender is ignoring the X-Ray (\"Allow selecting through the items\") and is selecting, randomly, occluded items.\nHaving a very narrow clipping does not mitigate the issue.\n\nExplanation video [SelectLight.mp4](SelectLight.mp4)\n\n[#82182.blend](T82182.blend)\n\n- Open file\n- Click inside blue circle\nOccluded vertex will be selected\n", "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related.", "Bevel modifier - Clamp Overlap broken\nWindows 10\n\nBroken: 2.79.0-git.43a6cf1-windows64\nWorked: 2.79 RC2\n\n\n\nSee attached blend file.[clamp.blend](clamp.blend)", "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", "Cannot to make single user in object properties (if object is used by multiple collections)\nOperating system:\nGraphics card:\n\nBroken:\n\n\nI made a linked copy of an object (not object data!) in another collection by dragging the object from one window of the outliner to another.\nNow in object properties showing amount users equals 2:\n\n\n\nif you click on button \"make a single copy\" then nothing will happen. I am not sure but seems this UI inconsistency\n\n\nOpen the file and try to make single user to click in object property window:\n\n[make-single-copy.blend](make-single-copy.blend)", "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "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)", "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", "Text Object: D key is used for the Annotate Tool\nOperating system: Linux-5.4.0-104-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.2.0 Alpha\n\nIn the keymap preferences there is an option to use the Active Tools for shortcuts instead of the modal operation.\nIt's called \"Tool Keys -> Immediate / Active Tools\".\n\nIf this preference is used and you go into edit mode of a text object, you are unable to type in the letter `D`.\nIt will always make the Annotate Tool active instead.\n\n- Enable the \"Active Tool\" keymap preference\n- Add a text obejct\n- Enter Edit Mode\n- Type in a word with the letter `D` in it like \"Addon\" ", "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).", "UV: (investigate) Render UVs of selected object in UV Editor while in Object Mode\nCurrently, the UV Editor only works while in \"Edit\" mode.\n\nHow firm is that restriction?\n\nIt would be nice if we could view UVs in the UV editor, even in \"Object\" mode.\n\nIf would be even nicer if we could use the basic edit tools, such as move, scale and rotate on those UVS, again, even in Object mode.\n\nUVs can be generated and adjusted procedurally, but there's no good way to see them. It would be nice to allow displaying (not editing) evaluated UVs. Combined with features like visualizing overlapping faces, this could save a lot of time.\n\nThis is an *investigate* task, to see if such a thing is even possible. If we discover it's possible, we'll then need to decide if it's desirable.\n\nThanks @BlenderBob for the inspiration!\n\n", "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)" ]

[ "Knife in multiedit\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15021.1007\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nHello. I don't know is this a bug or not. But when I use knife in multiedit mode, it snaps only to active object. I think it must snap to all objects in multiedit.\n\n\n" ]

[ "Driving object scale also scales its particle instances.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nWhen scaling the object that the particles are on, everything works correctly, the particles stay at the same size they are supposed to. \n\n\nBut when driving the exact same scale variable with a driver, for some reason the particles get scaled.\nThe property has to be on another object than the particle system, when it's on the object with particle system, then everything works as expected. \n\n\n\n\n- Open attached file\n- Change the 'prop' value (particle instances also get scaled)\n- Now select the object with the particles\n- Disable the driver\n- Scale in x direction (particles stay at the same size they are supposed to)\n\nPressing \"Update Dependencies\" fixes the scale, but in my real project that is unfeasible thing to do, I have many parameters that are driven that need to be animated and clicking them all through each time I make a tiny change is not possible. Also, rendering does not always fix the scales either. \n\n[DriverPartBug.blend](DriverPartBug.blend)", "Artefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel\nWindows 7 Ultimate, 64-bit SP1\nGeForce GTX 750 Ti\n\nversion: 2.79 (sub 1), branch: master, commit date: 2017-10-10 07:26, hash: 8d73ba5, type: Release\nbuild date: Tue 10/10/2017, 10:00 AM\n\nArtefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel. The scene is lighted with 3 spots each absolute red, green and blue.\n\n- Create a texture image file with absolute 0 spots in one channel. Or use this one: \n- Create a scene with 3 spots lights, each colored with an absolute red, green and blue color.\n- Add a random object with uvs\n- Assign the texture image file to the object (Tested with Principled BSDF, Diffuse BSDF, Toon BSDF).\n- Add Diffuse Direct and Shadow pass.\n- Render, get this: \n\n**Additionnal infos**\n- Other channels render correctly\n- Scene is lighted only with direct lights, bounces are set to 0.\n- Clamping lowest values to 1 in the texture map resolves the artefact partially.\n- Also shortly tested on unix system.\n- Blender file: \n[bug_cycles.blend](bug_cycles.blend)", "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). ", "Cycles: Bump node doesn't distort normals\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 10)\nWorked: Never\n\nHeight input have no effect on bump node output in cycles.\nThe main problem, that Generated texture cordinates give seams with bump. That is why I desided to try Normal input.\n\nEevee:\n\n\nCycles:\n\n\nHere the example file.\n[WhereNormals.blend](WhereNormals.blend)\n", "3D texturing: Fix seam bleeding\n# Version 1 (abandoned)\n\nThe concept of this approach is create a list of source pixels that should be copied to other areas of the texture. By doing this the seams will be fixed. During copying the pixels can be blended with near pixels to improve quality.\n\n* Scan over all uv edges that make the bounds of an UV island.\n* Scan over pixels that are 'intersect' with the found uv edges.\n* Pixels that are already part of the PBVH Pixels should be ignored.\n* Pixels that are not part of a PBVH Pixels should be 'fixed'\n* Find a corresponding pixels that could be used as a source to fix the pixel.\n* Add the source pixel to be copied to the pixel to be fixed. This should be added to the PBVHNode of the sourcing pixel. If the pixel was changed it should be copied to the target.\n\nDuring test we decided that this solution doesn't get to the quality we want.\n\n# Version 2 (new approach)\n\n- for now the unconnected uv edges will be the same as version 1, we can in the future change this by extending the edges. I left this out of scope for now.\n- split the mesh into uv island. \n- extract the pixels of the 'original' mesh.\n- per UDIM tile create uv island map (2d array with ints)\n- dilate the uv islands until they reach each other undecisive pixels should not be solved.\n- This map is used as a mask where uv island can extended.\n- per uv island find the sharpest corner.\n- go over the 3d mesh fan of the corner and see how this fan can be extended. For now I see 3 scenarios\n - the corner is a cut (both edges are connected in 3d space). for example see uvmap of cube. In this case we should duplicate the original faces and \n - the corner connects to another edge on the same uv island. might be similar to the first case, \n - the corner connects to one or multiple uv island. In this case the geometry that isn't connected in uv space, but is in 3d space should be added in between.\n- this generates new primitices that could be extracted using the pixel extractor.\n- the newly primitives should be stored in the PBVH as the uv coords must be stored somewhere.\n- the new primitives should still be mappable to the original primitives. ", "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.", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "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", "Cycles: Persistent Data option make Point Cloud position is dirty for transformed objects\nOperating system: Linux-6.2.6-76060206-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.105.17\n\nBroken: Curent main.\nWorked: Never (3.0+).\n\nIf you turn on `Persistent Data` in cycles render settings, and change some object position properties, point cloud objects gonna be incorrect positions have on render.\n\n| Shifted point cloud. Expected. | Second result with persistent data option. |\n| -- | -- |\n|  |  |\n\n1. Create Point Cloud object.\n2. Turn ON `Persistent Data`.\n3. Try to render.\nEverything is okay.\n4. Open N-panel. Just click on point cloud position properties. No need to really change something.\n5. Try render again.\n\n", "Shader Displacement issues with dicing camera\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\n**Short description of error** \nWhen using a Dicing camera, it doesn't update on its own, you have to make a change to the shader or the mesh for the dicing to update. \n\n\n\n- Open default .blend file\n- Switch to viewport rendering.\n- Force update the viewport (as shown in the video, just click and exit any node socket value)\n", "Cycles 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", "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)", "Dependency Cycle Detected when copying objects with cloth and collision modifier\nOperating system: Windows 10\nGraphics card: Geforce GTX 1080 Ti\n\nBroken: 2.80\n\n**Short Description**\nIf you copy objects that have a collision and cloth modifier attached to them (or copy the modifiers to another object), a dependency cycle is detected. This is really frustrating once you work with 10+ objects because blender re-detects the circular dependencies on every redo/undo and project load, making you wait for a good 30 seconds to a minute depending on the complexity of the scene.\n\n1. attach collision and cloth modifier to cube in startup project.\n2. Copy the cube.\n3. check console output.\n\nThe output should be something like this:\n\n```\nDependency cycle detected:\n OBCube.001/Geometry Component/GEOMETRY_EVAL() depends on\n OBCube/Geometry Component/GEOMETRY_EVAL() via 'Cloth Collision'\n OBCube.001/Geometry Component/GEOMETRY_EVAL() via 'Cloth Collision'\nDependency cycle detected:\n OBCube.001/PointCache Component/POINT_CACHE_RESET() depends on\n OBCube/Geometry Component/GEOMETRY_EVAL() via 'Point Cache'\n OBCube.001/Geometry Component/GEOMETRY_EVAL() via 'Cloth Collision'\n OBCube.001/PointCache Component/POINT_CACHE_RESET() via 'Point Cache -> Geometry'\nDetected 2 dependency cycles\n```\n\nAlternatively you can simply open the attached blend file and check the console output. For a simple test like this, it wont noticeably slow down the project but once you copy an object a couple of times the dependency circles appear to exponentially grow and slowing things down to a halt.\n\n[bug.blend](bug.blend)\n\n", "Displacement map, wrong normals and shadows on triangle geometry\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.69\n\nBroken: version: 2.92.0\nWorked: ?\n\nExperimental Cycles displacement introduces rendering artifacts on some geometries made of triangles. The problem seem to disappear on quad geometry.\n\nOpen the attached \"displace-problem.blend\" file.\nRender an image, or enable Cycles preview in viewport.\nThe left object is made of triangles, and appears with problems.\nThe right object is made of 1 quad, and appears fine.\n\n[displace-problem.blend](displace-problem.blend)\n", "Hiding faces on a specific mesh causes random hidden edges to display in place of non-hidden ones\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.2\nWorked: unknown, but same bug occurs in 3.5\n\nWhen selecting certain faces on this mesh (see attached STL file), pressing H or shift-H to hide faces will cause a random set of floating edges to display in the hidden regions, and the visible region will display with no edges (making it impossible to see your selection in edge select mode). The set of edges is truly random, as undo / redo will show a different set of edges each time.\n\n| Here is the full mesh with an example selection | Here is the result of pressing shift-H |\n| -- | -- |\n|  |  |\n\n1. Open the attached blend file bugball.blend, and enter edit mode on the ball to see the random floating ghost edges.\n2. Press 2 and try selecting things (selections on the un-hidden faces are invisible, and the ghost edges can't be selected).\n3. Press Alt-H and Shift-H to see that a different set of floating edges appears every time.\n\nIf the blend file doesn't work, try and import the attached STL file using file -> import -> stl and observe the same behavior.\n\n" ]

[ "Displacement not using correct information for instanced object that uses Object Info Random\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.56\n\nBroken: version: 2.93.0 Alpha\n\nNOTE: Also, the same happens in Blender 2.92.0\n\nIn a scene with multiple instance objects (instanced from a collection), the **Object Info --> Random** attribute is working for the Bump node, but not for the Displacement node. Better explained with images:\n\n\n- Here, you can see that the information that the information input of the Height of both Bump and Displacement is the same. A mask showing a number, and that random number selected through a ColorRamp will be the input for both at the same time, ensuring the bump node has the same information as the displacement node.\n\n\n- Still, the bump works fine, as expected:\n\n\n- But the displacement only displaces the information assigned to the original piece inside the collection:\n\n\n\n1) Open the attached scene [Rodrigo Neira - Bug Report - Displacement not working in instances.blend](Rodrigo_Neira_-_Bug_Report_-_Displacement_not_working_in_instances.blend)\n2) Check the shader editor, and **material of ficha.005 --> material ficha_numero**\n3) If Bump only is selected for Surface displacement options, and the Bump node connected to the PBR Node --> Normal it works as expected.\n4) If Displacement only is selected for Surface displacement options, and the Displacement node is connected to the Displacement of the Material Output, the displacement only shows the original displacement of the object inside the collection.\n - > Expected behaviour: Displacement should be using the same number mask/shape as when the bump is used.\n\nNOTE: The same happens if you select Bump & Displacement in Surface displacement options of the material options. \nI think this might be a bug - couldn't find if it's a limitation of the displacement already known.\nThanks in advance!! \n" ]

[ "HDRI background shows lighting artefacts at zero strength\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nDont know if this is a Blender issue, but I encountered a few HDRI files that still show light sources despite having zero strength in the viewport shading studiolight setting:\n\nThe HDRI file is:\n[blue_lagoon_night_2k.hdr](blue_lagoon_night_2k.hdr)\n\nThe lighting comes from remaining artefacts at the spot of the lamp. Its more noticable with a bit of blur, but you can still see it without.\nSince this is only an issue for some HDRI Backgrounds I assume it has to do with those files, I dont know. Regardless, it would be nice if Blender could take care of these cases to guarantee a dark background.\n\n\n[HDRIBackgroundStrengthBug.blend](HDRIBackgroundStrengthBug.blend)\n1. Install the attached HDRI File and set it as background.\n2. Change the strength setting for the Viewport Shading to zero.\nProblem:\nThe background lightens the scene at zero strength with the remaining artefacts.\n\n", "mask visibility in sculpt mode using shape keys or generative modifiers\nOperating system: Windows 10\nGraphics card: nvidia 1060 Ti\n\n2.8 RC2\n\nIf you have a mesh with a mask and create a shape key, the mask will be no longer visible, still active but not visible.\n\n\n- Add UV Sphere\n- Sculpt mode\n- Paint a mask\n- Create shape keys\n\n\nOr from the default startup:\n- in sculptmode, `Mask` > `Invert Mask` (default cube should turn dark)\n- strokes dont have an effect now (this is expected)\n- add **any** generative modifier to the default cube (e.g. triangulate)\n- back in objectmode, save the file\n- reload the file\n- enter sculptmode\n- no mask is visible\n- strokes dont have an effect now (this is confusing since you are not aware masks prevent an effect since you dont even see the masks)\n\n(note we have the option `Use Deform Only` in sculptmode which might be exactly for that purpose, still not being able to use masks with generative modifiers should be more clear)", "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", "Artifacts when composing render passes with SSS, EEVEE and SSR\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0 Beta\nWorked: I'm not sure this behavior is new. Blender 3.2 displays the same behavior.\n\nWhen compositing render passes that have been generated using EEVEE, and an object has Subsurface Scattering enabled, and Screen Space Reflections are enabled, and Half Res Trace is disabled, artifacts are generated. The combined pass, however, correctly renders.\n\n\n*What I get (demo file included below)*\n\n\n*What I should get*\n\nNote: if Half Res Trace is enabled, the problem disappears.\nAlso, if Cycles is used to render the same scene, the passes do not display these artifacts.\n\n\n\n\n- Create a file that uses EEVEE as renderer.\n- Enable Screen Space Reflections. Disable Half Res Trace.\n- Create an object with Subsurface Scattering\n- Enable the following necessary render passes: Diffuse Light, Diffuse Color, Specular Light, Specular Color\n# In compositing, mix as follows the passes: multiply Diffuse Light and Diffuse Color; multiply Specular Light and Specular Color; add them.\n\nChanging the roughness can make the effect more extreme. Having a very contrasty roughness map exacerbates the problem:\n\n\n*a contrasty roughness map*\n\n\n*the render showing the problem more extremely*\n\n\n*how it should be*\n\nThe final result should be akin to the one posted above. You can compare the composited result with the one that is already combined: the combined one does not display the issue. Using Cycles for the same setup also works without problems.\n\nThe inconsistency of results mentioned above makes me believe this is a bug, and hence my report.\n\nDemo file: [sstest.blend](sstest.blend)", "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", "bake operator reports uninitialised image that isn't even in use in the shader..\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\ncan't bake due to strange error\n\nopen blend file\nselect object\nselect the baked image texture node in the shader editor\nclick bake in the render setting (leave settings as is)\n\nstrange error pops up saying \n\"uninitialised image \"nightmare0134.png\" from object 'pavement.002'\n\nThis image isn't even in use by the shader.\n\nPS, it seems intermittently not possible to paste screengrabs into this new bug reporter. Also, how to do bullet points and embed video?\n\n", "MNEE shadow/caustic do not respect transparency (dark spots)\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**Short description**\nIf refractive shader mixed with transparent and body is mostry transparent, MNEE still produce very dark spots of shadow.\nLike this:\n\n\nFile:\n[test caustic.blend](test_caustic.blend)", "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", "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", "EEVEE-Next: Known Issues\nThis task lists the minor missing features that are known for not yet working with EEVEE-Next.\n\nPriority of each task needs to be assessed and assigned.\n\n# LookDev\n- [ ] camera world alignement isn't working.\n- [ ] blur background isn't working.\n- [ ] diffuse contribution isn't taken into account.\n\n# Shadow\n- [ ] big performance bottleneck caused by rendering method\n\n# Hardware support\n- [ ] Metal backend doesn't support shadow rendering and GI baking yet", "Inconsistent color space baking to float and byte images\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14742 Core Profile Context 21.8.2 27.20.22025.1006\n\nBroken: version: 2.93.6\nWorked: ---\n\nIn blender we can create an image with 32 bit resolution (See image):\n\n\nThe new 32bit image can be used for baking in order to obtain a normal map.\nThis map works perfectly until saved in PNG (16bit or 8bit).\nInterestingly you can bake directly on a 16bit image and the resulting image works even if it is saved in 8bit.\n\nHere is a file where I put different pixel resolution combinations on textures saved in PNG:\n[TesteNormal.blend](TesteNormal.blend)\n\n\n\n1 - Bake a normal map image with 32 bit option enabled. (see the pic \"sample3.jpg\")\n```\n A simple cube can be used, no need to add any detail.\n```\n2 - Save the image as PNG in 8 bit or 16 bit.\n3 - Create a material and connect the saved baked normal map image to the normal map node. \n```\n Change color space option to \"non-color\" \n```\n4 - Observe the object becomes dark in rendered mode in Eevee or Cycles. \n\n[Teste_Normal_Textures.blend](Teste_Normal_Textures.blend)\n", "Regression: Boolean Modifier Distorts UVs\nBroken: Blender 3.2.2 Official\nBroken: 2.93\nWorked: 2.92\n\nBroke with a3f091d7ce\n\n\nBoolean modifier distorts UVs of cutter object. In the attached screenshot and blend file. There are two cutters objects of roughly the same shape, one of them works correctly and the other doesn't.\n\n\n\n[tmp_2.blend](tmp_2.blend)", "Dithering is not applied for Texture Baking\nDebian amd64, Radeon HD with fglrx\n\n\nBroken: current GIT, also many previous versions were affected in case of BI Baking\n\n\nDithering is not applied for Texture Baking, resulting in banding artefacts.\nCycles Baking and BI Baking are affected.\n\nAlso when saving a 32 bit float image as 8 bit PNG, no dithering is applied (despite Dithering was set to 1.0, and \"Save as Render\" was activated).\n\nA .blend file is attached. Click on \"Bake\" and wait a few seconds. After baking is finished you should see the banding artefacts in the dark-gray regions.\n\nThanks\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.", "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" ]

[ "Baking Indirect Lighting is broken\nOperating system: Windows 11\nGraphics card: Nvidia 1660S\n\nBroken: 3.2 and newer\nWorked: 3.1.2\n\nCaused by c722993ef1\n\n\nBaking indirect lighting is currently broken and seems to simply ignore any light sources in the scene.\n\n\n- Open attached .blend file\n- Bake texture" ]

[ "Black Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0\n\nBlack Artefacts in EEVEE on Transparent BSDF when using Alpha Hashed for Blend mode and Camera Depth Of Field, if Shader Color is not pure white (similar problem with Layer Weight)\n\n**Exact steps for others to reproduce the error**\n- Open attached file (Just a simple box (can be a plane) with Transparent BSDF. Camera' distance or depth of focus influences the result. Attached pictures in Image Editor from a real case).\n- Press F12 to render\n[transprarent_shader_artifacts_with_camera_DOF1.blend](transprarent_shader_artifacts_with_camera_DOF1.blend)\n\n\n", "HDRI background shows lighting artefacts at zero strength\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nDont know if this is a Blender issue, but I encountered a few HDRI files that still show light sources despite having zero strength in the viewport shading studiolight setting:\n\nThe HDRI file is:\n[blue_lagoon_night_2k.hdr](blue_lagoon_night_2k.hdr)\n\nThe lighting comes from remaining artefacts at the spot of the lamp. Its more noticable with a bit of blur, but you can still see it without.\nSince this is only an issue for some HDRI Backgrounds I assume it has to do with those files, I dont know. Regardless, it would be nice if Blender could take care of these cases to guarantee a dark background.\n\n\n[HDRIBackgroundStrengthBug.blend](HDRIBackgroundStrengthBug.blend)\n1. Install the attached HDRI File and set it as background.\n2. Change the strength setting for the Viewport Shading to zero.\nProblem:\nThe background lightens the scene at zero strength with the remaining artefacts.\n\n", "The 3d cursor looks very dim on AMD cards with the Mesa driver.\nOperating system: Gentoo Linux\nGraphics card: AMD Vega64\n\nBroken: All current Blender versions (2.93 to 3.5)\n\nThe 3D cursor in the viewport seems to be drawn with transparency.\nHowever this is only an issue on AMD cards it seems.\nIt started happening 4-5 months ago, so this is most certainly a driver issue.\n\nOpen the default cube scene and observe that the 3D cursor looks very dim:\n", "Dynamic Indirect light cache\nThe idea would be to have a multiple level cache that stores a voxelized version of the scene to render the irradiance points.\n\nEach voxel would be linked to a set of surfel (surface elements) that stores color and normal of the surface.\nEach time the lights in the scene changes, the voxelized version is updated and propagates the change to the irradiance points.\n\nThis means having a list of surfel per voxel (say 6, 8) and a list of voxel per irradiance points.\nThis would be a mix of The Division dynamic indirect lighting [link]] and Mc Guire raytraced irradiance probes [[http:*jcgt.org/published/0008/02/01/|link](https:*www.gdcvault.com/play/1023273/Global-Illumination-in-Tom-Clancy).\nThis feature might be limited to hardware that supports compute shaders.\nThis is not a trivial feature and needs a lot of R&D.\n\nEstimate : 4 weeks\n", "Shading Problem in Eevee in Top Orthonographic View When the Scale is not Applie Yet\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\nWorked: Never\n\nThere is a strange shading problem in Eevee that happens when the object is scaled and the scale is not applied yet. The light needs to be at certain angle to make it appear. The problem also has to do with the topology of the mesh, it is hard to notice with just one face (though still there as you can see it flickers when you scale it), but it becomes obvious when subdivided.\n\n\nBased on the attached .blend file \nOpen my .blend file, you can see there is a circle and a light in the scene. You can see the problem by turn on render view. The light is placed at certain angle to make the problem show. \nThe circle was created using the below steps:\n\n(0. delete or hide my circle)\n1. Shift A and add a circle\n2. Lower left corner menu, the fill type choose Ngon\n3. Scale it up a little, don't apply the scale, and you can see it flickers during the scaling process\n4. Edit mode, hit the a key to choose all, hit the i key to inset the circle, and then inset it again, and see it has to do with the topology\n5. Object mode, ctrl a apply the scale, the problem is gone, it has to do with the scaling.\n[Orthonographic Top View Shading Problem.blend](Orthonographic_Top_View_Shading_Problem.blend)\n\n", "Multiscatter GGX Glass Shader - In a certain range of roughnesses, specular reflections darken/disappear.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using the Glass and Glossy BSDF with Multiscatter GGX and a roughness of around 0.02 the specular reflection somehow breaks, which is visible as excessive darkening.\n\nIn the images below, I have applied a gradient roughness texture starting at 0 at the top and 1 at the bottom. As you can see in the Multiscatter GGX there is a dark \"seam\" near the top of image that isn't present with GGX and probably shouldn't be there.\n\n|||\n| -- | -- |\n|Multiscatter GGX|GGX|\n\n[Multitest.blend](Multitest.blend)\n\nIn this test file only the specular reflection is visible. The gradient going into the roughness input goes from 0 at the top to 1 at the bottom. As can be seen there is a sudden dip at a roughness value of around 0.02. It is also visible without the gradient when simply entering values of around 0.02 into the roughness input.\n\nThis problem is exclusive to Multiscatter GGX and does not occur with other microfacet distribution models.\nEdit: The same problem has been found with the Glossy BSDF. \n\nThank you and have a great day!", "Strong emissive materials bleeding through grease pencil objects\nOperating system: Win10 Home 64\nGraphics card: rtx3070\n\nBlender Version\nBroken: 2.83, 2.90, 2.91, 2.92, 2.93, 3.0, 3.1\nWorked: N/A\n\nExact steps to reproduce the error:\n\nGive default cube an emissive material with strength ~50 or so and put any grease pencil object in front of it in Rendered view. This artifacting carries over into the actual renders. \n\n\n(I think it's an opacity issue, because creating a duplicate of the grease pencil on top of itself (Array modifier with 0,0,0 offset) covers the emission glitch up.)\n\n**Steps to Reproduce**\n- Open .blend file\n- Render in viewport\n\nTest File:\n[#94004.blend](T94004.blend)\n\n", "Render difference with big quad light and ray visibility\nall vendors\n\nBroken: 1ebc14064b\nWorked: 2.79a\n\nsome parts of principled shader render very glossy in latest master\n\nOpen attached file [bug principled v2.blend](bug_principled_v2.blend), render. \nIn 2.79a you get this (correct):\n\nand in latest master this:\n\nNote that I replaced wood tex by voronoi in file, but differences are also obvious.", "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\n", "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", "Ambiant Occlusion cycle node gives artecacts when the mesh has Custom Split normals\nOperating system: win 10 \nGraphics card: Geforce RTX 2070\n\n**Blender Version** \nBroken: 2.90.0 alpha\nWorked: N/a\n\nOn my mesh , with custom normals, (i applied a withged normal modifier) \nI had to clear the custom split normal date to get rid of artefacts given with the Ambiant Occlusion node in Cycles\n\n\nAlso seen with smooth shader:\n\n\nAnother way to have this bug (without Custom Split normals): \n- Create a suzanne.\n- Smooth the normals \n- Use Cycles render. \n- Add an Ambient occlusion node and plug it on an Emit shader\n[cycles_ao_smooth_normals_bug.blend](cycles_ao_smooth_normals_bug.blend)", "Inconsistency between CPU and OptiX GPU when using OSL hash function \nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken version: 3.5.0 Alpha\nWorked: NA\n\nWhen using the Open Shading Language \"hash\" noise function there is an inconsistency between the CPU and OptiX GPU implementation. The most noticeable is that the OptiX output is grey scale while the CPU implementation has colour.\n\n|CPU|OptiX|\n| -- | -- |\n|||\n\n1. In user preferences change your Cycles rendering backend to OptiX (requires a OptiX compatible GPU)\n2. Download the attached blend file and open it.\n3. Enter the rendered viewport and compare the results with CPU rendering and OptiX GPU rendering.\n\n[OptiX CPU OSL Hash Inconsistency.blend](OptiX_CPU_OSL_Hash_Inconsistency.blend)", "Glitches on Video Sequence timeline\nOperating system: Linux 5.9.11\nGraphics card: Intel Haswell\n\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nShowing glitches on video sequence timeline when area of Video Sequencer resizing\n\nSteps shown on video\n\n[2020-12-02_15-19-26.mov](2020-12-02_15-19-26.mov)", "Viewport material is darker than the rendered version\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 10.18.14.5067\n\nBroken: version: 2.82 (sub 3)\nConfirmed in 2.81 release\n\n\nThe material consists \na transparent shade mixed with a translucent shade, mixed with an emission shade with\nfrenel node multiplied with a noise texture as the factor\n\nThe sample sizes are the same\n\nJust render\n\n\n[necro_core_reduced.blend](necro_core_reduced.blend)", "Inconsistencies in GPU subdivision info message\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\nThis feature is introduced with 4d3bfb3f4195ac879b7330e981829122b2633e93\n\n1. Message does not update accordingly when...\n\n1-1. enabling and disabling GPU Subdivision in the preferences\n\n\n\n1-2. changing modifier visibility\n\n\n\n1-3. enabling and disabling auto smooth\n\n\n\n2. I don't know the technical details, but I feel that \"Using both CPU and GPU Subdivision\" contradicts to what the tooltip for GPU Subdivision says (\"Enable (...) for the last subdivision subsurface modifiers in the stack\").\n\n(On a related note, I think [documentation](viewport.html#subdivision) could be more descriptive about GPU Subdivision than just \"Under certain circumstances\".)\n\n" ]

[ "CPU + GPU render precision differences for small, far away area light\nOperating system: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\nBroken: version: 2.81 (sub 8)\nWorked: (optional)\n\nThis was recently reported in this thread : \n2\n\n I can at least say, that when using small area lights below a size of 1 (e.g. meter), and it’s getting darker (the light source is far away from the object) you can clearly see this problem: CPU renders the tiles darker than the CUDA GPU.\n\n\n\nCreate a new scene with the cube, remove the default light, create an area light, resize it to lets say 10% (or 1%… the smaller the bigger the effect) and rotate it that it lights the default cube.\nHere is a .blend that reproduce the issue :\n[TileProblem.blend.blend](TileProblem.blend.blend)\n\n" ]

[ "Clearing followed by setting a listbox created by UILayout.prop_search while keeping the mouse on the listbox crashes Blender\nOS: Ubuntu 16.04 x86_64\nGfx: Intel HD Graphics 530 (Skylake GT2) (driver: GL 4.5 (Core Profile) Mesa 17.3.0-devel)\n\nBroken:\n- 2.79-42a562496b5-linux-glibc219-x86_64 (latest build)\n- 2.79-5bd8ac9abfa-linux-glibc219-x86_64\n- 2.76b\n\nClearing followed by setting a listbox created by UILayout.prop_search while keeping the mouse on the listbox either crashes Blender or leads to unexpected behaviour.\n\nConsistently reproducible.\n1. Open the default startup blender file\n2. Open a textblock and paste and run the code provided in Appendix A\n3. In the 3D viewport, press SPACE and type \"Crashable\", then select \"Crashable Operator\" => at the right an operator panel will be drawn\n4. In the operator panel, click on the field next to \"Obj:\" and select e.g., \"Camera\" from the list\n5. Click the X sign right to \"Camera\" while keeping the mouse pointer pointed at the field\n6. Click again on the field\n\n**Expected behaviour of step 6.**\nStep 6 should be able to behave as step 4, i.e., one should be able to again select something from a non-empty list\n\n**Observed behaviour after step 6**\nOne of following, probably depending on how Blender's memory was allocated:\n - Crash\n - The list is empty\n\n**Appendix A**\n\n```\nimport bpy\n\n\nclass CrashableOperator(bpy.types.Operator):\n bl_idname = \"object.crashable_operator\"\n bl_label = \"Crashable Operator\"\n bl_options = {'REGISTER', 'UNDO'}\n\n obj = bpy.props.StringProperty(name=\"Obj\")\n\n def draw(self, context):\n self.layout.prop_search(self, \"obj\", context.scene, \"objects\")\n\n def execute(self, context):\n return {'FINISHED'}\n\n\ndef register():\n bpy.utils.register_class(CrashableOperator)\n\n\ndef unregister():\n bpy.utils.unregister_class(CrashableOperator)\n\n\nif __name__ == \"__main__\":\n register()\n```\n\n**Terminal output upon crash**\n\n```\n$ blender\nRead new prefs: /home/elias/.config/blender/2.76/config/userpref.blend\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n**Contents of \"blender.crash.txt\"**\n\n\n```\n# Blender 2.76 (sub 0), Commit date: 1970-01-01 00:00, Hash unknown\nbpy.context.area.type = 'TEXT_EDITOR' # Property\nbpy.ops.text.run_script() # Operator\nbpy.ops.object.crashable_operator() # Operator\nbpy.ops.object.crashable_operator(obj=\"Camera\") # Operator\nbpy.ops.object.crashable_operator(obj=\"\") # Operator\nbpy.ops.object.crashable_operator(obj=\"\") # Operator\n\n# backtrace\nblender(BLI_system_backtrace+0x30) [0x1361b10]\nblender() [0x97a98e]\n/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f242a7894b0]\nblender(rna_ID_refine+0x4) [0x11bac84]\nblender(rna_pointer_inherit_refine+0x66) [0x11a9af6]\nblender() [0x1273ae2]\nblender(RNA_property_collection_begin+0x15c) [0x11b161c]\nblender() [0xb654ae]\nblender(ui_searchbox_update+0x6a) [0xb7514a]\nblender() [0xb57089]\nblender() [0xb59f6d]\nblender() [0xb5a027]\nblender() [0xb5d7ad]\nblender() [0xb5ebe6]\nblender() [0xb5f433]\nblender() [0x985e81]\nblender() [0x986251]\nblender(wm_event_do_handlers+0x5f6) [0x9868e6]\nblender(WM_main+0x18) [0x97cfd8]\nblender(main+0xef4) [0x95ce04]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f242a774830]\nblender(_start+0x29) [0x97a2b9]\n```", "crash 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", "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", "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", "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 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", "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", "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 crashes as soon as an image texture is plugged in the material BSDF node\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\nSee attached log for more detail\n\nBroken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions\nWorked: ??? The earliest available build, 2.93.18, also causes the same crash\n\nThe second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes\n\n**Similar tickets**\n#76193\n#76377\n\n1. Start Blender.\n2. Create new default file.\n3. Select the default cube.\n4. Switch to Shading workspace.\n5. Add Image Texture node.\n6. Create new image or select an existing one.\n7. Plug Color output to the Base Color input of the Principled BSDF node.\n8. Watch Blender shut down.", "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", "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", "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", "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)", "bpy.ops.fluid.free_all() can cause a crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\npython script to free and re-bake smoke can cause a crash in 2.9x\n\nThe description of this bug is clearly documented along with the example blend file in [this blender stackexchange question ](python-script-to-bake-two-fluid-domains-aborting-cmd-line).\nIf I comment out the lines that contain:\n\n```\nbpy.ops.fluid.free_all()\n```\n\nin the following script, and instead manually free the bakes, all is fine. Otherwise the application crashes with console messages like:\n\n```\nUnable to remove directory\nor\nUnable to delete file\n```\neven if run from cmd line as Administrator\n\n\n```\nimport bpy\n\ndomain = bpy.data.objects['Smoke Domain Purple']\ndomain.select_set(True)\nprint(\"free Purple\")\nbpy.ops.fluid.free_all()\nprint(\"bake Purple\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\ndomain = bpy.data.objects['Smoke Domain Blue']\ndomain.select_set(True)\nprint(\"free Blue\")\nbpy.ops.fluid.free_all()\nprint(\"bake Blue\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\n```\n\n[dual smoke.blend](dual_smoke.blend)\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" ]

[ "Crashing after making boolean to objects with a stack of materials. \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.3\n\n[Crashing after making boolean to objects with a stack of materials. ]\n\n**Exact steps for others to reproduce the error**[bug_8.blend](bug_8.blend)\n[I make a boolean difference operation. After this Blender crashes. ]\n\n", "Boolean modifier crash\nOperating system: Windows 10\nGraphics card: GeForce 1060 GTX 6Gb\n\nBlebder: 2.92.0\nDate: 2021-02-24 16:25\nHash: 02948a2cab44\nBranch: master\n\nCrashes when Boolean modifier used.\n\nPick object B.\n\n[crash.blend](crash.blend)\n", "Crash to desktop with boolean modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 3.0.0 Alpha\nBroken: version: 2.93.2\nWorked: 2.92 (`2021-02-24`)\n\nPicking the target object for the boolean modifier crashes to desktop\n\n\n- Add Boolean Modifier\n- Pick object\n- Crash\n\n\n[2021-08-21 10-15-22.mp4](2021-08-21_10-15-22.mp4)\n\n[crash2.blend](crash2.blend)\n\n" ]

[ "Stroke overlay when erasing\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070 Ti\n\nBroken: (example: 2.80, 66684bdff30f, master, 2019-07-05)\n\n\nThe new alpha overlap stops working, when you erase somethin of that stroke.\n\n \nOpen a new project create a blank stroke object draw something try to erase it", "Cycles vertex color bump map banding \nOperating system: Win10\nGraphics card: GTX 1070\n\n2.79b release\n\nUsing vertex colors in cycles material as a mask for bump/normal texture causes banding/hard edges in render.\n\nBanding of vertex color is also visible when using it as a color for shader. \n\nIt might have something to do with the fact that vertex colors are represented in 8-bit sRGB values but on the other hand it renders as expected when using it as a mask for example for mix shader node. But the bump doesn't look correct in that case.\n\n\n[vertex_color_mask_problem.blend](vertex_color_mask_problem.blend)", "Reflection Plane + SSR produce fuzzy outlines\nIntel i9-10850K, 32 Gb RAM, NVidia GeForce GTX 1070 8GB\nWindows 10 x64\n\nBroken: 2.93, 3.0\nWorked: 2.92\n\nReflection Plane produces thick fuzzy outlines against the background when Screen Space Reflections is also enabled, it reacts to Half Res Trace option which makes it a little bit thinner but it's still very visible which didn't happen in 2.91 where the same outline also exists but is barely visible.\n\n\nOpen provided file, enable Rendered mode and observe the result in the mirror, disable Screen Space Reflections and fuzzy outlines will disappear.\n[Fuzzy_Reflection_Outlines.blend](Fuzzy_Reflection_Outlines.blend)\n\n\nSorry, I haven't seen the reply in my other report before posting this but anyway, is there any way to reduce this? This problem is VERY noticeable and causes a lot of problems.", "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "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", "No color drag'n'drop in Viewport Shading popover\nOperating system: Linux Mint\nGraphics card:\n\nBroken:2.81-a856c5eccffb-linux-glibc217-x86_64\n\n\nNo color drag'n'drop in 3d view solid (and wireframe) shader options dropdown.\n\nOpen default scene,\nclick on solid shading,\nopen the shader options dropdown,\nunder \"Color\" choose [Single],\nunder \"Background\" choose [Viewport],\ntry to drag the color of one to the other.\n\nAlso not works in wireframe shading dropdown.\n\n", "Color Picker in texture mode sampling incorrect values (sample merged OFF, sampling from another object)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.92.0\nWorked: ?\n\nThe color picker in \"Texture Painting\" mode seems to only sample the correct color when the look is set to **None**under the **ColorManagement->Look->\"None\"** and if the Viewport **Shading->RenderPass** is set to **DiffuseColor**.\nOtherwise, the color values are simply wrong, they are either too bright or too dark.\n*In the provided scene the issue is quite clear, but in more complex scenes with more complex lighting and post-processing the sampling becomes **completely** broken giving values that aren't even close to what is shown on screen.*\n\n**Expected Behaviour**\nThe way I would expect the color picker to work is that it either samples the color as **I** as a user see it on my viewport.\nOr that it samples the source texture at the pixel I am sampling without any extra lighting applied to it. *( This should be easily toggleable behavior but that is more of a feature request )*[ColorPicker_WrongSampling.blend](ColorPicker_WrongSampling.blend)\nRight now it seems to do neither.\n\n\n - Open attached .blend file.\n - Select the black cube and enter Texture Paint Mode.\n # Sample the color from the other cube *( I recommend sampling the green since the meshes are close to each other making it easy to see the color difference )*.\n\n\n", "Regression: Themes: Highlight color in the text menus\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6.2\n\nThe highlight color is not longer adjustable by the Selected color in the User Interface / Menu Item panel. But changes with the Inner color. This breaks theming.\n\n\n- Enter Preferences. \n- Navigage to Themes tab, User Interface, Menu Item panel.\n- Play around with the Selected and Inner color\n\n", "Error code in NodeShader Color default_value\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\ncode in files\nthe color default_value require a 3-dimensional array , but when specified as a 3-dimensional array, the red channel is missing\n\n\n", "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: Mismatching data types connections work differently from other node editors\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\nFloat math node overrides color data, even though it is muted. Same setup works in shader editor without problems.\n\nOpen file and activate *Viewer* in GN. Expected result: colored output (judging by shader area behavior)\n\n", "Exchanging a color in Grease pencil from a color attribute is bugged\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 3.4.1\n\n**Short Description**\nExchanging a color in Grease pencil from a color attribute is bugged\n\n- Go into 2D animation\n- Draw a shape with a fill color using a color attribute\n- Change color attribute and draw another fill stroke\n- In materials tab create a new fill color\n- Assign that color in edit-mode to the shape to replace color attribute. \nIt doesn't look like it got applied. Go into viewport shading with material view and the assigned color is there. Pressing F12 shows the color that is supposed to be overwritten.[Color error.blend](Color_error.blend)", "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", "Quad view viewport background color is not respected\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\nQuad view viewport background color is not respected\n\n- inspired this task by post and instructions:\nXL1v/ Viewport - Black and White template/style (not only black)\n\nThere is limitation, where user trying change view by NUMs to get FRONT, REAR, SIDE individually per square - by this we doing 2 quads to reach TOP, DOWN view for objects.. but alwyas user is limited to switch other views by NUMs or gizmo. I think that this blockade is stupid.\nfFdbbc/ Quad view needs improvement\n \n\n[#89337.blend](T89337.blend)\n\n1) Open file\nBackground color in ortho view is gray, even though viewport background is not.\nWhen `use_box_clip` property is disabled, background color is correct.\n", "Find solution to unify color picking methods with options for sample space\nReopened as, though the initial issue is invalid, the current solution, as it is, is problematic.\nThe sample_color paint operator {key S} has a problem with discoverability and is separate from both the general UI color picker and the sample tool. This needs a better design solution.\n\n**Old Description** (resolved by sample_color operator)\n\nRight now all color picking is using the display space, which usually makes it (almost) impossible to accurately pick colors from an image that is not sRGB for texture painting.\nSimilarly, for texture painting in the 3D viewport the picked color is that after shading and display transformation. This can be useful, but it should be optional. In a lot of cases the user wants to pick and draw a color from within the same image texture, without any additional color space conversion.\n\nThe View mode of the image editor already has a sample tool, which has the functionality to show the color data in image space without additional color management. So simply using this tool in paint mode for picking color with the option to select the color space would already be a huge benefit.\n\nFurther, having a similar tool for 3D texture painting would be even better, but I assume that this might have more difficult implications for the implementation. Tackling this for the image editor first using the Sample tool, might me a good trade-off for investing a small amount of work for maximum impact.\n\n[color_picker_behaviour-2021-03-02_15.50.34.mp4](color_picker_behaviour-2021-03-02_15.50.34.mp4)\n[non-color_picker.blend](non-color_picker.blend)" ]

[ "UI Themes: Grid color affecting axis color\n2.81a, 2.82 Beta.\n\n**Description**\nIn 3D View, the grid color overlays the XYZ axis colors, so it's impossible to set the colors I want to the XYZ axis. \nThis even happens if the grid color is set to transparent.\n\n[0020-1556.mp4](0020-1556.mp4)\n\n- Go to preferences -> Themes -> User Interface -> Axis & Gizmo Colors\n- Change X and Y axis color to black RGB(0, 0, 0)\n- Go to preferences -> Themes -> 3d View\n- change Grid color/alpha.\n\nX and Y axis color will be affected" ]

[ "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)", "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", "Selected Objects render state (hidden in renders) causes baking of black images (also these are visible in renders after baking, setting is not as it was before)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0\nWorked: Cannot find any - tested back to 2.81\n\nIf rendering of the selected object is not enabled, then the baking will fail with a black image created.\nStrangely the rendering icon for this object will be automatically turned-on in the outliner - if you hover your mouse over.\nBaking will still fail - even though the icon now shows that rendering is enabled.\nTurning off render, then turning it back on again will fix the problem so that baking will now work.\n\nLoad the blend file attached (or use your own scene set-up for baking).\n[Bake selected to active has black image.blend](Bake_selected_to_active_has_black_image.blend)\nClick on Bake to confirm that the baking is successful.\n\nDisable render for the Selected object.\n\nClick on Bake again, and a black image will be created.\n\nNote that the Selected object still has rendering disabled.. Move your mouse into the Outliner above the render icon, and observe that rendering for the Selected object automatically becomes enabled.\n\nClick on Bake again and observe a black image is still created.\nDisable rendering for the Selected object, then enable it again.\nClick on Bake again and the baking will be successful.\n\n\nObservations:\n1) If rendering is disabled for the active object, then this error is shown.\n\n2) The bake duration is the same whether the rendering is enabled for the selected object or not. (Mine was taking a 2.5 minutes, and it took a long time to figure out what the problem was.)\n3) Saving the blend file and reloading fixes the problem - the state is persisted as render==enabled.", "persisting issue: MacOS, Blender's system device usage rights (info.plist) add camera & mic usage descriptions\nOperating system: MacOS (13.2.1) \nGraphics card: any\n\nBroken: (All Blender addons that would need external peripheral like camera or microphone access, will cause Blender to CRASH, because of MacOS)\nWorked: (it's a MacOS dependent issue (since maybe macOS 12?)\n\n*\n\"Termination Reason: Namespace TCC, Code 0\nThis app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an com.apple.security.device.camera key with a string value explaining to the user how the app uses this data.\"*\n\n\nInstall an anddon that would need camera / microphone access. After checking the checkbox in blender addon menu, Blender crashes (or at the point that addon is running code that would need such peripheral. Nowadays you cannot add it manually and this needs to be addressed globally.\n\nFIX:\nglobally add info.plist usage rights for camera, mic and other widely used peripherals for blender's MacOS version, since the current state of MacOS, doesn't allow addon's to access any of those, and it really hinders the blender as a core, those of course aren't used if not needed, but at the moment addon developer cannot have any modules that use any of those without MACOS causing the blender to literally crash. I hope this could be corrected asap. Before it was still possible to manually grant access to applications via macos settings, but alas, its not anymore possible.\n\n", "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)", "Adaptive Domain creates lines in smoke\nOperating system: Win 10\nGraphics card: Dual RTX Titans\n\nBroken: Blender 2.82\n\nWith adaptive domain enabled, noticeable horizontal (and sometimes vertical) lines appear in the smoke\n[weird lines.mp4](weird_lines.mp4)\n\nSimple blend file: \n\n - Create a large box and set it as a gas domain.\n - Create a small object as the Flow (both 'smoke' and 'fire' reproduce it)\n - Put the flow object near the bottom of the domain\n - Enable Adaptive Domain\n - Bake\n - You should see lines like this: \n # Turn off adaptive. Not only will the smoke move faster creating a totally different looking simulation (which is problem in itself) but the lines will be gone: \n\nIt's most noticeable when the domain is large, and the adaptive box is only a small portion of it.\n\nIncreasing the adaptive margin to 24 helps somewhat, but it's still there. Any higher and it defeats the purpose of adaptive - baking takes as long as just turning it off.\n\nSample blend:\n[adaptive bug2.blend](adaptive_bug2.blend)", "Crash on deleting driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken: (\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\n)\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. I don't know where that driver on Location X came from. The original didn't have one. I then wanted to delete that driver. After deleting it and moving the current frame blender crashed.\n\n- Load attached file\n- Delete driver of 'Location X'\n- Press Cursor keys Left/Right a few times till crash.\n[crash.blend](crash.blend)", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Blender Mantaflow gas fire and smoke simulation - Adaptive Domain problem!\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nTHE SAME BEHAVIOUR FOR Blender versions 3.3.1 and 3.4.1.\n\nAdaptive Domain from time to time shrinks as intended, but those shrinks are sometimes visible.\n\n\n- Open [file](https://projects.blender.orgattachment)\n- Bake 180 frames\n- Check frames 173 - 178\n\nDomain shrinks while space is occupied by smoke with substantial density", "Can't bake to external textures (Python)\nHello, when trying to bake an object to an external texture, Blender seems to ignore the \"save_mode\" and bakes the texture to an internal buffer. I've tried two ways:\n\n```\nimport bpy\n\n# Bake selected objects\nfor obj in filter(lambda x: x.type == 'MESH', bpy.data.objects):\n\t\n\tprint('Selected: ' + obj.name)\n\t\n\t# Select current object\n\tbpy.ops.object.select_all(action='DESELECT')\n\tobj.select = True\n\tbpy.context.scene.objects.active = obj\n\t\n\t# Bake\n\tbpy.ops.object.bake(type='COMBINED', save_mode='EXTERNAL', filepath='E:\\\\baked.png', use_automatic_name=True, width=512, height=512)\n\t\n\t- Other version, doesn't work either\n\t- bpy.ops.object.bake(filepath=\"//baked.png\", save_mode='EXTERNAL')\n```\n\nAnd also setting the parameters in a different way:\n```\nbpy.context.scene.render.bake.filepath = 'E:\\\\baked.png'\nbpy.context.scene.render.bake.save_mode = 'EXTERNAL'\nbpy.context.scene.render.bake.use_split_materials = False\n```\n\nAlways, the execution of the previous code returns the following and does not create an image file:\n```\nSelected: Cube\nInfo: Baking map saved to internal image, save it externally or pack it\nSelected: Floor\nInfo: Baking map saved to internal image, save it externally or pack it\n```\n\nTried with different paths and parameters for the bake funcion, also creating image nodes and selecting / deselecting them in the node editor for the material.\n\nAlso, I found someone who had the same problem as me, and found no solution:\n676562\n\n\nFind attached a blend file: [Bake.blend](Bake.blend)\nIt's a simple cycles scene with a cube and a floor, Cycles renderer. It bakes correctly to textures (internal buffer).\n\n - Open the blend file or create your own scene\n - Run the code written above\n - Blender won't create a bake file, in the console you'll see \"Baking map saved to internal image, save it externally or pack it\"\n\n\nWindows 10, nVidia Quadro K5100M\n\nBroken: 2.79b f4dc9f9d68b, 2.77a abf6f08\n\nThank you", "Mantaflow: Crash when setting a Guide Fluid Effector\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.3.0\n\nAfter setting a mesh as a \"Guide\" fluid effector, checking the \"Guides\" box in the fluid domain settings crashes Blender. \n\n- Open attached file,\n- go to the fluid domain settings\n- check the \"Guides\" box. \n[Fluid_Guide_Crash_01.blend](Fluid_Guide_Crash_01.blend)\n\n", "Crash to login screen on macOS Ventura when enabling caustics and smooth shading.\nOperating system: macOS 13.1\nProcessor: 2.6GHz Intel Core i7\nGraphics card: AMD Radeon Pro 5500M 8 GB\nMemory: 16GB 2667MHz DDR4\n\nBroken: 3.4.1\n\nBlender/macOS crashes to login screen when enabling smooth shading on an object with \"Cast Shadow Caustics\" enabled.\n\nCreate a scene with:\n\n - A light with \"Shadow Caustics\" enabled\n - An object with \"Cast Shadow Caustics\" enabled and a transmissive material applied\n - An object with \"Receive Shadow Caustics\" enabled\n\nSet render engine to Cycles and device to GPU compute (crash does not occur with CPU compute).\nSwitch viewport mode to Rendered.\nSelect the cast shadow caustics object and enable smooth shading.\n\nmacOS will hang before crashing to a login screen.\n\nsystem.log reports:\n\nsessionlogoutd[4795]: DEAD_PROCESS: 3681 console\n\nConsole.app also lists a crash report for WindowServer (example crash report is attached).\n\n[Caustics-Crash-on-Shade-Smooth.blend](Caustics-Crash-on-Shade-Smooth.blend) [WindowServer-2023-01-19-171731.ips](WindowServer-2023-01-19-171731.ips)", "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", "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 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)" ]

[ "Flame fire crash guide December 21, 2022\nOperating system: macOS-13.2-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.5.0 Alpha\n\nFlame fire crash guide December 21, 2022\n\n@OmarEmaraDev \n\n\n\n\n\n[Blender-2022-12-21-010909.ips](Blender-2022-12-21-010909.ips)\n\n[Fire.zip](Fire.zip)\n\nJust create Shift + A then click Mesh > UV Sphere.\nObject menu > Quick Effects > Quick Smoke.\n\n\n\nClick Sphere object then go Properties.\nProperties Flow Type: change from Fire + Smoke to Fire.\n\n\nClick Smoke Domain Object then go properties.\nProperties Resolution Division from 32 to 512\n\n\nCache:\nEnd from 250 to 1000 (frames)\nType: ALL\nPush the Bake All) for a long while until crash guide.\n\n\n\n\n", "Crash when baking quick smoke fire simulation\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\nQuick Smoke within FIRE (Bake Data) button\n\n\nfrom 32 change to 256 see picture \n\nSee End: from 256 to 1000 (frames) \n\n(Bake ALL) on Type: ALL\n\n\n[Blender-2022-08-15-103438.ips](Blender-2022-08-15-103438.ips)\n[Blender crash guide on Mac appear.txt](Blender_crash_guide_on_Mac_appear.txt)\n\n[Quick Smoke within FIRE.blend](Quick_Smoke_within_FIRE.blend)\n\n\n" ]

[ "GPU Subdivision slows down in Sculpt mode, Weight paint mode.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.1\n\nGPU Subdivision slows down the work in Sculpt mode and Weight paint mode\n\n1. Turn on the GPU Subdivision.\n2. Enable the subdivision surface modifier on the model.\n3. Try to do something in Sculpt mode, Weight paint mode.\n4. Turn off the GPU Subdivision and follow step 3.\n\nWith GPU Subdivision enabled, the Sculpt mode and Weight paint mode tabs work much slower.\nIf it can't be fixed, then it would be logical for GPU Subdivision not to be enabled on these tabs.\n\nAt the same time, the GPU Subdivision works correctly in Object mode.\n", "Sculpt Mode: Inconsistent cavity auto-masking results\nOperating system: Linux-5.15.0-53-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.5.0 Alpha\n\nWhen using Cavity auto-masking the results can be different each time when executed, even though the mesh has not changed.\nThis can be observed when using the Mesh Filter tool with the Inflate tool setting.\nEnable Cavity auto-masking in the header and repeatedly execute the tool by click & dragging to the right, and undoing the action.\n\n|  |  | \n| -- | -- | -- |\n\nThe second of these images was the most common result for me. \nEach time I executed the tool my mouse cursor started at a different position on the screen, which might, but should not influence the result.\n\n- Add the monkey primitive\n- Subdivide the object 3 times and apply the modifier\n- Enter sculpt mode and make the \"Mesh Filter\" tool active\n- Enable \"Cavity\" auto-masking in the header\n- Click and drag from left to right and undo repeatedly to observe varying results", "\"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", "Incorrect order in undo stack when switching between Object Mode and Edit Mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83 (sub 10)\nWorked: I don't know, I am a new user\n\n**Expected Behavior**\nWhen you undo, you expect to undo the last thing you did (FIFO).\n\nCurrently, if I am in Edit Mode and I change the scale of an object in the \"Transform\" panel on the right, and then undo immediately, it will undo all changes I did in Edit Mode and only then, undo the scale change even though I just did the scale change.\nIn other words, for some reason the undo stack in blender prioritizes things you didn't do in the transform panel when you are in Edit Mode even if these other changes aren't the most recent ones.\n\nFile > New > General\nA cube should appear in the center\nUse Tab to go into edit mode\n(1) Do some changes like moving vertices\n(2) Now change the scale of the object in the transform panel on the right\nNow hit Ctrl+Z to undo the last change\n\nIt will likely undo (1) the \"Edit Mode\" change instead of (2) the \"Transform Panel\" change.\nIf you keep doing Ctrl + Z it will eventually undo the transform panel change after undoing all the \"Edit Mode\" changes.", "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", "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", "Cannot sculpt under masked geometry 2.92\nOperating system: windows 10\nGraphics card: nvidia 1050ti\n\nBroken: 2.92.0, also 5ec6c8d267\n\nWorked: (optional)\n2.83.12lts\n\nLast report on the same issue #80980 (Cannot sculpt behind Hidden geometry)\nCannot sculpt under maked geometry. I reported this bug in a previous version and it was fixed. the bug is now back.\n\n| ||\n| -- | -- |\n\n- Add a UV sphere.\n- Assign some vertices to a vertex group, \"del\".\n- Add mask modifier, mode = vertex group, select \"del\", check \"invert\"\n- Go to sculpt mode, notice the vertices highlighted under the brush or the geometry modified while sculpting. In 2.83.12, they're on the back side of the hole. In 3.0, they're part of the \"del\" group.\n\n\n\n\n", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "Color picker undo adds step when cursor exist\nRun blender, logging undo events:\n\n```\n blender --log \"bke.undosys.*\" --log-level -1 --log-show-basename\n```\n\n\n\nClick on the object color swatch and move pointer away from the popup.\n\nEven though no changes have been made, an undo step is added.\n\n----\n\nIsn't high priority, reporting so it's not forgotten.", "Multres disabled in Sculpt Mode when under another modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.92.0 Alpha\n\nWhen stacking another modifer like Solidify or Mirror over (listed below in the modifier stack) the multires modifier it will disable you from sculpting on the subdivision levels when entering sculpt mode.\nInstead it will show the base resolution. If any modifier visibility is toggled or sculpt level is switched it will be fixed.\nSometimes when sculpting on an object with this bug it also crashes but I couldn't reliably reproduce this.\n\nI assume the intended effect would be that the modfiers other than the multire get disabled, but not the multires itself.\n\n- Add a multires modifier on the default cube\n- Subdivide 2 times\n- Add solidifiy modifier \n- Enter sculpt mode\nNow instead of showing subdivision 2 it will show the base mesh\n- Toggle any modifier visibility, subdivision level or the sculpt mode option \"Use Deform only\"\nNow it will be fixed. Toggle out and into sculpt mode again and it will show the bug again.\n\n", "Adding new hook while in Edit mode breaks when trying to undo/redo the operator\nWin7 (32bit)\n\nBroken: 2.78a\n\n\n- Add Path from Curve menu, add new Armature\n- Assign Bone to control point as Hook\n- Blank Hook modifier appears along with real one\n\nScreencast: [screencast0001-0250.mp4](screencast0001-0250.mp4)\n", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "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", "Text editor undo system, undo step limiting behavior\nCurrently having a linear undo stack has a limitation which is most obvious with text undo.\n\nTyping a character uses a single undo step, meaning if you are working in 3D sculpting for eg, then type a short paragraph over 32 characters - you'll loose all your undo steps.\n\nProposed solution is for undo systems to support counting their undo steps separately, so text editing operations wouldn't use up undo steps for edits in other modes.\n", "Rigidbody crash undoing while animation plays (which was started at frame 1 or below)\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[animation_john2.blend](animation_john2.blend)\n\nOperating system: Windows 10\nGraphics card: Nvidia 2070 Super\n\nWorked: -\n\nBlender crashes when object is rotated to a steep vertical angle and animation player is run.\n\nFor animation_john2.blend\n- Play Animation\n- Select a bone (could be any other operator as well I think)\n- Undo (this will also jump back to frame 0 -- where we started -- which is the important part, starting animation at frame 2 or higher does not result in the crash)\n- Redo\n\nRepeat until crash. Occurs between 2-5 repeats.\n\nAlso occurs at other similar high angles." ]

[ "Undo queue in Multires Sculpt jumbled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0 Release Candidate\nWorked: 2.91.2 (stable)\n\ndirectly placing a brushstroke in multires edit and then performing an undo first does (apparently) nothing and then undoes subdivision and brushstroke together.\n\n\n - Create New Scene -> Sculpting\n - Add Multires Modifier\n - Press \"Subdivide\" (doesn't matter how often)\n - perform a brus stroke on the mesh\n # Perform Undo \n - > Apparently nothing happens\n # perform second undo\n - > Stroke and subdivisions are revoked together.\n\nIt seems to work fine in The current stable Blender Version, 2.91.2\n", "Sculpt Redo does not always properly apply the first stroke of the sculpt session\nBroken: At least 2.83, 2.90, 2.91, current master.\nWorked: ???\n\nWhen starting from `File -> New -> Sculpting`, draw two strokes, undo twice to go back to starting sphere, redo once (*nothing happens*), redo again (*both first strokes re-appear simultaneously*).\n\nNote that this is not reproducible when using default startup, and then switching to Sculpt mode.\n\nI believe this is because in the first case, initial undo step (memfile one) has active object already in Sculpt mode, and the first Sculpt undo step is actually stored for the first stroke.\nConversely, when switching to Sculpt mode from Object mode, that switch itself is stored as a Sculpt undo step, and the first stroke is the second Sculpt undo step.\n\nFurther investigation is needed though.", "Undo Can Get Stuck If Sculpt Mode Has Been Entered via Undo\nOperating system: Windows 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.91.0 release, 2.92.0 alpha 9b17e71c23a9\nWorked: ?\n\nWith a certain sequence of undo, redo and sculpt operations, part of the mesh can disappear, undo can get \"stuck\" or the mesh might even change.\nThey all appear to be triggered by entering the sculpt mode via an undo or redo operation.\n\n(I'm having difficulty reproducing the mesh partially disappearing, so this case is not described here.)\n\n[292_sculpt_undo.blend](292_sculpt_undo.blend)\nOpen the file.\nYou are already in Sculpt Mode; Dyntopo is on.\n\n(In this example sequence, the undo will get \"stuck\" and will need a redo to undo further.)\n1. Sculpt one dab on any face of the cube.\n2. Switch to Object Mode.\n3. Undo. *(You are now back in Sculpt Mode, the dab you drew is still there.)*\n4. Paint a dab on another face of the cube.\n5. Undo *(The second dab disappears.)*\n6. Undo again. *(Dyntopo is switched off.)*\n7. Undo again. *(Nothing happens, no matter how often you press it. The first dab is still there.)*\n8. Redo. *(Nothing happens.)*\n9. Undo. *(The first dab disappears.)*\n" ]

[ "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "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", "Replace object-linked materials feature\nMaterials linked to objects have some issues:\n- They cause problems for geometry nodes, which can arbitrarily change material slots during evaluation.\n- They tend to be confusing, partially due to relying on consistent indices between two different lists\n- They cause large performance issues for reference counting in the main data-base, since geometry-level operations also have to be aware of objects\n- Object-linking is theoretically redundant now that materials can be changed during evaluation.\n\nBecause of that, it would be best to remove the feature and replace it with something more generic.\nMost workflows are already possible with nodes like the \"Replace Material\" node, but we have to be able to replicate the behavior exactly in order to version the feature away. There are a few options:\n1. Add a modifier with a UI-list interface that sets materials at specific slots.\n2. Add the necessary features to geometry nodes (loop? lists?) necessary to make the behavior completely generic\n3. Just add a geometry node group with enough nodes to handle whatever list of object linked materials the object had.\n", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "Blender crashes: 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", "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", "\"Repeat History\" unavailable after \"Undo\"\nCurrently undo clears the operator history,\nideally this should instead keep these actions in sync with the undo history.\n", "Segfault pasting stale driver.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\nDrives copied and pasted with significant change in file data in between can trigger segfaults. \n\n```\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nblender(BLI_system_backtrace+0x34) [0x55dfd70fd084]\nblender(+0xe151bd) [0x55dfd4bd41bd]\n/usr/lib/libc.so.6(+0x3cf80) [0x7f9b26870f80]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder26build_object_data_geometryEP6Objectb+0x170) [0x55dfd7000380]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder17build_object_dataEP6Objectb+0x54) [0x55dfd6ffb4b4]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x1d3) [0x55dfd6ffe2c3]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder22build_driver_variablesEP2IDP6FCurve+0x77) [0x55dfd6ffad87]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder14build_animdataEP2ID+0x1f9) [0x55dfd6ffe8b9]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x228) [0x55dfd6ffe318]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder16build_view_layerEP5SceneP9ViewLayerNS0_26eDepsNode_LinkedState_TypeE+0xb2) [0x55dfd7003892]\nblender(_ZN7blender3deg23AbstractBuilderPipeline16build_step_nodesEv+0x76) [0x55dfd6fea296]\nblender(_ZN7blender3deg23AbstractBuilderPipeline5buildEv+0x42) [0x55dfd6fea4b2]\nblender(DEG_graph_build_from_view_layer+0x33) [0x55dfd6fd24e3]\nblender(+0xef501a) [0x55dfd4cb401a]\nblender(wm_event_do_depsgraph+0xc5) [0x55dfd4f59245]\nblender(wm_event_do_refresh_wm_and_depsgraph+0x92) [0x55dfd4f593b2]\nblender(wm_event_do_notifiers+0x36a) [0x55dfd4f6055a]\nblender(WM_main+0x2b) [0x55dfd4f5532b]\nblender(main+0x367) [0x55dfd4b9da67]\n/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f9b2685bb25]\nblender(_start+0x2e) [0x55dfd4bd056e]\n\n# Python backtrace\n```\n\n\n* Add a custom property to the Scene.\n\n* Right click on its value field, and run \"Copy as New Driver\".\n\n* Run `CTRL`+`N` or \"File\" —> \"New\" —> \"General\".\n\n* Right click on any value field, and run \"Paste Driver\".", "Can not undo Node Editor operators in Edit Mode\nOperating system: Linux-5.4.0-125-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.5.0\n\nIf Edit Mode is active (for Curves or Meshes), Undo on Node linking/moving etc. gets ignored.\nIf there is a reason for that, Undo history probably should reflect that, for example by not allowing iterating to steps in Edit Mode that won't match reality.\n\n[undo.blend](attachment)\n - In GN or Shader Editor create a new Node Link.\n - Undo.\n -> Undo History shows a step back, but nothing actually happens.\n\n", "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)", "Bake fluid domain simulation crashes when using a depsgraph poll\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.92.0\n\nWhen using bpy.context.evaluated_depsgraph_get() in a poll and then baking a fluid blender crashes\n\n1. use the provided file with a fluid prepared to bake data or create a fluid domain and a fluid source\n[mantaflow.blend](mantaflow.blend)\n\n2. make sure the chace type is set to modular\n\n\n3. run the simple operator script (should come with the blend file)\n[operator_simple.py](operator_simple.py)\n\n4. press the bake Data in the Fluid domain settings and blender should crash\n\n\n\n", "bpy.ops.fluid.free_all() can cause a crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\npython script to free and re-bake smoke can cause a crash in 2.9x\n\nThe description of this bug is clearly documented along with the example blend file in [this blender stackexchange question ](python-script-to-bake-two-fluid-domains-aborting-cmd-line).\nIf I comment out the lines that contain:\n\n```\nbpy.ops.fluid.free_all()\n```\n\nin the following script, and instead manually free the bakes, all is fine. Otherwise the application crashes with console messages like:\n\n```\nUnable to remove directory\nor\nUnable to delete file\n```\neven if run from cmd line as Administrator\n\n\n```\nimport bpy\n\ndomain = bpy.data.objects['Smoke Domain Purple']\ndomain.select_set(True)\nprint(\"free Purple\")\nbpy.ops.fluid.free_all()\nprint(\"bake Purple\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\ndomain = bpy.data.objects['Smoke Domain Blue']\ndomain.select_set(True)\nprint(\"free Blue\")\nbpy.ops.fluid.free_all()\nprint(\"bake Blue\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\n```\n\n[dual smoke.blend](dual_smoke.blend)\n", "Crashes when trying to mirror particles\nOperating system: Windows 11\nGraphics card: Nvidia RTX 2060\n\nBroken: 3.6.1\n\nWhen I try to mirror hair particles Blender crashes. I've tried it multiple times and it happens every single time. Ive tried applying the mirror modifier I have on the character but it still crashes.\n\nI have a retopologized character. I make a particle system for eyebrows. I try to mirror the eyebrows by selecting all the particles, going to particles and selecting mirror and blender crashes.\n\n", "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)", "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" ]

[ "Crash making linked objects local and undo\nDell Studio 1749, i3, Windows 7, 1 GB ATI Mobility Radeon HD 5650\n\nBroken: Blender 2.69.0 r60995\n\n**Steps to Redo**\nwhen importing the attached blender file objects into a new blender file, using file > link, linking just the objects, then make all objects local, then move up, move down, then as soon as i click 'ctrl & z' the blender crashes,\n\nAny ideas?\n\nundo steps set to 32\n\n[coffee-table3.blend](coffee-table3.blend)\n" ]

[ "Compositor : improve Viewer node behavior\nSome issue with the current design:\n* The backdrop only shows the output of the viewer node. This means that for simple cases, users need to manage multiple nodes.\n* It's not obvious when seeing the results of the viewer node that this is not what final rendering will actually output, which leads to mistakes and having to re-render.\n* Viewer nodes work differently in geometry, shading and compositing nodes, mainly for historical rather than good design reasons.\n\nTo address these problems, I propose to make the Viewer node behave more like the one in geometry nodes.\n* If there are no Viewer nodes, then image editor, 3D viewport and node editor backdrop and will show the (active) Composite output.\n* Like geometry nodes, the Viewer node will have a button to enable and disable it. When enabling, editors by default will show the viewer output with some visual indicator that it is a viewer.\n* The editors should have an overlay option to disable showing the viewer node, so it's possible to configure an editor to always show the final output with others showing the viewer output.\n* The \"Viewer Node\" image datablock will be removed.\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", "Changing outputs from Separate RGB node into Displacement (using microdisplacement) does not trigger geometry update.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\n\nChanging outputs from Separate RGB node into Displacement (using microdisplacement) does not trigger geometry update. Have to tab into edit mode to force mesh update.\n[rgb_disp_bug.blend](rgb_disp_bug.blend)\n\nAdd plane with microdisplacement enabled.\nConnect Image node to Separate RGB node and one of the channels into Displacement node.\nChange view to Rendered mode.\nChange channels from R to G to B to R and notice no geometry updates happen in the view port. (Make sure to use an image with different channels)", "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", "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)", "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)", "Meshes are invisible if any objects are set to display 'In Front'\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.14\n\nBroken: version: 2.83.0\nWorked: 2.82\n\nIf any objects are set to display as 'in front' in a project, all meshes will display only as faint outlines. In edit mode, meshes display similar to how they would if they were set to display as wireframe.\n\nAdd a new mesh, curve, or armature to the scene.\nObject properties -> Viewport display -> Enable 'In Front'\n\n", "Support previewing geometry in the viewport\n", "Incorrect interaction glass with visibility of other objects\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.3\n\nIncorrect interaction glass with visibility of other objects. I have objects which disappear if I look at them at a certain angle through the glass.\n\nGif of the trouble \n\n\nTest file:\n[#91424.blend](T91424.blend)\n", "Skin modifier does not work on meshes created from scratch during evaluation (primitives, etc.)\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.11\n\nBroken: version: 3.0.0 Alpha\nWorked: NA\n\nSkin Modifier does not work with Geometry Nodes Mesh Primitives, see attached blend file.\n\nOpen attached file, note that Skin Modifier has no effect.\n\n[GN_skin_modif_bug.blend](GN_skin_modif_bug.blend)\n", "Geometry Nodes: Evaluate node tree for get dependencies\n/ in a progress /", "Crash when loading a geometry nodes asset into itself\nOperating system: Win 11\nGraphics card: 2070\n\nBroken: 3.4, 4.0\nWorked: none\n\nWhen working on an geometry nodes asset in an asset library - if you search for the name and adding it to the graph it causes a crash. \n\nDrag n drop from the asset browser behaves correctly here - so I think its just the node search code which is missing the check for self referencing.\n\n1. Download the blend file.\n2. Put into a folder.\n3. Add folder as asset library in prefs -> file paths -> asset libraries.\n4. Open the blend file from that folder.\n5. Go to the geometry node graph (should be open already).\n6. `Shift` + `A` to add new nodes.\n6. Search \"noop\" and press enter.\n\n", "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", "\"Ctrl+Scroll\" to pan horizontally cause issue inside geometry node editor \nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.93.0\n\n[ The two actions (Pan horizontally & change any float value of the parameters) are linked to same key combo (Ctrl+Scroll) inside geometry node editor which conflicts,]\n\n[1. Add cube and goto Geometry node editor\n2. add Transform or any node inside geometry node editor.\n3. Try to pan horizontally with Ctrl+scroll. As soon the node hit your mouse pointer while panning, the panning action will stop and it will change the slider value where the node hit the mouse pointer, this cause accidental change in value and other issue. either use Alt+scroll to pan. this same thing should be fundamental everywhere that Alt+scroll to change different tabs and Ctrl+scroll to change values, if possible.{[F10173799](Untitled.png)}]\n\n", "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" ]

[ "Collection instances (Hair particle system, geometry nodes) visible when set to \"Indirect Only\" on view layer on OptiX Cycles\nOperating system: Windows 10.0.19043 Build 19043\nGraphics card: NVIDIA GeForce RTX 3070, driver version 471.11\n\nBroken: 2.93.1, I also tested the daily 2.93.2 build 9e64fd461ac3\n\nIf you have an object covered in a hair particle system in a collection, and you set the rendering mode of that collection to Indirect Only, you can still randomly see the particles directly when rendering with Cycles and OptiX. The visibility varies from render tile to render tile. The emitter object does not show up randomly like the particles do.\n\nBelow is an example scene rendered with OptiX. The cube and icosphere are the particle emitter objects that exist in different collections, and the Suzanne monkey heads are the particles. The collection containing the icosphere is set to Indirect Only mode. Thus the monkey particles on the right should be hidden from direct rendering, but appear randomly.\n\n\n\nHere is the same scene rendered with CUDA, and it works as expected.\n\n\n\nWeirdly, hiding the cube also hides the randomly appearing monkey heads on the icosphere.\n\n1. Open the attached blend file\n2. Make sure you have OptiX selected as the rendering device in preferences\n3. Press F12 to render\n4. Change rendering device to CUDA and render again for comparison\n\n[optix_bug.blend](optix_bug.blend)\n\nHere is the system info file from Blender. [system-info.txt](system-info.txt)\n\n\n---\n\nFrom #89707:\n\nWhen a collection is set to Indirect Only, and thus should not be directly visible, geometry generated by Geometry Nodes inside said collection ignores the setting and appears as visible.\n\n\n*the incorrect behavior, with Geometry Nodes enabled.*\n\n\n*the correct behavior, when the view layer visibility of Geometry Nodes is disabled*\n\n\n1. Apply a geometry node modifier to an object.\n2. Place said object in a collection.\n3. From the Outliner, set the aforementioned collection as \"Indirect Only\".\n4. Observe the incorrect behavior.\n\nA simple .blend file is attached, which clearly shows what is happening.\nI've tested this on both Blender 3.0.0 and Blender 2.93.1. In both cases, the error appears.\n\n[buggeo.blend](buggeo.blend)\n[system-info.txt](system-info.txt)" ]

[ "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", "Viewport animation render crashes when collapsing the viewport.\nBroken: version: 2.91.0 Beta (and 2.83, 2.80, ...)\nWorked: never\n\nViewport animation render crashes when collapsing the viewport.\n\n[0001-0485.mp4](0001-0485.mp4)\n[Viewport render crash.blend](Viewport_render_crash.blend)\n\n", "Can't see wireframe (vertex, selected components) through semi-transparent object\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 10)\nWorked: c26f470cfeea is last I have by hand\n\nIn the viewport, you can't see wireframe (vertex, selected components) through a semi-transparent object\n\n[75106.blend](75106.blend)\n1 - Create 2 objects one behind the other \n2 - Make front object semi-transparent (via Object properties > Viewport Display > Color > Alpha\n3 - Select the second object in Edit mode\n\n", "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", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n", "Blender 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)", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "Crash 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>", "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)", "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)", "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "Crash when 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 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", "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", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)" ]

[ "Crash after deleting something on the scene and then clicking on the viewport\nWin 10 64 bits\n\nBroken: 2.80 e829e47b558\n\nCrash after deleting something on the scene and then clicking on the viewport\n\nLaunch Blender, then delete something, let's say, the Cube, then click somewhere in the viewport (left click if you are using the LMB select, or right click if you are using RMB select), Blender will close. .\n" ]

[ "Knife Tool: incorrect interaction with Array modifier when the Merge \"First Last\" option is set\nOperating system: Win10\nGraphics card: nVidia 1070\n\nBroken: 2.80 (sub 44), branch: master, commit date: 2019-02-14 04:22, hash: caa8e7ff2894\nWorked: not sure\n\nWhen the Merge First Last option is set for an Array modifier, it seems like hidden, virtual geometry is picked up while using the knife tool to cut across the surface of the primary shape.\n\nThis results in an improper cut.\n\nBad in-progress cut:\n\n\nBad confirmed cut: \n\n\nGood cut -- with the First Last option turned off:\n\n\n[array-bug.blend](array-bug.blend)\n- Create a simple shape and array it in a radial fashion so that the first/last vertices of the shape are eligible for merge\n - Or just load the attached .blend\n\n- Attempt to make a cut across the main shape with the Merge First Last option set\n- Notice that the cut line is picking up some hidden edges somehow -- perhaps due to triangulation?\n- Confirm the cut and notice it's still incorrect and pretty weird", "Inconsistent tool selection and tool settings for different layouts\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\nBroken 2,83,9\n\nAs title said. Inside one layout all viewports have same settings and tool selection.\nExpected: global tool selection for SAME mode and editor. Different tool selection for different editors: 2D paint and 3d paint uses same brush inside one layout (and it is pain because zoom is different)\n\n[2021-02-09_04-19-36.mp4](2021-02-09_04-19-36.mp4)\n", "No way to distinguish enum buttons that support shift-click to select multiple\nBlender has some buttons that allow shift-click to select multiple, but no way to show the difference. eg:\n\nTransform Tool, Gizmo's (Move / Rotate / Scale)", "Auto keying not keying for child bones and not transformed\nOperating system: Windows 10\nGraphics card: RTX 3060 Ti\n\nBroken: (3.1.0 c77597cd0e15 master 2022-03-08 18:16)\n\nWhen I tried to auto key multiple bones by select these and hit G > Mouse1 only the top of parented bone is keyed and nothing for anything else \n\n・Add armature\n・In edit mode -> extrude bone\n・Enable Auto keying\n・In pose mode -> Select All (A) ->Move/Rotate/Scale(but not make any transform, just apply) to add a keyframe\n\nTest file with first 3 steps included:\n[#96473.blend](T96473.blend)", "Keyframed group inputs bound to index not property\nOperating system: Windows 10\nGraphics card: GTX 1070 (Laptop)\n\nBroken: 2.80.0 009dbc2bc9fb\n\nKeyframing a property on the group input stack, maintains the keyframe at the stack index rather than the mapped property. This means when the ordering of group inputs is changed the keyframe is maintained at the previous position/index rather than moving with the initial property.\n\n\nBased on the default startup\n\n1. Create node group with multiple inputs\n2. Keyframe 2nd property\n3. Push this group input up or down the input stack (while inside node group)\n4. 2nd property will stay keyframed rather than moving up/down stack with the correct property.\n", "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", "Huion KD100 - incorrect programmable keys reading\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 27.20.100.8477\n\nBroken: version: 3.3.1\n\nHi, I got a Huion KD100 Mini Keydial and Blender seems to be the only software not regonizzing it's programmable keys correctly. I have set it up as Numpad keys, but Blender does not recognize the assigments, reading the keystroke values for Num Lock off. Affinity Designer, Photo, Google docs, everything else recognizes the defined keys, even with app profiles. Sadly Blender does not as the only one.\n\nThe only step here is really to hook up a configured KD100 and trying to change the view. Can also be easily verified in the Preferences section by testing the key bindings. \nI would be more than happy to test/debug further with my device if that's helpful.\n\n", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "Sculpt mode: hide masked do not work when modifier enabled, but hidden part works with modifier.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\n\nAs title said. Hiding works with modifier but not work simultaneously as «hide masked»\nFor example, edit mode work well with mirror and hiding, hiding by faceset works well too...\n\n**Steps to Reproduce**\n- Open .blend file\n- Paint with mask brush\n- {nav Sculpt > Hide Masked} \n\nTest File:\n[#92372.blend](T92372.blend)\n[2021-10-20_18-49-00.mp4](2021-10-20_18-49-00.mp4)\n", "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", "The viewport lock modes are super glitch (in general) with zooms and centering\nOperating system: Windows 10\n\n\nBroken: blender-3.0.0-alpha+master.eae4e2251839-windows.amd64-release\n\n\n\nThe viewport lock modes like 3d cursor or object locking is super glitchy in general which creates a disorienting experience. The main issue is sudden jumps in zooms also sometimes the center or rotation becomes jumpy as well. Some jumps in the video is worse than the others. Bear in mind that I am not zooming intentionally when there is a sudden jump.\n\nThis gets even worse in different scene scales and scene layouts. Here I am demonstrating it only with the cursor but this erratic behavior happens with object locking too. This becomes even worse with a Wacom tablet since it is harder to keep the pen movement as static as the mouse while zooming.\n\n\n- Load the attached .blend file\n- Make sure the viewlock is set to the cursor, and have similar preferences as shown in the pictures\n- Try repositioning the cursor, just move the cursor to different objects.\n- Move the cursor to the surface of another object then try ctrl+single middle click to activate the zoom\n\n\n\n\n\n\n\nTest File:\n[glitchy_lock_modes_28082021_2053_04.blend](glitchy_lock_modes_28082021_2053_04.blend)\n\n[A7ysxb6GVc.mp4](A7ysxb6GVc.mp4)", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\n\n", "Grease Pencil: Erasing/Cutting does not auto-key layers\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.5.0 Alpha\n\nUsually whatever edits are done in Edit, Sculpt or Draw mode result in creating a new keyframe, if auto keying is enabled in the timeline.\nThe issue is that the Eraser brush and the Cutter tool in Draw Mode do not result in auto-keying.\nThis is easily resulting in lost work.\n\nNote: This is the same issue with the Annotate tools\n\nOn the other hand if \"Use Additive Drawing\" (Snowflake icon) is enabled in the header, erasing will result in correct auto-keying behaviour.\nThis inconsistency doesn't seem intentional.\n\n- Create a grease pencil object\n- Enable auto-keying in the timeline\n- Switch to draw mode\n- Go to the next frame and draw a stroke (It will correctly create a new keyframe)\n- Go to the next frame and erase part of the stroke (No new keyframe was created)", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)" ]

[ "Switching open windows ignores held modifiers on WIN32\nWin7x64 GTX660M\n\nBroken: 2.70 f93bc76\nWorked: (optional)\n\nIf multiple windows are open (but same Blender instance), shift+click or ctrl+click on the unfocused one (to pan or zoom in a viewport for instance) will be taken as a simple click instead. It makes working with floating viewports difficult since one must focus the window first, then act.\n\nPop out a new 3D view by shift-clicking the corner, switch from one to the other using click with any modifier key (ctrl or shift).\n", "Shift/Control/Alt doesn't work or only works on second click when clicking back on blender window\nOperating system: Windows 10\n\nBroken: 2.79, 2.92.\nWorked: 2.49b, 2.92*\n*The bug doesn't happen in 2.92 if right click select is set as default.\n\nShift/Control/Alt only works on second click when changing active window.\n\nOpen Blender\nLeft click on the Viewport.\nHold shift\nWhile still holding shift left click on Windows's Taskbar\nWhile still holding shift right click on the viewport. \nIt will open the context menu instead of moving the 3d cursor. That's the bug.\nWhile still holding shift right click the viewport again, it will work correctly on this second click.\n\nOther way to reproduce\nOpen Blender\nOn the menu Window>New window.\nMake the secondary Blender window smaller\nShift right click on the second window viewport.\nShift right click on the main window viewport. It will open the context menu instead of moving the cursor.", "Shift + Middle Mouse Button doesn’t work when Blender window is inactive\nOperating system: Windows 10\nGraphics card: Nvidia GeForce RTX 2070\n\nBroken: 2.8 91a155833e59\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhenever I alt+tab to another application, like a tutorial on youtube to pause it, and I get back to Blender with the intention of panning the viewport with shift+middle mouse button, Blender ignores that I hold the shift key and rotates the viewport instead as if I only pressed midmouse button.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nStep 1: make the blender window inactive by alt+tab to another application. Make sure that the other application doesn't cover the entire screen, and your blender viewport is still visible.\nStep 2: Shift+MiddleMouseButton into the visible blender viewport. Instead of the expected panning behaviour you will rotate the viewport, as Blender ignores that you are holding Shift." ]

[ "NaN in object matrix of instanced objects\nRyzen 7 3800x\n31.9 GB Ram\nOperating system: Windows 10\nGraphics card: Nvidia 2060 6GB Ram\n\nI tested the same scene out on my other box and the problem happened. Both machines are running RTX 2060s. One is a Intel box and the other AMD.\n\n**Blender Version** 2.81 and 2.82a\nWorked: Nothing has worked\n\n**Error**\nYouTube link to render glitches: e1ScHjBANLk\n\nWhenever I start a render, around frame 58 the sun shadows just disappear.\nIf I close the scene and open it back up and render the frame where the shadows disappear, it will render fine. But after about 50 or so frames the shadows disappear again. \nIt works fine in viewport. \n\n**note**\nI deleted the volume light box with just a 1000 floating sprite boxes for the dust inside the garage. After that, the issue went away all together. I then added the volume box back and the problem happened again. It must have something to do with volume lighting. The grass outside is over 12k clones using a particle hair so it has something to do with volume lighting and particles inside a object. \n\n**Files**\n[Blender_Bug.zip](Blender_Bug.zip)\nIt was 12 GB, removed extra elements and brought it down to this.\nAround frame 60 if you render the animation 1-300 the shadow will disappear. Escape the render… The viewport will continue to display the shadow. But after the shadow disappears during the render, and without closing and reopening Blender, whenever you render that frame, the shadow “sun light” is absent. \n\n\n\n\n", "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 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", "Join Geometry Node makes vertices unselectable + disappear on cage preview\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\n\nUsing Join Geometry makes the vertices unselectable when Geometry Nodes is being visualized in Edit Mode.\n\nWhen using geometry nodes to act as solidify I need to add a Join Geometry at the end. This makes my vertices both disappear and they are unselectable. This happens when the \"On Cage\" overlay is activated. It properly displays the wireframe but the vertices are gone and unselectable. Since it appears and works normally when I disable On Cage I figure this must be a bug.\n\n[Blender 2022-09-08 12-37-19.mp4](Blender_2022-09-08_12-37-19.mp4)\n[JoinGeometryBug3.3.blend](JoinGeometryBug3.3.blend)\n\n\n\n", "Masks overlay not visible with Mirror Modifier\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.5.0 Alpha\nWorked: Unclear. Tested all the way back until 3.1\n\nThe mask overlay is regularly disappearing when using modifiers. The most reliable to reproduce this issue is the Mirror modifier.\n\n- Add an object with a mirror modifier\n- Duplicate the object\n- Enter sculpt mode on one of the objects and create a mask\n- Exit sculpt mode, select the other object, then the primary object again and enter sculpt mode (The mask is no longer visible)\n- Use the shortcut `Alt Q` to switch to another object and switch back (The mask should now be visible)\n- Or disable the modifier and the mask should appear.", "Deformation checkbox should be visible but isn't\nI discovered this in 2.76, I upgraded to the official 2.78c release and it's still there.\n\nFor Rigid bodies of Shape `Mesh` there is a `deform` option that is only visible for Source of type `Deform`.\nHowever, this option can affect other Source types.\n\n\n**Steps to reproduce**\n - Open blender\n - Make the starting cube a rigid body\n - Check the \"animated\" box (so it doesn't fall away).\n - Set the shape to `\"Mesh\"` inside \"Rigid body collisions\"\n\nnote that a `\"deforming\"` checkbox has appeared just below.\nThat checkbox disappear with `\"Final\"` and `\"Deform\"`, but still has an impact on the simulation.\n\n---\n\n**Edit: Developer note:**\n\n> In #51233#457199, @sreich wrote:\n> This is intentional behaviour. \"Final\" includes generative modifiers which don't just deform the mesh but generate a new one.\n> Now we could do shenanigans like rebuilding the collision shapes every frame, but that would be extremely slow and unstable.\n> \n> As for convex hulls, they don't support deformations so everything is fine there too. Again, we could rebuild the shapes during simulation, but as already said, it's a bad idea.\n> \n> Making the checkbox greyed out is possible, but I'm not sure if it's a good idea, maybe a question for the UI team?", "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", "XYZ symmetry options: unclear release notes\nThe 2.91 release notes for 5502517c3c are lacking, both in clarity of the description and the discoverability of that change for the people it impacts.\n\n- The change is described in the Sculpting section, under \"[Sculpting Workflow with multiple objects](Sculpt#Sculpting_Workflow_with_multiple_objects)\". However, it is much broader than just that. Since this change also impacts weight painting, it is relevant to riggers as well. It should be described in a place such that riggers can find it.\n- The only description is \"XYZ symmetry is now a per mesh settings which is shared between all painting and editing modes\". This doesn't convey what this change means practically, it doesn't show the changes in the UI, and doesn't tell riggers how they have to change their workflow to account for this change.\n\nAs a side-note, the #animation_rigging module should have been involved in design task #79785 and the review of [D8587](D8587), since this change impacts workflow of riggers. Instead, it went completely under the radar.\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", "Blender Crash by doing 2d animations\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 500 Intel 4.5.0 - Build 31.0.101.2111\n\nBroken: version: 3.6.0\n\nWhenever I draw with a line, circle, arc, curve, interpolate, and box tool, my drawings disappear and reappear and then it suddenly crash.\n- 2D animation Draw Mode\n[\nPlease describe the exact steps needed to reproduce the issue]\n\n", "Nodes: Reroute node disappear when pressing `Ctrl H`\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: Never.\n\nIf the reroute is not connected to anything, then pressing `Ctrl + H` will make the reroute invisible.\n\n\n1. Add reroute in nodetree using `Shift + A`.\n2. Press `Ctrl + H`.\n\n", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "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", "Cycles rendering artifacts with fluid particles + Vector pass (missing particles)\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.2.0 Alpha\n\nSections of fluid particles are missing when rendering in cycles.\nThe issue occurs when you enable the vector render pass.\nThere are no issues when rendering in the viewport, only during the final render.\nThe parts that are missing changes every frame.\nIt also happened on the same computer with a different graphics card (RTX 2060). \n\nViewport render\n\ncycles render\n\nrendered only the particles\n\n\n- Open attached file\n- Bake fluid simulation data and particles\n- In {nav View Layer Properties > Passes > Data} enable `Vector`\n- Render scene\n\n[FluidSplash2.blend](FluidSplash2.blend)\n\n", "When you clear measurements through View > Annotations, they don't vanish immediately\nOperating system: Windows\nGraphics card: GTX-2080\n\nBroken: 3.4.1\n\n\nDeleting measurement annotations appears to be broken because the UI is not refreshed until you change tool.\n\n\n1. Create some measurements\n2. Open View settings Tab\n3. Remove ruler Annotations\n\nExpected behavior: Measurements are removed and action can be undone.\n\nCurrent behavior: The Annotation is no longer visible in the annotation list, but still shown in edit view.\n\nHere is a screen recording: 185530\n\n" ]

[ "Disappearing mesh in Rigify (follow up report)\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 2.83.5\n\nUpdate to bug report: disappearing Rabbit mesh in Rigify\n\nThis time the Rabbit mesh disappeared when I changed the IK to FK setting on the hand. Right now when I send it the mesh is missing.[JR FULL RIG V2.blend](JR_FULL_RIG_V2.blend)\n\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.", "'Show Instancer' option for Viewport hides the mesh in edit mode\nOperating system: Linux-5.7.8-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.90.0 Alpha\nWorked: Never\n\nWhen using either Face or Vertex duplication on meshes, turning off `Show Instancer` in the Instancing settings (Object Properties) hides the parent object.\nThe problem is when you enter edit mode. Both the instancer and the instances are invisible.\nOne solution could be to unhide the instancer.\n\n - Open attached file\n - Uncheck 'Show Instancer' for Viewport\n # In the 3D View, press tab or otherwise enter editmode\n\nYou now are editing an invisible mesh - since we can select and edit the mesh, it would be much, much friendlier to allow editing, as the user probably expects this, by showing the mesh just in edit mode - it could be wireframe only or semitransparent, to indicate that it's hidden in object mode.\n\n(This may be considered an enhancement or a bug - at the very least it feels like a lack of polish in the interface, but it would be extremely befuddling to some users should they find themselves in this state.)\n[instancer_bug.blend](instancer_bug.blend)\n\n", "Bevel Bug\nblender-2.80-07765499abee-win64 \n\n**cylinder :**\non the cylinder with a lot of segments, bevel doesn't merge in one point. Create nice see n-gon(normal we must see the only verts in one point)\n\n\n**Cube :**\nThe middle loop has deformed when we bevel sharp corner for small mesh. On the large mesh, we cant see this deform .\n\n\n[Cylinder_Bevel_Bug.blend](Cylinder_Bevel_Bug.blend)\n\n[Cube_Bevel_Symmetry_Bug.blend](Cube_Bevel_Symmetry_Bug.blend)\n ", "Armature modifier taking a performance impact, even when set to not be visible.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.2\n\nSome part of the Armature modifier is still calculating even when set to not be visible.\nCausing a performance impact, when an artist expects none. Other modifiers like Subdivision Surface do not have this issue.\n- unrelated, also kinda sucks that I get sub 24fps with 100k poly videogame ready models.\n\nHave a high poly model weighted and bound to an armature, with any simple animated movement. Take note of the viewport performance when viewing playback of the simple animation. Disable all visibility options on the Armature modifier on the model. Performance only increases slightly. Uncheck 'bind to vertex groups' on the modifier. See performance improve drastically, even though the modifier is set to not be visible in the first place.\n\nWith the attached blend file, a high poly model is already bound to an armature with a simple animation.\n[ArmatureModifierBug.blend](ArmatureModifierBug.blend)\n\n", "Node sockets disappearing but still dragging works\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.4.0 Alpha\n\nWhen a node is added and zoomed out, the node sockets disappear. But still, the drag function works.\n\n[Node Socket Bug Report .mp4](Node_Socket_Bug_Report_.mp4)", "Links persist invisibly after their source sockets are removed\nBroken: Probably forever (e.g. 3.0, 3.1)\nWorked: N/A\n\nIf the output socket of a node is removed, the input socket it was connected to does not show a button to input a value. It acts like it's still connected.\n\n**Detailed replication**\n1. Go into the Shader Editor\n2. Create the *Voronoi Texture* node and a *Math* node\n3. Set the *Voronoi Texture* node to 4D, and plug its new W output into the *Math* node\n4. Set the *Voronoi Texture* node to 3D. Observe that the input on the *Math* node still acts like it's connected\n5. Click and drag from that input on the *Math* node. A bogus wire will appear from the *Voronoi Texture* node, coming from where the W output used to be.\n\nYou can then plug this wire into another socket. It will disappear again once you let go. If you set the *Voronoi Texture* node back to 4D, the wires will re-appear.\n\nVideo example:\n\n[XwBMq60aMI.mp4](XwBMq60aMI.mp4)\n\n**Another example:**\n\n{[F13079601](free-socket.blend), size=full}\n\nIn this case you can even save the file in this state where you can't see or edit the value of the node until you disconnect it.\n\n", "Rigidbody Physics Refactor\n**Goal**\nThe goal is to simplify the rigidbody physics code.\n\nThis ticket is being raised after discussions with @ZedDB about this issue T91369 and the related tickets regarding rigidbody physics crashes. I attempted to resolve those crashes on their own, but really struggled to find a sensible way to resolve some of the memory management issues that were occuring. @ZedDB mentioned that this was an area of the code in need of a redesign for some time, and with comments like below predicting this could be an issue, we decided it could be a good time to start tackling it.\n\n\n\n**Approach**\nI want to start with some smaller low hanging fruit, that wouldn't change any logic but will improve the readability of the code. \n\n- [ ] There is some dead code that can be removed\n- `BKE_rigidbody_calc_center_of_mass` - probably worth keeping the logic but hiding with a `#if 0`\n- `BKE_rigidbody_world_groups_relink` is only used by `BKE_scene_groups_relink` which doesn't seem to be used anywhere else.\n\n- [ ] It would make things much easier to follow by separating the simulation logic from the rididbody creation/deletion logic, into a separate `rigidbody_simulation.c` file.\n\n- [ ] There is a lot of general tidy-up that would make the code more readable and easier to understand.\n\nOnce these tasks are completed we can start thinking about any larger design issues that need to be addressed - like with the memory management of the constraints. With more readable code, and a better understanding of the logic from the refactoring process, it should be a more solvable problem.\n\n", "Sculpt Mode - Using Mask while Multiress active = Crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.2\n```\n Tried also with\n```\n 2.83LTS\n 2.92beta 77f73a928439\n 2.93.0 ae1e68f5146d\n\nWorked: None\n\nWas working in Sculpt mode, tried to hide the arms and the program crashed.\nI tried with another objects with multires and it doesn't happen\n\nHere the .Blend with the problem\n [Multires prueba.blend](Multires_prueba.blend)\n\nGo to Sculpt Mode -> Try to mask with mask brush, Mask Lasso or Mask Box", "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```", "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", "Metaball names with digits in the end are invisible (also issue with renaming/duplicating metaballs)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIf you will try to use names like MetaballFamily2, Family will disappear. \nNames like Aaaa1aa and 1aaaaa — checked too, causes no problem\n[2019-07-11_19-49-29.mp4](2019-07-11_19-49-29.mp4)\n[untitled.blend](untitled.blend)\n\n\nMake metaball, add 1 to the family name\n", "Bug in particle system - missing particles representations\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.90.1\nWorked: potentially never, does also not work with 2.80\n\nWhen creating a particle system with `instance objects` and using more than ~15.000 particles, not all particles are represented with the instance object. The more particles the particle system contains, the more instance objects are missing. \nThe following images illustrate the problem.\n\nExample with 120 x 120 = 14.400 particles. All particles are represented with the instance object (in this case a cube) - except for the first particle at the top left corner. This particle is always missing - even for small particle systems. \n\n\n\nFor slightly bigger particle systems (e.g. 150 x 150 = 22500 particles), a few particles at random positions in the particle system do not contain an instance object (see the black dots)\n\n\n\nFor way bigger particle systems (e.g. 200 x 200 = 40000 particles) the last particles (i.e. the particles at the bottom right with the biggest indices are missing)\n\n\n\nThe presence of particles without instance objects also affects other particles when using specific nodes. For example, when using the `index` output of the `Particle Info Node` to compute a texture coordinate for each particle used to compute individual colors for the particles produced strange results.\n\nHere a working example for 120 x 120 particles (as reference)\n\n\n\nAnd here a non-working example for 200 x 200 particles (zoomed on the bottom-right corner)\n\n\n\nSide note: In all the examples, the particles are there, but the instance object representation is missing.\n\n\nExecute the following Python script within Blender's text editor. Or, when using Jacques Lucke's VSCode Plugin: execute the script (again) when Blender is already opened (since it does not work with a restricted context)\n\n[particle_sys.py](particle_sys.py)\n\nBlend file with the an incorrect particle system\n\n[particle_sys.blend](particle_sys.blend)\n", "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", "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 ", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n" ]

[ "Model disappears in Rigify\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 2.83.5\n\n\n\n" ]

[ "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Crash 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). ", "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", "Intel (R) HD graphics 4600 also has the problem of cubemaps shows black\nIntel (R) HD graphics 4600 also has the problem of cubemaps shows black\n\nSystem Information\nOperating system: windows7 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 3.4.0 - Build 10.18.14.5117\n\nBlender Version\nBroken: since 2.83.3 branch: master\nCurrent broken: 2.93.7\nWorked: 2.82a\n\nShort description of error\nLike #75943 and #79158, HDRI cannot be displayed normally\n\nCan be resolved adding \"**HD Graphics 4600**\" to the blacklist\n\nComment from #79158: \"*I'm not sure whether Intel's graphics cards are like this. Can you put this repair method in preferences as an option?*\"\nOr perhaps adding command line flag like: **--disable_texture_cube_map_array**", "HDRI background shows lighting artefacts at zero strength\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nDont know if this is a Blender issue, but I encountered a few HDRI files that still show light sources despite having zero strength in the viewport shading studiolight setting:\n\nThe HDRI file is:\n[blue_lagoon_night_2k.hdr](blue_lagoon_night_2k.hdr)\n\nThe lighting comes from remaining artefacts at the spot of the lamp. Its more noticable with a bit of blur, but you can still see it without.\nSince this is only an issue for some HDRI Backgrounds I assume it has to do with those files, I dont know. Regardless, it would be nice if Blender could take care of these cases to guarantee a dark background.\n\n\n[HDRIBackgroundStrengthBug.blend](HDRIBackgroundStrengthBug.blend)\n1. Install the attached HDRI File and set it as background.\n2. Change the strength setting for the Viewport Shading to zero.\nProblem:\nThe background lightens the scene at zero strength with the remaining artefacts.\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", "Script node with shader output crashes Eevee\nOperating system: OSX Monterey (12.6)\nGraphics card: Radeon Pro Vega 20\n\nBroken: git versions: blender-v3.2-release, blender-v3.3-release, master\nWorked: 3.2 release\n\nI'm testing the MaterialX standard surface shader. It seems to work when in Release versions, but in a debug build, it crashes when you connect the output of the shader to 'surface' in the terminal node.\n\nUsing the default scene, switch from Eevee to Cycles + Open Shading Language. Select the Cube, switch to Shading tab. Create a new material, and add a new Script node. Load the attached .oso file (to compile the attached .osl, you need to have MaterialX installed. I'm using 1.38.5). Attach the output of the script node to the 'Surface' input of the terminal. Boom! Where the crash occurs depends on whether your in Eevee preview, or Cycles preview.\n\n[out.osl](out.osl)\n\n[out1.oso](out1.oso)", "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", "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", "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", "Problems due to leftover Nvidia drivers\nOperating system: Windows 11 Home\nGraphics card: Intel Arc a770 16gb Limited Edition (latest drivers)\n\nBroken: (Blender 3.3, 3.5 and 4.0) Trying to work out if it is just my GPU that is the issues\n\n\nBlender 3.5.1 will not allow me to access editor preferences, and won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 3.3 allows me to access editor preferences, but still won't allow me to render in Cycles. CPU or GPU. Eevee works.\n\nBlender 4.0 allows for editor preferences, same issue with Cycles. Eevee works fine.\n\nBy not allowing me to access editor preferences or Cycles I mean it crashes.\n\nI have tried to converse with Intel engineers with a video of the crashes but they seem incompetent with knowing how to enable GPU rendering in their own tests.\n\n", "Mesh Attributes Python API Is Buggy\nOperating system: Windows 11\nGraphics card: NVIDIA RTX 3070\n\nBroken: 2.93 & 3.3\nWorked: \n\nAccessing geometry attributes via python causes internal errors and mismatched pointers.\n\n\n```\n- Blender 3.3.0 bug\n- 1) Open new file w/ default cube\n- 2) Paste this script into the scripting tab\n- 3) Make sure the cube is selected and run this script\n\nimport bpy\n\nme = bpy.context.active_object.data\n\nfva = me.attributes.new('float_vector_attribute', 'FLOAT_VECTOR', 'CORNER')\n\nprint(f'fva : {fva}.data_type = {fva.data_type}')\n\nfca = me.attributes.new('float_color_attribute', 'FLOAT_COLOR', 'CORNER')\n\nprint(f'fva (again): {fva}.data_type = {fva.data_type}') # output will be wrong\nprint(f'fca : {fca}.data_type = {fca.data_type}')\n\nme.calc_normals_split() # causes next line to crash\n\nfva.data[0].vector = (1, 2, 3) # only crashes the first time the script is run\n\n```", "Blender (silently) fails when importing Sketchup Collada File\nMid-2014 MacBook Pro with Intel Iris Pro 1536 MB Graphics\n\nBroken: Version 2.79 (2.79 2017-09-11, Blender Foundation)\n\nTried to import a .dae file downloaded from Sketchup, and nothing happened after selecting the file from the Import dialog.\n\n\n\n - Went to K-5299-RA-Highline-Classic-10-gpf-Comfort-Height-two-piece-elongated-toilet-with-Class-Five-flush-technology-and-right-hand-trip-lever \n - Downloaded the Collada File from the page; also uploaded here: [model.dae](model.dae) \n - Opened blender from the command line\n - Selected menu: File > Import > Collada (Default) (.dae)\n - Selected the model.dae in the dialog. The dialog closed, but see an empty scene still. I expected to see an error or something if it couldn't import it.\n\nOn the command line, I see the following:\n\n```\nRead prefs: /Users/myuser/Library/Application Support/Blender/2.79/config/userpref.blend\nColor management: display \"sRGB\" used by scene not found, setting to default (\"sRGB / BT.709\").\nColor management: scene view \"Default\" not found, setting default \"sRGB EOTF\".\nColor management: sequencer colorspace \"sRGB\" not found, will use default instead.\nfound bundled python: /Applications/blender.app/Contents/Resources/2.79/python\ndrop file /Users/myuser/Downloads/model.dae\nWriting node id='ID4', name='skpC9F6'\nWriting node id='ID5', name='instance_1'\nCannot find object for node referenced by <instance_node name=\"\">.\nWriting node id='ID6', name='_5299-RA'\nWriting node id='', name='SketchUp'\nWriting node id='', name='skp_camera_Last_Saved_SketchUp_View'\nWriting node id='ID3', name='instance_0'\ncreate <instance_node> under node id=ID3 from node id=ID4\ngot 25 library nodes to free\n```\n\nThe line `Cannot find object for node referenced by <instance_node name=\"\">.` being output does make me wonder if something is going wrong. However, I can see the file OK in a https:*threejs.org/ based Collada viewer (and the associated https:*threejs.org/examples/js/loaders/ColladaLoader.js )\n\n\n\nHas anyone else seen this problem in 2.79b?\n\n", "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", "Blender Freezes and Crashes on AMD Laptops with White and Black boxes\nOperating system: Windows 10 & 11\nGraphics card: Radeon RX 6600M ATI Technologies Inc. 4.5.14800 Core Profile Context 22.4.2 30.0.15021.7000\n\nI've been using Blender with many versions. From 2.8, to 3.1 and the laptops have issues with all of them.\n\nBlender will freeze, white and black boxes will appear, and then Blender will crash and Windows will close it.\n\nI don't have exact steps, because it happens infrequently. It can happen as quickly as opening Blender, or take an hour of work.\n\nI am a teacher using HP Omen laptops with AMD CPU's and graphics cards. I have 21 laptops, and about 5-7 of them have issues with Blender. I have done a clean install of the graphics drivers, updated Blender to the most recent version, and tried everything I can think of. My personal laptop rarely ever crashes, so it's hard for me to replicate the issue.\n\nI have attached log files from crashes from multiple laptops. Half the laptops have been upgraded to Windows 11, and that doesn't seem to make it more or less likely to crash. My hope is these logs can pinpoint what's happening so I can fix it. I\n\nLog files created with `blender_debug_gpu_glitchworkaround.cmd`\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\nLog files created with `blender_debug_gpu.cmd`\n\n[blender_debug_output (1).txt](blender_debug_output__1_.txt)\n\n[blender_system_info (1).txt](blender_system_info__1_.txt)\n\nWarning and errors:\n```lines=10\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_multi_rect_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_multi_rect_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_text VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_text FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_uniform_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_uniform_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_INST_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_WIDGET_BASE_INST_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_rect_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_rect_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_flat_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_flat_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_LINE_DASHED_UNIFORM_COLOR_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): GPU_SHADER_2D_LINE_DASHED_UNIFORM_COLOR_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_3D_uniform_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_3D_uniform_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_desaturate_color VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): gpu_shader_2D_image_desaturate_color FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_mesh_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_hair_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_opaque_ptcloud_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_composite_studio VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_composite_studio FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_merge_infront VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_merge_infront FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_mesh_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_hair_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_none_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_none_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_single_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_single_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_tile_no_clip VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transp_studio_ptcloud_tex_tile_no_clip FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transparent_resolve VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_transparent_resolve FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_effect_outline VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_effect_outline FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_taa VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_taa FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_0 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_0 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_1 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_1 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_2 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): workbench_smaa_stage_2 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_antialiasing_263 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_antialiasing_263 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_414 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_414 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_449 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_449 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_401 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_sphere_401 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_439 GeomShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n | \n 6 | #define DFDY_SIGN 1.0\n | ^\n | (#310) Inputs that are integers should be qualified with the interpolation qualifier \"flat\"\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_wire_469 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_shape_wire_469 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_wire_538 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_wire_538 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_solid_559 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_degrees_of_freedom_solid_559 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_stick_518 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_stick_518 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_499 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_499 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_489 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_envelope_489 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_wire_579 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_armature_wire_579 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_background_276 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_background_276 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_uniform_color_1465 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_uniform_color_1465 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_grid_905 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_grid_905 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_885 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_885 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_groundline_924 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_groundline_924 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_wire_962 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_loose_point_983 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_loose_point_983 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_point_1004 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_extra_point_1004 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_facing_1022 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_facing_1022 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_grid_1055 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_grid_1055 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_line_1151 GeomShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_vert_1170 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_motion_path_vert_1170 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_1204 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_1204 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_pointcloud_1257 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_pointcloud_1257 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_gpencil_1230 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_prepass_gpencil_1230 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_detect_1272 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_outline_detect_1272 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_dot_1410 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_dot_1410 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_shape_1429 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_particle_shape_1429 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_wireframe_1589 VertShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nWARN (gpu.shader): OVERLAY_shader_wireframe_1589 FragShader: \n | \n | (#62) enable/warn/disable extension is not found. Extension \"GL_ARB_conservative_depth\" is not supported\n\nERROR (gpu.debug): : GL_INVALID_VALUE : generated before glGenTextures\n```\n\nStack trace:\n```lines=10\nblender.exe :0x00007FF6F22F7D90 bli_windows_system_backtrace_stack_thread\nblender.exe :0x00007FF6F22F7010 BLI_system_backtrace\nblender.exe :0x00007FF6F228C530 blender::gpu::debug::debug_callback\nblender.exe :0x00007FF6F228C3F0 blender::gpu::debug::check_gl_error\nblender.exe :0x00007FF6F220EE50 blender::gpu::GLTexture::GLTexture\nblender.exe :0x00007FF6F21F8420 blender::gpu::GLBackend::texture_alloc\nblender.exe :0x00007FF6F21F2E20 GPU_texture_create_2d\nblender.exe :0x00007FF6ED267400 DRW_texture_create_2d\nblender.exe :0x00007FF6ED267810 DRW_texture_ensure_fullscreen_2d\nblender.exe :0x00007FF6ED2A4F90 workbench_cache_finish\nblender.exe :0x00007FF6ED25E4D0 DRW_draw_render_loop_ex\nblender.exe :0x00007FF6ED25F5A0 DRW_draw_view\nblender.exe :0x00007FF6EDBC7820 view3d_main_region_draw\nblender.exe :0x00007FF6ED56D940 ED_region_do_draw\nblender.exe :0x00007FF6ED1660C0 wm_draw_window_offscreen\nblender.exe :0x00007FF6ED165F10 wm_draw_window\nblender.exe :0x00007FF6ED165A10 wm_draw_update\nblender.exe :0x00007FF6ED1488F0 ghost_event_proc\nblender.exe :0x00007FF6EDCB1E10 GHOST_CallbackEventConsumer::processEvent\nblender.exe :0x00007FF6EDCFD680 GHOST_EventManager::dispatchEvents\nblender.exe :0x00007FF6EDCFE2E0 GHOST_System::dispatchEvents\nblender.exe :0x00007FF6ED14A980 wm_window_process_events\nblender.exe :0x00007FF6ED140110 WM_main\nblender.exe :0x00007FF6ECDA03C0 main\nblender.exe :0x00007FF6F246FE74 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFF7DCC7020 BaseThreadInitThunk\nntdll.dll :0x00007FFF7E582630 RtlUserThreadStart\n```\n\n----\n\n[blender_system_info_1.txt](blender_system_info_1.txt)\n\n[blender_system_info_2.txt](blender_system_info_2.txt)\n\n[blender_system_info_3.txt](blender_system_info_3.txt)\n\n[blender_debug_output_2.txt](blender_debug_output_2.txt)\n\n[blender_debug_output_1.txt](blender_debug_output_1.txt)\n\n[blender_debug_output_3.txt](blender_debug_output_3.txt)" ]

[ "CRASH when click \"Viewport Shading - Rendered\" icon\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.5067\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nWhen click \"Viewport Shading - Rendered\" icon, Blender 2.8 crashes immediately.\n\nWhen clicking \"Viewport Shading - Rendered\" icon (between \"Viewport Shading - Look Dev\" and \"Viewport Shading > dropdown\" arrow icon, Blender 2.8 crashes immediately.\n\n\n\n", "CRASH when textures are applied in \"Look Dev\" with EEVEE\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.5067\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nCRASH when textures are applied with Look Dev. Happens every time.\n\n\nMethod 1\n1. Add \"Image Texture\" node in Shader Editor.\n2. Connect to \"Base Color\" in Principled BSDF node.\n3. CRASH\n\nMethod 2\n1. Add image texture by clicking on add (texture) button next to \"Base Color\" field in properties panel.\n2. CRASH\n\nUPDATE: Got it to work once after Blender had been running for a few minutes (no idea whether this makes any difference). Tried again by rebooting Blender > apply image texture from Properties Panel > select \"Look Dev\" render > CRASH\n\nUPDATE 2: Got it to work a 2nd time. Still seems to crash most of the time though.\n", "CRASH when \"Metallic\" property is set to maximum (anything above 0.999~)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.5067\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nCRASH when \"Metallic\" property in Cycles node is set to anything above 0.999~, i.e. maximum.\n\nCRASH when \"Metallic\" property in Cycles node and in Materials context tab area is set to 1.0. Maximum seems to be 0.999~. Reproduced this crash 4 times, each time with the exact same result.\n\nUPDATE: If value is set to 0.9999, the value is automatically converted to 1.0 with no crash. If the value is then set lower and then higher again using mouse drag, there is no crash either. But when rebooting Blender 2.8 and trying to set value to maximum (1.0) using mouse, Blender CRASHES again." ]

[ "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", "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).*", "Rigid body Bounciness parameter not functioning\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: 2.92 and version: 3.0.0 Alpha\nWorked: 2.83.13\n\nIn recent Blender versions the bounciness parameter of rigid bodies does nothing.\n\nOpen attached file, press space to start animation.\nOlder versions: ball bounces\nRecent versions: ball falls and immediately comes to an halt when it hits the surface of the cube.\n\n[Bounciness bug.blend](Bounciness_bug.blend)", "Regression: Damaged normals in sculpting with Multires modifier\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nWhen sculpting, sometimes breaks normals. Switching between modes fixes this.\n| Edited sculpture | Object mode |\n| -- | -- |\n|  |  |\n\n1. Open attached file.\n2. Go to Sculpt mode.\n3. Do something.\nLook at the fact that in some places the normals are damaged.", "Armature animation glitch when using collection instances across scenes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\nWorked: Probably never (2.90 is buggy still)\n\nWhen an armature is included in a collection, and that collection is instanced in another scene, selecting a bone or moving in the timeline creates a seemingly random time-jump in the posing/animation, until the bone is moved, at which point the whole armature snaps back into its real position.\n\nThis issue only occurs when an armature is included in a collection that is instanced in another scene. If the armature is not in a collection or is not instanced, the animation plays back as expected. The meshes under the armature does the same, if one mesh stays in the collection, the bug still happens, everything needs to be removed for the bug not to happen.\n\nWorkaround:\nMoving the bone causes the entire armature to snap back into its correct position, so this can be used as a workaround to keep the animation accurate. Alternatively, the armature can be removed from the collection and into the main scene hierarchy.\n\nThank you for looking into this issue.\n\n* Open attached file\n* Click on any bone\n\nThe pose will change. Change frame and pose will jump unexpectedly again.\n\nSome info that may be helpful: This issue seems to happen when persistent data is enabled and frame is rendered. Armature will then \"remembers\" last rendered frame. The cause may be linked to usage of Autorig pro addon.\n", "Rigid-Bodies Colliding Improperly\n[Basic Setup with bug 2.blend](Basic_Setup_with_bug_2.blend)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.81 (sub 13)\n\nSome of the Rigid-Body objects in the included .blend go flying when animation is played, as though they were intersecting each other, but they are not.\n\nOpen the included .blend.\nPlay animation. The two objects named \"Suspension.FL will go flying off in opposite directions.", "CYCLES: Surfaces inside volumes are Not Lit or Shadowed by the volume if the volume is not visible to Camera Rays\nLinux Mint Mate\nGTX 1050\n\n\nBlender 2.81 Alpha\n2019-09-27 22:44\nHash: 1c1a3198af9d\n\n\nDiscovered while trying to catch shadows from volumes on surfaces for compositing.\n\nSurfaces inside of volume meshes are not shaded (lit/shadowed) by the volume if the volume is invisible to camera rays\n(checkbox in Object Properties -> Visibility -> Ray Visibility -> Camera)\nAs far as i can tell this also affects Holdout.\n\n\n\n\nCurrent workaround: make sure volume IS visible to camera rays, and instead bypass it in the volume shader using the Camera Ray socket on the Light Path node\n\n\nTo Reproduce:\n\nOpen attached .blend , press render\nNote the missing shadow/light where the volume cubes intersect the default cube.\n\nI have in the .blend also included the \"expected behaviour\" by using the workaround, switch the Scene from \"Bug\" to \"Workaround\" and press render again.\nNote the shadow/light now covers the default cube properly.", "Mantaflow APIC creates wrong droplet behaviour\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Alpha\n\nIf you create a big ball of water with the APIC solver, it breaks apart when falling. FLIP keeps the ball spherical until it touches the collision and APIC deforms it incorrectly immediately.\n\n**FLIP** (left) vs **APIC** (right) \ntimesteps were set to MIN 4 and MAX 8\n[Drop_FLIP_vs_APIC.mp4](Drop_FLIP_vs_APIC.mp4)\n\n\n\n\n - Create any primitive (I used an Icosphere in my case)\n - Perform a Liquid quick effect on that primitive\n - Change the simulation from FLIP (where it works) to APIC (where it doesn't work)\n - Simulate and observe\n\n\nBased on the default startup or an attached .blend file [Droplet.blend](Droplet.blend)\n\n", "Automatic weights fails with small-scale mesh faces / armatures\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro #2000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.41\n\nBroken: version: 2.91.0\n\nCiao!\nThanx for the wonderful Blender!\n\nIn my VSA Project a \nRig fail if a specific vertice is in the mesh, I cannot understand why.\nIf I delete it \nOM - CTRL P [With Automatic Weights] success\n!??\n\nIn file _KO the vertice is present and Rig fail\nIn file _OK the vertice is NOT present and Rig success\n\nThe two test file in attach are identical but the OK is without the vertice.\n\nThere is no a function that stop the rig process and let me know where the error is maybe moving on to the next step?\n\n!! Sorry files are big, but is my first post and I don't know how to cancel the uploading process of them !!", "Sculpting Has Unexpected behavior when Saving work\n**Broken**: 2.83.4, 2.90 beta 97dc370c50ed\n**Worked**: 2.82\n\n\nGlitches in the non-active mesh after sculpting the active mesh, saving, and updating the viewport.\n\n\n[Ogre.blend](Ogre.blend)\n\n* Sculpt\n* Save\n* Refresh viewport (e.g., continue sculpting)\n\nThe artifacts should be visible immediately.\n\n**Original message**\n\nWhen I am sculpting and I go to save my work, after a successful save I get weird artifacts in the mesh that I havent made edits on in sometime. And it seems to be the same mesh every time. This has happened over 5 times so i figure its just a visual bug.\n\nGet 2 seperate meshes ready to sculpt, then sculpt on one and save your work. This is all i did to see the bug arise.\n\n\n", "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", "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", "FLuid Manta Flow Bug\nOperating system: Windows 10\nGraphics card: RTX 3070\n\nBroken: 2.9.1 / 2.9.2 / 2.9.3\nWorked: (newest version of Blender that worked as expected) 2.8.3 / 2.9.0\n\nCaused by 55fd7f55bd\n\n\nUnable to make fluid work properly inside a containiser let say a sphere. I need to make fluid to fill completely the sphere but i am unable to do that. On version 2.9.0 and 2.8.3 it works perfectly... on version 2.9.1 and beyond it does not work....\n\nToo much step to describe but to resume :\n\n1 spehere is fluid > flow\n1 sphere is fluid > colision\n1 cube is fluid > domain\n\nI refresh the cache multiple times, i invert normals on the sphere and so on but liquid don't go inside the sphere or pass through but if i put the fluid source inside the sphere no fluid goes inside...\n\n[fluide.blend](fluide.blend)", "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", "Some effects [bloom, smoke, fire, ..] still don't save in PNG with transparent background (occlusion vs. emission)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\n\nwatch?v=mQqV77PaOVs&t=84s\nHere this function of preserving BLOOM effect was released, and now it work both on View mode and render mode. BUT! When you will try save PNG after rendering - you will have same result as in past, without blooming effect saved on alpha channel.\nHere is example: \n\n1 - open file [BLOOM BUG.blend](BLOOM_BUG.blend)\n2 - press F12 [render]\n3 - save result in PNG\n4 - open result in any paint software and put under result layer any colour\n\n" ]

[ "Fluid collision doesnť work for objects with armature modifier while \"preserve volume\" option is checked\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nDescribed in title. Found out after switching from 2.79, fluid stopped colliding with rigged character for no reason.\n\nOpen appended file. Try baking the simulation while \"preserve volume\" option is on and off, see different results.[fluid_armature_bug.blend](fluid_armature_bug.blend)\n" ]

[ "Armature modifier taking a performance impact, even when set to not be visible.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.2\n\nSome part of the Armature modifier is still calculating even when set to not be visible.\nCausing a performance impact, when an artist expects none. Other modifiers like Subdivision Surface do not have this issue.\n- unrelated, also kinda sucks that I get sub 24fps with 100k poly videogame ready models.\n\nHave a high poly model weighted and bound to an armature, with any simple animated movement. Take note of the viewport performance when viewing playback of the simple animation. Disable all visibility options on the Armature modifier on the model. Performance only increases slightly. Uncheck 'bind to vertex groups' on the modifier. See performance improve drastically, even though the modifier is set to not be visible in the first place.\n\nWith the attached blend file, a high poly model is already bound to an armature with a simple animation.\n[ArmatureModifierBug.blend](ArmatureModifierBug.blend)\n\n", "Cursor frozen when switching to walk/fly navigation while moving the mouse\nOperating system: Windows 10\n\nBroken: 2.82 (sub 3)\n\nSwitching to walk/fly navigation through the shortcut while moving the mouse, causes the cursor to become stuck. The cursor remains stuck until the mouse isn't moved anymore for a short moment.\n\n\n - Move the mouse around in 3D view.\n - While moving the mouse press the shortcut to enable walk/fly navigation.\n - Continue to move the mouse and observe the cursor not following the mouse movement.\n - Stop moving the mouse.\n - Move the mouse again and the cursor should follow as expected.\n", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "Statistics Viewport Overlay Showing Incorrect Value\nOperating system: Windows 11\nGraphics card: Nvidia GeForce RTX 1650\n\nBroken: 3.6\nWorked: Every other version I've used so far\n\nWhile working in the viewport, the \"Viewport Overlay: statistics (edges count)\" glitches out and shows the wrong number. Sometimes being absurdly high. The image shows the main objects in my scene with the most geometry, mostly being 2k to 10k faces each. It gets a bit annoying when I can't see the right count. I'm not sure how to reproduce the error on command, but I'll keep looking!\n\nBased on the default startup or an attached .blend file (as simple as possible).\nIt happens mostly while I swap in and out of pose mode but then again, I'm not too sure. However, this is usually the last action I take before I notice. I'm sorry for the insufficient information, but I hope you find the problem.\n\n", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n ", "MetalRT: Rendering being unresponsive with AO node\nOperating system: Ventura 13.4.1\nGraphics card: Apple M1 Max 32 Core\n\nBroken: Blender 3.6 LTS\nWorked: Blender 3.5.1\n\nAfter downloading the newest Version of Blender it seems that using the Ambient Occlusion Node need leads to Blender being unresponsive. Sample count stays on 0 and neither Viewport nor F12 Render is starting as expected. Trying to quit, Blender crashes completely.\n\n- Add new material\n- Add Ambient Occlusion Node\n- Select cycles and GPU\n- Enable MetalRT\n- Start Viewport Rendering.\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 ", "Use draw manager for clip editor drawing\nCould be stalled to 2.93 as there isn't an real issue here as far as we are aware of. The compositor issues are more tangable.", "Regression: lag from camera view when using mouse scroll\nOperating system: Windows 10\nGraphics card: Nvidia Titan XP\n\nBroken: 3.3.1-3.5\nWorked: 3.2\nCaused by befe38fe1d\n\nMassive lag in camera view mode with objects about 20 mil triangles when using mouse scroll with view locked to camera even in Solid preview mode. When using Ctrl Alt mouse move seems no lag, scroll works as usual. Only scrolling is not working properly, rotation works nomally.\nIn this video: Blender 3.3.1, two separate cubes subdivided to level 10, first trying to scroll with mouse wheel - it lags, then using Ctrl Alt Mouse - no lag, then again with mousewheel - lag. No matter if GPU subdivision is on or off.\n\n- Open attached .blend file\n- first trying to scroll with mouse wheel - it lags\n- using Ctrl Alt Mouse - no lag\n[Blender Mouse scroll issue.blend](Blender_Mouse_scroll_issue.blend) \n[Lag when in camera view Blender 332.mp4](Lag_when_in_camera_view_Blender_332.mp4)", "Mouse leaves window during walk navigation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.3.0\n\nmouse goes out in walking navigation\n\n\n- Simply open any file\n- Activate walking navigation and turn the mouse from top left to bottom right quickly several times (between 3 and 5 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)", "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", "Topbar gliches\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.3 Beta\n\nThis only happened on windows.\nWhen Status Bar is hidden and Resolution Scale is greater than 1, the Top Bar sometimes becomes unusable. (look at the end of video)\nMy guess it has something to do with notifications that are now displayed at Top Bar.\n[bug.mp4](bug.mp4)\n\nSame as in the video\n- On the `Windows` tab disable `Show Status Bar`\n- Go to {nav Edit > Preferences... > Interface} and change the `Resolution Scale` to 1.2\n- Save Preferences\n- Close the Temporary Window\n- Reopen the `Blender Preferences` window ({nav Edit > Preferences...})\n- Press `Save Preferences`\n\nInvoking save as temporary window also causes this issue\n\nTrying to resize Top Bar area or maximizing some other area fix the issue.", "Lag Adjusting Value Sliders & Navigating Nested Menus with a Wacom Tablet\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93.2\n\nTrying to change the value of shapekeys or shader sliders with my stylus doesn't get detected the first few seconds, then picks up, but in a non responsive way. Also while using my stylus, if I navigate to a nested menu like say \"Object > Transform\" There's a Lag when moving to another option in the \"Object\" Menu.\n\nThe steps above should apply. I did notice though, that if I change my Tablet API from 'Automatic' to 'wintab' in the the input preferences, it helps, but its still not as responsive as it is in 2.93\n\nAll these issues though, were non existent, if I tried using my laptop's trackpad. Also, my tablet is a Wacom Intuous Touch 5 with a stylus that supports up to 2048 levels if pressure sensitivity and has tilt support, just incase it could be any of these causing the issue. \n\nThanks.\n\n", "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" ]

[ "Blender mouse lags\n|Operating system:|Windows 10\n| -- | -- |\n|Graphics card:|`EVGA RTX 2080TI`\n||Also seen in a `GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67`\n|CPU:|AMD RYZEN 9 3950X 16-Core Processor, 3500 Mhz\n\nBroken: version: 2.83.2, branch: master, commit date: 2020-07-09 05:50, hash: 239fbf7d93\nWorked: It has worked before (but the version has not been informed yet)\n\nThis is a very minor glitch but I still find it very jarring.\nWhen I move the mouse around the UI it is really choppy, looks like the mouse is moving at around 24 - 30 FPS.\nbut if I do anything else like, moving/scale objects panning camera I am getting a 165FPS smooth experience.\nIt was like this in 2.83. Its not a problem I can still use Blender but it feels like quite a choppy experience seeing you are moving your mouse around half of the time.\n\nLiterally start a new project or open one , its always laggy\n[example.blend](example.blend)\n" ]

[ "Error \"Gizmos hidden in this view\" when trying to delete with measure tool and gizmos disabled\nOperating system: Windows 10 64 bit\n\nBroken: 2.83 release, 2.90 ec776f18ff70\nWorked: blender-2.82a-windows64\n\nIf the \"Measure\" tool is selected AND gizmos are turned off (\"Show Gizmo\", in the top right next to \"Overlays\"), trying to delete with the X Shortcut will result in the error \"Gizmos hidden in this view\".\nIf either\n* another tool is selected, or\n* gizmos are enabled\ndeleting works as expected.\n\n[delete_without_gizmo.blend](delete_without_gizmo.blend)\nOpen the file.\nHit the X key.\n\n", "Edge overlay seems to do nothing expected\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.1.0\nWorked: 2.79\n\nBack in 2.79, we could disable the \"edge\" overlay in edit mode. This was useful I.E. in cases where highlighting edges in vertex selection mode made things hard to read :\n\n\nIn the current stable version, this option seems to do nothing:\n\n\n\nActually, when in solid mode, it seems to display another layer of wireframe on top of the already existing one, which definitely looks weird and pointless. GIF demo:\n\n\n\nOn a mesh in edit mode, try toggling the edge overlay on and off.\n\n", "Armature layers can be put into an invalid state via the Python API\nThis is the Blender-side issue corresponding to [this addon report](104535).\n\nBroken: at least 3.6, and also latest main.\nWorked: unknown.\n\n\nUsing the Python API it seems to be possible to put armature layers into an invalid state. For example, here you can see that the layer buttons indicate that the bones are supposedly on a hidden layer, and yet they are visible:\n\n\n\nAdditionally, they *behave* as if they are on the currently visible layer. E.g. hiding and showing that layer hides/reveals those bones.\n\n\nCurrent reproduction steps involve Rigify and an external Rigify feature set:\n\n1. Enable the Rigify add-on.\n2. Install the Rigify feature set [\"Experimental Rigs\" by Alexander Gavrilov](angavrilov-rigs).\n3. Create an empty armature (by e.g. adding a single-bone armature and then deleting that bone).\n4. In edit mode on that armature, go to the Rigify samples and add the sample for `body_ik.leg`\n\n\n**Expected result:** armature layers are in a valid state.\n**Actual result:** armature layers are in the afore-described weird and seemingly invalid state.\n\n", "Sculpt: masks / face sets invisible in X-ray mode\nOperating system: Windows 10\n\nBroken: 2.91.0\n \nSculpt mask is invisible in X-ray view mode, but you can still paint the mask while in Xray.\nThis makes it hard to trace the background image when masking.\n\n \n\n", "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", "Bisect Tool rotation handle does not work from some preset orthographic views\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.91.2\n\n\nBisect Tool rotation handle does not work from some preset orthographic views.\n\n* Select default cube\n* Enter edit mode\n* Press numpad 1 to enter front orthographic view\n* Select all verts\n* Click bisect tool\n* Draw line across cube\n* Click circle widget to rotate bisection <- fails\n\nWorks fine from top orthographic view and from arbitrarily orientated perspective views.", "X axis isn't showing in camera view like Z axis \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.2.1\n\nX axis isn't showing in camera view like Z axis when we activate it from viewport overlays:[2022-07-06 22-43-44.mp4](2022-07-06_22-43-44.mp4)\n\n", "Camera Gizmo - Turning off Focus Distance has no effect\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.81 (sub 1)\nWorked: (optional)\n\n\nViewport Gizmos - Turning off Focus Distance has no effect\n\n[Based on the default startup or an attached .blend file (as simple as possible)\n\nSelect the camera. Turn on Limits in Viewport Display Panel of the camera. Focus Distance is dependant of this to be on. Now turn off Focus Distance. \n\nNothing changes. Shouldn't the yellow widget disappear? And why hide a widget that you explicitely have to turn on before?\n\n\n\n", "UDIM grid changes and enhancements\nThe UDIM tile grid behaves oddly/inconsistently in many circumstances for both configuration and display. This design tasks will hopefully a) enumerate the most egregious issues b) provide a place for artist feedback on the proposals c) document the ultimate decision for each item below.\n\nComplete\n- [x] The UV tile grid no longer disappears as soon as an image is loaded into the UV editor space (4fb7217043)\n- [x] [D11862](D11862): Provide a way to disable the grid entirely and respond to the Overlay toggles. Move current UI into Overlay panel as well. \n\nFuture design / discussion required\n- [ ] Should the tile grid only have manual/static dimensions or should it automatically adjust if the user moves a UV point outside the current dimensions of the grid?\n- [ ] Should the tile grid also be shown in the Paint/Mask/Viewer modes in addition to UV edit?\n- [ ] Should anything different be done about the grid when displaying non-square images?\n\nFeedback thread: 20136\n\nThis task will be used for general organization. Most feedback should be provided on the DevTalk thread above.", "GN: Delete Geometry node hides edges in some cases\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.2.0 Alpha\n\nHard to describe this one more abstract..\n\nI start with a mesh line primitive (0,0,0) (0,1,0) and extrude it **n** times along **x** to get a grid.\nNow I try to delete all points with a distance from the **y** axis greater than **d** \nWhenever **d** lies between the first and the last extrusion, the edges of the starting primitive are not displayed.\nIt shows up in the spreadsheet however and reappears if I apply the modifier and tab into edit mode and back \n\n[2022-02-05 19-27-50.mp4](2022-02-05_19-27-50.mp4)\n[del_geo_node.blend](del_geo_node.blend)\n\n", "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. ", "Mesh Analysis broken by Hidden Wireframe\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.93\n\n\nThe Mesh Analysis overlay seems to draw only back faces when the Hidden Wireframe overlay is also enabled:\n\n\n\nThe vertical red streak is Suzanne's right ear, which should probably be occluded. The back faces of the right eyebrow are also rendered green, but the front faces of the left one aren't.\n\n\nTurn on both the \"Mesh Analysis\" and \"Hidden Wireframe\" overlays in Edit Mode.", "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.", "When \"Pie Menu on Drag\" is enabled in user prefs, Ctrl + Z has a tendency to open the shading menu by accident\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52\nbuild date: 2019-07-06, 01:03:01\nplatform: Linux\n\nThis may be more of a design issue than a bug, but it's happened to me about 100 times now and it's quite irritating.\n\n**To reproduce:**\n\n - enable User Preferences > Keymap > Preferences > Pie Menu on Drag.\n - open a complex scene (one where the undo operator will have a significant lag) \n - fill the undo history with events, as though you've been working for a while\n - Press Ctrl + Z a couple times while moving the mouse a bit, rolling your hand so that Ctrl is released just before Z (in the manner of a busy artist)\n\nIf the user happens to release Ctrl earlier than Z while moving the mouse, this can bring up the shading menu, interrupting the user's workflow. This may sound like an edge case, but when working quickly, it's actually really frequent and annoying! It seems to especially effect large scenes where there is a lag in the effect of the undo operator.\n\nIdeally, the \"Pie On Drag\" feature should not listen for key presses if those key presses were part of a different combination that has yet to be completely released. What do you think?", "Links persist invisibly after their source sockets are removed\nBroken: Probably forever (e.g. 3.0, 3.1)\nWorked: N/A\n\nIf the output socket of a node is removed, the input socket it was connected to does not show a button to input a value. It acts like it's still connected.\n\n**Detailed replication**\n1. Go into the Shader Editor\n2. Create the *Voronoi Texture* node and a *Math* node\n3. Set the *Voronoi Texture* node to 4D, and plug its new W output into the *Math* node\n4. Set the *Voronoi Texture* node to 3D. Observe that the input on the *Math* node still acts like it's connected\n5. Click and drag from that input on the *Math* node. A bogus wire will appear from the *Voronoi Texture* node, coming from where the W output used to be.\n\nYou can then plug this wire into another socket. It will disappear again once you let go. If you set the *Voronoi Texture* node back to 4D, the wires will re-appear.\n\nVideo example:\n\n[XwBMq60aMI.mp4](XwBMq60aMI.mp4)\n\n**Another example:**\n\n{[F13079601](free-socket.blend), size=full}\n\nIn this case you can even save the file in this state where you can't see or edit the value of the node until you disconnect it.\n\n" ]

[ "Impossible to show only x/y axis in ortho front/side view\nOperating system: Win 10 64bit\nGraphics card: Geforce 940M\n\nBroken:\n2.80, 1fc75dbbceea, blender2.8, 2018-12-19\n\n\nwhen in I am ortho front or side view, and disable all but the horizontal (x/y) axes the z axis always shows nevertheless.\nbecause sometimes I just want to see the horizon" ]

[ "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", "Grease pencil. Mask not working when masking layer has more than one keyframe\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\nWhen my masking layer has only one keyframe, masked layers display as expected. When my masking layer has more than one keyframe expected masking doesn't happen.\n\n* open .blend (the mask layer has two keyframes, both having the same filled shape)\n* expected result: the strokes on the 'marks' layer that intersect the shape on the mask layer are always visible\n* actual result: the strokes on the 'marks' layer that intersect the shape on the mask layer are only visible after i delete the second keyframe on the 'mask' layer\n\nWhile dragging the timeline play head the marks layer appears as expected, correctly masked. But when i release the mouse button the marks layer disappears entirely again.\n\n[isthisamaskbug.blend](isthisamaskbug.blend)", "Poly Build Tool: Editing poly build keymap causes poly build tool to not work properly\nWindows 10\nGeForce GTX 1080\n\nv2.81 Alpha\nDate: 2019-09-10 15:07\nHash: 8f55794c0e80\n\nWith a default blender open, edit the poly build keymap. The tool doesn't work properly with the new key assignment. \n\nFor example, switch 'face at cursor move' to shift + left mouse, and 'poly build delete at cursor' to ctrl + left mouse.", "Action editor key frames not displaying sometimes\nSometimes when working with multiply animations and switching through them in the action editor. The Keyframes stop displaying for certain action. \nWhen the Panel with the action editor View is removed and added again, the displaying is working again.\nThis bug was seen in Version 2.76 and daily Build from 10/30/2015.\n\nError:\n\nFixed after closing and opening action editor view\n\n\nMy Project without Mesh. Bug is seen in walk_back_cycle action.\n[animation_editor_error_project.blend](animation_editor_error_project.blend)\n\nThis bug is very annoying in my workflow.\n\nGreetings and thank you for your work!", "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", "Color Ramp node keyed colors and keyed positions jumps to the next color stop when adding or removing color stops\nBroken: 2.7x, 2.8x\n\nThe keyed color and position should be assigned to the color stop itself, not it's order. As of now it follows the order of stops, so the keyed color and position jumps from one color stop to next one when a color stop is added or removed.\n|[2020-06-16 17-27-47.mp4](2020-06-16_17-27-47.mp4)|[2020-06-16 17-13-58.mp4](2020-06-16_17-13-58.mp4)\n| -- | -- |\n\n- open blender \n- go the shader editor\n- make a new material\n- add a color ramp node\n- Press \"i\" with the mouse hovering the black bar to key the color.\nnow the white color stop and do the same, key the color by pressing \"i\" over it.\nnow select the black color stop and remove it by clicking the \"-\"\n- press space bar to play, the keyed color will jump from the black one that was removed to the white one.\nThe same happens if you key the color stop's position instead of it's color.\nIt also jumps when adding in a color stop instead of removing one.\n", "Some transform modes don't apply absolute grid snaping \nOperating system: Windows 10 \nGraphics card: GTX 1080 ti \n\nBroken:\nBlender 2.8 January 31, 01:48:40 - 8c8979067490 Beta\nBlender 2.79 (It worked)\nBlender 2.77 (It worked)\n\nAbsolut grid snaping dont work with \"Face Inset\" and neither with loop cuts. \n\nTurn on the snaping (increment) -> turn on absolut grid snaping -> spawn a plane -> try to snap while loop cutting or inseting faces.", "Midpoint snap always turn on when panning with shift + middle click if use knife tool\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\nCPU : intel i3 2328m\n\nBroken: version: 3.0.0 Alpha\nWorked: ??? (i think before the gsoc knife feature is merged)\n\nmidpoint snap in knife tool get turn on(like a toggle) when panning if use knife cut\n\n1. use knife tool\n2. click some where to start cutting until purple line appear and click where you want cut\n3. pan with a shift + middle click\n4. see on bottom bar the midpoint snap option is turn on and not turn off until i click shift again (it behave like a toggle i think)\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", "TEXT outer and inner edge problem with letters. Vertices overlap when offset with \"fillMode\" \"Node\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.83.13\n\nVertices overlap when offset with \"fillMode\" \"Node\"\nThe issue is that a fusion360 user explained to me that in that program there is the OFFSET tool to create inner and outer edges in texts. It is a fundamental tool in any program. I thought I could solve it this way and there I found this problem that can be considered a bug.\n[BORDES EN TEXTO.mp4](BORDES_EN_TEXTO.mp4)\n\n\ncreate 2 texts\nA normal one.\none with fillMode Node to create an outer border\nmake sure that in the 2 texts there is a letter N\nIn the geometry property of the text with fillmode Node put offset 1 and Depth 1\nIn the N you will see this error.\n\n**I would have to calculate so that the vertices don't overlap.**[2021-05-24 15-09-04.mp4](2021-05-24_15-09-04.mp4)\n\n\n[BordeBug.blend](BordeBug.blend)\n\n", "Keyframes and drivers on custom nodes properties seem not working\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 540 Intel Inc. 4.1 INTEL-12.4.7\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI'm not able to animate the properties of custom nodes. Keyframes do not work properly: when I set one all the others seem to disappear and only the last value set as a keyframe is shown on every time step.\n\n1. Go to the text editor, import the 'Custom Nodes' template and run the script.\n2. Open the 'Custom Node Tree' area.\n3. Add a 'Custom Node', in the 'Some Nodes' category.\n4. Add a keyframe for 'my_float_prop' on frame 1.\n5. Change the frame, change 'my_float_prop' value and set a keyframe.\n6. Now I should see (at least it was like this in the last version) the property changing while scrolling through the timeline between the two keyframes I just set, but I don't. The property keeps the last value.\n", "Blender 2.7x keymap: Add reroute shortcut (shift right mouse) doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.91\n\nCaused by 58e554a55c\n\nShortcut for add reroute doesn't work in node editor.\n\nTry add reroute between two connected nodes using shortcut (shift + RMB during cross line).\n\n", "Design: More frame snapping options\n## Problem\nWhen dragging the frame cursor around you often want to hit keyframes.\nCurrently this is hard to do, especially when zoomed out. (also because you are not sure when you've hit the key)\n\nFrame snapping already exists, but it only snaps to seconds.\nThis is activated with `CTRL`\n\n## Design Question\n* Where in the UI should this functionality live\n* How can this feature be discoverable and understandable for users\n* What are the snapping options required and how do they work\n\n## Things to consider\n* there is different snapping behaviour in the VSE, so different time editors can have different snapping functions. This needs to be clear to the user\n* In the graph editor and the dope sheet there is already a snapping menu, but that is for snapping the keys while moving them. How do we differentiate the two\n\n## Proposed Solution\nThe idea is to add an option to the way the snapping is performed, e.g. either to seconds or to keys (or another snap type)\n[2021-10-02 19-50-20.mp4](2021-10-02_19-50-20.mp4)\n\nThe snap type would be chosen in a dropdown menu\n\n\nThe subframe setting would be moved to a scene setting\n", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "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" ]

[ "AutoMerge Keyframes only deletes unselected keyframes (scaling muliple selected to zero or snapping to the playhead fails)\n\n\nLinux Ubuntu & GeForce GTX 580\n\n\nBroken: master\n\nWith \"AutoMerge Keyframes\" toggled on it simply doesn't do that, whether you're scaling keyframes or moving them around.\n\n[auto_merge.blend](auto_merge.blend)\n\nMake an armature, go to pose mode and set keyframes on the bone. Scroll forward a few frames, move the bone around (and rotate) and key it again. Do this a couple of time so you have some keys to work with.\n\nIf you select all the keys in the dopesheet editor and scale them down so some of them land on the same frame, blender doesn't automerge them. The keys seem to still exist on the same frame, as you can see in the graph editor. Even if you select all the keys and move them by one frame (which should trigger the automerge) it still doesn't merge the keyframes.\n" ]

[ "Hidden user for Geometry node group\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\nNode group after delete still have user and do not appear in Orphan Data outliner.\n\n[2021-03-19_13-02-52.mp4](2021-03-19_13-02-52.mp4)\n\n- Open attached file or:\n - In the default Cube scene, open the Geometry Node editor\n - Press `New` and optionally rename to \"1\"\n - Duplicate the node tree and optionally rename \"1.001\" to \"2\"\n - In the node tree \"2\" add a group of the node tree \"1\" (If you switch to tree \"1\" you will see that tree \"2\" has 0 users)\n - Save the file with the tree \"2\" as the active\n - Reload the file saved\n - Switch to tree \"1\" (you will see that tree \"2\" still has users)\n[GN HiddenUser.blend](GN_HiddenUser.blend)", "Objects do not retain View State when turning Collections Off then back On\nOperating system: Linux-5.8.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0\n\nIf an object has been hidden within a collection, after turning the collection off and then back on the object becomes visible again. It's \"hidden\" state is not retained.\n\n\n- Drag the cube into a new collection\n- Disable `Hide in viewport (eye button)` option for cube\n- Disable `Exclude from view layer option (checkbox)` for collection.\n- Enable checkbox, now cube is visible (it should not)\n\nResult = the cube is visible, it should remain hidden.\n\nN.B. This does not affect whether the cube is hidden from renders - the render view state is retained.\n\n", "UI BUG: Icons in the property editor \"flicker\" when you hover them or click on them\nOperating system: Windows 10, 64 bits\nGraphics card: Geforce 1080 8gb, Geforce 1070 8gb\n\nBroken: blender-2.90.0-874af5301cdf-windows64\nWorked: 2.83.0 LTS\n\n\nIcons in the property editor annoyingly flicker, they change border thickness 1-2 pixels upon hovering over or clicking on them.\n\nThin:\n\n\nThen they get thicker:\n\n\nIt's very visible if you use Icon border settings in your theme and many monochrome themes dop use that setting, because not everyone wants to see distracting rainbow colors in their UI.\n\n\nGo to Blender Preference, Themes.\nOpen Icon colors tab and set icon border to 1.\nEssentially use any bright theme as it is very visible when your theme is bright and icons have borders.\n\n\nHover over icons in the property editor, see the flickering.\n\nHere's the video of the bug:\n\n[2020-06-22 01-18-44.mp4](2020-06-22_01-18-44.mp4)\n\n\n", "Edge masking artefacts on higher subdiv levels when removing the mask from lower subdivs\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90 (sub 2)\n\nThis is a follow-up report on this bug report I made: T76386\n\nTo quickly summarise, there are still masking artefacts that aren't removed when you delete a mask at a lower subdiv level. It only deletes the mask that all subdiv levels share, but in the process the edges of the mask remain at the higer levels because said geometry doesn't exist on the lower levels. This causes problems like these to occur:\n[Desktop 2020.05.17 - 00.35.46.01.mp4](Desktop_2020.05.17_-_00.35.46.01.mp4)\n\n\n1) Take a cube and subdivide it.\n\n2) Go down to level 0 and try to mask the mesh, which will be completely invisible. Then pick any subdiv level above it and mask.\n\n3) Remove the mask at a lower subdiv above level 0 and then move up one level. The mask edges should still be there.\n\n4) Repeat 3) until you reach the highest subdiv level.", "FADE INNACTIVE GEOMETRY MODE doesn't work properly with COLLECTION INSTANCES\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\n\nI really like this mode, but it feels likeit not completely done. It's not work with collection instances at all.\nHere is was my expectations and what it looks like currently: \n\nAnd even instances from other scenes ignore this mode too. Will be cool if it(instances) will work in stream ideology of this mode\n\n\nOpen this file [FADE INNACTIVE GEOMETRY DOESN'T WORK PROPERLY WITH INSTANCES.blend](FADE_INNACTIVE_GEOMETRY_DOESN_T_WORK_PROPERLY_WITH_INSTANCES.blend) and select (one by one) buttom figures (cone/torus/cube) and after selecting each one - press Tab.\nYou will see that instances ignores this mode\n\n", "Armature animation glitch when using collection instances across scenes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\nWorked: Probably never (2.90 is buggy still)\n\nWhen an armature is included in a collection, and that collection is instanced in another scene, selecting a bone or moving in the timeline creates a seemingly random time-jump in the posing/animation, until the bone is moved, at which point the whole armature snaps back into its real position.\n\nThis issue only occurs when an armature is included in a collection that is instanced in another scene. If the armature is not in a collection or is not instanced, the animation plays back as expected. The meshes under the armature does the same, if one mesh stays in the collection, the bug still happens, everything needs to be removed for the bug not to happen.\n\nWorkaround:\nMoving the bone causes the entire armature to snap back into its correct position, so this can be used as a workaround to keep the animation accurate. Alternatively, the armature can be removed from the collection and into the main scene hierarchy.\n\nThank you for looking into this issue.\n\n* Open attached file\n* Click on any bone\n\nThe pose will change. Change frame and pose will jump unexpectedly again.\n\nSome info that may be helpful: This issue seems to happen when persistent data is enabled and frame is rendered. Armature will then \"remembers\" last rendered frame. The cause may be linked to usage of Autorig pro addon.\n", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Transform Gizmos still visible when switching modal operation\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.3.0 Alpha\n\nRecently a change has been done to make the move, rotate and scale gizmos visible while dragging them.\nBut while dragging the gizmo you can still use modal shortcuts to switch to a different operation like move, rotate, scale, or even edge/vertex slide in edit mode.\nIf that happens the gizmo freezes in the current cursor position and doesn't change anymore.\n\n- Use the move tool\n- Drag the gizmo\n- While dragging press R or S\n\n- In Edit Mode use the move tool\n- Select an edge and drag the gizmo\n- Press G while dragging\n\n", "In spreadSheet Values ​​not visible\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\nMeasurements not visible\n, columns are not expanded, not sorted, not rearranged\n\n\n- Open attached file\n[long_integer_attrs__spreadsheet.blend](long_integer_attrs__spreadsheet.blend)\n\n", "Remove BKE_layer_collection_resync_forbid and BKE_layer_collection_resync_allow\nThese can be removed after each area has been checked and optimized to use the new structure (synced_ensure)\n\nRecently ceb0e7fcea was done and added a use for resync_forbid. This makes this ticket perhaps irrelevant?", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n", "Black render artifact with CPU+GPU rendering in viewport\nWindows 7 Pro\nNvidia Quadro P6000\nIntel Xeon E5-2690 v4\n\nBroken: daily builds 2.79 since at least 25.10.2017.\nWorked: -\n\nIf I enable combined CPU+GPU rendering, a black rectangle shows up on one of my objects. It shows up in viewport rendering, and also in the final render. This seems to be independent of the material used. I have provided a stripped down version of the scene where it is still visible. This time only in the viewport, the final render works for this simplified scene. \n\nThe artifact seems to be \"locked in space\", I can move or rotate the object away, so that it disappears. In some rotation angles it is not a black rectangle, but dense black lines. \nWhat is also interesting is that the surface of the object in not only black, but partly transparent. I have put a lamp and a cube inside the object in the demo scene, these should not be visible from outside, but they are.\n\n- Open file. In the render settings GPU compute should be turned on, and in the user preferences CUDA should have both the CPU and GPU selected.\n- Turn on viewport rendering. --> black box visible.\n- Then switch to CPU rendering. No more black box.\n\n[black_artifact_bug3.blend](black_artifact_bug3.blend)\n\n", "shadow catcher appearing in vector pass\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nvector data is present for the shadow catcher objects. This needs to be omitted otherwise the vector blur node can't be used to add motion blur to the 3d elements, because unwanted motion blur will be added to the environment pass. If it a backplate was used then it wouldn't be a problem, transparent film could be set, and the blur would only affect the geometry. This also has an issue though, because the vector blur pass modifies the alpha too, so the shadow catcher vector could still affect the blur of the 3d geometry even if it's hidden by transparency.\n\n\n1. open attached file\n2. go to frame 10\n3. open the compositor\n4. render still frame\n5. check the compositor backdrop (shows vector data for the shadow catcher).\n\nSame result if film is set to transparent.\n\n", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Parented camera not animated when switching view with markers and collection is disabled\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.5.0 Alpha\nBroken: version: 3.4.1\nBroken: version: 2.83.9\nWorked: probably never\n\nIn a scene with multiple cameras and markers used to switch between them, if the collection containing the cameras is disabled (hidden with the monitor icon) and the cameras have an animated parent, only the camera active at the start of playback will be animated. The animation works fine when the collection is shown.\n\n\n\n\n\n[bug_report_marker_cam_anim.blend](bug_report_marker_cam_anim.blend)\n- Open the attached blend file\n\n- Play the animation\n - The result is staggered because only one camera is animated\n- Show the Cams collection and play\n - The result is smooth because both cameras are animated—this is the expected behaviour.\n\nWhen the collection is hidden:\n\n\nWhen the collection is shown:\n" ]

[ "Objects in hidden collection become visible when the hidden collection gets parented to a visible collection\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02\n\nBroken: version: 2.81 (sub 8)\n\nWhen I hide collection with unhidden objects and then parent this collection to unhidden collection the objects become visible.\n(And even if you move collection back the objects is still visible).\n\n**1.** Create 2 collections (Collection_1, Collection_2)\n**2.** Select Collection_2\n**3.** Spawn an object inside\n**4.** Then hide Collection_2\n**5.** Move Collection_2 inside Collection_1\n**6.** BOOM! Objects inside Collection_2 are visible even though the collection is hidden\n\n{[F7724854](ezgif.com-resize.gif), size=full}\n\n[CollectionBug.blend](CollectionBug.blend)\n\nThanks! =)" ]

[ "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", "Blender crashes as soon as an image texture is plugged in the material BSDF node\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\nSee attached log for more detail\n\nBroken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions\nWorked: ??? The earliest available build, 2.93.18, also causes the same crash\n\nThe second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes\n\n**Similar tickets**\n#76193\n#76377\n\n1. Start Blender.\n2. Create new default file.\n3. Select the default cube.\n4. Switch to Shading workspace.\n5. Add Image Texture node.\n6. Create new image or select an existing one.\n7. Plug Color output to the Base Color input of the Principled BSDF node.\n8. Watch Blender shut down.", "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.", "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", "Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.0\nWorked: --\n\nLow resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to \"closest\" in the material shader.\n\nfeature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.\n\nplace object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. \n\ntextures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from \"linear\"(or whichever is set to default) to \"closest\"\n\nWe have 4 materials each having individual Image Texture nodes (but all using the same image).\n\nIf you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.\n\n", "Blender crashed in edit mode with material index creazy and strange normal\nOperating system: Linux pop-os 5.17.5-76051705-generic\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.1.0 / blender-3.2.0-stable+v32.e05e1e369187-linux.x86_64-release\n\nAn object imported from I don't know where, with crazy material_index : (-30086) in spreadsheet editor, and with strange normal, makes blender sik.\n\nIn edit mode, if I try to move the concerned geometry blender crashes systematically.\n\n[2022-06-16_bug-normal.crash.txt](2022-06-16_bug-normal.crash.txt)\n\n[2022-06-16_bug_system-info.txt](2022-06-16_bug_system-info.txt)\n\n[2022-06-16_bug-normal.blend](2022-06-16_bug-normal.blend)\n\nthank you,\n - Thomas", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Regression: Image Editor Texture Draw Stops Updating\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0 (probably introduced by {f663a1dc09}?)\nWorked: 3.0\n\nthis was actually exposed with 507a4deef1 (but we have seen before that that commit is not the real cause for a couple of issues -- @lichtwerk)\n\nImage on Image Editor -> Paint does not update when being drawn on at certain close view levels until the viewport is moved \n\nLoad default scene\nSwitch to Texture Paint tab\nCreate new image\nZoom in 7 or 8 times (for reference I am using a scroll wheel that has steps)\nDraw on the image\nIt will sometimes update fine, sometimes stop updating when it passes over a what looks like a UV boundry, that extends off the screen\n\nSee gif where I added a material to it\nSorry if this has already been reported, haven't been able to find a public bug tracker\n[image_paint_bug.blend](image_paint_bug.blend)\n\nThis is the file I (-- @lichtwerk) used on linux to bisect/reproduce on a 1920x1080 display (since this seems to depend on monitor/zoom etc):\n[image_paint_bug_repro.blend](image_paint_bug_repro.blend) ", "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", "Blender crash in bmesh.to_mesh() while using it to modify weights\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCrash in bmesh.to_mesh() if using it to modify weights in weightpainting while playing animation\n\n*Remove any lights or cameras, keep just one cube in the scene (for the simple script to work).\n*Subdivide it 5 times and apply the modifier.\n*Add the script below to the script editor and run it\n*Go to weight paint mode for the cube\n*Run the animation and try to paint. If you just click the left mouse button it will paint a dot and the script will work, but if you hold and drag, Blender crashes.\n\n\n```\nimport bpy, bmesh\n\n\ndef add_handler():\n # remove existing handlers\n old_handlers = []\n for h in bpy.app.handlers.frame_change_post:\n if \"paint_test\" in str(h):\n old_handlers.append(h)\n for h in old_handlers: bpy.app.handlers.frame_change_post.remove(h)\n # add new handler\n bpy.app.handlers.frame_change_post.append(paint_test)\n\ndef paint_test(scene):\n for ob in scene.objects:\n me = ob.data\n \n print(str(scene.frame_current) + \": Creating Bmesh\")\n bm = bmesh.new()\n bm.from_mesh(me)\n \n group_index = ob.vertex_groups.active_index\n dvert_lay = bm.verts.layers.deform.active\n \n for vert in bm.verts:\n dvert = vert[dvert_lay]\n try: dvert[group_index] -= 0.1\n except: pass \n \n print(str(scene.frame_current) + \": Writing Bmesh\")\n bm.to_mesh(me)\n bm.free()\n \nadd_handler()\n```", "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", "'Custom Split Normals' generated by the Boolean modifier does not match the normals of the object\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\nIf the object used as operand in the Boolean modifier has `Custom Split Normals` (either through the `WeightedNormal` modifier or manually added) the resulting object will have a \"broken\" `Custom Split Normal`.\nThis kind of works with objects which do not have any `Custom Split Normals` (so only shade flat and shade smooth, no weighted normals etc.) (although it also has it's problems. See #95913 (Strange shading behaviour when using boolean modifier))\nWhen `Custom Split Normals` are involved, the modifier uses the `Custom Split Normals` of the operand object on the target object to determine the shading on the affected areas.\n\n- Open attached file. (The left example has only shade smooth on the boolean object and on the right example the boolean object has a weighted normal modifier on the modifier stack).\nThe issue still persists even if you delete the weighted normals modifier on the target object in the right example.\n[Test_file2.blend](Test_file2.blend)\n\n---\nAnother example:\n[Test_file.blend](Test_file.blend)\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)", "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)", "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)" ]

[ "Texture Painting after boolean crash blender\nAfter using boolean on object I can't texture painting on it because I have instant crash of the client.\n\nI find place when something goes wrong.\nIn first file everything works fine.\n[Axe_01.blend](Axe_01.blend)\n\nAfter boolean on blade I can't paint on mesh.\n[Axe_02.blend](Axe_02.blend)\nAnd crash produce almost empty crash file\n[Axe_02.crash.txt](Axe_02.crash.txt)\n\nIt's don't even need to paint on object. ou can even click on empty space and crash will happen.\nSometimes it can paint once and next click will produce crash.\n\nVersions affected : \n2.93.13 LTS\n3.3.2 LTS\n3.4.1\n\nVersion Blender 3.5.0 - Alpha from December 29, 02:19:19 works fine with mine file [Axe_14.blend](Axe_14.blend)\nand with @AntonL020 from [Anvil Crash ](T103537).\n\nHope this will help with solving this problem on all stable versions of Blender\n\n" ]

[ "Sculpt with Perspective mode. Changing brush size is impossible with closups\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\n\nAs title says. This behavior prevents to use {key F} as size modifier on closeups.\n\n[2021-03-20_10-32-46.mp4](2021-03-20_10-32-46.mp4)\n\n[brushsize.blend](brushsize.blend)", "Sculpt Mode: Add exisiting Tools as Menu Operators\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\nPrevious limitations on using the Adjust Last Operation panel are being lifted, and fixing #99607 is being prioritized.\nThis will make it possible to add many active tools in the toolbar to the header menus as operators.\nThis has the following advantages:\n\n- Support the existing \"Operate → Settings\" paradigm\n- Many operators could be combined for simplicity\n- Easier to use various tools as one time operations instead of making them active\n- Easier to use filters via shortcuts and quick favorites.\n- Redo panel interactions for very high res meshes (Better with slow performance)\n- Simpler than implementing #97959. That can come after then.\n\n## Needed Operators\n\nThis is based on operators that currently only exist as active tools, or are not properly exposed at all yet.\nMany operators are depending on the cursor position. This feature should be used heavily: da2ba40268\n\nInitially or later on some operators can be combined into a single operator and accordingly renamed.\nThe first step is to add the existing operations as they are to the menus.\nThere are also still some open questions for some operators but these can be resolved during testing and review.\n\n### Sculpt\n\n##### Transform Tools\n- Move\n- Rotate\n- Scale\n- Sphere (From Mesh Filter)\n\n##### Trim Tools\n- Box Trim *(Trim Mode =\"Difference\")*\n- Lasso Trim *(Trim Mode =\"Difference\")*\n- Box Add (*Trim Mode =\"Join\")*\n- Lasso Add *(Trim Mode =\"Join\")*\n\n##### Project Tools\n- Line Project\n\n##### Mesh Filter Tool\n- Smooth\n- Surface Smooth\n- ~~Scale~~\n- Inflate\n- Random\n- Relax Topology\n- Relax Face Set Boundaries\n- Sharpen\n- Enhance Details\n- Erase Displacement *(Grayed out if if no Multires)*\n\n### Mask\n\n- Mask by Color\n\n### Face Sets\n\n##### Face Set Edit Tool\n\n- Fair Positions\n- Fair Tangency\n- Delete Face Set\n\n##### Other\n\n- Box Face Set\n- Lasso Face Set\n\n### Paint\n\n##### Color Filter Tool\n- ~~Fill Color~~ (Part of #99769)\n- Blur (Smooth color filter type)\n- Hue/Saturation/Value (Should be combined into one operator)\n- Brightness/Contrast (Should be combined into one operator)\n- Red/Green/Blue (Should be combined into one operator)\n\n##### Other\n\n- Expand Color by Topology (`sculpt.expand` with target data set to `Color`)\n\n## Layout\n\nThis is how the operators could be arranged. \n\n\n\n\n|  |  |  | \n| -- | -- | -- | -- |\n", "Blender 2.80 Canceling of visibility actions during opened panel with object default parameters.\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560\n\n2.80 beta, 1df6a98b176f, blender2.8, 2019-03-05\n\n**Error description**\nLooks like a small flaw. Panel with default parameters(radius, etc..) of standard objects if objects just created - will be canceling your actions with outliner panel (visibility actions) if you dont close it and continue changing parametrs after that\nDemo: 0876b975cd74ce4d9400b6556e5cbe14.mp4\n\n**Steps to reproduce**\n\n- Open new general template\n- Add mesh - circle\n- Hide cube in outliner\n- In Adjust Last Operation panel change radius\n\nCube is no longer hidden", "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", "Live unwrap interaction changes unwrapping and ignores pinned vertices\nBroken: 2.79 - 2.83 (sub 10), commit date: 2020-03-19 13:43, hash: `42012493a8`\nWorked: Never\n\nGrabbing and moving one of the pinned vertices seems to kind of reset the unwrap, even ignoring the pinned vertices.\nShort video demonstration:\neesv3\n\n- Unwrapped parts of an object.\n- Pinned some vertices in UV editor\n- enabled live unwrapping.\n\nor\n\n- Open this file: [LiveUnwrapPinFail.blend](LiveUnwrapPinFail.blend)\n- Go to edit mode\n- Move pinned vertices.\n\n\nIn some cases it also just doesn't do anything at all:\nignig\nHere is a file showing this other problem:\n[LiveUnwrapCube.blend](LiveUnwrapCube.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.", "Hair Curves: Posed hair curves get stuck onto a wrong pose upon entering and exiting Sculpt, Vertex Paint or Weight Paint mode on the surface object\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060 Super\n\nBroken: 3.6.1\nWorked: n/a\n\nOn posed hair when using the 'deform curves on surface' node, if you enter and exit Sculpt, Vertex Paint or Weight Paint mode on the surface object, the posed hair will get stuck on a wrong pose, see attached images for comparison. You don't have to edit anything for the bug to occur. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open the file and select the \"Surface\" object\n2. Enter and exit Sculpt, Vertex Paint or Weight Paint mode\n3. The hair curves object should now have deformed onto a wrong pose and can't be fixed until you reload the file\n\nThis bug still appears in the final render and can only be fixed by reloading the save file.\n\n", "Quadriflow Remesh: Undoing the next operator also resets the mesh\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.83.4\n\nUndoing the operation after the remesh also undoes the remesh.\n\n- Quadriflow remesh the default cube\n- Execute any other operator (switch to edit mode, add curve, etc..)\n- Undo\n\nThe mesh will reset to its state before the remesh.\n\n", "It is not possible to set a hotkey to Transfer Sculpt Mode\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nIt is not possible to set a hotkey to Transfer Sculpt Mode. Neither using the right-click menu nor via the Settings (including using the Python command)\n\n- Open default scene\n- Switch to Sculpt mode\n- {nav Sculpt > Transfer Sculpt Mode > Right click > Remove Shortcut}\n- Now try to assign shortcut\n\nThe shortcut wasn't saved.", "sculpt mode artifacts if displace modifier is active\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIn sculpt mode if the displace modifier is active the brush behavior is unpredictable, especially with the smooth brush.\nIt looks like that the sculpting mode takes account of the mesh after being modified by the modifier and start the sculpt over it.\n'm reporting this because in other modes the modifier and the actual edit of the mesh are handled as separate thing.\n| [smooth_brush_prob.mp4](smooth_brush_prob.mp4) | [06_24_2022.mp4](06_24_2022.mp4)\n| -- | -- |\n\n- Open any of the attached files and try to smooth or grab as done in the video\n\nthanks!\nMax\n\n\n[smooth_bug.blend](smooth_bug.blend)\n[sculptbug_24062022_1422_44.blend](sculptbug_24062022_1422_44.blend)", "mask visibility in sculpt mode using shape keys or generative modifiers\nOperating system: Windows 10\nGraphics card: nvidia 1060 Ti\n\n2.8 RC2\n\nIf you have a mesh with a mask and create a shape key, the mask will be no longer visible, still active but not visible.\n\n\n- Add UV Sphere\n- Sculpt mode\n- Paint a mask\n- Create shape keys\n\n\nOr from the default startup:\n- in sculptmode, `Mask` > `Invert Mask` (default cube should turn dark)\n- strokes dont have an effect now (this is expected)\n- add **any** generative modifier to the default cube (e.g. triangulate)\n- back in objectmode, save the file\n- reload the file\n- enter sculptmode\n- no mask is visible\n- strokes dont have an effect now (this is confusing since you are not aware masks prevent an effect since you dont even see the masks)\n\n(note we have the option `Use Deform Only` in sculptmode which might be exactly for that purpose, still not being able to use masks with generative modifiers should be more clear)", "Can not undo Node Editor operators in Edit Mode\nOperating system: Linux-5.4.0-125-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.5.0\n\nIf Edit Mode is active (for Curves or Meshes), Undo on Node linking/moving etc. gets ignored.\nIf there is a reason for that, Undo history probably should reflect that, for example by not allowing iterating to steps in Edit Mode that won't match reality.\n\n[undo.blend](attachment)\n - In GN or Shader Editor create a new Node Link.\n - Undo.\n -> Undo History shows a step back, but nothing actually happens.\n\n", "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", "Mask brush stops working in tiling sculpting mode after changing its size through \"F\" hotkey\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 2.93, 3.3.0\nWorked: -\n\nWhen an object has the Multires modifier, mask brush stops working in tiling sculpting mode after. (See video below)\n[Desktop 2022.09.17 - 21.18.10.07.mp4](Desktop_2022.09.17_-_21.18.10.07.mp4)\n\n- Open attached file or\n - Add a grid object\n - Add a multires modifier\n - Subdivide Simple a few times\n - Select mask brush in sculting mode\n - set tiling on x and y axis to 1 or 2m \n- try paint mask (sometimes the tiling doesn't work at this stage, you need to paint again and undo)\n- change brush size through F hotkey\n- try paint mask (tiling stops working)\n- press undo\n- try paint mask (tiling works again)\n\n[tiling_sculpt_bug.blend](tiling_sculpt_bug.blend)\n\n", "Color picker undo adds step when cursor exist\nRun blender, logging undo events:\n\n```\n blender --log \"bke.undosys.*\" --log-level -1 --log-show-basename\n```\n\n\n\nClick on the object color swatch and move pointer away from the popup.\n\nEven though no changes have been made, an undo step is added.\n\n----\n\nIsn't high priority, reporting so it's not forgotten." ]

[ "Sculpt mode: UNDO doesn't work for values in workspace / context window\nOperating system: Windows 10 Pro\nGraphics card: GeForce GTX 1080Ti\n\nBroken: Blender 2.8 RC2\nWorked: (optional)\n\nUNDO doesn't work for changing values in workspace area.\n\n1. Create a UV sphere and select it.\n2. Activate Sculpt mode.\n3. Sculpt some strokes with draw brush e.g.\n4. Change the brush value in the workspace area manually.\n5. Use UNDO -> The value will not be reset to the last value.\n\nUNDO doesn't work in sculpt mode for any value changes in the properties window.\n\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 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```", "Material Tab freeze still\n|**Operating system**:|Linux version 5.11.11-200.fc33.x86_64 ([email protected]) (gcc (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9), GNU ld version 2.35-18.fc33)\n| -- | -- |\n|**Graphics card**:|OpenGL version string: 4.3 (Compatibility Profile) Mesa 20.3.5\n||NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) (prog-if 00 [VGA controller])\n\nBroken: 2.83lts - 2.92.0 (Blender version has been downloaded from the Snap Store).\nThis same freeze also happens if using Blender from the Software store (2.91.2) or via the \"dnf\" command.\nWorked: N\\a\n\nIn Eevee, when opening the material tab, either blender crashes or my entire system freezes up and becoming completely unusable and requires a hard reset.\nwatch?v=te6IaP12Gbg&ab_channel=WhitequillRiclo\n\nPerhaps it is related to the compilation of shaders in the material icon.\n\n- Open the Material tab", "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 Python API - GPUOffScreen.draw_view3d() crashes blender with draw_type = POST_VIEW but works with draw_type = POST_PIXEL\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.1\n\nWhen using [GPUOffScreen.draw_view3d() ]] in a [[ https:*docs.blender.org/api/current/bpy.types.Space.html?highlight=post_view#bpy.types.Space.draw_handler_add | draw_handler ]], blender crashes when running the [[ gpu.shader.html?highlight=gpu+shader+from_builtin#built-in-shaders | 3D_IMAGE builtin shader ](https:*docs.blender.org/api/current/gpu.types.html?highlight=draw_view3d#gpu.types.GPUOffScreen.draw_view3d) if the draw_type was set to POST_VIEW but works if the draw_type was set to POST_PIXEL.\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script Crash3D and blender will crash\n\n\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script NoCrash2D, and it will draw the camera view in the viewport without crashing\n\nAttachments:\n\n[CrashScriptDrawView3D.blend](CrashScriptDrawView3D.blend)\n[blender.crash.txt](blender.crash.txt)\n\n\n\n\n\n\n", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "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", "Mode locked and crash if objects become disabled in viewport while not in object mode\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: didn't crash but showed an error message in 2.91.2\n\nObjects that are in a mode which is not Edit Mode nor Object Mode, will lock the mode setting (so the mode options are greyed out and unusable) if they get disabled in the viewport. Hiding will not cause the this bug, it needs to be disabled in viewport using that display icon in the outliner, not the eye.\n\nThe solution for this is probably to make the disable in viewport action switch the mode to object mode if the active objects gets removed (much like delete from outliner). Another solution would be to still allow the mode switch.\n\nMuch worse though! Blender crashes sometimes when it gets into this state. I can reliably crash blender as described below.\n\nGo into weightpaint mode of the default cube and disable it in the viewport using the outliner (you need to enable the option first). Now you are stuck and have to enable it in the viewport first to be able to edit anything.\n\nNow restart blender etc. and try this:\n1. Go into Vertex Paint Mode of the default cube\n2. Hit Tab to go into Edit Mode\n3. Disable the cube in the viewport using the outliner as above\n4. Hit Tab to switch out of Edit Mode -> Crash", "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)", "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) ", "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", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Cycles Rendering of project causes crash of program.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Windows 11)\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\n\nTrying to render, pressing F12 of the file to render project it crashes. I'm using Blender 3.6.2\nNot sure if you need textures, can provide if needed.", "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", "crash while setting vertices positions using foreach_set\nOperating system: macOS-12.6.6-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 6100 Intel Inc. 4.1 INTEL-18.8.6\n\nBroken: version: 3.6.0\n\ncrash while setting vertices positions using foreach_set\n\nstart blender, run script\n\n```python\nimport bpy\nimport numpy as np\n\nl = 2 ** 28\nme = bpy.data.meshes.new('mesh')\nme.vertices.add(l)\na = np.random.random((l, 3))\nme.vertices.foreach_set('co', a.ravel())\no = bpy.data.objects.new('mesh', me, )\nbpy.context.view_layer.active_layer_collection.collection.objects.link(o)\n```\n\noutput:\n```\nWriting: /tmp/blender.crash.txt\n[1] 13339 segmentation fault /Applications/Blender/blender-3.6.0.app/Contents/MacOS/Blender\n```\n\nin blender 3.4 while using 2**27 length output is this\n```\nError: Array length mismatch (expected -402653184, got 402653184)\nError: Python: Traceback (most recent call last):\n File \"/Text\", line 8, in <module>\nRuntimeError: internal error setting the array\n```\n\ncontents of `/tmp/blender.crash.txt` is just me running script, nothing interesting\n\ninteresting bit from crash report (i can provide in full)\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x10bbaef04 foreach_getset + 1124\n1 Blender \t 0x112f45046 cfunction_call + 134\n2 Blender \t 0x112f01015 _PyObject_MakeTpCall + 373\n3 Blender \t 0x112fdf95b call_function + 971\n4 Blender \t 0x112fdbc41 _PyEval_EvalFrameDefault + 24817\n5 Blender \t 0x112fd5a22 _PyEval_Vector + 146\n6 Blender \t 0x112fd5978 PyEval_EvalCode + 120\n7 Blender \t 0x10bb9cd2a python_script_exec + 506\n8 Blender \t 0x10c6754b0 text_run_script + 64\n9 Blender \t 0x10b600ce6 wm_operator_invoke(bContext*, wmOperatorType*, wmEvent const*, PointerRNA*, ReportList*, bool, bool) + 582\n10 Blender \t 0x10b600a03 wm_operator_call_internal(bContext*, wmOperatorType*, PointerRNA*, ReportList*, wmOperatorCallContext, bool, wmEvent const*) + 515\n11 Blender \t 0x10b602025 WM_operator_name_call_ptr_with_depends_on_cursor + 165\n12 Blender \t 0x10c36bffd ui_apply_but_funcs_after(bContext*) + 285\n13 Blender \t 0x10c366fc2 ui_handler_region_menu(bContext*, wmEvent const*, void*) + 434\n14 Blender \t 0x10b604a4f wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 1007\n15 Blender \t 0x10b604020 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 48\n16 Blender \t 0x10b6033ba wm_event_do_handlers + 2554\n17 Blender \t 0x10b5f91b0 WM_main + 32\n18 Blender \t 0x10adea41e main + 878\n19 dyld \t 0x12788152e start + 462\n```\n\n" ]

[ "Crash with OSL + Rendering Viewport + Material Tab in Properties\nOperating system: Windows 10\nGraphics card: GTX 970\n\nBroken:\n2.80, 5e356cc5c89b, blender2.8, 2019-01-12\nWorked: 2.79\n\nBlender crash when using OSL + Rendering with Cycles in Viewport + Material tab in Properties or Select material in Node editor or any other places that the material icons are shown.\n\nOpen Blender, Set Cycles and OSL on. Set render mode to Rendered. Open the Material tab in Properties editor." ]

[ "Outliner Floating window Drag & Drop to Geometry Nodes editor not working\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\nWorked: I don't know if it ever worked\n\nDragging and dropping objects from the outliner to the geometry node editor is not working\n\nFloat outliner to be its own window\ndrag and drop an object from the node editor to the geometry nodes\ndoesn't work.\n\n", "Geometry Nodes: Going back to frame before simulation cache returns no geometry if frame is out of scene frame range\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 4.0.0 Alpha\n\nOut of scene frame range:\n\n\nInside scene frame range:\n\n\n- Add geonodes modifier\n- add simulation zone\n- run simulation to build up the cache\n- Go to frame 0\n\n", "python display_shape don't work in GeometryNodeTree\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 3.1.0 Alpha\n\nWhen adding a custom node with custom socket to the GeometryNodeTree you can't alter the display_shape of the socket and the bpy.types.NodeSocketFloat or any socket type doesn't matter when connecting nodes it always stay red.\n\n\nAttached a blend file with the script for quick testing\n[tst.blend](tst.blend)\n\nThis is not a problem in the Shader or Compositing editors:\n\n", "Geometry Nodes Object Group input does not remove dependencies\n[system-info.txt](system-info.txt)\n\nBroken:version: 3.4.0 Alpha, branch: master, commit date: 2022-10-04 22:45, hash: f9a10e7ed039, type: release\n...been already around for a while\n\nIt seems that Blender does not correctly remove the dependency from the formerly connected object from the Geometry Nodes Object Group input.\nEven when deleting all the default values.\n\n- Append the object `Cube` from the attached .blend file\nit will also append Suzanne even though all former links in the setup have been removed.\nThe only thing that helps to get rid of the dependency is to delete the input and recreate it together with all the links. \n[dependency_bug.blend](dependency_bug.blend)\n...and do not get me wrong i really like Suzanne! But if she appears all the time even when she is not invited it gets a bit annoying.\n", "The image node in GeoNodes can't use UDIM tiles\nOperating system: Windows 11\n\nBroken: 4aac5b92c1bb\n\n\nIt seems like the image texture node is not able to access the UDIM uv range properly. As you can see in the image the objects have proper UDIM tiles that the regular textures can utilize . The image texture node of the geonodesseems to bound the UVs within 0-1 range and cant access the tiles.\n\nPassing the UVs from the modifier does not seem to help with it.\n\n\n\n\nload the attached .blend file\n\nselect the NOUDIM object\n\nopen the geometry nodes graph of the object's modifier\n\nenable the viewer node\n\n[_01122022_2239_12_02_2022.zip](_01122022_2239_12_02_2022.zip)\n", "Skipping node auto-attachment doesn't work with custom keymap\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\nWorked: none\n\nBy default holding `ALT` while dragging a node disables auto-attachment. However, this doesn't work when using a custom keymap that has been imported from previous version. The prompt doesn't show which key to hold, and holding `ALT` just makes the prompt flicker like crazy, but doesn't disable auto-attachment.\n\n\n\n\n**Steps to reproduce the bug**\n\n - Switch to a keymap that has been created with an earlier Blender version\n - Move a node in any node editor\n - Hold `ALT`\n\n\n\n", "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", "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", "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", "node editor: Texture preview refresh with cursor selection\nOperating system: 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux\nGraphics card: RTX 2070\n\nBroken: Blender 2.93.0, Commit date: 2021-02-17 06:07, Hash 17dddc941714\n\nwhen selecting things in geonodes space the texture preview refresh anomaly.\n\n- Open blender default file.\n- Open the geometry nodes editor\n- Add a geometry node group\n- Open the texture tab ( property panel )\n- Add a texture for the current brush\n- Change to cloud texture\n- Try to select things with cursor select ( Key : C ) in the geometry nodes area.\n- It will refresh the texture preview\n\n[untitled.blend](untitled.blend)\n[Kazam_screencast_00003.mp4](Kazam_screencast_00003.mp4)", "Cycles: Normal Edit modifier after displace modifier does not with motion blur (Eevee seems fine)\nTried on multiple systems\n\nBlender 3.0 (And the previous beta builds)\n\nThe normal edit mode will not work with motion blur enabled\n\nSee attached file - Using a NormalEdit modifier looks correct in viewport then fails at render time if motion blur is used in combination with the attached Geometry Nodes tree that is displacing the main geometry over time. \nWith the node tree disabled the NormalEdit modifier works even with motion blur.\n\n**Viewport Result:**\n\n\n**Rendered Result:**\n\n\n\n**Demo file:**\n[Bug (1).blend](Bug__1_.blend)\n[#93700 Cycles Normals Motion Blur Displace.blend](T93700_Cycles_Normals_Motion_Blur_Displace.blend)", "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)", "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", "Crazy-space support for meshes in geometry nodes\nIn [D15407](D15407) crazy-space support for curves is added to geometry nodes. Currently, meshes use a different system for crazy-space that is not really compatible with nodes as is.\n\nIt should be possible to use the approach implemented for curves for meshes as well, but that needs to be investigated further.", "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)" ]

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

[ "Viewport Slowdown on 11th gen Intel Xe graphics\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\n| Graphics card: | Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 27.20.100.8935 | @tommyoliversays, @CuriousHobbyist (#93114), @Jonathan-Monsonego (#93039), @Pyer (#93505), @Charlie3521 (#93257), @ImaRealBoi (#87147)\n| -- | -- | -- |\n| | Quadro RTX 3000 with Max-Q - 4.5.0 NVIDIA 472.39 | @Stay_Here\n\nBroken: version: 2.92.0, 2.93\nWorked: 2.83 LTS (better but not perfect, just takes longer for it to start occuring, maybe an hour as opposed to around 20 minutes in 2.92).\n\nWorking on a model slowly brings viewport down to single digit framerates.\nIt seems to be a twofold issue. Whenever you hit spacebar to playback animation, Blender starts using up more RAM. After working for about 15 minutes, 2.92 RAM usage increased from ~500MB at launch to over 3GB in the same scene while idle. Rotating the viewport also spikes GPU usage to over 50%, which immediately drops back to single percent digits when idling.\n|  |  | \n| -- | -- | -- |\n| Memory at launch | 15 mins after | Spikes rotating viewport\n\n- moving verts around over time or\n- hit spacebar to playback animation or\n> In #93114#1254781, @Stay_Here wrote:\n> The most likely scenario in my case is when two or more Blender(s) are launched. For example, open Blender.exe twice, then load two different characters in the two Blender windows. Let's say, character A and character B are loaded in the Blender window A and window B, respectively. After that, I spend some time on sculpting character A, and use the character B as a reference character. In this setup, Blender window B is seldom touched or manipulated, since it is just for reference. \n> \n> After about 10 mins to 2 hours on sculpting character A on the window A and open YouTube to listen some music, I jump to the Blender window B to navigate and change the view to the reference character B. At this moment, the lag in the solid viewport in the window B can be quite likely to happen. However, at the same moment, navigating in the window A is still smooth and unaffected.\n\n\n[imp2.blend](imp2.blend)\n\n", "Discrepancy between CPU and GPU rendering/material behaviour\nOperating system: macOS 13\nGraphics card: AMD W6800X Duo MPX module\n\nBroken: 3.3.1 (latest full release)\n\nI bought some assets which render with weird artefacts with the GPU, but work fine with CPU.\n\nThe assets are made by Bproduction (Florian Benedetto) on Blender Market. They are trees and vegetation models, which can be used individually or with Scatter 5.3. Simply put: they render properly with the CPU (Mac Pro, 24-core Intel), but render with horrible artefacts using the dual GPU. This doesn't happen with any other assets or materials I have.\n\nThe images below show the issue. I believe it's something to do with the material setup, but in any case it should render properly under both systems. Maybe it's an issue with macOS drivers?\n\n\n\n", "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", "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", "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", "2.83 3D viewport performance\nOperating system: Ubuntu 20.04 LTS\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2), version: 4.5 (Core Profile) Mesa 20.0.4\n[system-info.txt](system-info.txt)\n\nBroken: 2.83\nWorking: 2.82\n\nProblem seen in Workbench, Wireframe and Eevee.\nViewport performance it's really bad, I'm moving around just the initial cube scene at 15-20 Fps, older Blender versions movement is perfectly smooth.\nNo matter the scene/blend file, 2.83 offers worse viewport movement performance compared to older versions,\nIt's important to mention that only the viewport movement is being affected by this performance drop, everything else including rendering works smooth as butter just like older versions or even better. Splitting up the scene in windows kinda fixes this problem.", "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", "GPU subdivision: Wrong object's size when using subdivision surface modifier with GPU subdivision\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia Geforce GTX 660\n\nBroken: 3.1\nWorked: 3.0\n\nWhen GPU subdivision is activated, the object with subdivision surface doesn't show the correct size on the dimension section of the properties' sidebar.\n\nSelect the default cube.\nAdd Subdivision surface modifier\nOpen the properties' sidebar with N, the dimensions should be 1,68m (for X, Y and Z) but it shows 2,0m for all the axes. By deactivating the \"GPU subdivision\" the panel shows the correct dimensions.\n", "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", "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", "Viewport animation renders take progressively longer if there is a split in the scene!\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Ultra 1.2\n\nBroken: version: 3.6.2\nWorked: Never\n\nWhen animating a render from the viewport, if a spline is present in the scene each frame takes progressively longer and longer to render until it takes a painfully long time per frame. Once the spline is deleted from the scene, each frame takes the same amount of time to render!\n\nMake an animation of approx 1000 frames\nInclude a spline in the scene - you don't have to render it, it just needs to be in the scene!\nViewport Render Animation\nYou should quickly notice that each frame is taking longer and longer to render\nBy the time you get to frame 800 (if you care to wait that long) you will be pulling your hair out!\n...now delete the spline\nViewport Render Animation\nEach Frame now takes the same time to render and you can smile once more.\n\n....I'm already guessing that whoever is gracious enough to try this will magically not have the problem - if so, please reply and I will supply files... I just would rather not at this time as I am interested to see if it is indeed reproducible? I can confidently say that I have experienced this issue for at least 5 years, but it's only now that it has come to bite me again and I have finally proven (to myself, at least) that the issue is spline related - my scene had one single 'Annotation' spline that I wasn't even aware of hanging around in it and deleting it sped up render times by an order of magnitude!\n\nThanks\nWayne\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)", "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.", "Regression: Tiled rendering is not applied to texture baking in 3.x onwards, causing crash on large bakes\nOperating system: Win10\nGraphics card: AMD Radeon R9 280x\nSystem RAM: 32gb\n\nBroken: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: bcfdb14560e7, type: release\n(also tested Daily 3.2.2 and beta 3.3)\n\nWorked: 2.8x, 2.9x, 2.9 LTS\n\nPreviously tile based rendering was applied when using the bake to texture feature, allowing baking to very large canvases. As of version 3.x tiled rendering no longer applies when baking textures and crashes on large canvases. In my case I can no longer bake to a texture larger than 2^14 (16384x16384).\n\n- Open attached file or\n - From a new blend file, delete default cube,\n - switch renderer to Cycles (CPU).\n - Create a plane,\n - switch to UV and create a very large texture (in my case anything larger than 16384x16384, my previously and still working in 2.9x size is 19310x) with float precision and no alpha.\n - Create a new material,\n - remove the principled Shader,\n - connect the color output of a noise texture to the material output Surface,\n - add an Image Texture node and select the previously created canvas. In my case I disable bounces (set all to zero) and set samples to 1, Filtering to Box filtering. \n - Switch bake type to Emit.\n- Hit bake and blender crashes trying to allocate the memory for the render target canvas. Setting Tiled rendering to other sizes does not work either.\n\nNotes:\nI'm prebaking complex noise channels as it dramatically reduces render time on the final texture bake.\nYou may need to create an excessively large target canvas if you have a lot of ram.\nWhen stopping a bake half way through on 2.9x and lower version you can see tile based rendering has taken effect and the sizes declared are used.\nWhen stopping a texture bake on 3.x versions you can see that it is filling the entire canvas at once and not using tile based rendering, no matter what the tile size is set to.\n[bake_crash.blend](bake_crash.blend)\n", "Grease Pencil: Better render Anti-Aliasing\n## Motivations:\nThin lines are correctly rendered using grease pencil with the currently implemented post process Anti-Aliasing. This is done by making sure the line width is not less than 1.3 and by modulating its opacity.\nHowever, there is cases where this is not enough. For instance really dense drawings with small lines with little to no curvature still tends to flicker a lot.\nAnother case is when the gpencil strokes intersects the scene geometry. This makes the line less thick to the post process which makes it too small.\n\n## Proposed solution:\nWe propose to implement a Temporal AntiAliasing solution. It is robust and will match Cycles & EEVEE's film filtering if using the same filtering function. This only adds one temporary buffer (low VRAM usage compared to rendering at higher resolution) and is completely self contained (works with transparency and don't interfere with other features).\n\nI propose to only implement this for final rendering since it might introduce flickering that might be annoying while drawing.\n\nHowever this wouldn't solve the issue of gpencil strokes intersecting geometry.\nFor this I propose to erode or reproject the render's depth to match the render sample of the new AA scheme. This should fix the second problem completely.\n\n## Technical details:\n- Implementation just need to be ported from Workbench which has a lighter form of TAA than EEVEE. Also [D10414](D10414) can be of great help to reduce render/convergence time.\n- Depth buffer modification can be implemented after new AA is in." ]

[ "Poor cycles perfofmance in blender-2.72.2 than in blender-2.72.1\nOperating system and graphics card\nGentoo amd64 laptop\nAsus G75V with gtx660m\nand\nGentoo amd64 desktop\ni7-3...* dual gtx780\nBroken: git\nWorked: blender-2.72.1 (last 2 weeks from git plasma-desktopgL2782.png )\nshowthread.php?239480-2-6x-Cycles-render-benchmark&highlight=benchmark+bmw\nWith blender-2.72.1 i have render time 2 min 45 sec\nWith blender-2.72b i have render time 3.30\nWith blender-2.72.2 git i hane render time 3.40\nWhy? \nps: i have a nvidia-cuda-toolkit-6.5.19\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\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", "Sculpt Mode - Face Set FK, mirror X is wrong when Scale/Translate using Pose brush with Lock Rotation When Scaling\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\nBroken: 2.92, 3.5.0 Alpha\nWorked: Never.\n\n\n- Change to pose brush.\n- Change brush deformation mode to Scale/Translate.\n- Enable brush Lock Rotation When Scaling.\n- Try to pose the hand.\n- The other hand is flipped.\n\n\n\n\n\nThis is the file I'm using:\n\n[20221205_model_human_sculting_pose_brush_using_facecets_0001.blend](20221205_model_human_sculting_pose_brush_using_facecets_0001.blend)\n", "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", "Mantaflow not calculating volume correctly for liquids [due to Adaptive Time Steps?]\nOperating system: Windows 7 Pro 64-bit\nGraphics card: Nvidia GeForce GTX 1060 6gb\n\nBroken: version 2.83.0\n\nCreated Mantaflow liquid simulation.\n\nInflow object flowing into small tub (collision object) and from there into a larger tub below (collision object)\n\nSmall tub fills in something like 70 frames and then overflows into larger tub below which fills up in another 100 frames.\n\nThis cannot be. The larger tub is something like six to eight times the volume of the smaller tub and would not fill up this fast.\n\nIn my opinion, Mantaflow is calculating the flow so that there is an equal Z-axis fill rate, but this is totally incorrect with regard to volume.\n\n\n[mantaflow volume bug.blend](mantaflow_volume_bug.blend)\n\n[mantaflow volume bug.mp4](mantaflow_volume_bug.mp4)", "Rotate sculpting brush may have an incorrect pen pressure behavior\nOperating system: Linux-5.9.12-1-default-x86_64-with-glibc2.17 64 Bits\nGraphics card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.39.0, 5.9.12-1-default, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.4\n\nBroken: version: 2.92.0 Alpha\n\nThe sensitivity to pressure of the Rotate Brush in Sculpting mode appears to be too low: no matter how hard the pen is pressed on the pen tablet, disabling pressure sensitivity produces much more controllable/faster results. Potentially other brushes in sculpting mode could be affected as well in various ways (only a general impression; unclear as of yet).\n\nWith Grease Pencil, pen pressure sensitivity appears to be correct and similar to that observed with a typical drawing program (Krita). So, this does not seem to be a general problem with Blender or my own pen tablet.\n\nMy pen tablet is a Wacom Intuos 5 Large. In Tablet settings inside Blender Preferences > Input, Max Threshold = 1.0 (max), Softness = 0.0\n\n- Open the attached .blend file\n- Use the Rotate sculpting brush to attempt rotating the bumps on the provided plane object\n- Enable Pressure sensitivity for \"Strength\" in the brush and attempt it again applying maximum pressure on the pen tablet. Compare the difference in response\n\n[rotatebrush-veryhard.blend](rotatebrush-veryhard.blend)\n", "FLuid Manta Flow Bug\nOperating system: Windows 10\nGraphics card: RTX 3070\n\nBroken: 2.9.1 / 2.9.2 / 2.9.3\nWorked: (newest version of Blender that worked as expected) 2.8.3 / 2.9.0\n\nCaused by 55fd7f55bd\n\n\nUnable to make fluid work properly inside a containiser let say a sphere. I need to make fluid to fill completely the sphere but i am unable to do that. On version 2.9.0 and 2.8.3 it works perfectly... on version 2.9.1 and beyond it does not work....\n\nToo much step to describe but to resume :\n\n1 spehere is fluid > flow\n1 sphere is fluid > colision\n1 cube is fluid > domain\n\nI refresh the cache multiple times, i invert normals on the sphere and so on but liquid don't go inside the sphere or pass through but if i put the fluid source inside the sphere no fluid goes inside...\n\n[fluide.blend](fluide.blend)", "Cycles box mapping not working with rotated texture coordinates\nubuntu 14.04, 630GT, 4930k\n\nBroken: 2.74\n\n\nbox mapping doesn't work with object mapping (object) if the object is rotated (only 1 side is properly projected)\n\n\n1. open the blend file\n2. copy \"Cube\" and rotate it (90 degress)\n3. render\n\n\n\n\n\n\n\n\n", "Impossible to move with G key an object scale to 0 and parent to an empty\nOperating system: Windows 7\nGraphics card: GTX 780\n\nBroken: 3.5.1\nWorked: \n\nWhen an object is parented to an empty, and this object is scale to 0, you cannot move it anymore with the G key. But you can move it in the transform menu location.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open blend.\n2. Try to move object with G key.\n3. It is possible with Transfom menu.\n\nThanks a lot !\ndono", "Displace modifier with Image Texture causes scene slowdown\nOperating system: Linux-5.4.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\n\nBroken: version: 2.90.0\nWorked: 2.83\n\nCaused by 23919d2275\n\nMesh object with a Displacement modifier using IMAGE TEXTURE can grind scene to a halt by forcing modifier stack to reevaluate on smallest changes to scene (such as adding objects, removing etc). \n\nInterestingly with built in textures (Cloud, Voronoi) it's very fast and functions as should.\n\n\n- Add subD modifier. Relatively high level (with respect to detail)\n- Any image texture (e.g rocks, wood, cloth)\n- As bonus can add Decimate modifier to confirm slowdown and force reevaluation of scene.\n- Try add new objects, erase etc, everything will freeze until that particular objects modifier stack is reevaluated.\n\n\n\n[displace_image_slowdown.blend](displace_image_slowdown.blend)\n\nThank You!\n", "Smoke Domain glitching outside of its cache range 2.91.2, 2.9 Beta\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0 Beta\n\nIf you have a smoke/fire simulation and the playhead is outside of the cache range of the smoke domain. The 3D viewport and the render shows glitches in the domain.\nAlso the same glitch happens in 2.9.2\n\n[Mantaflow bug Test.blend](Mantaflow_bug__Test.blend)\n\n[2021-02-14 03-26-24.mp4](2021-02-14_03-26-24.mp4)\n[2021-02-14 03-34-25.mp4](2021-02-14_03-34-25.mp4)\n", "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.", "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", "Adaptive Domain creates lines in smoke\nOperating system: Win 10\nGraphics card: Dual RTX Titans\n\nBroken: Blender 2.82\n\nWith adaptive domain enabled, noticeable horizontal (and sometimes vertical) lines appear in the smoke\n[weird lines.mp4](weird_lines.mp4)\n\nSimple blend file: \n\n - Create a large box and set it as a gas domain.\n - Create a small object as the Flow (both 'smoke' and 'fire' reproduce it)\n - Put the flow object near the bottom of the domain\n - Enable Adaptive Domain\n - Bake\n - You should see lines like this: \n # Turn off adaptive. Not only will the smoke move faster creating a totally different looking simulation (which is problem in itself) but the lines will be gone: \n\nIt's most noticeable when the domain is large, and the adaptive box is only a small portion of it.\n\nIncreasing the adaptive margin to 24 helps somewhat, but it's still there. Any higher and it defeats the purpose of adaptive - baking takes as long as just turning it off.\n\nSample blend:\n[adaptive bug2.blend](adaptive_bug2.blend)", "Fluid domain renders as the original object when particle mesh is momentarily disappear\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0\n\nIf there is no mesh generated from active particles within the domain, the frame will render with the domain as its original surface.\n\nI have an emitter object that periodically (cycles) emits fluid into the domain. At times when there is no mesh generated from particles in the domain the rendering is correct -- the fluid mesh:\n\n\n\nAt some point when there is no mesh generated particles inside the domain, the render is incorrect -- the surface coloring on the domain boundary:\n\n\n\nIn the attached file, I would know when I might start to include the Fluid Domain in the rendering, but it would be rather difficult to tell when there are no more particles if velocities or emissions are complicated with noise.\n\nHere is the [StackExchange ](fluid-simulation-gives-a-obscured-render-when-active-fluid-particles-are-absent) discussion and an example blend file.[fluid render problem.blend](fluid_render_problem.blend)\n\n\n\n", "Performance test and notes regarding multires\nDaniel Bystedt and Dalai Felinto had a catch up meeting 11:th of May. During that meeting we talked a bit about sculpting. Dalai asked me to create this task and to add a test file and some more info which is detailed below.\n\n**Computer and Blender specs**\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nversion: 2.92.0\n\n\n**Blend file**\n[orc_head_5_subd_v001.blend](orc_head_5_subd_v001.blend)\n\n**Switching symmetry on/off**\nSwitching symmetry on/off is something a user does quite often in order to not make human faces (for example) look totally mirrored when sculpting. It’s a bit surprising that it is so slow when the vertex count is high. \n\n@PabloDobarro explained via chat: *The lag from turning on/off symmetry is because of a BVH rebuild. Symmetry is a property of meshes, so each time a property of the mesh changes, it considers it as a change in geometry and rebuilds the BVH again. It should be possible to do a more proper tagging of these changes to avoid this, which will fix this multires and any other future system we can make.*\n\n|Vertex count| Time to switch symmetry on/off\n| -- | -- |\n|10 million| 3 s 7ms|\n\n**Subdivide performance**\nSubdividing when vertex count will be above 1-3 million is usually rather slow. The user only have to subdivide the model once when sculpting a model so it’s not a frequent thing that you do. If it could be made faster it would be a nice improvement though\n\n|Vertex count| Time subdivide with multires|\n| -- | -- |\n|subdiv 2.6 million > 10 million| 16 s 5 ms|\n\n**Switching sculpt levels performance**\nSwitching sculpt subdivision levels is something the user does quite often, so if it is fast it would be great. The performance is not terrible though.\n\n|Vertex count| Time subdivide with multires|\n| -- | -- |\n|2.6 million > 10 million| 1 s 8 ms|\n\n\n**Performance investigation starting point**\n- Run a profiler to see if we do not have obvious bottlenecks and see that all threads are occupied\n- Measure exact memory footprint of OpenSubdiv topology. If it is not terribly big, can cache those on different levels while being in the sculpt mode\n- Look into sparse patch tables. This seems to be a solution to a specific of OpenSubdiv which is related on a single-threaded nature of topology construction\n- Run quick and dirty check whether using GPU evaluation brings 10x speedup (quick and dirty is because doing proper integration is not trivial and you don't want to do it if the speedup is not that great)\n- Check whether all tools are properly multi-threaded\n- Make ID_RECALC_PARAMETERS to work for non-geometry properties of meshes (to mitigate the symmetry lag)" ]

[ "[Mantaflow] low domain transformation performance\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.83 (sub 15)\n\nIf you move, rotate or scale the domain, then the performance of the blender decreases.\n\nPlayable in any scene:\n[mantaflow_domain_transforms.mp4](mantaflow_domain_transforms.mp4)\n\n" ]

[ "eGPU doesn't get used by EEVEE on Windows (Mac / Bootcamp)\nOperating system: Windows 10 1903 (Bootcamp)\nGraphics card: Radeon RX 560, Radeon RX Vega 64\nDevice: Macbook Pro 15\" 2018\n\nBroken: 2.82\n\nWhile using a eGPU on Windows 10 via Bootcamp, Blender doesn't use the external GPU to accelerate and power EEVEE. No matter if the Blender Graphic Setting preferences are set to High Performance, ergo utilizing the RX Vega 64 in any scenario. Missing usage of the external GPU can be tracked via the Task Manager -> Performance Tab. (See screenshots).\n\n**Note 1:**Cycles on Windows/OpenCL recognize and uses the external GPU with no issue as expected.\n\n**Note 2:** On Mac OS Catalina, EEVEE can use the external GPU as expected by enabling the option 'Prefer External GPU'.\n\nSo the problem affects only Windows when an external GPU is used for EEVEE only.\n\n\n\n\n\n\n\n- Open Blender and launch a rendering with EEVEE\n- Check GPU usage through Task Manager \n- On any operating during rendering the external GPU is not used at all.", "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", "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", "Grease Pencil ignores collection Line Art usage settings\nversion: 3.3.0 Beta, branch: master, commit date: 2022-07-28 22:39, hash: 6ca602dd9fa1, type: release\nbuild date: 2022-07-29, 00:21:12\nplatform: 'Windows-10-10.0.22000-SP0'\n\nrenderer:\t'NVIDIA GeForce RTX 3090/PCIe/SSE2'\nvendor:\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 516.59'\n\nGrese Pencil ingnores Collections Line Art usage settings. See my attachment and screenshot.\n\nOpen the attached file and check the line art settings in the torus collection.\n\n\n\n[gpencil_outlines-test-3_3.blend](gpencil_outlines-test-3_3.blend)", "Manipulators don't render properly\n## System Info\nOperating system: Debian 10.6 AMD64\nGraphics card: NVIDIA Corporation GF108 [GeForce GT 730] with proprietary drivers packaged from debian\n [system-info.txt](system-info.txt)\n## Blender versions\nBroken: 2.83 and upwards (latest build - Blender 2.92.0 Alpha November 22, 00:30:33- df8cc5662b9a - as well)\nWorked: 2.82 and older\n\n\n## Bug Description\nStarting a new (General) file, selecting the cube and pressing move or rotate, the manipulators render with some colored plane artifacts as in screenshots attached.\n\nThis is caused by the graphics card not being recognized and software rendering being used instead.\n\n## Demonstration\n\n### Video of bug\n\n[manipulators-bug.mp4](manipulators-bug.mp4)\n\n### Video of expected behavior\n\n[manipulators-normal.mp4](manipulators-normal.mp4)\n\n### Screenshots of bug\n\n\n", "Render error not shown in VSE\nOperating system: Windows 10\n\nBroken: 2.90 8956e9e5f6c0\nWorked: Unknown\n\n**Reproduction**\n1. In a scene's Compositing workspace, enable Use Nodes and delete all the nodes.\n2. In another scene's VSE, add the above scene as a strip.\n3. Render\n\n**Description**\n\nF12 on the outputless scene throws an error.\n\nThe VSE shows the checkerboard pattern even if there's another strip (e.g. solid black) below the outputless scene strip and does not throw any error. The outputless scene strip should either not interfere with the layers below it or show an error indicating it doesn't have an output.", "Blender 2.82: Fails to immediately report information to XServer on Linux\nOperating system: Manjaro Linux 5.6\nGraphics card: GTX 1070 ti\n\nBroken: 2.82, found as soon as app is open.\nWorked: 2.81\n\nIn Linux, if an app doesn't report anything to the Xserver, but still specifies window dimensions, it leads to a sort of awful stuttery broken effect while said app is loading. This is visible in 2.82, where, upon opening and loading, it fails to report to Xserver, and looks like this:\n\nIt looks like this while the app is loading (that is, only a title bar) and produces an odd effect if the window is dragged around during loading, and I can confirm that it lasts longer if Blender is put on a mechanical hard drive VS an SSD. This doesn't occur launching any other apps, nor even a binary of 2.81, which instead displays a gray screen while loading. This is obviously just an aesthetic problem, but it can (rarely) cause issues. \n\n\nOpen Blender. ", "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", "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", "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 ", "Particles animation dont show\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nemitter particles animation don't show movement when i press G shortcut to move the model that contain the particles but they don't show any movement, so i can't do an autokeying animation whit the desire movement of the mouse.\n\nadd a cube, put particle emitter, press space bar and G key to move, the particles don't show movement only flickering.\n", "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", "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", "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", "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" ]

[ "Blender 2.75a accept old Nvidia G210 whereas Blender 2.76-RC1 doesn't.\nWindows 7, 64 bits, Video card: Nvidia 210 (GT218 chip)\n\nBroken: Blender 2.76-RC1\nWorked: Blender 2.75a\n\nNo CUDA and GeForce 210 option anymore\n\n1) Be poor;\n2) Open Blender 2.76-RC1, Ctrl+Alt+U -> System -> \"Compute Device\" only CPU avaliable. \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", "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)", "VSE: Crash using Retime-Tool on extended Movie-Clip\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 4.0.0 Alpha\nWorked: N/A\n\nBlender crashes when trying to use the Retime-Tool on a Movie-Clip where the start was extended.\n\nIn the VSE\n\n1. Import a Movie-Clip (.mkv encoded with NVENC, H.264 from OBS in my case).\n2. Extend the left edge of the clip so it begins before the actual content begins (the first frame is looped up to the point the actual video starts).\n3. With the Retime-Tool selected move the right edge of the clip to change the playback-speed of the whole (extended) clip.\n4. Blender crashes\n\nVideo and blender.crash.txt are attached.\n\nWhen the clip is retimed first and then extended before its actual start (do step 3 before step 2) Blender doesn't crash and the result looks as expected.", "Render crash when using Python API to modify object Attribute data in frame_change_pre handler\nOperating system: Windows 10 Home\nGraphics card: GTX 1070 8GB\n\nBroken: Blender 2.93.0 84da05a8b806 (2021-06-02 11:21)\nWorked: n/a\n\n\nThis issue was discovered during development of an addon that generates procedural meshes in a `frame_change_pre` handler. When adding attributes to these meshes in the `frame_change_pre` handler, Blender can crash during render on random frames.\n\nThe `Render → Lock Interface` option is enabled as per the note in the [handlers documentation ](bpy.app.handlers.html#note-on-altering-data).\n\nI have created a simplified script that reproduces this crash during render, typically within a minute of starting the render. This script randomly generates triangles and attribute values in a frame change handler:\n\n```lines=5\nimport bpy, random\n\n\ndef frame_change_pre(scene):\n n_triangles = 10000 # number of triangles to generate\n n_attributes = 10 # number of attribute 'layers' to generate\n \n tsize = 0.1\n vertices = []\n triangles = []\n for i in range(n_triangles):\n xshift, yshift, zshift = random.uniform(-3, 3), random.uniform(-3, 3), random.uniform(-3, 3)\n vertices.append((-tsize + xshift, -tsize + yshift, zshift))\n vertices.append((tsize + xshift, -tsize + yshift, zshift))\n vertices.append((0 + xshift, tsize + yshift, zshift))\n triangles.append((3 * i, 3 * i + 1, 3 * i + 2))\n\n object = bpy.data.objects[\"Cube\"]\n object.data.clear_geometry()\n object.data.from_pydata(vertices, [], triangles)\n \n for i in range(n_attributes):\n attribute_name = str(i)\n try:\n object.data.attributes.remove(object.data.attributes.get(attribute_name))\n except:\n pass\n \n attribute = object.data.attributes.new(attribute_name, \"FLOAT\", \"POINT\")\n for value in attribute.data:\n value.value = random.uniform(0, 1)\n \n \nbpy.app.handlers.frame_change_pre.append(frame_change_pre)\n```\n\nIncreasing the number of triangles and/or number of attribute layers seems to increase the frequency of crashes. The crashes do not seem to occur when rendering from the command line.\n\nThis is the error reported after the crash:\n\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7736C6490\nModule : blender.exe\nThread : 00000814\n```\n\nAttached is the crash log: [attribute_crash_example.crash.txt](attribute_crash_example.crash.txt)\n\n\nAttached is a .blend file including the script that reproduces this issue.\n\n1. Open the .blend file\n2. Press 'Run Script'\n3. Begin rendering the animation (Blender > Render > Render Animation)\n\n[attribute_crash_example.blend](attribute_crash_example.blend)\n\n-----\nSeems easier to reproduce on a debug build since it hits an assert (although i'm not sure who is at fault there, could be the script, could be blender, @HooglyBoogly will likely know since he worked in this area recently) \n\n1) Make a debug build\n2) Load up the .blend above\n3) Hit the Play button on the Python script\n4) Rather than render, just his play on the timeline\n5) Boom!\n\n```lines=10\nBLI_assert failed: K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361, BKE_mesh_vertex_normals_ensure(), at 'CustomData_has_layer(&mesh->vdata, CD_NORMAL) || mesh->totvert == 0'\n\nStack trace:\nblender.exe :0x00007FF783355EA0 bli_windows_system_backtrace_stack_thread K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:233\nblender.exe :0x00007FF783354F30 BLI_windows_system_backtrace_stack K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:320\nblender.exe :0x00007FF783354900 BLI_system_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:386\nblender.exe :0x00007FF783359730 _BLI_assert_print_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c:50\nblender.exe :0x00007FF777848300 BKE_mesh_vertex_normals_ensure K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361\nblender.exe :0x00007FF7778467E0 BKE_mesh_calc_normals K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:475\nblender.exe :0x00007FF77951DC80 ED_mesh_update K:\\BlenderGit\\blender\\source\\blender\\editors\\mesh\\mesh_data.c:1106\nblender.exe :0x00007FF77885B520 Mesh_update_call K:\\BlenderGit\\2022_full_with_tests\\source\\blender\\makesrna\\intern\\rna_mesh_gen.c:7350\nblender.exe :0x00007FF778528720 RNA_function_call K:\\BlenderGit\\blender\\source\\blender\\makesrna\\intern\\rna_access.c:7336\nblender.exe :0x00007FF778A024F0 pyrna_func_call K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_rna.c:6304\npython310_d.dll :0x00007FFA32E09B40 _PyObject_MakeTpCall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:215\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:112\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4232\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E0EAC0 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:114\npython310_d.dll :0x00007FFA32E0ED10 method_vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\classobject.c:53\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:115\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4183\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E07FD0 PyVectorcall_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:255\npython310_d.dll :0x00007FFA32E086F0 _PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:290\npython310_d.dll :0x00007FFA32E07680 PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:318\nblender.exe :0x00007FF778A12F20 bpy_app_generic_callback K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_app_handlers.c:354\nblender.exe :0x00007FF776ECF220 BKE_callback_exec K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:51\nblender.exe :0x00007FF776ECF400 BKE_callback_exec_id K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:67\nblender.exe :0x00007FF7776D5C60 BKE_scene_graph_update_for_newframe_ex K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2648\nblender.exe :0x00007FF7776D5C10 BKE_scene_graph_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2712\nblender.exe :0x00007FF778A46A10 ED_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_edit.c:1729\nblender.exe :0x00007FF778A70B30 screen_animation_step_invoke K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_ops.c:4754\nblender.exe :0x00007FF777D74A30 wm_operator_invoke K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:1339\nblender.exe :0x00007FF777D6FE10 wm_handler_operator_call K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2340\nblender.exe :0x00007FF777D72F10 wm_handlers_do_keymap_with_keymap_handler K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2693\nblender.exe :0x00007FF777D720D0 wm_handlers_do_intern K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3020\nblender.exe :0x00007FF777D70B70 wm_handlers_do K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3161\nblender.exe :0x00007FF777D6A440 wm_event_do_handlers K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3775\nblender.exe :0x00007FF777D3EB60 WM_main K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm.c:642\nblender.exe :0x00007FF776EB2C60 main K:\\BlenderGit\\blender\\source\\creator\\creator.c:564\nblender.exe :0x00007FF7837A1B00 invoke_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7837A18B0 __scrt_common_main_seh d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7837A1890 __scrt_common_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7837A1BC0 mainCRTStartup d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFAE8F27020 BaseThreadInitThunk\nntdll.dll :0x00007FFAE9062630 RtlUserThreadStart\n\n```\n\n", "Regression: Crashes when uses preview or final render modes\nOperating system: Mac Os Monterey 12.6.1\nGraphics card: AMD Radeon R9 M380 2 GB\n\nBroken: blender 3.6.2\nWorked: Blender 3.4.1\n\nBlender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements.\n\nSimply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.\n\n", "blender 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", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "Crash 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", "Outline of plane in Object mode does not Render after applying transforms\nBroken: Current main.\nWorked: N/A.\n\nOutline of plane in Object mode does not Render after applying transforms and looking Down the plane in top down view or any view.\n\n1. Delete the default cube.\n2. Add a Plane.\n3. Numpad 7 for top down view.\n4. selct the plane and rotate on x axis 90 degrees\n5. Apply all transforms.\n\nFrom Blend File Just Select the plane and press numpad 7 to go to Topdown view and Out line should stop rendering.", "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 with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "Blender 2.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", "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.", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n" ]

[ "Crash when rendering to Quicktime\nOperating system and graphics card\n\nOS: OS X: 10.8.5 \nIntel HD graphics 4000\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\nBlender 2.68\nWorked just fine\n\n**Short description of error** When i trie to render an animation with the format quicktime the program just crash. I have tried several times on different files with the same result.\n\n**Exact steps for others to reproduce the error** I sate al frames and had al settings ready, i put output format to quicktime and then hit render animation. \n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "\"Long Hair\" children pulled to world origin when using Texture (2.93.4 regression)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.4\nWorked: 2.93.3\n\nMy particle hair system works as expected in 2.91+ up to 2.93.3:\n\n\nIn 2.93.4, the children are pulled towards world (not object) origin:\n\n\nThis appears to only happen IF a texture is used to affect Density AND \"Long Hair\" is checked.\n\n\n\n1. Move default cube away from origin\n2. Add particle system\n3. Enable interpolated children\n4. Check \"Long Hair\"\n5. Add a Texture (even a cloud texture works)\n6. Enable Density influence\n\n\n\nBlend file with error:\n\n[Bug3.blend](Bug3.blend)\n", "Poisson Disk distribution method is uneven with selection mask\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.2.0\n\nPoint cloud is not decent, if using selection mask to *Point Distribution* node. Applying it directly to input mesh geometry makes distribution even.\n\nIn attached file mute/unmute *Separate Geometry* node to see how point distribution is performing.\n[point_distribution_problem.blend](point_distribution_problem.blend)", "Physics different between rigid body and particle system\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.1.0\n\nInconsistent of physics behavior between particle and rigid body with same mass when affected by force-field.\n\n1. Turn off gravity.\n2. 1kg Cube with Rigid Body.\n3. A Particle system with the setting, scale: 1, mass: 1kg, and only emit one particle.\n4. Add a force field with strength of 10/-10.\n5. Play and see the difference.\n\nThe behavior in Particle System is 100x faster than normal rigid body. Is this expected?\n", "Edges are selected in face mode when deselecting vertices from vertex group Panel\nBlender Version\nBroken: Current main.\nWorked: N/A.\n\nShort description of error\nDeselect Button in Vertex Groups Panel will deselect vertices that are not assigned to any groups. Edges become selected while in Face Mode as well. Also the Select Button will Select Faces that are not assigned too but those Edges that are active in face mode must be Selected for the Bug to work. Pay attention to the Edge around the triangle Fan at the top of the uv Sphere While in face mode.\n\nBlend File Incuded for simplicity\nJust Press the Deselect and notice the Faces that Get removed. and the Edges are actively Selected.\n\n", "Intersect Knife produce wrong results when the faces are coplanar\nOperating system: windows 10\nGraphics card: 1070X2\n\nBroken: 2.83.5\nWorked: 2.79\n\n\nso all the points are on the plane, and I'd make a grid of faces. So i use the knife (self intersect) tool, which i used to use in 2.79, and it produces results that are not correct\n\n\n\n\nFile :\n[untitled.blend](untitled.blend)", "Remesh with small voxel size sometimes generates mesh with many holes\nOperating system: macOS-14.0-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: 3.1 - 4.0\n\nRemeshing breaks objects\n<video src=\"attachment\" controls></video>\n\nIn a new scene add a monkey model and jump into sculpting, change the voxel size to 0.0024 m and remesh...the object breaks\n\n", "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", "Bug: Extrude faces along normals + \"Individual origins\" pivot point\nOperating system: Windows 10 64-bit\nGraphics card: NVIDIA Geforce GTX 960M\n\nBroken: 2.80 957b4547aeeb 2019-01-28 22:11\nWorked: Set the piviot point option to anything else, such as bounding box center, 3D cursor, etc.\n\nWith pivot point set to **individual origins**, the tool **Extrude faces along normals** don't work properly. It just acts like the **extrude** tool.\n\nVery simple. open the startup file with a cube, set the pivot point to **individual origins** and use **extrude faces along normals**(Alt+E) inside the edit mode.", "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", "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)", "Flashing vertices on screen updates\nWindows 10 Home, version 1909, 64-bit\n| Graphics card: | Author:\n| -- | -- |\n| GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 | @Code_Craft_Plugin\n| GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89 | @MontagueMGM\n\nBroken: 2.83.0 - 2.83.10 (still broken as of latest 2.92.0 alpha experimental build acbda123ad08)\nWorked: 2.82.7\n\nVertices flash when the screen is updating. Only on my desktop using a GTX 780, not my laptop using an i7-1065G7 (Intel Iris Plus)\n\nCreate an Ico Sphere with subdivisions set to 6. It happens at levels 5 and 7 as well, but not nearly as noticeable. It seems related to a specific vertex count, rather than proportional to the number of vertices.\n\n[Blender 2021-01-12 02-13-49.mp4](Blender_2021-01-12_02-13-49.mp4)", "Particle System as flow source doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013\n\nBroken: version: 2.90 (sub 1)\nWorked: blender-2.83-c26f470cfeea-windows64\n\nParticle System as flow source doesn't work. Smoke is always emitted from mesh.\n\nIf file is opened in version that worked, smoke starts flowing from particles correctly. File doesn't have to be even re-saved in working version.\n\nBecause example file is reproducible only once, here are\n**Steps to create example file**\n- New General template\n- Add UV Sphere\n- Add particles to cube\n- Particle Properties > Emission > Number = 50\n- Particle Properties > Render > Render As = Object\n- Particle Properties > Render > Instance Object = Sphere\n- Particle Properties > Render > Scale = .6\n- {key F3} > Quick Smoke\n- Select Cube again\n- Physics Properties > Flow Source > Flow Source = Particle System (doesn't invalidate cache)\n# Physics Properties > Flow Source > Particle System = ParticleSettings (doesn't invalidate cache)\n\n[#76765.blend](T76765.blend)\n- Open file\n- Play animation\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", "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", "Make force fields support solid objects\nCurrently, if a force field is created with a *Surface* shape, particles (and hair and cloth) will be attracted or repelled along the normals of the mesh. With a positive force, particles are always repelled away from the nearest face. This works well for surface meshes, i.e. where the faces are two-sided. However, it is not useful for simulating solid meshes.\n\nFor a solid mesh, the faces should be considered to be single-sided: the direction of the force should not change when the particle crosses the face, as shown in B in the following diagram.\n\n\n\n - A: Current behaviour: force direction always reverses at face boundary and at midpoint between faces. Particles can get trapped inside solid objects.\n - B: Proposed behaviour: force direction is consistent across face boundary, but still reverses at midpoint. Allows particles to be repelled from surface and pushed out from inside.\n\nThis `.blend` file demonstrates the problem: if the particles or cloth end up inside the cube, they never escape. Under this proposal they should be repelled, because the force field strength is positive.\n\n[cloth_cube_repel.blend](cloth_cube_repel.blend)\n\nIf this is option is implemented, it could be exposed as a new option, or the *Both Z* / *+Z* / *-Z* options could be reused for it." ]

[ "Particle Created at Object's Origin Even If No Face Is There\nOperating system: Both Windows and Linux\nGraphics card: Various nVidia cards\n\nBroken: 2.90\n\nCreate an object with two separate components. Set its origin to somewhere strictly between the two components, so that the origin is not part of any face. Generate particles on that object. Then a particle can appear at the origin.\n\nCreate two planes. Space them apart. Join them. Set the joined object's origin to geometry. Put a particle system on it. Change end time to 1. Observe a particle is generated at the object's origin even though there is no face there.\n\n[Particle Bug.blend](Particle_Bug.blend)\n[system-info.txt](system-info.txt)" ]

[ "\"View\" settings not refreshing when going out of camera view\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.80 (sub 74)\n\nNot a big bug, but I'm reporting anyway.\n - Open file:\n[viewport_camera_settings_bug.blend](viewport_camera_settings_bug.blend)\n - Use middle mouse button to go out of camera view. Simple click should be enough.\n - Some of the settings in \"View\" will be greyed out until hovered over with mouse cursor:\n\n\n", "Black outlines around animated Objects when Scrubbing/Playback.\nOperating system: Windows 10 64 Bits\nGraphics card: GTX 1080 TI.\n\nBroken: version: 2.83.8 hash: 7c027f9480a9\nWorked: version: 2.83.4 hash: `abb7364912` (commit date: 2020-02-23 23:00)\n\nThere are some weird black outlines popping out during anim playback or scrubbing. \n\n***P**\n{[F8400153](spot.jpg) size = full}\n\n\n* open the file\n* If it is not already set, set viewport shading to material preview (that's where you can easily spot them)\n* playback the animation or quickly move the object\n\nThe black outlines will appear but the moment you stop they'll disappear, so you can screen capture the moment to check their existence ***P**.\n\n[Black.blend](Black.blend)\n", "Links persist invisibly after their source sockets are removed\nBroken: Probably forever (e.g. 3.0, 3.1)\nWorked: N/A\n\nIf the output socket of a node is removed, the input socket it was connected to does not show a button to input a value. It acts like it's still connected.\n\n**Detailed replication**\n1. Go into the Shader Editor\n2. Create the *Voronoi Texture* node and a *Math* node\n3. Set the *Voronoi Texture* node to 4D, and plug its new W output into the *Math* node\n4. Set the *Voronoi Texture* node to 3D. Observe that the input on the *Math* node still acts like it's connected\n5. Click and drag from that input on the *Math* node. A bogus wire will appear from the *Voronoi Texture* node, coming from where the W output used to be.\n\nYou can then plug this wire into another socket. It will disappear again once you let go. If you set the *Voronoi Texture* node back to 4D, the wires will re-appear.\n\nVideo example:\n\n[XwBMq60aMI.mp4](XwBMq60aMI.mp4)\n\n**Another example:**\n\n{[F13079601](free-socket.blend), size=full}\n\nIn this case you can even save the file in this state where you can't see or edit the value of the node until you disconnect it.\n\n", "Removing a quick favorite leaves sub-levels of enum menus open\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nBroken: version: 3.6.2\n\nRemoving a property while the list is expanding keeps it expanded.\n\n\n1. Add to quick favorite a property with an enumeration.\n2. Call it and open it.\n3. Remove a property from quick favorites.\n\n", "Clearing library overrides from the object menu differs from the outliner\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.6.1 Release Candidate\n\nPlease see the attached movie. Using the \"wrong\" menu will cause the material properties panel to become unresponsive (beginning of movie) with overrides still in place until you use the outliner (end of the movie).\n\n1. Link some objects from a file\n2. Override them down to the materials\n3. Swap out some materials\n4. Use the clear library override from the object menu\n\nResult:\n\nThe material overrides aren't cleared, but you also can't access the properties panel anymore.\n\nExpected:\n\nThe material overrides should be cleared.\n\nWorkaround:\n\nUse the outliner instead.\n\n", "The viewport lock modes are super glitch (in general) with zooms and centering\nOperating system: Windows 10\n\n\nBroken: blender-3.0.0-alpha+master.eae4e2251839-windows.amd64-release\n\n\n\nThe viewport lock modes like 3d cursor or object locking is super glitchy in general which creates a disorienting experience. The main issue is sudden jumps in zooms also sometimes the center or rotation becomes jumpy as well. Some jumps in the video is worse than the others. Bear in mind that I am not zooming intentionally when there is a sudden jump.\n\nThis gets even worse in different scene scales and scene layouts. Here I am demonstrating it only with the cursor but this erratic behavior happens with object locking too. This becomes even worse with a Wacom tablet since it is harder to keep the pen movement as static as the mouse while zooming.\n\n\n- Load the attached .blend file\n- Make sure the viewlock is set to the cursor, and have similar preferences as shown in the pictures\n- Try repositioning the cursor, just move the cursor to different objects.\n- Move the cursor to the surface of another object then try ctrl+single middle click to activate the zoom\n\n\n\n\n\n\n\nTest File:\n[glitchy_lock_modes_28082021_2053_04.blend](glitchy_lock_modes_28082021_2053_04.blend)\n\n[A7ysxb6GVc.mp4](A7ysxb6GVc.mp4)", "Grease Pencil problem (especially soft pencil) \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n\nSince couple version of Blender I cannot use a soft pencil (mainly) brush in Grease Pencil 2D animation mode. The issue depends on how much You zoom. When You zoom in and use same size it's not visible. When You zoom out and draw with same size dots are visible. \nIt's behavior is very strange now and produces bad results (visible dotted lines or other which are visible on attached file. Some of these issues occur when the brush is small (line type set as dots). This is much more more visible when stroke stabilization is on. The bug was not there about 2 years ago and I was able to use the soft pencil without such problems. When line type is set to line the pencil stroke has strange contour around and when self overlap is off it produces artifacts on edges. \n\n\n\nJust choose a soft pencil and make it small. Check it with stroke stabilization as well. Then change the line type to line with self overlap on and off. \n\n", "The display will be damaged when the node editor in Fullscreen Area mode (ctrl alt spacebar)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R7 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.11.1 27.20.12033.2007\n\nBroken: 2.93 as well as version: 3.0.0 Beta\nWorked: Haven't tested before 2.93.\n\nThe display will be damaged when the node editor in Fullscreen Area mode (ctrl alt spacebar).\n\n* Switch workspace to Geometry Nodes\n* Add a new Geometry Nodes modifier/datablock\n* Ctrl+Alt+Space to go fullscreen (not Ctrl + Space)\n* Select or move a node\n\nFile:\n[bug.blend](bug.blend)\n\nGIF：\n", "Using LineArt modifier , line behind object will appear unexpectedly.\nSystem Information\nOperating system: Windows-10 64bit ver.20H2 os build 19042.1052{[F10208498](2021-07-02__3_.png)}\n\nGraphics card: NVIDIA Quadro [P2000](P2000.txt) driver ver.R470 U1 (471.11) WHQL\n\nBlender Version\nBroken: version: 3.0.0 Alpha\n\n**Short description of error:**\nUsing LineArt modifier , line behind object will appear unexpectedly.\n\n[2021-07-09 10-22-31.mp4](2021-07-09_10-22-31.mp4)\n\n**Exact steps for others to reproduce the error:**\n[lineartTest.blend](lineartTest.blend)\n\n- Open file \n- Tweak camera shift X property from min to max\n\nLines won't be drawn for some objects. \nBug looks a bit different in `7489427e4d` than what's shown in video\n\nAny way ,I’m excited new features.Thank you all to a great work.\nHave a nice days.", "driver on an NLA animated time strip isn't purple and cannot be removed\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.93.0 Alpha\n+ version: 2.92.0\nWorked: never\n\nWhen adding a driver on an NLA animated time strip value, the value does not turn purple, and cannot be remove.\nDon't know if it's related or not, but you also cannot delete/clear keyframes on that particular value aswell. Should i do another bug report ?\n\n(see video attached)\nanimate the default cube (example : revolution on Z axis, from frame 1 to 250)\ncreate an empty, add a custom property, animate that property\ncopy the custom property as a new driver\ngo to the NLA, push down the cube action, go to it's strip option and check \"animated time strips\"\npaste the driver on the \"animated time strips\" value\n[bugreport_drivercolor.mp4](bugreport_drivercolor.mp4)", "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}", "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", "GPencil: Average tool in Vertex Paint mode not working as expected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nThe tool paints colors that exist in points far from the brush's area of influence and sometimes paints unexisting colors.\n\n1. Draw simple strokes with the Solid Stroke material.\n2. In VP mode paint half of it orange and half blue.\n3. try the the Average tool in the half blue area then in the other half.\n4. Now do Paint > Reset Vertex Color.\n5. Try the Average tool again.\n\n<video src=\"attachment\" title=\"Vertex Paint Bug-1.mp4\" controls></video>\n\n", "Restore default value operator removes redo panel\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.0\nWorked: 3.4.1\n\nWith user installed add-ons (sometimes Blenders own operators too) if the user tries to reset a value by RightMouseClick / \"Reset To Default Value\", the redo panel closes.\n\n1) Activate the user installed add-on\n2) Change a value\n3) RMB on the property from redo panel, select \"Reset To Default Value\"\n\nThis will close the panel and end the active add-on (may not happen on first attempt)\n\nYouTube video at the link:\n4woEVTFSrtw\n\n", "Certain Float Curve clipping values (e.g. `Min Y -1` together with `Min X 0` & `Max X 0`) break the UI\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\n\nchanging float curve clipping values (e.g. `Min Y -1` together with `Min X 0` & `Max X 0`) break the UI\n\nchange y clipping to -1 then zoom in/out with the magnifier icons:\n\nUI disappears\n\n\n" ]

[ "Blue dot in the middle of the screen\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0 Beta\nWorked: 2.83\n\nblue dot in the middle of the screen aligned with the center point of rotation\n\n\n\n\ndont know, just appears, took out all the addons i had and changed to default theme, the only thing that works is to revert to defaults for some reason\n\nwhen the viewport size changes its affected too but only the shape" ]

[ "Boolean - Animation - Viewport works correctly render view doesnt\nUbuntu 18.04, Win 7 x64\n\nBroken: d53093953f8\n\nBooleans dont match between Viewport and Render\n\n1. Open attached blend file\n2. Preview render (shift z)\n3. Notice the green on top\n4. F12 Render\n5. Notice how the green is no longer there\n\n[booleansBug.blend](booleansBug.blend)", "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", "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", "UI: activate_init doesn't work with Int and Float type properties\nOperating system: Windows & Linux\n\nBroken: 3.2\nWorked: Unknown\n\nUsing activate_init to allow users to directly edit a property doesn't seem to work when the property is of type IntProperty or FloatProperty.\n\n1. Open the attached script in blenders text editor\n2. Run the script\n3. Go to the 3d viewport\n4. Ensure an object is selected/active\n5. Run the simple operator, either through the menu or operator search\n6. Notice that the property in the popup is not directly editable\n\n[test_activate_init.py](test_activate_init.py)", "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", "FADE INNACTIVE GEOMETRY MODE doesn't work properly with COLLECTION INSTANCES\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\n\nI really like this mode, but it feels likeit not completely done. It's not work with collection instances at all.\nHere is was my expectations and what it looks like currently: \n\nAnd even instances from other scenes ignore this mode too. Will be cool if it(instances) will work in stream ideology of this mode\n\n\nOpen this file [FADE INNACTIVE GEOMETRY DOESN'T WORK PROPERLY WITH INSTANCES.blend](FADE_INNACTIVE_GEOMETRY_DOESN_T_WORK_PROPERLY_WITH_INSTANCES.blend) and select (one by one) buttom figures (cone/torus/cube) and after selecting each one - press Tab.\nYou will see that instances ignores this mode\n\n", "Eevee 'Principled Normal' connected to 'Normal Map' node is disabling 'Displacement'\nOperating system: Win 10\nGraphics card: 2x1080Ti\n\nBroken: blender-2.91.2-windows64, blender-2.93.0-420f538fadfd-windows64\nNever worked as long as I remember\n\nBasically connecting normal map to principled shader is disabling any displacement map connected to the output. Just unplugging normal from principled turning it on. I don't know if its a bug or is it intentional \n\nNormal and displacement plugged in - displacement not working\n\nNormal unplugged - displacement working\n\n\n- Open attached file\n- Compare the result in Eevee with Cycles\n[bump_test2.blend](bump_test2.blend)", "The X or Delete button does not work in the outliner (Blender File)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\n[The X or Delete button does not work in the outliner (Blender File)]\n\n- Open default startup file\n- {nav Outliner >Display Mode > Blender File}\n- In outliner {nav Brush > RMB > Delete > RMB > Assign Shortcut > X}\n- Attempt to delete any brush with hotkey (will not delete brush)\n- Change hotkey (eg {key Shift X}) and now attempt to delete brush with hotkey\n\nwhen you press X items in:\n| Broken | Brushes, Cameras, Images, Lights, Line Styles, Materials, Meshes, Palettes, Workspaces, Worlds |\n| -- | -- |\n| worked | Collections, Objects, Scenes |\n\n\n\n\n[Delete _X_ Button.blend.py](Delete__X__Button.blend.py)\n\n{[F12271213](Delete__X__Button.blend)}]\n\n", "Clang on windows\nWhile we have supported building with clang on windows for a while, support has deteriorated a little due to it not getting regular exercise also not all features were supported this is a list of outstanding issues with clang on windows.\n\nOrder of importance:\n\n- {icon circle color=red} **Very Important** - *These we should handle before the next release.*\n- {icon circle color=yellow} **Somewhat Important** - *These issues would be nice to do as soon as possible*\n- {icon circle color=green} **Less Important** - *Extra polish, nice to have*\n- `?` **Incomplete** - *Tasks needing more details before implementing.*\n \n- {icon circle color=green} Better documentation on how to build, [the initial commit ](rB81060ff6b26c22331d2066bb83d492bbe61e936c) had instructions but some of those instructions are no longer applicable \n- {icon circle color=green} [D5962: Fix: Building quadraflow with clang on windows.](D5962)\n- {icon circle color=green} ~~Building with clang+ninja is broken~~ fixed:34bd23dbb7\n- {icon circle color=gray} VS2019 IDE support is broken due to the llvm integration addon, VS2017 IDE works, ninja work for both 2017/2019 \n- {icon circle color=green} [D5976: Add support for building with OpenMP support for clang on windows.](D5976)\n- {icon circle color=green} [D6012: Fix: BLI_expr_pylike_eval_test test failing with clang on windows](D6012)\n- {icon circle color=green} Cycles had a broken AVX2 kernel when running the benchmarks on EC2 \n- {icon circle color=green} Too many warnings a full build log is over 1GB \n- {icon circle color=green} cycles kernels get fed clang flags which it does not recognize `-fno-trapping-math`, `-fno-math-errno` , `-fno-signed-zeros`", "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", "NLA Strip influence slider doesn't respond to autokey correctly.\nOperating system: Win 10\nGraphics card: GeForce GTX 1070\n\n\nBroken: 2.82 Release\n\n\nThe Influence property of the NLA's strip, has some strange behavior and something that might be a bug.\nThis was reported before in #63865, which was supposedly resolved, but the problem still exists\n\nWhen changing the value of the influence slider with the autokey turned on, it jumps back to its previous value and does not update to the new one. After repeating it 2 or 3 times it applies the value. When applying the value numerically it works fine, it seems to be a problem with the update of the slider.\nMoreover, when turning influence on it always adds a keyframe to the first frame of the action (where the action is on the timeline ). It sets a keyframe with the value 0, instead of the current value.\n\n- Open attached file\n- Select one of the Action strips.\n- In the Sidebar, go to {nav Strip > Active Strip} and turn on `Animated Influence`. (Note that a keyframe is added to the first frame of the action).\n- Go to a new frame with the Autokey turned on, change the value of the influence slider.\n- Go to a new frame - the value should jump back to the previous one\n\nI've made a short video which describes the errors\nwatch?v=Sh5MwYCH9T4\n\nSample file:\n\n[Influence_bugreport.blend](Influence_bugreport.blend)", "Rigid body Bounciness parameter not functioning\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: 2.92 and version: 3.0.0 Alpha\nWorked: 2.83.13\n\nIn recent Blender versions the bounciness parameter of rigid bodies does nothing.\n\nOpen attached file, press space to start animation.\nOlder versions: ball bounces\nRecent versions: ball falls and immediately comes to an halt when it hits the surface of the cube.\n\n[Bounciness bug.blend](Bounciness_bug.blend)", "Online Manual doesn't work for Panel Pin property\nSystem Information\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\nBlender Version\nBroken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: blender/blender@b292cfe5a9\nWorked: Was not working since 2.93 LTS, haven't tested lower ones, but I am pretty sure it is not working there as well\n\nShort description of error\nBlender Online Manual operator is not working for Panel Pin property, though it works for any other pinning property.\n2022-11-23 22-16-34.mp4\n\nExact steps for others to reproduce the error\n\n Open Sidebar (in any editor with Sidebar, shortcut {key N})\n Hover over panel header and press RMB -> You will see Pin property,\n press RMB in the Pin property to see it's context menu\n then press Online Manual or just press F1 key.\n\nNote that in the property editor the Online Manual works.\n\n\n------\n\nThis issue has been transferred from 102727\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", "[Python API] Not working `alert' property of 'bpy.types.UILayout' that contains 'popover'\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.1\nWorked: seems to be never worked\n\n**'Alert' property of 'bpy.types.UILayout' that contains 'popover' is not displayed**\n\n1. Open file `space_outliner.py`\n2. Set`OUTLINER_PT_filter` row layout `alert` property to `True` and `active` property to `False`\n\n\n\n**Expected:**\n\nWe expect row to be of red color because of `alert=True` and reduced opacity because of `acitve=False`\n\n**Result:**\n\n\n\nIt is not working for row layout that contains `popover` method\n\n" ]

[ "Radar and near logic blocks do not work in r 2.56.6 r36007\n%%%Just opened a file created in 2.56 that uses radar logic blocks. In 2.57 they do not work, and do not show in physics visualisation mode.\n\nThe blend attached has both radar and near active, and in theory change 2d filters on activation (collision with the plane with the 'floor' property). \n\nThis set up works for collison, ray and touch.\n\nPC:\n\nWin 7 x64\nGeForce 8800 ultra\nBlender r 2.56.6 r36007 (splash screen)%%%" ]

[ "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", "Blender crashes with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n", "Blender Crash when deleting images too fast\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.44 30.0.13044.0\n\nBroken: version: 3.2.0\n\nBlender crashes when deleting images in the Layer blend file libery\n(3.3 alpha is crashing also and i didnt found any report about this issue)\n\n\n* go to outliner -> select blend file\n* make sure to be in the material preview mode\n* delete the first image by right click and then click on delete image\n* (now u only need to rightclick and leftclick to delete next images, because u dont need to aim for the delete anymore)\n* delete images while blender tries to preview the last change after deleting one of the images\n blender crashes\nwhen deleting images too fast, my blender just crashes (happens on my bad pc often, because i download models and rework them)\nIf you wait for the new material preview of the model after deleting nothing happens, but if you dont blender crashes when continuing to delete images\n\nVideo: CvO9nw4qilc\n\n[pharaoh x suite.blend](pharaoh_x_suite.blend)\n", "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", "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", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Region overlap crashes when interacting with action zones\nEnable region overlap user preference.\n\nIn the default 3D viewport, press NKey, then drag on the corner widget. -> Blender crashes.\n\nAttached asan output: [region_overlap_azone.txt](region_overlap_azone.txt), [region_overlap_azone_2020_01_28_update.txt](region_overlap_azone_2020_01_28_update.txt) (found while investigating #46764).\n\nUpdated asan output\n\n\n----\n\nNote: Blender internals aren't well suited of handling regions being manipulated like this while the rest of Blender is being used. We could either prevent interaction during the fade, or disable it since its not really needed.", "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 on calling bpy.ops.mesh.loopcut in python script\nOperation system: macOS BigSur 11.6 (20G165) \nApple M1\n\nVersion 3.4.1 (3.4.1 2022-12-20)\n\nBlender crashes in background mode when you are calling bpy.ops.mesh.loopcut with overridden context\n\nRun Blender from cli with args:\n/path/to/bin --background --python bug.py\n[bug.py](bug.py)\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", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n", "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", "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", "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", "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" ]

[ "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", "Crash and hang when opening the 2d animation template\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.17.5 355.10.05.45f01\nmacOS Sierra 10.12.6\n\nBroken: version: 2.83.1\n\nBlender hangs (i.e. shows beachball) and then crashes when I try to create a new project form the \"2D animation\" template.\n\nSelect *File --> New --> 2d animation.*\n\n* Output of `blender --debug --factory-startup`: [1.txt](1.txt)\n\n\n* Stack trace: [2.txt](2.txt)\n", "Blender 2.83 on MacOSX 10.12.6 quits when switching the viewport shading to Material preview or Render preview\nOperating system: Mac OS X 10.12.6 (16G2136)\nGraphics card: NVIDIA GeForce GTX 775M, PCIe, 2048 MB\n\nBroken: 2.83.0\nWorked: 2.82a\nBlender quits when switching the viewport shading to Material preview or Render preview.\n\nBased on the default startup.\nBlender quits when switching the viewport shading to Material preview or Render preview.\n\nCrash report:\n```lines=20\nProcess: Blender [65294]\nPath: /Applications/Blender283.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.83.0 (2.83.0 2020-06-03)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [65294]\nUser ID: 501\n\nDate/Time: 2020-06-06 14:10:32.564 +0200\nOS Version: Mac OS X 10.12.6 (16G2136)\nReport Version: 12\nAnonymous UUID: 6B6BEF92-56C3-91A5-4785-56FAD6FB4292\n\n\nTime Awake Since Boot: 1800000 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_CRASH (SIGABRT)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nApplication Specific Information:\nabort() called\n\nApplication Specific Signatures:\nGraphics hardware encountered an error and was reset: 0x0000000d\n\n\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 1:\n0 libsystem_kernel.dylib \t0x00007fff8b1d8386 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff8b093a77 _os_semaphore_wait + 16\n2 libdispatch.dylib \t0x00007fff8b084891 _dispatch_semaphore_wait_slow + 103\n3 org.blenderfoundation.blender \t0x000000010adbde72 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x000000010adbc9de 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 \t0x00007fff8b2ca93b _pthread_body + 180\n6 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n7 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff8b1d8386 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff8b093a77 _os_semaphore_wait + 16\n2 libdispatch.dylib \t0x00007fff8b084891 _dispatch_semaphore_wait_slow + 103\n3 org.blenderfoundation.blender \t0x000000010adbde72 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x000000010adbc9de 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 \t0x00007fff8b2ca93b _pthread_body + 180\n6 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n7 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff8b1d8386 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff8b093a77 _os_semaphore_wait + 16\n2 libdispatch.dylib \t0x00007fff8b084891 _dispatch_semaphore_wait_slow + 103\n3 org.blenderfoundation.blender \t0x000000010adbde72 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x000000010adbc9de 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 \t0x00007fff8b2ca93b _pthread_body + 180\n6 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n7 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff8b1d8386 semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff8b093a77 _os_semaphore_wait + 16\n2 libdispatch.dylib \t0x00007fff8b084891 _dispatch_semaphore_wait_slow + 103\n3 org.blenderfoundation.blender \t0x000000010adbde72 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x000000010adbc9de 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 \t0x00007fff8b2ca93b _pthread_body + 180\n6 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n7 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff8b1e044e __workq_kernreturn + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2ca621 _pthread_wqthread + 1426\n2 libsystem_pthread.dylib \t0x00007fff8b2ca07d start_wqthread + 13\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff8b1e044e __workq_kernreturn + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2ca48e _pthread_wqthread + 1023\n2 libsystem_pthread.dylib \t0x00007fff8b2ca07d start_wqthread + 13\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff8b1e044e __workq_kernreturn + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2ca621 _pthread_wqthread + 1426\n2 libsystem_pthread.dylib \t0x00007fff8b2ca07d start_wqthread + 13\n\nThread 8:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff8b1d834a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff8b1d7797 mach_msg + 55\n2 com.apple.audio.CoreAudio \t0x00007fff75415935 HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 127\n3 com.apple.audio.CoreAudio \t0x00007fff754158a6 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 42\n4 com.apple.audio.CoreAudio \t0x00007fff754128d0 HALC_ProxyIOContext::IOWorkLoop() + 1196\n5 com.apple.audio.CoreAudio \t0x00007fff75412264 HALC_ProxyIOContext::IOThreadEntry(void*) + 128\n6 com.apple.audio.CoreAudio \t0x00007fff75411fa3 HALB_IOThread::Entry(void*) + 75\n7 libsystem_pthread.dylib \t0x00007fff8b2ca93b _pthread_body + 180\n8 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n9 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff8b1dfbf2 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cb7fa _pthread_cond_wait + 712\n2 org.blenderfoundation.blender \t0x000000010c8eeebc task_scheduler_thread_run(void*) + 172\n3 libsystem_pthread.dylib \t0x00007fff8b2ca93b _pthread_body + 180\n4 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n5 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff8b1dfbf2 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cb7fa _pthread_cond_wait + 712\n2 org.blenderfoundation.blender \t0x000000010c8eeebc task_scheduler_thread_run(void*) + 172\n3 libsystem_pthread.dylib \t0x00007fff8b2ca93b _pthread_body + 180\n4 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n5 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff8b1dfbf2 __psynch_cvwait + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cb7fa _pthread_cond_wait + 712\n2 org.blenderfoundation.blender \t0x000000010c8eeebc task_scheduler_thread_run(void*) + 172\n3 libsystem_pthread.dylib \t0x00007fff8b2ca93b _pthread_body + 180\n4 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n5 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 12:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff8b1d834a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff8b1d7797 mach_msg + 55\n2 com.apple.CoreFoundation \t0x00007fff758acb44 __CFRunLoopServiceMachPort + 212\n3 com.apple.CoreFoundation \t0x00007fff758abfd1 __CFRunLoopRun + 1361\n4 com.apple.CoreFoundation \t0x00007fff758ab824 CFRunLoopRunSpecific + 420\n5 com.apple.AppKit \t0x00007fff734edf02 _NSEventThread + 205\n6 libsystem_pthread.dylib \t0x00007fff8b2ca93b _pthread_body + 180\n7 libsystem_pthread.dylib \t0x00007fff8b2ca887 _pthread_start + 286\n8 libsystem_pthread.dylib \t0x00007fff8b2ca08d thread_start + 13\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff8b1e044e __workq_kernreturn + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2ca48e _pthread_wqthread + 1023\n2 libsystem_pthread.dylib \t0x00007fff8b2ca07d start_wqthread + 13\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\nBinary Images:\n 0x106351000 - 0x10f19afd7 +org.blenderfoundation.blender (2.83.0 - 2.83.0 2020-06-03) <95B530D5-AB91-34D9-89D7-A9E765FE466B> /Applications/Blender283.app/Contents/MacOS/Blender\n 0x1150aa000 - 0x11510bff7 +libomp.dylib (0) <C32CE1B6-6F34-34E2-B9A3-7B8AD010CE68> /Applications/Blender283.app/Contents/Resources/lib/libomp.dylib\n 0x11513e000 - 0x115140ff7 com.apple.ForceFeedback (1.0.6 - 1.0.6) <313F7E57-FA8B-3AEC-BE47-C2C7B4F6FFAB> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x11772d000 - 0x117894fff com.apple.audio.units.Components (1.14 - 1.14) <D4B6F2DA-EDA4-32DB-B3AA-BD40A06B444D> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11792b000 - 0x11792ffff com.apple.audio.AppleHDAHALPlugIn (279.48 - 279.48) <ECA84145-2AC4-347D-BBC0-933AAAC15356> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x119145000 - 0x1192ebfff GLEngine (14.0.16) <C21BEA53-21B2-3EBB-84C6-CFCAB4D6012A> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine\n 0x11932a000 - 0x119354fff GLRendererFloat (14.0.16) <8CB95D3F-453E-3FD1-B9AE-E72E00A9562F> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x12164c000 - 0x121689dc7 dyld (434) <33DB4E37-BC29-37A4-92AB-30328E66A8FA> /usr/lib/dyld\n 0x1239df000 - 0x1239dfff7 +_heapq.cpython-37m-darwin.so (0) <B2C16C94-AFCF-3321-9935-D846CAD5D883> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x123c31000 - 0x123c36ffb +math.cpython-37m-darwin.so (0) <8C6DB195-BA99-37F0-8F83-B6A50846E691> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x124482000 - 0x12448bffb +_socket.cpython-37m-darwin.so (0) <8F5E8658-C0D9-3347-8920-B09C8E70F737> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_socket.cpython-37m-darwin.so\n 0x1244dd000 - 0x1244e0fff +select.cpython-37m-darwin.so (0) <7B070545-FD04-37FB-B02C-578E78E52039> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/select.cpython-37m-darwin.so\n 0x1244eb000 - 0x1246ab4d7 +_ssl.cpython-37m-darwin.so (0) <4CB8A7FA-A711-3F4A-9E4E-629D2B00677A> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_ssl.cpython-37m-darwin.so\n 0x1247a2000 - 0x1247a6ff3 +_struct.cpython-37m-darwin.so (0) <D9C01FE2-CFD9-3CF5-897E-E60E75BAFED6> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_struct.cpython-37m-darwin.so\n 0x1247b4000 - 0x1247baff7 +binascii.cpython-37m-darwin.so (0) <9BA65CAC-5921-3C44-9D56-57C12E0872B9> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/binascii.cpython-37m-darwin.so\n 0x124843000 - 0x1249ad55b +_hashlib.cpython-37m-darwin.so (0) <99BF2485-60DB-3F52-9DB1-CBC47C63A05C> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_hashlib.cpython-37m-darwin.so\n 0x124a2a000 - 0x124a30ff3 +_blake2.cpython-37m-darwin.so (0) <5B267DCA-9784-3E40-A1EB-D8F87B3D5DC1> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_blake2.cpython-37m-darwin.so\n 0x124a3a000 - 0x124a4aff3 +_sha3.cpython-37m-darwin.so (0) <A40ED02F-5EA1-38B8-9763-70508791E022> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_sha3.cpython-37m-darwin.so\n 0x124a55000 - 0x124a55ffb +_bisect.cpython-37m-darwin.so (0) <8554F469-9D5F-3CA2-96A4-E5BD49959F63> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_bisect.cpython-37m-darwin.so\n 0x124a5d000 - 0x124a5effb +_random.cpython-37m-darwin.so (0) <F04007BC-59DF-35B2-9DAA-497E6424633E> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_random.cpython-37m-darwin.so\n 0x124aa6000 - 0x124ab4ff3 +_datetime.cpython-37m-darwin.so (0) <F163FDFB-833E-3737-A914-92E97094CD5C> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_datetime.cpython-37m-darwin.so\n 0x124b45000 - 0x124b46fff +_queue.cpython-37m-darwin.so (0) <54A5628B-DCB2-3A43-9663-E5617C7ED702> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_queue.cpython-37m-darwin.so\n 0x124b8f000 - 0x124c8dffb +unicodedata.cpython-37m-darwin.so (0) <91CE479D-0F97-3649-A105-E7A3425D40E8> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/unicodedata.cpython-37m-darwin.so\n 0x124d1b000 - 0x124d2dfff +zlib.cpython-37m-darwin.so (0) <1B6C3766-6D45-3DBE-9CB0-1E248836E828> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/zlib.cpython-37m-darwin.so\n 0x124e38000 - 0x124e4effb +_bz2.cpython-37m-darwin.so (0) <9DBD8BEA-132F-3B6C-88BD-61854B87CD49> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_bz2.cpython-37m-darwin.so\n 0x124e59000 - 0x124e87ffb +_lzma.cpython-37m-darwin.so (0) <7FA3FD49-E394-36DD-B23D-9A78635D6BA3> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_lzma.cpython-37m-darwin.so\n 0x124e96000 - 0x124e96ffb +grp.cpython-37m-darwin.so (0) <96FFE290-0576-3771-A211-62AC05FBB004> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/grp.cpython-37m-darwin.so\n 0x124ede000 - 0x124ee4ffb +_json.cpython-37m-darwin.so (0) <92B5CD6D-6140-3F86-A467-96002A6A52E8> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_json.cpython-37m-darwin.so\n 0x124f2e000 - 0x124f2eff3 +_scproxy.cpython-37m-darwin.so (0) <5F9616F1-1475-31B7-9EF6-DE7F425DD607> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_scproxy.cpython-37m-darwin.so\n 0x124ff6000 - 0x124ff7fff +_posixsubprocess.cpython-37m-darwin.so (0) <EFC1B711-3F9E-3F38-8F42-9B368CBB6FA6> /Applications/Blender283.app/Contents/Resources/2.83/python/lib/python3.7/lib-dynload/_posixsubprocess.cpython-37m-darwin.so\n 0x7fff704d3000 - 0x7fff70818ff7 com.apple.RawCamera.bundle (7.04 - 914) <86A67D11-9791-3CE6-9FF5-3387C0AB925B> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff70e23000 - 0x7fff71670fff com.apple.GeForceGLDriver (10.17.5 - 10.1.7) <7A5A5362-AF11-3BD3-A938-C47E2ADBA818> /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriver\n 0x7fff71671000 - 0x7fff71f36ff3 libclh.dylib (4.0.3 - 4.0.3) <217D02AE-81E3-3BF1-8FB5-77BF683A8FC0> /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib\n 0x7fff71f37000 - 0x7fff72047ff7 com.apple.GeForceMTLDriver (10.17.5 - 10.1.7) <4F41CF49-5613-3AA6-9B81-894AD262B1BF> /System/Library/Extensions/GeForceMTLDriver.bundle/Contents/MacOS/GeForceMTLDriver\n 0x7fff7237c000 - 0x7fff7237cfff com.apple.Accelerate (1.11 - Accelerate 1.11) <916E360F-323C-3AE1-AB3D-D1F3B284AEE9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff7237d000 - 0x7fff72394ffb libCGInterfaces.dylib (331.5) <17109679-A284-3C72-AA60-DBA815D3062B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff72395000 - 0x7fff728aefeb com.apple.vImage (8.1 - ???) <B58A7937-BEE2-38FE-87F4-5D5F40D31DC9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff728af000 - 0x7fff72a20ff3 libBLAS.dylib (1185.50.4) <4087FFE0-627E-3623-96B4-F0A9A1991E09> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff72a21000 - 0x7fff72a35ffb libBNNS.dylib (15) <254698C7-7D36-3FFF-864E-ADEEEE543076> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff72a36000 - 0x7fff72e2cfef libLAPACK.dylib (1185.50.4) <C35FFB2F-A0E6-3903-8A3C-113A74BCBCA2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff72e2d000 - 0x7fff72e43fff libLinearAlgebra.dylib (1185.50.4) <345CAACF-7263-36EF-B69B-793EA8B390AF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff72e44000 - 0x7fff72e4afff libQuadrature.dylib (3) <EF56C8E6-DE22-3C69-B543-A8648F335FDD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff72e4b000 - 0x7fff72e5fff7 libSparseBLAS.dylib (1185.50.4) <67BA432E-FB59-3C78-A8BE-ED4274CBC359> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff72e60000 - 0x7fff72fe7fe7 libvDSP.dylib (600.60.1) <4155F45B-41CD-3782-AE8F-7AE740FD83C3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff72fe8000 - 0x7fff7309afff libvMisc.dylib (600.60.1) <E18365D7-DCC4-3304-A8D1-395E656D7B99> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff7309b000 - 0x7fff7309bfff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <7C5733E7-0568-3E7D-AF61-160F19FED544> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff7335a000 - 0x7fff74133ff3 com.apple.AppKit (6.9 - 1504.84.100) <E39CD613-0104-3E26-B424-BE83CED656F9> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff74145000 - 0x7fff74145fff com.apple.ApplicationServices (48 - 48) <36EB2785-BBD2-33F0-BB13-8C804D47110A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff74146000 - 0x7fff741b4ff7 com.apple.ApplicationServices.ATS (377 - 422.4) <78B556FF-28E6-3147-AE0D-8E0EC45EEE77> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff7424e000 - 0x7fff7437dfff libFontParser.dylib (194.15) <FF329191-6339-363E-9D95-FFE9D55E7F60> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff7437e000 - 0x7fff743c8ff7 libFontRegistry.dylib (196.8) <5E5F95FD-F69B-3F1A-9592-C0AB8F5FF57C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff74426000 - 0x7fff74459fff libTrueTypeScaler.dylib (194.15) <513743F9-500B-37C5-A925-A82E7182F3E9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff744c6000 - 0x7fff74570ff7 com.apple.ColorSync (4.12.0 - 502.2) <ACA4001E-A0E3-33F6-9CD6-EEC2AA15E322> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff74571000 - 0x7fff745c2fff com.apple.HIServices (1.22 - 594) <EF8432A1-15C5-360C-9D14-19ADA43FCFDC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff745c3000 - 0x7fff745d2ff3 com.apple.LangAnalysis (1.7.0 - 1.7.0) <2CBE7F61-2056-3F96-99A1-0D527796AFA6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff745d3000 - 0x7fff74620fff com.apple.print.framework.PrintCore (12 - 491) <5027FD58-F0EE-33E4-8577-934CA06CD2AF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff74621000 - 0x7fff7465cfff com.apple.QD (3.12 - 313) <B339C41D-8CDF-3342-8414-F9717DCCADD4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff7465d000 - 0x7fff74668fff com.apple.speech.synthesis.framework (6.6.2 - 6.6.2) <7853EFF4-62B9-394E-B7B8-41A645656820> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff74669000 - 0x7fff74875ff7 com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <1F4026C6-23C1-39E8-823D-72298FECF75C> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff74876000 - 0x7fff74876fff com.apple.audio.units.AudioUnit (1.14 - 1.14) <2CEE36AF-79E6-3B3E-B369-285E6C1886F7> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff749df000 - 0x7fff74dbcfff com.apple.CFNetwork (811.11 - 811.11) <5E5A7D4D-BCBA-3995-8C13-4D01DE1FAB33> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff74dd6000 - 0x7fff74dd6fff com.apple.Carbon (154 - 157) <69F403C7-F0CB-34E6-89B0-235CF4978C17> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff74dd7000 - 0x7fff74ddafff com.apple.CommonPanels (1.2.6 - 98) <BF04BB22-D54C-309E-9F5C-897D969CAF70> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff74ddb000 - 0x7fff750e4fff com.apple.HIToolbox (2.1.1 - 857.8) <25E0AC26-27FE-32E5-9226-F4D42B25ED30> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff750e5000 - 0x7fff750e8ff7 com.apple.help (1.3.5 - 49) <B1A930E3-5907-3677-BACD-858EF68B172D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff750e9000 - 0x7fff750eefff com.apple.ImageCapture (9.0 - 9.0) <341252B4-E082-361A-B756-6A330259C741> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff750ef000 - 0x7fff75186ff3 com.apple.ink.framework (10.9 - 219) <1BD40B45-FD33-3177-A935-565EE5FC79D7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff75187000 - 0x7fff751a1fff com.apple.openscripting (1.7 - 172.1) <78F3256B-AF4C-324A-A591-ECA4443A469F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff751a2000 - 0x7fff751a3ff3 com.apple.print.framework.Print (12 - 267) <E2F82F1F-DC27-3EF0-9F75-B354F701450A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff751a4000 - 0x7fff751a6ff7 com.apple.securityhi (9.0 - 55006) <0DA7BABC-CE24-35FC-BF23-8EDF72D8C237> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff751a7000 - 0x7fff751adff7 com.apple.speech.recognition.framework (6.0.1 - 6.0.1) <082895DC-3AC7-3DEF-ADCA-5B018C19C9D3> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff7528e000 - 0x7fff7528efff com.apple.Cocoa (6.11 - 22) <85EDFBE1-75F0-369E-8CA8-C6A639B98FA6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff753d8000 - 0x7fff75465fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <78767F88-91D4-31CE-AAC6-1F9407F479BB> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff75466000 - 0x7fff75479fff com.apple.CoreBluetooth (1.0 - 1) <BCB78777-76F0-3CC1-8443-9E61AEF7EF63> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff7547a000 - 0x7fff75775fff com.apple.CoreData (120 - 754.2) <4C9CAB2C-60D4-3694-A0A0-5B04B14BD14E> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff75776000 - 0x7fff75823ff7 com.apple.CoreDisplay (1.0 - 1) <53D1EAFE-23A4-398D-BF52-E4299E670DB6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff75824000 - 0x7fff75cc0fe7 com.apple.CoreFoundation (6.9 - 1350.10) <60A73360-EE24-33A2-BF37-08CB8B96D2D9> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff75cc1000 - 0x7fff76343fff com.apple.CoreGraphics (2.0 - 1070.22.1) <8A053296-AA99-371C-B9C5-FCBF87C6CEFE> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff76344000 - 0x7fff76587ffb com.apple.CoreImage (12.4.0 - 451.4.9) <BE4303C9-C9D9-361D-AC94-DBE40EB6700E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff766ec000 - 0x7fff766ecfff com.apple.CoreServices (775.20 - 775.20) <22D3892B-719C-30B8-B84B-211CFE41AFA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff766ed000 - 0x7fff7673efff com.apple.AE (712.6 - 712.6) <9E9B4EC3-564D-3BA9-A9A4-1603E1F97F40> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff7673f000 - 0x7fff76a1aff7 com.apple.CoreServices.CarbonCore (1159.8 - 1159.8) <2B661676-E4F2-3E6F-BD25-DB685FCCA06A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff76a1b000 - 0x7fff76a4efff com.apple.DictionaryServices (1.2 - 274) <D23866E2-F7C8-3984-A9D4-96552CCDE573> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff76a4f000 - 0x7fff76a57ff3 com.apple.CoreServices.FSEvents (1230.50.1 - 1230.50.1) <2AD1B0E5-7214-37C4-8D11-A27C9CAC0F74> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff76a58000 - 0x7fff76bc4ffb com.apple.LaunchServices (775.20 - 775.20) <9106FF16-9587-313F-822C-2CD56204903E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff76bc5000 - 0x7fff76c75ffb com.apple.Metadata (10.7.0 - 1075.41) <FE2BC948-5014-3C50-9ED7-F9544B611363> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff76c76000 - 0x7fff76cd5fff com.apple.CoreServices.OSServices (775.20 - 775.20) <82D7E763-999D-31A0-AAE7-4F7A40105739> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff76cd6000 - 0x7fff76d46fff com.apple.SearchKit (1.4.0 - 1.4.0) <7A6DDA2B-03F1-3137-BA9E-1CC211973E26> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff76d47000 - 0x7fff76d8cff7 com.apple.coreservices.SharedFileList (38 - 38) <DA096678-93AB-3291-BDE2-482F1D544589> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff76e15000 - 0x7fff76f62ffb com.apple.CoreText (352.0 - 544.18) <B883809B-561B-31C5-949E-D2564B6F808A> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff76f63000 - 0x7fff76f98ff3 com.apple.CoreVideo (1.8 - 235.3) <AC11D5FB-C77B-34F5-B942-F698E84C229F> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff76f99000 - 0x7fff7700affb com.apple.framework.CoreWLAN (11.0 - 1200.31) <7300F2B4-0976-37F3-95E9-4B3BC102ED01> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff77108000 - 0x7fff7710dfff com.apple.DiskArbitration (2.7 - 2.7) <F47E07A4-D69D-312A-82C8-A1EE3C7C0EAC> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff7729f000 - 0x7fff77647ff7 com.apple.Foundation (6.9 - 1349.93) <A3CF1205-DE81-37FE-A574-0D381DECF122> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff77673000 - 0x7fff776a4fff com.apple.GSS (4.0 - 2.0) <453B5C6D-08B0-3199-AFC8-C71BABD6B704> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff77764000 - 0x7fff77807ff7 com.apple.Bluetooth (5.0.5 - 5.0.5f7) <DC83B429-A8C1-34F1-9FD9-C9BB99156DBE> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff77808000 - 0x7fff7789efff com.apple.framework.IOKit (2.0.2 - 1324.60.8) <46DA8966-AC27-3F51-BBB2-359A229BB0F7> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff7789f000 - 0x7fff778a5ffb com.apple.IOSurface (159.12 - 159.12) <E3D6FCED-F938-30A3-AD08-0998B674A492> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff778f8000 - 0x7fff77a58fef com.apple.ImageIO.framework (3.3.0 - 1599.13.1) <B48585FF-3B2D-32F6-85A6-07ECDDB2A6E9> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff77a59000 - 0x7fff77a5dfff libGIF.dylib (1599.13.1) <79C31DCF-3D95-32DE-9869-C1FA91F7C572> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff77a5e000 - 0x7fff77b4eff7 libJP2.dylib (1599.13.1) <5E34964D-36BC-3DDD-936B-D859B39117BB> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff77b4f000 - 0x7fff77b72ffb libJPEG.dylib (1599.13.1) <863E6D9C-E45A-33F7-8C52-2D2B81FCAE63> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff77b73000 - 0x7fff77b9aff7 libPng.dylib (1599.13.1) <06282D7B-70EC-34A5-9240-A80FD18DC2D0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff77b9b000 - 0x7fff77b9dff3 libRadiance.dylib (1599.13.1) <823DDB0C-6BD0-3073-ABE4-313FDA38E3B4> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff77b9e000 - 0x7fff77becfff libTIFF.dylib (1599.13.1) <B48CCFEF-BD6E-37EA-8F1C-CC2CF6775A0E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff78955000 - 0x7fff7896eff7 com.apple.Kerberos (3.0 - 1) <B9D242EB-E325-3A21-9812-C77CBBFB0D51> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff7914e000 - 0x7fff791a9fff com.apple.Metal (87.18 - 87.18) <E3618B54-C728-34CA-9E8A-9BD33A295D31> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff79a92000 - 0x7fff79a9afff com.apple.NetFS (6.0 - 4.0) <14A24D00-5673-330A-959D-87F72040DEFF> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff79c4b000 - 0x7fff79c70fff com.apple.audio.OpenAL (1.8 - 1.8) <E3447078-6A7E-3A6D-B136-B6EA93982EE1> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff79c71000 - 0x7fff79c79ff7 libcldcpuengine.dylib (2.8.5) <0D182C1C-2593-34C8-B454-78D3F5FF5724> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff79c7a000 - 0x7fff79cc8ff3 com.apple.opencl (2.8.6 - 2.8.6) <E7958F3E-F56C-35EC-87CD-6ADFC25D4512> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff79cc9000 - 0x7fff79ce2ffb com.apple.CFOpenDirectory (10.12 - 194) <A64E9A01-3F6E-36EA-9C10-88C564A68C9D> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff79ce3000 - 0x7fff79ceeff7 com.apple.OpenDirectory (10.12 - 194) <4298FFD0-B1A7-3064-AF5B-708B3FA38671> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff79cef000 - 0x7fff79cf1fff libCVMSPluginSupport.dylib (14.0.16) <25655EB3-7BF6-36EC-BD17-47F4DF499D7F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff79cf2000 - 0x7fff79cf5ff7 libCoreFSCache.dylib (156.3) <687C4CC3-6537-344B-8BE1-5234C8CB2864> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff79cf6000 - 0x7fff79cfafff libCoreVMClient.dylib (156.3) <E7AEFCBE-B6BF-3C7C-9A4E-E78CB04DB794> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff79cfb000 - 0x7fff79d04ff7 libGFXShared.dylib (14.0.16) <679D8495-1C5F-3932-A452-050A21E0EEBB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff79d05000 - 0x7fff79d10fff libGL.dylib (14.0.16) <0801F3B9-A525-32BB-9BC0-478947CE21D9> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff79d11000 - 0x7fff79d4dff7 libGLImage.dylib (14.0.16) <FE39C57B-056C-3CBF-B653-A8F2005631C1> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff79d4e000 - 0x7fff79ec4ff3 libGLProgrammability.dylib (14.0.16) <46B8611A-D245-33BF-AA38-E44B2119DA12> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff79ec5000 - 0x7fff79f06ff7 libGLU.dylib (14.0.16) <B285EAD6-B3AA-3753-BB85-75864BD6E76C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff7a86e000 - 0x7fff7a87cfff com.apple.opengl (14.0.16 - 14.0.16) <8D4CC067-4A70-34AE-945D-29407D780452> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff7b3ce000 - 0x7fff7b5cefff com.apple.QuartzCore (1.11 - 453.41.2) <564FBF07-0072-3587-91BE-7B0EFD6FBC1D> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff7bb39000 - 0x7fff7be3bfff com.apple.security (7.0 - 57740.60.30) <2DD7275B-40E5-3F8C-8258-8C73DD3EE438> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff7be3c000 - 0x7fff7beb1fff com.apple.securityfoundation (6.0 - 55132.50.7) <2AF6A217-45D3-30C2-86B6-F35AF827E698> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff7bedc000 - 0x7fff7bedfff3 com.apple.xpc.ServiceManagement (1.0 - 1) <F2AACDEF-7DCC-35B9-A6B6-119FF8D83DBB> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff7c266000 - 0x7fff7c2d5ff7 com.apple.SystemConfiguration (1.14 - 1.14) <98E76341-BB2F-3DF4-9DD4-F4AC7648EF0F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff7eb2e000 - 0x7fff7eb49ff3 com.apple.AppContainer (4.0 - 307.50.21) <C2E6BA3D-81FF-39C3-B4BF-DBB9A17DE078> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff7eb4a000 - 0x7fff7eb57ff3 com.apple.AppSandbox (4.0 - 307.50.21) <BF9FA426-8C11-358B-9E1F-A3901E3F2B14> /System/Library/PrivateFrameworks/AppSandbox.framework/Versions/A/AppSandbox\n 0x7fff7eb58000 - 0x7fff7eb7affb com.apple.framework.Apple80211 (12.0 - 1200.47.1) <F362FADE-B6F5-32B5-84E8-C3CE7FE5F851> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff7eb7b000 - 0x7fff7eb8afeb com.apple.AppleFSCompression (88.50.3 - 1.0) <478E8BFF-8BA2-375E-BE02-BA27F115C15A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff7ec7b000 - 0x7fff7ed0697f com.apple.AppleJPEG (1.0 - 1) <B9E9570D-04A4-34E4-B756-D200043B25B8> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff7f139000 - 0x7fff7f1b7ff7 com.apple.backup.framework (1.8.6 - 1.8.6) <2D75451A-8818-3D72-8480-489DF77D708B> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff7fe42000 - 0x7fff7fe69ff3 com.apple.ChunkingLibrary (173 - 173) <FC2165F9-FC93-39C0-8323-C2F43A5E00A3> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff8078e000 - 0x7fff80797ffb com.apple.CommonAuth (4.0 - 2.0) <A71AD8F9-5CC8-3072-8A0B-F5427D3E8163> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff80ee0000 - 0x7fff80ef0fff com.apple.CoreEmoji (1.0 - 40.3.3) <E9A28301-2D79-3A97-A046-028258A6ABE5> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff8122b000 - 0x7fff8125bff3 com.apple.CoreServicesInternal (276.2 - 276.2) <05EB7D45-DD4C-3A0F-AC63-A0C2A68E6481> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff814ec000 - 0x7fff8157bff7 com.apple.CoreSymbolication (62046) <2D4C3324-B647-3696-B92E-AAB1053EEB54> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff8157c000 - 0x7fff816bbfe7 com.apple.coreui (2.1 - 431.3) <8D0FA478-9B6C-3D6D-8ADF-8677BA0BF134> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff816bc000 - 0x7fff8178cff3 com.apple.CoreUtils (5.1 - 510.31) <B6636BBF-D37E-360E-A3EE-61BDC1736EEA> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff817dc000 - 0x7fff81841ff3 com.apple.framework.CoreWiFi (12.0 - 1200.31) <1B3FE242-8AEB-38BD-84A4-65DBC476FEEA> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff81842000 - 0x7fff81850ff7 com.apple.CrashReporterSupport (10.12 - 827) <802A9B81-E349-348B-90AB-10E40B654250> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff818c2000 - 0x7fff818ccffb com.apple.framework.DFRFoundation (1.0 - 104.25) <7CFF896C-EF22-3941-BB3D-F3615CE4C908> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff818cd000 - 0x7fff818d1ff3 com.apple.DSExternalDisplay (3.1 - 380) <4B5E3FF0-E8C3-38CC-BF72-418C928956AB> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff81907000 - 0x7fff8197cffb com.apple.datadetectorscore (7.0 - 539.1) <D84B64BA-CD56-368E-A31A-AC47C3780D0B> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff819b8000 - 0x7fff819f7fff com.apple.DebugSymbols (137 - 137) <58A70B66-2628-3CFE-B103-2200D95FC5F7> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff819f8000 - 0x7fff81b09fff com.apple.desktopservices (1.11.6 - 1.11.6) <225B3746-8626-34CD-8FA9-48A7C04ACCCF> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff81df1000 - 0x7fff82222ff7 com.apple.vision.FaceCore (3.3.2 - 3.3.2) <9391D5A3-738C-3136-9D07-518CB43DBADA> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff83579000 - 0x7fff83579fff libmetal_timestamp.dylib (600.0.49.9) <E5EED927-1671-3390-BCBB-D76201D63C73> /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib\n 0x7fff83586000 - 0x7fff83591ff3 libGPUSupportMercury.dylib (14.0.16) <BE0ED0DC-DDE4-32F0-9315-39678785A538> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff8384a000 - 0x7fff83866fff com.apple.GenerationalStorage (2.0 - 267.2) <22381303-B9A8-32D8-BDBF-871F0CDD81A5> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff83f77000 - 0x7fff83fedff3 com.apple.Heimdal (4.0 - 2.0) <9E554667-2A6D-3A86-883A-50C8AF98D0C0> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff84608000 - 0x7fff8460fffb com.apple.IOAccelerator (311.16.4 - 311.16.4) <F41EB563-1439-3745-BE98-4A4B6F45A7DF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff84611000 - 0x7fff84625ff7 com.apple.IOPresentment (1.0 - 29.10) <30DF04EE-10E2-353F-845F-A97B87DF3207> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff84626000 - 0x7fff84648fff com.apple.IconServices (74.4 - 74.4) <218DDD05-35F4-3833-B98D-471ED0EBC031> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff8472f000 - 0x7fff848e6fff com.apple.LanguageModeling (1.0 - 123.2.5) <A8CA965F-0399-310D-91C3-B93DDDE9A442> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff85207000 - 0x7fff85280ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <C323FC94-FFA5-3EE6-B2AC-7E61EA92F304> /System/Library/PrivateFrameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff8541d000 - 0x7fff85445ff7 com.apple.MultitouchSupport.framework (368.16 - 368.16) <F6EFB289-F4B1-36E7-88D4-D1C7B1630A23> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff854f7000 - 0x7fff85502fff com.apple.NetAuth (6.2 - 6.2) <E1D6BFF0-7F37-3866-9925-5DF40EB3A1F4> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff85ddb000 - 0x7fff85e1cff3 com.apple.PerformanceAnalysis (1.148.3 - 148.3) <DE16079A-5267-372A-9435-E993EB41252A> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff86504000 - 0x7fff8651efff com.apple.ProtocolBuffer (1 - 249.1) <A1F1B0F3-078F-378F-A9A9-0DEEA70E816A> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff86537000 - 0x7fff8655aff3 com.apple.RemoteViewServices (2.0 - 124) <6B967FDA-6591-302C-BA0A-76C4856E584E> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff87224000 - 0x7fff87227fff com.apple.SecCodeWrapper (4.0 - 307.50.21) <F8E957B2-D3F0-3B73-B38C-AE8868F00939> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff872b6000 - 0x7fff87343fff com.apple.Sharing (696.2.67.1 - 696.2.67.1) <267A3C7C-BB70-3E92-B773-A3F9EDD12E84> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff87364000 - 0x7fff875caff3 com.apple.SkyLight (1.600.0 - 170.3.11.11) <0F7F9F9B-90E2-3FE4-9A39-DE7EC10DAF79> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff877aa000 - 0x7fff877b6ff7 com.apple.SpeechRecognitionCore (3.3.2 - 3.3.2) <684BD1EA-8268-331C-A5A9-080EB375C658> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff87ea2000 - 0x7fff87f16fdf com.apple.Symbolication (62048.1) <1A30ED19-7532-3F46-9DD3-9879A973D0CF> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff88355000 - 0x7fff8835bff7 com.apple.TCC (1.0 - 1) <911B534B-4AC7-34E4-935E-E42ECD008CBC> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff883e7000 - 0x7fff884adff7 com.apple.TextureIO (2.8 - 2.8) <3D61E533-4156-3B21-B7ED-CB823E680DFC> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff88521000 - 0x7fff88522fff com.apple.TrustEvaluationAgent (2.0 - 28.50.1) <EBE65DD5-1732-3747-8C6C-7BECEBF089A4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff88523000 - 0x7fff886b4ff3 com.apple.UIFoundation (1.0 - 490.8) <0342C3E6-AB89-3F0D-A9CE-5F2CD3587B75> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff89183000 - 0x7fff89243fff com.apple.ViewBridge (283 - 283) <25A635B3-C87C-3D3A-ADF3-539713FA1048> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff8968e000 - 0x7fff89694fff com.apple.XPCService (2.0 - 1) <4B28B225-2105-33F4-9ED0-F04288FF4FB1> /System/Library/PrivateFrameworks/XPCService.framework/Versions/A/XPCService\n 0x7fff89765000 - 0x7fff89767ffb com.apple.loginsupport (1.0 - 1) <F3140B97-12C3-35A7-9D3D-43DA2D13C113> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff897bc000 - 0x7fff897d7ff7 libCRFSuite.dylib (34) <F78B7F5F-0B4F-35C6-AA2F-84EE9CB22137> /usr/lib/libCRFSuite.dylib\n 0x7fff897d8000 - 0x7fff897e3fff libChineseTokenizer.dylib (21) <0886E908-A825-36AF-B94B-2361FD8BC2A1> /usr/lib/libChineseTokenizer.dylib\n 0x7fff89875000 - 0x7fff89876ff3 libDiagnosticMessagesClient.dylib (102) <84A04D24-0E60-3810-A8C0-90A65E2DF61A> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff89877000 - 0x7fff89a8afff libFosl_dynamic.dylib (16.39) <E22A4243-D148-3C74-BA15-2D906A3D1F9E> /usr/lib/libFosl_dynamic.dylib\n 0x7fff89aa6000 - 0x7fff89aadfff libMatch.1.dylib (27) <70D4BD2A-9383-37F2-B0D6-9B592D236601> /usr/lib/libMatch.1.dylib\n 0x7fff89aae000 - 0x7fff89aaefff libOpenScriptingUtil.dylib (172.1) <0F1BA407-97D1-36F6-882D-A355EAAD5E00> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff89aaf000 - 0x7fff89ab3ffb libScreenReader.dylib (477.40.7) <F7305560-6CF0-3000-8301-72E04BEAA693> /usr/lib/libScreenReader.dylib\n 0x7fff89ab4000 - 0x7fff89ab5ffb libSystem.B.dylib (1238.60.2) <58358A17-4318-3AD9-B18E-CC36502B9127> /usr/lib/libSystem.B.dylib\n 0x7fff89b21000 - 0x7fff89b4cff3 libarchive.2.dylib (41.70.2) <907D1FB1-9A65-33F5-AFC8-0B6E5AE9D83A> /usr/lib/libarchive.2.dylib\n 0x7fff89b4d000 - 0x7fff89bc9fc7 libate.dylib (1.12.13) <D0767875-D02E-3377-84D8-5F174C27BEA9> /usr/lib/libate.dylib\n 0x7fff89bcd000 - 0x7fff89bcdff3 libauto.dylib (187) <34388D0B-C539-3C1B-9408-2BC152162E43> /usr/lib/libauto.dylib\n 0x7fff89bce000 - 0x7fff89bdeff3 libbsm.0.dylib (34) <20084796-B04D-3B35-A003-EA11459557A9> /usr/lib/libbsm.0.dylib\n 0x7fff89bdf000 - 0x7fff89bedff7 libbz2.1.0.dylib (38) <ADFA329A-DCE7-356D-8F09-A3168DFC6610> /usr/lib/libbz2.1.0.dylib\n 0x7fff89bee000 - 0x7fff89c44ff7 libc++.1.dylib (307.5) <0B43BB5D-E6EB-3464-8DE9-B41AC8ED9D1C> /usr/lib/libc++.1.dylib\n 0x7fff89c45000 - 0x7fff89c6eff7 libc++abi.dylib (307.4) <BC271AD3-831B-362A-9DA7-E8C51F285FE4> /usr/lib/libc++abi.dylib\n 0x7fff89c6f000 - 0x7fff89c7fffb libcmph.dylib (6) <2B5D405E-2D0B-3320-ABD6-622934C86ABE> /usr/lib/libcmph.dylib\n 0x7fff89c80000 - 0x7fff89c96fcf libcompression.dylib (39) <F2726F95-F54E-3B21-BCB5-F7151DEFDC2F> /usr/lib/libcompression.dylib\n 0x7fff89c97000 - 0x7fff89c97ff7 libcoretls.dylib (121.50.4) <64B1001E-10F6-3542-A3B2-C4B49F51817F> /usr/lib/libcoretls.dylib\n 0x7fff89c98000 - 0x7fff89c99ff3 libcoretls_cfhelpers.dylib (121.50.4) <1A10303E-5EB0-3C7C-9165-021FCDFD934D> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff89d53000 - 0x7fff89e37ff7 libcrypto.0.9.8.dylib (64.50.7) <B34BC0FA-18ED-37C5-9D46-393803CADEBB> /usr/lib/libcrypto.0.9.8.dylib\n 0x7fff89fd5000 - 0x7fff8a028ff7 libcups.2.dylib (450.4) <2DA65D4A-1428-3F74-869A-E16246DE88C7> /usr/lib/libcups.2.dylib\n 0x7fff8a0a5000 - 0x7fff8a0a5fff libenergytrace.dylib (15) <A1B040A2-7977-3097-9ADF-34FF181EB970> /usr/lib/libenergytrace.dylib\n 0x7fff8a0b5000 - 0x7fff8a0baff7 libheimdal-asn1.dylib (498.50.12) <1AC5AB99-2E62-3B9C-ADE4-AE65CFCDA471> /usr/lib/libheimdal-asn1.dylib\n 0x7fff8a0bb000 - 0x7fff8a1adff7 libiconv.2.dylib (50) <42125B35-81D7-3FC4-9475-A26DBE10884D> /usr/lib/libiconv.2.dylib\n 0x7fff8a1ae000 - 0x7fff8a3d3ffb libicucore.A.dylib (57168.0.1) <99D53A36-19F6-34F0-86AB-D8BD6C9BD3AD> /usr/lib/libicucore.A.dylib\n 0x7fff8a3d9000 - 0x7fff8a3dafff liblangid.dylib (126) <2085E7A7-9A34-3735-87F4-F174EF8EABF0> /usr/lib/liblangid.dylib\n 0x7fff8a3db000 - 0x7fff8a3f4ffb liblzma.5.dylib (10) <44BD0279-99DD-36B5-8A6E-C11432E2098D> /usr/lib/liblzma.5.dylib\n 0x7fff8a3f5000 - 0x7fff8a40bff7 libmarisa.dylib (5) <9030D214-5D0F-30CB-AC03-902C63909362> /usr/lib/libmarisa.dylib\n 0x7fff8a40c000 - 0x7fff8a6b4ff7 libmecabra.dylib (744.8) <D429FCC9-42A4-38B3-8784-44024BC859EF> /usr/lib/libmecabra.dylib\n 0x7fff8a6e7000 - 0x7fff8a761ff3 libnetwork.dylib (856.60.1) <191E99F5-4723-3180-8013-02AF2F9AE4B8> /usr/lib/libnetwork.dylib\n 0x7fff8a762000 - 0x7fff8ab34047 libobjc.A.dylib (709.1) <70614861-0340-32E2-85ED-FE65759CDFFA> /usr/lib/libobjc.A.dylib\n 0x7fff8ab37000 - 0x7fff8ab3bfff libpam.2.dylib (21.30.1) <71EB0D88-DE84-3C8D-A2C5-58AA282BC5BC> /usr/lib/libpam.2.dylib\n 0x7fff8ab3c000 - 0x7fff8ab6dfff libpcap.A.dylib (67.60.2) <B2D36AD8-D5C8-3875-AC81-4787A15E44C2> /usr/lib/libpcap.A.dylib\n 0x7fff8ab8a000 - 0x7fff8aba6ffb libresolv.9.dylib (64) <A244AE4C-00B0-396C-98FF-97FE4DB3DA30> /usr/lib/libresolv.9.dylib\n 0x7fff8aba7000 - 0x7fff8abe0fff libsandbox.1.dylib (592.70.2) <9017CBC7-DC59-3668-8E86-738D141AF11C> /usr/lib/libsandbox.1.dylib\n 0x7fff8abf6000 - 0x7fff8ad44ff7 libsqlite3.dylib (254.8) <1ECF7DF7-7A07-3B4B-A63B-F4EFF6BC7ACF> /usr/lib/libsqlite3.dylib\n 0x7fff8ae8d000 - 0x7fff8ae9aff7 libxar.1.dylib (417.1) <78B14DC5-5256-3820-8259-117C5046BB9F> /usr/lib/libxar.1.dylib\n 0x7fff8ae9b000 - 0x7fff8af8aff3 libxml2.2.dylib (30.24) <D84C6B99-6D4C-3651-8086-387D631CBA37> /usr/lib/libxml2.2.dylib\n 0x7fff8af8b000 - 0x7fff8afb4fff libxslt.1.dylib (15.9.3) <F57ED43F-7912-3C99-8500-AB0EEE9FA178> /usr/lib/libxslt.1.dylib\n 0x7fff8afb5000 - 0x7fff8afc6ff3 libz.1.dylib (67) <46E3FFA2-4328-327A-8D34-A03E20BFFB8E> /usr/lib/libz.1.dylib\n 0x7fff8afd5000 - 0x7fff8afd9ff7 libcache.dylib (79) <093A4DAB-8385-3D47-A350-E20CB7CCF7BF> /usr/lib/system/libcache.dylib\n 0x7fff8afda000 - 0x7fff8afe4fff libcommonCrypto.dylib (60092.50.5) <4C8A7FE1-C190-3015-A744-66F8220EAF6A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff8afe5000 - 0x7fff8afecfff libcompiler_rt.dylib (62) <55D47421-772A-32AB-B529-1A46C2F43B4D> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff8afed000 - 0x7fff8aff5fff libcopyfile.dylib (138) <819BEA3C-DF11-3E3D-A1A1-5A51C5BF1961> /usr/lib/system/libcopyfile.dylib\n 0x7fff8aff6000 - 0x7fff8b079fdb libcorecrypto.dylib (442.50.22) <E36CE660-855A-3166-8B9C-645C514B2C52> /usr/lib/system/libcorecrypto.dylib\n 0x7fff8b07a000 - 0x7fff8b0abfff libdispatch.dylib (703.50.38) <54B02414-5908-3EF0-B4D2-230B7FEB1CF7> /usr/lib/system/libdispatch.dylib\n 0x7fff8b0ac000 - 0x7fff8b0b1ffb libdyld.dylib (434) <4A0E66C1-4596-38E6-898E-BD2660478D3D> /usr/lib/system/libdyld.dylib\n 0x7fff8b0b2000 - 0x7fff8b0b2ffb libkeymgr.dylib (28) <7AA011A9-DC21-3488-BF73-3B5B14D1FDD6> /usr/lib/system/libkeymgr.dylib\n 0x7fff8b0b3000 - 0x7fff8b0bffff libkxld.dylib (3789.73.50) <E2CCB6DE-F92B-33CE-81A8-DDC42E62B62D> /usr/lib/system/libkxld.dylib\n 0x7fff8b0c0000 - 0x7fff8b0c0fff liblaunch.dylib (972.70.5) <1F770D9B-3892-3BBB-9471-68DDDDB0F69A> /usr/lib/system/liblaunch.dylib\n 0x7fff8b0c1000 - 0x7fff8b0c6ff3 libmacho.dylib (898) <17D5D855-F6C3-3B04-B680-E9BF02EF8AED> /usr/lib/system/libmacho.dylib\n 0x7fff8b0c7000 - 0x7fff8b0c9ff3 libquarantine.dylib (85.50.1) <12448CC2-378E-35F3-BE33-9DC395A5B970> /usr/lib/system/libquarantine.dylib\n 0x7fff8b0ca000 - 0x7fff8b0cbffb libremovefile.dylib (45) <38D4CB9C-10CD-30D3-8B7B-A515EC75FE85> /usr/lib/system/libremovefile.dylib\n 0x7fff8b0cc000 - 0x7fff8b0e4ff7 libsystem_asl.dylib (349.50.5) <096E4228-3B7C-30A6-8B13-EC909A64499A> /usr/lib/system/libsystem_asl.dylib\n 0x7fff8b0e5000 - 0x7fff8b0e5ff7 libsystem_blocks.dylib (67) <10DC5404-73AB-35B3-A277-A8AFECB476EB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff8b0e6000 - 0x7fff8b173fef libsystem_c.dylib (1158.50.2) <E5AE5244-7D0C-36AC-8BB6-C7AE7EA52A4B> /usr/lib/system/libsystem_c.dylib\n 0x7fff8b174000 - 0x7fff8b177ffb libsystem_configuration.dylib (888.60.3) <094DBBF4-276A-3A11-8AF3-72743CC338E6> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff8b178000 - 0x7fff8b17bfff libsystem_coreservices.dylib (41.4) <7D26DE79-B424-3450-85E1-F7FAB32714AB> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff8b17c000 - 0x7fff8b194fff libsystem_coretls.dylib (121.50.4) <EC6FCF07-DCFB-3A03-9CC9-6DD3709974C6> /usr/lib/system/libsystem_coretls.dylib\n 0x7fff8b195000 - 0x7fff8b19bfff libsystem_dnssd.dylib (765.50.11) <B87F96B8-2694-3DB3-9923-1B4E2245C8BF> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff8b19c000 - 0x7fff8b1c5ff7 libsystem_info.dylib (503.50.4) <611DB84C-BF70-3F92-8702-B9F28A900920> /usr/lib/system/libsystem_info.dylib\n 0x7fff8b1c6000 - 0x7fff8b1e8ff7 libsystem_kernel.dylib (3789.73.50) <932ACBB6-9962-3839-AEE3-D8AA6BF1DD02> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff8b1e9000 - 0x7fff8b230fe7 libsystem_m.dylib (3121.6) <86D499B5-BBDC-3D3B-8A4E-97AE8E6672A4> /usr/lib/system/libsystem_m.dylib\n 0x7fff8b231000 - 0x7fff8b24fff7 libsystem_malloc.dylib (116.50.9) <82647590-DAEF-3499-8BF3-F1E3048861FE> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff8b250000 - 0x7fff8b2a9ffb libsystem_network.dylib (856.60.1) <369D0221-56CA-3C3E-9EDE-94B41CAE77B7> /usr/lib/system/libsystem_network.dylib\n 0x7fff8b2aa000 - 0x7fff8b2b3ff3 libsystem_networkextension.dylib (563.60.2) <B021F2B3-8A75-3633-ABB0-FC012B8E9B0C> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff8b2b4000 - 0x7fff8b2bdff3 libsystem_notify.dylib (165.20.1) <B8160190-A069-3B3A-BDF6-2AA408221FAE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff8b2be000 - 0x7fff8b2c6fe7 libsystem_platform.dylib (126.50.8) <897462FD-B318-321B-A554-E61982630F7E> /usr/lib/system/libsystem_platform.dylib\n 0x7fff8b2c7000 - 0x7fff8b2d1ff7 libsystem_pthread.dylib (218.60.3) <B8FB5E20-3295-39E2-B5EB-B464D1D4B104> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff8b2d2000 - 0x7fff8b2d5ff7 libsystem_sandbox.dylib (592.70.2) <19320A42-2E3B-361B-BBDA-2F5F2E87B100> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff8b2d6000 - 0x7fff8b2d7ff3 libsystem_secinit.dylib (24.50.4) <F78B847B-3565-3E4B-98A6-F7AD40392E2D> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff8b2d8000 - 0x7fff8b2dfffb libsystem_symptoms.dylib (532.50.48) <1C822669-BF39-3639-A00B-B9170A63F342> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff8b2e0000 - 0x7fff8b2f3ff7 libsystem_trace.dylib (518.70.1) <AC63A7FE-50D9-3A30-96E6-F6B7FF16E465> /usr/lib/system/libsystem_trace.dylib\n 0x7fff8b2f4000 - 0x7fff8b2f9ffb libunwind.dylib (35.3) <3D50D8A8-C460-334D-A519-2DA841102C6B> /usr/lib/system/libunwind.dylib\n 0x7fff8b2fa000 - 0x7fff8b323ff7 libxpc.dylib (972.70.5) <255AA6A1-26AA-33F6-BC11-3DCE12A0BC0F> /usr/lib/system/libxpc.dylib\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: 981235\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=455.8M resident=0K(0%) swapped_out_or_unallocated=455.8M(100%)\nWritable regions: Total=347.2M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=347.2M(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 128K 2 \nActivity Tracing 256K 2 \nCG backing stores 440K 3 \nCG image 96K 8 \nCoreAnimation 36K 5 \nCoreUI image data 472K 6 \nCoreUI image file 184K 4 \nFoundation 4K 2 \nImage IO 76K 4 \nKernel Alloc Once 8K 2 \nMALLOC 277.3M 95 \nMALLOC guard page 48K 10 \nMALLOC_LARGE (reserved) 6144K 2 reserved VM address space (unallocated)\nMemory Tag 242 12K 2 \nMemory Tag 249 156K 2 \nOpenGL GLSL 256K 4 \nSTACK GUARD 56.1M 15 \nStack 14.6M 16 \nVM_ALLOCATE 31.3M 68 \nVM_ALLOCATE (reserved) 36K 2 reserved VM address space (unallocated)\n__DATA 87.0M 252 \n__GLSLBUILTINS 2588K 2 \n__IMAGE 528K 2 \n__LINKEDIT 156.1M 32 \n__TEXT 299.6M 250 \n__UNICODE 556K 2 \nmapped file 45.1M 11 \nshared memory 16.4M 13 \n=========== ======= ======= \nTOTAL 995.3M 790 \nTOTAL, minus reserved VM space 989.2M 790 \n\nModel: iMac14,2, BootROM IM142.0130.B00, 4 processors, Intel Core i5, 3,4 GHz, 16 GB, SMC 2.15f7\nGraphics: NVIDIA GeForce GTX 775M, NVIDIA GeForce GTX 775M, PCIe, 2048 MB\n```" ]

[ "Incorrect interaction glass with visibility of other objects\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.3\n\nIncorrect interaction glass with visibility of other objects. I have objects which disappear if I look at them at a certain angle through the glass.\n\nGif of the trouble \n\n\nTest file:\n[#91424.blend](T91424.blend)\n", "Rigid body doesn't work when collision is set to mesh, deform and deforming\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: Radeon RX Vega M GH Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.37.04 30.0.13037.4001\n\nBroken: version: 3.2.1\n\nThe rigid body simulation doesn't work with objects using collision with mesh, deform and deforming.\n\n* Make a plane, subdivided\n* Give it a wave modifier\n* Set up the rigid body type: dynamic, active, animated; collision: mesh, deform and deforming.\n* Use another object make it rigid body active\n* Run simulation\n* Sometimes works and when changing rigid body substeps per frame doesn't work at all (well sometimes works but when it does things jump out of control not like in Blender 2.79)\n\nIn Blender 2.79 works perfectly\n\n\n[Wave simulation 3.2.blend](Wave_simulation_3.2.blend)\n\n[Wave simulation 2.79.blend](Wave_simulation_2.79.blend)\n\nBlender 3.2\n\n\n\nBlender 2.79\n\n\n", "Weird Motion Blur with Simulation Nodes\nBroken: 3.6.2\n\nMotion Blur doesn't work properly with Geometry Nodes instances.\nAs shown in the rendered video, the motion blur seems to give weird results, the motion trails of the instanced particles from the Geometry Nodes (and Simulation Nodes) setup don't seem to follow their direction properly.\n\n<video src=\"attachment\" title=\"animation.mp4\" controls></video>\n\n[Test.blend](attachment)\n- Open file\n- Hit play to bake simulation until let's say frame 45\n- Render frame 45\n\n", "Generic Rigid Body Constraint Bug\nOperating system: Windows 10\nGraphics card: Radeon RX 470\n\nBroken: 2.83.0\nWorked: Unknown if it ever worked\n\nAngle limit not only doesn't work but causes weird neverending twitching back and forth\nUPDATE:\nTwitching happens for both cases when both rigid bodies are active and when one of them is passive.\n[M0DJ38oWQo.mp4](M0DJ38oWQo.mp4)\n\n1. Add 2 rigid bodies, 1 active, 1 passive animated\n2. Position them active on top, passive on the bottom\n3. Add an empty in between them, add a rigid body constraint to it, select the 2 rigid bodies in its settings, uncheck disable collisions.\n4. Change the joint type to Generic, limit location to 0-0 on each axis.\n5. Play. Now it works, once you select the passive RB and move it it should behave normal.\n6. Undo. Check angle limit on Z and choose some angle range (I had it set to -30 to 30).\n7. Play. Move the passive RB and watch it breaking.\n", "Avoid creating doubles in UV-Sphere primitive\nCurrently some new mesh operators are creating meshes with duplicate geometry, then removing it. This can cause problems - see: [D6001: Fix #70560: Large cones are created with double vertices (even though the radius is zero)](D6001).\n\n\nIt would be more elegant not to create duplicate geometry to begin with.\n\n- Committed fix for cone 5c8ccad652, while it still creates doubles, they are removed without relying on removing doubles.", "Z-fighting in wireframe moded\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.90.1\nAlso tested with the latest 2.92 alpha build. Same results.\n\nI experience Z-fighting in wireframe mode when there are overlapping faces.\nWireframe mode should only render edges. Z-fighting indicates that faces are rendered too, but it only happens when they partially overlap.\n\nDuplicate the default cube and move it slightly in one axis, so that faces of the two cubes partially overlap. Switch to wireframe mode and you will see faces flickering where they overlap. You won't see it if the two cubes fully overlap by staying roughly in the same spot.\n\n[wireframe glitch.blend](wireframe_glitch.blend)\n", "Regression: unhide now is global even in local mode\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.79b\n\nAlt+H in local view unhides objects all over the scene instead only local context, as it work in 2.79\nPlease fix. It is very handy feature and we have lost it.\n\n**Step to Reproduce**\n- Open .blend file\n- Select a sphere and Hide: {key H}\n- Select all three cubes and enter in Local view: {key /}\n- Hide cubes\n- Now unhide cubes in Local view: {key Alt H}\n- sphere is also visible (Either check outliner or Switch back from Local view)\n\nTest File:\n[#92527.blend](T92527.blend)\n[2021-10-27_12-23-23.mp4](2021-10-27_12-23-23.mp4)", "OpenSubdiv with \"On Cage\" shows vertices of edges that don't make any faces even when everything is hidden\nBroken: version: 2.90.0 Alpha\n\n**Description**\nWhen using the sub-surf modifier with cage enabled, if a mesh has edges that don't make any faces, then the vertices of those edges will still be visible when everything is hidden.\n\n[Open subdiv bug.blend](Open_subdiv_bug.blend)\nOpen the file and just press 'H'\n\n\n", "Usability issues with old group operators\nBroken: 2.79, 2.8x\n\n\nWhen using linked objects, all the Group commands [Remove From Group / Remove From All Groups / Add Selected To Active Group / Remove Selected From Active Group] except [Create New Group (Ctrl G)], do nothing\n\n\nIn my particular usage, I link a scene from one file into my main scene, afterwards I create a [New scene with Link Objects] from the Linked scene. \n\n [GroupsFail.blend](GroupsFail.blend)\n [GroupsFail-MainScene.blend](GroupsFail-MainScene.blend)\n\nI can Create Groups by selected objects, and I can remove the group from the object in the Object Properties tab but the only way to remove multiple groups is through python script or deleting the group itself.\n\nSince this report is used to more generally handle issues with the old group operators and other reports have already been merged here, will also list these:\n- Ctrl G is placing new collections inside \"Orphan Data\"", "Bent concave 2D curve triangulation problem w/ modifiers applied\nBroken: 2.80\n\n[BUG.blend](BUG.blend)\n\n(I think the problem is triangulation)\nTriangulation sometimes has problems with concave shapes, and I believe this is caused by triangulation (without overlaps) being much more difficult in 3d than 2d. But the problem shouldn't really exist (at least in my case) because the triangulation would work fine using 2D triangulation by projecting the points to 2d along the average normal of the face (it bends less than 90 degrees, so 2D triangulation would be perfect).\n\nOpen the project, the shape is completely wrong on the flat faces when using the curve modifier. It's supposed to be a concave crescent shape, instead of the convex hull sorta shape it has now.", "environment pass is occluded by geometry making it unusuable with a shadowcatcher\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 1)\nWorked: unsure if ever\n\nenvironment pass is occluded by geometry making it unusuable with a shadowcatcher\n\n\nopen attached .blend, go to compositing workspace, hit f12, when finished use the split viewer factor to slide between the image and the environment pass. \n\nPerhaps the transparency section needs an additional 'shadow catchers are transparent'.......although that wouldn't make much sense as shadow catchers should always be transparent. Regardless, the environment pass definitely shouldn't contain any geometry information. Is there ever a scenario where you'd want the environment AOV to be jet black where the 3d objects are located?\n\n[environment alpha bug.blend](environment_alpha_bug.blend)", "2.8 - Particles in multi-level nested collections not visible\nOperating system: win10x64\nGraphics card: AMD Radeon Pro WX 7100\n\nBroken: 2.80, 54ffc4e19dc4, 2019-02-25\n\n\n\nIn nested collections, objects with particles work only in two levels of nesting. Particles in further levels of nesting seem to ignore collections instancing.\n\n\nRelated file: [particle-instances.blend](particle-instances.blend)\n\n- create cones with hair particles on a collection called **branches** \n- create a cube on a collection called **tree** \n- add a collection instance of branches within the collection called **tree** (1st level of nesting of branches) \n- create a new collection called **trees** and add a few collection instances of tree. \n- for all objects in trees, the particles are visible ( 2nd level of nesting) \n- create a new collection called **instances** and add a collection instance of trees. Here, the particle settings are not replicated. (3rd level of nesting) .\n- For the sake of testing this further, create a new collection called **instances2** and add a collection instance of instances . Also, here the particle settings are not replicated. (4th level of nesting) \n\n\nIn collection Instances, only the initial particles are visible and their location seems to be reset based on the initial location\n\n\n", "mask visibility in sculpt mode using shape keys or generative modifiers\nOperating system: Windows 10\nGraphics card: nvidia 1060 Ti\n\n2.8 RC2\n\nIf you have a mesh with a mask and create a shape key, the mask will be no longer visible, still active but not visible.\n\n\n- Add UV Sphere\n- Sculpt mode\n- Paint a mask\n- Create shape keys\n\n\nOr from the default startup:\n- in sculptmode, `Mask` > `Invert Mask` (default cube should turn dark)\n- strokes dont have an effect now (this is expected)\n- add **any** generative modifier to the default cube (e.g. triangulate)\n- back in objectmode, save the file\n- reload the file\n- enter sculptmode\n- no mask is visible\n- strokes dont have an effect now (this is confusing since you are not aware masks prevent an effect since you dont even see the masks)\n\n(note we have the option `Use Deform Only` in sculptmode which might be exactly for that purpose, still not being able to use masks with generative modifiers should be more clear)", "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", "Booleans are completely breaking on my object\nOperating system: macOS Monterey (ARM64)\nGraphics card: Apple Silicon `M1`\n\nBroken: 3.2.0 Alpha & others\nWorked: *2.83.X*? (reported in comment)\n\nBooleans can often be very touchy and may require positioning them just right for them to do operations properly. It seems that it really depends on where the vertices line up. I've been cutting window slots out of ridged galvanized steel plates using boolean cubes and it's worked for every other object. However, this one particular piece in my scene has been causing endless trouble for me despite being the exact same procedure. Seems as though I need to put my boolean objects in the EXACT RIGHT place for them to work right. I found that adding a ludicrous number of subdivisions w/ the subsurface modifier can somewhat help, but it greatly depends on whether or not I position my cubes in the right spot. It is preventing me from placing my windows where they need to go on my scale accurate historic building recreation. I don't know why this object is being so temperamental but it is blocking me from making any progress on this side of the building and I'm afraid I'll keep running into the problem later on.\n\nI may post additional demo files that showcase more boolean issues as I frequently run into problems of faces not being filled properly, crappy vertex extrusions, objects being weirdly combined instead of differenced, and many more annoyances. I hope booleans can get a lot more love from the developers so that they work as intended.\n\n\n\nI'm not entirely sure how to reproduce an issue like this. It mostly plagues more detailed models but can happen anywhere and depends on object positions, alignment, topology, and so on. Attached is a problematic file.\n\n**Attached file information**\n[F12870489](brokenBooleans.blend.zip) There are several issues present. For one thing, the boolean modifier is struggling to cut a simple rectangle out of a plane. It is adding geometry to certain parts, cutting out geometry that shouldn't be cut out, and is not accurate at all. I've noticed that using the \"fast\" option usually yields better results than using the \"exact\" option. However, in the case of this object, it actually breaks it EVEN MORE! Try selecting the \"cutoutGalvanizedSteel\" (planar object) and setting the booleans to \"fast\" to see a new problem emerge. Adding a solidify modifier to the very top of the stack will fix the issue. However, booleans should work on planes, too.\n\n[F12871474](BorkedBooleans.blend.zip) Many different problems. Boolean objects are displayed as wireframes. If you see a boolean as having geometry, it's because it is being added by the Boolean modifier. The boolean modifier likes to add the boolean's geometry to the source mesh sometimes, even when it is set to difference or intersection. In issue 2, there is a mesh problem in the boolean. If you enter edit mode, you can see that the problematic vertices are selected. They crash the boolean operation altogether. Merging these vertices will solve the issue, but for more complex boolean objects, this may not always be an option.\n\n[brokenBooleans.blend.zip](brokenBooleans.blend.zip)\n[BorkedBooleans.blend.zip](BorkedBooleans.blend.zip)" ]

[ "Can't intersect rigid bodies of distinct collision group at start\nBlender 2.69 \n\nWhen two rigid bodies has distinct collision group they are supposed to not collide. It works ok except when they starts intersected , then the bodies are put separated, it is an undesired behavior\n\nit looks like when the rigid bodies are intersected at start, they come to be in the same collision group i dont know why\n\n[bug.blend](bug.blend)", "BGE Collision Mask Issue\nWin 7\nNo graphic card\nOperating system and graphics card\n\nBlender version 2.70\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\nI have some objects in group 2 but are only masked to collide with group 1. If the game starts without any of the objects intersecting, it works fine: they float straight through one another. But, if the game starts with them intersecting one another, they pop away like normal, before ignoring collisions once more.\n\n- Add a plane(ground),two spheres and two cubes.\n- Give them rigid body in game settings.\n- Give them collision bounds sphere for spheres and box for cubes.\n- Keep plane in collision group 1, Spheres in Collsion group 2 and Cubes in collision group 3\n- Enable Plane collision with all collision groups.\n- Enable Sphere collision with Plane(ground) only.\n- Enable Cube collision with Plane(ground) only.\n\nPosition of plane is as ground. above it in air position two sets of objects.\nIn set 1 a cube and a sphere are colliding/intersecting.\nIn set 2 a cube and a sphere above it are not colliding/intersecting.\n\nNow if you Press P and start Game Engine. Spheres and cubes in both sets should not collide (they only collide with plane.)\nBut due to some bug Set 1 objects push each other away and even after that remain collidable. Set 2 behaves Normally.\n\nAttaching Blend Thank You \nBased on a (as simple as possible) attached .blend file with minimum amount of steps\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.", "LibOverride - Update - Fix handling of temp ID\nLiboverride 'update' process (the part applying overrides again over a copy of the linked data, `BKE_lib_override_library_main_update` & co) needs some specific control over its usage of `BKE_id_copy_ex` to create the temp copy of the linked ID: It needs to prevent any potential modification of any other ID in Main.\n\nThis happens e.g. with regular copy of Collections, since the `parents` lists of their children need to be updated with a new pointer to the new copy. There may be a few other similar cases, this needs to be investigated.\n\nThis default behavior prevents from safely using `BKE_id_free_ex` on that same temp ID later on, even if the temp ID is not explicitly linked to any other ID.\n\nWhether this change requires a new specific tag, or could be part of one of the 'no main' cases, remains to be investigated as well. \n\n--------------------\n\n## Original Report\n\n\nOperating system: Linux-5.15.0-10056-tuxedo-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.60.11\n\nBroken: version: 3.5.0 Alpha, branch: master, commit date: Unknown, hash: f06a1368\nWorked: -\n\nBlender crashes when appending a collection (twice) from a file where this collection has been linked and overridden.\n\n\n*Note: Using a debug build with ASAN makes this reliable to reproduce.*\n\n 1. Open file `fileB.blend`.\n 2. Go to `File`>`Append`. Browse into `fileA.blend`>`Collections`. Untick the `Localize All` option. Choose `Asset`.\n 3. Blender crashes.\n\n[report_crash_link.zip](report_crash_link.zip)\n\n**ASAN report**\n```\n=================================================================\n==84954==ERROR: AddressSanitizer: heap-use-after-free on address 0x613000267ef2 at pc 0x000002b6fe58 bp 0x7ffc27cb7e40 sp 0x7ffc27cb7e30\nREAD of size 2 at 0x613000267ef2 thread T0\n - 0 0x2b6fe57 in collection_foreach_id /.../blender/source/blender/blenkernel/intern/collection.c:164\n - 1 0xd2a149 in library_foreach_ID_link /.../blender/source/blender/blenkernel/intern/lib_query.c:334\n - 2 0xd2a317 in BKE_library_foreach_ID_link /.../blender/source/blender/blenkernel/intern/lib_query.c:353\n - 3 0xcce9b3 in BKE_lib_id_clear_library_data /.../blender/source/blender/blenkernel/intern/lib_id.c:224\n - 4 0xcd1d22 in BKE_lib_id_make_local_generic /.../blender/source/blender/blenkernel/intern/lib_id.c:501\n - 5 0xcd2cef in BKE_lib_id_make_local /.../blender/source/blender/blenkernel/intern/lib_id.c:561\n - 6 0xbe3fa23 in BKE_blendfile_append /.../blender/source/blender/blenkernel/intern/blendfile_link_append.c:1111\n - 7 0x3a49cf1 in wm_link_append_exec /.../blender/source/blender/windowmanager/intern/wm_files_link.c:356\n - 8 0x39fe3ed in wm_handler_fileselect_do /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:2724\n - 9 0x39ffd56 in wm_handler_fileselect_call /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:2821\n - 10 0x3a04962 in wm_handlers_do_intern /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3315\n - 11 0x3a04e0b in wm_handlers_do /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3369\n - 12 0x3a0e0ed in wm_event_do_handlers /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3963\n - 13 0x39c81bd in WM_main /.../blender/source/blender/windowmanager/intern/wm.c:640\n - 14 0x801b57 in main /.../blender/source/creator/creator.c:585\n - 15 0x7fdac84b0d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58\n - 16 0x7fdac84b0e3f in __libc_start_main_impl ../csu/libc-start.c:392\n - 17 0x800e34 in _start (/.../build_linux_debug/bin/blender+0x800e34)\n\n0x613000267ef2 is located 114 bytes inside of 344-byte region [0x613000267e80,0x613000267fd8)\nfreed by thread T0 here:\n - 0 0x7fdac8bf0517 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:127\n - 1 0x1dd70304 in MEM_lockfree_freeN /.../blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:117\n - 2 0xce415b in BKE_id_free_ex /.../blender/source/blender/blenkernel/intern/lib_id_delete.c:168\n - 3 0xd254b5 in BKE_lib_override_library_update /.../blender/source/blender/blenkernel/intern/lib_override.cc:3793\n - 4 0xd26297 in BKE_lib_override_library_main_update /.../blender/source/blender/blenkernel/intern/lib_override.cc:3840\n - 5 0x3b96f2b in library_link_end /.../blender/source/blender/blenloader/intern/readfile.cc:4526\n - 6 0x3b972ab in BLO_library_link_end /.../blender/source/blender/blenloader/intern/readfile.cc:4545\n - 7 0xbe42109 in BKE_blendfile_link /.../blender/source/blender/blenkernel/intern/blendfile_link_append.c:1283\n - 8 0x3a49c39 in wm_link_append_exec /.../blender/source/blender/windowmanager/intern/wm_files_link.c:346\n - 9 0x39fe3ed in wm_handler_fileselect_do /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:2724\n - 10 0x39ffd56 in wm_handler_fileselect_call /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:2821\n - 11 0x3a04962 in wm_handlers_do_intern /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3315\n - 12 0x3a04e0b in wm_handlers_do /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3369\n - 13 0x3a0e0ed in wm_event_do_handlers /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3963\n - 14 0x39c81bd in WM_main /.../blender/source/blender/windowmanager/intern/wm.c:640\n - 15 0x801b57 in main /.../blender/source/creator/creator.c:585\n #16 0x7fdac84b0d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58\n\npreviously allocated by thread T0 here:\n - 0 0x7fdac8bf0a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154\n - 1 0x1dd70a49 in MEM_lockfree_callocN /.../blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:223\n - 2 0xcd81aa in BKE_libblock_alloc_notest /.../blender/source/blender/blenkernel/intern/lib_id.c:1101\n - 3 0xcd8341 in BKE_libblock_alloc /.../blender/source/blender/blenkernel/intern/lib_id.c:1113\n - 4 0xcd9ac6 in BKE_libblock_copy_ex /.../blender/source/blender/blenkernel/intern/lib_id.c:1274\n - 5 0xcd388a in BKE_id_copy_ex /.../blender/source/blender/blenkernel/intern/lib_id.c:637\n - 6 0xd241f3 in BKE_lib_override_library_update /.../blender/source/blender/blenkernel/intern/lib_override.cc:3725\n - 7 0xd26297 in BKE_lib_override_library_main_update /.../blender/source/blender/blenkernel/intern/lib_override.cc:3840\n - 8 0x3b96f2b in library_link_end /.../blender/source/blender/blenloader/intern/readfile.cc:4526\n - 9 0x3b972ab in BLO_library_link_end /.../blender/source/blender/blenloader/intern/readfile.cc:4545\n - 10 0xbe42109 in BKE_blendfile_link /.../blender/source/blender/blenkernel/intern/blendfile_link_append.c:1283\n - 11 0x3a49c39 in wm_link_append_exec /.../blender/source/blender/windowmanager/intern/wm_files_link.c:346\n - 12 0x39fe3ed in wm_handler_fileselect_do /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:2724\n - 13 0x39ffd56 in wm_handler_fileselect_call /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:2821\n - 14 0x3a04962 in wm_handlers_do_intern /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3315\n - 15 0x3a04e0b in wm_handlers_do /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3369\n - 16 0x3a0e0ed in wm_event_do_handlers /.../blender/source/blender/windowmanager/intern/wm_event_system.cc:3963\n - 17 0x39c81bd in WM_main /.../blender/source/blender/windowmanager/intern/wm.c:640\n - 18 0x801b57 in main /.../blender/source/creator/creator.c:585\n - 19 0x7fdac84b0d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58\n\nSUMMARY: AddressSanitizer: heap-use-after-free /.../blender/source/blender/blenkernel/intern/collection.c:164 in collection_foreach_id\nShadow bytes around the buggy address:\n 0x0c2680044f80: 00 00 00 00 00 00 00 00 00 00 00 fa fa fa fa fa\n 0x0c2680044f90: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00\n 0x0c2680044fa0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 0x0c2680044fb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 0x0c2680044fc0: 00 00 00 fa fa fa fa fa fa fa fa fa fa fa fa fa\n=>0x0c2680044fd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd[fd]fd\n 0x0c2680044fe0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2680044ff0: fd fd fd fd fd fd fd fd fd fd fd fa fa fa fa fa\n 0x0c2680045000: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd\n 0x0c2680045010: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2680045020: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n Addressable: 00\n Partially addressable: 01 02 03 04 05 06 07 \n Heap left redzone: fa\n Freed heap region: fd\n Stack left redzone: f1\n Stack mid redzone: f2\n Stack right redzone: f3\n Stack after return: f5\n Stack use after scope: f8\n Global redzone: f9\n Global init order: f6\n Poisoned by user: f7\n Container overflow: fc\n Array cookie: ac\n Intra object redzone: bb\n ASan internal: fe\n Left alloca redzone: ca\n Right alloca redzone: cb\n Shadow gap: cc\n==84954==ABORTING\n```\n", "Library Overrides of the Same Linked Armature Cannot be Posed Simultaneously\nOperating system: Windows\nGraphics card: RTX 3070\n\nBroken: 3.3.1\nWorked: NA\n\n**Short Description**\nWhen linking a rig and making it into a library override twice in one scene, the rigs function properly as separate rigs but both linked from the same file. However, if you try to go into pose mode for both at the same time and pose the rigs, you cannot pose them separately. This is a pretty specific issue but if you had two identical rigs and wanted to animate them interacting in some way, it would become extremely bothersome.\n\n**Steps to Reproduce**\n- Open `example.blend`\n- Select both armatures\n- Switch to pose mode\n- Select any bone of any armature (this will also select same bone of another armature)\n[bug.zip](bug.zip)\n", "For ID blocks, move + and x buttons into popover\nWith our ID blocks in the top right of the window, the little + and x icons make the Blender UI overly busy and complex. There's also the problem that, at least on Windows and Linux, the close button is in the top right corner of the display, creating this clumsy configuration of two X's. \n\n{[F5673488](Screenshot_2018-11-22_at_01.50.52.png), size=full}\n\nWe could change these ID blocks to work as popovers instead, creating a much simpler top level interface. When opened, we can display the controls to add, remove or rename items inside the popover, similar to what we already do for the presets:\n\n\n\nThis would result in a cleaner top level UI, and avoid the double X on some OS's:\n\n{[F6622971](Screenshot_2019-02-16_at_01.19.50.png), size=full}", "Add Support of PointCaches to Library Overrides\nSupport baking simulations into PointCaches for library overrides.\n\n**Milestone 1 - Minimal Viable Product - 2.92**\n- [x] Support baking **existing** cache slots on disk (59910f7217, 50ccf346f0, 13bcb000fa, b073f58a8e).\n\n**Milestone 2 - Support memory cache - ???**\n- [ ] Support baking **existing** cache slots in memory *(this requires some specific handling during application of overrides step)*.\n\n**Milestone 3 - Potential Extensions - ???**\n*Those will require #82160 (LibOverrides - Refactor how diffing of RNA collections is handled, and extend diffing possibilities.) to be tackled first.*\n- [ ] Support **adding** new cache slots to a simulation.\n\n\n--------------\n\n*Original Report*\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.09\n\nBroken: version: 2.92.0 Alpha\n\nCloth sim bakes work great on library overrides until you save and reload. Then the bake is lost.\n\n[Cloth.blend](Cloth.blend)\n[Library Override.blend](Library_Override.blend)\nDownload both files\nOpen \"Library Override.blend\"\nPress Bake\nSave\nReload\n\n", "Warnings, Restrictions, & Centralized Administration\nWith more organizations adopting Blender there is increasing need to simplify the deployment, maintenance, and administration of the program in large installations. This plan is meant to be a number of incremental steps that, once approved, I could implement myself. I have about 10 years of prior experience as a Domain Administrator on a network of approximately 600 users and 1000 computers in a Windows domain, and am familiar with the pitfalls and best practices.\n\n**Improved Warnings**\n\nThis doesn't seem related, but is. I would like us to implement something like [D10955: UI: Improved Operator Confirmations](D10955), which allow us to make warning dialogs much more easily than now that are also more informative, more customizable, and more differentiable. This way we can define many more than we have now to cover almost any situation where some users might want warnings, like when overwriting existing files or when files differ in version. We can define more because we'd also add the ability for users to easily enable/disable them.\n\n**Move Warning Configurations from Keymap to Settings**\n\nRight now the configuration of warnings is quite obscure, buried in the keymaps as an attribute of the entry. Most users will not be able to change the current warnings. I'd like to make a \"Warnings\" section in Settings with checkboxes to allow quick enabling and disabling of warnings.\n\n**Expose Factory Settings**\n\nRight now the default startup file and the factory preferences are only stored inside the executable. I'd like to optionally expose those for customization. Perhaps add a command-line argument to the executable that extracts copies of the embedded \"default.blend\" and \"prefs.blend\" to the install folder. These would be used instead, if present, in the same way that you can now override the splash image with a custom \"splash.png\".\n\nIn a large deployment you would put the blender installation folder in a shared read-only location that everyone would launch. That way you only have to install it once, not on every workstation. With this change you could, for example, change the fonts directory to be a shared network location. Change that in this one place and it becomes the default for everyone.\n\n**Add Restriction Settings**\n\nLike the \"Warnings\" section in Settings, I'd like to add \"Restrictions\". So checkboxes that, once enabled, restrict the user from doing some operations. For example to not allow the installation of addons. In a single-user installation this would not be used. But imagine an administrator setting these, along with warnings, and placing a \"prefs.blend\" file in the shared read-only network location of the Blender installation. It now means everyone on the network has the same defaults, warnings, and restrictions.\n\n**Project Settings**\n\nAs another layer of granularity, allow putting these shared defaults and preference files within the folder path of blend files. So while loading any \"blend\" file we also look in its folder and parent folders for defaults and prefs. This way you can have per-project settings.\n\n**Platform Enhancements**\n\nDuring startup we are loading settings for settings, warnings, and restrictions. Once this is done we could also call platform-specific routines if they exist, like checking settings in the Windows Registry for example. This is all that is required to support Group Policy, so an Administrator can set a path for all user, allow some groups to add addons, and only leaders to change restrictions, etc.\n\n", "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled", "Brush thumbnail redesign\nThis task is about revamping the current set of thumbnail images that are used across various modes and object types.\nThis is aimed to be done for the release of further brush assets in upcoming releases.\n\n### Current Issues\n\nThe issues with the current thumbnails are:\n- Many brush types are reusing/duplicating old thumbnails\n- They lack a coherent visual identity\n- Some modes are just duplicating the tool icons\n- Some thumbnails were lost in the transition to Blender 2.8\n\nHere is an overview of most current brush thumbnails:\n\n\n### Proposal\n\nThere are various aspects that can improve and unify the current use of brush thumbnails.\n\n##### Brush Type Icons\n\nA common use of online brush pack is to indicate the type of a brush via icons.\nThis can\n- help the user identify how a brush works\n- help the brush author categorize the brush assets\n\n\n\nThe inital idea was to tag brushes and have icons autoamtically added and dynamically scale with the asset thumbnail.\n\nBut for free customizability and unqiue visuals for each brush, these are instead part of the image.\n\n##### Accessible Style\n\nThere are key aspects for the new thumbnails. They must be:\n- Easy to reproduce by anyone (Simple Matcap & grease pencil elements)\n- Not set in a strict camera angle and shape\n- Focused on the recognizable effects of the brush\n- Additional elements are only added to communicate hidden informations (Categories and non-obvious brush behavior)\n\nThis will reduce the friction when making your own brushes. The ideal end result is that a casual brush user can screenshot their current work for a custom brush, and their brush will immediately fit in.\n\nThis is the current set of thumbnails:\n\n", "Design: Animation Editors UI Redesign\n**Problem**\nSeveral proposals have been made to improve the usability of the Animation Editors' (Graph Editor, Nonlinear Animation, & Dope Sheet) Headers and Menus:\n\n - [Redesign Graph editor Header and Menus to 2.80 Blender UI standards ](T89069)\n - [Design: More frame snapping options ](T91973)\n\nThe main issues outlined by these proposals are:\n - “View” Menu cluttered with Overlay checkboxes rather than Overlay popover as in 3D View\n - 2D Cursor, Frame Snapping, & Proportional Editing button right-aligned location does not match other Editors. Frame Snapping full-text Enum is too wide and inconsistent with other icon-only Popovers\n - Frame Snapping menu only allows for one snapping option as opposed to multiple-option snapping in 3D View\n - Graph Editor “View” Panel has one utility/poor usage\n - There is a need for a separate a Timeline Editor with Graph Editor, NLA, & Dope Sheet (e.g. changing Playback options, Keying Set) however the Timeline has many redundant options to Dope Sheet and is only needed for its Header.\n - Full-text \"Keying\" dropdown is wide, inconsistent with icon-only popovers, and separate from Auto-keying popover\n # Full-text \"Playback\" dropdown is wide, inconsistent with icon-only popovers, and separate from Playback controls\n\nThis design task addresses the issues brought up in these proposals and breaks them into subtasks.\n\n**Proposed Solutions**\n\n - Move Markers, Curve Extrapolation, Only Selected Curves Keyframes, Show Handles, Only Selected Keyframes Handles and 2D Cursor from View to a new Overlays Menu\n - Center Pivot, Snapping and Proportional Editing Header buttons. Change Snapping to icon-only popover.\n - Create UI allowing for implementation of multi-snapping options\n - Move Normalize Button from Graph Editor Header to View Panel. Rename \"View\" Panel to \"Graph\".\n - Add Playback & Frame Range Controls to Timeline Header\n - Add Keying Set Controls to icon only popover near Playback Controls\n # Add Playback options to popover by Playback Controls\n\n\n\n**Stretch Goals**\n - Add fixed height mini-timeline element to Playback & Range footer\n\n**Implementation Patches**\n\n\n - [Playback, Keying Set, and Frame Range controls update](D15626)\n - [Center Pivot, Snap, and Proportional Editing in Animation Editor Headers ](D15631)\n\n", "Solve the reversed-dependency logic in Object parenting.\nCurrent relationship between an object and its child at data-block level is reversed compared to the user-level one: the child points to its parent, which means that at ID management level the child is the 'owner' of its parent.\n\nThis is fully reversed compared to (expected) user understanding, where the child should be a dependency of its parent. This is illustrated e.g. in the Outliner tree view, where the child is shown as part of its parent hierarchy.\n\nThis reversed order of dependency between the user-level and data-level representations has always been a source of issues (e.g. complex weird code in Outliner tree building code, weird behavior in ID linking, e.g. when linking a parent object, it would not automatically link its children, and more recently more complex code in liboverride hierarchies handling).\n\nThe proposal to address this issue is to add a list of children objects to the parent one. Most likely implemented in a similar way as with e.g. collections children (i.e. a listbase of wrapper struct around object pointers). These new relationships would be come the 'main' ones between parents and children.\n\nThe current 'parent' pointer would be kept, but would become a 'loopback' pointer from ID management perspective (similar e.g. to the 'from' pointer of embedded IDs and shapekeys, or the 'parent' pointers of a collection).\n\nThat way, only the code setting a parent needs to be updated (and some versioning to initialize the list of children of course), and there should be no forward or backward compatibility breakage at all, since the existing parent pointer remain in use and keep the same meaning.\n\nThe only unknown consequences may come from moving that 'parent' pointer into the 'loopback' category in the `lib_query` foreach_id processing. It will certainly fix issues (or make existing code simpler by removing needs for special case handling), but it may also cause unexpected changes.\n\n", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "BKE_id_copy: Handle properly case when copying IDs into non-local destination (aka copied ID will belong to a library)\nThis is not used/needed in basic common situations, since duplicated ID from 'user PoV' should always become local data.\n\nHowever, internal ID handling can require duplicating linked data that should remain linked. E.g. depsgraph CoW evaluated IDs should keep their same library as their source ID. LibOverride code also needs to keep copied IDs in their original (or in case of recursive resync, into another) library.\n\nCurrent handling of these cases is fairly fragile and hacky. Think the best way to move forward would be to introduce a 'destination library' parameter in the lower-level part of the API (`BKE_id_copy_ex`). That BKE code can then handle things like making IDs local or not, updating accordingly the status (direct vs. indirect linked etc.) of the other IDs they use, assert that a local ID is never duplicated into a linked one, and so on.\n\n", "Collection usability\n- [ ] Viewport UI\n- [ ] Shortcuts to toggle visibility?\n[ ] . . .\n\nNeed a clear design on what to do.", "Some icons cannot be overriden from python (e.g. 'Constraint.mute', 'use_fake_user')\nBroken: version: 3.3.0 Alpha\nWorked: Looks like this was once working in 2.80 (but has stopped working in 2.81)\n\nSome boolean properties apply an offset to their icon depending on the state of the boolean. This offset is applied even when an icon override is used, like so: `UILayout.prop(icon=whatever)`.\n\n**Workaround**\n```python\ndef get_icon_value(icon_name: str) -> int:\n icon_items = bpy.types.UILayout.bl_rna.functions[\"prop\"].parameters[\"icon\"].enum_items.items()\n icon_dict = {tup[1].identifier : tup[1].value for tup in icon_items}\n\n return icon_dict[icon_name]\n\ndef draw_with_icon_fix(layout, prop_owner, prop_name, icon: str, offset=1, invert_checkbox=False, **kwargs):\n \"\"\"Drawing some booleans in the UI with a custom icon can be \n annoying because Blender might offset the icon based on the boolean state.\n You can use this function to counter that offset. To find the offset, you have to \n trial and error, it's either 1 or -1. (Or 0 but then you don't need this)\n \"\"\"\n\n bool_value = getattr(prop_owner, prop_name)\n offset = offset * int(bool_value)\n if invert_checkbox:\n offset = 1 - offset\n icon_value = get_icon_value(icon) + offset\n layout.prop(prop_owner, prop_name, icon_value=icon_value, invert_checkbox=invert_checkbox, **kwargs)\n```\n\n- File with script within: [icon_madness.blend](icon_madness.blend)\n- Script should self-execute, look for a \"FixMe\" panel in the sidebar.\n\n\nSo this file works in 2.80 and is broken in 2.81:\n[icon_madness_2.blend](icon_madness_2.blend)", "Library Overrides: Making an override for \"Selected & Content\" does not create overrides for content\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nLibrary Overrides: Making an override for \"Selected & Content\" does not create overrides for content\n\n- open `main.blend`\n- with the linked Cube selected, do Outliner context menu > `Library Override` > `Make` > `Selected & Content`\n- override for object is created, however override for mesh is not\n\nNOTE: if you do it a second time, it works as expected.\n\nfor a comparsion:\n- open `main.blend`\n- with the linked Cube selected, do Outliner context menu > `Library Override` > `Make` > `Content`\n- override for mesh is properly created (so Outliner should know what \"Content\" is here)\n\n" ]

[ "Library overrides\n**Status:** Achieved 2021 targets have been 'archived' at the end of this task, which is now updated for [2022 targets]().\n\n---\n\n**Team**\n\n**Commissioner:** @eyecandy @Hjalti @Rikstopher \n**Project leader:** @mont29\n**Project members:** @JulianEisel @Jeroen-Bakker \n\n### 2022 Targets\n\n**Milestone 1 - Resync Performances**\n- [x] #94059 (Library Override Resync Performance).\n - [x] #95283 (LibOverride Stronger Hierarchy)\n - [x] #94185 (Outliner ID remapping performance), #95279 (Remap multiple items in referenced data)\n - [x] #95682 (Library Override partial Resync)\n\n**Milestone 2 - Improve Usability**\n- [ ] #95708 (Library Override - Usability).\n - [ ] #95707 (Library Override - System override IDs)\n - [ ] #95802 (Library Override - Outliner UI/UX)\n - [ ] #95816 (Library Override - 'Cherry-Picked' Properties)\n\n\n**Milestone 3 - Dynamic Overrides**\n- [ ] #54792 (Dynamic Overrides - View layer overrides with override sets) *(old, to be revised/updated and fleshed out)*\n\n**Not A Milestone - Library Overrides for Material**\n- [ ] Solve issues related to the weird way materials are linked to object or obdata.\n- [ ] Support properly nodegroups (i.e. embedded data-blocks, some preliminary work has already been done but needs to be finalized and validated). #82404 (Library Overrides: Shader drivers stop working after save and reload)\n\n**Not A Milestone - Future Ideas**\n*Those are ideas existing from the beginning of the project, and which have a partial implementation in core code, but need more UI/UX design and development.*\n- [ ] #72629 (Library Override: Support editing of animation data in overriden data-blocks.).\n- [ ] #82503 (Add Support of PointCaches to Library Overrides).\n- [ ] Allow addition of CustomData layers to geometry IDs (new UV maps, shape keys, vertex groups...). *This will require a lot of preliminary work.*\n- [ ] Advanced types of override operations (multiplicative factor for 'factor' porperties like scale, 'bit wise' operations on enum flags, ...).\n\n---\n\n**Relevant links**:\n* [Blender Manual ](library_overrides.html)\n* [the workshop report about overrides from January 2022 ]()\n\n-----------------------\n### 2021 Targets\n\n**Description**\n**Big picture:** Replace animation proxy system, and support local changes from linked data.\n\n**Use cases**:\n* Animators using proxies for animation.\n* Multiple instances of the same character with different animations.\n* Multiple instances of the same character with variations (e.g., material tweaks, ...).\n* Set dressing with local variations of instanced assets.\n* Override linked in character with cached animation [cache modifier]\n\n**Design:**\n - [x] `Asses feasibility of auto-override - direct change of linked data`\n - [x] `Need storage optimization document` #78944 (LibOverride: How to handle heavy data-blocks (meshes, shape-keys, actions...))\n - [x] `Need final signed off design for outliner interaction`\n - [x] `Need final design for the ID template` #78012 (UI: Search Menu Design for Linked Data-blocks)\n\n**Engineer plan:**\nNone - underlying code is already implemented.\n\n**Work plan**\n\n**Milestone 1 - Usability Pass**\n- [x] #76555 (Library Overrides: Usability issues/paper-cuts)\n- [x] #78012 (UI: Search Menu Design for Linked Data-blocks), #79959 (Data-block Selector Design Changes)\n- [x] [D7631: Library Overrides UI: Show library overrides in Outliner](D7631)\n- [x] *#73154 (Library Overrides - UI: Add access to the 'auto override' flag of IDs) (Might become unnecessary, postponed until we know.)*\n- [x] Enhance ways to add more than one overrides of same data (this is currently possible, but not obvious nor user-friendly at all).\n- [x] #77083 (Library Overrides Constraint and Modifier Access)\n- [x] #79562 (LibOverride: Support edition of lists (colletions) of ID properties/py-defined RNA collections)\n\n**Milestone 2 - Proxy Replacement**\n- [x] #81049 (Add operator to convert proxies to library overrides )\n- [x] #72629 (Library Override: Support editing of animation data in overriden data-blocks.)\n- [x] #82503 (Add Support of PointCaches to Library Overrides)\n- [x] ~~Implement real override of shapekeys data-blocks (not editing existing shapekeys, but being able to add new ones, and change influence of existing ones).~~ *on hold, we probably want to get rid of shapekeys as data-blocks first.*\n\n**Milestone 3 - Storage Optimization**\n- [x] Do not store whole Mesh data-block in overrides, this is useless and uses a lot of disk space (other obdata IDs are much less critical on that regard, being much lighter, #78944 (LibOverride: How to handle heavy data-blocks (meshes, shape-keys, actions...))).\n- [x] ShapeKeys may need investigation here as well.\n\n**Milestone 5 - Remove Legacy**\n- [x] #91671 (Remove Proxies).\n\n**Not A Milestone - Address technical Dept**\n- [x] #82160 (LibOverrides - Refactor how diffing of RNA collections is handled, and extend diffing possibilities.). *Refactor/technical dept is fixed, potential future improvements are for later.*\n- [x] #83811 (Library Override: Investigate Resync Improvements.).\n\n---\n\n**Relevant links**:\n* #53500 (Library Override (parent task))\n* [Blender Manual ](library_overrides.html)\n* @eyecandy did a video to show shortcomes of the current implementation. [state_of_overrides_in_production.mp4](state_of_overrides_in_production.mp4)" ]

[ "Particles: 'render as' collection does not render/display instances inside that collection\nOperating system: Windows 10 x64 Pro (1809, ver 10.0.17763.720)\nGraphics card: Nvidia GTX 1060\n\nBroken: Tested with 2.79b, 2.80 Release and 2.81 (f3a4f12ac090)\nParticle emitter doesn't emit all group objects.\n\nOpen the attached blend file:\n - At the top, there are 12 objects all belonging to group \"LightString\".\n - The bottom mesh contains 12 vertices. A particle system is attached. It should emit all 12 group objects at once.\n\nProblem: Whatever I try, only 8 of the 12 group objects are shown.\n\n[Particles2.blend](Particles2.blend)", "Group output node `is_linked` attribute is False during linking process\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\n\nBroken: version: 2.91.0 Beta\n\nWhen a node is linking update method of its tree is calling. In this method sockets which was connected has status 'is_linked' as True except `group outputs` nodes. I would expect that sockets of those nodes also would have True in `is_linked` attribute.\n\n\n\n[untitled.blend](untitled.blend)\n- Open the file\n- run the script\n- after having made the links, the update callback will report 'is_linked' as False for the Group output node", "Node Group Sliders Slow Performance using Packed Textures\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.83.6, also tested in the 2.91 daily build, and 2.90.1. Same performance.\n\nUsing custom nodes groups sliders with packed textures make them very slow using Cycles, on EEVEE it seems working fine. \nIf i unpack the textures the sliders acts normally.\nI also notice every time i use any slider in the top left corner shows \"Updating images\" and the freeze occurs. \nI also discover if i change the values of all the sliders that are using the packed textures it comes back to normality and the lag disapears.\nIm not a tech but it seems it has something to do with loading the textures.\nSize and image formts seems that are not the problem i tried changing them.\n{[F9090399](Packed_textures_performance.gif), size=full}\n\n- Append node group with textures unpacked.\n- Sliders working good and fast with textures unpacked.\n- Pack the textures.\n- Sliders and load times freezing.\n- Unpack the textures again.\n- Sliders come back to normality.\nor\n- Open attached .blend file\n- Play with the custom node sliders\n- Unpack the textures again.\n- Sliders come back to normality.\n\n[Packed _Performance_new.blend](Packed__Performance_new.blend)\n\n", "Eevee: Image Texture Node: Switching the source from \"Generated\" to \"Single Image\" and back to \"Generated\" leaves the shader result as pink color\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\nWorked: Unknown\n\nSwitching the source of an Image Texture shader node from \"Generated\" to \"Single Image\" and back to \"Generated\" leaves the shader result as pink color in Eevee. If it is working correctly, it should display once more the original texture as seen initially with the \"Generated\" setting. The problem is present only when Eevee is used as renderer. With Cycles, the texture is switched correctly to undefined (pink color) when switching to \"Single Image\" and back to the original one if changed back to \"Generated\".\n\n\nLoad the attached .blend file, change the image source on the material texture node to \"Single Image\" and then back to \"Generated\" while Eevee is used as renderer. \n\nFor comparison: Change to Rendered Viewport and Cycles as renderer. Repeat the changing of the image source to observe the correct behavior.\n\n[generated-image.blend](generated-image.blend)\n\n\n\n", "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", "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", "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", "Generated texture coordinates missing when switching from solid to rendered mode\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.80.0-git.14884cda1ff5-windows64\nWorked: 2.79b f4dc9f9d68b\n\nThe \"Generated\" texture coordinates make textures \"stick\" to the surface, even if the object is being deformed.\nHowever, this does not work as expected in 2.80 with the Armature Modifier, neither in Eevee nor Cycles.\nIn 2.79 in works correctly.\n\nPossibly related: #59275.\nHowever, this bug affects both Cycles and Eevee, while that report only concerns Eevee (and Cycles works correctly).\nThe difference is that here an Armature is used, while that report uses Shape Keys.\n\n[generated.blend](generated.blend)\nThe scene contains a cube with an armature modifier.\n- Open in both 2.79 and 2.80.\n- Press F12 to render.\n- See how the texture mapping differs.", "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.", "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", "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)", "Python Nodes for Cycles, Eevee, Compositor and Textures\nThis task has the purpose of adding RNA classes that can be used to create custom python nodes for builtin nodetree types.\n\nThe main purpose of these classes is to provide a better interface for custom nodes, that can be used in the Shader, Compositor, and Texture Node Editors.\n\n- - [x] Add Shader RNA class\n- - [x] Add Compositor RNA class\n- - [ ] Add Texture RNA class\n\n- - [ ] Add Python utilities for managing custom nodes\n- - [ ] Add Python utilities for converting nodegroups into custom nodes\n\n- - [ ] Documentation\n\nAny comments, sugestions and corrections are welcome.\n\nSome custom nodes for testing the patches:\n[Testing_nodes.py](Testing_nodes.py)", "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", "[cycles] - Distorted highlights when rendering detailed bump maps\nOperating system: Linux Mint 20.1 Ulyssa 64-bit\nGraphics card: GeForce RTX 2060\n\nBroken: 2.83, 2.92, 2.93 alpha\n\nWhen rendering dense scratch textures as bump maps, highlights appear as distorted rays instead of circles around the light. The error occurs with any high-frequency lines/micro-scratch image, including procedural and high-resolution textures. Changing bump strength/distance affects the size of the rays, but does not correct them. I have also tried different texture filtering and mapping options, and they all produce similar results.\n\n* Create/download a high density micro-scratch texture (long, thin lines in random directions)\n* Use the texture as height input for a bump node - more tiling will increase the effect\n* Set the bump strength or distance to a low value, around 0.005\n* Connect the bump node output to a glossy/reflective shader \nThe attached blend file has two bump map examples, and a normal map created from one of the bump textures. The normal map has the desired result, while the bump maps have distorted highlights/reflections.\n\n[scratch_highlight_example.blend](scratch_highlight_example.blend)\n\nResult from bump map (second one in blend file)\n\n\nExpected result, using normal map (created from previous bump map)\n\n\nMany thanks", "Adding NodeGroupInput node with NodeSocketImage input to CompositorNodeTree causes Bad Access crash\nOperating system: macOS 12.3.1 (21E258)\nGraphics card: `Apple M1`\n\nBroken: 2.93.10, 3.1.0, 3.1.2, 3.2.1\n\n\nAdding both a `NodeGroupInput` node and a `NodeSocketImage` socket to a `CompositorNodeTree`'s input causes a crash upon entering the group view of the node.\n\n\nOpen a fresh Blender instance\n\nRun the following python commands:\n\n```\ngroup = bpy.data.node_groups.new(\"test\", \"CompositorNodeTree\")\ngroup.inputs.new(\"NodeSocketImage\", \"image\")\ngroup.nodes.new(\"NodeGroupInput\")\n```\n\nOrder of the last two commands does not matter.\n\nOpen up your compositing node graph and enable \"Use Nodes\" if you haven't already.\n\nGo to Add->Group->test\n\nThe application crashes immediately with the following error summary\n\n```-------------------------------------\nTranslated Report (Full Report Below)\n-------------------------------------\n\nProcess: Blender [83447]\nPath: /Applications/Blender3.1.2.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.1.2 (3.1.2 2022-04-01)\nCode Type: ARM-64 (Native)\nParent Process: launchd [1]\nUser ID: 501\n\nDate/Time: 2022-05-14 23:55:57.0678 -0700\nOS Version: macOS 12.3.1 (21E258)\nReport Version: 12\nAnonymous UUID: FFD4E34D-780E-1ED3-65BE-8567CF743554\n\nSleep/Wake UUID: DF7F69BF-5C10-4E9C-8649-79686FC1C136\n\nTime Awake Since Boot: 140000 seconds\nTime Since Wake: 5503 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 27\n\nException Type: EXC_BAD_ACCESS (SIGABRT)\nException Codes: KERN_PROTECTION_FAILURE at 0x0000000101784ddc\nException Codes: 0x0000000000000002, 0x0000000101784ddc\nException Note: EXC_CORPSE_NOTIFY\n\nVM Region Info: 0x101784ddc is in 0x100e48000-0x10a7dc000; bytes after start: 9686492 bytes before end: 151351843\n```\n REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n```\n - > __TEXT 100e48000-10a7dc000 [153.6M] r-x/r-x SM=COW ...MacOS/Blender\n```\n __DATA_CONST 10a7dc000-10ada8000 [ 5936K] r--/rw- SM=COW ...MacOS/Blender\n```" ]

[ "When the Bump node is placed in a node-group, bump is not working.\nOperating system: Windows-10-10.0.18362 64 Bits\n{[F7727044](BumpmapInNodeGroup.blend)}Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.01\n\nBroken: version: 2.81 (sub 8)\nWorked: (Blender 2.81 build September 04)\n\nWhen the Bump node is placed in a node-group, bump is not working (as it should). \n\n1) Add a plane and give it a new material \n2) Add: bump node and a texture. Noise for example. \n3) Connect Noise texture (Fac) to height socket of bump node. \n4) Connect the normal of the bump node (out) to the normal (in) of principled BSDF). \n\nThis works. But now; \n5) Make a NodeGroup of the Bump node and the noise texture \n6) Connect this nodegroup with the prinicpled shader (normal and optionally Base Color). \nNow there is no bump, and if you adjust the strength strange things are going on with the normals. \n\n[BumpmapInNodeGroup.blend](BumpmapInNodeGroup.blend)\n" ]

[ "Blander crash without ray shadows Nvidia GTX 950M CUDA\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nWhen turn off ray shadow visiblity render becomes slow and the blender crashes.\n[2019-10-28_03-53-23.mp4](2019-10-28_03-53-23.mp4)\n\n------------\nI tested again on GTX 750 Ti and 2.92.0 Alpha. If I turn shadows off first, then switch to rendered view, it gives bad render:\n\nIt disappears when you do something. Typical when there's something wrong in Cycles. I need to restart Blender to be able to render again.\nWhen I turn rendered view first, then turn shadows off, it sometimes crashes.\nThis is all Cuda. Optix renders nothing at all. I presume Optix doesn't do volumes yet.\nAlso noticed that deleting sun lamp and leaving only area lamps fixed the issue.\n\n**Steps to reproduce**\n[облака в стекле.blend](облака_в_стекле.blend)\n- Open file\n- Disable shadow ray invisibility on object\n- Switch to rendered shading\n", " Annotations are blended incorrectly (looks like added?) on viewport backgrounds in viewport renders\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER\n\nBroken: version: 3.0.0\n\nBlender renders colorful annotations as white while using the viewport render function, when the viewport background is set to be completely white.\n\n- Draw an annotation (e.g. blue)\n- Set the viewport background (via Viewport Shading) to \"Viewport\" and set it to be red (could be world as well if you like).\n- 3D Viewport > View > Viewport Render Image.\n- notice the blue annotation being added to red background (resulting in pink)\n- if you do this with a white background, you will think the annotations are gone (all strokes add to white... giving.... white :)\n\n[#93748.blend](T93748.blend)\n\n\n", "Bake artifacts with multimaterial in object\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nThen i try bake Ambient Occlusion in object with 2 or more assigned materials, Ambient Occlusiun bakes grey or black squares\n\n\n- Open attached file and bake ambient occlusion.\n[Bake_Test.blend](Bake_Test.blend)\n\n", "Same pattern looks different for Cycles and Eevee\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.1\n\nThis is the difference\n\n\n\n\nsimplified file\n[pixels tiled1.blend](pixels_tiled1.blend)\n\n\nold file \n[pixels tiled.blend](pixels_tiled.blend)\n\nI suppose the difference in Color Ramp or Noise node.\n", "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", "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)", "Light of 'Area' type lamp presents artifacts when placed at great distances\nOperating system: macOS-13.4.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: versions: 3.1 to 4.0a \n\nArtefact's appearing with bigger Arean Light distances and spread angle 0.1 to 20~ \n(Like for space scenes with bigger distance Area lights for better sun effects...)\n\nJust open one of the files or follow the image below to set up the light.\n\n", "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\n\n", "2.83lts Regression: Viewport render image ignores colormanagement, and appears to be hardcoded to use sRGB.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBisect points to 190fd795a9\nBroken: version: 2.83.0\nWorked: 2.82a\n\n`Viewport Render Image` ignores color management. The image produced is clamped to 1.0 according to the color sampler. It appears to be hard coded to sRGB.\n\nCreate a Scene that has scene linear color values above 1.0. Render with Filmic. Then do `viewport render image` and see how it produces an image with blown out highlights.\n\n2.82a:\n\n\n2.83:\n\n\n\n[test.blend](test.blend)\n\n", "Optix: Motion Blur seems to glitch out while rendering\n\nOperating system: Windows 11 Pro 22H2 22621.525\n\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\n\nBroken: version: 3.3.2 LTS / 3.5.0 Alpha (Broken in both)\n\n\nHaving motion blur on while rendering with Optix seems to not work as expected in this scene. It renders out with artifacts (Alpha / black squares). Things work fine **when you turn off motion blur or switch to Cuda**.\n\n \n\n**Steps to reproduce the bug:**\nOpen the attached fine and render frame #82 with Optix enabled.\n\n[Keyframe remove 1_010.blend](Keyframe_remove_1_010.blend)\n", "Motion Blur causes visual glitch on point cloud object moving\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\nWorked: not known\n\nPoint cloud object + Motion Blur + animation. The first frame of animated movement will incorrectly render compared to before and after the animation starts. \nConvert Cube to point cloud\nAdd a location keyframe on frame 2\nmove the object and add another keyframe on frame 3\nRender with motion blur turned on.\nCompare the rendered frames.\nframe 1 looks correct, frame 2 is too dim even though it is not moving yet.\n\nNote: CPU renders frame 3 incorrectly as well. not sure if this requires another bug report. \n\nFrame 1:\n\nFrame 2:\n\n\nFrame 3 on GPU:\n\nFrame 3 on CPU:\n\n[MotionBlur_PointCloud.blend](MotionBlur_PointCloud.blend)\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", "Volume voxels visible in compositing (Cycles)\nOperating system: Windows 10\nGraphics card: GeForce GTX 950 OC\n\nBlender 2.80 cc73d59ad580\n\nFirst of all :\nNot sure if this is a bug or if Im just not getting it.\n\nEverything is done in Cycles\n\nIm subtacting the DiffInd passes in compositing and I get the volxel shape of my smoke sim.\n\nHere a screenshot of my Nodesetup (note the backdrop)\n\n\nI do this to extract the Indirect lighting of for example fire or something else while excluding the sun and stuff.\n\n\nThis is the image (the white cuby thing to the right of the smoke)\n\n\n\n\nAdd a basic smoke simm with high resolution and a ground and wall.\nAdd a sun light\nAdd a new view layer\nExclude the smoke domain from the 2nd layer\nEnable the DiffInd pass for both layeres\n\nIn compositing :\nSubtract the DiffInd passes from each other.\n\n\nThis is an example scene:\n[debug.blend](debug.blend)\n\nIt seems like there is a problem how \"null\" surfaces get handeled.\nIf I set a layer to indirect only the indirect light only appear outside the voxels (where they are intersecting the geometry).\n", "Artifacts when composing render passes with SSS, EEVEE and SSR\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0 Beta\nWorked: I'm not sure this behavior is new. Blender 3.2 displays the same behavior.\n\nWhen compositing render passes that have been generated using EEVEE, and an object has Subsurface Scattering enabled, and Screen Space Reflections are enabled, and Half Res Trace is disabled, artifacts are generated. The combined pass, however, correctly renders.\n\n\n*What I get (demo file included below)*\n\n\n*What I should get*\n\nNote: if Half Res Trace is enabled, the problem disappears.\nAlso, if Cycles is used to render the same scene, the passes do not display these artifacts.\n\n\n\n\n- Create a file that uses EEVEE as renderer.\n- Enable Screen Space Reflections. Disable Half Res Trace.\n- Create an object with Subsurface Scattering\n- Enable the following necessary render passes: Diffuse Light, Diffuse Color, Specular Light, Specular Color\n# In compositing, mix as follows the passes: multiply Diffuse Light and Diffuse Color; multiply Specular Light and Specular Color; add them.\n\nChanging the roughness can make the effect more extreme. Having a very contrasty roughness map exacerbates the problem:\n\n\n*a contrasty roughness map*\n\n\n*the render showing the problem more extremely*\n\n\n*how it should be*\n\nThe final result should be akin to the one posted above. You can compare the composited result with the one that is already combined: the combined one does not display the issue. Using Cycles for the same setup also works without problems.\n\nThe inconsistency of results mentioned above makes me believe this is a bug, and hence my report.\n\nDemo file: [sstest.blend](sstest.blend)", "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" ]

[ "Blender 3.0 Denoising on Transparency Creates Artifacting (Blend included)\nOperating system: Win 10 (latest update)\nGraphics card: RTX 3090\n\nBroken: (3.0.0 and 3.0.1 dc2d18018171 Branch: Master)\nWorked: (2.9.0)\n\nWhen enabling transparency under \"Film\" settings, artifacts occurs in the transparency channel\n\nOpen attached .blend in 2.9.0 and 3.0.0 and hit render to see. I've set-up a compositor node setup to highlight and visualize the artificating found in 3.0.0. Try rendering with both Denoising methods to see variations in artifacts.\n\n**Other notes**\nI've played with as many render settings as possible and found that the denoiser is responsible. OptiX is worst, OpenImage is not as bad in artifacting.\n\n[alpha-transparency-denoising-issue-sample.blend](alpha-transparency-denoising-issue-sample.blend)\n\nNotice the clean colors in the greys (background composited in Compositor to help see issue)\n\n\nNotice the vertical and horizontal line noise\n\n\n[system-info.txt](system-info.txt)" ]

[ "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", "Unable to create manual curve to mesh UV with spline parameter\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\n\nBelow file is creating uv's from the curve length and profile and then outputting as a custom_UV attribute. There seems to be squashing happening at the beginning and end.\n\n[spline parameter fac bug.blend](spline_parameter_fac_bug.blend)\n\n\n\n", "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", "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", "Skin modifier root on every vert\nOperating system: win10\n\nBroken: (2.79b, 2.82)\n\nSingle vert is screwed into spiral via Screw modifier. Skin modifier treats every vert as root, ending up with bad polygon flow.\nLeft is object with modifiers, right is applied version to see issue clearly:\n\n\n1. Use single vert with offset from origin to create spiral via Screw modifier\n2. Put Curve modifier on it\n3. Add Skin modifier\n4. Apply every modifier before Skin\n5. Enter edit mode and see many roots\n6. Click \"Mark Root\" in Skin settings -> polygons calculated correctly\n\nIn attached file:\n6. Click \"Mark Root\" in Skin settings -> polygons calculated correctly\n[screw_skin_root.blend](screw_skin_root.blend)\n", "Regression: Quad View Gizmo Tooltips at wrong position\nOperating system: Windows\n\nBroken: 2.93.0, `92b0803f35a7`\nWorked: 2.93.0, `0876829e7a77`\nSuspected: cf6d17a6aa\n\nIn Quad View mode gizmo-tooltips are shown at the wrong position (always at lover-left view gizmos)\n\nStart Blender, in 3D viewport press Ctrl-Alt-Q, hover mouse over gizmos.\n", "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", "Preset icon overlaps panel header text\nOperating system: Mac 10.9.5\nGraphics card: Macbookpro NVIDIA GeForce GT 750M 2048 MB\n\nBlender 2.8 downloaded today\n\nIn movie editor\nthe text tracking settings is somehow mixed up with a button.\nI can sent a pic if you want.\n\nI am a amateur and English is not my first language, so i'm very sorry if i've wasted your time.\n\nGreetz \nLes", "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.", "Assign Shortcuts: creates shortcut in the \"wrong\" space\n**OS**: Linux 5.3.8-arch1-1 x86_64\n\n**Blender version**\nBroken: 2.8x (up to and including fc79d27951)\n\nWhen using the context menu to assign shortcut to a button or checkbox, the shortcut is created in a wrong space, which may lead to error popups when pressing that shortcut with mouse hovering over a different space.\n\n\n1. Load the default scene.\n2. In 3D viewport, expand the Overlays popover, right-click the Wireframes checkbox and assign a shortcut through the context menu.\n3. Note that shortcut works while the mouse is over the 3D viewport.\n4. Move the mouse over the Properties and try pressing the shortcut. You'll get an error popup.\n\nThis is due to the shortcut being created in the Window space, not 3D View space.", "PBVH Pixels should check on center uv coordinate.\nCurrently it checks on bottom left corner, but the painting is half a pixel shifted. By adding an offset of half a pixel this should reduce some artifacts.", "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", "3D cursor not respecting orientation setting if other tools are active.\n**System Information:**\nNA\n\n**Blender Version:**\nBroken: Blender 2.8 Beta 0f5b53ba4dc\nRetested with Blender 2.90 c880e54a95dd (2020-05-14 22:52)\n\n**Short description of error:**\nThere are a few inconsistencies with the 3D cursor in the 3D viewport. Here are the steps to reproduce.\n1. Load up Blender. For this example I will use left click select. Right click select also experiences this issue.\n2. Select the 3D cursor from the tool bar and in the tool settings change the orientation to something other than \"View\" (I'll use \"Geometry\" in my example).\n3. Switch to any other tool on the toolbar and move the 3D cursor using `Shift-RMB`. The 3D cursor will move, but it will take on the orientation of the viewport, not the set 3D cursor orientation.\n\nHere's some interesting things to note:\n\nIf the tool you have selected is \"Tweak\" (found by cycling through the \"Box select\" tool until you get to tweak), the 3D cursor orientation will respect the orientation set in the 3D cursor settings.\n\nThis is interesting because as @lichtwerk has pointed out in the comments, there are settings in the keymap panel to control this. In the keymap there are options under the section \"3D View>3D View (Global)>Set 3D cursor\" and \"3D View>Object mode>3D View Tool (tweak)>Set 3D cursor\". Both of these options default to have the orientation as \"View\" (but gray out) which is technically the cause for the behavior I saw in the original copy of this report, but for some reason, the \"tweak\" tool doesn't follow the keymap. Or both keymaps are supposed to reference the orientation set by the user (signified by the grayed out buttons in the keymap) and \"3D View (Global)>Set 3D cursor\" isn't doing that.", "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", "UI: Drag Tool option is misaligned and should not use colon\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\nDrag Tool option is misaligned and should not use colon:\n{[F11087908](image.png), size=full}\n\nBtw. `Gizmos:` shouldn't use colon either\n\n" ]

[ "Wrong proportional editing area of influence UI.\n\nBroken: all.\n\nIf you set the pivot point to the 3d cursor for example, the area of influence of proportional edit will mistakenly be drawn around the cursor, as the vertices there are not the the ones affected by it. The proportional edit circle should always be drawn around the selection, as this is what it influences, not around pivot point.\n\nHow it is: \n\nHow it would be better: \n\n\nMove cursor away from the cube.\nChange pivot point to cursor for example.\nTurn on proportional edit\nSelect on vertice of the cube\nRotate, or Scale or Move\nSee area of influence be drawn in the wrong place.", "Invisible Proportional Editing Circle\nOperating system: Darwin-18.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) UHD Graphics 617 Intel Inc. 4.1 INTEL-12.2.18\n\nBroken: version: 2.83.0\n\n\nOn MacBook Air when using proportional edit to move vertices, the circle to indicate the size of the edit does not appear. However, proportional edit is still adjustable by scrolling up and down on trackpad.\n\nI don't know exactly as it happened one day when I opened this file. The circle still appears when I create new project. Last things I did on the file before noticing the problem was rendering it and then create a new mesh called \"sprinkle\" a few days later.\n\n[donut.blend](donut.blend)" ]

[ "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)", "Blender 2.81 — Shadow glitches with Workbench render-engine (in viewport and same at render)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.81 (sub 9)\n\n\nBroken shadows \"traced path\" glithc effect in the air in places where geomety have \"complex area\" (when you use shadows from Workbrench render and same in viewport).\n[Screenshot ](l2ZRNEjhzLYbl2.jpg)\nHere is on [video ](#!0OoB2I7R!h1qq3DB20nOOgoxoYw9QT_kyoZO-a-1C7OSqRifExcs) uou can see it. Sorry for broken english.\n\n\nDon't know how to reproduce it step by step, so I've put the file here: \n[broken.blend](broken.blend)\n\n\n", "Keyed Particle Physics Incorrectly Rendered Under Eevee and Cycles, but Correctly Rendered in Viewport Render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nCreate two objects. Attach a normal particle system to the first one. Attach a keyed particle system to the second one, with the two relations \"first object\" then \"second object\". Therefore, particles should move from the first object to the second object. If the starting velocities are non-trivial and the keyed particles are generated over three or more frames (e.g., start time 10, end time at least 12) then the particles of the keyed system are correctly rendered in the viewport (rendered mode) but appear in different positions when actually rendering (pressing F12).\n\nI first discovered this with a more complicated example, and the same behaviour occurred under both 2.90 and 2.83 (normal releases). Googling did not turn up anything relevant. (Motion blur is off.)\n\nI have been able to recreate it with a simple .blend file attached. Included are two screenshots at frame 20, one of the viewport, one of the rendered image. While the difference is just one particle here (a red particle is over the left square in the viewport but off the square in the rendered image), vastly different behaviour can be achieved by increasing the difference between start and end times. \n\nIn the more complicated example, not included here, a particle would appear at the top of the screen and move towards its final destination. When rendered though, it would appear in the correct place on that frame but then immediately jump to a very different location on the next frame.\n\nNote: This bug might depend on the first object's particles having a short lifetime - the original motivation is having one object explode then morph into another object. The rendered animation looked very different (and incorrect) from the viewport animation.\n\n[system-info.txt](system-info.txt)\n\n\n\n\n\n\n[Debug 2.blend](Debug_2.blend)\n1) Open it.\n2) Set viewport to Rendered mode.\n3) Move playhead to frame 20.\n4) Observe the locations of the 4 red particles near Plane.001. (They form a loose \"T\" shape and none are touching Plane.001.)\n5) Press F12.\n6) Observe the locations of the 4 red particles near Plane.001 are very different. (Two are touching Plane.001 and the other two are in line ready to arrive at Plane.001.)\n\n", "Eevee refraction regression in orthographic view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.91\nWorked: 2.92\n\nIn orthographic view, with the view or camera camera perpendicular to a refractive surface, screen space refractions appears blurry, as if it had roughness, even with refraction shaders with 0 roughness\n\n2.91: \n\n2.93: \n\nEdit: In perspective it's also noticeable in the center. It looks like a small ball or dot that distorts the image slightly\n\n\nOpen file in different versions\n[bugRefractionEevee.blend](bugRefractionEevee.blend)\n\n\n", "Cycles viewport render border no longer shows scene behind with OpenGL\nOperating system: Ubuntu 18.04\nGraphics card: GTX 1080\n\nBroken: 2.80 Hash: 42dd888b98\nWorked: 2.79b.\n\nCycles Preview render removes all shading from the scene. This is very evident when using border renders to help isolate down sections to work on (which is key for working on large scale production scenes.\n\n1. Open attached blend file in blender 2.79\n2. hit shift z in the 3d viewport\n3. notice how you can see the building to the left\n4. close blender 2.79, and open the attahced blend file in blender 2.8\n5. hit shift z in the 3d viewport (blender 2.79 keymap)\n6. notice how you cannot see the building to the left anymore? \n\nThis means that reframing whilst border rendering is no longer possible, nor is it possible to change the border render without guessing to work on a different area of the frame without having to go back to solid mode and then back to rendered mode. Going in and out of solid mode can be 20-30 seconds on production scenes so limiting the amount of switching is important.\n\n[example.blend](example.blend)", "Blender renders wrong in viewport\nOperating system: macOS-11.2.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15\n\nBroken: version: 2.93.0 Alpha\n\n\n\n1) steps to reproduce:\n\nopen blend file [circular_circles_wave_emission.blend](circular_circles_wave_emission.blend)\n\n2) in viewport change to rendered view\n\n3) you will see:\n\n\n\n4) select the circles\n\n5) press tab and tab again\n\n6) you will see:\n\n\n\nwhich is correct\n\n", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n ", "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.", "Workbench Shadow Improvement\n### Respect World Space Lighting option\nCurrently, the shadow is always in world space. Use view space orientation when matcaps is used or when studio lights use view space orientation.\n\n### Follow the brightest light\nCurrently, the shadow is not following any of the lights direction in the studio lighting config. Selecting the most bright light seems like a good default. Otherwise, we can add a flag in the studio-lights to tag which one the shadow should follow.\nA toggle option to force the use of the custom shadow direction should be added (disabled by default in new files, enabled in older files).\n\n\n### Follow the matcap\nWhen matcap brightest spot can be extracted, we should make the shadow follow this direction.\n\n", "Viewpor render includes color management, even if the view shading mode does not\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\n\nBroken: version: 3.1.2\n\nA viewport render should look exactly as what's seen in the viewport, especially if that viewport is set to, for example, solid shading. Right now, it does not, because color management is taken into account even in shading modes which do not use it.\n\n1. Set viewport to shaded mode\n2. Set viewport background to a white color\n\n3. Set something in the color management panel to something crazy\n4. Observe how the viewport does not change.\n5. Make a viewport render\n\nResult:\n\nThe viewport render includes the crazy values from color management.\n\nExpected:\n\nIt should look like the viewport and nothing else. It's *technically* not a viewport render currently.", "File thumbnails don't always show rendered result\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\nBlender doesn't save previews that look as the eevee (or cycles) render when using a camera.\n\nUse a file with a camera, save while rendered mode is on, and it will look like workbench mode.\nDelete the camera, it will save as the mode is displayed and will do as rendered if that's what you have.", "Some Overlays are not rendered in Viewport Render (Text Info incl object name, Statistics, 3D Cursor)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.1\nAlso 3.1.0 Alpha\n\nUsing viewport render (or workbench) I'm unable to view object or empty names \n```\n(bpy.data.objects[\"NAME\"].show_name)\n```\n\nEnable show name on a visible object, and make a viewport render (bpy-ops-render-opengl)\nThe text isn't rendered in the image like it is in the viewport.\n\n", "Eevee RGB Curves node inaccurate compared to Cycles\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\n[eevee_rgb_curve.mp4](eevee_rgb_curve.mp4)\nThe transformation that the RGB curves node applies to a color differs slightly between Eevee and Cycles, even if the curve is left as default.\nNot sure if this is a bug or just a known limitation, but it breaks compatibility between Eevee and Cycles in edge cases.\n\n[eevee_rgb_curve.blend](eevee_rgb_curve.blend)\n\n", "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.", "The Viewport Display setting of Particles affect the Render result with Eevee \nOperating system: Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe Viewport Display setting of Particles affect the Render result with Eevee \n\nWith Particles selected Change \"Display as\" to \"Path\" in Viewport Display setting and Render with Eevee . error : Pathes will be dislpayed in render result \n[partical_render.blend](partical_render.blend) press render\n\nFrom other reports what is also affected:\n- `Viewport Display` > `Strand Steps`\n- `Viewport Display` > `Amount`" ]

[ "New soft shadows don't support viewport render [no TAA]\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n\nNot sure it's bug, or functional defects. \n\n\nDownload my file, than click View/ Viewport render image.\n\nscreenshots:\n\n\n.blend file:\n[viewport_render_soft_shadows.blend](viewport_render_soft_shadows.blend)\n\n" ]

[ "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "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", "Lost hotkey with save preset\n2.80\n\n\nI finally can replicate problem from 2.7x and it is still problem in 2.80. When you change some combination of hotkeys and save it to the preset. You lose some of them. On my GIF example Numpad 1 dissapear.\n\nSometimes it come back after restart Blender, but sometimes it is just gone.\n\n\n\n", "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", "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", "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)!!", "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)", "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)", "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", "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```", "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", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "Blender 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 Opens Window then Closes/crashes\nOperating system: Windows 10\nGraphics card: AMD FirePro W2100\n\nBroken: 3.5.1 2023-04-24 18:11 Hash:e1ccd9d4a123 Branch: Blender -v3.5-release\nWorked: first version used on this computer\n\n-First attempted to run blender, found error by running the debug, error:\n\n_EXCEPTION_ACCESS_VIOLATION_\n\n- Did specific driver updates for AMD FirePro W2100 and Intel CPU\n\n- Then ran dell command update\n\n- New error appeared after driver updates and running blender:\n\n_A graphics card and driver with support for OpenGL 3.3 or higher is required.\nInstalling the latest driver for your graphics card might resolve the issue._\n\n- Then downloaded GPU-Z to figure out OpenGL version\n- Open GL version was 1.1 when monitor DisplayPort was plugged into the motherboard\n- Open GL version was 4.5 when monitor DisplayPort was plugged into GPU\n\n- Now blender window would appear but closes immediately\n- running blender_debug_gpu_glitchworkaround.cmd in the Blender file worked to make Blender run but is NOT the overall fix\n- updated python\n- did windows updates\n\nunsure\n\n", "Crash 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 doesn't respond while selecting system console and saving or opening another file\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: 2.70 - 2.81.16 and 2.82 (sub 6)\nWorked: ... - 2.69 (when saving, but not when opening files)\n\nBlender doesn't respond while selecting system console and saving or opening another file\n\n - Toggle system console\n\n\n - Select any text or space in it\n\n\n - Save the file or open another without closing nor deselecting the text in the system console\n\n\n - Not respond\n\n\nNote: It works again when deselecting the text in the system console\n\nOdd behavoir: It does work when saving in 2.69 and olders, but doesn't when opening files", "Blender often crashes when I save file with python script\nOperating system: Windows 10\nGraphics card: AMD radeon (TM) R5 M430\n\nBroken: 2.82a \nWorked: (optional)\n\nBlender often crashes when I save file with python script in it, sometimes it doesn't\n\n\nwrite script with at least one mistake > toggle system console > select any text from the system console (to copy it for example) > run a script with at least one mistake > blender crashes\n\nNote: I use Notepad++ to write the code and then I copy from notepad++ to blender text editor", "Windows, Closing Blender with console window open can lead to lockup\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.83 (sub 11)\n\n\nClosing Blender with console window open can lead to lockup. I have to close Blender from the task manager then.\n\n\nOpen Blender. Open the console window. Click at the console window to give it focus. Now click at the close button in Blender. Blender will freeze. \n\n[2020-04-06 08-23-34.mp4](2020-04-06_08-23-34.mp4)\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", "AutoMerge Keyframes only deletes unselected keyframes (scaling muliple selected to zero or snapping to the playhead fails)\n\n\nLinux Ubuntu & GeForce GTX 580\n\n\nBroken: master\n\nWith \"AutoMerge Keyframes\" toggled on it simply doesn't do that, whether you're scaling keyframes or moving them around.\n\n[auto_merge.blend](auto_merge.blend)\n\nMake an armature, go to pose mode and set keyframes on the bone. Scroll forward a few frames, move the bone around (and rotate) and key it again. Do this a couple of time so you have some keys to work with.\n\nIf you select all the keys in the dopesheet editor and scale them down so some of them land on the same frame, blender doesn't automerge them. The keys seem to still exist on the same frame, as you can see in the graph editor. Even if you select all the keys and move them by one frame (which should trigger the automerge) it still doesn't merge the keyframes.\n", "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.", "Outliner: Sync Selection off not working when clicking LMB on data object name\nBroken: version: 3.0.0\nBroken: version: 2.91.2 (works correctly on meshes for some reason till worked version)\nWorked: version: 2.82\n\nWhen `Sync Selection` is off it's still possible to sync selection by clicking on object data name (+ small margin). Additionaly clicking on object data name will sync it with relevant slot in Properties editor. This bugged area becomes slightly longer to the left when active, see video.\n\n1. Open default scene.\n2. Turn off `Sync Selection` on Outliner.\n3. Deselect onjects in your scene by clicking on empty space in 3D Viewport.\n4. Select objects or object data in outliner without clicking on their name - see that `Sync Selection` is off\n5. Select objects or object data in outliner by clicking in their name - see that now parent onject is selected in Outliner aswell as in 3D Viewport.\n[Outliner Sync Selection off bug 2021-12-15 20-45-35-213.mp4](Outliner_Sync_Selection_off_bug_2021-12-15_20-45-35-213.mp4)", "Boolean - Animation - Viewport works correctly render view doesnt\nUbuntu 18.04, Win 7 x64\n\nBroken: d53093953f8\n\nBooleans dont match between Viewport and Render\n\n1. Open attached blend file\n2. Preview render (shift z)\n3. Notice the green on top\n4. F12 Render\n5. Notice how the green is no longer there\n\n[booleansBug.blend](booleansBug.blend)", "Adjust Last Operation: Other changes outside that panel are reverted back automatically\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n\nHere the demo and file\n[2020-06-23_20-30-11.mp4](2020-06-23_20-30-11.mp4)\n[Scene state reset.blend](Scene_state_reset.blend)\n\n1. Add some objects, add last one\n2. Change visibility for other objects via outliner\n3. Change property in adjustment popup\n4. Scene settings resetted to previous", "Design issue: Icon next to overridden property does not perform the function it strongly suggests\n3.0.0\n\nWhen a propertry is overridden, the \"animate property\" button next to it is replaced by this \"reset\" icon:\n\nThese really seem to suggest that clicking them will remove the override. Instead it just adds a keyframe as usual. This seems misleading.\n\n - Override a property of some library override asset\n - Click the button to the right of that property\n\n", "Collection visibility animated\nI need to recap with @brecht and @Sergey why we didn't push for this in 2.80. If it is doable and doesn't break our design, we should support this.\nBasically only the datablock settings (global viewport visibility, and renderability).", "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", "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", "Keyed Particle Physics Incorrectly Rendered Under Eevee and Cycles, but Correctly Rendered in Viewport Render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nCreate two objects. Attach a normal particle system to the first one. Attach a keyed particle system to the second one, with the two relations \"first object\" then \"second object\". Therefore, particles should move from the first object to the second object. If the starting velocities are non-trivial and the keyed particles are generated over three or more frames (e.g., start time 10, end time at least 12) then the particles of the keyed system are correctly rendered in the viewport (rendered mode) but appear in different positions when actually rendering (pressing F12).\n\nI first discovered this with a more complicated example, and the same behaviour occurred under both 2.90 and 2.83 (normal releases). Googling did not turn up anything relevant. (Motion blur is off.)\n\nI have been able to recreate it with a simple .blend file attached. Included are two screenshots at frame 20, one of the viewport, one of the rendered image. While the difference is just one particle here (a red particle is over the left square in the viewport but off the square in the rendered image), vastly different behaviour can be achieved by increasing the difference between start and end times. \n\nIn the more complicated example, not included here, a particle would appear at the top of the screen and move towards its final destination. When rendered though, it would appear in the correct place on that frame but then immediately jump to a very different location on the next frame.\n\nNote: This bug might depend on the first object's particles having a short lifetime - the original motivation is having one object explode then morph into another object. The rendered animation looked very different (and incorrect) from the viewport animation.\n\n[system-info.txt](system-info.txt)\n\n\n\n\n\n\n[Debug 2.blend](Debug_2.blend)\n1) Open it.\n2) Set viewport to Rendered mode.\n3) Move playhead to frame 20.\n4) Observe the locations of the 4 red particles near Plane.001. (They form a loose \"T\" shape and none are touching Plane.001.)\n5) Press F12.\n6) Observe the locations of the 4 red particles near Plane.001 are very different. (Two are touching Plane.001 and the other two are in line ready to arrive at Plane.001.)\n\n", "Objects in front of the selection stay in front in wireframe mode\nBroken: version 2.80+\nWorked: version 2.79\n\nIn blender 2.79, the wireframe of objects selected or in edit-mode was drawn in front of the wireframe of all other objects in the scene.\nIn blender 2.80 onwards, this doesn't happen anymore.\n\nHere's a model shown in 2.79b, with my usual theme:\n\n\nThe object in edit mode is behind the objects seen with gray wireframe. But because it is in edit mode, it is drawn in front of the others.\nThe same is true if the object is in object-mode but selected.\n\nNow compare the same model in 2.8x:\n\n\nHere the same object is seem in edit-mode. Now it is drawn behind everything else, which creates a noisy, low-contrast appearance, making it hard to see and sometimes hard to edit. \nSometimes it forces me to rotate the view to get other things out of the way (especially if the foreground objects have a lot of detail/geometry).\n\nIf you zoom in real close on an area where a foreground object overlaps the selection, snap a screenshot, and then scale or zoom the image, you can see how the foreground object is definitely being drawn in front of the active one:\n\n\nBottom line: In my opinion, in a normal view mode like Solid or Lookdev/Material, the selection of course should remain behind everything else (unless changed via its Object properties), but in Wireframe view mode the selected object should appear in front of other stuff.\nPerhaps an option is needed the Preferences to force the old 2.79b draw order.\n\n- Open attached file\n- Change the wire theme to something gray (or use the attached theme).\n[wireframe_in_2_79.blend](wireframe_in_2_79.blend)\n[classic-look.xml](classic-look.xml)\n\nThe original model is probably too big to upload here: Hypercube%20printer%20model%20(320x320%20bed,%20540x510x540%20frame).blend", "Regression: Global Viewport Visibility no longer readable when object is appended from another file\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.0.0 Alpha\nWorked: version: 3.0.0 Alpha\n\nGlobally disable in viewports Bug. I just upgraded from version 2.9 to version 3.X I downloaded version 3.5.1 and noticed this problem, then I downloaded some other versions of 3.X and noticed the same problem, the same problem as in version 2. X I didn't have it.\n\nWhen I create an object and then I disable the globally disable viewport option, and then I save the file, when I open another blender file and append to that object, it appears in the scene with globally disable viewport ON even if I saved it with this option to OFF. I know I can disable it, but this is very annoying when I append a rig and have to check that box 100 times on different meshes\n\nHere is a video to understand better : AecByo8PYQw \nI did that on 3.6.2 and 2.9.1 to see the differences. \n\n1. Open any 3.X version of blender. \n2. Delete the camera and the sun, keep the cube.\n3. Then disable the globally disable viewport option. \n4. Save the file somewhere. Then close blender.\n5. Open blender again (not the file you just saved) .\nThen append the cube you just saved and you will see that it appears with globally disable in viewport ON, even if you saved it with off.", "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.", "Force keyframe with “insert only needed” option on\nBroken: 2.80\n\nI suppose this was intended not a bug, but from an animator perspective it seems like a bug.\n\nWhy when \"insert only needed\" options is ON I can't insert keyframes manually? I only get \"Keying set failed to insert any keyframes\" info\n\nInserting manually only works if you do it outside the current range of animation, but then it removes the key frames next to it. I know there were flat, but it's frustrating when the software deletes keys from my animation. Is it possible to disable this option?\n\nI usually put keys on all available attributes so I don't accidentally change the pose, but on the in-betweens I like to have only keys on changed attributes\n\nIs there a possibility to forcefully insert a keyframe? or just set Autokey to insert only modified attributes? \n\nI somewhat got the functionality I wanted using KeyinSets with overriding the ION option but that worked only when Target ID-Block was set for a specific object. But creating & switching specific keyingsets for all animated object is way to troublesome while animating\n\nCheck the \"insert only needed\" in Preferences > Animation.\nManually add 2 keys for an object e.g. frame 0 & 10. Then try the same keyframe on frame 5. -> Keying set failed to insert any keyframes\" \nAlso later try setting keyframe on frame e.g 15 - > Keyframe on 10 disappears " ]

[ "Restrict Viewport Render keyframes from 2.79b do not correctly import into 2.8\nOperating system: Windows 10\nGraphics card: GeForce 1060\n\nBroken: 2.8 Beta 4c31bed6b46\nWorked: (optional) 2.79b\n\n\nWhen a file from 2.79 that is animating object viewport visibility is opened in 2.8, the 'Restrict Viewport Visibility\" keyframes no longer work. Presumably this is because the feature has been split into 'Hide object in viewport' and 'Disable object in viewport'. Ideally, 'Restrict Viewport Visibility' keyframes would be converted to 'Disable object in viewport' keyframes.\n\nOpen attached .blend in 2.79b\nPlay animation\nAt frame 30, cube is hidden in viewport\n\nOpen in 2.8 Beta\nPlay animation,\nAt frame 30, cube is still visible in viewport\n\n[hidecube.blend](hidecube.blend)\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", "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", "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", "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", "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", "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", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "Blender will not use new GPU for rendering or recognize it for OpenCL or\nOperating system: Windows 10, all up to date\nGraphics card: msi 4070ti (brand new)\n\nBroken: 2.93.18 as well as the most recent 3.5 on the splash screen, tried most of the in-between builds on clean reinstalls but same issue on all of them.\nWorked: no version\n\n**Error**\nAfter getting a new 4070ti, blender started crashing every 5-10mins or so while moving around a simple scene in the viewport set to material shaders mode, not render mode. The scene consisted of a couple of primitives with very simplistic wood, glass, and metal shaders. When I tried rendering as is it also crashes immediately upon rendering no matter what I use. GPU wasn't greyed out in render settings initially (though it now is), but only showed in preferences under CUDA, and wasn't recognized in OptiX or OpenCL (in newer blender models it also wasn't recognized by anything but CUDA). \n\n1. tried to render a simple scene with render settings set to new gpu\n2. render crashes immediately\n3. move around in viewport on material mode, barely move and blender crashes\n4. check Blender preferences <system <cycles rendering devices: gpu is visible in CUDA but not in any other options (originally was working on 2.93 where I wanted to use OpenCL, I know this isn't in the newer versions with OptiX/all non-CUDA options). Try unchecking CPU hoping to force blender to actually use the GPU and have tax manager up to see if gpu is even being used\n5. blender crashes without rendering, no sign of gpu being used on task manager but CPU usage spikes to 100%\n\n**What I've tried so far that might be helpful**\n\n- tried clean reinstalling different versions of blender, both newer/experimental and older/more stable builds\n- made sure I reset BIOS in case this is a new component/migration error\n- made sure the settings for blender in NVIDIA control panel were all compatible or high performance \n- made sure NVIDIA drivers are all studio version and up to date\n- made sure blender cache folder didn't have any kernel errors\n- installed any updates to windows, this did make the gpu visible in OptiX but unfortuantely the same issue persists even with OptiX on any version where blender just won't use it and uses only cpu (despite being unchecked)\n- double checking how much memory I have on my new gpu vs the old one - yup it does\n- benchmarked my gpu using port royal and making sure I could render a project in Premiere. GPU did fine on the benchmark test and was able to render a 20min video fine. Only blender seems to be the problem\n- noticed today in stackexchange there are a lot more reports with others having the same issue, even with equivalent AMD gpus, and all comments said this seems to be a bug\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```", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\n\n", "Crash 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 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", "Cycles HIP device crash on rendering on latest AMD Adrenaline Driver\nOperating system: Windows 11 Pro for Workstation\nGraphics card: AMD Radeon RX 6750XT (Driver: AMD Adrenaline 23.7.1, 23.7.2 23.8.1 23.9.1)\n\nBroken: 3.6.1 LTS (On latest driver)\nWorked: 3.6.1 LTS (On old driver: AMD Adrenaline 23.5.2)\n\nAfter synchronizing objects, Blender crash\nBut render the default cube scene Blender works well even using 23.7.1 driver\n\nBased on the default startup or an attached .blend file (as simple as possible).\nScene is from Blender official demo file: \nbarbershop_interior/\nCrash log file: \n\n", "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" ]

[ "Blender 2.80 instant crash at start\nWindows 7, GTX 1070\n\nBroken: I cant see splash screen because its crashing so from download page: blender-2.80-4503c96a175-win64.zip, Nov 13 2018 06:17:42\n\n**Blender crashes instantly, unable to launch**\n\nSimply try to run it", "Blender 2.8 crashes on start up\nWindows 10 Pro 64Bit\nIntel(R) Core(TM) i3-4005U CPU @ 1.70GHz, Intel® HD Graphics 4400\n8 GB RAM\nGeforce nvidia 820m (Dedicated)\n\nBroken: Blender 2.8 64 bit windows latest build (blender-2.80-4503c96a175-win64, Nov 13 2018)\nWorked: (optional)\n\nBlender 2.8 Crashes instantly when launching\n\n1. Opened Blender 2.8 from windows start menu.\n2. Blender crashes instantly\n\nI took a screenshot of the startup console, and it shows some error.\n" ]

[ "Blender Instantly Crashes When Rendering Cycles Or Clicking Wrong Setting\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nCPU: 12th Gen Intel(R) Core(TM) i7-12700KF, 3600 Mhz, 12 Core(s), 20 Logical Processor(s)\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.1.230821\n\nBroken: version: 3.6.2\n\nWhenever Blender attempts to render in cycles mode it exits immediately. It doesn't try for a few seconds, there's no loading, just click and instantly the process dies. This happens whether Preferences>System>Cycles Render Devices is set to \"None\", \"HIP\" with my GPU selected, or \"HIP\" with my CPU selected. Regardless of the cycles render device setting when I turn on viewport shading it works as it defaults to Eevee. However, if I try to change it to cycles, the moment I click cycles Blender crashes.\n\nThis same instant crash happens when I try to click OptiX or CUDA in Preferences>System>Cycles Render Devices instead on None or HIP.\n\n\n- Start Blender with a default project\n- Press Z then 8 to go into rendering mode\n- On the sidebar click render properties\n- Click the dropdown to change render engine\n- Click Cycles\n- Should see it crash instantly\n\nTo see the settings crash\n- Start Blender with a default project\n- Navigate to Edit>Preferences>System>Cycles Render Devices\n- Click between None, HIP, and OneAPI without issue\n- Click CUDA or OptiX and see the instant crash\n\n", "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", "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", "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", "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", "Viewport animation render crashes when collapsing the viewport.\nBroken: version: 2.91.0 Beta (and 2.83, 2.80, ...)\nWorked: never\n\nViewport animation render crashes when collapsing the viewport.\n\n[0001-0485.mp4](0001-0485.mp4)\n[Viewport render crash.blend](Viewport_render_crash.blend)\n\n", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "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", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "Crash when 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...", "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)", "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", "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 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>", "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)" ]

[ "Blender keeps crashing randomly\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.90.1\n\nFrom Version 2.91.0 up Blender keeps crashing randomly, it has often been an nVidia Driver, but today three times in a row in the course of an hour it was the Blender.exe if I read the Crash Log correctly. If I have to narrow it down, I would say it happened a few times after a \"Ctrl+Z\" command. But thats not always the case.\nI attached the last Crash Logs. Thanks for the help\n[Lab_00_C.crash.txt](Lab_00_C.crash.txt)\n\n[Lab_00_A.crash.txt](Lab_00_A.crash.txt)\n\n[Lab_00_B.crash.txt](Lab_00_B.crash.txt)\n\n[10193_01_Marktplatz_A.crash.txt](10193_01_Marktplatz_A.crash.txt)\n\n\n\n" ]

[ "Rendering instability from Blender 3.5 to 36+\nOperating system: macOS 13.4.1\nGraphics card: Apple/AMD W6800X Duo\n\nBroken: 3.6 to 4.0\nWorked: 3.5.1\n\nI get substantial instability when rendering animation sequences in Blender 3.6 and above, compared to 3.5. For example, I've built a large scene with lots of assets and displaced ground material. Today I left Blender 3.5 rendering and have outputted all 250 frames without a single issue using the GPU.\n\nBut previously in 3.6 I get a variety of frames – sometimes 30 or 40, sometime just a single frame – before I have to reboot Blender and start the rendering process again. I've tried all sorts of tricks, like using tiling to render and even switching to CPU-only, but in all cases, the animation process will eventually crash Blender. I thought it might be a VRAM issue, but my dual card has 32GB! My Mac Pro is a standard system with 64GB RAM and no strange or non-Apple additions – it should be rock solid.\n\nI don't have one specific scene to give you, but I've experienced all manner of instability since 3.6 came out – there is obviously a core difference in the app from 3.5 to 3.6+. However, I am really keen to help find the culprit. If you let me know what you need, I can provide crash reports or debug information, just point me in the right direction. Thanks!\n\n", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Crash after linked object is edited then switched to another scene (object origin scene)\nOperating system: Window10\nGraphics card:\n\n\nBroken: 2.90.1 ( hash: 3e85bb34d0d7 )\nWorked: unknown\n\n\nBlender simply crash and close the window directly after editing the \"linked\" object from 2nd screen and switched back to 1st screen.\n\n\n\nThis error can be reproduced with 2 scenes setup.\n\n- First scene contains a simple mesh object. Let's say a \"Cube\" object\n- Create a second scene.\n- In the first scene, select the \"Cube\" object then \"Make Links\" {key Ctrl L} to 2nd scene.\n- Now, we switch to 2nd scene. The 2nd scene now should contains the same \"linked\" Cube object from 1st scene.\n- Okay, this is important step. In this 2nd scene, we select this \"linked\" Cube object and set the Relations to: *Object > Relations > Make Single User > Object*\n- After that, we go to \"Edit Mode\" for this \"linked\" Cube object.\n- In \"Edit mode\", make a simple change to this \"linked\" Cube object.\n- Once simple change is done, don't do anything else. You just directly switch back to \"First scene\". CRASH here.\n\n", "Blender 3.5.0 Win11 RTX3090 Fatal Crash on activating Cycles\n@deadpin thanks for replying.\n\nDriver Version: 31.0.15.3161 (NVIDA 528.24) DCH Win1164 installed\n\nCycles now working without issue thank u.\n\n_Originally posted by @Jaymi-McManus in /blender/blender/issues/106953#issuecomment-923094_\n\n>>>>>\n\nUpdate: \n\n1. Closed the ticket too soon, after adding some simple color, specular, metallic, changes in BSDF and then navigating between layout and other tabs, fatal crash occurs again\n\n2. Updated NVIDIA drivers to 31.0.15.3161 (NVIDIA 531.61) DHC / Win11 64 the issue still persists\n\nUpdate logs attached.", "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "Eevee randomly causes system to crash when rendering\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory)\nCPU: Intel Core i9 9900k\nRAM: 32GB DDR4\n\nBroken: 3.0.0\n\n\nI'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know.\n\nI have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash.\nThe amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory.\n\nI'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine.\n[ocean_final.blend](ocean_final.blend)\nThe scene makes use of a lot of volumetric light and I also calculate the bloom.\n\nThere aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here.\n\nAll drivers are up to date and I also reinstalled Blender.\n\nNot sure, but I attached the .blend file as well as logs created in debug mode.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "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", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "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 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", "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", "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Blender 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", "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" ]

[ "Blender 2.91.2 crashes randomly\nOperating system:\nWindows 10 Pro version 2004 build 19041.804\n\nGraphics card:\n(2) 1080ti\n\nBlender 2.91.2\nRandom, unexpected crashes. It suddenly closes.\nIt worked fine since its release but now it keeps crashing all the time. No new software added to the system and still using the same video card driver I've been using for a while — Nvidia 456.38 WHQL\n\nFound this in the log\n\n\n```\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FFC988CFDAD\nException Module : nvoglv64.dll\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x0000000000004F30\n\n\nStack trace:\nnvoglv64.dll :0x00007FFC986B2C70 DrvPresentBuffers\nnvoglv64.dll :0x00007FFC98588BB8 Symbols not available\n```\n\nAn update: this time the crash doesn't seem to be related to the GPU but Blender itself:\n\n```\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF6CF6C3139\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000018\n```" ]