Nobody Special

@fat creason one thing I noticed recently when replaying a track, using the head-tracker to look around caused the recorded jester menu function to register incorrect input.

The temperature is not 35C at 25000'. I believe that is the surface temperature. Grabbed the PDF and I'm reading.

Thanks @Victory205 - I'm aware that the speed of sound depends on temperature and pressure. But I'm not sure temperature alone explains these data; the effect is dramatic, and IAS changes similarly. I didn't expect that. From thermodynamics the speed of sound should vary as the square-root of temperature. A 45C increase from 263K should result in ~8% change (from Vs = 331 sqrt(T/273) m/s, valid at sea level but the proportion should not depend on density). But what I found is a ~35% change in both Mach and IAS. Not trying to do a "gotcha" here - there are other factors, the most obvious being engine performance. I think that pressure is kept constant by using constant indicated altitude (?). Here is the reason I'm interested in this: when facing overwhelming numbers of bandits, my tactic has been to turn cold once I'm Winchester and/or distance has closed to ~20 miles. I'll use AB as needed to reach supersonic speeds, then drop to full mil power to conserve fuel. In Georgia at War, this often results in ~M1.45 or so - fast enough to keep a Flanker in afterburner from catching me. The trick is, since bandits have to use AB and I'm sipping fuel (relatively speaking), eventually they'll run low of fuel and RTB. I'm not sure if the same tactics will work in Syria at War. I'm trying to understand if my (ground) speed really is dramatically lower, or if this is just an instrument effect. I understand that the flight model fidelity may vary between different aircraft (never mind the fact that AI planes can be UFO's) -- I just want to understand the F-14's performance. I just found a useful calculator here. Using that to modify the temperature appropriately, I see that CAS and Mach actually do not change, but TAS does. That is consistent with my observations, and it suggests the F-14 top speed really does decrease by about 35% in hot weather. Interestingly, this also roughly confirms my estimate of the real impact of temperature on Mach: at fixed TAS, changing temperature by 45 degrees results in a ~10% change in Mach number.

I noticed a significant difference in behavior between playing Georgia at War and Syria at War, so I did some simple testing. I set up an F-14B with full fuel and no external loadout, at 25000' MSL and 950 knots which is approximately M1.5. Fly to the necessary altitude, then set autopilot on to heading and altitude hold, maintain maximum dry thrust. Accelerate time, wait for everything to stabilize and note the final IAS. I tested this at nominal (mission editor MSL) altitude and instrumental altitude but that didn't make much difference. At temperature -10C I can sustain M1.7 / 750KIAS; at 0C this is reduced to M1.6 / 720KIAS. At 10C M1.53 / 690KIAS or so. At 20C it's M1.44 / 650KIAS. But at 35C the plane decelerates to M1.04 / 450KIAS. I'm not claiming there is any problem, just thought this was interesting. It is a dramatic difference in performance in hot weather. I'm not sure if this is solely a difference in engine performance, or if the density of air is different under these testing conditions.

Can R-27ER re-acquire like that? Regardless I'd think the RWR should be providing warning if I were locked.

Jammer was off.

Simple BVR engagement: F-14B (there is an F-15C slot, but it was not occupied) against 2 Su-30s armed with R-27ER, -27ET, -77 and -73. The enemy group fired a single R-27ER (not ET) at me. I turned ECM off as soon as they burned through (when the RWR started to make noise again). As I climbed and launched my Phoenix, the launching aircraft turns away by at least 90 degrees, and my RWR went silent and did not sound again. I remained hot on the bandit, climbed through ~45k AGL at M1.2 when the missile hit me. I'm curious, what exactly was guiding it? SARH hit with no illuminator.trk Tacview-20210512-225539-DCS.zip.acmi Cacausus F14 vs 2 Sukhoi.miz

Possibly related - I've mapped my brake lever to both brakes, and (with only a small pull) to toggle the autopilot-on switch. After landing (and braking, which switches AP on while on the ground), I have to use the mouse to reset the autopilot-on switch before the keybinding or brake-lever toggle will work again. Maybe you can try using the mouse to toggle the switches and see if that works?

That's really odd. In the mission I've been using, the bandits are MiG-27s. I've tried P-STT as well as PD-STT, typically launching from 5 to 15 miles, and the missile just goes straight - it's obvious there isn't even an attempt to guide. I use both PAL and Jester-assisted locks. I just set up a test-mission with MiG-21s and sparrows worked well. Odd. Change that to MiG-27K and they don't work at all, even at relatively short range (~5 mi).

AIM-7 sparrows will not track on any target as far as I can tell. I've tested AIM-7M and AIM-7F, mostly against MiG-27s but not exclusively.

I haven't been able to hit anything with AIM-7M for quite a long time now. My typical test mission has MiG-27 targets - don't know if they have internal jammers (they are externally clean). Still an issue in 2.7.

Another crash, this one in PGAW after firing a sidewinder at a Su-25T. I'm not sure if this is the same issue (never had the pop-up before) but the circumstances were similar, and it wasn't GAW. dcs.log.old

I have several great pictures, but this one is a bit striking. Anyone want to guess how I got this? - No photoshop work here. (Yes it is dark, the white forum background doesn't help. Click to enlarge.)

I had 2 crashes with similar circumstances in GAW tonight. In the first instance, I was in a tail chase with a pair of Su-25Ts. I had Jester get STT but he lost it when switching to P-STT so I used PAL to re-acquire. Firing an AIM-7M from 10 miles did NOT cause the game to crash but the missile missed for some reason. The target turned so I rapidly closed the distance and fired an AIM-9M. The game immediately crashed. In the second instance, I fired an AIM-54C from about 30 miles in TWS. The radar lost lock and the missile did not ever go pitbull. I had to turn away due to SAMs but the Su-25T followed me, so after a bit I turned back, locked via PAL and fired the AIM-9M and the game immediately crashed. I submitted a crash report both times. There is an exception trace in the log starting at line 840 (attached). dcs.log

This just happened to me. Autopilot on, starting at ~6000 ft. I engaged full AB, dropped the tanks and climbed to 40,000 steeply at first, then gradually lowering the nose to about 5 degrees. Speed never reached M1.1 and after a while the engines exploded. Very cool effect. (And I love the new sounds!)

Thank you. That appears to solve the issue.

Thanks for the discussion of helicopter rotor returns, it makes sense. I'm happy to learn something new. :)

Don't the rotors provide a return at rather high doppler?

For the past 2 days I can't get DCS sounds to work with certain devices, and I also can't simultaneously get DCS and SRS sound. Here are some relevant messages and errors from dcs.log (in the F-14 free-flight, I swapped the audio output once or twice): 2020-09-27 01:23:48.702 INFO SOUND: Using driver: wasapi 2020-09-27 01:23:48.704 INFO SOUND: Found 5 available audio device(s): 2020-09-27 01:23:48.704 INFO SOUND: 0: ID: "{0.0.0.00000000}.{0ff738b5-8c2a-44b3-a55d-1f161fefc217}", Name: "Headphones (Jabra Evolve 75 Stereo)" 2020-09-27 01:23:48.704 INFO SOUND: 1: ID: "{0.0.0.00000000}.{36f6b5a3-6cd5-4061-bf2a-49b077df479d}", Name: "Headset Earphone (3- Jabra Evolve 75)" 2020-09-27 01:23:48.704 INFO SOUND: 2: ID: "{0.0.0.00000000}.{9637ca02-0e4b-4f28-8a16-d1c503303aa3}", Name: "Headset (Jabra Evolve 75 Hands-Free AG Audio)" 2020-09-27 01:23:48.704 INFO SOUND: 3: ID: "{0.0.0.00000000}.{a4dac6cf-dd1d-4994-bdf6-e5ee4a092d7a}", Name: "Headphones (2- B06 APTX Stereo)" 2020-09-27 01:23:48.704 INFO SOUND: 4: ID: "{0.0.0.00000000}.{eb8f17c6-40b4-4b37-a0e1-46768ecf3611}", Name: "3 - LG HDR WQHD (AMD High Definition Audio Device)" ... 2020-09-27 01:24:18.169 INFO SOUND: Opening default audio device. 2020-09-27 01:24:18.174 INFO SOUND: Driver reports 2 channels with mask 0x3 2020-09-27 01:24:18.174 INFO SOUND: Using 2 channels at 44100 Hz 2020-09-27 01:24:18.174 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:24:18.187 INFO SOUND: Opening audio device "{0.0.0.00000000}.{0ff738b5-8c2a-44b3-a55d-1f161fefc217}" 2020-09-27 01:24:18.188 INFO SOUND: Driver reports 2 channels with mask 0x3 2020-09-27 01:24:18.188 INFO SOUND: Using 2 channels at 44100 Hz 2020-09-27 01:24:18.188 INFO SOUND: Channel layout: Headphones/Stereo ... 2020-09-27 01:25:31.012 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/engines/f110intakeint_01): gain 2020-09-27 01:25:31.012 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/engines/f110engineint01): gain 2020-09-27 01:25:31.012 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/engines/f110intakeint_02): gain 2020-09-27 01:25:31.012 ERROR SOUND: invalid source_params(F14_PILOT_COCKPIT:aircrafts/engines/f110engineint02): gain ... 2020-09-27 01:25:49.844 INFO SOUND: Opening default audio device. 2020-09-27 01:25:49.846 INFO SOUND: Driver reports 2 channels with mask 0x3 2020-09-27 01:25:49.846 INFO SOUND: Using 2 channels at 44100 Hz 2020-09-27 01:25:49.846 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:25:51.503 INFO SOUND: Opening audio device "{0.0.0.00000000}.{9637ca02-0e4b-4f28-8a16-d1c503303aa3}" 2020-09-27 01:25:51.504 INFO SOUND: Driver reports 1 channels with mask 0x4 2020-09-27 01:25:51.504 ERROR SOUND: Driver reported an invalid output configuration! Forcing stereo output. 2020-09-27 01:25:51.504 INFO SOUND: Using 2 channels at 16000 Hz 2020-09-27 01:25:51.504 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:25:51.509 ERROR SOUND: Failed to Initialize IAudioClient: 0x88890008 (AUDCLNT_E_UNSUPPORTED_FORMAT) 2020-09-27 01:25:51.509 ERROR SOUND: Failed to start SND_Renderer. 2020-09-27 01:25:51.509 ERROR SOUND: can't start renderer 2020-09-27 01:25:53.103 INFO SOUND: Opening audio device "{0.0.0.00000000}.{9637ca02-0e4b-4f28-8a16-d1c503303aa3}" 2020-09-27 01:25:53.104 INFO SOUND: Driver reports 1 channels with mask 0x4 2020-09-27 01:25:53.104 ERROR SOUND: Driver reported an invalid output configuration! Forcing stereo output. 2020-09-27 01:25:53.104 INFO SOUND: Using 2 channels at 16000 Hz 2020-09-27 01:25:53.104 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:25:53.106 ERROR SOUND: Failed to Initialize IAudioClient: 0x88890008 (AUDCLNT_E_UNSUPPORTED_FORMAT) 2020-09-27 01:25:53.106 ERROR SOUND: Failed to start SND_Renderer. 2020-09-27 01:25:53.106 ERROR SOUND: can't start renderer ... 2020-09-27 01:27:18.362 INFO SOUND: Opening audio device "{0.0.0.00000000}.{0ff738b5-8c2a-44b3-a55d-1f161fefc217}" 2020-09-27 01:27:18.363 INFO SOUND: Driver reports 2 channels with mask 0x3 2020-09-27 01:27:18.363 INFO SOUND: Using 2 channels at 44100 Hz 2020-09-27 01:27:18.363 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:27:18.385 INFO SOUND: Opening audio device "{0.0.0.00000000}.{9637ca02-0e4b-4f28-8a16-d1c503303aa3}" 2020-09-27 01:27:18.385 INFO SOUND: Driver reports 1 channels with mask 0x4 2020-09-27 01:27:18.385 ERROR SOUND: Driver reported an invalid output configuration! Forcing stereo output. 2020-09-27 01:27:18.385 INFO SOUND: Using 2 channels at 16000 Hz 2020-09-27 01:27:18.385 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:27:18.388 ERROR SOUND: Failed to Initialize IAudioClient: 0x88890008 (AUDCLNT_E_UNSUPPORTED_FORMAT) 2020-09-27 01:27:18.388 ERROR SOUND: Failed to start aux 1 2020-09-27 01:27:19.461 INFO SOUND: Opening audio device "{0.0.0.00000000}.{0ff738b5-8c2a-44b3-a55d-1f161fefc217}" 2020-09-27 01:27:19.461 INFO SOUND: Driver reports 2 channels with mask 0x3 2020-09-27 01:27:19.461 INFO SOUND: Using 2 channels at 44100 Hz 2020-09-27 01:27:19.461 INFO SOUND: Channel layout: Headphones/Stereo 2020-09-27 01:27:19.472 INFO SOUND: Opening audio device "{0.0.0.00000000}.{0ff738b5-8c2a-44b3-a55d-1f161fefc217}" 2020-09-27 01:27:19.473 INFO SOUND: Driver reports 2 channels with mask 0x3 2020-09-27 01:27:19.473 INFO SOUND: Using 2 channels at 44100 Hz 2020-09-27 01:27:19.473 INFO SOUND: Channel layout: Headphones/Stereo I'm trying to use the Jabra headset (with microphone), which confusingly presents 3 different output devices to Windows. I used to use the "Headset (Jabra Evolve 75 Hands-Free AG Audio)" device, but it doesn't work. I can hear DCS sounds if I set the output devices to "Headphones (Jabra Evolve 75 Stereo)", but sound stops as soon as I connect SRS. SRS in-cockpit output works if SRS is set to "Headset (Jabra Evolve 75 Hands-Free AG Audio)", but I don't hear the DCS sound. I've tried re-pairing the Jabra bluetooth headset and turned off exclusive audio in the driver's advanced panel, but that did not help. I have not found any configuration where both DCS and SRS sounds can be heard. This is frustrating as it makes multiplayer very difficult. Please advise.

