Topics

1

Bug Reports / PLY export with texture gives huge and invalid mesh

« on: March 08, 2017, 11:58:31 PM »

When I export the same mesh (ca. 1.2 million polygons) as a PLY, once with texture and once without (both with vertex color exported), the with-texture mesh is 54.8 MB and will not load in Rhinoceros ("faile to read binaries properly") and GOMinspect ("a surface with 53 corners was found"). The mesh exported without the texture is only 24.7 MB and loads without issues. 

This is new with version 1.3.0 3772 64bit

2

Bug Reports / 1.2.0 odd bug: deleted points come back

« on: September 05, 2015, 12:59:37 AM »

I can't reply to the 1.2.0 pre-release topic, as it is locked, thus a thread here.

Since the latest release, when I delete points from a dense point cloud, save, and load the file again, the points are back again - as if I had never deleted them.

Is this a bug or has something changed about manual editing of dense clouds?

3

General / Photoscan rocks my colletion digitizing project!

« on: September 05, 2015, 12:34:48 AM »

Just wanted to point out to all that I am using Photoscan Pro for a collection mass digitizing project, in which I expect to make high-res models of some 400 dinosaur bones within 5 months - and Photoscan absolutely rocks!   

The bones are between half a meter and 1.5 m long, and I take roughly 200 photographs per bone. Half with one side of the bone up, then the other half with the bone flipped upside down, and laid on a different table in a different corner of the room. This way, matching points can only exist on the bone itself. And I have a ratio of successful models of 100%! It ALWAYS works!

Then, build a dense cloud, clean it up for a minute or two (there is always a bunch of points floating around from the backgrounds), build the mesh - DONE! All in all I spend less than 15 minutes per bone, for models with an accuracy of ca. 0.1 mm and around 8 to 20 million polygons each. Soon, the models will be accessible online, a huge boost to our science.

Well done, Agisoft team, and thank you very much!

4

Bug Reports / Image paths problem

« on: May 02, 2014, 04:33:56 PM »

I always used to move psz files and image folders around, and never had a problem as long as the relative positions were the same. Usually, I have a main folder in which I store my PSZ files, and subfolders with my images for the individual chunks. As long as I move the main folder with all its content, the photos are found correctly.

Only if I selected the 'Store absolute image paths' option in the Advanced tab of the preferences did this not work.

Now, I found that in some cases since the second-to-last version the images are not found although the absolute paths option is not checked. Am I doing anything wrong when copying complete folders?

5

Bug Reports / IGNORE - turns out this is a bug!

« on: May 02, 2014, 01:20:36 PM »

EDIT: found that what I wanted is actually how the program should work. It just sometimes doesn't.

Hi,

I usually place markers for aligning chunks on the images, not the 3D models. Then, I align the chunks, merge them - and the dense point clouds calculated for the separate chunks merge into one common point cloud, which I then scale and generate a mesh from.

However, if I place the markers for alignment of the chunks on the models, meshes but not dense clouds of the chunks become merged.

Is there a reason for this? If not, is it possible to add this option?

6

Feature Requests / support for interactive pen display / change to lasso selection

« on: March 10, 2014, 03:54:25 PM »

Currently, the lasso selection requires a lot of clicking. With an interactive pen display this is quite annoying and impractical. Would it be possible to either add support for stuff like the Wacom Bamboo pen & display, or simply change the lasso to a simple draw mode?

7

Bug Reports / 1.0.0 and 1.0.2 "stuck" at ca. 95% of dense cloud computing

« on: March 07, 2014, 12:18:01 PM »

HELP, please!

I used 1.0.0 for a long time and it worked fine. Three days ago, when calculating a batch process (dense cloud, high, 6 chuncks with ~40 cameras each, expected number of points around 8 million) the program got "stuck" at 95% of the first dense cloud in the reconstructing depth step, no remaining time shown. The elapsed time kept increasing to 145 hours. At that point I tried to the job via "cancel", which had no effect. Memory usage waas a ~2 GB of 8 available, CPU power was at 100% for one, with the remaining 15 idling.
I had to end photoscan via the task manager (end task).

I rebooted and tried again, this time with only one chunk. Same result, this time stuck at 92%, no time remaining shown.
I tried again, using a smaller box for the point cloud, and that worked.
I tried again, with a somewhat larger box, and it failed again.

I upgraded to 1.0.2 and keep having the same problem.

The size of the jobs is so small that normally Photoscan handled them within less than an hour without problems. It is not a memory issue (never more than 66% of available memory used). it is not a CPU issue, either.

I tried uninstalling and reinstalling - no change.

The "critical" size seems to be anything that calculates the depth reconstruction for more than 40 minutes.

Any suggestions how I can get this to work again? If needed I can post files.

8

Bug Reports / 1.0.0 progress time nonsense

« on: September 11, 2013, 11:40:17 PM »

I started an alignment process at work, flipped my laptop shut without pausing it, just now re-opened it. Interestingly, the program now lists the intervening 5 hours (during which the computer was in slumber mode, and nothing was calculated) as elapsed time, and accordingly projects a ridiculously long remaining time, which is shrinking rapidly.

Maybe you can fix that so that only time spent actually working is counted?

9

Bug Reports / Mouse behaviour for marker placement suddenly changed

« on: April 19, 2013, 10:30:37 AM »

EDIT: answered by support! Many thanks! Marker creation in 3D works differently than marker creation in 2D!


When I entered marker mode the right mouse button used to give me a little pop-up menu for creating, assigning and editing markers. Now it does nothing. Instead, the left mouse button places a new marker - but I can't edit it in any way, nor place it in a different photo. I also get kicked out of marker mode.

What's wrong???

10

Feature Requests / Incremental name change for auto-save in batch

« on: October 05, 2012, 11:28:27 AM »

Photoscan has an option to save the project after every step during a batch process.

For me it is often interesting to create meshes in LOW and ULTRA HIGH - but that can't be done via a batch process.

Could alter please the option so that one can additionally choose to have the name altered (*_01.psz, *_02.psz, etc) with every save?

11

Feature Requests / Alignment based only on markers

« on: October 05, 2012, 11:03:54 AM »

I sometimes have projects where there is a lot architecture in the background that tends to produce misalignments, because it is partially repetitive. The objects I want to model themselves often have too little texture to allow masking the background, as they alone lead to bad alignments, too. I should take photos with more overlap, but can't because I can't get far enough away from the object.

In these cases it would help if I could set markers - I have manually set over 100 in one project - and PhotoScan aligns the the photos based ONLY on my manual markers. The accuracy should be good enough for my task, because I usually have very small objects to set the markers, so my marker placement is highly accurate.

Can this be done easily?