Rhayvn

Here are a some that cover Blue vs. SU-27. Blue vs. Mig-29S (With AIM-120Bs) and one with the same scenario but the blue units are JF-17s with SD-10s. Notice the much better hit rate of the SD-10. Tacview-AIM120B2.zip.acmi Tacview-AIM120B1.zip.acmi Tacview-SD101.zip.acmi Tacview-SU272.zip.acmi Tacview-SU271.zip.acmi

I don't know what you -think- you fixed, but 120s are incredibly broken after the patch. Tested AI against AI and got a ~25% hit rate against Mirage 2000s, Mig-29As and SU-27s. When testing as a player against AI Mirage 2000 and Mig-29S, I managed to get the hit rate to 30% against the mirages but under 20% against the Mig-29S. Not. One. Single. Initial. Shot. Hit. Over 10 tests with player against AI. This is with a 50 mile initial setup and most engagements starting at 25-35K for both aircraft at high speed and then dropping towards the deck after defending against initial shots (First shots from both sides at 22-28 miles). This was a common engagement type pre-patch and was reliably first shot kill 50-75% of the time. The missiles are not low on energy when they get to the target. They are simply tracking poorly in terminal. Either flying a pure pursuit curve or appearing to drop track as soon as the AI does a roll while notching. This is the same experience every pilot in my group is having post patch. I setup the tests to control for other variables we were experiencing in missions and the tests proved consistent. If your goal is to have AIM-120s with about a 25% hit rate against any reasonably maneuverable target, you succeeded in admirable fashion. I am sure all the people who have extra time to use DCS over the holidays will appreciate the gift.

I know there was a thread that was closed previously. That thread is half a year old and ANY fuselage damage results in complete fuel loss at the same rapid rate no matter where or how major/minor the damage is. You stated that fuel leaks are likely when the fuselage is damaged, fine. But, having EVERY hit, no matter how minor, to the fuselage cause catastrophic, rapid, leaking from all tanks, with no way to preserve any fuel, is ridiculous. Please give us an update on this or let us know we have to live with a single 7.62 to the left side of the intake being the same end result as a direct missile hit.

Localizer works fine, but the glideslope is inactive until you cross the runway threshold.

This happens on nearly every airfield that requires back taxi on the runway after landing. That means nearly every single airfield. It renders them difficult to use for AI flights as they get stuck nearly every time after landing and the whole airport is shut down for AI takeoff and landing after that point. This should be easy to replicate as nearly every airfield on the map fist this description. If the wind is right and the landing aircraft can exit the runway before it passes the last (or only) taxiway, this doesn't happen. But that takes some work to figure out and use.

Has anyone made or located airport diagrams for the SA map? There are packs for kneeboards for all of the other maps, but I can't locate one for SA. The instrument approach charts are included, but no airport diagrams.

Could someone please describe the hood implementation? Is it similar to the C101 where the hood blocks all forward view? Or can you set it on and off during flight? Looking for a good two person training with a hood that can be set in flight, but can also be taken off to simulate breaking out of IMC.

Opened a brand new map, added the supercarrier CV with a single waypoint after the initial one, added the TACAN, ICLS, LINK4 and ACLS commands to the initial waypoint, added one client FA-18. Saved. That's it. Single CV, nothing at all else in the entire mission except the ship and the hornet.

Same result. All missions with ACLS work fine in SP, but not on a dedicated MP server. This includes a completely clean Miz file with only the CV and one client Hornet added to it.

Did you see the missiles from two of the ships detonating repeatedly at launch?

It's a short track, just a complex mission. I sent you a message with the link.

I would be happy to send the track file, but I can't get it below 9M and the limit here is 5. Is there somewhere else I can post it and give you the link?

I have been seeing, more and more frequently, that SAMs explode almost immediately after launch. This seems almost to be at random at mission start as sometimes, they work and other they have the issue. This is fairly game breaking as you can not predict when it will happen and makes any SAM related balance unpredictable. This error is present in the logs for each launch: ERROR SOUND: invalid host_params(MAIN_17098752/weapon): orientation They explode so quickly, tacview thinks they damage the launcher/launching ship:

Heya Folks, I am looking for a way (Moose/mist/ME) to enable a CV group to have two stations. By that, I mean the first station is WPs 1-6. WP 6 has a command to switch WP to WP 1. This works fine and the ship cycles through it's pattern. What I can not figure out, is if I also have a second route, with WPs 7-12, how to make the ship 1) go to WP 7 and 2) return to WP 7 when it hits WP 12. This is easy for a ground or air group, you just tie the go to waypoint command to a trigger and when that trigger is set, the group changes to it's new pattern. WP 6 can have the command to switch to WP 1 and WP 12 can have the command to switch to WP 7. Ship groups, however, can not do this. First off, they can only select a WP to go to from SP to 9. You can not use WPs 10+. Also, if you have the change WP command at more than one WP for the group, changing one, changes them all. No matter where the command is in the route, changing one to WP2, changes ALL of them to WP 2. That includes if you put them into the Triggered Actions section of the group. Changing the destination WP changes it everywhere. So, if anyone has advice on how to use Mist/Moose or other script to set a new WP for a ship group, please let me know. Thanks,

Hopefully an easy question. Once you create 10 TOO targets. The 11th is still #10 and I can't find a way to clear them or start over at #1. Can you just enter the number you want after you hit the TOO button? So, if I want it to be target 2, but when I hit TOO, 8 shows on the up front display, can I press 2 and override it? Have not had time to try that yet.

What altitude are you dropping them from? I am having issues with the bombs falling too fast when dropped around 20k feet. They seem to track ok until they exceed a speed around 500kts and then become erratic.

Is there no horn silence command? I looked for one, but hearing the horn on a long descent is beyond annoying.

Please allow us to fix it until/if you get around to it. It's well and good to say you need to fix it, but, the RAM air for example, was reported YEARS ago.

Eagle Dynamics\Custom\Mods\aircraft\F-16C\Cockpit\IndicationResources\Displays\MFD_stroke_font.svg Readability for the MFD font for those of us that have trouble reading the white text. Eagle Dynamics\Custom\Mods\aircraft\F-16C\Cockpit\Scripts.fonts.lua Eagle Dynamics\Custom\Mods\aircraft\F-16C\Cockpit\Materials.lua Eagle Dynamics\Custom\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\Common\indicator\StrokesDefs.lua Readability for the HUD, similar to the MFD, for those that have a hard time reading the default. Eagle Dynamics\Custom\Mods\aircraft\P-51D\Cockpit\Scripts\clickabledata.lua Fix for the RAM air control. In the default aircraft, you can move the control, but it does nothing.

Another example to make it more clear. These two aircraft are flying in close formation. I locked one up, then dropped the lock. Notice the one I locked and dropped, is frozen at the point I dropped the lock. The other on is constantly updated by DL. My radar is actually painting both, but the original dropped track is frozen at that dropped location.

If you lock a single target, or a second one in DTT, and lose the lock, the track is frozen on both the FCR and HSD pages. The target at 06 has been dead for over 5 minutes. The one at 18 is 20+ miles from the shown location. This is with an AWACS airborne that was showing those tracks on the HSD before I locked them. If I find the brick and relock the original target, the track updates it's location, but I get no datalink indication of where it is after the lock is lost. None. It's fozen in the lost lock location on both the FCR and HSD. Another example: The target at 32 was locked by me and then dropped. It is actually about 5 miles in front of the target at 26 at the time of the screenshot. But, the datalink is only updating the one, of the pair, that I never locked up. At this point I can turn in and re-acquire the target that was at 32 and the track will update based on my own radar lock, but never again by datalink. The only way to clear this seems to be switching from RWS to TWS or vice versa. This also only seems to happen with the last two tracks locked. Locking a third, removes the ghost of the first. This makes using the radar in a datalink environment highly problematic as not only are you not getting the right information, you are being shown out of date information. This also shows the ghosts when not using datalink at all, but I could understand that scenario as long as they eventually aged out or had a button to clear.

Seems to cause crashing with todays patch. Specifically seems to happen on shot down aircraft impact with the ground.

A few issues: There is incorrect symbology on the FCR now. A non datalink symbol is overlayed on top of the datalink symbol. This only happens in RWS SAM mode. Not in the others. Antenna elevation is not adjusted automatically. If the track goes outside of your scan zone, it will drop soft lock. This may be intentional, but it was not like that previously and is not like that for TWS or STT. 120s fired at a SAM target do not loft. The otherwise perform normally, but definitely do not loft. The same target in the exact same parameters will have the 120 loft if fired in STT or TWS. Bottom line, only partially fixed.

A few issues: There is incorrect symbology on the FCR now. A non datalink symbol is overlayed on top of the datalink symbol. This only happens in RWS SAM mode. Not in the others. Antenna elevation is not adjusted automatically. If the track goes outside of your scan zone, it will drop soft lock. This may be intentional, but it was not like that previously and is not like that for TWS or STT. 120s fired at a SAM target do not loft. The otherwise perform normally, but definitely do not loft. The same target in the exact same parameters will have the 120 loft if fired in STT or TWS. Bottom line, only partially fixed.

Happens fairly often and seemingly completely at random. Either with HPTP or without.