Part of our INSYDIUM Fused Collection, X-Particles is a fully-featured advanced particle and VFX system for Maxon’s Cinema 4D. Its unique rule system of Questions and Actions enables complete control over particle simulations.
Part of our INSYDIUM Fused Collection, X-Particles is a fully-featured advanced particle and VFX system for Maxon’s Cinema 4D. Its unique rule system of Questions and Actions enables complete control over particle simulations.
Example: Alcor AU6476 supports firmware upgrade via custom vendor request ( bmRequestType=0x40 , bRequest=0xA0 ). Reverse engineering the Windows update tool ( AlcorFwUpdate.exe ) reveals the protocol. For AU9214, the default baud rate is often 9600 8N1. Use a logic analyzer on TX/RX pins or socat on Linux:
lsusb -d 058f: -v | grep -E "idVendor|idProduct|bDeviceClass|bInterfaceClass" : Use USBDeview or Wireshark with USBPcap. Step 2 – Force class driver If the device is a card reader but appears generic: alcor micro usbdev
When plugged in, these enumerate as a with multiple interfaces — each memory slot appears as a separate logical unit (LUN). Without proper drivers, Windows sees the top-level device as “Alcor Micro USB Dev.” Example: Alcor AU6476 supports firmware upgrade via custom
| Chip | USB VID:PID | Description | |------------|-------------|------------------------------------------| | AU6370 | 058f:6377 | USB 2.0 SD/MMC/MS single-slot reader | | AU6366 | 058f:6366 | Multi-LUN reader (up to 4 slots) | | AU6476 | 058f:6476 | USB 3.0 + SD 4.0 (UHS-II) | Use a logic analyzer on TX/RX pins or
Introduction: The Unseen Workhorse If you have ever plugged in a budget USB hub, a no-name barcode scanner, a multi-format memory card reader, or a legacy serial adapter on an industrial PC, chances are you have unknowingly used a chip from Alcor Micro Corp . While not a household name like FTDI or Silicon Labs, Alcor Micro’s USB controllers are quietly embedded in millions of peripherals worldwide. The device that often appears in system information as “Alcor Micro USB Dev” or “Alcor Micro USB Card Reader” is a fascinating case study in low-cost, high-volume USB bridge design.
# Linux: unbind generic driver, bind usb-storage echo -n "1-2:1.0" > /sys/bus/usb/drivers/usb/unbind echo -n "1-2:1.0" > /sys/bus/usb/drivers/usb-storage/bind Many Alcor readers store firmware in SPI flash or internal ROM. Using dfu-util (if DFU class implemented) or fwupd (Linux Vendor Firmware Service) may detect it.
Example: Alcor AU6476 supports firmware upgrade via custom vendor request ( bmRequestType=0x40 , bRequest=0xA0 ). Reverse engineering the Windows update tool ( AlcorFwUpdate.exe ) reveals the protocol. For AU9214, the default baud rate is often 9600 8N1. Use a logic analyzer on TX/RX pins or socat on Linux:
lsusb -d 058f: -v | grep -E "idVendor|idProduct|bDeviceClass|bInterfaceClass" : Use USBDeview or Wireshark with USBPcap. Step 2 – Force class driver If the device is a card reader but appears generic:
When plugged in, these enumerate as a with multiple interfaces — each memory slot appears as a separate logical unit (LUN). Without proper drivers, Windows sees the top-level device as “Alcor Micro USB Dev.”
| Chip | USB VID:PID | Description | |------------|-------------|------------------------------------------| | AU6370 | 058f:6377 | USB 2.0 SD/MMC/MS single-slot reader | | AU6366 | 058f:6366 | Multi-LUN reader (up to 4 slots) | | AU6476 | 058f:6476 | USB 3.0 + SD 4.0 (UHS-II) |
Introduction: The Unseen Workhorse If you have ever plugged in a budget USB hub, a no-name barcode scanner, a multi-format memory card reader, or a legacy serial adapter on an industrial PC, chances are you have unknowingly used a chip from Alcor Micro Corp . While not a household name like FTDI or Silicon Labs, Alcor Micro’s USB controllers are quietly embedded in millions of peripherals worldwide. The device that often appears in system information as “Alcor Micro USB Dev” or “Alcor Micro USB Card Reader” is a fascinating case study in low-cost, high-volume USB bridge design.
# Linux: unbind generic driver, bind usb-storage echo -n "1-2:1.0" > /sys/bus/usb/drivers/usb/unbind echo -n "1-2:1.0" > /sys/bus/usb/drivers/usb-storage/bind Many Alcor readers store firmware in SPI flash or internal ROM. Using dfu-util (if DFU class implemented) or fwupd (Linux Vendor Firmware Service) may detect it.
xpScatter enables you to scatter your objects over multiple scene geometry, from splines to parametric objects all at the same time.
The topology tab will enable you to distribute your scatter on landscape slope, height, and curvature to create realistic ecosystems.
Animate your growth by using textures, X-Particles modifiers, and Mograph effectors.
Use multiple display modes for fast viewport performance. You can even restrict the scatter of objects to within the camera field of vision for optimal efficiency.
Our time and custom spline retiming option give you fine control over playback. The new cache layers in xpCache enables you to lock and unlock to re-cache objects in your scene.
X-Particles is built seamlessly into Cinema 4D like it is part of the application. It’s compatible with the existing particle modifiers, object deformers, Mograph effectors, Hair module, native Thinking Particles, and works with the dynamics system in R14 and later.
If you know how to use the Mograph module, you already know how to use X-Particles, it's that easy.
X-Particles has the most advanced particle rendering solution on the market. It enables you to render particles, splines, smoke and fire, all within the Cinema 4D renderer. Included are a range of shaders for sprites, particle wet maps and skinning colors. You can even use sound to texture your objects.
Perfectly partnered with INSYDIUM’s Cycles 4D and also compatible with the following:
