I just had a quick look, and there are many improvements. First of all, there is no need to just put the variable as its expression. For example, you have a variable called BB, and then you put BB as the expression. All this does is set BB it itself, so you can delete these variables. Next, I suggest using descriptive (for example FMCLKeypadInput for the keypad on my left flight management computer) variable names, so you and others (mainly others) can better understand how the code works. For the keypad itself, I suggest changing the InteractionType to Once, using the same variable name, with a different outputValue for each button. This is how all my button groups work. Since you have ABC and DEF for example instead of one button for each letter, it will be more complicated (I can help with that if you want), but for mine, I have a variable setter that first checks if the input is not 0, and then does a different action based on the value. I store letters as numbers, so pressing the A key would be 13, B would be 14, and so on. My FMC has a lot more complicated code, but the basic idea is to have a value for each possible character. Since you have three characters per button, I would recommend having a system to loop through each value, with something like a 2 second timeout for looping (example, have a variable called LoopTime that is Time + 2), and then check if Time > LoopTime to end the loop and type the next character.
I understand a lot of what I've said is just brushing the surface of what code to actually write, but if you're interested I can provide more information.
@XM803ENJOYER46 He's actually still here, kinda. It's been a few years but he does keep coming back. I think he's also upvoted some of my posts more recently.
@XM803ENJOYER46 10 years ago, the only way to build such a plane was to manually xml edit the position and shape of every single part. There was no fine tuner, no nudging, no connection editor, and not even precise fuselage values.
@hpgbproductions @Yish42 The button should also have a setter to 0, and an interactionType of Once or Continuous. Please note rate(x) in this case will be 100 or -100 for one single update.
I'm sure you're inactive now, but AltitudeAgl doesn't work with this map; it reads as if I am hovering above the ocean even though I'm landed on the airport. Are you able to fix this?
Update: The airport seems to be fine, but the terrain still doesn't work with Agl.
@vSoldierT Simplify equations as much as possible and avoid excessive trigonometric functions. On my EICAS and ND display, I used a script to generate arcs/circles out of dashes (no sin and cos in the label), but for a moving display like this one there is no way to remove most of them. On my modified version of the 1 part PFD (the 3rd version), I found several repeated calculations and was able to simplify them, but I still needed a lot of the sin and cos calculations (and others), since they had unique parameters. I also believe the more moving (dynamic) characters, the higher the lag. So there is no significant optimization possible, which is one of the main factors for me developing modded screens which have almost no performance impact yet even higher detail and realism.
@Aerovations It could use some refining, but it actually isn't too far off. I do think the SP2 tutorial plane (if there is one) would use SP2 parts and have more details than this one though.
@Mrcooldude @Aerovations I contacted SupremeDorian, it's a known issue with the server cache (happens at random intervals) and I think he's working on fixing it.
@Ren @X99STRIKER probably not too many since all time isn't visible unless you change the url.
Although I'm here again so I guess people still visit it
@dekanii Yeah I found that with my own label screens (the PFD is a heavily modified version of the 1 Part PFD Version 3) have a huge performance impact, while the modded screens I made (which have absurdly more details compared to the labels) have almost no impact. Although, this is vanilla which does give it an advantage, especially for mobile players.
Great job! I'm going to stick with my own heavily modified version for my plane (plus I'm focusing more on modded screens now), but this is very cool and I can see a lot of work went into it.
Would you be interested in testing my SWL-120 Parts mod? I get some warnings about PC-only stuff when I build it so I would be interested to see if it works on OSX.
@X99STRIKER I used my browser's built-in translate and it's, as expected, 2 pages of AI essay about a "valuable and supportive community to spark inspiration"
My files are different since I have other stuff like FT codes, diagrams, reference pictures, scripts, and other stuff still related to SimplePlanes. My entire "SimplePlanes" folder (not the AppData one; one in my own storage) is just under 10GB, the SWL-120 Unity project is abut 25GB, and I have about 1200 total xml files archived. I only have like 7 files in my actual AircraftDesigns folder, all of them being SWL-120 related.
@Sense2 The flight model is just... realistic. There is the right amount of thrust to weight, and a realistic drag. It's not realistic by real life terms since there's one hidden inlet with drag and the entire plane is just 30k pounds, but it feels realistic and I'll take it.
This advanced autopilot has autonavigation through a series of waypoints, VNAV (reach a target altitude at a target waypoint), and full autoland with automatically deploying spoilers. This video demonstrates a simple flight from Wright to Yeager, although up to 25 waypoints may be entered into the flight plan, with almost every mod plugin supported in the ILS, ND, and FMC.
Cool. I just used trigonometry to calculate the angle of depression for my VNAV system.
I also recently made a full autoland system for my SWL-120. This thing is insane.
@dots about the discord server rule, I run a server (the modding community, one of the last ones on the server list), and the only moderators are me (owner) and the former owner/founder DuckMint (also owner, and inactive). So you don't need a moderation team if you as the owner are capable of managing any issues.
@XM803ENJOYER46 Sorry, forgot about your message.
On this plane, there is no electrical system past the electrics being "on". I can't remember exactly what I did, but I think the starters are actually always on here. On my SWL-120, which does have simulated everything, the APU dial is only in the start position when the APU is starting, so I use that as my electrical load detector. The engines use pressurized air to start, and have a similar method, with the engine dial adding load when it is in the start position. I have a variable setter that sets it to 1 (run) after engine start is complete; same for the APU.
I am making the most detailed and realistic airliner in the history of the site, a project that has been in progress for 4 years (I mean 4 years of actual work too)
I just had a quick look, and there are many improvements. First of all, there is no need to just put the variable as its expression. For example, you have a variable called BB, and then you put BB as the expression. All this does is set BB it itself, so you can delete these variables. Next, I suggest using descriptive (for example FMCLKeypadInput for the keypad on my left flight management computer) variable names, so you and others (mainly others) can better understand how the code works. For the keypad itself, I suggest changing the InteractionType to Once, using the same variable name, with a different outputValue for each button. This is how all my button groups work. Since you have ABC and DEF for example instead of one button for each letter, it will be more complicated (I can help with that if you want), but for mine, I have a variable setter that first checks if the input is not 0, and then does a different action based on the value. I store letters as numbers, so pressing the A key would be 13, B would be 14, and so on. My FMC has a lot more complicated code, but the basic idea is to have a value for each possible character. Since you have three characters per button, I would recommend having a system to loop through each value, with something like a 2 second timeout for looping (example, have a variable called LoopTime that is Time + 2), and then check if Time > LoopTime to end the loop and type the next character.
I understand a lot of what I've said is just brushing the surface of what code to actually write, but if you're interested I can provide more information.
The best part about these comments is my comment from ONE HOUR AGO already has four upvotes.
+3@XM803ENJOYER46 He's actually still here, kinda. It's been a few years but he does keep coming back. I think he's also upvoted some of my posts more recently.
+2@XM803ENJOYER46 I was 7
+2@XM803ENJOYER46 10 years ago, the only way to build such a plane was to manually xml edit the position and shape of every single part. There was no fine tuner, no nudging, no connection editor, and not even precise fuselage values.
+4I have every single mod in the game, over 400 files.
+1@Yish42 Add a variable setter with the same name as the button and put 0 as the expression.
+1@hpgbproductions @Yish42 The button should also have a setter to 0, and an interactionType of Once or Continuous. Please note rate(x) in this case will be 100 or -100 for one single update.
+2I just code my own autopilot, which allows for deeper integration with advanced navigation systems.
When you need a train but can only use roads
+1I'm sure you're inactive now, but AltitudeAgl doesn't work with this map; it reads as if I am hovering above the ocean even though I'm landed on the airport. Are you able to fix this?
Update: The airport seems to be fine, but the terrain still doesn't work with Agl.
@TheMouse yes
@vSoldierT Simplify equations as much as possible and avoid excessive trigonometric functions. On my EICAS and ND display, I used a script to generate arcs/circles out of dashes (no sin and cos in the label), but for a moving display like this one there is no way to remove most of them. On my modified version of the 1 part PFD (the 3rd version), I found several repeated calculations and was able to simplify them, but I still needed a lot of the sin and cos calculations (and others), since they had unique parameters. I also believe the more moving (dynamic) characters, the higher the lag. So there is no significant optimization possible, which is one of the main factors for me developing modded screens which have almost no performance impact yet even higher detail and realism.
+3@Aerovations Same issue.
+1@AWESOMENESS360 I think you were confusing whereby and Bobbygomes21 6.3 years ago.
@Aerovations It could use some refining, but it actually isn't too far off. I do think the SP2 tutorial plane (if there is one) would use SP2 parts and have more details than this one though.
@Mrcooldude @Aerovations I contacted SupremeDorian, it's a known issue with the server cache (happens at random intervals) and I think he's working on fixing it.
+1@Wingsoffirefanatic @SemedianIndustries this may actually be similar to (if not better than) the SWL-10, but then there's the SWL-120.
+1@AndrewGarrison fair enough, thanks for the explanation
@AndrewGarrison Did you update something about the users all time page too? I just noticed a limit at Page 25. Going past doesn't work at all.
@Ren @X99STRIKER probably not too many since all time isn't visible unless you change the url.
+3Although I'm here again so I guess people still visit it
@dekanii Yeah I found that with my own label screens (the PFD is a heavily modified version of the 1 Part PFD Version 3) have a huge performance impact, while the modded screens I made (which have absurdly more details compared to the labels) have almost no impact. Although, this is vanilla which does give it an advantage, especially for mobile players.
+2Great job! I'm going to stick with my own heavily modified version for my plane (plus I'm focusing more on modded screens now), but this is very cool and I can see a lot of work went into it.
+1Would you be interested in testing my SWL-120 Parts mod? I get some warnings about PC-only stuff when I build it so I would be interested to see if it works on OSX.
+1@Sense2
clamp01(clamp01(IAS < 40 & OnGround = 1) = 0) * abs(clamp01(smooth(GearInput * 10, GearHydraulics) - 9))@Randomplayer The translation being thai checks out then.
So we have a NSFW bot. Great. I've seen worse somehow.
@X99STRIKER I used my browser's built-in translate and it's, as expected, 2 pages of AI essay about a "valuable and supportive community to spark inspiration"
@X99STRIKER I tried translating it and translate had a stroke lol.
My files are different since I have other stuff like FT codes, diagrams, reference pictures, scripts, and other stuff still related to SimplePlanes. My entire "SimplePlanes" folder (not the AppData one; one in my own storage) is just under 10GB, the SWL-120 Unity project is abut 25GB, and I have about 1200 total xml files archived. I only have like 7 files in my actual AircraftDesigns folder, all of them being SWL-120 related.
@X99STRIKER fiwfan is probably whatever scam service the bot is promoting.
@TheMouse He's back!
This is Sultan Island from The Items
@MetallicBeef6572 If you mean your own posts than I would say it's fine.
+1@MetallicBeef6572 What do you mean by comments?
If those people clearly requested to be tagged then it is generally okay, but just tagging a bunch of random people is not okay.
+1@XM803ENJOYER46 I am also that guy, thanks for noticing that.
+2@Sense2 The flight model is just... realistic. There is the right amount of thrust to weight, and a realistic drag. It's not realistic by real life terms since there's one hidden inlet with drag and the entire plane is just 30k pounds, but it feels realistic and I'll take it.
+1@Sense2 It already does.
+1This advanced autopilot has autonavigation through a series of waypoints, VNAV (reach a target altitude at a target waypoint), and full autoland with automatically deploying spoilers. This video demonstrates a simple flight from Wright to Yeager, although up to 25 waypoints may be entered into the flight plan, with almost every mod plugin supported in the ILS, ND, and FMC.
@HazerzIsBack yep. Still going. I think I'll finish it this year, and I'm actually making good progress. I only have 4 months left though
+1Interesting, although my waypoint/ILS system is too far completed to add this. Maybe for my next plane though (SP2)
Cool. I just used trigonometry to calculate the angle of depression for my VNAV system.
+1I also recently made a full autoland system for my SWL-120. This thing is insane.
I make SimplePlanes content but I only upload a few times a year and it's a lot of SWL-120 stuff.
+1@dots about the discord server rule, I run a server (the modding community, one of the last ones on the server list), and the only moderators are me (owner) and the former owner/founder DuckMint (also owner, and inactive). So you don't need a moderation team if you as the owner are capable of managing any issues.
+2@Kikikokikomarumaru15000 Thanks, it has been added.
+1I've always been here. While I may seem somewhat inactive, I check the website many times a day.
+1@Kenzo316actual Please read the FAQ on one of my recent progress updates
@XM803ENJOYER46 Sorry, forgot about your message.
On this plane, there is no electrical system past the electrics being "on". I can't remember exactly what I did, but I think the starters are actually always on here. On my SWL-120, which does have simulated everything, the APU dial is only in the start position when the APU is starting, so I use that as my electrical load detector. The engines use pressurized air to start, and have a similar method, with the engine dial adding load when it is in the start position. I have a variable setter that sets it to 1 (run) after engine start is complete; same for the APU.
I am making the most detailed and realistic airliner in the history of the site, a project that has been in progress for 4 years (I mean 4 years of actual work too)
@YokaiBear unfortunately no; mobile mods have been unsupported for many years