Floyd1212

You can make note of the MGRS coordinates of the target point and create a new waypoint with that information. You can use the cursor to add a new waypoint roughly in the same place as the target point by moving the cursor to the location of the target point. This is probably the quickest method I can think of. You can use a target point to set a DIR to for navigation. It wouldn't be part of the RTE specifically, but when you want to fly to that point use the DIR function, fly to it, then DIR to the next WP in your RTE again.

An updated release from a week or two ago fixed several issues. Working well for me now. So Scratchpad can now transfer the points into the TSD like The Way is doing? I'll have to give it another look, then.

I tested this last night and it didn't work as well as I was hoping. George found a few targets out in front of me (beyond 9999) and reported them in the list. I told him to Store the first target in the list and he stored a spot on the ground about 1km in front of me. After selecting that item from the list, he started lasing it and I was able to Store it again at the correct location. I don't think he is squirting the laser prior to storing when you haven't selected the item from the list yet. I'll do more testing again this evening.

I flew on a MP server last night in a Cold Start slot, and did not see this issue.

Page 74 of the (new) manual does a good job of explaining this. 8. SYM Rocker Switch. Controls the brightness level of displayed symbology on the TDU or within the CPG’s HDU. When the CPG’s selected sight is HMD, the symbology within the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the symbology brightness on the TDU will be adjusted. The symbology brightness may be incrementally adjusted using short presses, or continually adjusted using continuous presses. 9. BRT Rocker Switch. Controls the overall brightness level of the TDU or CPG’s HDU. When the CPG’s selected sight is HMD, the overall brightness level of the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the overall brightness level of the TDU will be adjusted. The brightness level may be incrementally adjusted using short presses, or continually adjusted using continuous presses. 10. CON Rocker Switch. Controls the contrast level of the TDU or CPG’s HDU. When the CPG’s selected sight is HMD, the contrast level of the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the contrast level of the TDU will be adjusted. The contrast level may be incrementally adjusted using short presses, or continually adjusted using continuous presses. 11. Asterisk Button. Resets the overall brightness and contrast levels to their default settings. When the CPG’s selected sight is HMD, the overall brightness and contrast of the CPG’s HDUwill be reset. When the CPG’s selected sight is TADS or FCR, the overall brightness and contrast of the TDU will be reset.

Yeah, if you follow the instructions provided to have the OS show all file extensions you probably would have seen "Export.lua.lua" which does not work properly. In your screenshot, you still aren't seeing the file extension for "TheWay.lua" either. Once enabled, it would look like this: This is by no means a requirement, but most Windows "power users" would have this enabled so they can better see what's going on under the hood. Glad you got that part working.

It looks like the manual you can download from the ED site is still the old version. Can ED update this to the new manual? https://www.digitalcombatsimulator.com/upload/iblock/c22/hyhtbs5kqjyjauapanut3az7bbs3p3b1/DCS_AH-64D_Quick_Start_Manual_EN.pdf In the meantime, the new manual can be found in the folder on your machine where the aircraft is installed: \Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Doc\DCS AH-64D Quick Start Manual EN.pdf

First, you need to show file extensions in your OS. Open File Explorer (open any folder). Click the View tab. Select "File name extension" so the box is checked. Filename extensions will now be visible. Now you can see that your file is actually called "Export.lua.txt". Click on the file name to edit it, and get rid of the .txt at the end.

I also like to fly with my TSD set to N-UP, so I often bring up the ASE overlay on the video feed from the TADS on the other display. This ASE overlay still presents the threats in relation to the front of the aircraft being at 12 o'clock, even when the TSD on the other screen is showing the threats relative to the ownship icon and direction of flight on the map. This way you get the best of both worlds.

Is the threat being shown at the 3 o'clock position relative to the direction your ownship is facing on the TSD? In other words, if you have the map set to N-UP and you are flying east, and there is a threat at your 3 o'clock, is it drawing the threat along the bottom edge of the TSD, to the south?

