Did they fix Sound Card issue?

[Mordoth]

The last time I tried to play (and I'm not sure if it was June '07 or '06), I wasn't able to log in because it would get stuck at a certain point in the log-in process and the issue was identified as being a problem with the SoundBlaster/Audigy card and disabling or using on-board sound cards allowed log in.

Just wondering if that was ever fixed?

[Deth]

Hey Mordoth Long time no see. I have a Sound Blaster Extreme Gamer and I can log in just fine with it. I did have a few problems when i first tried logging into blight with the new terrain client fix, not sure if it is sound blaster related or not and others seem to have the problem also, but that seems to be cleared up now.

[Vaz]

Disabling loading screen seems to fix it.

/setpref useLoadingScreen false

[Mordoth]

Well, I may see about logging in to visit Istaria once again when my holiday break begins at school. Not a lot of time otherwise between school and working full time. Just didn't want to have to pay a months subscription and be unable to play.

Is there a free trial for former players to check out Istaria again?

[Vaz]

Disabling loading screen seems to fix it.

/setpref useLoadingScreen false

Correction: This doesn't work.

But disabling soundcard via Device Manager works and is fast and painless.

[Mordoth]

Correction: This doesn't work.

But disabling soundcard via Device Manager works and is fast and painless.

so it's not been fixed?

[Vaz]

so it's not been fixed?

It hasn't.

[gopher65]

This bug still exists for me. I have a Creative Audigy 1. I hang during ports or during log in *if* I have my soundcard enabled.

[Kumu Honua]

And it will never be fixed.

Soundblaster is the one with the problem. Not horizons.

It is a known flaw in soundblaster cards.. (Also known as the screech of death)...

[gopher65]

Yup, I have issues with other apps too. None quite as bad as HZ though. This didn't *use* to happen to me in HZ. Something changed a month or 3 before the sale to EII that brought this on for me in particular. I didn't update any drivers during that period (or install any significant software that I recall), so I figure it was caused by either a windows patch or a HZ patch. I know other people had this issue right since launch, but I never did.