Topics

1

Feature Requests / Lock out interface rearrange when using intelligent scissors?

« on: January 02, 2023, 07:18:58 PM »

Hi, could we have the option or default behavior of the masking tools be that you cannot resize or rearrange windows in the workspace while using those tools? I consistently move my windows around when using the intelligent scissors and I find that genuinely annoying. Many thanks for reading.

2

Feature Requests / Mesh name display in viewport

« on: December 10, 2022, 06:16:26 PM »

Hi simple request,

Could we have either the option or the default behavior of the viewport that it displays the mesh's name above, below, before, or after, the triangle and vertice count?

Would be helpful when flipping between meshes with same triangle count but have other processing changes. Thanks.

3

Bug Reports / Baked textures softer in 1.85 than 1.84?

« on: September 19, 2022, 03:54:23 PM »

https://i.ibb.co/xmLD45p/softness.jpg

Opened an older 1.84 project to test 1.85 version, found that with the same settings (exception being enabling hole filing on 1.85 but I checked and that isn't the issue) and hardware, the texture bake came out a bit softer.

Duplicated mesh with custom UVs, textured from images, ghosting filter enabled, 16k map, mosaic blending.

4

Feature Requests / Texture transfer baker ray distance increase?

« on: August 30, 2022, 03:16:18 PM »

Hello, previously I was using Substance Designer for transfering a texture but decided to try Metashape as it can handle 16k. I noticed however that the ray distance is shorter than in designer, leading to the twigs on my mesh, which are the furthest points from my bake plane, to be partially black.


https://ibb.co/W3HvpC0
Left is substance designer, right is Metashape

Could we get a ray distance slider perhaps? Thank you.

5

Feature Requests / UDIM texture export naming should follow the common numbering

« on: August 11, 2022, 07:31:16 PM »

UDIM texture export naming should follow number name scheme, such as texture.1001.jpg, texture.1002.jpg, instead of texture.jpg, texture1.jpg as it is now.

6

Feature Requests / Camera enable/disable visibility filter for Photos window

« on: January 16, 2022, 08:35:34 PM »

Hello,

Would like to request the feature to filter out disabled photos from the Photos window.

A simple button, like the show masks, show depthmaps, etc, that just toggles visibility in Photo window of disabled photos. It should not affect the photo list displayed in the workspace window.

I can sort by enabled/disabled if I use the details view, but when filtering photos by marker, the sorting on the details view of Photo window does not respect enabled/disabled sorting if you have different folder paths for your images, so that is why I ask for this new feature.

Thank you.

Attachment shows sorting by enabled/disabled not working correctly when filtered by marker

7

Feature Requests / Several camera selection and masking ideas for improved texture generation

« on: December 14, 2021, 07:36:16 PM »

In order to capture complete texture information of a surface with highly varied surface depth, I have taken photos at extreme angles. This captures the missing data, but introduces unwanted blur if I do not use masks...

I leave these photos disabled, use just the planar photos for texturing, disable hole filing, and then mark the holes by hand, filter by each marker, and re-enable the extremely angled photos that capture those side and underside surfaces, and then mask out everything but the portion I need to fill the hole.

This works perfectly fine but is time consuming. This led me to wonder if it would be possible for Metashape to calculate the surface normal of each triangle/vertex, per camera, and their distance from the camera, and then enable the use of filter sliders and automatic masking.

One slider could filter cameras by distance from selected faces/points, to improve texture resolution by allowing easy disabling of user defined gradual selection of 'distant' cameras.

Another slider could instead mask selected cameras by face or marker selection, by the averaged or individual point normals to the camera angle. Metashape would first calculate the normal of every triangle, then calculate the 3D vector difference between the normal and the camera, to allow gradual removal by user defined amounts. This would mask all triangles/points per selected camera that have normal angles greater than a user defined angle.

A third slider could also mask points by distance from a selected camera, instead of disabling the entire camera. Highly useful for complex objects with variable height.

Here is an album illustrating what I am talking about, and I'm sorry I couldn't do better illustrations, and I was a bit hasty in coloring so this loosely represents the idea.
https://ibb.co/album/0CCt2p

The stack of magnets represent the surface normal, green is keep, red is mask, and yellow is when the surface normal angle is within the user's selected range, but has been also masked out, by distance from the camera.

If you wanted to get really fancy you could add an exception to allow excessive normal/camera angle differences only if there are no other suitable cameras. So instead of simply masking everything above a 90 degree angle for a photo, it would keep that camera's points/faces that exceeded that value if there was no view with a lower angle.

Vector math makes my brain go blank so I understand this isn't a trivial request, but you are all geniuses in my book. Metashape already has the best masking and filtering tools, this would make it the undisputed texturing champion. Thank you for reading.

Share your thoughts or suggestions! Perhaps some element of this is already a function of Metashape texturing algorithm?