Floyd1212

Like TheGhostOfDefi said, the box will appear when there are RLWR pings detected, and the icons of the radar/laser sources will appear around the perimeter of the box. A pic from page 511 of the manual shows the same threats on both the ASE page and the TSD page:

You need to drop the 5th digit as the Apache can only handle 4-digit precision for MGRS. Your waypoint should be 51884 23287

The island of Cyprus is a great little playground for helos. A good mix of mountains and hills, and a few flat areas, too. There are some fortresses in a couple cities on the east coast, and some castle ruins up in the mountains in the north. Nicosia has some unique features due to how the city is split between north and south with a UN controlled “DMZ” running through the middle. If you look for them, there are a lot of little outposts and guard towers along the entire UN controlled “stripe” through the island, and there are a couple compounds on top of the tallest mountain peak in the main mountain range.

Yes, the tail is quite active when trying to slow to a hover; I’m hoping this will be addressed in the future, along with the excessive crabbing. But, I don’t get what people are complaining about with the hold modes. Granted, I never use them in forward flight, but they seem rock solid for me to maintain a stable hover. If you have a little drift in any direction when you enable AT Hold, it will take one major correction to get back to the spot where you enabled hold, but then the helo stays planted for days. Trim it out with less than 2 knots of sustained drift, and engage AT Hold. Manage the collective to get the VSI steady at 0, and engage ALT Hold. Go make a sandwich.

Is that the nomex balaclava you are wearing under your helmet? I don't fly in VR, but I have seen others have issues with where the camera is positioned in relation to the helmet to where you see too much of the player model. Almost like if your eyes were pushed back another 2 inches into their sockets. You can either mess with your VR settings to reposition things correctly, or there is an option in the Special Settings to remove the balaclava from the player models.

Interesting...

Currently, player slots have to be placed on the map within the ME. It isn't like they follow that FARP when it gets teleported around around the map. With the next patch (tomorrow), we may see the dynamic player slots, which may provide a way to handle this better. Still unknown how all that is going to work..

Yes

I think you are missing the point. Ignore what it shows in the ME and when you spawn in you should have your 60/30 loadout.

Try safeing the aircraft from the back seat, after which George will immediately arm it again. Often after doing a rearm/refuel with Ground Override on, George won’t be able to use hellfires until you go through this workaround. Maybe a similar situation occurs after a repair?

When you spawn into your aircraft, despite what the ME says, do you have 60 flares and 30 chaff? That is the default setting, and should be present when you spawn, and when you rearm. At least, that is the way it seems to work for me.

You should have chaff.

We are also getting this a lot. If the CPG joins into an aircraft that is already running, the CPG will get a CTD. If they join a cold aircraft with the PLT, then they start up, it is fine.

I’m away from my computer for two weeks, but if you post the mission someone might be able to look at it and see if they experience the problem as well.

As I mentioned in that other thread, we have been flying nightly with multiple cold-start Apaches using DL (typically on VHF) without issue. Sharing waypoints, routes, targets, PP, RFHO, etc. Maybe it's mission-related? Maybe it's setup-related? It does work for us (if you ignore the NAK messages).

For clarification, boresighting and setting range to "auto" is applicable when using the HMD as your sight, i.e. shooting the gun at what you see out the window. Using the TADS with laser ranging will use its own calculations.

Okay, so I take back what I said above. Bumping the torque up to 91% does not solve the problem and allow you to maintain an OGE hover. I actually took over the controls and tried to hover it myself and George was actually able to do a better job than I could. He apparently knows the magic number not to exceed before you end up with diminishing returns and get yourself into a faster descent. At 87% he manages to flutter to the ground with grace, but if you pull even 88% you will start to drop faster, and then eventually VRS. Agreed, not a George problem. It just seemed he wasn't putting in the effort to maintain the hover by nudging the collective a tiny bit more, but in reality, he was so well trained that he knew it would be futile. We need a recording for George saying. "I'm losing it! I can't maintain a hover in these conditions!"

Wags has other videos on DataLink usage and sharing targets, but this is the video on setting it up.

Are you saying that it isn't possible to maintain a hover in those conditions, or was that a reply to someone else? It would seem to me that in the above screenshot, there isn't anything preventing George from giving it a little more collective from 87% up to 91% to maintain the altitude, no?

I also experienced this. I'm using an analog thumbstick on a Virpil Alpha to slew the MMS. It seems that if you are slewing hard left/right, for example, and accidentally give it a tiny bit of up/down on the stick, it just comes to a stop. Obviously, you can slew the MMS diagonally just fine under other conditions, so I'm not sure why this is an issue. I currently have a deadzone of 3 and a curve of 20 set for the thumbstick, so maybe messing with these values may help.

I feel like the AI's ability to hold a perfect hover in an aircraft that doesn't have hold modes is a bit unrealistic. It would be cool if he would drift around within a box of some reasonable size, and within a reasonable altitude band. Not sure what these numbers would be, but the way it is now it's like you enabled Active Pause.

That's not what is going on here. In these conditions the helo should maintain an OGE hover at 91%. George won't pull anything higher than 87% in that track file. (Sorry for cross-pointing this info in 2 threads. After seeing it is a George problem, it really belongs here.)

It looks like George will never pull more than 87% torque. If you require 91% to maintain an OGE hover, he will happily sit at 87% and settle to the ground. If you tell him to increase altitude, he will confirm the command, but then never increase the collective above 87% to even try and climb. EDIT: I should clarify, he seemed to be capped at 87% when playing back the track posted by Homelander where the temp is 50C. In other scenarios he seems to be capped at some other value. In 30C temps I could get him to hover by maintaining 107%, but in a 3rd test where the temp was 40C, he wouldn't go above 100%.

This appears to be a George issue. The PERF page says you will require 91% torque to maintain an OGE hover in the current conditions and weight. George seems to only want to pull 87%. Edit: Forgot to insert my screenshot.

Ah, you didn't mention George in your previous statement. You may just have a "George" problem. There are reported issues with George not being able to hold a hover in situations where a human pilot can. You may be better off commenting in one of those threads; the OP in this current thread was talking about losing the aircraft when coming in to land with a human pilot. Maybe try this one: https://forum.dcs.world/topic/350096-george-hovering-skills/ Yes, but the Ka-50 has twice as many rotors, yes? I'm half kidding, but the point is that the two aircraft are hard to compare because of their very different rotor designs.