Nealius

Crowd-sourcing info here, but after 1+hr flights in the Viper on Afghanistan, has anyone come across a really weird crosswind when landing at Kandahar 23? With mission wind set 100° (TO not FROM) 2kts, the DED wind page read a wind that shifted 270~330 up to 9 knots as I was descending on glideslope on runway 23, but I can't reproduce it in short test missions. That wind wasn't there when I took off. It's really weird. Has anyone else experienced the same?

I used to use "dot only" labels with the distances tweaked so that they only changed color within 2nm or so for VID in VR to be more realistic, however it seems "dot only" has changed to "dot neutral" and the label color does not change. "Symbol only" does work, however it doesn't seem possible to edit the symbol/position/color/range because such a "symbol only" entry does not even exist in the labels.lua file. Is there any way to get this capability back? Or edit the distance at which the "symbol only" label changes color?

My experience has been that AI-deployed flares are vastly more effective than player-deployed flares.

The yaw string is more accurate than the ball. The ball doesn't show actual slip until it's settled down from Newton's 3 forces acting upon it. E.g., bank to the left and you will see the ball swing right (indicating proverse yaw) while the nose reference and yaw string are still straight as an arrow.

Bug caused by the new launcher, it seems. I disabled the launcher and everything's been good so far.

You can see similar problems with the nomenclature used in the controls list. ED seems to prioritize the official terminology per the manual or other resources related to that item or module, to the detriment of the end user which needs more standardization for ease of use.

Wing fires on the B-17 is odd considering the self-sealing fuel tanks. I've removed one from a B-17 wing myself (well, me and like 8 other people because it's heavy af).

Yeah, I'm gonna pass on breaking all those user-made skins for a rudder animation fix that's hardly noticeable. We can't make a single coherent deck without the user-made skins; and half the default skins are for carriers we don't even have in DCS. This isn't MSFS where players just put around alone without the bigger picture of simulating military operations involving multiple aircraft.

There are also various roads that have breaks in them: And the road that should be going through the valley west of Tarinkot ends at a village.

I've read through the manual a few times but am really lost on the functional difference between VIP and VRP. In VRP, I have the target on a STPT, and the VRP is simply a HUD visual cue to start my attack run to the PUP. Nav/steering and CCRP symbology is to the STPT (Target). If I'm understanding VIP correctly, I would have the IP on a STPT, but no STPT for the target itself. Nav/steering is to the IP STPT, Target (TD box) is on whatever the programmed offset from VIP (IP STPT) is. But is CCRP symbology to the TD box rather than to the IP STPT? The manual seems to indicate so, but the picture on page 210 shows the ASL to the VIP and not to the TD box. Follow up to that, if using the TPOD, would the TPOD be slaved to the IP STPT (VIP) or to the TD box referenced from it?

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.