PickleMonster

I'm going to walk my statement back. I'm sure I saw a post by Nineline saying it was a bug, but I can't find it (so I may have totally misread it). However it is possible to set an option in the ME to set an multicrew aircraft as solo only which allows bouncing between seats. But this is only available on some aircraft right now (which may be what I was reading from Ninelines post).

This is wrong information. Not being able to switch between seats in the Mi-24 is a bug.

Hinds are unable to operate on any ships or carriers in the mission editor. I've tried both new and old Kuz models as well as US Carriers/Tarawa and the Oliver Hazard Perry. Giving the helo any of the takeoff Types in the ME moves it to the nearest airfield. And you're unable to set the ship as a landing point as well.

DCS is a game running on a consumer electronics. Not everything is going to be perfect. It's a very hard to pull off, edge case scenario that has zero impact on gameplay. You can do funky unrealistic stuff in all DCS aircraft. For example if you set wind speed high enough, any aircraft can pretend it's a harrier. And it's been stated time after time after time that the Gazelle will get revisited once the Kiowa is released and stable.

Sorry bud, the product is simply faulty due to cheap parts and construction. All your pots appear to be jittering which suggests it's the board itself that's picking up noise. DCS is very unlikely to have made any changes to your drivers. Even if it did, it would likely stop working altogether. This happening just after an update is just a coincidence.

And posts like this highlights one of the reasons they don't bother visiting these forums. Putting up with the same inane circular arguments.

Whut?

@Kappa. Have you heard that the guys have stopped working on the project? There's going to be long periods of testing, coding and tweaking which don't translate to exciting shiney features to show off. PC are also a small team and this isn't their full time job. The world has been in the grips of a pandemic for over a year now. They have to juggle their own jobs, thier own lives, and working on the project. Social media management is an expensive luxury. When they do engage with the community on here, they receive a lot of toxic comments. Some about the Gazelle, and some about things being "broken" on a module that's not even finished yet. When they stopped putting up screenshots people freaked out, when they restarted putting up screenshots people shouted "these aren't updates" Nobody has paid for pre-orders. Nothing has been released. None of us are owed anything by anybody here. Paradoxically people are screaming for PC to hurry up and release, but woe if a module is released "unready" or with bugs. Can we all just chill out, let the guys get on with their work and accept it'll be ready when it's ready?

With all due respect, thats delusional nonsense.

MS25212 is the set of standards laid out by the US and adopted by many NATO countries that define the sizes, colour, fonts and other items related to aircraft panels. The side panels will usually follow those standards. You'll also want to read up on Dzus rails and fastners, which is the items used to fix those panels to the cockpit. You'll probably not want to use Dzus due to the costs, but it'll give you some measurements for your own fixings and help work out the height of your panels. Width wise the standard is ~142mm. These however won't be much use for an up front controller which is mostly bespoke. One bit of advise I'd give for your front panel. Figure out how to make it work first before trying to figure out the layout. The space you have to mount everything and how you drive your MFD's will define a lot. Do you want everything free floating with individual mounts for your MFD/Tiny screen combos and UFC? Or do you want a big panel which looks like a traditional aircraft pit? Do you want a single monitor to drive your MFD's as well as a couple of gauges and some additional exports such as RWR's or the F-16's DED? Get some paper and plan it out first, knock up prototypes using cardboard or cheap sheet materials.

Those style of switch covers are made by a company called APEM, but they're not cheap (~$60). Microhelis.de however make a clone (which I think is 3D printed?) for about 1/4 of the price, and even come with a switch built into the cover for toggling a cover in the sim.

Changing the GUI scale didn't work for me either. However I reverted to one of the default monitor layouts luas and it started working. I think the new kneeboard doesn't like it when the GUI is a different width and height to the overall screen width and height. Added my monitor layout LUA for reference. I've got two monitors for DCS, both 1920x1080 for a combined 3840x1080 screen resolution. Helios.lua

I'm having the same issue. No border, not able to interact with it at all except scroll through pages like previously. I've also removed all mods and done a refresh on my install too.

I think the BB problem is a general DCS error as I've seen other airframe RWR's showing BB as threats too. It's likely that ED needs to fix that one and not PC.

Are there any guides on creating your own gauges? Or know if there's a generic glass cockpit digital display out there already?

Sure. "High Quality" I've flown literally half a Ka-50 back to base so many times. The HIP damage model seems to wax and wane between tissue paper and dense stalinium. Both the HIP and Huey do actually have FM issues reported. Polychop actually delivered a working MultiCrew (before it was broken beyond repair by DCS core code changes). People are still waiting for those features for the other helos. All the modules in DCS have quirks. Yet all the modules in DCS are far better than anything I've flown in X-Plane 11 or Flight Simulator. I'm happy with Gazelle as is, but welcome any improvements the PC team have learned from the KW. The Kiowa will be a day 1 purchase for me.

I half agree with you there. Concessions sometimes need to be made to compensate for the lack of a second body in the pit. That being said, I think the auto-hover is based on a real system and may represent it's own fickle requirements. We're probably getting as much feedback as the real world pilot would be getting. We don't get kinetic feedback (without specialist hardware) so the red box helps with that. Both the auto-hover and performing a good pop-up comes with practise. But a 1-2m pop-up on a button you hold down may be a great substitute for the lack of a human pilot.

We understand your point completely. The Gazelle isn't how you expect it should be. This is fine, you're allowed to have concerns. However it is not fine that you insist on derailing every thread in PC's section of the forum. Stop posting your personal issues with the module on everyone elses threads. You are destroying meaningful conversation when you do.

Once again. Your personal vendetta against PC has nothing to do with OP's original question.

Just watched a new F-16 video (with Harms) and noticed their RWR was also showing BB. Looks like it might be a general DCS issue.

What has this got to do with OP's original post? If you've still got issues, make a new post. Don't pollute other peoples threads with your rediculous crusade.

Same with the rotor break, if it also isn't fully enaged forward it will also stop the fuel flow lever from fully opening. As Gizmokev says, stick them on a keybind. Or look into some deadzones.

Perfect!

Is there a way to block someone? Because I'm getting tired of seeing the same stuck record.