Halo ce closes even with xfire off

[GoogleCodeExporter]

What did the Exception Report say (if this was on Windows)? Include Fault
Executable Name and Offset.
Didn't give one.

What steps will reproduce the problem?
1.Installed Open Sauce 
2.Started Halo CE
3.Halo CE closes

What is the expected output? What do you see instead?
I expected Halo ce to start.  I see Halo ce start then immediately closes

What version of the product are you using? On what operating system?
Halo1_CE_20120117. Windows Vista Home Premium 32-bit Operating System.

Please provide any additional information below.
Completely uninstalled xfire, and steam is turned off. Closed any other program 
that was unnecessary. Only windows task programs are running in task manager 
and google chrome. Took two screen shots of my processes that are running

Original issue reported on code.google.com by propas...@aol.com on 22 Jan 2012 at 10:08

Attachments:

• TaskM.jpg
• TaskM2.jpg

[GoogleCodeExporter]

Uninstall OS, then completely reinstall HaloCE and the HEK (if you use it), 
then reinstall OS

Original comment by kornma...@gmail.com on 31 Jan 2012 at 8:06

[GoogleCodeExporter]

I have uninstalled Os, and reinstalled HaloCE and HEK twice. Also I am the 
admin on my laptop.  Could my graphics card be the problem? Its a weak card and 
cannot handle shader model 3.

Original comment by propas...@aol.com on 2 Feb 2012 at 3:31

[GoogleCodeExporter]

Try going to your *HCEDir*\shaders folder and renaming vsh_OS.enc to something 
different. This will disable the shader extensions in OS.

Original comment by TheFieryScythe@gmail.com on 2 Feb 2012 at 8:33

[GoogleCodeExporter]

OS is working now, thank you. The F7 key is working too.  Quick question, with 
the shader extension disabled will I be able to play .yelo maps that have 
certain shaders or will they not show up?

Original comment by propas...@aol.com on 3 Feb 2012 at 3:36

[GoogleCodeExporter]

You will be able to play such maps (.map or .yelo, either can have extended 
shaders) but you won't get the graphical improvements on dynamic objects.

What graphics card/chip to you have btw? OS is supposed to check that your card 
supports the extensions but it's apparently missing something on yours.

I've added a user settings option to completely disable the shader extension 
system (revision aaa1db132328805abc9991b3193e4e6da37a9b98), but in the next 
release could you try it enabled first? Just in case it's an installation issue 
(though I doubt it).

Original comment by TheFieryScythe@gmail.com on 3 Feb 2012 at 8:44

• Changed state: Accepted

[GoogleCodeExporter]

My laptops graphic card is an ATI Radeon X1200.

I will test the next installation with shader extension enabled for the next 
installation.

I looked at the 4 scripts that disable the shader extension system, but can 
only find OS_Settings.User.xml. I do not know where the other 3 scripts are, 
and I looked in  Halo CE directory and documents\mygames\haloce\opensauce 
directory. 

Original comment by propas...@aol.com on 3 Feb 2012 at 5:44

[GoogleCodeExporter]

The option to disable the shader extension will be in the next build, it's not 
in the current release build.

Original comment by TheFieryScythe@gmail.com on 3 Feb 2012 at 6:14

[GoogleCodeExporter]

Could you rename your vsh_OS file back to the way it was (vsh_OS.enc), start 
Halo to make sure it is back to having this issue again, then replace your 
d3d9.dll with the one attached to this post.

When you run Halo again you should get a message box saying (I expect) "ps_2_b" 
or something like that. When you click ok, Halo should finish loading (you'll 
hear the main menu audio) but won't render anything because i've crippled it to 
be used for debugging this issue only. If it still closes unexpectedly after 
you click ok, then we still have a problem.

Let me know what that message box says, and whether Halo closes itself or not, 
then do a repair install and rename vsh_OS.enc to something else to get 
yourself back to where you were.

NOTE: Do NOT distribute this dll, it has been crippled and is intended for 
debugging purposes ONLY.

Original comment by TheFieryScythe@gmail.com on 4 Feb 2012 at 1:41

Attachments:

• d3d9.dll

[GoogleCodeExporter]

I did what you messaged. I got the "ps_2_b" message as Halo CE is opening. 
After I clicked ok, Halo CE closed like before. 

Original comment by propas...@aol.com on 4 Feb 2012 at 4:27

[GoogleCodeExporter]

I installed Version 3.0.1 and ran Halo CE and does same thing. I went under 
OS_Settings.User then turned <ShaderExtension enabled="true"> to "false" now 
Halo CE is working normally.  To experiment, I even tried turning each model 
under the ShaderExtension in the script to false and they would make Halo Ce 
close like before too, even with all of them turned false, while the 
ShaderExtension was enabled. 

Original comment by propas...@aol.com on 9 Feb 2012 at 3:16

[GoogleCodeExporter]

Yeah, I know what this issue is now. Even if you card supports up to shader 
model 2.a or 2.b, Halo is still told by Direct3D that it only supports shader 
model 2.0 so during the shader loading phase, it doesn't even try to load the 
new 2.a/b shaders and missing shaders cause Halo to close without warning. This 
only affects cards that support shader model 2.a/b as anything above loads the 
shaders correctly and anything below can't use the extensions anyway.

I have a fix, which will be coming in the next release if it doesn't cause 
other problems.

Original comment by TheFieryScythe@gmail.com on 9 Feb 2012 at 8:36

[GoogleCodeExporter]

Issue fixed by revision 2497d07404bba6ed637fd5fd6c1e058e568a419f (284)

Original comment by TheFieryScythe@gmail.com on 11 Feb 2012 at 2:12

• Changed state: Fixed