Pitufo

Hi i hope this is the right place to post this.. hoping the sound module author will see this. So i just setup my first transducer, I'm running steam DCS 2.5.6, Hp Reverb pro, voiceattack, and i have a program called soundswitch that hasn't caused me any problems so far. I have simshaker for aviators and i bought the sound module. I am running my transducer out of a usb "soundcard". The first time i started everything up sound module said there was an update available which I skipped because I was eager to test my setup. I'm hoping that wasn't a mistake as it hasn't offered to update since. When i first started Dcs ALL the sound was coming through the transducer. Setting headphone output to my reverb gave me beeps and bitching betty in my ears but that was it. I then stumbled across audio mirroring in steam VR and now i get game sounds in my headset along with rumbles through the transducer. But I'm not sure it's supposed to work like it's working. I thought simshaker sound module was supposed to identify aircraft module and play sounds for different events? So, id i understand correctly, I shouldn't be getting any output through transducer for say, title screen music. Also in the drop down menu I don't get any aircraft choices and i didn't see anything in the debug logging. Also I'm not noticing any specific rumbles for gear, flaps etc. Any help is much appreciated thanks.

Yeah, windows and dcs recognize them as separate boards with different long alpha numerical strings after them. Derek Spears says to not use a usb hub, which I am, and so far I'm finding that if i keep them plugged in to the same ports it all seems to work. I color coded the cables and ports. I wish i could change the display names of the boards to make it easier to program in dcs but I don't know how.

