Messages

1

General / Re: Unsuported datum

« on: May 31, 2022, 04:45:37 PM »

When importing from Arcgis Pro I got nothing. Only workaround is as previously mentioned.

2

General / Re: Unsuported datum

« on: May 30, 2022, 12:05:16 PM »

I think the key is to have the correct EPSG code as in AUTHORITY["EPSG","25833"] at end of prj file.

Thanks a lot, this worked, as well as just deleting the prj and importing in as 25833.

But I think it is strange that the output from ArcGIS Pro does ot work directly, but maybe there is a setting during export that adds AUTHORITY attribute to prj?

3

General / Re: Unsuported datum

« on: May 29, 2022, 08:58:57 PM »

Thanks, I'll give it a try. Although, i do think it is bad practice

4

General / Unsuported datum

« on: May 29, 2022, 05:16:14 PM »

I am trying to import a shape in EPSG 25833, the same as my MS project, but I get the Unsuported datum error. I can create shapes, but if I import a shape in the same coordinate system I get the Unsuported datum error. See attatchements.

5

General / Re: Calculating vertex colors very slow

« on: December 15, 2021, 12:18:08 PM »

I skipped 1.7.5 and jumped right to 1.8 beta and did not observe the same problem, CPU utilization was ~100% during vertex colorization.

6

General / Calculating vertex colors very slow

« on: December 13, 2021, 05:02:52 PM »

Im running an object scan which extracted 45M faces from 19,4 m dense cloud. Face extraction took 262 seconds  while colorize took about three times as long. While calculating vertex colors Metashape only utilized about 5% of CPU (24core ryzen, no core highly utilized) and nothing of GPU. Memory consumption minimal. Should this be the case?

Processor   AMD Ryzen Threadripper 3960X 24-Core Processor    3.79 GHz
Installed RAM   128 GB (128 GB usable)

Metashape 1.7.4 13028 64-bit

7

General / Re: Enable matcap view mode

« on: April 12, 2021, 12:10:28 PM »

I could not get the matcaps from blender (2.9 standard matcaps) in exr format to work. Downloaded a matcaplibrary in png and it worked.

However, when I try to view the model in matcap, the framerate drops to 1-2 fps (estimated). On shaded model it runs smoothly (don't know exact framerate). 15m poly model. Could this have something to do with resolution of matcap? The matcaps i have tested are 1024.

Running latest stable 64 bit windows Pro release of MS.

8

General / Enable matcap view mode

« on: April 09, 2021, 04:21:30 PM »

So I found the Matcap settings under model view and wanted to try it using  matcaps from blender, but it seems as though the function is not enabled. The check box "Enable matcap view mode is greyed out. Is there another way to turn it on?

I have tried it with several models and with different matcaps but to no avail.

9

Feature Requests / Re: Is there a way to change the Basemap displayed?

« on: March 22, 2021, 05:40:33 PM »

That would work. However, I cannot get my WMS to register. https://openwms.statkart.no/skwms1/wms.topo4?

The WMS provider is reporting full operational status.

10

Feature Requests / Re: Is there a way to change the Basemap displayed?

« on: March 22, 2021, 10:56:16 AM »

I would also like to see a feature where we could add our custom wms basemaps

11

Python and Java API / Re: Python scripts collection?

« on: March 09, 2021, 10:57:17 AM »

+1 great reasource!

12

Bug Reports / Re: Broken high res mesh

« on: March 09, 2020, 03:16:46 PM »

Ok, I will change to a lower limit, within my Vram. Will run another test for tomorrow.

13

Bug Reports / Re: Broken high res mesh

« on: March 09, 2020, 03:14:27 PM »

I have VBO activated and set limit to 41280 MB(!). Could that be an issue, that it has too much memory allocated? I was under the impression that the more the better was the general rule for VBO?

14

Bug Reports / Re: Broken high res mesh

« on: March 09, 2020, 01:36:22 PM »

I am running NVIDIA RTX 2070 with driver 26.21.14.4128

15

Bug Reports / Re: Broken high res mesh

« on: March 09, 2020, 11:15:15 AM »

Decimated the broken 360M model to 10M and it appears to be in order, at least in MS model view. I realize that a workaroud could soleve the problem, by steering away from the large model, but it is not a solution for the long run.