Im starting to feel like a bit of an idiot :/
Can I run the command anywhere? I get this as a response.
edit: I do have python installed.
I can run tradedangerous from a cli
Edit2: I found a way around my problem
Last edited:
Community Event / Creation TradeDangerous GUI front end
- Thread starter WombatFromHell
- Start date
Im starting to feel like a bit of an idiot :/
Can I run the command anywhere? I get this as a response.
edit: I do have python installed.
I can run tradedangerous from a cli
Edit2: I found a way around my problem
This problem happens if you forget to check the box that includes python in your system path during the installer.
It's one of the reasons I'm working with the Trade Dangerous Installer dev to get TDHelper included with his installer.
(Edit: I just added some more Q/A's to the FAQ for common questions like the above. Hopefully it'll help new users having trouble.)
It's one of the reasons I'm working with the Trade Dangerous Installer dev to get TDHelper included with his installer.
(Edit: I just added some more Q/A's to the FAQ for common questions like the above. Hopefully it'll help new users having trouble.)
Last edited:
Version 1.0.7.1 is rolling out now with lots of performance enhancements and bug fixes.
As usual, see the changelog for details.
As usual, see the changelog for details.
Thanks for all your work on this, just trying it out now Pilot log seems a lot faster
But it seems to be refreshing constantly and jumping back to the top Also hitting [C] clears it completely then re populates
made a quick video and posted on YT to show (hope this is just one of those bugs that only seems to affect my pc)
TDHelper v1.0.7.1 (Pilot log Refresh)
Hmm.. I'll investigate.
(Edit: Have you tried deleting your TDHelper.db, and letting the new version refresh it from your current logs?)
(Edit2: Nevermind, I think I found what's causing the problem.)
Last edited:
Deleting the TDHelper.db has fixed it. no constant refreshing.
Again great work on this couldn't imagine using TradeDangerous without it now
[Edit] Spoke to soon, on leaving the system the refreshing the pilot log is back again
Last edited:
Deleting the TDHelper.db has fixed it. no constant refreshing.
Again great work on this couldn't imagine using TradeDangerous without it now
Thanks, it's really a community effort. I couldn't do it without you guys being patient with me, and suggesting new features to make TDHelper and Trade Dangerous even better.
There's definitely a few bugs left in how the Pilot's Log gets updated, but it won't take a rewrite to fix them this time so it shouldn't take long. I'll try to get a fix out by tomorrow. I'm also trying to track down a bug in the circular buffer that causes it to spaz out sometimes on long text dumps like an import with "usefull".
Version 1.0.7.2 is rolling out with some more bug fixes for the Pilot's Log, Output log box, and recent systems dropdown. Hopefully, this should make the Pilot's Log and Recent Systems features behave properly now.
Let me know if you find any other weird behavior.
Let me know if you find any other weird behavior.
I'll be testing v1.0.7.3 thoroughly tonight before I release it sometime tomorrow if all goes well, it should resolve most of the issues with the Pilot's Log and recent systems drop down (for real this time). Hopefully, no more constant updating, cursor bug, and duplicate systems.
Thanks again for being patient with me.
Thanks again for being patient with me.
It took me a bit longer than I expected, but I'm finally rolling out v1.0.7.3 now.
There are a few minor issues with removed rows at the top of the Pilot's Log being regenerated after an update tick. I'll try to get it fixed for the next version. On the upside, there are tons of performance improvements in this version.
Have fun, and let me know if there are any new issues that pop up as a result of the changes. Cheers.
There are a few minor issues with removed rows at the top of the Pilot's Log being regenerated after an update tick. I'll try to get it fixed for the next version. On the upside, there are tons of performance improvements in this version.
Have fun, and let me know if there are any new issues that pop up as a result of the changes. Cheers.
Last edited:
Due to the fact that every upgrade that FD push out overwrites the AppConfig.xml file, I have taken to start using AppConfigLocal.xml to save my custom settings. FD are not supposed to overwrite this file (though some are reporting it does get deleted on updates, I have marked mine read only).
I would like to suggest you take the AppConfigLocal.xml file into account when checking Verbose Settings.
Thanks for the Great Software
I would like to suggest you take the AppConfigLocal.xml file into account when checking Verbose Settings.
Thanks for the Great Software
Due to the fact that every upgrade that FD push out overwrites the AppConfig.xml file, I have taken to start using AppConfigLocal.xml to save my custom settings. FD are not supposed to overwrite this file (though some are reporting it does get deleted on updates, I have marked mine read only).
I would like to suggest you take the AppConfigLocal.xml file into account when checking Verbose Settings.
Thanks for the Great Software
I've actually got it on my to do list. I'll work it into the next version due out in a couple of days. Thanks for the suggestion.
It's currently hardcoded to export to EDDN every time you do an EDAPI import. Maddavo picks up data from EDDN every few minutes or thereabouts. The only situations where you would need to think about exporting explicitly would be from an application like EliteOCR if you choose not to send it to EDDN, or if you're adding/changing station specific information, IIRC.
I thought it was but I wanted to make sure that the ship data was there. Now if we could only query modules
(though some are reporting it does get deleted on updates, I have marked mine read only).
I would like to suggest you take the AppConfigLocal.xml file into account when checking Verbose Settings.
Thanks for the Great Software
I can confirm that even with read only it gets removed (at least on my system) others say it survived so not sure why some users can while others cant use these local files.
wouldn't be the first time my pc acts differently to most!
@
Curious did your AppConfigLocal.xml survive todays update 07/07/2015?
Mine didn't and I also noticed that my Appconfig.backup file was also removed!
MY folder "FORC-FDEV-D-1001" - Elite: Dangerous - Premium Beta,
I'm wondering if its version of the game you purchased that has an affect on this local file as other users are claiming it is not removed
Due to the fact that every upgrade that FD push out overwrites the AppConfig.xml file, I have taken to start using AppConfigLocal.xml to save my custom settings. FD are not supposed to overwrite this file (though some are reporting it does get deleted on updates, I have marked mine read only).
I would like to suggest you take the AppConfigLocal.xml file into account when checking Verbose Settings.
Thanks for the Great Software
Curious did your AppConfigLocal.xml survive todays update 07/07/2015?
Mine didn't and I also noticed that my Appconfig.backup file was also removed!
MY folder "FORC-FDEV-D-1001" - Elite: Dangerous - Premium Beta,
I'm wondering if its version of the game you purchased that has an affect on this local file as other users are claiming it is not removed
No, mine didn't survive either and the AppConfigLocal.xml that was in the folder has also gone!
No it did not survive. I even marked it read-only, system.
My AppConfigLocal.xml wasn't touched at all, but the AppConfig.xml was overwritten as it should be after an update. I'm using the Steam version of the launcher, and it seems to work fine.
What you're seeing sounds like very strange behavior. By any chance are you using the Frontier in-house launcher to update? It sounds like a bug in their launcher, have you tried reinstalling your launcher if you haven't done so for awhile?