Talk:Sensor Profile
From PlanetsWiki
The entry on the wing sensor profile is not up to date with latest host changes: dependence on wing size and speed. Phaidros
My analysis is based on the scanning formula presented on Tim's documentation pages. However, I'm wondering if the formula is incomplete, or if the game code is buggy. The reason I wonder this is because jump gates are supposed to have a sensor profile of 500, which should be extremely easy to detect, yet they frequently come up as unknown contacts. --RogerN 00:59, 14 February 2006 (CET)
More tests confirmed that Tim's posted scanning formula does not agree with reality in the game. I have removed my analysis pending a new formula to work with. --RogerN 20:23, 14 February 2006 (CET)
This information is very good, it only miss the data for the bird version, doc state: pod, wing, base have lesser sensor profile than for other races.
Lord Lancelot 12:02, 15 February 2006 (CET)
Play the Robots for 2 years now and all I can tell is: Robot Q Tanker shows a very hugh sensor profile in the ship main screen if moving at full speed, BUT this can't be the truth. None of my Q's has ever been intercepted by any enemy race as long as it stays alone. And I have always around 2-3 per other player moving through their space with scanners on for spying. Wings seem to be invisible too, as long as they are docked to the Q.
Visibility of other ships moving with a Q seems to be reduced. The same seems to happen for new dropped minefields and for Bases a Q is in orbit of.
Q's are very good at destroying unguarded enemy Pods. Your foe gets a Pod Lost Message, but never knows who did this (and usually blames the Privateers).
Sorry - signature did not work for me - RoboDoc (15.02.06 - 20:12)
REmoved from main page, since it appear to be false
- Long Range Mine Detector It has a negative effect that it will make the ship with this device active show up as a contact for all other players in the game, regardless of range.
Lord Lancelot 00:13, 30 January 2007 (CET)
Some observations from mucking around with sensors and cloaking in the Planets 4 client:
The Sensor Profile value in the Ship overview window appears to add up the scanner emissions and cloaking device plus speed correctly and will include transporter noise to foreign objects (including ALL planets). Transports between own bases and ships don't appear to make any noise.
Cloaking bonus is applied to hull warp signature (with minimum value zero) before scanner noise is added. So a Thorn class (warp signature 40) using a cloak (-50) and low power scanners (+10) is actually visible, especially when moving around (the client reports this correctly, proven with a bit of testing).
Full cloakers will not be spotted regardless of what speed they are going at, as long as they leave their scanners passive and don't try to use their transporters on foreign objects.
So the formula being used for calculating the Sensor Profile value visible in the client appears to be this:
Basic Hull Visibility = Warp Signature Of Hull - 50 if cloaked (with a minimum value of 0).
Sensor Profile = (Basic Hull Visibility + Emissions + Foreign Transfers) * ((Speed + 80)/100) * 1000
Shard 14:38, 21 January 2008 (CET)
