This object is in archive!
Sensor Issue
Solved
Hi hard to explain but I’m on Xbox and I’ve just started having this issue where the sensor is working fine apart from when detecting asteroid/VOXEL it seems to detect it to soon, for example I can sent all directions to 0.1 and it will say there sense asteroid/voxel when there isn’t, I’ve tried uninstalling and installing the game still doing the same thing, Thankyou
I have the same bug
Hello Engineer,
we couldn't reproduce the issue on our side. Is it happening on Single Player for you or only on DS/Lobby? Is it happening on any blueprint for you or only on specific ones? If latter, could you upload it to mod.io and share a link in this thread?
Any additional information would help.
Thank you,
Kind Regards
Keen Software House: QA Department
Hello Engineer,
we couldn't reproduce the issue on our side. Is it happening on Single Player for you or only on DS/Lobby? Is it happening on any blueprint for you or only on specific ones? If latter, could you upload it to mod.io and share a link in this thread?
Any additional information would help.
Thank you,
Kind Regards
Keen Software House: QA Department
Thanks for getting back to me much appreciated, im Unable to upload anything till weekend not at home at the moment, ive been using single player creative mode, I’ve been making a multi planetary Space X styled starship that’s fully automated, been working on it for few months now, and I use the sensors to make a smooth landing, the problem seemed to have started since the last update, for example, I could be 10 meters from the ground(asteroid) and the sensor will be set to detect asteroid at 0.1 meters and it will set the sensor off when there is no asteroid in range if I’m a lot further away it won’t sense it, but it’s working fine when detecting everything else, I’ve tried starting new games etc and still does it thanks pete
Thanks for getting back to me much appreciated, im Unable to upload anything till weekend not at home at the moment, ive been using single player creative mode, I’ve been making a multi planetary Space X styled starship that’s fully automated, been working on it for few months now, and I use the sensors to make a smooth landing, the problem seemed to have started since the last update, for example, I could be 10 meters from the ground(asteroid) and the sensor will be set to detect asteroid at 0.1 meters and it will set the sensor off when there is no asteroid in range if I’m a lot further away it won’t sense it, but it’s working fine when detecting everything else, I’ve tried starting new games etc and still does it thanks pete
Video I took of it at 0.1 m
Video I took of it at 0.1 m
Here is a example when asteroid is in range of sensor supposed to turn light on and as you can see it turns on before sensor reaches ground
Here is a example when asteroid is in range of sensor supposed to turn light on and as you can see it turns on before sensor reaches ground
Hello Engineer,
based on the videos you've provided we have managed to reproduce the issue. It's been reported to our internal system.
We will update this ticket when we have any news
Thank you,
Kind Regards
Keen Software House: QA Department
Hello Engineer,
based on the videos you've provided we have managed to reproduce the issue. It's been reported to our internal system.
We will update this ticket when we have any news
Thank you,
Kind Regards
Keen Software House: QA Department
Thankyou very much, much appreciated
Thankyou very much, much appreciated
Hi, I appreciate your busy etc but was just woundering of a idea how long does it take to fix these sorts of bugs etc thanks Pete
Hi, I appreciate your busy etc but was just woundering of a idea how long does it take to fix these sorts of bugs etc thanks Pete
Any news thanks pete
Any news thanks pete
Hello Engineer,
there are no news on this issue currently, sorry. We will update this thread when we know more.
Thank you,
Kind Regards
Keen Software House: QA Department
Hello Engineer,
there are no news on this issue currently, sorry. We will update this thread when we know more.
Thank you,
Kind Regards
Keen Software House: QA Department
Just to add to this, the issue appears to impact both the Xbox and PC versions of the game; but only the Large Grid version of the sensor.
When testing it, it looks like the Large Grid version of the sensor is adding ~15m to the sensor range when it is set to detect Asteroids/Voxels. For Example, if the Sensor is set to 5m in all directions, it starts triggering at 20m; if it is set to 2.5m in all directions, it starts detecting at ~18m; etc.
Oddly, the Small Grid version of the sensor appears to be working as expected.
Thanks!
Just to add to this, the issue appears to impact both the Xbox and PC versions of the game; but only the Large Grid version of the sensor.
When testing it, it looks like the Large Grid version of the sensor is adding ~15m to the sensor range when it is set to detect Asteroids/Voxels. For Example, if the Sensor is set to 5m in all directions, it starts triggering at 20m; if it is set to 2.5m in all directions, it starts detecting at ~18m; etc.
Oddly, the Small Grid version of the sensor appears to be working as expected.
Thanks!
Hello, Engineers!
We're happy to inform you that the upcoming "203" update contains a fix for the bug you have reported. Thank you for taking your time to inform us about this issue and making Space Engineers better.
If you are still experiencing the bug on the new version, please let us know by commenting here or opening a new thread.
We are closing this thread as "Solved".
Kind Regards,
Keen Software House: QA Department
Hello, Engineers!
We're happy to inform you that the upcoming "203" update contains a fix for the bug you have reported. Thank you for taking your time to inform us about this issue and making Space Engineers better.
If you are still experiencing the bug on the new version, please let us know by commenting here or opening a new thread.
We are closing this thread as "Solved".
Kind Regards,
Keen Software House: QA Department
Replies have been locked on this page!