Oolite Bulletins

For information and discussion about Oolite.
https://bb.oolite.space/

Galactic Navy Strikes Back

https://bb.oolite.space/viewtopic.php?t=6299

Page 16 of 20

Re: Galactic Navy Strikes Back

Posted: Thu Nov 17, 2011 2:06 pm
by CommonSenseOTB
JazHaz wrote:
<cough> :oops:

Thought I'd check the Wiki one more time. Seems that there was v5.4.3 released in October. Installed that and the Seccom at Maxeedso suddenly decloaked...!

All is working fine now. Signed up for my first Reserve Duty mission (well with this Commander anyway).

:oops:
:o :) I find it amusing that an error by JazHaz using an old version results in Yodeebe posting a comment that sparks an idea in my head that I then post and gets split off into its' own thread.

See my signature, hehe! :lol:

Re: Galactic Navy Strikes Back

Posted: Thu Nov 17, 2011 2:13 pm
by Smivs
Some of my best ideas were other people's :?

Re: Galactic Navy Strikes Back

Posted: Thu Nov 17, 2011 2:34 pm
by JazHaz
CommonSenseOTB wrote:
I find it amusing that an error by JazHaz using an old version results in Yodeebe posting a comment that sparks an idea in my head that I then post and gets split off into its' own thread.
I thought the ideas you had were quite interesting, something I'd like to see developed too. That's why I suggested splitting the thread.

Re: Galactic Navy Strikes Back

Posted: Fri Dec 02, 2011 5:46 am
by Fatleaf
I found this in a log and thought I should report it,


04:44:38.719 [station.launchShip.failed]: Cancelled launch for a Rogue Frigate with role pirate, as it is too large for the docking port of the Coriolis Station.


Hope it helps.

Re: Galactic Navy Strikes Back

Posted: Fri Dec 02, 2011 9:42 am
by m4r35n357
Fatleaf wrote:
I found this in a log and thought I should report it,
04:44:38.719 [station.launchShip.failed]: Cancelled launch for a Rogue Frigate with role pirate, as it is too large for the docking port of the Coriolis Station.
Hope it helps.
Should be fixed in the next release, if I understand Eric's comments correctly, see this thread for history:
https://bb.oolite.space/viewtopic.php?f= ... ue+frigate

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 4:55 pm
by JazHaz
As per this thread.

Installed the current nightly, 1.76.0.4675, and was testing the new Enhanced Misjump OXP by cim, which works very well.

Got to interstellar space, surrounded by Thargoids and the Navy. Got destroyed as normal! :oops:

Checked my log, found the following errors:

Code: Select all

13:10:08.984 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-5778.29, -3755.24, -3478.65) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:10.171 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-6008.06, -3670.71, -3482.42) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:12.953 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-6619.03, -3541.26, -2988.17) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:14.296 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-6664.67, -3619.77, -2482.9) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:16.109 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-6322.07, -3850.83, -1918.95) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:16.796 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-4878.13, -4620.82, 1960.4) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:18.265 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-5825.08, -4105.93, -1379.5) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:19.984 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe5e34c0>{"Thargoid Battleship" position: (-5412.14, -4290.62, -911.441) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:23.343 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-4006.76, -5675.27, 667.237) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:24.843 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-3978.61, -5854.47, 364.403) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:25.015 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-3974.9, -5877.28, 326.127) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:26.296 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-3954.19, -6037.23, 41.8371) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:26.875 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-3945.98, -6107.7, -86.8239) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:27.156 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-3943.67, -6131.78, -133.282) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.
13:10:27.578 [ship.missileLaunch.invalidPosition]: ***** ERROR: The missile_launch_position defines a position (0, 0, -25.5) behind the <ShipEntity 0xe165640>{"Thargoid Battleship" position: (-3940.15, -6168.09, -203.113) scanClass: CLASS_THARGOID status: STATUS_IN_FLIGHT}. In future versions such missiles may explode on launch because they have to travel through the ship.

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 5:11 pm
by Fatleaf
Have a look at this post. The issue is with Thargorn Threat.

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 6:14 pm
by Eric Walch
Fatleaf wrote:
Have a look at this post. The issue is with Thargorn Threat.
Its not with Thargorn Threat, but inside GalNavy some values are still wrong, despite all the error logging that should have been noticed during the past 6 months.

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 6:33 pm
by Ironfist
The same error is also true for the Thargon Cruiser.

