Nealius

It's working for loops (last waypont > WP0) but it is not working for progressing through multiple waypoints as shown in my two track files. E.g. WP1 hold > push WP2 > hold WP4 > push WP5 > end WP7. They hold at WP2 and refuse to continue moving, or stop before they even get to WP2. They also ignore "on road" command between any hold point and destiation waypoint after Task Push.

CH-47s and Mi-8s have potential rotor clearance issues at these parking spaces when AI is taxiing to the runway. Human pilots can hug the grass side of the taxiway to avoid issues, but the AI aren't smart enough to do that.

DCS with all terrains except Sinai and South Atlantic + Dedicated server + Saved games = 1.35TB I'm worried I won't have room on my drive for the Germany map.

They work on the Hind, Chinook, and Apache as well. Unfortunately not on the Huey or Hip. Also not functioning at all on the Mosquito. Jets that should have rain repel (blast of air over the canopy) don't have that functioning either.

It seems like they only acknowledge static Hornets and Tomcats. For instance, if you park Hornets in the junkyard and next to the island (where they shouldn't be in real life) the taxi directors will not direct you to park there. However if you fill the same spots with a Hawkeye, forklifts, and helos (where they should be in real life), the taxi directors try to get you to park right in the middle of them.

@Flappie Still broken in 2.9.13.6818. Ground units will hold then AI task push to next waypoint only ONCE. Subsequent AI task push commands to continue their route are ineffective. This is game breaking for a multitude of missions that rely on ground units to hold then continue moving multiple times. Same symptoms displayed in the replay tracks posted above. They get stuck at the waypoint they were told to push to and ignore the rest of their route. Even adding advanced waypoint action to go to subsequent waypoints is ignored. This makes sense for AI task set which overrides everything, but AI task push is supposed to preserve other settings. I discovered a secondary workaround: AI task push to the last waypoint will get them moving again, but if you tell them to push to the next waypoint in the sequence they will stop.

Is there any documention on the tanker anchored orbit settings? 1. What does "hot leg bearing" do? 2. How does the track width affect bank angle?

There's quite a few already on many of the airfields. Some open, some closed. Few of which can actually be used for parking, though.

Assuming JDAM's, those would be using data from GPS satellites which have no INS drift. A 300ft discrepancy in the jet's position would be too small to matter.

Yep, close to a year and still no sufficient documentation. What little documentation we do have is user-created scattered on the forums or on some dude's paid-tier Patreon.

I have a mission with 9 random-generated strike tasks using flag 18 random value 1-9, and I need to set a briefing for each task. After typing the different briefing texts, and ensuring they are all correct, I hit save. After hitting save all 9 briefings have been overwritten with the text from the 9th briefing in the triggers list. Briefing images appear unaffected.

They really use have named it with the Suite number like Razbam did with the Mudhen. A-10C S.7 or whatever the suite would be for our "II" model.

In the Apache, for example, if you press the extend command too long it's pointed more upwards and is thus useless once approaching the ground during a landing phase. The retraction keybinds in DCS don't work like this unless you map them to a physical switch. You have to hold the key command/HOTAS button down and guess when it's been completely stowed because once you let off the keybind/button, the movement stops. In the Huey, Hip, and Chinook I always have to check external view to know when I can stop holding the retract command down. Thus the reason for my question. So in real life it's clearly a nonissue. In DCS it looks like the keybind behavior needs to be tuned so a single press of the key command will fully retract the light.

The CH-47 got functioning wipers within a couple months of release/request, and yet the Mi-8 and Huey have been totally forgotten.

One thing I've always wondered about these searchlights in all helicopters: how does the operator know that the light itself is completely stowed or extended to the desired position (mainly in the day when the ground illumination isn't visible)? There's no cockpit indication of the light's position or stowed/unstowed status.

Mission making for OEF is going to be a bit like mission making for the Normandy map. Everything really depends on which specific time frame you're wanting to replicate.

This should be as intended. The DSU-33 is a sensor that goes in the nose fuse well. It is not a fuse itself. It sends a signal to the fuse, and since the nose is plugged with the DSU-33 sensor then the only place a fuse could possibly go is in the tail.

There are a lot of modules that have the same rain repel system as the Hog (Tomcat, Phantom, etc.) but they aren't modeled. It doesn't seem like the developers of the modules have much interest in modeling that feature and ED doesn't seem interested in making the rain distortion more realistic (i.e. not as distorted as currently represented in-game).

Perhaps? So far I've had five occasions of this happening, all on the Afghanistan map: 1. Pitch down while at around 19,000ft and 4~5nm north/northeast-ish of Bost airfield, over Lashkar Gah. Pitch up "reset" at altitude while operating elsewhere in the Lashkar area (don't recall exactly as it was a few months ago but it was somewhere on the West/South quadrant from the airfield), at which point I did not experience a pitch up on landing at Kandahar. 2. Pitch down at the same location as situation 1, but no pitch up "reset" until flaring at Kandahar 05. 3. Pitch down on departure from Bagram 21R roughly 6~8nm somewhere between runway axis and 20 degrees east of runway axis. I didn't complete that flight. 4. Pitch down on tanker rejoin at 20,000ft, 2~3nm bearing 259T from Jalalabad airfield. Pitch up "reset" while flaring at Bagram 21L 5. Pitch down 6~8nm roughly 043T from Bagram while doing a TACAN arc to 21L. Pitch up "reset" while flaring at Bagram 21L. In missions where I avoid overflight of airfields I encounter no pitch down nor pitch up reset at any point during the flight. Now that I've typed these out, is it just me or is there a pattern of the first pitch change usually happening north/northeast and south/southwest of airfields?

Strange. On an attempted landing I had the nose swing up to 10 degrees, hit the trim reset which leveled me out, did a go around without touching trim at all, and on my second pass was able to land normally without any pitching issues.

This has been somewhat fixed in that it happens less often, at least for client/player aircraft and AI. However for static objects using non-default liveries, it almost always resets to the livery at the top of the list. I have seen it occasionally happen to certain player/client aircraft but it's so sporadic I haven't taken note of them.

No, trim reset. Might be named "reset trim" in the controls window, I don't recall.

Charlie model is going to be quite a bit different due to it's larger size affecting lift and wing loading. Who knows what else the Navy has in it for potentially more AoA capability than the other models. I wouldn't be surprised if they have different flight control systems logic. The Bravo certainly does for VSTOL modes. For the Navy variant we'd need PLM modeled as well.

Google Earth, View menu, historical data. There's a slider but only a handful of snapshots between 2008 and present have clear images.