Fin and Anthor should publish a set of "TripTik's" for the major routes in the sphere, and the highways to the tourist traps like Barnard's Loop.
Don't gave me too much idea ;p
I'm still working on the POI visitor lists
EDDiscovery
- Thread starter Finwen
- Start date
- Status
Don't gave me too much idea ;p
I'm still working on the POI visitor lists
Figured this one out. It had to do with permissions AND the fact that you have to have made a jump after starting EDDiscovery in order for it to work.
Does this support the upcoming 64 bit version of the game (Horizons)? I noticed because the app says 32 bit.
Yes is should work fine. WE will probably need to set verbose logging on again....
- - - - - Additional Content Posted / Auto Merge - - - - -
If it is persistant then i can repair the db file for you
send %localappdata%\EDDiscovery\EDDiscovery.sqlite to robert.l.wahlstrom@gmail.com
Wait, now I'm a bit confused. Is it working properly? Granted, I'm still actually downloading horizons so that may be why it isn't working properly. It keeps saying "Elite Dangerous is Not Logging System Names!" on the top right of the app screen.
Not to mention there are two folders in the products folder: one named FORC-FDEV, etc. etc. and another named elite-dangerous-64. Both have appconfig.xml files and graphicsconfiguration.xml files. Which one should we be linking the app to? I've tried both.
Thanks for keeping the app updated!
Not to mention there are two folders in the products folder: one named FORC-FDEV, etc. etc. and another named elite-dangerous-64. Both have appconfig.xml files and graphicsconfiguration.xml files. Which one should we be linking the app to? I've tried both.
Thanks for keeping the app updated!
Released EDDiscovery 2.6.0
http://eddiscovery.astronet.se/release/EDDiscovery_2.6.0.exe
* Will find 64 bit Horizon client.
Don't forget to set verbose logging again!!!
http://eddiscovery.astronet.se/release/EDDiscovery_2.6.0.exe
* Will find 64 bit Horizon client.
Don't forget to set verbose logging again!!!
Ok, did that. Will start up horizons to see how it works. I put the path for the file as C:\Users\~\AppData\Local\Frontier_Developments\Products\elite-dangerous-64. Assume that if I am never heard of again regarding this that this solution worked for me.
The error message is still there but I'll have to start up horizons to see if it fixes itself.
The error message is still there but I'll have to start up horizons to see if it fixes itself.
HI
I've installed v2.6.0 - set the logs directory in settings - verbose logging is on in ELite. EDdiscovery has synced with EDSM and shows all my systems visited before today, but nothing for today. I've made three hyperjumps to different systems tonight but the main window doesn't show them. The output window at the bottom left of EDdiscovery is showing netlog 151215204818.01 added to local database. I'm guessing that the name refers to the time of the netlog of my last flight - i.e. 15/12/15 @ 2048 hours which would suggest that the netlogs are being created by Elite and being read by Eddiscovery. The main window is still showing my most recent system entry from the 12/12/15 when I last used the program. (last few days I was in the beta so didn't use EDdiscovery). I've restarted Elite and EDdiscovery as well as the PC but still get nothing new in the main output window.
I'm using Windows 10 x64 bit.
If you need any more info to solve this, let me know.
Thanks
I've installed v2.6.0 - set the logs directory in settings - verbose logging is on in ELite. EDdiscovery has synced with EDSM and shows all my systems visited before today, but nothing for today. I've made three hyperjumps to different systems tonight but the main window doesn't show them. The output window at the bottom left of EDdiscovery is showing netlog 151215204818.01 added to local database. I'm guessing that the name refers to the time of the netlog of my last flight - i.e. 15/12/15 @ 2048 hours which would suggest that the netlogs are being created by Elite and being read by Eddiscovery. The main window is still showing my most recent system entry from the 12/12/15 when I last used the program. (last few days I was in the beta so didn't use EDdiscovery). I've restarted Elite and EDdiscovery as well as the PC but still get nothing new in the main output window.
I'm using Windows 10 x64 bit.
If you need any more info to solve this, let me know.
Thanks
Hard to say whats wrong but send me the latest netlog files and you appconfig.xml to me robert.l.wahlstrom@gmail.com and i can check.
FYI:
I am getting the same issue. Windows 10 running the Horizons 64 client.
I've updated to EDDiscovert v2.6.0.0 and can see all my old visited systems, but none of the new ones.
I did add VerboseLogging="1" to the Appconfig.xml.
I am getting the same issue. Windows 10 running the Horizons 64 client.
I've updated to EDDiscovert v2.6.0.0 and can see all my old visited systems, but none of the new ones.
I did add VerboseLogging="1" to the Appconfig.xml.
All grand for me on Win7. I knew it was too soon to upgrade
Serious note though...
The 64 bit client is a new install and doesn't over-write the 32 bit one. Are you sure you've set VerboseLogging on the right config and checked EDD is reading the right log directory (see the settings tab)
C:\Users\%user%\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs
and not
C:\Users\%user%\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1003\Logs
Serious note though...
The 64 bit client is a new install and doesn't over-write the 32 bit one. Are you sure you've set VerboseLogging on the right config and checked EDD is reading the right log directory (see the settings tab)
C:\Users\%user%\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs
and not
C:\Users\%user%\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1003\Logs
Yeah, I've edited the file xml file in elite-dangerous-64.
I also tried pointing EDDiscovery straight to the folder elite-dangerous-64\Logs, but it still only shows the old visited systems.
FYI:
this is the part in the xml:
<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
>
</Network>
I also tried pointing EDDiscovery straight to the folder elite-dangerous-64\Logs, but it still only shows the old visited systems.
FYI:
this is the part in the xml:
<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
>
</Network>
Shame on my programmer head.
It seems I was so excited about landing on my first moon that I forgot to restart the game. :/
Long story short, it works fine and I should go to bed.
Now I just have to figure out how to get rid of that pesky "Elite Dangerous 2.0" that's in the bottom left corner now and why it won't take 4K (native game res) resolution screenshots anymore (it spits them out in 1440p now)
But that's for another day and another thread.
Cheers.
It seems I was so excited about landing on my first moon that I forgot to restart the game. :/
Long story short, it works fine and I should go to bed.
Now I just have to figure out how to get rid of that pesky "Elite Dangerous 2.0" that's in the bottom left corner now and why it won't take 4K (native game res) resolution screenshots anymore (it spits them out in 1440p now)
But that's for another day and another thread.
Cheers.
- Status