Messages

1

Bug Reports / Error opening psx file: "Empty XML Data"

« on: January 23, 2020, 03:21:03 AM »

I recently came back to a project that is saved on a cloud drive (Mapped to K:\) that I cannot open anymore due to this error: "Empty XML data"

I have all of the files, (i.e. project.zip) and the folders for the project and I searched through this forum earlier but didn't solve the problem by making text edits to the .psx file.

Has anyone had a similar experience?

Here is what my .psx text looks like:

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.2.0" path="{projectname}.files/project.zip"/>

Here is what my doc.xml file looks like:

<?xml version="1.0" encoding="UTF-8"?>
<document version="1.2.0">
  <chunks next_id="2" active_id="0">
    <chunk id="0" path="0/chunk.zip"/>
    <chunk id="1" path="1/chunk.zip"/>
  </chunks>
  <meta>
    <property name="Info/OriginalSoftwareName" value="Agisoft Metashape"/>
    <property name="Info/OriginalSoftwareVendor" value="Agisoft"/>
    <property name="Info/OriginalSoftwareVersion" value="1.5.0"/>
  </meta>
</document>

2

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: May 24, 2018, 11:03:47 PM »

Hi Alexey,
I have gone back to the manufacturer of the PC and they suggested turning off a few CPUs in windows with the "Processor Affinity" option box. This did not have any effect. I am still getting the CUDA crashes.

I took your advice and detached all but one of the GPUS and everything worked fine. Attaching two or all three causes the crash. I am attaching the reports from Cuda-Z software showing the performance of each GPU. I hope that information is useful to you, because I can't interpret it.

3

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: March 30, 2018, 11:26:55 PM »

Sorry to bother again. I am posting this here because I can not add an attachment in a personal message.
We just purchased a Agisoft Pro license to work around this issue because this code worked the first time with the demo of Pro:

PhotoScan.app.settings.setValue("main/depth_max_gpu_multiplier", 1)

Unfortunately, I am getting the same crash again in Pro with this code pasted into the console before running the dense cloud process. I attached the console text here.

Again the error code is this:

Error: Kernel failed: the launch timed out and was terminated (6) at line 821

4

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: March 27, 2018, 07:14:37 PM »

Thanks for showing me this. I am still getting the same error in Standard. I attached the console text here.
I assume the DWORD item was 64bit, correct?

5

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: March 27, 2018, 06:30:11 PM »

Would you mind sending a screenshot to show what this looks like as it is written in the registry? I am new to editing these by hand.

6

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: March 26, 2018, 07:05:23 PM »

Thank you Alexey,
I did as you said and was able to get the model to process the dense cloud without any errors if I added the line of code you sent in a demo version of Agisoft Photoscan Pro. I don't have a license for Pro, so I can't save. Is there a way to duplicate this in Standard?

7

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: March 22, 2018, 10:08:48 PM »

I am still getting these CUDA crashes on the dense point cloud step. I have tried this with a different photo sets, but it is still happening, even when I reboot. I also asked my IT department, and outside of the driver, (which is updated), they have not been able to help.

GPUS:
3 x GeForce 1080 TI
Driver version:
23.21.13.9101

I am attching two full error logs from recent errors.
1. The error log named "Error1.txt" occurred when I checked all three GPUS and unchecked the CPU processing while running GPU processes.
2. The error log named "Error2.txt" occurred when I unchecked my top GPU and checked the CPU processing while running GPU processes.

I am unsure what to do next.

8

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: March 15, 2018, 08:02:12 PM »

I am sorry for the delay getting back to this problem. I have been working with our IT department to see if there is an issue with the configuration of the graphics cards in the PC.

So far I have had the problem only with 500+ photo projects, and I have noticed that immediately after a reboot of the PC, I am able to get the projects with larger numbers of images to process dense point clouds on medium settings, but after I get an initial failure, the CUDA errors will continue with all settings until I reboot again.

As soon as I know more I will offer an update.

9

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: February 23, 2018, 06:40:32 PM »

