Event controller, timer, - value bug
I've been trying for several hours to build an automation of multiple actions triggered by a single event.
I proceeded step by step, breaking down the actions with several timers, and manually tested that the movements could function without collisions.
If I trigger each step manually, it works fine.
So I started automating with timers to launch the initial action, and triggering the other actions with event blocks.
That's where I'm encountering strange things, things that are difficult to reproduce when I partially rebuild the components, as if the combination itself is creating the problem.
For example, in one of the triggers, I have a hinge that goes from 180° to 0°. At 85°, I want to trigger other actions, so I configured an event block to trigger actions when the angle is equal to or less than 85°.
This doesn't work. If I change the test to greater than 85°, I see that the block goes false. I change it back to equal to or less than 85°, and then the actions trigger.
I'm also seeing inconsistent values at several levels. For example, in the actions of an event control, I configure the angle value for a hinge to 180°. If I exit the menu and return, it resets to the initial value. I've also noticed this kind of problem on the rotors.
Due to the complexity of the problem, I would like to know the best way to provide you with all the details to reproduce the issue: sharing a push button, a video, etc.
I have the same bug
Here's a video example of a hinge event that isn't triggered by default, but it is if you modify the configuration. There's a light that turns red if the condition is false (in my opinion, it should be red upon activation) and green if the condition is true.
You'll notice that I'm triggering a timer with key 4 that changes the hinge's speed so it deploys. The light is neutral (white); it should turn red to indicate that the condition is false. At 85°, the light should turn green and deploy the piston and drill, but nothing happens. If I go into the event condition and change it from less than to greater than, the light turns red (which is correct). And if I set it back to less than or equal to 85, the light turns green and deploys the drills.
So, the configurations are correct in my opinion; it's a bug in the event value detection.
The problem is, if you want to reproduce it, simply adding a hinge and piston isn't enough. I can't reproduce the bug, so it must occur with more components in a broader context.
More info on the strange behavior: yesterday when I quit the game, I saved the ship. It was completely stable, and I was outside of it, underneath it.
When I opened the game this morning, the ship was completely erratic, going haywire as soon as the game started.
I think there's also a problem with state and values, as explained in the previous message. Some values aren't being saved, and strange interactions are occurring between multiple, complex components.
Since it's an Alpha version, I completely understand, and I think my experiments can help the developers identify and fix problems that shouldn't be present in a stable version.
Since I have quite a few different bugs, some related, some not, I'm wondering if it's better to submit a bug report with multiple issues or a separate report for each bug?
Here's a video example of a hinge event that isn't triggered by default, but it is if you modify the configuration. There's a light that turns red if the condition is false (in my opinion, it should be red upon activation) and green if the condition is true.
You'll notice that I'm triggering a timer with key 4 that changes the hinge's speed so it deploys. The light is neutral (white); it should turn red to indicate that the condition is false. At 85°, the light should turn green and deploy the piston and drill, but nothing happens. If I go into the event condition and change it from less than to greater than, the light turns red (which is correct). And if I set it back to less than or equal to 85, the light turns green and deploys the drills.
So, the configurations are correct in my opinion; it's a bug in the event value detection.
The problem is, if you want to reproduce it, simply adding a hinge and piston isn't enough. I can't reproduce the bug, so it must occur with more components in a broader context.
More info on the strange behavior: yesterday when I quit the game, I saved the ship. It was completely stable, and I was outside of it, underneath it.
When I opened the game this morning, the ship was completely erratic, going haywire as soon as the game started.
I think there's also a problem with state and values, as explained in the previous message. Some values aren't being saved, and strange interactions are occurring between multiple, complex components.
Since it's an Alpha version, I completely understand, and I think my experiments can help the developers identify and fix problems that shouldn't be present in a stable version.
Since I have quite a few different bugs, some related, some not, I'm wondering if it's better to submit a bug report with multiple issues or a separate report for each bug?
I created a simple structure to try and reproduce the problem.
The example consists of a hinge and a piston. The scenario is as follows: A timer triggers an initial action, such as changing the hinge's speed to change its position, and activates an event controller corresponding to the hinge's direction of action (in this case, "Open"). Then, I have a second timer and event controller to perform the reverse scenario (in this case, "Close"). This timer will also deactivate the "Open" event controller and activate the "Close" event controller, as well as trigger the piston's refilling.
The "Open" event controller will change the piston's speed value to extend it and change the light color to green when the hinge angle is greater than or equal to 90° for the true condition. For the false condition, it will simply change the light color to red.
The "Close" event controller will modify the hinge's angular speed to retract it to its initial position and change the light color to white.
We can therefore visually detect three states with the light: green indicates the hinge is at 90° or more in the "OPEN" scenario; red indicates the hinge is at less than 90° in the "OPEN" scenario; and white indicates the piston is retracted and the hinge is returning to its initial state of 0°.
The video shows an initial state just after the hinge returns to the 0° position, with the close event controller active and the open event controller inactive.
To aid visualization, I've included blocks and a screen to indicate which one it is. Green represents "Open" and The red "Close"
So if I modify the "greater than or equal to" condition, or its opposite value, and then revert to the correct setting, the triggering works correctly.
I created a simple structure to try and reproduce the problem.
The example consists of a hinge and a piston. The scenario is as follows: A timer triggers an initial action, such as changing the hinge's speed to change its position, and activates an event controller corresponding to the hinge's direction of action (in this case, "Open"). Then, I have a second timer and event controller to perform the reverse scenario (in this case, "Close"). This timer will also deactivate the "Open" event controller and activate the "Close" event controller, as well as trigger the piston's refilling.
The "Open" event controller will change the piston's speed value to extend it and change the light color to green when the hinge angle is greater than or equal to 90° for the true condition. For the false condition, it will simply change the light color to red.
The "Close" event controller will modify the hinge's angular speed to retract it to its initial position and change the light color to white.
We can therefore visually detect three states with the light: green indicates the hinge is at 90° or more in the "OPEN" scenario; red indicates the hinge is at less than 90° in the "OPEN" scenario; and white indicates the piston is retracted and the hinge is returning to its initial state of 0°.
The video shows an initial state just after the hinge returns to the 0° position, with the close event controller active and the open event controller inactive.
To aid visualization, I've included blocks and a screen to indicate which one it is. Green represents "Open" and The red "Close"
So if I modify the "greater than or equal to" condition, or its opposite value, and then revert to the correct setting, the triggering works correctly.
Replies have been locked on this page!