Scott-S6

Manley Power Best name ever. If you're into your WW2 naval history you'll know the name - captain and later Admiral Sir Manley Power. But, since he's supposed to be an American, Chad Wolf.

It varies. If you watch the animation in the cockpit you can see that some are pulled out before moving. I also had a look for a lever. Most are 3D printed, even some of the quite expensive ones, and I don't feel this is a good material choice. The only ones I found that weren't were commercial style levers which isn't what I wanted. If you don't want to make something then take a look at the panel from virpil which has a sizable landing gear lever. Might be what you're looking for. Winwing also have a panel with a landing gear lever but it's much smaller.

Okay, here's a rough and ready solution for you. If the on/off positions are out of sync you'll need to move the toggle to the menu position to resync them. There is a better solution referencing switch states directly but that'll need a little more digging. For each of the four CMSP switches you need an additional keybind in the input/joystick/default.lua {down = iCommandPlaneCMSP_JMR_MENU,up = iCommandPlaneCMSP_JMR_ON, name = _('CMSP JMR MENU'), category = _('CMSP Panel')}, {down = iCommandPlaneCMSP_JMR_ON, name = _('CMSP JMR ON/OFF'), category = _('CMSP Panel')}, {down = iCommandPlaneCMSP_JMR_ON,up = iCommandPlaneCMSP_JMR_ON, name = _('CMSP JMR switch'), category = _('CMSP Panel')}, That last line needs to be added. That toggles the state of the switch between On/Off when the switch is pressed and when it's released. Bind up position to menu and down position to switch (the new keybind). You now have working toggles. I'll update if I get the better but messier solution which references switch state directly working.

It's nothing to do with your board or switches - behaviour is exactly the same when bound to the keyboard. Menu returns to On when the switch is released. This works just fine with the toggle switch. On/off toggles on repeated presses. This is not what we want for a toggle switch. A new keybind will need to be created. ETA - I think the reason you aren't seeing discussion about this from other pit builders is that they're using DCS-BIOS which makes toggle switch behaviour easy to implement.

Why don't you ask their maintainers who've actually seen the pedal mechanism to comment? When you handle the unit it is obvious how it operates.

You can't see if they're rotating or not, they only rotate 5degrees in each direction. They do rotate however, they can do nothing else. The rails support the whole rudder pedal mechanism but have nothing to do with the operation of the rudder bar or the pedals. Look at them - note that the pedals are mounted to either end of a bar that has only one pivot at its center. They cannot move parallel. The pedals and brakes are FBW using force transducers as sensors. The status of the hydraulics has absolutely no effect on the feel of the pedals which are very stiff (110kg to full deflection) and barely move (less than half an inch) just like the stick.

Those are the mechanism to move the whole pedal assembly forward/backwards to fit the pilot (remember that the seat moves up and down, not backwards and forwards). They have nothing to do with operation of the pedals.

Look at the real unit I posted previously. There is no mechanism there for the pedals to move in parallel. They are both attached to a single rigid arm with a central pivot, rotating is all they can do. There are no rails for the pedals to move on or a dual arm parallelogram arrangement, one of which would be needed for parallel movement. (The very obvious rails at the bottom are the pedal adjustment mechanism, to move the whole unit forward or rearward to fit the pilot, they have nothing to do with pedal operation) The pic attached is not real pedals. These move in parallel and you can see the additional linkages, not present on the real ones, required to make that happen. The real unit uses force transducers for both rudder and wheel brakes. There is less than half an inch of motion for the rudder. As I said, someone that's actually seen the pedal mechanism is probably a more useful SME in this case than a pilot. With the extremely limited movement there's no way for a pilot to know if they're pivoting or parallel. They don't feel like they're pivoting. Regardless, the current animation is completely wrong. They should barely move - like the stick. (Cue people reporting that the rudder pedal animation is broken because they don't move...)

