parenting or phys_constraint

Discussion in 'Mapping Questions & Discussion' started by GreenLemon, Jun 4, 2017.

  1. GreenLemon

    GreenLemon L1: Registered

    Messages:
    30
    Positive Ratings:
    3
    Really simple question;
    -what make them different ?
    -when use one or the other ?
    -does they affect ent diffeently ?
    -sandwich are good !
     
  2. Idolon

    aa Idolon the worst admin

    Messages:
    1,548
    Positive Ratings:
    4,437
    phys_constraint is used when you're actually dealing with physics objects, while parenting is used when you want multiple objects to behave as one. Most often what this means is that, unless you're using a func_physbox or a prop_physics, you'll want to use parenting.
     
    • Agree Agree x 1
  3. GreenLemon

    GreenLemon L1: Registered

    Messages:
    30
    Positive Ratings:
    3
    if for example i'm parenting a base_boss to a func_tracktrain i should be using phys_constraint
     
  4. Idolon

    aa Idolon the worst admin

    Messages:
    1,548
    Positive Ratings:
    4,437
    If you're just trying to set up a standard tank for MvM, you don't need to do anything special to make that work. If you're doing something unusual, you'll likely want phys_constraint since the tank has a mind of its own. If the tank were only parented to the func_tracktrain as it went into the air, the tank would still obey gravity and sit on the ground.
     
  5. GreenLemon

    GreenLemon L1: Registered

    Messages:
    30
    Positive Ratings:
    3
    here is my problem at this moment , teh base_boss follow the func_tracktrain, but the console get fill with error
    [ pushing entity (core) that has parent (core_holder)! ]
    it's not really a problem but if i could get rid of this with anything possible, phys_constraint break instantly when activated

    even if there is not way to avoid parenting option it's not a real problem, just my server log getting reallly big size.