In-Development StatusDisplay - status.json / journal display and surface navigation assistant.

Robert Maynard

Volunteer Moderator
Hi,

The ship's fuel capacity is published in the session journal file in the "LoadGame" event at the start of each session, e.g.
Code:
"FuelCapacity":16.000000
as well as in the "Loadout" event when changing ship, e.g.
Code:
"FuelCapacity":{ "Main":32.000000, "Reserve":0.630000 }
 
Last edited:

Robert Maynard

Volunteer Moderator
Beta 0.1.0.1 released. Download link: https://cdn.discordapp.com/attachme...4/StatusDisplay_Beta_0.1.0.1_20240120-2003.7z

Changelog:

1) Added "transparent" panel to facilitate using multi-panels to create pop-up grids, e.g. to indicate when the vehicle is overheating.

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add defined buttons to display information read from the Journal.
3) Improve defined button display based on Status.json information.
4) Improve command set.
 

Robert Maynard

Volunteer Moderator
Beta 0.1.0.2 released. Download link: https://cdn.discordapp.com/attachme...6b2039b3e03359d09e63c60ddeb771d2212ec41df31c&

Changelog:
1) Rework of "No Background" toggle for grids and panels - now actually removes the background.
2) Addition of "No Lines" toggle for grids and panels, to remove lines surrounding buttons and grid elements.

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add defined buttons to display information read from the Journal.
3) Improve defined button display based on Status.json information.
4) Improve command set.
 
Last edited:

Robert Maynard

Volunteer Moderator
Beta 0.1.0.3 re-released. Download link: https://cdn.discordapp.com/attachme...ea2372127138f763c5e446bbf1046ace73ba906f645e&
Changelog:
1) Bugfix: user defined corner buttons now merge as expected.
2) Fix for crash when last line of StatusDisplay settings files does not have a carriage return at the end;
3) User defined button features expanded; can now react to a game flag with changed background intensity. Backround can flash at a specified rate when button reacts to game flag if desired.

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add defined buttons to display information read from the Journal.
3) Improve defined button display based on Status.json information.
4) Improve command set.
 

Robert Maynard

Volunteer Moderator
Beta 0.1.0.4 released. Download link: https://cdn.discordapp.com/attachme...eca1cc5ef22e24083dabce8895899aa52964ae9b9461&

1) Fixed regression in grid background intensity when borders are used;
2) Number of user defined buttons increased from 128 to 256;
3) Internal button handling simplified. Now both pre-defined and user-defined buttons share a single array, simplifying the code.
4) User defined button functionality improved; one of the three lines of button text can be changed if a specified game flag is active.
5) Processor clock speed information removed as there has been a regression in Windows functionality (it now always reports the same clock speed).Changelog:

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add defined buttons to display information read from the Journal.
3) Improve defined button display based on Status.json information.
4) Improve command set.
 
I was wondering, why the limit to the amount of rows in the elements? Would it not be possible to do a 12x12 grid?
1713131582717.png

I would really like to fill up my 1080 by 1920 monitor without stretching the elements.
 

Robert Maynard

Volunteer Moderator
Multiple grids (there can be up to 8) can be placed next to each other to provide a total grid size exceeding 12 x 12 elements (but panels won't merge across grids).
 

Robert Maynard

Volunteer Moderator
Beta 0.1.0.5 released. Download link: https://cdn.discordapp.com/attachme...559e8988c7d7f3fb0b04ee888d9082970709b3ba5b9a&

1) Added SCO FSD modules;
2) Fixed range estimate (with specified fuel) and fuel estimate (for specified range) calculations, thanks to members of the EDCD;
3) Added "Mass" panel for ship, i.e. unladen mass, cargo mass, fuel mass and total mass.

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add pre-defined panels and buttons to display information read from the Journal and Status.json.
3) Improve command set.
 
Beta 0.1.0.5 released. Download link: https://cdn.discordapp.com/attachme...559e8988c7d7f3fb0b04ee888d9082970709b3ba5b9a&

