mkel2010

I had version 8 installed and it worked without issue. Tonight I downloaded and installed version 9 using OpenMod Manager. In game, I started to get video freezes that eventually led to a crash back to the desktop. Uninstalled version 9 and the problem went away. First time I've ever had a crash back to the desktop with DCS. If there's anything I can provide to help troubleshoot the issue, please let me know.

I've never had that control bound to anything. Looking at the controls settings, the line for that control is blank except for the Keyboard column. What is the lua file that stores these settings so I can check to make sure?

What am I reversing the input to? The Ram Air control isn't mapped to anything on the throttle or base. The only mapping is the stock keybind.

I've noticed that the latest Orion II Throttle Base firmware, Version 1.19 is causing the cold Ram air control in the P-51D to be pushed and locked forward while the base is plugged in. As soon as the throttle is unplugged, the Ram air control works normally. Anyone else seen this issue? (Also in the Winwing Forum.)

I've noticed that the latest Orion II Throttle Base firmware, Version 1.19 is causing the cold Ram air control in the P-51D to be pushed and locked forward while the base is plugged in. As soon as the throttle is unplugged, the Ram air control works normally. Anyone else seen this issue?

When flying most modern jets, there are different throttle settings such as Off, Idle Cutoff and Afterburner. The throttle has detents in these positions and the finger lifts allow you to intentionally get past the detents. They also prevent accidentally pushing past a detent. The detents are another piece to the Winwing finger lift kit and they are adjustable for different aircraft.

Make sure you've gone through the Windows Speech Recognition training, at minimum. Once you've done that, you can turn off the Speech Recognition app while running VoiceAttack. VoiceAttack and Vaicom serve two different purposes. VA is for using voice to control in-game functions such as aircraft systems and Easy Comms menus. Vaicom lets you interact with AI wingmen, airborne controllers, etc. by voice. If both are installed, you'll have at least two separate profiles in VA: the Vaicom profile and the profile you created for your aircraft. You'll need to go into VA settings and make sure you set the correct setting to incorporate all your profiles together. With Vaicom installed, you'll need to configure multiple hat switches on a joystick to cover different radio channels whereas with just VA, you can configure a single switch. Bottom line is you don't need Vaicom to use VA, but you do need VA to use Vaicom. My suggestion would be to get VA setup and working before you try to get Vaicom working as the setup for Vaicom is much more complicated.

From this Reddit post on the same subject: SOLUTION: just reverse the cablepositions on the extruder-plug. On my 5 pro they are marked with different symbols on the cables. change from 1234 to 4321 (thx u/vent666). Dont try to push the little metall pins in the contact-points on the cables down to extract them from the plug, but lift the little white pins on the plugs just a little bit and pull the cables out then. If it is a firmware issue as some in that post suggest, the alternative would be to get a Sonic Pad and switch to Klipper firmware.

Even the best pilots make mistakes. "Excellent stick and rudder" did not and does not equate to perfect pilotage. Read Chuck Yeager or C.E. "Bud" Anderson's autobiographies. ED apparently didn't have human frailties in mind when they programmed the AI.

Very few human pilots - even at the highest skill levels - have ever been able to fly an aircraft "carefully manag(ing) energy never pulling excessive g." It would make the simulation much more realistic if ED were to introduce a randomization factor to this AI "skill."

Magnetic compasses don't account for magnetic variation - you do that in flight planning, adjusting the course to take the magnetic variation into account. That said, I use Matric represent some of the instruments and switches for the P-51 on an iPad. The instrument data is exported from DCS BIOS to DCS Matric to Matric. I had to come up with (I believe) Javascript formulas to take the raw data and convert it into a digital readout. For the magnetic compass I used this formula: return Math.round(value/182.041667,3). Value is the raw DNS BIOS reading, 182.041667 is the number of times 360 goes into the maximum DCS BIOS value for the compass and the three represent the number of digits. Round just rounds up to the next whole number.

I will go back and confirm, but I believe the fuselage tank is empty. When you say 60% fuel load, are you referring to total fuel onboard?

I get your point, but physics should be physics. It's a shame that after all the years of DCS' existence this hasn't been fixed.

Any pointers for maneuvering in air to air combat above 20k feet or so? Trying to turn at much over a standard rate turn, the P-51 wants to stall on me, even with one notch of flaps. It's fine at lower altitudes. The AI don't seem to have this issue.

I'm not having the problem you're experiencing, but I came across a video that just came out a few days ago about video settings in DCS. Maybe worth a look:

Please let us know when they fix it.

I just checked and I get the same message. It's likely because the grip doesn't need to update and having it connected while the base updates would likely corrupt the grip's firmware. Best bet is to disconnect everything but the base, keyboard and mouse to run the update.

Take a look at the DCS Community Keybinds, linked below. Installing it (and the Quaggles Command Injector) gives you a series of Custom key binds, which include Fast and Slow trim adjustments. There is a link to the Quaggles Command Injector on the page linked below. For me, the trim changes happened too fast for my liking and using these key binds have allowed me to slow the trim changes way down so no reason to believe they won't do the opposite for you. https://github.com/Munkwolf/dcs-community-keybinds

I went ahead and disconnected a couple of USB drives and the hub and updated my rudder pedals and throttle. Everything went well and force feedback actually works now with the throttle handle in DCS.

SimApp Pro warns that ALL other USB devices need to be disconnected (including USB hubs) before updating firmware on Winwing controllers. Has anyone done these updates WITHOUT disconnecting every other USB device in the system?

I feel your pain. It's much more noticeable when pushing above 50 inches of manifold pressure on a dirt runway as with some of the Normandy airfields. I would make sure you set the 6 degrees of right rudder and two degrees nose heavy pitch trim and try some take offs at around 50 inches of MP. You'll want to do this from an airfield with a long, wide hard surfaced runway like Manston. What has helped me (definitely not perfected yet) is to make sure you hit LCtrl + Enter to turn on the graphic for your control positions. Make sure to keep the stick aft of center until you get to 100 MPH and then just relax it to neutral; lift off about 120 MPH. Keep increasing the MP by 5 inches or so as you improve until you can take off without issue at 61 inches of MP. This is definitely a work in progress for me.

Not sure if this is a bug or I'm just doing something wrong. If I set rockets to single, I can fire them all day long (with unlimited Ammo setting on.) However, when I change the rocket setting to Auto and have the Rockets To Be Fired set to 2 or more, the rockets stop responding after the first salvo. I have to exit the mission and restart to get any rocket setting to work.

Yes, that was the solution to the issue.

I installed Open Mod Manager today to replace OVGME. I got everything set up and then tested DCS to see if I was able to get the community Keybinds back again (they'd previously stopped showing up.) On opening DCS, all the Custom keybinds were there. I shut down both DCS and OMM and then deleted the OVGME application. Came back a little later to fly in DCS and when I got into the settings, the Custom keybinds were gone. I went back into OMM and when i tried to load the hub I had created for the main DCS World folder, I received a Target Directory Access Error basically saying there was a permissions issue with the main DCS World folder. I tried recreating the hubs and had no issue with the hub I created for the Saved Games folder but still got the Target Directory Error for the main folder. The DCS World folder is marked as Read Only by Windows 11 and cannot be changed. I'm not sure that's the issue as it apparently worked correctly the first time. I was able to manually install the Quaggles Input injector in the main DCS World folder and everything works, but I'd like to hopefully figure out what the issue is. @sedenion EDIT: The solution is to run OMM as administrator.

Thank you.