I’ve recorded a few instances of poxbursters getting to detonation distance before they make a noise; giving you less than a second or two to register they’re there.
You can listen to it on any headphones/speakers, and afaik it’s the same (I alternate between a soundbar and beyerdynamics).
There might be an argument for saying the sound chip can’t process enough separate audio streams, but given as I bet we’re all on mobo chips that’s more a software design issue than hardware fault.
I suspect that at times there’s no obvious priority between sounds - if everything is trying to hit you then what do you play to the user and what do you suppress? Which I think came out of patch 13, as mentioned above, when they ramped up the number of Elites in packs.
I suspect you haven’t read the thread or understood the request. It doesn’t matter anymore, but if your clip cuts off when the que is played then it will of course look like evidence of a silent spawn. Which is why I asked for uncut gameplay.
But as I alluded, this doesn’t really matter as I went and found satisfactory evidence the issue exists when trying to understand what “acknowledged” means, which you can confirm by reading the thread. I still don’t know what FatShark defines acknowledged to mean, but that didn’t really matter.
I still strongly suspect players are including false positives in their reports, but this nuance is very difficult to convey to a lay audience and difficult to differentiate from legitimate claims.
Sorry fella. You were asking people what headphones they were using, and wondering if the xm4 may have something in common?
I was replying to that with what I thought was a useful example that you could play back on any device you wanted, as its clearly captured at the OS level and independent of playback device. As I understand it.
I’ll see if I still have the clip as it was originally the full round.
Well yeah, because that’s not how evidence works, saying a thing happens isn’t demonstrating that thing, but as I told the other guy, the thread is largely resolved at least until people claim the issue occurs after FS delivers a fix to the issue they say they are tracking.
As in reported in the bug section and acknowledged as a problem by Fatshark. I believe there might be few other reports there of that nature. Plenty of streamers on YT / Twitch have recordings which evidence how persistent this issue is, but then you don’t have to be a streamer to notice it.
You’re still not getting what I’m saying. How do I know that FS’s definition matches what you interpret it as? Right now it could mean, We've seen that you've reported something. and I can’t tell which is the definition they’re operating with.
I’m asking for some removal of your or someone else’s interpretation layer.
You don’t, but no-bugs tend to be marked by Fatshark as: (not-a-bug). Also people who looked at the code of the game pointed out the events which relate to spawning specials do not fire the audio engine correctly.
Fatshark staying silent on the audio not working as intended is another matter @FatsharkCatfish
That seems like the most obvious explanation. Pretty much everything is a high priority threat with the shift in spawn types towards high elite density, so a priority system where everything is a priority doesn’t work super well.
Its like a Ryanair flight; upgraded passengers get to board first, but pretty much everyone upgrades for hand luggage allowances
I wonder if elite sounds could be capped for large clusters - if there’s a group of 6 Maulers in close proximity, should it de-prioritise audio after the second (or third) one, so you can still determine “Is it 1 elite or multiple elites” and get some slots freed for other enemies.
Also, less mutant shouting could help. I don’t think a near-constantly audio cue is needed for them; give them a moment to rest their vocal cords!
EDIT: Also, thanks for posting the link of the recordings. I haven’t seen many clips of silent specialists, so I wanted to see/have a listen for myself
Atrox MK VII tactical axe 2nd attack in the chain has very low range and constantly misses even at closes range.
There is reports since October. Someone said it is like that since beta
Guess what?
Still misses
Another example: Charmed reload trait on the stubbers - how long already it has wrong description?
Who knows, but more than 6 month…
acknowledged too
Acknowledged means that Sharks see the posted issue as not working as intented. Simple as.
If it is working as intended, then you get “not-a-bug” flair on it.
If they need more info you get “need-more-info”
If it is due to player tampering with mods, then it is “mod-related”.
Kaerakh, I would suggest you to read few of the topics where the issue is being tagged by players, in some cases look for the the blue “dev” flair next to the user avatar in the thread, one of the devs took his time and kindly explained some behaviours of sound engine to the playerbase.
Long story short: sound engine is not working perfectly and they are trying to get it running smoothly again.
Care to elaborate?
I just expanded on the explanation provided by Jan, as you’ve replied to my previous answer and I do not like to leave stuff unfinished.
I am aware this is internet and written communication, which is lacking per definiton at times, but your reaction came to me as rather rude.
I’m not really interested in relitigating an issue I’ve already confirmed multiple times that I’ve conceded. I’m sorry that you feel it’s rude that I’m irritated that you’re badgering me with items that are irrelevant or addressed in posts you skipped, one could say it’s rude to do those things as well. Feel free to have the last word.
There should be an option to mark the thread as solved (regardless of where it’s posted), but barring that you could change the thread title and unfollow the thread.
