Generally you use smooth() to create a linear progression then add some sort of comparative operator to check when that progression reaches a certain threshold so you get the right sync times.
@Formula350
.
GearDown is a lot more intuitive.
Quite simply, if the gear is down, GearDown = true, and if the gear is up, GearDown = false.
.
The same applies for Activation Groups.
To take an example with AG1, if the AG1 is on, Activate1 = true, and if AG1 is off, Activate1 = false.
.
Basic Funky Trees documentation and guides are available at the FT guide page.
@AN2Felllla
.
Check your brackets. FT tries to auto-complete if possible, sounds like that might be the case. Are you using implicit multiplication as well?
@AN2Felllla
.
Please, I challenge you, point out where I have been needlessly verbose. If you can simplify my words without changing the meaning or making it too long, I'll gladly accept the proposition that I'm doing this verbose thing intentionally.
.
I forgot to mention, please drop the openly mocking attitude. It helps no-one.
@CaptFoxworth19
.
It's simply a stepped function. Each piston has a dependency on the threshold of the Throttle value, for example the first piston would have Throttle > 0.25 as the qualifier, the next Throttle > 0.5, etc.
@Lanc
.
We've gone over this once before--I assume this is a joke, but still, for those who take this a bit too far: just because one can make maps does not make you a developer... The two are very different things.
.
One can do programming magic... the other does not necessarily.
@Numbers
.
The current guide is definitely not the most easy thing to understand, but it still functions as extensive documentation that most can get by. Don't worry though, the project I'm pushing ahead right now is precisely an easier, more interactive course for FT.
@shipster
.
Seems like a known issue. I've had one other report from a iOS user that the sights do not seem to function. Thank you for the notification.
@X4JB
.
Thanks for the kind words. Here's my excuses for the annoyances:
The color palette issue: I would have liked to color the details slightly differently, but I ran out of color spaces and the extra color management was too much to bother with especially since there were too many involved. Also had some issues getting the whole thing to work in the first place. My colors are out of order for some reason.
.
The thumbnail: it was taken with ReShade on by Numbers, and there were certain issues with RTGI that I disliked a lot and I told him to turn it off for the thumbnail.
.
Shadows: is there an alternative? I do like having shadows vs. no shadows.
.
Regardless thank you for the feedback. Will keep this stuff in mind for the next time I decide to commit 8 months to a project! If it's any excuse, this is my first build. No joke.
Stating the obvious is not a "theory"- that's the opposite of a theory
"I've calculated it is impossible"- how do you even calculate this? Care to give a formula?
"It is the same reason an AI cannot create a perfect circle"- ROFL. The definition of a circle is given by x^2 + y^2 = r^2, you're saying an equation can't be calculated, what?
Your idea about "impeccable detail" is simply invalid because by your logic no production aircraft is perfect in the first place because they all have minute differences. You do realize that, no?
SP replicas are supposed to be a visual/performance replica. If it looks similar enough it's good enough. If it acts similar enough it's good enough, because in the given context it's the best thing we have.
Stop packaging your statements in such a verbose fashion. It helps no-one.
Absolutely game changing. I can't stress enough.
+1Probably the most game-changing update.
+1Probably the first application of FT.
+1@PlaneFlightX
+1.
I can't make any promises, but at least not long after 1.11 is out of beta. A lil' busy with schoolwork.
zum zum
+1@Sosig1
+1.
Feel free.
CoolPeach has it right, the devs have said already that they are planning to add more variable write out.
+1Documentation
+1Epic!
+1@BaconAircraft
+1.
smh im boutta orthographically project your butt
<3
Use sum for non returning values.
+1たしかに徹夜テンーションだなこりゃ
+1@Kangy
+1.
Scripts exist, they take 2 seconds for the job
@TheIronGamer300
+1.
Ping a mod to add the successor link for you, thanks for entering!
Here's something for doors that open then also close:
https://www.desmos.com/calculator/j3wlgr4mui
Generally you use smooth() to create a linear progression then add some sort of comparative operator to check when that progression reaches a certain threshold so you get the right sync times.
You could also change up this code format to work with GearDown.
+1@MaverickHendricks
+1.
Feel free.
@Formula350
+1.
GearDown is a lot more intuitive.
Quite simply, if the gear is down, GearDown = true, and if the gear is up, GearDown = false.
.
The same applies for Activation Groups.
To take an example with AG1, if the AG1 is on, Activate1 = true, and if AG1 is off, Activate1 = false.
.
Basic Funky Trees documentation and guides are available at the FT guide page.
@GuyFolk
.
Yeah! I first saw it on the Doom game that came up some months ago. It's useful but seems kinda gimmicky for moving components.
Still, this seems very well done.
+1Whoa! Interested in how you would've done the bouncing algorithm. Got a headache and gave up the last time I tried.
+1I object.
+1kthnxbye
+1@Dathcha
+1.
Maybe! I'll see what I can do to make a barebones computer.
@Sadboye12
+1.
Yeahhhhh!!
@AN2Felllla
+1.
Check your brackets. FT tries to auto-complete if possible, sounds like that might be the case. Are you using implicit multiplication as well?
@RC1138Boss
+1.
Quite literally a graphing calculator.
@Vincent_
+1.
Oh no! What am I gonna do now???
Kino's Journey!
+1@AN2Felllla
+1.
Please, I challenge you, point out where I have been needlessly verbose. If you can simplify my words without changing the meaning or making it too long, I'll gladly accept the proposition that I'm doing this verbose thing intentionally.
.
I forgot to mention, please drop the openly mocking attitude. It helps no-one.
@ArkRoyalTheDDhunter
+1.
Nope, completely unrelated. It's made using rockets. It's a further development of this system here.
Might be possible to have the AI cockpit track the player.
+1elongated circle
+1@CaptFoxworth19
+1.
It's simply a stepped function. Each piston has a dependency on the threshold of the Throttle value, for example the first piston would have Throttle > 0.25 as the qualifier, the next Throttle > 0.5, etc.
@edensk
.
Possible**.
**Requires stupid amounts of math. Math not included.
+1@Lanc
+1.
We've gone over this once before--I assume this is a joke, but still, for those who take this a bit too far: just because one can make maps does not make you a developer... The two are very different things.
.
One can do programming magic... the other does not necessarily.
Very scenic.
+1@PvtJok3r
+1.
Join link is uh, in the post.
@Numbers
+1.
The current guide is definitely not the most easy thing to understand, but it still functions as extensive documentation that most can get by. Don't worry though, the project I'm pushing ahead right now is precisely an easier, more interactive course for FT.
@spefyjerbf
+1.
Ha! Happens to me from time to time as well. No idea.
@KingOog000
+1.
;) Meant to be
@shipster
+1.
Seems like a known issue. I've had one other report from a iOS user that the sights do not seem to function. Thank you for the notification.
@X4JB
.
Thanks for the kind words. Here's my excuses for the annoyances:
The color palette issue: I would have liked to color the details slightly differently, but I ran out of color spaces and the extra color management was too much to bother with especially since there were too many involved. Also had some issues getting the whole thing to work in the first place. My colors are out of order for some reason.
+1.
The thumbnail: it was taken with ReShade on by Numbers, and there were certain issues with RTGI that I disliked a lot and I told him to turn it off for the thumbnail.
.
Shadows: is there an alternative? I do like having shadows vs. no shadows.
.
Regardless thank you for the feedback. Will keep this stuff in mind for the next time I decide to commit 8 months to a project! If it's any excuse, this is my first build. No joke.
@Nirvash
+1.
why must you do this
@RYAviation
+1.
And selected the weapon? Sounds like it might be some isolated issue on your end- never seen that one happen to anyone else.
Well edited!
+1@Sovetskysoyus
+1.
Drag is disabled on all parts except one or two parts. Thanks for the kind words!
@HappyFeetWhyshouldi @Jefftheneef @Bernkastel
+1.
Thanks for the kind words!
@DarthAbhinav
+1.
A bit too long! I might make a little something about exactly that sometime. A reflection of sorts, perhaps?
Stop packaging your statements in such a verbose fashion. It helps no-one.
+1@typeZERO
+1.
誤解してます、Adithecat3459ーさんは島風がアメリカの船だと言いませんでした
Fair point. I'll concede on that. Although, I've to admit that it genuinely is intrusive when I'm exposed to something multiple times a day.
+1