Jself

Got the first set of prints done, test fit and painted. It turned out pretty good. All I have are the green square buttons right now, they will be replaced by red/yellow for final assembly.

I will definitely share the files if successful

Inspired by Brun's UFC, I thought I'd take a stab at designing the rest of the Hornet's front panel. I play DCS in VR so I'm not worried about any of the displays, I just want to get the buttons/switches/knobs in roughly the right spot. I just got my printer so this weekend has been spent testing techniques/fitments of various components. I haven't printed a single part for it yet. I had a buddy print me the UFC using Braun's design so no need to re-invent the wheel. I'm planing on using his design. Here is a link to that thread: https://forums.eagle.ru/showthread.php?t=218874 I've scaled up the NATOPS foldouts (I know they are not the best) and used my best guess for angles and depths in DCS VR. Ultimately that's what I want it to match. Here is what I have so far.. a little bit of design / cleanup and then weeks of printing I'm sure. It will use 3 TM Cougar MFDs Everything is designed to print on an Ender 3 (230x230). As of right now its 43 separate printed parts should be 50ish when completed.

I recently switched over to the open beta version and every time I switch grips and load a new profile into the base...all my bindings are gone for the modules I used that grip/profile on previously. I never had that problem in the stable version. Is this a known issue or do I have something weird going on? I'm using a T-50CM2 base and TM F-18, VFX and WarBRD grips.

Yes it is. There is about a 1/4 gap between two strips of sheet metal. I just use a bolt up from the bottom and then a wing nut on top. It probably has 2 to 2-1-2 ft of adjustment. My youngest daughter (9) can barley get them close enough ( she has to put a pillow behind her on the seat.). I’m about 5’9 and there is at least another foot of adjustment. You can see it in the 3rd pic. Works really well

Not sure about DCS-BIOS but I know the sketches that use the joystick.h library will only work on the pro micro or Leonardo.

I think the VKB is a more accurate replica of an actual F-14 stick. I could be mistaken, but I don't think the VKB grips are compatible with TM/Virpil bases, I think you will have to buy a VKB base as well to go that route.

It doesn't feel as good as the TM grip. Its mostly plastic. The second stage of the trigger has a weird feeling..there is very little travel to the actual button it so it kind of just feels like you hit the stop. I don't really "feel" the second trigger. The other buttons are not quite as nice as TM either. The brake axis is about the only thing that is better vs TM. It is really nice ofr immersion when flying the F-14.. The F-14 is the only module I use the VFX for. If I fly anything else I'll use the F-18 grip

Hey everyone, I'm just about finished with my VR Simpit and I thought I'd share some pics. I mainly fly the f-14 but wanted to have flexibility to adapt to other modules as well, so I didn't go for a 1:1 F-14 replica, but the layout was definitely influenced. Details: - Chair came out of an old charter bus. A buddy of mine welded up the frame and all the mounts. - Virpil T-50 CM2 base w Virpil 200mm extension and VFX grip center mounted. I also have a TM F-18 grip. - Virpil T-50 CM Throttle. - Left Button box is an Arduino Leonardo controller - 10 3-way toggles, 5 buttons, 1 large 3-way toggle (landing gear). 3 Rotary Axes and 1 slider Axis (still waiting on the fader knob) - Right panel is an Arduino Micro Pro - 10 LED Buttons, 6 3-way toggles, another large 3-way toggle (tail hook), and 4 rotary encoders. There is also a Virpil warbid base mounted inside (for F-16 side stick - TM Viper stick on pre order) - Ejection seat handle is a custom switch I made out of rope, nuts, bolts washers, a small electric box, and some wire. It wires into the left button box and is controlled by the Arduino Leonardo. - TM TPR Rudder Pedals (adjustable via track mounted to the chair) - Monitor is a Dell 24" touch screen - HP Reverb headset - PC specs - AMD Ryzen 7, 32GB RAM, Super 2070 VC Let me know what you think

Awesome... thank you, that worked great!!

I've built some custom button boxes and would like to get some additional axes added for the tomcat. I was able to get the wing sweep lever working with the help of the bindings request thread in the bugs sub forum. I tried to use the same logic for the volume panel but can't seem to get it to work. Here is whats in the clickable.lua for sidewinder volume for an example: -- Pilot TONE VOLUME panel elements["PNT_2039"] = default_axis(_("Sidewinder Volume"), devices.ICS, device_commands.RADIO_ICS_Vol_Sidewinder, cockpit_args.RADIO_ICS_Vol_Sidewinder, 0, 0.1, false, false) Here what I tried to add to the default.lua in the joystick folder : {action=device_commands.RADIO_ICS_Vol_Sidewinder, cockpit_device_id=devices.RADIO_ICS_Vol_Sidewinder, name=_('Sidewinder Volume')}, It adds it to the axis list and lets me assign it but once in the game it does not adjust the volume knob and I get an error message in the top right corner of the screen saying "Unhandled Proxy Command 3397 val=nil" when the knob reaches 100%. Any help would be much appreciated

I'm new to DCS in general and especially to modifying the .lua files. I've built some custom button boxes and would like to get some additional axes added. I was able to get the wing sweep lever working with the help of this thread. I tried to use the same logic for the volume panel but can't seem to get it to work. Here is whats in the clickable.lua for sidewinder volume for an example: -- Pilot TONE VOLUME panel elements["PNT_2039"] = default_axis(_("Sidewinder Volume"), devices.ICS, device_commands.RADIO_ICS_Vol_Sidewinder, cockpit_args.RADIO_ICS_Vol_Sidewinder, 0, 0.1, false, false) Here what I tried to add to the default.lua in the joystick folder : {action=device_commands.RADIO_ICS_Vol_Sidewinder, cockpit_device_id=devices.RADIO_ICS_Vol_Sidewinder, name=_('Sidewinder Volume')}, It adds it to the axis list and lets me assign it but once in the game it does not adjust the volume knob and I get an error message in the top right corner of the screen saying "Unhandled Proxy Command 3397 val=nil" when the knob reaches 100%. Any Ideas?

SOLD!

I accidentally ordered 2 dust covers when I ordered my Throttle. It will fit the T-50 and T-50CM throttle (not the newest CM2). I have one still in the unopened package I'd sell for $20 shipped to the lower 48 states. May or may not fit other brands/models. dimensions - base - 10" x 6 3/4" Height back - 7" Height front - 3" It is this one here:https://virpil-controls.eu/vpc-mt-50-throttle-dust-cover.html