Hi all, yesterday I tried to import an *.obj, created in Poser into Bryce 4. No doubt, it is a big one (25MB)! The import was nearly finished, then a message was coming up - error occurs... (out of memory) The import was stopped. Do you know, where the limit is? Is there any chance to rise up the limit of memory in Bryce? I solved the problem by dividing the *.obj in several parts. It's not very comfortable but it works. Greetings Matthias

Oh god, tell me about it! I resolved the problem the same way, but it can become real tedious real fast doing it that way...I'd like to know if it is a problem with the architecture of Bryce itself, a hardware problem, Bryce's OBJ import plugin, or a limitation of an OBJ file created and exported from a program other than Lightwave or wotever the program is that OBJ is native to...I've read somewhere that there is actually a certain limit to the amount of faces an OBJ file/model can support before it packs it in...dont know what it is though...I hope you get some more feedback about this problem, as I'm keen to hear others veiws on it, I tried to allocate Bryce's TEMP or Brycespool or whatever its called to a partition on one of my drives that had heaps more space than its native directory, but unfortunately that didn't help either...

Hopefully I can shed a little light on the problem. When you get that error usually its associated with the graphics card, and memory in the machine. I don't know what you have for memory in your machine but here is what has happened to me. I have 512 megs of system memory, and a Elsa Geforce 2 32megs graphics card. When I tried one time to import a file that was over 100 megs the system gave me the error, went back and exported it in a different format and shrunk the file to about 60 megs. Now on my old machine it would have error'd out around 30-40 megs. You have to look at what you total desktop is and the othere images that are in the picture already, plus remember Win98 or NT or whatever OS you use take space also. I would love to run a test and see what the ratio is for memory -vs- image size is but that will probably never happen. What you can do is watch the total progress and then see right when it stops and gives the error. Lets say for example that it is a 100 meg file and at 65% your machine craps out. Then I think you could safely say your images need to be 65 megs or smaller to work right. I have used this theory and had success with it, but it is a hit and miss proccess, especially if you dont have a way of changing the image size. Hopefully that explains enough to help you.. If you have another more specific question with something, mail me.

Hi, thanks for helping, but we are sure, there must be another problem. - My machine is an Intel PIII Dual-Processor, SCSI and Windows 98, 256 MB RAM, No need for more, cause Windows 98 cannot manage more than 256 MB (128???) - Daniels PC is also Intel P4, single-Processor and Windows2000 installed, 512 MB - Matrox G450, Dualhead, 32 MB RAM You are totally in the right. We also watched the progress of this progress-bar yesterday (what a mess! Nearly 90 % done...). So we could figure out the limit of nearly 22MB. So the difference between your results (40-100 MB) and ours is rather big. We have bought just one version of Bryce and perhaps we'll install this version under Windows 2000 with the more RAM for try it and verify your advice. Thanks again Matthias + Daniel

This is true that Win98 can't manage memory at all but none the less, the program can. And system memory does seem to make a difference but only seems to affect it if you have less then 256 megs. We ran a test awhile back on this forum and found that really what seems to make a difference in what and how Bryce responds is Processor Power (Floating Point Calculations). We had people with machines that had 500 mhz procs with 64 megs, they put in 128megs and times went down, but not by half, just by seconds.. Then went to 256 megs and again just seconds off... then 512 megs, and nothing... So I think for object importing you need working memory, meaning memory the machine can allocate to processing (importing, converting) the image to the screen. Things to watch for is check your taskbar, especially the one next to the time.. Make sure you are running as clean or few of programs as possible. Do a clean reboot and check your system resources, they should be at least 90+%... Hopefully some of this can help you..