justinroth
Well-known member
I can't seem to find a solution. I updated to 2022+ and I have a good deal of faulty speed trees, mostly from mcguirel. I tried looking for asset versions as I know there aren't any updates. Any ideas?
2019 to 2022 faulty speed trees?
- Thread starter justinroth
- Start date
justinroth
Well-known member
I don't know but I'm sure it's the start of issues.
It is simple. N3V has neither the staff, or the funds, to thoroughly vet its updates. There is no "accountable$$$" profit from producing a clean update. They continue down the same path of "consolidated updates" where multiple items are changed resulting in an exponential chance for failure. For some totally unknown reason they insist on glorious big updates and the failure rate is almost always high. The boss, who is ex-marketing, can't seem to grasp that frequent, narrowly targeted, updates will prevent the angst and confusion of big splashes of updates with their accompanying marketing propaganda.
So, to continue the marketing theme we see the latest video touting a major effort in graphics design software. A revenue source for N3V is the production of product by skilled designers of railroad elements. To enhance that source, new tools are given to the artists for more and better products and thus increased revenue. More updates to come.....
So, to continue the marketing theme we see the latest video touting a major effort in graphics design software. A revenue source for N3V is the production of product by skilled designers of railroad elements. To enhance that source, new tools are given to the artists for more and better products and thus increased revenue. More updates to come.....
Check the version of the trees. If they are 3.5 or 3.7, they are not compatible with T: ANE or up due to the change from 32-bit Speed Tree libraries to 64-bit used in the current version. IDV, the company that creates Speed Trees offers no upgrade path between versions of anything, therefore, we lost out when going from 32-bit to 64-bit and we were required to create new trees all over again.
The solution is to take a TS12 route and replace the trees with something else. Clam1952 for instance created a bunch of billboard trees that look okay in TS12. Once the trees are replaced, you can then bring the route into T: ANE and up, mean TRS22 as well without issue.
The solution is to take a TS12 route and replace the trees with something else. Clam1952 for instance created a bunch of billboard trees that look okay in TS12. Once the trees are replaced, you can then bring the route into T: ANE and up, mean TRS22 as well without issue.
My preferred tree replacement (only suitable for personal use) which I use to make billboard into speed, is to find suitable replacements and then craft copies into "fake" upversions of the asset I'm replacing.
Just edit the config to KUID2:X:Y:99 and drag and drop into CM.
I upgraded the forests to Eagle River doing that.
Just edit the config to KUID2:X:Y:99 and drag and drop into CM.
I upgraded the forests to Eagle River doing that.
justinroth
Well-known member
This route came from 2019 sp2
justinroth
Well-known member
They are build 3.9 and 4.1
justinroth
Well-known member
Ok I figured it out. I should've known to check this. I went to each speedtree mesh library which were showing faulty and selected to view errors and warnings. I got some warnings but 0 errors. After doing this for every one they now show up correctly.
The faulty but not is caused by the indexing and cache in the database being reset during the DBR. Why this affects only some assets but not others is unknown. For me, it's not always Mcguirel's trees. I have some assets by others that get hit and because of that, I always view errors and warnings after an EDBR and even a regular DBR.
The pofig trees do not work above 12. There is no way to fix them. In the Reading and Northern route on Jointed Rail, it used a lot of pofig trees and they are all faulty in tane and 19 and up unless you download the fixed versions on the dls that have the trees replaced.
One could make pseudo updated ones locally as substitutes. I did that for Eagle River so all the billboards became speedtrees.
I took time to find speedtrees that looked similar, then cloned them.
I then edited the KUID of the clones to be the same KUID but upversioned (KUID2:X:Y:99) and then drag-n-drop the folders onto content manager.
The same could be done for the profigs, although not being able to see the height and width of the originals would make finding suitable subtitutes more challenging.