[Bug] Blender still broken on driver 2.6.2
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, rust
Research direction
The report links #321 and an attached video, but names no source files or tests. Start by reading #321 and reviewing the supplied logs and video to identify which failures share a cause; reproduce the Blender crashes and rendering issues on driver 2.6.2. Done means the reported Blender workflows work reliably, including mesh editing, video import, Eevee rendering, cloth simulation, and texture painting.
Written by the indexing model from the issue text.
Description
Send logs report ID
NM-FYA1V88P, NM-T7HX2M5E, NM-KBV603PZ, NM-QG14F0GK, NM-HQTX7NY7, NM-KGQNKN71, NM-VHRNK2YQ, NM-VHRNK2YQ, NM-3J4WTWM9, NM-TG39CY04, NM-C7BKCBEZ, NM-QBX0R2CM, NM-YWKZ02FJ, NM-FSJPNND5, NM-0R9P04W1, NM-EK6H1HF2
Where does it go wrong?
An app or game
What happens
Like #321
Blender still crashes when trying to edit the mesh via edit or sculpt mode, while many of the basic modifiers that do the same work.
https://github.com/user-attachments/assets/82bf2a96-f150-41f3-a47a-ab08046b876f
Some more issues I found:
Many UI elements don't render,
It crashes similarly in the video editor when importing a video,
The Eevee renderers all black (cycles is fine),
Cloth sim crashes,
Texture painting is kinda messed up, it doesn't initially appear in the viewport and you need to reload it
Written by you
- I wrote this report myself. AI-written issues are closed without review (see CONTRIBUTING.md).
App or game (if it is one)
Blender
Did you change anything yourself?
No
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- Avg merge
- 21h 20m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nullmoth/nvidia-macos-driver
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
nullmoth/nvidia-macos-driver#419 · 1 comment ·
Maintainers usually reply within 2 days
-
[Feature] Support Hyper-V GPU Partitioning (GPU-P) / VMBus Paravirtualized & SR-IOV vGPU devicesOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
nullmoth/nvidia-macos-driver#417 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
nullmoth/nvidia-macos-driver#416 · 1 comment ·
Maintainers usually reply within 2 days
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
component:benchmark
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agentic-os-org/ANOLISA#9177 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oracle/rust-oracledb#61 ·
-
bug priority-medium to-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Databricks tool-only response crashes in resolve_reasoning_and_content with KeyError: contentPossibly taken @1divyanshdev claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
BerriAI/litellm#48637 · 2 comments ·
Maintainers usually reply within 1 day