Jump to content
  • Lucario Boricua
    Lucario Boricua

    DATpacking the Network Addon Mod, the Official Way!

    :)     Hello to all my fellow Mayors and Simtropolitan simcitizens!!     :D

     

    Today I'll be explaining how to DATpack the Network Addon Mod with an official step-by-step guide. Over the years, the NAM has become both one of the largest mods for SimCity 4 and arguably the most important and widespread of them all. As such, it has an enormous impact on gameplay outcomes, gameplay options, and yes, a detrimental effect on the game's performance! DATpacking the NAM has essentially become a necessity to improve the game's performance by reducing the number of individual files the game must load from the Plugins folder, reducing the game's start-up time, first city loading time, menu loading time, and the transition time between the data views.

     

    A. Necessary Files and Requirements

     

    Latest version of the Network Addon Mod, at the time of this writing, Version 42 is the one available and officially supported. This tutorial is applicable to all the Java installer versions of the NAM (version 37 onwards).

     

     

    Select a DATpacking program of your choice (use only 1):

     

    1. Wouannagaine's SC4 DATPacker, NHP Productions: the simpler of the DATpacking programs and the basis of this tutorial. Downloading requires an account in the SC4 Devotion Lot Exchange (LEX). This version works well only on Windows operating systems. Link provided below.

    https://www.sc4devotion.com/csxlex/lex_filedesc.php?lotGET=26

     

    2. Memo's JDATpacker: the other major DATpacking program, this Java-based application provides cross-platform support, and as such, is the version recommended for Mac and Linux players. Downloading requires an account in the SC4 Devotion Lot Exchange (LEX). Link to program and to support thread provided below.

    https://www.sc4devotion.com/csxlex/lex_filedesc.php?lotGET=3140

    https://www.sc4devotion.com/forums/index.php?topic=16500.0

     

    If you are new to DATpacking mods and custom content for SimCity 4, make sure to follow the ReadMe files to set up the DATpacking application before proceeding with this tutorial.

     

    B. File Organization before DATpacking

     

    Make sure to follow the file organization provided here, which ensures the different components of the mod load in the correct order. This also allows auxiliary NAM support programs, such as the Traffic Simulator Configuration Tool, as well as patch files, to load correctly.

     

    1. Create a temporary Plugins folder for use with DATpacking. To do so, first re-name your gameplay Plugins to something else, and then create a new folder named Plugins. This helps keeps your files organize and facilitates selecting folders during the packing process.

     

     

    2. Install the Network Addon Mod. Make sure to carefully select any and all options you want (and de-select those you don't!).

    AuK3r35.jpg

     

     

    3. Let the installation run until reaching completion. The installation will appear on a folder named Network Addon Mod.

    smUaHLk.jpg

     

     

    4. Create a second folder which specifies that the files are DATpacked. I named mine "NAM 42 RHD US - DATPacked", as I keep more than one packed installation available, depending on what I need to do. Typical players will only need 1 packed version in most cases.

    W4HQb9J.jpg

     

    IWC1WED.jpg

     

    5. Open your NAM installation folder, and then open the 2 Additional Network Features folder. You'll see several folders containing the various families of NAM features. Right-click on each folder and add the number 2 before its name, and do this for all the folders found here.

    A5gJb2y.jpg

     

    ynimije.jpg

     

    6. Once done re-naming the folders inside 2 Additional Network Features, select them all and move them (cut, then paste) to the root Plugins folder.

    xhnCF7N.jpg

     

    5fCf4mS.jpg

     

    qGUDXoT.jpg

     

     

    7. After moving the now numbered folders, delete the now-empty 2 Additional Network Features folder.

    0tCLOwX.jpg

     

     

    C. The DATpacking Process

     

    Note: This part was written based on Wouannagaine's SC4 DATpacker:

     

    8. Open your DATpacking program and wait for it to load:

    GpvR1t6.jpg

     

     

    9. Once loaded, you should see a list of the folders contained within your default Plugins folder. The program will pack all the relevant files contained within a particular selected folder.

    OGx8T1p.jpg

     

     

    10. Select the numbered files forming part of the NAM installation, in this case we'll do so for files going from number 1 Core to number 8 Texture and Drive Side Support. Do not select 9 Traffic Simulator if you intend to modify these files through the Traffic Simulator Configuration Tool. Once selected, click on Start, and the program will DATpack the contents following the parameters specified.

    Vs2OOzz.jpg

     

    zXs9BRG.jpg

     

    11. Check that all the correct files were packed by opening the Plugins_Compressed folder (or any other target directory, if different). For a full standard NAM installation, you should have 11 files with the number 2, and all the numbers going from 1 to 8.

    e8yqyRZ.jpg

     

    gUTg3GF.jpg

     

     

    D. File Organization After DATpacking

     

    12. Move the packed files from Plugins_Compressed to your destination file for the DATpacked NAM. Do this as a cut and paste operation.

    kC834UE.jpg

     

    3VsbJPx.jpg

     

    YP27pwF.jpg

     

     

    13. Now go back to the root Plugins folder, and search for the folders which weren't packed. Following this procedure, they would be 9 Traffic Simulator and z_NAM Controller. Move them to your DATpacked NAM folder:

    x9nqJRW.jpg

     

    CT6vYgB.jpg

     

     

    14. Your DATpacked NAM should look this way. Make sure no files are missing:

    BRESza4.jpg

     

     

    15. Delete the unpacked folders remaining in the root Plugins directory, except for your original NAM installation files. It is strongly advised to keep the latter in a back-up location, ideally in a different drive to the one containing your SimCity 4 installation.

    cvFTnHr.jpg

     

     

    16. Move the original NAM installation files to your back-up location of choice. These backed-up files can be used if you ever have problems with the NAM installation, want to modify it, or if there were issues with the DATpacked files.

    N4YofkE.jpg

     

     

    17. (Optional) Re-name your DATpacked NAM folder to Network Addon Mod. This step is recommended if you intend to use the Traffic Simulator Configuration Tool, which will automatically search for your Network Addon Mod installation folder.

    nH34zFn.jpg

     

     

    18. (Required) Once all the files are ready and re-organized, copy your DATpacked NAM to your gameplay Plugins folder, and then change the names of the respective Plugins folders. Your gameplay Plugins should revert to Plugins, and your DATpacking Plugins folder should use a different name.

    Make sure there are no other NAM installation files in your gameplay Plugins, otherwise you won't get the loading time benefits and will get duplicate entries in the transportation menus in-game.

    OH2YxSt.jpg

     

     

    E. Final Remarks on the Subject

     

    In the past, the NAM Team advised against DATpacking for two reasons:

    1. When the Network Addon Mod adopted the modular distribution (NAM 21 to 30), DATpacking was a new advancement in SimCity 4 modding, and unfortunately coincided with some bugs associated to this file architecture, among them the infamous "red arrow" bug. On top of this, a common error which occurred frequently at this time, and which all users should avoid, was not deleting the DATpacked files of older versions when updating to the new version. Make sure to delete the DATpacked NAM files before installing the next version. This avoids carrying old bugs into the new installation, in addition to the duplicate menu items and wasting space in Plugins.
       
    2.  When the Network Addon Mod was monolithic and installed with the NSIS .exe installer (NAM 31 to 36), the mod was substantially smaller and thus didn't have as many individual files. Performance gains from DATpacking were not as significant, but between the late NSIS-era installer days (NAM 36) and today (NAM 42), with large size increases of the mod observed in NAM 37, 40 and 42. Additionally, the more frequent incidence of critical bugs meant that technical support provided by the NAM team required preserving the installer's provided file architecture to ensure correct loading order of the patches.
       

    The file architecture of the Java installer's output (applicable since NAM 37) includes numerous sub-folders and loose files. This is preferable for development, testing and de-bugging purposes. The downside is the number of files grows too much and the game spends a lot more time loading them. This is further aggravated by the ever-growing number of mods and custom content players have at their disposal, which can result in unbearably long loading times for the game, the cities and the menus. Additionally, Mac installations are limited in the number of custom files they can load from Plugins, making it a necessity to pack the files to stay below the limit.

    DATPacking is still recommended for players with the latest hardware, especially solid-state drives (SSDs). Even if these shorten considerably the game's loading times, it's still possible to get performance gains by providing fewer files for the game to load.

     

    When requesting technical support for DATpacked NAM installations, make sure that there are no duplicate files (DATpacked and unpacked alike) and that you're following the recommended file architecture for DATpacking the mod.

     

    :bunny:     And finally, please enjoy the shortened loading times with your DATpacked NAM, make use of that saved time to use more of our latest transportation goodies!!      :read:

    • Like 14
    • Thanks 5


    User Feedback


    Excellent tutorial, thanks. It came to me at the right time, I'm jumping from 36 to 42 and I'm dealing with the positive differences of this evolution. *:thumb:

    Very nice idea to leave the "traffic simulator" folder out of the packaging so that I can change them in the future, making the packaged NAM more flexible, so there's no need for repackaging. *:ohyes:

    First question: thinking about it, could I leave the "4 Automata Controller" folder out too? *:???:
    I put the "BL Radical", but I imagine that with big cities, this demands too much from my hardware, and it would be better to put a more standard automata.

    Second question: what would be the purpose of leaving the controller folder out too? Is it common to have users changing the controller?

    Share this comment


    Link to comment
    Share on other sites
    4 hours ago, carlosmarcelo said:

    Excellent tutorial, thanks. It came to me at the right time, I'm jumping from 36 to 42 and I'm dealing with the positive differences of this evolution. *:thumb:

    Very nice idea to leave the "traffic simulator" folder out of the packaging so that I can change them in the future, making the packaged NAM more flexible, so there's no need for repackaging. *:ohyes:

    First question: thinking about it, could I leave the "4 Automata Controller" folder out too? *:???:
    I put the "BL Radical", but I imagine that with big cities, this demands too much from my hardware, and it would be better to put a more standard automata.

    Second question: what would be the purpose of leaving the controller folder out too? Is it common to have users changing the controller?

    If you intend to change the automata controller, that's also an option. Interestingly enough, this folder contains one file.

     

    My recommendation for your particular case is to avoid the radical automata controllers, those increase the amount of visible automata over the game's default numbers. Standard, persistent and 24-hour, and their different combinations are less resource intensive options. 

    • Thanks 1

    Share this comment


    Link to comment
    Share on other sites

    Thanks for your Tutorial dude!

    I've just Datpacked NAM43 folder and I've got 1 minute of loading time. Does it is a reasonable loading time considering that i have a 1.10 GB folder of NAM43 after datpacking? @Lucario Boricua @Tarkus???

    Share this comment


    Link to comment
    Share on other sites
    3 minutes ago, ohdude said:

    Thanks for your Tutorial dude!

    I've just Datpacked NAM43 folder and I've got 1 minute of loading time. Does it is a reasonable loading time considering that i have a 1.10 GB folder of NAM43 after datpacking? @Lucario Boricua @Tarkus???

    Yes, that sounds accurate. My game takes about 4 minutes to load from starting to the region view; and I have about 5x in total file size in my Plugins folder. Many of said files could be packed more efficiently, but this is enough for me when playing.

    Glad to know it's helped improve your gameplay experience with faster loading!

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    @Lucario Boricua Thanks for your fast answer.

    I forgot to tell you that i had 800 MB of very ordered plugins folder that took 15-20 seconds to load. So i'm a little doubtful why the loading time of the ton of NAM43 hasn't been less time. Maybe it is because of the complexity of NAM folders by itself.

    image.png.16db00d270c4c2989cec5e5a95199666.pngimage.png.2c8f43999d990e583bc9d0c5c0a8e9ba.png

    Share this comment


    Link to comment
    Share on other sites
    19 minutes ago, ohdude said:

    @Lucario Boricua Thanks for your fast answer.

    I forgot to tell you that i had 800 MB of very ordered plugins folder that took 15-20 seconds to load. So i'm a little doubtful why the loading time of the ton of NAM43 hasn't been less time. Maybe it is because of the complexity of NAM folders by itself

    The NAM itself has a highly complex file architecture, with multiple nested folders featuring textures, network models, transit station models and lots, network paths, exemplars to control traffic-related content (traffic simulator, traffic data views, automata controllers), and various types of code to control transportation networks (INI and the various RUL code files). The game takes a long time to load mods which consist of numerous small files and folders (spends more time checking each and every folder and file to decide what to load), plus some of the NAM files are really large. By DATpacking, you reduce drastically the number of files and remove the irrelevant files; which drastically improves loading times.

    • Thanks 1

    Share this comment


    Link to comment
    Share on other sites

    @ohdude, most likely, I'd probably chalk it up to the NAM Controller.  That's the thing that requires the 4GB Patch in order to load--it's a hefty file, and among its subfiles is one (the RUL2 file) that has millions of lines of text in it.

    -Tarkus

    • Thanks 1

    Share this comment


    Link to comment
    Share on other sites

    Thanks @Tarkus and @Lucario Boricua, Now i have a clearer idea of what must be happening. But i have a last question: Why the NAM Controller folder is not DatPacked?? What would happen if we datpack it?

    Share this comment


    Link to comment
    Share on other sites

    Lucario,

    I followed your NAM rename and restructure subdirectory directions.  But I should note that I packed the entire plugin folder, not just NAM44.

    I found absolutely zero performance difference.  Tested were:

    * Load of game.  ~10s

    * Load of built up large tile.  ~100s

    Here my config:

    i7 OCd to 4.3GHz

    32Gb RAM

    2Tb SSD with memory disk cache

    WIN10 Pro 64

    I timed the second load in each benchmark.  This should not any boost from caching.

    Once in the game after the first region load (100s), I found other region loads only take 2-3s.  Needless to say, compared to most large footprint games and mods, the performance is excellent.

    Since I am a noob, I only have about 300Mb of mods besides NAM44 (1.2Gb).  I don't think I will go beyond 1Gb of mods when adding more assets.

    Even if I could get tile load down to 0.50s from 3s, I don't think it is worth it due to the diminished flexibility in easily testing mods.

    ---

    Have I done something incorrectly?  Or is my hardware bandwidth just making it irrelevant.  The packed size is almost the same as unpacked.  Therefore, the only area for improvement is the number of file reads.  For a mechanical disk, seeking is the longest part of reading, but an SSD and cache has no mechanical overhead to address data.

    Thanks.

    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    9 hours ago, MarkShot said:

    I only have about 300Mb of mods besides NAM44 (1.2Gb).  I don't think I will go beyond 1Gb of mods when adding more assets.

    In your case, it will make very little difference. I believe DatPacking is more suited to peeps with multi-GB plugins and/or tons of ploppable content (which slows menu opening if not packed).

    • Yes 1

    Share this comment


    Link to comment
    Share on other sites
    18 hours ago, MarkShot said:

    Lucario,

    I followed your NAM rename and restructure subdirectory directions.  But I should note that I packed the entire plugin folder, not just NAM44.

    I found absolutely zero performance difference.  Tested were:

    * Load of game.  ~10s

    * Load of built up large tile.  ~100s

    Here my config:

    i7 OCd to 4.3GHz

    32Gb RAM

    2Tb SSD with memory disk cache

    WIN10 Pro 64

    I timed the second load in each benchmark.  This should not any boost from caching.

    Once in the game after the first region load (100s), I found other region loads only take 2-3s.  Needless to say, compared to most large footprint games and mods, the performance is excellent.

    Since I am a noob, I only have about 300Mb of mods besides NAM44 (1.2Gb).  I don't think I will go beyond 1Gb of mods when adding more assets.

    Even if I could get tile load down to 0.50s from 3s, I don't think it is worth it due to the diminished flexibility in easily testing mods.

    ---

    Have I done something incorrectly?  Or is my hardware bandwidth just making it irrelevant.  The packed size is almost the same as unpacked.  Therefore, the only area for improvement is the number of file reads.  For a mechanical disk, seeking is the longest part of reading, but an SSD and cache has no mechanical overhead to address data.

    Thanks.

    DATPacking the NAM with a small collection of mods doesn't provide a large performance benefit, but it does when working with large mod collections. I at least did get a 3 minute performance gain when pairing DATpacked NAM with another 5GB worth of mods, and it does boil down to the number of tiles the game must load when it comes to launching the game from an SSD. There are, however, other benefits, such as decreasing the loading times between data views, especially the subway view and the Zones + subway data view. These are especially significant in large cities.

    • Like 4

    Share this comment


    Link to comment
    Share on other sites

    Thanks, Lucario.  I have the downloaded the utilities (I prefer the JAVA packer) and bookmarked the thread if I should feel the need into the future.

    • Like 2

    Share this comment


    Link to comment
    Share on other sites

    Hi, Luc, thank you so much for this detailed tutorial!
    It helped me a lot, and I always point out this post to others looking to datpacked their NAM or just gain some performance boost.

    A little feedback: seems like there's a slight jump from steps 6 to 7, where you mentioned moving the contents inside the folder "2 Additional...", but then jumped to showing all the contents of NAM folder already in the root of the Plugins folder. You did mention "Select them all ...", but I thought it was just the folders inside "2 Additional...". So, maybe you can improve/add more copy to explain it.

    Also, this one is really minor, but some of the pictures with 2 windows side-by-side, where the one that matters is only the left side, confused me too. Because I thought I had to do the actions from the left window to the right window. Maybe adding a slightly darker overlay will help with this.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    Just to be sure, the process is the same for newer versions of the NAM right? as the NAM has no z_nam and the Aditional networks folder has more folders and different names for them. Is there an updated version?

    Share this comment


    Link to comment
    Share on other sites


    Sign In or register to comment...

    To comment in reply, you must be a community member

    Sign In  

    Already have an account? Sign in here.

    Sign In Now

    Create an Account  

    Sign up to join our friendly community. It's easy!  

    Register a New Account


  • Recently Browsing   0 members

    No registered users viewing this page.

×

Thank You for the Continued Support!

Simtropolis depends on donations to fund site maintenance costs.
Without your support, we just would not be in our 24th year online!  You really help make this a great community. *:thumb:

But we still need your support to stay online. If you're able to, please consider a donation to help us stay up and running. This helps sustain a platform where we can share our community creations for years to come.

Make a Donation, Get a Gift!

Expand your city with the best from the Simtropolis Exchange.
Make a Donation and get one or all three discs today!

STEX Collections

By way of a "Thank You" gift, we'd like to send you our STEX Collector's DVD. It's some of the best buildings, lots, maps and mods collected for you over the years. Check out the STEX Collections for more info.

Each donation helps keep Simtropolis online, open and free!

Thank you for reading and enjoy the site!

More About STEX Collections