Ok, got the basic stuff done, work folder setup using OA.exe. (Copied the folders in, depbo'd the 3 from DTA into P:\root (Bin, Core, Languagecore) etc, presumably it was all good because I could fire up buldozer fine with just the elevation data in place (XYZ grid imported)
So, got my Sat_Lco png & mask ready, mask was just a single layer, using brown. I simply wanted to be able to see the elevation with the satelite layer to see in 3d how it was lining up. Going over the background image method through visitor wasn't really ideal for this.
So, imported the sat & mask (legend & layers.cfg also ready). Import goes fine. So, launch buldozer. It does it's thing converting the pngs to paa without a hitch, but, it just doesn't start afterward. The "Preparing surface materials" text shows, the line goes back and forth for a bit and then just stops. Doesn't crash, CPU is still showing 50% (assume 1 core maxed), but buldozer never actually opens the map.
FWIW, map grid was 2048,
cell size 6
area 12288m X 12288m, sat & mask both the same.
Texture size 48m
Sat grid 64, sat segment 512.
The one texture & rvmat (from a tutorial on here) used in the layers.cfg is residing in p:\myprojectname\mapname\data The layers folder is in data, with the thousands of png, paa & Rvmat files present. Opening some of the paa's up they look fine.
Map pew is in P:\projectname the sat & mask etc were in the source folder.
Any ideas of where to start looking for a cause greatly appreciated.
Should I revert back to plain Arma2 used for buldozer? Tried reimporting twice, but after an hour or so each same end result. Double then triple checked through the tutorials and my file structure, and didn't see anything out of place.
And an unrelated question: Since I imported the elevation data using an xyz grid, do I still need a pdl file? I only saw them mentioned in conjunction with greyscale png elevation imports. Without one, prior to the sat import troubles, the elevations looked fine in buldozer, just hard to judge things when it's all plain white. I should have known I'd turn an "easy" import of the satelite imagery into a multi hour fiasco.