Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Twinkling display bug on Win8 laptop with AMD 7650M #25

Closed
rossant opened this issue Aug 18, 2013 · 9 comments
Closed

Twinkling display bug on Win8 laptop with AMD 7650M #25

rossant opened this issue Aug 18, 2013 · 9 comments

Comments

@rossant
Copy link
Member

rossant commented Aug 18, 2013

I have a display bug on a new Sony VAIO laptop with Windows 8 64 bits and an AMD Radeon HD 7650M GPU (tried with latest stable Catalyst driver and beta driver 13.200). In all examples, the window alternates between the background color and the scene (2-4 times per second). This bug does not occur on other graphics libraries (e.g. Galry).

@campagnola
Copy link
Member

On all backends as well?

@almarklein
Copy link
Member

This might be related to the autoswap functionality that I added this weekend. If you remove the call to swap_buffers(), is the effect gone?

@rossant
Copy link
Member Author

rossant commented Aug 19, 2013

@lcampagn Ah, good idea. I just tried spinning cube with different backends:

  • pyglet: same issue
  • glut: works great
  • qt: same problem

@rossant
Copy link
Member Author

rossant commented Aug 19, 2013

@almarklein yes! removing the call to swap_buffers makes it it work on all backends. So this issue does not occur on any of your computers?

@almarklein
Copy link
Member

I only tested on Linux. But all backends work ok. I was actually surprised, because I expected problems if you swap buffers twice.

Ok, so now we know that swapping buffers twice should be avoided. We could make Canvas.swap_buffers() only work if the autoswap flag is off, so that the examples would just work. But I think we should accept this "problem" and fix the examples as soon as we have a new release.

@almarklein
Copy link
Member

@rossant Can we close this?

@rossant
Copy link
Member Author

rossant commented Aug 26, 2013

Is the auto-swap thing fixed on all machines? I think someone had an issue
yesterday on Windows during the sprint?

2013/8/26 Almar Klein notifications@github.com

@rossant https://github.com/rossant Can we close this?


Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-23250234
.

@almarklein
Copy link
Member

Yeah, but the issue was that he was accidentally using an old installed vispy 0.1.0

@rossant
Copy link
Member Author

rossant commented Aug 26, 2013

Oh yes you're right! Anyway the examples work fine now, I guess we can close this.

@rossant rossant closed this as completed Aug 26, 2013
djhoese added a commit to djhoese/vispy that referenced this issue Mar 15, 2020
…deep-1.3.2

Bump mixin-deep from 1.3.1 to 1.3.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants