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.


Messages - ilia

Pages: [1] 2 3 4
1
General / Re: Circular bands in texture
« on: March 21, 2024, 06:21:42 PM »
Sorry, wrong report.
For me the latest version 17803 actually solved this problem.

2
Alexey,

Sorry, when I was downloading the new version I accidently downloaded Standart one. So when I run professional one it was still the old one.
Now with 17803 build I have it resolved without such artifacts.

3
General / Re: Circular bands in texture
« on: March 21, 2024, 04:47:31 PM »
Alexey, sorry to copypasting it from another topic, but I think it makes sense to gather all this information in this one:

I think the problem is still here even with 2.1.1 version.
I've tried to run it again with and I see blurred stripes on the texture. I'm attaching screenshot of the same module textured with the same camera with CPU and with GPU.

Driver 555.61.
As a I guess: This driver comes with 12.4, but I have other CUDA versions in my path. Can it be related somehow?

4
Hi Alexey,

I think the problem is still here even with 2.1.1 version.
I've tried to run it again with and I see blurred stripes on the texture. I'm attaching screenshot of the same module textured with the same camera with CPU and with GPU.

Driver 555.61.
As a I guess: This driver comes with 12.4, but I have other CUDA versions in my path. Can it be related somehow?

5
Latest update -- no problems if switch off GPU texturing and use CPU for texturing.

6
Bug Reports / Re: FBX export ultra slow on Windows !!
« on: February 12, 2024, 08:02:03 PM »
Alexey,

A couple notes regarding 2.1.1 version you provided. Sorry to bring it less related to this thread. I tried 2.1.1 to also see if I can get any improvements for this problem:
https://www.agisoft.com/forum/index.php?topic=16226.0


And I've noticed one regression related to multirig setup.

1. I can't activate just a single slave camera from a rig and use it like that for texturing. Metashape now says "No cameras".
2. If I using Python API unselect "master" camera from a rig it by cam.enabled = False used for master camera cam it automatically disables all slave cameras also. Which didn't happen in 2.0.3 I used before.


7
Bug Reports / Re: FBX export ultra slow on Windows !!
« on: February 12, 2024, 05:16:09 PM »
Hi Alexey,

I just tested it on one of models I have next to me. For 31 mln. faces model it took:
a) 23 mins on 2.0.3 version
b) 2.3 mins on 2.1.1 version you just provided.

Seems like 10 times speed up on my machine. Nice work! Thank you!

8
And the latest observation -- I did the same project but without cameras being locked down in a rig and everything went good. Mesh was slightly worse (due relaxed constrains I guess), but no issues with texturing.

9
This getting stranger and stranger.

I select using Python commands just a single image in two rigs. And as the result I see the attached image, where some part of the mesh is textured despite the fact that is is behind both cameras which are on.
Another thing (attached images v2 and v3) is that somehow black area of non-visible part of the mesh cripples into nicely visible part and getting mixed with it. This is the second image I attaching to this post.

So it leaves a blurred stripes as on this column. I'm also attaching the two screenshots showing a single active images from two rigs to show what is visible and what is not.

Metashape version: 2.0.3, build 16960, x64 Win.

10
Hi,

I have a quite weird issue related to multicamera system. I was using a camera with 6 synced modules. Meshing went really well, but textures had visible artifacts. I've tried to narrow down by simplifying the mesh and throwing away more and more cameras and ended up with a single multicamera, simple mesh and the same issue.

One of slave cameras despite having a proper relative orientation estimation to master camera doesn't provide nice textures for part of its view. Some polygons in the view of this slave camera are properly textured (and for texturing this slave camera is used as no other cameras see these polygons), but other polygons just have a weird splat of single color.

Here is the project uploaded to GDrive with the data:
https://drive.google.com/drive/folders/1iV6ubNF6bi8TzZXByRm-VK4u4704lhds?usp=sharing

I suspect here a gimbal lock issue. Two angles of slave offset angles for this camera are close to 180.

I will try to roll this camera data 180 degrees to see if the problem disappear. This didn't help.

Metashape 2.0.3, also tested with 2.1.1 and got the same issues. Windows 10, RTX 4090, driver  536.99.

11
General / Re: Metashape Pro Crashing During Image Alignment
« on: February 09, 2024, 09:20:31 PM »
The folder is empty :(
 I hope, next time I will save it properly.

12
Camera Calibration / Re: A better way to calibrate cameras
« on: February 09, 2024, 09:15:56 PM »
Potential solution would be to place markers and in a room, if needed -- measure distances between them. And shot several images covering as much as possible.

13
General / Re: Metashape Pro Crashing During Image Alignment
« on: February 04, 2024, 04:30:04 PM »
I had crashes in alignment stage with Ryzen 5950X CPU.
It happened always when I've tried to reset some alignments or redo some alignments. Is there any chance that I can find these reports stored on the machine? I didn't click "send".

14
Camera Calibration / Re: A better way to calibrate cameras
« on: February 04, 2024, 04:22:57 PM »
PTGui for an examle do not estimate lever arm between optical centers, which is usual case for many panoramic cameras or rig setups.
But maybe I'm missing the idea here. May I ask you to rephrase it? Like what is the idea and why it would be better than any other calibrations setups using targets?

15
Hi

I have a project which is challenging to get matched together properly. I use NN masks to hide some objects, some time more agressively (like trees or bushes). Sometimes I build a mesh and use it as a source for masks to avoid matching points on a water for an example.

In this iterations sometimes I would like to clean up mask and rematch images using more keypoints (I apply "mask keypoints option" with alignment). But I don't see anywhere we I can reset keypoints for the image and have it recomputed if I updated masks to have them less conservative. If I reset alignment it still leaves keypoints stored for these photos (this setting is one and useful most of the time for my projects). But sometimes I want to enforce recomputing key points even with having this option on.

I've tried to look for Python API and it seems that it is not possible also to clean up keypoints for specific set of images or reset their alignment on the lower level, consider them in the project as the ones without keypoints to recalculate them.

May I ask you how to do that? Only one option I have in mind is exporting project, cleaning up keypoints for some photos and importing it back.

Pages: [1] 2 3 4