The SWL-10 actually seems like a good entry for this due to the engine/wing/gear configuration (although it's disqualified due to being finished over 3 years ago)
@vSoldierT ah I see. My own label screens were absurdly laggy, enough that I spent a few months making modded screens to replace them (and I'm very pleased with the outcome). If you want I can take a look and offer some improvements.
@fleia262 Ah I see. I tried making a fuel system with six and later three tanks (I think I even made a video or two), but gave up for now since it never worked right. I think I'll just do a crossfeed system which will be easier to code and not take up too much time. To be perfectly honest, there are a lot of general design improvements I would make to the overhead panel if I had to redo it (stuff like a visual layout of all the systems, like power flow on the electrical panel), but those are major changes and I'm leaving that for a possible SP2 remake of my plane (separate from the SP2 port of the SP1 edition, and a multi year megaproject).
There's just something about other people's planes and cockpits where even if they have less features (for example, if you look at my overhead panel you can see a lot of systems, most being functional), the features they do have look and function better than mine.
Again, great job with the cockpit, and I would love to see you spend another three years of your life finishing the rest of the cockpit and plane (jk lol).
I saw your tag yesterday but didn't get time to test it until today, great work! I went for a simple flight from Wright to Yeager (not in VR).
One major recommendation I have is to add labelled diagrams of everything. I'm not sure how actual training manuals look for real planes (something I'll need to figure out when I get to making documentation for my plane), but I would assume they detail every single control and what it does. The user manual (which I only noticed after taking off, what a great preflight lookaround I did lol) is a good start to this.
Another recommendation, which would be a great addition to the user manual (or maybe in some sort of EFB where everything can be found) is tables of all important information, such as what the airport codes (WLA, KAX, etc) mean, minimum/maximum airspeeds, and anything else. I was able to guess what Yeager was by the 01L/R runways.
I also noticed the fuel transfer systems seems to have an error when I activate more than one transfer button, as all buttons say error (and some have "On" and "Error" overlapping). Do you know why this happens?
The overall design of everything is very good, and I especially like the engine instruments and "System Data Display". You also made the text have proper backlighting which works with a switch, something I don't remember seeing before. It would be cool if every single system with emissive paint also had this effect (note, this is why I avoided any dials in my plane, as they are hard to turn on and off).
There are a few other recommendations I have if you're interested, about construction methods, coding errors, and improvements to some code.
Overall, I am very impressed with this cockpit! Well done!
@RedeemedSPer I have been ş̴̢̧̢̡̛̛̥̜̜̦̠͖̹͇͙͖͚͔̘͇͉̼͉͕̱̲̱͉̼̹͚̯͎̮͔̳̫̭͕̱̙͖̠̼̹̼̮̞̦͍̝̳̙̣̫̬̹̩̹͍̼̙̱̲͔͓̘̣͕̪̝͉̩̉̽̂͐̒̇̎̒̊̑̉́̄͗̓̄̒͊̃̂͛͋̍̀̒̍̇̈́̉̂̉̎̈̈́̋̀͆̾̓̀́̈̿͋̓͑̈́̆̌̂̓̍͌̔̔͌̀̍̕̕̕̚̚͠͝͠ǘ̴̡̢̧̧̢̡͉̠̱͈̭̬͍͓͖̙͖͖̫̮̥̜̤̘̬͔̬̥̦͈̞̣̳̬̟̊̄̔̔͐̄̕͝ͅͅm̴̢̧̫̞͖͔̠͈͚̗̖̯̪̟͕̲̰͓̼͇͉͕̜̼̺̞̘̜̠̙͚̖̦͚̠͍̗̑͗̅͗͒͜͜͠ͅm̴̛̛̫̺̟̼̮̫͎̬̤͈̹̬͉̟͕͕͓̰̳̬̠̲͙͎̪̳͚̤͙͎̤̤̫̝̣̖̫̗̜͈͓͈̝̗͚̹̞̬̻̭͓͎̻̼̙̩̮̣̥̰̦̞̃̔̎̂̓͑̆͒̒̉͆̑̒̈́͊̐́͌̎̅͘͘̚͜͜͜͠͝ơ̴̡̡̨̢̨̡̨͖̪̩̱͇͇̼̮̩̩͕͎̹̮̙̲͙̞̦̥̤̝͎̝͕̱̰̘̗̞̲̫̻͇̯̰̫̗̣̻̲͖̘̮̣̙̖̯͎̻̮̹̹̭̟̗͖͍͔̫̳̺̫̣̱̩̟̎͂͒́́̉̑̓̍̔̆͛̅̀̍̋̀̑̍͛̓́̀̂̈͊̉̉̏͆̃̈́̆̑̓͛̍̌͒̕͘͝͝͝ͅͅn̸̨̛̛̺̬̣͙̰̬̻͎̠̝͗͛̒̎͊͑́̃̄̇̃̓͊̈̅͐̑̍͐̽͐́̐̎̿͗̈̽̓̐̐͐̆̆́͒͆̈͘̚̕̕͜͜͝͠͝͝ě̸̡̨̡̛̛̛̻̳̦̟̩͈̻̦̩̟̭̩̺̟̪̖͚̹̞̺̱̺̬͖̯̜̤̯̹̺̙̖͙̹̭̣̲͚̩̰̱̮̬͔̫͔̱̈́͛̃̽̌͆̽̈́̄͆̔̽͒̀͋̉̂̈̈́̋͗̔̑̿̃͐̌̓̇̂̿̔́̿͛͊̔͐̈́̾͆̌̒́̍̀͌̾́͂͂̊̉̄͋̿̍̔̔̊̚̚̕̚͝͠͝͝ͅd̶̨̢̧̨̢̤̱͎̯̬̬̭̳̫͚̯͔̣͍̙̫̬̝̰̬͔̠̗͔̹̮̮̦̙͖̙͕̻̬̜̩̬̮̦̞̤͔͔̣̦̪͇͙̼̪̻̿́͜ͅͅ
@FaLLin1 I hope so to; although I doubt they will have the same level of functionality as these do (especially the version I use in my SWL-120, which also has a very complicated and integrated waypoint display system with purple waypoint paths)
Hiding parts does not hide them from the connect part menu. For example, if I hide a fuselage that would normally obscure a part, then select a part, click add connection, and attempt to click on the obscured part, I actually select the hidden part despite it not being visible.
@Alvinwilson345 Please read.
Mobile mods have been unsupported for 6 years now, and while some users have found ways to make mobile mods, these mods cannot use scripts (which this heavily relies on), and are made using an older version of Unity and unsupported mod tools.
@Sense2 "And now that we've finished our interior, let's add a simple cockpit to finish off the build. I think 99% realism should be okay for this build since I'm just showing you the basics."
@Sense2 Thanks for your advice! I will actually consider some of your suggestions since I don't really know how some of them work, especially how the non-normal sounds interact with each other and when they play.
1. If you mean the overspeed, I agree. Even the brown noise, which goes for 10 minutes (looped), has a slight cut when it loops. I might just go into Audacity and extend the overspeed alarm to be 1 minute or longer.
2. I could update the low airspeed mp3 to have two calls, and then not loop it. Easy change.
3. I technically could fix this, but it would make the whole system even more complicated. I do have warnings in specific groups, and certain sounds take priority (for example, the speed warnings go from stall, to low speed, to overspeed). It's not perfect, but again it's a game about simple planes.
4. So you mean that in addition to the sound, there should be a text warning? Where specifically should it go on the EICAS? In the (not built yet) messages section, or a larger warning at the top?
5. I actually was aware of that sound existing, but never added it. I will now look into adding it. I know it means the glideslope is not in the center, but when exactly does the warning activate?
@Boeing727200F I have screws, which will be replaced with even more detailed screws when I eventually mod all the cockpit details (a no mods version will of course be available). Honestly, to go any further would require me to use textures and spend too much time working on this, far beyond the loop of "I'm better now, let's replace this 2 year old part". I would be perpetually working on the plane, remaking every part forever. This has been my most complicated project ever, and will likely remain the most complex aircraft I ever make for a long time. Anything I make in SP2 will be slightly simpler, especially in the general construction due to the new parts.
Speaking of wiring, I do have a fully simulated electrical system which you can view on the EICAS display (not in this build).
@AuroraBrooke It is for my own plane and has integration with its systems, but similar to my Cockpit Screens mod, I might make a public version with most of the sounds.
To enhance realism in the SWL-120's cockpit, I have added cockpit sounds. To do this, I made my own mod part, with many sounds and effects all included in one part. The following groups of sounds are included:
- GPWS Approach Callouts
- GPWS Gear/Flaps Warnings
- Speed Warnings
- Bank Angle
- GPWS Descending Warnings
- Autopilot Disconnect
- Brown Noise (at high airspeed or engine power)
- Pax Signs (not shown here, just normal fasten seatbelt chimes)
Each sound has realistic activation parameters based on similar real-life airplanes.
Update 3/09/2025, I have tweaked some sounds (see Sense2's comments below), and added a new glideslope warning sound.
@SilverStar Forgot to make a description, will do.
Yeah I think the pull ups are a little loud; they are two different sounds mashed together by me to make "Pull Up.mp3".
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.
Seeras is a curator.
The SWL-10 actually seems like a good entry for this due to the engine/wing/gear configuration (although it's disqualified due to being finished over 3 years ago)
@vSoldierT no problem
@vSoldierT ah I see. My own label screens were absurdly laggy, enough that I spent a few months making modded screens to replace them (and I'm very pleased with the outcome). If you want I can take a look and offer some improvements.
Will everything function exactly like the real thing? (barring classified military documents lol)
+1@fleia262 Ah I see. I tried making a fuel system with six and later three tanks (I think I even made a video or two), but gave up for now since it never worked right. I think I'll just do a crossfeed system which will be easier to code and not take up too much time. To be perfectly honest, there are a lot of general design improvements I would make to the overhead panel if I had to redo it (stuff like a visual layout of all the systems, like power flow on the electrical panel), but those are major changes and I'm leaving that for a possible SP2 remake of my plane (separate from the SP2 port of the SP1 edition, and a multi year megaproject).
+1There's just something about other people's planes and cockpits where even if they have less features (for example, if you look at my overhead panel you can see a lot of systems, most being functional), the features they do have look and function better than mine.
Again, great job with the cockpit, and I would love to see you spend another three years of your life finishing the rest of the cockpit and plane (jk lol).
@Bigolfishboy yes
+1I saw your tag yesterday but didn't get time to test it until today, great work! I went for a simple flight from Wright to Yeager (not in VR).
+1One major recommendation I have is to add labelled diagrams of everything. I'm not sure how actual training manuals look for real planes (something I'll need to figure out when I get to making documentation for my plane), but I would assume they detail every single control and what it does. The user manual (which I only noticed after taking off, what a great preflight lookaround I did lol) is a good start to this.
Another recommendation, which would be a great addition to the user manual (or maybe in some sort of EFB where everything can be found) is tables of all important information, such as what the airport codes (WLA, KAX, etc) mean, minimum/maximum airspeeds, and anything else. I was able to guess what Yeager was by the 01L/R runways.
I also noticed the fuel transfer systems seems to have an error when I activate more than one transfer button, as all buttons say error (and some have "On" and "Error" overlapping). Do you know why this happens?
The overall design of everything is very good, and I especially like the engine instruments and "System Data Display". You also made the text have proper backlighting which works with a switch, something I don't remember seeing before. It would be cool if every single system with emissive paint also had this effect (note, this is why I avoided any dials in my plane, as they are hard to turn on and off).
There are a few other recommendations I have if you're interested, about construction methods, coding errors, and improvements to some code.
Overall, I am very impressed with this cockpit! Well done!
imgbb.com
@Graingy Trying to submit a comment on the Corsair spits the entire page HTML in a browser alert window. Also weird.
+1@RedeemedSPer I have been ş̴̢̧̢̡̛̛̥̜̜̦̠͖̹͇͙͖͚͔̘͇͉̼͉͕̱̲̱͉̼̹͚̯͎̮͔̳̫̭͕̱̙͖̠̼̹̼̮̞̦͍̝̳̙̣̫̬̹̩̹͍̼̙̱̲͔͓̘̣͕̪̝͉̩̉̽̂͐̒̇̎̒̊̑̉́̄͗̓̄̒͊̃̂͛͋̍̀̒̍̇̈́̉̂̉̎̈̈́̋̀͆̾̓̀́̈̿͋̓͑̈́̆̌̂̓̍͌̔̔͌̀̍̕̕̕̚̚͠͝͠ǘ̴̡̢̧̧̢̡͉̠̱͈̭̬͍͓͖̙͖͖̫̮̥̜̤̘̬͔̬̥̦͈̞̣̳̬̟̊̄̔̔͐̄̕͝ͅͅm̴̢̧̫̞͖͔̠͈͚̗̖̯̪̟͕̲̰͓̼͇͉͕̜̼̺̞̘̜̠̙͚̖̦͚̠͍̗̑͗̅͗͒͜͜͠ͅm̴̛̛̫̺̟̼̮̫͎̬̤͈̹̬͉̟͕͕͓̰̳̬̠̲͙͎̪̳͚̤͙͎̤̤̫̝̣̖̫̗̜͈͓͈̝̗͚̹̞̬̻̭͓͎̻̼̙̩̮̣̥̰̦̞̃̔̎̂̓͑̆͒̒̉͆̑̒̈́͊̐́͌̎̅͘͘̚͜͜͜͠͝ơ̴̡̡̨̢̨̡̨͖̪̩̱͇͇̼̮̩̩͕͎̹̮̙̲͙̞̦̥̤̝͎̝͕̱̰̘̗̞̲̫̻͇̯̰̫̗̣̻̲͖̘̮̣̙̖̯͎̻̮̹̹̭̟̗͖͍͔̫̳̺̫̣̱̩̟̎͂͒́́̉̑̓̍̔̆͛̅̀̍̋̀̑̍͛̓́̀̂̈͊̉̉̏͆̃̈́̆̑̓͛̍̌͒̕͘͝͝͝ͅͅn̸̨̛̛̺̬̣͙̰̬̻͎̠̝͗͛̒̎͊͑́̃̄̇̃̓͊̈̅͐̑̍͐̽͐́̐̎̿͗̈̽̓̐̐͐̆̆́͒͆̈͘̚̕̕͜͜͝͠͝͝ě̸̡̨̡̛̛̛̻̳̦̟̩͈̻̦̩̟̭̩̺̟̪̖͚̹̞̺̱̺̬͖̯̜̤̯̹̺̙̖͙̹̭̣̲͚̩̰̱̮̬͔̫͔̱̈́͛̃̽̌͆̽̈́̄͆̔̽͒̀͋̉̂̈̈́̋͗̔̑̿̃͐̌̓̇̂̿̔́̿͛͊̔͐̈́̾͆̌̒́̍̀͌̾́͂͂̊̉̄͋̿̍̔̔̊̚̚̕̚͝͠͝͝ͅd̶̨̢̧̨̢̤̱͎̯̬̬̭̳̫͚̯͔̣͍̙̫̬̝̰̬͔̠̗͔̹̮̮̦̙͖̙͕̻̬̜̩̬̮̦̞̤͔͔̣̦̪͇͙̼̪̻̿́͜ͅͅ
+3@Boeing727200F Not quite lol.
That's an easy way to delay the release date a few years though
@Thbigmanscoop109 Either this Christmas or early next year
Hello everyone, I have been summoned
+4@todaytoneet @AirFalcon My link
No Mobile
Mobile mods with scripts have been unsupported for 6 years now.
@Chinedu Must I put the no mobile statement on every mod I make?
+2@FaLLin1 I hope so to; although I doubt they will have the same level of functionality as these do (especially the version I use in my SWL-120, which also has a very complicated and integrated waypoint display system with purple waypoint paths)
Hiding parts does not hide them from the connect part menu. For example, if I hide a fuselage that would normally obscure a part, then select a part, click add connection, and attempt to click on the obscured part, I actually select the hidden part despite it not being visible.
@YarisSedan here you go
@Graingy bruh I don't need that much realism lol
No Mobile
Mobile mods with scripts have been unsupported for 6 years now.
@Alvinwilson345 Please read.
+1Mobile mods have been unsupported for 6 years now, and while some users have found ways to make mobile mods, these mods cannot use scripts (which this heavily relies on), and are made using an older version of Unity and unsupported mod tools.
@MTindustries I guess this is my response now; Christmas 2025, earlier if I can finish all the stuff I have to work on
+1From the mod The Items
+2@Icey21 @IMCI Murphy Airport is what Yeager Airport used to be called, likely after Kevin Murphy, one of the developers.
+2@Sense2 Thanks, I have updated that. I'll add you to the credits list for providing recommendations on the cockpit sounds.
@Sense2 Alright, and does it loop or just play once/twice like low airspeed?
@Icey21 nevermind, it will have absolutely everything, including Cat III autoland
+1boy do I have news for you
+1@Sense2 "And now that we've finished our interior, let's add a simple cockpit to finish off the build. I think 99% realism should be okay for this build since I'm just showing you the basics."
@Sense2 Thanks for your advice! I will actually consider some of your suggestions since I don't really know how some of them work, especially how the non-normal sounds interact with each other and when they play.
1. If you mean the overspeed, I agree. Even the brown noise, which goes for 10 minutes (looped), has a slight cut when it loops. I might just go into Audacity and extend the overspeed alarm to be 1 minute or longer.
2. I could update the low airspeed mp3 to have two calls, and then not loop it. Easy change.
3. I technically could fix this, but it would make the whole system even more complicated. I do have warnings in specific groups, and certain sounds take priority (for example, the speed warnings go from stall, to low speed, to overspeed). It's not perfect, but again it's a game about simple planes.
4. So you mean that in addition to the sound, there should be a text warning? Where specifically should it go on the EICAS? In the (not built yet) messages section, or a larger warning at the top?
5. I actually was aware of that sound existing, but never added it. I will now look into adding it. I know it means the glideslope is not in the center, but when exactly does the warning activate?
@Boeing727200F I have screws, which will be replaced with even more detailed screws when I eventually mod all the cockpit details (a no mods version will of course be available). Honestly, to go any further would require me to use textures and spend too much time working on this, far beyond the loop of "I'm better now, let's replace this 2 year old part". I would be perpetually working on the plane, remaking every part forever. This has been my most complicated project ever, and will likely remain the most complex aircraft I ever make for a long time. Anything I make in SP2 will be slightly simpler, especially in the general construction due to the new parts.
+2Speaking of wiring, I do have a fully simulated electrical system which you can view on the EICAS display (not in this build).
@Planemaster88 at least the SWL-120 is still in development, to be released hopefully this year.
@Prytton I don't really know, sorry.
@GorillaGuerrilla If you can figure out how to add it sure
@AuroraBrooke It is for my own plane and has integration with its systems, but similar to my Cockpit Screens mod, I might make a public version with most of the sounds.
@XM803ENJOYER46 all good then, no problem
Overclocked i9-11900k, 32GB ram, and RTX 4070ti
@SilverStar I've heard them and... umm... just go listen to them when he posts them
@CaptainNoble I have a description now
To enhance realism in the SWL-120's cockpit, I have added cockpit sounds. To do this, I made my own mod part, with many sounds and effects all included in one part. The following groups of sounds are included:
- GPWS Approach Callouts
- GPWS Gear/Flaps Warnings
- Speed Warnings
- Bank Angle
- GPWS Descending Warnings
- Autopilot Disconnect
- Brown Noise (at high airspeed or engine power)
- Pax Signs (not shown here, just normal fasten seatbelt chimes)
Each sound has realistic activation parameters based on similar real-life airplanes.
Update 3/09/2025, I have tweaked some sounds (see Sense2's comments below), and added a new glideslope warning sound.
@SilverStar Forgot to make a description, will do.
+1Yeah I think the pull ups are a little loud; they are two different sounds mashed together by me to make "Pull Up.mp3".
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