iOS Closed Beta

In iOS beta, the launch button on the home page “vrchat: //launch” is not intended. When mentioned from the homepage, you have to invite the user, which is a pain. JP: The launch button “vrchat: //launch” on the homepage is not recognized in iOS beta. If you launch from the homepage, you have to invite users, which is cumbersome.

—This is not a bug report, just a suggestion/feedback— Since the majority of supported apple devices have the Face ID feature, which uses the TrueDepth Camera System, we should utilize this ability to get accurate facial data when using face tracking that’s soon to be implemented. For those that don’t have the TrueDepth System, should use the camera by default. But if the TrueDepth Camera is broken or not working as expected (like broken face id) you should have an option to disable it and use the camera instead.

I keep getting logged out every time I switch to other locations (In the same country and region, like from Home to School and vice versa) I’m not sure if this is intentional or a bug but whenever I which to my Wi-Fi to my Cellular service, I would still receive notifications from my account but when I enter the app (In this case, tapping the notification) I would be logged out and require to login. I know this is some kind of security thing but it is becoming annoying to login every time

Within the IOS application, it would be nice if within the friends list you could search for certain friends, like on the website. Plus the added feature of filtering the list and sorting settings (like alphabetical, online/offline, etc)

Directions Open App Store Connect Select VRChat for iOS Navigate to the TestFlight tab For each group selected in the sidebar, under Test iPhone and iPad apps on Macs with Apple silicon click Enable Per instructions here: https://developer.apple.com/help/app-store-connect/test-a-beta-version/test-iphone-and-ipad-apps-on-macs-with-apple-silicon Motivation Apple Silicon Macs can run unmodified iOS and iPadOS software without needing build support, Catalyst, or a separate Mac build. By allowing Apple Silicon Macs to test VRChat for iOS, this would allow a Desktop Mode experience for Mac users in which they can provide valuable feedback in regards to core features and stability, whilst having additional RAM at their disposal which will negate resource issues. Additionally, iOS world and avatar creators who also develop on Mac within this beta would have the ability to near-instantly test their content, without having to switch devices, giving creators a better testing environment, and improving the pace of iteration. This would be a net-positive for creators on Mac.

Letting Apple vision pro play VRChat.

Apple Vision Pro is an MR headset that can run VR released by Apple. I think it is possible with iOS support, so I would like you to support. Apple Vision Pro https://www.apple.com/apple-vision-pro/ Developer Site https://developer.apple.com/visionos/ Related Tickets https://feedback.vrchat.com/feature-requests/p/support-for-apple-vision-pro

December 13th update brought an unneeded change to the compatibility of devices, specifically how the game treats unsupported (ones with less than 6GB) devices. Before, you could still play worlds on unsupported devices. You were given a warning about a device being unsupported. Your unsupported device could crash at some point, but you were warned that that would happen. Now, you are completely unable to play worlds on those unsupported devices. Whenever you click on a world or the Play! button, you only get a message that the device is unsupported and that one should get VRChat on other platforms. I can't state how limiting unsupported devices breaks stuff what I do personally. I tested worlds and avatars immediately after uploading to unity without booting up vrchat on a different device. When I translated a language string I could go in game where ever I am and look at the string to know if it's correct or not. The fact that it doesn't work in a single update is annoying and should be reverted to how it has been before. This is somewhat anti consumer in my opinion. I do not want to be forced to buy a better device or use a different device because developers decided so. I know the limitations of my device, respected the warning and never complained when it crashed (which was a rarity). I understand that people kept sending crash reports from unsupported devices, but they were absolutely warned. Please revert it to how it was before.

The version for iOS should dynamically choose different limits for devices that have actually powerful internal hardware, specifically talking about the M series iPads. The bare minimum I would just like is that a version for M series ipads or Macs (related https://feedback.vrchat.com/ios-mobile-beta/p/apple-silicon-mac-support ) running through the iOS layer would allow just custom avatar shaders. We already have desktop class games for the iPhone 15 pro max and later phones, let this platform shine the same way on this hardware

There are some iOS-compatible (including Android conversion) worlds that have very poor avatars as the 3d model But they can even run at 120 fps. If the reason for the restriction is crashes and low frame rate, then why not just use the Show Avatar feature? It's really painful to reduce the polys of Avatar to 20k. Through the new 6GB RAM limitation, this bad restriction SHOULD be removed.