Perhaps it can be better if you'll say it's unity's C# and miss some parts of description but tell it basic info about flight dynamics and geometry instead.
And as Redrocktumbler said you'll perhaps need to repeat your description once in a while, because ANN itself is stateless and "memory" of that one is just last ~3k of tokens glued to your message.
And no, you must not overestimate ANN, it's more like polynomial approximation than AI you wish to see.
Well, you're right that label will be recalculated every SP frame, but it will select one (very long) string instead of checking (and sometimes recalculating) hundreds of separate pixels. I don't really know if ternary with floats is equivalent to ternary with (very long) string at runtime, but either way i think there's more pixels than frames.
Is it really faster to use a variable and format string for each pixel (<#{!pixel?"0000":pixel}>...) instead of using an expression for each frame ({t=0?frame:""}{t=1?frame:""}...)?
@DatMaluchGuy19
Try to add 22 closing parentheses in the end of p_tgt.next.z,p_tgt.next.x,p_tgt.links.z,p_tgt.links.x and 3 closing parentheses in the end of p_tgt.next
@DatMaluchGuy19 VC variable, it's in meters per second, and it's signed i.e. negative value means it must go backwards. TC controls engine directly, you can set it to 1 if you want to go as fast as possible.
Husky's right, SP build files aren't that large.
If you want, you can upload them as hidden ("Visibility" button in uploading widget), they'll be saved on SP site but will only be visible for you.
@winterro p_tgt.i stores id of currently selected point
p_tgt.x, p_tgt.z are coords of currently selected point p_tgt.links.x, p_tgt.links.z are ids of points where it can go from currently selected one.
p_tgt.i switches to one of p_tgt.links.x%100, p_tgt.links.x//100, p_tgt.links.y%100, and p_tgt.links.y//100 every time car gets close-enough to currently selected point
Other variables aren't significant for routing, they're used to tame car itself, to make it unable to go to previous point, to make it not headbutt others, to make it stop at dead ends, to make it remember gifts without leaving too much inside label...
Link to txt file CameraPosX variable must be camera's horizontal offset in meters
IDK if it'll work, but if it will it must be 5cm orange circle clamped by two vertical edges located 10cm away from label's left edge.
__D is dampener, __P is gain PCi=(lerp(TAlt,h,pow(TD/200,2))-FCAltitude+rate(lerp(TAlt,h,pow(TD/200,2))-FCAltitude)*__D)*__P
40 here is some distance after which missile surely can't damage airplane
Missile's pitch angle=smooth((abs(Longitude-FCLongitude)+abs(Latitude-FCLatitude))<40|(PCi!=PCi)?0:sign(PCi)*90,(PCi!=PCi)?0:abs(PCi))
Be carefull, SP forum might not display full expressions
So, does anybody have any pointers about getting started?
Tutorial section of forums and videos, and perhaps some geometry.
What am i looking for with my centers of mass, thrust, and lift?
Thruster must face towards center of mass (if you don't want to use it to rotate craft), so for forward-facing engines usually center of thrust is directly behind center of mass.
Center of lift is where wing's forces are applied, it moves while you fly.
Usually wing pulls airplane up, so in cruise CoL is near CoM, but such airplane won't decrease pitchrate naturally.
At high AoA both lift and drag are higher, so if CoL is in front of CoM it'll pull airplane's nose back and upwards, increasing AoA even further, which will eventually lead to stall or uncontrollable spin.
If CoL is behind CoM, it will pull tail away from direction of flight, so airplane will be pretty stable, but if CoL will be too far from CoM you won't be able to control it.
In real life getting center of lift is not that easy, so usually it's recommended to get center of mass around quarter-chord behind midpoint of leading edge.
How do i make a slick or at least cohesive fuselage? I see some incredible stuff on here and want to leave my own work on the table.
I can't really say much about it. Fuselage is 28-sided (circular ones are 24-sided), in newer versions you can "slice" specific part from it with four planes. Greater ones are using hollow fuselages as plating (e.g. screenshot from this post), but it will require either a lot of time or geometry knowledge and calculator to align them properly.
Also, what the heck do upvotes do? And do i spend points to give them?
They do nothing but they're used in rating, both for crafts and users. You don't need anything to give one.
Stick here.
It's still good if you need abstract stuff.
From abstract stuff strong-willed ones build sub-assemblies and game itself.
From abstract stuff weak-minded ones build flying tic-tac and Andrew's face.
Well, i don't really understand how to get that index. It appears to be related to time (or rather number of crafts uploaded), last uploaded one (X0Zk6W) uses 1289, 0BFd5E from two days ago uses 1288, Maxwell from 8 months ago uses 1185.
Knowing that you can use brute force to try all possible indexes (looks like there's no rate limit) but it takes a lot of time and i feel bad about it.
async function get(airplane_id,minIndex,maxIndex){
lnk="https://jundroo.blob.core.windows.net/simpleplanes/GameData/aircraft/_I_/"+airplane_id+".xml"
if(minIndex===undefined){minIndex=0}
if(maxIndex===undefined){maxIndex=2048}
var res=-1
async function tryLoad(i){
try{
await fetch(lnk.replace("_I_",i.toString()))
.then((resp)=>{if(resp["status"]==200){res=i}})
}catch(err){return}
}
for(i=minIndex;i<=maxIndex;++i){
await tryLoad(i)
if(res!=-1){return res}
}
}
The last part (cGGD1h) is obviously aircraft id, but i don't understand what 728 means here and just letting it as-is doesn't works.
So to use it you need id of craft (which is not a thing everyone memorizes) and some number of unknown purpose (which might be id of archive or folder stored internally just for faster indexing).
So yes, "jundroo forgot to delete aircraft files" sounds cool but doesn't really sounds useful for now. (for crafts that were not deleted there's standard api, https://www.simpleplanes.com/Client/DownloadAircraft?a=ID)
@FlyingPotato_131 Thanks for reminding about it, but no.
It was generated 2.2 years ago and became legacy 2 or 3 months after. Just use labels if you need.
smooth(sign((input-current)+rate(input-current)*D),
P*abs((input-current)+rate(input-current)*D))
SP forum doesn't displays full line, so it's split with linefeed.
It's a form of PID, P is gain, D is dampener
It's always clamped between -1 and 1, and will perhaps be 1 at the level start.
It's generally not proportional to input and it's not suitable for rockets|TVC, but it works fine with control surfaces.
For high-speed airplanes, don't forget that airplane's behaviour changes with airspeed.
Try to increase D gain of PID to make it work correctly at some specific speed
Then add /max(1,pow(IAS/X,2)) to the end of code, X here is speed at which it works correctly (in meters per second).
@Skykid028 I do not have android device.
About colors, i got one more similar message recently and i noticed that result from different user is slightly different, but at the moment i don't know why is it different and how to fix it.
For your specific case i can suggest to increase number of bits per color if possible, although i doubt it is the problem.
min(90,max(10+atan(TAS/(2*pi*PROP_RADIUS*0.5*PROP_RPM*60)),0))/90 will perhaps work
PROP_RADIUS is in meters, not blocks.
So, you calculate velocity at the middle of blade, add velocity of airplane relative to air, calculate angle between result and propeller plane, and add 10 degrees.
@Johnnyynf Because of colliders?
Colliders are convex even for hollow fuselages, so i don't think they will make gear collide like actual one, it will rather work like cylinder or cone.
@jamesPLANESii
I think there's still things that act on specific part, not body, like collisions and bullets.
For entire body you can't remove internal faces, because body can be changed, e.g. one part can reveal other one when destroyed. But if some object is single part, you can make sure that it's meshes will never be changed, so you can remove all internal faces by the time you load part specifications.
@Yish42 TargetSelected, so it's about you having target, not about target locking you.
+1@Speedhunter
+2https://www.simpleplanes.com/Forums/View/1683931
https://www.simpleplanes.com/Forums/View/1454422
Perhaps it can be better if you'll say it's unity's C# and miss some parts of description but tell it basic info about flight dynamics and geometry instead.
And as Redrocktumbler said you'll perhaps need to repeat your description once in a while, because ANN itself is stateless and "memory" of that one is just last ~3k of tokens glued to your message.
And no, you must not overestimate ANN, it's more like polynomial approximation than AI you wish to see.
Well, you're right that label will be recalculated every SP frame, but it will select one (very long) string instead of checking (and sometimes recalculating) hundreds of separate pixels. I don't really know if ternary with floats is equivalent to ternary with (very long) string at runtime, but either way i think there's more pixels than frames.
+1Is it really faster to use a variable and format string for each pixel (<#{!pixel?"0000":pixel}>...) instead of using an expression for each frame ({t=0?frame:""}{t=1?frame:""}...)?
source?
+1I mean, i didn't saw her with cat ears, and style seems wrong (although maybe it's because of low resolution).
@DatMaluchGuy19
+1Try to add 22 closing parentheses in the end of
p_tgt.next.z,p_tgt.next.x,p_tgt.links.z,p_tgt.links.xand 3 closing parentheses in the end ofp_tgt.next@DatMaluchGuy19
VCvariable, it's in meters per second, and it's signed i.e. negative value means it must go backwards.TCcontrols engine directly, you can set it to 1 if you want to go as fast as possible.Ehm, you do know there's (builtin)
atanfunction for angle and pythagorian addition for distance, right?Husky's right, SP build files aren't that large.
If you want, you can upload them as hidden ("Visibility" button in uploading widget), they'll be saved on SP site but will only be visible for you.
@winterro
p_tgt.istores id of currently selected pointp_tgt.x,p_tgt.zare coords of currently selected pointp_tgt.links.x,p_tgt.links.zare ids of points where it can go from currently selected one.p_tgt.iswitches to one ofp_tgt.links.x%100,p_tgt.links.x//100,p_tgt.links.y%100, andp_tgt.links.y//100every time car gets close-enough to currently selected pointOther variables aren't significant for routing, they're used to tame car itself, to make it unable to go to previous point, to make it not headbutt others, to make it stop at dead ends, to make it remember gifts without leaving too much inside label...
@DatMaluchGuy19 Yes, you can.
+1Link to txt file
CameraPosXvariable must be camera's horizontal offset in metersIDK if it'll work, but if it will it must be 5cm orange circle clamped by two vertical edges located 10cm away from label's left edge.
FCLongitude,FCAltitude,FCLatitudeare coords of missileTD=sqrt( pow(Longitude-FCLongitude+TargetDistance*cos(TargetElevation)*sin(TargetHeading),2) + pow(Latitude-FCLatitude+TargetDistance*cos(TargetElevation)*cos(TargetHeading),2) )TAlt=Altitude+TargetDistance*sin(TargetElevation)h=5+195*(.5+.5*cos(clamp(0.1*TD+20,0,340)))+1800*(.5+.5*cos(clamp(.01*(TD-45000),0,180)))__Dis dampener,__Pis gainPCi=(lerp(TAlt,h,pow(TD/200,2))-FCAltitude+rate(lerp(TAlt,h,pow(TD/200,2))-FCAltitude)*__D)*__P40here is some distance after which missile surely can't damage airplaneMissile's pitch angle=
smooth((abs(Longitude-FCLongitude)+abs(Latitude-FCLatitude))<40|(PCi!=PCi)?0:sign(PCi)*90,(PCi!=PCi)?0:abs(PCi))Be carefull, SP forum might not display full expressions
+1AFAIK there's no way to get RWR in the game, but mention me please if you'll ever get one.
+2Don't worry, being stupid isn't something special nowadays.
Reshade is perhaps what you meant, but it have nothing to do with Jundroo.
Tutorial section of forums and videos, and perhaps some geometry.
Thruster must face towards center of mass (if you don't want to use it to rotate craft), so for forward-facing engines usually center of thrust is directly behind center of mass.
Center of lift is where wing's forces are applied, it moves while you fly.
Usually wing pulls airplane up, so in cruise CoL is near CoM, but such airplane won't decrease pitchrate naturally.
At high AoA both lift and drag are higher, so if CoL is in front of CoM it'll pull airplane's nose back and upwards, increasing AoA even further, which will eventually lead to stall or uncontrollable spin.
If CoL is behind CoM, it will pull tail away from direction of flight, so airplane will be pretty stable, but if CoL will be too far from CoM you won't be able to control it.
In real life getting center of lift is not that easy, so usually it's recommended to get center of mass around quarter-chord behind midpoint of leading edge.
I can't really say much about it. Fuselage is 28-sided (circular ones are 24-sided), in newer versions you can "slice" specific part from it with four planes. Greater ones are using hollow fuselages as plating (e.g. screenshot from this post), but it will require either a lot of time or geometry knowledge and calculator to align them properly.
They do nothing but they're used in rating, both for crafts and users. You don't need anything to give one.
+1Stick here.
It's still good if you need abstract stuff.
From abstract stuff strong-willed ones build sub-assemblies and game itself.
From abstract stuff weak-minded ones build flying tic-tac and Andrew's face.
Camera must not be attached to thing rotated by rotator.
ammo("Weapon Name")("here is " )See comment here for fly-by-wire, i don't want to repeat it here.
"going away from target" is literally
rate(TargetDistance)>0, is it what you need?Well, it sucks.
Knowing two of three inputs and HMAC, can we try to guess hash function and key they're using?
+1Well, i don't really understand how to get that index. It appears to be related to time (or rather number of crafts uploaded), last uploaded one (X0Zk6W) uses 1289, 0BFd5E from two days ago uses 1288, Maxwell from 8 months ago uses 1185.
Knowing that you can use brute force to try all possible indexes (looks like there's no rate limit) but it takes a lot of time and i feel bad about it.
async function get(airplane_id,minIndex,maxIndex){
lnk="https://jundroo.blob.core.windows.net/simpleplanes/GameData/aircraft/_I_/"+airplane_id+".xml"
if(minIndex===undefined){minIndex=0}
if(maxIndex===undefined){maxIndex=2048}
var res=-1
async function tryLoad(i){
try{
await fetch(lnk.replace("_I_",i.toString()))
.then((resp)=>{if(resp["status"]==200){res=i}})
}catch(err){return}
}
for(i=minIndex;i<=maxIndex;++i){
await tryLoad(i)
if(res!=-1){return res}
}
}
The last part (
cGGD1h) is obviously aircraft id, but i don't understand what728means here and just letting it as-is doesn't works.So to use it you need id of craft (which is not a thing everyone memorizes) and some number of unknown purpose (which might be id of archive or folder stored internally just for faster indexing).
So yes, "jundroo forgot to delete aircraft files" sounds cool but doesn't really sounds useful for now. (for crafts that were not deleted there's standard api,
https://www.simpleplanes.com/Client/DownloadAircraft?a=ID)@FlyingPotato_131 Thanks for reminding about it, but no.
It was generated 2.2 years ago and became legacy 2 or 3 months after. Just use labels if you need.
Do something with your text, it takes too much time to read it with all those effects.
Oh, so it can write a switch statement in python, so what?
@BotFinder2023 Boy, do you really think others are held together by magic?
+1smooth(sign((input-current)+rate(input-current)*D),P*abs((input-current)+rate(input-current)*D))
SP forum doesn't displays full line, so it's split with linefeed.
It's a form of PID,
Pis gain,Dis dampenerIt's always clamped between -1 and 1, and will perhaps be 1 at the level start.
It's generally not proportional to input and it's not suitable for rockets|TVC, but it works fine with control surfaces.
For high-speed airplanes, don't forget that airplane's behaviour changes with airspeed.
Try to increase D gain of PID to make it work correctly at some specific speed
Then add
/max(1,pow(IAS/X,2))to the end of code,Xhere is speed at which it works correctly (in meters per second).Welcome back, sensei!
@Skykid028 I do not have android device.
+1About colors, i got one more similar message recently and i noticed that result from different user is slightly different, but at the moment i don't know why is it different and how to fix it.
For your specific case i can suggest to increase number of bits per color if possible, although i doubt it is the problem.
@DJW730 AG1&TargetSelected
@StonedOutBurger Some people say it does but i didn't tested it myself.
Epic fail.
+1Try to ask in FTLab, they had a channel for pre-made codes.
you say while continuing to complain.
Did someone report about it? Is it possible to fix without tearing engine apart?
Rocket.
Labels, it will always be more customizable than any grid.
"S" on image is concealed in cloud, so looks like text says "TARFIGHTER", not "STARFIGHTER".
@piglincheerful To clarify, are you a bot?
+1What's up with that link you attached to the end of your comment?
There's always a way to ruin tech, but can you make the tech better?
+1@32 Just designer and it's not that close to release, more like pre-alpha.
+1Autocorrect preferring collar over collab? Hey, that's pretty interesting!
+1How did you even teach it?
@U2
To store value select address (buttons a0...a7), select value (buttons 0...7), enable wrt button, switch clk button.
To read value select address (buttons a0...a7), disable wrt button, switch clk button.
There's two pages from author on renderdock, perhaps there's more info than you found on old blueprint.
+2link1 link2
EA6B (electronic warfare) with chaos rat camo.
+1min(90,max(10+atan(TAS/(2*pi*PROP_RADIUS*0.5*PROP_RPM*60)),0))/90will perhaps workPROP_RADIUS is in meters, not blocks.
So, you calculate velocity at the middle of blade, add velocity of airplane relative to air, calculate angle between result and propeller plane, and add 10 degrees.
You can try to use button with interactionType=Toggle and some activation group for actual weapons.
+1@Johnnyynf Because of colliders?
Colliders are convex even for hollow fuselages, so i don't think they will make gear collide like actual one, it will rather work like cylinder or cone.
I mean control base can act as a spring both for position and rotation, and with some tweaking you can make it bend just as much as you need.
+2@jamesPLANESii
I think there's still things that act on specific part, not body, like collisions and bullets.
For entire body you can't remove internal faces, because body can be changed, e.g. one part can reveal other one when destroyed. But if some object is single part, you can make sure that it's meshes will never be changed, so you can remove all internal faces by the time you load part specifications.