Open Beta

Most avatars and prefabs that currently have VRCFT support were made with one of the popular driver prefabs in mind, (eg. Jerry's, Pawlygon, etc.). It will require an extreme amount of manual work to convert existing avatars to the new native FT system as it is. Many existing avatars rely on the Blended Shapes that are part of the Unified Expressions Standard ( https://docs.vrcft.io/docs/tutorial-avatars/tutorial-avatars-extras/unified-blendshapes#ue-blended-shapes ), instead of having every upper/lower/left/right etc. shape. Also many prefabs, such as those that animate ears/tail/etc. to the FT data rely on Simplified Tracking Parameters ( https://docs.vrcft.io/docs/tutorial-avatars/tutorial-avatars-extras/parameters#more-simplified-tracking-parameters ) such as the incredibly common SmileFrownLeft/Right and EyeLidLeft/Right. As it is currently, configuring the native FT system to support these existing avatars and prefabs requires cloning the VRCFT software and searching through the source code to find and assemble the relevant formulas to enter into the custom expression field, many of which you would have to enter twice if you also want it forwarded to an animator parameter at the same time. Please include support for the Blended Shapes and Simplified Parameters that are part of the Unified Expression standard, and save creators hundreds of hours of work, was well as the repetitive task of copying and maintaining the resulting complex configs across avatars.

The current Parameter Behavior system is fairly powerful, however it would save me a lot of code duplication and make it easier to maintain a large number of expressions If I could re-use the result of already evaluated expressions. For instance, if I have an expression like: MouthCornerPullRight * 0.8 + MouthCornerSlantRight * 0.2 that runs a blendhshape or parameter MouthSmileRight , then I could re-use that calculation in another expression like this: MouthSmileRight - MouthFrownRight and output that to a parameter or shape SmileFrownRight . Ideally either the animator parameter name or blendshape name could be used as the token to reference its value in subsequent expressions.

Currently all the face tracking configuration must be done on the avatar descriptor. This will be very difficult to maintain long-term. It also doesn't make that much sense, given that it's using the Unified Expressions standard, which will be more or less the same across every avatar, and has historically in the case of generic driver prefabs such as Jerry's and Pawlygon's. This also makes it incredibly difficult to maintain variants where the FT is sold separately and/or by an entirely different creator. Applying a product that is a face tracking add-on to an existing customized avatar is difficult to impossible with the ft config being part of the avatar descriptor. This is exacerbated by the current lack of support for Simplified Parameters ( https://docs.vrcft.io/docs/tutorial-avatars/tutorial-avatars-extras/parameters#more-simplified-tracking-parameters ) and Blended Shapes ( https://docs.vrcft.io/docs/tutorial-avatars/tutorial-avatars-extras/unified-blendshapes#ue-blended-shapes ) which will need many custom expressions configured to support existing avatars. Please split the FT configuration out to a separate component that is allowed to be on a child object of the avatar, that way it can be prefabbed. The only reference to an external object is the mesh, which can be assigned and saved as a string path like audio sources are in VRCPlayAudio.

When getting the new Terms of Service and Privacy Policy prompts in the new login UI, the new panels have now changed significantly from their old login flow versions, however they have several problems: The link text doesn't have an underline or other more obvious indicator (such as an icon) that it is a hyperlink, which might make it hard for some colour blind users. The link text is part of the label for the agreement checkbox, under standard UI rules in most platforms, clicking the text of a checkbox should just check and uncheck the text box, not perform a secondary action by also being a hyperlink. This hyperlink should be a seperate UI element with a clearer display text such as: 'View the <document> in your web browser'. There was no notification or even UI noise as far as I could tell when clicking the hyperlink to indicate that Vrchat had opened my web browser on my desktop meaing I clicked it several times and opened several tabs. The standard VRChat notification UI or similar should be used if the user to tell them a new tab has opened in their default browser for them to go read the documents. Given there was an update to both the ToS and PP at the same time, the dialog should let users know there are multiple documents to review and accept from the start. For someone being conscientious and taking time to take off their headset, review the changes before putting their headset back on and clicking accept, only to then have a second document to do that again! If there had also been an update to the Code of Conduct as well that would be really annoying! If multiple documents have updated, expand the size of the dialog as needed to display a link for each one and a checkbox for each one given all need to be accepted to continue into VRChat. Finally, a general comment on the policy document pages, a 'Diff' like view should be provided if someone accesses them from VRChat or the VRChat web panel like this, showing the changes between the last version they accepted and the current version (maybe with 'human-friendly' explainers as well). This way someone can easily review what parts have changed and not need to re-read the entire document and play 'spot the difference' on them. Various community members took it upon themselves to create diff-like views and this is something VRChat should do themselves as it would help give a better impression of honesty and transparency about what is changing and why.

The new profile themes allow users to choose arbitrary colors for text, buttons, icons, and backgrounds. Some combinations can make functional UI difficult or impossible to read, for example, white text on a bright yellow button. This is primarily a readability and visual-comfort issue. Poor contrast can affect users with low vision, color-vision deficiencies, migraines, light sensitivity, or other visual-processing difficulties. It can also be especially uncomfortable in VR headsets. Please add an accessibility option that lets viewers override custom profile themes with VRChat's default colors. Ideally, this would include a global toggle to show/hide custom profile themes, automatic use of default colors when a high-contrast accessibility mode is enabled, or contrast validation in the theme editor to prevent unreadable combinations. Profile customization is a nice form of self-expression, but the viewer's accessibility and readability preferences should take priority over another user's theme.

The new native SDK FT system only supports the Unified Expression tracking standard. Avatars built with other standards are stuck manually setting 120+ dropdowns in the avatar descriptor. Please allow the Auto-Fill Blendshapes button to automatically re-map the other tracking standards to Unified based on this spreadsheet created by ADJerry91 https://docs.google.com/spreadsheets/d/118jo960co3Mgw8eREFVBsaJ7z0GtKNr52IB4Bz99VTA/edit Obviously the results will not be perfect, but it would be a massive QOL improvment over having to do it manually.

Face a different direction to the forward direction of your playspace Join a different world Observe how the loading world isn't aligned to the direction you face when you enter

Please consider allowing creators to dampen both, visemes and face tracking, with different amounts, instead of just one or the other.

Menu setting toggles visually different from last version of the game. The toggle buttons in the settings menus are darker.

[fixed] Traced it to a hardware conflict with the hybrid GPU,.