Opened 13 years ago
Closed 18 months ago
#7790 closed bug (not reproducible)
Rendering Issues with VESA driver
Reported by: | Prognoz | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Graphics | Version: | R1/alpha3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Sometimes seems that the screen is not updated correctly, just partially, and some glitches appears. If i move the window application forcing the refresh of the screen the problem disappear. I've tested with a nightly build from 18 June and i couldn't replicate the problem. Also i tested this on a VM and running from the live CD and happened on both cases.
Attachments (4)
Change History (7)
by , 13 years ago
Attachment: | Screenshot 48.png added |
---|
by , 13 years ago
Attachment: | Screenshot 51.png added |
---|
by , 13 years ago
Attachment: | Screenshot 50.png added |
---|
comment:1 by , 6 years ago
by , 6 years ago
Attachment: | glteapot.png added |
---|
comment:2 by , 6 years ago
A really long time passed since i reported this, so i don't remember exactly what i tested. I installed again the last nightly build on VirtualBox and i still encounter some rendering issues. I'm not sure why i said it was a VESA driver issue, but i think that i tested with other driver and that particular issue was not present.
What i can easily see failing one of the things i posted 7 years ago: GL Teapot if i stop the teapot rotation ( stops refreshing the framebuffer ), and i move the mouse over, the mouse rectangle fills the framebuffer with black ( it looks like if the GL framebuffer were the frontbuffer ). Wonderbrush also failed in a similar way but i can't reproduce it again.
I don't think this issue should be still open, i will probably make more sense just to open an issue with the GL Teapot error.
Thanks.
comment:3 by , 18 months ago
Resolution: | → not reproducible |
---|---|
Status: | new → closed |
Closing as requested. The various isues with GL Teapot are caused by BDirectWindow and lack of hardware cursor support and are already tracked elsewhere.
Still an issue? Also, that looks more like an app_server problem than VESA, but I could be wrong.