I <3 MY 83+ SE!dysfunction wrote:Yeah but the 83+ SE is so much hotter, I mean it's case is practically see-through!
[Featured][Dev] Zelda (Best Project 2005)
Moderator: MaxCoderz Staff
- dysfunction
- Calc Master
- Posts: 1454
- Joined: Wed 22 Dec, 2004 3:07 am
- Location: Through the Aura
-
- Calc King
- Posts: 2195
- Joined: Sun 27 Mar, 2005 4:06 am
- Location: sleeping
- Contact:
-
- Calc King
- Posts: 2195
- Joined: Sun 27 Mar, 2005 4:06 am
- Location: sleeping
- Contact:
Spencer, the tileset you gave me was incomplete, I think. I am missing the door-below equivalent of tile 16. And for actions, am I just highlighting the tiles and then explaining them to you or am I missing some secret scripting panel. I also don't have those crazy eyes that you shoot, but I wasn't gonna use them anyway. Just letting you know.
Zelda's taking a break while an assembler fast enough to build it in a reasonable time is finished up. Written in C, it's compatible with TASM and adds in some extra options for label-only passes and define-only passes. Most conventional programs assemble perfectly and Zelda assembles without errors, but the binary differs in a few places from TASM (dunno why yet).
- Jim e
- Calc King
- Posts: 2457
- Joined: Sun 26 Dec, 2004 5:27 am
- Location: SXIOPO = Infinite lives for both players
- Contact:
Spencer has to compile a 4 paged app, and each page must be built seperately. Further, in order to get the labels from other pages he must compile once on each page, get a million errors, convert the symbol table, then compile again. So it's alot slower.
Hmmm....Brass added Defpage directive.... does that work for intel hex?
Hmmm....Brass added Defpage directive.... does that work for intel hex?
It takes about ten seconds. Early on I got in a habit of building often, very often, and it's pretty bad especially now when I just change one line in a script to see if it works.
My assembler sorts the opcodes based on how frequently it sees them. The more you assemble, the faster it'll get. Originally, this was just supposed to be a quick pass-one assembler, but since it looks up the opcodes anyways, may as well just write them to a binary file.
I do plan on adding the option of outputting intel hex.
Oh yeah, at the current equilibrium it should never get bigger than four pages.
My assembler sorts the opcodes based on how frequently it sees them. The more you assemble, the faster it'll get. Originally, this was just supposed to be a quick pass-one assembler, but since it looks up the opcodes anyways, may as well just write them to a binary file.
I do plan on adding the option of outputting intel hex.
Oh yeah, at the current equilibrium it should never get bigger than four pages.