Feature idea: selectively leaving features out based on user input. For instance, while creating the app, you could prompt the user "Include Sprite Tracking?", "Include 75% Zoom Level?", et cetera. Some games need very few of these features, so the slight speed increase would be worth it. I don't know how you've structured your code, so I have no idea if this is easy or not...just a thought.
EDIT: Also, please fix the sound going flat in higher registers if you can. Thanks!
Thats exactly the buffer use i use for PortalX ^^ And yeah the only way you would be able to free up the buffer is if you made your graphics non destructive, like have every sprite an XOR sprite so that you don't have to redraw the screen every frame.
Considered this. Will test soon.
Next update will have the sprite fix and improved logic for saving (the message comes up only when you reach the level, not when you reload).
Awesome! I was a big fan of the original and the 83 port (though I was disappointed that he forgot to edit the help text, please make sure to remove all references to colors... )
(for instance, someone said that Mr. Game and Watch was better in brawl than in melee) but I found Pikachu to be generally consistent except for the pro players
Aha. Also, G+W is waay better in Barlw. And Barlw+ and Barlw-.
Ah I see about the back-buffer thing. What do you have to do in the back buffer, though? I don't see anything in your code box like additional testing. Btw nice to see progress
I don't have to do anything in the back buffer, but I've tried eliminating it (and simply drawing the level every frame): the speed decrease is horrendous.
Spoiler For Offtopic:
this post marks the beginning of my post rush. I plan on hitting 250 by the end of this week. don't worry they'll all be productive.
I main CF in SSB64 (which I play online with Kaillera religiously), CF in Melee (which I don't play at all), and CF in Brawl (which I play semi-regularly). Spot the pattern.
Also, this is me, not implying that I'm good or anything. I have other vids on the same channel, but they're all from the last year. Watch some of Isai's vids (he used to play Melee and recently quit for 64). The guy is a machine. According to him, 1 frame delay is fake Smash.
*bookmarks* Looks great! "Bomb" blocks (that destroy blocks near them, even if they're normally unbreakable) shouldn't be too hard to implement...haven't seen your code tho, so I don't know. We're all behind you!
Repeat Q back buffer->front buffer do tests on front buffer draw all situational things on front buffer front buffer->screen End There's probably a way I can structure this differently, but it's eluding me at the moment... also, Dispgraphr is kinda slow compared to a single draw.
Show Posts
)
don't worry they'll all be productive.
