Hi,
For the past 2 years we have been making the Mesh in Matic and exporting the 4 required files to upload to Pix4d Cloud.
.obj + .mtl .jpg + offset.xzy.
Our latest run of some data, we are now getting a “tiled” output for the mesh within its own folder, however, depending on the size of the job, the number of tiles vary.
Understand if this is a new way forward, but how do you upload such mesh data to the cloud ?
Thanks !
Hi jhawkins,
This is our “scaleable mesh” option which is the default. However, you can change the mesh back to the “standard” option.
The other item to mention is that you can always use our Share to PIX4Dcloud feature within Matic. This will let you upload already processed results to the Cloud for viewing.
Hi jhawkins,
To add to what Mike was saying, you can upload the high resolution mesh directly from Matic using the Share to Cloud functionality. This will export the full resolution mesh a a 3D tiles asset, with the full LoD. Would that work for you?
yes this is a pain, I re processed 3 projects trying to create a single mesh for upload, and assumed it was a bug. The share to cloud option hasnt and still doesn’t work . If this mesh is better thats great, but can we then need a method that works for the cloud.
@jhawkins and @software6 the best way to upload your mesh to our cloud is to use the “Share to PIX4Dcloud” feature. Let us know how it goes or why you still export from PIX4Dmatic before uploading to PIX4Dcloud.
What issue are you running into when attempting to share to PIX4Dcloud @software6 ?
We just updated to 1.77.1 today and found the the exported mesh .obj is in tiles instead of a single .obj.
I can’t find an option to change from scalable mesh back to “standard” anywhere…
Our clients can’t handle tiled mesh, it needs to be a single file.
Any ideas?
@aus-bd-survey the pipeline we use to generate a mesh has recently changed and the 1.77.1 preview version indeed does not include a way to export a single-tile OBJ file. We are working on adding this option again. Do you know which third-party applications your clients need to import the mesh in use so that we can ensure good compatibility? In the meantime, I recommend you revert to the latest stable release, 1.76 (or wait a few days to use the 1.76.1 patch we are about to release).
GEM4D is one of the main third-party applications, as well as Vulcan for some other clients.
Will there be a fix for this after 1.77.1? or will be we forced to stay at 1.76?
@aus-bd-survey thanks for the info, and I confirm that we are planning to re-implement the mesh export of a single OBJ file as soon as possible. In the meantime, please use version 1.76.1.