OpenSauce Post Processing

Sorry where do I extract the two folders in the .zip to?

The contents of the "Halo CE" folder go into your Halo CE directory. The "OpenSauce" folder has the source code, for people interested in how it works.

Oh thanks alot

ok after running i get the Missing DirectX file prompt. and after following

Quote:

---

Originally Posted by FireScythe

I doubt it, this only uses colour information which is easy enough to get. Something like ambient occlusion would require depth information and maybe normals, which would be difficult to get, if possible at all (as far as I know).

Oh, and the missing DLL is because you need the latest DirectX release.

---

The website is telling me that my Windows isnt genuine :\ and it wont let me download the update. (which is odd considering I ordered this Windows Vista off the MS website).

Edit: Its k I found 3rd party source.

Edit 2: FFFFFFF----


Its not k, Its asking me where I want to extract the DirectX files too.. in which I have no fucking clue.

Edit 3: Its k, I found another 3rd party source with an auto installer , pheww.

Is it possible to have effects only work for specific assets?
IE: All spartans or weapons or vehicles on screen have a specific effect to them?

FireScythe: Compile using "Release" configuration. Will result in a smaller DLL, faster code and won't require the debug DX DLL.

Nice to see something come out of OS :). I'll check out the code later and see about adding it as an example to the next OS SDK release.

But yeah...besides just postprocessing what Halo has already created, there isn't too much you can do graphical wise without changing the game's own rasterizer code.

Oh this is a release build, and the DLL it ask's for isn't the debug version as it doesn't have the "d" suffix.

Apparently Microsoft seperated D3DX to a seperate DLL in February 05 and have have been incrementing its version on every update, with a new DLL. So as this build asks for d3dx9_41 (March 09 SDK) and the original OS asks for d3dx9_37 (March 08 SDK ?) it must ask for the specific DLL version from your SDK. So it might be worth pointing out what DX SDK to build with for OS2.

Well, not debug, but for whatever reason when compiling with the DEBUG condition (but not with the debug libs), it causes the resulting DLL to link to the specific DX DLL.

If you search the Debug build of the Yelo DLL for that DX DLL, you'll find the specific DX DLL name. However in a Release build it will just be the generic DX DLL with no specific version appended.

I haven't upgraded my DX SDK since Nov 2008, but I'll probably get the newest DX SDK August mid-month.

Hmm, I don't know what's going on then. I've compiled my code using a fresh copy of OS as a release build and its still using d3dx9_41.

I've made some changes so that the motion blur cache uses less texture memory so if you've had trouble with it, try the updated one:
Download

What the hell is an .iwd file?

yah i think he uploaded the wrong thing or something :|