Page 1 of 1
Can you identify this?
Posted: Wed Apr 14, 2010 11:52 am
by JazHaz
Just came across this strange looking object:
When I radar mapped it, it identifies as a Boa Class Cruiser. However it looks like an asteroid, in that its roughly globular, but has a texture that I've not seen before. Weirdly the target system doesn't put a box around it.
So I try shooting it. Imagine my horror to find my shields being depleted, and I also get an offender tag (probably from that police ship on my scanner)! I think it's me!:
Have I come across a strange spacial anomaly, that reflects like a fairground mirror, ie distorts?
Posted: Wed Apr 14, 2010 11:58 am
by JazHaz
Here's the last few entries in my log (some errors are probably nothing to do with it):
Code: Select all
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x30b12de8>{"Navy Viper" ID: 147 position: (-14028.7, 4896.17, 154360) scanClass: CLASS_POLICE status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x30afb3b0>{"Navy Viper" ID: 148 position: (-18639.3, 4985.41, 154170) scanClass: CLASS_POLICE status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x30b31430>{"Navy Viper" ID: 149 position: (-14931.9, 4781.51, 155608) scanClass: CLASS_POLICE status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x30b27218>{"Navy Viper" ID: 150 position: (-17662.6, 5062.09, 155599) scanClass: CLASS_POLICE status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x85077a8>{"Navy Viper" ID: 152 position: (-5982.16, -10186.6, 104258) scanClass: CLASS_POLICE status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
[shipEntity.setupEscorts.escortShipCircularReference]: ----- WARNING: Ship <ShipEntity 0x850e3b8>{"Navy Viper" ID: 153 position: (-6254.84, -10341.7, 104133) scanClass: CLASS_POLICE status: STATUS_IN_FLIGHT} requested escorts, when it is an escort ship itself. Avoiding possible circular reference overflow by ignoring escort setup.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[files.notFound]: ----- WARNING: Could not find texture file "bhmTurret_skin.png". Used default no textures material instead.
[ship.escortSetup.wtf]: Pending escort count for <StationEntity 0x29953980>{"Super Bulk Hauler" "Super Bulk Hauler" ID: 159 position: (2662.04, -11141.3, 261393) scanClass: CLASS_NEUTRAL status: STATUS_ACTIVE} is 3, expected 0. This is an internal error, please report it.
[bigShips_populator]: 1 big trader(s) added to the Cetege system.
[snapshot]: >>>>> Snapshot 1280 x 800 file chosen = oolite-007.bmp
[script.javaScript.warning.ooliteDefinedError]: ----- JavaScript warning ("Bounty Scanner" 1.061): Invalid value type for this property. Value not set.
[script.javaScript.warning.ooliteDefinedError]: ../AddOns/BountyScannerv1.061.oxp/Scripts/BountyScanner.js, line 97.
[script.javaScript.exception.ooliteDefinedError]: ***** JavaScript exception ("Bounty Scanner" 1.061): Error: Ship.displayName [setter]: cannot set displayName for player.
[script.javaScript.exception.ooliteDefinedError]: ../AddOns/BountyScannerv1.061.oxp/Scripts/BountyScanner.js, line 97.
[snapshot]: >>>>> Snapshot 1280 x 800 file chosen = oolite-008.bmp
Posted: Wed Apr 14, 2010 12:04 pm
by Diziet Sma
Hah! You've fallen victim to the weird, "Help! I'm killing myself!" bug...
Lemme guess.. you're flying a Boa Class Cruiser..
Despite the disguise (it can look like almost any object, but ID's as the same type of ship you're flying) you were shooting at a strange reflected image of yourself. Every time you scored a hit, you took a hit, right?
So far as I know, nobody has ever made any headway on working out why Oolite occasionally does this.. frustrating, huh?
Posted: Wed Apr 14, 2010 12:25 pm
by JazHaz
Diziet Sma wrote:
Despite the disguise (it can look like almost any object, but ID's as the same type of ship you're flying) you were shooting at a strange reflected image of yourself. Every time you scored a hit, you took a hit, right?
So far as I know, nobody has ever made any headway on working out why Oolite occasionally does this.. frustrating, huh?
Yes thats right, every time I scored, I took a hit. Sounds like my love life!!
Maybe my log might help with this (see second post)?
Posted: Wed Apr 14, 2010 12:27 pm
by Cody
Diziet Sma wrote:you were shooting at a strange reflected image of yourself. Every time you scored a hit, you took a hit, right?
Love it… could be straight out of a ‘Star Trek’ episode, some deception arranged by ’Q’.
Fascinating, as Spock would say.
Posted: Wed Apr 14, 2010 12:30 pm
by JazHaz
El Viejo wrote:
Love it… could be straight out of a ‘Star Trek’ episode, some deception arranged by ’Q’.
Fascinating, as Spock would say.
Thats why I called it a spacial anomaly!
Maybe its not a bug but a feature?
Posted: Thu Apr 15, 2010 12:50 pm
by ADCK
"Stop hitting yourself"
Freaky stuff, never seen this.
Posted: Thu Apr 15, 2010 12:59 pm
by Cmdr James
Diziet Sma wrote:Despite the disguise (it can look like almost any object, but ID's as the same type of ship you're flying) you were shooting at a strange reflected image of yourself. Every time you scored a hit, you took a hit, right?
So far as I know, nobody has ever made any headway on working out why Oolite occasionally does this.. frustrating, huh?
I am not certain, but I always presumed this was caused by the player having an ID of zero, and some incorrectly set up ships not having a properly initialized ID, so they end up with a zero.
Posted: Thu Apr 15, 2010 2:02 pm
by lfnfan
i prefer the 'spatial anomaly' theory.
coo-el and freaky all at the same time.
Posted: Thu Apr 15, 2010 3:17 pm
by Diziet Sma
Cmdr James wrote:Diziet Sma wrote:Despite the disguise (it can look like almost any object, but ID's as the same type of ship you're flying) you were shooting at a strange reflected image of yourself. Every time you scored a hit, you took a hit, right?
So far as I know, nobody has ever made any headway on working out why Oolite occasionally does this.. frustrating, huh?
I am not certain, but I always presumed this was caused by the player having an ID of zero, and some incorrectly set up ships not having a properly initialized ID, so they end up with a zero.
Sounds logical.. so I guess then the question becomes, "how does/can it happen that (very rarely) a ship/object does not have its ID properly initialised?"
Posted: Thu Apr 15, 2010 3:18 pm
by Diziet Sma
ADCK wrote:"Stop hitting yourself"
Freaky stuff, never seen this.
Give it time.. it's only happened to me once..
Posted: Thu Apr 15, 2010 8:20 pm
by JazHaz
Diziet Sma wrote:
Give it time.. it's only happened to me once..
It's happened to me twice now! It happened again in the next session to my original report!
Posted: Thu Apr 15, 2010 9:00 pm
by Cmdr James
it would be nice if someone who sees this could get some info from the target inspector or javascript console.