Can you even plot a route there on the galaxy map with that range?
In-Development TradeDangerous: power-user trade optimizer
- Thread starter kfsone
- Start date
Can you even plot a route there on the galaxy map with that range?
The development version of TD Helper now has a setting for the commander's re-buy percentage which is 5%, 3.75% or 2.5% depending on the commander and calculates the insurance of the current ship from this. It also updates the capacity to the installed cargo capacity, again of the current ship.
It's not ready for prime time as yet since there also needs to be a way to stop the insurance and capacity updates which means adding more controls to the main form.
But it's getting there.
It is, however, frustrating that certain information is not included in the profile. The re-buy percentage, for example and the min and max jump range for each ship. Both of those would be very useful.
Oh well.
There is a rebuy field in the Loadout event of the journal:
Code:
{
"timestamp": "2018-06-29T17:33:17Z",
"event": "Loadout",
"Ship": "Asp",
"ShipID": 12,
"HullValue": 6135160,
"ModulesValue": 23259866,
"Rebuy": 1102318,
...That is good to know, thanks.
I dare say that I could use that just to get the percentage as it doesn't change even if it is in the Journal and not the Companion API profile. Are the max & min jump ranges in the Journal I wonder...
[Edit] Apparently not.
Last edited:
Maybe ask the coriolis people how they figure it out?
They work it out from the load-out, engineering and a massive formula that details it all. The code is available to see on GitHub but converting it to TD Helper just for the min and max figures is probably a bit of a waste of time.
Little update: I'm pretty certain at this point that a default of 12.5 for the lsp is what we want to go with- it usually though not always gets rid of any really far stations, and on the few occasions it has any, it's usually just one.
With that in mind, Mark, do you think you can make TDHelper's penalty field allow values that involve 1/10ths? It currently only allows whole numbers.
With that in mind, Mark, do you think you can make TDHelper's penalty field allow values that involve 1/10ths? It currently only allows whole numbers.
Yeah, it's not that important. Those numbers don't change very often- only when changing modules on a ship- which is rare- or changing ships- which is what the multiple profiles are for. I kind of wish it would stop creating the "Default" profile I never use and open the last-used profile instead, since I name my profiles after the ship of mine it's configured for.
I do the same thing but at the moment the code is not set up to work any other way. The original developer took a bit of a short cut and stored all the data in the ship profile, the paths, the settings, everything.
I plan to change that so that the main settings, the ones you set from the settings form, will be in a separate config file and the rest in the ship profile. Then I'll be able to save the last used profile and restore it on load.
This will be the next thing after the EDCE integration is completed and available for use.
Last edited:
I have just releasee v2.0.0.1-Beta of TD Helper 2 which adds a very small change in that the lsp field is now set to include one decimal place so that values like 12.5 can be entered. The release can be downloaded from https://github.com/MarkAusten/TDHelper/releases, simply copy the files in the zip file over the existing TD Helper 2.0.0.0-Beta files.
The next release, v2.0.1.0 will be the EDCE integration release.
Stay tuned.
Done.
The next release, v2.0.1.0 will be the EDCE integration release.
Stay tuned.
Done.
Off-topic shameless self promotion - I am really proud of these : https://forums.frontier.co.uk/showthread.php/424051-Screenie(s)-v2?p=6828712&viewfull=1#post6828712
I have just released TDHelper v2.0.1.1 which can be found here: https://github.com/MarkAusten/TDHelper/releases
This adds EDCE integration and thus you will need to download and set up EDCE for which I have given brief details in the setup instructions.
Integrating with EDCE allows TD Helper to be updated from the commander profile downloaded from the ED Companion API and this information is used to update the credit balance and the ship's current cargo load out. You can also set the re-buy percentage in the settings if your commander has one that is different from the standard 5%. Alpha backers have 2.5% and Beta backers have 3.75%.
This percentage is used to calculate the insurance value in TD from the current ship's hull and module values.
Next up, changing the way in which the setting are saved so that common settings have their own configuration file thus allowing TD Helper to open up the last used profile instead of Default every time.
Thanks.
This adds EDCE integration and thus you will need to download and set up EDCE for which I have given brief details in the setup instructions.
Integrating with EDCE allows TD Helper to be updated from the commander profile downloaded from the ED Companion API and this information is used to update the credit balance and the ship's current cargo load out. You can also set the re-buy percentage in the settings if your commander has one that is different from the standard 5%. Alpha backers have 2.5% and Beta backers have 3.75%.
This percentage is used to calculate the insurance value in TD from the current ship's hull and module values.
Next up, changing the way in which the setting are saved so that common settings have their own configuration file thus allowing TD Helper to open up the last used profile instead of Default every time.
Thanks.
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 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.
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.
Thanks for the heads up on that one, I've amended the error.
Let me know if you have any other problems.
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.
Good point.
I think I'll add a checkbox next to the credit balance, insurance and cargo capacity number entry boxes which, if ticked, will prevent the update of these values. That way you can determine just what gets updated. I would see it working with all boxes unticked, retrieve the Cmdr profile which updates the values, then check the boxes of the ones you want to remain unchanged and add the appropriate amount as required.
Mark, one other thing I’ve noticed and it happens every time is that clicking the Cmdr Profile button runs the edce command and in common with other commands, changes the Run box to Cancel while it is running. When the command finishes (in 1.7 seconds in my case) the Cancel does not change back to Run. Clicking the Cancel still works as a run though, so it’s just a cosmetic glitch. Other than that, so far it’s all good!
Thanks for the update, I'll add that issue to my list of things to be fixed.