Wrong lens module... (part 8738)

,

Hi there,

it has been discussed over and over again… but I never really spent attention (because I was never affected by any wrong lens suggestion). That has changed with PL 10!

I have a couple of photos that were taken with a Nikon Z6iii and a FTZ-mounted 50mm/1.8G lens. When using my laptop the make and modell is identified correctly by PL10. But: On my desktop PL10 suggests other lenses (which I’ve never owned…).

The funny thing is: The metadata panel identifies the lens correctly (“50mm f/1.8G”), but the module loader only offers “Nikon F 50mm f/1.8 D” or a Vitrox lens.

So I wonder whether there is a way to either transfer the correct module from the laptop to the desktop or to force PL to download a profile of my choice?

(I am on Windows 11…)

Cheers!

In PL9 (I don’t have PL10 but I can’t imagine it’s different) in the main menu click ‘DxO Modules’ then choose the top option ‘Download additional DxO Modules…’

And report a bug to DxO (support.dxo.com) - then upload a sample RAW file to upload.dxo.com.

A few years back, PL assigned many wrong modules. On my Mac, I fixed this by editing the module database - until DxO came up with a fix.

Copying the module to the other computer is easy, but it does not necessarily fix the issue, e.g. if PL does not recognise the module as a viable alternative.

I wonder why the presumably same version of PL behaves differently on two computers - if both are equipped with the same version of OS…

Funny: After having used PL for more than four years this is the first time I realize that there is a “DXO Module” entry in the main menu… my gosh, I’m getting old :frowning:

Also funny: According to PL the respective module “Nikon Z6iii + Nikkor AF-S 50mm f/1.8G” is already installed. Nevertheless, the green icon to choose a lens module appears next to all photos taken with that combo…

So, it’s either re-installing PL (as a first step) or raising a ticket with the “fabolous” DXO support… Wonder whats faster :wink:

Anyway, thanks for guiding me in the right direction.

This is the module in question
grafik
and it was installed automatically.

Okay, re-installing solved the issue. Whatever the underlying reason for PL’s false judgement was, it is fixed now and the lens is identified correctly. But, indeed, I was puzzled as well that PL on my laptop did identify the combo while PL on my desktop didn’t. Perhaps the initial installation went wrong or the restart of the pc didn’t update required files… who knows!

Thanks again for directing me to the lens module panel in PL which I had ignored for years. Won’t happen again :wink: