Phil Smith
Donator
BTW, it's MFD, not MDF. MFD is Multi Function Display. MDF is wood
damn right:lol: i've corrected em all:lol:
Home cockpit for Orbiter
- Thread starter Phil Smith
- Start date
damn right:lol: i've corrected em all:lol:
Phil Smith
Donator
so cant get enough time to start building the mock up. :-( but anyway i think about how much mfds i need. i guess 4 of them will be fine. (2 for transX, one for surface and one for orbit)
Last edited:
yagni01
Addon Developer
Keep us posted.
Phil Smith
Donator
10-4:thumbup:
DanielStratton
New member
- Joined
- Nov 28, 2011
- Messages
- 1
- Reaction score
- 0
- Points
- 0
I am looking again at starting one of these. Now that the hardware required has become significantly cheaper.
Ive been out of the game for a while, so I am hopeing i could get some recomendations for specs for a dedicated Orbiter computer which i will build first with one (or three) monitors. Then work on the pit as i go.
Being a dedicated computer im guessing i can get away without specing it too much, so what i wanna know is, whats some good comfortable specs for running 2010 Edition?
Ive been out of the game for a while, so I am hopeing i could get some recomendations for specs for a dedicated Orbiter computer which i will build first with one (or three) monitors. Then work on the pit as i go.
Being a dedicated computer im guessing i can get away without specing it too much, so what i wanna know is, whats some good comfortable specs for running 2010 Edition?
I guess i'll chime in here, since I want to make a simpit too.
Although I have a slightly different mindset. I have yet to find a good resource for making a cockpit to your liking (correct me if I'm wrong here). And generating the input has always linked to modding a consumer grade joystick or the outdated Mjoy.
So what I would like to do is design an interface for "your" cockpit to connect to "any" flight sim using new and improved technology!. Someone already talked about an Arduino, which is my plan exactly (If you don't know what it is, and you are mildly interested in electronics, its the best $30 I've ever spent). The new Arduino can emulate virtually any HID device [Keyboard, Mouse, Joystick, etc.] along with inter-process communication [Arduino <-> Orbiter]. The interface is also modular, so you can fly Orbiter one day, and the next fly MFS (with appropriate changes, but same interface).
I have some scribbled down notes. So far its a 5 phase project, with phase I & II being the core of the cockpit and being applicable to any sim (basically just keyboard and joystick emulation). III & IV are program and / or ship specific (Orbiter; Ravenstar or DG, DCS Black Shark, X Plane, ...). Then V is just extra aesthetics. At the end, I would release the code, basic plans and how-to's. At that point, it just becomes a question of hardware.
That's the game plan. I still need to refine how I want to approach this, and I still need to dive into the orbiter API and get my hands dirty. But it seems feasible (but I may be way in over my head).
Although I have a slightly different mindset. I have yet to find a good resource for making a cockpit to your liking (correct me if I'm wrong here). And generating the input has always linked to modding a consumer grade joystick or the outdated Mjoy.
So what I would like to do is design an interface for "your" cockpit to connect to "any" flight sim using new and improved technology!. Someone already talked about an Arduino, which is my plan exactly (If you don't know what it is, and you are mildly interested in electronics, its the best $30 I've ever spent). The new Arduino can emulate virtually any HID device [Keyboard, Mouse, Joystick, etc.] along with inter-process communication [Arduino <-> Orbiter]. The interface is also modular, so you can fly Orbiter one day, and the next fly MFS (with appropriate changes, but same interface).
I have some scribbled down notes. So far its a 5 phase project, with phase I & II being the core of the cockpit and being applicable to any sim (basically just keyboard and joystick emulation). III & IV are program and / or ship specific (Orbiter; Ravenstar or DG, DCS Black Shark, X Plane, ...). Then V is just extra aesthetics. At the end, I would release the code, basic plans and how-to's. At that point, it just becomes a question of hardware.
That's the game plan. I still need to refine how I want to approach this, and I still need to dive into the orbiter API and get my hands dirty. But it seems feasible (but I may be way in over my head).
ao7g
Alien of the 7th...
Donamy
Addon Developer
Is that Jerry Springer ?
Similar threads
