At least my drifting problem is resolved.Question:
I only be able make 2 short flights at night....for those who had drfting problems on 1.4, are they solved on this new 1.5?
Im still not 100% sure......
weird....try reset all camps on photo mode, in settings ;-)
Thanks for the feedback about 1.5 drifting, guys!
1.5.3 still allows for a downgrade to 1.4.1, correct? If you suspect it is FW related on your original Phantom and your replacement Phantom, perhaps try to downgrade to 1.4.1 and check it out there.I've reset all camera settings and the RAW photos are still unacceptable. I believe there's an issue upgrading directly from 1.3 to 1.5 as this is the second P3P that it happened to. I might exchange this unit for another. Hopefully DJI can get this sorted out.
1.5.3 still allows for a downgrade to 1.4.1, correct? If you suspect it is FW related on your original Phantom and your replacement Phantom, perhaps try to downgrade to 1.4.1 and check it out there.
P.S. - I like your username if it means what I think it means. Tagalog?
This looks a little like the clipping warnings you get in adobe camera raw. Check your setting if you are using camera rawi just purchased a p3, and it had 1.3 installed. everything was fine. i upgraded to 1.5 and my RAW photos had blue and magenta pixels in the underexposed dark areas of the photograph. i thought my sensor had gone bad, so i exchanged the quadcopter for a new one. with the new one, in 1.3 RAW images were fine, then i upgraded to 1.5 and the pixellation was back, resulting in unusable photos. i've tried using the cleaner app which made things worse. anyone else experience this issue?
photo 1 - RAW with pixelation
![]()
photo 2 JPG with no pixelation from same shot
![]()
photo 3 RAW with pixelation at bottom
![]()
This looks a little like the clipping warnings you get in adobe camera raw. Check your setting if you are using camera raw
Who cares if the gimbal vibrates as long as the video is stable.As I posted in the other thread. I did get the gimbal vibration after updating to 1.5 last night. I downgraded back to 1.4 and problem disappeared.
We use essential cookies to make this site work, and optional cookies to enhance your experience.