HunchyTheHuncher

I would really like a seat with a cut out for a centre mounted stick. Besides buying an actual second hand pilot seat for a ridiculously expensive price there aren't any options out there. There is a DIY option, but I don't feel confident enough to take a hacksaw to my racing seat.

Technically correct, however in practice I have found that without MSAA I get a lot of terrain shimmering. This all but disappears when I use 2XMSAA. Setting PD at 1.5 with 2XMSAA is the happy medium I have found for sharpening up the image and eliminating shimmer whilst still maintaining 45 fps the majority of the time.

Thanks for the heads up. Shame, was hoping to get mine by Easter.

It seems like the general consensus is either Model A or B. I do like Model A, but agree with others that the 4 sliders would be excessive for DCS. I would much rather use rotary axes to control cockpit panel light intensity, etc. This suits me fine as I can get a cable of correct size without having to worry about extensions.

Which layout are you going for?

Some of you may be aware of the Black Hog b-explorer controller. Also check out . It's a new button box and I decided to pre-order one at the end of last year. Orders are now beginning to ship and customers are being given the choice of three different layouts to suit their needs: The Model A version comprises of: 6 axis (2 potentiometers and 4 sliders), 4 toggles (3-way momentary toggle switches) and 8 buttons (one of them with a clear cover). Although no descriptions have been given for the Model B and C configurations, the key difference appears to be the no. of sliders vs. rotaries. My question is which layout do you think would be most useful for DCS across all modules? I am leaning towards Model B (generic labelling of course), but would be interested to hear other opinions. Thanks!

i agree with this 100%, but I can understand why others do not think it is worth the drop in performance. After trying VR, the only reason I go back to 2D is when I am familiarising myself with a new module (remapping controls, learning navigation / weapons systems, etc) as I find this somewhat easier outside VR. Whenever I switch back from 2D into VR it's like lifting a veil and seeing things as they are meant to be seen. For me no 2D screen, regardless of the resolution or frame rate, can compare with that. I guess it depends on why you play DCS in the first place. To some, the technological aspects of flying a particular plane or participating in complex multiplayer scenarios with loads of assets is more important than the immersion factor and I can respect that. Current VR makes everything a little harder i.e. harder to run the game smoothly, focus on cockpit instruments and spot other units. For me though, I get a real buzz out of flying in VR. The sensorial and emotional experience it gives me outweighs any of the downsides.

Big thanks to Franky for adding all these extra bindings for the Viggen! I am have having difficulties mapping some of the ON/OFF toggle switches. For example: The "RB-04/RB-15/BK Release Mode Valb/Prep" switch can be clicked to either up or down in the cockpit. However, when I map the corresponding _My Buttons binding to a switch on my throttle (VPC MT-50), the switch can only be activated in one direction. I have tried mapping the binding to a momentary switch and latched switch, but the issue still persists. I am not sure whether the problem is being caused by my switch configuration or the coding for that particular binding: {down = 3307, up = 3307, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 0.0, value_up = 1.0, name = 'RB-04/RB-15/BK Release Mode Valb/Prep', category = '_My Buttons'}, --working Any help with issue would be much appreciated!