Messages

1

General / Re: Agisoft PhotoScan 1.4.0 pre-release

« on: November 22, 2017, 02:09:01 AM »

>Does it happen only with the certain pre-release build or you have observed it before with any 1.3.4 release versions?
>Also please specify, which antivirus you are using.

No, I have never seen this before on Photoscan, but it has happened on other programs.
The antivirus is OfficeScan from Trend Micro as shown in the printscreen.
https://www.trendmicro.com/en_gb/business.html

Erik

2

General / Re: Agisoft PhotoScan 1.4.0 pre-release

« on: November 17, 2017, 03:08:08 PM »

Our company antivirus software crashed my project and also Photoscan 1.4.0 which I downloaded last night.
Previous versions of Photoscan which have done the same I think have not had any issues. I guess you should talk to the antivirus-companies and get on their "white-list"

3

Bug Reports / Re: Photoscan version 1.3.4.5067 unusable

« on: November 10, 2017, 01:38:25 AM »

Hi, sorry for long delay, The version I went back to and is working is:
photoscan-pro_1_3_3_x64.msi   (96.2Mb)   downloaded on 2017-08-18.

best regards, Erik

4

Bug Reports / Re: Photoscan version 1.3.4.5067 unusable

« on: November 03, 2017, 10:58:49 PM »

hi, this log was from version 1.3.4. Dont want to touch the NVIDIA drivers du to other programs on the same PC.
Going back to an older version of Photoscan fixed the issue, so there are some bugs most likely.

have a nice weekend!

Erik

5

Bug Reports / Re: Photoscan version 1.3.4.5067 unusable

« on: November 02, 2017, 10:05:34 PM »

sorry, my 128Gb ram PC with 11Gb founders edition GTX1080 superturbo got out of memory!
Error: CUDA_ERROR_OUT_OF_MEMORY (2)

So I was uninstalling 1.3.4 and reinstalling an earlier version, here are the full log:


2017-11-02 19:00:43 Matching points...
2017-11-02 19:00:43 Using device: GeForce GTX 1080 Ti, 28 compute units, 11264 MB global memory, compute capability 6.1
2017-11-02 19:00:43   max work group size 1024
2017-11-02 19:00:43   max work item sizes [1024, 1024, 64]
2017-11-02 19:00:43 Error: CUDA_ERROR_OUT_OF_MEMORY (2) at line 115
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.047 sec
2017-11-02 19:00:43 OptimizeCameras: f, cx, cy, k1-k3, p1, p2
2017-11-02 19:00:43 Optimizing camera locations...
2017-11-02 19:00:43 coordinates applied in 0 sec
2017-11-02 19:00:43 Finished processing in 0.003 sec
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.046 sec
2017-11-02 19:00:43 BuildDenseCloud: quality = Lowest, depth filtering = Disabled
2017-11-02 19:00:43 Error: Null point cloud
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.011 sec
2017-11-02 19:00:43 BuildModel: surface type = Height field, source data = Dense cloud, face count = Medium, interpolation = Extrapolated
2017-11-02 19:00:43 Error: Null dense cloud
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.011 sec
2017-11-02 19:00:43 BuildOrthomosaic: projection type = Geographic, projection = WGS 84 / UTM zone 32N, surface = Mesh, blending mode = Mosaic, resolution = 0.2
2017-11-02 19:00:43 Error: Null model
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.012 sec
2017-11-02 19:00:43 ExportOrthomosaic
2017-11-02 19:00:43 Error: Null orthomosaic
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.011 sec
2017-11-02 19:00:43 ExportReport
2017-11-02 19:00:43 Generating report...
2017-11-02 19:00:43 Error: Null point cloud
2017-11-02 19:00:43 Saving project...
2017-11-02 19:00:43 saved project in 0.011 sec
2017-11-02 19:00:43 Finished batch processing in 761.041 sec (exit code 1)
2017-11-02 19:47:06 Checking for missing images...
2017-11-02 19:47:06 checking for missing images... done in 0.05 sec
2017-11-02 19:47:06 Finished processing in 0.051 sec (exit code 1)
2017-11-02 19:47:06 AlignPhotos: accuracy = High, preselection = generic, keypoint limit = 40000, tiepoint limit = 4000, constrain features by mask = 0, adaptive fitting = 1
2017-11-02 19:47:06 Detecting points...
2017-11-02 19:47:06 Using device: GeForce GTX 1080 Ti, 28 compute units, 11264 MB global memory, compute capability 6.1
2017-11-02 19:47:06   max work group size 1024
2017-11-02 19:47:06   max work item sizes [1024, 1024, 64]
2017-11-02 19:47:08 [CPU] photo 123: 40000 points
2017-11-02 19:47:08 Finished processing in 2.314 sec (exit code 0)
2017-11-02 19:47:08 Error: CUDA_ERROR_OUT_OF_MEMORY (2) at line 115

6

Bug Reports / Re: Photoscan version 1.3.4.5067 unusable

« on: November 02, 2017, 08:54:02 PM »

I agree and recommend removing 1.3.4 from beeing able to download.

Photoscan pro 1.3.4 build 5067(64bit)  was crashing twice when Aligning photos/Selecting pairs...

First time the whole computer froze! had to Power off!!!

second time: "Photoscan stopped working"

Now I have tried the -angle workaround.

Log from last crash:

