GrEaSeLiTeNiN

RMAP is here!

9 Aug update DCS: AH-64D by Eagle Dynamics Added RMAP Mode. Please see. Fixed: AG radar contacts are not shown on TEDAC and HMCS displays in C-Scope mode. Fixed: Datalink does not work if Cold Start is performed. Fixed: FCR Near bar, Far bar, and Elevation control corrections. Fixed: Image Auto Track (IAT) errors. Fixed: TADS optics mode indication is missing. Fixed: NTS and ANTS targets are being designated before the first FCR scan is complete. Fixed: Datalink acknowledgements not processed if DL protocols are not enabled on VHF radio. Fixed: Gun not firing if CPG sight is HMD and range source is laser. Fixed: RFHO selection menu not closing. RMAP!

Seems they forgot to add "T" to the binding under keyboard in the controls setup for both pilot and CPG. So if you press "T" on your keyboard to do a Force Trim, nothing will happen. But if you bind it to your stick, it will work. Or, simply add "T" in the box where its missing in the keyboard column (controls setup) - double click that box and key in "T".

Most modules do not have their key binds messed up after an update. So far for me, I think the Gazelle had the most key bind losses. Don’t overthink it. It’s not that bad unless you are changing PCs or setting up a new hotas. I have a hotas mapping diagram made in MS Word for every module I set up. So I can refer to the layout if I need to remap some missing bindings or if I need to refresh my memory between flying the many different modules. I don’t recheck the bindings for every module I own after an update. I just fly the module I want and if something doesn’t work I check and rebind.

Yeah the FCR is great esp with LINK to bypass those Xs (already destroyed targets). I hope the bugged C-Scope symbols get fixed too.

They are all in C:\Users\User\Saved Games\DCS.openbeta\Config\Input including the modifiers.lua You can make a backup copy of the Input folder. But I'm not sure a copy and paste into a new PC or new DCS install will work. You might need to reload them at the Controls setup for each module. Yeah it can be a hassle. But at least they are not lost in that sense. One QOL ED could have worked on (instead of less important things like the launcher) is the ability to save our profiles online into our ED account for syncing. My entire Input folder is only 583KB and I have quite a lot of modules.

The Master Arm On/Off toggle switch can only be mapped under CPG. But it will work for Pilot as well. If you map it under Pilot, the toggle will not work as the switch will be stuck in one position.

Ok, thanks very much for looking into this!

Did some auto pilot (CVS/ALV) testing today after being away from the Gazelle for some time. Seems to me... Auto hover (CVS green) is working but collective inputs can cause some jerking. Need to trim into a stable hover first. The ADI needles in doppler mode and the tablet's GS help provide the visual cues for hovering. Auto slave (ALV green) heading align is working (CVS must be on and green). But when turning on ALV from an off state, the yaw to align with the TV crosshairs is sudden and jerky. Once ALV is on, the yaw to follow the crosshairs is smoother. A stable hover with little to no initial yaw helps. Is the jerking in both cases realistic? Maybe PC could smoothen it out a little.

Hot starts or air starts still have the Starter switch in OFF position when it should be in the ON position. As discussed here.

Ehh.. sorry but how do I use the new script? Where do I place the lua file? Thanks

I’ll have to try without Olympus but as a solo player, I don’t know how to put units in the zone to capture it. I looked at the F10 menu but there does not seem to be an option for those kinds of actions. What is strange is that the FARP vehicles appear after capture (with Olympus) but without any helos. I think that’s why picking a slot from that FARP can’t work whether during the mission or when starting a new mission.

Well, I did use Olympus to capture the zone by spawning blue units in it once all red hostiles were eliminated. The blue units spawned by Olympus disappear in the next mission leaving only the blue units created by Expansion's scripts such as the FARP trucks and the Roland SAM, but no aircraft is present. Even the aircraft spawned by Olympus is prohibited from being flown by the player. It's like there is a blanket prohibition from flying any aircraft that is not from Nalchik.

Solo play issue: After a zone is captured and turned blue, the FARP appears with trucks but no aircraft. Consequently, I could not enter any aircraft in the slot I picked for that zone. Message says "currently blocked and can't be entered" even though the zone is blue. Also cannot enter any aircraft spawned via Olympus.

Look for MMS line of sight up/down/left/right (or vertical/horizontal if using axis) and MMS FOV under CPG and map it for the CPG. They will work for when you are Pilot as well if you keep that switch or HAT that you map those commands to unbound in the pilot's hotas setup.

We are their 2nd QA layer... lol Came across this old post on users' bug reporting frustrations. Nothing new.

Yeah, same observation here. I was wondering what was going on with the C-scope symbols. Fix one, break another, seems to happen often these days and they don't get fixed for quite a while. If they could just hotfix the easy ones and drop them in as small updates as and when ready, that would be nice. Long waits for huge updates that tend to break other things is getting frustrating.

I think it helps if you have a stick extension too. I have a standard warthog on a table so the Cayuse required some getting use to at first.

+1 pls fix

I hope someone does a mod as an option to replace the robot voice. Not realistic but ....

Bump - not fixed

No FIM-92s but had some luck with APKWS.

TIS in daytime is helpful too when adjusted right. Without it, it can be hard to locate targets in the MMS esp in built up or forested areas.

Well actually, at the 8:08 mark, his AP "goes completely mad". This AP problem has not been fixed for more than 6 months already.