| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
initial client update to Scene.AddSceneObject() from some of the SceneObjectGroup constructors
* I think this has been done cleanly from inspection and testing, but if prim creation or load suddenly starts playing up more than usual, please open a mantis
* This also has the effect of stopping the archiver generating ghost in-world prims
* Some code dupliction also removed
|
| |
|
|
|
|
|
|
|
| |
scene, rather than on creation of the group
* Adding to a scene is now parameterized such that one can choose not to actually persist that group
* This is to support a use case where a module wants a scene which consists of both objects which are persisted, and ones which are just temporary for the lifetime of that server instance
|
| |
|
|
| |
instead, on the basis that this is less likely to cause confusion with c#'s base object type
|
| |
|
|
| |
basis that they all take SOG parameters to improve code readability for now
|
| | |
|
| |
|
|
| |
(this took a while to run).
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Framework.Data.Base
We REALLY need to get the db layer sorted soon...
|
| | |
|
| | |
|
| | |
|
|
|
* This module more or less crashes every region in the instance if you enable it by moving it from local /bin to global /bin
* But hey, it crashes in lots of interesting ways.
|
