Krewmember

Members
  • Content Count

    66
  • Joined

  • Last visited

Community Reputation

105 Excellent

About Krewmember

  • Rank
    Rocketeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Sadly their is no good way to run unity games on the raspberry pi because the raspberry pi is ARM based and not x86. Unity can only compile ARM applications for android. The emulator is using the kRPC C# library. The kRPC mod sends and receives data over TCP so it can work locally or over a network. You could probably use ethernet over USB as well. That's a good idea, but I do not have the time or money to invest in such a project right now
  2. Here is the link to the github repo for the external rasterpropmonitor program's unity project. https://github.com/Krewmember/External-MFD Just be aware at the time of this post it is not compete and is still missing a lot of screens and the main screen does not have unit scaling, so let's say you are at 5.2Km it will display 5200.0m instead of 5.2Km. I will be working to fix this when I have the time.
  3. Yes I will be sharing the code when It's in more of a useful state.
  4. I'm glad you like it. Here is a screen shot of the simulated space shuttle attitude director indicator or "ADI". It's still very much a work in progress.
  5. Finally some progress worth posting I have mostly been working on just software for the MFDs, but I did finally get the annunciator working. I made this program using Unity3D and the kRPC C# library. It's emulates the RasterPropMonitor mod as a external standalone program. I have also been working another program that simulates pre-glass cockpit space shuttle instruments. I will get some screen shots of that and post them here as soon as I can. I now need to make some frames for MFDs that have buttons in them so I can interface with the software The LED colors and warnings are laid out just like the space shuttles caution & warning matrix
  6. A RPM style multi-function display would look petty cool on that monitor. Sadly, it did not get any farther then the last image that I posted. I was coding it in python and could not find a 3d library that would meet the requirements to render the navball At the moment I'm experimenting with Unity 3d and the kRPC C# Library and got some pretty good results. As Unity 3d has a good UI system and is designed for 3d games and apps. I will see if I can get some gifs and images of the tests and post them here. If you are going to use a breadboard I personally would get a Teensy. With male headers you can use it like a DIP package IC. Refresh rate of what? I'm going to guess you mean monitor refresh rate. Yes, you will notice the difference between say a 60hz and 144hz monitor, with a higher refresh rate fast movements will be smoother and have less ghosting. But you have to make sure that your graphics card can support higher refresh rates and has the power to run a higher refresh rate monitor. Also 120hz and 144hz monitors are more expensive then 75hz or 60hz monitors. I think that in a simpit for kerbal monitor or projector resolution will make more of a difference. As for external monitors for things like a multi-function displays and instruments, you can not get data from kerbal fast enough for refresh rate to make a difference. It's up to you to decide.
  7. The Arduino Mega can be used as a HID device but you have to flash a new bootloader. The Teensy has native HID support. The Teensy is also much faster, the Mega runs at 16mhz vs the newest Teensy the 3.6 which runs at 180mhz. Also the microcontroller in the Mega is only 8-bit the Teensy's is 32-bit. The Teensy is what mechanical keyboard builders use. But the Mega has female headers. With the Teensy you have to purchase the headers separately and have solder them on. So the Mega out of the box is easier to use. on the flip side though you can soldered female headers or male headers so that you can plug the Teensy in to a breadboard. For the I/O side of things, the Teensy has 25 Analog Inputs and 2 Analog Outputs so the Teensy can output 12 bit audio The Mega has 16 analog inputs and 54 I/O pins total. The Teensy has 62 I/O Pins total but you can only use 42 on a breadboard. As for price. The Teensy 3.6 is $30, a genuine Arduino Mega 2560 r3 is $38. But you can get clones for around $20. Just some things to consider.
  8. I think he said it was a fade controller out of a old video effects board. I did a quick google search and found that it's called a "T-bar controller". You can buy them new on places like Digikey for ~$300 which is pretty expensive. It wouldn't be too difficult to make your own. Take a look at this one for example. It's just a long shaft potentiometer mounted to a bracket with a bushing for the potentiometer's axle, and finally the handle which is just a aluminum flat bar with a hole drilled and tapped for a screw or set screw, this allows the handle to rotate the axle. Edit: If you want it motorized, just connect a gear motor to the potentiometer's axle and have the motor's controller read the value of the potentiometer and you basically have a servo motor.
  9. I haven't posted here in awhile, do to other projects consuming my time. Here is the simpit in its current state. The only things I have done since my last update, is install the monitor on the pilots side. I also removed the arcade joystick as I still need to modify it to have a third axis. Most recently I have been working on the software for the MFDs. My goal is to emulate RasterPropMonitor as close as I can. This is what I have achieved is far, Still vary much a work in progress. I used Python, kRPC and Kivy. I'm still deciding on the best way to render the navball.
  10. Now I see, thank you for clarifying I guess it could be done, but at this point in the build all I can say Is maybe Heck, if I were to make it go vertical why not just make a full motion platform
  11. I'm not quite sure what you mean, can you explain?
  12. I'm glad I can give some inspiration back to all you awesome people
  13. The annunciator is still on hold do to a lack of parts, but I have been working on other things why I get more parts. I finished the translation controller panel Just need to modify the arcade joystick so I can push and pull for forward and backward translation I also started work on the main flight stick pedestals. For the flight sticks I'm using Logitech Attack 3's they are cheap to get and have no twist for yaw, which is good because I'm going to use a set of CH Products Pro Pedals for yaw control. I also closed off the pedal compartments.
  14. I'm not sure at the moment.