EscortDeck

[NChw]

Docked in a Deep Space Dredger with a DTT Manta, usable, in the EscortDeck, locked.
After I launched the pad was still locked, but empty.
Nothing in Latest.log.
The DTT Manta is a special case, as in a prisitine condition it's too wide for the pads, but in combat, far before it's turned derelict, it looses its wings and then it fits in a pad.
I will turn debug back on on this OXP, perhaps next time there will be something in the logs.

UPDATE: usable DTT Mantas don't desappear at docking in a station (it was a Trade Post, not the main station), I was able to see it on the F4 interface for EscortDeck... I didn't store it in HypeSpaceHangar but launched, and it was gone.

From the Latest.log (I enabled Debug and put some logs cycling through the pads and "printing" the shipdata):

Code: Select all

11:42:16.036 [escortdeck]: Launching
11:42:16.037 [escortdeck]: Decks has 6 pads
11:42:16.037 [escortdeck]: Pad 5: null
11:42:16.037 [escortdeck]: Pad 4: null
11:42:16.037 [escortdeck]: Pad 3: 
11:42:16.037 [escortdeck]: Pad 2: 
11:42:16.037 [escortdeck]: Pad 1: 0,240,180107644484.46112,Derelict DTT Manta: Captain Blood's Song 6,Raleen,,,,,DTT Manta,,0,E1 DTT Manta,240,0.699999988079071,0.8999999761581421,1,0.8999999761581421,240,1,1,2,32,5,320,255,4,18,0.25,7,,15,,,128,128,2,128,128,2,0,dttmanta,EQ_WEAPON_BEAM_LASER,EQ_WEAPON_BEAM_LASER,,,,EQ_SC_SHIELD_CYCLER_INTERNAL,EQUIPMENT_OK,EQ_TELESCOPE,EQUIPMENT_OK,EQ_COMBATMFD,EQUIPMENT_OK,EQ_HEAT_SHIELD,EQUIPMENT_OK,EQ_MULTI_TARGET,EQUIPMENT_OK,EQ_FUEL_SCOOPS,EQUIPMENT_OK,EQ_ESCAPE_POD,EQUIPMENT_OK,EQ_ADVANCED_COMPASS,EQUIPMENT_OK,EQ_TARGET_MEMORY,EQUIPMENT_OK,EQ_ENERGY_UNIT,EQUIPMENT_OK,EQ_WORMHOLE_SCANNER,EQUIPMENT_OK,EQ_FUEL_INJECTION,EQUIPMENT_OK,EQ_NSHIELDS_NPC_SHIELD_BOOSTER,EQUIPMENT_OK,EQ_SCANNER_SHOW_MISSILE_TARGET,EQUIPMENT_OK,EQ_ECM,EQUIPMENT_OK,EQ_INTEGRATED_TARGETING_SYSTEM,EQUIPMENT_OK,EQ_TARGET_AUTOLOCK,EQUIPMENT_OK,EQ_SHIP_VERSION_69,EQUIPMENT_OK,,5.800000000000001,,,,22546,[object Object]
11:42:16.037 [escortdeck]: Pad 0: null
11:42:16.038 [escortdeck]: Spawn escort pad:0 d:null s:null
11:42:16.039 [escortdeck]: Spawn escort pad:1 d:0,240,180107644484.46112,Derelict DTT Manta: Captain Blood's Song 6,Raleen,,,,,DTT Manta,,0,E1 DTT Manta,240,0.699999988079071,0.8999999761581421,1,0.8999999761581421,240,1,1,2,32,5,320,255,4,18,0.25,7,,15,,,128,128,2,128,128,2,0,dttmanta,EQ_WEAPON_BEAM_LASER,EQ_WEAPON_BEAM_LASER,,,,EQ_SC_SHIELD_CYCLER_INTERNAL,EQUIPMENT_OK,EQ_TELESCOPE,EQUIPMENT_OK,EQ_COMBATMFD,EQUIPMENT_OK,EQ_HEAT_SHIELD,EQUIPMENT_OK,EQ_MULTI_TARGET,EQUIPMENT_OK,EQ_FUEL_SCOOPS,EQUIPMENT_OK,EQ_ESCAPE_POD,EQUIPMENT_OK,EQ_ADVANCED_COMPASS,EQUIPMENT_OK,EQ_TARGET_MEMORY,EQUIPMENT_OK,EQ_ENERGY_UNIT,EQUIPMENT_OK,EQ_WORMHOLE_SCANNER,EQUIPMENT_OK,EQ_FUEL_INJECTION,EQUIPMENT_OK,EQ_NSHIELDS_NPC_SHIELD_BOOSTER,EQUIPMENT_OK,EQ_SCANNER_SHOW_MISSILE_TARGET,EQUIPMENT_OK,EQ_ECM,EQUIPMENT_OK,EQ_INTEGRATED_TARGETING_SYSTEM,EQUIPMENT_OK,EQ_TARGET_AUTOLOCK,EQUIPMENT_OK,EQ_SHIP_VERSION_69,EQUIPMENT_OK,,5.800000000000001,,,,22546,[object Object] s:[Ship "DTT Manta" position: (1.00028e+07, 619.965, 3205.11) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT]
11:42:16.042 [escortdeck]: Pad 2: too wide (130m > 70m)
11:42:16.042 [escortdeck]: 2. spawn [Ship "DTT Manta" position: (1.00028e+07, 619.965, 3205.11) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT] r:too wide (130m > 70m)
11:42:16.042 [escortdeck]: Spawn escort pad:2 d: s:null
11:42:16.042 [escortdeck]: Spawn escort pad:3 d: s:null
11:42:16.042 [escortdeck]: Spawn escort pad:4 d:null s:null
11:42:16.042 [escortdeck]: Spawn escort pad:5 d:null s:null

