Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses repeated eglSwapBuffers failed with 0x300d warnings when opening the Lighthouse tab by preventing vispy from performing an extra buffer swap that Qt already handles when embedding the canvas.
Changes:
- Disable vispy’s automatic buffer swapping for the Lighthouse 3D scene canvas by setting
autoswap=FalseonSceneCanvas.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ArisMorgens
force-pushed
the
Aris/vispy_warning
branch
from
8779b4f to
89c91e1
Compare
gemenerik
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When opening the Lighthouse tab, we repeatedly get this warning:
This is caused by Qt and vispy trying to do the same job.
Specifically, vispy draws the 3D scene into an offscreen buffer (FBO), not directly onto the screen.
Qt has a built-in mechanism where after vispy finishes drawing into the FBO, Qt takes that image and puts it on screen by itself.
Then, vispy, by default, also tries to put the scene on screen itself after every draw. That's caused by the
autoswap=Truedefault. But since Qt is already doing it, vispy's attempt is redundant and that's where we get the0x300derror.