Z8 focus issue after 3.0 firmware update

[James Grove]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

James does this work when they add new line items such as the focus limiter. Your process makes sense. Just curious.

Yes I do the same for my Z9 as well.

Save my current settings to the CF Card

Copy the new firmware to a separate CF card

Update the camera

Reset the camera to defaults

Put my setting card back into the camera and reload them into the camera.

Turn the camera off and back on and then resave them.

Not had any issues. Hope that helps.

 

[sirhawkeye64]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware file particularly if things got rearranged in the menus, which seems that it can happen from time to time, so I always have historically had two backups -- one with just my copyright but otherwise default settings for the camera (as the copyright/author location/menu doesn't change between updates--it's always in the "settings"/wrench icon). And then a second settings backup with all of my settings (shooting banks, etc).

Now that I'm thinking about this -- Nikon probably has a way to "map" items from previous firmwares to new firmware versions if menu items have changed (ie. new items have been added and thus the menu item "position" changes).

--
* PLEASE NOTE: I generally unsubscribe from forums/comments after a period of time has passed, so if I do not respond, that is likely the reason. *

 

[Leonard Shepherd]

My setup: Z8 FW3.0, MC 105 LF 1.10, AF-S using shutter half press to focus, sIngle point, and I cannot reproduce your camera's behaviour. AF starts without hesitation, it takes a little longer at closeup distances fo actually find focus, but that is normal.

+1.

Perhaps a time coincidence – often (but not always) carefully cleaning the body and lens throat contacts resolves an auto focus issue

 

[PLShutterbug]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware

Firmware files don’t “read” other firmware files while upgrading - or downgrading. They simply replace all the system files in the system partition with new files, probably after wiping out everything already there.

So downgrading to 2.10 just replaces 3 with 2.1, just like upgrading replaces 2.1 with 3.

file particularly if things got rearranged in the menus, which seems that it can happen from time to time,

When have you experienced this? I never have. I think Nikon is smarter than that.

Now that I'm thinking about this -- Nikon probably has a way to "map" items from previous firmwares to new firmware versions if menu items have changed (ie. new items have been added and thus the menu item "position" changes).

Yes, they do. That’s why uogrades almost always work, and if they fail they are almost always due to user error.

 

[shuncheung]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware

Firmware files don’t “read” other firmware files while upgrading - or downgrading. They simply replace all the system files in the system partition with new files, probably after wiping out everything already there.

So downgrading to 2.10 just replaces 3 with 2.1, just like upgrading replaces 2.1 with 3.

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

 

[PLShutterbug]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware

Firmware files don’t “read” other firmware files while upgrading - or downgrading. They simply replace all the system files in the system partition with new files, probably after wiping out everything already there.

So downgrading to 2.10 just replaces 3 with 2.1, just like upgrading replaces 2.1 with 3.

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

 

[shuncheung]

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

The problem is that when Nikon introduces a major version of the firmware, they would insert new options into the middle of a list. For example, if Custom Settings D has 1 to 15, Nikon sometimes sticks new settings 12 and 13 into the middle of the original list, thus bumping the original d12 to d15 to d14 to d17. I.e., the old d12 is now the new d14, and the old d14 is now d16 .... Meanwhile, the new d12 is something completely new. It can be confusing.

 

[James Grove]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware file particularly if things got rearranged in the menus, which seems that it can happen from time to time, so I always have historically had two backups -- one with just my copyright but otherwise default settings for the camera (as the copyright/author location/menu doesn't change between updates--it's always in the "settings"/wrench icon). And then a second settings backup with all of my settings (shooting banks, etc).

Now that I'm thinking about this -- Nikon probably has a way to "map" items from previous firmwares to new firmware versions if menu items have changed (ie. new items have been added and thus the menu item "position" changes).

Never had an issue following the method I have posted. Pretty sure Nikon wouldn't want to mess that up as many people use the settings files, given how complex the cameras are.

I also keep a spreadsheet in case it does go Pete tong,

 

[Snapshotx7]

I had a problem with the 3.0 firmware on my first outing. I enabled the focus limiter feature and afterwards I could not change any settings with my buttons. Couldn't change ISO, shutter speed, aperture, anything. The i menu items also became blacked out. I tried turning the camera on and off. I tried different banks. Nothing worked. Fortunately I saved all my settings already. I reset all the camera settings, the loaded my saved settings and everything has been working since. This was the first firmware I've updated to with any hiccups. The firmware was installed without a lens attached on a full battery and while plugged in to a compatible PD charger.

 

[Pierre Lagarde]

I had a problem with the 3.0 firmware on my first outing. I enabled the focus limiter feature and afterwards I could not change any settings with my buttons. Couldn't change ISO, shutter speed, aperture, anything. The i menu items also became blacked out. I tried turning the camera on and off. I tried different banks. Nothing worked. Fortunately I saved all my settings already. I reset all the camera settings, the loaded my saved settings and everything has been working since. This was the first firmware I've updated to with any hiccups. The firmware was installed without a lens attached on a full battery and while plugged in to a compatible PD charger.

The only thing you need is a fully charged battery (ideally, a Nikon one), and no third party lens attached to the camera (may it be directly or with FTZ adapter). Having no lens is not mandatory and I even think it's probably better to let your most used Z lens on the camera with the usual configuration used with it.

Also, not sure, but, to my sense, PD charger attached while updating won't help with ensuring the process, and could probably even be a source of disturbance. Anyway, using any charger while updating is not something present in Nikon's recommendations.

Since the beginning I use Z cameras, I always followed this exact process, nothing more, nothing less (with a different computer, though ) and never had issues :

https://www.nikonusa.com/learn-and-...QJCU9b1olgyF1WojX4Cr-QAUTGwK_FqM_mRvvRoZGzbZS

 

[PLShutterbug]

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

The problem is that when Nikon introduces a major version of the firmware, they would insert new options into the middle of a list. For example, if Custom Settings D has 1 to 15, Nikon sometimes sticks new settings 12 and 13 into the middle of the original list, thus bumping the original d12 to d15 to d14 to d17. I.e., the old d12 is now the new d14, and the old d14 is now d16 .... Meanwhile, the new d12 is something completely new. It can be confusing.

Right. And they change wording, which further confuses things.

The way to “solve” this and maintain compatibility up and down is to assign each menu option a unique, non-changing ID. Then you can re-jigger the list up and down and it still works - at least in theory. However, it requires R&D and then maintenance for the relatively rare need to downgrade while maintaining all settings. It is more economical to simply replace the menu list wholesale and concerned users save old before upgrading so they can revert and restore.

 

[PLShutterbug]

I had a problem with the 3.0 firmware on my first outing. I enabled the focus limiter feature and afterwards I could not change any settings with my buttons. Couldn't change ISO, shutter speed, aperture, anything. The i menu items also became blacked out. I tried turning the camera on and off. I tried different banks. Nothing worked. Fortunately I saved all my settings already. I reset all the camera settings, the loaded my saved settings and everything has been working since. This was the first firmware I've updated to with any hiccups. The firmware was installed without a lens attached on a full battery and while plugged in to a compatible PD charger.

The only thing you need is a fully charged battery (ideally, a Nikon one), and no third party lens attached to the camera (may it be directly or with FTZ adapter). Having no lens is not mandatory and I even think it's probably better to let your most used Z lens on the camera with the usual configuration used with it.

Also, not sure, but, to my sense, PD charger attached while updating won't help with ensuring the process, and could probably even be a source of disturbance. Anyway, using any charger while updating is not something present in Nikon's recommendations.

Since the beginning I use Z cameras, I always followed this exact process, nothing more, nothing less (with a different computer, though ) and never had issues :

https://www.nikonusa.com/learn-and-...QJCU9b1olgyF1WojX4Cr-QAUTGwK_FqM_mRvvRoZGzbZS

Does that video describe unpacking the .bin file from a downloaded .exe? That step is no longer necessary so hopefully they have updated the video.

 

[Pierre Lagarde]

I had a problem with the 3.0 firmware on my first outing. I enabled the focus limiter feature and afterwards I could not change any settings with my buttons. Couldn't change ISO, shutter speed, aperture, anything. The i menu items also became blacked out. I tried turning the camera on and off. I tried different banks. Nothing worked. Fortunately I saved all my settings already. I reset all the camera settings, the loaded my saved settings and everything has been working since. This was the first firmware I've updated to with any hiccups. The firmware was installed without a lens attached on a full battery and while plugged in to a compatible PD charger.

The only thing you need is a fully charged battery (ideally, a Nikon one), and no third party lens attached to the camera (may it be directly or with FTZ adapter). Having no lens is not mandatory and I even think it's probably better to let your most used Z lens on the camera with the usual configuration used with it.

Also, not sure, but, to my sense, PD charger attached while updating won't help with ensuring the process, and could probably even be a source of disturbance. Anyway, using any charger while updating is not something present in Nikon's recommendations.

Since the beginning I use Z cameras, I always followed this exact process, nothing more, nothing less (with a different computer, though ) and never had issues :

https://www.nikonusa.com/learn-and-...QJCU9b1olgyF1WojX4Cr-QAUTGwK_FqM_mRvvRoZGzbZS

Does that video describe unpacking the .bin file from a downloaded .exe? That step is no longer necessary so hopefully they have updated the video.

It's the Mac version. Still indeed, the dmg should be no more in the pipe, but as it shows that you only have to copy the ".bin" to the card, it's the right way.

Even if I agree they should update it to the last direct ".bin" download way.

 

[sirhawkeye64]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware

Firmware files don’t “read” other firmware files while upgrading - or downgrading. They simply replace all the system files in the system partition with new files, probably after wiping out everything already there.

So downgrading to 2.10 just replaces 3 with 2.1, just like upgrading replaces 2.1 with 3.

No, here I mean the settings files you might save to a card from a previous version (like v2.10) and then load onto v3.00 after update.

file particularly if things got rearranged in the menus, which seems that it can happen from time to time,

When have you experienced this? I never have. I think Nikon is smarter than that.

I think in some of the updates, new items were added but I'm not sure if existing menu items were renumbered or if the new items just get appended to the appropriate section within the Custom menu settings for example (A, B, C, etc).

Now that I'm thinking about this -- Nikon probably has a way to "map" items from previous firmwares to new firmware versions if menu items have changed (ie. new items have been added and thus the menu item "position" changes).

Yes, they do. That’s why uogrades almost always work, and if they fail they are almost always due to user error.

--
* PLEASE NOTE: I generally unsubscribe from forums/comments after a period of time has passed, so if I do not respond, that is likely the reason. *

 

[sirhawkeye64]

I have not had any problems, but always save my settings, update the firmware, then fully reset the camera and then re load my settings.

Have you ever run into issue when restoring a firmware from an older "major" release? Such as restoring firmware from v2.10 onto a camera with v3.00 installed? I always had this concern that major firmware updates (2.xx, 3.xx) would not necessarily read a former firmware

Firmware files don’t “read” other firmware files while upgrading - or downgrading. They simply replace all the system files in the system partition with new files, probably after wiping out everything already there.

So downgrading to 2.10 just replaces 3 with 2.1, just like upgrading replaces 2.1 with 3.

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

No I mostly mean when upgrading. I didn't know if maybe reading a settings file from v2.10 for example on v3.00 could pose a problem, when new menu items were added. However, as I mentioned in my recently reply to this, new items may just be appended to the existing menu items so nothing may be renumbered and thus not an issue. That was my biggest concern. Although thinking about this, my guess is IF there happens to be a discrepancy in the settings file (ie. a menu item has a now "invalid" value) the camera just resorts to its default value for that menu item when restoring settings.

 

[Joshua Ziff]

My setup: Z8 FW3.0, MC 105 LF 1.10, AF-S using shutter half press to focus, sIngle point, and I cannot reproduce your camera's behaviour. AF starts without hesitation, it takes a little longer at closeup distances fo actually find focus, but that is normal.

+1.

Perhaps a time coincidence – often (but not always) carefully cleaning the body and lens throat contacts resolves an auto focus issue

+2