Ironfist

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 6:33 pm
by Fatleaf
That is weird as I have had Gal Navy for ages and this error has not been in the log. I tend to check regularly and report most I see.

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 6:43 pm
by JazHaz
Fatleaf wrote:
That is weird as I have had Gal Navy for ages and this error has not been in the log. I tend to check regularly and report most I see.
Maybe Thargorn Threat and GalNavy has been conflicting, and only TT has been winning over which OXP controls interstellar space? :roll:

Re: Galactic Navy Strikes Back

Posted: Sun Dec 04, 2011 7:02 pm
by Fatleaf
Could be JazHaz.

I have been looking into the shipdata.plist for Galnavy and there are a few entries for thargoids namely: galnav-thargoid, galnav-thargcruiser and galnav-thargbatship. But only one like_ship which is the galnav-thargcruiser with the galnav-thargoid. But no texture for any Thargoid. There is .dat models for them though.

I am a bit confused.

Re: Galactic Navy Strikes Back

Posted: Mon Jun 18, 2012 2:15 pm
by Fatleaf
I had a CTD and this is what I found in the log. A Mine sweeper ship was repeating its message over and over and it was when I went to attempt scooping the (now white on the scanner) Qmine that the CTD occurred.

Here is the edited log entry.

Code: Select all

Opening log for Oolite version 1.76 
20:06:16.050 [ai.error.stackOverflow]: ***** ERROR: AI stack overflow for <ShipEntity 0x17680f28>{"Quirium Cascade Mine"} in dumbAI.plist: GLOBAL -- stack:

  20:06:16.050 [ai.error.stackOverflow.dump]:  31: timebombAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  30: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  29: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  28: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  27: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  26: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  25: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  24: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  23: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  22: dumbAI.plist: GLOBAL
  20:06:16.050 [ai.error.stackOverflow.dump]:  21: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  20: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  19: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  18: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  17: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  16: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  15: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  14: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  13: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  12: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  11: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:  10: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   9: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   8: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   7: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   6: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   5: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   4: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   3: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   2: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   1: dumbAI.plist: GLOBAL
  20:06:16.051 [ai.error.stackOverflow.dump]:   0: dumbAI.plist: GLOBAL
20:06:16.052 [script.error.exception]: ***** EXCEPTION OoliteException: AI stack overflow for <ShipEntity 0x17680f28>{"Quirium Cascade Mine" position: (540.425, 4780.43, 524537) scanClass: CLASS_CARGO status: STATUS_IN_FLIGHT} while handling legacy script actions for <AI "navyBattlegroupMineSweeperAI.plist" state FLYING_ESCORT - safeScriptActionOnTarget:>

20:07:29.782 [exception]: ***** Exception during [manageCollisions] in -[PlayerEntity update:] : OoliteException : AI stack overflow for <ShipEntity 0x17680f28>{"Quirium Cascade Mine" position: (-382.765, 5135.34, 525023) scanClass: CLASS_CARGO status: STATUS_IN_FLIGHT} *****
Hope it helps.

Re: Galactic Navy Strikes Back

Posted: Sat Jul 14, 2012 3:41 pm
by Duggan
In the Reserve Leader board as displayed at Se com Stations I note that having flown in some 37 Sorties and exceeding the Pilot Xequati (or some such) who appears on the bottom of said Leader board having flown 32 sorties.

Would I be correct in assuming that it don't matter how many Sorties I fly, I am never going to get on the reserve Leader board?

Thanks in advance.

Re: Galactic Navy Strikes Back

Posted: Sat Jul 14, 2012 4:29 pm
by Pleb
No its a predetermined list of names and random number of sorties, that sometimes increases. The players sorties are listed below the others, regardless of how many you have.
All times are UTC
Page 16 of 20

Powered by phpBB® Forum Software © phpBB Limited