Print

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

[Hamm66]

Just a little something to play with.

Download here:

http://www.mission4today.com/index.php?name=Downloads3&file=details&id=1997

or here:

https://www.mediafire.com/download/eogzznq39g1kby2/The+First+Rhubarb.7z

Pop into your TFM 412 game folder.

['MadDog']

Each time that I run this mission my wingman crashes as he moves out from his pen. I can get him to start his engine by switching to Autopilot for a second but when I order him to 'Rejoin' he messes it up. Flying all the way over the bloody Channel all alone doesn't appeal somehow. Must be I have had my fill with CloD.

['MadDog']

Hello mate

Yes I do enjoy ordering my wingman about a bit. This time he is quite insubordinate for when I order him to start his engine he simply ignores me. Only me going to Autopilot changes his mind.

We clearly want to be able to taxi around a little before lining up on the flightline ready for take-off. In a few of Monty's missions I encountered similar issues with obstacle strewn terrain in front of the starting position. May not be the same for everyone of course.

Keep working on it if you can, I am sure that Monty and all the others who build missions went through the same difficulties too.

['MadDog']

Thanks Hamm66

I will download this updated mission. I am keen to fly it but would love to get my wingman on board too. Strangely, he keeps stumm when I order him to Start Engines. I have always flown full real settings and normally when I run campaigns or missions my crew don't send me to Coventry. This geeza though just refuses to co-operate. So you sometimes have the same experience with the Autopilot trick too eh? I won't use that again, I will have a look and see what is making him deaf to my orders. Dumb insolence it is!

[Plowshare]

I think the problem may lie in that the trees spook the poor b@stard. I just moved all the stuff out of the next revetment over and moved both planes to that one - the second a/c then moves.

About the "Start Engines" command: You need to remember that, even though you only have a wingman, you need to treat it as though speaking to an entire flight.

Here's the Command path:
<Tab>/"3. Red Flight"/"Q. Technical"/"1. Start Engines"

Everything works the way it should now.

Hope this helps.

Bob

['MadDog']

Aha, the plot thickens. So I have to address the whole flight irrespective of how many we are. Good, that will suit my lot, bunch of schizophrenic malcontents!

[Plowshare]

Hamm66:

I was mistaken before about it saying "3. Red Flight" - I'm so used to flying with three or more planes in a flight and the game automatically switches from "Pair" to "Flight" when there are more than two planes. I just used the command path as I always have without looking at the text.

For some reason the "E. Technical" when you first open the command text doesn't work for anything; at least not from all the testing I've done with this. Same as hitting <Tab>/"7. Squadron"/"Q. Technical"/"1. Start Engines" is redundant because, by the time you tell the squadron to start their engines, flights 2, 3, and 4 have already started up.

Moving on:

Yes, I'm finding that doing it your way works but, if you use this path, <Tab>/"3. Pair 1 [OR "Red Flight" OR "whatever the language is"]"/ "Q. Technical"/"1. Start Engines." the path is shorter, more intuitive, and will get everyone in your flight to start their engine(s) at once whether you have two, three, or four planes in your flight.

One advantage to your way of giving the command is that you can get your wingman to start his engine while the rest of your flight waits for you to give them the command. This also means you have to remember to tell the rest to start their engines or you're left holding the bag - again.

I hope this helps.

Bob