Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vampire_pilot]

This is a sample mission with a player flight and second AI operated Ar-234C as V-1 carriers.

To be able to pair a V-1 with an Ar-234C, the Arado needs to be set to the V-1 carrier loadout!

There are trigger text explanations for the AI flight, so you can observe it. I added further trigger info to noteworthy waypoints of the V-1s.
Look up the mission in FMB to understand what waypoints are needed for a player and AI flight.

I suggest not using the full set of AI-waypoints for a player flight, to avoid the player launched V-1 from doing stupid things of their own or circling back to missed waypoints. You will see the difference in the FMB.

The player launched V-1 needs at least one regular waypoint, which should be placed ahead of the release location, or else it will circle back to missed waypoints. You can add more waypoints for the V-1 on it's solo path.

Take off, head out over the Channel, drop to lower level (ca. 1500m) to undock the V1

- "Bomb Bay Doors" extends the launcher
- "Undock Aircraft" releases the V-1 and retracts the launcher

Note: autopilot can not take you off.

You will receive text messages for the AI flight's upcoming undocking actions to observe them

D/L
https://www.mediafire.com/file/t807pcugl08tu1p/Ar234C_V1Carrier_v3.zip/file

[SAS~Storebror]

Might be just me but I can't get the 234 to roll faster than... 0 km/h?


Mike

[Vampire_pilot]

it's just you. I played this thing a couple of times now.

Are throttle response and RPMs there?

Note: autopilot can not take you off.

[SAS~Storebror]

Yep, all my fault.
Turns out Windows mixed up Rudder Pedals and "Switchbox" controller IDs, hence brakes got applied constantly.


Mike

[Atoka220]

My issue is

When the prompt "AI launch coming up" appears, my V1 detaches on its own
And when the AI launch is supposed to happen, it doesn't, and the ai retracts the launcher with the v1 on top before turning for home

Correction, not returning for home but starting to circle around the waypoint where it was supposed to detach

For my v1 detaching, indeed, you shouldn't even touch your first waypoint, because it didn't happen when i didn't correctly pass it but headed for the target immediately

[Vampire_pilot]

You are on to something indeed.
Not sure what though.

Okay, two things. Apparently I made rookie mistake in building the player waypoints and not testing them right. If I had I would have seen that the player V-1 has too few waypoints.

But, and that concerns me more, the two V-1 in the mission seem to influence each other which they should not. I am afraid only Mike can look into this.
There never was such a complex test mission during the development. Player and AI never had such different paths and this issue never came up.

But in the meantime I will split into two missions: one for player setup and one for AI setup. Stay tuned for a v2.

[Vampire_pilot]

Mike, the V-1s in a mission influence each other's undock behavior by waypoint triggers, even in different flights.

[SAS~Storebror]

Haha, how funny 
Will take a look on Monday.

[Dimlee]

Do those V-1s talk to each other?
Modders did you create a real A.I... The genie is out of the bottle...
 

[SAS~Storebror]

For those who want to give it a try, please download the attached file and extract it to your "#WAW3" folder.
This should cure the unintended V-1 "cross-action".


Mike

[Vampire_pilot]

I have posted a v2 of the mission and updated my notes in the OP a bit.

Together with Mike's fix, I tested the mission okay. Let's hear what you say.

[Knochenlutscher]

Absolutely insane, Alter Schwede, Old Swede,

Thanks a lot, must try