nighteyes2017

I am currenty building a mission and have the same settings. Evade off, Status Red. I cannot get the SA15's to engage the harms. So whats the difference? I am trying to get the SA15's to defend the SA2 next to it. But every time the only start to launch about 1 second before the harm impacts the SA2. Too late. They used to be much more aggresive. I now am unable to get any sam to engage the harm. Maybe the new harm profile is now too good?

I heard that eventually, the new tgp will replace the old one, and that the old one will be removed from the game. If so, how would this affect existing mission files? Will the new one be automatically placed instead of the old one in mission files? cause that would be great!

It still doesn't make sense to me to just use a tv mode in the center which has the same level of zoom (absolute zoom, i'm not talking about the fact that the tv zoom has to zoom further than the ir to get the same picture). Not just in the TGP and flightsims, but as a general rule, PIP's are used to give a more zoomed in detail of a larger view. Think electronic microscopes for a second for example. The pip's on those monitors show a higher level of zoom than the general area the camera is aiming at and not just a crisper image. I get that the quality of the image is better in tv mode (what about at night?) but the zoom level itself in my opinion should also be higher. I cannot fathom that any airforce would miss something like that. I can even imagine that one could simple set the level of zoom of the pip itself. With the old TGP, i normally would set a zoom level where i can distinguish potential targets as small dots, and then inspect those dots using the FOV button, and if it is not a target, i zoom out again and scan further using that general level. Thus inspecting each potential dot. With the PIP, i would have expected this to be able to do in 1 pass. With the higher zoom in the PIP. So it is not intended to work like this? I would call that i missed chance. Unfortunately i don't have any documents or sources to show any of this, i am just very much wondering and speculating about the functionality and usefulness of the PIP here. If it just works like this in real life, fine. If we wanna do it as real as possible, no arguments there. It just that it seems a waste of potential functionality.

So from my previous bug report and the answer on it, i understand that the tv is actually at a higher zoom. but with the surrounding IR picture is basically means the same detail level. So whats the point??? I mean, i get it if the PIP show a higher zoom than the surrounding area. Isn't the idea then that you can use the surrounding area to see where your target pod is looking in the big picture, and then see more detail at the PIP? that would be a good workflow and i'm guessing here, but i think that would be the point. But if the PIP just shows the same picture, but just in TV mode, what is the use? I therefore think that the level of detail in the PIP should be higher than the surrounding area???

according to waggs' youtube explanation (part 1, 6m22s in). the PIP in the new tgp should have a higher magnification. but as you can see, it isn't

yeah, i'll try to make an extraction from different situations on the acmis, and pile them together.

From what i have seen the last five missions i have flown, this is still an issue. The ai is able to dodge aim120's by barrel rolling. The acmi's from those missions clearly shows multiple ai thrashing multiple missiles by rolling. Is this still on ED's radar?

Many thx!. So based on that, it sounds like the better option for that action would be to have it always turned on by default, and have to option to turn it off. Guess ill update my templates to turn this option on.

yeah i saw that, but that is not much information. That just calls for more questions than it answers. Like 'when does the AI avoid combat engagements?' This action was written for a reason. What is that reason? So far i have not encountered a situation where this action could have helped me out. How do i use this action exactly?

I understand that, but the general consensus is number two on the left. And even if you can do right and left hand, then you should make that an option like they did with echelon right en left.

Used the formation option on a group of 4 AI F16's. Set finger four formation. Seems its in reverse.

So what does this setting actually do in the mission editor?

Could we have the same ruler in de mission editor as in the mission itself using the F10 map? I mean, in the mission, the F10 map ruler shows true and magnetic heading at the same time, but not in the editor. Also, the compass rose is available in the mission, but not in the editor.

Some very weird AI behaviour only in multiplayer: The mission: Put 1 flight of 2 F16's on the ramp, cold start, set as clients Put 1 flight of 2 F16's on the ramp, AI cold start, set flag as uncontrolled. It happens only client side in multiplayer. After 60 to 80 seconds, the uncontrolled AI flight lead start gently rock left right around the Z axis while parked, then becomes faster and faster. The host does not see this, only the client. If multiple AI flights are on the ramp as uncontrolled, all the flight leads start rocking. Tested with several different hosts, and several different clients. Test with both AI and clients as F16 and F18's. Happened also, so probably not module related. If you let it continue for a while, it crashes the client. Mission file included. Client Track file included. EDIT: changed AI to A10II's. And then it does not happen. So maybe still related to F16/F18 ! spin test-20250112-140305.trk spin test.miz

For some unknown reason. The missions, wich have not been altered, now suddenly work again. I really didnt change a thing. Now however, the AI will not shoot sooner than 27nm. No matter wich aircraft or missile, AI shoots at 27nm. So a Mig31, loaded with R33 (54nm) coming in at mach 1.2 at 40000, set to max range launch, still will not shoot until 27nm. Each red aircraft, with either a R33 or a R27ER (37nm), no matter the settings, will not shoot before 27nm. Seriously, ED needs to look at AI BVR behaviour. A couple of updates ago this was a big improvement thingy. However its not working anymore.