"igazor;c-17549108" wrote:
Okay, some corrections to this Important PSA if I may. :)
1 - We have always advised fps capping for cards strong enough to throw frame rates above the refresh rates of one's monitor. That's most dedicated cards today and even some integrated ones, hardware has come a long way since 2009. This is not optional and failing to take TS3 not having a functional built-in fps limiter into account will not only lead to very poor game performance, but is dangerous as it can lead to the card burning out entirely and also damaging the system board on which it is installed. However, I have to push back on not using vertical sync. While vsync alone is often not enough, it together with triple buffering is often where to start and then one way or another usually a max frame rate does need to be set.
These steps are vitally important, I would say required, but not sufficient alone for many players to experience buttery smooth gameplay in all instances. Thus we have the mods, route-fixed worlds, and other tools available to us to help maintain gameplay.
http://www.nraas.net/community/TIPS-FOR-BETTER-GAME-PERFORMANCE
Not all players are on systems strong enough to carry all 11 EPs under any circumstances. That's going to vary by individual player.
2 - Your Additional Option will be neutral to the game at best and harmful at most. The setting referenced there is for the theoretical upper limit to the game's script heap (20 GB, not 2 GB, and changing that to 40 GB is not going to help anything). It has nothing to do with RAM usage.
TS3 on Windows is Large Address Aware (LAA) all on its own and will use up to just short of 4 GB of RAM when it needs to, provide the RAM is there for it to use. This came about with Patch 1.17 that was released alongside of Late Night many years ago. TS3 on Mac is currently limited to 2 GB and there is no way to improve upon that, although surprisingly enough a patch is in the works by EA to do so and is expected to be out later this year, we hope.
If done correctly it should work. On the rare occasions when it doesn't, the most likely cause is that there's something wrong with the graphics driver that needs to be investigated and remedied.
