450Devil

I recently set up some engagements of an AI Mi-24P versus human controlled AH-64D. The first engagement was an AI Mi-24P armed with AT-6 versus my human AH-64D armed with AGM-114L. What was noticeable was that (1) the AI Mi-24 detected me launching a AGM-114L and (2) it took evasive action. Also noticed was that the Mi-24P launched an AT-6 at my AH-64 and the AT-6 tracked to my aircraft despite the AI Mi-24's violent evasive maneuvers. As the AT-6 is SACLOS guided by the Mi-24's copilot/gunner, it appears that even though the MI-24 copilot/gunner would have lost sight (and therefore broke the SACLOS guidance) of my AH-64 due to the Mi-24's evasive action, the AT-6 still guided onto my aircraft. This is highly unrealistic behaviour. Second engagement was a rear aspect ambush wherein I allowed the AI Mi-24 to fly past my position and then took off and chased it down before firing my AGM-114L. As soon as I fired my AGM-114L the AI Mi-24 took evasive action. How the AI Mi-24 either knew that I was astern of it or that I had fired a AGM-114L at it is a complete mystery. The Mi-24 is equipped with the SPO-10 RWR which detects radars in the HJ Bands (Mhz). The AH-64 FCR operates in the Ghz band and so does the AGM-114L's onboard guidance radar. While I know that the Hind is still early access it appears that little is being done to have this module operate realistically.

Have found a procedural workaround. When I get into a position close to where I want to perch I go into a hover and rotate the aircraft 90 degrees to my desired line of sight and then drift right or left (as appropriate) to get to my perch and then counter rotate to the desired line of sight. Works OK but it would still be desirable to have a Drift Forward / Back command. Really loving the Kiowa. Definitely has the best AI pilot / copilot of all the modules.

Another option would be to have a voice command to elevate and depress the radar. Using Voice Attack you can set an Apache profile that has commands such as "Elevate Radar" and "Depress Radar". Although I am not normally a VR flyer, I have found Voice Attack very helpful for executing actions while keeping my hands on the cyclic and collective.

Hi Osiris66 When I use Tobii ET5 while flying the F-18 Hornet I cannot get the HMD to completely turn with my head movement. For example, if I turn my head as far as I can to the right (looking 90 degrees), the HMD display does not go any further than about 50 degrees of movement. It is not so bad in the Apache (IHADSS) but still somewhat restricted in its range of head movement. Does the HMD display in the F-18 track correctly follow your head movement when using Tobii ET5 with FacetrackNoIR? Attached screenshot gives an example of the issue with Tobii and the F-18 HMD. I do not have this issue with TrackIR as the HMD stays in the center of my vision. However, I like Tobii as it is wireless.

My bad. Many thanks Floyd.

I was on the Kola Map today and entered a waypoint into the KU. However, even though the KU showed the entry as correct, when I clicked on the Enter Key (on the KU) the waypoint's letter (MU) changed to DU. I did it twice to test and both entered waypoints changed. Track attached. DS-DCSNZA-TTI_2025_Summer_Kola_Peninsula_-_West_v2.6.2p-20250415-164544.trk

Really liking the Kiowa and its AI Pilot. Once established in a hover the ability to drift right or left (as required to unmask) is great. However, it would be an improvement if the AI Pilot could also be directed to Drift Forward / Drift Back as this would help in getting into the best position to use the MMS over intervening obstacles.

Page 24 of the Polychop Kiowa manual suggests that Button 19 of the TM Joystick be assigned to MMS Multi-Target Next Target Select. However, this assignment does not appear in the Kiowa Controls list. Has this assignment been labelled as something else in the Controls setup?

Had this happen to me yesterday when flying a SP mission. Thought it might be caused by how I had set (or failed to set) my HOTAS. I have the Power Levers bound to a rotary on my TM Throttle. For my SP mission it was a hot start so the Power Levers were already at 101 percent power. I did not adjust my Power Lever HOTAS rotary so it was physically still in the zero percent power position when I took off. As I was flying along and getting George (via Voice Attack commands) to set up the weapons, the aircraft suddenly lost all power. As I was at a low altitude I quickly pancaked into the ground. Left me wondering if the game suddenly (for some unknown reason) recognised that the Power Levers rotary on my HOTAS was still set to the zero percent power position. @unclesneep - at the time I did not consider any involvement with George but your description of the event above gives me food for thought. I will try and reproduce it and capture a track.

You might try deceasing the polling rate of your mouse as that has been indicated as a possible cause of micro stutters. This vid was posted recently

I use Tobii Eye Track 5 for headtracking. While I have little trouble rotating the Apache IHADSS or the F-18 HMD, I cannot move the Hind AI GUI more than a few degrees left or right. This makes it very difficult to fly and fight the Hind as a single player. Any suggestions for fixing this please. I have tried raising and saving the Cockpit Camera position but while this moves the GUI slightly up the screen it does not allow any more than a few degrees if left / right view rotation.