I have one suggestion: when the player has F10 menu radio messages to transmit, can you allow the message to be re-transmitted? Right now if you send an F10 message while tuned to the wrong channel, it seems like all the messages stop working and you miss instructions. I've done this a couple times and had to re-start the mission. If possible I'd only remove the F10 menu options after the player sees the reply. That way, the player can change their channel and re-try until they get it right.

Ok, makes sense. I pulled into a very nearly vertical dive, so the RWR must have been obscured.

I just played mission 4 of the (very fun) Earnest Will campaign. The F-4 hit me with a Sparrow according to the log. The hit occurred after I had re-committed, because the RWR "warbling" noise stopped around the time I started going defensive. The RWR made no noise from then until the time I was hit. Since AIM-7s require constant illumination from the launching aircraft, should the RWR make noise the entire time? Does it have blind spots?

It's not just "perception" - I have many tacview files for this mission. As long as the A-4s have chaff, my hit rate with AIM-54C is under 25% when launching from around <25 miles. The hit rate was 100% if I remove the opponent's chaff. I don't know if this is due to some modeled behavior of which I am unaware, or an issue specific to the A-4, or a bug in ED's missile logic, or something else. But the behavior is 100% reproducible. I can post a mission or tacview file if that is useful. (Is there a way to attach a file here?)

