LooseSeal

Definitely a decent order you've got there I've just ordered a Virpil throttle and Constellation - an upgrade from a Warthog setup. I think that will be more than enough for me, along with my MFG Crosswinds. So... what are you planning on connecting the collective grip to? I'm not that familiar with Winwing, but I imagine you need a base too? Also not sure why you need the Black Shark grip if, as you say, you're going to use the F-18 throttle as a collective. So maybe get rid of the collective grip? The only thing I would say is you're (in my opinion) outweighing the necessity of a throttle/collective with regards to the pedals - the pedals are much more important for helicopters. If I were you I'd keep your current throttle for a while and get a decent set of pedals instead, then when you can afford it get a throttle or collective.

Forgot about Rad Alt! That would be it. For the OP - it's located on the FLT -> SET page.

There isn't a "ground stabilise" in the Apache, as such, at least not yet. If you are the CPG and using the TADS to aim the gun, then you can use the LMC to somewhat stabilise the sight, while using the laser for correct ranging. If you are using the HMD to aim the gun, as either the CPG or pilot, then - either set the Man Range setting on the WPN page to auto (Box Man Range, then enter 'A' on the keyboard unit, then press enter - this will reset each time you select another weapon) or set the Man Range distance yourself. Auto is obviously more convenient, but works better on flatter ground.

Strange. I have no issues with this. Can't see that anyone else has either. I just quickly did both a cold start and hot start to check - no problems changing to automatic using the same process you described. I'm not sure what the issue is, but I don't think it's a bug introduced in the update. Maybe run a repair just in case?

First of all - are you the pilot and using George in this scenario? Or are you the CPG? It's not really clear.

Oddly enough, I've been following GPU prices for a while - and in the last couple of weeks the first glimmers of hope have emerged. Quite a few predictions of prices returning to some sense of normality this year. I have a 1080 and desperately waiting for the 3080 to come down a bit. Anyway, that's my contribution to the thread, haha - don't lose hope just yet!

Change one of your MPD's to the TADS view through the VID page. And you'll see the metres near the bottom when CPG is lasing, same as you would in the front seat.

Has anyone else ever got a "Mission script error" when loading up the next mission? Specifically, it says [string "..."]:15: '}' expected near 'lah' - you can play through the mission, but the results aren't detected and the state.json file isn't updated. I've replaced the MissionScripting file, but it isn't working. Ran a DCS repair then replaced it again. Still nothing. Kinda run out of ideas.

I'm fairly sure the Syria map has issues with charts appearing below a certain zoom level. Zoom out a bit and see if it appears. Also, seems obvious but are you waiting long enough for the map to appear? It won't appear until the system is aligned, or thereabouts.

So: master volume is up, the squelch switches are all down, electrical power is applied - but there is no static? And, when squelch switches are up, you can't use the radio to transmit? It seems strange. The best thing to do would be make a quick cold start mission in the ME, demonstrate the problem, exit the mission, then save the track and upload it here so we can see what's going wrong. Otherwise, it's quite hard to tell.

I don't know if I completely follow the issue. If you have no "squelch sounds" then you probably haven't turned up the master volume. Edit: See your last answer. What exactly is the issue? You hear the static noise from the squelch but cannot transmit via radio? Or you cannot hear the static?

What I meant was, in the screenshot, your HMD indicates that you don't have missiles selected. In the bottom right it says which weapon you have selected. That would be why the constraints box isn't showing there. But anyway, it shouldn't really stop George firing as he has them selected. I think it's because he's extremely sensitive to LOS issues at the moment. I just flew the Kodori Gambit mission and he wouldn't fire at an APC because its rear half was behind a barrier - I moved, then he fired.

I've been doing this one again - no cardiac arrest again, thankfully. But other issues - the convoy (as has been stated) moves to Pershing without me, but when it arrives one of the Humvees just drives around in circles - so that might be preventing more triggers? I got a message about being under attack by a mortar team in the valley, I went to check it out - nothing there. The mortar team eventually showed up about 15 minutes later. Anyway, thanks for having a look at it - I'm sure it'll be a good mission once the kinks are worked out!

