Agisoft Photoscan 1.3.1 crashes when dense cloud is building.

[Eirik Strøm Pedersen]

I having problems with the new version of Photoscan. The program crash during the build dense cloud operation. Anyone experience some of the same issues? It seems to be related to CUDA or grapich drivers. My grapich drivers are up to date as they was updated last week by the service department in our company last week, so that cannot be the issue.

Right now I'm useing a modded version of Photoscan delivered by Agisoft that solves the issues with running GPU operations with Open CL. But this soulution are just temporary. Attached is the overview of my grapich cards.

[Alexey Pasumansky]

Hello Eirik,

We are aware of this issue and are fixing it right now. Hopefully the solution will be included in the next update.

[Alexey Pasumansky]

For those you has issues during depth maps generation on NVIDIA cards using CUDA, I can suggest to check pre-release version of PhotoScan 1.3.2:

Professional: http://download.agisoft.com/photoscan-pro_1_3_2_x64.msi
Standard: http://download.agisoft.com/photoscan_1_3_2_x64.msi

[paulkemp]

Same error here. Wish I knew there was a 1.3.2 version, or that this was a known bug, before I tried 3 times building the dense cloud. 

edit: 1.3.2 also failing here.

Version 1.3.2 also fails at the same step as 1.3.1 for me:

2017-05-10 13:04:48 Depth reconstruction devices performance:
2017-05-10 13:04:48  - 4%    done by CPU
2017-05-10 13:04:48  - 95%    done by GeForce GTX 1080
2017-05-10 13:04:48 Total time: 419.371 seconds
2017-05-10 13:04:48
2017-05-10 13:04:48 Generating dense point cloud...
2017-05-10 13:04:52 selected 102 cameras in 3.623 sec
2017-05-10 13:04:52 working volume: 28412x9927x3742
2017-05-10 13:04:52 tiles: 7x2x1
2017-05-10 13:04:52 selected 5 cameras in 0 sec
2017-05-10 13:04:52 preloading data... done in 0.361 sec
2017-05-10 13:04:52 filtering depth maps... done in 3.086 sec
2017-05-10 13:04:55 preloading data... done in 0.824 sec
2017-05-10 13:04:56 accumulating data... done in 0.764 sec
2017-05-10 13:04:57 building point cloud... done in 0.008 sec
2017-05-10 13:04:57 selected 39 cameras in 0.001 sec
2017-05-10 13:04:57 preloading data... done in 1.957 sec
2017-05-10 13:04:59 filtering depth maps...

[Alexey Pasumansky]

Hello paulkemp,

Have you submitted the crash report already?

According to the log the issue is not related to the GPU-processing, so it may be a memory issue.

[paulkemp]

Hello paulkemp,

Have you submitted the crash report already?

According to the log the issue is not related to the GPU-processing, so it may be a memory issue.

No, not submitted a crash report other than the logs themselves.

Was able to complete it by installing Nvidia drivers 382.05 clean, removing geforce experiece and running photoscan 1.3.2.

Completed log:
https://pastebin.com/f0LVQMeA

[Alexey Pasumansky]

Hello paulkemp,

Is the provided log from 1.3.2 related to the crashed operation? It looks like the process has been completed correctly.

If you can reproduce the issue and crash the application, could you please submit the crash report, as it would contain additional information regarding the problem?

[BristarUK]

I'm also getting the same crash on 1.3.2 whilst filtering depth maps.

My Project is aligned on low, c.3700 cameras/images, dense cloud build on low.

Spec:

2 x Xeon E5-2640 v4
2 x Nvidia GTX 1080 Ti
256 GB RAM

Am running 381 nvidia drivers, am trying upgrading to 382.33

[Alexey Pasumansky]

Hello BristarUK,

Have you submitted the crash report already?

Depth maps filtering is performed on CPU only, so GPU is not used. However, I can suggest to run Memtest86 utility to be sure, that there are now RAM issues.

[BristarUK]

Have you submitted the crash report already?

Depth maps filtering is performed on CPU only, so GPU is not used. However, I can suggest to run Memtest86 utility to be sure, that there are now RAM issues.

Sorry Alexi, I'm against the clock on this one with the model needed by wednesday. So I just reverted to 1.2.6 and all is working again.

[FrostBite]

Just throwing in my two cents...

I was using a GeForce 560 and never had problems with Photoscan
I then installed a GeForce 1080ti and after that had problems with building the dense cloud. Right when it was filtering the depth maps the program would crash or Windows would get an error and the computer would reboot. I'm going to try reinstalling my old video card to see if that's the problem... Sucks if the 1080ti has compatibility issues with PhotoScan.

[Alexey Pasumansky]

Hello FrostBite,

Depth maps filtering is not utilizing GPU, so any additional information regarding the crashes would be helpful to find out the source of the issue.

[paulkemp]

Hello paulkemp,

Have you submitted the crash report already?

According to the log the issue is not related to the GPU-processing, so it may be a memory issue.

Hi. I am still having issues with 1.3.2 4139. How do I submit a crash report? Crashreporter.exe seems to indicate that it's run automatically. Can you provide  a link to an earlier stable version of Photoscan? 1.2.6?

It would be great with some answers regarding these bugs.

[FrostBite]

 Hey Alexy,

I was hoping that you're right. But I changed back to my old Geforce 560 and tried the same project again with the same settings and it worked without a problem.

The problem is related to the newer video cards and/or the drivers that are related to them.

Not sure what to do now... it really sucks, since I purchased the new Geforce 1080ti but can't use it for work.



If anyone has any ideas or solutions to this problem please let me know!!

[Alexey Pasumansky]

Hello FrostBite,

If the issue is reproducible, could you please submit the crash report and put the link to this thread in the Comments field of the crash reported utility.

Additionally I can suggest to use the clean driver installation and check the RAM.