0.9.2.0 Release
From OpenSimulator
(→Known Issues) |
(→Known Issues) |
||
| Line 17: | Line 17: | ||
Region handling of region environment changed to a unified system.<br> | Region handling of region environment changed to a unified system.<br> | ||
Previous had LightShare and WindLight running side by side, each with own data store and communication protocols, occasionally with conflicting results.<br> | Previous had LightShare and WindLight running side by side, each with own data store and communication protocols, occasionally with conflicting results.<br> | ||
| − | New viewers introduce extended environment | + | New viewers introduce extended environment features, so 0.9.2 now uses a internal representation more suitable for those new features. This new representation is automatically converted to and from LightShare or Windlight as needed.<br> |
| − | * LightShare no longer has its own communications protocol. This was already obsolete, so no point on asking viewer developers to keep supporting it. As consequence of this, some viewers may no longer detect region side changes either done by other users or scripts. | + | Region code will inform older viewers about parcels environment but not per altitude environment. |
| + | * LightShare no longer has its own communications protocol. This was already obsolete, so no point on asking viewer developers to keep supporting it. As consequence of this, some viewers may no longer detect region side changes either done by other users or scripts. This include changes on entering or leaving a parcel with own environment. (Firestorm or Dayturn will see changes, singularity will not, for example) | ||
| + | How the region environment will look on screen is still very dependent on the particular viewer, and keeps changing for the same set of parameters, But a major difference, that environment designers need to consider, is between viewers with the new features and previous versions versions with just Windlight.<br> | ||
| + | Perfect conversion is of course not possible, and may give bad results. | ||
| + | * New region environments should be created with the extended features editor, but still tested with a older viewer, that users will keep using for sometime. | ||
= Requirements = | = Requirements = | ||
Revision as of 01:54, 16 October 2020
CURRENTLY UNDER DEVELOPMENT
See last code changes at Dev (git master)
- A binary package automatically built from latest development code can be downloaded at OpenSim-LastAutoBuild.zip
- To build it yourself see Build_Instructions
Note: Due to the development work, this may be in bad state. Use with care
Contents |
General
Also see 0.9.1.1 Release Notes
Known Issues
Region handling of region environment changed to a unified system.
Previous had LightShare and WindLight running side by side, each with own data store and communication protocols, occasionally with conflicting results.
New viewers introduce extended environment features, so 0.9.2 now uses a internal representation more suitable for those new features. This new representation is automatically converted to and from LightShare or Windlight as needed.
Region code will inform older viewers about parcels environment but not per altitude environment.
- LightShare no longer has its own communications protocol. This was already obsolete, so no point on asking viewer developers to keep supporting it. As consequence of this, some viewers may no longer detect region side changes either done by other users or scripts. This include changes on entering or leaving a parcel with own environment. (Firestorm or Dayturn will see changes, singularity will not, for example)
How the region environment will look on screen is still very dependent on the particular viewer, and keeps changing for the same set of parameters, But a major difference, that environment designers need to consider, is between viewers with the new features and previous versions versions with just Windlight.
Perfect conversion is of course not possible, and may give bad results.
- New region environments should be created with the extended features editor, but still tested with a older viewer, that users will keep using for sometime.
Requirements
OpenSimulator 0.9.2.0 requires:
- At least .NET Framework 4.6 when running under Windows.
- At least Mono 5.x when running under Mono (Linux or Mac).
Due to database migration renumbering which occurred at release 0.9.0.0, if you are upgrading from a version of OpenSimulator prior to 0.8.2.1, then you MUST first upgrade to *0.8.2.1* and then proceed to upgrade directly to 0.9.2.0. See 0.9.0.0_Release#Pivot_Release:_0.8.2.1 for more advice.
Changes and Fixes
- Added a real transparent texture for default transparency and avatar alphas transparency. Asset 3a367d1c-bef1-6d43-7595-e88c1e3aadb3 must be removed by hand from any retained current regions cache (at bin/assetcache/3a3) and viewers cache clean. Then make sure you do one viewer login to an updated grid/region.
- Altered mechanism for reading OSSL section of OpenSim.ini to use config-include/osslDefaultEnable.ini which then loads config-include/osslEnable.ini overrides. Also note the section name is now [OSSL]. Please change your OpenSim.ini and config-include/osslEnable.ini accordingly using the examples in OpenSim.ini.example and configo-nclude/osslEnable.ini.example.
- Added some OSSL functions osGetSitActiveRange, osGetLinkSitActiveRange, osGetStandTarget, osGetLinkStandTarget, osSetSitActiveRange, osSetLinkSitActiveRange, osSetStandTarget, osSetLinkStandTarget, ….
- Removed outdated support for SimianGrid. Simian was a web/php alternative to Robust (https://code.google.com/archive/p/openmetaverse).
- Region environment handling changed to support new viewer features.
Acknowledgements
Many, many thanks to all the developers, testers and community members who contributed to this release and who help out with OpenSimulator generally. Your hard work makes this all possible.
