PickleMonster

Definately through hole, that's what the legs were designed for.

Yes. This is how it works in most software release cycles with a beta test phase. A beta is for testing new features before it hits stable. When the software is stable enough it gest moved to stable. Stable has never been nore never will be a guaranteed bug free experience. For OP, it's entirely up to you. Think about how you deal with bugs. If you don't react well to them, OB is not for you (and that's okay). With ED's new monthly release schedule (approximately) you're more likely to see a stable release a week or two later, usually after a hot fix.

On SRS, on the main area, there are two drop-down boxes for "speakers and optional microphone output". You want to set the right-hand one to "no output" or whatever the description is. It's on the main page so looks important so everyone ends up putting that on. But it's kinda of a niche feature that most of us won't need except maybe test your mic output.

Mi-8's aren't available to add for the Syrian faction. I know it's probably not the same model that Syria uses, but it's close enough for our purposes. Any chance we could get this added?

There's a lot of missing switchology functionality in many older DCS modules. And whilst you can hack them into existing LUA's they get overwritten every new update. The A-10C and Ka-50 in particular lack axis assignments for things like radio and lighting. I've had to use a 3rd party tool to mimic On-else-off toggle switches for a lot of my aircaft. It would definately be nice to see some older modules revisited to bring control assignments in line with newer modules.

Not really no. You can fly at night but the Shkval TV becomes useless in the dark as it's daylight only.

I used Shadow for a while when I was trying out Star Citizen. Unfortunately the support for USB devices is pretty limited. If you want to try anything make sure you have USB over IP turned on for Shadow. Never got flight sticks to connect consistantly, and never more than one device at a time. The official word from them was that TrackIR's are not supported. For anyone wanting to testing Simo's suggestion out, bear in mind that VPN's are against their TOS so you may end up getting banned.

*bangs head on desk*

I've been trying to buy some items from the microhelis.de website for a while now. But when I get to the checkout it says it couldn't figure out delivery and to get in contact with them to make the order. However I've sent several emails but heard nothing back. Has anyone else had issues ordering with them and do people know if the company is still operating?

DCS UFC's export scripts are based on the same scripts that the streamdeck plugin uses. Unfortunately the guy who wrote the app cut out a bunch of stuff not relevent to his own project and modified it. The end result is that both export scripts are similar enough that they can't be used at the same time, but are significantly different enough that you can't run both apps off the same export scripts. It's kinda rubbed me the wrong way, the original export scripts power at least three different applications (Ikarus, dcs flight panels and the streamdeck plugin). The DCS UFC guy is profiting off those scripts but doesn't appear to be making any attempt at maintaining compatibility or merging his changes back into the project. It's a shame really because I really liked the app.

Those are dog tags? I thought they were a heating element for the window.

Does it? Or does it say a lot about the toxicity within the DCS community? I mean yeah, Razbam does have issues. But lets not be children about it. I've got a long list of bugs for various Microsoft products but I don't sit with a spreadsheet expecting them to check in on it once in a while. Also if you're that concerned about bugs, why is this not in the bug section?

Nah I just think that people put far too much emphasis on the community bug tracker. For a start it's unofficial and doesn't represent what Razbam is tracking or even aware of. Secondly it's not updated, there's bugs in there that were squashed ages ago. Thirdly theres bugs in there that never existed or are something that's just WIP. Finally it seems to be used to passive aggressively shame the Razbam team. That's not healthy. If you've got a bug, report it to the bug section of the forums. To highlight this point, why is this thread in the general discussion section of the Harrier module and not in the bug section?

Works fine for me. Also the community bug tracker is absolute rubbish. The community doesn't update it and a lot of the "bugs" are spurious. It's essentially a passive aggressive dig at Razbam.

The aircraft horn appears to be broken. It appears to stick on when you press a keybind assigned to it.

There's three things that really help a cockpit builder out. 1. Export your displays. I can add display exports to the lua config files fairly easily but these are deleted when DCS updates. Having those already in place would help a lot. Additionally give your exports unique names. Currently most aircraft already export to the two MFD areas which is fine if the screen ratio of the thing you're exporting is square. Having it's own namespace allows you to give it a different set of size options in your display.lua which can account for ratios like 4:3 for the Vivien, Shkval and Kiowa MFD. 2. On-On and On-Off switches. Toggle switches come in two basic types. On-On which is where the switch is wired for two different on positions and On-Off where it's considered on in only one position. To cater for both you need keybinds for toggle up and down and On Else Off. On-Else-Off is used in the Harrier module, the switch in game is considered on whilst a switchstate is active otherwise it will be considered off. 3. For dials/knobs allow for the use of both Rotary Encoders and Potentiometers. I came across this recently building an ICP similar to the A-10's and the Kiowas where an audio channel is turned on and off using a push-pull knob. The only available hardware that gives that functionality is a potentiometer with a push-pull shaft. Unfortunatly potentiometers are not supported by the likes of the A-10C for it's radio volume controls, only potentiometers. This means I've had to add some kludgy Axis binds manually.

This has already been nixed by PolyChop. They're not developing M4 functionality becuase it's a lot of work for something that's going to be fairly janky in implementation and pretty much won't be used.

It's not. It's not even related to PolyChop or the Kiowa. Issues with LOS, RADAR effectiveness etc... are DCS issues and not something that PC are in a position to resolve.

The yellow lighting is for your eyeballs and flying at night. The blue lighting is actually UV and used for flying using Night Vision goggles. The UV lighting is the small knob along the bottom right of the front panel. The regular instrument lighting is the cluster of three switches with brightness knobs just below your caution lights. There's an overhead spotlight that's turned on by rotating the cap to the rear of the device. There's a red filter for this as well if you click on the front of the light.

I'll see if I can replicate this issue tonight as I'm flying online. No doubt I'll need to respawn a couple of times :P Also VMS? My last place I had an old Compaq DEC Alpha server that I had to dive into once in a blue moon. Man that brings back some memories!

What we do have are two additional multirole 4th generation fighters. Which was the second most requested feature and a dynamic campaign is in the works. Other requested features were the dedicated server and new maps, which they delivered. Recently ED held a poll on what's most important to players flying the F/A-18 and have altered their development efforts around this. Which is ironic because it also highlighted the problems with the community. Ground radar came top, despite it being a feature mostly ignored by real pilots. You can also note that the most popular request was for dynamic campaigns yet the least most popular request was for actual missions and campaigns. They may not have delivered a dynamic campaign engine yet, but there are definately plenty of other examples where they have listened. And working on modules doesn't mean other features cannot be developed.

Actually that's been really helpfull as I've been scratching my head with the same issue.

There are some issues with assigning axis to the UHF, VHF and FM1 radio volumes on both the pilot and copilot intercom panels. As shown in the image below. There are duplicates for Pilot VHF radio (as well as Copilot UHF Radio further up not in screenshot. There's also a "Volume FM1" and a "SA342 FM1 Volume 2" which I believe are for the pilot and copilot FM 1 radio volume. However they seem to be named inconsistantly although do appear to work to some degree (more on that later). There doesn't appear to be a UHF volume control axis option at all. I've had a quick look at the LUA and it appears there should be three axis assignment options for both the pilot and copilot intercom panels for UHF, VHF, FM1. Oddly assigning a control to the VHF axis modifies the UHF volume on the panel. The second issue is that the volume controls don't work either. Any movement on the assigned control turns the volume up to maximum.

Question is very lopsided. And why do you think ED needs a subscription model? Do you think thowing more money at modules will speed things up? https://en.wikipedia.org/wiki/The_Mythical_Man-Month

As Holton181 says. It had me scratching my head for some time trying to figure this out. It's only when the new lighting model made the master warning light very obvious that I figured something wasn't right. Pulling back and then rehoming the fuel lever fixed the issue and I was able to engage AP properly. It's now part of my ground checks.