[RELEASE] The Slug

[mandoman]

This is a Slug, er, I mean THE Slug. It is the Slug because it was the only name I could come up with when I went to save the initial design in Blender. It looked like a slug, so that's what I called it. The Slug is slow, and big. 100 tons of cargo capable kind of big. While it does have forward and aft lasers, it's kind of a sitting duck for Staer9's vultures, not to mention all the other pirate vultures out there, including my own. It does carry 10 missiles, and I advise you to keep them well stocked if you intend on flying this Slug. The NPC version is equiped with 6 escort ships. Fast, and quick little bullets called the Piranha. The Slug goes a max speed of 200, has a max energy level of 400, and a recharge rate of 4.5. Believe me, it's big enough to carry what it takes to have those energy levels, and it needs all the energy it can get. The Slug also comes standard with ECM, Docking Computers (which I have only used once, as it isn't that hard to dock if you're careful), fuel injection, fuel scoop, and shield boosters. I can't guarantee what individual system stations will sell it for, or include with it, though. If you are into trade, this ship is pretty good for that. I flew it several times, and though I didn't kill anything, most of the time I was able to get away from pirates, with fuel injection and tossing a few missiles around. If nothing else, the missiles are a much needed distraction to make your get away. Hope you enjoy it as much as I have.

https://www.box.com/s/40599934a30d3ceecf6f

[DredgerMan]

Hi Mandoman,

after loading the Slug, I got the following warnings:

