| |
Shadow
Account closed
Registered: Apr 2002
Posts: 355 |
Creating angle/radius tables
Is there a size-optimized way of getting a angle and radius table? It's easy enough to just precalc like this (pseudocode):
for(int x=0;x<w;x++)
{
for(int y=0;y<h;y++)
{
radius[tab]=sqrt((x-w/2)*(x-w/2)+(y-h/2)*(y-h/2));
angle[tab]=atan2(y-h/2,x-w/2)/PI);
tab++;
}
}
But what if you don't want to have the whole table precalced due to size concerns? Can you save space with some smart mirrortricks, etc.? |
|
... 13 posts hidden. Click here to view all posts....
|
| |
JackAsser
Registered: Jun 2002
Posts: 1990 |
For instance insane multiplexers, maximzing the number of $d020 splits... FLDs, FPPs, sprite stretching etc. etc. I really doubt the best VIC-coders back then ripped code and only applied trial and error etc. They created their own theories and models imo. Brainers usually does that, where as lamers don't. |
| |
Style
Registered: Jun 2004
Posts: 498 |
only teh lam0rxz rip!
Im a shit coder, but at least everything Ive written is mine alone.
|
| |
Oswald
Registered: Apr 2002
Posts: 5027 |
Jack, I think they looked at the vic as a black box, if I do this then this will come out and so on. they barely could have ideas of inner counters and stuff.
fpp fld etc.. you dont need to have much idea about it. its enough to know the sequence of the numbers to write to d011 and the right cycle. Again, it can work like a black box without deeper vic knowledge.
IMHO :) |
| |
Oswald
Registered: Apr 2002
Posts: 5027 |
Quote: only teh lam0rxz rip!
Im a shit coder, but at least everything Ive written is mine alone.
hahaha, then every good coder is a lam0rxz :-)
I dont mean byte by byte ripping man, but you can get a general idea about the algorythm and tricks if u look at ones code, and most of the time you can find stuff to improve. Then you write ur own and better code from scratch. If u are an experienced coder there's not much things under the sun to steal, coz u know all the tricks anyway.
These days, (altho its happening now very rarely) I check the code to see what method was used, and how good was it done. Often its hard to say how fast this or that would be, but if you find a demo using a similar effect, then u might peek the code and get an idea of the code-onscreenspeed ratio. |
| |
Jetboy
Registered: Jul 2006
Posts: 228 |
Tere is quite a difference between peeking at someones code, and reimplementing it your way, and just plain ripping.
There were no sources in the 80's/early 90's to learn from. All you had back then was C64 Refernece Guide. If you wanted to get some knowledge, the only way was peeking at someone else's code, or reinvent the wheel yourself.
There was much more learning in analyzing other's code in action replay's monitoe, than plain reading article on the internet and looking through clean sourcecode.
If one person was to invent everything we know now oneself, without external input, it would take that person couple tens of years, or more likely couple hundreds.
Articles explaining different theories were invention of the nineties. Earlier if you could find some codes in c64er or similar magazines there were mainly codes without too much proper explanations, beside, those were in german - so hardly readable to people who dont speak the language of Goethe. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11146 |
Quote:There was much more learning in analyzing other's code in action replay's monitoe, than plain reading article on the internet and looking through clean sourcecode.
word! and i would recommend everyone who wants to learn coding to sit down and study some simple stuff (like crack intros for example), modify them, rip them apart, try to understand what this or that is doing. everyone did it like that back then, and you certainly can learn a lot from it. |
| |
Copyfault
Registered: Dec 2001
Posts: 467 |
I can understand Styles point of view: me didn't peek through others code either. When I was younger I also thought it would be lame to look at other people's code, but this idea has fainted away...
Nowadays I do not find enough time (or am too mf lazy) to _seriously_ look through other's code; guess this explains why I didn't release anything yet, though my head is full of "ideas". Hopefully someone (something) forces me to release something somewhen... |
| |
Jetboy
Registered: Jul 2006
Posts: 228 |
still i wonder what HW means... |
| |
enthusi
Registered: May 2004
Posts: 675 |
hardware as opposed to SW ;) |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Shadow: You only need to store 1/8 of the table if you mirror the quadrant. In your quadrant table you only need to store values where y<=x since radius(x,y) = radius(y,x) and angle(x,y)= 90-angle(y,x). (NB. I move the centre of the coordinate system to make the formulas simpler)
Never looking at other peoples code strengthens your creativity, since you always have to come up with a solution yourself. However, when you have found a solution that suits your needs, you dont go looking for something better. If you do look at other peoples code, you are forced to understand the programmers way of solving things and thereby see other ways of solving things that your own.
I have met programmers who can only solve problems if they have seen a solution for a similar problem in advance. However, if you newer look at other peoples code your might be doing very basic things in an unnecessary difficult way because you never stumbled upon the elegant solution yourself. So there are pros and cons of both approaches.
|
| Previous - 1 | 2 | 3 - Next |
