Okay, so I've got my textures ready to present to DAZ for their approval, or whatever. So I add all 12 to a new presets folder for exporting, and it's 60MB. So I need to split them. So I take 6 of my 12 textures and put them in an old folder for exporting. Now it's 96MB!!!

So get this... half the textures, but nearly double the size. What is wrong with this picture?

So... on a hunch I create a new folder and reimport the 6 textures. Surprise! 35MB. So I deleted one to clinch it. Yup, it stayed at 35MB.

So, Bryce's hard disk management is as inefficient as its memory management... the preset remains in the preset file even after you delete it. A better way to fix this than creating a bunch of new folders is just to go into Windows Explorer and deleting the preset file, then going back to Bryce and reimporting everything.

AAARRRRGGG!!!! =(

Message edited on: 07/05/2005 06:16

It's completely insane, isn't it? You have my sympathies on this one, although they're not much practical use :-)

Lol Insane is putting it lightly Cambert. 8) It does really suck.... just have to deal with it for the time being. Hope DAZ does something about that with Bryce 6.

I doubt it. I'm just not that lucky, and, I suspect, neither are you. =) As a matter of fact, with my luck, Bryce6 will be Bryce5 with better import features. No, wait that was Bryce5.5...

Takes time... 6 months in testing was a very long time and I am sure testing could have gone on more...But there is a certain time when the Product has to go out to the Community.If DAZ would have taken any longer YOU guys and Gals would have kept Screaming Bloody hell and with VUE coming out and Grabbing alot of the user base from Bryce DAZ had to get it out... Now I am Sure that Memory and Library Issues are there on the Table as a "Next Version" fix...

If you are deleting the texture presets from a preset library, it only deletes the thumb not the texture, so you would need to export all the texures as individual presets and then import only those you want to a blank library preset to decrease the file size.....

But after you delete the thumb, and correct me if I'm wrong, but you can't access the texture. So why leave the texture on the hard drive? You should either have a retrieve option for deleted textures/objects, or you should remove the texture from the hard drive. It's just inefficient.

This has been an ongoing problem since Coral B5. I have learned to keep a new never used library for ALL presets. Simple copy and paste the user libraries before ver using them. Then When I need a new library I copy/paste then rename it. I also use temporary libraries, when making products to broker. After the product is complete then I create a new library for distribution, and delete the temp libraries.

It's true you can't access the mat, however, you can't actually delete it either, so the file size can be huge, when only 3 mats actually show....BTW, I have empty presets for download on my site if you need them...

Aye, it's actually been a problem since Bryce 3D, when they first started implementing this file/library structure. Even worse is the way Bryce will randomly "smoke" your whole folder, for no apparent reason, whenever it gets "too big". Although nobody has actually tested out what "too big" is, and methinks that it's not a size issue at all. Presently my Bryce "Presets" folder is at 1.93GB, with 1.03 GB of "User" objects... And no crashing, no problems with it all disappearing. So this leads me to believe, again, that it comes down to how Bryce saves and loads these .obp's, which are just about the stupidest file-type ever. If DAZ ever did anything right, they'd allow import-only for the .obp's, and convert everything to .obj's internally. But then again, how would they go about keeping Bryce's light system, materials, and curves in place? Methinks THIS is the real reason Bryce doesn't export anything, as opposed to Metacreations slacking off back in the day. It's a great question, "How would we export the lights and materials, too?" But, they did it with the terrains. So we know it's possible!

Zhann-- Which is why Bryce should remove it from your hard drive when you delete the thumb. What possible use is it to be able to delete the thumb and not the texture when you can't retrieve the texture? It just makes no sense. =( Thanks, but now that I've got it figured out I can easily make my own empty preset folders. =) LSD-- Why would you ever want to export the lights? I think that Bryce handles terrains differently from, say, the way it handles spheres? Not sure about that. What's interesting is that Bryce will report the number of polygons in a scene when you load it in. So polygons are involved, somehow... they ought to be exportable to obj format.

