Sansar Release Notes for July 31, 2017

Creator Beta: Today, we’re happy to announce that we’re opening Creator Beta to the public! Come join us in Sansar and invite your friends to visit your experiences! With this release, the Sansar client and website is now available to a wider audience!

Experiences that have compute scene reverb enabled may cause the client to crash.

At times, audio in experiences with Compute Scene Reverb cuts out when in free cam or first person mode.

Mouse camera trucking does not work if left click happens over an asset.

Duplicating a group of assets only shows one selection in the Scene Objects panel.

The first user selected material on an uploaded asset will not visually highlight after the user has selected it.

The object floating panel doesn't appear when an object is first selected or placed in the scene. Temporary fix: If you move the asset to the edge of the window, the object floating panel appears as expected.

Using Undo on an avatar with accessories after switching avatar gender does not re-apply the accessories that were previously on the avatar.

The UI elements for applied accessories are not highlighted in the Accessories sub-menu after cloning a look with accessories.

Using Undo on an attachment does not deselect the item in the Accessories sub-menu.

Right clicking a UI element in the Character Editor causes the avatar to rotate when moving the mouse around.

The "Publish to Atlas" button is still available even when a user is editing a scene (with no experience attached to it) in the scene editor. If this button is clicked, an error message will occur since there is no experience to publish.

The active shader for the second material selected in the material editor, will be applied to the first selected material.

Reversed UVs cause a normal maps normals to appear backwards, making what should appear pointing out, to be sunken in.

There are two "Show Rotation" buttons.

Known issues for this release

Sansar may crash when triggering certain features or apps.

The Sansar Client will crash if lots of high poly collision shapes collide with each other and become pinned.

The hand and the teleport beam show in desktop mode when leaving VR.

The more options button has to be clicked twice to open it.

At times, users' online statuses are not reflected properly in the People app.

Sansar will crash if an fbx asset contains 4+ vertices which are all stacked on each other.

If a value is typed into an input field and before pressing enter, a new asset is selected from the Scene Objects panel, the input value string will be applied to the newly selected asset.

Known issues from previous releases

General issues:

Attempting to open the Atlas after exiting VR mode in edit mode can cause Sansar to crash.

The more options button has to be clicked twice to open it.

Some user online status are not updating as expected.

Audio-related issues:

Audio Shapes: if you have a point source inside a static object, it will sound occluded by the object. We plan to fix this soon, but as a workaround you can change your sound into a Sphere or Box that extends beyond the object.

Avatar-related issues:

Avatars may take a quick step if a controller is used to navigate the avatar slowly through the experience.

Male avatars forward left strafe is not smooth while in first person camera mode. The avatar will appear to wobble left and right as they walk.

The new Arm IK feature is still being polished. Some bugs may trigger on the Avatar’s arms when it is enabled. For example, it's possible to get your avatar's arms to clip into its torso.

The same file can be uploaded to multiple categories in the Accessories sub-menu. This may lead to some odd results while customizing your Avatar.

Known issues within the Scene Editor:

Some textures appear posterized after uploading them to Sansar.

The undo button does not work when adding and removing components in an object.

Assets obtained from the store are improperly scaled when drag and dropped into a Sansar experience.

If a ribbon panel drop down is active, and the scene objects panel is used, the drop down panel will appear behind the scene objects panel.

If you make changes to your scene and save them, then enter VR and load the scene in the editor. If you try to visit the scene without building it first, it will take you to a building modal that has a cancel button that doesn’t function.

Objects can be scaled beyond their maximum set limits.

The Chat window in Edit mode is truncated in the default window view.

Some store assets that rely on the emissive.exr texture to be used as their diffuse color are being tinted by the empty diffuse attribute, making the asset appear dark and dull.

The sound effect for manipulating the gizmo handles have a noticeable lag. This may make it seem like the gizmo is slow in response to your mouse clicks.

Reloading a scene after deleting an object will cause the Scene Objects panel to reorder.

Setting Sky Distance with the slider is difficult for lower values.

Additional containers (and its components) that have been added to objects do not move with the object while visiting an experience.

Changes made to a component's properties in an object may transfer to a similar object with a similar component.

At times, users' online statuses are not reflected properly in the People app.

The Materials Editor still exhibits a few issues such as:

Non uniform repeating textures do not repeat with the designated values (Ex:2x5) and when used will only repeat to the lowest value (Ex: 2x5 = results in a 2x2 repeat).

Sansar crashes if an asset with a really high resolution texture is added to a scene from the inventory.

If the material editor is opened and saved followed by a custom name entered for the 'Item name in Inventory' field, the name will revert back to the default asset name.

The material editor will appear to open then close if an unsupported asset type is set as an .fbx file extension and loaded into the asset converter.

When an asset with more than 1 UV map is uploaded, only the first UV map will appear textured. All other UV maps will appear black.

Known issues related to Media Surfaces:

Media Surfaces continue to play for a few seconds after entering Edit Mode.

If a media surface source is set to a gif image, that image will become squashed into one of the corners of the surface. If tiling is used, the empty space will also tile along with the image.

Media surfaces do not appear to respect the UV placement of assets when a media surface is applied to that asset.

Known issues while visiting an experience:

Some dynamic assets do not appear to initialize their physics until they are moved in the experience. This is causing some physic based assets to appear to float in the air until an avatar bumps into them.