Steve-Law
Is there a logical explanation for this one then? (actual position data changed wink.gif

CODE

>TU 167: Move to planet orbit {12} {123}
Entering orbit of Planet (123)
Scanned:
AFF SHIP HERE I AM (4321) - {50 Heavy Hulls}
Class Class Ship Ship {Light Ablative Armour}
Total TU cost for this action is 5

>TU 162: Detailed Scan {4321}
Error - Position not found at this location.
Total TU cost for this action is 10



huh? blink.gif

(Actual turn sent to KJC)
Ted
Maybe the ship was moving from the location as you scanned it first time,so it wasn't there when the detailed scan order kicked in.
Steve-Law
QUOTE (Ted @ Nov 25 2004, 03:24 PM)
Maybe the ship was moving from the location as you scanned it first time,so it wasn't there when the detailed scan order kicked in.

Is that how orders work? I thought each position run through it's orders in turn not "simultaneously". Damned unlucky if that's what happened! The target moves away in that 5 tu window of opportunity! gah! ohmy.gif

Well I'm still there at the end of the turn I suppose I'll know if that happened tomorrow.
[oops, correction, no I'm not still in orbit, just as well really smile.gif ]
Gandolph
ive had this happen to me, i was told by Mica that the turn to detail scan is independant and the position may still be there, but you havent scanned it for this particular order, IE need more sensors, the profile of the ship is taken into account, the quad within the system etc etc etc

Steve-Law
QUOTE (Gandolph @ Nov 25 2004, 04:36 PM)
ive had this happen to me, i was told by Mica that the turn to detail scan is independant and the position may still be there, but you havent scanned it for this particular order, IE need more sensors, the profile of the ship is taken into account, the quad within the system etc etc etc

I think I understand what you're saying but does that make any sense? If it can see it in a general scan when simply entering orbit, surely it can also see it when directing a scan specifically for it?

Surely it would make more sense to have some kind of flag/record of the positions you've already scanned in the location? If you've already spotted it, a detailed scan can't fail, but if you didn't scan it the first time, *then* roll the numbers for it.

unsure.gif

(So this is "expected" behaviour then, if a little odd? i.e. not a bug?)
ptb
QUOTE
Surely it would make more sense to have some kind of flag/record of the positions you've already scanned in the location? If you've already spotted it, a detailed scan can't fail, but if you didn't scan it the first time, *then* roll the numbers for it.


or even just so you can change the error message to something along the lines of "your sensors are unable to retrive a detailed scan of the ship" or "your scan was blocked" etc etc...
Steve-Law
[From Mica]

Brought up at the pubmeet. A detailed scan is 10TU's so even
when accounting for increased chance it is not guaranteed the
position will be locked for a detailed scan.
We will probably adjust this to allow the detailed scan TU's to be
set by players.

Regards

Mica

[So moving this thread from bugs]