Official Fulqrum Publishing forum - Il-2 Sturmovik: Cliffs of Dover: Patch 1.00.14072 -ARIL 15

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)

- IL-2 Sturmovik: Cliffs of Dover (http://forum.fulqrumpublishing.com/forumdisplay.php?f=189)

- - Il-2 Sturmovik: Cliffs of Dover: Patch 1.00.14072 -ARIL 15 (http://forum.fulqrumpublishing.com/showthread.php?t=21452)

Jumping the camera through the enemy aircraft quickly when they're spaced out can crash the game now. Only bug so far in an otherwise great patch.

The Beta patch is great.. incorporated everything I was using formally into the GUI and the games immersion level if off the charts. Things I noticed

-The new Neg G Cut Out.. hate it..you really need to unt the nose over to get any kind of effect and even then it doesn't give you the sputting and black smoke.. I thought the original version was better.. But I would defer to whatever you found is the accurate effect at the accurate G loadings..

-Multiplayer on a server with a decent number of other players is incredible. The GUI to get there is a lot better but still needs work.. new pilots would be lost trying to figure out how to "fly".. even the final button press to launch can only be found if you scroll down a window.. Im sure a lot of people would not be able to find it.

Brakes and other axis control dont work on British planes.
They do on German aircraft.
No weep warning if it's on and working or not

ANDx3 2.8g 4g RAM
ATI 4850 HD
Win 7 HP 64bit

Quote:

Originally Posted by FS~Hawks (Post 265792)

Brakes and other axis control dont work on British planes.
They do on German aircraft.
No weep warning if it's on and working or not

There is no differential brakes on hurri and spit, use b instead

FPS and stuttering improved with beta patch.

However now getting CTDs which never happened with any previous build. My gut feeling is that they occur when there's a LOD switch and new textures are loaded. But it could just be coincidence and the fault is more general and connected to the new texture manager or something entirely different I don't know, lol, you're the developers!

There were 5 crashes since the patch was installed. I compared each .NET runtime dump with Winmerge and they are identical. Each one shows this:

Code:

Application: Launcher.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.Reflection.TargetInvocationException

Stack:

   at System.RuntimeMethodHandle._InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)

   at System.RuntimeMethodHandle.InvokeMethodFast(System.IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)

   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)

   at System.Delegate.DynamicInvokeImpl(System.Object[])

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.DispatcherOperation.InvokeImpl()

   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)

   at System.Threading.ExecutionContext.runTryCode(System.Object)

   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   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 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 MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.Dispatcher.InvokeImpl(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 System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)

   at AP9wCW2FvcllVvheGMp.mUneEX2pyKjk8Iw3C66.JTm2u1My4G7()

   at 9i0ieD2xV3vXGAmqlmL.BxYNQL2wg67OCFGEde3.tSuIdoton0CC2J2A9X3e(System.Object)

   at 9i0ieD2xV3vXGAmqlmL.BxYNQL2wg67OCFGEde3.BCVjupJrgHY(9i0ieD2xV3vXGAmqlmL.BxYNQL2wg67OCFGEde3, System.String[], System.String, System.String)

   at wL55x3Ne14YNTY9Ts2M.wg85OyNvygcfjBvDied.Tht7aGWctSr(System.String[])

   at maddox.Launch.Program(System.String[])

   at Launcher.Program.Main(System.String[])

The accompanying 5 Application Error dumps were also identical for "Faulting Module Name", "Exception Code:" and "Fault Offset".

Code:

Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7bafa

Exception code: 0xe0434352

Fault offset: 0x0000b727

Faulting process id: 0x10ec

Faulting application start time: 0x01cbfc7774ed150f

Faulting application path: e:\games\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

Report Id: e844c41d-6872-11e0-a4ae-00241dcfe9f5

Enjoying the simulation a lot until these crashes started. Keep the realism!

game hangs up when pressing shift+f2 to switch between the planes

Quote:

Originally Posted by ICDP (Post 265446)

Now go try a flight over Le-Havre (the Free Flight 109 over Normandy in quick missions). For me (and many others) there is a serious FPS hit in areas with industrial complexes.

Hi ICDP,

You're right, the industrial buildings at Le Havre apparently have a bigger impact performance-wise than central London. Perhaps those building types have not yet been optimized.

I get around 20-25 FPS with severe stuttering over that area (game visuals all at High). Regular housing areas don't give this amount of stuttering anymore.

Quote:

Originally Posted by Krähe (Post 265752)

Hello SQB, I just extracted the whole contents to steam/steamapps/common/cod and it worked fine, just say yes when windows asks you to overwrite, hope this helps.

cheers... but...
Turns out that was accidentally the RU version, so I went from the beginning with my backup and downloaded the regular version. But then I get "unexpect end of archive" ninja'd in by the guy who posted before me.

I'm gonna try the rapidshare/megaupload locations but this is weird and annoying :(

If i remember correct, before patch industrial building doesent hurts my fps like now.

Quote:

Originally Posted by Deadstick (Post 265667)

After installing the patch, the game no longer loads for me. :-x

I get the cross-hair flash up then nothing, guess I will wait until it is pushed through on Monday.

Same here.

I see the file sizes on 1C download for eng patch and megaupload also are different? RS link dead.

Anyone have another mirror with a patch I can try?