RegulatedNoise - trade tool with zxctypo's best-in-class OCR (EliteOCRReader as-was)

Duke

D
iAmLegion said:
New version out https://github.com/Duke-Jones/RegulatedNoise/releases
Click to expand...

Yesss :)

Major changes are
* check of prices and warning/hint if a price seems implausible
* saving the positions of all windows
* auto-open OCR tab if ocr starts



sutex said:
.... any solutions ....
Click to expand...

If you send me a few screenshots and your "RegulatedNoiseSettings.xml" + "AppConfig.xml" I can have a look..


Hobson's Choice said:
Very Many Thanks, Duke, for all your hard work.
New version is a strong improvement.
OCR almost completely error free - had only 1 error (IVL for SILVER) in 14 station commodity reads.
Additional options and range checking in Edit Data a real help (still won't trust auto-import. Far too many errurs (;)) from other commanders via EDDN).
Might be looking in wrong place but couldn't find an in-application donate button!
Click to expand...

You're welcome :)
Hint: Autoimport starts only if there was no implausible value before.

PS: Look on the settings-tab


@all:
I suggest to add all missing values (-1) for price checking - even if upper und lower value are the same.
On next implausible warning you can correct the values.
 

Duke

D
hey sutex,

I did a test and I had no problems to OCRing the screenshot.

Maybe you did the calibration on one resolution and the screenshot has another resolution ?

I took the Screenshot_0000.bmp (2715x1527) for calibration. RN warned me of the resolution
because it's another as the AppConfig.xml it has (it's 1280x720) but I ignored the warning.
After finishing the calibration and starting OCRing with the same screenshot (Screenshot_0000.bmp)
I got all values from the OCR algorithm without any error.

After that I startet OCRing with the other screenshot you've sent and I got only bull (Screenshot_0027.bmp).
Then I realized the Screenshot_0027.bmp has another resolution (1920x1080).

Be sure, you take a screenshot for calibrating with the same resolution as your screenshots ingame really have.

Can you check it again,please ?
 

sutex

sutex
Duke said:
hey sutex,

I did a test and I had no problems to OCRing the screenshot.

Maybe you did the calibration on one resolution and the screenshot has another resolution ?

I took the Screenshot_0000.bmp (2715x1527) for calibration. RN warned me of the resolution
because it's another as the AppConfig.xml it has (it's 1280x720) but I ignored the warning.
After finishing the calibration and starting OCRing with the same screenshot (Screenshot_0000.bmp)
I got all values from the OCR algorithm without any error.

After that I startet OCRing with the other screenshot you've sent and I got only bull (Screenshot_0027.bmp).
Then I realized the Screenshot_0027.bmp has another resolution (1920x1080).

Be sure, you take a screenshot for calibrating with the same resolution as your screenshots ingame really have.

Can you check it again,please ?
Click to expand...

yep I'll have closer look, This AppConfig.xml that has (1280x720) when the "Real screen" is (1920x1080) , but DSR in game has it at (2715x1527) which I like , much better ,This is all normal then ? Also my FOV is blank in OCR calibration tab, just a line , cant remember if it ever had numbers in there
End of the day RN was working find , before the screen resolutions changed, by DSR

The Screenshot_0027 was from before, sent the wrong one ,doh!.
 
Last edited:

Duke

D
sutex said:
yep I'll have closer look, This AppConfig.xml that has (1280x720) when the "Real screen" is (1920x1080) , but DSR in game has it at (2715x1527) which I like , much better ,This is all normal then ? Also my POV is blank in OCR calibration tab, just a line , cant remember if it ever had numbers in there
End of the day RN was working find , before the screen resolutions changed, by DSR

The Screenshot_0027 was from before, sent the wrong one ,doh!.
Click to expand...

POV ? do you mean FOV (next to the resolution) ? it's not an used field yet.

So it works ?
 

Duke

D
AAAAAAAAAAAAAAAAAAAAAAAAAARRRHHHHHRHHRHHHHHHHGGGG

sutex, I wonder why my test configuration recognized only BULL_SH_IT after I testet your config.

If you still have problems so DELETE THE FU'K'N "settings.ini" in the Brainerous subdirectory.
it could helping foolish015.gif
 

sutex

sutex
Duke Are you having a bad hair day ?
DELETE THE FU'K'N "settings.ini"
Click to expand...


This AppConfig.xml that has (1280x720) when the "Real screen" is (1920x1080) , but DSR in game has it at (2715x1527) I take it this is normal then. ?

I'll just save the LOG and CSV delete the rest , re-install & then calibrate again.
 

No3kins

N
My experience of DSR is that it only works in full screen mode. I run in borderless so I can use my 2nd screen for RN etc without alt tabbing. I can set my res to higher than native using DSR but the screenshots remain at the native res and the game quality does not improve UNLESS I go full screen. The DSR resolution is selected in game but it does not seem to actually apply.
 

sutex

sutex
No3kins said:
My experience of DSR is that it only works in full screen mode. I run in borderless so I can use my 2nd screen for RN etc without alt tabbing. I can set my res to higher than native using DSR but the
screenshots remain at the native res and the game quality does not improve UNLESS I go full screen. The DSR resolution is selected in game but it does not seem to actually apply.
Click to expand...


This AppConfig.xml that has (1280x720) when the "Real screen" is (1920x1080) , but DSR in game has it at (2715x1527)
Click to expand...

I changed the AppConfig.xml that has (1280x720) to (2715x1527) and recalibrated RN worked I'm running in borderless mode, have read that DSR does work in borderless but its fickle as what games it will allow it

All my screenshots are coming in at (1920x1080) , but RN is still saying (2715x1527) in the OCR tab, going back in game will try fullscreeen see if I can OCR then , keep you updated


UPDATE , set ED to fullscreen all the screen shots where in (2715x1527) , recalibrate to be sure & OCR worked ,the same station, but this time screenshot in OCR, kept picking up GOODS , the rest was ok, not sure what any of this means , but if I cant run borderless mode then Elite Copilot which I use for routing , will be a problem as it uses an overlay for EliteCopilot next route, top left of the screen , only will appear in borderless mode ,have tried to turn it off , but can see where , if its at all possible.

I do have a 2nd screen laying around but it just an old type LCD 4.9 , I also have an tablet which I use to view the Web server functions of either RN & EliteCopilot , RN I can turn off or on , I see no controls for EliteCopilot , it just broadcast next destination by default . The Web-server function OCR tab is difficult to use via Tablet. Both RN & EliteCopilot use the same address

Any suggestion, will plugging in a smaller resolution screen help ?


2nd Update Reset the game back to borderless mode screenshots are coming in at (1920x1080) recalibrate RN OCR , all working, When I first did all this AppConfig.xml was at (1280x720) and there were errors in OCR reading
Now with AppConfig.xml set too (2715x1527) , there are none. those who know may understand why, hope this helps
 
Last edited:

Duke

D
sutex said:
2nd Update Reset the game back to borderless mode screenshots are coming in at (1920x1080) recalibrate RN OCR , all working, When I first did all this AppConfig.xml was at (1280x720) and there were errors in OCR reading
Now with AppConfig.xml set too (2715x1527) , there are none. those who know may understand why, hope this helps
Click to expand...

I recommend after each change of the resolution and recalibrating: delete the "settings.ini" in the Brainerous subdirectory !!!
I't definitively a possible reason for bad results while OCR-ing numbers !
In the next release it will be done automatically.
 

sutex

sutex
Duke said:
I recommend after each change of the resolution and recalibrating: delete the "settings.ini" in the Brainerous subdirectory !!!
I't definitively a possible reason for bad results while OCR-ing numbers !
In the next release it will be done automatically.
Click to expand...
Ok
And this AppConfig.xml that did have (1280x720) when the "Native screen" is (1920x1080) , but DSR in game has it at (2715x1527) , I set to AppConfig.xml to 2715x1527 , now , but the DSR apparently does not work in borderless mode , what should it be RN is still showing (2715x1527) , I'm in borderless mode, whether or not DSR is working or not




Side note Something to think about
All of the above happened cause I have a new graphics card that allows DSR , (higher screen resolution other than native) which I like , I have hence found the limitations or Borderless mode verse Fullscreen.

My question is can RN work on a 2nd PC that's network ( router lan setup) , then one would be able to go Fullscreen , and not have to alt tab. I assume that any overlay attempt like others are doing, require borderless mode as well. Wonder if Fullscreen is becoming the holy grail , given limitations or Borderless & dsr & trading interfaces.
A simple tablet could then been the interface between the 2nd PC, using iDisplay solution http://getidisplay.com/ others around but I'm using this and it works.

I see problem like not be able to read the logs or screenshot as they are update but some form of sync could take care of that , is this too much or more like the Manhattan Project ! lol
 
Last edited:

Duke

D
It seems the info out of the AppConfig.xml is only for automatic calibration.
If you select a pic with another resolution you get a warnung from RN but if you
confirm RN takes the resolution of the bitmap as given.
The value from AppConfig.xml then is not of interest anymore.
 
Last edited:

Duke

D
new version released : DJ_0.12

changes:
Code: 
1.84_0.12_2
   * delete setting.ini if calibrating new (previous calculated digit width can result in bad OCR)
   * commodity warnlevels are now saved if changed
   * fixed crash reason if deleting all commodities from a station
   * Cmdr's Log now showing dates in local culture settings
-------------------------------------------------------------------------------------   
1.84_0.12_1
   * getting also current location in the current system from logfile
   * clock added (local and ingame time)
 

Hobson's Choice

H
RN Edit Data problem - Heeeelppp? :)

Hi Duke
Dloaded and using version 12. needed a recal, had serious garbage, all ok now.
However (sorry), have a problem with Edit Results window.
My screen res is native 1920x1080. This also appears in OCR Calibration resolution.
But....
I cannot see all of the raw image row and the OCR'd table is not resizeable.
Any suggestions.
I fully check all of my data before importing or uploading to EDDN and this makes it difficult.
The OK button is not fully visible and the 'implausible data' checkbox and 'price warning' button overlie the OCR'd row.
Can you change size of the bottom part of the window so all is visible, please?

http://alpha1.synology.me/tvr-images/RN-OCR-EDIT-problem.jpg
RN-OCR-EDIT-problem.jpg


p.s. found the donate button. :D

Cheers
HC
 
Last edited:

Duke

D
Hm, thats strange. I will check as soon as possible.
Did you use the v0.11 before ? Same behaviour ?
Looks like a problem with your personal resolution/system.

Which version of windows do you have runnin' ?
 
Last edited:

Moab

M
D:\.... isnt the Frontier Product directory error

Hi there, was not able to search in the forum if there may be an answer to my question already, so sorry, let me just ask:
When I installed Regulated Noise, it asked me to point to the installation directory of Frontier.

Mine is not in C:\Program~ Files or anything, it is on D:\Games\Frontier
Regulated Noise was not able to find Elite installed it thus did not accept the manually entered directory.



Any ideas? Thanks a lot.

BR
Moab
 

Duke

D
Look like you select the "EDLaunch" Directory ?
Try to select the "Products" directory (in the "EDLaunch" dir).

works ?
 
Last edited:

Hobson's Choice

H
Duke said:
Hm, thats strange. I will check as soon as possible.
Did you use the v0.11 before ? Same behaviour ?
Looks like a problem with your personal resolution/system.

Which version of windows do you have runnin' ?
Click to expand...

Hi Duke
Ok, yes it did occur in previous version 1.11
I am running Windows 8.1.
Beats the heck out of me :).
Cheers
 
You must log in or register to reply here.
Back
Top Bottom