369. Your first words were "Hello World."

That would be a soldering fail. The tip should be neutrally at +5 volts so it is definitely not connected. It can't be software either because changing the value of the port like that is the lowest level command possible for the link port.

Hopefully you're good at soldering. :)

For a volt meter, your best bet is to use Calcsys. I would assume you stuck a 2.5mm jack into the port and you aren't just sticking probes in there lol.

Go to calcsys, press 3, and you will be at port 00h which is the link port. With nothing else at this point, the calculator should be showing 5+ volts from both tip and ring to ground. Now press enter and type 03. This will set both of them to ground. They should be at 0+ volts or close to it. You can then test each connection by sending 01 for tip grounded and 02 for ring grounded.

I should also mention that when you send any of those values besides 00 the calculator, it will run very slowly if it even runs at all.

Don't expect to hear from me for about two weeks as I am going skiing in Oregon. Don't worry I didn't die.

It's currently in the making. Since I recently figured out usb pretty well. I think you will just connect the calc to the computer via usb and run my C++ program.

The number pad works for me at least.

What I want to do is still have the game played in wabbitemu, just use my calculator as a controller. Taking screenshots of the calculator would take way too long as you said. I just want to have the calculator setup to play with.

The two options I see are use the calculator as a keyboard, but windows might complain about so many buttons being pressed.

The other option is to learn visual basic and write a program that receives the keys pressed from the calc and translates them into computer key presses.

Edit: Nvm, I can do it in C++. Although I don't know how though.

This actually didn't really make the impact I wanted. The problem is that during my collision code, which is about ~150 t-states, adding in the partition check takes 34 t-states. So ya, it skips some, but it also adds to others. I might have to do some serious data switching in my enemy array. Actually, I will have to do some serious data switching.

Also, 16 partitions?

Edit:
    I swapped all of the enemies types (byte 0) with their partitions (byte 1). Every frame, all partitions get initially set to 0. Which means that null enemies get skipped faster. It also cut down my extra code to 30 from 38.

Edit 2:
     Talk about a lucky shot, I'm going to have to eventually make the game harder and do 24 bit scores as this is the second time this game I looped it.

For the extra ram page, I only have 1 so I never use more than one. And I was actually the person who put that info about 2.53 in wiki ti ;). (Missile was being restless)


Before I start, for clarification, the bullets check for collisions with enemies.

Instead of stacks, I saw making the second byte of enemy data it's partition data. When each enemy updates, it decides what partition it is in, and if it straddles it just says it's in both. The circles will say that they are in their partition and all surrounding ones which will at least save 1/4 of the screen. Then when each bullet comes through to check for enemies, it will determine it's partition and AND it with the enemies, if it returns NZ, check for collision, Z move on.


Dodgers: I am going to write this like code as it is easier than explaining.

Is enemy in bullet's way. (determine signs of sin and cos and compare to relative position)
No. return but check for kill
Yes
Is enemy within 20 x and 20 y
No. return, bullet misses
Yes. Use movement code in reverse, i.e. instead of chasing bullet, negate values and it runs.
Is enemy withing 10 x and 10 y
No. return, bullet misses
Yes. Do same as before but double the effects. Grand total of three speeds away
return and check for collisions.

Another note, these guys can only move a total of 6 speeds away per frame, this is because they got pushed so hard from the 5 shot that you couldn't kill them. Also, when I was changing to 8 bit, I had the numbers backwards and the dodgers became suicidal and flew towards the bullets.


Edit to your edit:
     Newer calcs have 1 extra ram page, no problem there.

Edit 2:
     It's too hard to control with 16 buttons, going back to the way it was before.