In-Development TradeDangerous: power-user trade optimizer

Why would he want to do that? It's nothing to do with your problem, it's something else. :)
so i can see why he is getting that message :p he probably added a space or something that and the error message does say press OK first and then take a sreenshot
 
Last edited:
delete all 3 boxes and retype the numbers and where that question mark is in the supply make sure you put a letter H M L for high medium and low also like what he said they were probably much higher then you are setting them for so you've hit a percentile barrier
 
Last edited:
I'm assuming the values you entered are correct. That warning is shown if the difference is more than 25% of the paying for price.. the difference in the above case is ~35% so you get the warning. ksfone may have to put in a special case for low price items.

I've mapped biowaste this evening at

14 19
11 14
14 19
15 20
11 14
14 19
 
I've mapped biowaste this evening at

14 19
11 14
14 19
15 20
11 14
14 19

those look accurate prices, it's just the difference between the sell/buy prices that triggered the warning. Just press ok. Glad you posted those prices, ksfone can look at some additional logic for them.

Did all of those prices in your list bring up the warning?
 
Did all of those prices in your list bring up the warning?
None of them did, I haven't tried importing them yet, they are screen grabs I made. I was just providing additional evidence that this isn't a fluke. Those are the only 6 stations I visited this evening where I captured price data.
 
there needs to be a easier way of getting prices, i herd that Elite Dangerous Data Network is in alpha now though

[sub]
It's long since time I posted this...

Announcing Elite Dangerous Data Network alpha test!

For full details see https://github.com/jamesremuscat/EDDN/wiki - which not coincidentally is also the Git source code repository for the project.

Quick summary:


There's a sample Python application in the Git repo - see Client.py.

This is half of what's needed - the other important thing is defining the format of the message. What's there currently is a starting point, but the questions for you all are:
  • What else needs to be in the market data message?
  • What other data would people be interested to see distributed over EDDN?

I'll be continuing to read this thread - and since I'm not back in the office until the new year, I should even have time to fix things if/when they break!
[/sub]



but also would be cool if we could get some kind of api going lol but has to be some easier way other than typing in every single number for every station and resource like that 1 tool where it takes screenshots and uses image recognition to see the numbers
 
Last edited:
im trying to add a station in the stationfile but what do i put in the number? 'Lhs 1914','Payton Orbital',here do i put a 0 or another number
 
im trying to add a station in the stationfile but what do i put in the number? 'Lhs 1914','Payton Orbital',here do i put a 0 or another number

Aside: I just checked in a possible fix for the mfd drivers, grab latest code and try a run command with "--check --x52" on the end, see if it works.

If you're adding a station, or updating an existing one, there a 3 columns in the .csv file:

'System Name','Station Name',distance

The third number should be 0.0 or the number of light seconds from the star to the station - basically the distance you get when you jump into the system.
 
there needs to be a easier way of getting prices, i herd that Elite Dangerous Data Network is in alpha now though

[sub][/sub]



but also would be cool if we could get some kind of api going lol but has to be some easier way other than typing in every single number for every station and resource like that 1 tool where it takes screenshots and uses image recognition to see the numbers

You don't *have* to type in all the prices yourself, you can crowd source if you want to use something like maddavo's. You can also use a text editor instead of the UI and only update *some* prices. E.g.

Code:
C:\trade\> trade.py update --notepad -T beagle2

This will open the data in a text presentation, with timestamps.

If you edit a line, just remove the timestamp.

Code:
@ ASELLUS PRIMUS/Beagle 2 Landing
   + Chemicals
      Hydrogen Fuel               101     102          ?     7863?  2014-11-26 15:56:05
      Pesticides                  176     190          ?     3774?  2014-11-26 15:56:05
   + Consumer Items
      Clothing                    326       0          ?         -  2014-11-26 15:56:05
      Consumer Tech              6951    7026          ?     1882?  2014-11-26 15:56:05
      Dom. Appliances             544       0          ?         -  2014-11-26 15:56:05
   + Foods
      Animal Meat                1553       0          ?         -  2014-11-26 15:56:05
      Coffee                     1630       0          ?         -
      Fish                        929       0          ?         -  2014-11-26 15:56:05
      Food Cartridges             218       0          ?         -  2014-11-26 15:56:05
      Fruit and Vegetables        450       0          ?         -  2014-11-26 15:56:05

(I edited 'Coffee')

After you're doing editing - by the UI or text editor - TD leaves a copy of your change as "updated.prices" which you can then upload to a site like mads.

Mad will ignore the "old" values and only use the ones you've changed.

The downside to this approach is that "Coffee" will now be timestamped as being recent data - we know that on 2014-12-15 it was 1630. But our data for everything else is old. If Coffee was the only thing that had changed at the station, there's no indication. All we know is that it was at price X on 2014-11-26.

To fix this, you have to actually /change/ every line by removing the old timestamps.

This actually turns out to be more work than just altering the prices that changed and letting it timestamp everything together.
 
Thanks, dude. I guess ... everyone to Wescott Terminal? :)

In seriousness - it does this when there is a >25% difference between the buy and sell price, but it looks like frontier take rounding into account before doing the comparison.

I've changed the code; 14:19 should now fly.

Let me know if I need to extend it further.

Oliver - thanks for all your hard work.

I had a couple today at 13:19 hope this works too!
 
Thanks, dude. I guess ... everyone to Wescott Terminal? :)

In seriousness - it does this when there is a >25% difference between the buy and sell price, but it looks like frontier take rounding into account before doing the comparison.

I've changed the code; 14:19 should now fly.

Let me know if I need to extend it further.

ya i had like 5 or 8 or so stations do that to me today most which were located in LHS 1914 but some was in NIMA and BRANGLAL
 
That could be from my TD_Export plugin from EliteOCR. I set the systemname to !UNKNOWN! if it's blank.

It should not be that hard to look up the system name from a station name. As much as I thank you for supporting these entries do not help at all in the prices file. Please take these few extra seconds to make your contributions useful.
 
It should not be that hard to look up the system name from a station name. As much as I thank you for supporting these entries do not help at all in the prices file. Please take these few extra seconds to make your contributions useful.

It must also be recognised that people like gazelle are trying hard to add value and efficiency to the data capture. He's put his hands up and suggested that the error may be his 'fault', but at least he's trying to help.
 
Back
Top Bottom