MileHiRyder

Yep, I've gone from crash before second mission to crash after first mission exit as well.

I see in the latest update summary this statement: Wingtip AIM -120 causes damage on Launch - Fixed As you can see in my debriefing the failure occurred immediately after firing AIM-120. If I recall correctly most if not all these failures I experienced were after AIM-120 launch. So I'm hoping this problem is fixed.

This has happened to me on multiple occasions as well. Here is the debriefing from the last incident. Next time I'll save the track and include it.

Just got this failure again tonight. Here is a screenshot of the debriefing:

Sure. On several occasions while flying the f16 in single player missions I'll hear a pop and begin losing control of the aircraft like a missile strike. However, looking at the mission debriefing I see the event listed as "failure" and the details say "AN/ALE-47 container failure". No missile strike is indicated. I've been assuming this is a simulated equipment failure but it never happened until a few months ago and its happened several times now. I was curious if anyone else has experienced this and was wondering what has changed recently. Thanks.

I've recently been getting an AN/ALE-47 container failure and getting it quite frequently. Does anyone know why? Thanks.

After experimenting some more, pressing alt-enter before launching a second mission makes no consistent difference. Crashes are very frequent but random regardless of what I do.

Running DCS (with full screen unchecked) I flew an instant action mission with the f16, quit then pressed fly again and DCS crashed as it did consistently before. I ran DCS again and flew the same mission then quit, before flying it again I pressed alt-enter one time...DCS crashed again before the second mission started. I started DCS a third time and after flying the same mission and quitting, I pressed alt-enter then alt-enter again before pressing fly again....the second mission started without crashing. Subsequent missions worked with no problem at all even though I didn't press alt-enter anymore. I shut down then restarted DCS and flew several missions in sequence again without crashing and without pressing alt-enter at all. Hoping the problem might have somehow been resolved, a little later I again restarted DCS and ran the same sequence without pressing alt-enter...it crashed on the second mission. Restarting and doing the sequence again this time pressing alt-enter twice after quitting the first mission, I was able to run multiple missions without crashing. I hesitated even posting this but it does appear that pressing alt-enter does have some effect.

Just updated and I'm still experiencing crashing on the second mission. It crashed 3 times in a row when attempting a second single player mission.

Didn't even know there was two clicks on that wheel. Always learning things on the forums. Thanks.

Using the Virpil software, is there a way I could change the color of the LED on my Alpha grip based on a button push on my CM3 Throttle? For example, I would like the Alpha grip LED to indicate when I have my airbrake on with a color change.

These settings seem to be working fine so far with DCS. The problem I have is that when I use the throttle for MS Flight Sim 2020, I can’t figure out a way to tune the axis so that the throttle position is zero when it’s resting at the lower detent like we can in DCS. Is there a way using the Virpil software to create a user defined “logical” axis range? In other words, when my throttle is resting at the lower detent it’s at 13%. I would like to be able to define the “physical” range of 13% - 100% to be a “logical” range of 0% - 100%. Any position below "physical" 13% would just be programmed for button clicks. This would enable the throttle to be used in any flight sim while keeping the detents in place and not requiring trying to tune out the 0 to 13% position.

I was having the same issue but I noticed it wasn't a problem with DCS not seeing the higher buttons, the VPC Joy Tester was indicating that the throttle wasn't sending anything higher than button 64. Looking at Ken's profile, he has assignments made to logical buttons 61 through 64 (the toggle switches). Mine were unassigned and I was trying to follow his instructions to program logical buttons 65 through 68 like you. Apparently the software doesn't like an unassigned gap between the logical button assignments because once I programed buttons 61 through 64 with my toggles, the throttle began sending all the assigned buttons up to 68. Problem solved. Seems like a software bug to me.

That's a significant number of full turns before stopping. How many turns does it take before the other detent snugs up?

I ordered my CM3 on Dec 5th (along with an Alpha grip and WarBRD base) and received an invoice two days ago. So I really appreciate all the information being shared by those of you who already have the throttle as I anxiously wait to receive mine. Thanks. The issue with the detent screw is disappointing to hear since this is so basic. Assuming you've already verified that the threads are not stripped, would a small thin washer on the screw enable the detent to be snugged up?