My pc specs

Dual core CPU.
1 Gb ram.
Onboard Intel graphics card supporting shader 2.0 v.s., p.s.
shared ram - allotted 128 Mb to graphics card.
160 Gb Hdd.

The demo runs at 60 Fps aprox.

Quote:

---

The demo runs at 60 Fps aprox.

---

How can you tell about that?

if you use taksi, you can set it up to take movies and it will make up for lag, just tell it how many frames per second you want it to run in the movie, and it will automatically speed up or slowdown the movie to make it run at that speed.

I'm wondering if anyone else who downloaded the game has experienced similar problems with msl_manni, like for instance cars passing through buildings or anything similar.

I suspect this has to do with low spec systems but I could also be wrong.

I have vsync on.
But as far as can understand, you are using the c_move to detect collisions.
And as a programmer I know that you cant be 100% percent correct with c_move. Take for instance two cars that are in opposite direction, they are always showing ridiculous collision behaviour in your demo. They shouldnt be overlapping or passing through each other.
60 FPS is a good framerate and you cant blame that for bugs in your collision detection. I prefer the physics objects instead of c_move to control the collision, as they are near percfect because they take the whole geometry into consideration, and NEWTON is best for every situations.
I have projects that run at 30 FPS but dont show any kind of bugs that I see in your demos. I would like to know if my prediction is correct.

I'm sorry to disappoint you but I don't do any collision detection, because:
(a) I don't trust c_move's collisions either,
(b) it would look ugly to have cars climbing the pavements in order to pass by each other (road is quite narrow, should have known better... )

Instead, cars use c_scan. Can't you tell from the distance they start to dissolve?

Of course, I could make many things different (and less ridiculous) if I had more time. But this game's main goal is to have a good friendly & enemy AI and that was where most of the development time was spent.

Hopefully there will be a patch coming out soon.

Well then I am very dissapointed in you, as you are trying to blame the Low FPS for poor collision behaviour. You already know that c_scan is the worst choice for collisions. But on the bright side you can pass on the demo to casual users till they dont point out the follies in your demo. But dont be alarmed if you get a bad critic for your game.LOL.

I don't understand your point in those arguments. I use c_scan for AI, so I take advantage of it in collisions too. But this game is not about collisions, and no player will ever bother because two cars behave weirdly when they cross each other.

I mentioned the low FPS specs because you said you saw a car going through a building, that's a totally different matter in my code.