Nealius

This appears to be broken again. Unit holding at waypoint 0 triggered to push next waypoint 1 ignores "on road" and drives off road. In some cases (Afghanistan) it will drive on the road for a bit before going off road. At second hold point, triggered push waypoint 2 is sometimes ignored and the vehicles are stuck (Afghanistan) or they will move a few meters towards the next waypoint and then get stuck (Caucasus). Mrap test-afghanistan.miz Mrap test-caucasus.miz

It seems that the ME doesn't register saves. Even after saving, if I click "fly" or "exit" it will ask me to save again despite having just saved it.

Both the airfield AND heliport need to be blue. You're parked within the heliport circle, and the system (for whatever reason) thinks you're contacting ground crew from the heliport and not the airfield. Since the heliport is neutral, they won't respond.

Dynamic weather is a legacy system full of bugs (like 30+ kts surface winds to get clouds to appear at all, after hours of lua editing to put pressure systems close enough to create those clouds where you want them).

Disk space is a growing concern. I had to uninstall South Atlantic and Sinai to save space, but with the rest of the terrains on DCS and Dedicated server I'm looking at 1.27TB. At this point I may move the dedicated server to a different drive.

I always set the ILS knob to the lowest possible position while still showing ON in the DED. The morse is still there, but it's not audible over engine noise and wind noise from speedbrakes out/gear down on approach.

JGSDF is in game as a default skin. JASDF, no one has made yet unfortunately.

Fog works for me if I set thickness to above Afghanistan's elevation. Dust storm does not because that thickness appears to be fixed, and below the map's elevation.

Here's what I mean. There's a major demarcation line between the low detail area of the map and what's essentially a no-detail area of the map. The SAT layer of the F10 map shows higher detail than this, while still being "low detail." This "less-than low detail" area, if brought up to "low detail area" standards shouldn't cause that much of a performance difference, should it?

This is correct. Squadron code and letter code have the same placement regardless of port/starboard. Typically squadron code always forward of the roundel, aircraft letter aft. There are some exceptions like the Mosquito where this is reversed because there's not enough space between the roundel and wing root for two letters--some squadrons using smaller fonts crammed them in there though. Some P-51 squadrons had the aircraft code on the vert stab instead of fuselage, etc. The system thinks L1949 is the serial number, BI is the squadron code, and L is the aircraft code because the system is designed to work with real codes/serial numbers that follow that logic. (Fun fact, L1949 was registered to a Hawker Hurricane that was lost in May 1940. BI doesn't appear to belong to a specific squadron but was allocated to RAF Holme-on-Spalding Moore.)

Configured, i.e. on-speed AoA. I said nothing about not being able to get the gear down. Once on downwind with gear/flaps down I'm still at 220-230kts, and the ballooning won't settle until I'm well past the LSO station. That's with a 3.5G (sometimes initially 4G) pull at 350kts in the break. 1.5nm is way to wide. Not enough G to decelerate for that. Groove turn at that distance would be 25 or even less AoB.

Low detail is of course understood, but present state is beneath low detail.

I messed with a carrier in the Arabian sea to check it out but haven't flown anything yet. Roughly an hour at 480KGS from a carrier group to Helmand which would make for some fun and challenging fuel management/cyclic ops timing. The textures between there and just south of the Afghan/Pakistan border look absolutely awful though. I don't expect high detail, but something better than random airbrushing would be nice.

Since the FM update the Hornet is a lot more slippery and doesn't slow down well without speedbrake usage, making the carrier break turn a little frustrating. Even when breaking 1nm past the bow like a T-45 nugget, aiming for 1.1nm abeam there's not enough maneuvering space to pull the necessary G to get configured prior to abeam the LSO station without using the speedbrake, yet accounts from pilots is that using the speedbrake is "for p***ies." My groove turn ends up delayed because the jet won't slow down quickly enough in the downwind.

Tracks are only valid on the versions they were recorded on. Sometimes there are exceptions.

+1. RAF bias with no modern RAF aircraft modules makes no sense. All our fast jet BLUFOR modules are American except for the Mirage pair and Viggen.

Both Hornet and Tomcat already have ball call and salute actions bindable to HOTAS.

Stennis existed since 2018 but was a inaccurate 3D model, smaller and with an inaccurate glidepath indication on the IFLOLS. The old Stennis was replaced with Supercarrier-parity Stennis that had functioning deck crew for SC owners and no deck crew for non-owners with the 2.7.15.25026 update on 08JUN2022.

I thought TACAN was a late 1950s development, after the Korean War?

It seems like, with enough research and calculating, we could come up with a user-defined slider curve to fix the throttle range at the user level while we wait for ED to address this, though with the default curve I notice that the throttle stops engage right at my physical AB detent on my Warthog throttle.

Since we have a timer for the fog and dust storm settings, a timer for cloud presets should theoretically be possible whereby the user can start the mission with one cloud preset, then at a defined time have the mission transition to a different cloud preset, e.g. starting off with "Broken 3" then at 2 hours after mission start transitioning into "Overcast and Rain 2" or somesuch to replicate changing weather.

P-47 and P-51 will follow USAAF convention as of WW2, which is XXY#### where X is the two-letter squadron code, Y is the aircraft code, and # are the last four digits of the aircraft serial number. Example: QP-U 473304 is a P-51 Mustang with serial number 473304, belonging to 334th Fighter Squadron (QP) and is possibly but not always the 21st aircraft in that squadron (U). In DCS we can only input "3304" for the serial number so a livery creator would have to bake in the leading "47." So in the mission editor you would have a number like "QPU3304." Spitfire and Mosquito will follow RAF conventions as of WW2, which are similar to USAAF in that you have a two-letter squadron code and a one-letter aircraft code, but the serial number format is different: ZZ###, where Z is a letter part of the serial number. Example: EG-T MM417 is a Mosquito FB with serial number MM417, belonging to No487 Squadron (EG) and is possibly but not always the 20th aircraft in that squadron (T). In the mission editor this number would be EGTMM417.

Fewer miles and more organized than a rats nest is clearly the point. No one insinuated that the Hornet had zero wiring.

@Flappie I was able to reproduce. Attaching client and server track files. Approximately 2 minutes after mission start, lead unit in the AI group starts "dancing." Approximately 2-3 minutes later, the last unit in the group starts dancing. After dancing for 2-3 minutes, the unit(s) become invisible yet are still present as objects and functioning AI. If this AI is triggered to start any time after they disappear, we have invisible AI flying around running amok. I've seen this happen with E-2s causing problems on the supercarrier (e.g. deck crew and JBDs responding to an aircraft which client can't see). All terrain shadows also disappear shortly after the last unit becomes invisible. Video (time lapse): uncontrolled-test-server.trk Syria-uncontrolled-test-client.trk

Aileron-Rudder Interconnect. It couples rudder with ailerons, e.g. when you move the stick for roll the rudder will move too. HAF -1 isn't classified. I believe it's ITAR restricted but not classified.