this is basicly a problem being continued from http://verge-rpg.com/boards/display_thread.php?id=12343

my funct:

//r1 is the radius of the full circle
//r2 if the radius of the inside circle
void DrawHollowCircle(int x, int y, int r1, int r2, int color, int dest){
int i;
setLucent(75);

for(i=r2;i<=r1;i++){
circle(x, y, i, i, color, dest);
}

setLucent(0);
}

now it works fine as far as I can tell... untill r1 becomes greater than 9. the second it hits 10 or greater it starts doing that crazy shiznik in the linked post.

does anyone have a better way of making this hollowed circle or a reason/solution to what is happening?

Yeah, you should never try to it that way -- you're liable to get holes.

OK! I figured it out! it's indeed a bug.
I recreated the event completely without any crap around it...


that is a circle with the radius at 550. if I set the radius to 500 it works fine. maybe you took measures to optimize by thinking no one would ever need this big of a circle?

lol, yeah I was thinking the same thing... actually if you use 750 you get a full flopping boob shape =p

the reason I'm using this big of a circle is because I'm not so much drawing them to the screen as I am drawing them to the map... the x an y are dependant of the xwin and ywin. Its my whole radius based tactics system here =p

if this is really a much faster/better algorithm, then dont let me make you get rid of it. I'm sure I can probably just resize a pre-drawn circle or something.

aen did. I should bug him.

However, I know for a fact that he was testing for 1) simplicity of code 2) ability to have 'perfect' _small_ circles, and circles with odd numbered widths. I do NOT believe he even looked at gigantic circles.

As for me, I tested the circle routine as being big able to make circles to fill the screen - eg circle out/in effect - and it does. I didnt really anticipate someone drawing a circle gigantically huger than the screen and only showing one side of it.

This could be problematic once we start getting 1024x768 VERGE games!


....


Problematic!

Luckily, andy had a copy of my routines lying around! He says he uses it in ika even, neat-o. Not sure if it's the ultra perfect version I finally ended up with -- I remember tweaking it a bit more after giving it to him. I'll probably test it further this weekend to make sure.

At any rate, the primary focus was on symmetry. I of course also wanted to be able to specify the oval size in the same way a rectangle is specified, with the oval fitting exactly within its bounds. I needed it for a tile plotting tool, and so I felt precision was important. Especially at small sizes. I don't think it produces 100% mathematically perfect ovals, but the results are pretty damn close. I'm also fairly certain it (or at least the perfect version) doesn't produce gaps at any size.

Here it is, in both outline and filled forms: aen_ellipse2.java.txt

Put the filled version in there now too. Same file.

Also! Be mindful of that "b2" variable if you're dealing with this code. There is of course already a variable by this name built in, so I renamed all instances to "bb2". I was scratching my head for a while at some pretty awful ellipses until I realized I had missed one or two of them.

sweet, it sure does work.
unfortunately you made me have to go though and add a color and destImage to everything and the functions work differently than the library ones... but its only a minor setback.

thanks a lot!