ZOD said:
They were undocumented varibles in both Tribes and Tribes 2, had the Dev wanted people to mess with them they would have documented or at least added them to client prefs. There is NO REASON they should be mesased with. People did JUST FINE without knowing or adjusting those settings.
Lock the game down as much as possible, lax it up as required, but do not leave the damn flood gates wide open from the start ala Tribes 1 and 2.
Well, you would also think that if the Dev didn't want people to mess with them, they would have harded coded the values.
There *is* a reason that the value should be messed with, and that is to get a more accurate representation of where the players are.
Players with lower pings will be at the greatest advantage without the interpolate setting, since they already have a very accurate representation. If anything, I think that interpolate *evens* the playing field.
In regard to interpolate, the flood gates should be left wide open from the beginning (make the interp setting changable in the GUI for T:V, out of the box), in order to make future "floods" concerning interpolate impossible.
TeckMan said:
Hard code the interp settings. This game shouldn't be about who can bear playing with the jerkiest game.
It should be up to the *user*
Following your reasoning, the graphics setting should be hard coded to the lowest settings for all players (regardless of what your computer can handle).
"This game shouldn't be about who can bear playing with the *lowest FPS*" ??
By increasing your graphics setting, you generally improve the visuals of the game at the cost of decreased FPS (increased jerkiness).
The interpolate setting is analogous -- By decreasing the interpolate value, you generally get a more accurate representation of where the players are, at the cost of increased jerkiness.
There are advantages and disadvantages for both sides of the spectrum, and it should be *up to the user* to decide what side he/she prefers.
