Halo 1 & 2 for PC
This topic has moved here: Subject: Patch 1.07 is against remote sound hack ?
  • Subject: Patch 1.07 is against remote sound hack ?
Subject: Patch 1.07 is against remote sound hack ?
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Then wy is it that vorbis.dll still crashes ?
It is not that often anymore since i copied the latest ogg vorbis dll to halo dir.
But it is still happening.

Don't come with drivers blabla, i already have them.
I no this exception happens to a lot of people.
How is it possible that there is still no technical answer from bungie or
microsoft ?

I posted this questions before but i only get the usual questions like state your specs bla bla

When i do i still do not get an answer that gives me peace.

So maybe now somebody knows what is going on ?
This happens since patch 1.07 never before the patch.
Typical microsoft/bungie behaviour, make a patch that is not fully tested !

  • 08.12.2005 2:30 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

you have no idea what you're talking about, do you?
A) you're hardly speaking english
B) the 1.07 hot fix (just like every other hotfix) was to prevent "a malicious user to cause the game to hang on the server". in other words, keep hackers out of your system.
C) the hot fix did nothing to the vorbis.dll or even the vorbisfile.dll in your halo directory.
D) anything wrong in that catorgory was caused by eaither a scratch on you disk that affected instalation, or because you -blamed- up your computer in some way. in any event, the only people that can help you is microsoft tech support
E) if this "happens to a lot of people" then why has no one heard of it before
Just go back under your rock and stop complaining. microsoft knows what they're doing, and have reasons behind it. you, who lack knolwedge of both their tasks and their methods behing them should not go off blaming them

  • 08.12.2005 4:26 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

if i rember right, the sticky about the 1.07 patch said something about a fix for audigy cards.

  • 08.12.2005 11:10 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

@lamwhie

First of all, simple minded "friend". If you happened to take the time to read the articles in this forum you would know that i am not the only one.
However since there is no search option here it is not that easy to find.
And since you never heard of this, it does not exist ?
Have you ever heard of google, or are you anti google too ?
Try google and type this in the search field :
"vorbis.dll halo exception"
And what do you know, it shows results...


And how is it that i never had this problem before untill after patch 1.07

You are just the usual loud mouth person who thinks he understand something without ever
working with the innerside of an os. How often are you on the microsoft tech site ?
How often do you keep track of bugs, flaws and solutions. The only thing you know is automatic updates. Does kernel mean anything to you ?

Anyway, i read a lot of forums and someone mentioned this possibility that there was a flaw in the way halo handles sounddata. Since i can neither confirm or deny this i asked this question here on this forum to see what comes up.

@Mr Ma5B

Thank you, for your comment.

I had before an soundblaster live 1024 from creative and now i have an audigy 2 OEM of
creative. The OEM is just an audigy 2 without IEEE1394 connector and THX certification .
This vorbis.dll exception that i am getting happened with both soundcards.

I guess it will never be solved since i have the latest drivers for everything. To be honest i tried different driver version (older, newer) for all my hardware, basic windows without personal modifications. It makes no sense at all. I left my hardware original at fsb 333. No difference. I ran memtest for days, cpu test. My system never shows any instability. I guess i will have to do some more searching.

  • 08.13.2005 2:04 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT


@ mr MA5B

The game never crashes with vorbis.dll so far during campaign. So i assume that it is online gameplay related.

I searched the hotfix sticky for audigy and found out that there where a few lines added to the config.txt for halo to correctly recognize new audigy cards.

My device ID = 1102 - 0008
My card is not an zs but it is still an audigy 2 so i will assume this is okay.

Here is my config.txt

// Audio cards

AudioVendor = 0x1102 "Creative"
AudioVendor = 0x1274 "Creative"
0x0008 = "SB Audigy 2 ZS Notebook"
HeadRelativeSpeech
EnableStopStart
break
0x0007 = "SB Live! 24-bit"
HeadRelativeSpeech
EnableStopStart
break
0x0004 = "SB Audigy"
HeadRelativeSpeech
EnableStopStart
break
0x0002 = "SB Live!"
EnableStopStart
break
0x1371 = "Sound Blaster PCI"
0x7002 = "SB Live!"


I found somehing about "EnableStopStart" on the gearboxforums.
I quote this from the gearboxforums :

