I been trying to upload 3 avatars and they are all having the same problem and I can not figure out how to fix it
1 Like
Hey No stress this is a rookie mistake, clear this box.
Basically the Blueprint (Pipeline) ID is the unique ID number for that avi upload, because someone else had used that ID to upload to their account u cant, this stops u from uploading changes to someone elses avi on their account without their permission.
All u need to do is clear that box by clicking “Detach” and upload again, the server will give you a new ID automatically.
Bonus information, if u want to upload a quest version of the avi go back there and copy the ID, when u upload a quest and PC version of the same avi they must have the same ID.
On the program side of it the servers treat them as 2 seperate avis, but link them through internet magic, and this ID on both is how the server knows that these 2 avis need to be shown to both PC and Quest at the same time.
I’m running into the same/a similar issue, and clearing the blueprint ID isn’t working.
Is there any other errors in the log there? Try clearing the log and then attempt upload again, when the errors appear try to screenshot them all and put here?
Sure thing, gimme a few.
Interesting ok, on the VRC content creator do u have the VRC base SDK and the Avatar package?
Yep looks good, and there where no other errors?
Sorry to have to ask all the questions.
Only what I gave.
Okay, so…I just changed the thumbnail pic (again) and it suddenly worked??? I’m starting to think something was triggering some automatic system thing.
Oh ok, there is limits to size and file type for thumb nails, the error messages are not very direct some times.
Yeah, lmao. Now I need to figure out how to make sure an av is quest compatible, so I can continue this little project!
Have fun.
with the error being the actual upload, it was the power of waiting a bit and trying again.
1 Like
The SDK can be quite temperamental with issues like this, so it’s worth taking your time to work through it carefully. Also, a big shoutout to @docteh—thanks for consistently addressing these posts. Appreciate your efforts, bud!