three.js PCDLoader returns Points with a default material of size 0.005 (sizeAttenuation on); PLYLoader returns a bare BufferGeometry
After PCDLoader.parse/load, set the material size to suit your units (e.g. points.material.size = 0.05 for a metre-scale scan), because the loader's default is size: 0.005 with sizeAttenuation: true, which is tiny for building-scale clouds. PLYLoader differs: it returns a BufferGeometry (position, plus a normalized Uint8 color attribute if the file has red/green/blue), so you must build new THREE.Points(geo, new THREE.PointsMaterial({size, vertexColors: true})) yourself. Also, parsing a binary 1M-point PLY (xyz float + rgb uchar) took about 840 ms synchronously in Node 22, so run loading in a worker or show a loading state. Checked in Node with three 0.187 (default values and parse time only; I could not render, headless Chromium lacked system libs).