Yup, that's it. I changed it, and it works now! That's pretty bad, though; I'm going to have to do that whenever I use sourcecoder. I'm either going to have to do this on calc, or switch to my Windoze partition to use Tokens/BexIDE... And this problem has consumed my weekend; I'll have to wait for the next weekend to keep working.
So... problems. Because of my roots as a BASIC proger, I've been optimizing as much as possible. The high score routine is embedded inside the game, but now I have to pull it out into a subroutine so the menu can call it. So I used sourcecoder to cut/paste it into the bottom, and had it run a subroutine - just to test if it worked. When I tested it on Tilp2, the Highscore turned into a bunch of random mumbo-jumbo and the calc froze... I don't wanna test it on my own calc... Here's the code:
A few commands are weird; it's the BASIC version of them. I've also attached 2 files; BOUNCSRC is the original that works; BOUNCSRS (1) is the funky one. Anyone know what's going on?
Thanks! I'll use a smaller ball if anyone can provide a hex code for it. No white holes, please. *as a side note, that animated bug on your signature is making me want to hit my monitor.
I also have an idea for the menu - choices in the middle, lined horizontally, and you have a paddle and ball bouncing just below the choice. The player moves the ball under the selection and increases the height to hit it! The ball would probably move left/right with the paddle, no real bounce physics. (So beginners have an easier time.) What do you think?
Thanx. I need the ball to be entirely solid - hit detection depends on pxl-test()s and there's always the chance that the ball hits, but the white part is exactly over the pxl-test() location. And the ball looks fine in my game.
I've noticed that in many games with balls, the sprites are partially white. EX: [0000182C3C180000] Why is that so, and is my ball sprite of [003C7E7E7E7E3C00] bad to use?
If you know Axe, I'd like help drawing the title screen that I'll be adding; fixing the random glitch where it starts flickering and then you die; improving the level editor; fixing the leftover timer glitch; fixing the ball-breaking-wall glitch; adding pause, walls, path prediction and slowmo; more additional features; etc... I have a lot to do...
This is my first real Axe game, Bounce! Inspired by Mr. Bounce by Pixelate - http://www.madebypixelate.com/games/mr-bounce - and now for the TI 83/84s! It's a basically Breakout with gravity, and a few twists added in. (I haven't got the twists yet, just the basic engine.)
Bounce the ball with your paddle and try to get it to hit the targets, but don't drop it. You only have 1 life! You have about a minute to get everything before the timer runs out - you won't die when it does, but you don't get the bonus points. My highscore so far is 630, can you beat it? (the default is 0 with "BLACKSCREEN INC", the name of a group of my friends and I made up when we sold games in school)
I've attached prgms A, AA, BOUNCE, and BOUNCSRC. They are the level editor, the level editor's source, my BOUNCE game, and its source, respectively. I was pretty lazy when making the level editor, so it's not very good. If you screw up, exit, then type 0:Asm(prgmA) - it'll delete and reset the map.
I'm using DirectLink, port #1. The problem is, it doesn't detect anything on the calc. When clicking the "refresh" button or attempting to backup the calc, Tilp crashes and the terminal spits out:
** (tilp:24205): ERROR **: Invalid byte sequence in conversion input
However, after sending a program, the program appeared on my calc's prgm list! Weird, I don't know why.
I have no idea what "libti*/gfm/tilp" is... Sorry, I'm a noob at this.
It sends files now! Unfortunately, it still can't detect my calc and therefore I can't upload to my computer. Which cable is it? Direct link, right? And which port do I need to use? (yes, I have "USB scan at startup" checked)
Here's the error then attempting to connect:
Spoiler For Spoiler:
Msg: failed to open the USB device. Cause: Check that the USB cable is plugged in and that the calculator is turned ON! Also, check libusb and usbfs for valid permissions. System: Inappropriate ioctl for device (errno = 25)
Also, when checking for calcs, terminal spat out:
Spoiler For Spoiler:
(tilp:4553): ticables-WARNING **: no devices found!
Show Posts
