Does the infamous T2 red-jack apply?
by Oliver Seiler · in Torque Game Engine · 10/06/2001 (12:16 am) · 5 replies
Given that the most recent T2 patch seems to have basically screwed the game for me, it brings up the point in my mind of whether Torque could exhibit the same problems.
The original Tribes 2 red-jack issue was that it would occasionally stop updating the screen, displaying the network lag icon (a red jack); there was never an obvious fix for this, and eventually it went away (at least for me) from one of the patches. The latest patch, however, has seemingly introduced the same problem but much more annoying in it's frequency.
Do any of the GG people have anything to say about these issues and whether they would affect the Torque engine? Obviously you guys probably haven't had anything to do with the latest patch from Sierra, but I'd like to have some idea of a) what caused/causes these problems, and b) how/whether they can be avoided. It definitely appears to be a problem with code as opposed to people's hardware.
Cheers
Oliver
The original Tribes 2 red-jack issue was that it would occasionally stop updating the screen, displaying the network lag icon (a red jack); there was never an obvious fix for this, and eventually it went away (at least for me) from one of the patches. The latest patch, however, has seemingly introduced the same problem but much more annoying in it's frequency.
Do any of the GG people have anything to say about these issues and whether they would affect the Torque engine? Obviously you guys probably haven't had anything to do with the latest patch from Sierra, but I'd like to have some idea of a) what caused/causes these problems, and b) how/whether they can be avoided. It definitely appears to be a problem with code as opposed to people's hardware.
Cheers
Oliver
#2
10/06/2001 (8:47 am)
Nope, the problem was definitely just with T2; generally everyone getting it had no problems with any other game except for Tribes 2. Perhaps it is related to something on the users machine (drivers perhaps) but based on the symptoms it't getting triggered only by T2...
#3
10/06/2001 (10:15 am)
Haven't heard of this problem related to T2, it's very possible this bug is in the Torque engine. Sometimes it's hard to track down bugs that don't manifest them selves on any machines we can test on, but if we run into it, or get a lead on it, we'll fix it. We're also in a little different situation now with the TGE. With the source available, you could to track down this problem yourself :) That would be much appreciated :)
#4
10/09/2001 (8:30 am)
As far as I can remember the original "red jack" problem was fixed in the second patch for T2. I can't remember what the problem was but it was fixed. Torque does not seem to have the problem. I haven't played T2 in a couple months and I have not patched it since then. Maybe they have re-introduced something that is causing the problem. Have you looked at the various forums for information on this? 
#5
10/09/2001 (11:30 am)
According to the community, the Red-Jack was reintroduced in the latest "final official patch". I've pretty much seen the entire QA cycle of T2. I was on the Beta, the Meta and waited through most of the patches. The majority of the major Red-Jack issues I witnessed and heard within the community, where addressed and fixed almost immediately. And the only time I really saw it was after a patch (if at all). I can pretty much guarantee it's a scripting problem accidently introduced by Dynamix. I highly doubt you'll run into it on the base Torque, other than in your own tweaking or bad server connection. But like Tim says, you can track it and kill it yourself if you find it. :) 
Torque Owner Ace
What it boils down to is the pj is more then likely user related.