When will we be able to export full Bryce scenes, or even Bryce-made objets ? Why are Bryce (that we purchased !) scenes & objects impossible to export to another software ? Are *.br2, *.br3, br4, *.br5 scenes and Bryce-made objects a monopole, or either if I don't understand, is there anybody or any software able to convert the *.br files into another 3D format ??? Almost any other graphic software exports many extra-format files now...And if I dcided to buy "Lightscape", which is ONLY a renderer ?...Am I bound to Bryce-rendering for the rest of my life ? My question goes now to Corel first, of course but I would have asked the same if it was still Metacreations. Am I carzy to ask this kind of question ? Can anybody ELSE (why not Corel) give me give us all_some explaination to this state of fact and "fatality" or could answer this ? Thanks if any of you guys do it ! liftan( Alfie)

For whatever reason they choose it all to be proprietary. If it were openable(?) in other apps I fear the prices would also be like the other apps.

the only native bryce objects worth exporting are the terrains and we have had that feature since version4

the rest are just cubes balls and pyramids etc.

what other native bryce objects do you want to use in your other 3d programs??

My website

YouTube Channel

The reasons exist, although they don't make up for Corel's lack of foresight with Bryce 5. Fools. So much potential wasted, I'd like to see them incorporate morphing and whatnot myself. Anyway, there is a third party utility called Poly Trans, which is the Riptide of the 3D world. It will convert any format to any other one, not just the most popular ones but like 30 different file types. I'm not sure yet if they have a .br4 or .br5 conversion, but if anyone does it's them. The "reason" is simple, it's all about roots. Bryce was originally just a plug in for making quick landscapes and skies in Photoshop, KPT Bryce. I don't think they intended to turn it into a studio platform, but dammit they should! They could charge more, it would still be worth it for some of us, perhaps make a Bryce 5 Studio version like they did with Ray Dream and Carrara... Maybe I've been informative... (goes to smoke)

yep QUiks got it right if you want all that kinda stuff youre gonna have to pay for it its some kinda math thing and math is money in this business more math more money .......the four "M"s.......hmmmmm

Well, my guess is that no matter what application you're exporting to, it wouldn't look the same... If you do a scene in Bryce, there is lighting, whcih is going to make or break the scene, as well as camera positioning, which is also going to determine what the scene looks like.. You bring a bryce scene into another application, they have a different camera, lighting is different... You have no scene... Also, another application wouldn't interpret the skies... That would be lost also... So, what are you really exporting?? A couple of models you imported and a terrain generated in Bryce??? You could export the terrain, import the models in the other application and start the scene there.. But then you wouldn't have the skies... Anyway, exporting a bryce scene into another applciation is no good, cause it's not going to give you option to tweak the bryce parameters... But maybe that's not what you mean...

I for one would love to be able to export the "little" spacechips that i've made in bryce, and a few other things, such as the Junk and the Sydney Harbour Bridge and Opera House. But no, they sit forlornly on my harddrive, waiting hopefully for the day when they might be used in other programs. Just my 2 cents worth.

Poly Trans does not convert any Bryce files, nothing does. Lightscape 3.2 ($600) does seem to be a renderer only and only opens .dxf and autocad files. I suggest checking out Truespace 5.1 ($300), Amapi 6 ($400), or Carrara ($400). Lightscape can render much better, but with what looks like no modeling abilities... I will take a wild guess that true exporting of absolutely anything/everything out of Bryce might roll around probably when Corel allows third party developers to create plug-ins for Bryce. Per a question I had asked Conan Hunter (Program Manager for Bryce 5), he said that Corel would indeed allow plug-ins for Bryce, the real question would be when. For now, Bryce can only export terrains, symmetrical lattices, and objects that have been imported in. You would then have to take it all into another program that allows true/full booleaning and exportation of the complete finished model. Now, I have exported grouped primitves out Bryce that had been imported in, I for one don't know how big the group could/would be and the export still work, mine were small. What I have is a collection of primitives that I can use in place of Bryce's primitives. This later allows me to export a model made out of Bryce with said grouped primitives. But a primitive and a terrain cannot be grouped together and exported...back to square one. And, again the fact that you would have to re-build it all in another program. Too many people want what you want out of Bryce for Corel or another developer not to make it happen one day. All those peole would be all to willing to pay for that new version or new plug-in...too much money to be made to ignore. Hope my ramblings helped somewhat - Agent Smith

Contact Me | Gallery | Freestuff | IMDB Credits | Personal Site
"I want to be what I was when I wanted to be what I am now"

Agent Smith is right. It probably will happen sooner or later. (I vote for sooner) Actually, I've built some pretty complex things in Bryce, and mine are junk compared to what aother Brycers have done. I, and I'm sure they, would like to export their Bryce stuff.
And if you want the real reason that Bryce hasn't exported up to this point...if you were Metacreations and you sold Ray Dream as a modelling program, why would anyone buy it if they could make Bryce their modeller? You could at the time model almost anything in Bryce that you could model in Ray Dream and Ray Dream had some pretty annoying bugs that Bryce did not. Heck I did ALL of my rendering in Bryce.

Why are you modeling in Bryce anyway? Its primary strengths are its fractal textures and atmospherics. The fractal terrain generation is also very strong - but other standalone proggys do that too. Like somebody else said, if you take the sky, textures and atmospheres away from a bryce native scene what do you have? Not much, and certainly not worth exporting as a whole. At any rate I view Bryce more like Quark - it's a 3D layout program - I don't make anything there, I just assemble my elements, format them nicely and render. You wouldn't expect Quark to be a vector drawing package too, would you? What I'd really like is for them to make object handling a bit easier - once you have a few dozen objects in the scene it gets tricky to grab just the right one. (especially if you were hitting a string of inspiration at the time and didn't name or family set anything) And collision detection (sigh) Just my .02 cents worth :) Lyrra

I agree Lyrra, it is very difficult to position things in Bryce. I prefer to do all my basic positioning in Amapi before importing to Bryce.

Right.... We could go on for days about the benefits of other programs. We are artists, these programs are our brushes and canvasses. Some tips for the last two newbies : When selecting objects in Bryce, there are many options to make life more manageable. I created a 5,000+ object castle starring families (for texturing purposes mainly) and that little, oft-missed key on your keyboard : The CTRL key. If you don't have one on your keyboard, I suggest upgrading to keyboard 2.0. It rocks, makes selecting ANYTHING in Bryce a snap, no matter how complex a scene you've managed to create. Combine that with the shift key and BOOM! Positioning stuff in Bryce is much easier with a good 3D card, like the Oxygen Labs VX1, but I admit I wish it had collision detection or something equally preposterous... Naming objects is important, like Lyrra said, but between families and the Control key, one can manage anything in the universe. If one were so inclined.