Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Pages: 1 [2]

Author Topic: IR Autolance and Proximity Charge Launcher issues.  (Read 1639 times)

eert5rty7u8i9i7u6yrewqdef

  • Captain
  • ****
  • Posts: 365
    • View Profile
Re: IR Autolance and Proximity Charge Launcher issues.
« Reply #15 on: May 15, 2023, 12:58:19 PM »

@Dwarrfslayer
I can double check, but when I tested it a couple days ago auto fire without a target always chooses ships over fighters.

Okay so I can see what might be the difference in perception - because the Autolance avoids shields I am wading into a fighter screen of shielded carriers with lances zapping broadswords left and right - possibly you are getting behaviour with unshielded or shields-down ships and it's targeting a higher priority vessel?

I generally am using Autolances on an Executor just to mitigate fighter swarms, if a ship goes down shields in range it's dead usually so that would be a reason I don't see the lances focusing them for too long and they are free to zap fighter wings incoming

Tested it again. Testbed is a shrike vs sim light support condor. The shrike will shoot the Autolance at fighters, until it gets in range of the condor, at which point it will only shoot at the condor until it moves out of range again. The Autolance rarely fire's due to condor's shields being raised.

The autopilot is controlling the missile slot, and the Autolance is set to auto fire so it's not an A.I. control issue. Version is the latest, Hotfix: 0.96a-RC9.

Edit: Exact loadout is following. Expanded missile racks, ITU, expanded magazines, and IPDAI. Four burst PD lasers, IR Autolance, Typhoon Reaper Launcher. 12 Capacitors.
Changing weapon grouping does nothing.
« Last Edit: May 15, 2023, 01:19:58 PM by eert5rty7u8i9i7u6yrewqdef »
Logged

Dwarfslayer

  • Ensign
  • *
  • Posts: 26
    • View Profile
Re: IR Autolance and Proximity Charge Launcher issues.
« Reply #16 on: May 15, 2023, 03:36:55 PM »

@Dwarrfslayer
I can double check, but when I tested it a couple days ago auto fire without a target always chooses ships over fighters.

Okay so I can see what might be the difference in perception - because the Autolance avoids shields I am wading into a fighter screen of shielded carriers with lances zapping broadswords left and right - possibly you are getting behaviour with unshielded or shields-down ships and it's targeting a higher priority vessel?

I generally am using Autolances on an Executor just to mitigate fighter swarms, if a ship goes down shields in range it's dead usually so that would be a reason I don't see the lances focusing them for too long and they are free to zap fighter wings incoming

Tested it again. Testbed is a shrike vs sim light support condor. The shrike will shoot the Autolance at fighters, until it gets in range of the condor, at which point it will only shoot at the condor until it moves out of range again. The Autolance rarely fire's due to condor's shields being raised.

The autopilot is controlling the missile slot, and the Autolance is set to auto fire so it's not an A.I. control issue. Version is the latest, Hotfix: 0.96a-RC9.

Edit: Exact loadout is following. Expanded missile racks, ITU, expanded magazines, and IPDAI. Four burst PD lasers, IR Autolance, Typhoon Reaper Launcher. 12 Capacitors.
Changing weapon grouping does nothing.

Okay, then it's due to the AI targeting the carrier as all the lances will focus the targeted enemy - I'd been piloting my ship so it was just autofire but under my gentle guidance to be more effective

I do see the problem with this if you were wanting an anti-fighter screen on your escort ships in this case
Logged
Pages: 1 [2]