While I claim no expertise in setting up and using Tobii ET5, I do not use Opentrack. My Tobii is set to Autostart with Windows in background (attached is a screenshot of my Tobii settings).

I have the Tobii ET5. I have the same issue with the HMD seeming to be restricted in the arc it can traverse when I turn my head. I think it is a function of where the game sets the pilot head and the difference in position of the player's head. What I have found helps somewhat is to move my head forward and then turn either left or right. That seems to increase the available arc but it is not a complete solution. If you find a better solution please post it.

Yesterday a friend who tried to join me in a MP server had a similar problem. We solved it by changing his DNS to the Google DNS. This link explains how to set up the Google DNS. https://support.myownconference.com/en/article/how-to-configure-google-dns-on-windows-11-for-faster-internet-19aw0jh/

In DCS Settings do you have Motion Blur set to OFF and the Motion Blur Amount slider full left?

After the first time (above) I removed my three mods (A-4, Hercules & Blackhawk), undertook a Repair and deleted the Fxo and Metashader2 files. Last night when I was on the Syria map in the DCSNZA MP server all appeared to be graphically OK until landing at a FARP that Blue had turned neutral. Then on the external F2 view there was a huge black explosion-like artifact towards the north (screenshot attached). Going back into F1 view it was not visible at first but after swapping from F1 to F2 views it then was visible from the pilot's seat. Of note the "clouds" appear to be between the viewer (me) and the artifact. I have tested the same locations in SP but all is OK so it seems to be linked to the map when used in a MP server. I hope ED can get to the bottom of this bug and put a fix in place.

Another graphics bug - same map - same MP server - different aircraft - different airfield

Was landing at Hatay on Syria Map when I got a graphic bug - large blacked out area of the map. Screenshot attached. This was on a MP server.

The DCS Apache manual provides the following information about the display of wind speed and direction on the TSD page: Wind Status. Displays the wind speed and direction of origin as computed by the aircraft Helicopter Air Data System (HADS). If wind speed is computed as <5 knots, the Wind Status will display “CALM”. If the NR is <50% and wind speed is >45 knots, the Wind Status will display the wind speed in yellow. Also from the DCS Apache manual: NR is the main rotor RPM. I noticed today when flying the Apache in a MP server that the Wind Status was 303/14 while airborne and changed to CALM when I landed even though the server had a ground wind direction / speed of 303 degrees 14 knots. I landed into the wind since the landing area was marked by smoke showing wind direction. Knowing the wind speed and direction is very helpful prior to taking off. I wondered if the Wind Status displaying CALM when the Apache is on the ground, even though there is a ground wind, is a bug?

I suspect someone has read the F-18 NATOPS manual A1-F18AC-NFM-000 page VII-24-24 which requires OFP (Offset Aimpoint Programming) to be enter in to a precision that is "hundredths of a minute" for PRECISE Unboxed and "ten thousandths of a minute ... and hundredths of a second" for PRECISE Boxed.

Thank you Zabuzard. I have now set up a Voice Attack command for Uncage (Jester Context Command Double Click). Easier than fiddling with the weapon Selector Knob. I suspect in real life the WSO would know when to uncage (without any pilot input, given that, while the pilot is the 'captain' of the aircraft, the WSO is the 'captain' of the sortie.

From my reading of the HB F-4 Manual the pilot can command the radar to cage by pressing the cage button on the throttle. When it comes to uncaging the radar it is then up to the WSO to press the Air to Air button. It would be helpful when in single player or as a single player on a MP server, if there was a Jester Command for the pilot to direct the WSO (Jester) to uncage the radar. At the moment I am finding that I have to jump into the WSO's seat to press the Air to Air button to uncage the radar.

Further to the above, when adding or editing waypoints using the Jester wheel, as well as the LAT / LONG, it would be helpful if we could also give the new / edited waypoint a name - such as F-IN or HOLD or HB or TGT as appropriate.

I have set up a single player mission using the waypoint settings F-IN, HOLD, CAP1, CAP2, IP, TGT, F-OUT, HB and ALT. Jester's calls as I approached F-IN, CAP1 and CAP2, IP, TGT and F-OUT are very helpful. It would also be helpful if Jester gave 10 miles to, 5 miles to and at HOLD calls similar to the CAP calls and for Jester to ask how long we are going to HOLD. A five minute alert to HOLD expiring would also be very helpful. Also, when on a bomb run - particular under Direct or Dive Toss - it would be very helpful for Jester to call speed and altitude prior to bomb release. Just some observations and wishes.

Further to the above. When using Stored Heading it is taking about 3 minutes 45 seconds to achieve alignment. The HB manual states that this should only take 2 minutes 15 seconds. Perhaps this second circle is increasing the time it takes to align the INS using Stored Heading.