| Previous | Next |
The following description shows the minimum and recommended hardware and software requirements.
Minimum
- Windows 10, 64 bits (PC or Mac computers using Boot Camp). (Windows 10 and Windows 11*)
- CPU (Intel i5/ i7/ Ryzen 7).
- GPU that is compatible with OpenGL 3.2. (integrated graphics cards Intel HD 4000 or above).
- Small projects (under 100 images at 14 MP): 4 GB RAM, 10 GB HDD Free Space.
- Medium projects (between 100 and 500 images at 14 MP): 8 GB RAM, 20 GB HDD Free Space.
- Large projects (between 500 and 1000 images at 14 MP): 16 GB RAM, 40 GB HDD Free Space.
- Very Large projects (1000 -2000 images at 14 MP): 32 GB RAM, 80 GB HDD Free Space.
- For larger projects take a look at PIX4Dmatic here.
Important: Unusually long times have been observed when processing with some Quadro GPU. This is related to some settings in the NVIDIA control panel. For more information: Long Processing Time for Step 3 with Quadro GPUs.
Recommended
- Windows 10, 64 bits (Windows 11 is not supported yet).
- CPU quad-core or hexa-core Intel i9/Threadripper/Ryzen 9/.
- GeForce GTX GPU compatible with OpenGL 3.2 and 2 GB RAM.
- Hard disk: SSD.
- Small projects (under 100 images at 14 MP): 8 GB RAM, 15 GB SSD Free Space.
- Medium projects (between 100 and 500 images at 14 MP): 16GB RAM, 30 GB SSD Free Space.
- Large projects (over 500- 1000 images at 14 MP): 32 GB RAM, 60 GB SSD Free Space.
- Very Large projects (1000 - 2000 images at 14 MP): 64 GB RAM, 120 GB SSD Free Space.
- For larger projects take a look at PIX4Dmatic here.
Important: Docker or any other virtualization/containerization is not part of the PIX4Dengine (although it may run in it) and so it is not included in Pix4D support. Make sure the HTTPs requests (our communication also uses TLS1.2 for message encryption) make it through your platform to https://cloud.pix4d.com/ All the protocols we use are all 100% industry standard with no customization. We do not recommend using the deep packet scanning.
Article feedback (for troubleshooting, post here instead)
0 comments