Lookiss

And here's a second track. This time using the Pavespike. I failed to drop and Jester just keep giving speed cues. Jesterkeepsgoing2.trk

Hello After releasing the bombs in loft mode, Jester just keeps giving speed updates. He just doesn't stop. Even after telling him to switch to the next waypoint, he's stuck there somehow. See attached trackfile Jesterkeepsgoing.trk

yup, same here, FC3 disabled and installing it doesn't work

I'm not sure if this is a bug or as intended. When you start the INS alignment, wait for RDY to appear in the DED. Then hit the wheel brakes and throttle up to about 80 or more, throttle down, the RDY disappears and the alignment stops. Maybe you're supposed to do the SEC test and the EPU test before starting the INS alignment. If so, it's not mentioned in the manual. See attached two tracks. INS align lost.trk INS align lost2.trk

I noticed similar behaviour for the AI F-15E S4+. It will only drop JDAMS, but no laser guided bombs. It does work with the older F-15E AI. GBU-54 are not dropped either by the newer AI F-15E S4+. F-15 S4 GBU-12 nodrop.trk F-15 S4 GBU-38 OKdrop.trk F-15 S4 GBU-54 nodrop.trk

Thanks, that explains it. Easy to work around for now.

I came across this bug when creating a night mission, starting at 02.00, on the Persian Gulf map. At 02.00, system time 22.00, go to CRUS page and you see 05.00 as ETA Same, but starting at 10.00, Zulu 06.00, go to CRUS and you see 06.00, so that matches. Maybe it's related to night time, maybe it's related to the map and time? See track files for both cases ETA match_10.00.trk ETA nomatch_02.00night.trk

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...