[1468] Badges don't appear on profile
complete
DAG-XR
Looks like VRRat yoinked my Early Supporter badge, and my current supporter badge. It's not appearing on my profile in 1468!
Photo Viewer
View photos in a modal
Log In
StormRel
marked this post as
complete
This post was marked as
available in future release
DAG-XR
Hurray :)
Campa
DAG-XR BluWizard Hi!
We're still investigating this one. A few questions -- how often do you encounter this issue? Are you able to reproduce it using certain steps, or does it always happen on affected accounts? Which badges should you be seeing on your accounts? Any additional info would be super helpful. 🙏
DAG-XR
Campa I encounter this issue nearly every session. I have a feeling that it <<might>> be connected to the same bug where group thumbnails will lag behind on profiles. I should have two badges for my profile; one for early supporter, and one for active supporter.
It shows up fine on the VRChat website and VRCX, but seems to only encounter on the client.
I think it just seems to affect you when you look at your own profile. I'm not sure about the badge status for other accounts.
Wolfy_527
Campa The problem appears to be happening every session for me as well. It occurs on desktop and in VR. I should have the same two badges that DAG-XR mentioned. The "Early Supporter" badge and the "Active Supporter" badge as well. As DAG-XR mentioned, it also shows up fine via the website and VRCX. I noticed on VRCX both badges are tagged as "False" for "Showcased" so I am not sure if this setting, internally, would have anything to do with that at all, but it might be worth looking into as a lead to something?
Photo Viewer
View photos in a modal
DAG-XR
Still present in 1470.
DAG-XR
And 1471.
This post was marked as
needs more information
DAG-XR
If there's anything I can provide, let me know. It's pretty easy to reproduce.
BluWizard
DAG-XR Got the same thing, but have a feeling it's the same as how you got it. I noticed it after viewing my own profile in different instances than my Home World. Could be an API glitch.
Campa
marked this post as
tracked