Gliptal

Whoops, this is on me.

Well I was the only one to get out alive on yesterday's flight so. :megalol:

When you're playing as the IP always tell your wingman to RTB at some point. If not, they'll try to keep formation with you during landing, and I suspect the high drag induced by the delta wing makes them crash at low speeds.

Yes the cross is in the air at the right set altitude.

I see this behaviour is back. :megalol: Just to have a 3D point to fly to rather than a 2D projection of it. It may or may not become more important later.

Was about to suggest that.

Yeah that's what threw me off. 100th of a seconds aren't a common unit.

Latest 1.5.5 version crashes with this mod enabled.

What's the units for intervals and such? Milliseconds?

Nice catch. The coordinates might be simply wrong, they should point to the shooting going on below you. The mission was mostly tested when the INS was still non-functional, so nobody thought of punching those coords in and cheching they pointed at the right place. It may also have been a typo in the script. EDIT: Heh, sniped.

Yes, it just makes it easier to manage mods. There's no way to keep a DCS file untouched during updates.

Yes the METARS might be slightly off. Most of the DCS auto-briefing's units are also in meters (for some reason). "299/04" is the wind (299° for 4 knots).

Seems like the startup bug affecting 1.5.5: try and request the ingame ATC the permission to startup as quickly as possible.

Good!

In the debriefing screen, it's either under Score or another label.

Never heard of such a limitation, but I can't check right now. What do you mean by inactive?

Answered in the bug thread: https://forums.eagle.ru/showthread.php?p=2972826#post2972826

That's odd, I can't see anything wrong. I've checked and we've never seen this problem during testing either. Would you mind reflying it, to see if it happens again? Might be an heisenbug.

You'll see in his next full mission video ATIS is not the only ATC entity you'll have to work with.

Nice work.

Use JSGME or OVGME.

What's that sexy GUI I see there.

Glad you got it sorted! Unfortunately the mission editor is a bit limited when it comes to trigger zones and such. Maybe BD could enlarge it a bit to give more leeway. The problem is that these types of bugs are mostly out of control of the mission designer. You can come up with workarounds and such, but with the current fast ED development cycle you never know when something unexpected will break your carefully planned interactions.

Colt is on CH3 of the Main (Green) radio. Climb at 16000 feet, reach WP 2, and look for Colt (they should be contrailing in and out of the clouds). Get close to them and an F-10 option should pop-up. Excellent. The first issue is definitely related to 1.5.5, see https://forums.eagle.ru/showthread.php?t=176957 The second issue is a retread of an old taxiing eisenbug that was thought to be solved but apparently is back. As a workaround, keep quite the spacing with your IP.

I'm really sorry you're having all these problems. When testing I always slowed down to about 100 knots with aerobraking and let the front wheel touch the tarmac before taking off. I then climbed to the pattern altitude and made a 180° turn so that I overflew the small village. Unfortunately I have no access to my gaming rig until tomorrow, so I can't test the mission myself nor give you an acmi file to take a look at. Spacing is fine. I remember this bug, and we definitely had it removed before 1.5.5 came in. How much time are you taking at startup? Are you skipping it with the F-10 menu or doing it all every time?