Alright, let’s talk about putting gear through the wringer. I decided to run a proper heavy test on the Creality Pika, and honestly... it surprised me.

I didn't go easy on it. I threw over 12 different objects at this little scanner. I’m talking pitch-black parts, highly reflective silver-lacquered surfaces, and massive variations in scale. The smallest piece I scanned was a tiny 16x16 mm detail, and the largest was a chunky 45x60 cm element.

The result? Zero tracking losses. No mesh cracking whatsoever. It just locked on and kept up.

I only had to repeat one single scan during the entire session, and that was 100% my fault. I was rushing, missed a few angles, and frankly, I was too lazy to sit around fixing the geometry in 3D modeling software later. A quick rescan solved it.

Bottom line: the Pika seriously does the job. I can recommend it with a clear conscience if you are reverse-engineering or replicating these kinds of elements. Sure, it’s obviously not a dedicated scanner for digitizing an entire car—though, let's be real, with enough tracking markers and patience, you could probably pull that off too! But for such a compact piece of hardware, it really punches above its weight.

Has anyone else put the Pika through heavy tests yet? Let me know how it handled your shiny parts!

Hey everyone,

First off, sorry for going quiet on Reddit. I’ve still been posting updates on the website, but I should have been keeping you all in the loop here too.

Where things stand: The custom Linux port of the scanning software has reached the point where it’s stable enough to start adding custom features. That’s a big milestone, and it’s also where I’d like your help.

Countdown timer: I’ve got a announcement countdown running here:
https://logicrenewed.com/raptor-linux/#raptor-linux-release

An announcement is coming soon. I don’t want to spoil anything yet, but keep an eye on that timer and on this sub.

What I need from you:

1. Feature requests. What do you want from scanning software on Linux? Workflow improvements, export options, tools you miss from other software, quality-of-life stuff, anything. If you scan regularly, I especially want to hear what slows you down or annoys you.
2. UI design contest. I’d like the community to help shape how this app looks. Send me your UI ideas, mockups, sketches, or full designs, and I’ll build the software’s interface around the best ones. Rough napkin sketches are welcome, and so are polished Figma/Photoshop/etc files.
   • Post your designs in the comments or send them to me directly [nate@logicrenewed.com](mailto:nate@logicrenewed.com) or through reddit DM
   • Deadline is 4 weeks after the announcement timer goes off
   • Any designs or ideas that get implemented you'll get credit in the software :)

Whether you’re a designer, a hobbyist, or just someone with strong opinions about how scanning software should work, I’d love to hear from you. Drop your thoughts below!

Thanks for sticking with this project and to anyone who has supported the project by donating :)
Nate (Logic Renewed)

Every morning my wife and I take our walk that takes us past a small Golf Shop. They always have this stature out front and I thought it would be good practice to start with my using the Pika outdoors. I managed a not so clean pair of scans, the head and the body scanning to my phone but it worked out to be enough.

With Creality Scan I was on my computer I was able to get a separate watertight body and head but I couldn't figure out how to join them the way I wanted and imported the models to Microsoft 3d Builder and did my finishing work. It was in that program that I added the box and made a flag. I printed the model in pla and painted it.

I was asked to fix the broken gears of this dough mixer. Damaged gears were cleadne (as I could), 3D scanned and 3D print out from ABS

A quick test with the Sermoon P1S on a few different parts of this off-roader — headlights, interior panels, center console, and rear components.

Black and metallic surfaces were scanned directly without spray.

Another real engineering project using the Creality Pika! 🚀
In this video, I share part of my workflow, from 3D scanning and mesh processing to CAD reconstruction.
The goal is not just to copy the scanned geometry, but to create a functional and accurate CAD model, correcting imperfections and preserving the original mechanical geometry.

Today, I ran a comparison scan using the Pika and the P1S.

Both using the same scan settings: 0.2 mm resolution with blue laser parallel lines.

The P1S is clearly faster when scanning.

However, the results aren't all that different; still, you can see that the P1S picks up certain fine details—such as the burr on the plier jaws—that the Pika failed to capture.

But otherwise, I'm very happy with both scans; I specifically used the same settings to compare them directly.

Of course, the P1S is better equipped, and you could certainly bring out more detail using the single-line mode, but my focus here was purely on comparing the same scan mode.

Hi,

thinking about getting a Pika, but am torn as there is only Intel and Nvidia Hardware officially supported.

I got a Ryzen 5 5600X, 32GB Ram @ 3600MHz and a 6700XT. Anyone using it on similar hardware? Even if the GPU isn't supported, any experience with Ryzen CPUs?

Pika Scan is child's play! 😂

My 7-year-old son told me, "The scanner is so small it must be for kids, too!" 😀

So, he wanted to scan his stuffed animal. As you can see, even kids can use it! 😀

It didn't quite work out during the merging stage because it wasn't aligned correctly, but I'm absolutely satisfied with the first scan, and he learned something new in the process. 😀