I've been playing a mission over and over for the past few days. In the mission, the client is an F-14B engaging first 4 community A-4 Skyhawks, and a bit later there are 4 Su-33s. The AIM-54C is almost completely ineffective against the A-4s; if I fire off 4 at around 20-25 miles and ~ 20,000+ ft., if I am lucky 1 will hit a target. I've looked in track files and watched one follow the target (locked in STT in this case, but I usually do TWS), then spontaneously and violently veer of course. As an experiment, tonight I removed all the chaff from the A-4s and tried again. Firing 4 missiles in similar conditions, I had 4 kills. I even managed to strafe the Su-33s on the ground as they were taxiing to the runway. I'm not sure if there is something particular with my mission, or with the A-4 as a target, that influences this outcome. I do recall the most recent patch was supposed to make the AIM-54 more resistant to chaff and/or ECM. Maybe the small size, maybe smaller RCS of the A-4 makes it easier for the missile to go for chaff? Otherwise I don't see how it would ever be effective for the intended fleet defense purpose, in a presumably heavy ECM environment. I'm aware there are issues with ED missile tracking, and I do see the missiles do the "weather-vane" behavior that I think corresponds to that issue. But they still hit the targets. Is the behavior here normal and expected?

In the same mission, non-supercarrier hot start, my takeoff is blocked by 4 static F-18s on the front starboard side of the deck. I guess we're supposed to launch from cat 3 and 4 but it is set to 1 and 2, with player on 2.