Kifter1983

Same for me as well, Open beta VR MT. Display is fine when not running VR (MT or non-MT) display is also fine if running VR without MT. It's only VR MT combination the TCS and latirn display is black.

I have the same issue, VDI is black when running VR MT version of the game. Tried fiddling with brightness / contrast but nothing is displayed (lantirn and TCS). I thought I had seen the problem acknowledged somewhere and that a fix was being looked into. Just found the thread:

Hi, I was trying out the wingmen/datalink tutorial for the Blackshark 3 and found a number of bugs: Asking a wingmen to navigate to a ingress point caused him to loose control and crash upon reaching the ingress point. Seems like the AI was struggling with altitude. It felt like perhaps the logic was asking him to hold his position at sea level, but was over somewhat hilly land. Asking a wingmen to navigate to an ingress point and attack a target caused him to navigate to the point, then hover a couple of meters off the water and sit there and not make an attempt to attack the target. Perhaps he was so low he lost line of sight? But then shouldn't the logic be that he attempts to slowly gain altitude until he either acquires los and engages the enemy or he rises a couple hundred meters, still can't acquire los and reports unable to attack? Asking a wingmen to attack an air defence target caused him to run right up to the target even though he has stand off missiles. If it wasn't a tutorial he would of just been shot down for sure. Surely any kind of 'air defence target' should always require stand off missile launches, and preferably if the wingman doesn't have any missile ammo remaining then call 'winchester' (or the Russian equivalent) and refuse the order. Asking a wingmen to attack a target causes him to acknowledge the order but then he just orbits me without ever attempting to attack the target. I suspect I selected the wrong target type, but if that's the case surely the logical thing to do is report 'unable' or 'no targets of that type found' not acknowledge the order, then orbit round me.

Just adding my voice to the others. I also find the IHADSS symbology is a bit too high in VR (using HP Reverb G1). It doesn't prevent me from flying... It's just a bit uncomfortable. Please allow either a config file tweak or a special settings slider adjustment to the sight height offset. Thank you!

I'm guessing you want to pass a target to your CPG? The CPG needs to have TADS as their sight, set their acquisition source as the the pilot helmet sight PHS (both can be found in the weapon MFD page) then the CPG presses the slave button on the TEDAC while the pilot is looking at the target, the TADS will swing round to point at the target, and finally with target in view, press slave again to unslave so the CPG can freely move TADS again. If the pilot wants to know what your CPG is looking at, just make sure you have your acquisition source set to either TADS or gunner helmet sight GHS. Then you can see a cross on your IHADSS of what he is looking at. It's not clear from your question if you just want to see a video feed from of what the other person is looking at on your MFD, but you can do that too. Either pilot or CPG can do that by pressing the VID button on the MFD, pick your video feed on the right buttons, then press T6 (top right MFD button) to declutter the video feed (remove all the MFD menus). Hope that helps

In LOBL George takes a minute to get setup, lase the target and only then will he fire when you grant consent. Easiest way to check if this has happened is to wait for the solid box on the IHADSS. Usually takes George about 10 - 15secs so be patient. You can get him to fire faster by switching him into LOAL mode. This will skip past his pre-setup and lase phase. I also think when in LOAL mode he'll still fire when outside of max range, 8000ft (need to double check that...). I tend to always switch George into LOAL for faster refire. Another quick tip, when a target is destroyed just hit George up to quickly select the next target if there's a few grouped in the general area. You don't need to deslave (George down) then reslave (George up) to move to the next target. That's said, if you're looking to target a new group I will then George down, George up as he seems to get tunnel vision (struggles to see new groups) if you just keep hitting up.

Hello all, does anyone know if it is possible to display target range (say on IHADSS)? I can get the range via the video MFD page but I'm wondering if there's a better way? I'm mainly playing single player and George will call out if a target isn't in range but not at what range we're at or how far we are out to get into firing range. Thanks

I think the Apache is quite demanding of the pilot. Looking at the Blackshark with coaxial rotor system, its great control input damping/stabilisation system and it's auto hover hold - the design really does a lot for the pilot and enables multi tasking for weapons release and simultaneous aircraft control. It's my opinion / feeling the Apache isn't built to that mindset, there's a dedicated pilot and a dedicated weapons officer and so there's not the need for automation to be helping the pilot out. That said when we get the altitude hold feature, I think that will help a lot of people out as I think the collective on this powerful aircraft is surprisingly twitchy and responsive. Dancing about on the collective adding load/torque, removing load/torque back an forth in large quantities it's going to introduce a lot of destabilisation and make hovering very difficult.

It's the right mouse button to uncage. Essentially the left mouse button just pulls the cage/uncage/horizon adjustment dial out, the right mouse button will turn it but not pull it in or out. To uncage just right mouse click and hold then drag the mouse down. To re-cage is a bit more tricky as you need to both pull the dial out and rotate it to lock it. To do that left click and hold then right click and hold, then drag the mouse up. It's important to left click hold, then right click hold and not just click both at the same time because if the simulation thinks you right clicked first, the left click doesn't do anything. Once the dial has rotated to a stop you can let go of the mouse buttons and the instrument will remain caged.

Just to let you guys know, there's a training mission included with the Apache that covers this and more (e.g. adding various points of interest) you might want to check it out.

Sorry, a bit off topic - just thought I'd share another tip. Have a look at this video which shows how you can setup a shift button on your hotas in DCS (no external software required) so you can double up the functionality of your other HOTAS buttons. The Apache has a lot of RL buttons, so this really helps to make the most of your HOTAS: Wags also did a great video highlighting all the important controls that should be mapped for quick access:

I also found it very helpful to de-saturate the collective axis (Thrustmaster Warthog HOTAS) as I was finding the collective very twitchy and sensitive. If you're finding that you're easily stalling the main rotor out, or hitting 130% torque and your throttle hasn't even traversed it's full mechanical range then you might consider doing this too. To do this you'll need to axis tune your collective axis in the games control settings, ensure it is a slider with the check box, now reduce the Y axis range. I used a value of 80% and found that much more comfortable. Note that this will effectively limit how much collective you can pull using your mechanical throttle axis, but I believe this is a worthwhile sacrifice for controllability as I don't think pilots IRL would be hammering the components of the helicopter by pulling extreme collective unless it was exceptional emergency circumstances.