Nealius

I might be late to the party but I recently discovered you can tilt the free camera (RCtrl+F11) clockwise or counterclockwise with the 3 and 1 keys, respectively.

It was with the taxi directors, yes. And I've been here long enough to know that even if we do provide track files things won't get looked at, usually because they're "too long" or involve "scripts" which somehow invalidates the whole bug report. But then when you provide a no-script short track it sits with 0 downloads for months, completely ignored.

Recent update has changed fog altitude to max out at the lowest cloud base height regardless of ME height setting.

Visibilty distance still seems messed up. With it set to equivalent 20nm visibility, returning to the carrier Mother isn't visible until 5nm or so.

Unlike a lot of languages that have one or two standardized romanizations, languages in this region don't. I've seen 4-5 different spellings for the same place across the ALT map, the MAP map, real-world MGRS maps, and Wikipedia. Getting all these names to conform to a standard is impossible when said standard doesn't even exist.

Last update screwed with the bindings. I lost my antenna elevation bindings as well and had to redo them.

Lots of issues still remain unfixed as well, and recently the IFLOLS calibration was broken. Two Hornets cannot be connected to Cats 1 and 2 simultanously, significantly slowing down launch operations. Deck crew have stopped moving with urgency and slowly walk, significantly slowing down launch operations. AI launching on the bow cats get stuck on the cat if other aircraft come in for recovery, breaking cyclic ops. IFLOLS is consistently about two balls lower than actual glideslope. Others are having issues where the IFLOLS isn't usable at all due to excessive light bloom.

Usually "one-way" airfields have a reason for being one-way: mountains, cities (post-WW2), etc. These don't have any logical reason for being one-way.

Similar to the Chinook, which got its coordinated turns implemented within a couple months of release. I hope with the new tail rotor modeling that’s indicated on the thread tag reassesses LTE tendencies. The Apache is the only helo module I’ve regularly experienced it in.

Most likely related to this issue:

What is this monument here? That particular screenshot is just beyond the Berlin TV tower, but there's another copy of it on top of a hill on the outskirts of the city to the northeast. I can't find any records of a monument like this.

That's a bit of a problem with a lot of the rain presets, as there are pockets of good visibility and very low visibility (calling for CASE III) as the carrier moves through the water.

Delay AI spawn by 1 second and they will skip the sixpac slots. Not lua editing needed.

Night is always CASE III regardless of weather, with "night" being specifically defined by the Navy as 30 minutes prior to sunset until 30 minutes after sunrise.

In my experience CASE switching in DCS is somewhat broken. Furthermore, in an episode (the one with CATCC Sue if I recall correctly) of the Fighter Pilot Podcast, CASE II is rarely ever done in real life. Typical operations are either CASE I or CASE III.

Why is it not being acknowledged that this was never an issue between the time that replay tracks were improved in the 2.9.0 patch and the subsequent updates that started causing issues? This is not a scripting issue as it happens in missions that have no scripts.

This error has been going on for nearly a year now but the popup warning is new. Usually you can get around it by selecting "quit to desktop" and renaming the lastmission.trk file but it's not guaranteed. I have one online flight that I wanted to lift MFD footage from. The client track has this error but the server track of the same mission, on the same PC, works fine. People have been sending track after track but we keep getting told the same excuse: "tracks break between versions" (they were recorded and played back on the same version) and "external scripts" (they happen without external scripts). There's no official recognition of there being a problem.

Could you get fire at point working without scripting? I've found it extremely finicky as of late. If the fire at point objective isn't precisely on something the AI have LOS on they won't fire, and it's really dificult to make sure they have LOS when there's so many tiny depressions and ridges in terrain that don't show up well on the map.

Then why is it marked as a helipad?

