Omni-Directional Env_ProjectedTexture

[Hollow]

So I've been working my way through a lot of the fixes for projected textures, along with implementing what Gary has worked out concerning the grain. But I am looking to create an omnidirectional dynamic light source (i.e cast in all directions) for use for things such as a light from a flame/candle in the centre of the room.

There is a video which employs the effect, seen here:

Though I doubt he is willing to share the code edit (nor the team of C17 unfortunately)

I've been skimming through the .CPP files and reckon it's to do with the FOV angles of the projected texture, as merely setting it in hammer to 360 does not work (in fact it casts no light at all)

Any ideas/suggestions?

[Chopium]

6 90 degree entities in the same spot?

[city14]

I was about to say that...

[Hollow]

Well there is that method, but, wouldn't that be extremely expensive to render?

[Gary]

I can run at 120+ FPS using that method(6 90-degree lights pointing in all directions), though it looks like crap most the time. Overlaping shadowmaps in Source = Bad

I am likely doing something wrong... well, I know using 6 90-degree projected lights to form an omni-directional one is the main problem. We really must do this the right way.

Here is what I got when I tried that method:




Then I made an plain texture for the light to fill in the gaps:




As you can see, I got quite a few graphical glitches. I have applied the parenting fix, jitter fix, and allowed for 7 shadow maps(6 for the light and one for the player's flashlight).

[Armageddon]

I wish people would stop posting all these awesome dynamic light videos, I just want to know how it's done.

[Plague]

I wish people would stop posting all these awesome dynamic light videos, I just want to know how it's done.

env_projectedtexture with code changes...
Problem is getting it to be less laggy is (as far as I know) not possible with the SDK code base.

[MáØ]

Problem is getting it to be less laggy is (as far as I know) not possible with the SDK code base.

I thought C17 had full working dynamic lights o.O

[Plague]

Entirely? I did not know if they do, But I assume it is not old computer friendly.
But maybe I'm wrong.

[Gary]

I never had problem with lag with it after I got my new graphics card(5770).

The real problem is making it look good, it's not easily scaled. It was only intended to be used as a flashlight, never to light a large area. I know how to change the shadow map resolution, but it appears it can't be higher then your view port.
Because of this, the only other way to use it on a large scale is to implement something like PSSM, which requires a good amount of graphics programming knowledge(that few modders have).

[Plague]

Key word, "New".
Do we have anybody with a crap computer who could test out these things XD.

But I might be wrong, I was in the mindset that they were not optimized.
(A fact which made sense since its only used for flashlights.)

[MáØ]

Plague, dynamic lighting is a relatively "new" bit of gaming engines. Why should people wanting to make a game look that good worry about the low end?

[Gary]

They are not greatly optimized as far as I am concerned. Though, I have no problem running it.

I remember, when I used to play Source with my onboard GPU, it's like an Nivida 6000 or something. One flashlight would take more then half my FPS away.

[Plague]

Plague, dynamic lighting is a relatively "new" bit of gaming engines. Why should people wanting to make a game look that good worry about the low end?

Valve, Not that I'm saying I care, just that Valve cares...

[Gary]

MáØ, they had shadowmapping in Halo2 for the xbox and Doom3 had stencil shadows for all light sources.