Jump to content

Kit Fox And Laser Ams


6 replies to this topic

#1 SmokeGuar

    Member

  • PipPipPipPipPipPip
  • The Grizzly
  • The Grizzly
  • 450 posts

Posted 27 September 2018 - 11:15 AM

Kit Fox mounted with 2 laser ams + 1 ams.

Shows in game as 2 laser ams + 1 laser ams. That 1 laser ams is inactive and does not respond keyboard active / inactive command.

#2 Akillius

    Member

  • PipPipPipPipPipPip
  • The Corsair
  • The Corsair
  • 484 posts

Posted 27 September 2018 - 04:18 PM

Nice bug!
Hmm but makes me wonder if the Nova S Champion does the same?
Nova appears normal, 2x laser ams, 1x ams. Except it does appear to shoot down sweet f all, no sounds of firing no ammo used, toggled from active to inactive with same results impressive bug.

Edited by Max Rickson, 27 September 2018 - 04:42 PM.


#3 Akillius

    Member

  • PipPipPipPipPipPip
  • The Corsair
  • The Corsair
  • 484 posts

Posted 27 September 2018 - 04:58 PM

I'm confirming the Kitfox C bug its totally repeatable.
And works... er, its broken just as OP described.

https://prnt.sc/kzlx7k

Posted Image

#4 TinFoilHat

    Member

  • PipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 261 posts
  • LocationUK

Posted 07 October 2018 - 06:54 AM

Is it the same going the other way? (i.e. 2 normal AMS with 1 laser AMS)

#5 Akillius

    Member

  • PipPipPipPipPipPip
  • The Corsair
  • The Corsair
  • 484 posts

Posted 21 November 2018 - 10:18 AM

I didn't test TinFoilHat's idea, hopefully test later on?

Anyways I jumped in QP with Kitfox and forgot it was setup with 1x AMS with 1/2 ton ammo, and 2x LAMS
And yeah that bug is still here. :/

Posted Image

Edited by Akillius, 21 November 2018 - 10:21 AM.


#6 Akillius

    Member

  • PipPipPipPipPipPip
  • The Corsair
  • The Corsair
  • 484 posts

Posted 21 November 2018 - 04:15 PM

Kitfox with 2x ams 1 ton ammo and 1x l.ams works normally I think??
They all show as active at least.

#7 Galaxie 500

    Member

  • PipPip
  • Philanthropist
  • Philanthropist
  • 35 posts

Posted 25 November 2018 - 03:11 AM

Can confirm, same bug still present currently, tested today.





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users