
I going to find out what the reason is.Īnother user sent me a dump file. Yes, it seems a few people have issues with ocr. I recommend using it and Duke is very good at responding to feedback and adding features that you think of where possible. THe latest version of OpenTrack has an improved off and centre toggle that does not have the issue. This caused a few problems with unrecognised data (which would now be detected by the data validation system in regulated noise and alert you to the issue). I was using opentrack with an EdTracker (cheers brumster!) and when I used the toggle to disable open track the view was not reset to 100% square (open track reported approx 0.2 degree of yaw I think even though it was set to off and recentre). You must ensure the screenshot is 100% square when you take it or the OCR will fail. Something to watch out for if using any form of head tracking. I could not find any sources in my database. I have had a couple of instances where it may be that a commodity has not been found at all (not certain it is not my fault), I am confident I visited a system or two with slaves available so when I found a mission that wanted slaves and paid a very good price I searched my database for the location where I found them. If anything suspect is found I am asked to check (which happens rarely for me).

I find it a very reliable and just use auto import everytime. I believe there are also price ranges defined for each commodity and if a price is detected outside of these ranges it again is flagged as suspect. If it has things like a demand but no corresponding price for that demand it is flagged as suspect. If any commodity is found that is not already in the "default" list it asks you if you want to add it to your local database first.
