Hello Gidske,
The problem with the actual file is caused by the different representation of Z values than is expected by PhotoScan. In your example it is represented by integer two byte values, while PhotoScan expects floating point value.
In the next version both options will be possible, but for the version 1.2.3 you need to save GeoTIFF using floating point format.
Also I've noticed that there are some extreme negative values in the file, however, in TIFF header these values are not specified as no-data value or interval.