Dependencies and Still Brown Boxes

[annlou 8]

Why would I still get brown boxes when I have all dependencies? I am really careful in checking what I need.

Any advice would be much appreciated.

Thanks

[MandelSoft 2,769]

What exactly did you download? It helps if you get into more detail about what you've done so we could see more quickly where it can go wrong...

[Cefien 361]

If you downloaded something and all its dependency but still got brown boxes. You probably need the bldgprop.dat file.

Also, mention what did you download like Mandelsoft said is not a bad idea.

[annlou 8]

Thanks folks for the help. I can't remember what I was trying to plop when brown box showed up but I will note it down when I next play the game. I have the bldgprop.dat file. In fact I have 1 and 2. Should I only have one? I checked out the Omnibus and it says that brown boxes can pop up if a dependancy has its own dependancy and I wonder if I have somehow missed that. Will check and see.

Thanks again

[A Nonny Moose 8,261]

BldgProps_Vol1 is the set for SC4, and BldgProps_Vol2 contains the added set for RH.

[lhrob 213]

I know it can be very frustrating when you come across dependencies which require dependencies. I think it's ridiculous, and it makes me want to scream at the content creator to simply develop their own textures and props instead of making people hunt down all these other files that were made by third-party creators. If I want to download Billy's Big Blue Building, and he used Penny's Pretty Props on part of the lot, I guess that's fine. But if Penny's Pretty Props depend on David's Dandy Downloads and Helen's Honey Hut .dat file, then my blood starts to boil. Because at any point, Penny could have overlooked one of David's downloads or forgotten to list Helen's .dat file, and like a virus it affected Billy's Building. SOOOOO...having said that, chances are whoever created the custom content (which is giving you trouble) failed to list all the additional dependencies that he/she used.

[A Nonny Moose 8,261]

Amen. I have a very short fuse for lots that do things like that. If a lot maker wants me to use his work, he is well advised to build it with "no dependencies". I balk at most lots that have a long list except those that use a few of the BSC packages. I just can't be bothered with all that stuff, it is carrying reusability just too far.

You see, in the programming world, you usually have access to a library that contains everything anyone should need and is called automatically by the link-loader. We don't have such a system, and I don't think one is even possible. Being my own linker is too much to bother with when there is no common set.

[MandelSoft 2,769]

I do use dependencies, but I prefer to refer to two or three very general packs that don't have dependencies on their own, something what I call single layer dependencies (things like BSC Textures or SG Props). Dual layer dependencies (dependencies that have dependencies) or even triple layer dependencies are really annoying. However, I've use a dual layer dependency once with a re-lot of one of SFBT's buildings, where the second level was only SFBT Essentials (a dependency all the included dependency buildings share). But yeah, preventing long lists of multi-layered dependencies is not recommended.

[longtimepcgamer 227]

Keep in mind that in some instances the order in which the files load can be an issue as well.