EDDiscovery

Status
Thread Closed: Not open for further replies.

Finwen

F
MalcYorks said:
Regarding overwriting the VerboseLogging setting:

I have just had confirmation from Michael Brooks (Executive Producer) that "If you put the change into AppConfigLocal.xml then it shouldn't be overwritten."

He then goes on to explain how where and what is needed so have a look at post 118 and onwards in thread:

https://forums.frontier.co.uk/showthread.php?t=158956&page=13

Basically you need a file called AppConfigLocal.xml containing:

<AppConfig>
<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
>
</Network>

</AppConfig>
Click to expand...


New (yet unrealesed 2.3 version) have support for detecting AppConfigLocal.xml file.

If it doesnt exist EDDiscovery will create one with verbose logging automatically.
 

Miklos Atreides

Miklos Atreides
I had a look at it and its pretty fine as is enables route tracking where I've been already and where to go. Great Job. Thank you for all the efforts you had.

Now as always here are some suggestions for futher improvments. (Perfection is the road, not the goal).
This is no criticsm rather than suggestion for improvement.

I am not that deep in the netlog, but can you find out what objects had what type of level scan?
(Would be great for explorers what bodies they scanned but maybe there is no info in the log.).

Can you plot the route in the graph? and maybe give a deeper zooming factor?
Its already really cool but following my own plotted path would be a touch nicer.

Many thanks for this cool tool will use it regulary.

Regards.

Miklos Atreides
 

Finwen

F
Improvment suggestions and bug reports are always welcome.

AS far as i know you cant se what you have scanned in netlog.

Ploting the route is something ii have planned to do. The graph is vary basic now. I want to develop it more.
 

Miklos Atreides

Miklos Atreides
Inhumierer said:
All systems you've visited are in red, all others in white. So the red dots are your route. And you can zoom in and out with the mousewheel, rotate it with the mouse.
Click to expand...

Thanks for info but already know this.

About the red dots I had a thought of this but wasn't explained yet or I haven't found that information. Finally to draw a line between the dots can show your course while
having dots only are saying 'Here I've already been'.

Regarding the zoom from opening the map the default is ok. Zooming out is for me ok too. But zomming in to look into the details getting closer stops somewhen but it seems not being near enough to me.

I do not know if its possible to enhance but its worth to mention it as an improvement while spending your free time to program such a project.
I am not nearly talented that way. So pulling the hat and give a lot of Kudos to the programmer.

Regards,

Miklos
 

Finwen

F
Released Version 2.3.0

Together with Cmdr Majkl we have created allot of new things in this version.

* Trilateration routine to get coordinates for unknown stars.
* Eddiscovery also creates an AppConfigLocal.xml file to automatically to add verbose logging in ED.
* EDDiscovery starts faster with more work running in different threads.
* Easy way to add distance to next system.
* And a long list of other small bugfixes and small changes.
 

Sheepz

S
Hi Finwen,

Thanks for the great program and the new version, it is really useful.

How do I use the trilateration routine? I have a lot of unknown systems (marked in blue), but the button is always greyed out whatever I have tried. I have previously provided the distances to the previous and next star systems.

Cheers

Sheepz
 

Finwen

F
Right now you can just do it of you are at a system without coordinates (blue).

Select the first system and press trilatate button. Will improve it so the button are for the current system i think.
 

Bam

Bam
I love the distance to next system box, so many times I have remembered to open the map to get the distance just as I hit 4,3,2,1...
You have done a great service to us short term memory problem people :)

Had one thing with the coordinate page, my distance and calculated distance to a system were the same but it showed as incorrect.
 

Rider

R
Hello, sorry to say that, but after last update I'm unable to make EDD works... It stars well, load travel history and starts writing:
Reading travel history Get stations from EDDB.(boom)
Program EDDiscovery2 has stopped working.
I'm running it on Win7 64bit, so far with any problems... Also, sometimes it continues with "Checking for new distances from EDSC. (boom)". It doesn't matter if I run E:D in background or not. System restart won't help. Please, do you have any advices what to try?
 

daver4470