15:35:19.162 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0xca61a98>{"Slug" position: (3350.85, -8467.26, 349603) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
SNIP
15:35:35.094 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x95649b8>{"Slug" position: (109084, 116135, 300989) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
15:36:15.304 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x287fe08>{"Slug" position: (-2019.16, 9265.73, 335757) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
15:38:21.963 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x98dacd8>{"Slug" position: (5743.95, 5672.31, 646.417) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
16:04:33.141 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x9508388>{"Slug" position: (-10997.1, -9114.72, 286540) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
16:04:33.365 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x15baca90>{"Slug" position: (-39502.6, 170971, 775757) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
16:20:11.009 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -20.5) behind the <ShipEntity 0x9509198>{"Thargoid Warship" position: (-4569.52, 16254, 172849) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
16:27:39.395 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x130f48f0>{"Slug" position: (-12946.3, -8307.75, 438814) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
17:41:03.671 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x13e87518>{"Slug" position: (9592.35, 586.931, 287807) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
18:03:53.242 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x13e835d0>{"Slug" position: (6630.65, 5134.76, 171589) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
18:03:53.457 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0xc9c7950>{"Slug" position: (-52985.7, 69773, 359448) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
18:03:53.526 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0xc9c8058>{"Slug" position: (-51994.2, 69853.5, 359189) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
18:06:08.242 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0xcb81298>{"Slug" position: (15127.2, 8725.69, -9367.32) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
18:27:36.570 [ship.setUp.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0xcf0ee10>{"Slug" position: (4917.04, 12522.7, 390086) scanClass: CLASS_NEUTRAL status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.

[Commander McLane]

Remove "escort" from the roles key, and you should be fine. The ship is probably not meant to be an escort.

[DredgerMan]

Remove "escort" from the roles key, and you should be fine. The ship is probably not meant to be an escort.

Ohh, that simple? Hmm, even I could do that. And done.

Two learning moments in one day!

Edited due to a stupid spelling mistake.

[DredgerMan]

Hmmm,

sorted one problem out, now a second.

19:38:50.602 [shipData.load.begin]: Loading ship data.
19:38:50.718 [plist.parse.failed]: Failed to parse ../AddOns/PiranhaV1.1.oxp/Config/shipdata.plist as a property list.
Parse failed at line 23 (char 928) - unexpected character (wanted '=')
19:38:50.778 [shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved: scarred-alloy
19:38:51.218 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "Piranha-player" does not have a corresponding shipdata.plist entry, ignoring.

I assume the third entry is to do with the Slug OXP as well as I haven't seen that one before.

[Commander McLane]

19:38:50.602 [shipData.load.begin]: Loading ship data.
19:38:50.718 [plist.parse.failed]: Failed to parse ../AddOns/PiranhaV1.1.oxp/Config/shipdata.plist as a property list.
Parse failed at line 23 (char 928) - unexpected character (wanted '=')
19:38:50.778 [shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved: scarred-alloy
19:38:51.218 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "Piranha-player" does not have a corresponding shipdata.plist entry, ignoring.

The first and last point to a problem in PiranhaV1.1.oxp. Its shipdata.plist contains a fatal syntax error which makes the whole plist unreadable for your computer. The error message points to line 23 of the plist, but it's also possible that the actual error is higher up. The third ("WARNING") is a secondary problem: because the shipdata.plist is invalid and discarded wholesale, there is no shipdata for the Piranha-player, which gets noticed when the ship shows up in shipyard.plist.

The second error message is odd. The scarred-alloy is part of Oolite itself, so it shouldn't be missing, unless you have messed with Oolite's own shipdata.plist.

[DredgerMan]

19:38:50.602 [shipData.load.begin]: Loading ship data.
19:38:50.718 [plist.parse.failed]: Failed to parse ../AddOns/PiranhaV1.1.oxp/Config/shipdata.plist as a property list.
Parse failed at line 23 (char 928) - unexpected character (wanted '=')
19:38:50.778 [shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved: scarred-alloy
19:38:51.218 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "Piranha-player" does not have a corresponding shipdata.plist entry, ignoring.

The first and last point to a problem in PiranhaV1.1.oxp. Its shipdata.plist contains a fatal syntax error which makes the whole plist unreadable for your computer. The error message points to line 23 of the plist, but it's also possible that the actual error is higher up. The third ("WARNING") is a secondary problem: because the shipdata.plist is invalid and discarded wholesale, there is no shipdata for the Piranha-player, which gets noticed when the ship shows up in shipyard.plist.

The second error message is odd. The scarred-alloy is part of Oolite itself, so it shouldn't be missing, unless you have messed with Oolite's own shipdata.plist.

I didn't mess with Oolite's shipdata.plist as such, just opened it to compare the escape pod entry there with the one for Neolite. But I used Notepad ++ and am pretty sure I didn't save the Oolite plist anyway.

[Commander McLane]

I didn't mess with Oolite's shipdata.plist as such, just opened it to compare the escape pod entry there with the one for Neolite. But I used Notepad ++ and am pretty sure I didn't save the Oolite plist anyway.

Do you have Neolite still installed? I guess it'll be the culprit.

EDIT: Yep. There is a bug in the shipdata.plist of Neolite_Core_Replace_1.1.1.oxp.

Code: Select all

    "scarred-alloy" =     {
        "like_ship" = "neo_alloy";

must be

Code: Select all

    "scarred-alloy" =     {
        "like_ship" = "alloy";

Note: the bug is only in the core replacement OXP. The core addition OXP is fine (there it must be "like_ship" = "neo_alloy"). I suspect a c&p-error.

[DredgerMan]

I didn't mess with Oolite's shipdata.plist as such, just opened it to compare the escape pod entry there with the one for Neolite. But I used Notepad ++ and am pretty sure I didn't save the Oolite plist anyway.

Do you have Neolite still installed? I guess it'll be the culprit.

EDIT: Yep. There is a bug in the shipdata.plist of Neolite_Core_Replace_1.1.1.oxp.

Code: Select all

    "scarred-alloy" =     {
        "like_ship" = "neo_alloy";

must be

Code: Select all

    "scarred-alloy" =     {
        "like_ship" = "alloy";

Thanks, Commander, I'll amend it at my end. Who klnows, I might just end up with an error free version of Neolite.

[mandoman]

Okay, I'm a bit rattled, here. I corrected the stupid "escort" goof I keep making, and now the Latest.log shouldn't come up with that problem. as for the Piranha error, I don't get that in my Latest.log at all, and I've had it running in there for quite some time. I have a question though. What ships use the Neolite shader oxps? I just want to remove them, because it seems to be a constant source of errors on my machine. Here is what my Latest.log says.

Code: Select all

15:15:35.182 [files.notFound]: ----- WARNING: Could not find texture file "FA_Tanker_normalmap.png".
  15:15:36.245 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:36.245 [shader.load.fullModeFailed]: ----- WARNING: Could not build shader neolite-std.vs/neolite-std.fs in full complexity mode, trying simple mode.
  15:15:36.255 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:36.255 [shader.load.failed]: ***** ERROR: Could not build shader neolite-std.vs/neolite-std.fs.
15:15:37.566 [ai.load.failed.unknownAI]: Can't switch AI for <ShipEntity 0xffcf1b0>{"Griffin Two"} to "traderAI.plist" - could not load file.
  15:15:37.622 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:37.622 [shader.load.fullModeFailed]: ----- WARNING: Could not build shader neolite-std.vs/neolite-std.fs in full complexity mode, trying simple mode.
  15:15:37.633 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:37.633 [shader.load.failed]: ***** ERROR: Could not build shader neolite-std.vs/neolite-std.fs.
  15:15:38.248 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:38.248 [shader.load.fullModeFailed]: ----- WARNING: Could not build shader neolite-std.vs/neolite-std.fs in full complexity mode, trying simple mode.
  15:15:38.259 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:38.259 [shader.load.failed]: ***** ERROR: Could not build shader neolite-std.vs/neolite-std.fs.
15:15:38.622 [files.notFound]: ----- WARNING: Could not find texture file "FA_Sunracer_normalmap.png".
  15:15:38.672 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:38.672 [shader.load.fullModeFailed]: ----- WARNING: Could not build shader neolite-std.vs/neolite-std.fs in full complexity mode, trying simple mode.
  15:15:38.682 [files.notFound]: GLSL ERROR: failed to find fragment program neolite-std.vs.
15:15:38.682 [shader.load.failed]: ***** ERROR: Could not build shader neolite-std.vs/neolite-std.fs.
15:15:38.893 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'NSPOSIXErrorDomain 111' (outStream status: 7, inStream status: 7)."
15:15:38.893 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'unknown error.' (outStream status: 0, inStream status: 0)."
15:15:38.893 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.
15:15:40.206 [Flightlog]: Kills Store set to player score
15:15:40.667 [Save Anywhere OXP 3.2]: initialising Save Anywhere OXP 3.2
15:15:40.735 [loading.complete]: ========== Loading complete. ==========
15:15:43.365 [files.notFound]: ----- WARNING: Could not find texture file "FA_Sunracer_normalmap.png".

I'll look into the error reported on the Piranha, but could someone give me a list of ships that use the neolite shaders? Thank you.

[mandoman]

The cause of error in Latest.log was due to the absence of an "=" symbol. Fixed, and posted a new link to corrected version. I still don't understand why I haven't been getting that error in my Latest.log, though.

[Fatleaf]

The answer has already been given: delete the Neolite oxp.

[mandoman]

I've done that before, and I still get shader errors. I'll dump it and see what happens.

I take it back, I've already removed it from AddOns, and that Latest.log was post removal. There must be ships I still have installed that use Neolite, and am getting errors because I removed the Neolite oxps. Also, I keep getting this error, but have no idea what oxp has the ship mentioned.

Code: Select all

15:15:24.340 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "asad_gunship_player" does not have a corresponding shipdata.plist entry, ignoring.

[mandoman]

If I'm frustrating you, believe me, I'm right there with you.

[Fatleaf]

I've done that before, and I still get shader errors. I'll dump it and see what happens.

I take it back, I've already removed it from AddOns, and that Latest.log was post removal. There must be ships I still have installed that use Neolite, and am getting errors because I removed the Neolite oxps. Also, I keep getting this error, but have no idea what oxp has the ship mentioned.

Code: Select all

15:15:24.340 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "asad_gunship_player" does not have a corresponding shipdata.plist entry, ignoring.

AH well, it looks like you are going to have to go through your ship oxp's and find out which one/ones it/they are!
Now THAT is frustrating