Messages

Oh cool, but if it can go behind the camera and look right surely there must be more to it than just doing the perspective and then clipping in 2D? Plus there's the risk of division by zero if a point has the exact same z coordinate as the camera?

Anyway unfortunately my Vectrex32 didn't arrive today, according to the tracking code it's in Australia and up to our local postal service to get it to me. But when it arrives I'll certainly spend a lot of time tinkering before writing any of my own code.

Since the Vectrex can only render a limited number of lines per frame, that 200MHz processor can do an awful lot of processing for each one. Even algorithms that run in O(n^2) (as many do) should be possible. So I'm really hoping to get some low-res but ultra fancy 3D working on Vectrex32, especially some sort of geometric depth buffer to produce proper clipped occlusion.

Really excited about the possibilities, can't wait till it arrives!

Thanks Bob.

I actually want to have large 3D models (like terrain) so I'll have line segments that will intersect the front clipping plane and go behind the camera, causing divisions by negative numbers in the perspective transform.

I'll code my own full 3D frustum clip instead and share the code on here when I'm done.

Do the 3D sprites handle full 3D frustum clipping? Or will I need to manually clip against the near and far planes?

I'm expecting my Vectrex32 to arrive tomorrow and am really keen to use that 200MHz processor + floating point for some 3D graphics. I'm hoping to have lighting and hidden surface removal going at a decent frame rate.

A couple of years ago I coded this demo in 6809 assembly.

https://www.youtube.com/watch?v=awMUFCYnQ4U