Me, too. No problems.

 

[arniebook]

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

The problem is that when Nikon introduces a major version of the firmware, they would insert new options into the middle of a list. For example, if Custom Settings D has 1 to 15, Nikon sometimes sticks new settings 12 and 13 into the middle of the original list, thus bumping the original d12 to d15 to d14 to d17. I.e., the old d12 is now the new d14, and the old d14 is now d16 .... Meanwhile, the new d12 is something completely new. It can be confusing.

Disclaimer … I Have not, yet, updated my Z8, and reading through this thread, I am feeling reluctant to do so … at least, until I see nothing but "joy and happiness" threads about FW 3.0.

That said, and armed only with the knowledge I have learned from reading this thread, I see a possible problem (and maybe a solution for the OP) that relates to your, above (and brilliant) example.

Using your example … Suppose the OP has “d12” set to some value other than the default or OFF. But, suppose in the update, the “new d12”, is now the new focus limiter feature, and because of some overlooked “glitch” in the mapping, the camera has used the OP’s “d12” setting, which has inadvertently activated the feature, affecting the AF on the OP’s Z8. Perhaps, the OP should find the new feature in the menu, and make sure it is turned off.

--
What we spend on this stuff is equal to the depth of our pockets squared ($²) times what we (j)ustify in our minds as to what we expect to do with our pictures plus (+) the (e)njoyment we experience from using our stuff and sharing the result ... $xxxx=$²(j+e )

 

[Pierre Lagarde]

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

The problem is that when Nikon introduces a major version of the firmware, they would insert new options into the middle of a list. For example, if Custom Settings D has 1 to 15, Nikon sometimes sticks new settings 12 and 13 into the middle of the original list, thus bumping the original d12 to d15 to d14 to d17. I.e., the old d12 is now the new d14, and the old d14 is now d16 .... Meanwhile, the new d12 is something completely new. It can be confusing.

Disclaimer … I Have not, yet, updated my Z8, and reading through this thread, I am feeling reluctant to do so … at least, until I see nothing but "joy and happiness" threads about FW 3.0.

That said, and armed only with the knowledge I have learned from reading this thread, I see a possible problem (and maybe a solution for the OP) that relates to your, above (and brilliant) example.

Using your example … Suppose the OP has “d12” set to some value other than the default or OFF. But, suppose in the update, the “new d12”, is now the new focus limiter feature, and because of some overlooked “glitch” in the mapping, the camera has used the OP’s “d12” setting, which has inadvertently activated the feature, affecting the AF on the OP’s Z8. Perhaps, the OP should find the new feature in the menu, and make sure it is turned off.

"d12", "a15"... do you think Nikon engineers are playing Battleships ?

I hope Nikon camera firmwares are using an internal dedicated code for each setting, not the facial ones.

I wonder how they could allow firmware backward compatibility if not.

 

[arniebook]

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

The problem is that when Nikon introduces a major version of the firmware, they would insert new options into the middle of a list. For example, if Custom Settings D has 1 to 15, Nikon sometimes sticks new settings 12 and 13 into the middle of the original list, thus bumping the original d12 to d15 to d14 to d17. I.e., the old d12 is now the new d14, and the old d14 is now d16 .... Meanwhile, the new d12 is something completely new. It can be confusing.

Disclaimer … I Have not, yet, updated my Z8, and reading through this thread, I am feeling reluctant to do so … at least, until I see nothing but "joy and happiness" threads about FW 3.0.

That said, and armed only with the knowledge I have learned from reading this thread, I see a possible problem (and maybe a solution for the OP) that relates to your, above (and brilliant) example.

Using your example … Suppose the OP has “d12” set to some value other than the default or OFF. But, suppose in the update, the “new d12”, is now the new focus limiter feature, and because of some overlooked “glitch” in the mapping, the camera has used the OP’s “d12” setting, which has inadvertently activated the feature, affecting the AF on the OP’s Z8. Perhaps, the OP should find the new feature in the menu, and make sure it is turned off.

"d12", "a15"... do you think Nikon engineers are playing Battleships ?

I hope Nikon camera firmwares are using an internal dedicated code for each setting, not the facial ones.

