Nealius

Ghazni citadel is also missing.

The Github explains everything: https://github.com/evogelsa/dcs-real-weather/blob/main/cmd/realweather/README.md

It looks like the calculator I was using assumed 15C. I've found another calculator that allows OAT delta in the calculation. The tanker speeds are an issue when Warthogs and fast jets are operating in the same area. A 10kt variance with temperature changes frome real weather injecting on a persistent server aren't an issue for fighters with excess power, but for an A-10 it could mean the difference between tanking and not tanking at all. We really need the AI to auto-adjust to a standard speed depending on the recipient aircraft. Mission builders can do a workaround with the AI task push to set different speeds but that can clutter the F10 menu or whatever flag triggers are in the mission, and on a server it could be abused by users who aren't tanking.

Campaigns-focused patches are very welcome. It's always a downer to be unable to enjoy a campaign for a month because of an AI or trigger bug that's fixed internally but waiting to be shipped with a larger package.

What's the name of the lua file and where is it located?

In the attached track there are two issues with air start tanker flight pathing and airspeed. 1. On mission start the tanker does not fly straight to its first waypoint. Instead it does a 180 turn away, followed by another 180 turn back to the waypoint, which takes it 12+ miles off course. In previous versions of DCS tankers would spawn flying in a straight line to their first waypoint. 2. Airspeed/Groundspeed/Mach seems to be off. No wind in mission so TAS and GS are effectively the same. According to online calculators like this one, 270KCAS at 20,000ft is 361.7KTAS or 0.588M. Inputting 362kts at 20,000ft in the ME gives 0.54M instead of calculated 0.588M. Furthermore, in the game the F2 info bar says IAS is 264kts, which is 354KTAS/0.576M. Getting the tanker to fly exactly 270kts indicated is trial-and-error because neither the ME calculations nor the actual speed in-game appear consistent. In previous versions of DCS tanker speeds only varied by +/- 2kts. Now it's +/- 6kts or more (I've seen KC-130s doing 234kts when set to do 250kts at altitude). EDIT for point 2: Changing mission temp to 15C gives 0.59M so the ME calculations seem to be correct and account for temp changes, but the tanker is still flying 6kts slower than it should be. tanker-s-turn.trk

"This part of the world" being limited to Peshawar. The mountains between there and Jalalabad are going to create different conditions in Jalalabad. Same for Bagram and Kabul in their valley bowl. Kandahar and Dwyer are also vastly different climates, where the nearest reporting station is Zabol, Iran, at 500m less elevation with different temperature patterns and much higher winds than what occurs in Kandahar.

The site seems to be buggy in Chrome. I've been logged out and when I log in it redirects me to sign in with no error message. Using the same credentials I am able to log in on Edge just fine.

This is still a massive issue particularly on the Afghanistan map, happening at nearly every single airbase even if you're just passing through but not landing. I don't understand why the threads are locked when it's still ongoing.

I tried a new cable and still had issues. Later determined part of the problem to be a dying powered USB hub. I got a new powered USB hub and have had no issues yet, however it seems there are also issues with DCS maxing all CPU cores when clicking slots in MP.

I never said it didn't. I was addressing the question about the stick position.

https://github.com/evogelsa/dcs-real-weather It unpacks the .miz file, edits the weather lua to match as close as it can get to a user defined METAR, then repacks it into the .miz file.

Brightness/contrast binds on the UFC work at the moment, however one of them will simultaneously reset the other when adjust a certain direction. Don't recall the specifics.

Stick is close to neutral in roll, slightly forward on pitch to track straight, on a knife edge pass.

I never claimed that you said it. I inferred there was a trademark issue from the information available because that's typically the cause of cases like this.

JSC is pulling a Glock on trademark infringment? I thought ED always had permission to recreate these aircraft, and in cases where they didn't there was a disclaimer on the loading screen.

Any more thought to adding an altitude setting for this? I would like to have radio transmissions so clients online must use the appropriate radio channels but terrain blocks the transmissions.

Just about every video or photo published, unless it's taken on a smartphone, has been color graded these days.

Just a note, the METAR information being used is from Peshawar, Pakistan, 104km away from Jalalabad. I've been trying to put real weather in my Afghanistan missions but it's frustrating because, for obvious reasons, not a single weather station in the country itself is functioning.

When I checked his .trk as a .miz all the waypoints had the same speed and altitude. Though to y'all's point it would be easier to set it up in a racetrack orbit anyway, especially for rejoin.

Try 274kts GS (220KCAS). 250 is too hard for the Hog. In your replay track the tanker is keeping speed and altitude. You are not. The probe is going through the nose because you drift up out of position. Put the velocity vector on the tip of the probe and keep it there all the way in. There are on the bottom of the nose of the tanker.

Supercarrier is already a CQ module. CASE I comms are CQ comms and not operational comms (which are actually no comms).

Speed in ME is TAS, not CAS. If you want 250kts at 15,000ft you need to program 311kts in the ME. (311KTAS @15k = 250KCAS). But IIRC real tanker speeds for the A-10 are 220-230KCAS, which would be 274-286KTAS at 15k.

We sorely need a thickness/height option to create dust storms at higher elevations.

If the player or group of clients is not going to be in 3 or 4 different places at once, or at least not with such a degree of separation to need wide variations in weather, then why do we need local fog instead of using the timed triggers or zone triggers as mentioned above? At a certain point we're increasing developer workload to chase perfectionism over pragmatics.