'mul' should be set to a value, usually 1 if you want thrust.
my guess, without looking at the lua, is that its not being given a default value (say 0).
either way, set mul to 1.
the advanced wire tool is definitely bugged there tho
This is my first time to ever try using vector thrusters, so all my settings are default. When trying to wire up the x y z inputs on the vector thrusters, I get the error above.Code:entities\gmod_wire_vectorthruster\shared.lua:79: attempt to perform arithmetic on local 'mul' (a nil value)
When trying to use the advanced wire tool, and it gives you a list of inputs, the x y and z show up in the list, but they refuse to highlight like all the other inputs when scrolling through.
Using latest SVN.
'mul' should be set to a value, usually 1 if you want thrust.
my guess, without looking at the lua, is that its not being given a default value (say 0).
either way, set mul to 1.
the advanced wire tool is definitely bugged there tho
VECTOR stuff is scripted bad on wire.
Example:
When someone spawns a vector thruster, Hydraulics do not work anymore as they used to, Strings which only have 1 letter, will fuck up in adv dupe (not highlighting) and vector thruster only works if it has a mul of 999999 in there, else its just plain weak and useless.
Thought Arcooke, you can still wire the vector thruster, You just have to try to wire up X to X and Y to Y etc, without having the highlights.
No, that doesn't work Synchro. That's what I said in my original post. If I try to wire x,y,z up to anything it gives the LUA error (I was wiring it to a beacon sensor). The highlight problem is separate.
Highlighting problem is in the advanced wire tool, this does not highlight ANYTHING with x y z
What is this highlighting problem?
Second, x,y,z are fine, you also have to wire the mul, otherwise it will be multiplying by 0.
EDIT: Confirmed. Once the vector thruster's letters go lowercase, it cases a mass amount of bugs. This can be replicated by spawning a GPS and a vector thruster.
Last edited by Anticept; 06-08-2008 at 09:55 PM.
The highlighting problem I think is refering to whenver there is an X Y Z outputs on any object (this is the same for the adv pod) when using the advanced wiring tool and you try and select them, it does not highlight them. They are selected internally and you can wire stuff up to them but the green highlight does not appear.
It seems to happen whenever X Y Z are in a row and in those situations (this may be a cause, coincidence, or consequence) they are often lower case and are always not selectable when they are lowercase. GPS is not the same way.
Bookmarks