Floyd1212

We often get the NAK message as well, but the data is received anyway. We also notice in a multi-crew setting you will sometimes receive the same message twice. And when you have a front-seater, adding aircraft to the preset using the Member Directory will result in two instances of the aircraft being added. ED, have you been able to test with 4 players occupying 2 aircraft?

It has been noted (by those who would know) that the crabbing is a bit exaggerated with the current flight model. If memory serves, at maybe 2.5x what it should be. This is the way it should work. If you are in aero trim (ball centered) you will be crabbing as you fly. If you are in nose-to-tail trim (with the flight path indicator at your 12 o'clock) you won't be crabbing, but you will need some left roll to maintain your heading.

And Bradmick has his series here:

This is what I do, but like you said, I do have to zoom in and out a lot based on what I am doing.

I will second the Virpil CM2 base with a 20cm curved extension. I tried an Alpha grip with the CM2 base and actually preferred the feel of the Warthog grip and buttons, so I am using that with the CM2 base. Great combo, with the center-less cams and loose springs. Their newer CM3 base has the dry clutches, so that is an option as well.

I have noticed the same thing. When I F2 to view a few of us landed on the grass, others are kicking up way more dust than I am.

The CMWS page is there to tell George to flip those switches for you, which are only located in the back seat. Where would you put "slide left" and "slide right" on the FLT Page? It looks like short L/R and long L/R are already in use. That being said, being able to bring up a specific page with a keystroke would be useful for some people.

I just went up in the Runway Start quick-action mission and couldn't get it to work either. I'm getting the same results as the OP. You can get the SKR option to be green after WASing missiles and telling George to lase, but when you press SKR, it will not take.

I replayed your track and saw what you were describing. I then replayed it again, and took control before you lifted off, and was unable to reproduce the issue with my setup. I would double-check your binds and make sure you don't have something silly bound to your Weapons Trigger Switch - Second Detent, like maybe your left mouse button?

I was flying with some buddies last night, and they caught this bug as they were getting started up, so they hopped out and saved the tracks. The desync occurs at 09:17:06 Z mission time (as indicated on the EUFD) when the PLT gets an FMC Disengaged warning out of nowhere. This is while the CPG is setting up his TSD on the right MPD, and presses T3 for SHOW, then T6 for COORD SHOW, and then L4 for ENEMY UNITS. The PLT sees this as pressing T6 for UTIL on the A/C Page, followed by L4 which turns off the COLL channel of the FMC. Here is the PLT track MPD Desync - PLT.trk Here is the CPG track MPD Desync - CPG.trk One other thing to note is that the CPG slots into the aircraft after the startup process has started, and he gets a Rotor Brake warning as soon as he spawns in, which is a desync issue that the PLT corrects by quickly toggling the Rotor Brake on and off again. This causes an auto-page to the A/C page on the left MPD in the back seat, but you do not see either MPD changing to A/C in the front seat at this time. I'm guessing that this is where the auto-paging desync occurs between the two seats, and then pushing buttons eventually leads to the FMC Disengaged message.

I think you will get a little push back on this statement... Raptor9 had a great post a few days ago:

I’m not seeing any new behavior with the collective not syncing on startup. My guess is you have another axis bound to the collective and there is “competition” for what position it should start in, then nudging your physical collective sets it back to zero. Having controllers get auto-assigned an axis is something we have seen after patching.

The "save" file is called "footholdCyprus_v1.lua" and is probably located in the parent directly above your "missions" folder. You can delete this file to start the mission over again. The actual .miz file is not modified when you run the mission. If you made a change to the .miz and ran your new one, it would try to load the same save file as the previous mission created. This is a tough mission to play solo, I will say that. It was designed for a small group of us flying 2-3 Apaches and an occasional A-10A.

If you want to shoot the gun with your helmet sight, select HMD as your sight (not FCR) so the gun will track your head movements, then WAS the gun.

I actually just uploaded a new "v2" version of the mission to fix some crashed caused after the 2.9 update. See the initial post for the new file. I also added FCR radars to some of the Apache spawns in each of the airfields. The persistence file is written to once a minute, and includes information about what zones have been captured by blue/red, and how many unit groups are left in each zone. If you restart the server, or come back to it later and play it in SP, it will reload that info from the file and pick up where you left off with the zone captures. If this isn't happening for you, it sounds like you don't have the missionScripting.lua file edited correctly. As for attacking a zone with a SAM, you can use the FCR now to help. You can also approach the zone from a different angle to maintain cover. You don't have to attack the zones in any particular order. You can also call in a JTAC drone to lase the threat for you, and you can engage from a safe position. Also, each time the mission starts over and restores the groups from the persistence file, they spawn in at a new (semi-)random location within the zone, so the next time you fire up the mission, that SA-8 may be in a different location within the zone.

You can also see this bug in Wags' latest video.

This didn't matter before when the only thing that would be affected by the ACQ set to TADS was the queued LOS reticle on the HMD, but now that we have the FCR as the active Sight, the ACQ affects this as well. It would be nice if there was a Slave button available in the back seat to make this happen on demand, but I guess it acts like it is slaved to the ACQ at all times.

What does the AUTO setting do? And could there be a situation where you are on a slight hill looking down and targets at 4km need one setting to see, and targets at 8km need a higher "step" in elevation to see?

We were seeing this in a multi-crew setting as well. PLT using FCR with active targets ready to go, and the CPG cannot select FCR as ACQ.

Something weird going on with the track replays. I watched your track the first time a regular speed and you fired 3 shots, and got 3 kills/criticals, all in the same area. Then I went back and watched it again, and took this screenshot to show none of your missiles were "going haywire", but it only gave you 1 kill in the BDA. So then I watched it again, and this time your missiles arced off to the left, and you again got 3 kills/criticals. Not sure what's going on anymore.

If you scan and get a return with targets, then launch a few missiles and they get the X on them to indicate they were shot at, does doing a new scan remove the X and allow you to shoot them again? I feel like the X stays there and they will be skipped over when prioritized. I will have to pay more attention.

Interesting. I was not able to pick up any of these static groups (which are within 6km) from up here.

I was complaining in another thread about not getting any radar returns for groups that are clearly right in front of me (often shooting at me), so I recorded a video and saved the track to post as a bug report. However, when I replayed the track, there were times when I was getting returns in the track when I wasn't getting returns at the time in-game. Here is a screenshot of what I was seeing in game, as captured by my video. But here is what I see when I playback the track file. The first thing you might notice is that the MPDs are displaying completely different things. This may be part of the problem, though really it shouldn't be. I use external touchscreen monitors in front of me running Helios to interact with them, and for some reason the track recording system does not register button presses I make through Helios. It does in real-time while I'm flying around, but what you see during the track replay is totally out of sync. But even when the displays don't match, every time I press the single-burst scan button, I see the white sweep back and forth. Why would returns not show up on my displays in game, but then show up in the track replay? At one point in the video, I am running in on the enemy units that are shooting at me, and still not getting any returns. Here is the track and video file. FCR Test.trk https://youtu.be/REv8tLs6h5Y EDIT: I should also point out that the original reason I was making the video/track was because I couldn't get any returns while perched on top of that hill. They are clearly within range and unobstructed by trees, so is it the look-down angle from up there? Is the radar not designed to scan low like that? And before you ask, yes, I manually adjusted the radar elevation to the lowest setting to look down, but you don't see me doing that in the track, just the video.

We get NAK responses a lot, even when the data goes through. We sometimes get duplicate messages incoming when the data was only sent once. We sometimes get members listed twice when added via the MBR DIR option. We sometimes don't get a response when requesting a PP report with other members flying nearby. This is all on a MP server with some aircraft flying solo and others flying multi-crew. Never tested with an AI wingman.

I am also experiencing zero returns on occasions where I have complete LOS of the target group. The T90 in the group is lasing me and firing Snipers my way, but the FCR is unable to see them in a scan. Then, sometimes it works and I get targets. What is the maximum look-down angle I can expect from the FCR? Can the radar see through the main rotor disc?