Hi, <snip>
Uh, no, this doesn't help :-(
Half-life supports only 16bpp(well, I can set it to other values with regedit, but it seems to have no effect), fglrx supports 24bpp only.
No problem here.
I switched to the Xorg radeon driver which has 16 bpp support(the 2nd column shows 16 now), and made sure that hl runs with 16bpp, but the error still occurs.
Yes it don't work, because you speak about frame buffer (named Color buffer on traces) when you speak about 16bpp. I spoke about depth buffer <snip>
- Depth : 32 <---- Is half-Life still trying to get 32bpp?????
Yes, but not 32bpp for frame buffer only for depth buffer (usually Z-buffer)
But even if it worked this way, this wouldn't be a good solution for ATI users, because playing newer games with the "radeon" driver is horrible. (e.g. Jedi Academy, gl-117, even tuxracer makes problems).
Removing the failing check from Wine's opengl code doesn't help, it causes a hard crash later.
Yes because game expect 32bpp for Depth buffer and if game try to read directly into this buffer you'll have some problems Regards, Raphael
I switched to the Xorg radeon driver which has 16 bpp support(the 2nd column shows 16 now), and made sure that hl runs with 16bpp, but the error still occurs.
Yes it don't work, because you speak about frame buffer (named Color buffer on traces) when you speak about 16bpp. I spoke about depth buffer
Good, thanks for explaining this to me. I mixed the two buffers. Well, HL doesn't offer any depth buffer setting. There's only one console command, "gl_zmax", which is supposed to set the maximum depth buffer size. The default is 4096, and changing this value has no effect on the error.(HL still tries to get a 32 bit depth buffer) I sort of fixed the problem for me by forcing the depth buffer to 24 bit in dlls/x11drv/opengl.c, but I understand that this is not a real solution. Is there any chance for a better fix? I have no chance to fix this in the game nor in the video driver Stefan
On Saturday 07 May 2005 12:41, Stefan Dösinger wrote:
I switched to the Xorg radeon driver which has 16 bpp support(the 2nd column shows 16 now), and made sure that hl runs with 16bpp, but the error still occurs.
Yes it don't work, because you speak about frame buffer (named Color buffer on traces) when you speak about 16bpp. I spoke about depth buffer
Good, thanks for explaining this to me. I mixed the two buffers. Well, HL doesn't offer any depth buffer setting. There's only one console command, "gl_zmax", which is supposed to set the maximum depth buffer size. The default is 4096, and changing this value has no effect on the error.(HL still tries to get a 32 bit depth buffer) :(
I sort of fixed the problem for me by forcing the depth buffer to 24 bit in dlls/x11drv/opengl.c, but I understand that this is not a real solution. Is there any chance for a better fix? I have no chance to fix this in the game nor in the video driver
I will see how we can have a better fix but for now can you try attached patch ?
Stefan
Regards, Raphael
Am Montag, 9. Mai 2005 00:34 schrieb Raphael:
On Saturday 07 May 2005 12:41, Stefan Dösinger wrote:
I switched to the Xorg radeon driver which has 16 bpp support(the 2nd column shows 16 now), and made sure that hl runs with 16bpp, but the error still occurs.
Yes it don't work, because you speak about frame buffer (named Color buffer on traces) when you speak about 16bpp. I spoke about depth buffer
Good, thanks for explaining this to me. I mixed the two buffers. Well, HL doesn't offer any depth buffer setting. There's only one console command, "gl_zmax", which is supposed to set the maximum depth buffer size. The default is 4096, and changing this value has no effect on the error.(HL still tries to get a 32 bit depth buffer)
:( :
I sort of fixed the problem for me by forcing the depth buffer to 24 bit in dlls/x11drv/opengl.c, but I understand that this is not a real solution. Is there any chance for a better fix? I have no chance to fix this in the game nor in the video driver
I will see how we can have a better fix but for now can you try attached patch ? Works. How about adding a registry key to allow the user to force a specific depth buffer size, just like the key to disable certain extensions? I've seen that a few windows drivers offer such a setting.
Stefan
participants (3)
-
fenix＠club-internet.fr -
Raphael
-
Stefan Dösinger