72 replies to this topic

[kucalc]

I'm working on a 3D FPS game for the fx-9860. Something kind of like DOOM and Wolfenstein for the PC. I have a basic demo of the 3D engine attached to this post. I'm still thinking about where to go with the story and what enemies to have. Do any of you guys have any ideas?

[E_net4]

Cool! I'm going to try this right away!

Edit: It's a great thing you've made a 3D engine for this calculator, but I'd rather like to have a Half-Life like engine... YEAH, CALL IT CASIOSource!!!!!!!1!111eleven

And yeah, post the source code.

[Fez]

I just tested it and it's really kool. Just a quick question. Is it my calc or is there suppoesed to be a white line running up the screen. It might just be because the grayscales(which look wicked btw) are to much for my crappy batteries XD. It's called call of duty but it seems more like a doom game. I think you will do better just making a pure doom game anyway. The gun looked cool as well. i was fiddling around trying to see if I could shoot. But you cant :INSERT NON EXISTENT CRYING SMILEY HERE:

[E_net4]

I just tested it and it's really kool. Just a quick question. Is it my calc or is there suppoesed to be a white line running up the screen. It might just be because the grayscales(which look wicked btw) are to much for my crappy batteries XD

Yes, it is supposed to show up. There's no way to get perfect greyscales.

And yes, do it Half-Life like!

[kucalc]

It's a great thing you've made a 3D engine for this calculator, but I'd rather like to have a Half-Life like engine... YEAH, CALL IT CASIOSource!!!!!!!1!111eleven

Lol, yes, but creating a real 3D engine would be kind of hard. The engine I'm working on is quasi-3D and it's hard to do things like looking up, jumping and crouching,

I hope that when I finish this game, the engine will be included along with Revolution-FX's graphics component.

I just tested it and it's really kool. Just a quick question. Is it my calc or is there suppoesed to be a white line running up the screen. It might just be because the grayscales(which look wicked btw) are to much for my crappy batteries XD.

Yeah, unfortunately, there is suppose to be a white line. It's a side effect of grayscales.

It's called call of duty but it seems more like a doom game. I think you will do better just making a pure doom game anyway. The gun looked cool as well. i was fiddling around trying to see if I could shoot. But you cant :INSERT NON EXISTENT CRYING SMILEY HERE:

Maybe I should just do a DOOM clone. I didn't put in any shot effects or enemies, because I don't know what enemies to have. If you guys want to help out drawing sprites, guns or special effects the specs are:

Sprites (enemies): 64x64 pixels - 3 colors (white, black and gray)
Guns: 16x16 pixels - 3 colors (white, black and gray)

[E_net4]

Um, why just 3 colours? Is it too slow for the Calc to render more colours?
Also, what is the syntax for 32x32 and 64x64 sprites?
Edit: Never mind, I found it out, I guess...

[thomatos]

Hi everybody ! I've just tried it, and that's great, the only thing is that grey is too dark I think ...

[kucalc]

Um, why just 3 colours? Is it too slow for the Calc to render more colours?
Also, what is the syntax for 32x32 and 64x64 sprites?
Edit: Never mind, I found it out, I guess...

I could do 4 colors I suppose. (White, light gray, dark gray and black).

Hi everybody ! I've just tried it, and that's great, the only thing is that grey is too dark I think ...

Maybe I should then switch to 4 color for the light gray.

[E_net4]

Indeed. Using 3 colours just sounds weird.
And the grey isn't so dark, it looks fine here.

[thomatos]

Oh no! the grey is really too dark, when you play, you sometimes cannot make difference beetween black and grey !

[E_net4]

Oh no! the grey is really too dark, when you play, you sometimes cannot make difference beetween black and grey !

Then there must be something wrong with your calculator. Try to change the contrast, mine's just fine.

By the way, I wonder how is one supposed to convert a 64x64 sprite into an array of data without spending months on calculations!

[Fez]

the image converter from seb. draw it in paint then convert it.

[kucalc]

There's also another great utility for creating grayscale code for Revolution-FX: http://www.planet-ca...v...es&showid=5

[E_net4]

And I thought I had to make my own program for it. XD

[Fez]

What grayscale "Magic Numbers" did you use for the gun. I haven't been able to find the right ones. The best I have had makes it look good. How I want it to look. But then the dreaded white line. Not only does it just sweap it, but it removes all gray leaving the border of the gun. Then it sweaps again, adding the gray back. Please tell me. What are the correct "Magic Numbers" XD

EDIT:
I have a sprite for a rifle if you dont already have one. Due to my REALLY bad understanding of grayscales, it's really bad flickering. I'll just provide the two arrays because you cant actually see it with my flickers.

