Cant see listed avatars, How to fix? about beatsabercustomavatars

[nicoco007]

My bad, turns out there were a few issues causing this. This version should hopefully work properly.

[nicoco007]

Did you extract the CustomAvatars\Shaders\customavatars.assetbundle file when installing the mod? It looks like the file being loaded is from an older version.

[haozi23333]

game version: 1.11.0
avatars: 5.0.0 RC1 RELEASE
openvr: 0.3.0 RELEASE
openvr-saber 0.3.0 RELEASE

avatar list cant display

[kissmonstar]

I'm having the exact same issue, and I installed everything fresh as I did a clean wipe of beat saber after the update

[Interpause]

will note I am having the same issue as well, also did a fresh reinstall

[paradox201]

hey - we are also getting the same issue exactly as pictured above - mod menu all ok - but just get the stats page - fresh install and have checked CustomAvatars\Shaders\customavatars.assetbundle came from the latest version

[trudruchocolatemilk]

same issue here, I also did a clean install, same thing

[nicoco007]

Could you try this version and let me know if it works? If it doesn't, could you please attach your latest log? It's the file called _latest in the Logs folder of your Beat Saber installation. Please use the version below!

[Slawsha]

This issue actually resolved itself for me yesterday. I just clean installed the game after mods became available again and dragged the folders directly into their respected locations. I used Avatars 5.0.0 and OpenVR 0.2.1 and they worked flawlessly for me. Thanks for your help.

[rchian3]

I am having the same issue. I tried the version in the comment above and it didnt work for me.
_latest.log

[Zerotwo111]

Having the same issue as well and tried the version you linked with same issues continuing. I linked the lastest log I aint sure what the issue is as I have a fresh install as well like everyone else.
_latest.log

[Lynlisss]

Having the same issue. Did a fresh install of everything and still get the same issue. Latest log is linked.
_latest.log

[trudruchocolatemilk]

same thing
_latest.log

[trudruchocolatemilk]

did a clean install and heres the new log
_latest.log

[nalister89]

That did it!! I can use my avatars again.

[nicoco007]

Awesome 😄 I'll just wait a bit to see if I missed anything (again) and then I'll officially release this version.

[felinearts]

5.0.0 RC2 fixes everything! <3

[Lynlisss]

Yes, yes yes! It works great now! Thank you so much!!!

[kissmonstar]

RC2 was a complete success here as well

[trudruchocolatemilk]

hell yeah man

[ggiinnoo]

This version also worked for me. I had the issue that there was no back button and no avatar selection. The avatar settings were there.

[nicoco007]

Looks like this is fixed, so I'll close the issue. I'll be releasing RC 2 in a few days since a couple of other issues have cropped up.

[emerycw7]

I haven't gotten this to work

[michaellgmichaellg]

My bad, turns out there were a few issues causing this. This version should hopefully work properly.

Might be just my setup, blade sorcery also doesnt work, vrchat does work tho, all to state that my body tracking feature isnt supported on any avatar including the template by default

[singeee]

Hello! I have a problem with that new custom avatars mod version. Half of my avatars stay on T-Pose while they were working fine with the old version...

[DrDraxi]

It doesn't work for me. Neither the new version or the "fix". Still can't see the avatars in the menu and have to restart the game to get out of it. :-/

[nicoco007]

@emerycw7 @DrDraxi Looks like there are still some lingering issues since a few other people have also said it's not working over here. I'll be posting updates there since the original problem here has been solved.

@michaellgmichaellg Remember that you have to calibrate or explicitly bypass calibration for full body tracking to work as of beta 8 of Custom Avatars. Also, you might be having the same problem as what's going on in #40. If that's not the case, could you please open a separate issue?

@singeee The problem you're having hasn't been reported yet. Could you please open a separate issue?