@Korzalerke Wait the account was deleted yet the following page works...
Using your sorcery, can you figure out how to unfollow banned/deleted accounts?
@Korzalerke On one of the account's posts was a comment tagging Andrew Garrison. I deleted it. And then I (as the account) got into a war with you (also as the account). It was quite funny.
@Korzalerke I don't remember... I edited the bio to something, upvoted some of my posts (just a few), and literally tagged myself on the password post. Then my actual account showed up, warned about the possibility of deleting the account, and then I may have deleted it (the account) soon after. I also removed the tag for andrew garrison on one of the posts, and got into a war with you on the same post.
@SnoWFLakE0s Cool, thanks. Yeah this could do with some improvements. I just made this in 10 minutes to graph something for school but saw the potential.
@ZharkovAndrey I wasn't aware of this issue. I will have a look now. Thank you for the feedback, and for letting me know.
Edit: The update appears to have broken ALL of the gauges. This means my other planes are affected as well.
Edit 2: I had a unaffected archival copy and used the codes off that. There are many codes which were affected, I am making an XML update soon. About your copies, there is no other option but to use the new version once that is out.
@Almost Right, I'll try to explain this in a comment.
Assuming you mean the engine goes to "idle" and then the player can throttle up, this is relatively easy, using variables.
Create three variables, called "Engine1On", "Engine1Throttle", and "Engine1Input".
In Engine1On, put the following code: clamp01(Activate1)
In Engine1Throttle, put the following code: clamp01(smooth(Engine1On, 0.5) > 0.9) * Throttle
In Engine1Input, put the following code: 0.25 * smooth(Engine1On, 0.5) + smooth(Throttle, 1)
This is a little different to my engine, which has a custom fan blade and more inputs, however this should work for your purposes. The key bit you wanted to know is how to get the throttle to "wait" for the engine to spool up. This is done using the comparison in Engine1Throttle. Note I recommend setting the attribute "throttleResponse" to something like 3. This attribute goes in the Engine category in OverLoad.
For the second engine, create the same variables, but replace Engine1 with Engine2. Also change Activate1 to Activate2.
If you have any questions let me know.
In response to your comment about the engine video being hard to understand, I would say I agree. A lot of my videos about code turn into 30 minute lectures on functions and code. What part is hard to understand? My voice, or the content?
@DerAtomherbst Rip.
It's kinda easy to build custom gear, just needs practice.
One thing to note is unless you are throwing blocks together, at least one part needs nudging.
I might make a tutorial on how to make custom landing gear.
@Soardivision160th The simple code we want is smooth(Throttle, x)
replace x with a number. Higher values are faster speeds and lower values area lower speeds.
How is the engine powered? A normal throttle input? It is perfectly doable, I just need the input of the engine to get coding (it'll take like 1 minute).
@BaconAircraft Yeah, I was trying to fix the jerky motion from the original and thought this would help. It sort fixes things, however by fixing some things with the target using smoothing it also helped. I recently learned about sine waves in school and am going to put that to use for even smoother transitions.
@AVERAGEAVIATIONENJOYER I have found the issue. In the two buttons, you set the input to be inA or deA, not in or de. Remove the "A" from them and it works fine.
Labels don't support a hybrid of displaying a string and a funky code. What I mean is the boolean selector you've got there is using one string (when it's off), and a funky trees expression when it's on. I would say have the label on a piston which extends when the system is turned on. Have the label itself always display the target's distance.
@Korzalerke Wait the account was deleted yet the following page works...
Using your sorcery, can you figure out how to unfollow banned/deleted accounts?
@Korzalerke On one of the account's posts was a comment tagging Andrew Garrison. I deleted it. And then I (as the account) got into a war with you (also as the account). It was quite funny.
@Korzalerke The war about who removed the andrew comment.
@Korzalerke I don't remember... I edited the bio to something, upvoted some of my posts (just a few), and literally tagged myself on the password post. Then my actual account showed up, warned about the possibility of deleting the account, and then I may have deleted it (the account) soon after. I also removed the tag for andrew garrison on one of the posts, and got into a war with you on the same post.
@Korzalerke I did have some fun (maniacal laughter) with the account first...
@Korzalerke I'm not saying I did, but I might have deleted the account to teach people a lesson about security.
@SnoWFLakE0s Cool, thanks. Yeah this could do with some improvements. I just made this in 10 minutes to graph something for school but saw the potential.
@SteamPunkPilot I live in [classified]. UTC + 10
@SteamPunkPilot Timezones... good morning. My videos premier at 8:00 AM AEST.
This video should help with what you want. Skip to about 5:15 to get to the startup sequence.
@ZharkovAndrey Issue has been fixed. You will need to update your copies.
@ZharkovAndrey I wasn't aware of this issue. I will have a look now. Thank you for the feedback, and for letting me know.
Edit: The update appears to have broken ALL of the gauges. This means my other planes are affected as well.
Edit 2: I had a unaffected archival copy and used the codes off that. There are many codes which were affected, I am making an XML update soon. About your copies, there is no other option but to use the new version once that is out.
@FRIGGLES Not sure what you mean, the latest teaser is here.
@Almost It shouldn't break them. Send me a link to the problem post and I'll have a look.
@Almost Variable setters button. It's not overload. It's the new (X) button next to it.
There was never a navigation system.
@Almost Right, I'll try to explain this in a comment.
Assuming you mean the engine goes to "idle" and then the player can throttle up, this is relatively easy, using variables.
Create three variables, called "Engine1On", "Engine1Throttle", and "Engine1Input".
In Engine1On, put the following code:
clamp01(Activate1)
In Engine1Throttle, put the following code:
clamp01(smooth(Engine1On, 0.5) > 0.9) * Throttle
In Engine1Input, put the following code:
0.25 * smooth(Engine1On, 0.5) + smooth(Throttle, 1)
This is a little different to my engine, which has a custom fan blade and more inputs, however this should work for your purposes. The key bit you wanted to know is how to get the throttle to "wait" for the engine to spool up. This is done using the comparison in Engine1Throttle. Note I recommend setting the attribute "throttleResponse" to something like 3. This attribute goes in the Engine category in OverLoad.
For the second engine, create the same variables, but replace Engine1 with Engine2. Also change Activate1 to Activate2.
If you have any questions let me know.
In response to your comment about the engine video being hard to understand, I would say I agree. A lot of my videos about code turn into 30 minute lectures on functions and code. What part is hard to understand? My voice, or the content?
@MTindustries 4000, but several versions with different levels of detail will be made.
If the B17 crashes, (which has happened a few times), my computer genuinely explodes. And it has one of the most powerful CPUs in the world.
T
@Korzalerke I forget the post, but they said it was extended.
Forum Post On Updates
Sure
Ah crap I decided to open the settings of the label.
This is actually insane dude.
@JA8119 Yes, you can't change it. Maybe for your next plane you could do it.
69 Upvotes
Please be an early April fools joke.
Wait this is a thing now.
Do not click those buttons unless you want the universe to implode.
@DerAtomherbst Rip.
It's kinda easy to build custom gear, just needs practice.
One thing to note is unless you are throwing blocks together, at least one part needs nudging.
I might make a tutorial on how to make custom landing gear.
@DerAtomherbst So I heard you needed a pdf
@Zaineman It was very detailed.
I had a look, and everything seems symmetrical. I'm not sure why it rolls. Sorry.
@Soardivision160th Why don't you post it and I'll have a look.
I use this to separate lines.
.
It is a good suggestion tho.
@Chickenlittle Sure, go ahead
@Soardivision160th The simple code we want is smooth(Throttle, x)
replace x with a number. Higher values are faster speeds and lower values area lower speeds.
How is the engine powered? A normal throttle input? It is perfectly doable, I just need the input of the engine to get coding (it'll take like 1 minute).
@Spillo Ok
@Spillo Thanks
.
Random question - do you have Discord?
The ILS and navigation system is AMAZING!!!
.
I'd really like to use this in my upcoming SWL-120
Test comment based on the forum post.
69 upvotes... rip
This
@BaconAircraft Yeah, I was trying to fix the jerky motion from the original and thought this would help. It sort fixes things, however by fixing some things with the target using smoothing it also helped. I recently learned about sine waves in school and am going to put that to use for even smoother transitions.
@AVERAGEAVIATIONENJOYER I have found the issue. In the two buttons, you set the input to be inA or deA, not in or de. Remove the "A" from them and it works fine.
@AVERAGEAVIATIONENJOYER I'll have a look.
First
Labels don't support a hybrid of displaying a string and a funky code. What I mean is the boolean selector you've got there is using one string (when it's off), and a funky trees expression when it's on. I would say have the label on a piston which extends when the system is turned on. Have the label itself always display the target's distance.