Here's a better angle on the pedals. It's very clear that they rotate. The movement, however, has a very limited range - far less than shown. The rotation will be very difficult to see in the cockpit with only a fraction of inch of movement. Maintainers may be better SMEs than pilots in this case.

Yep, that sounds like "we'll have more progress to show this year" to me.

It seems to me that something we need is a DCS specific mod manager to manage LUA edits. Regular mod managers do file replacement which means that when files get changed by the devs restoring our edits removes those changes. Plenty of threads where people have caused themselves problems by doing this. What I'm envisaging is a simple application with three functions: 1. Scan the aircraft folders looking for edits (identified by specific comments above and below them). Record the edits and the edited files. (this will be slow but you only need to do it if you've made new edits) 2. Go through the list of edited files, check to see if the edit is there and if not put it back in. 3. Go through the list of edited files, check to see if the edit is there and if so remove it. (for playing on servers that permit no LUA edits) This gives a cleaner and more reliable solution for restoring edits after an update. It also gives an easy way to revert to pure files for servers that require it. Any interest? Any suggestions? I'm considering making something to do this but if no-one else is interested then I won't bother to make an interface or package it.

I wonder how much of a market for ED China is? Saying that Taiwan is a country is a good way to find yourself unable to trade in China. Every statement and comment about that corner of the map would need to be VERY carefully vetted.

The M2000 has a few missing keybinds. I prefer not to use the mouse in the cockpit at all if possible but you can't fully bind the startup process.

Are your toggle switches on-on-on or on-off-on and which keybinds exactly are you binding them to?

Not even that. RAZBAM have confirmed that the handful of startup functions that have to be performed by the WSO will have pilot seat keybinds. Full functionality will be available from the pilot seat. This is a massive difference between the F15E and other two seat modules which YoYo keeps avoiding.

I think they've broken it temporarily. It clearly hasn't always been like that because I have the regular version installed in a non-standard location.

Are you trying regular or open beta? I tested the open beta installer and it definitely asks you for a location.

When you run the installer it asks where you want to install and I've just verified that the files it's downloading all go there, there's no write traffic on other drives. ETA - is it telling you there's not enough space before you select an install folder?

Your problem is where the installer is caching files, not where the installer is downloaded to? Your original post was ambiguous. Let me take a look.

You could change the path of the default download location in Windows registry. Or change the download location in the browser settings to something other than the windows default. Or you could right click on the download button on the dcs page, select save as and then choose the location.

For some reason the AV8B wants you to activate the export of the MFDs. There are two keybinds available for this. Right MPCD Export View ON/OFF Left MPCD Export View ON/OFF Bind those and press them when you're in the cockpit and the exports will work but you have to do it every time.

If we could have AI that manoeuvre within the same constraints that we do, that would be a good start. One step at a time.

That's not the only problem. You only need to look at some other games to see the potential problems. Skins with illegal content being the main one - instructions for making bombs/drugs, ITAR restricted materials, porn, etc. Ludicrously large skins to mess with other players. And so on. It's incredibly abusable. Even just allowing tail art has all of those problems.

If you search for "locking hinge" on eBay, Amazon, etc. you'll find them and there are many varieties and sizes. I used this type:

I posted this in the release date thread. Looks like they aren't planning on a eurofighter release this year. We believe that 2023 will be a truly exciting year for all, with the introduction of eagerly awaited modules like the DCS: F-4E by Heatblur, DCS: F-15E by RAZBAM, DCS: OH-58D Kiowa Warrior by Polychop, DCS: F4U-1D Corsair by Magnitude 3, DCS: C-130J by the Airplane Simulation Company, new Mirage F1 versions by Aerges, DCS: Normandy 2.0 map by Ugra Media, the DCS: Sinai Map by OnReTech, and more! Please don’t miss to watch our 2023 AND BEYOND VIDEO! Link I'm not really surprised they didn't want the eurofighter in the vid. There is a certain segment of the community that takes appearing in the vid as a firm commitment that it's coming in the next twelve months and then starts screaming if it doesn't (despite the "xxxx and beyond" name).