Nice plane! I could have done a better job with the cockpit (don't ask, It's pushing SP beyond its limits), but the other details are superb! The cockpit itself is also quite nice, it's an impressive level of detail.
@Korzalerke I too am working on an advanced network of code which will allow for mods to be added to the game package and be used on all platforms, even my smart calculator.
I am the god of the variables system.
My SWL-10 and upcoming SWL-120 both have/will have flight simulator realism.
I have made several variables tutorial videos. To use switches and buttons to effectively be extra AGs, this video explains that. You said the input didn't turn off. I have seen this issue a lot, and it is because you forgot to set the interactionType, which I mention in this video. For your purposes it should be set to Toggle.
Another note, about booleans. If you want to get a boolean out of a "custom AG", you can use this code in the input of the part in question: customInput = 1
Replace customInput with the name of the custom input of the button/switch you have.
I have also made a lot of other tutorials. Just look at my page from the videos perspective to see them all.
@CarrotSlicingCompanyCat How on earth did that get 9,700 downloads?
My SWL-10 got twice the upvotes, but just 4000 downloads.
In other news, this car was a waste of effort. It even had a video teaser.
Amazing plane, however the camera for the pilot should have auto center off. I couldn't interact with switches in the middle console before I turned it off. This can easily be addressed with an xml update.
.
(EDIT: I found the second camera for look around. Not sure why there isn't just one, but hey, it's your plane)
@iamTexas Yeah, that is a problem. There is a fix, just click on the parking brake, which is labelled in the diagrams, and is just to the left or right of the throttles. It's a red handle.
@TheMaus Correct. The only thing which comes close to a kit is I used a website called PCPartPicker to pick the parts I wanted. It found the best prices in different stores, and it ensured all the parts were compatible with each other.
Good plane, and I have some positive and constructive feedback.
.
Pros
.
Pretty detailed, I like how you put a semi-realistic checklist in the craft instructions. I checklist and instructions is key for someone who has never flown this plane before. Overall build quality is medium (high is like having 5000 parts for stuff like rivets, every single function of the real thing included), and looks nice.
.
Recommendations
.
I would recommend moving the checklist to a physical one, so as not to clog up the craft instructions. So have craft instructions list the action controls, and then have what to do with those controls be in a physical checklist.
.
Another thing I noticed is the prop blades. I did my preflight, lined up, flaps were down, and I went to take off... except I went backwards. VTOL controls flaps and prop pitch with no activation groups.
.
I ended up doing a no flaps takeoff, and the flight handling is what one would expect from a plane like this. It rolls a little sensitively, but most planes on SP have this problem.
.
Overall, good job, with a few recommendations.
The same issue occurs for all parts with sliders for me. No idea how to stop this and I didn't submit a bug report because I don't know what causes the issue.
@Falkenwut I know... Imagine if I finally completed my Python code that output the right code base on the heading and threshold coordinates, and then Jundroo released a new update called "Navigation".
New and improved guide:
1. Spend 10 minutes enjoying how easy the new update makes building cockpits.
2. Install some of the new gauges, levers, buttons, and dials, slap on a 10 part custom throttle (Airliners)
3. Enjoy your low-part count and detailed aircraft.
@windshifter1 that is not currently planned, but not impossible. Currently the closest thing to walking around is the galley cart, which already has issues like no collisions and no ability to climb ladders (there is no way to properly appreciate the detail of the avionics bay and crew rest areas). I'm currently focused on cockpit screens (teaser), but I do plan to finish off the interior after that, which may include extra interactivity.
SWL-120 Log:
Hours spent sitting at Wright testing cockpit stuff: 999
Hours spent in cruise testing autopilot: 999999
Hours spent testing variables in the debug console and not the plane: 9999999999
Hours spent flying actual aircraft: 0.1
@HuskyDynamics01 That's actually a pretty good idea! Instead of messing with all kinds of stuff on my wings after mirroring, I can simply... build them at the same time.
Same for engine fan blades for example; I can build one and instantly have another 23, all editable as well.
While the thumbnails were first taken in SP, they were modified too much, such that the original build's materials and "SP-ness" was not clearly identifiable. While light image enhancements are fine (for example reshade, adding text or small icons, and backgrounds), the thumbnails were too grainy and were not clearly identifiable as an SP build. I'm not a moderator; I'm just offering my opinion on why they were removed.
@RB107 It also depends on what I'm doing (especially since I spend almost all my free time on stuff related to my plane (and also because of how my plane is, a lot of my time is spent in other software like Blender, Unity, and Notepad++)). For example, when I'm doing something mindless like building a bunch of details I'll put on a podcast, and when I need to focus on 3 monitors of FMC code I'll put on some light music at low volume
Spooky coincidence, but my boot SSD went poof this morning as well. Luckily 99% of my data is backed up, but I lost 1 month worth of work on the SWL-120's mod. It's nothing critical, although it's a setback. I also am down to one laptop while I wait to get a new SSD as well.
@Boeing727200F I just understand how everything is connected. For example, if I wanted to move the turret of a tank, I would find the rotator it is connected to and nudge that, which moves everything else. In fact I don't even drag and drop stuff (aside from fuselages for alignment). I nudge everything into place and manually add connections.
@Graingy Funky trees is a programming language based around mathematics. Functions such as clamp(x, y, z) do things to and with numbers, and they can be stacked. Knowledge of algebra is essential for properly understanding the structure of code written in this language.
The code I wrote should alternate between 0 and 1 rapidly. The core of this is the pingpong(x, y) function. This alternates a value so it is never larger than y and never less than 0. For example, say I had pingpong(Throttle * 3, 1). From 0% to 33% throttle, it would be the same, however from 33% to 66% throttle it would go back down to 0. from 66% to 100% it would go back up.
The sum(x) function is the sum of all inputs over time (idk how to properly explain this). With a static number in there it will constantly go up. I put 5 so it goes faster than 1. This gets placed inside the pingpong function so it now alternates between 0 and 1 rapidly. The only problem is this is pretty much always greater than 0, activating the light.
The clamp function allows us to clamp values. For example, clamp(3, 1, 2) will output 2 because 2 is the maximum value. clamp(0.5, 1, 2) will output 1 because 1 is the minimum value. clamp01(x) is the same as clamp(x, 0, 1), and exists because it is used pretty often. Before we clamp anything, I then put our pingpong code in a boolean comparison, checking if it is greater than 0.5. This could actually work without clamping it since booleans get converted to -1 and 1 for math purposes, however I like to have clean 0 and 1 values, so I clamp01 it.
So there you go, all of clamp01(pingpong(sum(5), 1) > 0.5) broken down. Hope it helps!
For your information, anything above 0 in the input field of a beacon light will activate the light. As you want to control the blink pattern in more than one way, you will need additional FT instead of a simple blink pattern. TargetLocked ? 1 : (TargetLocking ? clamp01(pingpong(sum(5), 1) > 0.5) : 0)
Not sure if that will work or not, give it a try.
I guess I'm one of the old players, although the reason I don't seem that active is because I don't go looking for forums or airplanes that much. I don't even download much at all, unless requested to test something. If I stumble across a forum asking for help, I might make an effort, and if I'm asked outright then I'll make an effort to provide some help.
So to sum up, even though I check the site very frequently, I often just open it to check for notifications and then close it. Sometimes, like now, I browse someone's comments for no reason in particular and end up on something I want to comment on (for example this).
@LunarEclipseSP I also have plans to make a full (well, aside from externally modelled parts) no mods version of the entire plane. It will be unplayable and I may not even be able to do it, but when mobile users beg for a no mods version, I can link them the 30,000 part Yamato killer lol.
(I also have a cargo no mods version with some adaptations for vanilla, and it should be 5000-6000 parts in total)
The only thing that gives it away are the windows
+3Australia go brrrrr (6PM)
+3Welcome back to SP!
+3The ratio of points to followers is not the same. I have 200 yet have 5x the points.
+3Nice plane! I could have done a better job with the cockpit (don't ask, It's pushing SP beyond its limits), but the other details are superb! The cockpit itself is also quite nice, it's an impressive level of detail.
+3Nice work! Ignoring the problems with the plane itself (wheel colors, the fact the wheels aren't the new ones), the autothrust code is amazing!
+3@Korzalerke I too am working on an advanced network of code which will allow for mods to be added to the game package and be used on all platforms, even my smart calculator.
+3@Korzalerke Yeah, I wonder how many other people secretly work for Jundroo.
+3I am the god of the variables system.
+3My SWL-10 and upcoming SWL-120 both have/will have flight simulator realism.
I have made several variables tutorial videos. To use switches and buttons to effectively be extra AGs, this video explains that. You said the input didn't turn off. I have seen this issue a lot, and it is because you forgot to set the interactionType, which I mention in this video. For your purposes it should be set to Toggle.
Another note, about booleans. If you want to get a boolean out of a "custom AG", you can use this code in the input of the part in question:
customInput = 1Replace customInput with the name of the custom input of the button/switch you have.
I have also made a lot of other tutorials. Just look at my page from the videos perspective to see them all.
@CarrotSlicingCompanyCat How on earth did that get 9,700 downloads?
+3My SWL-10 got twice the upvotes, but just 4000 downloads.
In other news, this car was a waste of effort. It even had a video teaser.
Check out this map
+3If you're searching for the first time, I'd use something like one of these builds, and then save a location.
How does a 10 minute meme build get more upvotes in a week than my variables system work of art got in 2 months?
+3MrShenanigans. His B17 nearly bricked my $3500 PC with an 11900K i9.
+3@Rsouissi I'm not working on it right now and it is very specific to the aircraft.
+3I can't get the DX11 tab to show up.
+3Amazing plane, however the camera for the pilot should have auto center off. I couldn't interact with switches in the middle console before I turned it off. This can easily be addressed with an xml update.
+3.
(EDIT: I found the second camera for look around. Not sure why there isn't just one, but hey, it's your plane)
Random question - I did the math, and from the upvotes on your posts as of now, you should have 10810 points? Did you delete some old planes?
+3Now this will truly test my RTX 3060's capabilities.
+3@iamTexas Yeah, that is a problem. There is a fix, just click on the parking brake, which is labelled in the diagrams, and is just to the left or right of the throttles. It's a red handle.
+3Me: Creates a complex plane, and explains it in depth in the description
+3Some random person: hOW dO I flY THiS PLanE
You are at some point going to surpass me. I officially declare war to get to platinum.
+3@TheMaus Correct. The only thing which comes close to a kit is I used a website called PCPartPicker to pick the parts I wanted. It found the best prices in different stores, and it ensured all the parts were compatible with each other.
+3Thank god my new planes have autopilot, just set that to 5000ft @ 0 degrees @ 300 knots and note how long the plane flies for
+3FBI OPEN UP
+3yo I just built a pc with an 11900k should be enough
+3Good plane, and I have some positive and constructive feedback.
+3.
Pros
.
Pretty detailed, I like how you put a semi-realistic checklist in the craft instructions. I checklist and instructions is key for someone who has never flown this plane before. Overall build quality is medium (high is like having 5000 parts for stuff like rivets, every single function of the real thing included), and looks nice.
.
Recommendations
.
I would recommend moving the checklist to a physical one, so as not to clog up the craft instructions. So have craft instructions list the action controls, and then have what to do with those controls be in a physical checklist.
.
Another thing I noticed is the prop blades. I did my preflight, lined up, flaps were down, and I went to take off... except I went backwards. VTOL controls flaps and prop pitch with no activation groups.
.
I ended up doing a no flaps takeoff, and the flight handling is what one would expect from a plane like this. It rolls a little sensitively, but most planes on SP have this problem.
.
Overall, good job, with a few recommendations.
The same issue occurs for all parts with sliders for me. No idea how to stop this and I didn't submit a bug report because I don't know what causes the issue.
+3@Falkenwut I know... Imagine if I finally completed my Python code that output the right code base on the heading and threshold coordinates, and then Jundroo released a new update called "Navigation".
+3New and improved guide:
+31. Spend 10 minutes enjoying how easy the new update makes building cockpits.
2. Install some of the new gauges, levers, buttons, and dials, slap on a 10 part custom throttle (Airliners)
3. Enjoy your low-part count and detailed aircraft.
Very fun to use! I got 'victory'!
+3The 20,000 part Yamato, mobile edition lol
+3@windshifter1 that is not currently planned, but not impossible. Currently the closest thing to walking around is the galley cart, which already has issues like no collisions and no ability to climb ladders (there is no way to properly appreciate the detail of the avionics bay and crew rest areas). I'm currently focused on cockpit screens (teaser), but I do plan to finish off the interior after that, which may include extra interactivity.
+2SWL-120 Log:
+2Hours spent sitting at Wright testing cockpit stuff: 999
Hours spent in cruise testing autopilot: 999999
Hours spent testing variables in the debug console and not the plane: 9999999999
Hours spent flying actual aircraft: 0.1
@HuskyDynamics01 That's actually a pretty good idea! Instead of messing with all kinds of stuff on my wings after mirroring, I can simply... build them at the same time.
+2Same for engine fan blades for example; I can build one and instantly have another 23, all editable as well.
While the thumbnails were first taken in SP, they were modified too much, such that the original build's materials and "SP-ness" was not clearly identifiable. While light image enhancements are fine (for example reshade, adding text or small icons, and backgrounds), the thumbnails were too grainy and were not clearly identifiable as an SP build.
+2I'm not a moderator; I'm just offering my opinion on why they were removed.
@32 yeah they are supportive of me (as long as schoolwork gets done lol)
+2@IFVuser 2500.
+2Per engine.
And that will increase when I remake the engines again in the next few months.
@IFVuser That's without engines too
+2@RB107 It also depends on what I'm doing (especially since I spend almost all my free time on stuff related to my plane (and also because of how my plane is, a lot of my time is spent in other software like Blender, Unity, and Notepad++)). For example, when I'm doing something mindless like building a bunch of details I'll put on a podcast, and when I need to focus on 3 monitors of FMC code I'll put on some light music at low volume
+2@lalalalalion Thanks!
+2alright time to see how the NASA PC capable of running the SWL-120 handles this
+2Spooky coincidence, but my boot SSD went poof this morning as well. Luckily 99% of my data is backed up, but I lost 1 month worth of work on the SWL-120's mod. It's nothing critical, although it's a setback. I also am down to one laptop while I wait to get a new SSD as well.
+2Comment 1
+2Comment 2
This should provide some more information.
TLDR website performance reasons, although if you know what to do you can still do it.
@Boeing727200F I just understand how everything is connected. For example, if I wanted to move the turret of a tank, I would find the rotator it is connected to and nudge that, which moves everything else. In fact I don't even drag and drop stuff (aside from fuselages for alignment). I nudge everything into place and manually add connections.
+2I just do everything through connections and the "move connected parts" option in the nudge tool.
+2@Graingy Funky trees is a programming language based around mathematics. Functions such as clamp(x, y, z) do things to and with numbers, and they can be stacked. Knowledge of algebra is essential for properly understanding the structure of code written in this language.
+2The code I wrote should alternate between 0 and 1 rapidly. The core of this is the
pingpong(x, y)function. This alternates a value so it is never larger than y and never less than 0. For example, say I hadpingpong(Throttle * 3, 1). From 0% to 33% throttle, it would be the same, however from 33% to 66% throttle it would go back down to 0. from 66% to 100% it would go back up.The
sum(x)function is the sum of all inputs over time (idk how to properly explain this). With a static number in there it will constantly go up. I put 5 so it goes faster than 1. This gets placed inside the pingpong function so it now alternates between 0 and 1 rapidly. The only problem is this is pretty much always greater than 0, activating the light.The clamp function allows us to clamp values. For example,
clamp(3, 1, 2)will output 2 because 2 is the maximum value.clamp(0.5, 1, 2)will output 1 because 1 is the minimum value.clamp01(x)is the same asclamp(x, 0, 1), and exists because it is used pretty often. Before we clamp anything, I then put our pingpong code in a boolean comparison, checking if it is greater than 0.5. This could actually work without clamping it since booleans get converted to -1 and 1 for math purposes, however I like to have clean 0 and 1 values, so I clamp01 it.So there you go, all of
clamp01(pingpong(sum(5), 1) > 0.5)broken down. Hope it helps!For your information, anything above 0 in the input field of a beacon light will activate the light. As you want to control the blink pattern in more than one way, you will need additional FT instead of a simple blink pattern.
+2TargetLocked ? 1 : (TargetLocking ? clamp01(pingpong(sum(5), 1) > 0.5) : 0)Not sure if that will work or not, give it a try.
@SkyJayTheFirst Hi, I'd appreciate it if you didn't tag me just because I upvoted a teaser. Thanks!
+2I guess I'm one of the old players, although the reason I don't seem that active is because I don't go looking for forums or airplanes that much. I don't even download much at all, unless requested to test something. If I stumble across a forum asking for help, I might make an effort, and if I'm asked outright then I'll make an effort to provide some help.
+2So to sum up, even though I check the site very frequently, I often just open it to check for notifications and then close it. Sometimes, like now, I browse someone's comments for no reason in particular and end up on something I want to comment on (for example this).
@LunarEclipseSP I also have plans to make a full (well, aside from externally modelled parts) no mods version of the entire plane. It will be unplayable and I may not even be able to do it, but when mobile users beg for a no mods version, I can link them the 30,000 part Yamato killer lol.
+2(I also have a cargo no mods version with some adaptations for vanilla, and it should be 5000-6000 parts in total)