• Welcome to SC4 Devotion Forum Archives.
 

News:

The SC4 Devotion Forums are no longer active, but remain online in an archived, read-only "museum" state.  It is not possible for regular members to post or use the private messaging system, and no technical support will be provided for any issues pertaining to the forums in their current state.  Attachments (those that still work) are accessible without login.

The LEX has been replaced with SC4Evermore (SC4E), and SC4E maintains an active Discord server.  For traditional forums, we recommend Simtropolis.

Main Menu

Problems with Tree Controller

Started by Alan_Waters, January 08, 2016, 12:52:08 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Alan_Waters

I used "Cascadia Tree Controller" (seasonal).I removed because tired of guessing time. I decided to install a "CPT No7a MissouriBreaks TreeController", because it is best suited for the area where I live. Now, if you start the timer, the trees begin to disappear.
Can I fix this?
How to make the plains also plant trees?
And which tree controller is considered the best (no seasonal)?

Once again I am sorry for my english.

Thanks in advance!

mgb204

You can not remove a tree controller when any of the trees or flora it contains is still left in your city.

If you used the code "Flora Off" to remove such flora before the change, you probably just need to use "Flora On" to reactive the seasonal timing.

However, if you failed to remove all the trees/flora first, expect a CTD the moment you enter such tiles.

CP's tree controllers won't plant trees everywhere, not a lot you can do about, except fill the gaps with MMPs.

Seaman

Because the thread is quite new and my question somehow related, I dare to ask here:

1. I decided to use some of these amazing tree controlers for my Vancouver inspired region. I am torn between the "pacific northwest" and the "cascadia" tree controler. What are your experiences with the controlers. Any suggestions wich could help me with my decision?

2. I'm not into this seasonal thing and would love to have the controlers evergreen. But I am afraid, this isn't possible, right?

Alan_Waters

#3
I used the "Cascadia", but I did not like what they are seasonal. Therefore, I set "ARDEN Seasonal Tree Controllers (v1.0)". He has both a seasonal and evergreen. "Cascadia" very good, but unfortunately, there is no version of the evergreen.

mgb204

Quote from: Seaman on February 11, 2016, 09:12:58 AM
Because the thread is quite new and my question somehow related, I dare to ask here:

1. I decided to use some of these amazing tree controlers for my Vancouver inspired region. I am torn between the "pacific northwest" and the "cascadia" tree controler. What are your experiences with the controlers. Any suggestions wich could help me with my decision?

2. I'm not into this seasonal thing and would love to have the controlers evergreen. But I am afraid, this isn't possible, right?

Personally I'm very into Cascaida, but the PNW & Aerden controllers are also excellent if you are into HD flora.

