I keep fat fingering the cursor in SR2 mobile, I try to move a part and get left with a mess of duplicated fuselages (ik they're called fuel tanks in SR2 but let's be honest here, they're fuselages)
I have the second plane I ever built on the site, but my first one used VTOL engines before I knew how they worked, so it didn't fly for obvious reasons
Here's an FT fix: Roll=0?smooth(RollRate, 0.5):Roll
.
I forcefully induced auto Roll into one of my planes and managed to get it to stop by replacing the wings that use Roll with this code, multiply RollRate by a number to increase and decrease the strength of the correction, and replace 0.5 with a different number to increase or decrease the speed of the correction. The input for wings is in ControlSurface under InputId. Just paste the code there and it should be fine.
.
Please note that this is a band aid, this can cause weird flight characteristics on something that is very agile
Well people much worse than you have a higher point count anyways (such as me, my build quality sucks), so I don't see the point in you not deserving it.
.
Welcome to the dark side, your okthxbye permit will mailed to you shortly.
@AnimeGirlLover2010 it is too late. The edit history of your bio is saved. So are edits to forum posts, airplane Posts, and comments. Besides, your username has your birth year in it.
despite that circle not being anywhere in the designer
Remove the hubcaps from my GP1 then load it in on low physics. You will see the true meaning of pain. If it doesn't happen, full throttle then enable slow mo
Here's my take on it.
.
Since you want the engines to stall for a certian amount of time after a certian condition is met, we gotta use variables.
Var: Timer = clamp(Condition | Timer < 60 & Timer > 0 ? Timer-0.07 : Timer + 60 , 0 , 60)
.
Var: Condition = smooth(AngleOfAttack, Y) = X
.
Then add this to the end of your engine inputs (replace X with your current engine throttle code and Y by how fast you want the engines to react):
.
X - smooth(Timer < 60 ? 1 : 0, Y)
.
.
.
The timer is roughly 15 seconds long, change 0.07 to any number to suit your needs, the higher the number, the faster It will count and vice versa, with the number being subtracted from the timer Timer each frame.
.
Since I don't know what conditions you want for this, just replace Condition with whatever conditions are needed for the stall as long as it's a True/False statement. The Timer will activate as soon as the statement returns true, even if it is only for a single frame
. Here is an example build that uses the code
Heres an idea: make the whole thing non buoyant and use FT jet engines to set how high the whole thing sits in the water. Here is a formula I cooked up, it's untested but its similar to what I've used in an unreleased hovercraft I built.
. ActivateV ? (AltitudeAgl < W ? 1 : 0) : (AltitudeAgl < (X-Y*Z) ? 1 : 0)
.
Replace V with desired activation group to toggle between normal and flood mode
.
Replace W with the Altitude that the cockpit is at when the boat is floating normally
.
Replace X with the default altitude that the cockpit is at when the boat is floating normally when in flood mode
.
Replace Y with a slider input (VTOL/Trim)
.
Replace Z with a multiplyer, Since inputs are between -1 and 1, you need go multiply it to subtract from the base Altitude. I would start with 10 and go up or down from there
I recommend using the really small jet engines with a high engine multiplyer and a low max input (such as a multiplyer of 30 and a max input of 0.15)
.
This is for the whole boat flooding, if you want to only use one side, only apply this to one side of the ship and replace AltitudeAgl with PitchAngle and the default and desired altitudes with angles instead. (And make one end of the boat buoyant)
.
This will allow for extreme customization, as you can have everything be changeable in the variable menu, allowing for quick changes in the code without having to edit 40 jet engines for one slight change
.
Pros: immediate level change with easily adjustable angle, depth, and speed with little to no wobble
.
Cons: FT is complex and can get laggy, more jet engines are needed to keep the ship level, as if the boat tilts, it turns
Wing alireons will have a hard time tliting the faster you are
Here's an FT solution: Clamp(X/(TAS+1.5/Y), -1, 1)
Replace X with your desired input and replace Y with a number. The bigger the number you replace Y with, the smaller amount of resistance you will feel at high speeds. Ideally you should start with 1500-2500
1: raw
2: 6 years
3: it's a 27 way tie, I wont list them here
4: standard white bread, it works best for sandwiches
5: mobile
6: people are getting platinum a LOT faster than they used to, other than that, it's alright, though something seems missing from the old days
Attaching a label directly to the detaching end of a detacher renders said detacher inoperable until the label is removed.
.
Not sure why this happens but it's been infuriating me for the past hour as I'm making cockpit directions that dissappear once they are followed
Not things I hate doing but things I dislike in general:
.
1: having to rebuild something because i didn't make a backup
.
2: telling people that if they add the VR tag to their builds, they don't have to ping a curator (only ping me if the build in question is unlisted, otherwise, I can see it in my headset using the VR tag)
.
3: the undo button
.
4: connections on detachers, pistons, and suspension springs being incredibly wobbly even on high physics
.
5: the overabundance of replicas on the website (this game is about building the planes of your wildest dreams and you decided to build something that already exists. remember the days of hypno planes? Those were cool)
.
6: people who post memes in the airplane section
.
7: rewriting the same FT code 5 times because the last 4 iterations dont work or lag too much
.
8: Tuning PID loops
.
9: narcissists (there's not many, but I try my best to stay away when one crops up)
@xNotDumb I'll take a look either tonight or tomorrow night, I'm on vacation rn so maybe another curator will look at it. It has the VR tag so someone should get to it soon
@Bellcat I asked Pedro how many people applied, a lot of people did, it will probably be another day or two until someone is chosen, and a day or two after that for it to be official
May he rest in peace, for technoblade has never lost a fight, even against cancer. Since the cancer died when he did, the battle was technically a draw. Technoblade never dies!
@rexzion no, it's signed by me, as I'm the one responsible for printing them and giving them to people
I didn't notice you were platinum lol, congrats. Your Okthxbye permit should arrive in the mail soon
[Removed]
+2It wasn't SP, Tinkercad had a stroke when importing the model
I keep fat fingering the cursor in SR2 mobile, I try to move a part and get left with a mess of duplicated fuselages (ik they're called fuel tanks in SR2 but let's be honest here, they're fuselages)
+3Vote concluded: paint job 4 wins
(Though I like 3 better so I might release this as a combo pack)
Mobile has it turned off by default, I forget it exists until I play SPVR, which has it turned it on by default
+3I have the second plane I ever built on the site, but my first one used VTOL engines before I knew how they worked, so it didn't fly for obvious reasons
+1@MachesterF1 adding the vr tag makes sure that curators will look at it eventually. There's currently a huge backlog of builds at the moment
+3Scale them to zero.
+1Ok we get it, you use your crypto rig for gaming
+4You now hold the record for most upvotes on a single build in a day
+9You can enable mobile joysticks on the PC version in the settings
+1Got it while it was free, then got addicted
+2Because I can
+4Saw the flash of green right after the 30k mark, pretty sure that's me
+1The connections are just bad, pistons and detachers suffer from this too. There's nothing I know you can do to fix it
+2Not sure if it's the final teaser yet, I still have some stuff I need to tune on it
8: you forget to add the VR tag and get mad when the curators don't look at it
+8Here's an FT fix:
+1Roll=0?smooth(RollRate, 0.5):Roll
.
I forcefully induced auto Roll into one of my planes and managed to get it to stop by replacing the wings that use Roll with this code, multiply RollRate by a number to increase and decrease the strength of the correction, and replace 0.5 with a different number to increase or decrease the speed of the correction. The input for wings is in ControlSurface under InputId. Just paste the code there and it should be fine.
.
Please note that this is a band aid, this can cause weird flight characteristics on something that is very agile
snooter
Well people much worse than you have a higher point count anyways (such as me, my build quality sucks), so I don't see the point in you not deserving it.
+1.
Welcome to the dark side, your okthxbye permit will mailed to you shortly.
@AnimeGirlLover2010 your past usernames appear at the bottom of your biography.
@AnimeGirlLover2010 it is too late. The edit history of your bio is saved. So are edits to forum posts, airplane Posts, and comments. Besides, your username has your birth year in it.
@AnimeGirlLover2010 you put your exact birthdate in your bio. You are 12.
@Iaffey that pfp wasn't too inappropriate, besides, builds of such nature exist anyways.
+2@SheriffHackdogMCPE no
+1@ColonelCanada I belive this user will be banned, but for other unrelated reasons. The mods have already been notified.
+2Remove the hubcaps from my GP1 then load it in on low physics. You will see the true meaning of pain. If it doesn't happen, full throttle then enable slow mo
@ReinMcDeer this stalls for a certian amount of time
Here's my take on it.
.
Since you want the engines to stall for a certian amount of time after a certian condition is met, we gotta use variables.
Var: Timer = clamp(Condition | Timer < 60 & Timer > 0 ? Timer-0.07 : Timer + 60 , 0 , 60)
.
Var: Condition = smooth(AngleOfAttack, Y) = X
.
Then add this to the end of your engine inputs (replace X with your current engine throttle code and Y by how fast you want the engines to react):
.
X - smooth(Timer < 60 ? 1 : 0, Y)
.
.
.
The timer is roughly 15 seconds long, change 0.07 to any number to suit your needs, the higher the number, the faster It will count and vice versa, with the number being subtracted from the timer Timer each frame.
.
Since I don't know what conditions you want for this, just replace Condition with whatever conditions are needed for the stall as long as it's a True/False statement. The Timer will activate as soon as the statement returns true, even if it is only for a single frame
.
Here is an example build that uses the code
Heres an idea: make the whole thing non buoyant and use FT jet engines to set how high the whole thing sits in the water. Here is a formula I cooked up, it's untested but its similar to what I've used in an unreleased hovercraft I built.
.
ActivateV ? (AltitudeAgl < W ? 1 : 0) : (AltitudeAgl < (X-Y*Z) ? 1 : 0)
.
Replace V with desired activation group to toggle between normal and flood mode
.
Replace W with the Altitude that the cockpit is at when the boat is floating normally
.
Replace X with the default altitude that the cockpit is at when the boat is floating normally when in flood mode
.
Replace Y with a slider input (VTOL/Trim)
.
Replace Z with a multiplyer, Since inputs are between -1 and 1, you need go multiply it to subtract from the base Altitude. I would start with 10 and go up or down from there
I recommend using the really small jet engines with a high engine multiplyer and a low max input (such as a multiplyer of 30 and a max input of 0.15)
+1.
This is for the whole boat flooding, if you want to only use one side, only apply this to one side of the ship and replace AltitudeAgl with PitchAngle and the default and desired altitudes with angles instead. (And make one end of the boat buoyant)
.
This will allow for extreme customization, as you can have everything be changeable in the variable menu, allowing for quick changes in the code without having to edit 40 jet engines for one slight change
.
Pros: immediate level change with easily adjustable angle, depth, and speed with little to no wobble
.
Cons: FT is complex and can get laggy, more jet engines are needed to keep the ship level, as if the boat tilts, it turns
@idontknow8b @X99STRIKER microwaved
+2@idontknow8b if I have raw eggs, I can cook them into something, If you give me a cooked egg, all I can do is burn it
+2Here's an FT solution:
+3Clamp(X/(TAS+1.5/Y), -1, 1)Replace X with your desired input and replace Y with a number. The bigger the number you replace Y with, the smaller amount of resistance you will feel at high speeds. Ideally you should start with 1500-2500
1: raw
+42: 6 years
3: it's a 27 way tie, I wont list them here
4: standard white bread, it works best for sandwiches
5: mobile
6: people are getting platinum a LOT faster than they used to, other than that, it's alright, though something seems missing from the old days
Attaching a label directly to the detaching end of a detacher renders said detacher inoperable until the label is removed.
+1.
Not sure why this happens but it's been infuriating me for the past hour as I'm making cockpit directions that dissappear once they are followed
No
SP should already work on linux, as SP runs on the steam deck
What bomber? I don't see a bomber
+1Not things I hate doing but things I dislike in general:
+4.
1: having to rebuild something because i didn't make a backup
.
2: telling people that if they add the VR tag to their builds, they don't have to ping a curator (only ping me if the build in question is unlisted, otherwise, I can see it in my headset using the VR tag)
.
3: the undo button
.
4: connections on detachers, pistons, and suspension springs being incredibly wobbly even on high physics
.
5: the overabundance of replicas on the website (this game is about building the planes of your wildest dreams and you decided to build something that already exists. remember the days of hypno planes? Those were cool)
.
6: people who post memes in the airplane section
.
7: rewriting the same FT code 5 times because the last 4 iterations dont work or lag too much
.
8:
Tuning PID loops.
9: narcissists (there's not many, but I try my best to stay away when one crops up)
@BeastHunter I haven't heard any news of a new mod on the backend, though you could be right
+1@DeezDucks wait, you can edit comments?
Yeah we can - Vincent
+2Tea please
+2Talc: 0
Bronze: 100
Silver: 1,000
Gold: 5,000
Platinum: 25,000
Jade: 1*10²⁵⁵
Almadine: 1*10⁹⁹⁹
Grandidierite: NaN
@xNotDumb it's fine, I'm currently
Not doing much right now anyways, there's a heavy rainstorm outside at the moment
@xNotDumb I'll take a look either tonight or tomorrow night, I'm on vacation rn so maybe another curator will look at it. It has the VR tag so someone should get to it soon
@Neruneten21
+1See here
@Bellcat I asked Pedro how many people applied, a lot of people did, it will probably be another day or two until someone is chosen, and a day or two after that for it to be official
+1May he rest in peace, for technoblade has never lost a fight, even against cancer. Since the cancer died when he did, the battle was technically a draw. Technoblade never dies!
+6@asteroidbook345 yea, it was only open for about 3 days, I wonder how long it will take for them to decide
+1