Document not shown in real size on screen

[cdaerr]

Hi,

I created an A5 document and pressed Ctrl + 8. I expected that the document is shown in real size on my screen, But it is not. It is shown too big. See the photo attached to this post.

 

[harrym]

This 'may' help

Personally I use 34% zoom. 

[cdaerr]

Hi harrym,

thanks for tis hint, but on pressing Strg+8, which is the same than "Ansicht->Zoom->Tatsächliche Größe" 10mm of the document should be 10mm on the screen. On my Surface Book it works perfect. See Screenshot attached to this post.

The problem is only on my Desktop PC with HiDPI screen of 150ppi. The Surface Book has 268ppi and there it works.

I think this is bug in Affinity Software.

 

[Mark Ingram]

Hi, we use the DPI information that has been provided by the monitor manufacturer (as we need to know the physical dimensions of the screen, as well the pixels dimensions, and display scale). If this information is accurate, the actual size will be correct (as you mention, it works on a Surface Book).

[cdaerr]

Hi,

in the Log.txt at AppData directory I found the following DPI information:

 

The Screen manufacturer (LG) provides the following value in his datasheet:

 

Is there a way to change this value manually?
I could not find something in the setup.

Thanks for helping at this problem

 

[Mark Ingram]

Hi cdaerr, thanks for that information. There isn't currently a way to override the DPI setting, without changing the registry (which the manufacturer of the monitor has written). Perhaps we could add a way to do this in the future. You might want to get into contact with the monitor manufacturer and ask why their DPI isn't configured correctly in Windows.

[cdaerr]

Hi,

where in the registry is the dpi written?
Where can I read this information to show this to the manufacturer?

Thanks

[Mark Ingram]

5 minutes ago, cdaerr said:

Hi,

where in the registry is the dpi written?
Where can I read this information to show this to the manufacturer?

Thanks

 

Hi, it's a different key for each monitor device, so my Dell P2415Q monitor data is located here:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\DELA0BE\1&8713bca&0&UID0\Device Parameters

 

If you want to have a browse, look in the folder:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\

 

And you'll probably notice "Default_Monitor" and then some other folders. Each of the non-default folders will represent a monitor device on your system. See if they have a "Device Parameters" folder within them.

[cdaerr]

Hi,

thanks for that information. I took a look in the registry and I identified the monitor in the registry, but I could not find any information on PPI value. Se the screenshots attached.

[Mark Ingram]

Hi, the EDID value in your second screenshot contains binary information, and in there is information on the physical dimensions of the monitor. If those physical dimensions are incorrect, when we calculate DPI using the pixel resolution later on, the DPI will be incorrect.

[cdaerr]

Hi,

thanks with decoding the EDID information I could locate the problem:

 

The real size value should be:

 

Is there a way to change this information?

Thanks

[Mark Ingram]

Apparently your monitor manufacturer can provide an INF file which can override those settings:

 

https://docs.microsoft.com/en-us/windows-hardware/drivers/display/overriding-monitor-edids

 

Quote

• A better solution, described here, is for the manufacturer to implement an INF file that contains the correct EDID info, and have the customer download it to the computer that's connected to the monitor. Windows extracts the updated EDID info from the INF and provides it to components instead of the info from the EEPROM EDID, effectively overriding the EEPROM EDID.

 

I would suggest contacting the monitor manufacturer for further information.

[harrym]

Hi cdaerr,

Sorry I clearly didn't understand the actual issue. Very informative topic!

 

Regards

[cdaerr]

Hi Mark,

one month ago the monitor Manufacturer (LG) promised to examine the proposal with the INI file. But since this time I got no further resopose. I don't think that I will get a positive feedback. The Porposal of LG was to send in the monitor for correction. But I have bad experience with send in to LG.

So could you please help creating my own INI File?

Thanks

[Mark Ingram]

15 hours ago, cdaerr said:

Hi Mark,

one month ago the monitor Manufacturer (LG) promised to examine the proposal with the INI file. But since this time I got no further resopose. I don't think that I will get a positive feedback. The Porposal of LG was to send in the monitor for correction. But I have bad experience with send in to LG.

So could you please help creating my own INI File?

Thanks

 

Hi, I'm sorry but I won't be able to help with this. I have never done this before, and would not feel comfortable making overriding changes to a customer's hardware. Unfortunately communicating with LG is your best bet (unless you would like to make an INF yourself, following the instructions in the link I provided). If they don't get back to you, you could always try returning the monitor?

[Jack Humbert]

