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

Duke · Feb 4, 2015

sutex said:
Will the latest Base from GITHUD always be in sync with your International version,
I see no reference in GitHud issues of the list of bug fixes been closed by your fixes

Yes, I want to sync it as fast as possible if there's a new version.
The fixes/changes I implemented were born on my personally needs - so at this moment
I didn't look really on the official buglist.

sutex said:
"So if I override my current RN version with the International RN version, will the next GITHUD RN update , still be compatible"

It should be. There are no changes on the internal datastructures. Only additional structures and improved functionality.
The next official version should run without problems. I also will have a eye on it for future versions.

Jawada · Feb 4, 2015

I have a simple question. What is the default setting of RegulatedNoise considering Data sharing.
Is data uploading by default on or off ?
How do i turn it on /off ?
Thanks for reply

Duke · Feb 4, 2015

Default is off.
If you want to recieve the EDDN data you have to click "start listening" on the EDDN tab.
If you want to send your data to EDDN you have to check "Post data to EDDN in import" - it's default off.

iAmLegion · Feb 4, 2015

Duke, i sent you a pm.

Got a bug so here it is again https://www.dropbox.com/s/c1c5iywsalntybp/RegulatedNoiseDump.dmp?dl=0

Getting it with the regular version too.

sutex · Feb 5, 2015

iAmLegion said:
Duke, i sent you a pm.

Got a bug so here it is again https://www.dropbox.com/s/c1c5iywsalntybp/RegulatedNoiseDump.dmp?dl=0

@ Duke

Can you keep us up to date on this , as nothing is been raised at GITHUD with any issues, given its International RN version, & not Main RN, I can understand this, maybe start another Issues for IRNV I'm not sure if this is correct, but would be good if everyone was on the same page , so too speak, to deal with bugs

As for development , of Main RN it seems to have slowed, can I suggest Duke that you start looking at enhancement , least this way , it wont conflict with other work DEV might be doing , as I think most of the enhancement will be left to last. Enhancement A-Z of station names would be a good place to start, as searching for that one station is a royal pain at the moment

iAmLegion · Feb 6, 2015

Any update duke?

Duke · Feb 7, 2015

I'm sorry. The dump file didn't help much. Maybe it wasn't 100% applicable
because it coukld be that I did some changes on the source code without saving the previous version.

Feel free to get the current version from github: https://github.com/Duke-Jones/RegulatedNoise/releases/latest

I saved the version (https://github.com/Duke-Jones/RegulatedNoise) so I hope the dump files will work properly now.

On the other hand I have found another error that cause the app to crash. I will publish this version as fast as I can (family, children, playin' ED, work, party

).
There will be also an enhanced error logging included.

@ iAmLegion: the error occurs every time or only sometimes ?

iAmLegion · Feb 7, 2015

Duke said:
I'm sorry. The dump file didn't help much. Maybe it wasn't 100% applicable
because it coukld be that I did some changes on the source code without saving the previous version.

Feel free to get the current version from github: https://github.com/Duke-Jones/RegulatedNoise/releases/latest

I saved the version (https://github.com/Duke-Jones/RegulatedNoise) so I hope the dump files will work properly now.

On the other hand I have found another error that cause the app to crash. I will publish this version as fast as I can (family, children, playin' ED, work, party ).
There will be also an enhanced error logging included.

@ iAmLegion: the error occurs every time or only sometimes ?

It happened after i scanned a really long station name so could it be that it cant handle a certain lenght of chars?
And it happens every time i launch, crashes right away and create a dumpfile.
github version crashes too.

Duke · Feb 7, 2015

iAmLegion said:
It happened after i scanned a really long station name so could it be that it cant handle a certain lenght of chars?
And it happens every time i launch, crashes right away and create a dumpfile.
github version crashes too.

ok, then get the 184-002 from github and send me a generated dump (launch error) file from this version.
Please send also a dump file from the <station name length error> - and the screenshot that causes the crash.
hope I can find out something.

you can send the files to duke.jones(at)gmx.de

iAmLegion · Feb 7, 2015

Duke said:
ok, then get the 184-002 from github and send me a generated dump (launch error) file from this version.
Please send also a dump file from the <station name length error> - and the screenshot that causes the crash.
hope I can find out something.

you can send the files to duke.jones(at)gmx.de

Sadly dont have the screenshot left and not certain on what station/system it was

But most likely either
badbadzist - bouvard ring or fabian terminal
or Harm - finlay-freundlich ring or gentl hub

Dropbox link to dumpfile https://www.dropbox.com/s/c1c5iywsalntybp/RegulatedNoiseDump.dmp?dl=0

Duke · Feb 7, 2015

@iAmLegion:
I checked the dump file. The reason for the crash seems to be an incorrect path.
The app wanted to read AppConfig.xml but couldn't find it:

base = {"Could not find a part of the path 'C:\\Users\\%Username%\\AppData\\Local\\Frontier_Developments\\Products\\FORC-FDEV-D-1010\\AppConfig.xml'."}

(i have chaged the username to %Username%

)
Has the path changed ?

EDIT: the part "...\\Frontier_D evelopments\\..." looks strange with the space in it ?!? :S

EDIT again: no sorry , the space comes from me

but is the location right ?

iAmLegion · Feb 7, 2015

Duke said:
@iAmLegion:
I checked the dump file. The reason for the crash seems to be an incorrect path.
The app wanted to read AppConfig.xml but couldn't find it:

(i have chaged the username to %Username% )
Has the path changed ?

EDIT: the part "...\\Frontier_D evelopments\\..." looks strange with the space in it ?!? :S

EDIT again: no sorry , the space comes from me
but is the location right ?

Ah ok, i know what it is then.
Maybe add a check if the path is correct and if it isn't make it not crash but notify about it

iAmLegion · Feb 7, 2015

Duke said:
@iAmLegion:
I checked the dump file. The reason for the crash seems to be an incorrect path.
The app wanted to read AppConfig.xml but couldn't find it:

(i have chaged the username to %Username% )
Has the path changed ?

EDIT: the part "...\\Frontier_D evelopments\\..." looks strange with the space in it ?!? :S

EDIT again: no sorry , the space comes from me
but is the location right ?

When i removed this file https://www.dropbox.com/s/ce5ffpbpy523q1k/CommandersLogAutoSave.xml?dl=0 it started to work also, but as soon as i ad it back it crashes.

Duke · Feb 7, 2015

Hm, I would say thats not the problem file.
Remove the RegulatedNoiseSettings.xml file or set the correct path in this file.
I think the <GamePath> or the <ProductsPath> is wrong.

my paths looks like this:

<ProductsPath>F:\Games\ED\EDLaunch\Products</ProductsPath>
<GamePath>F:\Games\ED\EDLaunch\Products\FORC-FDEV-D-1003</GamePath>
<ProductAppData>C:\Users\<user>\AppData\Local\Frontier Developments\Elite Dangerous\Options</ProductAppData>

If you delete this file RN will create a new file - this should work.

Edit : Ok now I see a problem with the CommandesLogAutoSave.xml too.
Theres somthing missing at the end.
Delete this file - so a new one will craeted or add following lines at the end :

remove the last 5 lines:

<CommandersLogEvent>
<EventDate>2015-01-25T17:18:40.7899435+01:00</EventDate>
<EventType>Jumped to</EventType>
<Station />
<System>HIP 6237</System>

add:

</ArrayOfCommandersLogEvent>

the it should work again (I hope ;-) )

iAmLegion · Feb 7, 2015

Duke said:
Hm, I would say thats not the problem file.
Remove the RegulatedNoiseSettings.xml file or set the correct path in this file.
I think the <GamePath> or the <ProductsPath> is wrong.

my paths looks like this:

If you delete this file RN will create a new file - this should work.

Edit : Ok now I see a problem with the CommandesLogAutoSave.xml too.
Theres somthing missing at the end.
Delete this file - so a new one will craeted or add following lines at the end :

remove the last 5 lines:

add:

the it should work again (I hope ;-) )

I removed it all hehe, just as good.

Jawada · Feb 7, 2015

Duke said:
Default is off.
If you want to recieve the EDDN data you have to click "start listening" on the EDDN tab.
If you want to send your data to EDDN you have to check "Post data to EDDN in import" - it's default off.

Thanks a lot Duke!

Duke · Feb 9, 2015

for all with strange crashes:

you may test the 003beta : https://github.com/Duke-Jones/RegulatedNoise/releases/tag/1.8.4-0.0.3b

The errorhandler should show some more information on the reason

sutex · Feb 9, 2015

Duke said:
for all with strange crashes:

you may test the 003beta : https://github.com/Duke-Jones/RegulatedNoise/releases/tag/1.8.4-0.0.3b

The errorhandler should show some more information on the reason

COOL at GITHUD ,

iAmLegion · Feb 10, 2015

Seems updates has slowed down on this awesome program

*Edit*And now it is bugged again for me

sutex · Feb 10, 2015

iAmLegion said:
Seems updates has slowed down on this awesome program

*Edit*And now it is bugged again for me

Yes I think other life stuff has moved the devs on for a bit, Seen no post in a while, another DEV Duke is working on it now https://github.com/Duke-Jones/RegulatedNoise/releases

Originally Posted by sutex

Will the latest Base from GITHUD always be in sync with your International version,
I see no reference in GitHud issues of the list of bug fixes been closed by your fixes

Duke Yes, I want to sync it as fast as possible if there's a new version.
The fixes/changes I implemented were born on my personally needs - so at this moment
I didn't look really on the official buglist.

Originally Posted by sutex

"So if I override my current RN version with the International RN version, will the next GITHUD RN update , still be compatible"

Duke It should be. There are no changes on the internal datastructures. Only additional structures and improved functionality.
The next official version should run without problems. I also will have a eye on it for future versions.