key_stroked

Anti-virus is disabled on my computer. I have also tried all types of repair but the problem persists. Is it possible for ED to remove autostart scripts from the Integrity Check filter?

I don't understand the IC system. I log in, the shield is green, and I pick a multiplayer server. Halfway through loading into the server, it kicks me out and says I have a tainted client (it just told me I was clean). The thing it's complaining about is a custom autostart script I made to automate some MFD setup on the F-18, since we don't have any data cartridge capability and I got sick of setting up all my radar settings per mode by hand. Why does it tell me my client is fine and then kicks me out after I try to join a server? Why would a modified autostart script be considered "bad" for IC? It doesn't give me any advantage other than saving me a couple minutes on the ground at start up. This makes no sense. @BIGNEWY @NineLine

Crickets

Thanks, that link had good info.

Just to update this, I circumvented the issue by pulling forward slightly so the wingsweep on the F-14 doesn't touch me even if he extends them fully. A couple close calls with aircraft taxiing right next to my nose, but I was able to finish the mission this way.

Weird. I'm playing the Raven One: Dominant Fury campaign, and part of the scoring system is to be recording certain parts of the missions. I assumed those were the switches.

Resurrecting this thread because I've done extensive searching and haven't seen anything talked about NAVFLIR functionality for the hornet by ED since this post was made. ED, can we please get an update on the features our ATFLIR pod are supposed to have?

Screenshot attached. I'm looking for the keybinds to the switch circled in red. The tooltip calls it the "Mode Selector Switch", but looking in the F-18 key mappings, I can't find that anywhere. I also searched the keybinds for "Video" and "Recording", but the only thing that comes up is the HUD Video Control switch on the HUD controls panel, which isn't the same panel. Is this switch (plus the other two next to it for source selection) not a part of the default keybinds?

Thanks didn't know this forum existed

In the designer notes for mission 6, it says to get ground crew to remove chocks within the first 5 minutes or else the F-14 parked next to you will damage your F-18 when it starts up. I've tried the mission 3 times, always removing chocks as soon as soon as my jet loads, and every time the F-14 starts up I take damage. It's always the left wheel. I get warning bells in the cockpit, my gear lever is glowing red, and if I look at my jet from external view, my wheel is completely bent in. How do I fix this from not happening?

Ah, thanks for the followup. I haven't come across this issue since I reported it, but I do use a modifer key that simulates holding down the Shift key. Next time I'll try tapping that a few times.

I've used the SIM setting for guns before, so I figured that this campaign would be utilizing that training feature, even though I didn't see it mentioned in the briefings or any of the promo material in the store. During the 2nd mission, the FAM flight, the voiceovers talked about how SHOWTIME would be calling out who was alive and who was killed based on the data supplied from the TACTS pod. I figured that if I managed to bracket a target in my gun reticle and pull the trigger in SIM mode, SHOWTIME would tell me I had scored a kill. For the F-5 and F-16 engagements, I got behind them but couldn't get close enough before they dove for the ground and broke the hard deck, terminating the engagement. Each time my wingman told me I had won the engagement. During the F-15 engagement, the first thing he did was cut across my line of sight (which I thought no one was supposed to do as per the safety rules briefing) and forced me to avoid him, and during a high G angled pass he did a snap shot that blew my wing off. This was at 6,000 ft ASL, which in Nevada is REALLY close to the ground. I ejected with barely any time for the chute to open. I just wasn't expecting that. For a super realistic campaign that had 25 pages of real looking procedures and safety protocols and ingress/egress routes and arrival/departure procedures and charts for Nellis, I was extremely shocked that I actually got shot down in a training exercise. I failed the mission, and I was kind of ticked off because it took a while to get to that point in the mission, and no one told me I was going to get shot at by live ammo. I'm enjoying the campaign so far, but that bit of extremely important info really ought to be included in at least the text briefing, with some type of DCS-ism explanation as to why live ammo is being used in this version of a simulated training mission.

Holding Tab, pressing Shift+Tab, or pressing Ctrl+Tab do nothing. The focus is on the chat window and is stuck there. Can't press escape either to get the menu to quit. I have to force quit through the task manager.

Can you get markpoints to show up on the A2A radar display?

For those that don't know, you can pick up low level (or possibly high level? Haven't tested high level) helicopters using the ground moving target radar (GMT). They show up as very faint lines but they're there. If you designate on a faint line, this will slave your TGP to the area and then you can visually pick out the helo using FLIR/TV. At this point you can change to auto tracking and your TGP will track with a contrast lock. What I want to know is if you can then: 1. Keep that contrast lock on the helo even when switching radar modes. 2. Switch to A2A radar 3. Slave the radar to focus on the TGP contrast lock 4. Acquire the helo with the radar in an STT lock Is this even possible? Up until now, I've been doing the GMT/FLIR trick to get a visual diamond on the HUD and determine where to point my AIM-120 circle for a maddog shot since I can't get an STT lock normally because the helo is so small and so close to the ground. I've found the hit rate to be about 50/50 doing this. An AIM-9X has better tracking, but is easily spoofed with the 50 million flares that AI helos pump out when you fire (magic all-seeing AI that knows I fired a heater missile at them from behind).

If I'm in the pilot seat, I can switch radios normally using the RTS depress switch on the cyclic. But if I'm in the Gunner seat, then George has the flight controls and the RTS keybind on the cyclic won't cycle the SRS radios. If I press the RTS rocker switch on the EUFD panel and press the ENTER key, the * next to the SRS radio display on the left won't change. Is there some sort of SRS trick I need to do?

There is nothing in the axis layer. The other 2 columns to the right are trackIR and mouse. I only have the three devices plugged in (throttle, stick, rudder). I've tried a repair, but it didn't do anything. I tried a repair but I didn't touch the folders in the main install location. I can try that next I guess.

CA feels like their red headed step-child. Often neglected and given attention last.

This doesn't fix the issue. In the screenshot above, I'm getting the red ! mark even with nothing bound. There is no conflict. I did more internet digging and someone said to manually add in the axis ID to the default.lua file in input -> F-14B Pilot -> joystick, so I tried that (shown below). This worked until I restarted DCS, and now I'm getting a red ! mark next to the "Pitch", and JOY_RZ is binding itself to my rudders (I'm not even sure what axis RZ is). I tried to hit clear before rebinding my stick Y axis to pitch. No messages tell me of anything conflicting, and hovering over the red ! mark with the mouse doesn't tell me anything either. This is what I saw tonight before I hit clear. Pitch has a red ! mark. If I hit clear, I see this. My UI Layer keybinds don't even have anything bound to any axis. To reiterate, I completely wiped all my keybindings last night by deleting the input folder from Saved Games -> DCS.openbeta -> Config and started rebinding all my modules from scratch. So far I've bound the F-14, F-18, SA342, and the Huey. Out of all those modules, only the F-14 is having the red ! mark issue. Any other suggestions?

Thanks for poking them. Really though, how long are we expected to wait for these fixes? CA right now is borderline unusable with all of the glaring issues it has. Can't manually drive anything up inclines, random slowdowns in the middle of nowhere, pathing issues, no sound for dynamically spawned units, ranging and ballistics issues for certain tanks like the Leo, JTAC binocs can't zoom as far as the driver can, and the list goes on. How can they honestly keep selling this for $40?

Another patch cycle, and nothing has been fixed. I'm absolutely disgusted with ED and their treatment of Combined Arms. This is pathetic.

This has been broken like this for 2 patch cycles now. I'm convinced ED doesn't test anything CA related.

I did some internet digging and found out others have been having this issue, but I couldn't find anyone that said they fixed the issue. For most, it happens to only Heatblur's products. All I can say is I've been using the F-14 since launch and never had an issue with axis bindings. As soon as I received my Warthog Throttle the other day and swapped it in place of my X-56 throttle, the throttle and rudder are now showing red exclamation marks, even if nothing is bound to those axis slots. I can bind an axis to the throttle and rudder, but moving a physical throttle/rudder doesn't show any white bars showing the axis movement. I have tried deleted the config -> input folder from the DCS Saved Games location and letting the folder rebuild itself fresh, but this screenshot was taken after doing that. Windows can see all of my devices just fine, and they show up correctly in the Devices control panel. I'm able to test the rudder and throttle just fine using Window's built in axis/button So why is this happening to only Heatblur's products? And how do I fix it?

Have either of you tested on a dedicated multiplayer server? And are you testing with units spawned on mission start, or with dynamically spawned units? Because I'm in a dynamically spawned unit right now on a multiplayer server, and this M1A2 has no engine audio. I've cycled engine start on/off as well. No change.