"Here's some interesting info. I was poking around the config file and I noticed the setting EnableStopStart listed under the Audigy section. This is described as "Sound card supports fast calls to stop and start buffer functions." So I commented out this line and tried the game. I still got sound dropouts in the cutscenes, but not so many as before and at different times; however, these cutouts (just like the other ones) always occurred at the same exact times (relative to this setting). So it seems like the problem is due to an some kind of error writing to the sound buffer when using hardware sound. Because the same amount of data is being written to the buffer the dropouts occur at the same times. Not sure how they would have missed this in testing since it seems anyone with an Audigy and hardware sound is having this problem."

Cannot find anything on "HeadRelatedSpeech " or "Break" at the moment.

I will do some more researching.
If i remember correctly, i never had the vorbis.dll exception problem with audio hardware acceleration disabled.
But what is the fun of playing halo without positional sounds ?
I will turn on and off these setting in my config.txt(after making a backup afcourse) and see what happens. Maybe i will find something.
It is funny that i do not experience any cutscene audio dropouts as mentioned in the gearboxforums. I only have the vorbis.dll exception.



  • 08.13.2005 2:49 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

wanna know something funny? i have the same exact sound card.......
no problems here
and i want to appoligize about som of what i said. i'm sick and tired of people blaming all their problems on MS. want to know why MS is the biggeest corperation in the conutry/world/universe? they know what they're doing. saying they don't just aggravates me.
now you can run to your friends and laugh about how i defended the evil imperial empiie

  • 08.13.2005 7:39 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

I guess you have still much to learn...

At this moment i found another person with the same MB as myself with an audigy having the same problem. At this moment i have removed the entry "HeadRelativeSpeech" and playing halo to see if it has any effect. Yet as much that you don't want to here it, there are a lot exploits not commonly known but very effective. As i read the gearboxforums i noticed that there was a lot of talk about the halo port to pc was not up to par when compared to halo for the xbox when it comes to quality.

  • 08.13.2005 8:34 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

while were talking about sound, is there a way to fix the timing on the cutscenes, such as when MC steps out of his cryochamber?

  • 08.13.2005 4:25 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

No. And yes the port wasn't very good. Have you tried re installing windows? Its sometimes better just to start over, compared to tweaking.

  • 08.13.2005 9:46 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Hello everybody,

I removed the "HeadRelatedSpeech" command but i still get the vorbis.dll exception.
I have to say that sometimes it happens 5 times in an hour and then it sometimes does not happen for hours(when i have the time to play for a long time).
I placed the "HeadRelatedSpeech" command back in the config.txt

@Chewy gumball

I installed a fresh new windows and it did not solve the vorbis.dll exception.


@ mr MA5B

What soundcard do you have ?
Is it listed in the config.txt ?
If so you can make a backup of your config.txt and try disabling or enabling these commands

I notice there are only 3 commands for creative cards :
HeadRelativeSpeech
EnableStopStart
break
The break command is where halo stops reading this section of the config.txt and jumps to the next section.
At least this is what i think, please correct me when i am wrong.
So you can try disabling the "HeadRelativeSpeech" and "EnableStopStart" command.


when you put "//" in front of the command it will be disabled.

At this moment this is all i know.

It is to bad that there is no answer from bungie themselfs.
They must no more then they want to tell.
I will search the gearboxforums too but i do not have high hopes.

There is maybe also another possibility : pci latency or pci timer
In the bios. There is this command and it is usual set to 32. Maybe if you
increase it to 64 it may help. but be warned, you can get nasty side effects in other
programs or games or devices. So backup all your imported stuff first to a cd or dvd before trying. I remember this from the time when i had an via chipset (686B southbridge)on MB together with an creative soundblaster live 1024. Horrific i might say.



[Edited on 8/14/2005]

  • 08.14.2005 3:09 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Hello everybody,

I tested this on a server where the ping on average was 80.
My own ping was 34 according to halo.
When i disable the "EnableStopStart" command, i notice the following effect.
While in heavy battle i notice that sometimes my gunfire falls away.
I shoot but i do not here the sound. Also from the enemy the sounds dissapear.
Also when you hit someone you do not here constantly the "tuut" sound that confirms you actually hit that person. So i would not advice to disable that. To be honest, these settings seem to have different effects on different configurations, testing is the best way to find out. I tested this under online gaming. Under campaign during the opening cutscene i do not see any loss of lipsync when the characters speak. Sounds and video run perfectly in sync during campaign and the cutscenes as well.

Bungie, if you people can help, i am all ears




[Edited on 8/14/2005]

  • 08.14.2005 4:37 AM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

You must love the "suffering"...

  • 08.14.2005 9:30 AM PDT