Release ED-Intelligent Boardcomputer Extension

Duke, vielen Dank für Regulated Noise! Super Tool. +Rep!
I have a quick question though: when I update the version, can I unzip the newest version into the old folder or will that overwrite my data, settings and calibrations?

Also, demand/supply levels in my data are often named wrongly (LOW insted of MED etc.) although the numbers are recognized correctly. Is that normal behaviour?
Finally, on my screen there is a lot of white in between the different parts of the tool etc. and the splash screen also looks funny - see screenshots. Doesn't bother me much, but I thought you might want to know. I am running 1920x1080.

Again, thanks a lot!


btw: you runnin' the 0.20 - it's one of the worst versions - please update immediately :D
 
Can someone tell me how I can change the path RN uses to find the log files? I installed the Steam version of ED so all the logs are under that new directory but RN does not seem to have a way of pointing it at the new path. I tried renaming the old Frontier directory thinking RN would ask me where the files were as it did when first installed but it just crashed RN. Alternatively maybe someone could tell what file to manually modify? Perhaps the prog needs the functionality added. EliteOCR allowed me to so it.
 
Last edited:
Can someone tell me how I can change the path RN uses to find the log files? I installed the Steam version of ED so all the logs are under that new directory but RN does not seem to have a way of pointing it at the new path. I tried renaming the old Frontier directory thinking RN would ask me where the files were as it did when first installed but it just crashed RN. Alternatively maybe someone could tell what file to manually modify? Perhaps the prog needs the functionality added. EliteOCR allowed me to so it.

open RegulatedNoiseSettings.xml and delete the two lines starting with

<ProductsPath>....
<GamePath>...
 
Aw! Now you done broke it! :) I tried ignoring the error but now Price Comparison by Station has no system names in dropdown (though 'By Commodity' shows all the data is there). Never mind, I will delete the whole thing and start again. I still have all the CSVs so it is only the commanders logs that I lose and that is not a major issue. Jiust giving you this info in case there is something you want to fix.

Addendum: I renamed the old directory. Can I move across the Commanders Log files from there? Do I also copy across the CommandersLogAutoSave? What about the .bak version?

----------------------------------------------------------------------------------------------------------------------------------------------

2015/05/31 08:58:42: ERROR: Error in main init function
2015/05/31 08:58:45: ERROR: System.IO.IOException: Cannot create a file when that file already exists.


at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIOError()
at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
at RegulatedNoise.Form1.SaveSettings() in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 1198
at RegulatedNoise.Form1.cbActivateOCRTab_CheckedChanged(Object sender, EventArgs e) in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 6189
at System.Windows.Forms.CheckBox.OnCheckedChanged(EventArgs e)
at System.Windows.Forms.CheckBox.set_CheckState(CheckState value)
at System.Windows.Forms.CheckBox.set_Checked(Boolean value)
at RegulatedNoise.Form1.ApplySettings() in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 850
at RegulatedNoise.Form1..ctor() in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 243
2015/05/31 08:58:45: ERROR: Cannot create a file when that file already exists.


2015/05/31 08:58:45: ERROR: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIOError()
at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)
at RegulatedNoise.Form1.SaveSettings() in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 1198
at RegulatedNoise.Form1.cbActivateOCRTab_CheckedChanged(Object sender, EventArgs e) in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 6189
at System.Windows.Forms.CheckBox.OnCheckedChanged(EventArgs e)
at System.Windows.Forms.CheckBox.set_CheckState(CheckState value)
at System.Windows.Forms.CheckBox.set_Checked(Boolean value)
at RegulatedNoise.Form1.ApplySettings() in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 850
at RegulatedNoise.Form1..ctor() in e:\dev\VS2013\RegulatedNoise.git_DukeJones\RegulatedNoise\Form1.cs:line 243
 
Last edited:
Hm, if I delete both lines it's working - no crash.
Are you sure you've not wrecked the xml structure ? (e. g. deleted to much or too less ?)

simplest way is to copy the new RegulatedNoiseSettings.xml from the new directory to the old direcory and
then re-rename the directory to the old name.
In this direction you've only 1 file to copy
 
Last edited:
new version out:

Code:
1.84_0.25
   * added new translations to commodities
   * added latest EDDB data files
   * all EDDN setting are saved 
   * autostart of EDDN is possible
   * fixed: crash when open warnlevel-listview 
   * add warnlevel-object for user added commodities
   * fixed: crash when open warnlevel-view from "edit/delete ocr results" table
   * preparation for ED 1.3 : saves now commodities added by user, even if RN is updated ( --> \Data\Commodities_own.xml)
   * fixed crash while adding new, unknown systems
 
Last edited:
I am getting a "Not Responding" message each time my ship moves to a new system. That is each time the log file changes.
This can last for 3 or 4 minutes so some trips are missed.
It seems to be due to the length of the log.
A new install does not exhibit the problem.

I am using Windows 8.1 and latest Regulated Noise.

Could you make the Commanders log export to CSV format please.

Regards
 
Last edited:
Guys, for a day our two there are quite wrong data coming from EDDN making impossible high profit roots. Maybe it is a lame question but how can I delete these wrongly scanned stations?
 
Do you have some samples of those data ?

Sure, please check the attached screenshot.

EDDNerror.jpg
 
Guys, for a day our two there are quite wrong data coming from EDDN making impossible high profit roots. Maybe it is a lame question but how can I delete these wrongly scanned stations?

- you can purge ALL EDDN data (button on "EDDN" tab )
- you can delete specific datasets of a station ("By Station" tab)
- you can delete specific datasets of a commodity ("By Commodity" tab)
- you can delete all data which is older than x days (setting tab, right side at the bottom)

General recommendation:
Set all "-1" values of the plausibility-limits to a value that is plausible.
So such values will be blocked. A value of -1 means "do not consider"
this limit for this commodity.
-
 
Last edited:
- you can purge ALL EDDN data (button on "EDDN" tab )
- you can delete specific datasets of a station ("By Station" tab)
- you can delete specific datasets of a commodity ("By Commodity" tab)
- you can delete all data which is older than x days (setting tab, right side at the bottom)

General recommendation:
Set all "-1" values of the plausibility-limits to a value that is plausible.
So such values will be blocked. A value of -1 means "do not consider"
this limit for this commodity.
-

Sorry Duke, I do not really get what you say. I have never touched any settings - these data just started to appear some days ago.
Where should I set the plausbility limit?

Thanks!
 
Are you talking about the -1 data ?
All others prices seems legit to me
See:
- http://ed-td.space/en/11/Station/idSys/10107/nSys/Jeterait/idSta/10791/nSta/Barnard+Port
- http://ed-td.space/en/11/Station/idSys/19521/nSys/Yawa/idSta/393/nSta/Dean+Hub

Strangely -1 should not be a value sent to EDDN.
Do you have any date that can point me to the log so I can see who is doing that ?

on the settings tab next to the "purge older data" button is a
button "edit commodity price warn levels". Replace all -1
with a plausible values

OR (at least)

set every unknown range to "0"

I try to explain:
in each case there are 2 values building a range for
* "demand sell"
* "demand buy"
* "supply sell"
* "supply buy"

Set the two values every range to plausible values
OR (if you have no idea)
set both values to a zero range :
e. g. "Demand Sell Low" is -1, "Demand Sell High" is 4500
then set "Demand Sell Low" also to 4500.

But then every incoming price will rejected as implausible unless it's exacty 4500.

If you work with EDDN it's difficult because there's at the moment no function to
update the warn levels from rejected EDDN data (it's planned) but if you
scan prices yourself you will be informed about implausible data and then you can
update every "zero" price range step by step (or scan by scan ;-) )

Sorry, it's not perfect - it was just a "quick made" emergency brake to notice
if you scan wrong prices and also reject wrong prices from EDDN

PS: if both values of a range are -1 so set both to somthing like 1 or whatever
remember: "-1" means "ignore limit"

PPS:
The price warn levels will be calculated on first run of RN.
They come from the file "station.json". For every commodity
the max and min price will be collected from all existing prices from EDDB.
These values are the values for the warn levels
They never will be automatically updated in the current versions of RN

but you can force a recalculation:
delete the file "commodities_RN.json" from the data subdir.
On next start the warn levels will be recalculated from the
existing stations.json
(I recommend before recalculation to get the latest stations.json with the latest prices from the EDDB website)
and then don't forget to change all "-1" again
 
Last edited:
on the settings tab next to the "purge older data" button is a
button "edit commodity price warn levels". Replace all -1
with a plausible values

OR (at least)

set every unknown range to "0"

I try to explain:
in each case there are 2 values building a range for
* "demand sell"
* "demand buy"
* "supply sell"
* "supply buy"

Set the two values every range to plausible values
OR (if you have no idea)
set both values to a zero range :
e. g. "Demand Sell Low" is -1, "Demand Sell High" is 4500
then set "Demand Sell Low" also to 4500.

But then every incoming price will rejected as implausible unless it's exacty 4500.

If you work with EDDN it's difficult because there's at the moment no function to
update the warn levels from rejected EDDN data (it's planned) but if you
scan prices yourself you will be informed about implausible data and then you can
update every "zero" price range step by step (or scan by scan ;-) )

Sorry, it's not perfect - it was just a "quick made" emergency brake to notice
if you scan wrong prices and also reject wrong prices from EDDN

PS: if both values of a range are -1 so set both to somthing like 1 or whatever
remember: "-1" means "ignore limit"

PPS:
The price warn levels will be calculated on first run of RN.
They come from the file "station.json". For every commodity
the max and min price will be collected from all existing prices from EDDB.
These values are the values for the warn levels
They never will be automatically updated in the current versions of RN

but you can force a recalculation:
delete the file "commodities_RN.json" from the data subdir.
On next start the warn levels will be recalculated from the
existing stations.json
(I recommend before recalculation to get the latest stations.json with the latest prices from the EDDB website)
and then don't forget to change all "-1" again

Thanks Duke, I will give a try!

However just came across a problem: scanned a station at Nungamici (Roosa Hub). Resonating Separators are neiter demanded nor supplied. The sell preice is 5341, the buy price is 5391. The OCR halts with implausible data for this commodity. No matter how I change the warn levels, the OCR does not move on.
Any idea?
 
can you post screenshots please :
1 x from the station market (the F10 Screenshot)
1 x from the implausible data list
 
Back
Top Bottom