Lookiss

Hmm, I checked, but it seems that the HOTAS is not animated at all. So no way to trigger anything in the ME through HOTAS commands.... if that's the case, then it's kind of disappointing in terms of campaign building. Unless there's a different way of doing this?

Hello Does anyone know where I can find the argument numbers for the HOTAS? For the Hornet, these are in the clickabledata.lua, but not for the F-16C. I just want to use the weapon release button (or other buttons) as a trigger in the ME. The HOTAS is not mentioned at all in the file. Thanks!

Good to know, thanks. So something is off then :-)

This is still a bug unfortunately. F-14GBU.trk

I've done some more taxiing. I found that if I stay around 5-6 kn, I don't black out or damage anything. According to the manual taxiing can be done up to 15 kn though. So something it not right.

aha interesting!

I tested this several times, with empty loadout and full loadout. At first I thought the plane was just too heavy, but I get the same results with an empty loadout. Select the Overcast and Rain, put yourself on the runway, throttle up to 100rpm, accelerate, and the plane starts shaking. Next the engine gives up. This in all three overcast conditions I also tested the same conditions with zero wind, engine just gives up. It doesn't stop, but the RPM goes down. Take-off impossible. Without the rain, you can take of normally. Both tracks attached. MB-339enginestopTO-badweather.trk startbadweather.miz MB-339enginestopTO-badweatherZerowind.trk

In flight, flaps don't get stuck, although visually it doesn't make sense of course. They should get damaged at least. Or MK82's should not be loaded on the inner pylon.

At cold start, when loaded with MK82 (both dumb and snakeyes) on the inner pylon, the flaps down intersect with the rear of the bombs. When you then turn on the battery, raise the flaps and then lower them again, the flaps are stuck. Maybe MK-82's are not supposed to be loaded there? I haven't tested in flight yet... MB-339snakeeye-vs-flapsodown.trk

What works for me is 800 mils, 45 deg dive, 2000-3000ft release. I tried doing the same at 140-150 and even 200, but I was unable to get the same results. No idea if it's real-world accurate, but it does work for me.

This is still a regular occurence... I lost the front gear just taxiing out to the apron.

I didn't find any mention of this bug. If it was, my apologies. After landing and taxiing to its parking space, the canopy opens and disappears. See attached track file. (I know it's a minor bug, but I thought I'd mention it) MB-339canopygone.trk

This is actually also happening with static aircraft. It will revert back to the first livery in the list each time you load the mission, but only after you restart the game. While in the game the livery usually stays the same when reloading the mission. So it's a bit annoying when trying create a scenery with statics, but the liveries just don't match.

AI Task Set for switch to waypoint hasn't worked in a while. I only use AI Task Push for that. Wasn't this as intended or did it used to work for both Push and Set? I don't remember to be honest...

Thanks, yes, there's no other choice to go for a workaround through either a second a/c or just use radio transmissions in the triggers. silence=on doesn't seem to work for E-3 and E-2. I don't know if this is a bug or intended.

Anyone know how to silence an awacs plane, but without losing the datalink? The option silence=on doesn't work for awacs plane. I'd like to trigger custom voice overs using the E-3 on a specific frequency. Transmitting messages works, but the default awacs calls don't stop with the silent option. It does work for other planes, but apparently not for awacs. I'm not sure if this is a bug... Thanks!

Re my previous post on strange AI refueling behavior, here's a track file. I had to accelerate a lot to go through it faster. It's basically a sead mission, two hornet flights and two viper flights. When coming back they have a refuel WP. I used 2 separate tankers for each. In both cases, the F-16's remain stuck and one flight of hornets ends up flying above the KC130's wing. Attached 1 track file and the miz file. PGC_refuel test2.miz refuelAIbehaviorr2.trk

AI refueling still is kind of bugged for me. It's hard to replicate though. If I test it in various little scenarios, it works. But in the mission I'm working on, AI still gets stuck and sometimes hornets fly above the KC130's wings as if the refueling probe is above the wing... The mission was created before the update. Maybe I should delete those aircraft and re-enter them. But that sounds a bit silly... or not. Either way. Something's wrong in the state of Denmark...

I recently threw myself again in the mission editor. A few useful options to have would be these: - Bingo fuel condition for AI. Basically if AI is bingo fuel, then flag or whatever you need. - Refuel AI with an added option to link it to a specific tanker. That way you avoid having 2 AI groups chasing the same tanker while there's a second tanker nearby. - Trigger to light up the runway, useful for designers who want to use custom ATC coms instead of the default ones. - in the trigger window, grouping triggers would be a great option to have. A bit like group layers in Photoshop.

Ok so the evil looking pilot and the AI pilot with the extra face on his belly are both in stable and open beta.

Btw, this is Stable, error still present after clean up and repair track added. pilot body error.trk

Looks like the pilots seem a bit scrambled. This is for A-10A and A-10C, not A-10C II. Is this just me? This happened after the last update.

Ok thanks for that input. In the end I went for a combination of everything, but it's hard to keep track when checking and re-checking everything in the trigger table. For my next mission I'm just going to use the radio transmissions and create zones near where the transmission occurs, and flags to stop transmission. I remember reading that ED was working on "Message to group", but with a frequency option. That would be easier, since you wouldn't need to stop the transmission each time.

Sorry if this has been addressed already. I couldn't find anything searching the forum. Essentially I'd like to set several radio transmissions between me and my wingman on the UFH AM freq (or any other), to be triggered by flags or zones. From what I was able to find, I can have a radio transmission start triggered by a flag (either through a radio item F10 or "Start wait user response"). And each time stop the transmission in a next trigger, for example time since flag x. I enter multiple zones from which the transmissions are being emitted, according to the where the planes are. In theory this should work, but it's quite convoluted... I know, the easy solution would be "message to group'", but then frequency of your radio doesn't matter. I can also enter a trigger command for the unit itself and have it triggered by AI TASK PUSH. But what if I have multiple transmissions? You can't set condition flags in there. And then there's the radio transmissions you can set as advanced waypoint actions with flags. But I assume these are valid as from that WP, but what if they're triggered when you're far past that WP. Will they still work? I'd like to experiment with that, but maybe someone already has and could spare me the headache :). I have a feeling the solution will be a combination of all of the above depending on the situation in the particular phase of the mission. Any tips are welcome.

Thanks, it's what I thought as well.