Matic 1.76 to CloudAdvanced: problems with mesh georeference

Hello,
we have observed this error multiple times, but it is not reproducible. When uploading a dataset directly from MATIC to CLOUDadvanced including a mesh (the standard one, not the scalable one), we sometimes get an error regarding the mesh in the cloud. It says there the mesh is not georeferenced and that we should upload the offset.xyz. I would like to mention again that we uploaded directly from Matic to Cloud. Normally, we don’t upload any offset files in this workflow.

Previously, we could solve this error by uploading the dataset again from Matic to Cloud. It’s a bug anyways but at least there was a workaround. Sadly, this step doesn’t work anymore now. We tried the upload multiple times and got the same error again.

Can anyone help? The project is fully georeferenced in Matic. We also need the mesh in Cloud Advanced!

I’ve noticed that if I look in cloud before the upload is complete. I think Matic uploads that file last for whatever reason.

Cool, thanks. So the solution would be uploading into the cloud from matic while logged-out in the browser from Cloud? Will try that immediately!

I’ve always just used Matic’s send to cloud feature, not tried uploading them from the exports.

Ok so I guess we read us wrong @scavendish. I also always directly upload from Matic to the cloud. Don’t know why sometimes I do have this error.

Update: tried to upload from Matic to Cloud without being logged in, same error, mesh is not georeferenced. Meanwhile I uploaded the project 3 times, always the same error :man_shrugging::man_shrugging::man_shrugging:

Please Pix4d-Support, provide some help!!

Also I realized, that although the orthomosaic is there, the preview in the timeline is now missing. Why? :man_shrugging::man_shrugging::man_shrugging:

Hello Pix4D Support, any solution? Can you please look into it?

@Anastasis_Spachos

@Pierangelo_Rothenbuhler can you maybe tell your collegues from support here is a new question online? I thought it will be better to post it here in the troubleshooting section than opening a ticket, so others from the community can find a solution directly, if they run into the same problems. Thanks :folded_hands:

SOLVED!

The mesh now is georeferenced. I don’t know why! I found an older post here saying almost the same: you have to sit and wait, until CloudAdvanced is georeferencing it. I did not observe this before, but good 2 know. :victory_hand:

Now everything looks normal:

You mean mine from yesterday where I basically said that it won’t happen until the very end :rofl:

Glad you fixed it.

No, I meant this post here: 3D Mesh is not georeferenced question

It’s all about waiting :wink::oncoming_fist: Thansk for your input ScotT!! @scavendish