maximum speed on func_door?

Discussion in 'Mapping Questions & Discussion' started by Bucake, Jul 15, 2015.

  1. Bucake

    Bucake L1: Registered

    Messages:
    18
    Positive Ratings:
    1
    google didn't help me get my answer.
    i wish there was a dedicated thread for "small questions", because i feel sort of silly to make a thread for just this one question.

    anyway;
    is there a way to make a func_door move instantly?
    and is there a maximum speed a func_door can move at?
     
  2. YM

    aa YM LVL100 YM

    Messages:
    7,099
    Positive Ratings:
    5,745
    Don't use a func_door, use a func_movelinear

    I don't think func_doors have a max speed but they can't move instantly. func_movelinear however stores a value between 0 and 1 to use as it's position so you can send it an output to set the position to 1 and it will jump to the end, or 0 for the start.
     
    • Thanks Thanks x 1
  3. Bucake

    Bucake L1: Registered

    Messages:
    18
    Positive Ratings:
    1
    great! exactly what i needed :)

    thanks a lot for your response
     
  4. A Boojum Snark

    aa A Boojum Snark Toraipoddodezain Mazahabado

    Messages:
    4,769
    Positive Ratings:
    5,535
    Movelinear still moves with SetPosition, it isn't instantaneous, despite its cousin momentary_rot_button having a SetPositionImmediately input.

    Aside from using two func_brush that simply turn off/on, your only option would be a func_tracktrain with the teleport flags enabled on the paths.
     
    • Thanks Thanks x 1
  5. Bucake

    Bucake L1: Registered

    Messages:
    18
    Positive Ratings:
    1
    thanks for replying :)
    i tried it out and noticed that func_movelinear indeed isn't instantaneous.

    but enabling/disabling a func_brush sounds good to me. (should've thought of it!)

    edit: if i set the Solidity to Toggle and then use a trigger_mutiple to switch between Enable and Disable, i get the Problem that the trigger_multiple has bad I/O connections.. what am i missing?
    edit: it seems to work, despite the reported Problem. any way to fix this Problem, or is it just something to ignore?
    edit: creating a new func_brush seemed to get rid of the I/O Problem. changing entities from one to another can apparently sometimes cause problems that you can't fix.
     
    Last edited: Jul 16, 2015
  6. Kill_the_Bug

    Kill_the_Bug L14: Epic Member

    Messages:
    1,473
    Positive Ratings:
    240
    do you want to see it move? just toggle a func_brush on/off