I wonder how they could allow firmware backward compatibility if not.

Pierre ...

I was just using “d12” in reference to the above, hypothetical example by Shuncheung.

Not familiar with “Battleships”, but, from your post, as well as noting, that, “a14” is the last “a” setting on my (still not updated) Z8, I’m daring to ASSUME that, Nikon added “a15” to the “a focus” menu in the CUSTOM SETTINGS MENU, to control the new focus limiter feature …True? That would be logical, and, if so, thanks, for offhandedly mentioning it. Still, I stand by my suggestion to the OP to check that particular menu setting, to assure it is not set to something that may interfere with auto focusing.

“Mapping” is a word used elswhere this thread that would be synonymous with your phrase, “internal dedicated code”. A mistake in that “code” would still cause problems, but I don’t think such a mistake exists, and there is some other, yet to be discovered, explanation for the OP’s focusing problems.

Arnie

 

[Pierre Lagarde]

I think the concern is that if one saves the camera settings to a file while on FW 3.0, after you downgrade to FW 2.10, the camera with 2.10 may not be able to read the settings from 3.0.

I have never tried that before, but I would save the settings when the camera is in 2.10, do the upgrade to FW 3.0, and you can optionally save the settings again to another file. If you need to downgrade, reload the earlier settings file with FW 2.10.

Depends on the format - if it is position-dependent (I.e.: the AF Mode setting is byte 1342 in the file for v3.0 but byte 1256 for 2.1) then no. If the settings file is JSON or XML, which are not position-dependent, and Nikon designed its settings-file reader to ignore anything it does not expect, then older firmware may be able to cope with a newer-FW file.

The problem is that when Nikon introduces a major version of the firmware, they would insert new options into the middle of a list. For example, if Custom Settings D has 1 to 15, Nikon sometimes sticks new settings 12 and 13 into the middle of the original list, thus bumping the original d12 to d15 to d14 to d17. I.e., the old d12 is now the new d14, and the old d14 is now d16 .... Meanwhile, the new d12 is something completely new. It can be confusing.

Disclaimer … I Have not, yet, updated my Z8, and reading through this thread, I am feeling reluctant to do so … at least, until I see nothing but "joy and happiness" threads about FW 3.0.

That said, and armed only with the knowledge I have learned from reading this thread, I see a possible problem (and maybe a solution for the OP) that relates to your, above (and brilliant) example.

Using your example … Suppose the OP has “d12” set to some value other than the default or OFF. But, suppose in the update, the “new d12”, is now the new focus limiter feature, and because of some overlooked “glitch” in the mapping, the camera has used the OP’s “d12” setting, which has inadvertently activated the feature, affecting the AF on the OP’s Z8. Perhaps, the OP should find the new feature in the menu, and make sure it is turned off.

"d12", "a15"... do you think Nikon engineers are playing Battleships ?

I hope Nikon camera firmwares are using an internal dedicated code for each setting, not the facial ones.

I wonder how they could allow firmware backward compatibility if not.

Pierre ...

I was just using “d12” in reference to the above, hypothetical example by Shuncheung.

Not familiar with “Battleships”, but, from your post, as well as noting, that, “a14” is the last “a” setting on my (still not updated) Z8, I’m daring to ASSUME that, Nikon added “a15” to the “a focus” menu in the CUSTOM SETTINGS MENU, to control the new focus limiter feature …True? That would be logical, and, if so, thanks, for offhandedly mentioning it. Still, I stand by my suggestion to the OP to check that particular menu setting, to assure it is not set to something that may interfere with auto focusing.

“Mapping” is a word used elswhere this thread that would be synonymous with your phrase, “internal dedicated code”. A mistake in that “code” would still cause problems, but I don’t think such a mistake exists, and there is some other, yet to be discovered, explanation for the OP’s focusing problems.

Arnie

Much clearer. I agree. In fact, they may be using UUID or some kind of technical ID that is shared in all versions, the menu and position being just an information for each, and right, that doesn't mean there can't be bugs elsewhere.

But I may be optimistic, and it also could be just haphazard programming