How about a "general knowledge" topic?
Posted 30 August 2010 - 01:44 AM
I'll give some simple examples.
Some days ago, I wanted to know what was causing the flickering on some sprites. The answers were really logical, but wrong, and I don't think it would be welcome to steal the focus again the basic Q&A thread to tell about it, and it would be lost really quickly anyway. Now, I know for sure it's the number of pieces on the same horizontal line that causes it, so the more you "optimize" a sprite to use tiles that have been used before, the more likely you are to make the flickering happen. In that thread, it would say something like:
"What causes flickering of sprites? - too many pieces of sprites aligned horizontally"
And so, people could save hours of useless sprite optimization.
Another example, a little glitch that can appear if you modify S1 to jump higher or a similar function: the lava wall in marble zone 2 will move if you get out by the top, so here it would read, in a "known glitches" section:
"Lava Wall (S1-Marble Zone): the lava wall will begin to move if you jump out of the corridor
- reason: the object checks if you went out of its activation area,
- solution: deactivate it when you're out of range vertically but not horizontally"
I'll stop here with examples. I think such a mini database could be useful, both to avoid the copy/paste so many people hate and to list hints and glitches so people can debug their hacks more easily, correcting glitches they may not notice otherwise.
Posted 30 August 2010 - 06:11 PM
Posted 31 August 2010 - 02:44 AM
Suggestions and critics welcome, of course.
Posted 01 September 2010 - 05:04 PM
Edited by Dandaman955, 01 September 2010 - 05:05 PM.
Posted 01 September 2010 - 09:37 PM
The point is to create a thread where people can drop such informations without giving away their solutions and code, in other words to list issues and give directions to resolve them.
I think I'll also add some basic informations about how to "read" some asm functions so people can avoid mistakes easily. For example what the dn/an mean, or the "i" after some functions, etc. Once you have those in mind, you're less likely to mistake add.w for addi.w, and knowing what things like "$18(a0)" really mean can't hurt. Maybe some tips about a few asm functions could fit as well.
Trying shouldn't hurt anyway, I don't think it can be counterproductive. At worst it could be useless. ^^'
Posted 07 September 2010 - 11:48 PM
So, I've collected some infos so I could have at least one entry for each section I had in mind (excepted some level subsections and s2, s3k, s3Db etc. sections). Not a huge lot, but it's hard to find back things that only floated around the mind for a few minutes, and it isn't meant to be complete on day 1.
Now though, about the way to post it, I think the best (most optimistic) if the topic was to grow in the future would be to use several posts, to clearly separate the sections (and avoid reaching the max size limit per post) and update them when necessary. Is it ok?
Posted 08 September 2010 - 12:39 AM
Well, while I understand the method you're going for here, wouldn't quote boxes be sufficient enough to do the same thing?
You can hold multiple different things sepearted under one post.
And 1 + 1 = 7! =P
Posted 08 September 2010 - 12:54 AM
Well, if there's no maximum post length to worry about, I guess some good text formatting will be enough. I'll do that tomorrow.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users