So my main question at the moment is: Is there any work being done to have a common way of doing the relaying of the journal events to companion apps? I'm quite happy to open source mine if that's what you lot want. Any common system would have to be open sourced …
That would be great!
I am working on this problem myself on the opposite end of the spectrum: macOS utility app ingesting journal files and sending out events via socket connection to iOS app. I'm building the journal update portion fast and brittle for now just so I can test my app. Obviously a cross-platform utility app solution for journal propagation is needed if my iOS tool makes it to the light of day.
I would be willing to test and contribute to this project as much as I could, although I'm quite the Java novice.
That would be great!
I am working on this problem myself on the opposite end of the spectrum: macOS utility app ingesting journal files and sending out events via socket connection to iOS app. I'm building the journal update portion fast and brittle for now just so I can test my app. Obviously a cross-platform utility app solution for journal propagation is needed if my iOS tool makes it to the light of day.
I would be willing to test and contribute to this project as much as I could, although I'm quite the Java novice.
My java app should already do this. Well it would do if I knew what the mac configurations are. Would you mind doing a little testing for me? I'm happy to share.
Before I can share with you I would need to know where the Journal files are write on the Mac.
Ta
Yeah you and me both! :S
I can't test at the moment as I actually don't have the latest ED beta at my disposal. I don't think it's available for us common Steam users.
Can I ask...
Maybe this has been answered but I can't see it in the thread or the manual.
How does this log behave if a user has multiple accounts?
It would not be good for a consuming app to pollute one CMDRs data into another, this is something that would be very difficult to undo.
To work around it a player might be faced with copying, renaming files between each login.
Does the logging mechanism support multiple CMDRs? I don't think this is an uncommon scenario.
Cmdr name is in the loading lines, so you already can track which account is used now. (Note: in order to change account you need to restart the game, so, new log, new cmdr)Can I ask...
Maybe this has been answered but I can't see it in the thread or the manual.
How does this log behave if a user has multiple accounts?
It would not be good for a consuming app to pollute one CMDRs data into another, this is something that would be very difficult to undo.
To work around it a player might be faced with copying, renaming files between each login.
Does the logging mechanism support multiple CMDRs? I don't think this is an uncommon scenario.
No the API don't give theses informations, you have to scan them one by one.When I first enter a system, I can click on each body in the system and get basic information even about unexplored objects that haven't had a detailed scan done of them.
For example, I can get the number of Earth Masses, its Radius, Orbital Period, Semi-Major Axis, the level of reserves in any rings it has, the names of those rings, and the semi-major axis, inner and outer radii of the rings.
For asteroid belts, I can get the ring type, moon masses, orbital period, semi major axis, orbital eccentricity and inclination, and its argument of periapsis.
These are all provided without a detailed scan of the object.
Are those details provided by this API outside of a detailed scan report just like they're provided without a detailed scan report in game?
(And is there any valid reason why non-belt objects don't also provide orbital eccentricity, inclination, and argument of periapsis?)
{ "AbsoluteMagnitude": 15.62851,
[B] "Age_MY": 5474,[/B]
"BodyName": "Akandi C",
"DistanceFromArrivalLS": 81478.195313,
"Eccentricity": 0.110937,
"OrbitalInclination": 13.053893,
"OrbitalPeriod": 103157.84375,
"Periapsis": 194.812363,
"Radius": 128304968.0,
"RotationPeriod": 80407.734375,
"SemiMajorAxis": 1758718464.0,
"StarType": "T",
"StellarMass": 0.074219,
"SurfaceTemperature": 1120.0,
"event": "Scan",
"timestamp": "2016-10-13T21:08:50Z"
}
{ "AbsoluteMagnitude": 10.917847,
[B]"Age_MY": 5474,[/B]
"BodyName": "Akandi B",
"DistanceFromArrivalLS": 81486.09375,
"Eccentricity": 0.110937,
"OrbitalInclination": 13.053893,
"OrbitalPeriod": 103157.84375,
"Periapsis": 14.812368,
"Radius": 287746976.0,
"RotationPeriod": 144619.671875,
"SemiMajorAxis": 514086784.0,
"StarType": "M",
"StellarMass": 0.253906,
"SurfaceTemperature": 2212.0,
"event": "Scan",
"timestamp": "2016-10-13T21:17:50Z"
}
{ "AbsoluteMagnitude": 9.188385,
[B]"Age_MY": 5474,[/B]
"BodyName": "Akandi A",
"DistanceFromArrivalLS": 0.0,
"Eccentricity": 0.069828,
"OrbitalInclination": 10.100887,
"OrbitalPeriod": 72381833216.0,
"Periapsis": 216.665939,
"Radius": 344099296.0,
"Rings": [
...
],
"RotationPeriod": 242933.828125,
"SemiMajorAxis": 10712330010624.0,
"StarType": "M",
"StellarMass": 0.382813,
"SurfaceTemperature": 3012.0,
"event": "Scan",
"timestamp": "2016-10-13T21:26:48Z"
}
Bug report: Age_MY gives different value than the ingame value for stars in a system.
In Akandi the ingame age is 5572 MY for all stars, but the journal says it's 5474. My first thought - must be a multiplier (1.076553). But seems not like it - other samples from different systems show different multiplier. So what's going on with this value?
Our top ludoastrophysicists have been granted funding for a research project to look into this in-silico cosmological anomaly.