AlliedModders

AlliedModders (https://forums.alliedmods.net/index.php)
-   Scripting Help (https://forums.alliedmods.net/forumdisplay.php?f=11)
-   -   Information about SV_TouchLinks (https://forums.alliedmods.net/showthread.php?t=196389)

dFF 09-20-2012 06:29

Information about SV_TouchLinks
 
I need some info about SV_TouchLinks, like who call this function for amxx. I tried to search at HLDSK but i don't found anything (i'm noob with HLDSK).
Thanks.

Arkshine 09-20-2012 14:25

Re: Information about SV_TouchLinks
 
It's an engine function, you are not going to find something in the HLSDK.

SV_TouchLinks is called from SV_LinkEdict.

And SV_LinkEdict is called from :

Code:

Direction Type Address              Text               
--------- ---- -------              ----               
Up        p    LoadGamestate+44A    call    _SV_LinkEdict
Up        p    CreateEntityList+286  call    _SV_LinkEdict
Up        p    SetMinMaxSize+FC      call    _SV_LinkEdict
Up        p    PF_droptofloor_I+C4  call    _SV_LinkEdict
Up        p    PF_setorigin_I+37    call    _SV_LinkEdict
Up        p    SV_movetest+17C      call    _SV_LinkEdict
Up        p    SV_movestep+355      call    _SV_LinkEdict
Up        p    SV_NewChaseDir+24E    call    _SV_LinkEdict
Up        p    SV_NewChaseDir2+24A  call    _SV_LinkEdict
Up        p    SV_MoveToOrigin_I+CB  call    _SV_LinkEdict
Up        p    SV_StepDirection+8B  call    _SV_LinkEdict
Up        p    SV_FlyDirection+4F    call    _SV_LinkEdict
Up        p    SV_PushEntity+D6      call    _SV_LinkEdict
Up        p    SV_PushMove+168      call    _SV_LinkEdict
Up        p    SV_PushRotate+173    call    _SV_LinkEdict
Up        p    SV_Physics_Follow+148 call    _SV_LinkEdict
Up        p    SV_Physics_Noclip+106 call    _SV_LinkEdict
Up        p    SV_Physics_Step+45D  call    _SV_LinkEdict
Up        p    SV_Physics+76        call    _SV_LinkEdict
Up        p    SV_RunCmd+C0C        call    _SV_LinkEdict
Up        p    SV_SetupMove+7CC      call    _SV_LinkEdict
Up        p    SV_RestoreMove+16C    call    _SV_LinkEdict

From an AMXX native, you have a good chance with PF_ functions (EngFunc_DropToFloor, _SetOrigin).

dFF 09-21-2012 10:42

Re: Information about SV_TouchLinks
 
Thanks for reply and information.

So, only EngFunc_SetOrigin and EngFunc_DropToFloor can be cause some crash on my server, that's strange. I used engine function drop_to_floor to drop some custom entityes (drop_to_floor from amxx engine module is same like EngFunc_DropToFloor, those call same functions?) and dosen't see to be a problem. And i used fakemeta function EngFunc_SetOrigin to set origin to some entityes, need tried engine function entity_set_origin to see if is a fakemeta problem ?

Here is the crash log:
Spoiler

the log is say the crash whas generated by AMXX Engine functions
Code:

#0  0xf70afcc0 in SV_TouchLinks () from /home/cs_classic/cs/engine_i686.so
#0  0xf70afcc0 in SV_TouchLinks () from /home/cs_classic/cs/engine_i686.so

(i hope i not say bullshits)

Can be drop_to_floor (AMXX engine function) fault?
Now, i don't have free time to analyze with GDB to see exactly problem. Did you have an idea what can be the problem?

avril-lavigne 09-21-2012 19:29

Re: Information about SV_TouchLinks
 
I use drop_to_floor without any problems.

joropito 09-21-2012 20:52

Re: Information about SV_TouchLinks
 
Run the server with this command line

Quote:

LD_LIBRARY_PATH=:. gdb -args ./hlds_i686 -console -master +ip **.**.***.** +port 27028 -game cstrike -dir /home/cs_classic/cs +mapcyclefile mapcycle.txt +map de_dust +maxplayers 26 +exec server.cfg -sys_ticrate 1000 -zone 8192 -pingboost 3 -num_edicts 2048 -secure -debug
Then, inside gdb:

# r <enter>

If you're prompted to continue, use yes. Let it run and play.
After the crash, inside gdb:

# backtrace <enter>

Then post the output here.

Sometimes drop_to_floor crashes if you screw up things in entities, maybe some flags or offsets.
Are you sure you're not calling drop_to_floor(0) ?


All times are GMT -4. The time now is 08:12.

Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.