Event controller not registering altitude
Need More Information
I built a drone with an event controller to trigger at 500m but the altitude on the controller remains at 3m, its altitude on being built on my base.
If I copy and paste the drone at height the event controller registers the correct altitude
I have seen others with similar issues of altitude not updating in the controller but no solution
I have the same bug
Hello, Engineer!
Thank you for reaching out with this issue. We were unfortunately not able to reproduce the issue on our end. Could you please provide some additional information for the issue? Is this happening in a single player game or on a server? Does it happen constantly and on different grids or setups, or is the issue only with this particular one?
You can access your blueprints files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers\Blueprints. Select the correct folder where your blueprint is saved (local or cloud), zip the file and attach it here. Alternatively you could also share the world where the issue is happening saved in \Roaming\SpaceEngineers\Saves.
Thank you very much.
Kind regards,
Keen Software House: QA Department.
Hello, Engineer!
Thank you for reaching out with this issue. We were unfortunately not able to reproduce the issue on our end. Could you please provide some additional information for the issue? Is this happening in a single player game or on a server? Does it happen constantly and on different grids or setups, or is the issue only with this particular one?
You can access your blueprints files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers\Blueprints. Select the correct folder where your blueprint is saved (local or cloud), zip the file and attach it here. Alternatively you could also share the world where the issue is happening saved in \Roaming\SpaceEngineers\Saves.
Thank you very much.
Kind regards,
Keen Software House: QA Department.
Thanks for looking into this for me
Single player, local PC
The problem appears to only occur when the drone is initially connected via a merge block
A stand-alone drone works OK
Placing the drone on a connector, no merge block, it works OK
Hope this helps
Thanks for looking into this for me
Single player, local PC
The problem appears to only occur when the drone is initially connected via a merge block
A stand-alone drone works OK
Placing the drone on a connector, no merge block, it works OK
Hope this helps
Having the same problem, I have done some testing, this is what I found so far and could reproduce somewhat reliably.
I built a simple merged ship that broadcasts a message when it reaches 10m on side [A] and 11m on side [B], it has an event block, broadcast controller and antenna on both sides.
For the tests, spawn the attached blueprint on the ground, set both thrusters to full override and press the button (wich unmerges the grids), the altitude for the [B] event block is frozen at ground (or rather at now [A] grid) level.
If you update (place or remove) any block on the grid before pressing the button, it works as intented.
However, whether or not you update any block if the last blocks you place are another pair of merge blocks, when unmerged the event block will get frozen again.
In any of the cases, when the elevation of the oposite grid ([A]) updates, it also unfreezes the frozen one ([B]).
It does not seem to happen if only side [B] has an event block.
Maybe it can help finding the problem.
Having the same problem, I have done some testing, this is what I found so far and could reproduce somewhat reliably.
I built a simple merged ship that broadcasts a message when it reaches 10m on side [A] and 11m on side [B], it has an event block, broadcast controller and antenna on both sides.
For the tests, spawn the attached blueprint on the ground, set both thrusters to full override and press the button (wich unmerges the grids), the altitude for the [B] event block is frozen at ground (or rather at now [A] grid) level.
If you update (place or remove) any block on the grid before pressing the button, it works as intented.
However, whether or not you update any block if the last blocks you place are another pair of merge blocks, when unmerged the event block will get frozen again.
In any of the cases, when the elevation of the oposite grid ([A]) updates, it also unfreezes the frozen one ([B]).
It does not seem to happen if only side [B] has an event block.
Maybe it can help finding the problem.
Replies have been locked on this page!