how would i make a 3d interface for rpg S.o.S

[Mitchell]

Well, to convert a 3d coordinate pair (like a vertex of a polygon) to a screen coordinate is complex.

No it's not. To draw 3D shapes to the screen is complex. You can play copypasta with any number of formulas on the internet, but stuff like textured triangles takes time.

Does the said code happen to involve matrix transformations?

[Brick Break]

Well, to convert a 3d coordinate pair (like a vertex of a polygon) to a screen coordinate is complex.

No it's not. To draw 3D shapes to the screen is complex. You can play copypasta with any number of formulas on the internet, but stuff like textured triangles takes time.

Does the said code happen to involve matrix transformations?

Matrix transformations are unnecessary. Full 3D can take the form of raycast vertices of triangles. Any transformations that occur can be calculated at the time of the transformation, and the main renderer can handle the per-vertex stuff. Hopefully, though, all this functionality will be buried under layers of subroutines.

[Brick Break]

look what i found  
i have my interface haaaaaa evil me i know there was one made some where for me  

Code: Select All | Copy To Clipboard

...

That's OpenGL. Sorry, you're out of luck. Lithium's raycaster won't run on Wine, and Irrlicht has all the same problems as OpenGL.

So, what do you do? Check out that tutorial that those nice folks at petesqbsite gave you. It has all the 3D math you need. If you want, you can use the FB extended library to draw your triangles. I will be coming out with my own renderer soon, though, so I wouldn't jump the gun and use that DLL just yet.

[Mitchell]

Raycasting polygons? Unless you're referring to ray *tracing*, you cannot render true 3d polygons with raycasting. There is no concept of height in the processing, just hacks in the final rendering to the screen to give the illusion of height.

And yes, to build a normal, fully functional 3d graphics engine, you will have to be able to process matrix transformations. If you don't, you will run into many limitations. Many old raycasting games were usually set indoors to hide it. id's old raycasting engines were plagued with "i-cant-do-thats" because of these very same issues. Not to mention matrices are a very very efficient and effective way to manipulate structures. You want a swinging door? Multiply the door's coordinates by a rotation matrix, instead of having to write extra code for that door specifically.

[Brick Break]

Rotations will come into effect, but it will be through a rotateobject() subroutine, and not matrix transformations. Also, using my method, I can have at least 2 axis of camera rotation without any "hacks".

[Mitchell]

Rotations will come into effect, but it will be through a rotateobject() subroutine, and not matrix transformations. Also, using my method, I can have at least 2 axis of camera rotation without any "hacks".

How do you look up and down without skewing? And why the extra code for rotateobject? With matrices, all you do is specify how to multiply them together. Then when you want to actually do something, you simply call a function that multiplies the matrices together. One function to handle rotation, translation, skew, and projections. You just have to make the matrices.

For example, how do you make the transformations of a 3d leg walking? Imagine having to code that. However, I can do it easily with matrices.

Code: Select All | Copy To Clipboard

Draw_leg:
    Rotate thigh connected to hip
    render thigh
    Translate down to knee
    Push matrix to stack
        Rotate calf relative to knee
        render calf
        Translate to ankle
        Push matrix to stack
            rotate foot
            render foot
        pop matrix
    pop matrix

[neo]

wait a min here ....... all we would have to put in to this code is a no clip so you dont walk past walks .
and from there you fix up the code to make a small editor.
so i have a lay out.....
opengl i dont like ps .........
but now i have code to understand how all working in so.
i will make a clip on youtube showing this interface off but tonight if i can find the time.

[Brick Break]

Rotations will come into effect, but it will be through a rotateobject() subroutine, and not matrix transformations. Also, using my method, I can have at least 2 axis of camera rotation without any "hacks".

How do you look up and down without skewing? And why the extra code for rotateobject? With matrices, all you do is specify how to multiply them together. Then when you want to actually do something, you simply call a function that multiplies the matrices together. One function to handle rotation, translation, skew, and projections. You just have to make the matrices.

For example, how do you make the transformations of a 3d leg walking? Imagine having to code that. However, I can do it easily with matrices.

Code: Select All | Copy To Clipboard

Draw_leg:
    Rotate thigh connected to hip
    render thigh
    Translate down to knee
    Push matrix to stack
        Rotate calf relative to knee
        render calf
        Translate to ankle
        Push matrix to stack
            rotate foot
            render foot
        pop matrix
    pop matrix

Don't drag me down to your cheap math and your high-level memory addressing. I already had to sacrifice JavaScript compatibility with pixel drawing, now I'm not going to kill QBASIC compatibility with matrix transformations.

Unless you can do it without trigonometry, I see no reason to do this.

As for neo, congratulations on realizing the truth about hardware acceleration, now give me a few days and you'll have your rendering library.

[neo]

kool thx you

[Brick Break]

kool thx you

You're welcome.

Within 2 days, my solid-shaded polygon renderer should be complete. Then, it will be a simple matter of applying some basic raycasting maths.

[neo]

way kool

[Brick Break]

way kool

A little late on that comment there. I'm still waiting on someone to finish the function.

That someone hasn't yet made themself known.

[neo]

   oh why god why nooooo lol

[Brick Break]

  oh why god why nooooo lol

Lol? I don't think it's a lolzing matter. If we could get someone to finish that function, that would be great.

[neo]

in time we will have it working