>The app may need to focus on the area around a tile boundary (which is why >I'm even working with tile merging), so the merged output would have to be >pre-Reduce -- for that area at least. > >I might combine my simple LOD technique with your Slab-Append approach, or >write a custom loader. I'll have to think about it. > >Thanks, > >Randy > >-- >
You may want to use Greg's approach to get the pieces you need around the "4-corners" then follow up with mine since Construct reinstates the product array and mesh array for the positions/connections. I wonder if you could use "!import" to call a dx script that did the preprocessing then passed your interactive net only the resulting smaller patch? This reminded me of a project I did 6 years ago where we had the whole NYS elevation and landuse, veg map, etc. to work with, but looking back I see the GIS folks has already pasted each whole coverage data set together, so my routine was to open a reduced subset of the base map (whole state), let the user browse the area of interest; using either 2 Probes or a Probelist (I forget which), they could indicate the rectangle of interest (which of course was visible as they changed Probe positions), then when they said "go" the corners of that rectangle were passed to a "!import" routine that externally subsetted from the complete coverage data sets (I think elevation was 72Mb and veg was 45Mb or something like that) and returned only the subset at user-specified resolution (up to 1x). In other words, there was quite a bit of "net" and user-interaction before the actual Import, which is kind of unusual since most nets start with Import. But as I say, my problem was easier since I didn't have to tile on the fly. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