Check your radios, and check if Easy Communications is enabled in Options > Gameplay. I'm not a DCS guru, but I think this is the way it works: If Easy Comms is enabled, you should always be able to use "\" to call up the comms menu. If Easy Comms is disabled (either by you, or by the forced settings in the mission itself), you have to make sure your radios are set to the correct frequencies, and then use "RALT+\" to call up the comms menu.

You might take a look at the RotorOps mission generation tool. You can pack the zones with as much armor as you can stand, and there is even a “Defend” mode where an enemy column of armor is advancing on you, and you have to annihilate it before it overruns your defenses. Other options are the Foothold and Pretense missions. These can be difficult if you are playing them SP, as there are enemy AI CAP flights that are looking for targets to shoot down. Foothold might be a better starting point between those two. None of the above are fully “scripted” missions with “characters” talking to you over the radio, or with surprise events happening off triggers, but if it’s armor you want to shoot at, check them out.

During your startup procedure you need to flip each of the squelch switches forward, momentarily.

If you read above, it appears this is one of the fixes the author is currently working on.

Apologies. I was getting your posts and martinistripes confused. One last suggestion for your FFB situation: What if you were to let your stick fall forward after you take your hands off of it, and then tap trim again with a bind on the keyboard? Would this reposition the red X under the white diamond, or would this then update some feedback to the stick and it would simply fall forward a bit from the new position? Not knowing how the G940 works internally, is there no way to service or modify the internals to tighten up the mechanism?

Going back to look at the video, it does appear that the white diamond (your stick position) has moved off of the red X (the trim setting) slightly. After establishing the hover and engaging ATT Hold, are you continuing to move the stick, or does the stick drift off on its own? Maybe tighten down those dry clutches a bit more?

Yeah, I can't speak to that control setup. Maybe ED can chime in and say whether they have Beta Testers using a dry-clutch setup like yours. One option you might look into is using a program like Joystick Gremlin (or others) that can map your X & Y axis to a virtual joystick axis, then DCS sees the inputs on that virtual joystick. Then you could setup buttons on your controls to essentially "disconnect" your stick from the game so there are no inputs sent to DCS while ATT Hold is enabled. Then when you cancel ATT Hold, tell JG to reconnect your axis and you are back in business.

If you are not using a FFB stick, and if your controls are of sufficient quality (or maybe with a small deadzone applied to the X & Y axis for a "sloppy" stick) the hold modes should be able to hold the aircraft fine. The rolling to the right at cruising speeds does not sound normal, either. You might try loading a short track so the community can take a look and help you troubleshoot your issues.

For what it’s worth, the videos I made with examples were mostly (all?) in a MP server, but not in a multi-crew setting; I was flying to the BP and then switching to the front seat while in a hover. Also, I was at a higher elevation than my targets for most of my videos. I do think there was one situation where I was firing across a valley to targets on the other side, and they were slightly above me.

Wow, that's a lot of work; thanks for taking the time. I hope ED is taking the time to look into this as well.

I can't speak for whether this particular track is playing back properly or not (though the OP can confirm), but I will say in my experiences both firing them myself from the front seat and from using George, I have seen many Limas missing their target and hitting the ground just like this, instead of finding any of the many tanks or vehicles it had to choose from in the vicinity.

Wow, that was a very long track just to watch you fire one missile. Thank God for the time acceleration feature. It did appear that George found a target, lased it, and launched the missile, and then the missile fell short of the target. I would also be interested in feedback from ED or a SME as to why the missile was unable to hit the target, and whether in a real-world situation if it should have. One thing to note: as you are starting up the aircraft, it doesn't look like you get a good IHADSS Boresight, but this shouldn't effect the missile being able to track. You do see that when you tell George to slave to your LOS, his crosshair ends up high and to the right of your LOS.

Here is a thread with a SME discussing the tail rotor thrust after the changes made in OB ver 2.7.18.30348.

We have seen issues in past with the George UI from users running 4K resolutions... https://forum.dcs.world/topic/323995-george-menu-now-in-the-middle-of-the-screen-in-4k-resolution-location-not-scaled-properly/

Yes, this is a limitation with George as PLT. I'm not sure what we can expect from him in the future, but your best bet right now is to take control from him (while still in the front seat if you want) and get your ass out of there.