Current processing problems?

Support Bugs
#1

Is there currently a processing problem on the sketchfab site? I have just tried to upload a model from within metashape, and Sketchfab site comes up a processing failed error (error 13). I tried to reupload manually with an OBJ export - same result. I know the obj file is OK because it loads into other programs with no problem. I also tried uploading an old model that worked last month - and again same error 13.
Is it just me or is the processing engine having major issues?

Edit: I just tried directly uploading and exported obj file (fresh upload rather than replacing the failed upload), and it worked fine. It seems Metashape may have changed the format of their directly uploaded files to an incompatible format??
cheers
Bill

#2

Hi Bill,

I don’t see any failed uploads on your account. Can you share the URL or a sample OBJ/MTL that fails?

I’m not aware of any overall processing issues, and I’m not seeing any drop in uploads coming directly from Metashape.

Metashape Uploader failing
#3

G’day James,
That’s because I deleted them all. I will upload one again today and let you know when it is uploaded. I think this is an issue with the new version of Metashape. I have asked this same question on the Metashape forum but have not received a response as yet. Thanks for your response.
cheers
Bill

#4

G’day James,
I have just uploaded another model from within Metashape giving the same error 13. I am fairly sure now this is a Metashape (v2.01) issue. I manually uploaded an obj export of the same model as a fresh upload and it worked fine.
cheers
Bill

#5

I am also having issues with the Metashape uploader. I also get an error 13. I will ask for support on the Agisoft forums.

#6

I have already raised the issue there and the problem has been acknowledged. They are working on a hotfix.
cheers
Bill

#7

The hotfix (build 15986) fixed this issue for me.

#8

Hi, I’m having the same issue with Metashape uploads - except I get the error code 400 - unknown error. I’m using Version 2.0.1 build 15816.

#9

You need to get the hotfix (build 15986) and install it - this build corrects the issue.
cheers
Bill