UPDATED (2x): OpenSauce and Halo CE Crashing *PLEASE TEST FOR FEEDBACK*

May I ask, what happens if you inject the OS dll after you launched the game with Xfire? I'm curious if they can both work at once. If they can, then that's something that Xfire needs to look into doing, like Steam.

*sorry* i didn't post about my prob earlier. it crashed when i booted up. i'm running vista x64. core 2 quad, 4 gb ram, evga 9800 gtx, evga 780i sli mobo.

thank you VMware. ima boot up all of my VMs and test this to see how it runs. :)

i'll get back to you asap...


~Scooby

Scoob, make sure you're not using Xfire and check that there's no init.txt in your CE directory.

Also, does Halo crash immediately on launch, or does it load and then crash before the main menu?

Edit: If you have the dll error, then download the new OS d3d9 in the first post. There was a mistake during compiling which caused to ask for d3d9x_37.dll

There you go Jcap.

I opened up halo CE first.
Then injected it.

http://www.xfire.com/video/c59f8/

Offtopic here, but is there a list of commands that i can use with OS? I have no idea how to make it any different than reg CE

Quote:

---

Originally Posted by supersniper

There you go Jcap.

I opened up halo CE first.
Then injected it.

http://www.xfire.com/video/c59f8/

---

Well there we have it. Xfire doesn't know how to hook a game properly.

I'm going to guess that if it Xfire could look like Steam, both would work.

Xfire should be injecting itself into the game after it has fully loaded, much like Steam does. This is a problem with Xfire's programming, not with OS or any d3d9. No matter what you use, Xfire will crash the game with a hook in the folder. This is just shitty coding by them.

I'm considering making a post on their forums about it in the feature requests section. They should absolutely do it the same way Steam does.

I wonder if this happens for all games. It probably does. It might be the reason why SoftTH (Software Triplehead) disabled Xfire from hooking into the game - because it crashed with everything.

Success!

I deleted init.txt from my CE directory, and everything worked! I tested OS on one of the maps in the Infernal Map Pack.

Also, I request a list of commands, as well. Speed doesn't work, and I can't tell what does or doesn't.

Ok, so it turns out that you can inject OS after Xfire has loaded, but Xfire cannot be injected after OS is loaded. Interesting.

I noticed that if you open Xfire after CE has loaded, it will immediately inject itself. So, I then started CE with OS, then launched Xfire. A few seconds later, Halo crashed.

There has to be a conflict that Xfire has, trying to modify something that OS has already modified. OS can work with whatever Xfire hooks, but Xfire cannot work with whatever OS hooks. But what? Is it possible to find out?

Code:

---

------------------
System Information
------------------
Time of this report: 5/30/2009, 22:22:52
      Machine name: SCOTTSTATIONARY
  Operating System: Windows Vista™ Ultimate (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)
          Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
      System Model: Maximus II Formula
              BIOS: BIOS Date: 07/21/08 18:05:22 Ver: 08.00.14
          Processor: Intel(R) Core(TM)2 Quad CPU          @ 2.40GHz (4 CPUs), ~2.4GHz
            Memory: 4094MB RAM
          Page File: 4165MB used, 4206MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 10
DX Setup Parameters: Not found
    DxDiag Version: 6.00.6001.18000 64bit Unicode
  DxDiag Previously: Crashed in system information (stage 4)

---

NO ISSUES

64bit BTW.

e.

Quote:

---

Originally Posted by ICEE

Offtopic here, but is there a list of commands that i can use with OS? I have no idea how to make it any different than reg CE

---

This.

Also if you use the dxtweaker to use con's filter effects or the camo fix
just inject the .dll after halo ce loads and it will work fine and run the halo camo patch.