Hi all,
I’m encountering two critical issues with PTGui Pro 13.3 on Windows 11 Pro that I haven’t been able to resolve after extensive troubleshooting. Hoping someone can shed some light on what might be happening.
Link to Google drive Containing Project files/Raws/Template/and Batch list
Issue 1 – Batch Stitcher Failing to Process Projects
The Batch Stitcher intermittently fails to stitch certain projects without providing a clear error message.
I’ve uploaded sample input files and project files here:
👉 Google Drive link
There doesn’t appear to be a consistent pattern — same template and similar input sets sometimes succeed and sometimes fail.
Issue 2 – Successful Batch Jobs Producing Distorted Output
For projects that do complete “successfully,” roughly 50% of the resulting TIFFs are unusable due to warping or exposure artifacts.
Representative examples:
IMG_20251111_110053_00_113.tif – Exposure seam artifact
IMG_20251111_110116_00_114.tif – Warped / skewed output
IMG_20251111_144414_00_274.tif – Warped / skewed
IMG_20251111_144454_00_275.tif – Severe distortion
IMG_20251111_150936_00_287.tif – Extreme warping
IMG_20251111_170323_00_325.tif – Severely distorted projection
Troubleshooting Steps Attempted
Performed a clean reinstall of PTGui Pro 13.3.
Deleted all templates and recreated them manually.
Tested using another operator’s template (same behavior).
Rolled back NVIDIA drivers to multiple previous versions.
Verified all input images are level
Avoided proximity to near-field objects and seam-critical content.
Confirmed system is idle during stitching to rule out resource contention.
Despite these steps, the problem persists across multiple projects and image sets.
System Configuration
CPU: Intel Core i9-13900KF
RAM: 32 GB DDR4 @ 4400 MT/s
Storage: 2× 2TB NVMe SSDs
GPU: NVIDIA RTX 4080 (multiple driver versions tested)
Additional Notes
The issue seems to have come out of nowhere.
All affected projects use the same camera and lens parameters that previously stitched without issue.
GPU acceleration is enabled.
CPU/GPU temps remain nominal during stitching.
If anyone has experienced similar instability in batch processing or can suggest specific diagnostic flags/logging options, I’d appreciate any guidance.
It would be particularly useful to know whether PTGui caches optimizer results per batch task or if corruption in a shared temporary file could cause inter-job warping.
Thanks in advance for any insight.
— Markos
