Still, it was three bloody thousand characters of programming... I probably spent longer in programming that AFN2 than some of those popular builds spend in the whole plane's building progress.
Ah this is officially (?) called the "Fw Fighter w/ BMW 802"
The picture you posted (with contra-rotating propellers) is a variant with BMW 8011 engine.
I was going to make this myself....
@Ja380 You did not specify how long you want the door to close, I will assume it's also 8 seconds.
clamp01(smooth(LandingGear, 0.0625) * 2) for landing gear (set rotator speed to 100%)
clamp01(smooth(LandingGear, 0.0625) - 0.5) for door.
try it, I can't verify if it would work with just typing...
@exosuit You don't understand.
That method only works when you shoot 600 rounds in one burst. It does NOT simulate ammo consumption. It simulates gun overheat instead.
If you stop firing halfway, say, in 300 rounds, supposedly you should only have 300 rounds left, but the burst count system will reset you back to first round and you will still have 600 rounds in your next burst.
@exosuit That wouldn't work. once you stop firing the burst count is reset.
For example, assume you have burst count 200, and you stopped firing after 100 rounds.
Your next burst will still have 200 rounds, and unless you accidentally fired 200 rounds in one burst, you will still have indefinite ammo.
Uh, perhaps I should ask something before answering.
Do you comprehend the term "PitchAngle" correctly?
This is about AIRCRAFT pitch (i.e. nose up or down) not propeller or rotor pitch.
I see you mentioning rotors and it's quite alarming, so I think it's better to ask beforehand.
Now, assume that you know what PitchAngle does, and by "rotor" you mean "rotator"...
"The rotor rotates an additional 5 degrees each time "...
I assume you want a continuous output, not a step output as you are saying literally.
The input "PitchAngle" maxs out at 90 so you don't have to worry about upper limit, so it's PitchAngle/90 and set the rotator max at 1.
"how does the rotor can only be controlled when PitchAngle is below 0?"
you need to funky tree the activation group.
type "PitchAngle < 0" in the "activationGroup" slot.
Yeah I'm experiencing similar symptoms too.
I think you should slow down. Segregate your project into small bits. For example:
I'm now making my Ju 288 G-2 set to release after 1.9.2 is officially released. Now my build schedule looks like this:
Today: finish the instrument panel of the cockpit remake (which has been ongoing for a week)
Tomorrow: investigate the possibility of re-arranging nose shape
2 days later: make the new airbrake exterior
weekend: make the rear seat, radio stack
whole next week: make the turret, experiment with overspeed/engine overheat mechanism (which usually should only take 2 days)
Once you finished the objective of the day, close SP and do something else.
If you still feel stress, further reduce the load per day.
@SnoWFLakE0s I don't know much about structure, but yeah, maybe starting from scratch would be easier than modifying current SP into something like that.
I am modifying one of my works now, and yes, modifying is really more painful than creating from the very start.
get a 1.9.203 beta and use smooth function.
Assume you want to activate it 5 seconds after AG1 is turned on, input this on the "inputid" or "input":
sign(smooth(Activate1, 0.2))
@SnoWFLakE0s The point for this change is to make sure anything that FTed during 1.9.1 using LandingGear input still works in 1.9.203.
My stuff still does (improvement, they didn't in 202), but no guarantee everyone else's stuff does unless the LG input is the same as 1.9.1.
Since we took the trouble to invent the GearDown input for the "gear down light" purpose, why not just leave LandingGear the way it was in 1.9.1? that's the only way to ensure 1.9.1 planes still works perfectly without having to re-program.
...
my planes will continue to use LandingGear input because 0=down 1=up makes more sense mechanically (because 0 means initial state, and since planes are usually spawned on the ground, the initial state is "down".)
...
Either way I made 3 versions of my Ju 288.
One for 1.9.1 landing gear input, one for .202 beta input and one with .203 beta.
This "should" cover all probable circumstances.
@ThomasRoderick Well this thing was a WWI concept that the luftwaffe came up in 1940... it's already outdated.
Torpedoes are expensive, that's why they tried to find a cheaper solution.
That's why this thing fell out of favor when rocket munitions and guided bombs came out.
@Tang0five You engrave the cockpit camera point in the solid object.If you engrave the cockpit right on the boarder between two adjacent solid object, both will be transparent.
Note this doesn't work for hollow fuselage. only solid fuslage, sphere, hemisphere etc.
@jamesPLANESii my script:
clamp(sin(PitchAngle - -AngleOfAttack * cos(abs(RollAngle))) * GS / 167, -1, 1)
I think the difference is that my VSI would have homogeneous rotation while yours would be more sensitive on smaller readings. (aside from that I neglected slip angle)
Perhaps I should adopt your formula too.
What baffles me is that since the angles are in degrees (instead of rads) there shouldn't be a need for the pi factor....
@jamesPLANESii more like acceleration XYZ, and two versions, one relative to plane, one relative to map.
And I really hope for some parts-related values like
hp(partID), connection(partAID, partBID)
RPM(engineID) (right now we're using throttle input which isn't accurate, especially for engines with manual propeller pitch)
Plus a total new system, sequence. Useful for fancy landing gears.
@thefalkenreich Nah it's more like a series.
Originally it was SU1946 (Simple Universe 1946) with 1946-ish planes plus very overpowered engine.
Now I'm working my way back the timeline and make SUWW2 (late-WWII non-jet planes that does well in in-game WWII challenges (such as WWII Dogfight and WWII Torpedo Bomber challenge)
I also have a stall alarm, it works like this:
input: Sign(min((abs(AOA) -15), sign(IAS), sign(IAS - 223)))
so when AoA is > 15 at any direction AND IAS is >0 AND IAS is < 223 m/s, the buzzer will go off.
v>x doesn't seem to work with funky trees and I advise replacing them with "sign(v - x)"
@Adityo0502 Probably it was a bad choice to use the boom 9000 mod bomb parts to form the bomblets, whose bomb explosion is like 10-20x the load to the system...
@IStoleYourMeme Possible reason:
1. space between the symbols
2. you used .03 instead of 0.03 which causes the system to require the space
for your reference the altitude I'm using does not require spaces between the / and the functions and numbers
To everyone on this thread: I've made a basic instrument panel based on the settings of this post.
@Minecraftpoweer
@RailfanEthan
@EternalDarkness
Perhaps you guys would be interested.
@pancelvonat I hope you do understand that "I remember...." sometimes can also mean that "I am not entirely sure but I have an impression that..."
think about...
私の記憶によるでは
or something like that. (I'm bad in Japanese).
Like I said I'm bad at Japanese so you should probably expect a number of wrong Japanese here...
Still, it was three bloody thousand characters of programming... I probably spent longer in programming that AFN2 than some of those popular builds spend in the whole plane's building progress.
+1This is like the 5th time someone asked this.... you can literally just type "funky trees" in the aircraft search and find plenty of answers.
+1@SovietBun Nah it's fine, I still have plenty of Luft '46 stuff to make.
+1Ah this is officially (?) called the "Fw Fighter w/ BMW 802"
+1The picture you posted (with contra-rotating propellers) is a variant with BMW 8011 engine.
I was going to make this myself....
What ads? (using adblock)
+1@Shippy456 It's basically a programming language introduced in version 1.9. Now it has been used to build just about anything.
+1@Ja380 You did not specify how long you want the door to close, I will assume it's also 8 seconds.
clamp01(smooth(LandingGear, 0.0625) * 2) for landing gear (set rotator speed to 100%)
clamp01(smooth(LandingGear, 0.0625) - 0.5) for door.
try it, I can't verify if it would work with just typing...
+1Oh wow I was about to make this.... glad I chose something else...
More specfically I think this is the 252/3
Nice build!
+1@AircraftoftheRedStar Judging from other Luft 46 entries it looks like P.0310 blah blah blah is just a drawing number anyway...
+1if liking anime = weebs... yeah count me in.
+1- use cannon to propel your plane.
+1@SimoneRomano Good to hear.
+1Next time I make a plane with a manual fuel pump, I'll stop using countermeasures as input.
@USSR
+1@WarHawk95
@Miyubiaircraft
@Miyubiaircraft
+1@ChiChiWerx
@Dastin
Those instruments are possible now already. I think we need some advanced parts shaping tool (like subtraction) and better damage/crash model.
+1@exosuit You don't understand.
That method only works when you shoot 600 rounds in one burst. It does NOT simulate ammo consumption. It simulates gun overheat instead.
If you stop firing halfway, say, in 300 rounds, supposedly you should only have 300 rounds left, but the burst count system will reset you back to first round and you will still have 600 rounds in your next burst.
+1@exosuit That wouldn't work. once you stop firing the burst count is reset.
+1For example, assume you have burst count 200, and you stopped firing after 100 rounds.
Your next burst will still have 200 rounds, and unless you accidentally fired 200 rounds in one burst, you will still have indefinite ammo.
Uh, perhaps I should ask something before answering.
Do you comprehend the term "PitchAngle" correctly?
This is about AIRCRAFT pitch (i.e. nose up or down) not propeller or rotor pitch.
I see you mentioning rotors and it's quite alarming, so I think it's better to ask beforehand.
Now, assume that you know what PitchAngle does, and by "rotor" you mean "rotator"...
"The rotor rotates an additional 5 degrees each time "...
I assume you want a continuous output, not a step output as you are saying literally.
The input "PitchAngle" maxs out at 90 so you don't have to worry about upper limit, so it's PitchAngle/90 and set the rotator max at 1.
"how does the rotor can only be controlled when PitchAngle is below 0?"
+1you need to funky tree the activation group.
type "PitchAngle < 0" in the "activationGroup" slot.
Yeah I'm experiencing similar symptoms too.
I think you should slow down. Segregate your project into small bits. For example:
I'm now making my Ju 288 G-2 set to release after 1.9.2 is officially released. Now my build schedule looks like this:
Today: finish the instrument panel of the cockpit remake (which has been ongoing for a week)
Tomorrow: investigate the possibility of re-arranging nose shape
2 days later: make the new airbrake exterior
weekend: make the rear seat, radio stack
whole next week: make the turret, experiment with overspeed/engine overheat mechanism (which usually should only take 2 days)
Once you finished the objective of the day, close SP and do something else.
+1If you still feel stress, further reduce the load per day.
@SnoWFLakE0s I don't know much about structure, but yeah, maybe starting from scratch would be easier than modifying current SP into something like that.
+1I am modifying one of my works now, and yes, modifying is really more painful than creating from the very start.
- set the thickness of the tip side to be 0 (not sure how that'll look though)
- put a fuselage cone (not going to fit perfectly if you have control surface)
+1I tried to make an "automatic compensating" turret that automatically shoots along your turning arc, it wasn't very useful though.
+1get a 1.9.203 beta and use smooth function.
+1Assume you want to activate it 5 seconds after AG1 is turned on, input this on the "inputid" or "input":
sign(smooth(Activate1, 0.2))
@SovietBun It will be more than just recoding so it will take a while.
+1@SnoWFLakE0s The point for this change is to make sure anything that FTed during 1.9.1 using LandingGear input still works in 1.9.203.
+1My stuff still does (improvement, they didn't in 202), but no guarantee everyone else's stuff does unless the LG input is the same as 1.9.1.
Since we took the trouble to invent the GearDown input for the "gear down light" purpose, why not just leave LandingGear the way it was in 1.9.1? that's the only way to ensure 1.9.1 planes still works perfectly without having to re-program.
...
my planes will continue to use LandingGear input because 0=down 1=up makes more sense mechanically (because 0 means initial state, and since planes are usually spawned on the ground, the initial state is "down".)
...
Either way I made 3 versions of my Ju 288.
One for 1.9.1 landing gear input, one for .202 beta input and one with .203 beta.
This "should" cover all probable circumstances.
Zuiun is good.
+1Wait wut?
+1Latitude and longitude!?
GPS is HERE!
@ThomasRoderick Well this thing was a WWI concept that the luftwaffe came up in 1940... it's already outdated.
+1Torpedoes are expensive, that's why they tried to find a cheaper solution.
That's why this thing fell out of favor when rocket munitions and guided bombs came out.
Oh wow they really added Calculus!
+1@Tang0five You engrave the cockpit camera point in the solid object.If you engrave the cockpit right on the boarder between two adjacent solid object, both will be transparent.
+1Note this doesn't work for hollow fuselage. only solid fuslage, sphere, hemisphere etc.
@CrashFighter05
+1@Sm10684
@Miyubiaircraft
@MrSilverWolf I didn't have any exact blueprints, so I think I may have to correct about that on the release version.
+1@FranzPeterSiegfried
+1@edensk
@RailfanEthan
@Evenstsrike333
+1@Wi1dSk7
@MethaManAircraft
@jamesPLANESii my script:
+1clamp(sin(PitchAngle - -AngleOfAttack * cos(abs(RollAngle))) * GS / 167, -1, 1)
I think the difference is that my VSI would have homogeneous rotation while yours would be more sensitive on smaller readings. (aside from that I neglected slip angle)
Perhaps I should adopt your formula too.
What baffles me is that since the angles are in degrees (instead of rads) there shouldn't be a need for the pi factor....
@GeneralPatrick2 Congrats on getting the closest answer lol.
+1Should've saved before doing major changes....
+1I usually save every 5 minutes or so...
Use the mod, turn on the mod, take screenshots in-game (F12), your last 3 will be automatically there when you intend to upload
+1@Random40 Well I'm not trying to make the whole plane invincible... but perhaps it's too late now (260 parts and counting), maybe for my next plane.
+1basically anything other than the biggest two jets have pretty slow consumption that nobody actually worries about it...
+1I think this has been suggested before, but just like many good suggestions, it was soon forgotten...
+1@jamesPLANESii more like acceleration XYZ, and two versions, one relative to plane, one relative to map.
And I really hope for some parts-related values like
hp(partID), connection(partAID, partBID)
RPM(engineID) (right now we're using throttle input which isn't accurate, especially for engines with manual propeller pitch)
Plus a total new system, sequence. Useful for fancy landing gears.
+1@thefalkenreich Nah it's more like a series.
+1Originally it was SU1946 (Simple Universe 1946) with 1946-ish planes plus very overpowered engine.
Now I'm working my way back the timeline and make SUWW2 (late-WWII non-jet planes that does well in in-game WWII challenges (such as WWII Dogfight and WWII Torpedo Bomber challenge)
I also have a stall alarm, it works like this:
input: Sign(min((abs(AOA) -15), sign(IAS), sign(IAS - 223)))
so when AoA is > 15 at any direction AND IAS is >0 AND IAS is < 223 m/s, the buzzer will go off.
v>x doesn't seem to work with funky trees and I advise replacing them with "sign(v - x)"
+1@Adityo0502 Probably it was a bad choice to use the boom 9000 mod bomb parts to form the bomblets, whose bomb explosion is like 10-20x the load to the system...
+1Can't see the picture...
+1@IStoleYourMeme Possible reason:
+11. space between the symbols
2. you used .03 instead of 0.03 which causes the system to require the space
for your reference the altitude I'm using does not require spaces between the / and the functions and numbers
To everyone on this thread: I've made a basic instrument panel based on the settings of this post.
+1@Minecraftpoweer
@RailfanEthan
@EternalDarkness
Perhaps you guys would be interested.
From my experience this usually happens when you scale the cannon smaller and the full-sized shell impact something on its way out...
+1@pancelvonat I hope you do understand that "I remember...." sometimes can also mean that "I am not entirely sure but I have an impression that..."
think about...
私の記憶によるでは
or something like that. (I'm bad in Japanese).
Like I said I'm bad at Japanese so you should probably expect a number of wrong Japanese here...
日本語のwikipediaでは、52型の翼端は”切り捨て (丸形)"などと記入しています
多分僕は”切り捨て”だけを覚えて、そして”切り捨てならば元の丸形は無くすはず”などと判断して、そのせいで間違ったと思います。
英語は君にとっても、僕にとっても母語じゃないので、いろいろの誤解になったではないかと思います。英語では、コメントの最後に”end”、”period"とか書いたら、相手は簡単に”俺はもうお前と話したくない”という意味と理解される。そして向こうは”どうしてこいついきなり怒ったんだろう”と疑問が出ます。
とにかく、52型は切り捨てかつ丸形、そして君のあの”end"は悪意がない、これらをお互いに理解したら、今回の件はこれでいいだろう？
+1僕も時々日本製航空機を作るから、良かったらこちらにも参考しませんか？