martinistripes

I'm using a stick without springs, so it doesn't recentre when taking my hand off and I'm using the correct trimmer option. No return spring in the pedals either. Don't get me wrong, I can fly it. But need to constantly babysit it with corrections even with the hold modes on.

I too feel that the autopilot channels are weak. Obviously no idea they are in the real aircraft but, both altitude and attitude hold are not effective enough to allow you to take your hands off the stick for more than a few seconds. George seems to hold it perfectly still when you switch seats. I also get often get sudden roll to the right when cruising at ~80 - 100 kts. Again not sure if this is normal behaviour. If these are both real behaviour then, I will learn to live with it.

Playing Liberation in Syria with the AH-64D at the moment. I'm getting JTAC messages appear with grids and laser codes and not sure what I should be doing with this information. The details appear in text top right of the screen. Am I supposed to take a written note of the information that appears? Because it's not on screen long enough, unless I was to pause the game. Also, (likely more of an Apache issue) having great difficulty in getting my CPG to locate and designate targets, even when telling him exactly where to look.

Thanks, we'll try this next time it happens. His two week trail runs out tomorrow, but he's said he's going to buy it. He's not a simmer at all, and it's the first time he's tried DCS. Say's a lot for the module.

I've been playing with a human CPG recently on custom built missions that I've kept simple to allow us learn the systems. Quite frequently (I'd say a third of our play throughs) the laser range finder stops working for no obvious reason. I've gone to my CPG's PC, checked over things myself and can't figure out why. The right bumper on his gamepad is bound to RHG Trigger (2nd detent) and the aircraft is armed. No diagonal cross is showing on the TADS and no range information. And this is regardless of firing off to an angle or directly in front of us. We basically have to exit and restart when this happens. Any suggestions on what it could be, and what else we can do to fault find?

You're right, I forgot about the AI Gunner skill option. I'm probably talking more from my experience in the training missions.

He doesn't search himself for targets yet (which I'm sure a real CPG would be doing). So in that sense, he's difficult. But like you said, when you tell him where to search he comes up with a long list of targets and seems to know exactly what they all are in a couple of seconds. In this sense, he's overpowered. I hope that we'll end up with something very realistic. Not dumb, not OP.

I know how to get George AI to look in a certain area and find targets there. How do I direct my human CPG in coop? What are the options (other than a verbal target indication)?

Thank you for continuing to work on this map; very happy about the improvements coming!

For anyone else that finds this: LCTRL+LSHIFT+TAB to open the window Click the little transmitting mast icon so that it turns green. When you press the ICS (VOIP) button now, the "I PTT" box should turn red to show you're sending on the intercom. Additionally, my CPG started with his in-cockpit master volume knob turned to minimum. So check that your volume is turned up and the in-cockpit intercom switch is set to PTT.

Thanks for the explanation.

I've tried binding a switch to ICS (VOIP) in the controls menu. However, when pressing it the rocker on the cyclic in game doesn't move. Apart from starting up the helicopter as per the tutorial, are there any other steps I need to make? Note, I'm hosting my own server (if it makes a difference). And "voice chat" is turned on in the options.

Looking at the new framerate counter, mine says GPU BOUND (theor. fps: 2000.00). Can anyone explain? Additionally, I'd planned to load into an instant action mission to test MSAA against SAA. First time I loaded in with 2 x MSAA and my fps was at 34, unusually low for me in 2D (I have laptop 3070 ti). I then exited and went to 4 x MSAA and this time my fps was at 58 (which is where I've limited it in nvidia control panel). However, after perhaps 10 secs or so at 58 fps, it then dropped back to 34 again. I then loaded in with 1.5 SAA, again my fps was 34. My first thought was my GPU is throttling but temp is at 75. Doesn't seem excessively hot to me. (I'm using MT preview by the way) Checked the CPU and that was at 93 deg. could this explain my fps drop?

If I'm using a stick with dampers and no springs, do I still need to Trim (R/Up)? Or is it negated by the fact there's no tension trying to return my stick to centre?

Interesting and informative post, thanks.

Personally, I would just like to hear what a real pilot/RIO hears with his helmet on (with nothing added or removed). For this reason, I'm not a fan of the switch sounds but I understand the motive behind making them the way they are. Likewise, when I'm on an external view, I'd like to hear anything that could be heard IRL. As simmers we have the luxury of a master volume slider if a realistic noise is too annoying for us.

If we can't get Tommy, would also be happy with Sean Young voice acting.

In the style of the F-14A Fear the Bones campaign, with Tommy Lee Jones hired to voice your CPG. Please. Reflected Simulations, you got this.

Thanks, I'll give this a go.

Is it possible to have two different system options depending on if I launch Desktop or VR? Because I'm switching back and forth quite a lot between the two. Desktop for learning systems and procedures, VR for dogfighting and the occasional carrier landing. Currently, if I was playing VR last, I have to launch DCS desktop, then put all system settings back to High, which then forces a restart. Then when I next play VR, launch in VR, change system settings to VR Preset, which again forces a restart.

I don't mean to hijack your thread, but I've also had issues with the ACLS. I've been using the Instant Action F-14A/B Case III missions in Syria, Caucasus and Mariana's. The two times I used the ACLS, the first time it flew me into the back of the carrier, and the 2nd time it didn't catch a wire. Should it work every time or is a bit of error built into the simulation. Should I use a bit of stick correction before touch down? I have break out, flaps down, hook down, gear down and DLC on.

Should there be a sound effect for the wings sweeping forward/aft? I swept them aft after the engine had spoiled down (before losing power) with the canopy open after landing. They were completely silent while moving. I realize it's not a realistic situation, but... Attention to detail and all that. EDIT: Actually, thinking on this more. I'm guessing with 'hear like helmet' on, you would probably hear nothing. But as an external view observer, I presume there'd be some noise.

The newer NXT EVO has dampers built in. I just removed my springs and tightened the dampers recently. It now stays perfectly in place when taking my hand off. For the Apache it's working well (much better than with springs); can't say for the Shark as haven't flew it for a while. If you have the original NXT, I believe VKB have an upgrade kit to turn it into an EVO. I would say it's the next best thing to having a FFB stick.

Don't know if it's related but my view control (using the MSFFB2 hat) were sticking mid dogfight, panning my view too far or not responding. I only noticed it in the Tomcat. Could be related or just old hardware playing up. Anyway, I'm happy VKB NXT EVO F-14 stick user now; very nice all-in-one solution if you travel or don't have the space for a permanent setup.

Yeah fair enough... please, be disgruntled.