RegulatedNoise - trade tool with zxctypo's best-in-class OCR (EliteOCRReader as-was)
- Thread starter maxh2003
- Start date
OK, this one's failing because you've changed the UI colour and at the moment it's hard-coded to search for orange.
Version 1.2 will let you change the colour it looks for - it's a bit experimental and people will have to tinker with it I think - and it'll do all sorts of weird things if anyone tries to use white, grey or black...! But it worked just now for me on a similar screenshot.
Now that I think about it, this might be a very good way to improve OCR accuracy... "might" being the operative word...
Great tool but it seems my screenshots gets the ocr to mess up a bit. In some instances it thinks that 3 rows of text is one row so for example it reads it as metalaluminiumsomething.
Here are a few screenshots.
https://www.dropbox.com/sh/m8xeqgnl0pylv1p/AADZkQes2NN_fRdc9qS5d36ja?dl=0
Here are a few screenshots.
https://www.dropbox.com/sh/m8xeqgnl0pylv1p/AADZkQes2NN_fRdc9qS5d36ja?dl=0
http://i.imgur.com/42gm02W.png calibration.txt values.
http://i.imgur.com/2vGpftB.png The problem
EDIT Ok have the old version , trying new now
Ver 1.1 still having issues
http://i.imgur.com/BOw04c5.png Image & Error box Ver 1.1
http://i.imgur.com/Q0QIL7R.png Error BOX Ver 1.1
http://i.imgur.com/gEGA8OA.png calibration.txt values
Last edited:
Unfortunately, I got the same error and without the source code can't really say what might be missing. I guess I'll wait until you publish some new version. I thought of doing some OCR myself as I have lots of experience messing up with some other games but we don't need 10 projects doing the same time and I probably won't have time to support it anyway. If you can somehow share the source code I can troubleshoot. Or, I can try sending you the entire config.
OK, I think that's happening for you because in some/most of the screenshots, there is an orange highlight in the list of commodities. You need to make sure commodities aren't highlighted, like your Screenshot_0001.bmp. If you've got any highlighting on the commodities list, like in Screenshot_0006.bmp, it won't work properly - at best it sems it will decide that all the highlighted ones are the same single commodity...
OK, I can see the problem here, if not how it's happened.
Your ninth calibration point has a horizontal position of 892 pixels. But your tenth calibration point has a position of 828 pixels, which puts it to the left of the ninth calibration point.
Point nine should be "just to the left of the line dividing Demand and Supply", and point ten should be "in between the Supply, and the Supply Level (LOW/MED/HIGH)". So you can see that in theory, point ten should be on the RIGHT of point nine.
Possibly this is user error
or possibly there's a bug in the calibration code and it didn't give you the right instructions (or the instructions just aren't very good). Either way, try recalibrating and see what happens when you calibrate points nine and points ten.State the obvious: there are lots of calibration problems the code could check for, and indeed it could auto-calibrate...
Last edited:
Updated to v1.2, this time with C# source code too, for anyone who feels like messing about with it.
v1.2
* Add ability to restrict price analysis to systems within x light years, based on data from http://starchart.club/map
* Add ability to handle different UI colours than orange - hit the big obvious button on the Calibration tab to find out more
* Also, no need to restart app if it finds no rows - it will pop a message to warn you, but will then try again with the next screenshot. Popup might need removing in due course because it steals focus and that's evil...
v1.2
* Add ability to restrict price analysis to systems within x light years, based on data from http://starchart.club/map
* Add ability to handle different UI colours than orange - hit the big obvious button on the Calibration tab to find out more
* Also, no need to restart app if it finds no rows - it will pop a message to warn you, but will then try again with the next screenshot. Popup might need removing in due course because it steals focus and that's evil...
Last edited:
Thank you for the hard work, source is also much appreciated
NP... but please don't judge my code too harshly, I'm well-aware of how many imperfections, unoptimised bits, lazy copy-and-pastes and so on there are! I'm particularly fond of the bit where I wrote about a million separate delegates and then remembered you can just use one generic one instead... :-D
That said, all constructive criticism/suggestions/complete rewrites gratefully accepted!
ok thanks, will try again
- - - - - Additional Content Posted / Auto Merge - - - - -
Getting this with the 1.2 build
running win 8.1
View attachment 6553
Click in the upper menu on the downward pointing arrow and you will get all the files in one zip-file.
Thanks for the bug report, iAmLegion, and to everyone else who's feeding back too. This is the only way I can fix stuff like this so your help is greatly appreciated!
OK, iAmLegion, could you put this EXE => https://drive.google.com/file/d/0B8HLRQqyuPD9X09OU2JfdFZFQnM/view?usp=sharing over the existing one in your RN directory and run it? It's the same as 1.2 (so it won't fix anything) but when it b0rks, it should give an extra popup: "B0rked in ImportSystemLocations..." before it gives the usual "Application has encountered an error" popup. If you could post that first popup (the new one) it'd help me work out WTH's going on here!
Thanks for the bug report, iAmLegion, and to everyone else who's feeding back too. This is the only way I can fix stuff like this so your help is greatly appreciated!
OK, iAmLegion, could you put this EXE => https://drive.google.com/file/d/0B8HLRQqyuPD9X09OU2JfdFZFQnM/view?usp=sharing over the existing one in your RN directory and run it? It's the same as 1.2 (so it won't fix anything) but when it b0rks, it should give an extra popup: "B0rked in ImportSystemLocations..." before it gives the usual "Application has encountered an error" popup. If you could post that first popup (the new one) it'd help me work out WTH's going on here!
At your service!
View attachment 6556
Hey Max,
New poster, new player and I have to say your tool is great. The web interface is hilariously useful to have the tablet sitting with me.
I do however come bearing a funky error for your delight.
The use-case scenario is this:
1. Launch, calibrate, enable.
2. Eat cake, maybe exit and re-launch. Visit a station, F10 a few nice screens as per guidelines (res of 1680x1050)
3. alt-tab and start correcting, get 3-4 in (last time was at Beryllium) and get the below.
4. Curse, click continue and be unable to use, so re-launch. Lose the info it had got through for that station so far.
(aplogies for split url, new account restrictions)
InternetsSlashSlash imgur . com/a/c7GZC?gallery
If you think it's an interesting one, do let me know if you'd like more info.
New poster, new player and I have to say your tool is great. The web interface is hilariously useful to have the tablet sitting with me
.I do however come bearing a funky error for your delight
.The use-case scenario is this:
1. Launch, calibrate, enable.
2. Eat cake, maybe exit and re-launch. Visit a station, F10 a few nice screens as per guidelines (res of 1680x1050)
3. alt-tab and start correcting, get 3-4 in (last time was at Beryllium) and get the below.
4. Curse, click continue and be unable to use, so re-launch. Lose the info it had got through for that station so far.
(aplogies for split url, new account restrictions)
InternetsSlashSlash imgur . com/a/c7GZC?gallery
If you think it's an interesting one, do let me know if you'd like more info
.Brill. I do believe I've fixed it. The correct answer being... your Windows locale doesn't use "." as the decimal separator, so it's not reading the system locations file correctly - and the fix is for me to hard-code it in the app.
Can you try this one? It "should" work - although there might be one or two more bugs like this in the app. https://drive.google.com/file/d/0B8HLRQqyuPD9b3hTMlZ4WGJEQ3c/view?usp=sharing
Interesting indeed. Here's a test you could run for me. Find the screenshot it was processing when it crashed, and move it out of the screenshots directory. Now start RN, start monitoring as usual, then move that screenshot back into the directory. RN should pick it up and OCR it as if it's a new screenshot. Does it crash RN every time it sees that screenshot?
You might need to try with a few screenshots to find the one causing the crash, it's not necessarily clear to the end-user which screenshot is being processed at any given time.