Python A6 Sensors bug. Anyone confirm?

StephenB

StephenB
Greetings Commanders I recently upgraded from a B6 to A6 Sensor suite in my Python and have discovered abnormalities. It says it has a range of 7km but can't find targets above 6km. Not only that but it will sometimes only show targets less than 3km from my position changing pip positions to systems has no effect. Can anyone else confirm that this too is happening to them or have I been drinking too much Eranin pearl whiskey.

I have ticketed it but I'm not sure if the ticket was received? Usually it sends confirmation to my email but it has not.
 

CMDRBreizhbugs

C
StephenB said:
Greetings Commanders I recently upgraded from a B6 to A6 Sensor suite in my Python and have discovered abnormalities. It says it has a range of 7km but can't find targets above 6km. Not only that but it will sometimes only show targets less than 3km from my position changing pip positions to systems has no effect. Can anyone else confirm that this too is happening to them or have I been drinking too much Eranin pearl whiskey.

I have ticketed it but I'm not sure if the ticket was received? Usually it sends confirmation to my email but it has not.
Click to expand...

Happens to me sometimes... (whatever ship i drive)
Probably shieldless target that emit less heat and so are more stealthy so that you cant select them until they are close enough...
 
Last edited:

Ben Salient

B
I often get upset with my ship scanner in RES , ships appearing out of nowhere right up my tail pipes , ships that I am following at 4km suddenly vanishing from scanner completely while I can visibly see them.
losing target only for the ship to suddenly reappear & be target/lockable at the same distance / place it was previously at
..
I just put it down to a mix of the things people have mentioned above , along with clutter / asteroid interference with scanner capabilities ... I find it less stressful than screaming Glitch/Bug/Busted @ the screen:cool:
 
Last edited:

possessed

possessed
StephenB said:
Greetings Commanders I recently upgraded from a B6 to A6 Sensor suite in my Python and have discovered abnormalities. It says it has a range of 7km but can't find targets above 6km. Not only that but it will sometimes only show targets less than 3km from my position changing pip positions to systems has no effect. Can anyone else confirm that this too is happening to them or have I been drinking too much Eranin pearl whiskey.

I have ticketed it but I'm not sure if the ticket was received? Usually it sends confirmation to my email but it has not.
Click to expand...

It is not a bug, NPC or player disappearing from radar is sign they lowering heat signature of the ship.
 
Last edited:

DrakeAurum

DrakeAurum
As of v1.2, small ships such as Sidewinders were adjusted to have naturally lower heat signatures, making them better suited to smuggling. As a result, even when they're not running silent, it's not uncommon for them to be difficult to track on sensors, popping up and then going unidentified again until you get to close range.
 

fergal

fergal
possessed said:
It is not a bug, NPC or player disappearing from radar is sign they lowering heat signature of the ship.
Click to expand...

This.
Every ship produces less heat, so the range on the sensors isn't a real value.

I can pick up anacondas at res sites at 7.5km with A6 sensors on the python, but some clippers are at under 4 km, you can visually see what they are before the sensors tell you.

This might be the shieldless clippers, they would have less heat, will need to pay attention next time.
 

StephenB

StephenB
Lasse B. said:
I also seem to remember that heat output of a vessel also influences how long it appears on one's scanner.
Click to expand...

CMDRBreizhbugs said:
Happens to me sometimes... (whatever ship i drive)
Probably shieldless target that emit less heat and so are more stealthy so that you cant select them until they are close enough...
Click to expand...

I forgot about that. It could very well explain what's happening. Though I still don't understand how I have never seen a target at more than 6km, surely not all targets are saving heat? When I had my B6 sensors I never noticed any drop in range, even from shield-less ships.

I may just downgrade back to my B6 sensors, it scanned at 7km without fail which looking at it now may be a bug.

Thanks all for helping enlighten me.
 
Last edited:

Troa Barton

Troa Barton
The condas sensors are also worthless, I just upgrade them to D class if I have the power overhead. Nothing beats your eyes for locating targets.
 

xondk

X
Remember sensors rely on heat, if the ship you are trying to get a lock on has a very low heat output then it won't resolve until you get significantly closer.
 

possessed

possessed
fergal said:
This.
Every ship produces less heat, so the range on the sensors isn't a real value.

I can pick up anacondas at res sites at 7.5km with A6 sensors on the python, but some clippers are at under 4 km, you can visually see what they are before the sensors tell you.

This might be the shieldless clippers, they would have less heat, will need to pay attention next time.
Click to expand...

You do not have to teach me about mechanics in ED, soo pls...

Note: I pay attention more than you think, and I don't underestimate others in the forum...
 
Last edited:

CMDR iLikeCookiesQ

C
StephenB said:
Greetings Commanders I recently upgraded from a B6 to A6 Sensor suite in my Python and have discovered abnormalities. It says it has a range of 7km but can't find targets above 6km. Not only that but it will sometimes only show targets less than 3km from my position changing pip positions to systems has no effect. Can anyone else confirm that this too is happening to them or have I been drinking too much Eranin pearl whiskey.

I have ticketed it but I'm not sure if the ticket was received? Usually it sends confirmation to my email but it has not.
Click to expand...

in RESs the asteroids limit the detection range of your scanners.. I know for a fact that kill warrant scanners have reduced range in a RES. Maybe this also applies to sensors.
 

DrakeAurum

DrakeAurum
CMDR iLikeCookiesQ said:
in RESs the asteroids limit the detection range of your scanners.. I know for a fact that kill warrant scanners have reduced range in a RES. Maybe this also applies to sensors.
Click to expand...
I've never found KWS range reduced in a RES, and I've been using them for ages.

The one thing to look out for is that the range listing in the item description doesn't do fractions, so although the D-rated and C-rated scanner both say 3km, the D-rated one's range is actually 2.5km.
 

Alex Brentnall

Alex Brentnall
Range is rounded up so a 6.5km scanner shows in the stats as 7km for example. Many people have reported this and it is not a bug, merely an interface issue.
My testing has led me to believe that Res, nav beacon, random space has no influence on any scanner or sensor.
 

Morbad

Morbad
Not a bug and the sensors are likely working as they should.

The range listed is still affected by thermal output. An 8km range sensor can fail to detect a cold enough target at 1km or a silent running one at 600m, yet still resolve targets of low-middling heat at 8km.

CMDR iLikeCookiesQ said:
in RESs the asteroids limit the detection range of your scanners.. I know for a fact that kill warrant scanners have reduced range in a RES. Maybe this also applies to sensors.
Click to expand...

Never heard of, or encountered, this phenomena.
 
Last edited:

CMDR Stevieweevie

C
Not entirely on topic but since its just been mentioned...

What is the benefit of buying a higher grade KWS that consumes significantly more power whilst having the same range and scan time of a much cheaper one? Surely it cannot be just for a 0.X km increase or the useless integrity boost?
 
You must log in or register to reply here.
Back
Top Bottom