Results 1 to 4 of 4

Thread: Ropes, default connection point name of a slung load? – (on the load NOT the heli)

  1. #1

    Ropes, default connection point name of a slung load? – (on the load NOT the heli)

    Does anyone know the default connection point name (toPoint in the ropeCreate Syntax) in a LOD (memory point etc) that will override the behaviour of the ropes connecting to the centre of a LODs volume of a slung load in the absence of such a named point?

    As I have some objects that should be connected near the end/s rather than in the centre, this is also to alleviate the problem of the rope/load physics having spasms associated with ropes fixing to the centre of an object which can then freely spin about it Y axis which would not happen if the rope was connected above and forward of the CoG or LOD centre.

    I have looked at lots of the BIS modals in O2 and have yet to find a named point, and yes I do know you can name a specific point in memory lod or x,y,z point if using the ropeCreate Syntax but I am looking for the point name used by default when inserting a scripted TkoH attach sling load waypoint so save using the ropeCreate Syntax

    Any help would be appreciated.

  2. #2
    Hi,
    I dont think there is any Magical point simply CoG or model coord [0,0,0] that it defaults too.
    Zamerny i think was the old center memmory point not sure they still use it these days though .

  3. #3
    Staff Sergeant
    Join Date
    Jul 12 2010
    Location
    UK
    Posts
    246
    Author of the Thread
    Ok, I have done some investigating and “slingload0” and “slingload1” should be valid points on BOTH the helicopter AND the load, however if a slingload0 & slingload1 is placed in the memory LOD of the load to be lifted nothing happens and the rope WONT connect at all (i.e. the presence of slingload0 or slingload1 in the load to be lifted is enough to override the currant bounding-box method BUT the code or script to actually put the rope to slingload0 or slingload1 is missing/faulty etc thus the rope does not appear and the waypoint stays active)

    The reference to slingload0, slingload1 and the bounding box (which is used at the moment) in relation to the slung load & also the helicopter is in “modules_h.pbo” (path within .pbo is: HSim\modules_h\functions\Waypoints\fn_wpSlingLoadA ttach.sqf)

    The txt of fn_wpSlingLoadAttach.sqf is in the spoiler below, I have tried logical changes to the reference to “_targetPos” being slingload0 or slingload1 in both the “//--- Prepared” and “//--- Attach” sections without luck and I have slingload0 & slingload1 in my memory lod and have tryed using them one at a time.
    (tested from tkoh root folder\HSim\modules_h\functions\Waypoints\fn_wpSli ngLoadAttach.sqf)

    I guess this may be why the medium heli has the as yet unused CargoHook.p3d and CargoHook_military.p3d that fit in the belly, either that or the means to swap between the hook lod1 and the none hook lod2 of the CargoHook.p3d proxy is not yet done like for doors and other bits. found

    Spoiler:
    Last edited by b101_uk; Dec 23 2011 at 19:57.

  4. #4
    A couple of things I noticed in the code, not sure if what you tried in your above statement overrode this?

    The txt of fn_wpSlingLoadAttach.sqf is in the spoiler below, I have tried logical changes to the reference to “_targetPos” being slingload0 or slingload1 in both the “//--- Prepared” and “//--- Attach” sections without luck and I have slingload0 & slingload1 in my memory lod and have tryed using them one at a time.
    (tested from tkoh root folder\HSim\modules_h\functions\Waypoints\fn_wpSli ngLoadAttach.sqf)
    On line 61 references _vehPos, it should be _targetPos by the look of it.

    Code:
    //--- Hook point on target
    			_targetPos = _target selectionposition "slingload0";
    			_targetPos = if (_targetPos distance [0,0,0] > 0) then {
    				_target modeltoworld _vehPos;
    			} else {
    				_targetBboxZ = boundingbox _target select 1 select 2;
    				_target modeltoworld [0,0,_targetBboxZ];
    			};
    Then on line 197 where I think the main issue is, as this is where the actual connections and rope creation occurs.

    Code:
    //--- Get connection points
    _targetPos = _target selectionposition "slingload0";
    _targetPos = if (_targetPos distance [0,0,0] > 0) then {
    	"slingload1"
    } else {
    	_targetBboxZ = _bboxTarget select 1 select 2;
    	[0,0,_targetBboxZ];
    };
    From my reading of things I would have thought that would be "slingload0"?
    then _targetPos is used below.
    Code:
    _rope = ropeCreate [_heli,"slingload0",_target,_targetPos,_ropeSegments,_ropeLength];
    So thinking is most likely in the ropecreate code if the target pos is undefined it defaults to [0,0,0]?

    Have you tested by manually creating a rope with your object and using "slingload0" as the targetpos?

    Could somebody else check my line of thinking, if correct then a ticket could be created for it.

    Hope this helps
    Blake.
    Last edited by blakeace; Dec 24 2011 at 22:40.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •