frostycab

Don't blame me if this goes wrong, but what I used to do when I was short of drive space was to simply drag the Mods folder out of my DCS install directory and put it somewhere safe. Then I'd delete the DCS folder and install the OpenBeta version. Once it installs I'd drop the Mods folder back into it, and then try an update and/or repair, which will ensure that all your modules are up to date for the beta version. Always worked for me. EDIT: Bindings aren't shared, so you may need to re-map everything. You can backup your DCS/Config/Input folder, but I've had minimal success with that in the past as my controller ID's all seemed to change.

Just tested it. Seems to work OK for me. Test conditions: Instant Action - AH-64D Runway Start. VHF freqs default to 121 and 121.5 standby. UHF freqs default to 305 on both sides. Retuned UHF to 302 on COM page, so now have 302 and 305 set. Cyclic RTS press to select UHF. Pressed SWAP button on EUFD and frequencies swapped. Pressed cyclic RTS a few time to go back VHF. Pressed SWAP on EUFD and frequencies swapped. I repeated the test using a cold aircraft running on external power and had the same functionality. No problems with SWAP button in any configuration I ran. Might be something wrong with your installation, or perhaps (more likely) I've misunderstood the problem at hand.

On TSD or WPN page press R6 (ACQ) and then select TADS (B6 I think normally).

Given the way some people respond when *tentative* release dates are missed I don't think you'll find anyone ED rushing to even guess when that's going to happen. If it gets dropped into Stable and something breaks it'll just bring out the Troll Brigade, so I'd say sit tight and enjoy it in Beta for now.

It is accurate to the behaviour of the real aircraft, so not a bug.

At 132 knots with 82% torque that amount of forward cyclic seems perfectly normal to me. Cruising along 100 knots with less torque reduces the necessary cyclic input by quite a bit. Engaging ATT hold mode doesn't do a lot that I can see right now, but I understand it's still WIP. The Apache was never known as a particularly fast helicopter, so for now my advice would be just to slow down and take it easy.

Are you running both DCS and the Streamdeck software in administrator mode?

It's not really AH-64 specific though, is it?

100% correct. It's also worth noting that if you don't turn it on the auto-ranging for the gun will not work either, as it uses radar altitude to base its calculations on. Don't panic if nothing happens when you turn it on. It seems to take 20 seconds or so to initialise.

Tracks can be virtually useless after you've been in the air for a bit. They've always been that way for all aircraft unfortunately. People have been petitioning for an updated/improved track facility within DCS for as long as I can remember, but it's not something anyone expects to see in the near future. Are you using them for learning the aircraft itself, or for examining the overall tactical situation to see if you made good tactical decisions? If it's the latter then I'd recommend getting TacView and watching the action there.

I believe the RTS depress on the cyclic mirrors the down function on the RTS rocker, so to move up you need to use the rocker or keep hitting the RTS on the cyclic until it cycles around again. To swap with the current frequency with the stored alternate you must use the swap button on the EUFD.

Where? Have I gone blind?

I was close! It's late here

I've had this confirmed to me by Raptor9. Each time you WAS a weapon the gun it will revert to the last manual range entered, and is intentional.

Same issue for me. Will try to get a track next time when I do a shorter flight. Last one was rather long.

As Deadpoetic6 said, I suspect RAD ALT being off is the issue, as auto-ranging uses trigonometry based on the RAD ALT to calculate range.

I don't suppose anyone has done a tutorial on this softwrae, have they? I *think* I've got it talking to DCS (the mcp_CanopyOpen flag seems to change correctly inthe software when I test with the Hornet), but I don't think I understand how to get it to actually output anything to the LEDs on my CM3.

Yup. From what I understand SKR is used primarily when another unit is lasing for you. It allows you to see the point that the missile is tracking regardless of whether your own TADS is looking at it.

Have you set your ACQ to TADS?

I did think of one way of dealing with the collective, but it's a theory that may or may not work in practice: The idea is that the collective becomes "locked" wherever George has is set when you transfer back the PLT seat. It only "unlocks" once your physical collective axis moves through the point its locked at. So let's say George was holding 60% collective when you swapped seats, but you had your collective axis bottomed out. You then raise your physical collective until it matches George's, at which point you feel it start to respond in the aircraft. You can think of it as a sort of reversed center trim.

I tried an MP flight the other day and got repeated SA-15 warnings from an F-15 that was buzzing around.

I know this may sound condescending, but you are actually in a mission when you try the DCS Comms, aren't you? Silly mistake that I made when I first tried. AND You've got the correct path set in the ID Lookup page? Another silly mistake I made 2 days ago

Master volume dial?

When you exit the mission and go to the summary screen there's a button at the bottom that says something like "Save Track." Do that, and then attach it whenever you make a bug report if you can. Really helps the guys at ED see what's going on.

Don't know quite why I'm seeing lot's of duplicate posts on the forum tonight, but you should probably look at the other thread.Don't know quite why I'm seeing lot's of duplicate posts on the forum tonight, but you should probably look at the other thread.