Thanks for that guide!
I was able to re-purpose an older procedural mesh BP to make the static mesh ready to point sample the texture data. It looks to be working ok, but I am wondering where these odd diagonal lines in my test scene come from. This is from part of Portland.
Wondering if it could just be from the source having subtle elevation changes and using an additive shader to view it. I haven’t used two texture for the precision yet so this is just one 16bit texture. Or could this be improper sampling? It should be sampling every texel but obviously I could have bugs there.
FWIW, I found that to convert from 16bit png to a format UE4 could take, I had to use photoshop to convert to EXR. But if I just converted the 16bit image to 32 and saved as exr it seemed to be applying gamma. If I instead made a new 32-bit document and pasted the 16-bit file into it, that seemed to avoid the gamma issue. Having a gamma issue for a texture like this will bunch most of the points up towards one side.
I’d like to get this plugin installed to matlab so it can write EXR directly but I am not sure exactly how to install it, or if I need to have a separate source file version besides the compiled version I have. http://www.mit.edu/~kimo/software/matlabexr/
EDIT
After debugging the point cloud in CloudCompare (by setting colors to None and reducing point size to 1) I can see that the stair stepping is indeed in the data. I guess using aggressive subsampling causes this? Maybe just the effect of part of a layer just barely overlapping with the low density?
