i'm not sure if this is the right place to ask this question, i've had a quick search and i can't find anything that helps. but basically after upgrading to 6.40.5 pro from the 6.31 trial i've found that when the player model collides with models in the level (e.g. buildings) the screen jerks around a lot.

i'm not sure what's happened as all i did was build the same level i made with the trial. when i walked into a building in the trial version the player was stopped then smoothly slid along it's surface the more you pushed into it, but now it jerks around quite a bit.

i wonder if this is something anyone else has encountered? i may have neglected to update a specific file? i'm using the plBiped stuff from template_6.

anyway, hope someone can help!

I know c_move's collision has been improved a lot lately. You might try setting
"move_friction = 0;" and see if that helps.

thank you - i will give that a go. it's not the end of the world if it doesn't work like earlier, but hopefully it does!

jerky collision can occure if your using the my.polygon = on on your moving entity ( which you shouldn't be doing)

ahh that's exactly what i'm doing!

however i was doing that in 6.31 too, without the problem... is there a better way? i've had a look around and the .polygon method was the only simple method i could find...

make your static models/entitys poly precise for collision.

moving entitis should not use it ( untill octree culling eventualy), defualt now moving entities use a elipsoid collision hull. ( remember even with the poly collision the engine is still for now a BSP engine nd still has 'some' of teh limitations of a BSP engine, but not all)

watch your models animations, incase in its aniamation frames it moves its mesh outside the defualt collision hull area ( the models collision hull is set based on the BASE (first) model frame of the entire model)

you may need to manualy increase its hull size to compinsate for animations excedding the hull

thanks a lot for your help!

i'll look into these - i think you may be onto something with the idea about some models animating and going outside the hull.

I'm getting the same issues, with an ellipoid player hull colliding with a polygon structure such as a building, it's as though the player is getting stuck and it's position being changed to fix the issue, and it jerks. It's even worse when 2 ellipoid hulls collide, jerks like crazy, I've tried all suggestions in this thread and it's not working. I may have to upload a demo to show the issue. Can anyone help???

I have an issue that seems to bear some relation to what is described in this thread.

For a project I am currently working on, I have a configuration where I can enable freezing of 'updates' to move variables immediately after a c_move call for the applicable move mode. Essentially, I can single step c_move calls using the [ enter ] key. (I'm not using freeze_mode or breakpoints to do this. ) So the sequence might be:
calculate movement
c_move
freeze next calculate movement and next c_move until [ enter ] key press
look around and look at debug values
[ enter ] key
repeat

player: defined as the moving entity of interest with polygon flag set to off
poly-structure: defined as a static non-moving entity such as building, surface to move on, etc. with polygon flag set to on

It seems, for me, there is a bit of c_move indecisiveness, when the player moves over certain types of poly-structures. It appears that the player 'flickers briefly' between an 'old position' (or maybe an undetermined position A) and a 'new position' (or maybe an undetermined position B) when c_move is invoked 'on' those types of poly-structures. It appears the greater the distance c_moved the more obvious or prenounced the issue becomes. Note that in the scripts, there are checks for collisions, and it seems that the issue even occurs when there are no direct collisions with the applicable poly-structure entity. Perhaps, there are merely mistakes in the scripting, but I have spent hours upon hours trying to determine the cause of the issue. If it is not a scripting mistake, then my current substandard, half-baked theory is that the issue occurs primarily when the player penetrates the bounding box area of the applicable poly-structure to deeply, like when the player walks a good distance into a poly-structure house, and perhaps when this 'deep' bounding box penetration occurs, there might be a built-in, hidden mechanism that tries to push or move the player back out or correct the penetration. (If I recall correctly, I think that I directly observed and/or read about similar mechanisms.) If such mechanisms exist, while they might be practical in some instances, there may very well be instances where they should be 'disabled'.

Sweet so we're not alone with this issue

Would you know if this has been addressed in the bug forum or elsewhere? Perhaps we can start a thread there? Unless there's an obvious answer we're missing. Can anyone confirm if this issue is non existant in 6.3