![]() |
Only if not already created: a new tyCache object - Printable Version +- tyFlow Forum (https://forum.tyflow.com) +-- Forum: tyFlow Discussion (https://forum.tyflow.com/forum-1.html) +--- Forum: Bugs and Issues (https://forum.tyflow.com/forum-3.html) +--- Thread: Only if not already created: a new tyCache object (/thread-4829.html) |
Only if not already created: a new tyCache object - im.thatoneguy - 06-16-2025 This doesn't appear to be respected. It will keep generating more and more tyCaches. Quote:Export Particles: RE: Only if not already created: a new tyCache object - tyFlow - 06-17-2025 Is there something idiosyncratic about your output path? Non-english characters, UNC path, relative path, etc, or something? Because in normal circumstances this feature is definitely working... RE: Only if not already created: a new tyCache object - im.thatoneguy - 06-19-2025 (06-17-2025, 01:22 PM)tyFlow Wrote: Is there something idiosyncratic about your output path? Non-english characters, UNC path, relative path, etc, or something? Because in normal circumstances this feature is definitely working... Not UNC, but is network drive. W:\25002 Seattle Mother Earth\Assets\MotherNature\DataIO\VegetationCaches\tyCache_tyFlow_Lashes.tyc Is there a maxscript I can step through and debug? RE: Only if not already created: a new tyCache object - tyFlow - 06-23-2025 The check function takes the fully-resolved input path of all tyCache objects in the scene and does a lower-case comparison to the fully-resolved output path - if a match is found, a new tyCache object is not created. If repeated exports are continually re-creating new tyCache objects with that option enabled, then some part of your output path is changing when it's being resolved...hard to guess what, though. You can test with a more benign output path (ex: "C:\temp\output.tyc") to compare whether the function is working in principle. |