It looks like there's a bug either in how Windows reports a given screen's resolution or a bug in how TCE reads that resolution. I use the "Change the size of text, apps, and other items" in Display Settings to make things easier to see and read on my 3840x2160 screen. However, TCE then reads that as actually being 1920x1080 and taking scans of just the upper left quarter of my screens resulting in an OCR scan error since it's only getting a small chunk of what it needs.. If I set the Change size slider in Display Settings to 100% and relaunch TCE then it correctly reads the resolution and takes working scans. This is 100% repeatable on my end.
http://tinypic.com/r/2mf0yz6/9 This is the screenshot TCE's OCR outputs when a scan is done with my Display Settings like they normally are.
All depends on your 2D settings at windows and if you are using the scaling option, this will also affect TCE. When using the scaling option, you can see at the Options panel > System what is reported from windows to TCE and if you don't use the same resolution at ED, then your issue is happening. So either you change your desktop resolution to the 3D resolution in ED or vice versa. Whatever your resolution is, both 2D and 3D must be the same in case of OCR.
But I strongly suggest to use EDMC instead, so you don't require EliteOCR anymore, but it's your choice.
I had an error occur whilst I was sorting the STAR CLASS in NAVIGATION/STAR SYSTEMS Panel. I just selected continue, I didn't take note of the error, as I assumed it was caused by sorting when the current star system I was in was being updated. However when I jumped to the next STAR SYSTEM something extremely odd occurred, my STAR SYSTEM list was massively out, e.g. the 1st system in the list was WREDGAEI RQ-B C27-4 90.47 LY's away, when it's actually 6k LY's away.
So I checked the stars coordinates and that's where the issue lies. TCE states the Coordinates to be: -3378.46878/ 162.15625 / 124.40626, when the correct coordinates should be; -3382.21875 / 82.21875 / -5988.
DB states coordinates differently: -3382.219 / 82.219 / 82.21
So it looks like as TCE was adding and updating this star system, when the error was thrown something went wrong with the update. System is Hypou Aim HG-Y e8
DB sent.
I've manually corrected the coordinates myself: Basically the Z coordinate got corrupted, however this hasn't resolved the problem.
I now get a list of stars that are 6k LY's away from my current position and none of the stars I've recently visited and updated.
I've reopened the DB and the Z axis hasn't been updated and remains set to 82.21, reopening the DB after saving shows that it's changed and saved correctly, but after starting TCE it gets reverted back to 82.21
All coords changes are done by TCE upon the value's of the journal output. So if you could provide me your journal log for the session, I can easily follow the issue, what happened.
Thanks