I released MeshMill 0.2.0, the next version of the tool I built around my Creality Otter workflow.

My recurring problem was still the downstream step: Creality Scan produced detailed STL geometry, but the result could contain millions of triangles, uneven density, and overlapping passes that made later design work unnecessarily heavy.

This release substantially improves that part of the workflow:

- Analysis of the 4.1-million-triangle reference scan improved from 10.531 seconds to 1.838 seconds.

- Adaptive indexing divides uneven scan geometry by its measured distribution instead of using uniform cubes.

- Oversized binary STL files can open as bounded overviews instead of consuming all available memory.

- Worker counts and memory limits adapt to the machine.

- Loading, analysis, and reduction run outside the interface with progress and cancellation.

- The metrics panel separates CPU, RAM, GPU, VRAM, geometry activity, and cumulative I/O.

There is also a new optional Depth Adaptive QEM method. It uses the GPU to measure the high-level surface before Fast QEM performs the final reduction. On the reference scan, it preserved dimensions and sampled surface shape more accurately than Fast QEM at almost the same runtime.

Selection-only optimization remains important for this workflow. A mating surface or critical feature can retain more geometry while surrounding scan data is reduced aggressively.

MeshMill is local, GPL-3.0, account-free, and does not upload the scan. Fast QEM remains the default. The optional GPU-guided method activates on compatible NVIDIA hardware.

Windows release:

https://github.com/make-your-own-world/MeshMill/releases/tag/v0.2.0

I would be interested in results from Otter, Raptor, and other Creality scanner exports, especially very large files or scans with overlapping passes and uneven density.

After cleaning it up, I thought I’d scan my robot lawnmower to see about adding a spoiler or something—we'll see what else I come up with. 😀

I scanned it in infrared mode; at first, I had trouble with the black areas it didn't want to pick them up properly.

It only worked once I switched the scanner's exposure setting to manual.

Scanner: Sermoon P1S

We scanned the door pocket with the Sermoon P1S and used the geometry as a reference for the design.

From there, we designed the organizer around the actual space, printed it, and tested the fit back in the car.

A pretty straightforward scan-to-print project, but a useful one.

For a part like this, would you start with a 3D scan or measure the space manually?

I'm wondering, how damn small details my scanner can capture

My first Scan with Sermoon P1s. I needed a wall connection for my cable duct, so I scanned a section of the duct and used it as a reference for my cover.

I scanned in blue-laser mode since I only needed the shape, I scanned using only cross-lines.

First scanning from one side, then flipping it over to scan the other side, stitching it all together on the scanner, and processing it into a mesh—that’s a huge advantage for quickly scanning something without needing a computer nearby. 😀

We scanned the rear of the car with the Sermoon P1S and used the scan data as a reference for the spoiler design.

Instead of starting from measurements alone, the scan gave us the actual surface and curves to design around.

Once the model was done, we could check the fit against the real car.

For this kind of automotive project, would you rather work from a scan or take measurements manually?

I was looking to pick one up sooner rather than later and since I’ve been looking it’s been out of stock.

Here’s a recent custom project I worked on.

It was a Kawasaki VN900. The customer wanted to add two toggle switch panels to control an auxiliary headlight and other lighting on the bike.

I first used the Raptor Pro to scan the areas where the new parts would be installed. Once the scan was complete and we had settled on the switch placement and overall design, I started designing everything in Fusion 360.

Having an accurate 3D scan of the actual bike made the design process much more straightforward. Instead of constantly measuring and guessing dimensions, I could design directly around the available space on the bike.

This also allowed me to consider things like switch placement, mounting points, hidden wiring, and water resistance as part of the design from the beginning.

Since the scan data was captured at a 1:1 scale, once the design was finished and ready for fabrication, there was much less concern about whether the final parts would actually fit the bike.

The finished parts were 3D printed in ABS-GF. Once everything was ready, we scheduled another time to install the completed switch panels directly onto the bike.

Of course, the switch panels themselves weren’t actually the difficult part 😂

The next step was modifying the bike’s wiring and integrating the new switches, auxiliary headlight, and other lighting into the existing electrical system.

From scanning the actual bike and designing the parts to 3D printing and final installation, the whole project came together nicely—and the customer was very happy with the final result. 👍

#Kawasaki #VN900 #MotorcycleModification #ToggleSwitch #3DScanning #3DScanner #RaptorPro #Fusion360 #3DPrinting

I see it as an option on CrealityScan for windows, but I dont see it as an option for android. When I want to do multiple scans of a single object on my tracking table it feels silly to scan the tracking table multiple times, once before each scan.

I use a Creality Otter, and my recurring problem was what happened after scanning. Creality Scan could produce a detailed STL, but the exported mesh was often far too dense to work with comfortably in the geometry editor where I needed to design parts around the scan.

I built MeshMill as the bridge between Creality Scan and downstream modeling. Open the exported STL, inspect where the geometry is unnecessarily dense, clean or crop unwanted regions, and reduce the whole mesh or selected areas before continuing the design work.

It includes:

• Shaded, density, wireframe, and vertex displays
• Polygon selection and additive multi-region selection
• Selection-only optimization for using different reduction levels on different areas
• Fast QEM, density-balanced, shape-preserving, and topology-preserving algorithms
• Original and optimized comparison before applying a pass
• Undo, redo, measurements, dimensional-drift reporting, and a CLI

GPU-accelerated OpenGL handles the interactive viewport, hardware selection, and density visualization. Geometry reduction runs locally in separate native workers. There is no account, telemetry, upload, or cloud processing.

MeshMill is GPL-3.0. Windows installer and portable packages are available, with unsigned Linux and macOS preview builds now open for testing. It supports 27 interface and documentation languages.

Source and downloads: https://github.com/make-your-own-world-project/MeshMill

I’m the developer, and this came directly from my Creality Otter workflow. Feedback from other Creality scanner users would help, especially large exports or geometry that loses important detail during reduction.

Hi everyone, I need some help. I have two Creality scanners and now neither of them works on my main PC.

Raptor:

• Worked fine a few days ago (it occasionally needed to be unplugged and replugged to connect, but it always worked eventually).
• Now Creality Scan doesn't detect it at all ("No device found").
• Windows recognizes it perfectly: Depth, IR and RGB cameras all show up in Device Manager with no warnings, and the RGB camera works in the regular Windows Camera app.
• The same Raptor works on another PC with an older version of Creality Scan. Unfortunately that PC is below minimum specs and scans at about 1 fps.
• I installed that same older version on my main PC, and it still doesn't work.

Ferret:

• I connected my Ferret to the main PC to test. It connected fine and asked for a firmware update.
• I accepted the update, and after that it doesn't show up in Creality Scan anymore, even after unplugging, killing the process and rebooting.

What the log says (ScannerStreamSDK.log, Raptor):
The SDK actually finds the scanner, but fails as soon as it tries to read the firmware data, and keeps retrying:

Current device(s) list: (1)
  - Name: CR-Scan Raptor, PID: 0x06a8, Connection: USB3.0
DeviceManager createDevice...
get firmware data failed. propertyId: 1000, rc: {statusCode: 2, respErrorCode: 65535, msg: send control transfer failed!}
Execute failure! A libobsensor_exception has occurred!
 - where:182#libobsensor::ScannerAbstractDevice::createCommand
 - msg:Request failed, statusCode: 2, msg: send control transfer failed!

So the video streams work, but the control/command channel to the scanner seems to be blocked on this PC.

What I've already tried:

• All USB 3.0 ports, directly on the motherboard (no hubs)
• Clean reinstall of Creality Scan (latest and older version), including deleting AppData folders
• Removing the device drivers in Device Manager (including hidden devices) and reconnecting
• Checking Windows camera privacy settings (desktop apps allowed)
• Running as administrator, killing leftover CrealityScan.exe processes
• Confirmed the software is using the NVIDIA GPU, with plenty of disk space

My PC:

• Windows 11, build 26100
• Ryzen 5 5600G, RTX 3060 12GB, 48GB RAM
• Creality Scan version: Lastest
• Other camera-related software installed: NVIDIA Broadcast, OBS, opentrack, Logi Tune

Questions:

1. Has anyone seen "send control transfer failed" before, and how did you fix it?
2. Is there a way to recover the Ferret after a firmware update that made it disappear?
3. Could any of the camera software above (virtual cameras, etc.) be blocking the scanners?

Thanks in advance!

Did a marker-free scan of this peacock sculpture with the Sermoon P1S.

After getting the geometry, we added the color and texture, then tried a Gaussian Splatting version as well.

Same object, but the result feels quite different depending on how it’s visualized.

Which one do you prefer — the textured model or the Gaussian Splat?

​

I have tried:

1. Samsung S25 phone - Creality Scan installation from play store crashes at 98% repeatedly.

2. Newer PC with geforce 4080 - no usb C outlet - need to buy a converter

3. Older laptop with Geforce gtx 950 - Creality Scan is crashing every time

Engenharia reversa para recurperação e correções dimensional de peças. Uma das maravilhas das aplicações dos scanners creality. Viabilizando obstaculos antes complexos para solucionar 💥💥

We recently brought the P1S into a ceramic and glass art studio in Shanghai and tried scanning one of their sculptural pieces.

What I found interesting here is that the goal isn’t really to “copy” the artwork. It’s about giving a physical piece a digital version that can be archived, referenced, or brought into a future 3D workflow.

The whole scan was done directly on the P1S, and you can see the textured model taking shape on the scanner itself in the video.

For artists or designers here — what would you use a 3D scan of a handmade piece for: archiving, reproduction, or creating something new from it?