Also coming is more of the HTTP Protocol update. There is more work being done on the HTTP library, viewer changes, and more to be done server side. All of these new features will mean new problems for the FS Team and other Third Party Viewer (TPV) Dev’s.
Jessica’s point is ALL the TPV Dev’s and LL will see lots of problems over the next 3 to 6 months. The basic state of things will be: Fubar.
The benefits in the long run will be Avatars rezzing faster, from SSAB. The improved HTTP protocol will reduce tp failures and make for faster texture and mesh rez.The plan is all the changes will be improvements and hopefully worth the coming months of problems. So, it is going to be a shaky start, but hopefully have a good ending in midyear.
So, you have been updated and warned.
There are cool features coming to the next release of FS. One new feature is from an effort to avoid having to clear viewer settings with each new install of the FS viewer. It is a drag changing all the setting back to your personal preferences. So, the Team has added a settings export and import. Jessica hopes this is the end of the settings corruption on new version install. This feature may not be ready for the next release, but certainly for the one after.
The Team is working on an import/export of prims feature. The FS Team hopes this import/export format becomes the OpenSim/SL standard. It will work in OpenSim.
There is also a new version of the Quick Preferences panel coming. The Team tried to get the prefs most people wanted in the panel in past versions. But, that didn’t work for everyone. So, the new Quick Prefs will let you add and remove preferences of your choice. My understanding is that if it is a Debug Setting you can add it as a Quick Preference, which will make for some interesting support problems. However, your Quick Preferences will save in the viewer settings export.
There is not as much new stuff as Jessica would like in the likely next release. That is because of the work load from LL changes. There priority effort is directed at getting the Lab’s changes working well in FS. So, new features that offer any problem will likely be dropped to get a SSAB cable version out.
Jessica wanted to be clear that not all the bugs they are running into are the Lab’s bugs or fault. Some are made by the FS Team.
Chiclets – you are going to be able hide most of them in one of the next versions of FS. The original idea was to turn off all the chiclets and have the notices appear in the V1 style. Chiclets for inventory offers and group stuff will remain as it seems there is no easy way to revert them back to a V1 style. The changes to turn off chiclets are proving to be technically challenging. The FS Team is working on it.
V1 search – The Team has built in a V! Search feature. However, when the Lab turns off the servers that provide the service, V1 search is gone. But, V1 Search will remain in operation on OpenSim grids.
I missed part of this, but there is something about more floaters being added for for block-mute, groups, more… which are little UI changes but big changes for usability.
Jessica’s belief is that while the Lab is flexible on the SSAB rollout date,the Lab is pushing developers to get SSAB support out. Jessica believes they can push the Lab a bit to allow the Team to get things working well. But, there will be a point where the Lab says enough is an enough and sets a hard roll date.
The Lab has been offering lots of help to TPV Dev’s. Nyx and Oz have both been there for the Dev’s. But, there are things the Lab cannot help with, things like RLV and features unique to FS or other TPV’s.
Stable or not stable SSAB in FS will come out at some point. The push is to get things working well. But, perfection is NOT the goal.
An interesting aspect of SSAB will be breaking copyboting, at least for a time.
Singularity has a SSAB viewer, but rumor is that version of the viewer is broken. So, as far as I know there is no working SSAB enabled viewer. The Lab has an internal project viewer for SSAB and some people have links to it. But, it is not ready for massive testing, so those are mostly being kept private.
A question came up on the problem of having both of the two versions of FS (SL and OS) installed at the same time. By default the OpenSim and SL versions install to the same directory and the last installed wins. The fix is to install one, change the desktop icon name, change the Start Menu item’s name, THEN install the ‘other’ version into a folder other than the default. Then yu ave both copies and use them in SL and OpenSim.
If you don’t need to use the Navmesh editor for Pathfinding just install the OpenSim version. Much easier.
A question came up about whether two versions of the viewer will be needed for OpenSim and SL because of the SSAB code. The answer is no. This can sound confusing, so follow closely. We currently have the Viewer Side Avatar Bake (VSAB) in the viewers, all makes. That is going to stay in some form. The SSAB is being added. So, both processes will be available in the viewer. Depending on what the region server tells the viewer, either VSAB or SSAB will used.
Over time some part of the VSAB system may be removed from the SL viewer. BUT… the VSAB code is used when you change appearance. It provides you a quick update of your avatar’s appearance without having to wait for the SSAB servers to respond. It also saves the SSAB service having to bake every little change you make. Sometime after you stop changing appearance, a signal is sent to the SSAB servers and they update based on the content of your Current Outfit Folder (COF).
So, mot of the VSAB code is going to stay. In viewers that are to be used on other grids, the older VSAB code will be used. So, for TPV’s most of the code will remain. They will just add the SSAB code. So, there will be no need for special versions of the viewer for OpenSim and SL because of SSAB.
There is a media streaming problem in FS– Someone in the team said it is fixed and will be in next release.