[quake3-bugzilla] [Bug 4774] Railgun trace bug when shooting at long range

bugzilla-daemon at icculus.org bugzilla-daemon at icculus.org
Sat Nov 20 07:25:06 EST 2010


http://bugzilla.icculus.org/show_bug.cgi?id=4774

--- Comment #2 from Gig <thegig at supereva.it> 2010-11-20 07:25:01 EST ---
It seems that this may not be only a "graphic" bug, but also that the railgun
does NOT hit anything over a certain distance: its range seems shorter than the
range of the machinegun (it's a server-side thing, so changing cg_oldrail cvar
makes the trace seem normal, but you don't hit anything anyway).

In this thread on the OpenArena forums
http://openarena.ws/board/index.php?topic=3996.0
it has been told that the railgun range is 8192 units, while the machinegun
range is 8192*16=131072 units.

But OpenArena took part of its code from Team Arena, and someone says that for
Team Arena it's id Software that shortened the range of the railgun, maybe to
avoid extremely far frags in the three "mpterra" maps.

I'm sure that the standard baseq3 has got the "graphic" part of the bug, but I
don't know it it has got also the "short range" shot or it is only part of Team
Arena.

Maybe, if the railgun range is 8192 and you will not change this (I don't know
if ioquake3 makes such kind of changes), it would be better to maintain the
graphic bug, too... to be able to argue if your shots are useful or useless
when shooting at very long distances (but only if you use cg_oldrail 0). Fixing
the graphic bug and adding a "too far" or "out of range" message after such
kind of shot would be a more elegant solution.

-- 
Configure bugmail: http://bugzilla.icculus.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the quake3-bugzilla mailing list