Forum

Author Topic: Agisoft Metashape 2.2.0 pre-release  (Read 32228 times)

dcobra

  • Jr. Member
  • **
  • Posts: 59
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #45 on: November 29, 2024, 03:57:06 PM »
When I start a worker in network mode the Agisoft startup screen is displayed but never disappears. It remains on the screen in front of everything making it difficult to see anything. It says Loading geoids... Is this expected behavior?

dcobra

  • Jr. Member
  • **
  • Posts: 59
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #46 on: December 02, 2024, 12:15:28 AM »
.
« Last Edit: December 02, 2024, 02:00:28 AM by dcobra »

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #47 on: December 02, 2024, 12:01:29 PM »
Hello dcobra,

Thank you for reporting.

We will fix it in the next update, as the splash screen should not show up, when Metashape is stated in network worker mode.
Best regards,
Alexey Pasumansky,
Agisoft LLC

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #48 on: December 02, 2024, 12:34:15 PM »
I have two display adapters in my computer, an AMD Radeon RX 6600 XT and an NVIDIA GeForce RTX 3050. In Metashape Preferences it list the AMD Radeon RX 6600 XT twice, one Vulkan and the other OpenCL. By default the OpenCL one is checked. Is this the prefered settings, and what is the difference?

Hello bisenberger,

The issue with AMD graphic card doubling in Preferences would be fixed in the next 2.2.0 pre-release update.

As for the Vulkan checkbox, you can check it on, but in the current version it does not have any effect. Later it would have meaning for GPU-based texturing and vertex colorization procedure.
Best regards,
Alexey Pasumansky,
Agisoft LLC

JMR

  • Hero Member
  • *****
  • Posts: 528
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #49 on: December 03, 2024, 10:47:03 PM »
Point cloud export problems:
I have a dense cloud colored in my project.
Exported with colors in LAS gives no colors
Exported with colors in LAZ gives wrong colors
Exportes with colors in E57 coes out slightly trimmed
Exported with color as PLY and no program seems able to open, even metashape crashes.

Saving the project as psz 1.8  gives an error I've never seen before



Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #50 on: December 04, 2024, 03:43:40 PM »
Hello José,

Was the point cloud generated in Metashape based on images or was it imported from another source as a laser scan?
Best regards,
Alexey Pasumansky,
Agisoft LLC

JMR

  • Hero Member
  • *****
  • Posts: 528
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #51 on: December 04, 2024, 07:23:48 PM »
Hello José,

Was the point cloud generated in Metashape based on images or was it imported from another source as a laser scan?
Hi Alexey
5 oriented scans plus 3 panoramic images aligned. All good,
Merded scans into one point cloud and then colorised. All good
export point cloud packed as potree zip, all good.
export as LAS no color
export as LAZ no color
export as E57. color is fine but there is a part of the cloud missing.
Thanks

JMR

  • Hero Member
  • *****
  • Posts: 528
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #52 on: December 04, 2024, 08:19:24 PM »
weird clipping to boundary shape with the beta:


Same operation with 2.1.2


Regards
Geobit

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #53 on: December 05, 2024, 03:56:53 PM »
Hello José,

The issue with the point cloud export should be fixed in the next 2.2.0 update.

As for the orthomosaic clipping by boundary - we are not yet able to reproduce the problem. Do you observe it in any project?
How the original (not clipped) orthomosaic looks like, what is the source image format and bit depth? Any additional information related to the project specifics might be helpful.
Best regards,
Alexey Pasumansky,
Agisoft LLC

JMR

  • Hero Member
  • *****
  • Posts: 528
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #54 on: December 05, 2024, 09:57:26 PM »
As for the orthomosaic clipping by boundary - we are not yet able to reproduce the problem. Do you observe it in any project?
How the original (not clipped) orthomosaic looks like, what is the source image format and bit depth? Any additional information related to the project specifics might be helpful.
Hello Alexey. Believe it or not, now I cannot get the orthomasaic madness to occur again.
the not clipped one is this:

I created a dupicate applying clipping and duplicating orthophotos, and got the one I sent yesterday with the blocky blacked out areas. By doing the very same today, the black thing never comes up. ??? why on earth? so for the moment, you can forget the weird issue.
Thanks for your support,

Geobit


avolodin

  • Newbie
  • *
  • Posts: 6
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #55 on: December 10, 2024, 01:24:50 PM »
Metashape 2.1.3 BSODed our windows machine on our pipelines regularly so we had to downgrade to 2.0.4. Does Metashape 2.2.0 contain any improvements/fixes for camera alignment or camera optimizations? Otherwise we would love to stay on 2.0.4

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #56 on: December 10, 2024, 02:36:19 PM »
Metashape 2.1.3 BSODed our windows machine on our pipelines regularly so we had to downgrade to 2.0.4. Does Metashape 2.2.0 contain any improvements/fixes for camera alignment or camera optimizations? Otherwise we would love to stay on 2.0.4

What OS version and CPU you are using? BSOD is usually an indication of hardware problems.

If you have 13900K or 14900K CPU series, check the possible solutions in the following thread to avoid hard crashes: https://www.agisoft.com/forum/index.php?topic=15903.30
Best regards,
Alexey Pasumansky,
Agisoft LLC

jeffreyianwilson

  • Newbie
  • *
  • Posts: 37
  • Technical Director at Rendered.AI
    • View Profile
    • Portfolio Webpage
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #57 on: December 12, 2024, 04:35:08 PM »
Hi

I'd like to report crashes when trying to open depth map with Navvis VLX e57 as well as crashes with alignment of the same scan.  There are no issues with the same e57 file in MS Pro 2.1

Here is a link to the e57 file: https://1drv.ms/u/s!Apf7aUOlxOfskYRWQ1-Gd5MLi3GjLA?e=SwTLLW

Jeff
« Last Edit: December 12, 2024, 04:36:51 PM by jeffreyianwilson »
Jeffrey Ian Wilson
Technical Director / Program Manager
3D Scanning Masterclass
https://jeffreyianwilson.com

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #58 on: December 12, 2024, 08:13:26 PM »
Hello Jeff,

Thank you for reporting and sending the example. We were able to reproduce the issue - problem will be resolved in the next 2.2.0 update.
Best regards,
Alexey Pasumansky,
Agisoft LLC

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 15246
    • View Profile
Re: Agisoft Metashape 2.2.0 pre-release
« Reply #59 on: December 16, 2024, 12:25:44 PM »
Saving animation video as mp4 H-264 ends wih a crash. (Catastrophic error)

Hello José,

Can you please specify the OS version that you are using and the capture video parameters: resolution of the output video, track length in seconds, frame rate?

Win11pro 24H2, AMD Ryzen 9 9950X, 65gb ram, 2x RTX4080super.
Video length 30s
Framerate 60fps, 4K

Thanks

Hello José,

Do you have a kind of "Error: Can't write video: Catastrophic failure (0x8000FFFF)" message? If so, please check that there is sufficient disk space on the target drive. Such problem is usually observed, when there is not enough disk space in the output location.
Best regards,
Alexey Pasumansky,
Agisoft LLC