Jump to content

Recommended Posts

Posted

It's rather strange, but if I set AI to start hot on the "ramp" of the Stennis, they refuse to taxi to the catapults with a client slot occupied on deck. If I remain as a spectator, the AI will taxi and takeoff fine. If I set them to take off from "runway," they will takeoff fine regardless of me being a spectator or filling a client spot. I have seen it affect Tomcats, Hornets, Hawkeyes, and Vikings.

 

Track files attached.

Taxi Client.trk

Taxi Spectator.trk

  • 3 weeks later...
Posted

I can confirm this.

It only happens with missions running in a multiplayer server though.

I've built a mission with client slots that have AI wingmen. When running as standalone mode there will be no problems.

When running the mission in a multiplayer server though the AI simply will not move, neither in the Stennis and neither in Kobuleti so I'd say is not a carrier specific problem.

Posted
Figures it would be an MP problem. That means it will take forever to get addressed, if at all.

 

 

yeah :)

I simply removed all AI wingmen, after all they don't contribute much.

Usually they will run out of fuel 30 seconds after calling "bingo fuel".

Otherwise they will never spot the ground units you want them to attack.

Posted

I just wanted them for immersion. Tired of doing CASE I with a static deck and static airspace, but don't really have the time to hop online with a full-time job and a UTC+9 time zone. Any time I do get on servers are totally dead.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...