Reply To: req: Multithreading – performance issu large map

Home Forums General Discussion req: Multithreading – performance issu large map Reply To: req: Multithreading – performance issu large map

#15616
Blokker_1999
Participant

Except, for most people, for most of the time, the product works as advertised. It’s like complaining that photoshop is barely useable when you load  in a picture that is 1GB in size and has a few gigapixel … It’s the same with TF, the amount of data is simply too much for the system to handle. And as stated before: that is not really a bug. A designflaw? Probably.

I had a quick look at the save games, and I have to say that that has shown me a thing or two. My save files on the maps that become unplayable are around 130MB of compressed data. Uncompress that file and you get to around 400MB of data. That data has to be taken from the game at every turnover of the year and it is that data that the game needs to keep it’s calculations going. That’s still a massive amount of data to keep reprocessing over and over again.

Further more, I would like to point out that as far as I know, digital goods are still exempt from legislation offering a 2 year waranty on goods. Which means that as a consumer you only have the rights that are granted to you in the licenses that you agreed upon while installing the software. While there was an attempt to modernise this legislation in the first half of 2009 ( http://news.bbc.co.uk/2/hi/technology/8044125.stm ), it apperantly died a quiet death. Which means one has to fall back to the game’s license and the Steam Subscriber Agreement:

 
Steam Refund Policy
As with most software products, unless required by local law, we do not offer refunds or exchanges on games, DLC or in-game items purchased on our website or through the Steam Client.  Please review Section 3 of the Steam Subscriber Agreement for more information.

An exception is made for games purchased during a pre-order period if the request is received prior to the games’ release date.

 

Now can we please go back on topic (which is talking about the actual issue instead of complaining that it’s a gamebraking bug that demands legal action)