Amateur strategy hour I guess but the problem I see with the North German plain is its proximity to the North Sea. The Soviets would have to dominate that area with their navy to keep NATO carrier groups out and intercept flights out of the UK. Which doesn't look feasible in that triangle between the UK, Netherlands, and Sweden. Sweden was officially neutral but in reality not, so they surely would have helped with ASW in the North Sea. Another issue with the North Germain plain is that, being a plain, it's probably going to be prime killing grounds for Apaches, Kiowas, and Abrams. The East German border down near Fulda is probably the closest to any major West German strategic areas--I could be wrong as I'm still getting acclimated to the geography. So that's one bonus point, but that assumption is just as flawed as WW2 Germany's assumption that the Allies would launch Overlord between Dover and Calais. If they did zerg rush Frankfurt they could have cut off southern Germany, creating a pocket trapped between mountains, East Germany, and Soviet-aligned Czechoslovakia. Switzerland wouldn't do anything. Getting forces across the French border there in Stasbourg or across from Austria would be difficult due to the mountains. Austria's one flat border area is next to Czechoslovakia. To RVT20403's point, the terrain around Fulda favors the defender but that also goes for the Soviets if they managed to take southern Germany. If successful they could expand their territory to an easily defendable enclave jutting further into NATO territory. Russians are pretty notorious for playing the long game, so I wouldn't think they would try to take the whole of West Germany, instead at first taking chunks of territory, then rebuilding for a decade or so, then taking another chunk. I'm still curious, though, how much it favors a NATO defender. As modeled in DCS I find the hills and trees to make it nearly impossible to use Apaches and Kiowas as intended, forcing us to go high to see over the terrain and trees to find and engage targets, which exposes us to Soviet ADS and CAP aircraft. Trying to rely on the terrain masking and stalking inevitably ends up with point-blank engagements where we're more likely to be taken out by a TOW missile or Shilka than we are to knock out a tank with a Hellfire. I really want to see an episode of "History Undone" on this topic.

While we don't have an EGI, the real manual for this system states that the Kalman filter continuously updates the RLG INU with GPS data as errors are accumulated, and that errors tend to accumulate in 84-minute cycles, with 16m spherical error probable on military GPS. With an 8-minute or less alignment that indicates RDY, CEP is stated as 0.8nm per hour. This is also valid for stored heading alignments. The Kalman filter with status HIGH has a position error less than 300ft, however the manual also states the same as the mini-update that GPS accuracy is 40 meters. The last time I tested, the Kalman filter/GPS was working and keeping error within 300ft. Using INS only drift rate was exceeding 0.8nm/hr, showing a drift of 0.8nm (going off the DED delta when doing a fix) after only 30 minutes of flight after a cold start, so drift rate seems to be twice as fast as it should be. 400-foot drift with GPS on shows that the Kalman filter is no longer working. People constantly complain about nav accuracy with JDAMs but the bigger issue, especially now with Cold War Germany, is that we cannot do pre-planned pops as the Viper was designed to do in that era because the nav system and HUD symbology is too inaccurate for weapons delivery. Sure CCIP gets your bombs on the target, but the VRPCCRP/VIPCCRP and OA1/2 plus TD box symbology is supposed to put you on a proper wire, which is dive bombing 101 fundamentals. The drift is too excessive and fixes too unreliable to get on a proper wire for the intended target. Fixes don't even work well from a cold start aircraft. They work on an air start and when doing a fix almost immediately after mission start, but when doing a fix after cold start and a 30+ minute ingress, only the selected STPT gets fixed and the remaining STPTs on the flightplan do not get updated. 2003 Block 50 manuals have EGI. F-16.net discussions indicate Block 50s had EGI by 2005. Our INS+GPS supplement system I can only find in late 1990s manuals. Most likely they're modeling a specific tail number that was late to the upgrades.

Using the MOOSE RAT script to spawn AI traffic, helos starting on the helo pads at Tempelhof fly straight into the terminal building on takeoff. Lua scripting does not alter AI pathing behavior. Tempelhof.trk

Are we going to get another sound update? The .50cal sounds like it's suppressed and is completely inaudible from external views.

Must have been the 4k textured easter eggs.