That all makes sense. I will try all those recommendations
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Quote from: Remnant on May 30, 2014, 01:27:12 pm
Also, it looks like the axis are flipped in the terrain set: What is labelled X axis actually goes north/south, while Y goes east/west. This will import very poorly into WM since it doesn't match the usual coordinate system convention (X,Y ordered where x comes first in the coordinate pair, and runs east/west). Re-label the tiles appropriately and you should be OK!
Quote from: e2clipse on May 30, 2014, 12:47:45 pm
Maybe you should use the selectors seperatly and combine them as a next step
So 1 time file out to height, one time file out to slope then take a combiner and choose he best combiner method maybe?
Quote from: Remnant on March 20, 2013, 02:02:29 pm
YES) If you have multiple input files, and they fit neatly onto a grid, you can use a Tiled File Input device to bring the entire set of heightfields into World Machine in one swoop. They just need a naming structure something like this: mytile_x0_y0, tile_1,4, etc. Where the first and second numbers are X and Y grid coordinates of the heightfield. This works great for sliced terrain datasets, but if you want to have more loosly-defined locations (perhaps with overlap) then you will need to do something else...