Complete.Org: Mailing Lists: Archives: freeciv-dev: April 2006:
[Freeciv-Dev] Re: (PR#16431) [PATCH] cairo conversion of gtk2 client
Home

[Freeciv-Dev] Re: (PR#16431) [PATCH] cairo conversion of gtk2 client

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: patg@xxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#16431) [PATCH] cairo conversion of gtk2 client
From: "John Bauman" <john@xxxxxxxxxxxxxxxx>
Date: Sat, 22 Apr 2006 13:58:02 -0700
Reply-to: bugs@xxxxxxxxxxx

<URL: http://bugs.freeciv.org/Ticket/Display.html?id=16431 >


----- Original Message ----- 
From: "Christian Prochaska" <cp.ml.freeciv.dev@xxxxxxxxxxxxxx>
To: <patg@xxxxxxxxxxxxxxxxx>
Sent: Saturday, April 22, 2006 4:24 PM
Subject: [Freeciv-Dev] (PR#16431) [PATCH] cairo conversion of gtk2 client


>
> <URL: http://bugs.freeciv.org/Ticket/Display.html?id=16431 >
>
>> [guest - Sa 22. Apr 2006, 16:59:27]:
>>
>> > [cproc - Fri Apr 21 18:06:29 2006]:
>> >
>> > This made the terrain look right with the "nv" driver, so the image
>> > probably gets corrupted somewhere in the outcommented part.
>> >
>>
>> Commenting those lines put the sprites on the client instead of the GDK
>> surfaces (which are xlib surfaces). So the problem could be related to
>> these.
>> The patch I attached here creates 32 bits pixmaps explicitly. Maybe
>> we'll get some results. If that still doesn't work, a runtime check will
>> probably be required to see if offscreen pixmaps can be used.
>>
>> patg
>>
>
> It also didn't work with this patch. You mentioned 32 bits per pixel, so
> I tried switching video modes and it turned out the terrain was drawn
> correctly when I changed from 24 bit mode (maximum with nvidia drivers)
> to 16 bit mode and also when I changed the resolution in 24 bit mode
> from 1024x768 to 800x600 or 640x480. Also, in 16 bit mode the "high CPU
> load" problem disappeared.
>
It sounds to me like you don't have enough video memory to fit all the 
graphics, but Google says that your card has 64 MB of memory, which I would 
think should be enough for this. 





[Prev in Thread] Current Thread [Next in Thread]