Greyman

I'm also a VR pilot who has recently returned after a year or so away from DCS and even though that return was initially more out of desperation, over let's say another flight sim offering, it has to be one of the best moves I've made. The performance, especially for me in VR, has been a literal eye-opener and I'd somehow forgotten how much satisfaction one can derive from blowing virtual stuff up. My first flights were with the A10C II, as I'd previously flown it and its predecessors for years, but I've more recently being enjoying the virtues, and challenges, of the Apache. Only yesterday, I discovered the Briefing Room website and although I've yet to get to fly any generated missions or campaigns, I have been having a go at generating both and it definitely looks like a winner. All in all, whether the alternative use of my PC simming time improves or not, I'm pretty well hooked on DCS again.

As I found, probably to some innocents' cost, when pressing the spacebar, in response to a mission prompt. I've since cleared the default keyboard spacebar binding, to avoid a repeat.

Point taken on staying on topic. I've asked a question in the Stolen Content download page comments, but have also done a full DCS repair and will test that out later. Thanks Edit: It looks like I might have found the fix anyway. I've updated the version of MIST that was loaded into the mission files and the issue appears to have gone away. I suspect that an update(s) of DCS, after the missions were built, has made the included version of Mist be incompatible and fixes to MIST just needed to be applied to the mission files. I'll put that one into my list of things to remember, for any future missions that might stop working.

I keep getting the one below, when flying the Stolen Content Mission #1 (daytime) :- I'd try to figure out what might be causing it, but I can't find any way to do so. It is certainly a pain, when flying in VR and probably is in 2d also, so it'd be great if someone could provide any clue as to where I might start to look for a possible solution.

Might there be another mod that I need to download or might I need to do a DCS repair, as although the daytime mission #1, that I've done so far, does seem to sort of work, I keep getting the following pop-up message? When in VR, this can be a bit of an immersion-breaker.

Perhaps associated with this, I have found that to see the heading tape, at the top of the IHADDS, I need to either raise my eyes significantly or lower my head, until it feels like I'm going to soon be looking at my RL knees. The latter solution above does still also require me to raise my eyes, relative to my head position. Alongside this, particularly when I take the first solution above, I get pretty significant flickering of the heading tape. This reminds me of the effects of the early implementations of ASW, in the Oculus Rift CV1, where it couldn't cope with the sorts of thin straight lines that appear on HUD-type displays. I am currently using a Quest 3, via Virtual Desktop, using SSW, and although that might just indicate an issue with the *SW features, the rest of the IHADSS display is rock-steady when you look at it head-on, as it were. I'll have a tinker around with the SSW settings in Virtual Desktop and see if I can correct this behaviour, but in the meantime, I can at least add my view that the IHADSS does appear to be a little on the high side. Edit: It would appear that it is looking through the IHADSS, with the spinning main rotor in the background, that is causing the flickering, so not sure whether this can be rectified? As for the high heading tape, looking down a little, when resetting the VR view, does appear to lower the IHADSS, as does "lowering one's seat" via RCtrl&RShft&numlock 2, it may be that a tweak of the VR pilot's initial position might therefore be a more friendly solution, than having to fiddle with it after starting each flight?

Thanks for that and your post was very well timed too. I'd recently tried out the Syria Map and as it is currently on sale, the stars have aligned, as it were. i've just bought Syria map and will be giving these missions a go, later this morning. Thanks again for your help.

The reservoir mission appears to have an issue with refuelling/rearming at the PARIS Farp, which is reasonably important, given the sparsity of the initial loadout. Maybe I'm missing something, like not activating an earlier trigger, but it is still frustrating when trying to find working missions that will allow for some quality practice.

I've just stumbled on this one too. I have been moving my Apache around, just in case it was being pedantic about exactly where you park, but still no joy. Given that I've just necroed this thread, over 2 years later, would tend to indicate that this is not of the greatest of priorities. Could anyone please recommend some SP missions, payware or freeware, where a newb might gain a fair range of experience in flying this beast?

Thankyou muchly for that. With him saying "armed" it did appear to be more of a human interaction mistake, on my part, than a mechanical or electrical issue, but I'd not come across that Down-short command yet, so all's good.

Can anyone think of a reason why the master arm switch might not be too keen on being returned to the safe position, as that's what I've had recently? It just stays in armed and when I try to toggle it off, with either a mouse click or the bound push button on my HOTAS, I get a voice, the CPG presumably, telling me that I'm armed. As a relative newb, it's probably something I'm doing wrong, but need help figuring out what.

Now I just need to figure out how to beat the mission. So far, I've taken out the 4-5 tanks that can be killed from before getting to W01 and the artillery that you can shoot from the BP (55), with a refuel in between. Oh and I gave the IL-76 a bit of a rough time with a full load of rockets. My flight were an absolute waste of time, as most of their missiles appeared to miss whatever it was they were aiming at. They did appear to at least be contactable however. After rearming and refuelling again, at a nearby airport which I'm not certain was the alternate I'd been told to fly to, I headed for the mountain and the EW and SAM targets. Suffice it to say, the ship at anchor had other ideas and despite showing very little interest in me when I had been taking out the nearby artillery, it gave me a real pasting with its AAA. This caused, what I could call, a "forced landing". More thought and skill needed I guess.

