feefifofum

Thanks, I'll keep an eye out for any other strangeness. Just got those guys behaving again a couple weeks ago so hopefully they'll give me a break

Thanks all, this has now been fixed internally and will push with the next update! The AI's departure pattern has changed recently, which caused them to no longer fly through the area which set off the intercept dialogue. I have also adjusted the AWACS' orbit to ensure they are able to detect the bandits. Please submit a track in a separate thread for your issue with mission 02, thanks!

I see the Flankers taking off and flying their route as programmed, which is what confused me; I confirm the same results however; no voiceovers after the rejoin despite that. I'll investigate why AWACS is not seeing them and subsequent voiceovers aren't playing ASAP. Appreciate the extra effort getting the track to me!

Got your track! Running it now, thanks. This should shed some light on things

That is a good one....it looks like he was damaged and may have actually belly landed on the top of the mountain! Since he didn't quite make it back to Russia, it never triggered the "Foxhounds bugged out" message...guess I need to add a check if their speed drops to 0 as well! Please let me know if anyone manages to encounter this again!

Hi TunedPort, I just tested the trigger that causes the jets to take off and did not experience the issue you described. If possible, should you or anyone experience the issue again could you please include a .TRK or .ACMI ? Spoilers below

Lovely, didn't realize that had been added.

Sounds like the AI have gotten a stick jammed somewhere over taking off. Thank you for the report, I'll investigate this ASAP! In the meantime, if you'd like to skip ahead in the campaign, you can find instructions for doing so in HERE

Custom sound emitters have been a long standing request...no traction yet unfortunately, though It would be a welcome edition.

Thanks for the report, I will look into this ASAP!

Thanks for the report. If possible, please include a .TRK or .ACMI file Did they crash immediately after your rendezvous, or when asked to turn towards the hostile aircraft?

This should be all fixed now, leave a post if you encounter any other issues!

Hi TI! A fix for this particular issue should be included in the next patch; in the meantime, the workaround is to reduce your closure rate to force the MiGs inside of 30NM before they fire. With recent updates to the missile models, AI are firing at a farther distance than they used to and falsely triggering the "shots fired outside of engagement range" condition.

Good news is the WH stick is the same as the F-16's, and has bindings set up by default, and the WH throttle comes pre-bound with a very respectable approximation of the 16's throttle functions. Winwing also just released their F-16 throttle (though I suspect it will be out of stock for a while) if you're a stickler for 1:1 control setups.

Bah, there must have been a change to the parking positions or hitboxes. Fixed (again) ! I've moved all ground units well clear of the F-15s so hopefully this problem won't reappear

One of these days I'll get around to rebuilding it now that we actually have a Syria map! This is a truly ancient relic from the DCS 1.2 desert mod days

Should go - c:/users/YOURUSERNAME/Saved Games/DCS.openbeta/Mods/aircraft/A-4E-C Make sure you installed the module into your saved games directory only, NOT the main installation directory.

Pay a visit at the 71st If you find yourself wanting more once you are comfortable with the basics, I run the 71st's partner squadron which is a little more realism-focused (though not so much that you'll be filing virtual paperwork.)

The mismatched sizes are unfortunately going to make that a pretty strange experience. If possible, I'd recommend identical (at a minimum, size and resolution. preferably same mfgr) displays for anything you want to use to render the actual simulator in-flight. If you're planning on using the second display to render instruments only, you shouldn't have a problem, but some setup is required either way. First, in your System options uncheck "Full Screen." Unless you are running additional software to fool windows into thinking your multiple displays are a single monitor, full screen rendering is not compatible with multiple displays. Next you must set your system resolution to the TOTAL pixel volume of all your monitors. For example, if you have three 1080P displays arranged horizontally, your TOTAL resolution is 5760x1080. If those monitors are arranged vertically (with respect to the "Display" settings in Windows) the total resolution would be 1920x3240. Next you must set the appropriate aspect ratio for the display elements you want rendering the actual simulator. Exclude any displays that are only showing avionics. Get this number by dividing your horizontal resolution by your vertical resolution. I.E. 1920x1080 = 1920/1080 = 1.77 Next, you must select a .LUA file using the "Monitors" drop down menu that will tell DCS where to render what element of the cockpit. There are a few preset options for rendering multiple displays; your best bet is to find one of these that is close to what you want (I.E. 3 screen, 1 camera + MFDs on 2nd screen etc.) and do some experimentation with placement and size. For an example of a basic 2-screen setup, with one 1080P display rendering the sim and a second display showing the two DDIs and AMPCD check my post in this thread.

Hi bkrull. Are you trying to use multiple monitors for the sim, or just your main display?

Thanks for the report! This issue has been resolved and patched in the Open Beta. You can either update your own installation now to the open beta branch following the instructions in this thread or hang tight until OB merges with stable.

The Hoggit scripting wiki should have most of your answers - https://wiki.hoggitworld.com/view/Simulator_Scripting_Engine_Documentation

Alright! I believe I have discovered the issue. As a temporary workaround, reduce your speed or increase your aspect as you approach the bandit to deny him a shot until he is inside of 30 nautical miles. I'll make the necessary adjustments to the original triggers to prevent this issue from occuring in the future, thanks for the report!

EDIT: I think I may have an idea what the problem is. Thanks for the .ACMI, I will confirm ASAP

Hi Buzz. Is it possible you told your wingman to engage the bandits? A .TRK (or .ACMI would be even better) would be helpful for debugging.