Agisoft Metashape
Agisoft Metashape => Bug Reports => Topic started by: Iluvathar on March 10, 2020, 02:25:14 PM
-
Hello,
Since the last update, texture generation is taking a really long time, i have a considerable number of iteration packs. Can someone explain the reason ?
Thanks a lot
-
Hello Iluvathar,
Can you share any sample mesh model to support@agisoft.com which can be used to reproduce the problem, specify the processing parameters used and also provide the processing log from your tries?
-
Hello Iluvathar,
Can you share any sample mesh model to support@agisoft.com which can be used to reproduce the problem, specify the processing parameters used and also provide the processing log from your tries?
Hello Alexey,
I also ran into this issue, do you still need test data?
-
Hello wojtek,
If you have the sample mesh that can be used please share it with us along with the processing parameters used and processing log.
-
Hello wojtek,
If you have the sample mesh that can be used please share it with us along with the processing parameters used and processing log.
I sent it to support@agisoft.com
-
Hello i'm trying to extract a sample from my work by cutting my scene, i have a 11000 pics scene and selected a part of it, reduced overlap to have just the images of the selected part enabled, the images that are useless are disabled, how can i select all the desabled pictures at once ?
-
Hello wojtek,
Thank you for sharing the sample data, it is useful for the further investigation. As soon I have any news regarding the problem, I will post an update here.
Hello Iluvathar,
Currently you can do that only using the script:
import Metashape
for camera in Metashape.app.document.chunk.cameras:
if camera.enabled:
camera.selected = False
else:
camera.selected = True
-
Files sended with wetransfer containing a part of the model with much less pictures, i ran the workflow and had much less iterations, hope it will help
-
Thank you for additional data.
Hopefully, the UV parametrization will be fully fixed in the next version update. For example, the model provided by wojtek took about 30 minutes.
-
I am also having this same issue after the update. Textures on anything processed never complete. For instance I began processing a chunk last Friday, and this morning after 60+ hours the Texture was only approximately 50% complete. The chunk has 1100 photos but i am seeing this issue with any amount of photos.
-
As a workaround in the version 1.6.2 you can create the following Tweak via Advanced preference tab and set its value to True:
main/texture_enable_legacy_uv
After that select Legacy parametrization option in the Build Texture dialog instead of Generic. Generic option will be fixed in the next version update.
-
As a workaround in the version 1.6.2 you can create the following Tweak via Advanced preference tab and set its value to True:
main/texture_enable_legacy_uv
After that select Legacy parametrization option in the Build Texture dialog instead of Generic. Generic option will be fixed in the next version update.
Using Legacy may be a bit tricky, though (see image).
(just tested this, sorry for not replying to the previous email)
-
Hello wojtek,
Legacy is a way to pass the infinite iterations bug, although the texture atlas is considerably less optimal compared to the Generic parametrization expected result.
-
Another possible workaround in the version 1.6.2 is using multi-page atlas with 1000 pix pages, for example, instead of single 8K atlas use 64 pages of 1K atlas, although it might not be an option, if you need a single page as an output.
-
Hi
Same problem for me.
Legacy works but result is not great.
I look forward to the urgent fix in the next version. :)
Many thanks
Dave
-
We have published pre-release of 1.6.3, please check if Generic UV parametrization works fine now:
https://www.agisoft.com/forum/index.php?topic=12182.0
-
Hi Alexey,
still takes a very long time or gets stuck, compared to a similar project that doesn't triggers the pack iterations loop.
I will upload the project for you and send a link to support@agisoft.com so you guys can check it.
cheers
Willi
-
Hi Alexey,
still takes a very long time or gets stuck, compared to a similar project that doesn't triggers the pack iterations loop.
I will upload the project for you and send a link to support@agisoft.com so you guys can check it.
cheers
Willi
Hey Will,
I didn't manage to get it stuck yet, the process is taking a while but it does complete eventually.
-
I have a two projects where it gets stuck ... or at leased takes an unusual long time compared to similar projects. For example the on in my other post runs already for an hour while a similar one completes in 9 minutes.
cheers
Willi
-
I have a two projects where it gets stuck ... or at leased takes an unusual long time compared to similar projects. For example the on in my other post runs already for an hour while a similar one completes in 9 minutes.
cheers
Willi
Play around with the "texture_size" parameter in BuildUV, it seems to control how tight the packing is (thanks!) and larger value == longer processing time from my current testing.
-
Where do I find this BuildUV texture_size thing? :) I have been doing some more tests and so far the only way I could get it to work was to split the 16k texture into multiple ones, that also processes a hell of a lot faster doing 4x8k. Alexey did you guys look at that project I send, any idea why this one takes so long?
-
Hello Willi,
We are checking the provided project now.
-
Still getting the same issue in version 1.6.3 build 10638 when texturing dense meshes (20M+ polys).
Mak
-
Hello Mak,
Is it possible to share the processing log and the project (or at least the mesh, that we can re-import and run Build UV operation onto)?