I’ve heard of lying by omission. Lying by saying too much when it’s two points seems a bit harsh to me.
Something I just noticed about Groups is that there is an option to allow standard members to invite other users to a group, however, this also means they have the ability to accept/join/block join requests.
Is the team able to make it so that there’s an option to just invite other people into the group, with a higher-up role accepting/declining the request when available?
This “issue” persists to other options as well, where an option can grant an option, with an additional option to do owner-levels of customization. Enabling “View all members”, for example, also enables “Manage Group member data”
i have an amazing idea
Since it is difficult to optimize, and unwilling to introduce related shader improvements
Can you define a very poor hard limit, after the official launch of android in the future, you may not need VRchat plus, you can consider allowing plus users to use very poor models (but there is a hard limit)
Only plus users can upload and apply these models on the quest/android side
After all, there are not so many plus users, and releasing some caps can also test the impact?
If there is no way, you can also preset to block these models, prompt warnings, and manually select and open them.
But I think it may be at the expense of some android users who have not replaced their low to mid level SOCs.
Their performance is only equivalent to a fifth to sixth of 8gen2, or even older maybe an eighth, nowhere near the quest2 that is still and only running, and once that happens these models will be so low in fps that they will be impossible to experience, even though these people are already struggling to run the established medium to poor models.
The VRChat devs wrote the system so they can do whatever.
https://feedback.vrchat.com/groups
Feature requests or whatever makes the world go round
This sounds like an issue with the user interface.
First off, i didn’t say he’s lying, but that it seems that he’s lying. However, i admit i could’ve used a different word anyway. i meant something like “this looks dishonest”. English is not my native language, sorry.
What i meant by that is that one of the points was a well-known fact that was the reason behind creating the separate branch in the first place.
it literally cannot be used as a reason to delete it now.
Doing it anyway seems to me that it’s used as a “filler” - you know, like when you don’t know what else to write in your resume for a job of a programmer, so you write in “btw. i’m also forklift-certified, i can swim, and i like Michael Jackson’s songs”, or some other irrelevant factoid.
But why use a filler anyway? The other reason was just fine on its own.
Well, maybe there is something that they just didn’t want to mention publicly, which caused a feeling of emptiness that they felt a need to fill in.
Maybe i’m reading too much into this, but it just looks sketchy. And at best is just irrelevant.
I don’t know why people become all weirdly suspicious and distrusting when it comes to something as mundane as a dev log.
You’re reading far too much into it.
1 Like
Will this be compatible for mobile-based VR headsets like Google Cardboard?
How many people would actually have a good experience with Google cardboard? Seems like a good way to farm negative reviews on the play store when they release it to anyone.
If you live somewhere that Quest hardware isn’t really available, are powerful phones actually available, or would you be playing at sub 20fps?
Outside of viewing 360 photos and video I’ve always felt that Google cardboard is a great way to scare the average person away from VR tech.
i have one thing you guys need to fix and thats a function to let childeren and adult separet from each other becouse the childeren in vrchat are really making my angry to play it again
Okay, so - On my Tensor G1, VRChat plays terrible. Likely because it’s a poorly optimized chipset. That’s true, and I get why they might want to block Very Poors on there.
But I’m upgrading to an 8 Gen 2 soon - with a high end phone like that, I am absolutely DESTROYING the XR1 used in the Quest 2. Why should I not be allowed to see Very Poors if I want to?
Out of curiosity – I use a Pixel 6 Pro (with a Tensor G1) and I get really good performance. Your report caught my eye!
Can you make sure that you don’t have other applications running in the background?
Hi Tupper! Thank you for responding.
So I wanted to confirm that I am on a Pixel 6, not a 6 Pro. Before it was patched so you couldn’t see your own Very Poor I was getting ~30FPS - I’m now getting ~60FPS which is fine.
However, my main issue has been hitching. I’m thinking likely it’s memory related, but I’ll get horrendous hitching when loading into worlds or generally playing like you see sometimes in Quest when you’re low on memory. It can make the game basically unplayable.
I’ll take a screen recording soon so you can see what I mean. Basically, it’s the whole “freezing for a good few frames, audio is messed up” stuff.
Also, I can confirm the issues persist when no apps are open, no notifications are open, and Android reports no open background apps.
Oh, don’t post it at me, I won’t be able to do anything with it. Put it on our Mobile Alpha feedback board!
2 Likes
I would still like to see an Event Window, so users can go to events in VRChat. This feature is a huge part of what is missing in VRChat! I have multiple events each week that nobody can find. It’s extremely frustrating to help people find my events. I think it would make VRChat even more amazing than it is. Please consider doing this. I beg you. Thanks.
1 Like
Thought this might be a good place to post this… people are aware of Quest users having memory problems right? I didn’t for the longest time, a friend reported issues all the time but now I’m getting the error on a regular basis. Can’t join Quest worlds that I could before if I visit one or two other worlds first. So I clear the cache, restart VRC and this time I can enter the world.
Obviously telling the user to clear a cache they don’t control isn’t a good experience. Can a “clear on exit” or “clear on failure to load” option that doesn’t require exiting the app (or something like it) be considered? A cache that generates failures requiring restarting isn’t useful.
1 Like