It looks like it was probably my finger trouble all along. I'd wrongly assumed that the 251MHz was the frequency that I'd be contacting the flight on, when in fact, a quick look at the mission file confirmed they are on 127.5MHz, which had already been programmed into the VHF channel. All I needed to do was to toggle between the two frequencies for the FARP and the Flight. I'm not sure what the 251MHz channel is for, but it is possibly used by the controller, when they provide mission status changes? I'll activate Vaicom Pro again and I suspect that will work fine also, now that I've figured out the frequencies. Thanks

Thanks for that. I fly in VR and use Vaicom Pro and although comms with ATC seems to be working fine, there might be something I'm missing on that. I'll take Vaicom out of the equation, by just using the comms menu, where PTT buttons shouldn't be an issue. So far, I've tried it when leaving all of the frequencies as they were at mission load-up and have also tried changing UHF to 251MHz and VHF to 121.5, but the other aircraft just don't appear to be hearing me. If I don't get anywhere with my troubleshooting, I'll record a very short track, perhaps just up until taking off and flying for a short while. That should show up any issues with my setup and also with the commands I'm choosing. Thanks again.

As my takeoffs can sometimes still be a little, shall we say, erratic, I've noticed that if I hinder the takeoff plans of a neighbouring member of the team, even without actual contact, he/she and their lead/wingman, will simply land and shut down their engines, taking no further part in the mission. Maybe they've just lost their dummies in the back of the aircraft, after throwing them, and can't take off without them? Seriously though, even without any takeoff mishaps, I've also had problems getting them to respond at all, to flight commands, even though I had set the UHF frequency to 251MHz and VHF to 121.5MHz? I must be doing something wrong somewhere.

I'm a bit lazy so just gently push my cyclic forward with enough collective to tip the nose down slightly and unweight the tail enough to let the tail wheel centre.

I've just been through the same troubleshooting process, having started to get this issue over the past couple of days, probably since increasing my texture resolution setting to High from Medium. I left that setting as it was and changing the codec seemed to have fixed it for me too. Looks like the AV1 codec might start to struggle with more demanding traffic, maybe.

It was AAA that got my engines, one at a time with probably 10mins in between. I didn't do any hovering, even with just one engine lost, and headed away from the target area when the second one "went pop". However, I was able to get all of the way back to base, albeit with obviously degraded performance. Perhaps I should have paid more attention to the engine display, but didn't save a track. Just looking through my settings it would appear that at some point in the past, I'd activated crash auto-recovery, so maybe that was my "problem". I've turned that off now, so will try it again. If it still happens, I'll save the track.

Well, I've just had another, perhaps more successful, attempt at the mission, although it didn't end overly well. I apparently "lost" both engines, but was still able to limp back to base, which must be over 20km away. Is there something about the damage model I'm missing, as losing both engines on an aircraft that only has two engines doesn't really sound like it should end too well? Also, I was hoping to repair, reload and rearm, before returning to the target area to finish the job, but it looks like the mission designers must have had a single visit in mind. OK, it didn't end overly well, but I've had a ball and George appeared to behave himself pretty well too.

It must be just me then. Maybe I've been away "flying" civil aircraft for too long? Yes, understanding and distinguishing between these two did cause me a little difficulty getting my head around, but I think I'm there now. Also, perhaps as in RL, adding the need to communicate effectively with another "person" can add complexity to any task. However, all of the above just adds to the fascination with being able to master this bird's systems. As for flying it, I've flown most of the other helicopters in DCS, and a fair few in other sims, and I have found this one to be really enjoyable and rewarding to fly.

That's going to be really helpful and thanks for taking the time. I'm getting there, slowly but surely, and it might just be me, but is this just a more complicated aircraft to master than those that have gone before?

It looks like it was just finger-trouble on my part, particularly in understanding whether George is actually searching or not. All of this "slaving, de-slaving" stuff was apparently too complicated for my small brain. I've just done the mission again, following the same start up process, and did manage to get the "blinkers" from George's head, as he was seeing and engaging targets. However, I still failed the mission and I'll blame the other 3 in the flight, as they appeared to be not too keen on engaging AAA, despite me "asking them" to do so, via the flight section of the menu. Suffice it to say, they left enough AAA to take out my No 1 engine, followed a few minutes later by No 2. It flew OK with just 1, but I'm afraid none was asking a bit much. Apparently, I just need to "git gud", as my son always says when I mess up on the sim.

I'd taken a bit of a, shall we say enforced, break earlier this afternoon, after first trying the mission and was just going to give it another go, when I saw this thread. I flew a different mission successfully yesterday, when George was able to spot all of the potential targets, but this one involves a cold start, so I might just be missing a vital step somewhere. I'll try again, with a "full fat" start up checklist. Maybe throwing George his spectacles is part of the start up procedure? Sorry. I couldn't resist.

I've just done the Syria "Scud hunt" mission and thought that it was probably my relative inexperience at using the AH64D that was somehow preventing George from seeing targets. As this bug has apparently now been sorted, can anyone suggest anything else that might cause George to be less than an effective CPG? He didn't even spot the three AAA that were shooting at our aircraft, so maybe Specsavers would be part of a solution?

Could it have been that of the two sets of bindings for the power levers, one for the pilot and one for the CPG, that only one of them had the inverted flag set?