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

Eplieptic Graphics Overload #2

Open
nyghtly-derek opened this issue Oct 9, 2019 · 5 comments
Open

Eplieptic Graphics Overload #2

nyghtly-derek opened this issue Oct 9, 2019 · 5 comments
Assignees

Comments

@nyghtly-derek
Copy link

System information:

image

Description of bug:

The application's graphics immediately malfunction upon opening, blinking excessively between many different colors.

The loop can be stopped by pressing L. After that, the application works correctly, allowing the user to draw and delete lines, etc.

I believe this bug is probably specific to Windows 10.

@nyghtly-derek
Copy link
Author

A simple way to prevent this bug might be to clear the screen in between drawing loops, or to clear the screen immediately upon opening the window.

@Liby99
Copy link
Owner

Liby99 commented Oct 9, 2019

Thanks so much for reporting the bug! I'm trying to reproduce it on my windows machine...

@Liby99 Liby99 self-assigned this Oct 9, 2019
@nyghtly-derek
Copy link
Author

@Liby99 I have access to another Windows machine--I'll try and reproduce it on there as well.

@tonnylyz
Copy link
Collaborator

@nyghtly-derek Hi! I have also tried reproducing on my Windows machine. Though I once saw some weird cyan colored canvas when sketching on it, I cannot reproduce it anymore.

I think this is an upstream library bug regarding back end/GPU, and we can do so little.

I also released an alpha build for Windows x64, you can test it. We very appreciate for your feedback and bug reporting.

@nyghtly-derek
Copy link
Author

Just tested the master branch on my other windows machine. No graphics glitch detected this time.

Here are the specs:

image

Worth noting that the computer with the glitch was using onboard intel graphics whereas this computer has a dedicated graphics card.

Might be worth reporting this upstream. I assume Piston is the relevant crate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants