Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Missing mesh libraries at a guess.
Quick check
<kuid2:19691:100014:2> Tb Forest Library
<kuid2:19691:100014:1> Tb Forest Library
<kuid:19691:100014> Tb Forest Library
<kuid2:19691:100011:2> Tb Grass Library
<kuid2:19691:100011:1> Tb Grass Library
<kuid:19691:100011> Tb Grass Library
MY CM shows the most recent versions of the libraries are all installed
I have a whole bunch of these, all on the DLS and all coming up faulty with multiple "Alias mesh not found " warnings for each one. Also there are TB grass assets that flag faulty when updated. What gives?
Make sure that ONLY the most recent version is installed - delete the obsolete versions.MY CM shows the most recent versions of the libraries are all installed
Open each asset and change
<kuid2:19691:100014:1> or <kuid:19691:100014> in the mesh table and kuid table:
To: <kuid2:19691:100014:2>
John
Make sure that ONLY the most recent version is installed - delete the obsolete versions.
It is the only one installed.
It's likely the other way around - the latest updates take advantage of features not available in earlier versions.Hmm in which case they probably aren't configured for TANE upwards
Doesn't this mean the kuid2 obsoleting system isn't working as it should? Surely, it should be automatically using the latest version, without any forcing?
I have noticed that assets use 2 different wintering methods. One that you mentioned makes it winter/not winter based on the altitude setting. The other method is based on the time of year regardless of snowline settings. I suppose these methods are the discretion of the asset creators. I have seen a couple hybrids where below the line is controlled by the calendar, and above winters them out all year. I don't know if "meant to work" has a writ in stone definition or not.(Just a side note about the trees. They go snowy in December/January even when below the snowline. In other words, the author doesn't understand how the seasonal system is meant to work).
I have noticed that assets use 2 different wintering methods. One that you mentioned makes it winter/not winter based on the altitude setting. The other method is based on the time of year regardless of snowline settings. I suppose these methods are the discretion of the asset creators. I have seen a couple hybrids where below the line is controlled by the calendar, and above winters them out all year. I don't know if "meant to work" has a writ in stone definition or not.
Roger that. Something learned today by me. Funny thing is, the trees I place are hybrid. They flower for spring, full canopy for summer, color up for autumn, and strip bare for winter with no snow/ice. Drop the snowline and every tree above goes bare and white. Best of both worlds IMO.(snipped)...the Wiki contains the express instruction; "If you wish to use "snow" on your asset use the Snowline options, not the Winter options" (snipped). That's how it's "meant to work".
Roger that. Something learned today by me. Funny thing is, the trees I place are hybrid. They flower for spring, full canopy for summer, color up for autumn, and strip bare for winter with no snow/ice. Drop the snowline and every tree above goes bare and white. Best of both worlds IMO.
These do exist too a small degree. Had static trucks that wintered over above the snow line. Can't remember if they changed with the months tough. Tripped over them while trying a winter wonderland route creation once in TANE.Exactly. That’s the standard “seasons + snow” system that N3V want creators to adopt for trees that can exhibit all those changes.
I noticed that one of the examples in the Wiki even allowed for different snowlines at different times of year (if I read it correctly) which is an even more complex configuration. At the other extreme, you can do buildings and vehicles that only need one regular skin and one snowy alternative, no seasons.
So it’s a very flexible system, but one that can sometimes be misunderstood.
I've been playing around with changing the background trees (and there are tons of them) on the BC&SJ route from st_rmm trees to billboard trees for performance reasons.
In the process I've run into the OP's problem in spades.
Is there another family of high-performance trees that does come with the library version issues baggage of the tb forest series of trees?
I'd expect that future sharing of the BC&SJ route would be much smoother if the installee didn't have to mess with tb forest library versions!
Horace