企业入驻搜索写评价分类关于
简体中文English

Van Tran

加拿大

1 评价
2 被浏览
0 有帮助

1 条评价

Creality

Raptor scanner

Subject: CR-Scan Raptor Freezes During Scanning — Request for Assistance Hello Creality Support, I am requesting technical assistance with a brand-new Creality CR-Scan Raptor. I purchased the scanner and also purchased a new MSI laptop specifically to run the Raptor. The laptop has an AMD Ryzen 7 processor, 16 GB RAM, and an NVIDIA RTX 5060 Laptop GPU with 8 GB VRAM. The scanner is detected correctly by Windows and Creality Scan. Calibration was completed, and Preview works normally. However, when I start an actual scan, the software freezes after several seconds. I have spent approximately 5–6 hours troubleshooting this issue. I tested: * Creality Scan 4.3.1 and 4.3.2 * Blue Laser and Infrared scanning * Different scan resolutions * Different USB ports * Restarting the computer * Reinstalling the software * Recalibration * Direct USB connection with no hub * NVIDIA RTX 5060 GPU selected in Creality Scan The scanner is clearly communicating with the computer and capturing data before the freeze. For example, one scan reached approximately 1,114 frames, 118,093 points, 22 markers and 50 FPS before the scan stopped responding. The scanner temperature was only around 35–38°C, so overheating does not appear to be the problem. I have now returned the scanner to Canada Computers for diagnostic testing. They are keeping the scanner for several days and told me that if their testing confirms the scanner is defective, they will replace it. At this point, I would like Creality to advise: 1. Is this a known issue with the CR-Scan Raptor and Creality Scan? 2. Is there a known Windows 11, RTX 5060, driver, firmware, or software compatibility issue? 3. Is there a recommended fix that I have not already tried? 4. If the scanner is confirmed defective, should it be replaced with another Raptor? I purchased this scanner specifically for 3D scanning work and have already invested in a new computer to run it. I would appreciate a clear technical response rather than being directed through the same troubleshooting steps again.

2026-10-06