I had the same instinct. I tried turning off the CPU before I sent my previous reply.

Do you know of some other options?

10

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: February 22, 2018, 11:36:02 PM »

Hi Alexey,
I was able to do a fresh driver install and test it successfully when I ran the dense point cloud stage on "Mediu." but when I switched it toi high, I get the same CUDA error you see below:

2018-02-22 15:32:22 [GPU] estimating 1126x1722x288 disparity using 1126x861x8u tiles
2018-02-22 15:32:22 timings: rectify: 0.015 disparity: 0.145 borders: 0.012 filter: 0.038 fill: 0
2018-02-22 15:32:22 [GPU] estimating 1572x1238x224 disparity using 786x1238x8u tiles
2018-02-22 15:32:22 [GPU] estimating 1064x1889x384 disparity using 1064x945x8u tiles
2018-02-22 15:32:24 [GPU] estimating 1157x1962x384 disparity using 1157x981x8u tiles
2018-02-22 15:32:24 GPU borders filtering failed: the launch timed out and was terminated (6) at line 216
2018-02-22 15:32:24 using CPU implementation...
2018-02-22 15:32:24 Error: Kernel failed: the launch timed out and was terminated (6) at line 769
2018-02-22 15:32:24 GPU processing failed, switching to CPU mode
2018-02-22 15:32:24 [CPU] estimating 1064x1889x384 disparity using 1064x945x8u tiles
2018-02-22 15:32:24 Error: Kernel failed: the launch timed out and was terminated (6) at line 821
2018-02-22 15:32:24 GPU processing failed, switching to CPU mode
2018-02-22 15:32:24 [CPU] estimating 1157x1962x384 disparity using 1157x981x8u tiles
2018-02-22 15:32:24 timings: rectify: 0.021 disparity: 0.292 borders: 0.028 filter: 0.108 fill: 0
2018-02-22 15:32:24 Error: Kernel failed: the launch timed out and was terminated (6) at line 821
2018-02-22 15:32:24 GPU processing failed, switching to CPU mode
2018-02-22 15:32:24 [CPU] estimating 1381x7424x160 disparity using 1381x1061x8u tiles
2018-02-22 15:32:24 Error: Kernel failed: the launch timed out and was terminated (6) at line 170
2018-02-22 15:32:24 GPU processing failed, switching to CPU mode
2018-02-22 15:32:24 [CPU] estimating 1126x1722x288 disparity using 1126x861x8u tiles
2018-02-22 15:32:25
2018-02-22 15:32:25 Depth reconstruction devices performance:
2018-02-22 15:32:25  - 36%    done by GeForce GTX 1080 Ti
2018-02-22 15:32:25  - 32%    done by GeForce GTX 1080 Ti
2018-02-22 15:32:25  - 32%    done by GeForce GTX 1080 Ti
2018-02-22 15:32:25 Total time: 664.673 seconds
2018-02-22 15:32:25
2018-02-22 15:32:25 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-22 15:32:25 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-22 15:32:25 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-22 15:32:25 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-22 15:32:25 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-22 15:32:26 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-22 15:32:26 Finished processing in 691.457 sec (exit code 0)
2018-02-22 15:32:26 Error: the launch timed out and was terminated (6) at line 198

11

Bug Reports / Re: CUDA Crash during dense point cloud processing

« on: February 21, 2018, 08:18:59 PM »

Thanks for the fast reply. Here are the specs:

NVIDIA DRIVERS: 23.21.13.8813 on 3x GeForce 1080Ti
Windows 10 Enterprise 64bit
Photoscan 1.4.0 Build 5650

12

Bug Reports / CUDA Crash during dense point cloud processing

« on: February 19, 2018, 09:25:11 PM »

I have a  very new multi-GPU machine that has been crashing during the dense point cloud processing due to an error you can see below from the console. It does not happen with a smaller 200 photo process, but this set with 421 photos is causing this error. Does anyone know a good fix?