2017-11-02 18:29:18 Using device: GeForce GTX 1080 Ti, 28 compute units, 11264 MB global memory, compute capability 6.1
2017-11-02 18:29:18   max work group size 1024
2017-11-02 18:29:18   max work item sizes [1024, 1024, 64]
2017-11-02 18:31:13 12622242 matches found in 115.733 sec
2017-11-02 18:31:16 matches combined in 3.014 sec
2017-11-02 18:34:34 Agisoft PhotoScan Professional Version: 1.3.4 build 5067 (64 bit)
2017-11-02 18:34:34 Platform: Windows
2017-11-02 18:34:36 OpenGL Vendor: NVIDIA Corporation
2017-11-02 18:34:36 OpenGL Renderer: GeForce GTX 1080 Ti/PCIe/SSE2
2017-11-02 18:34:36 OpenGL Version: 4.5.0 NVIDIA 384.76
2017-11-02 18:34:36 Maximum Texture Size: 32768
2017-11-02 18:34:36 Quad Buffered Stereo: not enabled
2017-11-02 18:34:36 ARB_vertex_buffer_object: supported
2017-11-02 18:34:36 ARB_texture_non_power_of_two: supported
2017-11-02 18:34:36 Using simple console. Rich console can be enabled in Preferences dialog.

7

Bug Reports / ETA on new version of Photoscan?

« on: March 10, 2017, 12:35:09 PM »

Hello,
is there an estimated time of arrival for a new version of Photoscan?
We are now version 1.3.0 build 3772 (5 February 2017), and have problems with utilizing it fully because of the current bugs. If possible, can we use a development/beta version and we take responsibility for results and reporting to you?

thanks,

Erik

8

Bug Reports / Holes in orthomosaics, both from DEM and Mesh

« on: March 07, 2017, 05:29:16 PM »

hello,
as reported in the General forum,
in version 1.30(build 3772) we get holes in orthomosaics, both from DEM and Mesh

Also, when building mesh with the option "Interpolation: Extrapolated"
And Close Holesin the mesh
And building orthomosaics with the options "HOLE FILLING:Yes"

I also get the same error when using a DEM  for building orthomosaics with the options "HOLE FILLING:Yes"

overlap picture for this area in white is attached, of course it is not the best overlap, but I think the areas have at least 4 images(but holes are mostly in forest).

There must be a new bug in this, as I get results like the attached, lots of small holes[no snow]... 


CPU: i7-6820,
64Gb ram
GPU: GTX 980M & Cuda

* In Preferences - GPU, should we Use cpu when perfoming gpu acc. proc.?



Best regards, Erik

9

Bug Reports / Re: version 1.30(build 3772) crashing building a batch process

« on: March 06, 2017, 03:53:16 PM »

Thanks.

I think there is also a problem with region beeing reset in a large project.
In a resulting ortho the region is getting reset to the project default when batch processing.
(ortho should be much more than 100 000*100 000 pixels)

10

Bug Reports / Re: version 1.30(build 3772) crashing building a batch process

« on: March 06, 2017, 02:38:57 PM »

Yes correct,
at least two times when trying to select the coordinate system in the Batch Processing.
I dont remember the third&fourth crash last week.
I will send a more detailed report if it crashes again.

11

Bug Reports / version 1.30(build 3772) crashing building a batch process

« on: March 06, 2017, 02:03:39 PM »

version 1.30(build 3772) have been crashing much more than previous versions, for example several times when building a batch process (even before starting it). I have used the automatic crash reporting to send the crash reports to Agisoft.

CPU: i7-6820,
64Gb ram
GPU: GTX 980M & Cuda

Erik

12

General / Re: Holes in orthophotomap

« on: March 06, 2017, 01:57:51 PM »

Thanks Alexey!
I have submitted crash reports, this have happened when changing  a batch process (even before starting it).

The orthomosaic with holes have source mesh, overlap picture for this area is attached, of course it is not the best overlap, but I think the areas have at least 4 images(but holes are mostly in forest). I am now trying "close holes" in the mesh.

CPU: i7-6820,
64Gb ram
GPU: GTX 980M & Cuda

* should we Use cpu when perfoming gpu acc. proc.?

13

General / Error: Holes in orthophotomap

« on: March 06, 2017, 01:11:01 PM »

Yes, when building orthomosaics you have the options "HOLE FILLING:Yes" and first when building mesh you have the option "Interpolation: Extrapolated". Perhaps you should add "Close Holes" after building the mesh to avoid the small holes as shown in the attchment, but then the orthomosaic-option "HOLE FILLING:Yes" have a problem
There must be a new bug in this, as I get results like the attached, lots of small holes[no snow]... 

And version 1.30(build 3772) have been crashing much more than previous versions, for example when building a batch process (even before starting it). I have used the automatic crash reporting to send the crash reports to Agisoft.

Still there are lots of new options in version 1.3, THANKS Agisoft 

CPU: i7-6820,
64Gb ram
GPU: GTX 980M & Cuda
(should we Use cpu when perfoming gpu acc. proc.?)

Best regards, Erik

14

Bug Reports / Re: Error: Can't write pyramid data

« on: May 18, 2016, 11:57:42 AM »

Thanks, I got it working by removing unnecessary chunks in the project, and reducing the area a bit and using the mesh with 1.87mill faces, 0.9mill vertices.
Now the colours are good thanks!

15

Bug Reports / Re: Error: Can't write pyramid data

« on: May 13, 2016, 02:36:45 PM »

Hello,
I am also getting the same errormessage when  Building 0.05m Orthomosaic from the Mesh(1.8mill points, 1067 images, 4 good GCP's + 2 checkpoints)
I am also using version 1.2.4 64 bit, build 2399 with all data on a local SSD-disk with plenty of free space.
Images are 24bit JPG,  16Mpix.
Orthomosaic 38720*39140 pixels, blending mode: Mosaic, color correction Enabled.
Some few images are a bit oblique but absolute values pitch is less than 25 degrees.

Creating the Orthomosaic from DEM works, but with VERY bad colors, see attached.