Oh yeah, it totally handles things differently between objects. The poly-count from it's terrains? Bogus. Maybe it's real, but entirely worthless from any technical standpoint, unless you're exporting them and need more than you have or something... Why would you want to export lights? Hmm, torches. Castle scenes. Spacecraft. Lasers. Anything that's not dark, basically! The other problem with Bryce and .obj, for example, is that it's primitives don't ever truly boolean. So, you'd have some REALLY messed up objects, if you ever could export them. Nothing would look remotely correct, and you'd have to re-do the boolean process in other proggies. Which would be pointless, because all of the other proggies do modeling faster, more efficiently, and with far less wasted polys than Bryce... No, they can't just "fix" what they've got in this case. For Bryce to be able to export primitives, it will require a complete reworking of that section of the core. As in, delete the whole section and start over... So I doubt we'll see that anytime soon. My faith in DAZ rivals my faith in religion, but I personally believe Jesus will return before DAZ "finishes" Bryce 5.6, 5.7, or 5.8, much less the so-called "Bryce 6" shenanigans. And like I've been saying for years, they need to just skip Bryce 8 altogether. Bryce 9 has a much nicer ring to it! "Bryce 9 : Universe Creator" See what I'm saying? Sounds BADASS!

What I meant was I've never heard of any other program exporting lights. As far as I know Truespace doesn't, Wings certainly doesn't, I don't know about Maya, but Poser doesn't. Naturally there would be a use for it, though replacing lights in the appropriate program shouldn't be terribly difficult (depending of course).

Personally, I agree that nearly every other program is much better for modeling. Therefore Bryce really has no use for an export feature, since any other program is better (unless you want to get your scene from Bryce to Poser, in which case there is a small problem). So unless DAZ adds a lot of modeling capability to Bryce6, I think that the ability to export booleans would be unnecessary.

I think that they should try to figure out something to add to Bryce that other programs don't have. Right now, everything that Bryce has already exists in a better form in another program (most notably Maya). I have no idea what this could be, but it might make Bryce a more desirable package.

Now, if they could make it as powerful as Maya while still retaining the useability of previous versions... but that of course is so completely impossible as to border the rediculous.

Message edited on: 07/06/2005 08:29

Aye, but they COULD focus on what Bryce was originally intended for in the first place : landscapes. Sure, Terragen is badass and Mojoworld is even more amazing. And Vue Infinite of course is just devastating, but there's no reason that Bryce couldn't compete in this arena... Imagine, if you will, a program with Bryce's interface that made it easy to insert, grow, and create plants, for example. I've seen awesome plants in Vue, but Terragen has none that I know of, and Mojoworld just started doing plants... Just an idea. Who knows where DAZ is going with it, if anywhere... Metacreations, they are not.

Unfortunately. =) I like the idea of a more advanced plant and tree system. I'd say if they added that, along with dynamics (again, they could purchase a commercial license for the Havoc engine and use that rather than starting over from scratch), along with one or two upgrades to Bryce's memory and disk space management, I'd be happy with that for Bryce6 so long as they don't overprice it. Leave the full version at $100, and make the upgrade from Bryce5 somewhere around $60 or $70, and I'll probably go ahead and upgrade. But if they just make it another "upgrade" like Bryce5.5 was, will no real visible upgrades (just more stable), I'll be very unhappy and cheerfully ban Bryce until Bryce10. It's really too bad that the original team is no longer working on it. I'm sure that DAZ is very competent, but let's face it: Meta started it all. =)

They just started give them time...And the Makers have and more then likely being Harrased by DAZ on what they really had in Mind when this all started.....

Just FYI, it is 'recommended' that when creating preset libraries that you add a MAXIMUM of 22 items to each library, and then create a new one for additional items, this applies to mat. object and sky preset libraries....anything over that and Bryce will surely balk, it's a fact, and poof! libraries gone. Another good reason for exporting to a folder 'elsewhere' on you hard drive any newly created preset libraries, and be sure to update them fequently. It's also easier to find things that way.... my preset libraries look like this; Main Library -Installed -Zhann1 -Zhann2 -Zhann3 -Downloaded Presets Sub Categories(under each of the main ones) -Plants -architecture -vehicles -space-scifi -interiors -exteriors -etc. These apply to objects and mats, mostly, but it makes finding things and exporting entire libraries easier...