You could try: Activate5=(1)&(PitchAngle>60 | PitchAngle<-60) ? 1 : 0
However, I'm not sure if the gyroscope will accept this as an activation group (some parts don't accept expressions as activation groups).
I also haven't tested this code, but if the gyroscope will accept expressions as activation groups, then the code should theoretically work.
The most likely cause of the problem is aircraft/part collisions.
This can be fixed by simply setting disableAircraftCollisions to false on all of the landing gear components.
If you have already addressed this issue, then I have no other solutions at the moment.
@Far2Crispy Custom landing gear is quite complicated.
If it helps, rotators have a Current Angle output variable in the part output menu, which can be found above the connections tool.
This can be used for custom landing gear functions.
Analyzing and reverse engineering other user's landing gear might be a good way to start.
If you intend to start from scratch, here is a very useful guide to FT: https://snowflake0s.github.io/funkyguide/.
@MrCOPTY The flight computer is much farther forward than the view perspective (and the same is true for the CoM).
If you look closely, you can see the flight computer between the main wings of the aircraft.
@MrSilverWolf The CoM was nowhere near that far back on the aircraft. I also had the same issue with two previous aircraft attempts.
It's quite possible that the cause of the issue is an outdated mod.
The mod doesn't seem to work well with the default helicopter rotors.
I noticed that while the mod was enabled, my autogyro's rotor would randomly explode (this was only happening when the mod was enabled).
A small bug fix update would be helpful, since the mod can still be incredibly useful.
Unfortunately, I was unable to fix the problem. Without the existence of a simple delay function, it will probably require more complicated expressions to create input delays.
You would probably need to use AngleOfSlip data to determine your aircraft's flight direction. Such data would probably work best in a warning light.
Perhaps something like this: IAS>5&(AngleOfSlip>90 | AngleOfSlip<-90) ? 1 : 0
The code shown above worked for me when I used it. The code must be put into the input text field of the beacon light using the XML editor.
@ProfessionalLander That's ok.
Copy this into the post: .
I tested it, and it should work fine.
@ReinMcDeer It's fairly stable.
Of course, it still drifts a bit, so it does require the the user to be active at the controls to make adjustments to the aircraft's course.
The spaces between the text characters is a problem.
Do this: .
I recommend postimages.org for image uploads. Just be sure to use the direct link and not the normal link.
@asteroidbook345 You're thinking of TARS, CASE, or KIPP.
Yes, I was thinking about making TARS, but I made this instead.
Thoughts or suggestions? Let me know!
You could try: Activate5=(1)&(PitchAngle>60 | PitchAngle<-60) ? 1 : 0
However, I'm not sure if the gyroscope will accept this as an activation group (some parts don't accept expressions as activation groups).
I also haven't tested this code, but if the gyroscope will accept expressions as activation groups, then the code should theoretically work.
The most likely cause of the problem is aircraft/part collisions.
This can be fixed by simply setting
disableAircraftCollisionstofalseon all of the landing gear components.If you have already addressed this issue, then I have no other solutions at the moment.
@Bobyo You wouldn't be wrong. It is heavily based on the Thrust SSC.
Note: this is a filler project. I plan to upload a new aircraft soon (most likely another fighter jet, but that could change).
Thoughts or suggestions? Let me know!
@Far2Crispy Custom landing gear is quite complicated.
If it helps, rotators have a
Current Angleoutput variable in the part output menu, which can be found above the connections tool.This can be used for custom landing gear functions.
@MrCOPTY This also happened with two previous attempts at making an aircraft.
+1The problem could be an old mod.
@spindriftpilot No problem!
Analyzing and reverse engineering other user's landing gear might be a good way to start.
If you intend to start from scratch, here is a very useful guide to FT: https://snowflake0s.github.io/funkyguide/.
@MrCOPTY The flight computer is much farther forward than the view perspective (and the same is true for the CoM).
+2If you look closely, you can see the flight computer between the main wings of the aircraft.
@asteroidbook345 That's okay.
Users eventually figure out that the main server is functional, but these types of posts help expedite the process.
T.
+2For both of them.
Just add an @ in front of a moderator's name.
Tag a moderator.
For example: @TheFlightGuySP
@MrSilverWolf The CoM was nowhere near that far back on the aircraft. I also had the same issue with two previous aircraft attempts.
It's quite possible that the cause of the issue is an outdated mod.
The mod doesn't seem to work well with the default helicopter rotors.
+2I noticed that while the mod was enabled, my autogyro's rotor would randomly explode (this was only happening when the mod was enabled).
A small bug fix update would be helpful, since the mod can still be incredibly useful.
Note: I did find a solution to the problem.
However, I would still like to know to source/cause of the problem.
@Noname918181 It worked.
@Noname918181 I will note that the CoM is far in front of the view perspective.
I suspect it might be a glitch of some sort, but I could be wrong.
@Noname918181 Thanks! I'll try it out.
@WinsWings I'm glad you like it!
@MrCOPTY That's okay.
+1It may or may not help, but I do have a tutorial forum on creating solid rocket engines.
+1Unfortunately, I was unable to fix the problem. Without the existence of a simple
+2delayfunction, it will probably require more complicated expressions to create input delays.I'll look into it.
+1@atgxtg Looks great! A nice, simplistic design with lots of functionality.
@atgxtg No problem!
@IceCraftGaming Thanks! It's certainly one of my best builds to date.
+1You would probably need to use
AngleOfSlipdata to determine your aircraft's flight direction. Such data would probably work best in a warning light.Perhaps something like this: IAS>5&(AngleOfSlip>90 | AngleOfSlip<-90) ? 1 : 0
The code shown above worked for me when I used it. The code must be put into the input text field of the beacon light using the XML editor.
@ThereIsNoahScape What's ironic is that I have physics on "High".
@Echostar Thanks!
Link to the aircraft.
Link to the aircraft.
@NARGII
@PionierDynamics
@STENDEC
@X99STRIKER
@BeastHunter
@MrCOPTY
@Echostar
@IceCraftGaming
Thoughts or suggestions? Let me know!
@GuardianVN Just as a confirmation, the image I'm seeing is a small bomb about to hit a turret.
+1I do not know how to fix the problem any further.
@ProfessionalLander You should be able to.
+1It's a bit strange that it isn't visible to you, since I'm able to see it.
@ProfessionalLander The image is visible to me. Refresh the page and see what happens.
+2@ProfessionalLander I should also note that the
+2red textisn't needed to put in an image.@ProfessionalLander That's ok.
+2Copy this into the post:
.I tested it, and it should work fine.
@ReinMcDeer It's fairly stable.
+1Of course, it still drifts a bit, so it does require the the user to be active at the controls to make adjustments to the aircraft's course.
@ProfessionalLander Send the image link. I might be able to fix the issue.
+2The direct link is what needs to be put in the
+2(image link)section.The spaces between the text characters is a problem.
+2Do this:
.I recommend postimages.org for image uploads. Just be sure to use the direct link and not the normal link.
Many more people know about this server, they just haven't logged on yet.
+3@idk201011323 Thanks!