const unsigned char Rifleone[] = {0x00,
0x00,0x00,0x00,0x01,0x80,0x03,0xC0,0x05,0xA0,0x04,0x20,0x0C,0x30,0x14,0x28,0x14,
0x28,0x14,0x28,0x14,0x28,0x14,0x28,0x14,
0x28,0x14,0x28,0x14,0x28,0x14,0x28};

const unsigned char Rifletwo[] = {0x00,
0x00,0x00,0x00,0x01,0x80,0x03,0xC0,0x07,0xE0,0x07,0xE0,0x0F,0xF0,0x1F,0xF8,0x1F,
0xF8,0x1F,0xF8,0x1F,0xF8,0x1F,0xF8,0x1F,
0xF8,0x1F,0xF8,0x1F,0xF8,0x1F,0xF8};

[E_net4]

I assume that "0x00" can be replaced by "0", which makes the source code smaller... right?

We need more greyscales knowledge.

[kucalc]

This is what I use for initializing the engine. For three colors (black, gray & white):

GrayInit(3280, 3280);

For four colors (black, dark gray, light gray & white):

GrayInit(3270, 1453);

[Fez]

Thank you.

[E_net4]

I still wonder how you did the 3D rendering, kucalc. Are you going to give us the source code?

[k3v]

Raycasting no doubt? Hehe i was wondering if you could post the source to a simple non texture-mapped raycaster as ive read up on the technique but cant find any code that i can understand Eg. the previous build of this 3D game

Also, just a quick question (exams over so im back into programming ) i couldnt be bothered making new post, how can i clear and update "buffers" continously without getting flicker? AKA clear them behind the scenes like Casio VRAM... If i chuck in a

memset(&buffer1, 0, 1024); 
   memset(&buffer2, 0, 1024);

It clears the "viewing" screen in real time creating flicker... In your 3D game theres no flicker...

[kucalc]

Raycasting no doubt? Hehe i was wondering if you could post the source to a simple non texture-mapped raycaster as ive read up on the technique but cant find any code that i can understand Eg. the previous build of this 3D game

First of all, welcome back k3v! I'll release the code when I find the time, I'm really busy now with other projects. Maybe I could turn it into a Christmas gift project for you guys or something...

Also, just a quick question (exams over so im back into programming ) i couldnt be bothered making new post, how can i clear and update "buffers" continously without getting flicker? AKA clear them behind the scenes like Casio VRAM... If i chuck in a

memset(&buffer1, 0, 1024); 
   memset(&buffer2, 0, 1024);

It clears the "viewing" screen in real time creating flicker... In your 3D game theres no flicker...

I actually do use memset() to clear the buffers in my 3D game. Do you have GrayInit set up properly?

[k3v]

First of all, welcome back k3v! I'll release the code when I find the time, I'm really busy now with other projects. Maybe I could turn it into a Christmas gift project for you guys or something...

Haha... okay

I actually do use memset() to clear the buffers in my 3D game. Do you have GrayInit set up properly?

Are you clearing the screen continiously though? Like not just when you move?

[E_net4]

Um, you forgot about something. There is no such thing as a 3-pin cable to connect more than 2 calculators at once.
And so, no counter-strike.

[kucalc]

I think he means playing a two player game. Revolution-FX allows multiplayer games on the fx-9860, but only upto two.

Only 25 more days until Christmas!!!

[E_net4]

Yeah. And 24 fer meh birfday.

[Fez]

what birthday near christmas. You lucky sunuva turkey. Hang on, ur not lucky. Do you get extra pressies XD

[E_net4]

Usually, yes.
I get moar cookies! :cookie:
...kucalc! I told you to add the cookie emoticon! XD

[kucalc]

I don't want to be a drag, but let's keep this ontopic. Someone here in the forums has reported this as being off-topic, so let's stay on track.

[E_net4]

Yeah, right.

What about the game/engine's name? Are you going to keep it as "Call to Duty"?

[Fez]

Yea right sorry. I seem to have a rep with all the forums im on as the one most likely to take topics of topic XD

[E_net4]

I really did have to take a real look on what you said:

Maybe I should just do a DOOM clone. I didn't put in any shot effects or enemies, because I don't know what enemies to have. If you guys want to help out drawing sprites, guns or special effects the specs are:

Sprites (enemies): 64x64 pixels - 3 colors (white, black and gray)
Guns: 16x16 pixels - 3 colors (white, black and gray)

