Messages

61

Bug Reports / Re: Processed thumbnails load too slowly

« on: August 24, 2021, 08:40:51 AM »

Looks like this is fixed in 1.7.4?

62

Feature Requests / Close Holes - Within Selection

« on: August 22, 2021, 08:39:13 PM »

I think that would be useful, close holes that only works on current selection (closes holes present in the current selection)

63

General / Re: Face Count, VRAM and Model viewport display.

« on: August 20, 2021, 06:17:35 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.

Hey Alexey,

Have you guys been able to reproduce what we've reported in this thread?

64

General / Re: Metashape crashing intermittently during saves

« on: August 14, 2021, 08:31:05 AM »

Has there been any more developments on this issue?  I am having the same issue.  Cisco AMP for Endpoints Connector is attempting to quarantine metashape.exe because it is classifying it as a W32.MAP.Ransomware.rwd.  Only happens on certain projects when I'm attempting to create a mesh from depthmaps.  Happens on one with 388 24mp images with medium depthmap quality and high qualty mesh

You might want to reach out to Cisco about this?

65

General / Re: Face Count, VRAM and Model viewport display.

« on: August 13, 2021, 12:15:45 PM »

I tested this with "Show Aligned Chunks" and I could easily display 2 chunks with 300M meshes each for 600M total.

VRAM was loaded up quite heavily but still not 100%.

Looks like the 350M limit is a Metashape problem.

66

General / Re: Face Count, VRAM and Model viewport display.

« on: August 12, 2021, 09:43:34 AM »

For me it looks like a GPU driver problem. Maybe Metashape will be able to workaround it via subdivision of the mesh rendering into multiple draw calls (while the whole geometry data is already in VRAM)?

The cut-off seems to be 350M faces in my case. Has anyone been able to display more complex meshes?

67

General / Re: Face Count, VRAM and Model viewport display.

« on: August 10, 2021, 02:05:14 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.

Hey Alexey,

Thanks, I did have VBO setup already. This is what happens when I try to load a 550M mesh (see attachment).

Doesn't seem to be a VRAM issue as task manager does not show the utilization anywhere near 100%.

edit: attached a second image showing the other result that I'm getting (430M mesh).

68

Python and Java API / Render Viewport with Matcap visible?

« on: August 09, 2021, 04:32:23 PM »

Is this possible? .renderImage only renders with the texture map enabled (black when there is no texture). Is there something I'm missing?

ps. .captureView is not right for the job as it's not rendering an image that aligns with any given camera/photo.

69

General / Face Count, VRAM and Model viewport display.

« on: August 08, 2021, 11:32:16 AM »

Hey,

Is what is possible to display in the viewport at one time dictated by the VRAM or some other internal limit as well? I'm on a 3090 and considering getting an A6000 for the extra memory.

I can currently display about ~300M face meshes with the 24Gb of VRAM 3090 has. Bigger meshes (400, 500M) display in fragmented way (ie only 10 is visible for example).


Alexey, can you advise?

70

General / Re: image stabilisation - yes or no

« on: July 31, 2021, 02:11:49 PM »

Most datasets carry larger issues than the miniscule variation an IS on/off ever could in my opinion. Introduce small shake/blur to any of the pictures and you have a larger issue that a tiny shift of some sort.

71

General / Re: Green blotches on textures generated.

« on: July 31, 2021, 02:08:45 PM »

Which Metashape version are you using? There were rainbow bleeding errors pre 1.6.6.

72

General / Re: Color can affect quality?

« on: July 23, 2021, 04:17:52 PM »

The parts with lesser results probably have less overall noise and thus the reconstruction is not as accurate? Color per say should have no impact on any of it I think.

73

General / Re: Align taking exponentially longer w/ more tracks added...

« on: July 18, 2021, 03:12:50 PM »

It is actually quite impressive how fast this aligns considering what hardware you run it on 

74

Bug Reports / Re: 1.7.3 - Sample Points Bug

« on: July 15, 2021, 01:51:52 PM »

Hello wojtek,

Please check the pre-release version of 1.7.4:

http://download.agisoft.com/metashape-pro_1_7_4_x64.msi
http://download.agisoft.com/metashape-pro_1_7_4.dmg
http://download.agisoft.com/metashape-pro_1_7_4_amd64.tar.gz

http://download.agisoft.com/metashape_1_7_4_x64.msi
http://download.agisoft.com/metashape_1_7_4.dmg
http://download.agisoft.com/metashape_1_7_4_amd64.tar.gz

Beautiful, thanks!

75

Python and Java API / Best Way to edit Metashape.Image()

« on: July 07, 2021, 01:35:49 PM »

Hey Alexey,

Can you advise me what would be the best way to edit a Metashape.Image() that i get by using model.renderDepth()?

I'd like to replaces values below a certain F32 treshold with 0 and then convert to an 8bit Metashape.Image()

Many thanks in advance.


Edit: I just realized I can simply iterate over the Image() and copy values to a new numpy array then convert that to an image using PIL. If there are better solutions please advise though