Xarthor : Yes It's true but... I want the better control I can have with my game... Camera and movement is a big part of this...

tompo : I see the help since yesterday but I don't no...

I have read this: "SCAN_ENTS scans for the object's >>>>origin<<<< only. If you have a large object, you will probably need to increase the scan range or add additional triggers around the object's circumference."


But if I have an entity SIZE: 10000 height 100 width 5 Z-width

Hmmm that not work right?

I have try with:

IGNORE_ME <- Work but Origin of the entity

SCAN_ENTS | IGNORE_ME <- Work but Origin of the entity same of ignore_me alone because SCAN_ENTS is activate by default

SCAN_LIMIT | SCAN_ENTS | IGNORE_ME (enable_scan my other entity) <- not work : 0 all time


other mode in ref:
SCAN_POS Scans for camera positions placed in the level. (I think is not that)
SCAN_PATHS Scans for path start positions. (I think is not that)
SCAN_NODES Scans for path node positions. (I think is not that)

I like your help if you have any idea

Thank you,
Julien

ho and it's nice I will only use the c_move and put my movement system in the garbage :'(

c_move doesn't do any physics. use c_move, and then if you want any special reaction type thing, do that yourself.

if you want to actually check if an entity is intersecting another one (collision detection requires motion for there to be a collision, but it seems you want to detect an intersection) you should request in the "Future" forum.

i'll do that myself, actually

julz

or try:
1. my.polygon = on; //polygon colision if You have a large model
2. convert model to terrain

Please note:
The polygon flag should be used on STATIC models ONLY!
No model which is moved in any way (c_move e.g.) should have the my.polygon flag set to on!