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.


Topics - Kjellis85

Pages: [1] 2 3 4
1
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.

2
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

3
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.

4
Bug Reports / Broken high res mesh
« on: March 04, 2020, 01:18:26 PM »
EDIT: ran it again with 100M face count (original set at 0) and it worked. Could be an issue with 0 face count.

Tried building mesh from a 154M pointcloud (generated in MS) but get this weird looking mesh, that is supposedly 373M poly high. Have made this previously with no problem.

2020-03-04 08:32:40 BuildModel: quality = Ultra high, depth filtering = Mild, source data = Dense cloud, surface type = Arbitrary, face count = 0, interpolation = Enabled, vertex colors = 1
2020-03-04 08:32:40 Generating mesh...
2020-03-04 08:32:40 Grid size: 8990 x 1574 x 22341
2020-03-04 08:32:40 Tree depth: 15
2020-03-04 08:43:37 Tree set in 656.832s (154227843 points)
2020-03-04 08:43:51 Leaves/Nodes: 1023032137/1169179585
2020-03-04 08:48:17 Laplacian constraints set in 265.912s
2020-03-04 08:48:20 Depth[0/15]: 1
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0 / 0
2020-03-04 08:48:20 Depth[1/15]: 8
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0 / 0
2020-03-04 08:48:20 Depth[2/15]: 64
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.00100017 / 0.000999928
2020-03-04 08:48:20 Depth[3/15]: 512
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.000999928 / 0.00200009
2020-03-04 08:48:20 Depth[4/15]: 4096
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.00499988 / 0.00600004
2020-03-04 08:48:20 Depth[5/15]: 32768
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.0219996 / 0.0180004
2020-03-04 08:48:20 Depth[6/15]: 13472
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.00800037 / 0.0269995
2020-03-04 08:48:20 Depth[7/15]: 36768
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.0190001 / 0.0489998
2020-03-04 08:48:20 Depth[8/15]: 121864
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.0429997 / 0.0740004
2020-03-04 08:48:20 Depth[9/15]: 441448
2020-03-04 08:48:20    Evaluated / Got / Solved in: 0 / 0.136 / 0.174
2020-03-04 08:48:20 Depth[10/15]: 1682024
2020-03-04 08:48:22    Evaluated / Got / Solved in: 0 / 0.701004 / 0.821996
2020-03-04 08:48:22 Depth[11/15]: 6582408
2020-03-04 08:48:26    Evaluated / Got / Solved in: 0 / 2.021 / 2.387
2020-03-04 08:48:26 Depth[12/15]: 25565256
2020-03-04 08:48:43    Evaluated / Got / Solved in: 0 / 7.639 / 8.752
2020-03-04 08:48:43 Depth[13/15]: 95368864
2020-03-04 08:49:48    Evaluated / Got / Solved in: 0 / 29.501 / 32.825
2020-03-04 08:49:48 Depth[14/15]: 318797312
2020-03-04 08:53:35    Evaluated / Got / Solved in: 0 / 102.649 / 113.56
2020-03-04 08:53:35 Depth[15/15]: 720532720
2020-03-04 09:01:52    Evaluated / Got / Solved in: 0 / 234.363 / 236.971
2020-03-04 09:01:53 Linear system solved in 815.592s
2020-03-04 09:02:34 Got Iso-value in 41.031s
2020-03-04 09:02:34 Iso-Value -0.0517755
2020-03-04 09:16:43 373736974 faces extracted in 848.316s
2020-03-04 09:29:55 Calculating vertex colors...
2020-03-04 09:29:55 processing nodes...  done in 11.708 sec
2020-03-04 09:30:07 calculating colors...  done in 2177.03 sec
2020-03-04 10:06:25 Peak memory used: 79.40 GB at 2020-03-04 08:43:34
2020-03-04 10:06:25 Finished processing in 5625.24 sec (exit code 1)
>>>

5
General / Index overflow
« on: February 14, 2020, 10:15:29 AM »
I am encountering Index overflow on a 582M poly dense cloud, processed at Ultra High. During meshing the index overflow happens after 24 minutes. Is this a RAM limitation or a bug?

Specs:
i9-9900K @3.6GHz
128 GB RAM
RTX2070

6
General / Hardware test thread
« on: December 12, 2019, 12:30:54 PM »
This is a forum request, not a feature request, so I am posting here ::)

I think a lot of people who are interested in building their own rigs for processing are wondering what to choose. There are several commercial sites that have guides and recommendations for what kind of setup you should buy, but I think most of these sites are biased towards their own products, as well as not being up to speed with all the different products out there. Currently, the AMD CPU's and GPU's are making waves, but very little information about their metashape performance is to be found. But I am pretty sure some of the users here have real world experience using these. Therefore I propose that we create a sticky thread were people can post system specs and report from a run on a given test set of images, perhaps one for aerial and one for a statue or figure. That way we can keep track of how well different systems perform.

