Messages

16

General / How is AMD Ryzen performance on photoscan v1.3?

« on: April 19, 2017, 07:12:20 PM »

Hi,

In a Anandtech review (http://bit.ly/2pCzq20), Photoscan v1.0 got mixed results vs Intel. Since this benchmark in based on on the old v1.0, i was wondering how it's perform with all the tweaks on the lastest version.

Any info?

Regards,

tutoss

17

General / Re: Why does my model look so miserabel?

« on: November 10, 2016, 02:25:50 AM »

Hi hermiew,
well, to use markers, you need coordinates of them.
Try take more photos and align them without markers

18

General / Re: Banana shape effect

« on: September 26, 2016, 06:08:14 PM »

you can try add a previous camera calibration parameter and fix it. Works for me.

tutoss

19

Feature Requests / Re: Rolling shutter integration

« on: September 21, 2016, 07:51:56 PM »

any news on this?

20

Feature Requests / Re: Rolling shutter integration

« on: September 11, 2016, 07:54:59 PM »

+1

21

Feature Requests / Re: Rolling shutter integration

« on: August 03, 2016, 11:00:15 PM »

+1

22

Feature Requests / Re: Show progress in taskbar

« on: June 22, 2016, 12:01:47 AM »

AGREE!!!

23

General / Re: error: bad allocation (not enough memory) only on 1.2 (1.2.3)

« on: January 29, 2016, 10:59:02 PM »

Alexey,
there is uploading via wetransfer, splitted in two files.

Chunk properties:

24

General / Re: error: bad allocation (not enough memory) only on 1.2 (1.2.3)

« on: January 28, 2016, 06:21:11 PM »

Hi Alexey,
Yes, is the 64bit version (checked in about Photoscan...)

Wetransfer link of the log:
http://we.tl/qR37DiWhpn

settings used (same on 2014 (1.0 i think) and 2015 with Photoscan 1.2.1 due to expansion of the project (more images)):
accuracy: high
pair preselection: reference
key point limit: 40000
tie point limit: 0

Precalibrated camera with same file on both years

The first error is with all images referenced but with the elevations forced to zero
The second error is with all images without Z modification (original process)
The third error is the abort of the current process (half of images)

Regards,

Tutoss

25

General / error: bad allocation (not enough memory) only on 1.2 (1.2.3)

« on: January 28, 2016, 05:03:03 PM »

Hi,
i got this error with this version in the alignment step. Is a big old Project (8600 images) and i reprocessing it for test purposes.
With 1.0 and 1.1 is processed without issues in the same pc (64 gb ram) and i processed projects with 21000 images on v1.1 without problems  .

26

General / Re: Poor quality results in 1.1.6 build 2038 (64 bit)

« on: December 18, 2015, 03:53:55 AM »

Hi alexey,
the tipical settings for aerial data with geolocation info:

accuracy: high
pair preselection: reference
key point limit: 40000
tie point limit: 0 (to replicate Photoscan 1.0)

Dense cloud medium and aggresive filter.

27

General / Re: Poor quality results in 1.1.6 build 2038 (64 bit)

« on: December 17, 2015, 03:45:55 PM »

But why with the sparse cloud without any hole the dense cloud have two big holes?
The only difference on the workflow is the "pair preselection" method.
Anyway, for aerial photos with geolocation info, the "reference" method is the idea..

28

General / Re: Poor quality results in 1.1.6 build 2038 (64 bit)

« on: December 12, 2015, 05:57:06 AM »

Any comments from the devs are welcome 

29

General / Re: Poor quality results in 1.1.6 build 2038 (64 bit)

« on: December 09, 2015, 11:40:42 PM »

Well...very strange...all cameras aligned...sparse cloud without holes....and dense cloud with two big holes!!
BUT...the photos from the holes had less projections than the zones without holes on the dense cloud.

30

General / Re: Poor quality results in 1.1.6 build 2038 (64 bit)

« on: December 09, 2015, 03:13:16 AM »

Hi jdmcbr,
can you upload the dataset of images to try?