I am also getting graphics corruption with both 4.5.0-beta1 and 4.5.0-rc1. I
am running 32-bit Vista.
I have the same settings as Miles when pressing '1' in qtdemo. When running
the demos, however, there seems to be no problem - only the demo app is
exhibiting this behaviour.
This did not occur in 4.3.x for me.
Is there any update to this problem on the Qt side?
"Miles Gazic" <miles.gazic@xxxxxxxxx> wrote in message
> All the examples in the opengl directory appeared to work, including
> the ones named "pbuffers", "pbuffers2", and "textures".
> When I pressed '1' in qtdemo, I got a window that said this:
> Rendering system: OpenGL
> Adapt: on
> Adaption occured: no
> OpenGL version: 2.0 or higher
> Color bit depth: 32
> Wanted FPS: 100
> Benchmarked FPS: not calculated
> Animations: on
> Blending: on
> Ticker: on
> Pixmaps: off
> Rescale images on resize: on
> Timer based updates: on
> Separate loop: no
> Screen sync: yes
> I haven't tried Qt 4.4.4 or disabling the pixelbuffer object
> extension, I'll post to the list again when I do.
> On Fri, Jan 23, 2009 at 1:55 AM, Trond Kjernaasen <trond@xxxxxxxxxxxxx>
>> Miles Gazic wrote:
>>> On a 2.8GHz Pentium 4, 1GB RAM, ATI Radeon HD 2400 Series video card,
>>> ATI driver version 8.471.0.0. Built qt-win-opensource-src-4.5.0-beta1
>>> from source using Visual C++ 2008 Express Edition with SP1.
>>> qtdemo has corrupted graphics, looks like when the horizontal sync
>>> isn't working on a CRT (but just in that window, the rest of the LCD
>>> is fine :D). Or like if you have textures and a framebuffer without
>>> the same pixel size. No command-line output or errors of any kind.
>>> The app ran without crashing, and I could click the UI (if I guessed
>>> the right place to click).
>>> Let me know if there's any other info needed.
>>> PS: Image here:
>> That looks bad indeed. If you press "1" while the Qt Demo is running,
>> you'll get information about which rendering system is being used. I
>> assume it's using OpenGL in this case. Do you see similar behavior in
>> any of the other OpenGL examples that's shipped with Qt? Do you know if
>> this happens with Qt 4.4.x on the same system?
>> It seems that the texture uploads are corrupted for some reason, and it
>> might be related to the pixelbuffer object extension we use to upload
>> textures (if it's supported by your card). You could try to disable that
>> feature by commenting out the check for it in src/opengl/qgl.cpp (lines
>> 1713-1719, in one of the bindTexture() overloads), recompile the GL
>> module and see if that helps.
>> Trond K.
>> Qt4-preview-feedback mailing list
Qt4-preview-feedback mailing list