Jump to content

Viper1970

Members
  • Posts

    2057
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS, Prepar 3D, Strike Fighters Project 2, First Eagles, IL-2 Series, ARMA 2 & 3, Dangerous Waters, Steel Beasts Pro PE and a lot of Retro Simulations like the whole old Janes Series (Longbow Anthology, F-15, F/A-18, USAF Fighters, IAF Fighters, Fleet Command...) Novalogics Commanche Gold, F-22, F-16, MIG-29 or JSF, MIG-Alley and so on, I'm still enjoing to play sometimes :-)
  • Location
    Bavaria/Germany
  • Interests
    Military Simulations (really huge collection - nearly everything since 1988), RC-Models, Music

Recent Profile Visitors

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

  1. The first prototype of the new Aircraft MPD, which I will use instead of the Masterpilots. It is based on Apache MPD, but has a bit more buttons to be usable for other airframes, too. I don't want to make an exact replica here, cause it should be universal useable also for further modules in DCS or any other flightsim that supports such complex inputs. The dimension is the same as the MFD frame of the Masterpilot (which is already a whole lot bigger as the Cougar MFD's). The original Apache MPD is much bigger, but my panels are not that big and I also wanted to have space for some backup instruments in the panel, which should also be displayed with the TFT. Some details are still missing and will be implemented later, like the bars between the buttons.
  2. It looks like this could work, but the problem I had in my tests was that the device forces the PC/Laptop to use it's resolution if connected. Means if your tablet has an 1024x600 resolution your PC will also switch to this resolution. No problem if you are running a separate computer for the displays and connect the Android device to it, using a network from this computer to the sim-computer (like it's possible with BMS for example), but a problem if the simulation should also run the same machine you use spacedesk with. But maybe I didn't go deep enough into it cause I gave up trying pretty quickly, because my tablet at the time was also too slow. @No1sonuk Have you made further experiments with it? Would be great if you could inform us about the result. I'm also very interested in this for future projects. -------------------------------------------------------------------------------------------------------------------------------------------------------- I have now dropped the idea of using my Masterpilots, cause they are to big for the helo-panel and there is no more room left for other instruments. I will do extra printed MFD-frames and use the same square-buttons for it, I also used for the jet-panels UFC and for some buttons in the right console. This way I could also integrate the functions in the corner of the MFD's and altogether will be connected to a Pokeys card. I have 15 Pokeys cards, two are used for the command unit, so 13 are left. The pit itself uses 8 cards, three in each side console and two in the overhead. The jet-panel also needs two cards, so this makes 10 together and leaves me three cards for the use with anything else. I will use another two for the helo-panel and can then use the last remaining for a future project (maybe the Apache TEDAC ). There is no need to use as many cards as I use, if you go the matrix way, but I want to have the things as simple as possible and only use matrix functions if there is no other way. Every box should have it's own Pokeys card to keep the wiring easy. This way it's also always possible to add some extra functions, if needed, at a later time. Maybe with a plug at the box, at which you could connect an extra external device. And I got 10 of those Pokeys for low as a complete set on ebay, some years ago, so I had only to buy 5 new.
  3. The idea behind my new home-cockpit is on the one hand to give a realistic feeling of the airplanes that have always fascinated me and on the other hand to remain as universal as possible to be able to operate almost any aircraft. It is even possible to use the "cockpit" again as a race rig, which it actually is. The panel can be removed in a few simple steps, the steering wheel mount can be folded up, the rudders can be replaced by a car-pedal set and even an H-shifter with handbrake lever can be attached at the place of the sidestick. So to speak (in German) its the "eierlegende Wollmilchsau" (egg-laying wool milk sow). The whole thing is not easy to build and of course can never be as perfect as a real replica of a single airframe, but for me the immersion and especially the right handling of the controls is important in the first place. Of course you don't need a pit when you fly in VR, but I also want to have the possibility to fly relaxed in front of the screen and use my pit there. I could not decide for a single kind of aircraft or helicopter, nor between VR or cockpit, so at the end that concept came out.
  4. The Jet Panel is ready now. It's not perfect, but ok. Better than a simple button box . I used a lot of the F-15E layout at the UFC, cause this can also be used for other airframes. Some parts of the F-16 ICP are also used. I had to take care of the TFT (the transparent box beyond the panel), so that no parts of the switches or buttons go out of the back of the panels' plate. That's also the reason I placed the switches on the sides of the panel relatively far at the outside. This is the only section where I can place inputs that are very expansive in depth. The wires will go through the frames on top of the panel-plate and those of the outside inputs will be placed at the back of the panel. All wires will be routed into the UFC box, the outside ones behind the sun-shield (still missing), where two Pokeys cards and the USB-hub are mounted inside. Maybe I have to canabilize the hub and only use the electronics, without the case to get all fitted inside this box. P.S: The rocker switches at the UFC are only place holders. There will be momentary 3way used instead of those simple on/off rockers. I still have to make all the holes also, but I want to do this as the last part. Maybe some further things at the layout must be changed again and this way it's much easier to do it.
  5. The jet and the helo panel as they are at the moment, so far. Now I will do the rest of the 3D models which than should be printed, like an universal usable UFC/IPC, frames for analog gauges and so on (maybe require some adjustments of the panel plates again). and a little later... Nothing finished yet Some things will move from the consoles to the panel and new things will be integrated to the consoles.
  6. I have it on my radar now, and maybe it will be a future addon for my pit, if it's finished (the pit ). At the moment I'm doing my front panels. Have made some simple 3D models of the Masterpilot and also the Cougar MFD (thanks to a guy at Thingiverse that made the F-16 MFD based on the Cougar MFD already), to have a better idea of the dimesions during planning. The base-plate of the panels are already cutted out of a piece of a cabinet back-wall. This material is relatively strong but very thin. You can easily cut out holes with a mini jigsaw or a decoupage saw. I aleady cutted out the holes for the MFD-displays. On this plate the MFD frames and some other 3D printed panel parts will be mounted. I will also add a small sunshade and the whole panel should be easy to remove with a hook-in device in front of my "panel-TFT", so that is simple to change between different panels. The USB devices on each panel will be connected to a central USB-hub, also mounted at the panel, and in the end only one USB- cable should be necessary to electronically connect the whole panel to the PC. That's at least the plan.
  7. Is there an option in Mobiflight to specify to which program (.exe) it should send the emulated keypresses? I once had a tool for FSX that also worked with other simulations (LinkToFS Arduino Keys), but only if you explicitly specified in the config to which program the keypresses should be sent. Even if you only wanted to test everything in Notepad, you had to specify the Notepad.exe. The Pokeys cards I use are different, they send out keypresses in general, just like a keyboard does, no program has to be in focus. Unfortunately I haven't done anything with Mobiflight for about 3-4 years, so I'm not up to date. But that will change soon, when I make my 4-Engine Throttle.
  8. @RealDCSpilot Wow, this FFB base is so amazing! I have also immediately read on here in the forum and have also immediately registered in the Discord channel. The part is just absolutely brilliantly implemented! The best base I have seen so far.
  9. The cockpit console layout. The next will be the front panel layouts for the jet and the helo panel. After this I will do the layout of the overhead. Between the angled front consoles and the back consoles there will be placed the throttle on the left and the sidestick on the right.
  10. I would be interested in this too, because I have some Arduino Megas lying around here that I wanted to use with Mobiflight for special inputs for the big birds like transport helicopter or aircraft in P3D. When I heard in the Mobiflight forum that you can also use simple keyboard emulation for virtually any program without depending on the FSUIPC, I was excited. I also immediately thought of DCS. My HOTAS are all based on TM elektronics and my cockpit is almost exclusively implemented with Pokey's cards, but some things like my 4 Engine Throttle Quadrant and other future things I wanted to implement with Arduino Mega cards, because I still have a lot of them left and thought this would be usable as a pure keyboard input emulation for DCS also. Actually, this should be possible if the keypresses are really purely simulated. DCS would definitely have to recognize this as well, since this is nothing different than input via a keyboard or eg. like TM TARGET or Joystick Gremlin also can do. The Pokeys cards also work without any problems in DCS, so the Mobiflight boards, should do the same.
  11. Yes they are really good! I'm very often listen to tracks of them at the moment! My dad was a drummer in a rock band back in the 60's and I started to play guitar but never really learned it. Now my son plays guitar and is really good at it. He is a great SRV fan (Stevie Ray Vaughan). I have infected him with my music virus Collecting music is another hobby besides flight simulation I have
  12. The Lenovo M7 is really good (Android 11 Go), but it's small. For me this was the reason I bought it, cause I want to have a tablet that exactly fits at one of my 18,5x18,5cm button box and leaves some space to integrate a few switches at the side of the tablet also. An 8'' tablet would have been to big for this. I was able to get one of the last at Amazon. At the Lenovo store they are already sold out and the newer tablets are all min. 8''. Fore sure 8'' would be nicer to work at, but it's really too big for my little consoles. The F-14D grip is ready printed. Here are some pics of the shells, as always only loose put together. I added the F-14B grip (modified - not ready Virpil VFX) as comparison.
×
×
  • Create New...