I came across a problem with the new Large Mesh Splitting option of XSI
v5.x where the process of actually splitting the mesh to reduce memory
load took ages for certain types of geometry. Since your scene renders
fine in v4.2, you might have hit the same problem. Try a Large Mesh
Splitting value of 2 (the maximum possible), which reduces the impact of
this feature as much as possible.
Let me know if that helps. Cheers!
-André
Rainer Schmidt wrote:
I am stuck... Seems to be a cluster related problem.
I tried to import a .obj. That failed.
I used C4D to import that .obj into C4D and it worked just fine.
Textures and everything.
Now I exported that again as .obj with C4d and can read it with XSI.
Great...
Whatever was 'wrong' with the .obj in the beginning was ironed out by
C4D.
After the import I end up with 1 polymesh with 35 clusters with
material/texture assignments.
NOW, after loading it takes about 9 minutes on my Opteron 280 box to
have the first render region starting to render.
Render itself takes a few seconds. Default settings. No
FG,GI,aliasing...
After that, it renders as usual. Quick. I can add lights etc. All good.
The moment I define another cluster for a new texture. Or delete a
cluster,
, modify any cluster, it takes about 9 minutes again to have the next
render region start rendering.
The memory stays pretty much the same during the 9-11 minutes. One
CPU is maxed out and I have no idea what the heck is going on.
I exported the mesh as .xsi. Shut everything down, started again and
imported the .XSI file just to encounter the same problem.
Any ideas how I can get rid of that problem? I have to work quite a
bit on the model... sighhhhh
Rainer
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
