But this results in two different tiers remaining the same speed. I've tried isolating each level so that only one trait is active at a time but that doesn't seem to work at all.
Graion Dilach wrote:To put it more bluntly: traits which support multiple instances can be used as an if/elseif situation, with each "else statement" would be provided through separate trait instances. However condition support != multiple traits support, there are a few conditionable traits which can't have multiple instances without bugs/crashes
Graion Dilach said this in a omnom thread that also brought up speedmultiplier. Is this a case of traits having bugs with multiple instances? Or is there potential for a work around?
Blackened wrote: ↑
But this results in two different tiers remaining the same speed. I've tried isolating each level so that only one trait is active at a time but that doesn't seem to work at all.
You're not seeing any change in speed because there is no difference between speeds 113 and 107 (95%).
If you want to check this try creating a duplicate transport but with speed 107, you'll notice it's the same speed as the 113 transport.
Some LST speed windows:
[103-113]
[94-102]
[86-93]
[79-85]
[74-78]
[69-73]
Speedmultiplier stacks with previous ones. So with the 95--80 the final speed is actually 58% of the instead of 80.
I haven't tried that second option as I was using && by recommendation from Sircake but that didn't work. I'll try it with ! and see if I get any results.
is what's missing from what I'd guess. The game doesn't know what the "Loaded" condition would be otherwise. If I'm correct that will fix the OP setup.
The other setup - condition expressions doesn't support commas, you need to use && for the and condition, so it should look like Loaded >= min && Loaded < max.
Frame_Limiter wrote: ↑
You're not seeing any change in speed because there is no difference between speeds 113 and 107 (95%).
If you want to check this try creating a duplicate transport but with speed 107, you'll notice it's the same speed as the 113 transport.
Some LST speed windows:
[103-113]
[94-102]
[86-93]
[79-85]
[74-78]
[69-73]
This seems to be the root of the problem. I couldn't create a duplicate LST because the code refuses to cooperate (looking at you mysterious idle sequence)
I'd set the speed to 105 as the default was way too fast.
And so it would be:
105 (empty)
99.75(100 or 99)
94.5(95 or 94)
89.25(90)
84
As you said there is no difference between 100-94. I'll have to find another work around