New firmware updates available for Nikon Coolpix S6800, S6600, S5300, P520 and P330 cameras
Today Nikon released firmware updates for five different Coolpix cameras that include various fixes:
Firmware update v1.1 for Nikon Coolpix S6800
- An issue that meant in some rare cases after a lens error occurred the camera could not recover even when it was turned off and then on again has been resolved.
Firmware update v1.1 for Nikon Coolpix S6600
- An issue that meant in some rare cases after a lens error occurred the camera could not recover even when it was turned off and then on again has been resolved.
Firmware update v1.1 for Nikon Coolpix S5300
- An issue that meant in some rare cases after a lens error occurred the camera could not recover even when it was turned off and then on again has been resolved.
Firmware update v1.1 for Nikon Coolpix P520
- When the camera was turned off after taking a still picture with GPS options > Record GPS data set to On, in some rare cases, the camera could not be turned on again. This issue has been resolved.
- After shooting using subject tracking with AF area mode set to Subject tracking, the monitor display turned completely black, or partly white. Also the buttons and controls failed to respond. This issue has been resolved.
Firmware update v1.1 for Nikon Coolpix P330
- When the camera was turned off after taking a still picture with GPS options > Record GPS data set to On, in some rare cases, the camera could not be turned on again. This issue has been resolved.
- After shooting using subject tracking with AF area mode set to Subject tracking, the monitor display turned completely black, or partly white. Also the buttons and controls failed to respond. This issue has been resolved.
- When White balance was set to Fluorescent FL1 (white fluorescent), Fluorescent FL2 (daylight white/neutral fluorescent), or Fluorescent FL3 (daylight fluorescent) in the RAW (NRW) processing parameters screen, colors in the preview display and in JPEG images created with RAW (NRW) processing were incorrect. This issue has been resolved.