EVE Information Portal

Well the workaround works fine (maybe he set it in xonar panel instead in windows properties ? these are two different things).

So for other folks:

You must set the frequency for shared mode in windows. Not in xonar panel.

Every Cloud I have encountered, whether it be a WH gas site, or a WH sleeper site with clouds, has the detrimental effects described previously.

Windows 10 Pro, 64 bit
Intel core i7-2600 @3.40 GHz
16GB RAM
AMD Radeon HD 5700 series


at this point i have just set my graphics to "******" in order to be able to function normally in the game. Before the patch, everything was set to max with zero issues.

I'm not sure what you guys did to "improve" cloud rendering, but you went the other way with the end result.

The Venerable (Force Auxillary) and Vanguard (Carrier) Serpentis capital ships are accessible through the skill certificates, Capital Armour Tanking being one of them.
They have no icon, and the exact same stats/requirements as their respective Gallente capital ships, and dont show up on the "Required For" tab on any skills, making me think they arent meant to be there.

Also the 3 Serpentis capital ships arent showing up in the variations tab for the respective Gallente caps

Does that mean you cannot switch to a higher sample rate even if you want to?

I'm still wondering what it actually means on the CCP side that the Asus card is trying to run at a sample rate not supported by eve. So which sample rates ARE supported by eve, since I haven't found a sample rate that eve would refuse to output sound. It just kills everything else. So while I appreciate all the efforts, from an explanatory and logical point of view, it doesn't make sense.

Please take the time to bug report when this happens, so CCP gets your setup. It's obvious for me, that this is a technical issue. But according to CCP Darwin the problem is currently assigned to the content / artist team in order to tweak specific sites only.

Bit late but here are my system specs for the clever people (devs)

Motherboard: Asus Maximums VII hero
CPU: Intel 4790k stock
RAM: 16GB DDR3
Graphics: AMD R9 295x2
Sound card: Creative Soundblaster Z
OS: Windows 7

I should also mention that I just tested the workaround and it works. However it's worth noting that nothing has changed settings wise in windows (that I know of) since the update and it seems to be Eve related. I would be happy to try some other ideas via email or even arrange a Skype call for troubleshooting. I shall find out tomorrow (later today as it's 0202 local time) if it's fixed sound with the other clients running.

Kind Regards

Thor

The time it took you to write two posts would have been more than sufficient to submit a bug report and add the DXdiag file to it, which gives much more detailed information about your hardware configuration than the few things you just mentioned.

Speaking of which, will there be an actual fix for the sound thing or will the current "workaround" remain the only solution from here on? Because all things considered, this has nothing to do with our configurations but how EVE is handling sound, since that's the only thing that changed.

I've verified that turning off the "effects" switch will also inhibit cloud rendering without turning down shader quality. After turning off the switch, you'll need a session change (warping, docking, jumping) for it to take effect.

How is that ironic? The sound thing was/is specific and mostly related to people running dedicated sound cards, ASUS apparently in the majority of it, but as reported other dedicated sound cards are affected as well. But certainly not all of them. If it was every single dedicated sound card, I'm positive we would have seen MUCH more people posting here, and the issue being much faster resolved too.

The possible argument of "people not using dedicated sound cards much" is not going to cut it because
a) those people who play eve online with a fairly old machine likely already busted their onboard sound long ago and moved to a dedicated one, especially when some people get the idea that the sound card is going to unload stress from their CPU (which is only partially valid). Just because of that, I'm sure people have put in a dedicated sound card just because they could.
b) Considering the eve online population, I'm fairly positive that there are more tech savvy playing eve than not, which also caters to some enthusiasts of all sorts. This ranges from the audiophile (and audiofool) area over people saying "I want everything dedicated in my rig, because yes" up to people who like to use separate inputs and outputs for their devices (aka using one soundcard hooked to speakers for game sound while the other uses some earhook headset for VoIP. Let's not talk about people having some external hardware for their streaming setup, or for people who do music production.

Those are just assumptions though. Only CCP statistics showing what percentage of the player base uses a dedicated sound card (or has one installed - which are two different things) and showing how many of them are ASUS / affected cards would make any of that point valid. My main notion remains; if this was a more widespread problem, we'd be on page 60, not 6.

Back to the clouds ; If EVERY single machine or a vast majority would be affected, then
a) we would see a LOT more complaints
b) It would likely never passed QA. I'm not convinced that every single QA person and every single CCP Dev uses the exact same rig at work. I could also think such a problem would have been pointed out on sisi. It's not like CCP ignores every single thing posted on sisi feedback on purpose contrary to popular belief, before you bring up that point.

So again it makes sense to gather specific bug reports (with dxdiag info among other things) through an interface with a team that is hired to do nothing but sit there and go through bugs. The forums aren't the right place for that. Sure, double is better (even triple, if you want to count reddit, quadruple if you want to count twitter / facebook) but it's always important to start where it's the most useful and the most reasonable.

So yes of course you can replace my "sound" with "clouds" as you so wittily did, but it doesn't change the fact that both don't affect the majority of players. Else this topic would already be bloating to dozens of pages. It doesn't matter if every cloud affects you. If you want them to fix it faster, you can do one of two things: provide them with every possible hardware configuration to test or (more reasonable) file a bug report so they get the specific things. Only then can they pinpoint common culprits and see what happens with that.

By the way, you said you were done ;) Ironic you still posted.

You have the code with regard to clouds, and sound, when both worked perfectly before the patch.

This is all the information you need. Simply apply it, and put things back the way they were, then leave it alone.