@TheVizzyLucky Thx man!

@lafario
Vorenda:
![](https://jundroo.blob.core.windows.net/simplerockets/files/2025/2/15/8hI2TQ/UserView-0.jpg)
Maia:
![](https://jundroo.blob.core.windows.net/simplerockets/files/2025/2/15/7qN066/UserView-0.jpg)

Could you get a picture link for the planets I've made, Thier called Vorenda and Maia? I need them for a post amma make

@Survisor Theoretically, V0.2 can track satellites, but I don't think the zoom is good enough for that.

@Survisor It currently can't track satellites, I'll try to implement it in a future update.

@TheVizzyLucky the text one seems very easy to understand, Thx again man!

@lafario The blue texts are links, you make them with [text](link), so, for example, if you want the text to say "google" and the link is "https://www.google.com" it looks like this: [google](https://www.google.com)
The lines are much easier, that's just three underscores.
Everything is explained here.

@TheVizzyLucky how did you make the text in your bio blue, Also how did you make them fading lines.

@TheVizzyLucky ok ty man!

@lafario Sure, I'll try tomorrow.

@TheVizzyLucky can you do it for me I've tryed and its not working!

@lafario That's done with min FOV and camera size. You can set scale in cameraVantage to a high value and set part scale to a low value.

@TheVizzyLucky How do I make it so I can zoom in really close on mars jupiter? etc.

@lafario In Tinker Panel. Camera's properties > open Tinker Panel > click on "Edit hidden properties" > find tab "CameraVantage" (2 to the left I think) > find property "fieldOfViewMin", Change that to a really low value just over 0 (like 0.0005). Wasn't it tinkered before?
Edit: Just saw your new comment; You could try 0.0005 as fieldOfViewMin, I think that should increase your max zoom.

@TheVizzyLucky My setup: Field of view: Is -50
Field of view max: Is 300
Field of view min: Is -70

@TheVizzyLucky we're do i find the fov??

@lafario If there are any problems when implementing, feel free to ask. Also, you could try sth like 0.0005 as min FOV, maybe that increases the max zoom... I don't know how the game handles negative FOVs, so I can't predict how much improvement there is though.

@TheVizzyLucky nice

@lafario That's what the program is for. By only for satellites I meant it only works on cameras mounted on a satellite, it can target anything.

@TheVizzyLucky Am not really sure, mine make to look at planets

@lafario Simple, but cool. What's the max zoom? You could additionally make a simple tracking program (it's actually easy for satellites):
while (true) {
wait until (activation group 1);
set targetVar to user input (Enter target:);
set targetVar as target;
lock heading on target;
wait until (not(activation Group 1));
lock heading on none;
}
(targetVar is a variable)
That's everything you need for a simple tracking program (only on satellites). Of course, there are lots of ways to make this more complicated though.

Check my craft out, Its called PlanetsSope.

@Survisor Thanks for the tip, going to move the chip up in the next update. I think the targeting is a bit off because of calculation inaccuracies of the game (not entirely sure though), and these inaccuracies are multiplied because of the zoom (0.00083% of default FOV + huge camera (size increases zoom further)). That‘s why I added Pitch and Yaw control for correction. Or are the inaccuracies so high that you can‘t correct them?

Edit: Another thought: Where do you spawn the telescope? What‘s the heading? Heading correction doesn‘t work yet and I didn‘t test many different positions, so that could be the cause too.
A third thought: Did you test it on moons / planets? Since this wasn‘t intended to be used for satellites, I didn‘t test that.
Edit 2: Found the reason for the inaccuracies! It was the weight. This will be fixed in the next update, but you can tinker mass scale of all parts above the hinge rotator to 0% on this version to make it accurate. Going to test it on sattelites soon to tell you more about that.
Edit 3: I tried moving the command chip up, but that didn't help. The shaking is probably because the camera isn't moved continuously, it calculates the angles and moves the camera to the newest position. That way it 1. actually shakes a tiny bit and 2. the target's movement isn't cancelled perfectly. But you can minimize the shaking by slowing down time.

You should move the chip on the bottom to somewhere on the top so the bottom is actually flat and dont move. And also it never move the camera to the center of the target, it cant even target a geosynced sat.