Forum Agisoft Metashape

Hello Tom, Thank you for additional information. We will fix the issue in the next version update (definitely in next 2.4.0 update, and hopefully also in 2.3.3). Meanwhile for rather small models (few millions of faces) you may consider disabling the use of GPU and run Tools Menu ->gt Model ->gt Colorize Vertices command using CPU only over already generated mesh model (in such case keep Calculate Vertex Colors option disabled in Build Model dialog

For the Drone mission planning tool (Tools/Plan Mission) I would like to limit the maximum altitude, the same way minimum altitude limit is now implemented. I am often doing surveys of large mountain cliffs for geological research, and sometimes my flight height runs into the hardware limitation of the drone. In my experience the mission planning tool tends to design the survey to fly higher than the designated area of interest, even if I limit the camera pitch to 0°. Being able to set the maximal elevation limit would solve this issue. I expect that this would not be to difficult to implement, so fingers crossed! Best regards, Marko

Yes, fisheye equisolid is correct.

Hello Tom, Thank you for sharing the sample data. Can you please confirm that selected Fisheye Equisolid option is correct for the camera used?

I would add that I see the same failure on other similarly structured projects, which were colored properly by version 2.2

The source images for this project are in 4 directories, and 4 calibration groups, nbsp corresponding to the 4 cameras of the capture rig. nbsp Disabled all but the first image in each group =>gt black mesh with gpu enabled and a colored one with gpu disabled. Same result with only the first 4 photos in one directory enabled. I made a low-res model from those 4 photos. nbsp It colorized properly on cpu but was black on gpu. nbsp Saved with only 4 depth maps and the model as '#039cucumber-test-minimal.psz'#039. nbsp The project and the 4 photos are available for download via these links https://drive.google.com/file/d/1-L5mkc-H0EwWk9kBmHhb7o62nBIPDkDN/view?usp=drive_link , https://drive.google.com/file/d/1XsB0mx9dPBDUnnR49-2NIiO8NR8A3Gp-/view?usp=drive_link , https://drive.google.com/file/d/1cvp6mfSVX5H47Evwr86Wm5r93EccXJiA/view?usp=drive_link , https://drive.google.com/file/d/1gXBX2QXv6klzae03jxxTKvUEwUASEbTF/view?usp=drive_link , https://drive.google.com/file/d/1yRMoIIHxc5HNa1a2O1DYqFhvB1yuOhjg/view?usp=drive_

Hello Tom, Have you checked, if the same small project worked when only CPU is used (GPU disabled in Metashape Preferences window)? You can disable all but two images in the chunk and try same operation again, if it also gives black result (as it likely would), can you send the project saved in PSZ format that contains only camera alignment and low-res model and any couple of images from the set to support@agisoft.com via file transfer service?

Hello Tom, Have you checked, if the same small project worked when only CPU is used (GPU disabled in Metashape Preferences window)? You can disable all but two images in the chunk and try same operation again, if it also gives black result (as it likely would), can you send the project saved in PSZ format that contains only camera alignment and low-res model and any couple of images from the set to support@agisoft.com via file transfer service?

Quote from: Paulo on Today at 02:07:03 AM I got same error in Classifying with training in latest release 2.4.0 build 23256 (64 bit) Hello Paul, Fix was not included in 23256, it was prepared before fix has been committed to pre-release.

I got bored and got ChatGPT to puke out a batch file to do what'#039s needed. See here: https://www.agisoft.com/forum/index.php?topic=17608.0</a

Want to test new versions/builds? nbspnbsp But can'#039#039t disturb your production used version? nbspnbsp Now you easily can! This has always been possible... But an annoying, manual task copying/renaming folders in the Program Files folder. So i created a batch file to automate copying builds into their own folders. This tool copies you Metashape Std/Pro installation(s) to another folder that includes the version and build in the name. It also creates same named shortcuts in the start menu, nbspnbsp too. (Which looks great when using Open-Shell, but shite on Microslop'#039#039s Start Menu) This allows you to have many, many versions/builds installed at the same time. To do this, start with the oldest builds first, run the tool, then the next, run the tool, etc... Then install any new pre-release versions, as they'#039#039re

Hi Alexey, I got same error in Classifying with training in latest release 2.4.0 build 23256 (64 bit)