fix: Access violation crash

[erictuvesson]

fixes #21

[kikootwo]

Just wanted to copy my comment from the issue here, in case it went under the radar:

First of all, thank you for the prompt and detailed reply!

I should have been more specific, you were correct in your assumption that the vertices are a large list of triangle data. Every 3 > make up a triangle. In my implementation, I am doing the same thing as you (without the fancy linq chunk). I make 1 polygon > per triangle.

I tried your newest committed code. I no longer get the stack overflow exception, but I am hitting your new BSPMaxDepthException. I tried returning there, instead of throwing an exception, but then the model is missing its back face. I even tried replacing my polygon building with your linq query version and got the same polygons and the same final result.

Maybe I misunderstood, were you saying this is a known limitation? Or am I still doing something wrong here?

And finally to comment on the speed: Yes, CSG modelling is slow. But you should take pride in the fact that your library is essentially the only C# implementation that I have found actively being developed and in rudimentary tests, performs 4x faster than the other solution I am using. #