Apart from my machine specs, Pentium2 450 mhz, and 128 meg RAM, (not the worst but still woefully inadaquate) I am curious as to why a model, once optimised in Stream Tuning Studio takes far longer to reload for inspection than to load the original mtx/mts file published for Stream Tuning Studio from Viewpoint Scene Builder.

I Optimised a model from 200 odd kb, the filesize fell right down to 40kb with no visible loss of quality, Exellent! But reloading to the apps full rendered view for inspection took 10 minutes, the hard drive going beserk writing and RAM totally used up. The same thing happens when trying to load the file into Adobes new beta Virtual World programme, Atmosphere. The original unoptimised file, 200kb loads quite promptly, but slows movement noticeably. The same but optimised model, 40kb causes Atmosphere builder to take at least 8 to 10 minutes just to open the scene containing the file! this is way too long to wait, really holds up progress! Once loaded though, movement around the scene is much smoother and easier with the optimised model. I am just curious as to what is taking place here, and if there's anything I can do to minimise these long initialization times.

We've found the same problem, i couldent understand why some models take some long to load, often being under 150k. It seems that if the models are not run through tuning studio they load a lot quicker, although file sizes are obviously much larger.

Is there a work around this as we've also found it with our Atomsphere virtual world:

http://www.plannet.co.uk/atmos/

We ran all the models through tuning studio and the world ground to a halt with a lot of write to disk action and a big hit on ram. Once we re-uploaded the non optimised version all was fine.



Smithee

Do you remember what type of image compression you used, JPEG or Trixel NT?
If you could please email me (mpetrov@viewpoint.com) your file we will be able to analyze the problem and give a definite answer.

We have the same problem. The hard drive is running and memory is being used up.