MBot

I am still rather confused about the left and right scale and the relationship between the Aspect and Vc switches. According to the manual, Vc should change the scale in pulse doppler search mode, but it does not seem to have any effect. The switch changes the right scale in STT though.

Might this point to a larger issue with the trapping dynamics of the Tomcat? Like others I have frequently seen bolters with the Hornet if parameters are not met exactly. With the Tomcat on the other hand I have not yet seen a single bolter unless the wires were completely missed high/long. The hook will catch a wire every single time.

Really the only solution is to wait for ED to fix the scripting engine.

Apparently the latest OpenBeta has broken some of the world events. A crash event currently doesn't log who has crashed (initiator). Hopefully this get's fixed in the next OB.

sTs8lAbA1FE YB13EFKX6fs That second video is fascinating. These are apparently some very late software modifications from 1986. A lot of the attack mode transitions shown near the end are very reminiscent of the Hornet (AUTO->CCIP transition). A difference I spot is that when an attack is made with CCIPD (=CCIP WPDSG in the Hornet) but no release is made when the solution cue hits the flight path marker, the system automatically switches to normal CCIP. Lateral toss bombing looks pretty funky :) Interestingly but not unexpectedly for the era, low level operations seems to be pretty much the center of attention.

+1 By the time we will have a working Harpoon for the Hornet, it will be highly dersirable to complement anti-ship strikes by being able to knock out individual ship radars with HARM. Right now, HARM hit ships in the center of the hull where it does little structural damage and has no effect on ship sensors.

Regardless of the detailed size of the map, I sincerely hope that the outline of the complete eastern Mediterranean coast is included in the same style as the whole Black Sea outline is included in the Caucasus map. Eastern Med and Black Sea are about the same size too, so I think this is feasible. I think this will be essential for 6th Fleet naval operations.

Yes sure.

Good catches. Both issues should be covered by some code re-writes I have done over the past months.

Things are going well. The engine updates I wanted to do are are done. The Hornet campaign is completed and in intensive play-testing for about a month now. It plays very nice and I love it :) But then I build stuff the way I do primary for my own enjoyment, so mileages may vary. There is still some polishing going on but I think a release will come soon.

Fixed with latest Open Beta, thank you.

Currently, only AWACS aircraft can provide over-the-horizon datalink targeting information to ships to launch anti-ship missiles such as Harpoon, SS-N-12 Sandbox or SS-N-19 Shipwreck. I suggest to add a separate Enroute Task that would allow any aircraft or helicopter designated so to provide such tarting information to ships. This would allow to use aircraft such as the Tu-142 Bear or S-3 Viking or helicopters such as Ka-27 to reconnoiter targets for ship-based ASM strikes. In addition I suggest to add a number of ASM-armed submerged submarines, for example: Oscar-class armed with SS-N-19 Shipwreck Los Angeles-class armed with Sub Harpoon These subs would be submerged and extremely simple to implement. No 3d model, no damage model, no weapons except the ASM, no sensors except the datalink for the ASM. Their only purpose would be to serve as undetectable launching point for ASM cued by the aircraft mentioned above. Combining these two very simple features would allow to set up a bigger variety of high-stakes intercept missions for the Tomcat, Hornet or Su-33: Shoot down the naval reconnaissance aircraft before it finds your carrier and initiates a sub-based anti-ship missile strike.

The Rapier FSA Launcher has the GT.attribute "SAM TR" (tracking radar). This is incorrect, as the Rapier launcher is only equipped with a search radar and doesn't have a tracking radar. The tracking radar for the Rapier system is the separate Blindfire unit. The "SAM TR" attribute for the Rapier launcher should be removed as this interferes with AI SEAD tasking. The configuration file in question is: CoreMods\tech\TechWeaponPack\Database\vehicles\SAM\Rapier_FSA_Launcher.lua

You are overcomplicating things. ROE Only Designate is a default behaviour, it will always be active if you don't set anything else. We don't need to search for workarounds. AI trying to attack EWR without being tasked to do so is a bug that was introduced with the last Open Beta and needs to be fixed. It is as simple as that.

