Important:
This version has a bug where the sensor is limited to a quarter of its intended search area! Please use this fix instead!
Motion Detector
V1.0
Introduction
This craft comes with three sensors of different sizes, ranging from a diameter of 10cm to 60cm. Each sensor is designed to be put on any other craft where it can automate various tasks. It continuously scans a range of ~70° for any movement. Whenever it detects a movement, it warns you in the command disc's local log and broadcasts "movement" to nearby crafts. This broadcast can then be used to automate anything from lights to alarm systems.
Range
Each sensor scans a range of approx. 70° in the direction it's facing. By default, it has a range of 10 m, however, you can easily modify this by changing range in the Vizzy.
The Warning
Each sensor warns you in two ways:
1. Local Log
You can find the first warning in the command disc's local log. Additionally, it returns the estimated size of the moved object. This number ranges from 0 to 1 with 1 being the entire scanned area.
2. Broadcast
To use the sensor for other Vizzys, you can use the second warning. Each sensor broadcasts "movement" to nearby crafts whenever a movement is detected. Additionally, the same estimation as in the local log is transmitted in the data.
Credits:
This craft, including Vizzy and sensors, was entirely made by me (TheVizzyLucky).
If you upload any craft that uses this, please credit me.
- Motion Detector by [TheVizzyLucky](https://www.simplerockets.com/c/9CB6Za/Motion-Detector-V1-0)
Note: This is just an example. You can copy this or write your own.
And with that, thanks to everyone who downloads this. If you like my crafts, please consider upvoting them so more people can see them - Thanks!
Vizzy Problems?
GENERAL INFO
- Predecessor: Movement Detector | V0.2b
- Created On: Android
- Game Version: 1.3.114.0
- Price: $10k
- Number of Parts: 10
- Dimensions: 1 m x 1 m x 1 m
PERFORMANCE
- Total Delta V: 0m/s
- Total Thrust: 0N
- Engines: 0
- Wet Mass: 433kg
- Dry Mass: 433kg
STAGES
| Stage | Engines | Delta V | Thrust | Burn | Mass |
|---|
11 Comments
- Log in to leave a comment
-
-
2,214 TheVizzyLucky+2 one month ago
@OrionTechnologies @ergiThe24 @Silverback @Brkknight @StocktonAerospace @lafario @Spenzerointernational @shushijie @Cyberstar3964
First of all, sorry for tagging you all.
There is a big bug in this version that limits the sensor to a quarter of its intended search area. Since you have upvoted this, I assume you might want to use it at some point - sorry for the tag if not - I tagged you here so you can use the fixed version instead.Fix
Also, thanks for your upvotes!
-
-
-
-
-
-
-
-
About the bug:
Each sensor scans its surrounding with two nested for loops whose local variables are used in a vector that represents the direction of the ray. These values should go from -0.7 to 0.7, in steps of 0.1. However, this seems to be working until the variables approach the floor of the end value, which in this case is 0. That's why they go from -0.7 to -2e-17 (don't ask me why it's not 0). The resulting search area looks like this:
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
■■■■■■■■□□□□□□□
□□□□□□□□□□□□□□□
□□□□□□□□□□□□□□□
□□□□□□□□□□□□□□□
□□□□□□□□□□□□□□□
□□□□□□□□□□□□□□□
□□□□□□□□□□□□□□□
□□□□□□□□□□□□□□□
□ = Intended search area
■ = actual search area
The Fix
Once I knew what caused the problem, the fix was actually pretty simple: I just set it to go from -7 to 7 (step size 1 now) and divided the values by 10 when used.