Oolite Bulletins

• Deep Space Dredger: c works some of the time - the rest of the time it takes a veritable eternity as it sends your Cobra whizzing off to the far end of the galaxy; C never works

• SLAPU/ZGF: c works; but C does not

• Luxury Liners: yet to try c; but C works just fine

dybal wrote: ↑Thu Oct 15, 2020 1:06 am

I always assumed the Blue Danube was a reference to 2001 A Space Oddisey

Cholmondely wrote: ↑Wed Oct 14, 2020 11:36 pm

Deep Space Dredger: c works some of the time - the rest of the time it takes a veritable eternity as it sends your Cobra whizzing off to the far end of the galaxy; C never works...

 "allows_fast_docking" = yes; 

Nite Owl wrote: ↑Thu Oct 15, 2020 5:09 am

Cholmondely wrote: ↑Wed Oct 14, 2020 11:36 pm

Deep Space Dredger: c works some of the time - the rest of the time it takes a veritable eternity as it sends your Cobra whizzing off to the far end of the galaxy; C never works...

In order for the Fast Docking Computer (shift+c) to work the following code must be included in the station's or carrier's entry in shipdata.plist:

Code: Select all

 "allows_fast_docking" = yes; 

It might behoove you to make an in depth study of the HOW TO OXP page as you seem to have reached a point where The Dark Side is calling out to you. Do not worry, cookies are available. When first starting out on my never ending tweaking parade the list of plists that are a bit further down on that page proved invaluable. They give you access to an endless realm of possibilities. JavaScript and Materials and Shaders and all of the other stuff that make Oolite what it is are topics for later discussions. First learn the basics of the plists in an OXZ's Config folder and what they can and cannot do. Bookmark the HOW TO OXP page as you will be referring back to it quite often. My journeys there still occur almost daily.

In the macOS, iOS, NeXTSTEP, and GNUstep programming frameworks, property list files are files that store serialized objects. Property list files use the filename extension .plist, and thus are often referred to as p-list files.
Property list files are often used to store a user's settings. They are also used to store information about bundles and applications, a task served by the resource fork in the old Mac OS.
Property lists are also used for localization strings for development. These files use the .strings or .stringsdict extensions. The former is a "reduced" old-style plist containing only one dictionary without the braces (see propertyListFromStringsFileFormat),[1] while the latter is a fully-fledged plist. XCode also uses a .pbxproj extension for old-style plists used as project files.

Cholmondely wrote: ↑Thu Oct 15, 2020 7:27 am

Would you happen to know of anything a tad less jargonised?

I also notice that very few of the programming tools which people have mentioned in these hallowed pages seem to work on an AppleMac!

montana05 wrote: ↑Thu Oct 15, 2020 9:49 am

Cholmondely wrote: ↑Thu Oct 15, 2020 7:27 am

Would you happen to know of anything a tad less jargonised?

I also notice that very few of the programming tools which people have mentioned in these hallowed pages seem to work on an AppleMac!

Try this one: .PLIST File Extension, basically similar information but explained for non-programmers as well.

.Category:Oolite scripting shows the available files Oolite is using.

Nite Owl wrote: ↑Thu Oct 15, 2020 5:09 am

Code: Select all

 "allows_fast_docking" = yes; 

