Sorry to make yet another post about this - I am processing 80-90 fields I flew over the last few weeks. These range in size from very small, to very large requiring multiple batteries.
The small fields, which are a real part of the portfolio, do not capture many images. The lack of side-overlap seems to be triggering a stall when doing high quality processing - right at 27%.
I’ve been lead to believe that the high quality processing provides more accurate results than the fast option - which leaves embarrassing and visible distortion in the orthomosaic.
I don’t remember having these issues on small fields in prior versions of the software - I am currently running V2.9.3.
Can the good people at Pix4D work on this, ASAP?
(Yes, I have a ticket opened late Friday, but I’ve had many more failures since I opened it and I believe this is a much bigger issue than it at first appears…)
-Mike
Hi Mike, we will keep helping you on the support ticket, we can’t do anything extra here.
I’ve had other fields fail - this is in danger of upsetting the business. I posted there because I thought other users may have information from their own uses - there are lots of variables..
We understand.
It seems you have Elevation optimization on when capturing the images. You can see this by checking the last images from a certain angle.
Removing these images allows PIX4Dfields to process correctly. Please disable this setting from the remote controller
Thank you, Jose for your super-fast analysis of my files and quick response. This is SUCH a good example of customer support!
I’ve tested this on several other fields and things are working again, by removing those files. I will update my workflow to remove Elevation Optimization when capturing fields.
I appreciate you,
-Mike
I have the save problem with Mavic 3 Multispectral. Everytime I check Elevation Optimization before my flight, when processing it in Pix4D it gets stucked.
I simply turn that option off, and I didn’t notice any significant difference in the results after the analysis.
Correct. Glad to know that fixed it for you, too!
-Mike