If you're actually knowledgable about Asia you'd know how terrible Japan is. Aside from the fact that most of Asia would rejoice if Japan stopped doing generically terrible Japan things, that makes no sense anyway.
If you're going on about anime itself, China owns most of the industry already anyway.
Smooth is a much better method for storing data--there's a good reason most of us are using it for a memory function. It is very flexible in terms of storing data, as it can change values instantly to a very specific desired value or reset to a default value instantly as well.
@WolfSpark
.
Impossible with the design of SP systems--also file uploading by users en masse is generally a bad idea.
.
A tone generator is possible and a mod implementation already exists, so that sounds more likely.
@Aweyer26 @DDVC
.
Sorry for that! I changed the directory and some overhauls are being made to the site overall. I added a redirect for those who aren't up to speed yet.
@JuanShot2Go
.
An automatic notice should appear now to all that access the old link, I made it automatically redirect. Thanks for your interest! Actually, accessing the page gives me extra pennies so :) indulge yourself.
@Aweyer26
.
I've recently made some updates to the site and as a result the link has changed slightly. It's at https://snowflake0s.github.io/funkyguide instead of https://snowflake0s.github.io/funkyguide.html. Sorry for the inconvinience.
This also is the driving principle behind the workings of the stopwatch. What's more, you can even store longer numbers to specifically code for certain events and create processors.
Definitely why the smooth function remains one of the most important functions we have. As for the rate though, I personally recommend using a really large number, like pow(10,5) in order to ensure that the function properly "snaps" to any value.
Increased flexibility in FT #2:
Possibly accessing FT data for specific parts, instead of only the cockpit--perhaps in the form of calling existing variables with the part id, like GForce.id(204) to get data for that part.
Increased flexibility in FT #1:
Variables of some form to condense blocks of code
.
Implementation of this is unclear to me as well, but I would imagine it being some part of the aircraft file's header in the backend, and in the frontend probably some entry field, similar to Overload, where we enter a name for the variable and its contents.
.
This would allow for this custom variable to be referenced multiple times in inputs of the aircraft, greatly simplifying and modularizing FT code.
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.
@PioThePioneer
.
Well, the goal is to provide a kit that you snap together in the designer and can admire while loaded in the sandbox. If nudging is part of the assembly process, just make it apparent in the manual. Manually adding connections for assembly is fine as long as the instructions make it clear.
@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.
Coolio
Ficc
@BaconAircraft
+1.
smh im boutta orthographically project your butt
<3
A piece of advice... Learn to use perspective lines
+3If you're actually knowledgable about Asia you'd know how terrible Japan is. Aside from the fact that most of Asia would rejoice if Japan stopped doing generically terrible Japan things, that makes no sense anyway.
If you're going on about anime itself, China owns most of the industry already anyway.
Use sum for non returning values.
+1Unsure if this uses the same change counter concept I use, but sum(abs(rate(Bool))) can count the number of changes of a Boolean.
Magic
+4Smooth is a much better method for storing data--there's a good reason most of us are using it for a memory function. It is very flexible in terms of storing data, as it can change values instantly to a very specific desired value or reset to a default value instantly as well.
You can't fix this without a new codebase. Maybe in SP2 if ever.
+9@WolfSpark
+3.
Impossible with the design of SP systems--also file uploading by users en masse is generally a bad idea.
.
A tone generator is possible and a mod implementation already exists, so that sounds more likely.
@Aweyer26 @DDVC
+2.
Sorry for that! I changed the directory and some overhauls are being made to the site overall. I added a redirect for those who aren't up to speed yet.
Also off to college to study engineering--only thing is I'm more than likely to continue playing. Well, good luck!
+2Kekkus
Neato! Almost a bit like playing snake.
@JuanShot2Go
.
An automatic notice should appear now to all that access the old link, I made it automatically redirect. Thanks for your interest! Actually, accessing the page gives me extra pennies so :) indulge yourself.
@HNL47
.
You won't get updates though :(
@Aweyer26
+3.
I've recently made some updates to the site and as a result the link has changed slightly. It's at https://snowflake0s.github.io/funkyguide instead of https://snowflake0s.github.io/funkyguide.html. Sorry for the inconvinience.
This also is the driving principle behind the workings of the stopwatch. What's more, you can even store longer numbers to specifically code for certain events and create processors.
+2Definitely why the smooth function remains one of the most important functions we have. As for the rate though, I personally recommend using a really large number, like pow(10,5) in order to ensure that the function properly "snaps" to any value.
+3The FT site had a directory change, it's more like an actual website now.
.
https://snowflake0s.github.io/funkyguide
@Hascup
.
Point is, it exists, and the carrot operator likely won't be added. I'm not a fan either, but it's what we have.
たしかに徹夜テンーションだなこりゃ
+1@Hascup
+2.
x^a = pow(x, a)
.
How many of you have actually read my FT guide >:(
You did mention it yourself, but revamping fuselage hitboxes would be huge... Especially for cool mechanical things.
+11@Kangy
+1.
Scripts exist, they take 2 seconds for the job
@Darren101
+3.
You can just, you know, make custom weapons... It has been done for ages.
Increased flexibility in FT #2:
+36Possibly accessing FT data for specific parts, instead of only the cockpit--perhaps in the form of calling existing variables with the part id, like
GForce.id(204)to get data for that part.Increased flexibility in FT #1:
+27Variables of some form to condense blocks of code
.
Implementation of this is unclear to me as well, but I would imagine it being some part of the aircraft file's header in the backend, and in the frontend probably some entry field, similar to Overload, where we enter a name for the variable and its contents.
.
This would allow for this custom variable to be referenced multiple times in inputs of the aircraft, greatly simplifying and modularizing FT code.
@SemedianIndustries
.
Check for bracket errors, etc etc... Plenty of room for human error.
Hi, I am told that apparently I am a racist rapist
@SemedianIndustries
.
Not really.
WHEEEEEEEEEEEEE
No. Activation groups are their own variable. You can just set Pitch as the activation condition for something though...
So it does work fairly well, seams exist but I'm pretty satisfied. Check out my profile!
@TheIronGamer300
+1.
Ping a mod to add the successor link for you, thanks for entering!
@gmmmsoares
+2.
Oh yeah! I forgot to add a deadline, I'd say two weeks is a good enough margin for decent submissions.
@Kangy
+2.
Not necessarily time, but instead the smooth section's output. Sort of.
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@JuanAlt
.
Go ahead, don't mind. Try to consolidate your comments if possible though!
@JuanAlt
.
Any piece of furniture is acceptable. Just make sure it is either a replica or believably Ikea-styled.
@JuanAlt
.
Yes, make sure to also provide some form of assembly instructions. The more realistic the better score you will receive.
@PioThePioneer
.
Well, the goal is to provide a kit that you snap together in the designer and can admire while loaded in the sandbox. If nudging is part of the assembly process, just make it apparent in the manual. Manually adding connections for assembly is fine as long as the instructions make it clear.
@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.
Cring
But video
The trap is Vince hasn't uploaded in some
+6Fever dream
You've just been blocked. Don't follow dumb trends in the future.
+4Good luck in your future endeavors.