Yes, the cones are rotating, but it's very hard to explain what their doing.. i'll upload a video soon.

thats the best variant

I got some help from Julio and Delfi on Newton forum.
Problems with rolling objects, bouncing from edges can be solved by greatly increasing NewtonUpdate call frequency. So if the problem of GS is that it doesn't allow you to call a function in a while loop more often than once per frame, you can use a for loop in that while loop, which slices the current (time_frame / 16) into time intervals (subDt) so little, that when calling NewtonUpdate as many times as the count of slices, you get the necessary NewtonUpdate call frequency. Of course, you also you have to pass NewtonUpdate the correct sub delta time.

Here's the code, adapted to your wrapper, for super precision required in simulations:


You could pass the desired Newton FPS with newton_start() for example.


Another problem is that while boosting Newton FPS to solve bouncing on edges problem solves it in case of models, it doesn't work for blocks. What do you suspect? Vertices set not precisely enough maybe?
I'll investigate this myself after I fully integrate Newton into my game. Finally I have at least one firm solution. Thanks so far.

Wow, looking like this works :))
i tried some examples of time slicing, but looking like this really works, thank you

I don't think, that its because of vertices... Maybe try to increase frequency.

No problem. I wanted to give something back.

I tried increasing the frequency up to 10000, but even that didn't help.
Fortunately, the blocks work perfectly as walls with continuous collision mode on, and I can build floor with a set of 2^n x 2^n models easily.

Try to increase to 1000000.. you'll see the difference
I think, you may make newtonFPS lower.

Than 1000? No, I don't think so. Notice that my test case works with about 400 - 500 FPS, which gives 400 - 500 FPS for Newton. Setting it to 1000 gives two or three times that much FPS (three times because of that +1. It's AT LEAST 1000). It's suspicious that you need at least 1000 FPS, but it does make the difference. You can try lowering it for the test case below GS FPS and you'll see the ball bouncing then.

[EDIT]
Lines
var vratio = (dt * newtonFPS);
var n = integer(vratio) + 1;

can be merged into one line
var n = integer(dt * newtonFPS) + 1;
of course.

Real difference i see only with newtonFPS = 100000, then it works very laggy. Anyway, there is a little difference between 1000 and 1: car bounce in different ways... I'll check it in your level

If you've already boosted the Newton's FPS, which is what would satisfy Newton guys, maybe it's about time to report a bug at their forum

Ah, i see... with your update function, ball doesn't move through the wall