Unexpected desktop moment on launch

[overmage]

These logs have any clue in them?

[ship.escortSetup.wtf]: Pending escort count for <ShipEntity 0xc6457d0>{"Ixian Battle Cruiser" ID: 282 position: (381174, 135548, 632751) scanClass: CLASS_NEUTRAL status: STATUS_LAUNCHING} is 2, expected 0. This is an internal error, please report it.
[files.notFound]: ----- WARNING: Could not find texture file "moray-neolite-effectsmap.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "moray-neolite-normalmap.png". Used default no textures material instead.
[ship.escortSetup.wtf]: Pending escort count for <ShipEntity 0xf173670>{"Strelka Cruiseliner" ID: 285 position: (142.28, 94.8535, 758.828) scanClass: CLASS_NO_DRAW status: STATUS_COCKPIT_DISPLAY} is 4, expected 0. This is an internal error, please report it.
[ship.escortSetup.wtf]: Pending escort count for <ShipEntity 0xf173670>{"Strelka Cruiseliner" ID: 285 position: (142.28, 94.8535, 758.828) scanClass: CLASS_NO_DRAW status: STATUS_COCKPIT_DISPLAY} is 4, expected 0. This is an internal error, please report it.
[ship.escortSetup.wtf]: Pending escort count for <ShipEntity 0xd8830b8>{"Strelka Cruiseliner" ID: 296 position: (142.28, 94.8535, 758.828) scanClass: CLASS_NO_DRAW status: STATUS_COCKPIT_DISPLAY} is 4, expected 0. This is an internal error, please report it.
[sound.customSounds]: ***** ERROR: could not resolve sound name in customsounds.plist for '[menu-navigation-not]', no sound will be played.
[ship.escortSetup.wtf]: Pending escort count for <ShipEntity 0xfae34a8>{"Falcon-E" ID: 303 position: (1781.1, 3489.74, -6698.76) scanClass: CLASS_NEUTRAL status: STATUS_LAUNCHING} is 1, expected 0. This is an internal error, please report it.
[Pi-Forty-Two Con stores]: Adding constore with player launching from station
[ship.escortSetup.wtf]: Pending escort count for <StationEntity 0x160dbb78>{"Deep Space Dredger Freighter" "Deep Space Dredger Freighter" ID: 322 position: (11848.4, 8970.07, 457475) scanClass: CLASS_NEUTRAL status: STATUS_ACTIVE} is 8, expected 0. This is an internal error, please report it.
[bigShips_populator]: 2 big trader(s) added to the Diso system.
[testscript.spawn]: Generated 8 griff_cobby3 for testing purposes.
[script.javaScript.warning.206]: ----- JavaScript warning ("yah_station_facing" ): Entity.setOrientation() is deprecated, use entity.orientation = foo instead.
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0xf408e90>{"Grass Snake" ID: 344 position: (491927, -3.22251e+006, 925510) 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.

[Screet]

These logs have any clue in them?

What I understand from these log infos, it should be harmless errors. If a crash happens, you should also check "stderr.txt"

However, since you are using the trunk version with it's new graphics features...I do wonder if you suffer from the same problem as L did, when he made his reports about "crashy dredgers":
https://bb.oolite.space/viewtopic.php?t=6185

Did you give his test-case oxp a try?

Interestingly, it only crashed on his system so far, but reproducible. The workaround for him was to turn off the shaders...

Screet

[another_commander]

I see a couple of issues with the log you posted. First,

Code: Select all

[files.notFound]: ----- WARNING: Could not find texture file "moray-neolite-effectsmap.png". Used default no textures material instead. 
[files.notFound]: ----- WARNING: Could not find texture file "moray-neolite-normalmap.png". Used default no textures material instead. 

Your Neolite OXP is incomplete and is missing textures. It looks like these textures are used in the shaders for effects and normal maps and if I am guessing correctly this could be the reason for your crash. Maybe you can follow Screet's suggestion and switch shaders off. If it works, then it most likely will be it.

Also, your Grass Snake shipdata info is referencing Grass Snake (or some other ship) as an escort ship and tries to assign escorts to escorts. Although this does not crash Oolite any longer, it is a bug in the plist and it will be a good idea to remove the escort references from the Grass Snake's shipdata dictionary.

[Lestradae]

... shipdata info is referencing Grass Snake as an escort ship and tries to assign escorts to escorts. Although this does not crash Oolite any longer, it is a bug in the plist and it will be a good idea to remove the escort references from the Grass Snake's shipdata dictionary.

I have a question regarding that.

The circular escorts bug, does it happen anytime when a ship that is selected as an escort also has escorts defined for itself?

Because, if - say - we have a Behemoth with Tigers defined as escorts, and the Tigers have for example Cobra Mk III's defined as escorts, then I assumed that a Behemoth would simply be spawned with the Tiger escorts but without a Cobra Mk III armada, while if a Tiger was spawned it would be spawned with its Cobra Mk III escorts.

If I understood you correctly that is not the case? Meaning, that any ship that is getting selected as escort ship anywhere in shipdata.plist must not have escorts selected for the case it isn't an escort itself?



L

[another_commander]

Correct. If your ship has escorts defined in shipdata.plist, then it should not be an escort itself. You resolve the issue by either removing the escort role from the roleset or by removing the escorts references. *

In any case, the escort ship should not be the same as the ship generating it. The circular reference warning would occur also if the Grass Snake has escorts other than Grass Snake defined. I expressed myself somewhat inaccurately earlier (sorry, this happens when you post in the middle of the night). I hope things are somewhat clearer now.

*Edit:Misinformation corrected. Actually, it can be an escort itself and the game takes care of any problems that may result from ships being escorts to escorts.

[Lestradae]

Thanks for the info A_C, another to-do point.

[Screet]

Correct. If your ship has escorts defined in shipdata.plist, then it should not be an escort itself. You resolve the issue by either removing the escort role from the roleset or by removing the escorts references. In any case, the escort ship cannot be the same as the ship generating it. The circular reference warning would occur also if the Grass Snake has escorts other than Grass Snake defined. I expressed myself somewhat inaccurately earlier (sorry, this happens when you post in the middle of the night). I hope things are somewhat clearer now.

Hmmm. Just a question: If L. would produce a tiger and then like-ship a tiger-escort with escort role and a tiger-leader without escort role, but escorts on it's own, everything would be fine?

Screet

[another_commander]

Yes, that would be the way to make a group of same ships where one of them is leader and the rest are its escorts.

[another_commander]

Because, if - say - we have a Behemoth with Tigers defined as escorts, and the Tigers have for example Cobra Mk III's defined as escorts, then I assumed that a Behemoth would simply be spawned with the Tiger escorts but without a Cobra Mk III armada, while if a Tiger was spawned it would be spawned with its Cobra Mk III escorts.

Lestradae, I just reread what you have written here and it is exactly what happens. I really need to take reading lessons or stop trying to respond to the forum while at work I am editing my earlier posts accordingly.

[Lestradae]

A_C, no problem

No harm done, the new info just makes my to-do list shorter.

Also looking in ten times a day from work over here - should actually be doing something(s) else ...

Cheers,

L