Discussion 2.1 Patch Notes: "Add system X, Y, Z co-ordinates to network log"

This should prove a very useful addition, I infer from this that the positional data for Star Systems can now be scrapped from your AppConfig.xml file so we shouldn't need to enter new star system coordinates manually into EDDB :D
 
This should prove a very useful addition, I infer from this that the positional data for Star Systems can now be scrapped from your AppConfig.xml file so we shouldn't need to enter new star system coordinates manually into EDDB :D

Not quite. You'll still need to upload part or all of your network log file for the likes of EDDB to parse the system co-ordinates out, with the admins coming up with code to parse and store the relevant data (and it means that you'll have to visit the system - not always necessary with trilateration).

What two competing systems?

Fair point. If the maths is right then results should be the same.
 
Not quite. You'll still need to upload part or all of your network log file for the likes of EDDB to parse the system co-ordinates out, with the admins coming up with code to parse and store the relevant data (and it means that you'll have to visit the system - not always necessary with trilateration).

I should be able to code EDDI to send the data straight to EDSM.

Fair point. If the maths is right then results should be the same.

And it turns out that we're lucky in that FD picked Sol as their origin as well so it looks workable. The only potential issue is that the co-ordinates are logged to 3 decimal places, which might lead to inaccuracies. We'd need AnthorNet to weigh in on this though.
 
Only want to show you all the new format of the "System" line from the netlog, if not already known:

Code:
{15:04:12} System:"Sol" StarPos:(0.000,0.000,0.000)ly Body:34 RelPos:(-0.537345,2.69377,-1.20617)km NormalFlight
 
Last edited:
Only want to show you all the new format of the "System" line from the netlog, if not already known:

Code:
{15:04:12} System:"Sol" StarPos:(0.000,0.000,0.000)ly Body:34 RelPos:(-0.537345,2.69377,-1.20617)km NormalFlight

Interestingly it sometimes writes out a short-form version, possibly if you enter supercruise or if you jump systems (haven't worked out when). So if anyone is coding you need to take account of both forms.

The short form looks something like:

Code:
{15:04:12} System:"Sol" StarPos:(0.000,0.000,0.000)ly Supercruise
 
Last edited:
Interestingly it sometimes writes out a short-form version, possibly if you enter supercruise or if you jump systems (haven't worked out when). So if anyone is coding you need to take account of both forms.

The short form looks something like:

Code:
{15:04:12} System:"Sol" StarPos:(0.000,0.000,0.000)ly Supercruise
Oh my...it's now distinguishing between NormalFlight and Supercruise. And I'm seeing data about undocked vs. docked vs. landed.

It may be possible to build a legitimate race tracking app. :)
 
Oh my...it's now distinguishing between NormalFlight and Supercruise.
It's done that for a while. Not really anything useful that tools can do with the info 'though, which is why EDMC and other tools don't expose it.

And I'm seeing data about undocked vs. docked vs. landed.
Please paste examples of these for those of us not on beta. The "docked" log entry will be really useful for tools like EDMC, TCE etc.
 
Last edited:
Please paste examples of these for those of us not on beta. The "docked" log entry will be really useful for tools like EDMC, TCE etc.

Here are examples:
Code:
{12:02:45} Commander Put Docked
{12:05:38} Commander Put Undocked
{12:09:05} GetSafeUniversalAddress Station Count 1 moved 0 Undocked Not Landed
{12:35:20} GetSafeUniversalAddress Station Count 1 moved 0 Undocked Landed

TCE Mk.II V1.2.4.2 now supports "Docked" and "Landed" status.
 
Last edited:
Here are examples:
Code:
{12:02:45} Commander Put Docked
{12:05:38} Commander Put Undocked
{12:09:05} GetSafeUniversalAddress Station Count 1 moved 0 Undocked Not Landed
{12:35:20} GetSafeUniversalAddress Station Count 1 moved 0 Undocked Landed

TCE Mk.II V1.2.4.2 now supports "Docked" and "Landed" status.

Curious, I haven't seen these entries. Do you have verbose logging turned on?
 
I also think I've seen the pad number coming from some logs I receive.

I've been playing around with the data in the new logs and I'm not yet sure that it's useful. The 'Commander (Get|Put) (docked|undocked)' message might show up at times when it shouldn't, and not show up at times when it should. I'll see if I can work out what's going on.

The log does show pad number but does so for all ships in the instance, PC or NPC, so it's hard to pick out the right entry to use. There is a ship ID but it appears to change on a per-instance basis (possibly a pointer) so can't be used as a reference point either.
 
Yeah, after playing with it more, I can confirm that a log is not added directly as a result of docking / landing state change, it's simply being shown in other messages.
 
Yeah, after playing with it more, I can confirm that a log is not added directly as a result of docking / landing state change, it's simply being shown in other messages.

Yes, there is a delay more or less.
But why FDev adding new messages into the log for the state. It could be so easy to change only the current "System" line into something like:

Code:
System:"Sol" StarPos:(0.000,0.000,0.000)ly Supercruise
System:"Sol" StarPos:(0.000,0.000,0.000)ly NormalFlight
System:"Sol" StarPos:(0.000,0.000,0.000)ly Docked
System:"Sol" StarPos:(0.000,0.000,0.000)ly Landed
 
Back
Top Bottom