Hey all - this was the only thread I found on the subject that shedded the needed the light on what actually needed to be done to fix the issue, so I thought I'd describe what I did in hopes that other people can replicate it, or it can be put in a wiki/how-to somewhere. I'm running Windows 10, but I suspect the EDID modification process would work on other systems, if you're able to install it correctly. I'm using monitor that didn't have a driver (Massdrop Vast) which had the incorrect "Image Size" values in the "Detailed Timing > Timing" section of the EDID (I'm not sure these names are accurate, but this is what the editing software calls them, so I'll be using them below).

Before doing any of this, I would make sure your manufacturer hasn't already supplied a driver that will update these to be the correct values - there is some risk to messing up your EDID (although there is a checksum, so I'm not sure how messed up it could get).

I don't know of the risk involved in changing values in your EDID, but I wouldn't be surprised if some damage could occur with the wrong ones, so please proceed with caution, and if you have any questions, please don't be afraid to ask. Please note that all code blocks require customization - nothing here can be copy & pasted. I'm also not an expert in any of this, and have only figured this out today.

Obtaining the current EDID

Like others mentioned above, the EDID key is located here (<some_id> and <other_ids> will be specific to your monitor) - you can view this in regedit.exe:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\<some_id>\<other_ids>\Device Parameters

If it's not obvious which id is the monitor you want to modify, you can go to Settings > Display, and selected the monitor you're working with, then click Advanced Display Settings > Display adapter properties for <monitor>. In that new window, go to the Monitor tab > Monitor Type > Properties button, then Details tab > Property: "Device instance path", and you should see something like "DISPLAY\ICB3500\5&44F2E74&0&UID4355", which is the location in the registry that you need.

To get this into a text file, we need to export it, and can do so by right-clicking on the "Device Parameters" folder - save this as "edid.reg" somewhere where you'll be able to open it to edit it. 

We now need to prepare the EDID for editing - if you understand what's going on, feel free to convert this binary however you want (there might be programs that do this as well), but since it's just text, it's pretty easy.

You'll need some sort of text editor to open the edid.reg file - be sure to right-click on the file and click "Edit" instead of double-clicking - opening it should look something like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ICB3500\5&44f2e74&0&UID4355\Device Parameters]
"EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,24,62,00,35,00,00,00,00,28,1b,01,04,b5,52,\
  23,78,3f,76,90,a8,54,4d,9f,25,0e,50,54,bf,ef,80,d1,c0,81,c0,81,00,81,80,a9,\
  c0,b3,00,b3,28,21,e8,3e,d0,70,a0,d0,a0,29,50,30,20,3a,00,33,5a,31,00,00,1a,\
  e7,7c,70,a0,d0,a0,29,50,30,20,3a,00,33,5a,31,00,00,1a,00,00,00,fd,00,31,7d,\
  a0,a0,41,01,0a,20,20,20,20,20,20,00,00,00,fc,00,4d,61,73,73,64,72,6f,70,5f,\
  56,61,73,74,00,7b

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ICB3500\5&44f2e74&0&UID4355\Device Parameters\WDF]

Open up a new text file, and copy in the values after "hex:" all the way to the end of the key (7b in the case above). That should look something like this:

00,ff,ff,ff,ff,ff,ff,00,24,62,00,35,00,00,00,00,28,1b,01,04,b5,52,\
  23,78,3f,76,90,a8,54,4d,9f,25,0e,50,54,bf,ef,80,d1,c0,81,c0,81,00,81,80,a9,\
  c0,b3,00,b3,28,21,e8,3e,d0,70,a0,d0,a0,29,50,30,20,3a,00,33,5a,31,00,00,1a,\
  e7,7c,70,a0,d0,a0,29,50,30,20,3a,00,33,5a,31,00,00,1a,00,00,00,fd,00,31,7d,\
  a0,a0,41,01,0a,20,20,20,20,20,20,00,00,00,fc,00,4d,61,73,73,64,72,6f,70,5f,\
  56,61,73,74,00,7b

We also need to remove the "\" characters (the spaces and newlines are ok, though) - doing so will look like this:

00,ff,ff,ff,ff,ff,ff,00,24,62,00,35,00,00,00,00,28,1b,01,04,b5,52,
  23,78,3f,76,90,a8,54,4d,9f,25,0e,50,54,bf,ef,80,d1,c0,81,c0,81,00,81,80,a9,
  c0,b3,00,b3,28,21,e8,3e,d0,70,a0,d0,a0,29,50,30,20,3a,00,33,5a,31,00,00,1a,
  e7,7c,70,a0,d0,a0,29,50,30,20,3a,00,33,5a,31,00,00,1a,00,00,00,fd,00,31,7d,
  a0,a0,41,01,0a,20,20,20,20,20,20,00,00,00,fc,00,4d,61,73,73,64,72,6f,70,5f,
  56,61,73,74,00,7b

