Hi, I have a weird problem, I issue the stand command. my hip rotors are in the center position, but the whole legs are still shaking and ALL rotors are going from -0.5 to 0.5 velocity and eventually the stand command "fails" any idea?

Also 2 legs who are identical are behaving differently since this issue, is the script broken ? since I also can't get the demo mech to function properly

quick thing: Does this still work?

@ChaosOverlord

You can create any combination of blocks (hinges, pistons, rotors), in theory! The script makes configuration pretty straightforward, though it may take some tweaking to get the timing right for more complex builds. Share a link to a blueprint sometime and I’d be happy to take a look!

Instead of rotors, is it possible to use the new hinges combined with pistons? Would circumvent the torque restrictions

Cool! Thanks!

"When I was I was Distracted"

Um... hey, what's that. Oh, tacyons, close this tab... You think you get distracted (:

@TheTownWitchDoctor

Hey there! Sorry again for the delay, haven't been on too much and when I was I was distracted ;). As for the run toggle, it took me a while to track down but I think I found the issue (assuming it is still the Sentinal Mech).

Short version is that you didn't specify a "run" block-level configuration so the run multiplier in the CustomData config is actually only multiplying by the defaultVelocity (also in CustomData). If you aren't using the default velocity, I recommend adding a run value to each of your blocks to specify the velocity you want it to use!

@CTH2004

WSAD controls came out a while ago ;). Please refer to the "watch" command in the "Available Commands" section of the guide: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1324799895

I can't get the "run" toggle to work for some reason. All variables are configured in the custom data and thruster overrides are set for both walk and run, but when I toggle to "run" after running a "walk" command all velocities/overrides remain the same? I don't know if I'm doing something wrong or not.

Could we have WASD control? I'm about ready to work on "THE PLAN"

@BL8NT

I think they use the default velocity variable for their speed. You can edit that in the CustomData of the PB.

Syntax might a bit off but it looks something like:
default_velocity:2 <- Change the 2 to a 5 for example.

I must admit that in some situations I find myself mashing certain commands, especially with heavier mechs. Center and crouch are usually the culrpits. I will caution that you will want to make sure the default velocity works for the rest of your mech *or* that you have the mech's components' velocity explicit (My Rotor [mech] vel:2).

Hey Drag0nsKin, a quick question. Is it possible to increase the speed for stand/crouch actions? It's very slow and multiple attempts are required to get to the designated position. Is it something I can adjust in a setting?

@BL8NT Made some small updates to the guide in the "Available Commands - Control your Mech" section. Private shares are fine too if you want a second set of eyes on the setup!

Will you be updating the guide soon? I'd like to see your examples for run toggle. Thanks!
I'd link stuff but it's all a work in progress right now.

Oh I see! Sorry for the confusion. Looks like I never added the toggle explanation to this guide

Run is not actually a separate command in the sense of making the mech do something, but instead it switches between walk and run settings. So for exampleif have 2 hot keys setup for the script: One that runs the script with "watch" and the other that runs the script with "run". Use the "watch" command and then press "W" to get the mech moving. Once it gets up to max walking speed, use the "run" hot key and the mech will switch to a faster pace (depending on your run settings) :).

If you want to share a blueprint I wouldn't mind taking a peek. I love seeing these things!

Yes, I've been following the guide. It's very helpful so far!

When I use the program block with run as an argument I get an error in the block that it doesn't know run.

"You must use one of the following arguments when running this script: watch, unwatch, walk, walk1, reversea, reverseb, reversea1, reverseb1, revereseab1, stand, crouch, stop, reset, setup, none."

Then it seems like the script is looping and the game starts to slow down until I recompile or run a different argument, such as stand.

I see the custom data entries for run but it also mentions they only apply when RUN toggle is on. That is where I'm a little confused I think.

@BL8NT Yes, depending on which command you want it to do you pass different values to the script using the Arguments field. Some examples are: "walk" and "stop". There are more in the Available Commands section of the guide though :).

My favorite command to run is "watch" as the argument to use WSAD will control your mech.

Hey Dragonskin, looks great so far. Just a glitch with the programming block or a misunderstanding on my part regarding the run command. Is it an argument when running the program block?

Hey @BL8NT and @CTH2004! Sorry for the delays, haven't played much lately. Got some updates in there for you all if you are still interested!

@Josh The squash
No videos yet unfortunately :(. It is high on my list of wants, but getting the time is challenging for me right now.

Check code shows:

Program(1063,50): Warning:'IMyTextPanel.WritePublicText(string,bool)' is obsolete:'LCD public text is deprecated.

Hey Just wondering if anyone made a youtube guide for this because I understand things If I get to see them better If not can someone help me understand it a little better Thank you

I’m not sure if it is or isn’t broken (Never been able to get it to fully work, I meet clang a lot , and I must admit, I like him (At times, at other times I want to kill him))

But, since there have been about 3 major updates to the game since the last version, you might want to consider looking at it and updating it!

Not sure what you mean by the 1.180? This script started at version two and replaces MK I (https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1223700031) .

Yes it still works, the guide is up-to-date if you are interested :). As for conveyor hinges, I have not tried them, just vanilla rotors and pistons. If you so happen to I would be interesed in hearing the results though!

Hey,
Does this script still work as of 1.180? Can blocks like conveyor hinges work with the script? Thanks

@kendall

Yes, using landing gear as "feet" is part of the functionality. The guide shows you how to name the landing gear so the script can utilize them.

Have you made this script compatible with landing gear so you can climb up the side of a ship in spaceflight?

sweet

@jnanibhad55

Simple answer, yes. If you want all 3 legs on different walking patterns then that would require two PB's, but the setup would be the exact same (the 2nd PB would be used to drive the 3rd leg on whatever timing sequence you wanted).

would i be able to make a tripod with this?

New Beginners Walkthrough and Complete Guide available

thannnnk youuuuu ! I'm gonna try that now. ^^

I will be releasing two example mechs very soon! One is teased through the .gif in the description, the other is a simpler bipedal mech that covers the basics. I will also introduce a tutorial video in the near future!

If you have [b] on one side of your mech, and that side is doing the same as the other side (the [a]) side, then I would suggest trying negative values for the velocity.

For example

If you have one part that looks like this:
Rotor [right] [mech] [b] vel:1

and it does the same as a block that looks like:
Rotor [left] [mech] vel:1 or Rotor [left] [mech] [a] vel:1 (these are the same thing)

Change the bad block to:
Rotor [right] [mech] [b] vel:-1

Hi there ! I tried very hard, and used the doc as recomended. but the legs of my craft still do the exact same thing, even when tagging it b on one side. with the good []
What do I do wrong ? is there some example worlds or blueprint that I can use as reference ?

Let me know how she drives!. I'd be happy to look over any configurations and builds if you've got em, whether you need help or want to showcase it

Finally a mech driver script! :D

Thanks!

Looks like all I needed was to access the Ship Controller. It is done now and totally worth it. I am really glad you brought it up!

The more I hear this idea the more I like it! It looks like that script (gravity drive) got it's setup from the VTOL script and from what I can tell it is all handled by the Script. That would be even sweeter for me to keep it vanilla! I'll keep you updated!

It would be cool if it was controllable with WASD. Just like This Sciprt (Yes, It is a grav-drive script, but the concept should work!)

Awsome!