1) Added SCO FSD modules;
2) Fixed range estimate (with specified fuel) and fuel estimate (for specified range) calculations, thanks to members of the EDCD;
3) Added "Mass" panel for ship, i.e. unladen mass, cargo mass, fuel mass and total mass.

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add pre-defined panels and buttons to display information read from the Journal and Status.json.
3) Improve command set.
Link doesn't work.
 

Robert Maynard

Volunteer Moderator
Links to images and files on Discord have been a bit dysfunctional lately, e.g. they work when posted then don't some time later. The easiest way to get the file is to join the Discord and download the latest version (or even previous versions) from the #release channel.
 
I know there is a couple of CPU grid items, is it possible to get more computer component information? Are the grid items hard coded or is it some kind of scripting/programming that can be modified/added to?
 

Robert Maynard

Volunteer Moderator
Not sure that names of hardware vendor / model are easily extracted from Windows.

Panels are indeed hard coded, although as there is already the ability for the user to define buttons, it's not outwith the realms of possibility that user defined panels could be a thing at some point.

What did you have in mind?
 

Robert Maynard

Volunteer Moderator
Beta 0.1.0.6 [released 30th August 2024] Downloadable from Discord: https://discord.gg/zESmTrej9F

1) Complete rework of ship and module data storage and handling to use Coriolis-Data files instead of hard coded definitions (permission very kindly granted by the EDCD);
2) Python MkII and Type-8 Transporter added;
3) Modules panel reworked accordingly;
4) "Est. Range" panel added; shows estimated range based on sequential maximum fuel jumps plus one "what's left in the tank" jump. No account it taken of fuel scooping or reservoir replenishment.
5) Min/Current/Max range panel added; should show same ranges as in Outfitting.


To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add pre-defined panels and buttons to display information read from the Journal and Status.json.
3) Improve command set.
 
Last edited:
Not sure that names of hardware vendor / model are easily extracted from Windows.

Panels are indeed hard coded, although as there is already the ability for the user to define buttons, it's not outwith the realms of possibility that user defined panels could be a thing at some point.

What did you have in mind?
Thought it would be kind a cool to see a graph of my CPU, GPU, RAM usage and all that in a panel. I have a "hiccup" happening on my computer while in game and I have been trying to determine what it is. Thought it would be neat to see those while playing in Status Display to see if I can narrow down what to chase. But overall it would still be kinda cool to have some indicators just to add to the immersion, even if they aren't game related.

Hey, in thinking about it, would it be possible for Status Display to capture game control input? I use dual Virpil Omnithrottles and finding center is harder than it should be. It would be nice if I could have a panel showing the controllers axis inputs. Or even buttons! :D
 

Robert Maynard

Volunteer Moderator
I'll certainly have a look at CPU, GPU & RAM utilisation.

Regarding capturing device inputs, I don't want the app to be anything but a display tool for the game (blurring the edges a bit by considering the PC upon which the game is running) - capturing device inputs goes beyond that, sorry.
 
I'll certainly have a look at CPU, GPU & RAM utilisation.

Regarding capturing device inputs, I don't want the app to be anything but a display tool for the game (blurring the edges a bit by considering the PC upon which the game is running) - capturing device inputs goes beyond that, sorry.
Thanks for the response and I totally get it. :D
 

Robert Maynard

Volunteer Moderator
Beta 0.1.0.7 [released 12th January 2025]
1) Mandalay and Cobra Mk V added;
2) Panels which display positional co-ordinates should now display latitude then longitude;
3) "Remaining" panel for NavRoute updated to add estimated fuel to destination;
4) Locations for gathering G4 raw materials added to Navigation.json.

To do list:

1) Improve parsing coverage of possible events listed in the Journal documentation.
2) Add pre-defined panels and buttons to display information read from the Journal and Status.json.
3) Improve command set.
 
Back
Top Bottom