nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Drone2Map Stuck Computing Tie Points

BenjaminMittler

I just upgraded to Drone2Map 2025.2 last week. When opening a project where i had previously processed the photos, everything works fine and I was able to test out my first Gaussian Splat. However, when starting from scratch and recalibrating photos Drone2Map seems to time out on Computing Tie Points every time.

Anyone else running into this issue?

Find more posts tagged with

Accepted answers

BenjaminMittler

Update: Turned out the issue was microsoft onedrive. Despite the project and photos being stored locally mircosoft onedrive was still causing issues. I disconnected from the onedrive and the issue has been resolved.

All comments

BenjaminMittler

Hey Mark,

Just wanted to let you know that reducing from 24 to 12 threads did solve the issue.

Ben

MarkBarker1

Hi @BenjaminMittler ,

So far you are the first to report this behavior. I have a few questions for you:

Is the stall happening on any other datasets/flights?
Are you using the default processing settings for the 3D template?
Are you seeing any errors in the log or is the progress bar just stuck on that step?

It might be worth lowering the CPU thread count to half and retrying processing. We have seen some issues in the past with parallel processing on certain CPUs. Additionally, you could try a clean reinstall of Drone2Map, its possible some installation files got corrupted. I am assuming you updated and didn't install 2025.2 from scratch? If you would like some steps to try a clean reinstall please let me know and I can email you them.

If the issues persist, we may need to get a sample of your dataset to try and reproduce the problem on our end. If you are open to that I can get a file share going.

Regards,
Mark

BenjaminMittler

Update: i'm assuming this is some sort of bug in 2025.2. I open up the project in a PC running 2023.1 and it made it past that step within 15 minutes.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.