2018-02-19 13:15:46 [GPU] estimating 2339x1537x832 disparity using 1170x769x8u tiles
2018-02-19 13:15:46 timings: rectify: 0.03 disparity: 0.402 borders: 0.031 filter: 0.088 fill: 0
2018-02-19 13:15:46 [GPU] estimating 1889x1945x192 disparity using 945x973x8u tiles
2018-02-19 13:15:50 timings: rectify: 0.058 disparity: 0.377 borders: 0.018 filter: 3.42 fill: 0
2018-02-19 13:15:50 [GPU] estimating 1224x924x896 disparity using 1224x924x8u tiles
2018-02-19 13:15:50 GPU rectifying failed: the launch timed out and was terminated (6) at line 216
2018-02-19 13:15:50 using CPU implementation...
2018-02-19 13:15:50 Error: the launch timed out and was terminated (6) at line 216
2018-02-19 13:15:50 GPU processing failed, switching to CPU mode
2018-02-19 13:15:50 [CPU] estimating 1224x924x896 disparity using 1224x924x8u tiles
2018-02-19 13:15:50 Error: Kernel failed: the launch timed out and was terminated (6) at line 199
2018-02-19 13:15:50 GPU processing failed, switching to CPU mode
2018-02-19 13:15:50 [CPU] estimating 2339x1537x832 disparity using 1170x769x8u tiles
2018-02-19 13:15:50 Error: Kernel failed: the launch timed out and was terminated (6) at line 821
2018-02-19 13:15:50 GPU processing failed, switching to CPU mode
2018-02-19 13:15:50 [CPU] estimating 1889x1945x192 disparity using 945x973x8u tiles
2018-02-19 13:15:50 Error: the launch timed out and was terminated (6) at line 198
2018-02-19 13:15:50 GPU processing failed, switching to CPU mode
2018-02-19 13:15:50 [CPU] estimating 1472x1562x128 disparity using 1472x781x8u tiles
2018-02-19 13:15:50
2018-02-19 13:15:50 Depth reconstruction devices performance:
2018-02-19 13:15:50  - 35%    done by GeForce GTX 1080 Ti
2018-02-19 13:15:50  - 32%    done by GeForce GTX 1080 Ti
2018-02-19 13:15:50  - 33%    done by GeForce GTX 1080 Ti
2018-02-19 13:15:50 Total time: 202.378 seconds
2018-02-19 13:15:50
2018-02-19 13:15:50 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-19 13:15:50 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-19 13:15:50 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-19 13:15:50 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-19 13:15:50 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-19 13:15:53 Warning: cudaStreamDestroy failed: all CUDA-capable devices are busy or unavailable (46)
2018-02-19 13:15:53 Finished processing in 231.347 sec (exit code 0)
2018-02-19 13:15:53 Error: the launch timed out and was terminated (6) at line 198

13

Bug Reports / Re: Crash Photoscan when opening OpenCL PReferences

« on: May 12, 2016, 01:10:01 AM »

Thanks. I submitted a crash report.

I also added some text above just after you replied about the display driver.

Thanks

14

Bug Reports / Re: Crash Photoscan when opening OpenCL PReferences

« on: May 11, 2016, 10:43:30 PM »

I first thought that Remote desktop was the problem, so I tried Teamviewer and it happened again. Finally, I checked the server locally and the same crash occurred.

The Teslas are the only cards installed on the server. Could the problem be with the Microsoft Basic Display Adapter that is actually running the display?

Driver Version: 6.3.9600.16384

Thanks for your help Alexey.

15

Bug Reports / Re: Crash Photoscan when opening OpenCL PReferences

« on: May 11, 2016, 10:12:00 PM »

Hi,
I am having the same problem on a machine running windows server 2012. As soon as I click the OpenCL tab, Photoscan crashes.

I described the problem in Agisoft Crash Reporter as well. I am thinking this may be an issue with the drivers - With the current operating system, I don't know if I can update to the most recent drivers, but I am also using brand new NVidia Tesla K80s in this server, so they cant be too out of date.

Thanks in advance for any help.