General Thread

by Aardappel on 01/05/2002 01:55, 15499 messages, last message: 12/08/2021 21:22, 8825804 views, last view: 12/09/2021 01:14

for questions, announcements etc.

   Board Index   

#1610: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Jorge on 06/15/2003 13:43

That's my hardware/software:

* Pentium III, 666 MHz, 256 MB ram
* Voodoo 3 2000 PCI, 16 MB
* Kernel 2.4.18 and XFree86 4.2.0 with DRI/GLX, they are configurated properly (Quake3 runs nicely)

This is the bug:

I don't see the water texture. Fonts and icons aren't showing too. The screenshot: http://lilo.uah.es/images/cubebug.png

Thanks in advance :)

reply to this message

#1611: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Jorge on 06/15/2003 15:15, refers to #1610

Fonts fixed, water don't.

The maximum texture size for Voodoo 3 is 256x256. 'newchars.png' is 512x512: i've resized the image. The fonts are showing now.

The water texture is hardcoded and i don't know how resize it.

Please, can you write a patch?

reply to this message

#1612: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by pushplay on 06/15/2003 21:50, refers to #1611

Spend the extra fifteen bucks and get a geforce2(mx). Your entire life will get better if you do.

reply to this message

#1613: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Jorge on 06/15/2003 22:42, refers to #1612

Oh... I can't live without "hibernate", and the Linux nvidia driver doesn't support that feature.

Seriously, a Geforce2 is too expensive for me (130 €! I could pay for English lessons with this money).

OTOH your donation will be appreciated X)

More ideas?

reply to this message

#1614: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by pushplay on 06/16/2003 00:51, refers to #1613

130? What the heck?

http://search.ebay.com/search/search.dll?cgiurl=http%3A%2F%2Fcgi.ebay.com%2Fws%2F&krd=1&from=R8&MfcISAPICommand=GetResult&ht=1&SortProperty=MetaEndSort&query=geforce2+mx

reply to this message

#1615: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Jorge on 06/16/2003 11:04, refers to #1614

Ebay is a shop far, far away. Too expensive shipping costs.

I come from Afri^H^H Spain, live in a near-to-where small village, and i hasn't got a car.

My motherboard doesn't have an AGP port and the local seller sells 3D Blaster PCI (geforce2 mx 400) for 124,99 € only.

It's a sad story, isn't it? :)

Thanks for your interest but i will write the patch, if nobody writes it first, because:

* Cost for patch: 0 € (I must only study OpenGL %}).
* Cost for Geforce2: X €

Note: X > 0.

My 4 years old Voodoo works fine except for Cube. I have the manual with technical specs. Why change?

reply to this message

#1616: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Jorge on 06/16/2003 13:42, refers to #1615

Sorry, i mean "near-to-nowhere" small village :).

Gasp! your ebay link is too long. You broke this forum 8)

reply to this message

#1617: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Aardappel on 06/16/2003 14:33, refers to #1610

this is not a problem with the v3, but with the linux drivers. On windows the textures are correctly scaled down.

Maybe for next release I will integrate a workaround.

reply to this message

#1618: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20

by Jorge on 06/16/2003 15:09, refers to #1617

Thanks! if you need a betatester for the workaround perhaps i can help you :)

reply to this message

#1619: problem with cube

by fulltimepc on 06/16/2003 21:05

hi! I get the following error when running cube_unix, WARNING: cannot use overbright ligthing using old ligthing model, and them cube show only 256 color where is the problem? I have mandrake 8.2 running en HP vectra 400

please help me!!!!

reply to this message

#1620: Re: BUG: Linux/Voodoo 3 2000, Cube 2002_10_20 (SOLVED)

by Jorge on 06/16/2003 23:00, refers to #1610

Finally, Cube works fine with Voodoo3 on Linux, although the driver is broken. I resize the images, mantaining aspect ratio:

packages/golgotha/water2.jpg
packages/payne/Brick58_512x512.jpg
packages/models/monster/bauul/skin.jpg
packages/models/monster/rhino/skin.jpg
data/newchars.png

The maximun size of textures is 256x256.

reply to this message

#1621: Jorge

by pushplay on 06/17/2003 00:36

You're really getting screwed over there for video card prices. There's a Spanish eBay you might want to check out.

