Just wondering if anyone else has M3 and having issues impoting into Bryce? I loaded the new M3 lastnight. Posed him, added the free boots that came with it and then exported as an .obj. When I went to import into Bryce, I got the "Unexpected Error (out of memory)". Got this about 10 times trying to get him in there. I went back to Poser and removed the boots and he finally loaded into Bryce. But it took about 10 mins to get in there. My system is a P3 933 Mhz, with 512 RAM. (System tool says I have like 360 RAM free when trying to import). Anyone have any ideas how to work around this??? I have e-mailed DAZ, but never sure if these guys will reply or not. Thanks for your time all. Any help would be appreciated. -Bruce

Did you run the object group through Grouper before importing him? Apart from that I can't think of why it would create such a problem on importing. Maybe M3 is just a massive obj, do you know how big the file is? Catlin

michael is a 11 mb monster when exporting from poser,but i had no problems with importing him into bryce 5,ok i have 2,4GHZ and 1024mb ram.

Yeah.. 11 MB raw (no clothes). Sorry, never had to use Object grouper before.. what is it? Where do i get it? Maybe that will be the answer. Thanks again, Bruce

I found Grouper. DL'd and installed. Read through the tut on his page etc. Looks to me like I need to upgrade my PC. It still refused to load the M3 with the boots!! All the grouping only managed to reduce the file size from 28.1 MB to 27.8 MB. Woo hoo! LOL Maybe I am not using the grouper correctely, but I did what I thought I was suppose to. May be time to go to a P4 processor. Thanks all for your helpful comments. It was much appreciated. -Bruce

Now, what you can do is use a trick. Pose Michael with the boots. Enclose both in the primitive box. Export Michael and box, import in Bryce, delete the box. Don't touch anything. Export boots and box, import in Bryce, delete the box. Now you have Michael and boots in their proper places, texture, group, enlarge, whatever.

What difference does that make Erlik, I've never heard of doing that before?

The imported objects always get a size of 40.96 units high, deep or wide. if you make a cube around michael the cube gets 40,96 units. if you use the same cube for the boots that cube will import as 40.96 units too. because the original cube was the same size for both the boots and michael the scale of the two seperately imported files stays correct. if you wouldn't use that cube while exporting you'd have a michael of 40,96 units high and a couple of boots that are also 40.96 units high. result is that michaels boots don't fit anymore. Splitting up michael and his boots in seperate files will be less hard on you memory during importing.

I am sure this will work, but concidering how long it is taking me to even use M3 in Poser as well, I think I am going to put M3 on hold until I can upgrade my PC. Thanks all for your help. It was greatly appreciated. You guys are the best. -Bruce

Thanks for the explaination Rayraz, it's amazing the amount of info you can pick up in this place. 8)