IPD / Lens spacing is not being used for video displayed in hmd

I've only ever had a consumer Rift and I have that file.
Deleting it doesn't seem to change anything.

why not make some hidden tool for DK2 users only?

So, any update ? Is there a fix incoming ? Can we donwload the console app to check ?

I have the console app on my work computer. But you can test with Oculus World Demo that comes with the SDK. So download this:
https://developer3.oculus.com/downloads/pc/1.7.0/Oculus_SDK_for_Windows/
Then look in "ovr_sdk_win_1.7.0_public\OculusSDK\Samples\OculusWorldDemo" and double-click "OculusWorldDemo.exe". When it loads, press the space bar once and look in the middle where it says "IAD". If things are broken, this will show 64.0 rather than the actual value set by the physical slider (like 68.8 in my case).

Ok, the demo show the correct IPD for me (even though the TL demo shows 64).

So I'm noticing something strange.

I've built my own demos in unity with the latest oculus plugins and they've always shown an IPD of 64mm
(when pressing the space bar to show info). However,  the SDK world demo you recommend shows the correct IPD of 66.

Why is it that the SDK world demo is literally the only one that has ever shown the accurate IPD while my own and every other demo I've come across with the ability to show info like altspace shows and IPD of 64mm.

What would cause this disconnect?

cybereality said:

No, ProfileDB.json should not be used, and you should delete the file if you are using a consumer Rift. The IPD value is read directly from the hardware (since you can adjust the IPD slider at any time) and not saved in a profile. That may be part of your problem.

No matter how many times I delete this file it always makes it's way back eventually. Probably after going through the height setup prompt or re calibrating my sensor angle. The file for me reads as follows:

"{

Tested in my own code, the IPD is properly reported now in the eye offset.

It would be great to be able to override the default "64" value (why 64?) in an ini file somewhere, for old / noncompliant / whatever apps.

64mm is the average eye spacing, which is why it's the default. The value, in this case, comes from the runtime service, and the value can be retrieved by calling an API function. So if an app, even an old app, is rendering properly it should automatically get the correct value from the headset. If it isn't, then something else is broken.