Sat, Sep 21, 4:21 PM CDT

Renderosity Forums / Bryce



Welcome to the Bryce Forum

Forum Moderators: TheBryster

Bryce F.A.Q (Last Updated: 2024 Aug 28 6:28 pm)

[Gallery]     [Tutorials]


THE PLACE FOR ALL THINGS BRYCE - GOT A PROBLEM? YOU'VE COME TO THE RIGHT PLACE


Subject: rendering time for large picturesin Bryce 4


Brasseur ( ) posted Sun, 02 July 2000 at 9:50 AM ยท edited Wed, 31 July 2024 at 7:37 PM

I've bought Bryce4 just now, and 've always worked with Rau Dream studio and Poser4 . Bryce is good for small and not complexes scenes; I've tried a scene with 4 imported and multitextured Poser models, and a few imported objects from RDS : the result :a scene file of 70 MB space, and no possibility to render at 300 dpi (for publication artwork)and 2000/2000 pixels. So big files are quite easy to render in RDS, but not at all in Bryce . Have somebody an idea ?


willf ( ) posted Sun, 02 July 2000 at 10:38 AM

I normally render scenes without antiallasing and then use a slight blur filter in photoshop. Can't see any need to soften the render in Bryce & then sharpen it in photoshop for printing. There are some "tricks" to speed-up time and keep file sizes smaller but i'm not too familiar with them. I believe there might be some info in the tutorial files.


lilmikee ( ) posted Sun, 02 July 2000 at 10:52 AM

You are able to save image as 300 dpi for printing. I recently had the same problem and was told to go to file and select render to disk and there you can set your resolution. Hope this helps...


lilmikee ( ) posted Sun, 02 July 2000 at 10:54 AM

Also btw, I recently got rds about 2 months ago because it was a great price in order to create models for poser or bryce. Is there any good cd tutorials out there for it since it's hard to find stuff for it now that it doesn't exist anymore?


Brasseur ( ) posted Sun, 02 July 2000 at 2:11 PM

RDS is not so difficult to work ; except maybe the free form modeler, the rest is quite logical and fast to use. Load at the beginning the 3D assistant to help you create conventionnal forms. You can find some specific tutorials on the web (b.e.http://www.geocities.com/SiliconValley/Heights/5696/)


plmcelligott ( ) posted Sun, 02 July 2000 at 3:55 PM

I only use the on screen render for tests. For final output at full resolution, I will always use render to disk. It is noticeably faster than a screen render.


bonestructure ( ) posted Sun, 02 July 2000 at 4:55 PM

I've never had a problem rendering complex scenes in Bryce. Yes, they can take a while, but if your work is good, it's worth it. I just like the way Bryce renders look

Talent is God's gift to you. Using it is your gift to God.


Ironbear ( ) posted Tue, 04 July 2000 at 11:51 AM

Yes, bryce files can get fairly large. I'm looking at my vault and noticing that my "Temple of the Lovers" file is 60mb and "Vampires in the Mist" is 35.5mb. It is worth it though. One thing that I have noticed is that on my machine, when I'm dealing with high ambience .mats or lots of transparence/reflection, imported meshes seem to render faster that bryce primitives. Don't know why, that's not what the tutorials tell me should happen. One way to speed up and cut file size is to: a) work w/o textures untill you get final positioning, b) one every thing is where you want it, eliminate the details that cant be seen. Then texture and render. With groups, work in solo mode as much as possible. Also, group complex objects: the raytracer calcs wether it hits the group, then the sub group, then the object. Wherever you can, use image textures. They don't necessarily cut down render time, but they're smaller than geometry. Hope this helps...

"I am a good person now and it feels... well, pretty much the same as I felt before (except that the headaches have gone away now that I'm not wearing control top pantyhose on my head anymore)"

  • Monkeysmell


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.