Profile image

ATTENTION GET! A few minor suggestions

5,080 KingHandspider  2.5 years ago

These are a few of my unfilled needs I've come across while designing an early jet-age airliner cockpit (hehe)

More options for switches and buttons

Specifically:
- The 'interactionType' field is only accessible through XML/Overload at the moment. It's not a huge challenge, just a minor inconvenience.
- Similarly, the Input for switches and buttons can only be set to a custom variable through XML/Overload. Again, not horrible, just inconvenient.
- On the topic of switches, I would love to have three-way switches for things like position lights (strobes/steady). I imagine these would be controlled by clicking through their states, e.g. OFF --> I --> II --> OFF or something similar.
- I'd also like to see the emission level of labels (both the individual part and the labels on switches and buttons) controllable by an input, for things like warning lights or especially cockpit illumination at night.
- In a similar vein, having buttons light up independent of them being pressed.

Custom Gauge Faces

This one will be harder to implement, but custom gauge faces would be vurry nice.

K n o b

At the moment, I can sort of fashion knobs out of round buttons and gauges, and have the "position" advance every time the button is pressed, but it would be nice to have a dedicated part for this. Amen.

Bitchin' Betty. Maybe... Hecklin' HellFire? Whinin' WNP?

In my pursuit of cockpit-design, I've realized that my options for audible warnings and other guff are very limited. I'd like to see bloops, beeps, bwaap-bwaaps, and other shtuff. Amen.

If would like me to addendum this post, leave a comment with your own suggestion!

  • Log in to leave a comment
  • Profile image
    4,165 Formula350

    I have way too many of my own suggestions I'm compiling (after 15 minutes of having the update installed....) to have you try and shoehorn into your post! lol That, and I need line-breaks and more than the 4000char limit that comments afford me :}
    .

    Ka-nobs

    For "Knobs" I use a Magnet, scaled way down (via XML of course). A size of 0.05,0.2,0.05 is about perfect, using the "Simple Throttle" as a reference.
    .
    Now comes the probably tricky part, since I have yet to really dive in to stuff, as I've mentioned: Getting it to do what you need a knob-interface to do, using the limitations of SP...
    .
    Depending on what that new "Joystick Base" dohicky can do and how we can interact with it... My first thought is to slap the Knob on one of those (scaled way down to match), and use it's output to base other stuff's capabilities on.
    IF that wouldn't work, my next suggestion would be to use a simple Rotator, tying those same "stuff" to the Rotator's position. So if it's currently rotated to 5deg of its 90deg max, then whatever its Input value fort that would trigger one function (although, probably best to set it as a range so it doesn't need to be precisely at 5deg). Then next, 10deg, same thing, triggers next function. Rinse, repeat.


    Now, if none of that would work, then we'd have to go FULL KLUDGE and is probably similar to what you already did, but is sort of combining everything together.... :}
    What comes to mind for me is to have:
    -Either the "Joystick Base" or a "Rotator"... probably will need both, though?
    -That Magnet Knob connected to that
    -A button (scaled to be a thin line), at a 45deg angle maybe, positioned on the right-most side, colored bright
    -Another button (similarly scaled) rotated opposite, positioned on the right-most side, colored a contrasting color (or the same *shrug)
    -2 "Text" parts, each with a *V
    (letter vee), rotated around and positioned next to the bottom end of the button, to make an "Arrow"; one pointing one way, the other the opposite way
    .
    When you interact with one button it turns the "knob" one direction via stepping the Rotator X-amount each press, hopefully creating an input (or output I guess?) with that Joystick Base, which in turn triggers whatever you need it to based on the specific output value.
    <con't...>

    Pinned 2.5 years ago
  • Profile image
    4,165 Formula350

    Gauge Faces

    Even if only having it so you can color the face, that'd work, too.
    Granted, in most professional (ie a governing body oversee with standards), I'm sure black face with white text is mandatory for gauges....
    However, more private/civilian stuff, and even things like non-transportation related gauges, there are different colors. Mostly white, but with aftermarket vehicle gauges for older cars, you can get all manner of colors for the faces.
    .
    So I'd suggest a case of having a preset list of color ranges that if the Face gets colored to it, the Text is forced to be something else. Bright Red face = Bright White text. White face = Black text. Navy Blue face = Bright Gray text, etc etc.
    Or, simpler and lest labor intensive (to determine which colors get which text): Just make the text color become the literal inversed color of the face! SP already is capable of this with Glass, when you set the transparency to -100. Black glass becomes white, Red becomes Blue, and so on.
    ($10 says I've reached the post character limit... lmao)
    (EDIT: Yep! Reposting to solve that...)

    Pinned 2.5 years ago
  • Profile image
    9,318 Tookan

    @45678
    by using the Schwartz!

    +1 2.5 years ago
  • Profile image

    @45678 Yeah I guess your right (Thank you for getting my reference lol)

    +1 2.5 years ago
  • Profile image
    1,137 45678

    @BlackhattAircraft

    we probably just need to clear the jam off the radar dish.

    +4 2.5 years ago
  • Profile image

    Bruh just do vertical text curvature make it actually useful on aircraft that aren’t boxes

    +4 2.5 years ago
  • Profile image

    three way switches is def something I hope gets added

    +3 2.5 years ago
  • Profile image

    yeah we need the bleeps, the sweeps, and the creeps!

    +4 2.5 years ago