Posted 20 March 2008 - 06:19 PM
I learned rudimentary C in the early 90s from the Netrek and Xtank projects.
I learned Perl in the mid 90s to write web applications for ISPs.
With a bit of Python under my belt, I intend to learn CrystalSpace/CEL while working on Interstate Outlaws.
From my reading of the CEL docs, there is a lot of potential for this project inherent in the API.
Reading through the IO source, there is a lot of fleshing out to do.
I believe this project could fill a gaming niche that has been vacant since the demise of I76.
Let's have a peek at your development objectives and let's make these buggies DANCE.
Posted 21 March 2008 - 06:08 PM
Posted 30 March 2008 - 02:54 AM
It would be great to have you on board. We need all the coding help we can get! Get in touch with me, my email is cfraz89 @ ** gmail ** . com
Posted 30 March 2008 - 02:40 PM
I learned BASIC and 6502 assembler in the 80s to create my own games, including competitive AIs.
wow ... that must be very interesting , i wanna learn about it !
Posted 24 April 2008 - 02:46 PM
Vector shapes also meant a lot of binary math, all done on paper. First you used graph paper to plot out the shape, then you converted it to a series of vectors, then you converted the vectors to their binary representations, then you combined them with binary math to end up with the bytes that represented the shape. Once all your shapes were encoded thusly, you would calculate the shape table index to define the number of shapes and byte offsets to each, then POKE the entire shape table into a specific memory location, byte by byte. (See Example 19)
Once that was done, you could rotate, scale or color the shape when drawn on the screen. (Though the color wouldn't matter unless you had an expensive color monitor. Most were orange or green.) The XDRAW routine drew the shape with an XOR mask so it wouldn't erase other graphics it moved over, mostly. It also returned a collision detection value your game logic could use to determine, for example, if your lunar lander just collided with the moon. Check the vertical and horizontal velocity values to see if you need to draw the spinning explosion vector shape (HCOLOR=5) and POKE a suitable series of tones to the speaker.
And all this happened in 280x192 resolution, unless you opted to use four lines of text at the bottom of the screen (a text HUD used less CPU than a graphical one) which left you with 280x168.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users