That video from Casmo sorted out all my issues with rockets - it really is secretly easy. Line up the I beam with the crosshairs and you're basically winning. I have more success with rockets in the Apache than any other helo module.

I think this is because the OP hasn't WAS'd Hellfires on his side, so he doesn't see the constraints box. Not sure if that should cause the CPG not to engage though.

Surely you should only be unlocking it for corners, then re-locking when going straight? Personally not having that much trouble with it unlocked for taxiing round corners, just needs practice. If you think you need subtle pedal movements for hovering, for taxiing you should take those subtle movements and divide them by 10. I would honestly say you're either doing something wrong or there's something amiss with your bindings/controls. It shouldn't be behaving like that. I'm not convinced there should be much friction/weight on it. Anyone who's used a WWII aircraft knows just how light and squirrely a tailwheel can be. The majority of an Apache's weight is probably centred towards the front of the aircraft. As soon as collective is increased, the first part of the aircraft to lift off the ground is the tailwheel, so it makes sense to me that isn't much of a weight sensation there.

There may be a bug, because I did a mission recently in the Persian Gulf and the KU always started with the 31NAA... MGRS coordinates, which definitely wasn't where the aircraft currently was.

Huh. I'll probably just skip the mission then. Honestly, a bit disappointed with the missions they've put out with the module. It feels like nobody gave them a quick playthrough to see all was ok. No convoy in this one, no FARP in the Reservoir mission and issues with coordinates in the Scud mission. Yet my log says there was no MANPAD or anything. He just died. For no reason. It's really weird!

There I was, flying along to the 3rd waypoint when I heard a small "ugh" and the screen went black. All I can imagine is he's had a heart attack, or an aneurism? Never had that kind of unexplained sudden death happen to me before in DCS. Now, I did abandon my wingman at the base because he decided he wanted to spend 15 minutes taxiing down a long runway then taxiing right back up it again. Is it because I got too far away from him? Anyone else done this mission?

RedKite has done a decent video on the topic here, if anyone wants a bit more clarification on things through the medium of RedKite's dulcet tones.

There was very long thread on here over the last year about how often radar-guided Hellfires had been fired in anger using the Apache. No idea where it is now, but I think the overwhelming evidence pointed to only laser-guided really being used in conflicts. I honestly feel like there's an almost unspoken, mythical sort of 'oooh, shiny' idea attached to something being radar-guided. So, for whatever reason, we immediately assume it must be really useful. Like how we were all looking forward to getting A/G radar for the Hornet, and then I personally found it absolutely useless and would much rather just use a targeting pod. Looking at how British Apaches were used in Afghanistan, you get the idea that they used the FCR to get a better picture of threats in the area, but actually engaged them using laser-guided Hellfires.

Yes! I couldn't stress this enough. Turning off that indicator was one of the best things I did. It allows you more to 'feel' where the trim is rather than constantly checking to see where your stick is positioned. It's very distracting.

You think they should have delayed it because some people don't understand how to use trim? I think I must be missing something. We are missing the altitude hold function, and that's it. If people are struggling to hover, the addition of altitude hold isn't going to make a huge difference. After all, switching on Att and Alt hold is not the equivalent of autohover. You still need to fly the thing. This is why there are two crew members! I honestly don't understand where the "inordinate" amount of effort to hover is coming from.

Ah thank god, that's great news. I was under the impression it would be the same as Petrovich. Happy to know I was wrong!

Only when you tell him to look, unfortunately. I think there could be a better and more realistic system, personally, as the CP/G surely should have some agency in the matter. I've said it before - there should be a probability-based concept where George starts to identify targets within a certain range based on factors such as lighting, unit size, tree coverage, terrain, etc etc. Yet I can't see ED doing that for a long time.