ruprecht

Definitely playable in SP. Startup from the backseat, then jump in the front (press 2). George is ok for hovering and cruise, but I wouldn't trust him at lowish levels over bumpy terrain. I do all the manual flying from the front under 500' unless we're hovering in a battle position. George in the frontseat is functional but not great. No IFF and kinda frustrating in anything but simple training scenarios. Kick him to the back. In terms of an experience: MP with another human > SP CPG, george in the back > SP/MP pilot, george in the front

Thanks for confirming Wags. This is probably my #1 wishlist item for the module, along with VR performance.

Thanks bud. We have it up on the Rotors & Rust server and will let you know how it goes. Your missions are a server favourite.

Hey Grimm, I put a RotorOps mission (the Cyprus one) up on my server last night and the boys have been loving it. Only change I made was adding 6 Apache slots and we're fighting through zone 3, with a few apache wrecks littering the hills RPGs are no joke! Really feels alive, great job. Would there be a possibility to configure how many of each aircraft slot you wanted in the configurator? Again, really nice job (and you too, Mr Nobody).

True. I just manual mine to 500 and it's close enough for quick defensive work.

I was the same, but I was only aligning the circles and not putting the crosshair in them. It could be if you are only crosshairing the boresight, but not aligning the circles as well, your natural head position is close enough so it doesn't make much difference. Doing it the real-world way (crosshair aligned *and* concentric circles) seems to me to be the most accurate and accounts for all natural head positions.

Seems more useful to default to A for quick reactions, and save N or manual for more deliberate attacks. But I don't work at Boeing so...

These are people who have noticed an extreme difference in playability between the apache and other modules. They're not moaning because they have weak or badly tuned rigs. They went from X framerate in other aircraft to 0.1 - 0.25X framerate in the apache. It's a problem specifically with the apache, for some people. Take my case. I've had playable frames for years with textures high. I jump in the apache and it's a slideshow. Back to the hornet, it's fine. I change textures to medium, the apache is fine. It's a total cop-out to say "tune your rigs" to people. It's a demonstrable, reproducible issue with high textures in the apache - and *only* in the apache - on some systems. Let's say it's a GPU memory usage issue. You have a 16GB card and see no issues. Other people have a 12GB or 8GB card and see issues. Or maybe it's an issue specifically with NVidia cards. "Tune your rigs" is a pointless approach to problems like this, unless your proposed solution is everyone should upgrade to 16GB AMD cards to make up for the apache's lack of optimisation.

Textures medium completely solved it for me. It was the only change I made, and it is night and day different. Back to almost Hornet levels.

I think there's some problem with unloading memory. I bound a button to alt-tab, and every time my frames start to tank, I hit that button to alt tab out for 5-20 secs. This stabilises the FPS again for another 1-10 minutes, at least until DCS crashes (or until I crash the helo while alt-tabbed). Quest with an NVMe drive and 32GB. Performance is unchanged in the Hornet. Hecking terrible in the Apache. It's straight up broken in VR. Haven't tested (and won't) in flatscreen.

Thank you both.

Has anyone successfully used a Leonardo or Pro Micro (ATmega32u4) with the Flightpanels dcs-bios fork? The original docs suggested a ATMega328 or ATMega2560 was required. tia

Enormous help, thank you. Cursor slew is on the warthog TDC, "Man TADS" on the Cougar throttle is the Thumb Force Controller. I don't have room to actually move the cougar controls, the sticks themselves are fixed. Thank you also, this feedback was exactly what I was hoping for

Here's what I'm looking at so far for a mapping. I've activated my old HOTAS Cougar as a TEDAC in addition to my Warthog. I fly exclusively in VR, so I can't be reaching for a keyboard. No point trying to map everything 1:1 as the controls are too different. So I've generally gone for: TADS on the Cougar FCR on the Warthog Throttle Flight stuff on the Warthog stick ... with some exceptions for Hornet familiarity (e.g. location of the countermeasures in panic situations). It will very very likely change, especially on release when we see what the actual mappable functions are. Hopefully ED will continue the excellent support they've provided for switches. Hope it helps, roast me

Activates and deactivates the FCR transmitter. Two position momentary.

Hey @Surrexenjust want to say thanks, we have a group of 5 really enjoying this. Casual question, no biggie: is there a reason you haven't implemented CA artillery in the spawn menu? I'm considering adding it, but wondering if you've tried and found it broken or something. Thanks

Gorilla is NATO shorthand, I believe, for a large group of hostile aircraft. Feet Wet means currently over water, or transitioning from land airspace to oceanic airspace. Opposite of Feet Dry.

I'll try to help with a few: "no factor" Not a present threat "tapes on, armstrong" I believe this is the same as "fence in" - and references turning on the HUD tapes "5 mikes" -> I suppose it is 5 minutes yep "put your pod at lines 4 and 6" Refers to the 9-line format you've just been given by the JFAC. Line 4 and 6 is the target elevation and position. Basically, look at the target with the TGP.

Lately I've been having terrible input lag. Essentially if the VRK app is focused, it runs great. If it's in the background and DCS is focused, it's virtually unusable, and I never used to have this problem. I'm running a single kneeboard with just a notes page. Any ideas?

The mission flew normally up to the revised tasking. I released JSOW on the briefed target, and the Harriers gave me "no joy" while the missile was still airborne. Then I assigned Nicky to the 2nd target. I didn't see a release on F6 view and after that we just orbited awaiting BDA, which never came. Eventually I hit TANK fuel and RTB with no further mission comms. Nicky was still orbiting over Khasab when I was on deck (though I did get Mission Complete). Any idea what I might have done wrong?

Dare I ask how this is going?

Same with me. Played tonight, no comms until Cajun chewed me out inbound. The takeoff times on the kneeboard are really out. Especially with no comms, I just assumed we'd try to keep those times, but I ended up on a cat with a moonshadow stuck behind me, the rest of my flight still parked and had to orbit at WP1 for them to catch up. Fun times though, and loving the CAT III practice.

Have been very happy with mine, thanks @Deltaalphalima1. I am starting to notice some calibration drift, what's the right way to recalibrate? Thanks

Nice to see the Australian ships. Will donate if and when a non-exe OVGME or zip package is released. Some of my squadron mates refuse to install exe mods, so I can't use this in my missions.

It would be nice if all the shader gurus collaborated to open source their mods at a single github. That way if Kegetys or one of the others drops off the planet (heaven forbid) others can pick up their work.