[Bug] Flickering when moving/interacting with the Simulator window (RTX 5070 Ti)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- desktop, operating-systems
Research direction
Start with the documented -nvrmnoflip workaround in README/TROUBLESHOOTING.md and test whether it changes the Simulator flicker on the reported RTX 5070 Ti setup. The issue does not identify a driver source file or test; use the supplied log stream command to reproduce the capture-session errors. Done means documenting or fixing the cause so moving, interacting with, or refocusing the Simulator no longer causes flickering.
Written by the indexing model from the issue text.
Description
Send logs report ID
Pending — Send logs to NullMoth fails on every attempt (3x, same error each time) with "The server did not confirm the report bytes" for every file, including small ones (collection-errors.txt, driver-state.txt). Network side confirmed clean: 0% packet loss ping to nullmothsystems.com, clean TLS/HTTP2 handshake to the main site. Looks like a server-side issue with the log-upload endpoint specifically.
Where does it go wrong?
On the desktop (flicker, lag, displays, sleep)
What happens
On a Hackintosh with an RTX 5070 Ti (nvidia-macos-driver 2.3.6, installed/updated via the 1401 Mac app), Xcode's iOS Simulator shows heavy flickering and rendering corruption whenever the Simulator window is moved, dragged, or interacted with (clicking inside it, or when it loses/regains focus). It makes the Simulator basically unusable for normal iOS development.
macOS: 15.8.1 (build 24H32) — Sequoia, one of the versions listed as tested in the README.
While reproducing it with:
log stream --predicate 'process == "Simulator" OR process == "CoreSimulator"' --level debug
every window activate/deactivate cycle logs this pattern:
Simulator: Terminating capture support for coordinator '<DeviceCoordinator: 0x...>'
...
Error Simulator: Failed to try resuming capture session: <private>
This suggests Simulator's internal frame-capture session (the one that pipes the virtual device's framebuffer into the host window) fails to resume cleanly when the window becomes active again, which lines up with the visible flickering.
Screen recording of the issue is attached below.
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)
Xcode / iOS Simulator (Simulator.app, Apple)
Did you change anything yourself?
Haven't tried -nvrmnoflip yet (I saw it's the documented fix in the project's own README/TROUBLESHOOTING.md for "desktop flashes or tears while the cursor moves", but haven't tested it on this Mac).
Used an AI assistant (Claude, in Claude Code) while diagnosing this: it pointed me to the -nvrmnoflip entry in your docs and suggested capturing log stream output on the Simulator/CoreSimulator processes to narrow down where the flicker was coming from (see the capture-session log pattern above). No EFI/config values were copied from anywhere else.
https://github.com/user-attachments/assets/34ea8e15-7e66-49dc-8ea5-b70250b1d842
- 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
-
[Bug] `nullmoth-wsreset.sh` never restarts WindowServer at the real login window: `/dev/console` is `_windowserver`, not `root` (guard + test blind spot)Possibly taken A pull request linked to this issue is open or already merged. Open
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
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nullmoth/nvidia-macos-driver#326 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nullmoth/nvidia-macos-driver#325 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 24/100
nullmoth/nvidia-macos-driver#324 · 2 reactions ·
Maintainers usually reply within 2 days
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
area:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aaif-goose/goose#13031 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
meta.json, text.txt and try JSON are written non-atomicallyPossibly taken @qwertymuzaffar claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
qwertymuzaffar/parrot#47 ·
Maintainers usually reply within 1 day
-
priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
storytold/photocraft#8041 · 1 comment ·
Maintainers usually reply within 1 day