Phenomenal

If anyone is knowledgeable on this sort of thing should I replace math.sin with a less accurate calculation or a lookup table? (why doesn't it just use one anyway? I suppose because of memory overhead)

Edit: Lookup table gives a small speedup, going to use more accurate calculations and just put them into the lookup table now

Edit 2: Not much but I bought myself 6 extra fps from it, doesn't mean much but should help lower end systems

Yup, stack overflow can suck sometimes. If your question is programming related I might be able to help.

@Mighty Professional It was to do with my implementation of an algorithm being bugged, has to do with C# and OpenTK although it's a logic error pretty sure so if you know C# and want to take a crack at it I'd be more than grateful.

Sure shoot me a link

Yeah, that was what most people said. 

The topic isn't very recent though, I posted it like 14 weeks ago.. People just keep adding their own ideas because they don't read. 

Im going to wait for source before bringing it back up 

No comments needed when your code is good enough to self document. Please confirm @panda

tl;dr for what I came for: Yes with caveats

v me answering multiple questions

Usually that's the case. At the very least some comments documenting intended code flows and use cases for methods are necessary because things have multiple meanings but don't necessarily do those multiple things.

Intersect is uh, very not self-documenting for the most part though. It's getting better, but no amount of documentation (actual comments and self-documenting code) in the world would give the average person on this forum who would give quotes for those features any real idea of what they're dealing with for at least a couple weeks, if not a month unless it's extremely basic. That said, there's a limited amount we can do to make something so innately complex and large sufficiently simple to internalize in order to give reasonably accurate estimates and not shots in the dark.

 Over and out