So...after watching any info i could find on solaris masterclasses and in forums i am stuck.

it seems no matter what i do i can`t have a single final.usd file that contains my scene.i have animated trees with variants working as expected but when i try to import my fuid sim mesh Geo there is no way to get it work.

I use a SOPimport node that grabs the file cache of the sim surface.It imports the animated geo when working in solaris but when i use a usdROp at the end of my network to wrap it on a final Scene file that contains everything i am forced to use the "Flush data after each frame" cause it`s too large to fit on memory.

So i dont get a single "final.usd" file but a per frame "final.$F.usd" files.
If i start a new scene to get the whole Shot with a single import it gives a warning to load the file sequence with the Geometry sequence node.Despite the warning it seems to work ok but as the docs suggest it creates a layer per frame which is not advisable.

Geometry sequence on the other hand brings in the hierarchy of the scene but everything is with the override symbol in the scene graph view and no geometry at all.

Tried exporting only the cached sim surface with the usd export Sop but when i import it it seems its loading all Frames at memory.i Have 128GB+80 swap and it crashes!

No matter what i tried (sops USD export,single file per frame frame final usd,Stitching,creating a single file just for testing with 10 frames p.e so it can fit in memory) nothing works.Even tried using an initial frame of the sim referenced and the connect to geometry sequence lop (cause that way i could get the geo.)

I`ve seen a similar post that had the same struggles and he pretty much wanted the same thing.A final "Shot "file containing references to the Big caches.

The other animated assets of the scene doesn`t seem to have a time dependent icon on them and if plug a usd export and Render current frame only i get them animated in a single file.

Thanks in advance.

You can use "Flush data after each frame" even without putting $F in your file name. If you do that, it appends each frame's data to the same USD file. You get the benefit of only needing to have one frame of data in memory aat a time, without having to deal with per-frame USD files.

The downside of "flush data after each frame" is that the final single USD file will often end up being larger then if you left this toggle off. But as long as you're careful about authoring only time-vary data as USD time samples, the difference should be pretty small.

So it seems it was my misconception that the 1 to-4kb generated usd files that where referencing the bgeo cache would do the trick.
It has to be a .usdc cache with the actual data in it. Of course it worked inside solaris cause it was a live sop import.

I am caching this way right now and of course i get the .usdc slowly consuming any free disk space the disk had and a single "final shot" usd.

I feel silly!

Thanks for the info!