Anim8or Community

They work very well. I noticed great improvement between v1229 and v1230.
When in fast select, with the move tool, if I select an edge and then drag one of its points, the whole edge will move. Is this expected? On the contrary, if I select a face, then drag one of its edges, the edge will be moved.

You're seeing some light about the collision issue? That's great! It was making me feel kinda down.

You made my day. No, week. Oh my, you enjoy something so much when you miss it for so long!

It works perfectly. Makes no sense. Are you sure the error is in the line - triangle collision code?
I remember writing some code for 2d collision back then... the problem wasn't in the collision detection method, but in the code that was using it. I mean, maybe it's not a matter of how you find the collision, but what you do afterwards.

http://en.wikipedia.org/wiki/Free_and_open-source_software

I made it... it renders a black screen, so it seems the function returns always false. Weird. Maybe some more bugtracking will show the cause.

Are you working on other things meanwhile?

EDIT: Oops, it was a bug outside the function... my fault... please stand by.
EDIT2: Still black.
EDIT3: Ok, working... I'm now trying to convince WinGDI to display it on screen. Somehow!
EDIT4: AH finally!

cooldude234, could you please run this on your PC and send me the result? Double clicking on the window saves the image in C:\test.bmp.

The attached test.png is what I get. Edges look OK here. Also the bright line at the middle is a good sign. We'll see if this is a matter of different pc architectures (I doubt it).

EDIT5 tart.exe had a bug, I uploaded new version below.

Sorry for being idle, the semester has started and I had to cope with it.

cooldude234, can you please give me again an example input to test? i.e. 3 points of a triangle and 2 points of a line that you know they produce wrong results? Because I made many tests and it works so far flawlessly.

I just tested your code, it doesn't work.

DOH. :-/
Did you also test the code I sent you in the PM and it still doesn't work?

Also what method are you using (I really don't understand any the code too much), is it this method you are using?
http://geomalgorithms.com/a06-_intersect-2.html

Nope, the method I use is based on solving linear systems of equations. I might upload some explanation later.

Right now I'm trying to figure out how a, b and c are being represented as the plane, because the math that you used to make the plane defined by the triangle is exactly the same as the code I used for finding the normal of the triangle (by getting the cross-product). But you cannot have a plane with the normal, you need a point as well to define the position (I use the first vertices read because its quick and easy, it doesn't matter which it is anyways).

You forgot 'd'. (a,b,c) is indeed the normal of the plane. But, a*x+b*y+c*z=d is what describes the actual plane. I put it in a linear system with the other equations (lines etc) and new results are produced. The assignments I do (abcd,a1a2 etc) are actually the solutions of the linear systems.
No, of course I didn't solve them myself. get wxMaxima from here: http://sourceforge.net/projects/wxmaxima

The code for finding the collision point is correct, I've tested it many times. Now, what happens with the code for checking if it belongs in the triangle... that's another weird problem.

EDIT: wait, what do you mean 'the collision spot is smaller than the actual triangle'?

Oh, oh I found the bug. I'll post a new version once I fix it. Thanks for the input, it helped.

(If you're curious, rti3 code was made to work only with equilateral triangles... [What on earth was I thinking?] Anyway, I'll have news soon.)