We can now save this as "edid.txt" or something similar, and it's ready to be imported into the editor.

Modifying the EDID

The program I used is called EEditGold, is free, and can be downloaded here:

https://ez.analog.com/video/w/documents/750/advantiv-edid-editor

Once you have that installed, open the program, select File > Import > Text, then click "Select" and navigate to the location of the "edid.txt" file we just created. Open this, and click "Import".

From here on, it will really depend on the current status of the EDID file. The two spots I needed to edit were under EDID > VESA > Db1 and Db2 (navigated to on the left side). In both of these sections, the Detailed Timing > Timing > "Image Size (mm)" were incorrect. I measured both the width and height of my monitor in millimeters, and entered the values here (in both Db1 and Db2). For what it's worth, my EDID > VESA > Basic entry show the Screen Size > Image Size values correctly (note that these are in centimeters), but these must not be used/reported. I also updated the "Product Name" that was under Db4, because mine was generic and unhelpful. I wouldn't go around changing too many values not outlined here, or at the very least, just change one at a time, and be prepared for things to break.

Once you're happy with your changes, hit File > Export > Text, and click "Select" - name it "edit-fixed.txt" and hit "Save" in the file selector, then "Save" in the next window.

Now, with your edid.reg file still open, save it as "edit-fixed.reg" before you start making changes to avoid editing your original edid.reg file (in case something goes wrong). Open your edid-fixed.txt, and copy that entire file into edit-fixed.reg, after "hex:", completely replacing what was there previously. It should look something like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ICB3500\5&44f2e74&0&UID4355\Device Parameters]
"EDID"=hex:00,FF,FF,FF,FF,FF,FF,00,24,62,00,35,00,00,00,00,28,1B,01,04,B5,52,23,78,3F,76,90,A8,54,4D,9F,25,0E,50,54,BF,EF,80,D1,C0,81,C0,81,00,81,80,A9,C0,B3,00,B3,28,21,E8,3E,D0,70,A0,D0,A0,29,50,30,20,3A,00,33,5A,31,00,00,1A,E7,7C,70,A0,D0,A0,29,50,30,20,3A,00,33,5A,31,00,00,1A,00,00,00,FD,00,31,7D,A0,A0,41,01,0A,20,20,20,20,20,20,00,00,00,FC,00,4D,61,73,73,64,72,6F,70,5F,56,61,73,74,00,7B

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ICB3500\5&44f2e74&0&UID4355\Device Parameters\WDF]

Now, we need to modify the url of the key, adding a "\EDID_OVERRIDE", and renaming the key from "EDID" to "0" - this will allow us to run/merge in the .reg file. We'll also remove the WDF reference at the end of the file. Doing so should look like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ICB3500\5&44f2e74&0&UID4355\Device Parameters\EDID_OVERRIDE]
"0"=hex:00,FF,FF,FF,FF,FF,FF,00,24,62,00,35,00,00,00,00,28,1B,01,04,B5,52,23,78,3F,76,90,A8,54,4D,9F,25,0E,50,54,BF,EF,80,D1,C0,81,C0,81,00,81,80,A9,C0,B3,00,B3,28,21,E8,3E,D0,70,A0,D0,A0,29,50,30,20,3A,00,33,5A,31,00,00,1A,E7,7C,70,A0,D0,A0,29,50,30,20,3A,00,33,5A,31,00,00,1A,00,00,00,FD,00,31,7D,A0,A0,41,01,0A,20,20,20,20,20,20,00,00,00,FC,00,4D,61,73,73,64,72,6F,70,5F,56,61,73,74,00,7B

You can now save your edid-fixed.reg file.

Finishing things up and applying the change

Before you run/merge the edid-fixed.reg file, be sure your edid.reg file still exists and has your old EDID information. You may need this if something goes wonky. In the case that it does, be prepared to have another monitor to use to restore your EDID. To do that, merge your original edid.reg file (just to be safe), and delete the "0" key from that folder in your registry location. Then, restarting your computer should get things back to normal. Please note that I haven't had this happen to me, so these restoration directions are purely speculative.

If you're comfortable, right-click > "Merge" on your new edid-fixed.reg file, and restart your computer. You might also be able to press Ctrl+Win+Shift+B, to restart your graphics driver, but I wasn't able to test this before making the change.

Affinity documents should now be correctly sized at 100%/Actual Size on the monitor you configured (as long as it's your main monitor, maybe? I haven't tested this extensively yet).

[Horseflesh]

Great post, thanks. Found it when I was trying to figure out why my LG monitor at "actual size" zoom was way off. Sadly that utility is temporarily unavailable, I hope it is restored soon.