Well, the problem is most probably related to having the "Random Samples
" animation mode selected. As commented on another related thread
some time ago:"We have found that XMeshLoader could produce issues when used in combination with Random Samples animation mode."
Unfortunately, we can't do much more in this case as we have no influence of how the XMeshLoader
treats the geometry. We strongly advice to use the "Follow Geometry
" animation mode if any of XMeshLoader object(s) is used. If needed several items with adjusted Frame Offset
can be used. Actually, that's probably the best workaround.
Regarding the need of having marked the "Keep Mesh in Memory
" option for XMeshLoader object used with Forest Pack for network rendering handled by Backburner:
As documented on Thinkbox Software site
: "Keep Mesh in Memory - Keeps the current frame's geometry in memory, so the XMesh Loader wouldn't reread the data from disk when updated. If unchecked, the file will be read each time an update happens (which can be useful if the files are being constantly updated from another copy of 3ds Max, for example)."
Actually, in our tests it works fine even without having this option marked (tested with XMeshLoader 220.127.116.11681). If possible, please send us the simplified scene (containing problematic Forest object(s)) through WeTransfer
to email@example.com to analyse it here. Thanks in advance.