As a sample I have run a test on ultra using the Monument sample set on my system with the following specs:
CPU: Intel Core i9-9900K CPU @ 3.60GHz
GPU: GeForce RTX 2070 4GB
RAM: 4x32 GB (128GB)
Storage: Western Digital WDC PC SN720 SDAPNTW-512G-1006

Attached is the processing report.

7
Feature Requests / Upload data ArcGis Online
« on: December 03, 2019, 12:04:17 PM »
I would really appreciate an upload module that is linked to ArcGis Online. Arcgis is the most widely used application for GIS professionals and the current workflow between MS and ArcGis is somewhat cumbersome.

8
Bug Reports / Cloud error (SOLVED)
« on: November 13, 2019, 04:06:34 PM »
I am trying to run a project in the cloud, but after upload i get the attached error message.

9
General / Best practice tiny objects
« on: May 31, 2019, 12:17:41 PM »
I have made some attempts at doing tiny objects but I am struggling to obtain proper overlap. I am using a Syrp mini turntable rig with synchronised shutter and a NIkon D610 60mm macro for shooting.

My example is a 1200-year old brooch, aprox 45x27x12 mm dimensions, and ~1mm wall thickness. I have to be extremely cautious handling it and cannot use any adhering materials such as putty directly on it to stay in optimal positions. I did several rounds at different angles, but issues with DOF and (I think) the wall thickness is preventing the different sets from aligning.

My question is; have you done any small object like this - and if so; what is your methodology?

10
Feature Requests / shortcut rename chunk
« on: November 23, 2018, 12:33:00 PM »
Could we have custimizable actions for chunk (right click chunk -> rename etc.)?

11
Bug Reports / SLPK invert Z
« on: October 29, 2018, 12:24:49 PM »
I did an slpk export of a tiled model and tried import to arcgis pro, but I am getting negative Z-values close to the inverse of actual Z. The model looks fine and there is no issue with display, other than an inverse of Z.

12
General / Inner boundary model clipping
« on: September 21, 2018, 03:37:53 PM »
I see in the changelog for 1.4.3 build 6529* that it says "Added boundary clipping for model export.". I only get this to work as outer boundary clipping. Is it only possible to have an outer boundary, or is it a bug that makes inner boundary not work? If I use only Inner boundary, it exports the model as if it is outer boundary.

*I am running 1.4.4 (6848)

13
General / ArcGIS integration
« on: September 12, 2018, 12:15:38 PM »
There is still no integration between PS and ArcGIS as far as I can see. I have tried asking about this before but haven't goten any clear answer regarding whether or not it is being developed or not. So in the mean time I was hoping that somebody had done some groundbreaking work on this, other than converting collada-models in ArcScene from lokal to UTM using model swap technique. Anyone working with ArcGIS Pro that have a sollution? Is there any way of converting vrml to GeoVRML for instance?

14
General / Ortofoto from bottom of trench
« on: September 11, 2018, 02:49:27 PM »
So I am trying to find a best practice workflow for generating ortophotos from trenches. I am only interested in the very bottom of the trench, but I end up with getting "bleeding" from the top of the trench. It probably has to do with the fact that the images are taken slightly oblique  in order to get the whole trench bottom. I have tried manually editing the seamlines in order to avoid this, but it is a very tedious and time consuming task.
The image I have attached shows the orto produced with full geometry produced, ie. the entire trench is meshed, then orto produced on mesh. Same result happens if I use dense cloud or if I trim the mesh/point cloud so that only the bottom is left. I have also tried masking everything but the bottom, but nothing seems to work.

Any ideas??

PS: Can we please have a larger file size than 512kB on attachments? Can't even do a screenshot without exceeding the limit...

15
General / Best practice - fine detail on low poly output
« on: June 22, 2018, 02:56:45 PM »
I am looking for a good workflow on mesh decimation without loosing fine details.

My subjects for this workflow are rock art sites. They are typical large areas, from 2x1 meters, up to 50x5 meters. Some of theses sites have carvings covering a large  percent of the surface, with typical carving depth of between 1-5 mm. If i process 200+ (24mpx) images on ultra high, I will end up killing my hardware. Even if I could manage to process it, it would take a lot of processing hours, and the end result would be useless because there are no way I could disseminate a 300M poly model to any user, let alone publish it on any standard platform. So what I need is a good workflow that A) reduces time spent modelling "un-interesting areas" at more than necessary quality whilst going ultra on points of interest, i.e carvings, and B) decimate mesh without loosing fine details.

I know this is a lot to ask, if at all possible, but I am hoping for some ideas that might solve some of my challenges.

Pages: [1] 2 3 4