diff options
author | Justin Clark-Casey (justincc) | 2011-09-09 00:29:59 +0100 |
---|---|---|
committer | Justin Clark-Casey (justincc) | 2011-09-09 00:38:04 +0100 |
commit | 086bf9f15db05ca2be1cf0dda24f8ee7a368988d (patch) | |
tree | 54cf631d998183bb893e644fd4daf1e49bd11b3e /OpenSim/Region/DataSnapshot/DataRequestHandler.cs | |
parent | Fix test failure. Oversight in setting up the tests themselves. (diff) | |
download | opensim-SC_OLD-086bf9f15db05ca2be1cf0dda24f8ee7a368988d.zip opensim-SC_OLD-086bf9f15db05ca2be1cf0dda24f8ee7a368988d.tar.gz opensim-SC_OLD-086bf9f15db05ca2be1cf0dda24f8ee7a368988d.tar.bz2 opensim-SC_OLD-086bf9f15db05ca2be1cf0dda24f8ee7a368988d.tar.xz |
Save the default terrain texture UUIDs for a new region instead of leaving them as UUID.Zero.
Leaving them at UUID.Zero meant that when a viewer 2 logged into a region that had been freshly created, it received UUID.Zero for these textures, and hence display the land as plain white.
On a simulator restart, the problem would go away since when the database adapators loaded the new region settings, RegionSettings itself has code to use default textures instead of UUID.Zero.
This commit resolves the problem by saving the default texture UUIDs instead of Zero.
However, we currently have to do this in a roundabout way by resaving once the RegionSettings have been created by the database for the first time. This needless complexity should be addressed.
This change will also have the effect of replacing any existing UUID.Zero terrain textures with the default ones.
However, this shouldn't have any effect since the UUID.Zeros were already being replaced in memory with those same UUIDs.
Diffstat (limited to 'OpenSim/Region/DataSnapshot/DataRequestHandler.cs')
0 files changed, 0 insertions, 0 deletions