Sansar - known issues list

Various bug fixes on the chat and people app, including but not limited to:

Text could not be copied from the chat app.

The People app button no longer highlights when users receive friend requests. However, friend requests still come in successfully.

The Chat app appears on screen slightly off screen in certain screen resolutions, hiding the text input field. You must manually move the chat app in the screen to reveal the text input field.

When a message with only non-latin characters is sent in chat, it does not show in the Chat app history. Non-latin characters can only be sent if regular characters are submitted with it in the same message.

At times, Avatar IDs display incorrectly and shows a long string of text and numbers. When this happens, try closing and re-opening the People app to see the correct Avatar ID.

The script color parameters appear cropped at the default Properties panel width. The "Red" field label is missing and the input field touches the TestColor label.

Ignored friends requests reappear as pending when the client is relaunched.

Duplicating a 3D model while dragging it to the scene will duplicate the item while it is still in it's cube form. This cube form will remain visible as a cube within the scene editor and while visiting an experience.

At times, male avatar clothing and accessories fail to show up in the client after purchasing or redelivering the items from the store. In order to see the items correctly in the lookbook, try closing and relaunching Sansar.

New known issues in the latest release

Events in progress cannot be edited.

The typing indicator will not go away if the chat panel was closed while it is active.

Known issues from previous releases

Issues related to using Sansar in VR:

The screen will flicker violently in desktop mode when wearing the headset while exiting the lookbook app. This does not affect what is visible in the HMD lenses.

Toggling from the first person to the third person in VR mode may cause the avatar to shift to the left or right of its original position.

Issues that may be observed while using various apps:

Issues that may be observed while exploring the Atlas app:

Users may get disconnected from Sansar which may cause the Atlas to appear blank or lose the remember me info.

Leaving an Experience that was entered from a search action returns the user to a blank page.

Favoriting/unfavoriting an experience from the web Atlas will break the favoriting/unfavoriting button in the client. As a workaround, we suggest closing the Atlas panel in the client and reload the data.

The right arrow on the experience details page in the Atlas only scrolls to the last loaded experience on the Atlas and fails to scroll through all experiences on the Atlas.

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

The input focus of the reticle (pointer) in VR may lose it's input focus when the Atlas scroll bar is grabbed.

Issues related to the chat app:

Adjusting the scale in Edit Mode in VR does not affect the chat app. Thus, the chat app does not scale along with the user, making it hard to use in a small or large scale.

The Chat app looses focus when the app launcher is behind it in VR.

Issues related to the people app:

Scaling the friends list can cause friends to become selected.

Issues related to exploring a user's profile:

Any changes to the user profile may not be visible to other users. The profile will only be visible if other people relaunch their Sansar client.

When viewing a user's profile from the Atlas, selecting an experience from the profile does not open the experience details modal.

Issues related to the Events app:

An event listing will disappear from the Events app if the experience associated with it is deleted. In addition, this does not pull the data entirely and the time slot of the missing event will still be "taken", preventing the creation of a new event under the time slot. To fix this issue, you may request for assistance from the support team.

The Events app does not refresh data when you switch between tabs. To refresh data, you will have to exit the events app and open it again.

Issues related to the Lookbook app:

The client crashes when entering "Adjust clothing" mode and selecting "Done" at the same time.

Uploaded character asset thumbnails with transparency appear with white backgrounds.

The pins still stay in place when pressing R to reset in clothing adjustment mode. To remove, press W+Left Mouse button.

When using the BACK button in the clothing adjustment mode, a Discard/Save modal appears as the changes are finalized.

Issues that may be observed on avatar clothing and accessories:

Male astronaut outfit has hidden surface removal happening on visible parts of the leg when walking.

Roughness and normals appear off when importing an Marvelous Designer items created in Marvelous Designer 7.5

Issues related to the My experiences app:

The My Experiences app does not automatically refresh to show the updated image of an experience. To see the changes, close and re-open the My Experiences app.

Issues that may be observed while editing a scene:

Issues related to scripts:

No script collision event is generated when an agent inside a trigger volume exits the experience.

Scripts do not receive command events for Modifier combos if the modifier is pressed first.

Issues related to interfacing with the scene editor:

Sansar will crash when leaving edit mode if a script was dragged out and back into the inventory panel.

The client stalls and takes a while to transition into the loading screen after clicking "Visit Now" from edit mode.

The Diagnostic modes should only trigger while visting or editing a scene. At times, when it is enabled, the effects may spill into the Atlas or lookbook. This may have some weird visual effect or may prevent some buttons from working.

