Railworks America

I am packaging up the assets for the Lafayette route and it is big. 735 meg. Is this too big to download? Should I break it up into smaller parts? How big/small?

I suggest approx 200 meg pieces.

Uh, 32 views and 1 reply. Does that mean you do not care about downloading a 735 meg file?

That is just the assets. The rolling stock is another 500 meg.

Is this before you compress it or after?

buzz456 wrote:Is this before you compress it or after?

735 meg rar file with max compression. 1.4 gig uncompressed.

That's about the same size as most of the major routes.

As an insatiable downloader, I'd say: split it if there's a logical divide (eg between assets and content), otherwise keep it as a single download, as anything less than 1GB is acceptable to me as a recipient.

But... is there a significant effect on the downloading server if the downloaded segments are (a) few and large, or (b) many and small?

Kind regards,

John M

PS My normal download rate is 0.75 MBytes/sec...

J

It really doesn't matter how big the download is, just as long as it fits on RWA servers, if it acceeds the download library limit, then there's a problem.


But other then that, it doesn't really matter how big it is if it fits.



...Cheers...


Jon

No worries about download size to me.

The server is 1 TB, no problem with size. Upload limit is 942 MB or something like that. I upload with FTP so there is no size limit for me. The web thing has limits according to the way php is configured. The file library is now 28 gig.

Download size does not worry me.

Doesn't matter.

Size doesn't matter to me. Use to downloading up to 22GB or more on some games.......Gerry

Large files aren't the issue, Bob. The biggest problem is with your server's bandwidth and associated charges.

That isn't that big Bob. Like others say, I don't care how big the package is.

To put this in perspective, my Assets for Donner are 2.5GB plus another 683MB for the route folder.
That's over 3GB all together.