Import of HF causes contour lines in mesh and textures
Posted: Tue Sep 19, 2006 3:29 pm
Hi Aaron,
Proud new owner of the pro version comes up with first question!
When importing terrains to TSE (Torque Shader Engine) the heightmap has to be saved as a RAW file, then a flipped version has to be used in L3DT to generate all of the light maps, alpha maps etc. If this is not done the texture and mesh do not line up correctly in TSE. Don't ask me why.
Anyway, the problem is that when I export the heightmap as a RAW file and flip it in Paintshop Pro, L3DT screws up when I re-import the heightmap. It displays parts of the map in two sections at the top of the HF screen, and the bottom of the HF shows as completely flat.
I tried exporting and flipping the HF as a BMP and as a PNG. When I re-import either of those they come in sort of correctly, but have contour line type steps in the terrain all over the place, instead of smooth gradations.
Any idea what is the best way to flip a HF from L3DT without getting corruption or strange artefacts? Or is this an import bug?
Thanks a lot,
Dave.
Proud new owner of the pro version comes up with first question!
When importing terrains to TSE (Torque Shader Engine) the heightmap has to be saved as a RAW file, then a flipped version has to be used in L3DT to generate all of the light maps, alpha maps etc. If this is not done the texture and mesh do not line up correctly in TSE. Don't ask me why.
Anyway, the problem is that when I export the heightmap as a RAW file and flip it in Paintshop Pro, L3DT screws up when I re-import the heightmap. It displays parts of the map in two sections at the top of the HF screen, and the bottom of the HF shows as completely flat.
I tried exporting and flipping the HF as a BMP and as a PNG. When I re-import either of those they come in sort of correctly, but have contour line type steps in the terrain all over the place, instead of smooth gradations.
Any idea what is the best way to flip a HF from L3DT without getting corruption or strange artefacts? Or is this an import bug?
Thanks a lot,
Dave.