@Sm10684
.
PC builds by nature are more beefy and detailed. Mobile builds are generally far, far less detailed than are PC builds. My older builds did plenty well w/o ingame screenshots...
@RedVine
.
I think there's a limit to how far FT can go. Remember, SP wasn't built with ingame scripting support in mind. These other examples were... an IDE seems difficult to implement as well. For full on programming capability, I'm getting hopes up for SP2... You probably know how hard it is to modify and add than it is to write anew.
@WalrusAircraft
.
Again, I played with Python for a grand total of about 5 hours till this point... I don't think I'll be able to do any CAD-file to SP conversion scripts in the near future, but I'll think of it as a potential project to work towards.
Thanks for the compliments.
@WalrusAircraft
.
A bit of extra drag and angled detachers. I opted not to add extra for the sake of people making things with this system. The more crucial part is the angle of the detacher. Play around with how the detacher is oriented until you get some desired result... On the original I just made some randomized changes to the detacher angles to make tumbling occur.
@SemedianIndustries
.
Seems good to me! I'll be looking at the whole flight system holistically. Though, is it possible that you provide a generalized formula?
@spefyjerbf
.
Yep, I wanted try doing option #2, but that made the XML file sort of inaccessible... Although either way unless you've downloaded the script you have to copy and paste.
For the XML file output, I redirected the console output stream to an external file write:
.
producefile = input("Output file to command line? (Type 1 for Yes, 0 otherwise) \n")
if producefile == 1:
print("Check the side bar for the Subassembly XML file.")
import sys
sys.stdout = open("CannonSubAssembly.xml", "w")
@mohsen
.
This guide is outdated. Check snowflake0s.github.io for a better guide. Although basic algebra is highly recommended, the guide it meant to teach you from the ground up.
@Type2volkswagen
.
50% is not a number. Use 0.5 instead. Also capitalization for Fuel. Also for logic operators, either side should be a boolean value. So instesd of the max function, use Fuel < 0 as the qualifier for fuel being more than 0.
@spefyjerbf
.
Yep, just within the next month (before May 1st). I have no limit to the amount of system you can include, I'll try to judge them somewhat separately. If the whole system is designed to work in tandem, I'd say that counts as a single system with multiple components.
@ChisP
.
Depends on how you view it though. I'm not looking for something complicated. Merely some sort of general system that is generalizable, functional, and creative.
@Tang0five
.
Oh heck yes! It's as simple as using Overload and writing something in there- every platform has Overload. (A bit more than that, but oh well) If you're not well oriented with the system, I suggest you check out my online guide.
@Type2volkswagen
.
I see the problem. Not a bug. clamp(Yaw, -1,0)
See this? If you are in a left turn, your Yaw value is -1. -1 means false or off, so it's expected that your light isn't on. Instead, try putting an abs() around the expression to let the left turn expression return 1 when Yaw = -1.
"Mobile friendly"
+1Laughs
Cool, good job!
@DarDragon
.
The hull needs a bit of work. The turret is great though.
@Sm10684
+1.
PC builds by nature are more beefy and detailed. Mobile builds are generally far, far less detailed than are PC builds. My older builds did plenty well w/o ingame screenshots...
@rainskaos
+5.
Use the script I provided in the comment below.
@RedVine
.
I think there's a limit to how far FT can go. Remember, SP wasn't built with ingame scripting support in mind. These other examples were... an IDE seems difficult to implement as well. For full on programming capability, I'm getting hopes up for SP2... You probably know how hard it is to modify and add than it is to write anew.
@WalrusAircraft
.
Again, I played with Python for a grand total of about 5 hours till this point... I don't think I'll be able to do any CAD-file to SP conversion scripts in the near future, but I'll think of it as a potential project to work towards.
Thanks for the compliments.
@iwannabeelected
.
I believe there are sensitivity controls... However I don't use mobile so I may be wrong.
@WalrusAircraft
.
A bit of extra drag and angled detachers. I opted not to add extra for the sake of people making things with this system. The more crucial part is the angle of the detacher. Play around with how the detacher is oriented until you get some desired result... On the original I just made some randomized changes to the detacher angles to make tumbling occur.
XML edit the reference link.
@nadvgia
+1.
Good work! Counted into list of entries.
@SemedianIndustries
.
Seems good to me! I'll be looking at the whole flight system holistically. Though, is it possible that you provide a generalized formula?
@DarDragon
+1.
Executable code. Who knows, I could've put in a virus in there if I had malicious intent.
@spefyjerbf
.
Yep, I wanted try doing option #2, but that made the XML file sort of inaccessible... Although either way unless you've downloaded the script you have to copy and paste.
For the XML file output, I redirected the console output stream to an external file write:
.
producefile = input("Output file to command line? (Type 1 for Yes, 0 otherwise) \n")
if producefile == 1:
print("Check the side bar for the Subassembly XML file.")
import sys
sys.stdout = open("CannonSubAssembly.xml", "w")
.
Like so.
I guess it's open source? Feel free to modify as you see fit.
@TheMachinist
.
Of course. Also, use this for automatical generation of this system to whatever style you want.
@MontyPython
.
Just tag me in the comments of the unlisted build. That's how we do this around here.
@mohsen
.
This guide is outdated. Check snowflake0s.github.io for a better guide. Although basic algebra is highly recommended, the guide it meant to teach you from the ground up.
@rainskaos
.
That adds 2000 parts to whatever you're making. You sure?
@MontyPython
.
When you post, select Unlisted instead of Public.
@MontyPython
.
Try posting unlisted, tag me and I'll try to fix.
@cedblox332
.
It's pretty much SimplePlanes' very own language. A bit different from conventional languages, however.
It works. Set first gun to correct delay, the rest all to 0 or 0.001.
Cool! Entered into list of entries.
@SemedianIndustries
.
Weird, seems fine to me. Send me a unlisted post or something so I can investigate.
@Sm10684
.
clamp01(-(Pitch = 0))@Type2volkswagen
.
Also, forgot to mention... Parentheses. Write your input like (a) & (b).
@Type2volkswagen
+1.
50% is not a number. Use 0.5 instead. Also capitalization for Fuel. Also for logic operators, either side should be a boolean value. So instesd of the max function, use Fuel < 0 as the qualifier for fuel being more than 0.
@SemedianIndustries
.
Do you know what sine and cosine is?
They are sinusoidal functions, dude. That's what they're supposed to be doing.
@JaeBeansS
+1.
https://snowflake0s.github.io/funkyguide.html
@USSR @LastManStanding
.
Overload is inbuilt with 1.9+.
@marcox43
.
You can try using the old "hollow fuselage" method to build your wheels... You'll get a better hitbox that way.
@zap210
.
I've noticed. Seems like a very smart mechanism, if I find that I need gears again (probably will...) I'll use that method. Thanks.
@icantake
+2.
Basic
But that doesn't teach you about how to do the things involved in this build. Check this site for info on Funky Trees.
Reminds me a lot of the mechanical fire control systems that had gear-based integration and derivation. Good work.
@asteroidbook345
.
Precisely.
@spefyjerbf
+1.
Yep, just within the next month (before May 1st). I have no limit to the amount of system you can include, I'll try to judge them somewhat separately. If the whole system is designed to work in tandem, I'd say that counts as a single system with multiple components.
@CookieCrumz
+2.
role=AirToGround@ChisP
.
Depends on how you view it though. I'm not looking for something complicated. Merely some sort of general system that is generalizable, functional, and creative.
@Hedero
.
Thanks! Not really getting used to the black point color.
@EliteArsenals24
+1.
Thanks! Anybody can do what I do with some time, lol.
@nadvgia
.
Awesome, I'll be awaiting your entry!
@WarHawk95
+1.
Oops, thank you! Fixed.
While you're at it, check my challenge out!
@Tang0five
+4.
Oh heck yes! It's as simple as using Overload and writing something in there- every platform has Overload. (A bit more than that, but oh well) If you're not well oriented with the system, I suggest you check out my online guide.
Included in the build is an experimental 360º turret. Pitch & Roll for controls.
Heading is from -180 to 180 deg- probably why.
@LotusEngineering
.
A ton of these are already possible, I see no incentive for devs to add those... but some things are valid ideas.
@Type2volkswagen
.
I see the problem. Not a bug.
clamp(Yaw, -1,0)See this? If you are in a left turn, your
Yawvalue is-1.-1meansfalseor off, so it's expected that your light isn't on. Instead, try putting anabs()around the expression to let the left turn expression return1whenYaw=-1.@SemedianIndustries
.
The parts have nothing to do with the input. You can recycle the same input for use in other things, though.