From the logs, it was spawned then found too wide for the pad (I presume I could find it near the Witchpoint...)

But in-flight I've had no trouble picking-up a derelict DTT Manta (no wings!) into EscortDeck, drop it and pick it again (I didn't try to launch and call back the usable one)... I guess restoring the shipdata to the spawned DTT Manta didn't restore it to the un-winged version.

I have a similar, but more fundamental issue:
Note: this is the first time that I have tried to use an Escort Deck along with a big ship that needs the player to swap to a Cargo ship to dock
I collected a usable Medical Moray Boat onto my EscortDeckXL, along with 7 other derelict ships and then docked my Andromeda into a Deep Space dredger (by landing my Cargo ship). All went well, as the 7 non-usable salvaged ships were automatically sold. I picked up a load of alloys and launched back to 'become' the Andromeda. My Medical Moray Boat still was there on slot 1. I then docked into the main station in that sector and the Moray was still visible on slot 1 when I checked via the F4 menu. However, when I launched again, it vanished. Nothing appeared in the log to explain why.

I tried reloading the docked savegame and selling the Manta, then replacing it with a cheap (new) adder escort, which loaded onto slot 1 of the deck. On launch, it had vanished too...

To try and narrow it down, I stripped out most of my loaded oxps, leaving only:
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/CabalLibray-1.7.2.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.CaptMurphy.ShipStorageHelper.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.EricWalch.DeepSpaceDredger.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.Norby.Andromeda.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.Norby.EscortDeck.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.Norby.Trails.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.Svengali.OXPConfig.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.Thargoid.Bigships.oxz
C:\Oolite/oolite.app/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.zzz.Montana05.resource_pack_01.oxz
../AddOns/CombatHUD-WS_v4.1.oxz

...but the issue remains. Any suggestions on how to turn on logging or identify a problem in the save file/log?

[Cholmondely]

Any suggestions on how to turn on logging or identify a problem in the save file/log?

You need LogEvents installed (Misc. oxp available on the in-game Expansions Manager)

The detail will then be output to your Latest.Log

[NChw]

[Replying to myself ]

From the same Andromeda savegame and the same limited set of oxps, I bought an adder escort, which loaded into slot 2 on my EscortDeckXL. On launch, my escort deck was empty.


I reloaded and sold the Andromeda by changing my ship to a Cobra Mk1, which strangely appeared with its own Escort Deck (not XL) that still had the Moray Medical Boat derelict on board in slot 1. As this was a 52 ton ship on a 20 ton deck, I was not hopeful On launch, the escort deck was empty.
I repeated those steps and sold the offending Moray escort from the Cobra deck, prior to launching. On buying an added escort... this stayed in place when I launched


I restarted and then sold the Moray bought the Cobra again with a sidewinder escort...
on launching, the adder was safely available on the escort deck in slot 1.

So... my problem may be to do with the Andromeda interaction with the escort deck. I note that the XL deck for the Andromeda has eight bays each of 70x29x95 and the Moray is 59x29x70, so it should fit on the deck.

[NChw]

Any suggestions on how to turn on logging or identify a problem in the save file/log?

You need LogEvents installed (Misc. oxp available on the in-game Expansions Manager)

The detail will then be output to your Latest.Log

Thank you kindly! I will work on that later...

[NChw]

I turned on logging and did not see anything useful:
for the Andromeda launch where it loses the escort, there just is no line reporting that the escort was spawned at 0 km (which was present in the log of the cobra launch that kept its escort).

I copied logcontrol.plist into AddOns and then set _override = yes; to turn on all available logging.
This give me a big log file, but I don't see any error or failure messages.