D
Rider said:
Hello, sorry to say that, but after last update I'm unable to make EDD works... It stars well, load travel history and starts writing:
Reading travel history Get stations from EDDB.(boom)
Program EDDiscovery2 has stopped working.
I'm running it on Win7 64bit, so far with any problems... Also, sometimes it continues with "Checking for new distances from EDSC. (boom)". It doesn't matter if I run E:D in background or not. System restart won't help. Please, do you have any advices what to try?
Click to expand...

I'm having the same issue, alas. I got the program to work last night (somehow), but I haven't been able to replicate that success today. Tried the usual suspects -- disabling firewall/antivirus, repaired my .NET install, reverted to prior version (although I don't think that does anything at all, as the functional bits aren't in the local file, I believe).... exact same issue.

Let me know what, if any, troubleshooting info would be useful to you. Happy to oblige. Your program is awesome, and I refuse to play Elite without it!


Also on Win7 64bit. Previous versions worked without issue -- it's something that immediately arose with the update.
 

Majkl

Majkl
@Rider, @daver4470:
Strange, not sure what could be going on. There is something you can try: look into the Event Log for applications - open Administrative Tools > Event Viewer, select Windows Logs > Applications and then find the error related to EDDiscovery (1st line in the detail should say Application: EDDiscovery.exe or something like that). There may be more of them related to the same incident.
 
Last edited:

daver4470

D
Update to my last post:

I read some of the stuff earlier about v2.3.0 being aware of an AppConfigLocal.xml file if one exists, and creating one with verbose logging if it does not. I checked, and I wasn't seeing any AppConfigLocal file in my ED directory. So I created one (as recommended). EDDiscovery opened without crashing afterwards. I'll report back if this is a consistent fix, but that may be part of the issue.
 

Zeeman

Zeeman
Just had a quick look at the new update - looks like we can triangulate systems in app now!!! AWESOME! I'll be giving this a go tonight, seeing a smy current system is 65292Ly form Sol, should be a good test.

I'm very surprised (and impressed) to see this was implemented so soon, I was expecting a few more weeks! Huge kudos to those working on this!!!

Much much respect! I'd buy you all beers if I could!

Z...
 

daver4470

D
@Majkl -- I actually hadn't thought of that.... I always forget to check the event viewer when stuff like this happens.

Anyhow, I'm seeing two errors thrown -- a .NET runtime error and an app error. They both appear to be I/O exception related, so (given that I seem to have fixed the problem by adding the local .xml settings file) I'm still thinking that the .xml file creation feature is possibly the issue here.

Here's the copied text from the event notices. Most of them are identical; there are one or two that are different. I can post those as well if necessary.

The .NET error:

Code: 
Log Name:      ApplicationSource:        .NET Runtime
Date:          6/27/2015 8:14:44 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Application: EDDiscovery2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
   at System.Net.GZipWrapperStream.Read(Byte[], Int32, Int32)
   at System.IO.Stream.InternalCopyTo(System.IO.Stream, Int32)
   at System.IO.Stream.CopyTo(System.IO.Stream)
   at EDDiscovery2.EDDB.EDDBClass.DownloadFile(System.String, System.String)
   at EDDiscovery2.EDDB.EDDBClass.GetStationsLite()
   at EDDiscovery.EDDiscoveryForm.GetEDDBUpdate()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-06-28T00:14:44.000000000Z" />
    <EventRecordID>503351</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Dave-Laptop2</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: EDDiscovery2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
   at System.Net.GZipWrapperStream.Read(Byte[], Int32, Int32)
   at System.IO.Stream.InternalCopyTo(System.IO.Stream, Int32)
   at System.IO.Stream.CopyTo(System.IO.Stream)
   at EDDiscovery2.EDDB.EDDBClass.DownloadFile(System.String, System.String)
   at EDDiscovery2.EDDB.EDDBClass.GetStationsLite()
   at EDDiscovery.EDDiscoveryForm.GetEDDBUpdate()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()
</Data>
  </EventData>
</Event>

The app error:

Code: 
Log Name:      ApplicationSource:        Application Error
Date:          6/27/2015 8:08:35 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Dave-Laptop2
Description:
Faulting application name: EDDiscovery2.exe, version: 2.3.0.0, time stamp: 0x558d45cf
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18869, time stamp: 0x556363bc
Exception code: 0xe0434352
Fault offset: 0x0000c42d
Faulting process id: 0x367c
Faulting application start time: 0x01d0b1368e09dc83
Faulting application path: C:\Users\Dave\AppData\Local\Apps\2.0\JT8MY6WN.NZG\EL2W515L.AAM\eddi..tion_681bc25e6f52ba09_0002.0003_471266085bb8fe65\EDDiscovery2.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: d12cb535-1d29-11e5-9a13-8c89a5030da8
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-06-28T00:08:35.000000000Z" />
    <EventRecordID>503334</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Dave-Laptop2</Computer>
    <Security />
  </System>
  <EventData>
    <Data>EDDiscovery2.exe</Data>
    <Data>2.3.0.0</Data>
    <Data>558d45cf</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.18869</Data>
    <Data>556363bc</Data>
    <Data>e0434352</Data>
    <Data>0000c42d</Data>
    <Data>367c</Data>
    <Data>01d0b1368e09dc83</Data>
    <Data>C:\Users\Dave\AppData\Local\Apps\2.0\JT8MY6WN.NZG\EL2W515L.AAM\eddi..tion_681bc25e6f52ba09_0002.0003_471266085bb8fe65\EDDiscovery2.exe</Data>
    <Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
    <Data>d12cb535-1d29-11e5-9a13-8c89a5030da8</Data>
  </EventData>
</Event>

Hope that's useful...
 

Inhumierer

Inhumierer
Runs fine here. Maybe EDDiscovery tries to get the EDDB data and runs into timeout, so it gets an unexpected (empty?) answer or a timeout error message and doesn't handle this. So this may only happen if EDDB is unresponsive. Ony an idea...
 

Rider

R
Thanks for event viewer hint - it's exactly the same here:

1) .NET runtime:

Application: EDDiscovery2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
at System.Net.GZipWrapperStream.Read(Byte[], Int32, Int32)
at System.IO.Stream.InternalCopyTo(System.IO.Stream, Int32)
at System.IO.Stream.CopyTo(System.IO.Stream)
at EDDiscovery2.EDDB.EDDBClass.DownloadFile(System.String, System.String)
at EDDiscovery2.EDDB.EDDBClass.GetStationsLite()
at EDDiscovery.EDDiscoveryForm.GetEDDBUpdate()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

2) Application error:

System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2015-06-28T11:10:08.000000000Z

EventRecordID 181917

Channel Application

Computer Amalthea

Security


- EventData

EDDiscovery2.exe
2.3.0.0
558d45cf
KERNELBASE.dll
6.1.7601.18869
556363bc
e0434352
0000c42d
103c
01d0b192f93c8780
C:\Users\Rastislav\AppData\Local\Apps\2.0\O089X2PW.T2B\XCO3LEE9.TW4\eddi..tion_681bc25e6f52ba09_0002.0003_471266085bb8fe65\EDDiscovery2.exe
C:\Windows\syswow64\KERNELBASE.dll
3bf63c99-1d86-11e5-b83e-000272d4f1f9
 

daver4470

D
Crash is now (repeatedly) back for me, so I guess my .xml idea wasn't the issue...

After poking around the logs for the new crashes.... Inhumierer is probably on to something. The problem seems related to the update call for the StationsLite DB from EDDB. Something is causing an unhandled exception in that routine.
 
Last edited:

Majkl

Majkl
@daver4470: Thanks.
It gives an overview of what is happening, unfortunately it doesn't explain why... Looks like something strange is going on while downloading the file. HTTP request starts ok, but then some IO error occurs while downloading it and saving it to the local file. That is strange, since it's exactly the same server and routine as with downloading tgcsystems/tgcdistances (that appears to work for you).

If you want, you can:
1. download ProcDump from here: https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
2. extract it somewhere
3. open Command Line (start > run > cmd.exe) or PowerShell
4. go to the folder where you extracted it (e.g. C:\Users\<username>\Downloads\Procdump)
5. enter the following command and press enter: .\procdump.exe -accepteula -e -ma -w EDDiscovery2.exe
6. start EDDiscovery and wait for it to crash

Now, in the Procdump folder, there should be a file named like EDDiscovery2.exe_YYMMDD_HHMMSS.dmp. Compress it and send it to me, e.g. via private message.

Thanks and sorry for your troubles.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom