Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Check the lock status on the hinges / rotors, if they are locked, it can mess up PARK.
Second thought,
Check your park group, make sure everything is in there, recompile if you have to change anything.
Third thought.
More information about your build, what you need it to do, and how it should work.
Possibly custom data from the parts that are not working.
With that information, we may be able to give more relevant advice / troubleshoot.
This will happen regardless of the step number; if a step can't be completed then none of the steps after it will run.
"Anything other than the above will be considered a command to switch profiles.
For example, typing "secondary" would cause the script to attempt to switch to that profile, and gives a warning if no such profile exists."
To control / use your Arms Profile run the PARK PB with the command Arms
To control / use your Main profile run the PARK PB with the command Main
If the currently running profile has return value set up, you can run the PARK PB with the return command to reset the profile to it's return position.
On my previous save, running all the exact same mods, with a fairly identical-ish crane truck, it worked flawlessly for weeks. (until Klang saw fit to completely destroy all that I had created)
Also huh, I am not sure what is going on, it should be converting the text to lowercase before running the command, maybe next time I mess with scripts I can go into it and see if I missed some kind of language compatibility issue.
Also thats good to know about "mult 2". Though if it doubles everything, Ide rather have the finer control over each setting with profiles.
Also if you want to increase speed you don't need to use another profile just use a run command "mult 2" for double speed "mult 1" for the normal speed set in custom data, "mult 3" for triple speed etc.
It is currently unclear if PARK is being used to steer the turret, or the entire tank.
When you hit A it goes left...
even tried to set a - rpm number didn work
Both can't use the same group name, for example "PARK", and play nice together.
Example
The PB controlling the solar array could use the group name "PARK Solar"
The PB controlling the crane could use the group name "PARK Crane"
Then it just comes down to making sure the right things are in the right groups and are set up correctly.
1. Recompile the PB EVERY TIME I change something.
2. Make sure I am changing the setting in the RIGHT PROFILE.
3. Make sure the piston/rotor/hinge I am changing IS IN THE GROUP controlled by PARK.
Number 3 got me earlier today. LOL! :-)
When I follow all three, PARK works correctly, unless I set something to the wrong value. :-)
I'm having trouble getting the Return Order Priority to work.
When i change it to anything other 0, the script seems to ignore it completely, it just run everything at position 0, then just stops.
How can i figure out what is going wrong?
Does this only happen if they are both connected to the same grid?
Might try changing the name of the PARK group on one of the PB's and see what happens.