mkel2010

I haven't had a chance to check the Master Caution issue as I am currently out of town. That said, I watched a video where someone reset the Master Caution with the Elec Caution Reset Button on the LEFT Console. Is that a necessary step in clearing the Master Caution?

I have the Orion II with the F-15 grip and didn't have any issues with using it for the P-51. Are you running SimApp Pro (the app the comes with Winwing hardware?) First, check to see if there are any firmware updates and apply them. Then use SimApp Pro to test and calibrate the throttle axes and make sure they are responding. When you map the throttle in DCS, does moving the throttle result in the white line moving when the throttle is moved on the controls setup page for either the P-51 or F-86?

That was the issue. I used a throttle mapping from the User Files section and didn't realize that was bound to a switch. I'll have to check on the ejection handle issue again. As I recall, the Master Caution light was still lit even though the ejection seat was armed. And yes, these are the Caucasus map training missions.

Today is the first full day I've had with the F-16 Module. I'm trying to work through the take-off and landing training missions. For both of them, the mission starts with the jet already powered up. And in both cases the Main Power switch is set to Battery when the mission starts. The switch is not bound to anything except the standard keyboard bind. Any ideas on how to correct this? I've also noticed that the Master Caution light is always on and can't be turned off.

I didn't have the control mapped to anything except the standard keyboard mapping. That's why it was weird.

I'm not sure what caused the issue in the first place, but it seems to have corrected itself. Weird.

Whatever caused the issue has corrected itself, apparently. Weird.

Re-installing version 9 after the rebuild seems to have fixed the issue.

OVGME hasn't been updated in 8 years. I use Open Mod Manger instead: https://github.com/sedenion/OpenModMan That said, I did the slow repair of DCS after uninstalling version 9. I will try installing it again the next time I use DCS and will report back.

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.