Hi,
I hadn´t problems like that
I had scenes with about 5 000 to 16 000 spheres and could select them in
about 5 to 10 minutes. ( more than 8 000 objects i guess is the sonic
barrier from there it takes longer in an exponential way)
I discovered that operator staks slows things down and also membership to
groups seems taking longer to select
But if you have a more ore less plain scene than it
Sometimes it helped to eexport my objects as model and import them in a new
scene
Regards
holger
> Von: Luc-Eric Rousseau <lucer(at)Softimage.COM>
> Antworten an: <XSI(at)Softimage.COM>
> Datum: Mon, 30 Oct 2006 19:35:37 -0500
> An: <XSI(at)Softimage.COM>
> Unterhaltung: large selections
> Betreff: RE: large selections
>
> in which version?
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM]On Behalf Of B
> Miller
> Posted At: Monday, October 30, 2006 4:59 PM
> Posted To: xsi
> Conversation: large selections
> Subject: large selections
>
>
> hi all,
>
> I've got a scene with 1200 low poly objects (each object is about 20 polys)
> all under a single null. Selection is a nightmare. Every time I select more
> than about 50 of these objects at once, xsi freezes up and one of my two procs
> is fully burdened for between 10 and 20 minutes, sometimes longer.
> Interactivity is gone, the screen doesn't refresh, etc. Same thing happens if
> I minimize XSI with this scene. Memory usage is inconsequential. All objects
> are frozen.
>
> Any ideas? I'd prefer to leave the objects in a flat hierarchy if possible.
> Anybody have any idea what XSI is actually doing? I've had this problem
> before, BTW...
>
> cheers,
>
> Brett
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
> unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
