This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Builderboy
Pages: 1 ... 80 81 [82] 83 84 ... 375
1216
« on: May 19, 2011, 05:15:57 pm »
8 bytes  each pixel is 1 bit, and 8x8 is 64 pixels total, and 8 bits per byte, so 64pixels divided by 8pixels per byte equals 8 bytes ^^ EDIT: With simpler explanation 
1217
« on: May 19, 2011, 05:06:21 pm »
Oooh gotcha, that makes more sense ^^
1218
« on: May 19, 2011, 05:00:26 pm »
Its because you are increasing the velocity of B when you collide. You want it to stop right? Try 0->B instead of B+1->B
1219
« on: May 19, 2011, 04:39:04 pm »
Wow that all looks so awesome! I especially like the fire  I am in the middle of adding a fire like element into my game as well, in the form of fuses. I still noticed something weird going on with the boxes when you jump into them in the second screenshot. They seem to be moving into you?
1220
« on: May 19, 2011, 04:20:37 pm »
Notice how in your code, it goes like this:
Keypresses
Move Object
Check for collision
What this means is that if you press a key, it *Will* move the object, because it's only after you move the object that you check to see if it should be stopping. Move the collision test before the movement and it should work
1221
« on: May 19, 2011, 04:19:14 pm »
I deleted the test program I made to see if pulleys were going to work
1222
« on: May 19, 2011, 04:16:41 pm »
Lol well I'd have to make it again, since I deleted it And everybody needs to have faith in their own projects!
1223
« on: May 19, 2011, 03:21:48 pm »
This will stop it when the sprite is exactly on the 0th pixel, that might be not what you want though.
!If Y/256
0->A->B
End
Do you want to stop the sprite completely, or only the Y velocity? Or maybe if it goes past the 0th pixel?
1224
« on: May 19, 2011, 03:15:49 pm »
While its definitely not lacking in physics, I'm sure it will be easier than enabling full dynamic physics across every object and enemy
1225
« on: May 19, 2011, 03:04:59 pm »
Is that all of your code? Because that works perfectly fine on my calc
1226
« on: May 19, 2011, 02:59:55 pm »
Nope, no difference
1227
« on: May 19, 2011, 02:53:29 pm »
It occurred to me that I'm treating memory almost as magic in some cases.
So, some questions.
What's the difference between doing
[FFFFFF->Str1
[010203
[More hex
[504432]
and
[FFFFFF
[010203
[More hex
[504432]->Str1
In the first example, the location Str1 points to is the first byte FF of the first line. In the second example it points to the byte 50 in the last line. If want to load a large amount of memory (using hex, strings or Data()) on multiple lines, how does Axe know when the block of memory ends? For example, if I have
[0102
"Foobar"
Data(42)->Str1
How does the compiler know the limits of the block of memory?
I'm not quite sure what you mean? You have defined 51 bytes in that code, and so Axe adds those 51 bytes into your program.
1228
« on: May 19, 2011, 01:53:22 pm »
That crashed your calculator? What version of Axe are you using? Under no circumstances should that code cause a crash o.O
And yes that will work for acceleration, but you are accelerating at .5 (128/256) pixels per frame, which is actually really really fast for a high framerate program. Try turning it down to like 8 or so.
1229
« on: May 19, 2011, 10:39:59 am »
Yeah, I was surprised in the end how little lines of code I could do this in  It took lots and lots of time to get it down to that level, the original even had 2 square root functions o.O
1230
« on: May 18, 2011, 11:40:01 pm »
I am single and just interested in being single right now. I actually recently broke it off with by gf, and i have to say im feeling a lot better and just not ready to get back into the game for a while. Plus i'm gonna be moving to santa cruz in a year and a half so don't want to get too committed You all might have noticed my activity has gone up recently, now you know why 
Pages: 1 ... 80 81 [82] 83 84 ... 375
|
Show Posts