My normal processing routine is to perform steps 1 and 2, then run a LAStools script that reduces noise and removes many pointsin flat areas on the densified point cloud. Then I import it back into Pix4D and then generate the mosaic. This drastically speeds up mosaic generation and in some cases makes it possible at all when I have clouds over 1 billion points. In my opinion the resultant mosaic is better too.
With the most recent update (2.1.49 64-bit), Pix4D fails, saying the cloud is empty. I have viewed the cloud in CloudCompare and it looks excellent, with about 175,000 points, down from 55 million in the original. I have also tried saving the cloud as a LAS instead of a LAZ but there is no difference.
As a work-around I am using the full cloud.
Let me know if you need any project data for troubleshooting.
I have exactly the same problem, I have a project with 2500 photos data set and when the software finished the step 2 I get the same message and the process stopped. I am losing time and money in my projects due to this issue, I am going crazy trying to get god results and my customers are angry. This is not fair for something you paid. Please, what can be done? How can I get the previous version.
In your case you probably have too many points in your point cloud. I did a 2500 photo project earlier this year and had a little over 1 billion points, which Post Flight Terra 3D (the sensefly rebranded version of Pix4D) refused to load. I cleaned the cloud using LAStools and brought it down to 170 million points. Once loaded manually the mosaic was produced easily.
This method may not work now, though, as I have reported above.
Another option is to change densification options. Try image scale at Half Size and uncheck Multiscale. If that doesn’t work, change point density from optimal to Low (or High to Optimal, depending on where your settings are now.
I normally run my processing from a remote desktop and I needed to do some testing to ensure the remote desktop wasn’t the problem. I’m running Pix4D on my desktop right now as it happens and I tried loading a processed point cloud using the menu option and encountered the same problem.
Support told me to try dragging the point cloud from file manager into the layer tree while in the Ray Cloud editor, and then try step 3 processing again. I hadn’t actually tried it until just now and it does work.
So, Process > Import Point Cloud for DSM Generation is broken but there is a work-around.
Hi, I realize this is an old thread, but the problem still happens occasionally to us on different builds of the software.
Like the OP responses and other posts have said, be very careful using ‘multiscale’ and any greater density than 1/2 image (default) on Step 2… I think Pix4D has the ability to create bigger point clouds than it can read.
100% of the time- for us- we increase our RAM and we can then load the point cloud on Step 3.
here is a similar problem. Pix4D creates a point cloud (~ 2,5 billion points) but can not turn it in step3. It loads the points till 90 % an then aborts with message:
[ 99%RAM][ 3%CPU][Error]: >>>Load point cloud<<< failed with error (vector too long)!
As I tested here having the same problem, I was able to export a cloud that works with Global Mapper, but only if:
The cloud has UTM coordinates (in meters, not geographic degrees)
I chose not to include header information
I chose export version of LAZ 1.1
So, at least one of these three settings was a problem for PIX4D, i could not test many combinations because the cloud is big. But I suspect the main cause may be the UTM coordinates, as the external program was creating a cloud in WGS84 Geographic system.
Anyway… despite all the trouble of creating a cloud with very limited options, when the cloud is imported in Pix4D it goes way off place… it looks like Pix4d ability to import clouds is really bad. (I double checked with other softwares and the imported cloud is exactly at the same place as the cloud Pix4D exported, so, it should not be shifted when importing at all - I cannot say whether Pix4D shifts the cloud when exporting or when importing, anyway, it renders the feature useless)
Additionally, Pix4D is unable to import the very cloud it exported itself.
(My version is 4.7.5, the latest stable version in Aug/2022)
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.