Quote from: WAS on June 07, 2021, 02:55:36 PMI wouldn't expect TG cataloging paths on one machine would work on another machine. Especially if it's based in users file space. I think this is exactly why we have the "gather project" function, to ship it to other machines or farms.
The gather project has been my workaround to this, but it's kind of annoying to always have to do this. The way asset search folder is described, it sounds like it's meant to negate the need for this. I interpreted the description to mean it functions like "Hmm, not seeing that terrain file, oh lemme check this other folder for a file with that name...found it". Is that now what this means?
Quoteis this Windows? Can you post the text of the path you're using?
I keep all the relevant files in a cloud sync folder. Currently using Terragen within a Windows virtual machine. Much of the relevant files are contained along these lines.
Sync Folder->Terragen 4 Projects->Various sub-folders containing my TGD files
Sync Folder ->Artwork Assets->Terragen->Plant TGOs->Various sub-folders containing TGO files for plants
Sync Folder ->Artwork Assets->Terragen->Various other sub-folders of pre-set files
Sync Folder->Artwork Assets->World Machine->Terrain Files
Now, going forward, I could just be careful to keep the file scheme the same across computers. The sync folder is accessed in the VM via a shared folder that's interpreted by Windows as the Z:/ drive, but all my old stuff was not made in this scheme and I would like to avoid having to manually fix a project every time I decide to open it up again for remembering how I did something, re-rendering it, or doing a derivative project.