CompuServe Messages

>> I hope they fixed another Altitude Mapping bug: the one-pixel border which appears when you use repeating maps.<< Me too, Charles. This one's been around for quite awhile. But at least I found some work-arounds for this, in case anyone needs them. For a flat surface, you can tile maps together in an image processor BEFORE applying them, and not use Repeat. But this won't fix the seam on Cylindrical or Spherical maps. So here's a nasty work-around for that. Create a Front and Back Hemisphere for your object using Subgroups. Take the bump map into an image processor like ADPro, and ROLL the seam so its in the middle of the image. Apply the original bump image to the Front Hemisphere Subgroup, apply the rolled image (with the Brush axis also rotated 180 degrees in Z) to the Back Hemisphere Subgroup. This way you hide the seams of both images in a part of the object where they aren't visible. The bump maps (excuse me, Altitude maps) apparently make a smooth transition across Subgroup boundaries. <retching sound> But it works. Altitude maps are the biggest memory hogs though, and for users, especially with low memory environments, there needs to be a better solution. For the other problem I mentioned earlier, about bump (sorry, Altitude) maps going haywire when locked to a morphed object, there IS NO workaround that I can see. Tim