Sorry DRY411S, the last line in the Default.xml is:"<CopySystemToClipboard>false</CopySystemToClipboard>" and also in your ship.xml (sorry for my bad english :-() . If you change the path to the log-files (<NetLogPath> ...) , TDHelper find the correct system and station but the pilots-log is not updated. Can anyone correct this ?
In my case, I needed to edit that xml file as well as Default.xml
In the new Elite Dangerous path you need to edit the AppConfig.xml tp switch on VerboseLogging. If you don't do that, the NetLog will not contain the system name for the Pilots Log.
Ok DRY411S, thats right. I edit the AppConfig.xml and set VerboseLogging=1. Since that TDHelper shows me the right system and station in the input-windows top left, but in the "pilot's log" are only old messages. Did you have correct systems and stations in your pilot-log ?
Ok DRY411S, thats right. I edit the AppConfig.xml and set VerboseLogging=1. Since that TDHelper shows me the right system and station in the input-windows top left, but in the "pilot's log" are only old messages. Did you have correct systems and stations in your pilot-log ?
Hello, I've been using Trade Dangerous since yesterday. I've notice that sometimes the calculations would on purpose select stations that does not have markets, like KAIAKUL/Bliss Gateway. I've attempted to manually update the data and had maddavo --reset-all to fix it but no matter what whenever I tell it to do the calculation on a specific origin it keeps telling me to go to KAIAKUL/Bliss Gateway.
Is there a way to fix this? I've been searching for hours and some reason can't figure out how to solve this. I'm using this app on linux in a seperate computer if that make any difference.
first, sorry for my english but maybe I can help you. I understand you want to exclude stations. Is that right ? Then you can use the command "avoid". Put the stations or systems in the input window next to "avoid" and the stations are skipped in the calculation.
Well, not exactly exclude I just want to have the database updated. So if I were to tell it to calculate the run again for me it won't output stations that have no market for it. Right now, even after updating the database to say there is no market using, trade.py "Bliss Gateway" --market N , it will still tell me to go to that station. I can use the command avoid but what about other station that is similar to bliss gateway? I wouldn't know if that station have a market or not unless I search it up before hand.
I've also corrected other stations that have no market but when I tell it to calculate a run in the area of that those station it will include them.
Ok, sorry, now I understood. Puhhh, the problem I had not yet. I have no idea how to get around the problem. Sorry ! I think this problem came with the Update. I have tested just TD and I got no result.
Here my command: trade.py" run --fr="HIP 83716" --cap=32 --ins=1900000 --cr=17000000 --ly=22 --empty=23.3 --pad=LM --gpt=1400 --hops=3 --jum=6 --start=2 --ls-max=6000 --age=30 --loop -vv
But Update the database with maddavo is no problem.
Hey maddavo (if you read this) do you have any idea ?
Ok, sorry, now I understood. Puhhh, the problem I had not yet. I have no idea how to get around the problem. Sorry ! I think this problem came with the Update. I have tested just TD and I got no result.
Here my command: trade.py" run --fr="HIP 83716" --cap=32 --ins=1900000 --cr=17000000 --ly=22 --empty=23.3 --pad=LM --gpt=1400 --hops=3 --jum=6 --start=2 --ls-max=6000 --age=30 --loop -vv
But Update the database with maddavo is no problem.
Hey maddavo (if you read this) do you have any idea ?
Well, not exactly exclude I just want to have the database updated. So if I were to tell it to calculate the run again for me it won't output stations that have no market for it. Right now, even after updating the database to say there is no market using, trade.py "Bliss Gateway" --market N , it will still tell me to go to that station. I can use the command avoid but what about other station that is similar to bliss gateway? I wouldn't know if that station have a market or not unless I search it up before hand.
I've also corrected other stations that have no market but when I tell it to calculate a run in the area of that those station it will include them.
OK, there's a few things going on there. Firstly, lets address the updating, then the data, then the run.
So it sounds like you are getting updates OK? To confirm - what happens when you run this command:
trade import -P maddavo -O corrections,stations,shipvendors,exportcsv
As an example - this is what happens in my shell:
Code:
C:\Users\Dave\Documents\TradeDangerous>trade import -P maddavo -O Corrections,Stations,exportcsv,shipvendors
NOTE: Importing Corrections
NOTE: Importing Stations
NOTE: AULIN/Kuo City (#3263) updated in local db: mkt('Y'=>'N')
NOTE: BELALANS/Shoemaker City (#4737) updated in local db: mkt('Y'=>'N')
NOTE: ELEU/Bradshaw Station (#9325) updated in local db: mkt('Y'=>'N')
NOTE: ELEU/Pierce Gateway (#9328) updated in local db: mkt('Y'=>'N')
NOTE: KAIAKUL/Bliss Gateway (#20659) updated in local db: mkt('Y'=>'N')
NOTE: KAUSHPOOS/Norgay Port (#21312) updated in local db: mkt('Y'=>'N')
NOTE: KHARINDA/Chargaff Hub (#21506) updated in local db: mkt('Y'=>'N')
NOTE: MARIDAL/Dedman Gateway (#27195) updated in local db: mkt('Y'=>'N')
NOTE: RAPA BAO/Thomson Orbital (#32714) updated in local db: mkt('Y'=>'N')
NOTE: Importing ShipVendors
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Category.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Item.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\System.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Station.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Ship.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\ShipVendor.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\RareItem.csv re-exported.
NOTE: Requesting http://www.davek.com.au/td/prices-3h.asp
NOTE: Downloaded 473.6KB of gziped data 2.5MB/s
NOTE: 23 stations updated:
DEVAKU/Howe Terminal, KHAIMA/Artyukhin Terminal, PSI TAURI/Blackwell Station, LP 302-22/Clement Dock, LALANDE 43492/Polansky Hub, SANKA/Wilson Depot, XUANDUNA/Check Ring, TJURINAS/Herndon Dock, ZHOU :):):):)/Rosseland Station, ACIHAUT/Cuffey Plant, ...
NOTE: Import complete: 3000 updated and 128 new items over 56 stations in 48 systems
NOTE: Import completed.
Next lets talk about data. If you're worried that the data is out-of-sync or is bad somehow, you can do an update, do a buildcache and an update, or do a complete wipe and an update. The last one will definitely work. You know how to do an update. To do a buildcache (this rebuilds your local database from the data files in your data folder:
trade buildcache -fi
A buildcache is forced by TD before any command whenever it detects that a data file has been touched later than the local database - but from memory it is not run with the "i" option which ignores errors. So you could just open any data file like the Station.csv - resave it - and the next TD command will also do a buildcache.
Lastly - to wipe the data you can just delete the TradeDangerous.db file. But the when the database is rebuilt it may be using bad data so you also replace the Station.csv, ShipVendor.csv and TradeDangerous.prices from Maddavo Market Share . Then you can do a buildcache and it will build the database with completely fresh data.
Now time to note something - what does market 'N' mean? Well, it means that in the Station.csv the market has been set to N (no market). BUT note that sometimes there might be a station that had a market and now doesn't. The prices for that station are still in the TD.prices file and still in the database. Changing the market -> N doesn't get rid of the prices. TD has a behaviour where if it detects prices for a station then it will set market -> Y. So what you may find is that a station you set market -> N will sometime later magically have switched back to market = Y.
When you generate the run that takes you to somewhere that doesn't have a market anymore - I venture that it is picking up those old dead prices. So, you can delete the prices by doing an update on the station and manually setting all the prices to zero.
I have been wary of deleting prices for stations where their market = N. This is because sometimes in the past the value has been changed to N by accident - and if I deleted the prices then well, they're gone. There are 9 stations that keep popping up market Y -> N whenever I do a station import to TD. I haven't tried trading around any of them so I haven't come across your issue. I'll have to look further into it and work out what's best to do.
I have taken ShipVendor updates offline from Maddavo Market Share as it is causing a performance issue at the moment. I cannot address it until after new years in January.
With the API back up there will be many people collecting prices from planetary markets. This is great, BUT please be aware that the station must be in the Station.csv before prices are accepted for a station. This hasn't happened for ages because we had a full list of space-based stations. But now we have to add planetary stations. I have already seen on EDDN that there are many stations coming through with incorrect name spellings so I cannot allow them to be made automatically from EDDN.
To add a station to the MMS Station.csv there are a few methods:
* Add it locally, export your Station.csv and the upload it (but until the station add command supports the 'planetary' field then the station won't be marked as planetary.
* Add it to EDDB.IO using ROSS (MMS syncs with ROSS every 24hrs so there can be up to a day delay)
* Add it to MMS directly using http://www.davek.com.au/td/editstations.asp
I have created a "horizon" branch with "planetary" support in my bitbucket repo:
Code:
Added "planetary" column to station table and maddavo import.
Added "--planetary" argument to station command.
Added "--no-planet" switch to buy, local, nav, rares, run and sell command.
Added "Plt: X" output.
I havn't tested it much. You can try it out if you want.
I have taken ShipVendor updates offline from Maddavo Market Share as it is causing a performance issue at the moment. I cannot address it until after new years in January.
OK, there's a few things going on there. Firstly, lets address the updating, then the data, then the run.
So it sounds like you are getting updates OK? To confirm - what happens when you run this command:
trade import -P maddavo -O corrections,stations,shipvendors,exportcsv
As an example - this is what happens in my shell:
Code:
C:\Users\Dave\Documents\TradeDangerous>trade import -P maddavo -O Corrections,Stations,exportcsv,shipvendors
NOTE: Importing Corrections
NOTE: Importing Stations
NOTE: AULIN/Kuo City (#3263) updated in local db: mkt('Y'=>'N')
NOTE: BELALANS/Shoemaker City (#4737) updated in local db: mkt('Y'=>'N')
NOTE: ELEU/Bradshaw Station (#9325) updated in local db: mkt('Y'=>'N')
NOTE: ELEU/Pierce Gateway (#9328) updated in local db: mkt('Y'=>'N')
NOTE: KAIAKUL/Bliss Gateway (#20659) updated in local db: mkt('Y'=>'N')
NOTE: KAUSHPOOS/Norgay Port (#21312) updated in local db: mkt('Y'=>'N')
NOTE: KHARINDA/Chargaff Hub (#21506) updated in local db: mkt('Y'=>'N')
NOTE: MARIDAL/Dedman Gateway (#27195) updated in local db: mkt('Y'=>'N')
NOTE: RAPA BAO/Thomson Orbital (#32714) updated in local db: mkt('Y'=>'N')
NOTE: Importing ShipVendors
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Category.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Item.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\System.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Station.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\Ship.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\ShipVendor.csv re-exported.
NOTE: C:\Users\Dave\Documents\TradeDangerous\data\RareItem.csv re-exported.
NOTE: Requesting http://www.davek.com.au/td/prices-3h.asp
NOTE: Downloaded 473.6KB of gziped data 2.5MB/s
NOTE: 23 stations updated:
DEVAKU/Howe Terminal, KHAIMA/Artyukhin Terminal, PSI TAURI/Blackwell Station, LP 302-22/Clement Dock, LALANDE 43492/Polansky Hub, SANKA/Wilson Depot, XUANDUNA/Check Ring, TJURINAS/Herndon Dock, ZHOU :):):):)/Rosseland Station, ACIHAUT/Cuffey Plant, ...
NOTE: Import complete: 3000 updated and 128 new items over 56 stations in 48 systems
NOTE: Import completed.
Next lets talk about data. If you're worried that the data is out-of-sync or is bad somehow, you can do an update, do a buildcache and an update, or do a complete wipe and an update. The last one will definitely work. You know how to do an update. To do a buildcache (this rebuilds your local database from the data files in your data folder:
trade buildcache -fi
A buildcache is forced by TD before any command whenever it detects that a data file has been touched later than the local database - but from memory it is not run with the "i" option which ignores errors. So you could just open any data file like the Station.csv - resave it - and the next TD command will also do a buildcache.
Lastly - to wipe the data you can just delete the TradeDangerous.db file. But the when the database is rebuilt it may be using bad data so you also replace the Station.csv, ShipVendor.csv and TradeDangerous.prices from Maddavo Market Share . Then you can do a buildcache and it will build the database with completely fresh data.
Now time to note something - what does market 'N' mean? Well, it means that in the Station.csv the market has been set to N (no market). BUT note that sometimes there might be a station that had a market and now doesn't. The prices for that station are still in the TD.prices file and still in the database. Changing the market -> N doesn't get rid of the prices. TD has a behaviour where if it detects prices for a station then it will set market -> Y. So what you may find is that a station you set market -> N will sometime later magically have switched back to market = Y.
When you generate the run that takes you to somewhere that doesn't have a market anymore - I venture that it is picking up those old dead prices. So, you can delete the prices by doing an update on the station and manually setting all the prices to zero.
I have been wary of deleting prices for stations where their market = N. This is because sometimes in the past the value has been changed to N by accident - and if I deleted the prices then well, they're gone. There are 9 stations that keep popping up market Y -> N whenever I do a station import to TD. I haven't tried trading around any of them so I haven't come across your issue. I'll have to look further into it and work out what's best to do.
After I buildcache -fi and updated using "trade import -P maddavo -O corrections,stations,shipvendors,exportcsv" I seem to be getting a whole bunch of warnings. "WARNING: import.prices:<number> ERROR Unrecognized item name: "<item>" Do I just ignore these?
I also figure out why no one or rarely anyone will run into that problem. It's as you say, TD some reason pick up old dead prices and uses them. That is if you leave out an option. This is what I typed
If I include the --age option bliss gateway or stations with no market will not appear. I guess the fix for this is to manually remove prices that don't exist for stations that constantly comes up with markets.
Sorry, I hope this doesn't bother you too much. I'm still new to ED. Thanks for replying.
After I buildcache -fi and updated using "trade import -P maddavo -O corrections,stations,shipvendors,exportcsv" I seem to be getting a whole bunch of warnings. "WARNING: import.prices:<number> ERROR Unrecognized item name: "<item>" Do I just ignore these?
uhhhhh, I'm slightly confused but thats no problem 
