Metaballs are great, but are not so great for fine details I've found (at least I've never been about to get fine details from them lol). Lattices often work better. Trouble is, there's this annoying line running along the edge. I know what causes it, but I have no idea how to fix it. This lattice is running at 1024x1024, and still has a line. I'm going to try something in Paint Shop Pro real quick...

Okay, this is better but still not great. I made the map in PSP and cut off the edges abruptly, as you can no doubt tell from the side pixelation. Help!?!?

Attached Link: Gear Trinity

No matter how big the resolution you use, nor how you fiddle with the terrain/lattice itsel, you will always have a seam. You can get it fairly small, but there will always be something showing.

All you can do is try to hide it with the angle of the camera, or with textures. The same is true of terrains and lattices in Vue.

AgentSmith

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

I thought frogdot had an idea or a solution to this a couple years ago... could be wrong though. Maybe if he sees this thread maybe explain a little... like I said though, I could be wrong. Joe

When I don't want seams, I export the lattice to Wings, select the edge loop along the seam, and push the verts into place.

That must bring Wings to its knees to import such a big poly mesh! AS

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

I think AS's problem could have been solved by using Gear Maker....

Available on Amazon for the Kindle E-Reader

All the Woes of a World by Jonathan Icknield aka The Bryster

And in my final hours - I would cling rather to the tattooed hand of kindness - than the unblemished hand of hate...

Jay, that sounds like a good idea. I was about to just leave Bryce competely and model everything in Wings, except when I needed to model something with primitives (as I believe Bryce is very good for this). This would also have the added bonus of not having Bryce save those large bump maps both when I save the file (I have a slow harddrive), and when I render the final pic. At least I think Bryce saves it. Instead it will just save the object; I think this should be faster? Thanks and hope Frogdot does have a way around this.

That was one sent to me from Incarnadine (16-bit tif). ;o) AS

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

Yeah, any images in Bryce are used uncompressed. So, a .jpg used for a bump map will turn into the size of a .bmp inside of Bryce. It's usually best to try to use a seamless/tile-able image for texture & bump maps, that way you can just scale them up, to increase the texture density, instead of having to use giant images. I usually try to just use 512x512 for maps like that. (texture, bump, diffusion, etc) Sometimes it just has to be bigger, though. AS

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