FoxTwo

If you're not having fun maybe you should take a break.

Good call. Just recreated the issue and closed the sound module. Restarted it, had to fiddle a bit with pausing and resuming the sim to get the data going between the two again but once it did, the issue persisted. So I guess the sound module is out as a potential culprit.

Thanks for the update at least.

It's built into the game now there's no reason to run viacom pro. Heatblur just has to go back and flag the audio properly for headset/helmet along with the RWR and sidewinder tones. ED has been going back and fixing it on modules I've reported the issue on including the F/A-18C, F-16C and F-15C.

A trackfile wouldn't help, I've got one saved from when it's happening and closing the simshaker for aviators system tray process and restarting the application fixes it, even in the track replays. Output is set to sound, and so there's the sound module to factor in as well since I have it going to an amplifier that feeds a transducer. For me it's 100% repeatable by hopping in the F-14 instant action mission 'take off', playing with the flaps a bit, which will work normally. Then hop into the F/A-18C instant action mission 'ready on the ramp', play with the flaps, exit, hop back into the F-14 instant action mission, play with the flaps and you get a 'blip-blip-blip' sound. Since track files don't work, here's the output from my audio device recorded with audacity's wasapi mode to prove I'm not just losing my mind. f-14_flaps.zip

Yes, but they have to update the module to fix it. I reported it as a bug.

I'm still having the issue where if I switch between modules the flaps audio loses its mind until I restart. I just get a stuttering on-off-on-off-on vibration instead of a smooth vibration until the flaps movement is finished. It's even impacting in-game DCS sounds, audio routed to headset/helmet is getting cutoff. Instead of "ready pre-contact" I'll just hear "read..." and the betty sounds from the F-18 will say "flight" instead of "flight controls, flight controls". Closing and restarting the simshaker for aviators module fixes the problem. Sound outside of DCS (SRS) is normal and plays just fine. I think it's impacting sounds over a particular length maybe? I don't know. I know it becomes a systemic problem that only fixes itself when I close and restart simshaker for aviators. I use multiple sound cards in my machine, the on-board realtek for simshaker audio, a USB adapter for headset/helmet/comms, and an external USB DAC for 2.1 through speakers.

2070 super will be marginally faster than the 1080ti (5% maybe).

It's not just the sidewinder, it's the RWR and Jester audio too. All should be going to the headphones/headset and are instead registering as cockpit sounds.

Likely but temper your expectations. Regression bugs happen all the time, and introducing lighting engine changes isn't a small thing. Big push for 2.5.6 is probably the supercarrier so anything that impacts that EA release will be moved out if it causes a delay.

F-15C sidewinder and RWR tones are not being routed to helmet/headset audio and are going to the speakers. Betty sounds work as expected and are heard as headset audio. This was reported and fixed on the F/A-18C and F-16C last week. Would love to see (hear) it in the F-15C as well.

I'd settle for just proper harrier support period.

They're never going to have the exact same reading at the same position but it should be closer than that. At 50% throttle with the throttle locked together my warthog reads 8172 8140 So yeah I'd at least talk to TM. Hopefully you're within the warranty period.

Drop it into IFA and leave it there.

Which I think explains the claustrophobic feeling of wrongness on a full deck. Too narrow like you're shoulder to shoulder inside a packed subway car.

From an ACM radar mode video I was watching they said that sensor select right would exit ACM mode but it seems like the only way I can exit ACM is to hit the button on the MFD. Also how do I recenter the tpod? In the harrier it's NSW/undesignate but that doesn't seem to work in the F-18.

It's not lost entirely, it's just based on name. You can go into the : Saved Games\DCS\Config\Input\aircraft-name\joystick find the mapping for your old stick names, then rename them with the names of the new sticks.

If you're looking for a more permanent solution I'd recommend the springs I linked earlier. https://www.primeline.net/sp-9602-ext-spring-716x-1-12x-047-steel-single-loop-closed I just got mine today and the centering force is significantly better. No loss of travel, but it takes a small amount of additional effort to move the pedals.

You'll probably want to click "reset windows name/calibration" as well.

Thanks for fixing the sidewinder helmet sounds. It's a small thing but I appreciate how quickly it was addressed.

I can twist mine by small amounts as well if I grip it tightly, so don't worry. But do follow the recommendation and remove the screws to prevent damage to either the stick or the base.

Oh man, I can't thank you enough for that. I can get rid of my jerry rigged taped splice nightmare for $8 shipped from Amazon. I'll still get a cable from virpil eventually but for an immediate solution that's fantastic. In case anyone stumbles across this post looking for the info, you want a Logitech cable for the MX518/G400/G1/MX500/G100/G300/MX51, and you'll have to swap pins 1 and 3 (red and green wires). Other than that it plugs right in.

Ok just confirming that this is an issue. ED fixed this on the F/A-18C and the F-16 in today's open beta update.

Nellis AFB is 28.01 mmHg but the F-14's altimeter stops at 28.10. This is probably accurate but I just wanted to confirm.

It'll be fine, the majority of the stress on the cable is mostly from constant movement and not from bending it in one place. There should be space to put it in the cavity so it's not pushing on the PCB but even if it was, it shouldn't cause a problem.