I was sure I had :ugh:, and i can't repro that bug here. It was just removing a redefinition of an int32 and removing the default setting intialisation from Initialize() wasn't it?Quote:
Originally Posted by Kornman00
E: In CameraFov.inl that is.
Printable View
I was sure I had :ugh:, and i can't repro that bug here. It was just removing a redefinition of an int32 and removing the default setting intialisation from Initialize() wasn't it?Quote:
Originally Posted by Kornman00
E: In CameraFov.inl that is.
Still gives the black screen as well.
Nvm, Firescythe knew the error I stated.
I don't really know how to compile dll's, would you mind uploading any changed files?
Also, how exactly do you load the effects?
I tried pp_set_effect_active pp_visr and it did nothing.
It's been established that this is an old FOV bug, where you go ingame and change your FOV to fix it.Quote:
Originally Posted by Pyong Kawaguchi
The most recent DLL is included in the last build. To set up external effects you edit the PostProcessingSetting.txt to add an effect that uses the PP_Visr shader. Like so:Quote:
Originally Posted by Pyong Kawaguchi
After saving the settings file you can either restart Halo or open the console and use "pp_unload" then "pp_load" to reload all external post processes using your edited settings file.Code:[Shaders]
Count: 13
[0]
Name: PP_Bloom
[1]
Name: PP_VISR
[2]
Name: PP_DOF
...Other shaders...
[Effects]
Count: 3
[0]
Name: DOF
Indicies: 2
Render Point: 2
[1]
Name: VISR
Indicies: 1
Render Point: 2
[2]
Name: Bloom
Indicies: 0
Render Point: 3
The halo script/console commands for changing effects can only be used with maps that have tag based effects compiled into them, such as the damnation_pp map included in the most recent build.
I should point out that apart from the bloom shader (which you would typically want to be always on), the other shaders included are only really meant to show what kind of things can be done using the post processing extension so that map makers can see what they can do with their maps. Although, in the case of the VISR effect, that would be better suited as a coded subsystem to allow more control than Halo script would allow.
Will there be a way to load specific Pp shaders without them being in the map itself in the future, via console.
e: I'm using the latest build and changing the FoV did nothing to get rid of the black screen.
I have no plans to put console commands in to manipulate external effects myself, since I only intended for them to be used as always on effects and as a quick tesbed for developing internal map effects. Though saying that, if someone else was to add such commands to turn external effects on and off in future I have no problem with that.
If anybody's interested, shaders aren't applied directly to the scene, they are applied through an effect object that can have a chain of upto 32 shaders to create more complex results, which means that a command to toggle en external effect would still require the effect to be defined before hand in the settings file. Applying individual shaders such as PP_VISR.fx on the fly would be ill advised.
As far as the black screens concerned......:gonk:.
Im using the HD5850 as my gpu, I wonder if they process motion blur differently?
ATi 4850. Perhaps you're using something in the motion blur that is Nvidia specific? idk what though.
I need to determine whether it's specifically the motion blur thats the problem, or if its the render point that is the problem. So if someone with the problem could do the following that would be helpful :).
1. Download >>this<< and extract the two files into your shaders directory (its a settings file and a red tint shader). Backup your settings file if needs be.
2. Start up halo and turn off motion blur using "pp_motion_blur_enabled 0" in the console.
If the screen is tinted red then it's a motion blur specific problem, if it stays black then its a render point problem.