Lord Vader

I tried the Start Up tutorial and it never asked me to operate the ramp from the aft position. Are your referring to the Internal Cargo tutorial? Even in that position, I have the mouse cursor enable, if I need to move the POV, I press the mouse middle button or LALT+C and it toggles between cursor and POV moving the mouse. Even in that tutorial, the command to open the ramp is via the key combination from the cockpit, no controls are requires when in the aft position. The suggestion to move there is just to observe the ramp opening and monitor the cargo loading. Currently there is no interaction with the ramp controls from that position either, the only thing you can control is the radio panel (right side, mid fuselage). Do you have any mods installed? Have you tried a repair?

Glad you sorted this out. As for the sun visor effect, it's been noted by the team. I can't say if or when it may come.

Not a problem, @Augermc. Don't hesitate to reach us if you require further help.

Check the left console panel for AUDIO1, you will have two knobs with the labels OFF (turns off squelching), SQL (default position, squelch on) and GD (to monitor the guard frequency) for both Comm 1 and Comm 2 radios.

@Captain Orso Up, Down, Left and Right correspond to the control directions on for multiple position switches in most, if not all, controllers in the market. Even though the motions to move forward or aft are more accurate, I think it's common sense to know "Up" is forward and "Down" is aft. I will present this to the team, nevertheless. Also, please tell us where does it states this: I have not found a "Vor and Aft" reference, at least for "Vor" in our Early Access Manual for the DCS: AH-64D. Was this a typo? Were you trying to say "Forward and Aft"?

Hey @Augermc This can happen when there's a high concentration of targets. Basically George will list all targets he sees according to his own priority, giving you the option to choose an item on that list. It's hard to see what you're trying to aim at, but in the list he's listing a SAM site, so I would say he's just prioritizing the threats he sees. If you continue to think this isn't working correctly, please send us a track file of the situation and we'll have a look.

Hey @Trespasser We tried this and a long DMS aft press indeed removed and reactivated the symbology. Please check your HOTAS settings or button assignments to confirm you're doing the right procedure.

@Hiob The receivers responsible for TACAN and ILS (AUDIO2) are indeed capable of squelching automatically. @razo+ryou can only manually turn off squelching for Comm1 and Comm2 audio.

Hello @Locutos Are you using the right comm menus for ICS (RShift+Space) or Radio (Ralt+\)?

Hey @IanC58 The current logics for troop transportation are a work in progress. It currently may not work correctly as we are still developing this. Thanks for understanding.

Hi @Freakmeister51 I have the mouse cursor pressing the mouse middle button or Alt+C. Don't you?

Hi @LuseKofte There have been some reports of flighplan issues frozen after messing with the EGI. This is something we're working on currently.

Hi @FusRoPotato We appreciate personal opinions, especially when they are based on real life experience, of course. However, with the issue above, as well as with the track that was tested with the team, it was concluded that no fix is required for the conditions demonstrated. If you have any evidence to present showing the situation above is not accurate, feel free to PM that evidence (making sure it's publicly available non-classified data) to @BIGNEWYand we'll certainly look into it.

Just to clarify everyone, in the STBY mode, only the radar transmitter and RF transmission circuits are deactivated. Therefore, it should be similar with SIL mode concerning "false" targets depiction.

It's alright, @beacon take your time. We're monitoring some similar reports and gathering info. Your cooperation is valued.

@Carbon715 Thanks for your clarifications. I've raised this internally for analysis.

Glad you guys are enjoying it. Thanks for your support and patience.

Hi again @beacon I had suggested a simple clean mission with two aircraft to test it out. If your file is too big, then perhaps it's unusable due to either time duration or number of objects in place. Please try to demonstrate the event in a short track. Also consider some maps may have denser areas or require further optimizations, so maybe pick maps like the Caucasus for tests.

Hello @Ahmed We've sent this to internal analysis. Thanks for bringing this to us.

Hey @Xvraiden Indeed the C-Scope symbology should be observed regardless of having an FCR or not. This was working correctly back when you originally created the thread. Thanks for bringing this to us. We've sent this for internal analysis.

Wait, why are you trying to boresight and already boresighted sight and why are you doing it on a moving aerial target?

Hey @Anoro We're refining how the CDU works, one of the items is indeed how the CLR button actually clears the scratchpad inputs. Stay tuned for future updates.

Hey @shaji Like @BIGNEWYsaid it is reported internally. We're working on it for now, I'm afraid we can't give estimates at this time but rest assured we'll certainly fix anything that needs adjustments.

Hello @Carbon715 We've recently reviewed some logics of the EO weapons and that's what may be causing some confusion on your side. The AGM-65 have have two important modes of operation: SLAVE - commanded by one of the sensors (TMS Up), moving the weapon LOS to the SPI and SLEW when the weapon is SOI and the seeker is not tracking a target (TMS Up again). In this last mode, the seeker LOS is being controlled by the cursor switch and LOS circle is displayed in the HUD/HMD and will not follow a moving SPI, like it does when in SLAVE mode. If you have any non-classified documented evidence this should work some other way, as always, send us that documentation via PM for our analysis.

Hello @SAB0T The DCS: CH-47F flight model is currently still under development. This includes items like the various trim and AFCS logics. We understand this is an inconvenience for those with FFB joysticks but, rest assured, this is going to be improved in the near future.