Modding a tree controller is possible, but changing it from Seasonal to non-seasonal directly would likely be as much work as creating a new one. However, it should be possible to modify the tree flora RTK values (that's just the equivalent of a hyperlink to the tree), so that all the Autumn and Winter props (Spring too where applicable) link to the Evergreen summer trees. Comparatively that wouldn't be so much effort, and it would potentially cover other scenarios where seasonal flora was used.

Seaman

#5
Quote from: mgb204 on February 11, 2016, 09:50:37 AM
However, it should be possible to modify the tree flora RTK values (that's just the equivalent of a hyperlink to the tree), so that all the Autumn and Winter props (Spring too where applicable) link to the Evergreen summer trees. Comparatively that wouldn't be so much effort, and it would potentially cover other scenarios where seasonal flora was used.

I'm a complete newbie to SC4 modding (although I have some general coding knowledge), so i guess I'll have a close look on the Ardeen controller.

But your reply made me curious. I already thought it shouldn't be imposssible to get en evergreen controller from an existing seasonal one due to the fact, that nothing has to be added. I read your reply in a way, that it is theoretically possible to copy/paste the existing links for one season to all other seasons?

PS: I guess anyone who spent hours and days for building a nice seasonal controller will get close to an heart attack when reading this...

mgb204

#6
If you got "copy/paste links" from my previous comment, I'd be willing to bet you'd have no trouble working this out.

Rather than change any of the complex Flora props (part of the tree controller), you should approach this by editing the tree props themselves. The hardest part is probably working out which trees to change, since many of the dependencies contain trees the controller may not use too.

As an example, the simplest file I can think to use is Girafe's Bushes (sorry Girafe, I love seasons  ;D)...

Before you begin, it's useful to have a spreadsheet like Excel open for keeping track of IDs. Better to work out what ID's you require before you start editing.

Now, using iLives reader, open the file "Grfe_props_pack_bushes.dat" from Girafe's download. Here the files are neatly organised in groups of 40 files. 20 are "S3D" files, these are the models. The other 20 are FSH files, they are the textures. Ignore the Type and Instance IDs, concentrate on the middle one, Group. Note how each group of 40 files will have the same Group ID? So for the first single bush prop, the following group IDs are used:

Summer - db3d9fcc
Autumn - fb5bfcd5
Winter - 5b5b032c

As I mentioned before, these ID's are just links, so if we gave copies of the Summer trees the Autumn and Winter IDs, they would appear instead, whenever they are referenced by the game.

A good workflow for doing this is as follows:

  • Highlight the first 40 items, nice and easy since it's 20 S3D/FSH files and Girafe's modding is tidy :).
  • Right click and select the option "Add to Patch".
  • Click on the patch button at the top of the Reader interface.
  • Select the Create DAT button.
  • Select where to save, and give the file a meaningful name.

You now have a new DAT, containing only the files you need to work with. Of course as you become more comfortable with the process, it's quicker to patch multiple sets of files in one go. To start though, it's easier if you only have the files you need.

Open this new DAT you created. It contains only a copy of the Summer single bush prop now, or 40 files. Once more select all 40 (be careful not to select any DIR files). This time right click and select "Copy Files". Then select the last item in the group only (to ensure the new files are pasted after them), right click and select "Paste Files".

Now you have two identical copies of the Summer single bush prop. Click on Tools in the file menu, then TGI Editor. In the group field, replace the ######## with the Autumn ID, i.e. FB5BFCD5. Then in the lower box, you need to highlight only the files you wish to re-ID. This is a little counter intuitive, because the list you see here is in reverse order to the list in the main reader window. So in essence, you want the top 40 lines, to help you, notice how the Type ID changes for each set of 20 S3D and FSH files? Having selected the correct files, click apply. When you close this window, you will see the ID's change. Repeat this copy/re-ID process once more for the Winter prop, with the ID 5B5B032C. Now save your new dat file, it will replace the original entirely.

Bear in mind the following if you undertake this:

  • Some props (mostly CP's) have a 4th season, Spring. In such instances you need to make a 3rd copy too.
  • Girafe has only placed the models in this DAT file, but some creators will package other files in there too. If that's the case, you can do one of two things. Load your new file after the original, overriding it, and worry no more about it. Or, to avoid many duplicate files, you can copy over the other files to your new DAT (Open both in reader, use the Copy/Paste facility described above).

This might seem a little complex at first, but after doing a couple, you should be up to speed. You need to look at every dependency for the tree controller and dig out the trees it uses to un-season-ify them.

Of course it's probably better modding to edit the tree controller flora props, which would then link to the evergreen models. But this is much more complicated in practise and prone to errors too. I hope this small guide is helpful to you :).

Seaman

#7
well I've said that I have zero experience with SC4 modding, but with this unexpected guide (wow, thanks for that!!) I may give it a try. Maybe I can work something out and maybe! I have enough stamina to get through the vast amount of props, I asume to be in there. I've read enough threads in this forum to know that it's a long way to go from an initial idea to the final mod.

ah, by the way: if my real life is complaining, I will tell them you made me do that  ;) again, I've read enough at this place to know that SC4 modding has to be some kind of addiction.


Edit:
ok, I figured it out and was able to follow your idea. I think I can do it. But it feels strange to have 3 or 4 identical copies around and by intuition I would rather mod the links in the controller directly. But after a brief glance into the controller .dat I realized without further introduction I am not able to do anything over there (trial and error seems to be an improper approach here  :P)