Re: We all have problems!!!
Posted by: xparasite9
Date: 2006-07-04 11:36:37
Glitch City Laboratories closed on 1 September 2020 (announcement). This is an archived copy of a thread from Glitch City Laboratories Forums.
You can join Glitch City Research Institute to ask questions or discuss current developments.
You may also download the archive of this forum in .tar.gz, .sql.gz, or .sqlite.gz formats.
It doesn't matter. the word itself is still offensive and the only way for it to truly be censored is to have it be all asterisks. That way, the offensive word is removed and is not offensive. These words are not intelligent words. The members who use them are stupid, because they cannot think of a better fitting word.
This forum makes no effort to be entirely kid-friendly.
There will be swearing, although the harshest is automatically censored, and there will be mild sexual references. Overall this forum is rated PG-13. You will also find some R-rated content, but that will always be specifically marked as such.
Children under 13 are not advised to join the forums unless they are aware of what sort of content they will find here and have the maturity to know what they should view and what they should not view.
This forum is primarily aimed at the slightly older side of the Pok?mon fan spectrum. There are many other Pok?mon-related forums made and maintained for children, but this is not one of them. If you are a parent of a member under 13 and do not wish for him or her to view the forums, that is understandable and you may contact the administrator to have your child's account disabled.
050) SWEARING IS ALLOWED
Censorship sucks. Don't bitch about it.
If you're going for an optimized cycle count, use precalced lookup tables instead of realtime calculation. It takes more memory, but it's much faster, especially with more complex math. Sinuses are excellent candidates for tables.
Always, always, ALWAYS hook your main display code into the Vint if your project is of a substantial size. This will ensure that your output is perfectly smooth. Vint hits at line $E0. If your code is small and only for testing a routine, then feel free to busywait. But know that, if you get too much code running in a frame, then you're bound to hit your display code late sooner or later. If you hook into Vint, then even if your main program loop takes a bit too long, then at least your display code will hit at line $E0 consistently.
Access to VDP RAM during the visible screen is extremely slow, whether you're using DMA or making the 68k do the dirty work - for example, while you can make 205 accesses to VDP RAM during Vblank, you can only make 20 accesses during active scan. Also note that VRAM accesses are byte-wide, while CRAM and VSRAM accesses are word-wide. If the screen is disabled via VDP register $02.6, then you can access VDP RAM like you would be able to during Vblank.
I'm talking about the original intent in posting the thread. If it wasn't only directed at IRC, then I'll just split off all the IRC shit and throw it away, keeping the shit that refers to board issues.
Ok, mabye I misworded it. He's immature.
If you're talking about Wild Missingno., xparasite9, she's a girl.
yeah, viewpoint. I don't know.
I actually agree with GoldenChaos, but I'd rather not see these words.
I actually agree with GoldenChaos, but I'd rather not see these words.
That's why there's a censor.