I've dropped off the board lately, life getting in the way and all that, but I have a couple of dreams I'm hoping to tinker with and wondering if someone can tell me how plausible they are.Go big or go home: The Engineering Station
I've got a couple of Teensy
boards on order for this, basically I'm thinking of building a custom control much like a lighting or audio desk with motorized sliders, so the engineer can adjust the energy and coolant levels using that. I assume I should
be able to utilize the built-in webserver to make this work? Basic points I've already thought about are:
- Could just buy a midi desk and start with that.
Yeah but why would I want to buy a midi desk when it won't be quite right, won't let me enjoy figuring out how to build it and won't cost as much as a custom build likel will by the time I'm done :P
- Motorized Sliders
Not really needed for Power but it seems to me I should have this for coolant so when you change one system and it redistributes across others this is mirrored on the board. Plus that's just cooler, right?
- That's a lot of sliders...
Yeah I probably would want to support the full possible 18 sliders to cover the 9 possible subsystems (if a ship has both Warp and Jump). I looked at using a MUX with one of the various arduino units but Teensy comes with 21 analog inputs if I recall correctly so that's plenty.
- I don't believe EE supports binding keys to the client
Pretty sure @daid
has mentioned this in the past. If that's correct then probably one of the simplest ways it could be achieved is out of the question.
- Pretty sure there's not currently support for setting these levels via script.
If I'm wrong about that, happy days!More of a Proof of Concept: The Helm Throttle
Probably a better thing to start with, thought I'd look at getting a throttle set up probably just a simple rotating potentiometer with a lever and handle attached, though something closer to the controller here
could be cool.
Alternatively could just use a throttle from a H.O.T.A.S. controller set, but this has similar challenges. I do like the idea of having a split throttle where "impulse" is controlled via one axis, then you bring it back to 0 to bring up the warp (which would nicely mirror the in-game behaviour).
Again the issue would seem to be that we don't bind keys to the controls, and there's not currently a way to use a script to say set thrust = X.
Any thoughts? Doomed to failure?