I cant kill!!

by J-Francois on 01/27/2004 21:23, 55 messages, last message: 06/02/2004 09:41, 32196 views, last view: 05/19/2024 01:02

I can\'t kill monster. When a shot, its like a shot on a wall. Please help me!!!

   Board Index   

#1: re,,,

by Facechild on 01/27/2004 22:54

are you on multiplay or singleplay, if your on multyplay its mostlikly that you've lagged out of the server. :p as for single play i have no clue.

reply to this message

#2: Re: re,,,

by cubed|r3dr4t on 01/27/2004 23:49, refers to #1

´tell me your Graphic-card

reply to this message

#3: Re: re,,,

by J-Francois on 01/28/2004 00:08, refers to #2

I have a ati radeon 9500pro

fps around 250fps

Redhat 9 and gnome....

the same think appen in single an multiplayer..

reply to this message

#4: Re: re,,,

by Aardappel on 01/28/2004 01:21, refers to #3

ATI's linux driver's have problems with cube... I am working with ATI on this as we speak.

reply to this message

#5: Re: re,,,

by evilmrhenry on 04/23/2004 09:40, refers to #4

What is the current status on this?

Is there a workaround?

(got the same problem here)

reply to this message

#6: Re: re,,,

by jcdpc on 04/23/2004 12:16, refers to #5

I dont think there is, but i think it will be fixed really soon (like this week) because there's an april cube release. if you really really want to play, try jumping back and forth while you shoot, and you might hit something ... maybe.

reply to this message

#7: Re: re,,,

by Thalion on 04/23/2004 13:19, refers to #6

This won't help =)
Your only option is to wait for the new Cube release, or to play on Windows. Maybe Wine(X) can handle Cube? Didn't check...

reply to this message

#8: required opengl32.dll

by LavaBeam on 04/23/2004 16:09

www.dll-files.com or whatever and search for opengl32.dll(or opengl.dll but opengl32.dll is better)thats how i fixed the shooting problem to my windows 98SE

reply to this message

#9: Re: required opengl32.dll

by ph0ok on 04/23/2004 16:12, refers to #8

he uses linux ;)

reply to this message

#10: Omega drivers maybe?

by e:n:i:g:m:a on 05/02/2004 01:02

Maybe the Omega Drivers would work?? Are they even for linux? Hmmmmmm...

reply to this message

#11: still not fixed

by evilmrhenry on 05/26/2004 07:08

I just got the 20040522 version of cube, and the problem is still not fixed.

In addition, I tried it with WineX, and the problem exists there as well.

reply to this message

#12: Re: still not fixed

by D.plomat on 05/26/2004 10:16, refers to #11

Indeed it's not fixed with the new version of Cube, as the bug is not in Cube but in the OpenGL driver. If you know how to compile Cube you can propose Aard to do some testing on your machine.

About Wine, i don't know as i never used it, but i think when using OpenGL it probably uses back the Linux OpenGL, as a windows driver don't have direct access to the hardware on the Linux box, right? so if the graphics driver in Wine is only a redirector/converter to the Linux drivers it probably won't change anything... unless there is a way to allow the windows drivers direct access to the hardware?

reply to this message

#13: yup

by Aardappel on 05/26/2004 22:52

its a problem with the ATI linux drivers. Either ATI gets their act together and fixes it, or someone proposes an elegenant workaround (the current cube code contains such a workaround, but commented out because its not working).

reply to this message

#14: ..

by Thalion on 05/27/2004 06:34

> someone proposes an elegenant workaround

A not-very-elegant workaround was proposed in the thread where I posted my first report on this error. Simply speaking, just add a config option to enable this workaround by request. So, whoever has an ATI card, will have to edit the config. Not very good, but at least it'll work.

reply to this message

#15: Re: ..

by Aardappel on 05/27/2004 18:47, refers to #14

then please tell me what the actual workaround would be, i.e. what changes to code. Please test it before you tell me :)

rather than a switch, automatically enabling the workaround when it detects significantly wrong depth values (as I was trying in the current code) may be better... avoids a lot of FAQs

reply to this message

#16: ..

by e:n:i:g:m:a on 05/28/2004 02:25

Does anyone know if this bug is fixed for ATI cards in linux?

reply to this message

#17: ..

by e:n:i:g:m:a on 05/28/2004 02:25

Does anyone know if this bug is fixed for ATI cards in linux?

erm, for the 2004 release that is...

reply to this message

#18: Re: ..

by Thalion on 05/28/2004 16:10, refers to #15

Unfortunately the code was lost when I installed FreeBSD on the partition where Gentoo was =( However, as far as I remember, I just multiplied the Z-value returned by glReadPixels by 256

This however breaks the rendering for non-buggy drivers, that's why it has to be enabled with a switch.

reply to this message

#19: Re: ..

by Aardappel on 05/28/2004 16:18, refers to #18

if you look at the code, that is the fix I attempted... I guess what you mean the *256 should happen on the float in int representation, because doing it on the float itself does not work (the depth value is not linear).

As I said, it doesn't need a switch, I can simply detect the case.

If anyone wants to try this, let me know. They have to be available on irc a lot, know how to compile the source, and obviously run linux on ATI.

reply to this message

#20: Re: ..

by Thalion on 05/28/2004 16:28, refers to #19

I have SuSE 9.1 installed now (btw, a neat distro!), so I can check that. In 20 minutes or so.

Will you be on IRC?

reply to this message

   Board Index