I take this is a result from the CS library and not something intel put in their own drivers... I've installed the latest driver version. Most of the demo applications with CS run perfectly, however, with the walktest I get some flickering issues. A screenshot can be found at: http://www.science.uva.nl/~tlmkaste/csbuggy.jpg and the verbose output dump can be found at: http://staff.science.uva.nl/~tlmkaste/output.txt
My questions: Why is the card referred to as buggy?
Is there a work around to get rid of the flickering?
During initialization it is also mentioned that:
crystalspace.collisiondetection.opcode:
OPCODE WARNING: found 6 degenerate faces in model! Collision might report
wrong results!
OPCODE WARNING: found 14 degenerate faces in model! Collision might report
wrong results!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My system has a Intel 82945G express graphics card, when I run the walktest demo it prints the following during initialization:
crystalspace.canvas.openglcommon.driverdb:
Applied: Intel: Extreme Buggy Graphics
I take this is a result from the CS library and not something intel put in their own drivers... I've installed the latest driver version. Most of the demo applications with CS run perfectly, however, with the walktest I get some flickering issues. A screenshot can be found at: http://www.science.uva.nl/~tlmkaste/csbuggy.jpg and the verbose output dump can be found at: http://staff.science.uva.nl/~tlmkaste/output.txt
My questions: Why is the card referred to as buggy?
Is there a work around to get rid of the flickering?
During initialization it is also mentioned that:
crystalspace.collisiondetection.opcode:
OPCODE WARNING: found 6 degenerate faces in model! Collision might report
wrong results!
OPCODE WARNING: found 14 degenerate faces in model! Collision might report
wrong results!