Sparklies firework on .ase models (in svn build)

[tZork]

Ran into the same thing, it looks like its trigged by a change in how darkplaces handles deluxe maps. revert to rev 8515 of darkplaces and you good to go.

[divVerent]

Well, the revert won't happen in the darkplaces trunk, so please do not rely on that (as that reopens the other old bug that the same places always get black... not exactly better). Work around it in your map until the bug is fixed in the map compiler.

This is clearly not an engine bug, but it happens now when the deluxemap vector the map compiler wrote is a zero vector.

[divVerent]

First of all, try again using CURRENT NetRadiant, i.e.
http://emptyset.endoftheinternet.org/~r ... -win32.zip
or later. I fixed a bug causing stuff to receive light from the wrong side in that. You may be using an older q3map2, which causes this.

Secondly, if this does not help, please supply the .map file and ALL required content that's not in Nexuiz svn to me, so I can debug it.

Thanks

[divVerent]

One instance of this is caused by a bogus normal vector, pointing INTO the triangle instead of OUT of it. May happen when smoothing normals. See how the blue normal below the spectator text points DOWN.

Any instance of this when NOT smoothing normals, that is, using mere brushes and not q3map_nonplanar?

Any instance of this when q3map2 does the normal smoothing, that is, using mere brushes and q3map_nonplanar instead of making the normals in the modeling app?

[divVerent]

Proof that this is a q3map2 problem:


Surface normals of the model.


Surface normals as seen by q3map2.

These normals mismatching (because q3map2 downsamples them into a bitmap, instead of using their exact values), and deluxemaps being in MODELSPACE, causes these problems.

But as Id Software don't care for q3map2 bugs, and I gave up debugging this (any attempt to fix the normals q3map2 uses leads to black spots on the lightmaps/deluxemaps, for no imaginable reason), this will NEVER GET FIXED.

Thank you, for never helping out.

I can't do everything alone.

And when it goes on like this, I will leave and the project will die. Because you guys never help.

We need people to help with the project (in NetRadiant too, as you see here), but as this is never going to happen... it'll be the end. I wonder if there will ever be a next version, given the current state of the project.