This is almost certainly *not* a platform issue, the differences are likely down to specific setups since none of you are working from the same scene files. If you want a proper test to suss out and possibly issues between people's different machines/OSs, whatever, then there's no way to do that other than using the exact same TGD with the exact same settings.
That being said, I think most of this has been explained through the thread by now. Y and vHeight differences have been explained before, and Matt's quote is a good summation. Whether negative values should work to restrict export on the other side of the planet, I'm not sure, the same idea occurred to me. But I'd really just ask why you even need to restrict distances if you're doing a top-down export.
Only other thing I want to say is that yes you *can* export imported geometry using the micro exporter *if raytrace objects is disabled*. But keep in mind it will just be part of one big geometry export, so your trees or whatever will be part of the same geometry dump as your terrain, and it will be hard to separate them. This is *not* a good way to get a stand-alone object into a different format or anything, but it can occasionally be useful, for example using a population object export for shadow casting or "hold out" or something in another app.
- Oshyan
