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

Using ED in fullscreen to be able to use Nvidia DSR The tablet using idisplay I mentioned in previous post does not like full screen either.
The web server function in RN is the only way to go, but needs some work, when current issues at Githud have cleared , I'll raise it there. just giving you a heads up Duke.

Both RN & EliteCopilot https://forums.frontier.co.uk/showthread.php?t=82832&highlight=w0nk0 use the same address. for information to be displayed. So been experimenting with Voice attack to open and close both applications , if I need one or the other Web servers functions , again this is problematic in fullscreen, as I can lose window focus.
The goal, for me is to stay in game , no alt tabbing and just use the android tablet to control third party apps via touch screen or Voice attack
 
Last edited:
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

please try the 0.13 prerelease. I did some changes on this issue (and also on checking logfiles for current location).

@all: If you have some issues with 0.12 then have a try with 0.13 pre


Using ED in fullscreen to be able to use Nvidia DSR The tablet using idisplay I mentioned in previous post does not like full screen either.
The web server function in RN is the only way to go, but needs some work, when current issues at Githud have cleared , I'll raise it there. just giving you a heads up Duke.

Both RN & EliteCopilot https://forums.frontier.co.uk/showthread.php?t=82832&highlight=w0nk0 use the same address. for information to be displayed. So been experimenting with Voice attack to open and close both applications , if I need one or the other Web servers functions , again this is problematic in fullscreen, as I can lose window focus.
The goal, for me is to stay in game , no alt tabbing and just use the android tablet to control third party apps via touch screen or Voice attack

I'm not sure - would it help if you can choose the port of the RN webserver ?
To change this it's really a small piece in code.
 
Last edited:
I have the same problem. My ED is installed on drive N: and this app refuses to accept that and keeps popping up a "that doesn't seem right..." window. Not only that you can't cancel the app. I had to find the process and kill that. You need an Exit button. I tried point it at the My Pictures directory and it would not take that either.

Never mind the solution was posted above you need to point at the 'products' folder.
 
Last edited:
Hey Duke,

Firstly, thanks for the great work developing this further. Of all the various tools, this suits me the best and I'm sure that goes for quite a few others too. So, Thanks.

Now onto the obligatory 2p worth of how to make it better. On your ToDo list on Github, you've got "show distance in lists" which I guess is related to the distance to station you've just started to include; if you didn't already have it mind, it would be great if you could show the distances to both stations in the search results in the "Find Round-Trips" section on the Price Analysis, Station-To-Station tab. I guess you could achieve the same effect already by filtering on distance, but seeing the figure for each route would be nicer. Also, my near lay-person's assumption is that if you're already got distance data, showing in an extra column or 2 wouldn't be a huge job ;)

Having just made the leap to an Imperial Clipper, the only other major thing on my personal wish list is to show and filter searches based on Landing Pad size. I'd be more than happy to enter that info manually for each station if needed, though I if you're getting station distance info from the Station.csv file in the data subfolder - that's got max_pad_size in there.

I couldn't see Landing Pad size on your wish list, so if it's too big a job, I think the disable station option would be the next best.

Again, thanks for the good work :)
 
hey GW42, thank you for support.

feel certain that all of your wishes are planned - e.g. LandingPadSize-Filter.
The currently used database and datastructure is from EDDB. Unfortunately (and of course in cause of the size of the ED universe)
the data is incomplete so that's important to have a option to edit the existing stations/systems
or add complete new systems/stations. If this is done (it's in work now , you can test the prereleases on GitHub
- a StationToStarDistance-Filter is in the 0.13_4 prerelease. I cause of incomplete data I added a special option on the settings
tab for non-existing Station2Star informations) I will add more possibilities to set filters.

Duke


PS: the main database comes from EDDB - so I would be very lucky if you support this
database with feeding it with data. It's planned to realize a possibility to add station and system
base data (no price data) from RN directly to EDDB (if you enable this option) - but if you ask me when it comes ...

EDDB : http://eddb.io/ (request the database)
ROSS: http://ross.eddb.io/ (adding and editing system and station data to EDDB - LogIn needed)
 
Last edited:
PS: the main database comes from EDDB - so I would be very lucky if you support this
database with feeding it with data. It's planned to realize a possibility to add station and system
base data (no price data) from RN directly to EDDB (if you enable this option) - but if you ask me when it comes ...

EDDB : http://eddb.io/ (request the database)
ROSS: http://ross.eddb.io/ (adding and editing system and station data to EDDB - LogIn needed)
If you post commodity data to EDDN then missing stations will be automatically created on EDDB.
 
If you post commodity data to EDDN then missing stations will be automatically created on EDDB.

Yes, but not everyone wants to share the commodity data and if .... there are still no infos about the details (e. g. distance to star, landingpadsize....)
right ?
 
Last edited:
Yes, but not everyone wants to share the commodity data and if .... there are still no infos about the details (e. g. distance to star, landingpadsize....)
right ?

True. Just thought I'd point out the easy way :) Thanks for encouraging people to update EDDB, we recently broke the 15k station mark.
 
so, that you will not be bored I did again a new version:

v1.84_0_14

Changelog (thanks to "Pibbs Jawada", "Reno T [UGC]" and "iiooii") :

Code:
1.84_0.14_2
   * added a progress view for calculating best routes with cancel option
   * filter added : max. distance for trade routes
-------------------------------------------------------------------------------------      
1.84_0.14_1
   * changes on log scanning issue + additional log info
 
Last edited:
Lack of boredom is a good thing!

Works like a dream, Duke. Many thanks for the update.

so, that you will not be bored I did again a new version:

v1.84_0_14

Changelog (thanks to "Pibbs Jawada", "Reno T [UGC]" and "iiooii") :

Code:
1.84_0.14_2
   * added a progress view for calculating best routes with cancel option
   * filter added : max. distance for trade routes
-------------------------------------------------------------------------------------      
1.84_0.14_1
   * changes on log scanning issue + additional log info
 
ok new to this app, working well so far ,, but some station names get added wrong ,, like parckard goose ,, also seen as parckard goo'se etc etc ,, which file do i need to find to edit the wrong names and correct them ,,

thanks
 
The easiest way is to add the station to the eddb (see links in this post)
After the next dump you can download the current data with the new station included. Put the files into the "data" subdir


EDIT:
I hat a look into the EDDB and the station ist already included - 67 days before.
So it's another problem in your case.

The recognition of the station takes the ocr-assumed name.
And then it looks into the system data and gets all stations in the current
system (the system which is shown in the "System From LogFile" box).

Finally the station with the nearest approximation to the ocr-assumed name
is taken ..........hm, which version do you have runnin'

"RegulatedNoise 1.84" (development stopped 2 and a half months ago)

or

"RegulatedNoise DJ v1.84_0.14"

?

If you use the "RegulatedNoise 1.84" so it's a expected behaviour ;)

If your'e using "RegulatedNoise DJ v1.84_0.14" so it's at the moment not clear what the problem is :S
 
Last edited:
im not using EDDB as it crashs the app, i just got the app from link in 1st post which looks to be 1.84 , not 1.84_0.14 , but i noticed edit and del buttons in Price Analysis which allowed me to change the station names and some wrong added system names
 
quote_icon.png
Originally Posted by Duke https://forums.frontier.co.uk/showthread.php?t=97059&p=2097007&viewfull=1#post2097007

Hi themroc,

as you may know involuntarily I become the new main developer of "Regulated Noise".
28/01/2015 was the last time maxh2003 was logged in this forum and on the comments
on GitHub he also didn't respond.

So I spent much time on the development of the program and I started -among other things- to implement the
structure of the eddn json files into RegulatedNoise. This step is finished now and RegulatedNoise uses now the EDDB data
as it's base data for route calculating and all other stuff which is included or will be included in near future in RegulatedNoise.
For updating the local data it's only necessary to download the EDDB json files and put them into the data subdir of RegulatedNoise.

The next step (I'm currently working on it) is to give a option to complete incomplete data or add
not existing data (systems and stations) into the program (means into the local EDDB json files) .
So the player has the possibility to correct/add some data - and therefore the implemented filters and
data views in RegulatedNoise can work correct if the gamer has found a new system or station
(even if the data is not in the EDDB yet).

The idea now:
If EDDB would have a option to upload the data of systems and stations I
would use this interface. Also the small infos (which normally only manually with
ROSS can be added) like "landing pad size" or "has blackmarket" can be
filled from RegulatedNoise. The possibility to add or changed data through
this API should be bound to a existing ROSS account - so only registrated users
can use this way of filling the database.

At this moment I'm only asking for a upload function for filling the EDDB database
with missing data. I think it's ok if the update (download) of the local RegulatedNoise
databases still working through manual download of the EDDB json files.

What do you think about the possibility to add missing stations and systems or
set missing informations like MaxLandingPadSize for a station on the direct way?

Duke Jones

Hey Duke,

can you hit me up on IRC? Just go here: http://webchat.quakenet.org/?channels=eddb
I guess we should talk about that issue.

Best
themroc

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


And the outcome is ...... :eek:
 
And the outcome is ...... :eek:

Didn't spoke to him yet ....
Maybe this evening....

@all : there's a new pre-release out - please check if you like....

Changes:
Code:
1.84_0.15_1
   * auto show systemdata
   * port of webserver is adjustable
   * show number of stations in system
   * completed splash screen
   * optimized program start behaviour
   * viewing of station data (not finished)


And the outcome is ...... :eek:
It's not so easy as it seems - so it will not come in near future.
As a first step maybe a api comes to announce the base data of unknown systems/stations in eddb
- but without detail data like landing pad size and distance to star.
You still have to add those info with ROSS.
 
Last edited:
Back
Top Bottom