Baldrick33

Sounds like you have resolved it, that must make you feel good cracking that one!

I believe you can do exactly that now. Just bind the camera movement controls and don't bind the zoom controls.

I would have thought by definition zoom is unrealistic. It is an aid to help overcome limitations in a simulation given we don't have a perfect representation of what we see in RL.

I also use Joy2key as you describe with a rotary on a button box so I can move the mouse cursor up and down if needed to save my neck! Another rotary is used for mouse wheel. Plus I have a button mapped on my stick to recentre the mouse (again using Joy2Key - absolute mouse position 50:50), this could also be used to drop the mouse down slightly by changing the Y value

These look fantastic!

The question I answered was generic "i still cannot see the advantage of having the programme over a self made voiceattack profile" It may not work well for your specific case but that doesn't render it to not be of great benefit to others. Perhaps you should make a constructive suggestion rather than rubbishing a product with an attention seeking thread title...

A quick question: Is it possible to automate the start of SSA, e.g. to add it to the list of external applications to start up with SkateZilla's DCS launcher program? I can't find an exe that starts SSA, the process seems to start from within the menu program. Is there a parameter that can be added to the menu program exe shortcut (SimShaker for Aviators Beta.exe)

For someone like me that has not previously used voice attack I found VAICOM an easy way of implementing voice comms. I don't use SRS nor wish to use voice control for anything other than comms so it has worked for me out of the box. I guess in your usage scenario I can see some complexities but as a ready made package I have been impressed with how well it works.

My experience using VR: I start SteamVR Start SSA - sound module loads Start DCS Note that starting SteamVR starts WMR in my case as I have a Reverb. This changes the default sound device. Not that it should matter as I have a different sound device assigned to the Sound Module and DCS has its own assignments (not default). However, when SteamVR stops after use the default sound device switches back. If I leave SSA open and start SteamVR and DCS again chances are the sound module won't work - it shows the correct device in settings but hitting test & play nothing comes through. So I restart SSA to get it working. In my case the order is important as I think starting SSA before SteamVR/WMR causes an issue with the Sound Module where the Windows sound devices are switched. So as long as I follow the order at the top of this post it works fine very time. I hope this helps.

@flusim3Do you use VR?

That did it - Bah Humbug!

Agreed but at least there is a way around it. Alternatively use the in built modifier but it isn't as elegant a solution. If DCS could allow short and long presses of buttons to input mappings that would be better (clearly it can distinguish between them as it does in the implementation of TMS, DMS etc in the A-10) but that might not be a quick fix.

As a work around it can be done using something like Joystick Gremlin and a Tempo option. Short press: Comms Menu Long press: Push to Talk They would be seen by DCS as two separate buttons to map.

It really shouldn't matter, as a rule I start Simshaker first. To check the SoundModule is correctly configured before starting DCS, you should click on the grey icon in the Windows task bar and it will indicate which soundcard is being used and any issues with the software in the box at the bottom. You could click on test and then play to prove the buttkickers are working. You shouldn't have to do this every time just to be sure all is working ok. Sometimes a Windows update messes up the soundcards and it needs to be re-assigned in the settings tab.

That sounds like a possible reason, the buttkickers should only be receiving a signal from SSA for it to work correctly AFAIK

My assumption is the telemetry is produced regardless of the view chosen, which is what is being sent to the buttkickers. So always as if flying from the cockpit.

Not at my PC now but I believe an “ideographic space” will work, this is achieved by pressing the Alt key and 3000 on the num key pad

Your thought process is the same as mine! I have recently got the TM F18 grip to go with my TM base for now, hoping to get a Virpil base next, I currently use a 100mm extension with my TM so probably be the CM2. I really like the F18 stick, it fits my hand better than the original A10 one, plus it is a bit lighter. I think most Virpil products are on back order, so I would wary about waiting for them to be in stock.

Yes my understanding is the CM2 is designed with extensions in mind and has a smaller deflection range and the Warbrd designed without extensions. However, both can use extensions or not as preferred. There is no risk of damaging the Warbrd base with extensions just that the deflection range may be too great for comfort or fit.

My understanding is the Warbrd can also be mounted. It has a greater deflection range which may be handy if you never plan to use an extension. The CM2 base is easier to change cams and springs if you plan to regularly tweak things.

It is not to do with your installation but rather the latest build of open beta: https://forums.eagle.ru/topic/287242-odd-action-names-have-appeared-in-several-aircraft-controls-lists-following-patch/#comment-4831288

Also a lot depends on what you plan to use DCS for. Some of the lighter weight single player missions run pretty well, especially on the Caucasus map. More complex single player missions and some of the newer maps can struggle with VR, multiplayer with lots of assets likewise.

It seems a bit variable. I got through four Reverb G1s under warranty, one of which I needed to adjust using the WMR tool, the others including the current one. I did try a G2 with DCS and saw no issue. Maybe the elephant in the room is the reliability of the headsets and cables. The Quest 2 seems pretty solid in this respect.

Good advice here. In my experience there is a wealth of knowledge and willingness to help on these forums. I feel I know my way around the DCS control systems, it is incredibly flexible but sometimes that flexibility means needing some initial setting up rather than working out of the box. Happy to help if I can.

G1 and Quest2 owner here and I concur with everything Werewolf-fs says. G1/2 for simulations, Q2 for other stuff.