This doesn't work. I checked your sample mission and it displays exactly the same problem.

As usual with custom solutions, ED has changed some things, breaking my own implementation. With 2 or 3 wingmen, AI leader will no longer climb with out-of formation wingmen even if these wingmen have their own egress tasking. The wingmen will still climb according to their own tasking but the leader will egress at 1000 m, refusing to climb without his flight in formation. Weirdly, the AI leader will climb with only one wingman though with the same setup, but not 2 or 3. So with the usual flights of 4, this means that leaders will again hang low over the target area, getting shot down frequently. Very confusing and extremely frustrating, considering one month ago everything was working great.

The presence of an EWR unit (1L13, 55G6) causes flights with air-ground tasks to ignore their ROE and constantly switching between their designated target and targeting the EWR unit. After destroying their designated target, flights will loiter around the EWR unit, initiating and braking off strafing attacks ad infinitum. This all happens despite the flights being set up to not attack targets of opportunity. It only seems to happen with an EWR unit present. I couldn't recreate it with other radar units. Please see attached mission demonstrating the setup. Thanks for checking this ASAP, as this is a mission breaker. EWR_Target_Switch.miz

Just to let you know, I am considering of dropping formal Coop support. There is an issue with communication with ATC/AWACS not working in multiplayer which I am simply unable to solve. It works when running the mission through the ME but it doesn't when running the same mission in multiplayer. My suspicion is that the problem is related to DictKeys but I cannot track it down. There are more, minor issues in MP such as static airplanes on carriers not being oriented correctly (the same mission run though the ME is ok) and problems with aircraft selection on mission start. Simply opening the mission in the ME and re-saving before launching Multiplyer solves all those problems. So if you have to go the ME for each mission anyway, you may as well set the right number of clients there. That is why I will probably disable client selection in FirstMission.bat. Regular SP is completely unaffected by all this.

From old Lock On days I remember that the units MANPADS Commander and Dog Ear radar would supply target information to other units in their group. Testing this in DCS with the getDetectedTargets() function, indeed other air defense units in a group inherit detected targets by Commander/Dog Ear. Despite this, the engagement behaviour of such air defense units does not change at all, they engage targets at the same time as if they would have detected them on their own. MANPADS Commander and Dog Ear have zero practical effect in game. I wonder if this is by design or if this is a bug that crept in at some point.

This looks fantastic, excellent job!

The thing is, I want uncontrolled aircraft on the ground to be targeted by AI. But by specifically tasked strikes with suitable weapons and tactics. I don't want the escort fighters of such strikes to go down and do strafing runs. I will probably just have to remove all gun ammo for fighter escorts. It's not a pretty solution but better than the AI committing mass suicide over airbases.

This is still a problem and a mission breaker. AI fighters with Search and Engage tasks suicidally head to airbases within their engagement distance and strafe uncontrolled aircraft on the ground*. Is this acknowledged by ED (or shall I bother to open another report in the AI bugs subsection)? It is absolutely silly to watch F-14 and F-15 throw themselves against airbases until everyone is dead. *and hitting the ground while doing so half of the time, but that is yet another AI issue...

There is something off with tasking. setTask() kills the group's default mission, causing it land at the nearest base, and popTask() crashes the game. Also is it not foreseen to be able to add tasks at the end of the queue?

This old issue persists. Not only are AI F-5E-3 and MiG-21bis look-down capable, which they should not be, they also have the incredible radar target detection range of over 150 NM! Generally, there seems to be something wrong with the AI radar model. AI aircraft seems to have identical look-down and co-alt radar performance. And for example even the MiG-29 has a look-down detection range against a small fighter (Tiger) of 90 NM. Both things I remember to have been considerably better several years ago. Did the AI radar model break and no one noticed? Also see here, bug report that is still applicable stuck in the 2.0 legacy section: https://forums.eagle.ru/showthread.php?t=198655

Lowest AI attack altitude with retarded bombs is 990 ft. This defeats the purpose of the bomb and should be a lot lower. Lowest Snake Eye attack profile in F-5E-34-1-1 is 100 ft.