Messages

1

Bug Reports / Error when doing the natural texture - Version 2.3.1 build 22416

« on: May 09, 2026, 04:17:52 PM »

Hi,

I'm reporting an error that i'm getting when using the natural settings in the texture mesh:

Error: getDevice().waitForFences(vk::Fence(*fence), true, getTimeoutNanosecs()): Timeout (2) with code 453151251236 at line 1308



small part of the log:

Code: [Select]

loaded mesh in 0.874 sec
preparing model...
loaded mesh in 0.882 sec
4071547 vertices, 8123530 faces
done in 1.074 sec
downscales: x2 images, additional x2 for depth
640/640 checked: 1 cases = 640 (3xuint8)
most popular type: 3xuint8
640/640 cameras left after 0 cameras were filtered w.r.t. type and layout
1 resolutions: 5456x3632 (640 cameras)
creating 1 temp image dirs for 640 keys...
4071547 vertices, 8123530 faces, 4096 atlas size (2x2047)
estimated vram usages: 321.32 MB 462.55 MB 437.15 MB 842.45 MB
required available vram: 936.06 MB
Found 1 GPUs in 0.002 sec (OpenCL: 0 sec, Vulkan: 0.002 sec)
Using device: AMD Radeon RX 7900 XTX, free memory: 23748/24560 MB, Vulkan API 1.4.344, driver version: 2.0.388
1 enabled GPUs found with Vulkan support and enough VRAM
CPU fallback found:
Using device: CPU AMD Ryzen 9 5950X 16-Core Processor llvmpipe (LLVM 12.0.1, 256 bits), free memory: 49950/65446 MB, Vulkan API 1.4.318, driver version: 25.2.7
Peak memory used: 332.80 MB at 2026-05-09 08:37:52
7 images preparing subtasks scheduled
Peak memory used: 16.00 KB at 2026-05-09 08:37:52
preparing 92 images (group #1/7)...
done in 92.852 sec
Peak memory used: 5.22 GB at 2026-05-09 08:38:02
preparing 92 images (group #2/7)...
done in 91.995 sec
Peak memory used: 5.38 GB at 2026-05-09 08:39:33
preparing 92 images (group #3/7)...
done in 92.034 sec
Peak memory used: 5.15 GB at 2026-05-09 08:41:05
preparing 92 images (group #4/7)...
done in 92.916 sec
Peak memory used: 5.09 GB at 2026-05-09 08:42:40
preparing 92 images (group #5/7)...
done in 92.531 sec
Peak memory used: 5.32 GB at 2026-05-09 08:44:12
preparing 92 images (group #6/7)...
done in 92.644 sec
Peak memory used: 5.26 GB at 2026-05-09 08:45:46
preparing 88 images (group #7/7)...
done in 88.681 sec
Peak memory used: 4.87 GB at 2026-05-09 08:47:17
7 faces resolution subtasks scheduled
Peak memory used: 16.00 KB at 2026-05-09 08:48:37
loading model...
4071547 vertices, 8123530 faces
model loaded in 0.196 sec
estimating faces resolution from 92 cameras (group #1/7)...
expected vram usage: 437.15 MB
Found 1 GPUs in 0.002 sec (OpenCL: 0 sec, Vulkan: 0.002 sec)
Using device: AMD Radeon RX 7900 XTX, free memory: 23748/24560 MB, Vulkan API 1.4.344, driver version: 2.0.388
Using device: CPU AMD Ryzen 9 5950X 16-Core Processor llvmpipe (LLVM 12.0.1, 256 bits), free memory: 51181/65446 MB, Vulkan API 1.4.318, driver version: 25.2.7
using 31/32 cpu threads

[#1 GPU] using AMD Radeon RX 7900 XTX - processed 22 cameras in 127.669 sec, kernels exec 0 sec (0% baking + 0% fences), speckles filtering 4.959 sec (2.165 sec CPU)
[#2 GPU] using CPU AMD Ryzen 9 5950X 16-Core Processor llvmpipe (LLVM 12.0.1, 256 bits) - processed 0 cameras in 0 sec, kernels exec 0 sec (0% baking + 0% fences), speckles filtering 87.238 sec (0.317 sec CPU)
Error: getDevice().waitForFences(vk::Fence(*fence), true, getTimeoutNanosecs()): Timeout (2) with code 453151251236 at line 1308

After version 2.2.3 (21752), i was never successful of doing the Natural Texture in agisoft. In the previous version Version (2.3.0 build 21868), my pc every single time would randomly restart doing the natural texture and now in this new version (Version 2.3.1 build 22416), i'm getting the error above!

And its SO SLOW in the versions 2.3 and above. In 2.2.3 the natural texsture was quick and perfect.


I can send anything that you guys need to analyse!

Thank you and long live AGISOFT!


EDIT. i unchecked (in the GPU tab) the CPU and looks everything is working fast and good now.

2

Bug Reports / Re: Automatic Ground Classification issue in version 2.0.0 and 2.0.1

« on: March 17, 2023, 07:49:56 PM »

same here just did a ground classification on v. 2.0.1 and low points are wrongly classified (under roofs or over hangs, along walls). Definitely this did not occur with 1.8...

I'm getting the same problem.

Lets hope they found a fix.

3

Bug Reports / Re: Agisoft 2.0: Reason: VK Error : VkResult is "ERROR_TOO_MANY_OBJECTS" at line 12

« on: January 12, 2023, 05:34:41 PM »

Hello JM,

Thank you for additional information regarding the texturing issue, we will try to reproduce it on our side on a similar configuration and analyze the problem.

As for your question about GPU initialization line output, for OpenCL devices Metashape gets the "compute units" number from the driver reply upon CL_​DEVICE_​MAX_​COMPUTE_​UNITS call. It seems that for modern ADM graphic cards with RDNA architecture the command returns number of WGP (so-called "workgroup processors") which are actually dual compute units.
Additional information on this matter can be found here:
https://www.amd.com/system/files/documents/rdna-whitepaper.pdf
https://en.wikipedia.org/wiki/RDNA_(microarchitecture)#Differences_between_GCN_and_RDNA

However, Metashape is not relying on this output, the task of parallel computations on all available compute units is performed by GPU driver. You can check GPU load using dedicated utilities, such as GPU-Z, for example.

Alex thank you for the explication.

Regarding the 'Texturing' problem, if it reduce the pixel size from the original 0.0037561 to, for example pixel size = 0.006, i dont get constantly the error (just a 1 or 2 times).

Hope it helps!


best regards,
JM

4

Bug Reports / Re: Agisoft 2.0: Reason: VK Error : VkResult is "ERROR_TOO_MANY_OBJECTS" at line 12

« on: January 11, 2023, 08:21:49 PM »

Gonna use this thread to another problem:

[GPU 1] Using device: AMD Radeon RX 7900 XTX (gfx1100), 48 compute units, free memory: 24557/24560 MB, OpenCL 2.0

The 48 Compute Units are 'wrong' (?), It says 'Compute Units 96' https://www.techpowerup.com/gpu-specs/radeon-rx-7900-xtx.c3941


Could it be a bug?

edit. its because they are 2 chiplets with 48 in each one. But agisoft only saw 1 chip (48 cu) rather then the 2 chips (96 cu).

Any idea how to fix this, if possible?

5

Bug Reports / Re: Agisoft 2.0: Reason: VK Error : VkResult is "ERROR_TOO_MANY_OBJECTS" at line 12

« on: January 11, 2023, 12:03:37 AM »

Hello JM,

Can you please share the log from the beginning of Build Tiled Model task (or at least its texturing phase) and also the starting lines of Metashape from the Console pane?

Hi ALex,

Here it is the log

2023-01-10 18:31:26 Agisoft Metashape Professional Version: 2.0.0 build 15597 (64 bit)
2023-01-10 18:31:26 Platform: Windows
2023-01-10 18:31:26 CPU: AMD Ryzen 9 5900X 12-Core Processor
2023-01-10 18:31:26 CPU family: 25 model: 33 signature: A20F10h
2023-01-10 18:31:26 RAM: 63.9 GB
2023-01-10 18:31:26 OpenGL Vendor: ATI Technologies Inc.
2023-01-10 18:31:26 OpenGL Renderer: AMD Radeon RX 7900 XTX
2023-01-10 18:31:26 OpenGL Version: 4.6.0 Compatibility Profile Context 22.12.2.221216
2023-01-10 18:31:26 Maximum Texture Size: 16384
2023-01-10 18:31:26 Quad Buffered Stereo: not enabled
2023-01-10 18:31:26 ARB_vertex_buffer_object: supported
2023-01-10 18:31:26 ARB_texture_non_power_of_two: supported
2023-01-10 18:31:26 Using simple console. Rich console can be enabled in Preferences dialog.

2023-01-10 18:32:00 BuildTiledModel: source data = Depth maps, pixel size = 0.00375611, tile size = 256, face count = High, ghosting filter = 1, quality = Low, depth filtering = Moderate, PM version
2023-01-10 18:32:00 Generating depth maps...
2023-01-10 18:32:00 Preparing 1666 cameras info...
2023-01-10 18:32:00 cameras data loaded in 0.44 s
2023-01-10 18:32:01 cameras graph built in 0.726 s
2023-01-10 18:32:01 filtering neighbors with too low common points, threshold=50...
2023-01-10 18:32:01 avg neighbors before -> after filtering: 166.956 -> 21.4004 (87% filtered out)
2023-01-10 18:32:01 limiting neighbors to 16 best...
2023-01-10 18:32:02 avg neighbors before -> after filtering: 21.4004 -> 8.46098 (39% filtered out)
2023-01-10 18:32:02 neighbors number min/1%/10%/median/90%/99%/max: 1, 3, 7, median=16, 16, 16, 16
2023-01-10 18:32:02 cameras info prepared in 2.754 s
2023-01-10 18:32:03 saved cameras info in 0.023
2023-01-10 18:32:03 Partitioning 1666 cameras...
2023-01-10 18:32:03 number of mini clusters: 34
2023-01-10 18:32:03 34 groups: avg_ref=49 avg_neighb=43.5 total_io=189%
2023-01-10 18:32:03 max_ref=50 max_neighb=108 max_total=158
2023-01-10 18:32:03 cameras partitioned in 0.023 s
2023-01-10 18:32:03 saved depth map partition in 0.002 sec
2023-01-10 18:32:03 loaded cameras info in 0.055
2023-01-10 18:32:03 loaded depth map partition in 0 sec
2023-01-10 18:32:03 already partitioned (50<=50 ref cameras, 23<=200 neighb cameras)
2023-01-10 18:32:03 group 1/1: preparing 73 cameras images...
2023-01-10 18:32:03 tie points loaded in 0.007 s
2023-01-10 18:32:04 AMD Radeon RX 7900 XTX (gfx1100): no SPIR support
2023-01-10 18:32:04 Found 1 GPUs in 0.034 sec (CUDA: 0.024 sec, OpenCL: 0.01 sec)
2023-01-10 18:32:04 Using device: AMD Radeon RX 7900 XTX (gfx1100), 48 compute units, free memory: 24557/24560 MB, OpenCL 2.0
2023-01-10 18:32:04   driver version: 3504.0 (PAL,LC), platform version: OpenCL 2.1 AMD-APP (3504.0)
2023-01-10 18:32:04   max work group size 256
2023-01-10 18:32:04   max work item sizes [1024, 1024, 1024]
2023-01-10 18:32:04   max mem alloc size 20876 MB
2023-01-10 18:32:04   wavefront width 32
2023-01-10 18:32:04 Using device: CPU AMD Ryzen 9 5900X 12-Core Processor (using 19/24)
2023-01-10 18:32:04 Loading kernels for AMD Radeon RX 7900 XTX (gfx1100)...
2023-01-10 18:32:04 Kernel loaded in 0.002 seconds
2023-01-10 18:32:13 group 1/1: cameras images prepared in 10.566 s
2023-01-10 18:32:13 group 1/1: 73 x frame
2023-01-10 18:32:13 group 1/1: 73 x uint8
2023-01-10 18:32:13 group 1/1: expected peak VRAM usage: 123 MB (64 MB max alloc, 1368x1368 mipmap texture, 16 max neighbors)
2023-01-10 18:32:13 AMD Radeon RX 7900 XTX (gfx1100): no SPIR support
2023-01-10 18:32:13 Found 1 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2023-01-10 18:32:13 Using device: AMD Radeon RX 7900 XTX (gfx1100), 48 compute units, free memory: 24557/24560 MB, OpenCL 2.0
2023-01-10 18:32:13   driver version: 3504.0 (PAL,LC), platform version: OpenCL 2.1 AMD-APP (3504.0)
2023-01-10 18:32:13   max work group size 256
2023-01-10 18:32:13   max work item sizes [1024, 1024, 1024]
2023-01-10 18:32:13   max mem alloc size 20876 MB
2023-01-10 18:32:13   wavefront width 32

2023-01-10 20:35:16 Avg camera fetch time: 0.431827 sec
2023-01-10 20:35:16 Total stalled time: 47.913 sec
2023-01-10 20:35:16 Avg camera processing time: 0.0130877 sec
2023-01-10 20:35:18 Cannot use GPU. Reason: VK Error : VkResult is "ERROR_TOO_MANY_OBJECTS" at line 12
2023-01-10 20:35:18 Performing blending on CPU...
2023-01-10 20:35:18 rendering 5149 pages
2023-01-10 20:35:22 calculating mesh connectivity... done in 0.029 sec
2023-01-10 20:35:22 detecting outliers...

is it enough?

Its always the same problem in lowest, low, medium or high.

Thank you.


Best regards,
JM

6

Bug Reports / Agisoft 2.0: Reason: VK Error : VkResult is "ERROR_TOO_MANY_OBJECTS" at line 12

« on: January 05, 2023, 09:40:01 PM »

Hi,

So i'm getting the error following error doing texture blending in tiled model:

Cannot use GPU. Reason: VK Error : VkResult is "ERROR_TOO_MANY_OBJECTS" at line 12
Performing blending on CPU...

Currently using a 7900xtx with the latest drivers.


Any ideas why?


Best regards,
JM

7

Camera Calibration / Re: Rolling shutter

« on: July 31, 2022, 06:03:36 PM »

Any news regarding this?

https://www.agisoft.com/forum/index.php?topic=14671.msg64383#msg64383

Regularized model is suitable for the case when the drone flies without turning the camera, i.e. during the shooting to a new route, the camera does not turn and the drone moves in parallel.
When using a Regularized, only two parameters are optimized for each frame: axis shift XY in the plane of the photo. When using the Full model, 6 parameters are optimized for each frame: shift along the XYZ axes and rotation along the XYZ axes.

Thank you for the explanation. Perfect!

8

Camera Calibration / Re: Rolling shutter

« on: July 30, 2022, 06:39:41 PM »

Any news regarding this?

9

Bug Reports / Re: Bad Texture Blending (1.8.3 vs 1.7.5)

« on: June 19, 2022, 06:06:57 PM »

Hello JM,

Can you send the mesh models exported with UV parametrization from both version projects to support@agisoft.com?

Sure, Alexey.


Thank you for the reply.

10

Bug Reports / Bad Texture Blending (1.8.3 vs 1.7.5)

« on: June 16, 2022, 12:03:41 PM »

Hi!

So i'm having some wierd bugs with texture blending in the latest version (1.8.3), only in some parts of the model, as you can see in the attachments. This doesnt happen in the 1.7.5 version.

Any ideas what could this be? A bug?


Its a 3D project (church) with around 1600 photos from various angles.


Thank you for the best photogrammetry software ever! 

Best regards,
JM