Camera names don't match
Fix renders marked Not used or placed in the wrong spot because their names don’t match a camera.
Each render is placed at the camera with the same name in your points file. When the names don’t match, the render can’t be placed, or lands in the wrong spot.
Symptoms
- The Renders step says … with no camera, and those renders are marked × or Not used.
- The check step says There’s no camera called … in the points file.
- The Camera points step says … without renders, ignored. These are cameras no render matched.
- A render shows in the wrong room, or two renders sit in the same spot.
How names are matched
- The file name without its extension is compared with each camera name. Cam_Kitchen_01.jpg matches the camera Cam_Kitchen_01.
- Capital letters don’t matter.
- If there’s no exact match, a render matches a camera whose name it contains, or that contains it. If several do, the longest camera name wins.
1. The names are spelt differently
The most common cause. Compare the render name with the camera name in points.txt, letter by letter. Watch for 01 versus 1, extra words, and _ versus -.
Fix: rename the render to match its camera, then drop the folder again. Renaming the render is quicker than re-rendering.
2. The camera name has spaces
The points file can’t hold names with spaces, so the camera is missing or renamed. The exporter warns you and Fix names swaps each space for _.
Fix: after Fix names, rename those renders the same way, with _ instead of each space. Then drop the folder again.
3. The camera isn’t in the points file
The render’s camera wasn’t selected when you pressed Save camera points, or the points file is from an earlier export.
Fix: select every tour camera (Select layer is quickest), press Save camera points again, and drop the folder again. See Export with the ArchviewVR Exporter.
When you’re adding a render to a saved project, drop the new points file with it. Without one, a new render has no camera and is marked Not used. See Replace or add renders later.
4. A render matched the wrong camera
Loose matching can pick the wrong camera when names are short or overlap. For example, a render called Kitchen.jpg could match Cam_Kitchen_01 or Cam_Kitchen_02. The same goes for a render with something extra, like Cam_Kitchen_01_v2.jpg, dropped alongside Cam_Kitchen_01.jpg: both go to one camera.
Fix: give every render exactly its camera’s name, and keep only one version of each render in the folder.
5. The wrong file was read as the points file
Any .txt, .csv or .json file in the folder can be taken as the points file. Check the Camera points step shows points.txt. If it doesn’t, move notes and old exports out of the folder. See Organising your folder.