Oolite Bulletins

Looking at the code I found this class:
https://github.com/OoliteProject/oolite ... GraphViz.m

It looks like Oolite can generate graph data. But when and how would it get visible?

The graph data is for the graphviz open source visualization application. This feature was introduced long ago for assisting with visualizing AI states, planet description generation rules (back when this was all procedural, not useful now that we have everything fully laid out in planetinfo.plist) and OXP verifier related stuff. The data is generated in the graphviz input language format, .dot.

The AI graphs are applicable only for the old style .plist AIs and don't generate anything useful for the JS ones. In any case, to generate the .dot files, just add to your .GNUstepDefaults these keys: then launch the game and go about your business normally. Any plist AIs activated during that session will be written into Logs/AI Dumps/*.dot and the planet descriptions procedural rules will be written in Logs/SystemDescription.dot.

What do they look like once processed in graphviz? Here are examples:
route1traderAI.plist:


SystemDescription:

Thank you for that explanation. Yes, this could give in-depth information about the game state.

another_commander wrote: ↑Tue Sep 12, 2023 10:53 am

The graph data is for the graphviz open source visualization application. This feature was introduced long ago for assisting with visualizing AI states, planet description generation rules (back when this was all procedural, not useful now that we have everything fully laid out in planetinfo.plist) and OXP verifier related stuff. The data is generated in the graphviz input language format, .dot.

I've linked in all this to the wiki together with the screenshots (my additions for 12 September 2023)

("AI checking section") -> == Understanding what is happening ==



Is there also a screenshot of the OXP verifier process anywhere? Then I can link that in too!

And also a screen shot of a normal OXP Verifier read out? (I never got it to work)

another_commander wrote: ↑Tue Sep 12, 2023 10:53 am

The graph data is for the graphviz open source visualization application. This feature was introduced long ago for assisting with visualizing AI states, planet description generation rules (back when this was all procedural, not useful now that we have everything fully laid out in planetinfo.plist) and OXP verifier related stuff. The data is generated in the graphviz input language format, .dot

I thought planetinfo.plist was an override method. Are you saying that internally there is a giant planetinfo.plist and no procedural generation is done anymore? Therefore I couldn't do the old trick of changing the galaxy seed in the save file?

Phantor Gorth

PhantorGorth wrote: ↑Wed Sep 13, 2023 6:28 am

I thought planetinfo.plist was an override method. Are you saying that internally there is a giant planetinfo.plist and no procedural generation is done anymore? Therefore I couldn't do the old trick of changing the galaxy seed in the save file?

Yes. The current planetinfo.plist has a size of 2,737 KB and contains the full data for each of the 2048 planets. I think the only procedural stuff remaining are the core game planet textures.

PhantorGorth wrote: ↑Wed Sep 13, 2023 6:28 am

I thought planetinfo.plist was an override method. Are you saying that internally there is a giant planetinfo.plist and no procedural generation is done anymore? Therefore I couldn't do the old trick of changing the galaxy seed in the save file?

I have only found 2 current working examples of changed galaxies (both cim's) - SotL Exploration & SotL AltMap. I understand that he used his Galaxy Generator to generate the descriptions.

I'm not sure whether the scenario.plist and the "loader" oxp are a necessary part of the Galaxy changing process. But it does seem that one now needs an oxp to change the galaxy.

The planetinfo.plists are huge (16Mb for AltMap, 3Mb for Exploration - no people? just one galaxy?) - and with lots of extra data