EDDiscovery 18.X is now out. Modules panel upgrades and Engineering

Jack Schitt

Jack Schitt
Eahlstan said:
If you delete the SoundBlaster using the Add-On manager and reinstall it you're prompted to choose a folder again.
Click to expand...
And indeed that is what happened when I did it again. I've no idea why that dialog didn't pop up the first time. I've tried to reproduce using various methods of closing different windows in different orders and in each case the dialog appeared. Bizarre.

Thanks for the help. FWIW I've popped something in the Suggestions forum requesting Assist events be added to the Journal. Not sure much will come of it but we can only ask.
 

varonica

varonica
Systems aren't showing up in the EDSM database at the moment, not just ones I have uploaded but many explored ones just taken from the galaxy map, anyone else having an issue, some sort of error with the database? Also seem to affect EDDB. Systems I have visited, that report in EDDiscovery that they have been scanned and uploaded just show as system not found now whereas immediately after scanning they showed up fine. Most nearby systems, I am in a heavily explored area, also show up the same, some sort of data interchange error possibly. It doesn't seem to affect old system like Sol, but for instance HD 81941 that I have scanned fully and was working a couple of days ago no longer showing up, only getting system not found error.
 

varonica

varonica
Ok I have played around with different options and it appears they have either implemented stricter rules on the text entry box in EDSM or my spreadsheet is suddenly adding an extra invisible character to the system name, problem solved, phew.
 

robbyp

robbyp
Trying to get to you know what, using the 3dmap to fly around the restricted sectors..

1662044418997.png
 

Codger

Codger
Hey, I got a question about the jpg conversion naming stuff.

It appears that "BodyName" also contains "System Name". For example I get the following sort of name:

3308-09-24 17-49-50 Foerst JI-K d8-802-Foerst JI-K d8-802 B 3 c

The system is Foerst JI-K d8-802. The body is B 3 c. But the converter puts the bodyname as Foerst JI-K d8-802 B 3 c, and I can't seem to prevent it. I don't need the system name twice.

I tried the other naming options and they all do this. And there isn't one for just Bodyname anywhere, so I can't just use that.

Is there a way around this? The names are too long and have redundant data this way.
 

robbyp

robbyp
We can add just bodyname to the list of filenames.

I think the original idea is that you'd actually always want the system-body name in the file name, as if you copied them out of the folder, you'd lose context on what system it was taken in.
 

Codger

Codger
robbyp said:
We can add just bodyname to the list of filenames.

I think the original idea is that you'd actually always want the system-body name in the file name, as if you copied them out of the folder, you'd lose context on what system it was taken in.
Click to expand...

Eahlstan said:
Currently not, but I see your point.
I added bodyname options, so it will be possible to use those in the future.

View attachment 324308
Click to expand...
Awesome, that's great. Thanks much!
 

robbyp

robbyp
How Update 14 and EDD will work.

As you probably know, Frontier are splitting the galaxy: Legacy galaxy and Live galaxy.

EDD keeps a history of your endeavours. After this split occurs, you will have two parallel commanders, each with the same previous history, but one in the legacy galaxy and one in the live galaxy.

EDD needs to keep them separate. To do this, when a journal file is written for the legacy commander and EDD sees it, it will create a new commander called cmdrName (Legacy). You will still have a commander called cmdrName.

Gameplay journal entries in legacy mode will be assigned to the legacy commander, gameplay journals entries in live mode will be assigned to the normal commander.

Version 16.0 will support this.

If you continue to use the previous EDDs, all gameplay, live and legacy, will be assigned to your single commander instance.

Unfortunately, as of Saturday, Frontier have not disclosed to us at EDCD how we can identify a legacy game from a live game. Hopefully by Tuesday they will, and it will be simple, and the EDD team can produce a 16.0 client which supports this. If not, I suggest you only play in live galaxy until we get this information and can produce 16.0.

Regards

Commander Robby.
 
Last edited:

robbyp

robbyp
Obv the proof will be in the pudding if this works correctly in our new parallel universe, but i've released it so that if you do play in legacy, you'll at least have a chance:

github.com

Release EDDiscovery Release 16.0 Update 14 support, Carrier Panel, Stats, Many improvements · EDDiscovery/EDDiscovery

WARNING: Back up EDDUSER.sqlite before you run this (normally in %LOCALAPPDATA%/eddiscovery unless you've specified a new folder or using the portable version). Just in case. Console commander acc...
github.com github.com
 

robbyp

robbyp
It seems to work, the legacy commander creation while keeping your history.

This was all back of the envelope btw, very little information was disclosed by Frontier on this. You can thank all of us guessing at EDCD on how to work this.
 

Gut

Gut
+
I'm using 15.1.4.0 version , after loading i keep getting this " Error sending EDSM events Game/Build version not found " , Should i use the 16.0 update , or is something else wrong ?
 

varonica

varonica
Gut said:
+
I'm using 15.1.4.0 version , after loading i keep getting this " Error sending EDSM events Game/Build version not found " , Should i use the 16.0 update , or is something else wrong ?
Click to expand...

The 16 is running fine for me, no problems so far that's the way to go.
 

Jorki Rasalas

Jorki Rasalas
Mmm, I'm having a Senior moment....I think I've misunderstood.

Downloaded Update 14. Downloaded & installed EDD 16.0.0.0 portable & run it.
Run Launcher & entered EDO on primary account, seems ok, only two commanders (Jorki primary & Tyko secondary) in EDD selection window.
Closed EDO, logged out. Opened for secondary account. Ran Legacy Horizons, did an FSS scan, closed game. Journal file shows no "legacy" other than "Specialised Legacy Firmware". EDD commander dialog still only shows Jorki & Tyko commander names. Why no "Tyko (Legacy)"?
 

Jorki Rasalas

Jorki Rasalas
Eahlstan said:
Sure you ran the legacy version and not just Horizons 4.0?
Click to expand...
It definitely said Legacy Horizons. My second account hasn't got EDO so I dont think it has access to Horizons 4.0.

Ive closed the PC, got to take the copawlot to the vet for a bloodtest. Will try again tomorrow...
 

Eahlstan

E
Everyone has access to Horizons 4.0

If you upload your journal files from that day ( shell:SavedGames\Frontier Developments\Elite Dangerous ) we could check which version you loaded.
 
You must log in or register to reply here.
Back
Top Bottom