Reality Factory

I have a transparent texture applied to a tree model, but when I look at said texture, it looks like so:

There are other tree parts behind, but they don't render for some funny reason (indicated by the red arrows)
So is it my graphics card or what?

I'm having the same problem, I guess it's not fixable and it's Genesis's fault. But maybe i'm not right, but I guess I am. I left my problem there.

Take-a-look at here:

download/file.php?id=1125

You can clearly see that white border there!

Well, at least if the game play is focused on the ground instead of up in the trees the player's won't notice. Or you cheat like so:



I used brushes with dimensions of 256x256x1 with a foliage texture applied, and made all but the two side faces flagged sky.
Hope that helps you out, Gamemaker!

Thanks, but I didn't made my tree-leaves(?) as level geometry. I modelled them in 3DS max with one cilinder and 4-planes. I had to double them, because Genesis supports only one-sided polygons.

I thought so. Just with using world geometry to make the foliage the results look a little nicer, e.g. not having genesis 3d trying to optimize what you don't want optimized.

GaMer, you do mean something like smoothing?

From my understanding what is going on with making transparent actors is that when the clipping code wasn't written with transparent textures in mind. No one has gotten around to fixing it in the source code, so it will clip "through" (pardon the term) the polygons. More polygons would mean less of it, but the code for world geometry was written with transparent textures in mind, so using brushes gives better results.

I dont know if it has a connection,but i noticed when you place two static entities for test -character and his armor -in the same location,the thin parts of the armor that are close to the character skin-even noe touching-
are rendered transparent in some parts as you change distance from it.
When you use one static entity with the character and armor attached before export/actor build-
it renders well.
It might be that there s a rendering confusion between two different meshes very close.