Results 1 to 4 of 4

Thread: Mapmaking in Bryce. Any advice?

  1. #1
    Professional Artist Carnifex's Avatar
    Join Date
    Feb 2008
    Location
    Sweden
    Posts
    220

    Default Mapmaking in Bryce. Any advice?

    I just read another thread (Nematodes) about making maps in Schetchup and Bryce.
    I tried out to make city maps in Bryce 6 some years ago but it seemed to slow down to a halt when I added too many buildings. (I think I remember that it took hours to save the file.) Have any of you had similar experience? Maybe I did something wrong (I think I used quite high res textures as I wanted to be able to zoom in).

    Here's an old snapshot:
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	fredport3_center.jpg 
Views:	151 
Size:	148.1 KB 
ID:	50844  
    Last edited by Carnifex; 12-31-2012 at 07:11 AM.

  2. #2

    Default

    Hi Carnifex -

    Thank you for mentioning my thread which is over in the 3D forum.

    I don't know if I can provide a solution to issues that you've experienced with Bryce. I'll say up front, the best advice I can offer is probably - isolate the nature of the problem to as specific an issue as you can, then search the daz3d knowledgebase/user forums for an answer.

    FWIW, here are some of my experiences. Perhaps they will be useful to you or others who read this thread. They are applicable to Bryce 7.

    Export from Sketchup to Bryce has some gotchas. For example, Sketchup instanced components don't import into Bryce. I found that it worked well to

    - texture a model in Sketchup
    - explode the model in Sketchup
    - group the model in Sketchup by texture
    - export by group
    - import the group into Bryce and texture it

    Other approaches will certainly work.

    Not knowing details, I can't say how your textures might impact Bryce.

    When it comes to anything in 3D modeling, CPU power is crucial. For example, I began my project on a P4 2.4Ghz machine. By the time my Bryce file grew to about 50MB, any operation had become uncomfortably slow. So I got an i7-2600 3.4Ghz machine and it handled my model well, til the file grew to about 110MB, at which point it didn't.

    With the slower computer, I could make Bryce crash while applying a texture to a big complex object. I could solve the problem by splitting the object into smaller groups, but I also found that the problem went away when I transferred the project to the faster machine.

    Render time varies greatly depending on options you select. In particular, Shadow Softness, True Ambience, and HDRI/IBL lighting will drastically increase render times. Like, an image that renders in a few minutes without these features takes maybe a day to render with them turned on. Probably ditto with volumetric planes and volume materials.

    There are other things that can bring things to a halt in Bryce, like display modes more complex than Default Wireframe.

    As you work, test render regularly to make sure that the project remains within the limits of your patience and your computer's capabilities.

  3. #3
    Professional Artist Carnifex's Avatar
    Join Date
    Feb 2008
    Location
    Sweden
    Posts
    220

    Default

    Thanks or your advice Nematode. I now remember that the big problem was saving the file - it literally took hours (maybe 2 hours?) to save the file. Rendering is one thing but that you could plan ahead - but long save time is actually more troublesome I think.

    I just installed Bryce 7.1 and I have a fairly good computer (although a couple of years old now) so I'll try it out today - let's see where it goes.
    Last edited by Carnifex; 12-31-2012 at 06:18 AM.

  4. #4
    Guild Member ManOfSteel's Avatar
    Join Date
    Mar 2012
    Location
    San Francisco, CA
    Posts
    86

    Default

    Unfortunately, Bryce is not suited to a super high polygon count and large textures. It's my favorite 3D program but it has its limits. Here are a few things you can do to manage memory better.

    1) Let Bryce do the material if possible. Bryce is great at doing glass, metals, stone, etc. By contrast, applying an image texture requires more memory and looks terrible. So forget using a picture of glass, or a picture of water, or a picture of brass.

    2) Scale down certain oversized textures. You don't need a 4000 X 4000 pixel picture of a doorknob handle or a porch step. Again, if possible, let Bryce handle those with a suitable procedural texture, or reduce the 4000 X 4000 image to maybe 2000 X 2000. Depending on the complexity of the image, that's about a quarter size (in memory) of the original and you might not even be able to tell the difference even at a close zoom.

    3) Download and install the Large Address Aware plugin. Bryce is a 32 bit program and thus is wired to only recognize a maximum of 2 gigabytes of memory. By installing this little program, you can enable 32 bit programs to recognize more memory, in most cases (as I understand it) up to a little over 3 gigabytes. I don't have time to look for the download page now, but I'll look for it and post it here. I noticed a definite improvement when I enabled it for Bryce.

    I'm back. Here's the download page for the Large Address Aware program.
    http://www.techpowerup.com/forums/sh...d.php?t=112556
    Last edited by ManOfSteel; 12-31-2012 at 09:38 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •