CompuServe Messages

Mike, I understand the need to establish a 1-pixel border around the altitude map. After all, I assume the normal disturbance at any point is calculated by conputing the difference between that point's brushmap pixel, and the pixels above and to the left; this means the top row and left column of the brushmap need fake neighbors. But why oh why has Scott decided to initialize that 1-pixel border with 128 values? Why not simply wrap around and initialize the border with pixel values from the other side of the brushmap? What Imagine seems to do: Assign storage for altitude map + border: === === === === === === === — — — — === === — — — — === (— = brushmap, === = 1-pixel border) === — — — — === === — — — — === === === === === === === Assign initial values (I created some hypothetical brushmap values) 128 128 128 128 128 128 128 1 2 5 4 128 128 11 22 55 44 128 128 111 122 155 144 128 128 211 222 255 244 128 128 128 128 128 128 128 Using my idea, the matrix would look like this: 244 211 222 255 244 211 4 1 2 5 4 1 44 11 22 55 44 11 144 111 122 155 144 111 244 211 222 255 244 211 4 1 2 5 4 1 Why don't you run that idea by Scott and see if it's compatible with that actual altitude mapping algorithm? Would this result in a seamless repeating map? Blaq!