Nealius

Ah, it's relative. I've been brainwashed by years of BMS where the elevation is referenced from sea level. OA1 and OA2 are not relative to the waypoint elevation, correct? That's opposite what the manual says: VIP for something that comes up, VRP for pre-planned attacks like popups.

Is there a minimum altitude for the VRP and PUP symbology? Inputting 200ft or 100ft puts the HUD cues at around 350~400ft; they won't seem to go any lower. The F-16 manual doesn't mention any altitude limits.

175 is correct, but in mph on the gauge. Mission Editor only works in knots and kmh, unfortunately.

Viper shouldn't have tracers. IIRC the only aircraft with tracers in US service are the Eagle variants and the Tomcat.

+1 We have chocks for nearly every fixed-wing aircraft in the game now, however the implementation is haphazard, with some aircraft started chocked up, others not.

The default Japanese skin is depicted with a bright orangish brown, a very green green, and black. This is not correct. Here are the official color chips as published by the Ministry of Defense's (NDS Z 8201E): The green is 3414 "deep green" The brown is 3606 "brown" The black is actually a dark OD, 2314

The colors also are not correct. The green should have a more grey hue, and the brown should have much less red.

Very minor animation bug, but MFD buttons are not animated when pressed via keybinds (e.g. Cougar MFDs). When clicked they are animated as normal. In the track file I demonstrate by pressing a few on the lower row, left MFD. Apache-mfd.trk

Markpoints or drop, slew, designate, drop. If it's only two targets, it's usually more accurate to manually target between drops while lasing the designation. The GBU-38s with plugged nose fuses have had very poor accuracy for me recently, while the DSU-33 ones seem hyper accurate for some reason.

The max temperature possible on the map is 40C. This makes it impossible to set realistic weather. Example: Today's forcast at Tarinkot is high of 41C. Not only are we not able to set 41C, when we set 40C, the in-game OAT at Tarinkot becomes 31C because it is at about 4,500ft elevation. In order to get correct temperature at Tarinkot, we have to add 9C (2C per 1,000) to real-world reported temp to the mission editor temp, e.g. 50C to get a desired reading of 41C at Tarinkot. Due to the DCS weather engine applying ME weather at sea level, and Afghanistan is largely above 3,000ft elevation, a max temp of 40C means that we effectively can't set any mission temp higher than about 34C.

Thanks. Those were the only two not named in the template. I managed to locate Coyote from a document referencing it being north of a town, but couldn’t find anything down in the Dwyer area on Google.

If the beta testers spent as much time arguing on forums and insulting customers as they do testing, we wouldn’t have this bug in the first place.

I'm guessing the FOB north of Hadrian is Coyote? What's the name of the FOB southeast of Dwyer?

For those (me) with DCS on a drive other than C:\ here's how to do it: 1. Navigate to DCS World OpenBeta Server\bin folder 2. Press and hold shift while right-clicking somewhere in the folder, select "Open Powershell window here" 3. Enter the following: .\DCS_updater.exe install AFGHANISTAN_terrain Powershell will not run files if the filename isn't preceded by ".\" and the ">" before "install" is not necessary.

Typically USN and USMC does use Navy-supplied weapons even when stationed on shore. At least that has been the case for ODS, OEF, and OIF. However in ODS they used Mk20s, even from carriers if the reports are accurate...I'm guessing the CBU-99/100 came about later in the '90s? I can't find a whole lot about the history of specific variants. USN Academy training manual on weapons doesn't even have the Mk20 in it, though it does make mention of it twice. All cluster munition diagrams are for CBU-99/100, and GATOR.

Just checked myself, and yeah the Mk20 does not have an altitude fuse option at all. However, the Hornet (and Tomcat, and Harrier) should be using the CBU-99 anyway as that's the thermally-protected Naval variant of the bomb. No idea how the USAF guys are supposed to use their Mk20s, though, if there's no altitude fuse option.

Does temp and baro pressure affect rotor spool up times in a similar fashion as it does with engines? The real-world video appears to be winter. DCS video is spring/summer, and most likely warmer.

Is it possible you have the wrong fuse set in the payload menu? The airburst fuse has a much different nose section than the default fuse that was standard pre-update. It does not have timer options, and has an altitude function drop-down menu.

Doesn't really help that the real-world terminology is a bit of a mess, and varies by country. Currently "AA" seems to mean anything that's surface-based anti-air, including both ballistic projectiles and guided missiles. In the US services I heard rumblings of moving away from "AAA" to "ADA" (Air Defense Artillery?) but a cursory search only shows the US Army using that term. There doesn't seem to be an agreed upon definition of the terms, and no mention of "AA" vs. "AAA" differentiating between projectile size; that was done by affixing "light" or "heavy" to the acronym of choice, e.g. light AAA or light flak for 20mm etc., heavy AAA or heavy flak for 88s. That's in general usage, though, while guns like the QF 3.7 are offically named "AA" for whatever reason. Ignoring the acronyms and country/linguistic variations, all are classified as "anti-aicraft gun," so something to that effect might be a better category. Which really makes more sense as a broader category anyway since cannon, auto-cannon, small-bore, large-bore, rifle, etc. are all ultimately "guns" in the end.

22JUL hotfix, still doing CASE II when visibility is CASE III. Surely I can't be the only one who does carrier ops in weather other than CAVOK high noon.... OVCRA3.trk

Would be nice to have it consistent with the current system on the Viper and Hornet, where the head is invisible within reasonable constraints, but appears once the camera position is well outside normal movement range.

I suppose you could scribble in the coords of the markpoint then overwrite one of your 1~24 points (assuming 25 is Bullsey; might want to keep that one).

Can the TGP be slaved to OA points? I've only ever used them for pre-planned pop-up symbology so far and don't recall any systems slaving to them.

IIRC External wing tanks should be CATIII, so I leave it in CATIII and just punch the master caution to reset.

The way my dumb butt would probably do it is put the TGP on that reference point, then fly within 5nm of that reference point and look out the window, then draw a mental circle about that distance around the reference point. If I have a bearing as well, I would set the course line on the HSI and overfly the actual target to get a visual reference, and perhaps an OFLY markpoint, but OFLY markpoints in DCS always seem to be off by a few miles.