SC4 tooks forever to load!

[simcity1999 34]

Even until few minutes it still not load at all. What can I do to improve performance as I don't want to waste my time. Specs: PC Specs: Intel i5 3570 (Turbo boost 3.8GHz, Quad Core, 6MB Cache) | 4GB DDR3 Ram | AMD Radeon HD 7850 VGA Card (2GB GDDR5, 256 bit, 860 MHz) | 500GB SATA3 7200RPM HDD (53,7GB free on C:) | Sony DVD-RW | Genuine Windows 7 Home Premium 64 Bit (won't update to windows

[z1 566]

DatPacker.  I have 4.5 GB of plugins, and my game starts up in one minute, and a city of 2 million Sims loads in 30 seconds, both from a cold start.  And my computer is slower than yours.

[simcity1999 34]

Thanks, I will try to use datpacker, as I never modify downloaded mods at all. And I will also remove unnecessary files (like pictures, readme files, which are useless at all).

EDIT: I've packed my plugins folder using datpacker, and it reduces the loading time from few minutes to only 32 seconds! Thanks to z1 and the creator of datpacker!

[Ro-Bo 183]

Many will say datpack everything except NAM. Did you?

[simcity1999 34]

I datpack everything as I don't know that saying yet. But I try to do that.

[T Wrecks 10,209]

You see, there are files you can throw into your plugins and leave untouched. Most buildings etc. belong to this category. No matter if these disappear in a large DAT.

 

However, there are also files that need to be accessible for updates. The NAM is composed of such files. The NAM is constantly maintained, fixed, and updated, so its files must be accessible for the installer to overwrite/patch them as necessary. If the NAM files are in that huge DAT, the installer will not find them. Instead it will end up dumping a new NAM in your plugins, and the old one will remain in that DATpacked file - this means you'll have a version conflict.

 

It is also very, very unwise to DATpack everything and throw away the folders containing the individual files. Whenever you discover an error or realise that you need to change something for whatever reason, you can go back to the individual files, make the required change, and then DATpack again, replacing your old DAT with the new one that contains the change/fix you made.

 

If that one huge DAT is all you have left, you'll have a hard time finding anything inside.

[aaaling 83]

So, essentially we should DATpack everything except the NAM?

 

How big should the DATpacked files be? Bigger 400MB files, or smaller 100MB files?

[Ro-Bo 183]

Reading TWrecks' post, probably it wouldn't hurt DATpacking NAM. Just makes sure to backup the unpacked NAM. So, whenever you want to update NAM, get rid of the DATpacked NAM, and load the backup (unpacked) NAM in your Plugins folder before running the update.

[aaaling 83]

Well, for some reason, after DATPacking more of my plugins, the game still takes a long time to load, although it shortened slightly.

 

Also, the SFBT Rail Catenaries props disappeared after DATPacking that with other plugins. The lots are still there, but the catenary props aren’t.

[A Nonny Moose 8,261]

DATpacking requires some judgement as to what exactly to subject to this treatment.  Never DATpack anything that is subject to frequent update like the NAM.  Besides, I often rerun the NAM installer to tune things and to include/exclude thing at need.

 

Considering the cost of RAM these days, I believe every multi-core machine should have at least 2GB per core.  In the case of the OP, I'd suggest 8 GB instead of 4.  You want to keep those cores busy and most programs do not multi-task as yet. 

 

Multitasking must be coded into the program.  It is expensive to do and debug, so don't expect much anytime soon.  The hardware usually outstrips the programming capability by a couple of steps.  Then the O/S guys catch up, but the application programmers are usually far behind.  Ever try to convince management to upgrade to some new technical step?

[z1 566]

Well, for some reason, after DATPacking more of my plugins, the game still takes a long time to load, although it shortened slightly.

 

You really have to DatPack almost everything for the maximum benefit.

 

 

Also, the SFBT Rail Catenaries props disappeared after DATPacking that with other plugins. The lots are still there, but the catenary props aren’t.

 

A number of mods have folders that start with "z", or should otherwise be loaded last.  If you're not DatPacking everything (except possibly the NAM and RTMT), then these should not be DatPacked.

[aaaling 83]

You really have to DatPack almost everything for the maximum benefit.

 

So how big should those DATPacked files be? As big as they can, or several 100MB-or-less files?

[A Nonny Moose 8,261]

They are what they are.  However, you should DATpack stuff in groups for easier maintenance.  As z1 has already mentioned a couple of things you should not pack in one swoul foop, it is wise to not pack specialty items that are subject to update.  That's NAM, any folders beginning with z_ etc. that force them to load last (they are usually quite small).

 

I don't have much by way for plugins, so I don't DATpack.  My loading time is just about long enough for me to go out to kitchen and get a drink.  Probably less than 2 minutes.  Just a second, and I'll time it ... 15 seconds to the region map then 1 minute and15 seconds to my largest city.  My unpacked plugins suite (cleaned of garbage) is 886.1 MB.  I do not load RHW nor GLR because I don't use them. 

 

You should think about what you use, and put the rest aside in a different folder especially if you've ever had an attack of the "gee, I want that" syndrome.

 

Of course there is another major difference between our systems:  I am running Linux with an ext4 journaling file system.  You are probably running Windoze 7 or 8 with a probably unmaintained NTFS file system.  Read the first line of my signature and you'll get the picture.  When was the last time you ran the disk maintenance utilities provided by Microshaft?

[aaaling 83]

I’m actually using Windows Vista, with 4 GB of RAM.

[simcity1999 34]

DATpacking requires some judgement as to what exactly to subject to this treatment.  Never DATpack anything that is subject to frequent update like the NAM.  Besides, I often rerun the NAM installer to tune things and to include/exclude thing at need.

 

Considering the cost of RAM these days, I believe every multi-core machine should have at least 2GB per core.  In the case of the OP, I'd suggest 8 GB instead of 4.  You want to keep those cores busy and most programs do not multi-task as yet. 

 

Multitasking must be coded into the program.  It is expensive to do and debug, so don't expect much anytime soon.  The hardware usually outstrips the programming capability by a couple of steps.  Then the O/S guys catch up, but the application programmers are usually far behind.  Ever try to convince management to upgrade to some new technical step?

Thanks, I will consider adding 4GB of additional RAM.