top speed and engine thrust is way above the real counterpart's top speed and thrust, but it's quite fun to fly. Try disabling drag on all parts except wings and one fuselage part and edit the drag of that single part to set the correct top speed (give the engine an accurate thrust amount before you adjust drag)
Also, trim is inverted and the wing loading is just too low, I higly doubt this plane stalled at 50 knots irl
@Thecatbaron I was using full trim on final approach at ~140 knots, but the fully loaded thing does make sense
I love the engines, by the way, great job!
set the image(s) as blueprint, click upload, take the screenshots of the image(s) and done. Don't forget to move the "blueprint" away from the build if you don't want it to appear in the pics
each image has its own aspect ratio, for example, a 1920x1080 image will be 16:9.
You can use any image as blueprint, the only requirement is that it shouldn't be a .gif file
The North American F-100 Super Sabre is an American supersonic jet fighter aircraft that served with the United States Air Force (USAF) from 1954 to 1971 and with the Air National Guard (ANG) until 1979. The first of the Century Series of USAF jet fighters, it was the first USAF fighter capable of supersonic speed in level flight.[4] The F-100 was designed by North American Aviation as a higher performance follow-on to the F-86 Sabre air superiority fighter.[5]
Adapted as a fighter-bomber, the F-100 was supplanted by the Mach two-class F-105 Thunderchief for strike missions over North Vietnam. The F-100 flew extensively over South Vietnam as the air force's primary close air support jet until being replaced by the more efficient subsonic LTV A-7 Corsair II.[6] The F-100 also served in other NATO air forces and with other U.S. allies. In its later life, it was often referred to as the Hun, a shortened version of "one hundred".
In January 1951, North American Aviation delivered an unsolicited proposal for a supersonic day fighter to the United States Air Force. Named Sabre 45 because of its 45° wing sweep, it represented an evolution of the F-86 Sabre. The mockup was inspected on 7 July 1951, and after over a hundred modifications, the new aircraft was accepted as the F-100 on 30 November 1951. Extensive use of titanium throughout the aircraft was notable.[8] On 3 January 1952, the USAF ordered two prototypes followed by 23 F-100As in February and an additional 250 F-100As in August.
The YF-100A first flew on 25 May 1953, seven months ahead of schedule. It reached Mach 1.04 in spite of being fitted with a de-rated XJ57-P-7 engine. The second prototype flew on 14 October 1953, followed by the first production F-100A on 9 October 1953. The USAF operational evaluation from November 1953 to December 1955 found the new fighter to have superior performance, but declared it not ready for wide-scale deployment due to various deficiencies in the design. These findings were subsequently confirmed during "Project Hot Rod" operational suitability tests.
floor(smooth(clamp01(LandingGear), 1/a)) delays input when activated, ceil(smooth(clamp01(LandingGear), 1/a)) does it when deactivated, a is the delay in seconds
It might not be the beta but it had never happened to me until this time:
After spending a couple hours applying the smooth feature to a plane, I saved it and my computer suddenly crashed. When I booted it up again and opened SP this message appeared and was unable to load the plane. The xml file was blank as well
For important speeds/limits use IAS
The higher the altitude the higher the stall speed in TAS is, while in IAS it doesn't change.
I would explain what both exactly are if I wasn't so sleepy, maybe someone else can do it instead
top speed and engine thrust is way above the real counterpart's top speed and thrust, but it's quite fun to fly. Try disabling drag on all parts except wings and one fuselage part and edit the drag of that single part to set the correct top speed (give the engine an accurate thrust amount before you adjust drag)
Also, trim is inverted and the wing loading is just too low, I higly doubt this plane stalled at 50 knots irl
the hinge must be angled too
Mm
@WarHawk95 it sadly doesn't, although it would be a really good feature
@Thecatbaron I was using full trim on final approach at ~140 knots, but the fully loaded thing does make sense
I love the engines, by the way, great job!
Lacks a bit of pitch authority, but other than that it's excellent as always
You're welcome!
clamp01(PitchAngle < -30 & IAS > 134.112 & Activate5)
+1you forgot the 10 fps
+4the guys below don't make mods, it might be possible to do
you do it by going to the second pinned forum post and reading the last part
you merged the E and C variants into a single one, what a horrible crime
You find photoshop CS6 for free in many places, works great
set the image(s) as blueprint, click upload, take the screenshots of the image(s) and done. Don't forget to move the "blueprint" away from the build if you don't want it to appear in the pics
I'm not really sure I understood what you need, do you want an engine that acts as afterburner when throttle is above 90%, or something else?
use structural wings, enable control surfaces on them via overload if necessary.
+1don't remove mass from hinges/rotators if what they move has mass
@Mekomara nice lol
Horizontal: 180 degrees, shortestAngle --> true
TargetSelected ? (TargetHeading-Heading)/180 : 0
Vertical: 180 degrees, shortestAngle --> true
+1TargetSelected ? clamp(TargetElevation-PitchAngle, -90, 10)/180 : 0
bug, it's been there forever
each image has its own aspect ratio, for example, a 1920x1080 image will be 16:9.
You can use any image as blueprint, the only requirement is that it shouldn't be a .gif file
looks good, but the seat is too far back
+1@natemomog yes
why is the tower on the left side...
Not possible unless the cockpit part is on the bomb
yes
The North American F-100 Super Sabre is an American supersonic jet fighter aircraft that served with the United States Air Force (USAF) from 1954 to 1971 and with the Air National Guard (ANG) until 1979. The first of the Century Series of USAF jet fighters, it was the first USAF fighter capable of supersonic speed in level flight.[4] The F-100 was designed by North American Aviation as a higher performance follow-on to the F-86 Sabre air superiority fighter.[5]
Adapted as a fighter-bomber, the F-100 was supplanted by the Mach two-class F-105 Thunderchief for strike missions over North Vietnam. The F-100 flew extensively over South Vietnam as the air force's primary close air support jet until being replaced by the more efficient subsonic LTV A-7 Corsair II.[6] The F-100 also served in other NATO air forces and with other U.S. allies. In its later life, it was often referred to as the Hun, a shortened version of "one hundred".
In January 1951, North American Aviation delivered an unsolicited proposal for a supersonic day fighter to the United States Air Force. Named Sabre 45 because of its 45° wing sweep, it represented an evolution of the F-86 Sabre. The mockup was inspected on 7 July 1951, and after over a hundred modifications, the new aircraft was accepted as the F-100 on 30 November 1951. Extensive use of titanium throughout the aircraft was notable.[8] On 3 January 1952, the USAF ordered two prototypes followed by 23 F-100As in February and an additional 250 F-100As in August.
The YF-100A first flew on 25 May 1953, seven months ahead of schedule. It reached Mach 1.04 in spite of being fitted with a de-rated XJ57-P-7 engine. The second prototype flew on 14 October 1953, followed by the first production F-100A on 9 October 1953. The USAF operational evaluation from November 1953 to December 1955 found the new fighter to have superior performance, but declared it not ready for wide-scale deployment due to various deficiencies in the design. These findings were subsequently confirmed during "Project Hot Rod" operational suitability tests.
+1@Typhoon03
you have an underscore in your username
+1that sounds like a problem of your device, I've never noticed any delay
+1
+3floor(smooth(clamp01(LandingGear), 1/a))
delays input when activated,ceil(smooth(clamp01(LandingGear), 1/a))
does it when deactivated,a
is the delay in secondsIt might not be the beta but it had never happened to me until this time:
After spending a couple hours applying the smooth feature to a plane, I saved it and my computer suddenly crashed. When I booted it up again and opened SP this message appeared and was unable to load the plane. The xml file was blank as well
attach the wing parts to rotators, 10 degrees should be enough
"endooosk" :(((((
+1nice plen
You can also allow the structural wing to have control surfaces via overload
false is the default option for zeroOnDeactivate, you will have to set it to true to notice a difference
missile gets stuck
hi
@Cemo43 thanks!
if you mean that the payload wobbles then make sure the pylons' massScale isn't less than 1
hidden by a moderator
dang, this got completely ignored
+1nope
@Poro Not if you open the image in a external browser
@Aldriech Always use IAS, mach number is directly proportional to TAS though
For important speeds/limits use IAS
The higher the altitude the higher the stall speed in TAS is, while in IAS it doesn't change.
I would explain what both exactly are if I wasn't so sleepy, maybe someone else can do it instead
there's this
You could also use
debugExpression
in the dev consoleBan evasion also breaks the rules, you should have used the beautiful "contact" button at the bottom of the site
100 posts to go
For that just tell the creator in the comments, it would be pretty useless imo
lol