Shimmergloom667

I just spend an evening with the squad (4 persons tonight) firing -E and -F Mavs entirely without issue - what problem are you experiencing?

They work fine, they just dont have tone.

I can't enjoy the software if it has falsely modelled systems. And why should my enjoyment be worth less than yours, who may be satisified with some half-baked stuff we have in the Harrier as is?

I can refuel all of them, but some modules I don't fly as regularly and need a bit of Zen to get right within, say, 2 or 3 tries. Hornet & Viper: super easy, I do it for relaxation Tomcat: easy enough, but I don't fly it terribly often A-10: view of the refueling lights a bit nasty, but given its docile nature - no issue Harrier: my Nemesis, but after spending a week doing little else I can do it pretty comfortably now M2k: about the same as Hornet, could probably do it sleeping Jf17: surprisingly difficult due to pitch sensitivity. It could use the Viper's FLCS change when refueling

No issues with my squad either, running on dedicated server. Cleared Contact consistently within 0.1nm aft of tanker, no display issues of hoses.

No

My buddies in the squad and me find the Hornet to be way floatier in close with the SC as well. I didn't crosscheck with old Stennis, tbh, so one would have to do that first to rule out imagination.

In TWS, the undesignate button (which is NWS as well, on the ground), designates targets. The function is aptly called undesignate-to-designate. That shouldn't happen on the ground in the first place (radar silent with wow), but sometimes it does happen, and sometimes it bugs targets way outside of any radar acquisition cone.

TMS down returns it to SPI, which is steerpoint, which is correct behaviour.

So, my sound driver indeed was the culprit: one of the SteelSeries Engine updates must have either damaged or updated the sound driver, but I thought it was DCS since it seemed to have been working elsewhere and a repair somehow seemed to kinda fix things. Full uninstall and reinstall (so far) fixed my problem for good. Thanks to all for your valuable input!! :)

Thanks a lot, c0ff! I will reinstall my stuff later tonight and keep you updated on my findings! :)

Huh, so that sounds like a driver issue... that would also explain why a friend said, that the Hornet video for him was left ear only (which is strange considering the log days "front right"). I am still getting both ears, but then the SteelSeries headset is a virtual 5.1 or 7.1 thingy, so that would explain that. OK, will try reinstalling drivers when I come home from work, thanks already!

Thanks for the tip - I had uninstalled the Nahimic App earlier already, since it interfered with Voice Attack. There was a Nahimic service still running, unfortunately stopping the service didn't change the behaviour. Thanks for chiming in, though, much appreciated!

The same happens in other modules as well: here I am in an F-18, without ambient sounds, without switches clicking. As soon as I start the engine fire test, and thereby starting some sound file, the switches and ambient sounds work as well. The engine fire test sound stops and immediately all other sounds start fading as well:

Here is a Video of the phenomenon. I have no sound mods installed. As soon as ANY other sound loads, the ambients shortly work - like when I push the primer pump, I can hear the sound for it, and then I can also hear ambients and the circuit breaker buttons, which subsequently fade to nothing again. Also the sound for the inertial flywheel doesn't sound correctly, but once I start the engine I can hear it. Additionally: as soon as the engine is running, I can hear button clicks perfectly well. As long as SOME sound is playing, all these small ambients seem to play as well.

Additionally, even after a repair, ambient sounds strangely fade: I just hopped into the cockpit of an Fw190, and once in the cockpit I hear ambient sounds (wind etc) and hear the "click" sounds when I press circuit breakers, but the sounds get lighter and lighter until they fade to nothing. When I cycle through the F2 view (its an instant mission), I get engine sounds of other planes, and switching back to my own I get "click" and ambient sounds again, which fade after a few seconds.

Since OB 53756 I consistently don't have sound after booting my PC unless I run a repair. I am running SteelSeries Arctis Pro Wireless Headphones, they are the default device in Windows. When I start the game, there is no menu music, loading a mission gives no ingame sounds whatsoever. Alt+tabbing into other programs gives working sound, SRS works as well. When I subsequently close the game, run a repair and start DCS the problems stop - I am greeted with menu music and ingame sounds in a mission. Attached are a DCS log after a start of the game WITHOUT sound and a log WITH sound, after starting a game having ran a repair before. dcs_without_sound.log dcs_with_sound_after_repair.log

Maybe, maybe not. It's not like we are scoring points for something. :dunno:

If you have never witnessed badly designed user interfaces, software implementations and/or hardware limitations in the military, then you have served in the single one on this planet that doesn't suffer from said things :dunno:

That is the case, though, just look at neither the A-10s integration having an offset function like in the Hornet, nor the Viper having one.

Sounds like he didnt spend time in any military, ever, tbh :D

You absolutely can. MAV takes priority for FOV change on Hotas, though.

No

Set the INS to IFA - in-flight alignment. As long as you have valid GPS it will align the bird perfectly well. Also see: https://forums.eagle.ru/showthread.php?t=283532

TMS aft simply undesignates and should default to the standard SPI, which in the Viper is the STPT. So basically: CZing the TGP sounds correct to me. That is correct as per RL.