The SHIFT key may be rendered stuck when used in combination with the A or D keys. While visiting an experience, this means the teleport beam may remain active while shift is not held down. In edit mode, this means that scene objects will be multi-selected in the scene.

Issues related to the inventory and scene objects:

Multi-object 3D models uploaded with a collision shape do not move when the motion type is set to "Dynamic".

Clicking on a scene object component will cause the object to be selected in the scene and highlighted in the scene objects panel. However, clicking on a selected component for a second time will cause the scene object panel highlight to turn off even though the object remains in it's selected state.

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

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

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

Selecting a container or component in the scene objects panel may cause the panel's contents to shift.

Issues related to object manipulation and editing:

Spam deleting scene assets may cause Sansar to crash.

The highest volume level of an audio emitter triggers when the user is a few feet away from the emitter, instead of at the point where the user crosses the audio emitter shape.

Moving an audio emitter while in VR mode does not move the previewed audio with it.

Spam deleting scene assets may cause Sansar to crash.

Moving an audio emitter while in VR mode does not move the previewed audio with it.

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

When 'surface snap' is enabled in edit mode, grabbing objects while editing in VR becomes difficult.

Shift + click to select multiple objects does not work when the properties panel is open. Make sure that the properties panel is closed when selecting multiple objects.

Some textures may reflect black patches when it contains colors out of the normal range.

The user input value on a Volume RBOD component's scale in the scene objects heirarchy changes in relation to the user input value assigned on the object's top-level scale. The Volume RBOD component's scale becomes auto-computed and multiplied times the user input value in the object's top-level scale.

Additional containers (and its components) that have been added to objects do not move with the object when built into a scene. This is testable when you visit the experience.

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

Objects can be scaled beyond their maximum set limits.

Issues related to multi-part objects objects:

Assets that have been rigged with groups nested under groups will appear mangled and broken in an experience.

Multi-part objects can be uploaded with collision meshes. However, when a multi-part object is uploaded with a collision mesh, only the first object of the multiple parts will be visible while the collision volumes of all the parts will still be in effect.

Issues related to animated objects:

Animated asset do not snap properly to surfaces when first added in a scene.

When editing an animated object, the Scale property only affects the object's size and not the distance the object travels during its animation. This means that scaling an animated object can often lead to unexpected and undesirable results, so make sure to model to the appropriate scale in your 3D modeling tool.

Deleting the animation component of a rigged asset causes the asset to disappear when visiting the experience.

If an animated object's static mesh component is moved from its original container in the scene objects panel, the object's animation will no longer play.

Issues related to materials and textures:

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

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

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

Issues related to media and audio streams:

Adjusting a media surfaces Height and Width values while audio/video preview is off can result in the media surface displaying the media at the original/last previewed values.

Audio from media streams may start warbling and may be exacerbated by actions like rotating the camera, minimizing/maximizing the camera window, or task switching with other apps in the desktop.

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.

Issues that are related to working with scripts:

RigidBodyComponent.SetMotionType() callback reports success even when it fails to set static object to dynamic.

RigidBody.SetOrientation(Sansar.Vector) should be a deprecated method. However, scripts with the function can still be uploaded in Sansar and errors out. Moving forward, it is best to use the RigidBody.SetOrientation(Sansar.Quaternion) method instead.

Clearing debug messages from the script debug console will reappear and stack on each other every time the script console is opened.

Issues related to lighting:

Only one of the lights animates when importing a group of animated lights from Blender into Sansar.

When viewed from a far camera angle, a group of multiple point lights may begin turning on and off, making some lights look dark.

The shadow of a dynamic object placed under a spot light may remain in place and still cast a shadow, even when the object is picked up.

When undo (ctrl+undo) is used to remove directional lights in a scene, it causes an error and prevents a user from adding another directional light into the scene.

Issues related to using VR while editing a scene:

Switching to VR while building a scene makes the 'building' indicator vanish and stay hidden until the build process is completed.

In desktop mode, trigger volumes show the gizmo and the mini-object toolbar, which acts as a visual indication that it is selected. However, in VR mode, the gizmo and the mini-object toolbar are missing, thereby showing no visual indicator that it is selected.

Issues that may be observed when uploading scene items:

Issues related to the PC and file explorer:

If temporary files for Sansar are partially deleted, all future imports through the asset importer fails. However, if all contents in the temporary folder are deleted, it doesn't affect future imports of the files.

Some objects may fail to upload indefinitely when the import cache is lost or corrupted unless the user deletes the whole import cache.

PC network drives fail to appear on the file explorer when uploading a file using the upload tool.

