To answer a question posted above - the rubber-banding is a performance issue and thus is better or worse depending on your computers ability to keep up with loading.
Quote:
Originally Posted by Diernes
This never happened to me at all in the original game, obviously something was done to the engine for IT. Cant you just reverse that change? Surely the content loading is not fundamentaly different from the original game.
|
Yes, this is true. The rubber-banding was introduced inadvertently as a result of an attempt to fix the stuttering / hitching that some people complained of in TQ. However, as good intentions often do, this fix seems to have gone horribly wrong. This is an unfortunate example of the risks involved in patching / making changes late in a project. Occasionally you hear of companies releasing with a known bug and it seems horrible that they would do such a thing. However, once you get too close to a release date it is very difficult to delay even if the publisher wanted to because of marketing schedules and commitments to retailers. So developers end up in a situation where they need to assess the risk of attempting a late fix or releasing with a known problem. Our revisions to the loading system were not working correctly and we did not want to release with a known bug so we attempted a fix. You know how this story ends of course, we got burnt and the rubber banding effect was introduced and not caught in what time we had left to test before release.
I'm not a programmer, so I don't know the specifics but I'm told it isn't as simple as just reverting back. Extensive changes were made to implement the new loading system and the programmer that worked on them has since left the company. We could still try to revert back but it seems like it might be better to try and fix the current implementation, which should hopefully eliminate the hitching of TQ and the rubberbanding of TQIT.