...The hell? I don't think we really need 64x64 sized enemies. There is no image filtering, and so lots of pixels won't show up.
Also, the size! It's just too heavy for an enemy.
1. With the current storage methods, we store 8 pixel information on a byte. This means 8 bytes for 64 pixels, times 64, which make 4096 bytes.

2. An enemy doesn't just have 1 frame, it has various frames! Also, we can't just change the rotation of the sprite in the scene to make it look another way. More sprites are required, and Doom uses more than 4 different rotations of the enemy, but 4 would be enough. If we multiply: 4096 * 4 = 16384 bytes

3. No, I'm not done yet! There are animations for each rotation of the enemy, which makes it/him walk or attack/shoot. In Doom, most of the enemies use more than 1 or 2 frames for the attack sequence, and 2 or 3 frames for movement. If we used 3 frames(2 for walking, 1 for attacking), as we want a reasonable look of the enemy, we get: 16384 * 3 = 49152 bytes

4. And then, there is this: The greyscales AND the sprite mask! :shock: This means at least 2 more images for each frame! 49152 * 3 = 147456 Bytes = 144 KBytes

And no such thing as a CASIO program ever had such a space in memory.
Either you didn't explain what you want to do with the enemies, or you pretend to do some special method for them. Anyway, keep this in mind.

[kucalc]

...The hell? I don't think we really need 64x64 sized enemies. There is no image filtering, and so lots of pixels won't show up.

I find that 64x64 sprites come out nicely. The textures on the walls are 64x64 sprites.

1. With the current storage methods, we store 8 pixel information on a byte. This means 8 bytes for 64 pixels, times 64, which make 4096 bytes.

Lol, you computed it wrong. (64 pixels/bits * 64 pixels/bits) / 8 bits per byte = 512 bytes per 64x64 pixel sprite. Or 8 bytes * 64 lines = 512 bytes. 512 bytes is 87.5% less than 4096 bytes.

[E_net4]

And this is, my folks, one of the biggest hates of Maths.
So the amount of bytes would be... 18KB...

I find that 64x64 sprites come out nicely. The textures on the walls are 64x64 sprites.

The problem with using these sizes are because we can only enjoy them by full if we are really close to them. Anyways, make sure you do your best on this project. A calculator version of Doom is getting near.

[E_net4]

You might want to have this. It's a pack with some sprites of the demon character of Doom that can be used in this. I did not put a walking to the right version, as I thought you could just mirror the sprite walking to the left in-game. If not, you can just edit the bitmaps in this pack and do what you want.

[kucalc]

Ok, thanks. The sprites are awesome!

[kucalc]

Yeah, so I was messing around with the code and I managed to get a way to scale images so I can have sprites. Here's a little demo, nothing much new added, just that there has been some progress: http://www.mediafire.com/?4vhzgn3udt9

[Fez]

only just realized, this topic is taken from UCPF XD

anyways, im now downloading the game XD

looking good so far.

I cant wait to shoot that demon XD

Also, i can kinda walkthrough the demon rofl.

anyways, great, can't wait for the finished project

[E_net4]

Tried it. Here's what I'd like to say about it:

- I really think you should use 4 colours. It'll use the same amount of picture data and will look better. Also, the demon I gave you is supposed to work on 4 colours.
- Remember that the demon doesn't always look at the player, so you might need to do some calculations in order to figure out what specific frames to use (If the demon's running away from you, you wouldn't use the frames where it's looking at the player)
- (Optional) Give us the source-code! XD ...Alright, I'm kidding. Just take your time to get something stable.

I might help you with more sprites later.

Tried it. Here's what I'd like to say about it:

- I really think you should use 4 colours. It'll use the same amount of picture data and will look better. Also, the demon I gave you is supposed to work on 4 colours.
- Remember that the demon doesn't always look at the player, so you might need to do some calculations in order to figure out what specific frames to use (If the demon's running away from you, you wouldn't use the frames where it's looking at the player)
- (Optional) Give us the source-code! XD ...Alright, I'm kidding. Just take your time to get something stable.

I might help you with more sprites later.

[k3v]

Dude! That looks freaking awesome! Keep up the good work! Haha...

Hehe please dont wait to long to release the raycasting engine because then it'll just get more complicated Haha, i just wanted to see the "ray" [space] "casting" part in action as ive read quite a number of tutorials and want to see some code i understand in action. Aka the angle calculations and square detection etc.

- I really think you should use 4 colours. It'll use the same amount of picture data and will look better. Also, the demon I gave you is supposed to work on 4 colours.

For me the Fx-9860 Lcd blurs way to much in motion to be able to differentiate between more then one shade of grey, and theres hardly enough contrast to see it static...

Just leave it as is, its looking awesome