Author Topic: weird: armor damage / thermal detect range  (Read 1733 times)

0 Members and 1 Guest are viewing this topic.

Offline Nibelung44 (OP)

  • Commander
  • *********
  • Posts: 302
weird: armor damage / thermal detect range
« on: October 22, 2013, 11:51:44 PM »
why I detect them with thermal at 60 m,given their thermal strength and  the value of my Goliath scanner?



Why the dents to my armor are 4-2? I thought that with a strength 6 missile, the format would be 3-2-1 (not that I complain  ;) )
 

Offline Nathan_

  • Pulsar 4x Dev
  • Commodore
  • *
  • N
  • Posts: 701
Re: weird: armor damage / thermal detect range
« Reply #1 on: October 23, 2013, 02:07:19 AM »
First off, your Goliath has a thermal sensitivity of 110, which means it can detect a 1000 signature at 110M km. those ships have a thermal signature of 960 which means they can be detected at 960/1000 * 110 = 105.6M km.

Second, armor damage for missiles penetrates on square values. in order to go 3 deep a strength 9 warhead is required, the extra damage above four thus bled to the sides rather than penetrating deeper.
 

Offline Nibelung44 (OP)

  • Commander
  • *********
  • Posts: 302
Re: weird: armor damage / thermal detect range
« Reply #2 on: October 23, 2013, 02:13:49 AM »
1. Indeed. So why they are detected at 60m ?

2. right, good point.
 

Offline Paul M

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: weird: armor damage / thermal detect range
« Reply #3 on: October 23, 2013, 02:14:32 AM »
You should detect them at roughly 100 m km.  But what I think may be going on is that you are detecting them with your longer range active array for the first time and that updates all contact information.  What is the range and resolution of your long range active sensor?  Does 59.3 m km correspond to where you should pick up those ships with it?

As for the second question the correct format for a strength 6 missile is what you see: 4-2.  You need a strength 9 missile to penetrate 3 layers of armour 5-3-1.
 

Offline Hawkeye

  • Silver Supporter
  • Vice Admiral
  • *****
  • Posts: 1059
  • Thanked: 5 times
  • Silver Supporter Silver Supporter : Support the forums with a Silver subscription
    2021 Supporter 2021 Supporter : Donate for 2021
    2022 Supporter 2022 Supporter : Donate for 2022
    2023 Supporter 2023 Supporter : Donate for 2023
Re: weird: armor damage / thermal detect range
« Reply #4 on: October 23, 2013, 09:50:38 AM »
Another possibility re. detection range would be, if you run a relatively long interval, 1 day, for example, aurora often skips a beat and stops running too late with the contact already way into your sensor coverage.
Ralph Hoenig, Germany
 

Offline Nathan_

  • Pulsar 4x Dev
  • Commodore
  • *
  • N
  • Posts: 701
Re: weird: armor damage / thermal detect range
« Reply #5 on: October 23, 2013, 12:18:35 PM »
oh didn't understand the question, that is probably an increment mess up as others have noted.
 

Offline sloanjh

  • Global Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 2805
  • Thanked: 112 times
  • 2020 Supporter 2020 Supporter : Donate for 2020
    2021 Supporter 2021 Supporter : Donate for 2021
Re: weird: armor damage / thermal detect range
« Reply #6 on: October 24, 2013, 07:42:14 AM »
Another possibility re. detection range would be, if you run a relatively long interval, 1 day, for example, aurora often skips a beat and stops running too late with the contact already way into your sensor coverage.

This is why I try to always do a save just before a spot where I expect a contact, e.g. when exploring a new system.  If this happens, I roll back to the save and re-advance time with a smaller increment.

John
 

Offline Paul M

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: weird: armor damage / thermal detect range
« Reply #7 on: October 24, 2013, 09:52:36 AM »
From the trails on the ships it is isn't a question of the time step.  The last time step was 3 minutes.  Please look in the upper right hand corner of the picture, there you see a light blue arc of a long range active sensor.  I'd judge the resolution is probably crappy given the R80 systems detection range.  The enemy ships just got picked up by that active sensor and that updates the contact information.  I recall seeing that type of contact update when the ship crossed over from thermal sensor only to active scanner dection before. 
 

Offline Nibelung44 (OP)

  • Commander
  • *********
  • Posts: 302
Re: weird: armor damage / thermal detect range
« Reply #8 on: October 25, 2013, 01:12:31 AM »
They have a mass of 9600 tons and the resolution is 80. Quite sufficient...
 

Offline Paul M

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: weird: armor damage / thermal detect range
« Reply #9 on: October 25, 2013, 02:27:14 AM »
They are a factor of 2 too far away to be picked up by your MR41-R80 system based on the Expeditionary fleet.  It has a range of 41.3 m km.  Your Faragut squadron isn't showing any active emissions and you have a ring arc on the upper right edge of the screen that looks to be an active sensor from your expeditionary fleet.  The range must be 59 m km to the enemy from the Faragut squadron so it is outside of their active sensor range for a MR41-R80 system on them even if they had it active which they don't appear to have.

You must have a low resolution long range active sensor to even be picking them up.  Because your MR41-80 sensor system can't be doing it.

The other thing is that the range to the enemy from the expeditionary fleet is much greater than 59.3 m km (close to a factor of 2*) so it is likely you just picked them up with your passive IR system.  That would also generate that message.  I assume the Goliath is on the Expeditionary fleet?

*The range to the expeditionary fleet from the picture is: 59.3 m + 41.3 m + 4 m = ~105 m km.  This agrees with the Goliath's expected detection range.
 

Offline Nibelung44 (OP)

  • Commander
  • *********
  • Posts: 302
Re: weird: armor damage / thermal detect range
« Reply #10 on: October 25, 2013, 03:00:32 AM »
Not sure I understood fully all what you said, sorry  :)

The Farragut has also a 247-R80 scanner, this is the one you see in the upper right edge. I spotted the aliens since some time with it, even if the Thermal one only picked them at 60 and not 100 or something as I expected...

But this might just be an interval problem indeed...
 

Offline alex_brunius

  • Vice Admiral
  • **********
  • Posts: 1240
  • Thanked: 153 times
Re: weird: armor damage / thermal detect range
« Reply #11 on: October 25, 2013, 05:27:50 AM »
Another option is that the aliens did not go full speed until after they detected being locked by your 247-R80 scanner.

That would have resulted in your thermals not picking them up.

I am not sure if NPRs can behave like this though, but it would explain what you observed.
 

Offline Paul M

  • Vice Admiral
  • **********
  • P
  • Posts: 1438
  • Thanked: 63 times
Re: weird: armor damage / thermal detect range
« Reply #12 on: October 25, 2013, 06:34:44 AM »
Where is the Golliath?

If it is on the Expeditionary fleet then you just now picked them up on your thermals.  That would explain why the contact is updated (the reverse of how it usually works with me).

The range you see, 59.3 m km, on the target indicator is to the Faragut.  The range to the expeditionary force on the other hand is ~105 m km and that is the correct distance for the Goliath to have picked up their thermal signature.