is a sensor bug ?

[tripodalt]

https://steamcommunity.com/sharedfiles/filedetails/?id=3023768573
I MADE A BENCH TEST FOR SENSORS
pitch and yaw are ok
but the red color roll show a strange behavior
i triple checked the seting but maybe i missed one
its not a bad angle or scaling
its a pause before reacting and once reached continue to move
the angular test is not sucessfull i guess it requiert skill at geometry
for the normal i finally understood its vectors and i need super long slider actuator what will mYBE REQUIERT A CAMERA TRACKER OR SUCH HUGE COMPLEX DEVICE
https://steamcommunity.com/sharedfiles/filedetails/?id=3023767607
if you want to check or it its already a know bug or if its obivious and im not aware let me know

[AC Dosage]

Sensors zero when spawned and start from there.

Actuators should be on seek mode this makes them try to get to input +/- #s.

Actuators on accumulated mode add/subtract from their current position while +/- input and hold position after 0/neutral input.

Actuators of different types rotate at different speeds so their speeds need adjusting if synchronizing between actuator types, there is a demo in the workshop by litchysu or armoured soul i think.

[AC Dosage]

You will have to fill in for the new actuators that aren't included.

https://steamcommunity.com/sharedfiles/filedetails/?id=2389312214

[AC Dosage]

Note : With world space off make sure red widget is aligned with the front axis of the creation so pitch and roll work as intended. The metal face of a sensor is considered the normal.

[AC Dosage]

I had just run into this issue with your demo, i was in world space so i thought there was an issue with sensors so keep that in mind when placing sensors.

[tripodalt]

ok for the metal face normal
ok for the metal face normal = unsnapable hole axis
red widget the roll axis
if you try my demo the red roll test fail at half and its very strange not as if i messed the axis or the seting it follow with delay and continue to rotate after
i updated for the normal angle speed but your metal info was my issue
and the angle speed i not found how to calcul
the seeking seem the most easy but i dont reached to understand the setings
i found an old post of 2019 that i have to digest:
The max is the ceiling for the input, and vice versa for the min.

Say, for example, you had a proximity sensor with the max at 5 and the min at 3. If the nearest object was 4 meters away (13.33 blocks; one block is 30cm), the output of the sensor would be 50%. If it was 4.5 meters away, it would be 75%, and so on for other distances.
If the max was say, 7, then 5 meters would be 50%

It creates a sort of gradient between the min and Max values for the outputs.
Everything above the max value outputs 1, anything below outputs 0.

The same applies to speed, acceleration, and other sensors.


If you make the max higher than the minimum, everything outside of the max-min range activates the thruster. So if the max was 3, and the minimum was 5, 1 would activate the sensor but 4 wouldn't.

[tripodalt]

Originally posted by AC Dosage:

Note : With world space off make sure red widget is aligned with the front axis of the creation so pitch and roll work as intended. The metal face of a sensor is considered the normal.

the red widget direction is the normal +
at least from the youtube tutorial i just seen

[AC Dosage]

The metal face is the normal for use with sensor modes with normal in the name, the red widget is just the direction the sensor should be aligned with the front of a creation or the direction of travel so you get the results you'd expect. If you want measurements in a specific direction the normal modes are very helpful and the metal screen is what is referred to as the normal.

Non-normal modes i believe are from where the sensor is spawned out in all directions which is useful in fewer situations than the normal modes which are focused and linear from the point of spawn, been a while since i looked at non-normal sensor behavior because i found normal mode so useful but it may not allow for negative measurement, zero being the center i think it just counts from zero/origin up.

https://en.wikipedia.org/wiki/Normal_(geometry)

[tripodalt]

maybe its like you say but i found it counter intuitive if other sensor use the red widget as reference and not this one
can you just workshop a bench demo for ilustration i bet it will help all the noobs and get huge counts
i checked normal definition and it dont make mention of normal angular speed
from the tutorial of a non expert all non normal refert to positive value in any direction when normal is a single direction who can be minus or plus

[tripodalt]

thx for the help about seeking and normal speed
i reached to use the normal speed for stabilisation and updated the bench test
i also found that not a bug but again i messed with the forward red widget direction
for the normal angular speed i dont found the seting and i will check the other bench linked
https://steamcommunity.com/sharedfiles/filedetails/?id=3023767607

[AC Dosage]

https://steamcommunity.com/sharedfiles/filedetails/?id=3024616120

[tripodalt]

I UPDATED MY BENCH I WAS WRONG BECAUSE THE NORMAL ANGLE SENSOR MUST SIGHT THE OUTSIDE OF THE RADIUS WITHE THE FLAT GRID AND I GUESS THE RED WIDGET HAVE TO BE IN THE TURN DIRECTION