Feature Requests

First of all, avatars have a feature called “Hide Avatar Globally.” For example, if you come across a giant cockroach or an offensive public avatar, using this feature doesn’t just hide “that person’s avatar”; instead, it hides “that specific avatar” regardless of who is using it. I’d like to see this feature implemented for items as well. In other words, instead of a feature that simply “hides this item right here and now,” I’d like a feature that “replaces this item with something else whenever anyone spawns it.” When I saw the Bee Blaster distributed as an April bonus, I almost asked, “Is April Fools’ Day still going on?” A Canny has already been posted, but it’s that controversial—it’s already been banned at some VRChat events, and people are saying things like, “I’ll block anyone who points this at me.” Canny: https://feedback.vrchat.com/vrchat-plus-feature-ideas/p/cancellation-of-bee-blaster-item-release Currently, it’s possible to restrict item usage on a per-instance or per-world basis, but it’s a shame that other items can’t be used just because of a single “item that’s like a joke that isn’t funny.” Furthermore, if user-created content is introduced in the future, this feature will become even more important. = JP = まず初めに、アバターには"Hide Avatar Globally"という機能があります。 これは例えば巨大なコックローチだとか、不快なPublicアバターを見つけた時に使うことで、"その人のアバター"を非表示にするのではなく、誰が使っている場合でも、"そのアバターを非表示にする"といった挙動が出来ます。 この機能をItemにも実装してほしいです。 つまり「今この場でこのアイテムを非表示にする」という機能ではなく、「このアイテムは誰が出現させても別の何かに置き換える」と言った機能です。 4月の特典として配布されたBee Blasterを見た時、「エイプリルフールはまだ続いてるの？」と言いたくなりました。 既にCannyが出ていますが、それくらいの物議を醸す代物で、既に一部のVRChatイベントで使用禁止が通達されていたり、「これを向けてくる人間がいたらブロックする」と言ったことを言う人も出てきます。 Canny: https://feedback.vrchat.com/vrchat-plus-feature-ideas/p/cancellation-of-bee-blaster-item-release 現状だとインスタンスやワールド単位でアイテム使用を制限することは出来ますが、たった一つの"笑えない冗談みたいなアイテム"のために他のアイテムが使えなくなるのは無粋ですし、今後ユーザーが作成可能なコンテンツにしていく場合、この機能はさらに重要になることでしょう。

Current problems Almost all avatars have a performance rank of "Very Poor," making it virtually impossible to block avatars based on their performance rank. This means that blocking based on polygon count or texture size, which directly impact performance, is currently impossible. While other blocking methods exist, such as blocking by download size or uncompressed size, these are insufficient alternatives as they are also affected by texture compression settings and the size of other assets. As a side note, because the performance ranking system is effectively non-functional and has no limitations, the polygon count of avatars and costumes sold on BOOTH seems to be increasing year after year without limit. Recently, commonly used avatars have approximately 150,000 tris, and costumes have approximately 200,000 tris. Request details I think the triangle count in the performance ranking system needs to be updated. Currently, all grades below "Good" have a uniform polygon count of 70,000. This limitation is a bit excessive for current hardware. https://creators.vrchat.com/avatars/avatar-performance-ranking-system/ Remarks I have conducted some (very simple) testing in the past. I believe that optimizing to under 300,000 tris is sufficient for instances like talking with a small number of friends, and under 70,000 tris for large instances like events. The testing was done with a single avatar, but I created a tool to ensure that each mesh is a separate asset for the testing. https://misskey.niri.la/notes/aggjg6jmjz I'll leave the final updated figures to the VRChat staff, but I have roughly the following figures in mind. Poor: 300,000 tris Medium: 150,000 tris Good: 70,000 tris Related posts https://feedback.vrchat.com/feature-requests/p/option-to-not-take-polygons-into-account-when-enabling-minimum-displayed-perform https://feedback.vrchat.com/feature-requests/p/client-side-polygon-limit-slider https://feedback.vrchat.com/feature-requests/p/avatar-polygon-limit-in-safety-settings https://feedback.vrchat.com/feature-requests/p/increase-the-polygon-limit-by-30k-for-medium-ranked-avatars-on-pc https://feedback.vrchat.com/avatar-30/p/incremental-triangle-limit-for-performance-rankings https://feedback.vrchat.com/feature-requests/p/add-performance-rank-that-exceeded-polygon-limit https://feedback.vrchat.com/feature-requests/p/performance-ranks-below-very-poor 日本語 / Japanese 現在の問題 ほとんど全てのアバターのパフォーマンスランクがVery Poorであるため、パフォーマンスランクを使用したアバターのブロックが事実上できない状態になっています。つまり現在は負荷に直結するポリゴン数やテクスチャサイズでのブロックが不可能です。他のブロック手段としてダウンロードサイズ、非圧縮サイズによるブロックも存在しますが、テクスチャの圧縮設定やテクスチャ以外のアセットサイズによっても変動するため代替とするには不十分です。 余談ですが、パフォーマンスランキングシステムが事実上機能しておらず制限も存在しないため、BOOTHで販売されているアバターや衣装のポリゴン数が年々際限なく増え続けているようです。最近よく使われているアバターのポリゴン数はおよそ15万ポリゴン、衣装はおよそ20万ポリゴンになっています。 リクエスト内容 パフォーマンスランキングシステムのトライアングル数をアップデートする必要があると思います。現在ではGood以下は一律7万ポリゴンです。この制限は現在のハードウェアにとっては少し過剰です。 備考 私は過去に（非常に単純な）検証を行いました。少人数のフレンドと会話するようなインスタンスでは30万ポリゴン以下、イベントなどの大人数インスタンスでは7万ポリゴン以下を目安に最適化すれば十分であると考えています。検証は単一のアバターで行われていますが、メッシュはそれぞれ別アセットになるようにツールを作成して検証しています。 https://misskey.niri.la/notes/aggjg6jmjz 更新後の数値の決定はVRChatのスタッフにおまかせしますが、私は大まかに以下の数値をイメージしています。 Poor: 300,000 tris Medium: 150,000 tris Good: 70,000 tris 関連する投稿 https://feedback.vrchat.com/feature-requests/p/option-to-not-take-polygons-into-account-when-enabling-minimum-displayed-perform https://feedback.vrchat.com/feature-requests/p/client-side-polygon-limit-slider https://feedback.vrchat.com/feature-requests/p/avatar-polygon-limit-in-safety-settings https://feedback.vrchat.com/feature-requests/p/increase-the-polygon-limit-by-30k-for-medium-ranked-avatars-on-pc https://feedback.vrchat.com/avatar-30/p/incremental-triangle-limit-for-performance-rankings https://feedback.vrchat.com/feature-requests/p/add-performance-rank-that-exceeded-polygon-limit https://feedback.vrchat.com/feature-requests/p/performance-ranks-below-very-poor

It would be nice to be able to block a specific item globally, the same way avatars can be blocked, regardless of who is using them. This feature could be very useful for people with specific phobias (for example insects with the new bee gun, or fire from the New Year items), or just people who find certain items annoying, but still want to see and interact with other items.

With the addition of Loading Screen Customisations, adding a feature to hide Information and Tips during loading would be nice. This could be done manually on each tip card to "Do not show this again", ensuring new tips will still be shown or as a whole "Do not show Info Boxes" option. Especially with the new Old Loading Screen, the boxes block the view of the great and vast space of VRChat. I attached an image of what I mean by Information/Tips boxes.

As VRChat continues to grow, along with its development tools, there is increasing ambition to create larger and more complex worlds. However, the current 1.2GB world size limit can, in some cases, become the primary constraint once all aspects of a world are accounted for. With that in mind, some of us would like to propose increasing this limit for verified/CE creators within the VRChat community. This change would make it easier for verified creators, and those using the Creator Economy, to build more detailed and ambitious worlds, (particularly game-focused ones.) This size increase would hopefully not be too much but would be asking for the change from 1.2GB to 1.5GB~2.0GB allowing for more wiggle room for more content in a world.

It would be nice to be able to see if you have a friend or a blocked person in it, because then you could drop a portal to your friends world (if it is friends+ or public) or avoid the world were a blocked person is.

They should be like avatars and worlds, where anyone can upload and share an accessory without needing to manually get permission from VRChat. Please don't let this amazing feature sit and rot like you did with spawnable items.

◆Current problems Please fix the issue where, if I take a photo while the camera screen is flipped left to right, the resulting image is also saved with the image flipped left to right. ◆Details of the Problem If you press the button in the upper-left corner of the camera to switch to selfie mode, the camera screen will flipped left to right. If you take a photo in this state, the resulting image will also be output with the image flipped left to right. When taking photos in VRChat, I often use selfie mode because I’m usually taking pictures of myself or myself and my friends. If the photos you’ve taken of yourself or your friends didn’t turn out well, you’ll need to use photo editing software to fix them. Since many VRChat users are particular about their avatars' appearance, it's preferable to take phots without flipping the image horizontally. ◆Request details I would like a feature that prevents the image from being flipped horizontally in selfie mode, or one that automatically corrects the horizontal flip when the image is exported. ◆Related posts https://feedback.vrchat.com/bug-reports/p/about-inverting-the-saved-image-when-taking-a-selfie-with-the-camera ◎日本語 カメラ画面が左右反転している状態で撮っても出力された写真は左右反転していない状態で保存してほしい ◆現在の問題 カメラ画面が左右反転している状態で写真を撮ると、保存された画像も左右反転してしまう問題を修正してください。 ◆問題の詳細について カメラ画面の左上にあるボタンを押して自撮りモードに切り替えると、画面が左右反転します。この状態で写真を撮ると、撮影された画像も左右反転した状態で出力されます。 VRChatで写真を撮るときは、自分や自分と友達と一緒の写真を撮ることが多いので、よく自撮りモードを使います。 自分や友人の写真を撮った画像が左右反転していた場合、ペイントソフトなどで修正することになります。 VRChatのユーザーの多くはアバターの外見にこだわりがあるため、写真を撮影する際は画像を左右反転させない方が望ましいです。 ◆リクエスト内容 自撮りモードで画像が左右反転しないようにする機能、あるいは画像をエクスポートする際に自動的に左右反転を修正する機能を追加してほしいです。 ◆関連する投稿 https://feedback.vrchat.com/bug-reports/p/about-inverting-the-saved-image-when-taking-a-selfie-with-the-camera

This can massively reduce download size of worlds in some cases with almost no performance impact. Currently we have to ship complete meshes with the world package instead of in some cases just the list of points/parameters needed to generate meshes, which places a very low and immovable cap on the amount and quality of content in driving worlds, for example. As driving worlds attempt to become more engaging and social, we are running into completely impassable issues that mean reducing comfort (more jagged colliders) for playable time (length of roads). This also results in layouts which are dictated primarily by world size and less by the activity which is the purpose of the world (driving!). This doesn't just impact driving worlds, but also worlds that may have a lot of very modular geometry which currently has to be combined manually or batched in-editor for optimization reasons, and these could also be vastly more efficient with content-per-unit-download size if this combining/batching could be done at runtime in the Start() method.

Many times there's important info that's contained within a description but for many users, it's hidden under the world actions buttons and if you're joining someone, you won't think to look at it. Having it appear at some point can ensure the user is informed, at least a little about the world they're entering.