@lafario I was lucky I clicked on this notification first - I was curious what you meant by "trolling". But thanks for the laugh! Btw, do you want to test a new program? I want to test its behaviour on other devices, you can find it here. Edit: Oops, wrong link, it's here.
@lafario I‘ll send you a pic later, currently can‘t play. You should be able to control the thrust once the AG is disabled though, can you send me a pic of your program?
@lafario In case you do: In this (gif again) program, the values are calculated. Depending on how strong your engines are, you might have to change the 30 in the / block. I didn't use if ... else ... here because the calculated value is already 0 when you're too fast. Edit: If the link doesn't work again, try this
@lafario Instantly isn't possible. Vizzy can control the craft like a player does, but it can't cheat (which instant speed / altitude changes would be).
@lafario You could try sth like this. Basically, it repeatedly checks if you are too slow (in which case it goes full throttle) or if you are too fast (-> Throttle 0%).
@lafario Once you're back: The link I sent you is a gif, but you'll have to wait a bit until it starts. In the beginning, it's the same as the 2nd image, but then it shows what you have to do.
@HermesAerospace Aber ich kann (wahrscheinlich aber auch in einem Update) versuchen, von AGs auf Buttons umzustellen. Dann kann man immer noch wählen, hat aber trotzdem alle AGs frei.
@HermesAerospace Das Problem mit Monden ist, dass Ellipsen auf MfDs immer bunt ausgefüllt sind. Wenn man nur eine Ellipse hat (für das Craft), kann man einfach eine schwarze, etwas kleinere an der gleichen Stelle spawnen, bei mehreren (Craft + Mond(e)) geht das aber nicht so einfach. Deshalb wird das wohl eher etwas für ein späteres Update (wenn ich es überhaupt umsetzen kann). Für das System bezweifle ich, dass jeder hier das metrische kann (auch wenn es in der Raumfahrt natürlich Standard ist), und weil 2 Systeme nicht zu viel zusätzliche Arbeit sein sollten, werde ich wohl versuchen, beide zu machen.
@HermesAerospace Ich habe gerade mal meine Gedanken zur neuen Idee festgehalten. Hier ist die aktuellste Version. Die AG für Monde wird schwer, die kann ich ja aber auch später noch hinzufügen. Was denkst du?
@HermesAerospace Ich habe gerade leider doch noch ein Problem gefunden: Das Programm funktioniert wohl nur mit einem perfekt runden Orbit. Bei allem anderen stimmt das Ergebnis nicht. Ich wollte nämlich dieses Programm benutzen.
@HermesAerospace Der Orbit funktioniert tatsächlich. Da ich ja schon ein Programm für die Karte habe (Custom Map), wird dein Vorschlag wahrscheinlich Version 1.1. Das einzige, was beim Berechnen leider ignoriert wird, ist die Rotation von Droo.
@HermesAerospace Die Liste und die Karte selbst sollten kein Problem sein. Für den Orbit muss man die Position in der Zukunft voraussagen. Das wird kompliziert, könnte aber mit viel Glück funktionieren. Da muss ich mal ein bisschen herumprobieren, ich melde mich dann bald wieder bei dir.
@lafario Turns out, the game spawns you just slightly above ground. That's why the vizzy thinks you aren't grounded for the first few frames. Putting "Wait 1 Second" in the beginning should fix it.
@lafario I'm not sure about the Drood. As it doesn't seem to have Additional settings (or Tinker panel), I can't think off a way to get its id, or add a flight program. Might be possible by having a look in the XML, but Android doesn't like that.
@lafario Isn't that what you want it to do? You're below the minimal speed and you're in the air, so it explodes. Reply to the Explodes when starting game comment
Almost. Just one tiny mistake in the second part of the "Wait until" block: You want it to check if the length of velocity Surface is below 200, your program gets the length of velocity Surface < 200. So, currently, that part looks like this:
(velocity Surface < 200)length
But you want it to look like this:
(velocity Surface)length < 200
You need a "<" block for the speed. In the left side of that, you put the "(velocity Surface)length", in the right side you put the speed. Then, that whole thing (the filled < block) is put into the "and" block (which side doesn't matter here). And in the other side, you put the "not(misc Grounded)".
3 mistakes:
1. Where you entered "Fuel Tank", you need the id of that fuel tank. Click on the fuel tank in the designer and open its properties. In "Additional Settings", you can find its id.
2. "Activated" just activates it. Click on "Activated" and choose "Explode" instead.
3. The blue part in the "Wait until..." block is a bit wrong. Make sure it looks exactly like the one in the picture I sent you before.
@lafario What happened to your question (the display text one)?
+1 7 months ago@lafario So the display screen is a MfD?
7 months ago@lafario What is "it"? You can't click a vizzy, you need a part that can be clicked (or an AG). What should that part / AG be?
7 months agoWhat should be clicked? A Button on a MfD or an AG?
7 months ago@lafario I was lucky I clicked on this notification first - I was curious what you meant by "trolling". But thanks for the laugh! Btw, do you want to test a new program? I want to test its behaviour on other devices, you can find it here.
+1 7 months agoEdit: Oops, wrong link, it's here.
Even ChatGPT told me I probably found a bug...
+1 8 months ago@lafario If target node can't do it, I don't know what else could, but a second target node won't help
8 months ago@lafario That‘s strange, as far as I know
8 months agotarget node ...should work for crafts@lafario Doesn‘t it already work on crafts?
8 months ago@lafario Best I could find is this. It gets you within 3 m/s on the default plane.
8 months ago@lafario The speed probably is because the throttle gets quite low once you‘re close to the target speed. I‘ll try a few more equations…
+1 8 months ago@lafario You used 2 different AGs. First you used 3, then 1.
8 months ago@lafario I‘ll send you a pic later, currently can‘t play. You should be able to control the thrust once the AG is disabled though, can you send me a pic of your program?
8 months ago@VectronTechnologies Often not what I asked for, but at least they look good.
8 months ago@lafario Or you could try
8 months agosqrt(x - speed) / 10@lafario If the thrust is too low, put a lower number where the 30 is (like 20 or even 10). That should improve it.
8 months ago@lafario In case you do: In this (gif again) program, the values are calculated. Depending on how strong your engines are, you might have to change the 30 in the
8 months ago/block. I didn't useif ... else ...here because the calculated value is already 0 when you're too fast.Edit: If the link doesn't work again, try this
@lafario You mean for auto throttle?
8 months agoThe GPT I used: ChatGPT - image generator
8 months ago@lafario Wdym make Throttle smoother? And for the targeting:
8 months ago@lafario Instantly isn't possible. Vizzy can control the craft like a player does, but it can't cheat (which instant speed / altitude changes would be).
8 months ago@lafario You could try sth like this. Basically, it repeatedly checks if you are too slow (in which case it goes full throttle) or if you are too fast (-> Throttle 0%).
8 months ago@lafario No problem
8 months ago@lafario Perfect, now you just have to put a "Wait 1 second" in front of everything else. Then, it should work.
8 months ago@lafario Try this link
8 months ago@Babrivin1946 Thanks! I'm already back, but I did.
8 months ago@lafario Once you're back: The link I sent you is a gif, but you'll have to wait a bit until it starts. In the beginning, it's the same as the 2nd image, but then it shows what you have to do.
8 months ago@lafario https://i.im.ge/2025/03/26/p02G8P.az-recorder-20250326-181809.gif
8 months ago@HermesAerospace Deshalb will ich, dass man sie ausblenden kann. Sie sind nur für Mondmissionen und Gravity Assists sinnvoll.
8 months ago@lafario This time it's the first part of the Wait until. You need to put the misc Grounded in a not(), and that not(misc Grounded) in the ( ) and ( )
8 months ago@HermesAerospace Aber ich kann (wahrscheinlich aber auch in einem Update) versuchen, von AGs auf Buttons umzustellen. Dann kann man immer noch wählen, hat aber trotzdem alle AGs frei.
8 months ago@HermesAerospace Das Problem mit Monden ist, dass Ellipsen auf MfDs immer bunt ausgefüllt sind. Wenn man nur eine Ellipse hat (für das Craft), kann man einfach eine schwarze, etwas kleinere an der gleichen Stelle spawnen, bei mehreren (Craft + Mond(e)) geht das aber nicht so einfach. Deshalb wird das wohl eher etwas für ein späteres Update (wenn ich es überhaupt umsetzen kann). Für das System bezweifle ich, dass jeder hier das metrische kann (auch wenn es in der Raumfahrt natürlich Standard ist), und weil 2 Systeme nicht zu viel zusätzliche Arbeit sein sollten, werde ich wohl versuchen, beide zu machen.
8 months ago@HermesAerospace Ich habe gerade mal meine Gedanken zur neuen Idee festgehalten. Hier ist die aktuellste Version. Die AG für Monde wird schwer, die kann ich ja aber auch später noch hinzufügen. Was denkst du?
8 months ago@HermesAerospace Das wäre viel einfacher
8 months ago@HermesAerospace Ich habe gerade leider doch noch ein Problem gefunden: Das Programm funktioniert wohl nur mit einem perfekt runden Orbit. Bei allem anderen stimmt das Ergebnis nicht. Ich wollte nämlich dieses Programm benutzen.
8 months ago@lafario That's strange, it works fine for me. Could you send me a screenshot of your vizzy again?
8 months ago@HermesAerospace Der Orbit funktioniert tatsächlich. Da ich ja schon ein Programm für die Karte habe (Custom Map), wird dein Vorschlag wahrscheinlich Version 1.1. Das einzige, was beim Berechnen leider ignoriert wird, ist die Rotation von Droo.
8 months ago@HermesAerospace Die Liste und die Karte selbst sollten kein Problem sein. Für den Orbit muss man die Position in der Zukunft voraussagen. Das wird kompliziert, könnte aber mit viel Glück funktionieren. Da muss ich mal ein bisschen herumprobieren, ich melde mich dann bald wieder bei dir.
8 months ago@HermesAerospace Und für die Karte: eher so wie die hier oder eher so?
8 months ago@HermesAerospace Also ein MfD mit einer Karte vom Orbit und einer Liste mit allen Daten (Geschwindigkeit, Höhe, Treibstoff, ...)?
8 months ago@lafario Turns out, the game spawns you just slightly above ground. That's why the vizzy thinks you aren't grounded for the first few frames. Putting "Wait 1 Second" in the beginning should fix it.
8 months ago@lafario Oh, now I get it. I currently can‘t try it myself (makes debugging way easier), but I should know more in a few hours.
8 months ago@lafario I'm not sure about the Drood. As it doesn't seem to have Additional settings (or Tinker panel), I can't think off a way to get its id, or add a flight program. Might be possible by having a look in the XML, but Android doesn't like that.
+1 8 months ago@lafario Isn't that what you want it to do? You're below the minimal speed and you're in the air, so it explodes.
8 months agoReply to the Explodes when starting game comment
Oh, and there is sth else you forgot: You still need to click on "Activated" (on the last block) and choose "Explode" instead
8 months agoAlmost. Just one tiny mistake in the second part of the "Wait until" block: You want it to check if the length of velocity Surface is below 200, your program gets the length of velocity Surface < 200. So, currently, that part looks like this:
8 months ago(velocity Surface < 200)length
But you want it to look like this:
(velocity Surface)length < 200
You need a "<" block for the speed. In the left side of that, you put the "(velocity Surface)length", in the right side you put the speed. Then, that whole thing (the filled < block) is put into the "and" block (which side doesn't matter here). And in the other side, you put the "not(misc Grounded)".
8 months ago3 mistakes:
1. Where you entered "Fuel Tank", you need the id of that fuel tank. Click on the fuel tank in the designer and open its properties. In "Additional Settings", you can find its id.
2. "Activated" just activates it. Click on "Activated" and choose "Explode" instead.
3. The blue part in the "Wait until..." block is a bit wrong. Make sure it looks exactly like the one in the picture I sent you before.
Pictures
Where to find the part id?
How the blue part should look
8 months agoI can't see the picture (I assume there is one...). Can you send me the link?
8 months agoEdit: Can see it now
@lafario You mean the one in the “Wait until …“ block? That‘s the only blue part
8 months ago