+- tyFlow Forum (https://forum.tyflow.com)
+-- Forum: tyFlow Discussion (https://forum.tyflow.com/forum-1.html)
+--- Forum: General Discussion (https://forum.tyflow.com/forum-2.html)
+--- Thread: cache from beta can not be read by latest tyflow (/thread-4016.html)
cache from beta can not be read by latest tyflow - caypiranha - 12-14-2023
Hello Guys,
I am having here tyCache sequence made once by the open beta. Same to an Alembicfile.
If I want to load this into the latest tyFlow version 1.xx.xx it is not recognized by the tyCache reading Object.
Is that intentionally to cut the last bridge between the Beta and Version 1.x or am I making something wrong?
thanks in advance!
RE: cache from beta can not be read by latest tyflow - tyFlow - 12-14-2023
That's correct...it wasn't done intentionally just to cut off the connection between latest and BETA, but the compression scheme I now use was changed a while back in a way that makes it impossible to load older caches by the latest builds.
RE: cache from beta can not be read by latest tyflow - caypiranha - 12-15-2023
Hi Ty,
Yes, I understand. Technically they are too far away now. Bad luck, if someone simulated a Day long or so... isn't there a converter for it? I unfortunately use TyFlow very occasionally. This time only for a few hundred of drops pouring in a melter. But I need to cache them before uploading to a renderfarm (or?) And I don't want to do that in Pflow, since I can't get the drops there to stand still /freeze, or in other words: don't have time to take time on Pflow - which I use almost never =)
RE: cache from beta can not be read by latest tyflow - tyFlow - 12-15-2023
If it's just particles, you can export to PRT and then load that into a tyCache (tyCache supports PRT loading). If it's geometry too (shapes and such), you can export to a different format (ex: Alembic).
RE: cache from beta can not be read by latest tyflow - caypiranha - 12-19-2023
thanks for feedback. I´ll give it a try with alembic in this case.
RE: cache from beta can not be read by latest tyflow - caypiranha - 01-06-2024
short back to this topic: yes, I am having geometry. So I exported as alembic. Connected *.abc to "Alembic Object" in Max.
Works well with one exception, that assigned Material is somehow differently interpreted and is not looking as expected.
The screenshot shows static objects of baked edit polygons. And the strange transparent /chrome-looking drops are the alembic obj.
Sharing the same material.
Where´s the trick?
RE: cache from beta can not be read by latest tyflow - tyFlow - 01-07-2024
Try importing your ABC with a VRayProxy object, if possible. It properly assigns material IDs whereas that functionality does not work in vanilla Max.
RE: cache from beta can not be read by latest tyflow - caypiranha - 01-08-2024
Thank you for your feedback. I will try this via VrayProxy as well. For now and somehow, breaking, linking to tyCache and render it - does it now pretty well.
RE: cache from beta can not be read by latest tyflow - caypiranha - 01-08-2024
...trying to do it with tyCache. How do I avoid the following issue to me:
The Polygonblock and the TyCache node are assigned once with a VrayMaterial and another one with a FastSSSMat.
Both are sharing, that the light cache give a very different appearance compared to the Polyshell underneath.
Only when the final rendering goes along, the VrayMat make finally no difference. The FastSSS still gives in final rendering
a darker appearance. What´s the deal with that?
normal VrayMat. strange LC
...but rendering is fine:
FastSSS: strange LC also here, but rendering does somehow cover what probably went wrong
(like the few greyish ones in front of where the picture has been already finaliced.
using VrayProxy produces the issue to me here, that it is placed somewhere in the Pampa where I never would find it except pressing Z