Cameron Huddlestone-Holmes: |Could you please explain what you mean by the "2Gb limitation on individual |objects"? Is this a hard limit in dx's coding?
That should be "arrays" and not "objects" (my fault), but yes, I think that's the way the original developers have described it in the past. The limit is due to using 32-bit signed integers to index into arrays. |If my original data file is a regular grid and under but close 2Gb, and I |am only slabbing/including for example, will dx be creating any bigger |objects? Depends. If you keep it as a regular grid, probably not. But if you do something which changes the storage scheme (like isosurface generation or an Include with culling on), possibly. |I assume you can avoid the UI bugs in the 64-bit version if you run dx in |script mode? Perhaps. I don't know for sure whether the strange UI values were resulting from 64-bit issues in the dxui GUI code or possibly in the dxexec->dxui communication layer, but my bet is on the former. Just haven't made time lately to dig back into it; 64-bit porting is pretty mundane ;-) Randy -- Randall Hopper (mailto:[EMAIL PROTECTED]) Lockheed Martin Operation Support EPA Scientific Visualization Center US EPA N127-01; RTP, NC 27711
