-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comp_numeric_transition incorrectly stops after only 40% done #265
Comments
Oh I actually noticed this the other day when trying to use it with a light pattern input in PEE, I just figured it was toggleable lights being buggy and gave up and reverted it to how it was before |
Created a separate issue for deceleration bug mentioned here: #266 |
Confirming it stops at 40% specifically, when the end value is set to 3, it ends at about 1.2, which is 40% of 3. |
What mode do you have it set to? Note that the start/end value is always a "position" value, then depending on the mode it might output a velocity instead. If you set it to speed, it might be expecting to adjust the speed of the train so it moves 1 unit, explaining the small speeds. Also, I did make a example map showing a few ways to use this ent. |
It's set to "Adjust Velocity".
The previous version of HA worked fine. I am using floats between 0 and 1 because |
In the current version, "instantly set" seems to work for this purpose |
The other modes don't seem to be doing the right thing though. |
I am trying to set up a
comp_numeric_transition
to make an elevator (func_tracktrain
) speed up. Before updating HammerAddons,comp_numeric_transition
worked fine for speeding up but not slowing down. Now, when the Start Value keyvalue is 0 and the End Value keyvalue is 1, thecomp_numeric_transition
stops at roughly0.4
and then triggers its ownEnableRefire
input, which i guess indicates it considers itself ready, which it is not.Only by setting the ending value to a higher number (e.g. 3) i was able to get proper elevator acceleration / speed up.
I'm not sure if the deceleration issue is fixed in the new version. If it isn't, i will create a new issue.
The text was updated successfully, but these errors were encountered: