Results 1 to 14 of 14

Thread: Launcher crashes in 4.57 with DMP files

  1. #1
    Ace
    Join Date
    May 2015
    Location
    Kansas City, Missouri area
    Posts
    515
    Post Thanks / Like
    Total Downloaded
    130.02 MB

    Launcher crashes in 4.57 with DMP files

    I have been having quite a few Launcher crashes in 4.57.

    Based on when they happen, best guess is it might be something related to either sounds or force feedback joystick (I run a MS Sidewinder joystick with FF turned on).

    I've attached seven recent DMP files in case they are helpful:

    cppcrash.zip

  2. #2
    ATAG Member ATAG_Torian's Avatar
    Join Date
    Sep 2011
    Location
    Newcastle, Australia
    Posts
    1,592
    Post Thanks / Like
    Total Downloaded
    108.53 MB

    Re: Launcher crashes in 4.57 with DMP files

    Hi Flug,
    Always worthwhile with any "I have been having (whatever problem)" thread to include your system specs (like in my sig below).
    A couple of things to try initially:
    Check the game files in Steam to make sure the game isn't corrupted.
    Windows updates have been known to foul up video card drivers and cause this sort of thing. It's a simple re-install of the driver to fix tho.
    In CloD game "Options" check ur Video settings and see if u are in Full Screen ON or in Pseudo. If Full Screen is ON then try setting it to Psuedo.
    Do u have a system monitor utility that can show gpu and cpu temps as well as other performance parameters that might indicate a bottleneck ?
    MooO system monitor is a free utility if u don't have one https://www.moo0.com/?top=https://ww...SystemMonitor/
    System specs:
    Gaming laptop: Metabox P750ZM, CPU Intel i7-4790K @ 4GHz, GTX 980m with 8Gb DDR5 VRAM, 16Gb Dual channel DDR3 RAM, 2 x Samsung EVO 840 500Gb SSDs, Win10 Home 64bit.

    Gaming PC: MSI PRO Z690 WIFI DDR5 mobo, Intel i5 12600KF cpu, 32Gb Corsair DDR5 5200Mhz RAM, Samsung 980 Pro 1 TB M2 SSD, Corsair 850w psu, MSI RTX 3070 8GB vram vid card, Windows 10 Home 64bit.

  3. Likes ATAG_Vampire liked this post
  4. #3
    Ace
    Join Date
    May 2015
    Location
    Kansas City, Missouri area
    Posts
    515
    Post Thanks / Like
    Total Downloaded
    130.02 MB

    Re: Launcher crashes in 4.57 with DMP files

    Quote Originally Posted by ATAG_Torian View Post
    Hi Flug,
    Always worthwhile with any "I have been having (whatever problem)" thread to include your system specs (like in my sig below).
    A couple of things to try initially:
    Many thanks for this. My graphics card "died" last summer. So I went many months with no graphics card (motherboard built-in), then replaced it with my old, slow but known-good card, and now to you--thanks for pointing out that the Windows update hosed may graphics cards settings--I figured out that it was working just fine the whole time.

    (When Windows killed the settings it made something happen at boot, and then it posted to my 2nd monitor, which I didn't notice thanks to another computer hooked up to it that takes over the screen if the first computer isn't active--and so I assumed it must be dead. Anyway, long story short, all fixed and working again thanks to your comment above.)

    Anyway, regardless of completely updated drivers on my old card (GTX 960 or something like that--it's not installed now), and new GTX 1060 installed and brand new drivers, I was still getting the regular crashes.

    I strongly suspected the crashes were due to a bug in the force feedback handler. Pretty much every single Launcher crash comes at a moment when I would expect to feel a little bump or vibration to start on the stick.

    So here is a selection of Error logs from Windows Logs over the past month. There are lots more, but that are all basically the same--maddox.objects.effects.ForceFeedback (or perhaps whatever calls it) seems to be the cause.

    Also FYI I went into SteamLibrary\steamapps\common\IL-2 Sturmovik Cliffs of Dover Blitz\parts\core\FF and removed all of the .FFE files except for SPRING.FFE.

    No crashes whatsoever since then.

    I am pretty such this is caused by a certain bump or jolt effect in the forcefeedback code--maybe in punch.ffe or shake.ffe? Anyway, when a certain effect of that type triggers in certain situations, then crash with the error as listed below.

    My system info is at the bottom just FYI.

    Code:
    Application: Launcher64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at <Module>.rts.?A0xf78dec5b.setEffectGain(rts.EFFECTS_NODE*, Int32)
       at GvrAEaiQCsaTWDfv1L3BIjUpzF_5ixJ7$knEUZUtsHPH+mzGiM$1StfeoZYMEqjoX6USSNn7CoU01r6g40DfHswWHYSZLH2QnJ1S$M06_2MaDAY_8ZHpeFjyipCbCwHVEn5c.nSkwFUPXx$MsWNNDwg4J02I(Single)
       at maddox.objects.effects.ForceFeedback.qOzDLZvHVuIRfHyFarYSsXA(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.W4PoHpqEPh6sCwH_SvBfcsLKYxyFvVEILkmOnJeyy3Yb(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.NdtVfBFOUo8sBpHhW4o0nPg(Double)
       at TNKkAcSuawGGAInhdCMgtVB1jZvc_joc87rBU8BjL6yN.vBp10yIv7$PiEY8l9wwBPME(Double)
       at 5VUIhZAfLLjlWb5rvC1y5Il_cwouhW5eZUX_AMML8alS+zHbrQdalUr$0FVVJ70h5H2O7SvcGFYB4EvDP6PMb3RJvqO3gSg71zWPFnl$OVlPSlQ.gT2xRAUYioNJspz1Vabv0$Q()
       at 4lFQrekintdZTkhMfDPtQkRUhCiE4wEk3Y$4KfiOXE3S.gT2xRAUYioNJspz1Vabv0$Q()
       at B3ik9i8vEcErjO61EnV5pr8xSg_fKyjgLBB2LLZAsCag.9pab1TQFb7TOkw5gQ3ntgHA()
       at iIer_m0niFeAfdO$W3iyIyiI$ngG4FHCF6MXe1TJ$JOb.RCg41tE05t0y9dUsvW1Y5dA(Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.s1J6D1WkYrSB0YrRqEzT6Lg(Boolean, Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.bh301Qde8FIoiT4wyRV9J$s(Double, Double)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.fJXDhLsKN6ayoknA3AcuyfM()
       at 29RjLSAReXEUSv0bsMmaiA9zVXLP0ym1LjCepgx5u8k7.WuROX084_l22L6Cx4AzEfnQ()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.pAIf0AEqmWcHUcu2It$ySZs()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.O64GqHFa2fopqVi6EWi5LMNa6pj6LaV7rC9iPR5wvIfY()
    
    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.4RbSSDv13n5tsTfRCBplbDw()
       at RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ.ccgEwiqz06skldTjEnhRh8k(RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ, System.String[], System.String, System.String)
       at 9MJVJS0Op_RWoEUtjFFh0i6XF1D7pu8BBz_H2DLdBD4y.MYwNeGOD_3nnjet2W4J1Qjw(System.String[])
       at maddox.Launch.Program(System.String[])
       at Launcher.Program.Main(System.String[])
    Code:
    Application: Launcher64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at <Module>.rts.?A0xf78dec5b.setEffectDirection(rts.EFFECTS_NODE*, Int32, Int32)
       at GvrAEaiQCsaTWDfv1L3BIjUpzF_5ixJ7$knEUZUtsHPH+mzGiM$1StfeoZYMEqjoX6USSNn7CoU01r6g40DfHswWHYSZLH2QnJ1S$M06_2MaDAY_8ZHpeFjyipCbCwHVEn5c.jVhH_8x1F1jBXhDf5KfJ1Qg(Single, Single)
       at maddox.objects.effects.ForceFeedback.dF4VG9CgY$yrAkrTivZ9pX0(Single, Single, Single)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.W4PoHpqEPh6sCwH_SvBfcsLKYxyFvVEILkmOnJeyy3Yb(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.NdtVfBFOUo8sBpHhW4o0nPg(Double)
       at TNKkAcSuawGGAInhdCMgtVB1jZvc_joc87rBU8BjL6yN.vBp10yIv7$PiEY8l9wwBPME(Double)
       at 5VUIhZAfLLjlWb5rvC1y5Il_cwouhW5eZUX_AMML8alS+zHbrQdalUr$0FVVJ70h5H2O7SvcGFYB4EvDP6PMb3RJvqO3gSg71zWPFnl$OVlPSlQ.gT2xRAUYioNJspz1Vabv0$Q()
       at 4lFQrekintdZTkhMfDPtQkRUhCiE4wEk3Y$4KfiOXE3S.gT2xRAUYioNJspz1Vabv0$Q()
       at B3ik9i8vEcErjO61EnV5pr8xSg_fKyjgLBB2LLZAsCag.9pab1TQFb7TOkw5gQ3ntgHA()
       at iIer_m0niFeAfdO$W3iyIyiI$ngG4FHCF6MXe1TJ$JOb.RCg41tE05t0y9dUsvW1Y5dA(Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.s1J6D1WkYrSB0YrRqEzT6Lg(Boolean, Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.bh301Qde8FIoiT4wyRV9J$s(Double, Double)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.fJXDhLsKN6ayoknA3AcuyfM()
       at 29RjLSAReXEUSv0bsMmaiA9zVXLP0ym1LjCepgx5u8k7.WuROX084_l22L6Cx4AzEfnQ()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.pAIf0AEqmWcHUcu2It$ySZs()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.O64GqHFa2fopqVi6EWi5LMNa6pj6LaV7rC9iPR5wvIfY()
    
    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.4RbSSDv13n5tsTfRCBplbDw()
       at RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ.ccgEwiqz06skldTjEnhRh8k(RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ, System.String[], System.String, System.String)
       at 9MJVJS0Op_RWoEUtjFFh0i6XF1D7pu8BBz_H2DLdBD4y.MYwNeGOD_3nnjet2W4J1Qjw(System.String[])
       at maddox.Launch.Program(System.String[])
       at Launcher.Program.Main(System.String[])
    Code:
    Application: Launcher64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at <Module>.rts.?A0xf78dec5b.setEffectDirection(rts.EFFECTS_NODE*, Int32, Int32)
       at GvrAEaiQCsaTWDfv1L3BIjUpzF_5ixJ7$knEUZUtsHPH+mzGiM$1StfeoZYMEqjoX6USSNn7CoU01r6g40DfHswWHYSZLH2QnJ1S$M06_2MaDAY_8ZHpeFjyipCbCwHVEn5c.jVhH_8x1F1jBXhDf5KfJ1Qg(Single, Single)
       at maddox.objects.effects.ForceFeedback.dF4VG9CgY$yrAkrTivZ9pX0(Single, Single, Single)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.W4PoHpqEPh6sCwH_SvBfcsLKYxyFvVEILkmOnJeyy3Yb(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.NdtVfBFOUo8sBpHhW4o0nPg(Double)
       at TNKkAcSuawGGAInhdCMgtVB1jZvc_joc87rBU8BjL6yN.vBp10yIv7$PiEY8l9wwBPME(Double)
       at 5VUIhZAfLLjlWb5rvC1y5Il_cwouhW5eZUX_AMML8alS+zHbrQdalUr$0FVVJ70h5H2O7SvcGFYB4EvDP6PMb3RJvqO3gSg71zWPFnl$OVlPSlQ.gT2xRAUYioNJspz1Vabv0$Q()
       at 4lFQrekintdZTkhMfDPtQkRUhCiE4wEk3Y$4KfiOXE3S.gT2xRAUYioNJspz1Vabv0$Q()
       at B3ik9i8vEcErjO61EnV5pr8xSg_fKyjgLBB2LLZAsCag.9pab1TQFb7TOkw5gQ3ntgHA()
       at iIer_m0niFeAfdO$W3iyIyiI$ngG4FHCF6MXe1TJ$JOb.RCg41tE05t0y9dUsvW1Y5dA(Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.s1J6D1WkYrSB0YrRqEzT6Lg(Boolean, Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.bh301Qde8FIoiT4wyRV9J$s(Double, Double)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.fJXDhLsKN6ayoknA3AcuyfM()
       at 29RjLSAReXEUSv0bsMmaiA9zVXLP0ym1LjCepgx5u8k7.WuROX084_l22L6Cx4AzEfnQ()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.pAIf0AEqmWcHUcu2It$ySZs()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.O64GqHFa2fopqVi6EWi5LMNa6pj6LaV7rC9iPR5wvIfY()
    
    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.4RbSSDv13n5tsTfRCBplbDw()
       at RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ.ccgEwiqz06skldTjEnhRh8k(RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ, System.String[], System.String, System.String)
       at 9MJVJS0Op_RWoEUtjFFh0i6XF1D7pu8BBz_H2DLdBD4y.MYwNeGOD_3nnjet2W4J1Qjw(System.String[])
       at maddox.Launch.Program(System.String[])
       at Launcher.Program.Main(System.String[])
    Code:
    Application: Launcher64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at <Module>.rts.?A0xf78dec5b.setEffectGain(rts.EFFECTS_NODE*, Int32)
       at GvrAEaiQCsaTWDfv1L3BIjUpzF_5ixJ7$knEUZUtsHPH+mzGiM$1StfeoZYMEqjoX6USSNn7CoU01r6g40DfHswWHYSZLH2QnJ1S$M06_2MaDAY_8ZHpeFjyipCbCwHVEn5c.nSkwFUPXx$MsWNNDwg4J02I(Single)
       at maddox.objects.effects.ForceFeedback.qOzDLZvHVuIRfHyFarYSsXA(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.W4PoHpqEPh6sCwH_SvBfcsLKYxyFvVEILkmOnJeyy3Yb(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.NdtVfBFOUo8sBpHhW4o0nPg(Double)
       at TNKkAcSuawGGAInhdCMgtVB1jZvc_joc87rBU8BjL6yN.vBp10yIv7$PiEY8l9wwBPME(Double)
       at 5VUIhZAfLLjlWb5rvC1y5Il_cwouhW5eZUX_AMML8alS+zHbrQdalUr$0FVVJ70h5H2O7SvcGFYB4EvDP6PMb3RJvqO3gSg71zWPFnl$OVlPSlQ.gT2xRAUYioNJspz1Vabv0$Q()
       at 4lFQrekintdZTkhMfDPtQkRUhCiE4wEk3Y$4KfiOXE3S.gT2xRAUYioNJspz1Vabv0$Q()
       at B3ik9i8vEcErjO61EnV5pr8xSg_fKyjgLBB2LLZAsCag.9pab1TQFb7TOkw5gQ3ntgHA()
       at iIer_m0niFeAfdO$W3iyIyiI$ngG4FHCF6MXe1TJ$JOb.RCg41tE05t0y9dUsvW1Y5dA(Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.s1J6D1WkYrSB0YrRqEzT6Lg(Boolean, Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.bh301Qde8FIoiT4wyRV9J$s(Double, Double)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.fJXDhLsKN6ayoknA3AcuyfM()
       at 29RjLSAReXEUSv0bsMmaiA9zVXLP0ym1LjCepgx5u8k7.WuROX084_l22L6Cx4AzEfnQ()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.pAIf0AEqmWcHUcu2It$ySZs()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.O64GqHFa2fopqVi6EWi5LMNa6pj6LaV7rC9iPR5wvIfY()
    
    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.4RbSSDv13n5tsTfRCBplbDw()
       at RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ.ccgEwiqz06skldTjEnhRh8k(RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ, System.String[], System.String, System.String)
       at 9MJVJS0Op_RWoEUtjFFh0i6XF1D7pu8BBz_H2DLdBD4y.MYwNeGOD_3nnjet2W4J1Qjw(System.String[])
       at maddox.Launch.Program(System.String[])
       at Launcher.Program.Main(System.String[])

    SYSTEM INFORMATION

    Microsoft Windows 10 Pro 64 bit, 10.0.18362 N/A Build 18362
    Total Physical Memory: 20,437 MB
    ASUS GeForce GTX 1060 3GB
    Intel Core i5-2500 Quad-Core Processor 3.3 GHz 6 MB Cache LGA 1155
    Intel DB65AL motherboard
    ARCTIC Freezer i11 CPU Cooler for Intel
    SVGA 500 watt power supply
    Microsoft Sidewinder 2 Force Feedback joystick
    Probably some other things

    I ran a system monitor for quite a while and neither the CPU nor the graphics card ever gets anywhere near the warm range, let alone hot.

    Right now with the game and everything running full tilt the CPU is at 54 degrees & the GPU at 62.

    I usually run the game in Psuedo mode. I tried switching it to Windowed instead and of course it acts exactly the same (crashes until forcefeedback files removed).

  5. Likes ATAG_Torian liked this post
  6. #4
    Ace
    Join Date
    May 2015
    Location
    Kansas City, Missouri area
    Posts
    515
    Post Thanks / Like
    Total Downloaded
    130.02 MB

    Re: Launcher crashes in 4.57 with DMP files

    Looks like I reported this on the bug tracker about a year ago:

    https://tfbt.nuvturais.de/issues/1105

    My speculation at that time was that the crash/freeze happens when the force feedback turns back on after being turned off. This happens quite often as FF turns off whenever you tab out of the game, then turns back on a various specific times in the game when you go back in.
    System: Microsoft Windows 10 Pro 64 bit, 10.0.18362 N/A Build 18362, 20,437 MB |
    ASUS GeForce GTX 1060 3GB | Intel Core i5-2500 Quad-Core Processor 3.3 GHz 6 MB Cache LGA 1155 | Intel DB65AL motherboard | ARCTIC Freezer i11 CPU Cooler | SVGA 500 watt power supply | Microsoft Sidewinder 2 Force Feedback joystick

  7. Likes ATAG_Torian liked this post
  8. #5
    ATAG Member ATAG_Torian's Avatar
    Join Date
    Sep 2011
    Location
    Newcastle, Australia
    Posts
    1,592
    Post Thanks / Like
    Total Downloaded
    108.53 MB

    Re: Launcher crashes in 4.57 with DMP files

    Yes it looks like a good story for a FF issue.
    I haven't owned a FF stick for about 15 years as I found them to be more problematic than helpful.
    It seems that support for FF devices with Microsoft's newer XInput (which supersedes DirectInput) is flakey at best...see here https://en.wikipedia.org/wiki/DirectInput
    Are FF sticks still being made ? If so then maybe a newer one may work better.
    System specs:
    Gaming laptop: Metabox P750ZM, CPU Intel i7-4790K @ 4GHz, GTX 980m with 8Gb DDR5 VRAM, 16Gb Dual channel DDR3 RAM, 2 x Samsung EVO 840 500Gb SSDs, Win10 Home 64bit.

    Gaming PC: MSI PRO Z690 WIFI DDR5 mobo, Intel i5 12600KF cpu, 32Gb Corsair DDR5 5200Mhz RAM, Samsung 980 Pro 1 TB M2 SSD, Corsair 850w psu, MSI RTX 3070 8GB vram vid card, Windows 10 Home 64bit.

  9. #6
    Ace
    Join Date
    May 2015
    Location
    Kansas City, Missouri area
    Posts
    515
    Post Thanks / Like
    Total Downloaded
    130.02 MB

    Re: Launcher crashes in 4.57 with DMP files

    Here is another similar report, even with the special effects/shaking etc disabled, and only "spring.ffe" still enabled:

    Code:
    Application: Launcher64.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at <Module>.rts.?A0xf78dec5b.effectStart(rts.EFFECTS_NODE*)
       at GvrAEaiQCsaTWDfv1L3BIjUpzF_5ixJ7$knEUZUtsHPH+mzGiM$1StfeoZYMEqjoX6USSNn7CoU01r6g40DfHswWHYSZLH2QnJ1S$M06_2MaDAY_8ZHpeFjyipCbCwHVEn5c.0tsuKWJ8RUYenfdALhxW5f0(Int32)
       at maddox.objects.effects.ForceFeedback.x62dvA3NupTvFEUw7p9AUw6a2UU_GwtX_6BOJmFv0$UD(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.W4PoHpqEPh6sCwH_SvBfcsLKYxyFvVEILkmOnJeyy3Yb(Double)
       at qzyn6S1fnNdM1KCowEdjUpN8pMSp6s_V4DDSjCKf5BQ6.NdtVfBFOUo8sBpHhW4o0nPg(Double)
       at TNKkAcSuawGGAInhdCMgtVB1jZvc_joc87rBU8BjL6yN.vBp10yIv7$PiEY8l9wwBPME(Double)
       at 5VUIhZAfLLjlWb5rvC1y5Il_cwouhW5eZUX_AMML8alS+zHbrQdalUr$0FVVJ70h5H2O7SvcGFYB4EvDP6PMb3RJvqO3gSg71zWPFnl$OVlPSlQ.gT2xRAUYioNJspz1Vabv0$Q()
       at 4lFQrekintdZTkhMfDPtQkRUhCiE4wEk3Y$4KfiOXE3S.gT2xRAUYioNJspz1Vabv0$Q()
       at B3ik9i8vEcErjO61EnV5pr8xSg_fKyjgLBB2LLZAsCag.9pab1TQFb7TOkw5gQ3ntgHA()
       at iIer_m0niFeAfdO$W3iyIyiI$ngG4FHCF6MXe1TJ$JOb.RCg41tE05t0y9dUsvW1Y5dA(Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.s1J6D1WkYrSB0YrRqEzT6Lg(Boolean, Boolean)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.bh301Qde8FIoiT4wyRV9J$s(Double, Double)
       at xyxg72wf9bJ567Yz2522U8xGm17btCKoTb8ZxYKhp3sq.fJXDhLsKN6ayoknA3AcuyfM()
       at 29RjLSAReXEUSv0bsMmaiA9zVXLP0ym1LjCepgx5u8k7.WuROX084_l22L6Cx4AzEfnQ()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.pAIf0AEqmWcHUcu2It$ySZs()
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.O64GqHFa2fopqVi6EWi5LMNa6pj6LaV7rC9iPR5wvIfY()
    
    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at AYB56PA7FbyE$$8MFI6r974O4H8hT6AeUdaoTWW4GX4D.4RbSSDv13n5tsTfRCBplbDw()
       at RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ.ccgEwiqz06skldTjEnhRh8k(RIBv6rZ4rWCEDrD_jR11yJglo$kmWoA8pzekY30BkcFZ, System.String[], System.String, System.String)
       at 9MJVJS0Op_RWoEUtjFFh0i6XF1D7pu8BBz_H2DLdBD4y.MYwNeGOD_3nnjet2W4J1Qjw(System.String[])
       at maddox.Launch.Program(System.String[])
       at Launcher.Program.Main(System.String[])
    I'm going to try it next with FF completely disabled and see how that goes.

    FYI as far as I know the only way to turn off FF in CloD is to simply remove the .FF files from parts/core/FF. Seems to work.
    Last edited by TWC_Flug; Feb-09-2020 at 03:32.
    System: Microsoft Windows 10 Pro 64 bit, 10.0.18362 N/A Build 18362, 20,437 MB |
    ASUS GeForce GTX 1060 3GB | Intel Core i5-2500 Quad-Core Processor 3.3 GHz 6 MB Cache LGA 1155 | Intel DB65AL motherboard | ARCTIC Freezer i11 CPU Cooler | SVGA 500 watt power supply | Microsoft Sidewinder 2 Force Feedback joystick

  10. #7
    Ace
    Join Date
    May 2015
    Location
    Kansas City, Missouri area
    Posts
    515
    Post Thanks / Like
    Total Downloaded
    130.02 MB

    Re: Launcher crashes in 4.57 with DMP files

    Quote Originally Posted by ATAG_Torian View Post
    Yes it looks like a good story for a FF issue.
    I haven't owned a FF stick for about 15 years as I found them to be more problematic than helpful.
    It seems that support for FF devices with Microsoft's newer XInput (which supersedes DirectInput) is flakey at best...see here https://en.wikipedia.org/wiki/DirectInput
    Are FF sticks still being made ? If so then maybe a newer one may work better.
    Lots of people still use the MS Sidewinder 2 as there is some feeling that (even now) it is in some sense still the "best" force feedback joystick.

    The error here seems more related to a C# bug, though--something along the lines of "Object reference not set to an instance of an object"?
    System: Microsoft Windows 10 Pro 64 bit, 10.0.18362 N/A Build 18362, 20,437 MB |
    ASUS GeForce GTX 1060 3GB | Intel Core i5-2500 Quad-Core Processor 3.3 GHz 6 MB Cache LGA 1155 | Intel DB65AL motherboard | ARCTIC Freezer i11 CPU Cooler | SVGA 500 watt power supply | Microsoft Sidewinder 2 Force Feedback joystick

  11. #8
    Combat pilot Dawson's Avatar
    Join Date
    Jun 2020
    Location
    Ontario
    Posts
    172
    Post Thanks / Like
    Total Downloaded
    255.83 MB

    Launcher crashes still in 5.032

    I frequently but unpredictably experience this problem just as Flug describes. It may go a couple weeks without happening then will happen twice in the same day.

    It seems to happen when I first spawn in to a new plane or just as I press the trigger to shoot.

    The event in not recorded in the game log but it generates two events in the Windows logs.
    1. Event ID 1000. Faulting event Launcher64.exe, Faulting module KERNELBASE.dll
    2. Event ID 1026. Application: Launcher64.exe, Source .NET Runtime

    Each occurrence generates a dump file as was the case with Flug.

    I also use a Microsoft FFB2 and was beginning to suspect it was force feedback related before I found this thread.

    Was Flug's dump file ever investigated? Would more samples be helpful?
    Last edited by Dawson; Jun-12-2022 at 21:40. Reason: spelling

  12. Likes TWC_Flug liked this post
  13. #9
    Veteran Combat pilot Lorena's Avatar
    Join Date
    Nov 2017
    Location
    São Paulo / Brazil
    Posts
    304
    Post Thanks / Like
    Total Downloaded
    98.49 MB

    Re: Launcher crashes in 4.57 with DMP files

    wierd, i don't remember to have any kind of issue with my ffb2, but i will keep an eye for ffb related errors
    PC: MSI 1080ti Sea Hawk | Gigabyte Z170x Gaming 7 | Intel i5 6600k @4.2gz | Noctua dh-14 |Thermaltake Versa N21 | 32gb Corsair Vengeance LPX ddr4 | Thermaltake tr2 rx 850w | 960evo NVMe SSD 250gb| 2 x 34` LG 34um67 | HyperX Cloud Stinger | Razer Deathadder v2| Trackir 4 | Microsoft ForceFeedback 2 | Ttesports Challenger keyboard |Windows 10 Enterprise x64 |

    VR: REVERB g2 2160x2160 per eye
    Nvidia driver version: 536.23

  14. Likes Dawson liked this post
  15. #10
    Ace
    Join Date
    May 2015
    Location
    Kansas City, Missouri area
    Posts
    515
    Post Thanks / Like
    Total Downloaded
    130.02 MB

    Re: Launcher crashes still in 5.032

    Quote Originally Posted by Dawson View Post
    I frequently but unpredictably experience this problem just as Flug describes. It may go a couple weeks without happening then will happen twice in the same day. . . .

    I also use a Microsoft FFB2 and was beginning to suspect it was force feedback related before I found this thread.

    Was Flug's dump file ever investigated? Would more samples be helpful?
    I don't know that it was ever investigated. But someone working in the code would know a lot better than I!

    I believe one problem is, that no one on the dev team uses a force feedback joystick. That makes testing etc problematic!

    Anyway, I just disabled completely all forcefeedback effects in the game, by removing the FF files as described above.

    Since then I have had ZERO crashes in the game - either 4.5 or 5.0.

    Before that, crashes were pretty regular. So I am very close to 100% convinced that the force feedback code is the cause of the problem.

    FWIW with the sim's FFB turned off, the joystick is limp and floppy, making it almost impossible to fly. To get around that issue I use a little utility called simFFB.

    It is disappointing to lose the forcefeedback effects - particularly the feedback related to speed and stalls was super-helpful in a practical way for piloting, and also a big help for immersiveness etc. But in a way I like the simFFB setup almost better. You can customize the spring, resistance, and damping factors so that the stick has a very realistic yet also very precise feel. You can set up a key to reset the forcefeedback as needed (and that is necessary every time you tab out of and back into the sim - it resets the FFB to zero each and every time) but even better, you can set up a joystick button to recenter the stick at its current position. This is an amazingly simple & precise way to trim out the aircraft. I probably use it 100 times or more every flight.

    It looks like a new/improved/updated version of simFFB is available here - looks even better than the one I'm currently using.

    The one I have been using looks like the version by Jazzerman here. I can definitely recommend Jazzerman's version - the new/improved/updated version looks good, too - I just haven't had a chance to try it.

    The settings I use are spring 76%, damper 40%, friction 16, swap axis (checked), Init dinput (escape - choose some key that is easy to reach in your CloD setup, but not used for anything else), Joystick button 1 (used for instantaneous trimming - obviously you can choose whichever joystick button you prefer), and under the Options menu "Instantaneous trimmer" selected.
    Last edited by TWC_Flug; Dec-12-2022 at 02:47.
    System: Microsoft Windows 10 Pro 64 bit, 10.0.18362 N/A Build 18362, 20,437 MB |
    ASUS GeForce GTX 1060 3GB | Intel Core i5-2500 Quad-Core Processor 3.3 GHz 6 MB Cache LGA 1155 | Intel DB65AL motherboard | ARCTIC Freezer i11 CPU Cooler | SVGA 500 watt power supply | Microsoft Sidewinder 2 Force Feedback joystick

  16. Likes Dawson liked this post
  17. #11
    Veteran Combat pilot Lorena's Avatar
    Join Date
    Nov 2017
    Location
    São Paulo / Brazil
    Posts
    304
    Post Thanks / Like
    Total Downloaded
    98.49 MB

    Re: Launcher crashes in 4.57 with DMP files

    now that i notice that you are still in 4.57

    I am using my ffb2 on the newest 5.034 version and never had any kind of problem or crash
    PC: MSI 1080ti Sea Hawk | Gigabyte Z170x Gaming 7 | Intel i5 6600k @4.2gz | Noctua dh-14 |Thermaltake Versa N21 | 32gb Corsair Vengeance LPX ddr4 | Thermaltake tr2 rx 850w | 960evo NVMe SSD 250gb| 2 x 34` LG 34um67 | HyperX Cloud Stinger | Razer Deathadder v2| Trackir 4 | Microsoft ForceFeedback 2 | Ttesports Challenger keyboard |Windows 10 Enterprise x64 |

    VR: REVERB g2 2160x2160 per eye
    Nvidia driver version: 536.23

  18. #12
    Combat pilot Dawson's Avatar
    Join Date
    Jun 2020
    Location
    Ontario
    Posts
    172
    Post Thanks / Like
    Total Downloaded
    255.83 MB

    Re: Launcher crashes in 4.57 with DMP files

    Flug, thanks for the update. I looked at SimFFB in the past but didn't put it to use. I'll consider it again.

    My notes tell me I disabled all the effects except shake.ffe and spring.ffe. but it didn't help. I may have tried everything disable but I'm not certain.

    I build a new PC in early November I haven't had an issue yet.

    Lorena, the reference to 4.57 is due to the age of the original post.

  19. #13
    Veteran Combat pilot Lorena's Avatar
    Join Date
    Nov 2017
    Location
    São Paulo / Brazil
    Posts
    304
    Post Thanks / Like
    Total Downloaded
    98.49 MB

    Re: Launcher crashes in 4.57 with DMP files

    using windows 11 now?

    since i own a ffb2 and never ever had an issue with il2, hard to find the issue.

    i never installed any 3rd party driver, just plug and play.

    maybe if you do a clean install of windows?
    PC: MSI 1080ti Sea Hawk | Gigabyte Z170x Gaming 7 | Intel i5 6600k @4.2gz | Noctua dh-14 |Thermaltake Versa N21 | 32gb Corsair Vengeance LPX ddr4 | Thermaltake tr2 rx 850w | 960evo NVMe SSD 250gb| 2 x 34` LG 34um67 | HyperX Cloud Stinger | Razer Deathadder v2| Trackir 4 | Microsoft ForceFeedback 2 | Ttesports Challenger keyboard |Windows 10 Enterprise x64 |

    VR: REVERB g2 2160x2160 per eye
    Nvidia driver version: 536.23

  20. #14
    Manual Creation Group DerDa's Avatar
    Join Date
    Apr 2015
    Location
    Heidelberg
    Posts
    2,137
    Post Thanks / Like
    Total Downloaded
    280.96 MB

    Re: Launcher crashes in 4.57 with DMP files

    I had ctd frequently, before using ffb and after. I don't think it is related.
    Absolutely random, sometimes twice a week, sometimes nothing happening for months.
    Had my dumpfiles sent to Artist lat year or so, he just could find out that it was 'something buried deep inside Windows (10)'.
    It always happened when I issued some kind of command by keybard or stick, could be raising the gear or pulling the trigger) but no consistency again.
    It seemed more hassle to me to set up Windows completely from scrap than starting the game anew, when it happened (although I lost a 116 mission campaign on TWC once).
    NVIDIA driver versions might have something to do with it.

    No issues for several months now (knock on a Mosquito).

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •