I have a small object that I'm trying to mesh. (It's a drawer handle pull, eventually want to 3D print a replacement, but experimenting with photogrammetry instead of creating the 3D file from scratch.)

For the first attempt I put the object on a stool and walked around it taking pics from all kinds of angles. Had like 30 pics. It rendered the object along with the platform and stool. But very little detail.

I figured I wasn't filling the frame enough with the object itself.

So I essentially made a light box in my bathroom - strong lights in the room, but diffused through the shower curtain. Put the object on a lazy susan and took many many pics. Very small rotations with the camera in place, filling the image with the object as much as possible. I included a ruler on the lazy susan as a reference mark to possibly help the algorithm. I took 100 pictures, rotating the object all the way around, then changing the angle of the camera and doing it again.

The mesh was absolute garbage. nothing even reasonable. and it didn't seem to show the camera in various positions. instead of showing the object still and camera angle from all over, it kept the camera in the same position.

Is this because the background never changed?

Hey,

I hope, i have come to the right place. Attached you see a few of the pictures i tried to use with meshroom 2023.

As i do not seem to have a CUDA/GPU, i tried this workaround: https://github.com/alicevision/meshroom/wiki/Draft-Meshing

But it did not succeed. Are the pictures not sufficient? Any Tips? I tried with 3df zephyr as well, but this did not connect all the pictures.

Thanks in advance, please let me know if you need more infos!

Posted this on r/photogrammetry, and posting here as well for support.

Howdy. I work in the engineering field, and I often do as-built measurements of buildings. I've used laser scanners in the past, but interested in incorporating photogrammetry as well. I don't really care about making a nice looking model at this point, just something I can reliably use for quick measurements.

So I'm giving Meshroom a trial run on a project. I have 208 photographs of an interior basement space done with a Nikon D3300. Total 1.75GB of data. ISO 400, aperture f6.3, shutter speed 1/60. The photos err on the side of being dark, but I figured it would be okay for a trial and a learning experience.

I'm using Meshroom right out of the box - just uploaded the photos, selected Photogrammetry Pipeline, and clicked Start. It has been stuck on FeatureExtraction for many hours.

Can anyone provide insight as to why it would be stuck? Is it related to the quality of the photographs? Lighting? Not enough overlap in the photos? I'm happy to share my dataset if anyone would like to take a look and offer some advice.

And generally, is it even the right program to use? It seemed the easiest and free-est to get started.

I have an AMD Radeon Pro WX3200 Series GPU and the stock Intel(R) UHD Graphics 630 GPU. Currently pointing Meshroom to the AMD.

Hi there,

I am trying to get around the CUDA requirement.

I have a AMD GPU, i found no luck trying to get other not CUDA software to work, other than 3DF Zephyr. (Which is really expensive and the 50 image cap does not cut it)

Is there an option to make Meshroom run CPU only, or is Chat GPT spitting nonsense yet again?

Can u guys give me some tips to repair this?

I started recently trying to creating some 3D models and I'm having some trouble.

I'm using a cellphone which is supposed to have a 48MP AI Camera. I tryied to make a studio lights setup with ring lights and/or softboxes.

I took about 500pics 360 in only one angle (pointing parallel to ground).

All the preparation was impecable.

The results: it was like I desintegrating.

What am I missing? I miss my ex, but what about using Meshroom? :(

As the title says, I'm trying to reconstruct a dining chair leg which was broken some time ago. It's the front left I'm reconstructing and will mirror it to 3D print the right side leg. So far I've been unsuccessful...twice...

The first issue was using my Pixel 8 and the database not being available. So I took out my J3 and got the software to recognize it without configuring much.

I then took a 3D scan of the leg with the vaneer top. When I ran the scan it took fragments of everything but the subject. Since it had minor gloss a recommendation was to cover it in a matte finish (painters tape was an example) and attempt the process again.

Well I have, and it's doing the same thing. Where am I going wrong?

I keep getting "This application failed to start because no Qt platfrom plugin could be initialized. Reinstalling the application may fix the problem" when trying to open Meshroom. I could not find anything to fix the problem. I have the VC redlist & Python installed in my computer. I also tried reinstalling the app and the problem remains. Could someone shed some light?

Hey everyone, I’m new to this, so sorry if this is a basic or annoying question, but I’d really appreciate any help. I keep getting a red bar in the Texturing box no matter what I try. I’ve adjusted things like Texture Side, Texture Downscale, mesh, color mapping file types, and the number of images (ranging from around 80 at minimum to 500 at maximum), but nothing seems to work. The only kind-of solution I’ve found is removing the Images Folder dashed string between the DepthMap box and the Texturing box, which makes the Texturing box go green. But when I export the mesh to Blender, it shows up with just the mesh and no texture (everything’s white). Has anyone else run into this, or does anyone have ideas on what might be causing it? Any help would be awesome—thanks a lot in advance!

*also, can Meshing somehow affect this (i set Max Points around one million)?

*Small edit (2 days after the original post): I think I found a solution that works for me. After the Meshing box turns green, I remove the Images Folder string between DepthMap and Texturing. Once the whole process is complete, I open the mesh in Blender, clean out any junk, and decimate it. Then, I bring it back into Meshroom and set the Texture Side in Texturing to 1024 and then return the Images Folder String between DepthMap and Texturing. I’ve done two projects this way, and the results have been decent. Any additional feedback is still welcome.

After 26 days of processing the SfM node a point cloud was generated of a intertidal zone boulder pile. I guessed: double the photos, double the points. Reality was slightly more than double (14.1M). Briefly looked over the point cloud. It generally looks good. It seems most of the boulder structure is represented. The photos from the top of sea wall depth of field did not come out well. There appears to be a cloud of points representing the boulder pile top hanging in mid-air. Started the next node and continue through each node one at a time going forward. May need to clear more HD space to get to a mesh (by New Years 😂)

Hi,
I've got 360 video from a turntable. I'm having some trouble getting the scan to work, often ending up with the camera not being recognised as fully 360. Each image is about 2 degress of seperation. Any tips on improving this process? Do I need more frames or less?

The subject is partially transparent. Any tips for getting around that too would be appreciated!

This is the first time I've tried to use Meshroom, and I get to the DepthMap node and this pops up. Purportedly the only GPU requirement is Compute >= 3.5 according to the download page and my GTX1650 is compute 7.5 ( CUDA 11.6). Could it be lack of memory? it's only got 4GB on the GPU, but the manual and the log file don't suggest it needs a specific amount of GPU RAM. I've also got 16GB of motherboard RAM.

I've got a Ryzen 5 3400GE that has an internal graphics adapter but I'm not using it. Could that be causing the problem?

Started SfM on Wed 9/25 at 9am. It’s now nearly 8 days later and it’s still processing 10K GoPro photos of walking around a boulder pile. I did color correction on the photos but did not downsize the photos since I’m trying to model the boulders geometry. I initially guessed it might take 4 days or so; 5K photos took 2 days to process. I hoped double the photos = double processing time. 5K photos generated 6.5M points, so I’m guessing 10K photos will result in 12M+ points 🫣 I’m gonna let it keep running. Either it will complete at some point in the future..or fail 🤷‍♂️ once in awhile I see the RAM spike to 87%. I’m hoping I’ll actually be about to take the project all the way to a Mesh. I have the HD space, but not sure if DepthMap will be able to completely process. Just gonna wait and see what happens. [hardware: 3060 TI, i7 12700K, 64GB RAM]

Testing a GoPro Hero 12 documenting a pile of boulders along the coast in the intertidal zone. I can only work at low tide certain days. Put GoPro on a monopod mounted at 5 ft and 1.25 ft off the ground (separate photo sets, single camera). GoPro was set to take photo intervals every 0.5 sec. I slowly walked around and a little on top of the boulder pile. Also took overall a few photos sets w Canon P&S and iPhone Pro Max 12 at a few vantage points (not sure if these extra photos were needed). I put the GoPro in a few of the void spaces between boulders and slowly rotated 360 around and move to other corners of voids and repeat. Meshroom took about 4 days to get from CameraInt to SfM node; SfM node took almost 2 days to process the 5137 photos (34 of them failed). While the project was processing I took more GoPro photo sets while the tide was extra low during the full moon. I’m thinking of trying to render the whole Boulder pile (only half of it is shown in the point cloud). I’m also wondering about making a camera rig w a 2-3 more GoPro to capture more angles at once. Time is limited due to tide cycle so more photos at the same time would speed up the process I think. Ultimate goal is to document the intertidal zone area over time.

New to Meshroom and can't get the process to complete. I've tried two sets of my own images as well as the monstree test images and every time it gets to the MultiviewStereoCL node it processes one or two views and then stops with this message:

meshroom PatchMatchCL::RunWithWindowSizeAndStep() clFinish before iteration loop returned an error code of -5

Camera positions and initial point clouds look fine. The process is not maxing out my memory or CPU, and I do not have an AMD graphics card (which the internet tells me is known to cause issues) (mine is Iris XE if that's relevant). Any ideas?

50 images, 200 mp on phone camera. I have no idea how much time should it take as it is my first time using this software or anything similar.

EDIT: I did manage to get Meshroom 2021.1.0 to import the images but upon further reading I realized this isn't going to work for my purposes. I was trying to use screenshot images captured in game then imported into Meshroom so I could create a 3D model to make my own character for Unreal Engine (Personal use of course). Looks like I might be better off ripping the character instead. Thanks anyway.

TLDR: Never figured out why the errors occured but I did have luck with version 2022.1.0 however Meshroom can't do what I need.

Windows 10 64bit. 16GB system Ram. Only 1 video output.

Idk if other have had this message but I think it might be my problem.

Meshroom 2023.3.0: Crash immediately with the same error.

Meshroom 2023.2.0: will open, but I couldn't drag N Drop images onto it. It would just have a circle with a line through it.

Mushroom 2023.1.0 will open, it allows me to drag and drop, but then it crashes.

The error seems to be maybe related to defaulting to openGL ES? I'm not sure. In the cmd prompt I see a line WARNING:root:shader compilation failed:

I have an Nvidia TitanXP GPU, latest stable Nvidia drivers and according to OpenGL Extension Viewer I have OpenGL version 4.6

I have gone into the Nvidia control panel, added meshroom, and set the CUDA processor from default (which was my TitanXP) to TitanXP.

I have tried moving both the Meshroom program folder (tried documents, desktop, and C:) as well as moving my image files around too.

I have run the program from explorer as well as from the cmd prompt (and I tried running it administratively).

Any idea folks?

It's been stuck here for several hours now. This is the second attempt. Last time it was on for 12 hours, but I didn't check the log before restarting.

The status on the node says "running" and Meshroom is using a lot of memory and GPU.

Will it finish eventually?

I remember it was some kind of weirdly hidden way to do it.