Sansar - known issues list

Known Issues

Latest resolved known issues 

  • Several issues that would make Sansar crash.
  • The UI might disappear by pressing the Y button (Oculus) / left menu button (Vive) when in VR in the log-in screen, home Atlas and loading screen.
  • Audio/media streams that are assigned in the scene settings panel in one scene may appear in the audio emitter stream drop down menu in other scenes.
  • Moving the right arm on an avatar from behind the head and up and over to the chest area can cause the arm to twist permanently.
  • The male avatar's right thumbnail texture is not properly lined up with the thumb.
  • Using avatar emotes in an experience causes avatars to stop performing idle animations.
  • The avatar head can only be moved in a limited range.
  • Sansar will occasionally crash if the user goes in and out of the avatar customization app and saves changes to an avatar.
  • MD clothing items created using the male body shape on female avatars causes the clothing item to conform to the male avatar's body shape, instead of the female one. This causes those clothing items to float above the female avatar, instead of naturally laying on the female avatar's body.
  • When importing objects, an object without a collision mesh's Motion Type cannot be set to keyframed or dynamic and can only be set to static. Currently, the import panel doesn't make it clear that the dropdown is disabled without a collision mesh.
  • Sansar crash can be caused by deleting a portion of the cache and then upload an asset that relied on that piece of cache that was deleted. Or, caused by uploading the same asset numerous times before the others uploads have finished.
  • Animated objects lose their animation when uploaded with a collision mesh. (Expected behavior)
  • Sansar crashes if an asset with a really high-resolution texture is added to a scene from the inventory.
  • People App button fails to highlight when users receive friend requests.
  • Various sound effects were missing or incorrect.
  • If a user selects a Sansar avatar look without making edits, the looks thumbnail may generate a black background.
  • Deleting the animation component of a rigged asset will cause Sansar to crash.
  • The input boxes in the Diagnostics toolbar cannot be typed in.
  • Panel settings in Edit Mode are not persistent.
  • Scene objects increase the prim count in the Diagnostics tool.
  • Occasionally, when visiting experiences in VR and switching into 1st person camera mode, the avatar may render incorrectly and obstruct view.  

New known issues in the latest release

  • Avatar movement is not consistent when holding the chat panel in VR mode.
  • The Chat app looses focus when the app launcher is behind it in VR.
  • The input focus of the reticle (pointer) in VR may lose it's input focus when the Atlas scroll bar is grabbed.
  • 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. 
  • Deleting the animation component of a rigged asset causes the asset to disappear when visiting the experience.
  • 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. 
  • At times, the first playback of certain media streams start off at a very low volume. We recommend re-entering the scene to fix the volume to the correct level. 
  • RigidBodyComponent.SetMotionType() callback reports success even when it fails to set static object to dynamic.
  • Toggling in and out of VR while saving or building a scene may cause the client to crash.

 Known issues from previous releases

  •  General
    • The Avatar info tool fails to appear when hovering over an avatar.
    • 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.
    • 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.
    • The screen will flicker violently in desktop mode when wearing the headset while existing the lookbook app. This does not affect what is visible in the HMD lenses.
    • The client stalls and takes a while to transition into the loading screen after clicking "Visit Now" from edit mode.
    • The client crashes when a user is kicked out of Sansar by admins.
    • 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 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.
    • 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 People app button no longer highlights when users receive friend requests. However, friend requests still come in successfully.
  • 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.
  • Avatars & the Lookbook app
    • The pins still stay in place when pressing R to reset in clothing adjustment mode. To remove, press W+Left Mouse button.
    • In VR, the female avatar's left hand twitches against the hip while performing the idle animation.
    • When using the BACK button in the clothing adjustment mode, a Discard/Save modal appears as the changes are finalized.
    • Avatars appear to have slouching shoulders after calibrating height in VR.
    • 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.
    • Avatars fall unnaturally in experiences with low gravity.
    • 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.
    • The 1st person desktop camera may shake when visiting an experience. This is most notable when looking straight down.
    • 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.
    • Some dynamic objects will appear to spring back and forth on screen when held by an avatar.
    • 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.
  • Items & the upload tool
    • Parenting an object to a bone rig will cause failures upon import into Sansar.
    • Assets that have been rigged with groups nested under groups will appear mangled and broken in an experience.
    • 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.
    • Exporting assets with Y up from Z up native programs does not convert to Z up when entering Sansar.
    • 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.
    • A majority of textures assigned to .obj files do not import into Sansar.
    • Some textures appear posterized after uploading them to Sansar.
    • 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.  
  • Edit Mode:
    • Some textures may reflect black patches when it contains colors out of the normal range.
    • Script functions to set RigidBody position, orientation, and velocity on static objects are reported as a success, despite failing to move static objects. As a note, static objects cannot be moved by scripts.
    • 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. 
    • When viewed from a far camera angle, a group of multiple point lights may begin turning on and off, making some lights look dark.
    • 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.
    • 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 multipled times the user input value in the object's top-level scale.
    • When 'surface snap' is enabled in edit mode, grabbing objects while editing in VR becomes difficult.
    • Switching to VR while building a scene makes the 'building' indicator vanish and stay hidden until the build process is completed.
    • Script properties revert back to default values when uploading a script while the properties panel is open.
    • Occasionally, dynamic objects do not collide with other objects and may temporarily fall through them for a few seconds, before snapping back to the other objects' surface.
    • 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.
    • Clearing debug messages from the script debug console will reappear and stack on each other every time the script console is opened.
    • 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.
    • 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.
    • 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.
    • The undo button does not work when adding and removing components in an object.
    • Items obtained from the store are improperly scaled when drag and dropped into a Sansar experience.
    • Objects can be scaled beyond their maximum set limits.
    • 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.
    • Reloading a scene after deleting an object will cause the Scene Objects panel to reorder.
    • Additional containers (and its components) that have been added to objects do not move with the object while visiting an experience.
    • Sansar will crash if an fbx file contains 4+ vertices which are all stacked on each other.
  • Materials editor
    • 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.
  • 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.
  • Visit mode:
    • Some dynamic assets are not culled properly in experiences.
    • When laid flat against a flat object plane, thin object bodies fall through the flat plane.
    • Throwing objects against other avatars may cause them to move back slightly.
    • The avatar info tool remain active on screen even when you are no longer hovering an avatar.
    • 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.
    • 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.
    • At times, some lights do not bounce diffuse colors correctly. Bounced light may not show against the ground or walls.
    • At times, some lights do not bounce diffuse colors correctly. Bounced light may not show against the ground or walls.
    • Selecting a container or component in the scene objects panel may cause the panel's contents to shift.
    • At times, crashes may be experienced when switching between experiences.
    • Black patches may appear over objects in a scene while visiting experience.
  • People app
    • Message and Mute options are available when searching for the currently logged in user in the People app
  • VR mode
    • 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.
    • VR selection reticle intermittently persists on screen after exiting VR mode
    • UI text unexpectedly changes position when moving panels around.
    • In VR, male avatars using VR controllers appear to lean towards the left side when the controllers are active.
Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.