OpenSauce Post Processing

The ingame switcheroo isn't meant for constant toggling of effects, it's there to 1) provide global effects that are set once and used all the time, and 2) provide a testbed so that developers can rapidly test their shaders without having to recompile their maps and restart Halo for every tweak.

ATI 4850 here as well.

Quote:

---

Originally Posted by FireScythe

The ingame switcheroo isn't meant for constant toggling of effects, it's there to 1) provide global effects that are set once and used all the time, and 2) provide a testbed so that developers can rapidly test their shaders without having to recompile their maps and restart Halo for every tweak.

---

Considering we do have to turn off halo (pp_unload and then changing the settings file's effects, then typing pp_load doesn't work) it's still a lot of work just to add a simple change in the effects that a person wants to have displayed... I also see a possible implementation of my numpad thing with PostProcessing so we can possibly disable and enable individual effects. In fact, I think I'm going to add my numpad to PP so I can use both.

I can already think of some sick sp levels that combining my little thing with Post-Processing would work amazingly with.

Also, my problem with motion blur isn't related to Usertool at all. Just the effect itself.

e: Oh and there's some other stuff I didn't mention.

What happens when you pp_load? If your previous effects return then there's something wrong in your settings file, in which case post it up and lemme see.

Nvm, it works just fine. I think that it's just one shader takes precedence over another some times.

Is there any chance of an FOV hack being enabled as well with this?

Do you mean changing your FOV? Because thats a default part of OS2, accessible by pressing F7 ingame.

Quote:

---

Originally Posted by FireScythe

Do you mean changing your FOV? Because thats a default part of OS2, accessible by pressing F7 ingame.

---

Perhaps he wants a 3p view in OS.

First thing that would need to be fixed is the third person targeting...

I'm considering adding 4 more blocks to the shader_post_process and instance tagsso that float2/3/4 values can be changed in the tag rather than in the code, but this would break any current shader_post_process tags that are around. So, if anybody has any desperate need to save their shader (if say, you've compiled your shader and no longer have the source) then let me know, and I can whip up a quick conversion program.