My testing has set SizeX and SizeY in the Region.ini file and the right terrain things happen. If SizeZ is not specified in the Region.ini file, it defaults to 4096 (Constants.RegionHeight) which, after looking around, is only used by BulletSim to constrain some of the physics collision scans. I'd be interested to hear what is really happening when it fails for that user. -- mb
On Sat, Nov 29, 2014 at 8:30 AM, Kevin Cozens <ke...@ve3syb.ca> wrote: > On 28/11/2014 9:10 PM, Justin Clark-Casey wrote: > >> Yeah, I've only removed it from config generation, it still exists >> everywhere else in the code. If it is used in the future it's a one line >> change to start putting it in generated region configs again. >> > > FWIW, in 0.8-post-fixes the SizeZ parameter affects terrain in a var. I > had someone who was setting up vars. They omitted the SizeZ parameter from > the regions INI file and the terrain wouldn't appear as it should. I > haven't seen it first hand but I'm told the terrain was around the 0m mark > or below. > > -- > Cheers! > > Kevin. > > http://www.ve3syb.ca/ |"Nerds make the shiny things that > distract > Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're > | powerful!" > #include <disclaimer/favourite> | --Chris Hardwick > > _______________________________________________ > Opensim-dev mailing list > Opensim-dev@opensimulator.org > http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev >
_______________________________________________ Opensim-dev mailing list Opensim-dev@opensimulator.org http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
