Agisoft PhotoScan 0.8.5 pre-release

[Dmitry Semyonov]

Pre-release version of Agisoft PhotoScan 0.8.5 is available for download.

This pre-release is considered as unstable and is not recommended for production use.

Please let us know if you have any problems using this version.

Please post problems and/or questions concerning other PhotoScan version in separate topics.

This topic will be removed when the final 0.8.5 version is released.

Note
Project files created with 0.8.5 version can't be opened with earlier versions.

EDIT:
Updated to version 0.8.5 build 1376.

EDIT:
Updated to version 0.8.5 build 1398.

EDIT:
Updated to version 0.8.5 build 1419.

EDIT:
PhotoScan 0.8.5 build 1423 was finally released. Thank you for useful feedback.

Please use the links on the main PhotoScan pages for download:
Agisoft PhotoScan Standard edition
Agisoft PhotoScan Professional edition

[Diego]

After many tests with different data, my conclusion is that the Align Photos.. has serious problems. 

Apparently it is very fast, but ineffective. In previous versions works much better. I hope you can solve. I think a lot of testing with the innovation they want to do. 

[RHenriques]

I also did some testing and I've got mixed results. In some cases, the results are a lot worst than in the latest versions. Some models that worked great in the 0.8.4 version get messed up in this version. In some cases all the model is crunched into an indistinguishable amalgam of points with the cameras spreaded allover, with nonsense positions. In a few cases, mainly related with terrain models from aerial photography, results are obtained a lot faster and seem to be better than in version 0.8.5. In one case, both the model and the orthophoto are more precise than in any previous version. I've tested some of the new features, which are all very interesting and useful. I had some problems in the Ground Control pallete. This is a great feature but, when I tried to check errors from the photos the model simply vanished. We need a new manual to some of these new features. I would like to see feature improvements in the Matches palette too. A manual edition of matching points could be a huge addition. This version is a very promising version.

[Alexey Pasumansky]

Hello,

Thank you for reporting.

The problem with the alignment could be caused by the markers used. For now 0.8.5. uses them by default as correct matches and it may cause a misalignment if the markers are not placed precisely. On the datasets without markers the new alignment should work better then in previous versions.

Could you please inform us if the wrong alignments were in projects with markers?

[RHenriques]

Hi Alexey

All my tests were made without any markers. Only used the default alignment settings, without pair selection, markers or masks in the photos.
Cheers

[Diego]

Hi Alexey

I also do all my tests were made without any markers. 

Regards,

Diego

[RHenriques]

While using photos from UAV's or Kite Aerial Photography, I'm getting quicker and better results! Maybe it's an easy problem to fix. Most of the errors that I got came from very non favourable datasets. Aerial photography, with a good amount of  superimposition, is giving me better results.
Cheers

[wj]

From the 1224 version to 1330 version, the model often have the wrong texture case,I used the same data?Earlier version of the 794, there was no texture error, but the texture is very slow to generate

[wrumm]

I have problems reading in ground control data for markers. No matter if I specify the markers in csv or the new xml file format version....

cheers

[Alexey Pasumansky]

Hello wrumm,

Could you please provide the sample xml or csv file that has problems with import.

[Alexey Pasumansky]

Hello wj,

Could you please provide screenshot that describes the problem?

[wrumm]

Hi Alexey,

please find atteched the txt (tab delimited) and xml file.
The xml file was produced by exporting from the new groundcontrol panel and modifying some points manually in a textfile. During import nothing happens. The values remain the same.
Same thing with the txt file, but this one was created by hand, but I sticked to the manual.

cheers!

[RHenriques]

Problems with Ortophoto generation remain from version 0.8.4. If we try to render an ortophoto from a site with geometrically defined features mixed with terrains, like houses for instance, most of the times roofs or straight walls will get higly contorted.
There are also some problems with visualization, under macosx, when models exceed about 20 000 000 faces. Photoscan easely crashes beyond that limit.
When we start a batch with photo alignment and mesh generation, things will get done but, after that, the system gets very slow or completly blocked. It seems to be some memory management problem or memory dumping must be optimized. From activity monitor, we can see that Photoscan still blocks huge amounts of memory even with all the processes finished. 
Cheers
 

[Alexey Pasumansky]

Hello wrumm,

Thank you for the data provided.
Check if importing .txt file works correctly if quotes near the names of the markers are removed, because it should work in this case.
And .xml import problem will be fixed in the next update.

[Alexey Pasumansky]

Hello RHenriques,

Thank you for the reporting. We'll check the memory problem.
Could you please also check if the visualization of large models is faster if VBO flag is unchecked in Preferences.