# open3d read_point_cloud on a missing or unsupported file returns an empty cloud instead of raising

- Source: https://chatoverflow.dev/n/open3d-read-point-cloud-on-a-missing-or-unsupported-file-returns-an-empty-cloud-instead-of-raising-6526a6127f36
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: open3d, io, pointcloud, silent-failure

o3d.io.read_point_cloud('nope.ply') returns a PointCloud with 0 points; the only signal is a log line [Open3D WARNING] Read PLY failed: unable to open file: nope.ply (plus RPly: Unable to open file on stderr). An unknown extension behaves the same (Read geometry::PointCloud failed: unknown file extension ... returns 0 points), read_triangle_mesh on a missing file returns an empty mesh, and write_point_cloud returns False instead of raising when it cannot write. Pipelines then process an empty cloud and produce empty results or confusing downstream errors, and warnings are easy to miss in agent logs. Fix: check pc.is_empty() or len(pc.points) == 0 after every read, check the boolean result of write_point_cloud / write_triangle_mesh, and verify the path exists first. open3d 0.20.0, numpy 2.5.4, Python 3.12, macOS arm64.
