Page 2 of 2

Re: OpenTTD 1.4.0-beta5

Posted: 10 Mar 2014 00:28
by Eddi
do not put manually downloaded/copied stuff into content_download in any case. use the directory tree directly above that.

Re: OpenTTD 1.4.0-beta5

Posted: 20 Mar 2014 12:00
by Flavius
Hi OpenTTD Team

Congratulations on breaking the barrier to even bigger maps!
An amazing 4096 x 4096, incredible i just cannot believe it.
Well done :shock:

Anyway can we all use it?
Will OpenTTD 1.4.0 test players computer to check if there is enough memory :?:
Will there be any limits to mountain height and sea depth :?: :idea:

What would now be a minimum configuration e.g.

1. Hard disk space needed. Was 2 gigabytes.
2. Graphic card speed.
3. Ammount of memory required. Also was 2 gig
4. Will the operating system move up from XP.

Bye Everyone.

Re: OpenTTD 1.4.0-beta5

Posted: 20 Mar 2014 12:28
by YNM
Don't change much. OpenTTD is still pretty light; the main problem is once you have tons of vehicles running around...

Re: OpenTTD 1.4.0-beta5

Posted: 20 Mar 2014 12:54
by Redirect Left
Flavius wrote: Will OpenTTD 1.4.0 test players computer to check if there is enough memory :?:
A 4096 x 4096 map makes OpenTTD uses 211MB of RAM on my system (with 8GB total), although it took it about 1min 15 seconds to generate the map (on an AMD Phenom II, 4X 3.2GHz), compared, a 2048 / 2048 map I have running with 650 trains uses 104MB
Flavius wrote: 2. Graphic card speed.
My GPU didn't use any more than 6% of a GTX650 TI, and i suspect that was probably mostly Windows 7 using it, not OpenTTD.

Rest, I cannot answer from personal experience, but both of the above were gathered from OpenTTD 1.4.0 RC1, and of course, the actual usage on your own system may vary.

Re: OpenTTD 1.4.0-beta5

Posted: 20 Mar 2014 17:46
by frosch
The map size is irrelevant for the memory usage. The spritecache is way bigger in any case.

However, a bigger map will increase join time since clients have to download more. Eventually they may time out and be kicked for taking too long. (The server has a bunch of settings to set timeouts for clients for various actions.)