http://search.es.ebay.com/search/search.dll?MfcISAPICommand=GetResult&cgiurl=http%3A%2F%2Fcgi.es.ebay.com%2Fws%2F&ht=1&SortProperty=MetaEndSort&ebaytag1code=186&shortcut=4&maxRecordsReturned=300&maxRecordsPerPage=50&SortProperty=MetaEndSort&image2.x=0&image2.y=0&image2=Find+It&query=geforce2

reply to this message

#1622: Ok

by pushplay on 06/17/2003 00:36

Now I really broke it.

reply to this message

#1623: Re: Jorge

by Jorge on 06/17/2003 11:37, refers to #1621

The shipping costs are only for "Peninsule and Baleares Isles", i live en Canary Isles: in the middle of Atlantic ocean, 4" from tropic of Cancer, in front of the Moroco's sahara coast, 1400 KM from south of Spanish peninsule.

This cards (i've read the link) are in Valencia (1800 KM) and Barcelona (2300 KM).

By the way, there are Geforce2 cards for 45/50€ here... But no PCI, and i haven't AGP port.

Well, the next time i travel to peninsule, i can buy a Geforce2.

is it a thymus?, it's probably.

reply to this message

#1624: Re: Jorge

by Jorge on 06/17/2003 12:02, refers to #1623

Ehem...

Thymus->swindle

reply to this message

#1625: Re: problem with cube

by Jorge on 06/17/2003 12:41, refers to #1619

What is your videocard?

Open a console and try this:

$ glxinfo | \
grep GL_EXT_texture_env_combine

If you don't see anything is "normal" than you can't use "overbright lighting" (Your hardware/driver doesn't support it).

Try:

$ glxinfo | grep ^direct

If you don't see "direct rendering: Yes", your videocard is misconfigured.

Do you can play to "Tux Racer", "Armagetron" (other 3D game)?

reply to this message

#1626: Aard, you're a smart guy. riddle me this...

by pushplay on 06/19/2003 12:33

I thought 32 triggers was enough for any map, but I was wrong. So I wanted to code up a general method constructing a menu listing from i to i+16 entities, and a final menuitem "more..." which would call the method again listing i+17 to i+33 entities and so on for infinite depth. Entity name and an argument listed as parameters. I coded it up in the way which seemed natural, but forgot that $arg# is global and bound at run time. So I didn't get the results I wanted. After some head scratching I can't think of another way to do this. Is there?

reply to this message

#1627: Excessive latency?

by Jorge on 06/20/2003 01:19

I've been playing Cube on official servers, with ~110-250 ping time and my bullets don't touch other players: i shoot them (instgib) but anything doesn't happen, they don't die.

If the other player is quiet and i am in front of him, i need ~15 shoots for kill him (instgib mode!).

What is the problem?, excessive ping time?. I think that 140 ms isn't much time, isn't it?, cheating?, is it a bug of linux_client? (i'm using "cube_linux_clients_2002_10_28.tar.gz")
or ... a punishment for annoying you?, am i so bad?.

reply to this message

#1628: Re: Excessive latency?

by Thalion on 06/20/2003 01:32, refers to #1627

It's a known bug in Cube.

Actually, since most calculations are done client-side, you hit people _immediately_. There's no delay regardless of your lag and/or packet jump. So, as soon as you hit someone in instagib, he should die (for you, at least).

Sometimes, however, it happens so in instagib that a player becomes invincible. I had experienced it myself for two times. Dunno why it happens at all, and why only in instagib and not in any other mode (or maybe it does, I just haven't seen it?). Anyways, the best thing you can do in this case is to restart the match.

reply to this message

#1629: Re: Excessive latency?

by D.plomat on 06/20/2003 10:31, refers to #1628

Well, i think the client shooting validates the hit, send it to the client shooted, which calculates the health amount he loses, eventually dies and send it back to other players, so you can see a player dying 2*ping later after you shoot at him. this explains "mutual kill", in insta, even if the rifle is direct hit. Also if a player have a HUGE lag, he is stalled here, each time u shoot at him, you send him the info that he was hit, and he'll die only when it's connection gets back to normal -or disconnected ;)-. I may be wrong, but i think shooting at him is useless, and he may even already have been fragged by another player, just that he didn't had time to die ;)
For the invincibility, i experienced it one time... i began wondering when i used my 99 rifle ammo, and finished the round using the gauntlet, and tryed to get killed to start a new life with plenty ammo :)
In this case, you can just... notice the player, most of the time he will disconnect/reconnect

reply to this message

   Board Index