Enabler

The Due has 2 ports. One for programming and another native. Indeed, they both recognize as different ports when plugged in. I did get a simple sketch with 1 button and one encoder to work as a hybrid through a Micro (only one comm connection). I will use the Due program technique to make a hybrid through the native port and see how it goes. I expect that should work.

Good catch. After fixing that, my HID buttons are recognized and functioning as bound, but the encoders are not being read.

This is awesome. But I am running into one problem. I think there is a conflict in DCS. Attached is my combined code. It is my switch code for my seat controls, EHSI and Fuel Qty Sel. It works perfectly as USB-HID before adding the DCS-BIOS snipets. After adding DCS-BIOS to it, it compiles fine. I test the buttons with Windows USB Game Controller setup. The buttons all work perfectly. The board is connected and ready for DCS to run. I load DCS, and from the main screen go to controls, and bind the push buttons. No problem. they show as expected as Joy1, Joy2, etc. At this point all indications are that I expect this to work. I go to instant action, F-16, ready on the ramp. Test the buttons. Nothing. Turn the encoders, nothing. I return to the desktop, reopen Game Controllers, and all the buttons still show but will no longer activate. Any ideas? Did you experience that at all? Or does your combined code only work with LEDs? This is running on a Due.

If I continue to have this issue with generating a viable USB-HID code, then that would be a decent interim solution. I use this board to run my EHSI buttons, encoders, Ejection controls and Fuel Qty Sel panels. They all worked great with a Mega and DCS-BIOS. All the buttons work great as USB-HID on a Due board, but I just can't get the encoders to replicate their proper function as does DCS-BIOS. Do you think I can combine the Joystick (not Serial) and DCS-BIOS libraries (Serial) in one sketch (Arduino Due) so I can run all buttons/switches as USB-HID and the encoder functions as DCS-BIOS? My latest pit update is here and I'm due for another soon. GD ViperWorks - YouTube

Make this change to your void loop section. Between the correct number of switch positions mentioned above and this debouncing code, it should fix your problems. void loop() { delay(10); }

I have been converting my Viper pit over from DCS-BIOS inputs to USB-HID. This allows me to bind all inputs as a "joystick" button or axis. The advantage over Bios is the ability to bind the switches in DCS directly for all aircraft rather than one specific one. Reprograming my Viper EHSI, I'm having a problem coding for the 2 rotary encoders. I have tried numerous different codes specific to encoders but have not had any luck. While the DCS-BIOS code works perfectly, I am still planning to convert to USB-HID with the Joystick library. The code I have had some success with is simple and the encoders turn the course and heading bugs. However, they require many rotations for few changes in game. The questions I need answers to are: (I am using Arduino Due, but code for Micro and Leonardo are the same.) 1. Can I add code to this to simply change the rotation ratios of the encoder pins? 2. Is there a way to extract the actual code for Course and Heading from within the DCS-BIOS library to enter this manually? (Not referring to the code snippets.) 2. Do I need more specific code for the encoder to function? 3. Can someone help me with the code I need to add? This sketch includes other buttons in the array for various nearby panels and switches. The pins for the encoders A+B are 55/66 and 58/54. Thanks for your help! HID_Ejection_EHSI_Fuel_Qty_Sel_Due_0x14_Ver2.ino

I have the same issue with 4 external viewports. 2 MFDs, RWR and EHSI. The images paint and update, but the old images never disappear. Creating the kaleidoscope we are all experiencing.

The Viper Maverick training mission crashes each time you hit the SA-13.

It looks like something that was accidentally deleted during the update and hopefully this post will be read by the devs and added back in on their end. Other viewports (MFDs for example) still contain their export data so I will assume it was an error during the RWR update just released.

Here is the problem and the solution. I found it after hours of snooping and I know little to nothing about coding. It turns out my gut feeling was correct. I learned how to find the viewport export codes. Then I compared the old file from my desktop (wasn't updated yet) to the new file in my pit which was updated. There was indeed a piece of code missing in the file "RWR_ALR56_init.lua" file. The following is missing, and when added back, the viewport works once again. dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F_16C_RWR", "RWR")

Since the new OB update, my RWR is no longer being exported to my custom built RWR screen. The attached photo shows it functioning the day before the update. Now, it is just dark afterward. All the screen configurations are correct. I suspect that with the upgrade to the RWR in the sim, the name of the viewport may have changed and is no longer "F_16C_RWR". Is this the case? If so is there are new name for the viewport? Thanks.

I export viewports and data to instruments. I mostly fly the Viper and use it for that. While I don't export through helios to activate switches (only display) there are many of the instrument bindings within the Viper profiles that do not work yet. You can tell where it says "TODO" in small letters beneath the data you are binding to the instrument or switch. My Viper can export the RWR and DED, but won't update data to the Stby ADI or Fuel Flow because of this very reason.

I ran a repair and that still did not fix the problem. I imported my save profiles. they show in the program folders. They can be seen "load profile" in client. But they do not activate. When hovering over the controller title, the active profile shows. It never shows the profile I loaded. Nor can I re-save to my preferred profile.

Tobii software is lacking compared to TrackIR. It has only one curve for sensitivity and speed. It needs one for each axis. I need it to slow down in the vertical axis when looking into the cockpit and speed up when looking outside.

I purchased several new aircraft after the beta update of Dec 23. When mapping my controllers, I was unable to save these profiles with a specific name (Viggen Stick, Viggen Throttle, etc). Nor could I locate them in the profiles in client, nor through windows folders. My Viper profiles, which are my most refined profiles, are also missing. Yet the settings I had are still functioning. However, I also cannot save the profiles under new names. Another related settings and profiles issue is when I try to adjust an axis. I can use the sliders on the page but the graph does not show any of the control inputs. Is this just me? Is this a new bug with the new beta? Is there a fix?

Even though TrackIR software was closed, the problem persisted. But what made Tobii work was to physically unplug the TrackIR. Now to work on the settings. Regarding the OP, it would be great with the Apache, except for one issue I am experiencing with its functionality. The software works best with eye gaze off. With both head and eye tracking, I find the image to be unstable. Especially when looking close and into the cockpit. It's difficult to activate switches when the image dances a little. Also, the Viper HMCS is not tracking true. With eye track off, I turn my head to look behind but my HMCS lags behind, requiring me to turn my eye back toward it. This can make Apache use awkward. Another issue with the Viper HMCS is mark points. I place the reticle on the target, ground stabilize it (TMS fwd short) and the mark is about 120 degrees from where I set it. I need to manually slew it to the proper spot before I save it. Overall, I'm liking the hardware. The settings software is a little lacking though. It took me a while to get my TrackIR to function as I desired, I imagine in time this will work itself out too.

Yes I've also disabled TrackIR to make sure there is no conflict.

I can't even get mine to work at all. Tobii Experience sees my eyes and tracks. But I can't get it to work in DCS. I run the Beta from a simpit. The sensor is about 5 feet from my head.

Since the latest beta update of 2.7.7.14727 I experience a random flashing black screen. It occurs for varying lengths of time up to a second or two. It often flashes several times within 20 seconds. It makes the game unplayable. It occurs on the main menu as well as in flight. I have already reinstalled my video driver with a clean install. It worked for 1 day. My card is a Nvidia 3080 Ti.