31
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: December 21, 2021, 04:31:26 PM »
Last night I did a test with 3 chunks in a batch and it seemed to work properly. I’ll try more today to confirm.
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.
32
Bug Reports / Metashape stops when Mac sleeps
« on: December 18, 2021, 06:48:16 PM »
A problem I have with 1.7.3 (the version I use most of the time) is that the application doesn't prevent the Mac from going to sleep while Metashape is working. So, if I run a Batch and leave the room I often come back to find my Mac asleep. When I wake it I see that Metashape has stopped where it was when the Mac dozed off (usually after 15 minutes since that's what I have it set to in System Settings). Metashape then continues once the Mac is awake.
This can be prevented with a single like of code:
UpdateSystemActivity(OverallAct);
I don't know if the later versions of Metashape already do this, but if not, that line of code needs to be called every ~30 seconds from a NSTimer function. This will prevent the Mac from going to sleep while Metashape is working.
This can be prevented with a single like of code:
UpdateSystemActivity(OverallAct);
I don't know if the later versions of Metashape already do this, but if not, that line of code needs to be called every ~30 seconds from a NSTimer function. This will prevent the Mac from going to sleep while Metashape is working.
33
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: December 15, 2021, 09:22:48 PM »
Also, I get error messages and failures on some Chunks during a batch. In that last example, the 4th Chunk will always fail to generate a mesh when using Batch. I get "Error: Operation not applicable" and "Error: Null model" towards the end of the batch on that. But as always, just doing it by hand works perfectly fine. It only fails during a Batch.
34
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: December 15, 2021, 08:23:59 PM »
I don't know if this is the same issue as the Batch bug reported above, but I have noticed that if I am processing multiple Chunks in a single Batch, the first Chuck works fine, but the meshes on the remaining Chunks tend to be malformed. For example, attached are two screenshots of Chunk #2. The first shows the malformed mesh that was created during the Batch. However, if I simply build the Mesh again manually I get the correct results as shown in the 2nd screenshot.
In this particular instance I had 4 chunks in the Batch. The first was fine, but the other 3 were completely malformed.
In this particular instance I had 4 chunks in the Batch. The first was fine, but the other 3 were completely malformed.
35
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: December 03, 2021, 06:11:34 PM »
I just had my first system freeze with the new beta. This time I had Metashape running a batch and during the depth map generation process I launched Blender. As soon as Blender came up and showed me it's window the system froze. In previous versions of Metashape the depth map process would cause my Mac Pro and MacBook Pro to randomly freeze up even if I was doing nothing. However, I have noticed a pattern that if I try to use Blender at the same time it seems to cause these freezes to happen far more often. Perhaps both applications are fighting for GPU resources? I'm not sure why that would cause the Mac to entirely freeze up and require a hard reboot though. I can use Blender while Metashape is working in the background about 90% of the time, but sometimes it seems to trigger these freezes. Blender, of course, never causes a system freeze on it's own - only when Metashape is doing Depth Map generation in the background.
36
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: December 03, 2021, 05:58:17 AM »
Well, this scan had 70 cameras and came out quite blobby on the underside. Some of the blobs are connected to the main geometry so it's not usable. This is the first failure I've had with this new beta version. I'll have to go back to 1.7.3 to get this one to work properly.
-Brian
-Brian
37
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: December 02, 2021, 08:25:38 PM »
So far I'm having good luck with this beta. There's still a lot of blobby gibberish being generated in most of my scans, but it's usually far enough away from the real geometry and not connected to it that it's fairly easy to remove. Still, 1.7.3 was the last version that generated totally clean meshes that didn't need any cleanup (for my application). The native Apple Silicon support is nice, and there's definitely a speed boost with this build. No crashes yet which is promising 
-Brian
-Brian
38
General / Re: Agisoft Metashape 1.8.0 pre-release
« on: November 30, 2021, 04:53:44 PM »
I just ran two tests with build 13597 and I'm happy to report that the blobby mess on the underside of the geometry has been almost entirely fixed. It's still not quite as clean as 1.7.3, but it's MUCH better than any version from 1.7.4 to the previous beta. In my first test the geometry was 100% clean with no blobs. In my second test I had some very tiny blobs, but they were disconnected from the main geometry and far away, so very easy to clean up in Blender. I have attached a screenshot showing this.
I did see one error in the Log during Texture map generation: "Failed to initialize context. Reason: VK Error: VkResult is "ERROR_INITIALIZATION_FAILED" at line 66". However, it seemed to have created the texture just fine despite this error message. I have uploaded a screenshot of that as well.
The last observation I have that it is now showing both [GPU1] and [GPU2] in the log. With 1.7.3 it only showed one GPU on my MacBook Pro M1 Max. In the Log you can see that it says "Found 1 GPUs", so I'm not sure why it's acting like there are 2. Is that normal?
This is the first version since 1.7.3 that I think I will be able to use, so thanks for the great work!
-Brian
I did see one error in the Log during Texture map generation: "Failed to initialize context. Reason: VK Error: VkResult is "ERROR_INITIALIZATION_FAILED" at line 66". However, it seemed to have created the texture just fine despite this error message. I have uploaded a screenshot of that as well.
The last observation I have that it is now showing both [GPU1] and [GPU2] in the log. With 1.7.3 it only showed one GPU on my MacBook Pro M1 Max. In the Log you can see that it says "Found 1 GPUs", so I'm not sure why it's acting like there are 2. Is that normal?
This is the first version since 1.7.3 that I think I will be able to use, so thanks for the great work!
-Brian
39
General / Re: Dense cloud filter by confidence question
« on: November 30, 2021, 01:41:37 AM »
I've always had the "Calculate point confidence" option on, but I had assumed that Metashape automatically did something with those values. Now that I read that article I see that it's only useful if I'm going to manually remove points with low confidence. Is that correct?
Does having the Calculate Point Confidence option on add much time to the processing, or is it essentially free anyways?
Does having the Calculate Point Confidence option on add much time to the processing, or is it essentially free anyways?
40
Bug Reports / Re: Still experiencing random system freezes on Mac
« on: November 30, 2021, 12:04:54 AM »
Now that I've had more time with this I've concluded that the freezing is actually quite common, especially on any Chunk with more than 60 photos in it. I'm really disappointed that this is still happening on my brand new Mac. I figured it was happening before because I was running a 2013 Mac Pro with almost no VRAM or RAM. With this new MacBook Pro with 64 gigs of RAM I had hoped this would stop happening. Very, very frustrating.
-Brian
-Brian
41
Bug Reports / Re: Still experiencing random system freezes on Mac
« on: November 23, 2021, 12:28:33 AM »
One observation is that if I'm using a GPU / VRAM intensive program in the background while Metashape is building the depth maps (like Blender) it seems to increase the failure rate to about 1 in 3. In other words: quite often. It completely freezes the MacBook Pro when this happens.
42
Bug Reports / Still experiencing random system freezes on Mac
« on: November 22, 2021, 09:40:20 PM »
A while back I reported a problem I was having on my old 2013 Mac Pro where Metashape would cause my entire Mac to completely freeze and I had to do a force reboot. This would happen about 60% of the time it would do a depth map generation pass. I was told that it was probably because of the low VRAM on that machine, so I should try reducing the tile size to 512 with a parameter tweak and see what happened. That reduced the system freezing to about 5% which was a much more tolerable occurrence.
Now, on my new MacBook Pro with 64Gigs of RAM/VRAM I still get the occasional system freezes during Depth Map generation. I'm back to using the default 2048 tile size, but it still happens around 1 in 40 times, so rare, but still every week.
This is with Metashape 1.7.3. I can't use the later versions because 1.7.3 is the last version that builds meshes from Depth Maps properly.
-Brian
Now, on my new MacBook Pro with 64Gigs of RAM/VRAM I still get the occasional system freezes during Depth Map generation. I'm back to using the default 2048 tile size, but it still happens around 1 in 40 times, so rare, but still every week.
This is with Metashape 1.7.3. I can't use the later versions because 1.7.3 is the last version that builds meshes from Depth Maps properly.
-Brian
43
General / Re: Disappointing performance results on new MacBook Pro M1 Max
« on: November 14, 2021, 04:23:45 PM »
It probably all depends on what you're comparing it to. Compared to my old 2014 MacBook Pro it's *lightning* fast. I couldn't run Metashape on that old MacBook Pro at all it was so slow. But compared to my 2013 Mac Pro it's not significantly faster which surprised me. The CPU intensive stuff is definitely faster, but since 95% of what Metashape does is on the GPU and that's only a tiny bit faster than what's on my old Mac Pro there isn't a huge overall gain.
44
General / Re: Disappointing performance results on new MacBook Pro M1 Max
« on: November 11, 2021, 01:55:34 PM »
That’s the version I tested, but I have to use 1.7.3 because it’s the last version that correctly build meshes from depth maps. Ends up the non-native versions like 1.7.3 run about the same speed as the native 1.8. Most of the work is done on the GPU and Rosetta 2 does a great job of converting the CPU code.
45
General / Re: Disappointing performance results on new MacBook Pro M1 Max
« on: November 04, 2021, 07:42:32 PM »
I still get the blobs using that version on my M1 Max. Therefore, I’m still using the old version before all of that broke.