Issues related to importing objects:

.fbx files that only contain an asset identified with the _collision name, are imported in as a static mesh, instead of a volume component.

Poly reduction executed upon upload may cause dark tangent/binormals to appear on high poly meshes.

Poly reduction executed upon upload may cause holes to appear on high poly collision meshes.

Poly reduction executed upon upload may cause uneven reduction on some high poly meshes.

Parenting an object to a bone rig will cause failures upon import into Sansar.

Exporting assets with Y up from Z up native programs does not convert to Z up when entering Sansar.

A majority of textures assigned to .obj files do not import into Sansar.

Some textures appear posterized after uploading them to Sansar.

Issues that may be observed while visiting an experience:

Issues related to exploration and instancing:

The held state and positioning of an object does not update immediately from one user's viewpoint after a user grabs the object from another user.

The teleport beam reads the flat surface of a ceiling and allows the user to teleport through the ceiling and onto the roof.

Teleport selection beams are blocked by an object collision's collision mesh if a user winds up within that mesh. To leave, try teleporting straight up to the top of the object.

Underhand throwing an object can cause it to rotate and jump oddly through the air.

Dynamic objects may appear in different locations to users viewing the same objects.

The client shows a scene with a flat background or lighting while loading a scene in VR mode.

Dynamic assets can be picked up through static objects.

Some colors appear to smear while looking around in a VR headset.

You must keep the grip button held in order for the VR reticle to interact with Modal dialogs that are presented from Object Interactivity Panels.

At times, crashes may be experienced when switching between experiences.

Intermittently, users may be kicked back to the Atlas when they are trying to connect to a new instance.

The 1st person desktop camera may shake when visiting an experience. This is most notable when looking straight down.

Fast moving animated platforms can cause avatars to pop back and forth while idling.

Issues related to avatar movement:

Avatar arms may twitch in VR when held at certain angles.

Avatar IK movement pops when switching between first and third person VR

Avatar torso and arms twitch while in VR mode.

Avatars may appear in the wrong location to another user due to out of sync object animations.

Muting and unmuting the microphone while talking may cause the avatar's head to snap.

In VR, male avatars using VR controllers appear to lean towards the left side when the controllers are active.

Avatar movement is not consistent when holding the chat panel in VR mode.

In VR, the female avatar's left hand twitches against the hip while performing the idle animation.

Avatars do not run at full speed when using the simple controls. This applies to the Oculus touch controllers and the standard gamepad.

Avatars have IK issues in the elbows and arms while rotating the Touch controllers or Vive wands.

In VR, avatar wrists twist around like "candy wrapping" when turning the hands inward and outward using the touch controls.

The avatar head may appear broken when the avatar is looking around in VR mode.

The avatar continues to move forward for a few steps even after the controls for running has been let go.

Avatar heads' rotation and tilt no longer have any limitations set.

Male avatars' right hand shakes when the right VR controller is rotated at certain angles.

In VR, shoulders will clip through MD clothing as the avatar walks and moves their arms around.

Occasionally, some avatars get caught on some objects as the objects are pushed away from them.

Switching your avatar between genders may cause the avatar's mouth to not move in accordance with the vocal sounds you create.

At times, objects grabbed in VR appear offset and do not track the user's hands.

Occasionally, some dynamic objects may jump away beyond the expected force from the avatar when colliding with them.

It's possible to get your avatar's arms to clip into its torso.

The female avatar's nose will tear up when the nose slider is set to the maximum value.

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.

Issues related to avatar interaction:

The Avatar info tool fails to appear when hovering over an avatar.

The avatar info tool remain active on screen even when you are no longer hovering an avatar.

Throwing objects against other avatars may cause them to move back slightly.

Issues related to interaction:

When laid flat against a flat object plane, thin object bodies fall through the flat plane.

Dynamic objects appears offset from the hand you picked them up with. Additionally, tossing and catching dynamic objects may exacerbate the issue and make the objects float a few inches away from the avatar hands.

Teleporting using a teleport script into an enclosed space from an unenclosed space causes collision culling of the room and it's contents.

Avatars fall unnaturally in experiences with low gravity.

Issues related to rendering the scene:

Some dynamic assets are not culled properly in experiences.

Black patches may appear over objects in a scene while visiting experience.

Issues related to sound:

Audio events triggered by trigger volumes start playing every time the avatar enters or exits the volume, even though the audio file is already playing. This results in multiple overlapping audio playbacks.

Issues related to lighting:

At times, some lights do not bounce diffuse colors correctly. Bounced light may not show against the ground or walls.