@MitchellAviation
I'm sorry
it's just, I say what I say
yaknow dudes who will blatantly say whatever the fuck is in their minds, not thinking about whether if they're being rude or not?
yeah I'm that type of guy
sorry.
regardless, if you're making a teaser at least put an image or smth to make it appeal to the wider audience and not some guy who requests T on all of the teaser posts
btw about that MBT
it's still under development by Solm Defense Vehicle Manufacturer, might take a bit more time to be ready
once it's on full scale production, several units will be sent to the Krakabloan Army, prices can be considered later
in the meantime, if you want, we can send some upgraded KM2As, one unit will cost W$ 449.000 if all is taken into consideration
Tank: W$ 260.000
Logistics: W$ 20.000
Maintenance: W$ 24.000
Proper training: W$ 145.000
@Mrgoofy
I'm not really sure how I could simplify it more but here we go
basically the engine is only able to be operated in one way, not two ways
and since it's only be able to be operated in one way, only pitch down activates the engine, and not pitch up
to counteract this, put abs(Pitch) on the input so the engine turns on regardless of whether you pitch up or down
one reason is because the engines only support one sided input, which means it'll only pick up the positive value of the input, and not the negative
and since pitch down is positive pitch input, it only picks up the input from the pitch down
one way to fix this issue is using abs(Pitch) as the engine input
what abs(x) does is it turns every value except neutral or 0 of what x is to a positive value
so for example, if you pitch up 0.1 times the max value, it doesn't output the value as -0.1 (which is what it does without abs(x)) but rather as 0.1
it depends on the creator I guess
if for example they feel most mobile devices could handle their builds, they'll mark it as a mobile friendly device
I myself consider a build to be mobile friendly to be around <300 parts, but even a 300 part creation would sometimes be unfriendly, so the barrier is really vague tbh
so... How are you trying to achieve this "warning"?
Through texts, mayhaps? or lights?
nvm, I understand now, kinda
lemme get this straight
you want to make a warning about the rpm overspeed by stating how much time it has spent in it's overspeeding state, and you want it to count from 0 again when it reaches safe rpm before it spent 11 seconds in it's overspeed state?
in that case smooth(RPM1>maxRPM, (RPM1>maxRPM ? 1/11 : 1)) should work
need explanation?
so, RPM1>maxRPM should've been a boolean, right? But a boolean is also a value. True is essentially just 1, and False is 0. smooth(x, l) is essentially forcing the value to go through a rate, instead of instantaneously turning into the value it's supposed to be, whether it activates or deactivates.
to combat this, use the "if" format on the l part of smooth(x, l). If it reaches the maxRPM, it'll smoothen out the code. If it returns to a safe RPM after it oversped, it'll instantly return to 0 because you're not limiting it's rate of change, aka matching the same max rate as it's max value.
if you don't want the final value to show up as 1, then add *11 at the end of the code.
can confirm, this is how I did le gura plane
however, image from texts I don't recommend because it will significantly take up your performance
and you don't want to fly your own creation with 2fps after all
all I want honestly is a rework of the weapons (including but not limited to the combat that is AI and the countermeasures) and some measures of part reduction
as long as those things can be achieved, I'm happy
yeah sure, part reduction has been able to be achieved with the addition of fuselage cutting but imho, there's alot more things that can still be done
images aren't loading
@MitchellAviation
I'm sorry
it's just, I say what I say
yaknow dudes who will blatantly say whatever the fuck is in their minds, not thinking about whether if they're being rude or not?
yeah I'm that type of guy
sorry.
regardless, if you're making a teaser at least put an image or smth to make it appeal to the wider audience and not some guy who requests T on all of the teaser posts
nice.
PAT saikou
shame I'm not into mcdonalds
street foods are somehow always better
stop making teasers like these I swear
it's not going to appeal to the larger audience if it's plain like this
people need to stop complaining about some useless internet points
projectiles which lands at a steep angle does that though...
@Yourlocalhuman
read the comment again, I edited it kek
btw about that MBT
it's still under development by Solm Defense Vehicle Manufacturer, might take a bit more time to be ready
once it's on full scale production, several units will be sent to the Krakabloan Army, prices can be considered later
in the meantime, if you want, we can send some upgraded KM2As, one unit will cost W$ 449.000 if all is taken into consideration
Tank: W$ 260.000
Logistics: W$ 20.000
Maintenance: W$ 24.000
Proper training: W$ 145.000
@Inuyasha8215
that's the part where I don't understand
it's not funny
ok
@JustWingIt
oh ok
then yeah, change the Pitch to Roll or Yaw
@Yourlocalhuman
it could also end up being more than 50 tons :v
@Yourlocalhuman
it'll be in 30-40t is that good?
ya'll need an MBT? I'm tryna make one rn
le comanche
amazing.
grief
but that's how life goes, they take everything away from you, it's just a matter of time
sorry.
I don't know why, it doesn't even matter how hard I try
jokes aside, I can't think of anything else so I'll just updoot this post
@HoshimachiSuiseiMyBeloved
elo
oops, didn't realize the part count exceeded the limitation.
@jamesPLANESii
yeah, I'm aware
but tbf Idk what he's trying to do either so technically
zero wa warukunai yo ne?
@Mrgoofy
Idk, figure it out yourself
no.
part of code is wrong
aeh
@OwO
what the hell are you talking about
@32
not sure
but the most important part is what throttle percentage is it at for the aircraft to be level
@OwO
what the fuck do you mean a pudding
depends on how strong the thrust of your aircraft is compared to the weight of your aircraft
get those datas first then we can talk about business
just try not to care then
also this was a fucking month ago it's not even worth bringing up anymore
@OwO
never once I remembered talking about a pudding
@OwO
mayhaps you got the wrong person?
@OwO
I don't though
@OwO
wtf do you mean
@OwO
what
this is more of a Feeling type of forum tbh
hard to tell with such little detail
heya
so uh
new things? there's quite alot of them
@Mrgoofy
you're supposed to be putting that code only on the blasto vtol though
@Mrgoofy
I'm not really sure how I could simplify it more but here we go
basically the engine is only able to be operated in one way, not two ways
and since it's only be able to be operated in one way, only pitch down activates the engine, and not pitch up
to counteract this, put
abs(Pitch)on the input so the engine turns on regardless of whether you pitch up or downone reason is because the engines only support one sided input, which means it'll only pick up the positive value of the input, and not the negative
and since pitch down is positive pitch input, it only picks up the input from the pitch down
one way to fix this issue is using
abs(Pitch)as the engine inputwhat
abs(x)does is it turns every value except neutral or 0 of whatxis to a positive valueso for example, if you pitch up 0.1 times the max value, it doesn't output the value as -0.1 (which is what it does without
abs(x)) but rather as 0.1it depends on the creator I guess
if for example they feel most mobile devices could handle their builds, they'll mark it as a mobile friendly device
I myself consider a build to be mobile friendly to be around <300 parts, but even a 300 part creation would sometimes be unfriendly, so the barrier is really vague tbh
very epique
so... How are you trying to achieve this "warning"?
Through texts, mayhaps? or lights?
nvm, I understand now, kinda
lemme get this straight
you want to make a warning about the rpm overspeed by stating how much time it has spent in it's overspeeding state, and you want it to count from 0 again when it reaches safe rpm before it spent 11 seconds in it's overspeed state?
in that case
smooth(RPM1>maxRPM, (RPM1>maxRPM ? 1/11 : 1)) should work
need explanation?
so, RPM1>maxRPM should've been a boolean, right? But a boolean is also a value.
Trueis essentially just 1, andFalseis 0.smooth(x, l)is essentially forcing the value to go through a rate, instead of instantaneously turning into the value it's supposed to be, whether it activates or deactivates.to combat this, use the "if" format on the
lpart ofsmooth(x, l). If it reaches the maxRPM, it'll smoothen out the code. If it returns to a safe RPM after it oversped, it'll instantly return to 0 because you're not limiting it's rate of change, aka matching the same max rate as it's max value.if you don't want the final value to show up as 1, then add *11 at the end of the code.
can confirm, this is how I did le gura plane
however, image from texts I don't recommend because it will significantly take up your performance
and you don't want to fly your own creation with 2fps after all
pink.
very pog :D
all I want honestly is a rework of the weapons (including but not limited to the combat that is AI and the countermeasures) and some measures of part reduction
as long as those things can be achieved, I'm happy
yeah sure, part reduction has been able to be achieved with the addition of fuselage cutting but imho, there's alot more things that can still be done
@ReinMcDeer
thanks
@NotRandomBuilder8732
lah kan bilang sendiri