In-Development TradeDangerous: power-user trade optimizer

I just have had the worst trade run in a long time. I used age=2 and still had loads of horrible stale data.

Now, according to TD, the data wasn't stale and so it appears it was doing its job, certainly after I uploaded, the data was up to date and correct again.

Example, data less than 24 hours old (same station, before & after I landed) - you can see how this ruined my profit for this hop:

Code:
Basic Medicines                  4986       0    207198H         -  2018-07-03 07:18:29
Basic Medicines                   423       0       641M         -  2018-07-04 03:25:56


This happened all the way along a 10 hop route (and not just medicines). Prices all out of whack. So - I don't know what to make of it. Has something happened which caused a lot of prices to shift wildly? Has a load of crappy data got into the system somehow? Has TD somehow wierded out its dates and pooped out a broken DB?

I suspect it's not TD - but figured I'd throw it out here for discussion.
 
Last edited:
Gratz. Toss up for me, I may make explorer before trader. Home stretch for both.
I'm 80% to rear admiral. Then it's off to grind empire ranks, and then finally maybe I'll leave the bubble. I'm only Ranger for explorler, so I have a ways to go for elite there. I don't ever plan on getting elite in combat. That's not my strength.
 
I just have had the worst trade run in a long time. I used age=2 and still had loads of horrible stale data.

Now, according to TD, the data wasn't stale and so it appears it was doing its job, certainly after I uploaded, the data was up to date and correct again.

Example, data less than 24 hours old (same station, before & after I landed) - you can see how this ruined my profit for this hop:

Code:
Basic Medicines                  4986       0    207198H         -  2018-07-03 07:18:29
Basic Medicines                   423       0       641M         -  2018-07-04 03:25:56


This happened all the way along a 10 hop route (and not just medicines). Prices all out of whack. So - I don't know what to make of it. Has something happened which caused a lot of prices to shift wildly? Has a load of crappy data got into the system somehow? Has TD somehow wierded out its dates and pooped out a broken DB?

I suspect it's not TD - but figured I'd throw it out here for discussion.

That is certainly weird. TD does have a few weirdnesses when it comes to dates. I'm seriously considering converting the TD DB's dates to the epoch format EDDB and EDDN use, just to make that a bit less of a hassle.
 
I find myself double checking some wierd TD entries directly on EDDB. Sometimes it's just wildly stale data.

Trouble is, I don't generally notice until I land (I mean that bad data was supposedly less than 24 hours old) and by then my ED tools have automatically uploaded new data to EDDB and I can't check against their records.
 
That is certainly weird. TD does have a few weirdnesses when it comes to dates. I'm seriously considering converting the TD DB's dates to the epoch format EDDB and EDDN use, just to make that a bit less of a hassle.

I get the feeling that Oliver was just too wedded to his .prices format and that without Maddavo to provide (effectively) a middleware interface from eddb --> .prices, TD can get upset. Realistically, it would have been better coded to stay closer to the data format of the source, rather than doing unnecessary conversions, with the associated possibility of errors.
 
TDs prices format does copy the commodity market screen of the game. You know, we did manually input the data with an texteditor first and it was very good that the format to input it was the same we saw on screen. EDDN and EDDB came later.
 
TDs prices format does copy the commodity market screen of the game. You know, we did manually input the data with an texteditor first and it was very good that the format to input it was the same we saw on screen. EDDN and EDDB came later.

Wow. I don't remember doing that and I was premium beta. Maybe I was using Slopey at the time, laughing as the community described his and other tools as some kind of ED Ragnarok. Let's see... my earliest post in this thread is December 2014 and I'm in the changelog for early 2015.

So I still claim I'm an early adopter, but I don't remember typing in prices by hand. I remember EliteOCR.
 
Last edited:
TDs prices format does copy the commodity market screen of the game. You know, we did manually input the data with an texteditor first and it was very good that the format to input it was the same we saw on screen. EDDN and EDDB came later.

I remember it well!

Wow. I don't remember doing that and I was premium beta. Maybe I was using Slopey at the time, laughing as the community described his and other tools as some kind of ED Ragnarok. Let's see... my earliest post in this thread is December 2014 and I'm in the changelog for early 2015.

So I still claim I'm an early adopter, but I don't remember typing in prices by hand. I remember EliteOCR.

Oh yes, I remeber typing it in by hand; OCR never worked properly for me.
 
I have just uploaded a new beta version of TD Helper 2, version 2.0.3.0.

Introduction

Version 2.0.3.0 adds a number of new features and as some of them are breaking changes it is highly recommended that you install this version as a fresh install.

The major change of this version is moving from individual XML configuration files, one for each ship plus the default configuration, to a single INI file that contains all the settings, including the ship data.

This INI configuration file is constructed by TDH2 on start up if the file is not found and the ship variables are updated each time the 'Cmdr Profile' button is pressed. The laden and unladen jump ranges of all the ships and the cargo capacity of all but the currently used ship are not changed when the profile is read unless it is the first time the ship is seen in the which case they are set to 1.

The current settings are saved on exit including the currently selected ship in TD Helper and at other suitable times during useage.

I have also included a warning message when the system is loading up the net logs after TDH2 is started since this can take some time. Once these have been loaded, the pilot's log populated and any favourite locations added to the source system/station list, the message will disappear that the form will be enabled for use. This warnig only diplays if the process has taken longer than 5 seconds.

If you should sell a ship in the game simply run the 'Cmdr Profile' and TDH2 will notice the missing ship and remove its data from the configuration file.

The most noticable change in TDH2 is that the controls on the main form have been rearranged into a slightly more logical layout and to accomodate a much wider ship list. The ship data, for example, are aranged close to the ship selector button, the stock related controls are also grouped together and so on. This was done primarily to allow a wider ship list as the previous width was way too small.

The update facility has been updated so that changes can be automatically downloaded. To switch this off tick the 'Disable auto-updating' check box on the settings form.

The speed at which the net log files are processed has been reduced by virtue of ignoring ones that have a time stamp older than the latest entry in the database.

Once I have have some feedback from the beta testers and fixed any issues, I think it is time to let this out into the wild with a production release.

As before, the beta release can be found at https://github.com/MarkAusten/TDHelper/releases and the set up instructions in the wiki.

Thanks.
 
Last edited:
Hi, Mark.

I don't use TDHelper, but when I run TD, I often put in more than the minimum for insurance. Should the worst happen, I want to rebuy my ship AND have enough capital to take advantage of its capacity right away to start rebuilding my nest egg.Thankfully that isn't an issue right now, but when I make that last 40% to Rear Admiral and spend my hard-earned credits on a Corvette, I might need to do that again :)

Just a thought.

I had second thoughts about this and decided to leave it unchanged. If the user wishes they can increase the re-buy percentage to allow a bit of leeway when running TD and this means that a new field for the addition buffer amount is not required.
 
I had second thoughts about this and decided to leave it unchanged. If the user wishes they can increase the re-buy percentage to allow a bit of leeway when running TD and this means that a new field for the addition buffer amount is not required.
Fair enough; 'twas just a thought :)
 
Mark - found a typo in your "Set for Beta Testing instructions". Its where you have "Open a CMD window to the cdce_client folder and enter the following command: python ecde-setup.py "

It should read python edce-setup.py As a copy and paste user I was wondering what was going wrong trying to run that command!

Just going through the rest of the setup for 2.0.1.1 now.

Errrm... the way I see it, you need to run

python client-setup.py

I've got version 2.0.1 - is that the correct one?
 
Hi Mark - You don't need to separately download eddblink as per your setup guide. If you are downloading eyeTD, it comes bundled.

Are you sure?

I ask as when I wrote those instructions a week or so back, the file in the Eyeonus TD installation was not the same version as the latest one in the EDDBlink repository.
 
Back
Top Bottom