We are running into a bit of an issue which requires us to work around it by removing xmesh from the scene (deleting history), otherwise we cant work with the scenes. And removing xmesh removes our ability to easily update to new versions
The problem is that xmesh reloads the full cache every time you step onto a frame, even if that frameās cache was already loaded. This is something we could live with (although no optimal), but it does that even for single frame cachesā¦
so say, you have a static geo of a high rez destructed sim, that would not change at all. Its a single frame. But every time we move the timeslider in maya, xmesh reloads the full cache from disk The only way we can work in these scenes is to remove xmesh
Do you have a rough timeline as to when to expect that?
The reason Iām asking is that we are actively using this in production, and its becoming an issue that makes xmesh unusable. The caches are huge, its a fracturing TP sim of an extremely detailed mesh. If we keep using xmesh, it adds 10-30+ seconds whenever the artist changes frames, even though the cache is a single frame currently (to be fully animated later). For animators thats a killer
Are you loading the exact same xmesh file for each frame, without even changing the frame number part of the filename? (Either by enabling āLoad Single Frame Onlyā, or by setting the frame range to a single frame?)
In this particular case, it was an xmesh with 2 frames only (frame 1000-1001), so in the whole range of the animation, only one sample would be used (the shot was in range 1001+ )
