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

Yes, works with default UI on Windows XP SP3

Quote:

---

Originally Posted by paladin

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.

---

This.

Quote:

---

Originally Posted by Kornman00

On XP, I believe there is a way to save the Exception Data of which it notoriously Gathers. Try clicking the "View Details" linkish looking thing (IIRC) and see if it lets you.

On Vista its a little different. This difference actually made developing hacks like Yelo more time consuming to debug on my end as the amount of steps involved.
1) Control Panel->Problem Reports and Solutions->View problem history
2) Find HaloCE (or it may be the name of the dll, dx3d9.dll or w/e)
3) Right click->View problem details.
4) Copy to clipboard & pasta in your post
5) ???
6) Fix?
7) Deficit

---

How about people start doing this instead of pulling ideas as to why it isn't working out of their arse

You can inject OS and have it work because none of its DX code gets called. Its only when the game calls it's version of Direct3DCreate9 that OS's DX code is executed. While I didn't use any of the DX resources by default in Update 1, Update 2 does (a la Battery menu system).

:D
Success!

Code:

---

------------------
System Information
------------------
Time of this report: 5/27/2009, 17:04:56
      Machine name: JOHN
  Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
          Language: English (Regional Setting: English)
System Manufacturer: n/a
      System Model: n/a
              BIOS: Award Modular BIOS v6.0
          Processor: Intel(R) Pentium(R) 4 CPU 2.40GHz
            Memory: 1024MB RAM
          Page File: 382MB used, 6545MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
    DxDiag Version: 5.03.2600.5512 32bit Unicode

---

Renamed the init.txt and OS works like a charm.

Just out of curiosity kornman, has the OS sdk changed at all to allow these fixes, if so will there be an updated release?

Bit of proof. It is awesome setting gravity to 0.000 when you are in the air, the physics kick in proper good if you spin around.

So it is xfire_toucan_xxxxx.dll (in this case xfire_toucan_37323.dll) which injects itself into the game. Find the conflict!

Edit: Ok, maybe the dll doesn't directly crash it. I can inject it, but of course it won't do anything without Xfire to work with it (Xfire was closed). I started CE with the d3d9, injected toucan, and then it was fine, despite not having any actual overlay because the key commands in Xfire's settings do not work.

whenever i put the dll into the folder after startup, xfire works but its as if open sauce isnt there. The gravity command doesnt work, and thats the only one i know.

That's because CE can only inject it on startup. And as Kornman has said numerous times, it needs to be loaded before CE loads its code for all of its features to work properly.

Quote:

---

Originally Posted by Kornman00

Update 2 CAN'T be used with a DLL injector. A portion of the new code has to be ran before the game's systems are initialized.

---

Or just use winject and inject it after load up...
it bypasses all errors really. and still works.

Works for me.

Code:

---

------------------
System Information
------------------
Time of this report: 5/31/2009, 14:48:43
      Machine name: SEAN-PC
  Operating System: Windows Vista™ Home Premium (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)
          Language: English (Regional Setting: English)
System Manufacturer: Compaq-Presario
      System Model: KQ513AA-ABA SR5510F
              BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ (2 CPUs), ~2.6GHz
            Memory: 3070MB RAM
          Page File: 1569MB used, 4792MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 10
DX Setup Parameters: Not found
    DxDiag Version: 6.00.6001.18000 32bit Unicode

---

Running on 32-bit, no crash, gravity worked fine.

Worked with my friend too.

Code:

---

------------------
System Information
------------------
Time of this report: 5/31/2009, 15:49:59
      Machine name: DAN-PC
  Operating System: Windows Vista™ Business (6.0, Build 6000) (6000.vista_gdr.090302-1506)
          Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
      System Model: System Product Name
              BIOS: BIOS Date: 10/14/08 13:14:26 Ver: 08.00.14
          Processor: Intel(R) Core(TM)2 Duo CPU    E7400  @ 2.80GHz (2 CPUs), ~2.8GHz
            Memory: 3326MB RAM
          Page File: 1233MB used, 5597MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 10
DX Setup Parameters: Not found
    DxDiag Version: 6.00.6000.16386 32bit Unicode

---

We even played a game, testing the multiteam vehicles and everything. We didn't find any problems. (Except when we found out that normal gravity is 0.003565, when I assumed it was 1)