I just tested it, and the wobble you speak of is an intentional design by the original creator. There is some funky trees code used to stabilize the aircraft that results in the canard not behaving as you would expect.
@RepublicOfCursedPlanes Oh, if you mean the plane in the images, it's actually a different plane entirely. I just use the same general fuselage construction for all my planes.
I always use grammar when commenting or posting on this website, sometimes omitting full stops for short, one sentence comments. In Discord grammar's mostly a lost cause, however.
Never ever
Mods are only "technically" supported + scripts are not supported + idk how to make android mods + no
Comments asking for android or any mobile version will be removed because clearly no-one can read
@HazerzIsBack Just going to let you know, behind the scenes I've been working on the cockpit screens, among MANY other details. I'll even share this sneak peek of some new stuff. EICAS Closeup. It's fully vanilla btw, no mods except for the 3D models (none of which are in the cockpit).
Expect an official progress update in the next few weeks.
If it's at the default of 100, it doesn't show up, just like a lot of other attributes. If you are on PC, use this script, otherwise send it to me and I'll do it.
@MobileBuilder21 In my opinion, the best practice for variables is to leave the switch alone. By putting a switch on, say, BatteryInput, and the actual battery on Battery * BatteryInput, if the battery is 0 the switch does not turn off. This makes it more realistic.
@MobileBuilder21 I checked out you file, the main issue is the lack of having separate switch variables. The switches should always be their own variable (e.g. BatteryInput), and the Battery variable simply references that switch. Try doing this and let me know how you go.
Also another bug I just remembered, if there is no camera set as the "cockpit view" camera (after fly-by view), then using the input to cycle through previous cameras doesn't work. If I try and go back, I can't go further than chase view. This is likely because the game is trying to find the cockpit view camera but can't because it doesn't exist.
This video should help with the startup sequence. About the RPM, you can make the gauge linked to thrust but change the multiplier so the gauge needle shows a different value than the thrust gauge.
@SPAircraftOfficial @Maver1ck To further improve this code, use:
clamp01(Throttle > 0.8 & IAS > 857.5)
Is 1 when the conditions specified in the post are true, otherwise it is 0.
Hi again, I'm working on modifying your ILS to suit my systems, and I have a question.
How did you calculate the latitude and longitude values for each runway threshold? I've noticed there are two latitude and two longitude values per runway, and I'm not sure how they were calculated. I'm asking this because I want to add two more airports into the system. I managed to reverse engineer the math and got pretty close, but my glideslope is off a bit.
After analysis, I was able to determine the very small mass is the culprit.
This, but if you count in development, this.
+1I've had this bug many times. What happens is no menu items disappear when they should. Simple solution, exit and reenter the designer.
+2@ToeTips @florky No clue.
I played it on an old iPad that is now long gone. Can't remember much aside from it including a lot of ragdolls and beams.
I just tested it, and the wobble you speak of is an intentional design by the original creator. There is some funky trees code used to stabilize the aircraft that results in the canard not behaving as you would expect.
@HazerzIsBack 2 years*
@Sense2 Hopefully Christmas
@jamesPLANESii @XtarsAgency You didn't copy the direct link. It needs to end in .jpg.
@1link598 Thanks! I'm really hoping for Christmas this year, but we'll see when I get closer.
@RepublicOfCursedPlanes Oh, if you mean the plane in the images, it's actually a different plane entirely. I just use the same general fuselage construction for all my planes.
+1Loaf of bread
@RepublicOfCursedPlanes What do you mean?
+1@Wolf211 Your only posts are over a year old, I'm not sure what post you are referring to.
@Wolf211 The content on the homepage is only stuff that is a less than a week old, maybe that's why?
@Wolf211 Strange, what problems do you encounter?
@jamesPLANESii ok this is staying
+2@jamesPLANESii What he said
@jamesPLANESii This has gotta be a record for the best first build.
+3@32 SP is heavily CPU bound, not GPU at all. Unless you install mods that add 3D models, the GPU has literally no impact.
Here
I always use grammar when commenting or posting on this website, sometimes omitting full stops for short, one sentence comments. In Discord grammar's mostly a lost cause, however.
Set one cannon's delay to 0 (using xml)
Those are broken propeller blades from a despawned AI craft.
+2NO ANDROID
Never ever
Mods are only "technically" supported + scripts are not supported + idk how to make android mods + no
Comments asking for android or any mobile version will be removed because clearly no-one can read
I would use
+1clamp01(!Activate5) * InputReplace
Inputwith Pitch, Roll, or Yaw based on what control surface you are replacing.@MrShenanigansSP I wish I could run it
+4This needs more recognition, have a spotlight.
I just checked the reference list, and unfortuantly there isn't a way to tell if you are targeted. I hope this helps.
+1@Mustang51 Not sure what you mean. My code is 1 whenever you go above mach 1. I'm not sure what you mean by "specific speed".
@TinyMaus Yes, but heavily modified. Some of the things I've added are autopilot target markers, ILS markers, some text modifications, and much more.
@HazerzIsBack Just going to let you know, behind the scenes I've been working on the cockpit screens, among MANY other details. I'll even share this sneak peek of some new stuff. EICAS Closeup. It's fully vanilla btw, no mods except for the 3D models (none of which are in the cockpit).
Expect an official progress update in the next few weeks.
If it's at the default of 100, it doesn't show up, just like a lot of other attributes. If you are on PC, use this script, otherwise send it to me and I'll do it.
+2@MoDeRAzToRZ bAn this guy nOWWWW!!!
@TheTomatoLover I'm not though...
+1I'm just interested in aviation.
@MobileBuilder21 In my opinion, the best practice for variables is to leave the switch alone. By putting a switch on, say, BatteryInput, and the actual battery on Battery * BatteryInput, if the battery is 0 the switch does not turn off. This makes it more realistic.
@MobileBuilder21 I'm sorry, but I have my own projects to work on.
@MobileBuilder21 I checked out you file, the main issue is the lack of having separate switch variables. The switches should always be their own variable (e.g. BatteryInput), and the Battery variable simply references that switch. Try doing this and let me know how you go.
Also another bug I just remembered, if there is no camera set as the "cockpit view" camera (after fly-by view), then using the input to cycle through previous cameras doesn't work. If I try and go back, I can't go further than chase view. This is likely because the game is trying to find the cockpit view camera but can't because it doesn't exist.
@WNP78 I've tagged you on a plane with simple recreation steps.
you can teleport
When any part outputting to a variable is destroyed it causes a null reference exception and all variables stop evaluating.
This video should help with the startup sequence. About the RPM, you can make the gauge linked to thrust but change the multiplier so the gauge needle shows a different value than the thrust gauge.
@HazerzIsBack ... and the SWL-120 is still in development lol
@Maver1ck This goes in the input section of the engine. It goes in the throttle.
@SPAircraftOfficial @Maver1ck To further improve this code, use:
+1clamp01(Throttle > 0.8 & IAS > 857.5)
Is 1 when the conditions specified in the post are true, otherwise it is 0.
+2clamp01(TAS > 343)This is 1 whenever you are above Mach 1.
Yesn't
Hi again, I'm working on modifying your ILS to suit my systems, and I have a question.
How did you calculate the latitude and longitude values for each runway threshold? I've noticed there are two latitude and two longitude values per runway, and I'm not sure how they were calculated. I'm asking this because I want to add two more airports into the system. I managed to reverse engineer the math and got pretty close, but my glideslope is off a bit.