Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - wojtek

Pages: 1 2 [3] 4 5 ... 19
31
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: November 30, 2021, 07:35:14 PM »
Second example looks good!

I will be doing some testing as well :)

32
Python and Java API / Re: Undo via Python?
« on: November 30, 2021, 05:16:15 PM »
Hey, any hope for Undo in the api for the next 1.8.0 build? :) Pretty please :)

33
Feature Requests / Re: Close Holes - Within Selection
« on: November 30, 2021, 05:15:53 PM »
Hello wojtek,

We'll try to implement that in the next version update.

It's there, thanks a lot for implementing this!

34
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: November 25, 2021, 03:49:02 PM »
Accidentally ran a batch in 1.8.0 the build (trying to figure out what went wrong exactly)

EDIT: looks like that happened at the mesh generation stage, i retried that part using the 1.8.0 depth maps and it worked ok in 1.7.3. So it is not all wasted :)

35
General / Re: 1.8.0 produces softer meshes. Why?!
« on: November 24, 2021, 12:42:17 PM »
Hmm, in that particular example the extra 'sharpness' is mostly excess noise in my opinion.

Look at the nose, which result is closer to what your actual nose looks like??

36
Hi,
Before I mess about uninstalling 1.7.4 and figuring out how to install 1.7.1 , has the inability of 1.7.4 to create textures correctly (no blurred areas)  been fixed yet as it was reported a month or so ago, and with hard evidence sent to tech support, but not heard back from them at all.  :(  Not the usual 2 day service mentioned there.  several weeks so far. Others also said it was a bug, and suggested 1.7.1

I also still find that Photoscan is usually better at aligning all images, as well as making the texture without blurred areas. If it wasnt that it was SLOW, 5 x as slow, and had no mesh from Depth map, and lousy 3D model manipulation tools , I would prefer it, as it is I am between a rock and a hard place., Unable to actually do a simple job with whats offered by Agisoft.

Steve

It's better in the latest 1.8.0 build, all 1.7.4+ builds are borked afaik.

37
Python and Java API / Re: Save Images with Markers
« on: November 13, 2021, 03:26:14 PM »
You could use PIL library to insert a graphic where your marker coordinates are and save it as a copy. It's a fairly simple library to work with.

38
General / Re: Pausing processing, exiting, reloading, continuing....
« on: November 10, 2021, 03:23:29 PM »
The alignment process for my project is taking 2.5-3 days, due to the overlapping nature of the scans and my 'crap' hardware...
Is it possible to pause Metashape in the middle of doing its processing, such that i can load another project, do processing, play a game, or edit videos, and then come back to MS and resume the processing job?

I've tried just the 'Pause' button on the "Processing in progress..." dialog when running my batch jobs, which does pause it, but it doesn't seem to release all the,  GPU resources, VRAM, and RAM (i guess, i have lots of this, so never been a problem) such that i can do anything else that requires the GPU...  It's crashed.
Is there a way of pausing it such that it doesn't crash?

The situation i have right now is that I've got my dive site aligning, which is going to take another 2 days, but I've got some turntable scanning of insect models to do, which will only be a few hundred photos at most, but will probably cause the crash again, if my experiences before are correct.  And i don't want to kill the batch job and lose the day of processing that it's already done.


It'd be excellent if we could pause MS, such that it does then free up all the resources, such that we could run another instance of MS, or PP, or a game, etc... And then press resume later, and it continues...
OR
To copy Windows, perhaps Metashape could have a hibernate feature, whereby it pauses, saves it exact state, and closes completely... Then absolutely anything could be done, updates, reboots, etc, annoying but sometimes necessary...  Then later, we could reload Metashape and resume the job from hibernation, where it continues where it left off...  As long as all the data is in the same place, everything should work fine.
Perhaps when this kind of pause/hibernation is demanded, MS might have to finish it's subtask and write off the completed zip files, etc, such that it can do a clean interruption.

Thanks.

I wouldn't hold your breath, that is a fairly complex thing to do for a very small amount of users that don't use dedicated hardware for processing. Would be cool, though.

39
General / Re: Dens cloud acces using meshing from depth maps
« on: November 08, 2021, 11:00:10 PM »
Dense cloud is filtered out of the depth maps, yes. But you need to use "Build Dense Cloud" for that, you can re-use existing depthmaps for this if you already built your model, though.

40
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: November 08, 2021, 04:03:18 PM »
Yeah, i'm not getting very good results either. Is there a tweak to revert back to depthmap version from 1.7.3?

edit: I will upload a test dataset and email it to support.

edit2: email sent

41
General / Re: Dens cloud acces using meshing from depth maps
« on: November 08, 2021, 01:08:55 PM »
Dear all,

when meshing using depth maps, a dense cloud is also generated, bit I find no way to get access to that DC.
Is there a way to see, analyse, export this dense cloud?

Thank you and best wishes,
Micha

If you're generating a mesh from depth maps then no dense cloud is being generated (only depth maps that are used for the model)


42
Feature Requests / Re: Close Holes - Within Selection
« on: November 05, 2021, 11:05:58 AM »
This has been added to Version 1.8.0 build 13354!

Thanks for the quick turn-around for the feature request!

Works great and it's implemented in the API as well :)


One more request, it would be nice if we could override the selection to the newly created faces (just like it works without "Apply to selection" enabled).

That way we can apply smoothing or some other operation on the new faces created.

43
General / Re: Face Count, VRAM and Model viewport display.
« on: October 28, 2021, 05:50:34 PM »
Hello wojtek,

For high-poly models display you can enable VBO option in the Advanced Preferences tab and assign considerable amount of VRAM to it. On RTX 3090 you can try to set 6 GB in VRAM field and check, if it allows to navigate ultra-high poly models smoothly. Also please check, that NVIDIA driver is up-to-date.
Alexey, can you please give us some guidance with respect to VBO?:
  • When we should consider enabling it?
  • What value in relation to how much VRAM we have?
  • Or how big our models are?
  • And what implications does this have to other parts of Metashape, alignment, meshing processing, etc?
  • Should it be disabled during processing, and only enabled for the final model?
  • And it obviously works wonders, but what is VBO, what does it actually do in MS???
Thanks.

VBO is explained here: https://en.wikipedia.org/wiki/Vertex_buffer_object

Keep it enabled, it should have no effect on anything but model display. in 1.8.0 the only setting is the on/off switch.

44
General / Re: Face Count, VRAM and Model viewport display.
« on: October 28, 2021, 03:48:35 PM »
Hello wojtek,

If you have time, please check pre-release of 1.8.0 build 13257 for high poly models display (with Enable VBO support option ticked on in the Advanced Preferences dialog).

Hey, I just checked and looked for this thread to provide feedback. It does look like you have fixed the issue I was getting. Thanks!

EDIT: Also it seems that moving the viewport when the model has selected faces does not slow things down by as much as before. Great stuff.

45
Feature Requests / Re: Weld vertices
« on: October 22, 2021, 12:11:19 PM »
Gonna bump this up as I think it's one of those things are pretty slow to do in an external package (when polygon counts get high).

Pages: 1 2 [3] 4 5 ... 19