@Hiimakeplanes I think it's a matter of making your thumbnails "pop". Typically you don't want your build to blend into the background. You also want to use fonts that compliment the build theme/screenshot (hopefully that makes sense).
I would recommend using Photoshop. Or, if you are unable to afford Photoshop, you can use Pixlr, which is essentially an online photoshop tool.
I use it for my screenshots. Here's an example: https://i.postimg.cc/qMQXvgfB/Nightswift-Thumbnail.png
That just means that a user wants to be tagged on your upcoming post.
For example: if I comment "T" on a teaser, the creator will tag me on the aircraft post with @TheFlightGuySP.
Adding a firingDelay attribute to the rocket pod via the XML editor should allow you to change the firing time.
The value is in seconds (seconds between each rocket firing).
@ColonelCanada They are likely using a fancy text generator. I belive it says at the bottom of the text formatting guide that strikethrough (along with a few other things) does not work on the website.
Problem#1: Flaps/Slats would probably fix that. Symmetric is the general choice for supersonic aircraft but is a bit unstable at high AoA (in my experience). It might also be the position of the CoM.
Problem#2: I would use a less powerful engine, and then just fly to higher altitudes for higher speed (this is more realistic).
Problem#3: Set the part type to Wing-2 in the XML editor.
@Bryan5 The current designation is E200, but that will change to E210 with the weaponized version.
I don't have an actual name for it yet, but I'm considering something like Nightswift or something on that order.
In other words, it's not necessarily inaccurate, it's just that the text labels require significantly more calculation than a basic block.
The extra calculation is mainly all the special variables and parameters associated with text labels. Rendering is also a little more complex, which adds to performance cost.
A single performance "point" is worth about 1 basic block. Fuselage components, as well as any other part that requires more calculation, has a higher individual performance cost. This is also coupled with the XML calculations of the aircraft, which can vary depending on variables, special functions, drag, etc. Edit: drag/collisions do not affect performance cost, just the performance itself.
Not every upload website works for the SP website.
I personally use postimages.org (if you use this, use the direct image link and not the normal image link), but Discord also works.
I haven't tested this, but I'm fairly certain floor(smooth(Activate#, 1)) would work.
Of course, you should change Activate# to your actual ejection input.
You can also change the number to adjust the delay. Making the number smaller increases the delay.
To increase high-altitude maneuverability, your aircraft either needs to travel faster or have less weight. This has worked in my experience.
Greater wingspan is also helpful if the aircraft doesn't need to go very fast.
@Hiimakeplanes
+1
is for uploading images.@Hiimakeplanes I think it's a matter of making your thumbnails "pop". Typically you don't want your build to blend into the background. You also want to use fonts that compliment the build theme/screenshot (hopefully that makes sense).
+1I would recommend using Photoshop. Or, if you are unable to afford Photoshop, you can use Pixlr, which is essentially an online photoshop tool.
+1I use it for my screenshots. Here's an example: https://i.postimg.cc/qMQXvgfB/Nightswift-Thumbnail.png
These are useful for getting more publicity on a post.
+1That just means that a user wants to be tagged on your upcoming post.
+1For example: if I comment "T" on a teaser, the creator will tag me on the aircraft post with @TheFlightGuySP.
Adding a
+1firingDelay
attribute to the rocket pod via the XML editor should allow you to change the firing time.The value is in seconds (seconds between each rocket firing).
@IceCraftGaming Haha, thanks, I'm glad you've enjoyed it!
+1From the looks of it, if you export the aircraft as an
+1.obj
you should be able to import it to Paint 3D.@MrCOPTY I've been thinking about it. I might post it as a filler post after my Nightswift.
+1@MrCOPTY Yep! It's made out of a few fuselage parts and formation lights.
+1@Coop09814 Yep, that will work. It will also create a lot of noise, so I would recommend using lower volume.
+1@ColonelCanada They are likely using a fancy text generator. I belive it says at the bottom of the text formatting guide that strikethrough (along with a few other things) does not work on the website.
+1Very nice!
+1T
@Coop09814 I'm sure there is. I'm not sure what that would be, however.
+1Wing-2
in the XML editor.Ooh, smooth tail logo.
+1T
Sailplane perhaps?
+1@MrCOPTY Thanks, I'm glad you liked it!
+1My next PSM aircraft will be even better!
Ooh, looks nice.
+1T
@rexzion o
+1Beautiful!
+1T
Never knew these existed...
+1It's oddly satisfying, and somewhat amazing...
@Bryan5 The current designation is E200, but that will change to E210 with the weaponized version.
+1I don't have an actual name for it yet, but I'm considering something like Nightswift or something on that order.
Hello there. Just figured I should let you know that only the first three people in a comment get a notification.
+1Looks great!
+1T
In other words, it's not necessarily inaccurate, it's just that the text labels require significantly more calculation than a basic block.
The extra calculation is mainly all the special variables and parameters associated with text labels. Rendering is also a little more complex, which adds to performance cost.
+1A single performance "point" is worth about 1 basic block. Fuselage components, as well as any other part that requires more calculation, has a higher individual performance cost. This is also coupled with the XML calculations of the aircraft, which can vary depending on variables, special functions, drag, etc.
+1Edit: drag/collisions do not affect performance cost, just the performance itself.
Ah, minhas desculpas. Eu entendi errado a pergunta.
+1@MAPA Much appreciated!
+1Congratulations!
+1@N1KO Very nice aircraft you have made!
+1@PPLLAANNEE I've been thinking about modifying the Little Bugger to have a parafoil, so I might do that at some point.
+1@TheGliderGuy Much appreciated!
+1Very nice!
+1T
Ah, it worked.
+1Very nice.
Imgur images don't work on the SP website. That's why you haven't been able to upload an image.
+1Not every upload website works for the SP website.
+1I personally use postimages.org (if you use this, use the direct image link and not the normal image link), but Discord also works.
Perhaps a sailplane?
+1Or maybe a tailless aircraft of some sort?
@WINGSIRON Glad I could help!
+1The code is stored in the Variables menu.
+1Both my C200 sailplane and more recent D800 have wingflex code. You may use those if you would like, but you will probably need to adjust the values.
+1@IMULAerospaceIndustries Nice! Glad I could help!
+1I haven't tested this, but I'm fairly certain
+1floor(smooth(Activate#, 1))
would work.Of course, you should change
Activate#
to your actual ejection input.You can also change the number to adjust the delay. Making the number smaller increases the delay.
@Kendog84 Hmm, seems logical.
+1@MAPA @MrCOPTY @Bo1233 Thanks!
+1To increase high-altitude maneuverability, your aircraft either needs to travel faster or have less weight. This has worked in my experience.
+1Greater wingspan is also helpful if the aircraft doesn't need to go very fast.
@PPLLAANNEE I can't unsee that.
+1@Bo1233
+1I apologize. You requested that I tag you on my future posts, and I forgot to tag you sooner.
@MrCOPTY It's essentially a fighter/interceptor F-20 Tigershark in certain aspects.
+1@PlaneGuy01 Hmm. Well, I'm not entirely sure how to fix the issue, since I don't typically mess with
+1ammo()
.