Started by ajcgi, March 23, 2011, 10:21:08 am
Quote from: Matt on March 26, 2011, 01:58:44 amThe Image Map Shader and the Heightfield Load can also read EXR files (I think both 16 and 32-bit), and 16-bit TIFF files.
Quote from: Oshyan on April 13, 2018, 08:52:09 pmThe Displacement of EXR (and any incoming file without georef/height information) is assumed to be 0-1, in meters. - Oshyan
Quotewhere TG interprets colour contrast as displacement, but the multiplier must usually be upped.
Quote from: digitalguru on April 17, 2018, 07:41:23 amQuotewhere TG interprets colour contrast as displacement, but the multiplier must usually be upped.I think I see what you mean (but correct me if I'm wrong )It sounds like you're looking at a map that may be normalised - that is, all the values are between 0 and 1 and it's only the contrast between those values that give you a sense of the displacement from the original terrain. You then need to add a multiplier to "expand" those values so the displaced terrain matches the original. This is very arbitrary though, and prone to errors. This is why OpenExr is the way to go when using images for displacement and height-fields - the pixel value corresponds directly to height of displacement - a pixel value of 150.675 will displace to 150.675 metres in Terragen. Though a common mistake is to not match the area covered by the displacement image - that is. if your displacement map is generated from a terrain 1000 metres square, then it must be mapped to the same size area in Terragen (or whatever software) for the ratio of height to width to be correct.Another reason why OpenExr is a good idea to use is that, in the main, it is saved as linear data - most software (can't speak for Softimage, though I would hope it would) would read and write an OpenExr and not apply any gamma correction to it - if it did, your height data will change - it must be interpreted linearly.