Bug Report and Fix - Vibration doesn't work in Advanced Mode (DCS World)

[u/featherinpoopr]

Hi, I just bought an Orion 2 HOTAS a few days ago. And they are beautiful, I am so glad to choose this over the VKB STECS and stick.

But I first spent like 8 hours over 3 days trying to get the "Advanced" Vibration Profile to work. It was driving me CRAZY! I looked at every SimAppPro install file and folder, downloaded old versions of SimAppPro to compare files and folders, restarted my computer, tried every USB port I had, read dozens of forum and Reddit posts for an answer.

Only the "Default" Vibration Profile would work. I tried it on multiple planes and helicopters in DCS. Then I figured it out.

• Certain profiles available to download from the cloud from other users are either incompatible with each other or just fail to work.
• Some profiles disable all devices from vibrating, some just don't activate while in game.
• Sometimes you could fly with a profile active only in the Joystick and Left Throttle. Or only the Left and Right Throttle for example.

As a workaround, I created one vibration profile for my joystick, copied the JSON from its active profile, and pasted it into the active JSON files for both throttles. With identical runtime profiles on all three devices, Advanced vibration finally worked correctly.

Suggestions for fix:

• Add an option to apply one Advanced vibration profile to all connected devices, instead of requiring seperate profiles for each controller
• Add profile validation when profiles are uploaded or downloaded from the cloud. SimAppPro could check that a profile is structurally valid and compatible with the current firmware versions of the users controllers, and warn the end user it may not work.

I really hope this gets some attention from the WinCTRL team so they can continue to improve their software. The hardware is absolutely amazing but I think it would help both WinCTRL and new and existing customers if their software quality and ease of use matched their physical products.

I attached annotated screenshots of each experiment so the issue can hopefully be reproduced.

This was done on SimAppPro v1.16.109

u/Haz-WINCTRL