I can't imagine why that would cause everything else to be redrawn, but you can just redefine SensorHud::update somewhere that loads later (something like scripts/autoexec/zsfds.cs would suffice if you don't care).  Just putting in a line like this should stop it fine:

Code:

function SensorHud::update(%this) {}

Or you could go into the original function (in hud.cs) or the packaged one (in freeHuds.cs) and add "return;" before it runs anything... but it's probably simpler just to put in the line I mentioned if you don't know how to mess with the scripts. :p

Me, I'm usually just sporting a construction tool.  :p

I am a pretty good at long-shot mortars though, and am pretty fond of immolating people with plasma rifles.

I run on a 4870 myself (though not an X2, and on XP), which runs the game flawlessly.  The only time its had any issue with the game was with adaptive AA enabled, and even then it was just a few artifacts in the GUI.
Other than what's already been mentioned though, I can't think of anything at the moment that might cause that.

Did you turn off $Host::CRCtextures in the serverprefs as mentioned previously?

Well, there's no saying for certain when it could be added in, but once the groundwork is laid it should go along quick enough. 
While we won't be adding maps to the core patch download, we wouldn't be opposed to featuring files such as map-packs on the downloads page.  We had planned to have more extensive web features up by this time, but unfortunately I had a few other things come up, so didn't have the time...

Yes, as Eolk mentioned, the CRCTextures option is your most likely culprit and most common cause of disconnections of this sort...  I suppose the next down would be adding new datablocks while the game is in progress. :p
The AI errors shouldn't be a problem.

Yeah, for once it really was unavailable...  We will probably have a status check on the site pretty soon to ensure there're no mix-ups like this in the future.

Sorry for the inconvenience.

The errors you get aren't that they don't exist, but that they are in use.  Open up your task manager (Ctrl-Shift-Esc) and click "Processes", then find and end all instances of "rubyintersect.dll", and you shouldn't have any trouble re-installing or updating the patch if need be.
However, the server listing does not have anything to do with these DLLs.  Failure to retrieve the list is almost always caused by an antivirus program blocking the traffic as mentioned in the FAQ entry, but there has been some debugging and a possible fix should be in a mini update sometime this weekend.  If you think this fix might benefit you before this is up, you can send me a message on here or IRC to get a work-in-progress package.

We played this a bit when T2o was still up, so I should still have the installer saved... here: http://www.tribesnext.com/krash/SMASH.exe
I'm not sure if it's the final version, of course.

Peter, you need to install the patch after installing the game.  There is no update search if you've installed it correctly.

rb10, the server is not down.  Your problem is unrelated to this one... if you are able to retrieve the server list, it is mostlikely unrelated to the patch and you may want to try restarting the computer.  If you are unable to retrieve it, you should check the FAQ post regarding HTTP filtering.

Find the directory you installed to (usually C:\Dynamix\Tribes2), right-click it, and click delete.

You might want to add an exception for admins,

Whoops! Good catch. :p

If you're looking to stop fake votes you could do something similar to that Blak, but I wouldn't replace the entire function unless you know exactly what you're doing.

Yeah... skiing was really implemented as a part of the game this time around.

Just one.  Do not end the ruby intersect task.  You won't be able to generate a key without it.

This can happen if the IPv4 acquisition fails, or is set to an address other than the one reported to the list.

Try setting $Host::BindAddress or $IPv4::InetAddress to "72.76.21.8" and see if it works.