Engoo

[Spirit]

[qbism]

... IN DOS?!
Surprised due to DOS memory constraints.

Stainparticles is a fascinating concept. Is there a way to check particle collision while drawing surface blocks? Then stuff doesn't have to be precalculated and stored... as cached particle overlay surfaces?

The particles don't have to be precise, maybe a 'particlemap' modeled after lightmap could be used. Instead of blending, a discrete pixel would be written whenever a threshold is crossed, filtered through a dither lookup.

[leileilol]

[qbism]

OK, I've just got dithering on the brain.
So a particle hits a surface... does code delete the particle and run 'R_AddStainparticle' similar to FTE 'R_AddStain''? Or is the particle turned invisible, flagged, and scanned somehow for impact location after surfaceblocks?

[leileilol]

I'd want to skip drawing of the particle totally if it's within the wall.



Also , while trying to experiment to add echo to the sound system, I accidentally muffled sound effects however it's staticy. I might be able to utlilize this 'effect' for underwater...

[mankrip]

[leileilol]

I would have a second 'mix' surfaceblock.

[mankrip]

Padding the surface cache at mix time after the R, G and B channels have been processed wouldn't allow to be implemented, because it requires the texture and the lighting to be processed differently (wrapping the texture's edges, while expanding the lighting's edges), so you would still get in all surfaces.

Well, at least the speed gains would be retained.

[leileilol]

I'm not too concerned with fixing the kernel filtering at this point (especially when dealing with C spans contradicts the aim for performance, and i'm not sure if this rgb abrash surfblock theory is faster than my current c surfaceblocks yet (which I optimized quite a bit out of since to the point where I think something slow is happening in MarkLights)).

The strange waterwarp particles crash in Windows is more fatal, and now i'm starting to see a strange bug appear involving trail particles causing them to suddenly jump and make a long line. ugh

[mankrip]

[leileilol]

No that's not the same bug. Sometimes the particles THEMSELVES will suddenly move, not the same as calculating a trail from the new entities' now void origin.

This started happening after I installed VC6 SP5.... hmm!

At least I keep a public svn repository so I can go back and see what the hell I did wrong.

EDIT: Rolled back to VC6 and the bug went away. Hmm!

[leileilol]

Please, do not adjust your set...

[ceriux]

is that like a quad effect ?

[ceriux]

is that like a quad effect ?

[ceriux]

is that like a quad effect ?