PLEASE HELP!!! Okay so I've got it all wired up and everything works.... until it doesn't. I've got 2 derek spears 64 button boards in the big panel and a 32 button board in each of the side panels. Thing is, after I program everything in DCS it scrambles everything the next time I load it up. This is extremely frustrating I've been working on this for like 3 months. I tried renaming the boards in regedit (not sure I should be messing with that, but I did it individually for the 4 boards, RIGHT MFD, LEFT MFD, SWITCH PANEL and UFC PANEL. When I plug everything in, DCS reads 2 (different letter-and-number code gibberish things) UFC PANELs and 2 RIGHT MFD panels. I have no idea what to do from here. Also as you can see I changed the idea of the latching white buttons for different DDI's and UFC functions because it was too hard to keep track of what was latched or not in VR. Now the white rocker switch serves as a modifier if I want to operate the lower AMPCD.

I'm just using derek spears boards so all i can change that i know of is the polling rate to 20 15 10 or 5.... Which doesn't help.

Hmm. And you didn't have to tweak the sensitivity at all?

Hi I'm also having a bit of a problem with push button rotaries... I'm using a Derek Speare board. The issue is that they seem a bit TOO sensitive. And also, seemingly randomly the opposite direction "click" will register. This DCS BIOS that was mentioned.. is that something additional i need to download? Also is there any fundamental difference to the encoders that come on a chip with 5 pins and the ones mentioned above in this thread? Thanks.

I just did the CCRP training mission and when I try and move the cursor around in the HUD with my ministick (X56) it goes all buggy and strobes/flickers between 2 different points. Seems to work all right with a button on a 4 way though

Yeah what he said +1

So I've got one 64 button derek speare board working and set up... It's basically everything on the left side. I have a 32 button board in the mail but then i realized i should have gotten another 64 so that's on order too. Im going to use the 32 board for another smaller separate MFD setup on the left. That'll free up the 2 spots on the left and right where the white latching buttons are. The idea is that i was going to set the white buttons up as modifiers (they're latching) for left right and down MFD and the UP one will let me use the surrounding buttons as a sort of UFC interface. With the top left blue being "1" the middle red "2" or North/Up etc and the top 3 rotary encoders push buttons being "clear" "0" and "ENT". The positioning of the red buttons is for tactile reference in VR. So far so good but I'm learning what a pain in the ass the different modules are for not having different options for input types.

That's great. I've got a question about the rotary encoders, the ones I'm using are kinda quirky. They have a push button and the shaft is 6mm... Sometimes they register the opposite direction click, and seem to be either too sensitive or not sensitive enough. I'm using a derek speare board. Any thoughts?

THANK YOU Ummm... Does it have to be Open Beta? I'm using Steam 2.5. Ahh I see there's a couple for the launch bar and the hook bypass... I was just about to post in the bugs cause I just got the first part of my box set up and was having a meltdown over those. That's a typo in the CPT_LIGTHS and THROTTLE_EXTERIOR_LIGTHS right? Should be LIGHTS? Or not? EDIT: THIS IS AWESOME. I don't suppose this could be the right place to ask about buggy rotary encoders? I've got a Derek Speare board with 2 more in the mail and I've setup some push button rotaries and configured them properly (I think) in the configuration utility... But they don't always want to register a click for a click and sometimes register the opposite input. Is this a problem with the rotaries or a software/OS problem I could configure?

Hey so is it possible to make other lines of code similar to that one for the speedbrake? Case in point: I'm building a button box and I thought there would be an abstraction for Master Arm ON else Off but no such luck. The Harrier has one. I would have rather only used one button input instead of now having to go and replace my On/Off switches with ON/ON or ON/OFF/ON switches.

Reverb disconnect/reconnect Hi not sure if this is the right thread to post in... So I got a new Reverb V2 the other day and it's great, amazing, holy S*&^! Except while playing DCS, and it seems only while playing DCS the headset will freeze, and then strobe and the sound will switch to my PC speakers. It lasts about 3-5 seconds. And it keeps randomly happening. I'm not convinced the HMD is defective though because it won't seem to do it in any other application that I've tried. Anyone got any thoughts on what could be causing this? Thanks in advance. Also, I followed that guide by Thud I think their name was. Super useful. So I do have the settings mentioned in there set in Nvidia control panel.

Why isn't there a CC\CCW binding for specifically the HSI selector? I don't want to use 7 different inputs on my button box or the keyboard or the mouse as I fly in VR. Thanks.

Hi anyone know how to get voice attack to start dcs right into VR mode? If I run the executable, or the RUN.BAT file I get a message on my screen saying that I'm trying to run it in native desktop or something. The idea is to not have to grab my controllers now that I've switched to WMR. With Oculus I just clicked the icon on my desktop but I haven't been able to figure out how to do that with WMR. Thanks.

Ya that's it LeCuvier. I was just frustrated with the X56 I think. And I didn't realize the F/A-18's speedbrake was designed for partial extension. Thanks for the mod. Is it an actual mod file or do I just need to insert that line of code and that's it? So while I'm at it and I suppose it's off topic, how come the Mirage doesn't have a left/right command for the HSI knob?

So I scrapped the X52 idea I kept frying one of the upper stick boards. I've decided to just build my own panel. I've got a 64 button board from Derek Speare in the mail. Here it is so far.

I was waiting on this... Bought it, refunded it... Now I've bought it... And.... NO Speedbrake abstraction that works with X56 Logitech Rhino. WTF. For the price and the hype about it I thought it must be a top notch, Problems solved module. As a beginner in this but experienced with other modules (M2000C has speedbrake abstaction). Why hasn't this been fixed/implemented? When other modules just do it....?

Haha new here don't look at the dates

What I meant was it would be cool if the dcs software would allow assigning different keystrokes for different positions of the rotaries. So say from 0 to 25% button 1, 25 to 50 button 2 etc

I don't see what the problem would be, just mapping two momentary inputs to either end of on-off-on switch. And the x52 has i think 4 axis plus the 2 stick axis but I don't think I'll use the stick axis. I'm more trying to figure out how to organize it all before hand. Like how many 3 pos switches, what to build it out of, how many on offs etc... EDIT: Umm... Anyone know where to find a wiring diagram for the X-52? I took it apart and it's a hot mess of spaghetti wires breaking off everywhere

Hi so I'm learning dcs in VR with a Logitech x56 (new version) and I'm getting a little frustrated with the lack of 3 position switches and not being able to easily use the switches under the throttle. So i was thinking of just repurposing my old saitek X52 into a button/dials box. I'd just need to replace the 2 way switches with latching 3 way switches right? Any thoughts/suggestions?

I started having the same problem just randomly all of a sudden, the game starts and i use voice attack, and say "pause" and the pause screen goes away, but using pause again won't get it to start no matter what. The command to show frame rate works but thats about it. I was messing around with settings beforehand with oculus tray tool and some graphical settings and tried to remember what i had changed. Well, one of them was enabling heat blur... I turned it back off and now it works. I have no idea if that was the problem though. It didn't matter if it was vr or full screen. And i was using the mirage instant action scenarios.

I wanna use my x56 rotaries for stuff without having to use the saitek software. Wouldn't it be possible to map the bands somehow for things like knob positions or radar azimuth?

The x56 can map the mode switch as a MODIFIER not a switch... I've got mode 2 and 3 mapped as modifiers and mode 1 blank.