<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0">
<dict>

	<key>biosphere_dome_sub</key>
	<dict>
		<key>ai_type</key>
		<string>nullAI.plist</string>
		<key>energy_recharge_rate</key>
		<real>0</real>
		<key>forward_weapon_type</key>
		<string>WEAPON_NONE</string>
		<key>max_energy</key>
		<real>50</real>
		<key>name</key>
		<string>sphere-sub</string>
		<key>model</key>
		<string>sphere.dat</string>
		<key>roles</key>
		<string>sphere-sub-role</string>
		<key>thrust</key>
		<real>0</real>
		<key>frangible</key>
		<false/>
		<key>rotational_velocity</key>
		<!-- Frist number speed higher the slower - rotate around Y axis -->
		<string>25 0.0 0.342 0.0</string>
	</dict>
	
	<key>biosphere</key>
	<dict>
		<key>ai_type</key>
		<string>stationAI.plist</string>
		<key>bounty</key>
		<integer>0</integer>
		<key>energy_recharge_rate</key>
		<real>25</real>
		<key>forward_weapon_type</key>
		<string>WEAPON_NONE</string>
		<key>fuel</key>
		<integer>70</integer>

		<key>has_ecm</key>
		<true/>
		<key>has_shield_enhancer</key>
		<true/>

		<key>max_energy</key>
		<real>10000</real>
		<key>max_flight_pitch</key>
		<real>0</real>
		<key>max_flight_roll</key>
		<real>0</real>
		<key>max_flight_speed</key>
		<real>0</real>
		<key>thrust</key>
		<real>0</real>

		<key>max_missiles</key>
		<integer>0</integer>
		<key>missiles</key>
		<integer>0</integer>

		<key>model</key>
		<string>bs_base.dat</string>
		<key>name</key>
		<string>Bio-Sphere</string>
		<key>roles</key>
		<string>biosphere carrier</string>

		<key>beacon</key>
		<string>B-code</string> 
		<key>beacon_label</key>
		<string>BioSphere</string>
		<key>scanClass</key>
		<string>CLASS_STATION</string>

		<key>subentities</key>
		<array>
			<string>biosphere_dome_sub 0 0 -10 1 0 0 0</string>
			<string>dock -0.1 -116.5 38.2 1 0 0 1</string>

			<string>*FLASHER* 0 266 -16 40 0.5 0.5 50</string>
			<string>*FLASHER* 0 -418 0  40 0.5 0.5 50</string>

			<string>*FLASHER* -181 -116 188 20 0.5 0.5 20</string>
			<string>*FLASHER* 181 -116 188 20 0.5 0.5 20</string>

			<!-- Docking Cross -->
			<string>*FLASHER* -0.1 -116.5 38.2 40  1 0.5 10</string>
			<string>*FLASHER* -0.1 -103.5 38.2 60  1 0.25 5</string>
			<string>*FLASHER* -0.1 -129.5 38.2 60  1 0.25 5</string>
			<string>*FLASHER* 20.1 -116.5 38.2 60  1 0.25 5</string>
			<string>*FLASHER* -20.1 -116.5 38.2 60 1 0.25 5</string>
		</array>
		<key>frangible</key>
		<false/>
	</dict>

</dict>
</plist>

Cholmondely wrote: ↑Wed Mar 24, 2021 1:34 pm

Nite Owl wrote: ↑Thu Oct 15, 2020 5:09 am

Code: Select all

 "allows_fast_docking" = yes; 

This was the code Nite Owl gave above for "Viennese Waltz-free" docking with modern OXP dockables.

1/2) What about legacy script (as for BioSphere)?

Might it be:


<key>fast_docking</key>
<string>yes</string> ?


2/2) And ... which bit of the shipdata.plist tells Oolite that the bally thing is actually dockable in the first place?

<key>allows_fast_docking</key>
<string>yes</string>

Cholmondely wrote: ↑Wed Mar 24, 2021 2:05 pm

Thank you for your help!

hiran wrote: ↑Sun Jan 07, 2024 8:14 pm

I am trying to understand how the docking computer works. Blyme, I did not read this full thread - but it seems related to the docking computer.

First I tried to find docking computer logic at all. Seems it is contained in the vanilla game distributed over several files:
Partly in PlayerEntity, partly in ShipEntity. Partly in the dockingAI.plist script.

But nowhere I find the real algorithm how to approach the dock. Seems the dockingInstructions must be coming from somewhere else - a location that I have not yet found.

Cholmondely wrote: ↑Sun Jan 07, 2024 8:51 pm

hiran wrote: ↑Sun Jan 07, 2024 8:14 pm

I am trying to understand how the docking computer works. Blyme, I did not read this full thread - but it seems related to the docking computer.

First I tried to find docking computer logic at all. Seems it is contained in the vanilla game distributed over several files:
Partly in PlayerEntity, partly in ShipEntity. Partly in the dockingAI.plist script.

But nowhere I find the real algorithm how to approach the dock. Seems the dockingInstructions must be coming from somewhere else - a location that I have not yet found.

Is DockingAI relevant?