@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 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 Oh, I just noticed I forgot sth in the picture: In the picture, “Activated“ of all the parts was set to “0“, you‘ll need to set “Explode“ to “1“.
@lafario limit is the speed (in m/s) you need to fly so the aircraft doesn't explode. E.g., if your part ids are 4, 52 and 137 (you'll probably need more exploding parts than 3 though) and the airplane should explode below 100 m/s, the program will look like this:
Wait until ( (speed surface)length < 100 )
Set part 4 Explode to 1
Set part 52 Explode to 1
Set part 137 Explode to 1
Btw, this program also runs on the ground. If it should only run while you're actually in the air, the first block looks like this instead:
Wait until ( ( (velocity surface)length < 100 ) and ( not( misc Grounded ) ) )
@lafario Finally found time to explain: First, you'll need to use "wait until (velocity surface)length < limit". Then, you'll need to find the id of the most important parts. I recommend the biggest fuel tanks (for a big explosion) and the command chip (to make sure the "core" explodes). You can find the id in the part's advanced properties. You'll have to experiment a bit for the amount of parts: too few parts and not everything might be destroyed, too many is just unnecessary work, and an unnecessary long vizzy. For the explosion, there is a simple vizzy block. Put a "Set part id Explode to 1" for every part you want to explode. If you do this for enough parts, the rest will be destroyed by these explosions too. You might have to put the command chip's explosion in the end though, otherwise everything you want to explode after might not be destroyed.
@lafario Thanks! It was fun, even though the snow already started melting. Btw, I just saw your request, going to send you the program soon - I'm going to bed now though.
If both (height and speed) need to meet these requirements, you can use this program:
if (altitude ASL <= 15000 or (velocity)length < 2 * mach speed) {
Set part engine's part id activated to false;
}
If only one of these requirements needs to be met, you can use "and" instead of "or" in the if block. If you need help doing that, you can send me the craft if you want. Edit: Forgot to mention before: You need to put all this in a "while (true)" block. Also, I just fixed a small mistake in the program. Edit 2: Note: This deactivates the engine, so you'll have to manually activate them afterwards. If you want it to be automatically activated, you can add
else {
Set part engine's part id activated to true
}
They seem to be using Markdown for formatting. There are some good markdown tutorials out there (linked one is just an example). Note that simplerockets.com doesn't support html, so things like <br> (in general: Most things that use <...>) won't work. Still, there are some more possibilities that aren't mentioned here, so maybe you could add a note, maybe with a link? (Or, quick alternative, pin this comment)
@lafario I got a notification telling me that you mentioned me in a post called "Picture gallery", but I can't find that. Anything you still want to tell me?
@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?
2 months ago@VectronTechnologies Often not what I asked for, but at least they look good.
2 months ago@lafario Or you could try
2 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.
2 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
2 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?
2 months agoThe GPT I used: ChatGPT - image generator
2 months ago@lafario Wdym make Throttle smoother? And for the targeting:
2 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).
2 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%).
2 months ago@lafario No problem
2 months ago@lafario Perfect, now you just have to put a "Wait 1 second" in front of everything else. Then, it should work.
2 months ago@lafario Try this link
2 months ago@Babrivin1946 Thanks! I'm already back, but I did.
2 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.
2 months ago@lafario https://i.im.ge/2025/03/26/p02G8P.az-recorder-20250326-181809.gif
2 months ago@HermesAerospace Deshalb will ich, dass man sie ausblenden kann. Sie sind nur für Mondmissionen und Gravity Assists sinnvoll.
2 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 ( )
2 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.
2 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.
2 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?
2 months ago@HermesAerospace Das wäre viel einfacher
2 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.
2 months ago@lafario That's strange, it works fine for me. Could you send me a screenshot of your vizzy again?
2 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.
2 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.
2 months ago@HermesAerospace Und für die Karte: eher so wie die hier oder eher so?
2 months ago@HermesAerospace Also ein MfD mit einer Karte vom Orbit und einer Liste mit allen Daten (Geschwindigkeit, Höhe, Treibstoff, ...)?
2 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.
2 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.
2 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.
2 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
2 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:
2 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)".
2 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
2 months agoI can't see the picture (I assume there is one...). Can you send me the link?
2 months agoEdit: Can see it now
@lafario You mean the one in the “Wait until …“ block? That‘s the only blue part
2 months agoThe first reference material (B14643 I think) doesn‘t work… I‘m redirected to a “buy this Domain!“ website. Otherwise, great guide!
2 months ago@lafario Oh, I just noticed I forgot sth in the picture: In the picture, “Activated“ of all the parts was set to “0“, you‘ll need to set “Explode“ to “1“.
2 months ago@lafario That example will look like this.
2 months ago@lafario limit is the speed (in m/s) you need to fly so the aircraft doesn't explode. E.g., if your part ids are 4, 52 and 137 (you'll probably need more exploding parts than 3 though) and the airplane should explode below 100 m/s, the program will look like this:
Wait until ( (speed surface)length < 100 )
Set part 4 Explode to 1
Set part 52 Explode to 1
Set part 137 Explode to 1
Btw, this program also runs on the ground. If it should only run while you're actually in the air, the first block looks like this instead:
Wait until ( ( (velocity surface)length < 100 ) and ( not( misc Grounded ) ) )
2 months ago@lafario Finally found time to explain: First, you'll need to use "wait until (velocity surface)length < limit". Then, you'll need to find the id of the most important parts. I recommend the biggest fuel tanks (for a big explosion) and the command chip (to make sure the "core" explodes). You can find the id in the part's advanced properties. You'll have to experiment a bit for the amount of parts: too few parts and not everything might be destroyed, too many is just unnecessary work, and an unnecessary long vizzy. For the explosion, there is a simple vizzy block. Put a "Set part id Explode to 1" for every part you want to explode. If you do this for enough parts, the rest will be destroyed by these explosions too. You might have to put the command chip's explosion in the end though, otherwise everything you want to explode after might not be destroyed.
2 months ago@lafario A program were if you fly lower than a set speed your airplane explodes.
2 months ago@lafario Thanks! It was fun, even though the snow already started melting. Btw, I just saw your request, going to send you the program soon - I'm going to bed now though.
2 months agoIf both (height and speed) need to meet these requirements, you can use this program:
3 months agoif (altitude ASL <= 15000 or (velocity)length < 2 * mach speed) {
Set part engine's part id activated to false;
}
If only one of these requirements needs to be met, you can use "and" instead of "or" in the if block. If you need help doing that, you can send me the craft if you want.
Edit: Forgot to mention before: You need to put all this in a "while (true)" block. Also, I just fixed a small mistake in the program.
Edit 2: Note: This deactivates the engine, so you'll have to manually activate them afterwards. If you want it to be automatically activated, you can add
They seem to be using Markdown for formatting. There are some good markdown tutorials out there (linked one is just an example). Note that simplerockets.com doesn't support html, so things like <br> (in general: Most things that use <...>) won't work. Still, there are some more possibilities that aren't mentioned here, so maybe you could add a note, maybe with a link? (Or, quick alternative, pin this comment)
Edit: Another Markdown tutorial
3 months agoEdit 2: Even more tutorials and Cheat Sheets:
https://www.markdownguide.org/cheat-sheet/
https://help.obsidian.md/syntax
https://daringfireball.net/projects/markdown/syntax
Current Priority:
- SpaceX Starship
- Submarine
3 months agoI just noticed that this reads more like an advertisement than an announcement, that wasn't what I intended it to be. Sorry!
3 months ago@lafario I got a notification telling me that you mentioned me in a post called "Picture gallery", but I can't find that. Anything you still want to tell me?
3 months agoIs the last image intentionally a 404 error?
3 months ago