ZGameEditor forum

This is a proof-of-concept that thru determination and blatant hackery, an old coder like me can figure out how to make this work.

A little known character, "the Mutant", displays all the correct views all the time.

Getting closer.
You can hide the slide with fog, poorer lighting, and background objects.

Cool

He looks quite evil. Movement and animation seems to work properly, nice work!

Just shoot it.

An observation @ ZGE depth sorting.
Shoot to activate mutant.
From current position observe how some bars are rendered in front of model.
If you move to observe models path by fence, you will see wall avoidance is set.
If you move to observe model perpendicular to fence during travel, the depth sorting is correct.

The current depth sorting technique only takes the Model's position in consideration. So when you place Models within a vicinity of each other that is smaller then the "size" of meshes they render .. this can happen yes.

You're making things difficult for yourself though. If you just go with nearest neighbor filtering ( and 1-bit alpha maps ), you don't have to worry about opacity blending .. and won't need any sorting either.

K

If you just go with nearest neighbor filtering ( and 1-bit alpha maps ), you don't have to worry about opacity blending .. and won't need any sorting either.

Help! Ya lost me again.

Attached is a example of two sprites that use a texture with a alpha channel ( 1-bit, so only black or white ) without any actual Depth-Sorting.

K

To get it working on my ATI-card I had to change to the following in the fragment-shader: It's a pain that the rules of shader compilation are different between vendors.

I actually hesitated for a second when writing that statement .. but figured ATI's compiler wouldn't be THAT picky*. Guess not

@ y_offs_et : You don't have to use a shader though, you can use the fixed-pipeline function glAlphaFunc as well.

*Does (pixel.a != 0.0) work without the "f" suffix though?

K

Strange... I got two colourful diamonds on a changing background without problem.
Now to look at the code....

Edit - let me rephrase that - it compiles without problem - editor opens all components OK... until I click App. .... When I get this message ... and the preview has no bitmap but still changing background.

Anyway, previous is cool.

Back to my original depth sorting... I think I've figured what is happening.
These textures are 64x64 , but the actual area used most of the time is 32 wide in the middle. I thought about cutting them down, now I will.

When the sprite turns to face the player, a portion of the sprite is thru the wall.

EDIT - Actually, that wasn't it, and cutting the textures produced more problems. I was mixing meshes and sprites.

These variants works also:

I kept poking away once in a while, and came up with the beginnings of an editor, for anyone interested.