Unvanquished Forum

You said there are new shadows but they don't seem to work for me

I've taken the new .zip file and extracted it over the old unv but i've seem to of lost shadows all together (except for the blobs)

Help me out please...

Please describe this further. Which renderer are you using? Did you set the cvars I listed in the article?

i click on deamon.exe like always and started a test server fired my gun while in third person view and saw no shadow from the gun flash, normally there would be but now...nope.

I had alpha 16 and i just overwritten it with alpha 17.

Also i tried to type in cg_playershadows 1 but it didn't work, it said cg_playershadows didn't exist.

Shadows look very good, but I have noticed a small problem; it is as if the models (player models) shine and illuminate the map in its path.

also when I activated the shadows, I perceived a slight drop in fps. (wich is logical)

And a few question:

r_smp, good for something?.

cpu or gpu? which one is responsible for calculating shadows.

I guess you agree with me that modern computers are real monsters, it would be fantastic that the engine could take well advantage of modern processors, and separate some processes in different threads (I'm thinking of the work of calculating the shadows)

Congratulations.

Don't extract it over an old copy of Unvanquished. You may end up loading old assets or code. Just extract to a new directory and run it from there.

icaro440 wrote:

r_smp, good for something?.

cpu or gpu? which one is responsible for calculating shadows.

I guess you agree with me that modern computers are real monsters, it would be fantastic that the engine could take well advantage of modern processors, and separate some processes in different threads (I'm thinking of the work of calculating the shadows)

r_smp is a dead cvar that does nothing because the support for it was compiled out.
All shadows are done on the gpu. Doing it on the cpu would be terribly slow.
The only things the cpu does is setup a few matricies and vectors and passes references to the gpu after doing a bit of occlusion culling using the static visibility data and frustum culling using the viewport. All of this is so cheap it basically isn't even a factor in the speed.
The gpu handles all the work of creating the shadow and projecting it on the scene.

The work the cpu does for shadows is very minimal. Unless you have an absolute beast of a gpu, it is unlikely to be the bottleneck in shadows rendering.
If you do have such a gpu, then you can already run at a constant 150+ fps at all times anyway, so I doubt you would care what the bottleneck was ;).

Fuma wrote:

r_smp is a dead cvar that does nothing because the support for it was compiled out.
All shadows are done on the gpu. Doing it on the cpu would be terribly slow.
The only things the cpu does is setup a few matricies and vectors and passes references to the gpu after doing a bit of occlusion culling using the static visibility data and frustum culling using the viewport. All of this is so cheap it basically isn't even a factor in the speed.
The gpu handles all the work of creating the shadow and projecting it on the scene.

The work the cpu does for shadows is very minimal. Unless you have an absolute beast of a gpu, it is unlikely to be the bottleneck in shadows rendering.
If you do have such a gpu, then you can already run at a constant 150+ fps at all times anyway, so I doubt you would care what the bottleneck was ;).

Crystal clear, thank you.

thanks that worked

now i got this going on

can someone help me fix this?

I experienced similiar issues. I don't think shadows are ready yet.