Command doesn't work?

  • #1, by tangerinedogTuesday, 12. February 2019, 06:35 5 years ago
    I've followed this tutorial (and just about any other tutorial I could find) to the letter, but now, after adding an object to my scene, adding an object area for that object and listing all the actions in the object's actions tab... it doesn't work when I click the thing.

    My Character moves to the object, which is as it should be, but nothing happens!

    Even when I set it to immediate execution instead of execution at destination. The Character still moves over, but none of the action parts are performed.

    Why?

    Newbie

    12 Posts


  • #2, by esmeraldaTuesday, 12. February 2019, 08:42 5 years ago
    Did you link the interface to your character (character tab "interfaces")?

    If you did, maybe you could post some screenshots of how you set up the commands and the actions with the sceneobject.

    Key Killer

    508 Posts

  • #3, by sebastianTuesday, 12. February 2019, 15:47 5 years ago
    is the character actually reaching the object or does he stops at the wayborder? 

    Thread Captain

    2346 Posts

  • #4, by tangerinedogTuesday, 12. February 2019, 16:08 5 years ago
    I have linked the interface.
    And the Character reaches the object (which is set as walkable) - I've even made the border encmopass almost the entire screen for testing purposes. Still no joy.

    Now the action part I've set as a result of the command works if I just set the action as a left click.

    Edit: I've even started the game anew from scratch. Same issue.

    Edit II: Fixed it by dumb luck - Instead of having a walkable object in the borders, I set the object to not walkable and the position to that of a waypoint. Then, I set the borders not to include the object area anymore. Now, the immediate execution works without the Character moving and the execution at destination works with the Character moving.
    Could you please explain to me why that is?

    Newbie

    12 Posts

  • #5, by esmeraldaTuesday, 12. February 2019, 16:57 5 years ago
    The position in the properties tab of the scene object is not the position of the object but the position for a character to interact with the object.
    So this positon has to be within the wayborders so the character can reach it. Else the action will not be executed. At least when the command is set to execute at destination.

    But the command should have worked when set to immediate execution. So I'm not sure what the problem here was. (would need more screenshots of your settings)

    Key Killer

    508 Posts

  • #6, by tangerinedogTuesday, 12. February 2019, 18:02 5 years ago
    The position in the properties tab of the scene object is not the position of the object but the position for a character to interact with the object.

    Well, exactly! But Previously, I had it set to walkable and the Character trodded over to the exact place I had clicked the object in.

    So this positon has to be within the wayborders so the character can reach it. Else the action will not be executed. At least when the command is set to execute at destination.

    That's where things fell apart - upon reaching the destination, nothing happened.
    The Character moved to that point even after right clicking though. Having set the right click action in the mouse properties to never send the Character anywhere, I was supprised by that as well, but that's a whole other can of worms.

    But the command should have worked when set to immediate execution. So I'm not sure what the problem here was. (would need more screenshots of your settings)

    I'll provide them asap, but 'til then, please assume I've done this.
    As I said, I started from scratch and performed nothing but the steps listed there (as well as setting an object area and creating another object that reliably could be toggled via an immediately executed left click action on the first object in question. That contraption works now, so I guess that rules out any mistake in there.)


    Newbie

    12 Posts

  • #7, by afrlmeTuesday, 12. February 2019, 18:29 5 years ago
    if it's set as a walkable object, then the character will walk to position on the object that you clicked on as opposed to walking to the specified object position (interaction position). I guess this would be useful for something like an elevator or platform, or floor based puzzle, but in general you shouldn't need to tick that box for most interactions.

    As Esmeralda said, the interaction position needs to be inside of the way border for the character to be able to reach the objects interaction position & to execute the command/actions. I'm guessing that setting the object as walkable, that it was preventing it from reaching the destination & likely cancelling out the immediate interaction action(s).

    Imperator

    7278 Posts

  • #8, by esmeraldaTuesday, 12. February 2019, 18:55 5 years ago
     I'm guessing that setting the object as walkable, that it was preventing it from reaching the destination & likely cancelling out the immediate interaction action(s).
    I never used the object walkable option. But I did a quick test with an existing project and ticking the box did not work as intended:
    If a position is set, the character walked to the set position, not the clicked position (both inside the walkable area and inside the object area). Action got executed.
    When I deleted the position, the character walked to the upper left corner, not the clicked position. But the action (still execute at destination) was executed.
    Immediate actions work in both cases.

    Edit: In the new Visionaire version either the deleting of positions or the aligning is a bit broken, I guess. Someone mentioned an aligning problem before.
    When I created a new object with no position, the character would walk to the left upper corner again, but the action was not executed.
    Same with immediate action - walking to upper left corner, no action.

    Key Killer

    508 Posts