Ummm...that link is to a raycaster, which renders stuff quite differently from a polygon engine.

That's true, but then again doesn't hurt to learn more than one method of doing so, it may help you out when you're trying to figure out other methods.

Quote from: fb39ca4 on June 27, 2011, 07:53:44 pm

Ummm...that link is to a raycaster, which renders stuff quite differently from a polygon engine.

Depends on the particular polygon engine. In any case, it's example code for handling 3d objects. The only really significant difference between polygons and raycasting is how you detect them. Actually, now that I think about it, BenRyves' Nostromo demo used polygons.

Yes, I think that uses polygons, but withouth textures.

And abouth raycasters: I don't know exactely how they work, but if i am correct, raycasters with textures renders by casting a ray for each collum of pixels, calculate the height that the slice should be, then it draws a collum of the texture on the buffer, stretched to the correct height. (correct me if I am wrong)
A polygon based engine works by calculating the 2D coordinates of 3D points, and then drawing something between them. So if what i said abouth raycasters is correct, then code used for texturesin raycasters is useless in polygon based engines becouse those engines render in completely different ways.

I tried that, and i only found C code (and I don't understand anything of C) or OpenGL stuff, which uses the graphic card for rendering (and the graphic driver in a calc is way to primitive for that.

I found the asm scource code of a 3D engine with textures, But I think it's made for an other processor and with an assembler with a different syntaxis.

does anybody knows what these instructions could mean?
- mov
- int
- cmp
- jne
- je
- jge
- jmp
- jl
- cdq
- idiv


EDIT: I just accidentaly double posted (wasn't paying attention). I've merged those posts now.

CDQ: Convert Double to Quad

Double: is this like the java double (a floating point number)? And what do you mean with quad?

I decided to give up on textured triangles. They are way to hard

But becouse I really want textures, I tried writing a routine for textured quads, and it worked
This only took me 10 minutes to code:

Now I still have to port this to asm. I'll let you know when i've done it (or when i have an other problem).

I assume you're not worrying about perspective correctness?

I've tried it and the texture is only a bit of near the center. On a screen with a very low resolution, it would only be noticable when you are very close. And becouse the quad isn't made out of two triangles, it would always have almost the same effect as persfective correction.

what method are you using for this?

interpolating. A lot of it.

uBer coders?

Yes, my name starts with a B. My real name is Ben, and my surname starts with a G. That's how I've shosen my name.