dwpenney

Can you add me to the list as well?

Yeah I would love to see the STL to get an idea how you broke that model up into individual pieces to print and assemble. Very nice job!

My understanding from previous posts in the thread is that he is using ABS with and acetone vapour cleaning. I need to get an enclosure for my Ender 3 before I can get to ABS printing :-)

I may have it 'fixed'. I was using a powered USB hub but going direct to the motherboard has it working! Woo!

If it helps, here is what I have: And what I am seeing in the VKB Button Tester: And in DCS (not the Alt was as I was alt-tabbing to get the screenshot):

I think I understand. I named my device MBB_V01 and that column shows up in the DCS device list. I select that and try to map something and it does not respond. I am not sure of any way to trouble shoot this.

May be a stupid question but I thought I would ask here (instead of beating my head against my desk :-) ). I have my hardware all constructed and set up with MMJoy. Firmware loaded, config loaded and everything works in the Windwso and VKB Button Test Utilities. However, when I go into DCS ... it 'sees' the MMJOY device but does not seem to accept any button presses from it. I can manually map a button (ex: selected Master Caution in the F-18C, went to the MMJOY column, selected assign and selected button 4 from the drop down) but in game nothing from the MMJoy device responds. Is there some magic sauce I need to use? EDIT: It is a Teensy 2.0 USB device.

Same here :-)

Did you try removing the shaders (and when you restart DCS, it rebuilds them)? Try removing the following folders in your Saved Games folder: c:\Users\<your_user_name>\Saved Games\DCS\fxo c:\Users\<your_user_name>\Saved Games\DCS\metashaders2 And the next time you start, DCS will rebuild them. Looking through your log, I see that the EDCORE is dumping a stack trace that mentions AmsDxGsaFreeCompiledShader. Everything else looks 'ok'.

This is a pretty awesome project. I have been considering a switch box of my own and this thread has given me lots of ideas! How are you doing the electronics. I see that all of the boxes are connected by a 'bus'. Is that encoded somehow? In my box I was (am) considering shift registers to handle all of the buttons but yours has waaay more than what I have at the moment (30 buttons). Curious about how you are collecting all that data electronically. Plus, would love to eventually see the STL files in the future, however you want to make them available.

Could I offer a suggestion? Maybe a comms entry in the Carrier Info menu section for a Comms check. LSO could respond "5 by 5" or something. To make sure that the sound files are loaded. I'd like to find a way around having to add all those triggers by having some other script load them all at mission start.

Love it! Thanks!

These work for me: https://www.amazon.ca/gp/product/B0085I4D5C The link shows as unavailable (and I would not recommend this seller as the FedEX charges on receiving the package in Canada were excessive. There were caps thrown in with the devices, however, so that was nice.

Great to have you there! :-)

A little shameless plug for the Mudspike DCS Fall Fly-In that concluded late Sunday night. Not sure if RAZBAM knows about the site but there were a lot of people interested in flying and fighting the AV-8B in DCS 1.5.8. I was surprised at just how hungry people were to fly the Harrier! Sure, there were a few bugs but overall I can not remember anyone being unable to take part. We had a lot of people join and help each other out over the weekend, patiently learning the systems, the flight dynamics and how to implement the Harrier as the pointy end of the stick. Well done RAZBAM! Some great screenshots of the AV-8B over here: https://forums.mudspike.com/t/3rd-dcs-fly-in-screens-aars-thread/5179 I apologize if this seems like a self-serving thread but I wanted RAZBAM to know that their AV-8B was the star of the weekend and I did not want to reproduce all of the screenshots over here.