Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fightingirish]

I would like to know if anyone is still having trouble with pulling on take off with the latest version.

Yep still pulling in a tight circle when attempting to take off

[mandrill]

Yep still pulling in a tight circle when attempting to take off

Are you sure that you selected "all engines" after cranking up engine #2?

[CWatson]

Are you sure that you selected "all engines" after cranking up engine #2?

I was wondering the same. Bombsaway has tested them in both DBW
(410) and 412 and his results are the same as mine in 409, no longer pulls, unless "all engines" is not selected when throttle is applied.

I wonder how many do not have a pulling issue?

Thanks for the input,
                             CW

[SAS~Bombsaway]

There are several factors that may be causing the issue and from what I have found they are all pilot error.

1- When the plane starts out on scramble mission the tail wheel is turned slightly so if you are in cockpit view and lock your tail wheel, the plane will turn to the left. You need to pull the plane forward a bit and the tail wheel will straighten out. Then you can lock it.

2- When you start your engines, after starting the second engine make sure you have hit the key for " Select all engines" or only one will power up and you will pull to one side. You can check to make sure both are powering up by looking at the RPM gauges in the cockpit. Top two center. If both are moving then you have selected both engines.

3- If your throttle is not at zero % when you start a scramble mission and then you back it to zero then start engines, sometimes the game still reads it at a powered throttle and the plane will turn.

4- If you have trim on your stick and it is not zeroed out then that can cause pull as well.

As CWatson said, I tested in both 4.10 and 4.12 and I made the above mistakes at fiirst and then after correcting them, pilot error, the plane, both versions, will take off correctly.

[CWatson]

 One of the issues seems to be the angle of the tail wheel when a mission is stared on the ground.
I have altered the classfile so the default  position is strait when mission starts on the ground.

Here is the new classfile here for those who want to try it now:
https://www.mediafire.com/download/zz7h8bsgn84d0v0/class.rar


It will be included with other changes in the next update.


Thanks again,
                    CW

[Benno]

C.Watson

I installed your upgrade and had a go.   The Mk7 ground handling is fine now. During takeof run in a Mk5 I wanted to do a SD and got a CTD and this text

Code: [Select]

______________________________________________________________
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x69e55390
Function name=(N/A)
Library=C:\WINDOWS\system32\atioglxx.dll

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.



Current Java thread:
at com.maddox.opengl.gl.ReadPixels(Native Method)
at com.maddox.opengl.util.ScrShot.grab(ScrShot.java:33)
at com.maddox.il2.game.Main3D$4.begin(Main3D.java:2730)
at com.maddox.rts.HotKeyCmd.start(HotKeyCmd.java:103)
at com.maddox.rts.HotKeyEnv.startCmd(HotKeyEnv.java:247)
at com.maddox.rts.HotKeyEnv.keyPress(HotKeyEnv.java:286)
at com.maddox.rts.HotKey.msgKeyboardKey(HotKey.java:119)
at com.maddox.rts.MsgKeyboard.invokeListener(MsgKeyboard.java:83)
at com.maddox.rts.Message._send(Message.java:1217)
at com.maddox.rts.Message.sendToObject(Message.java:1191)
at com.maddox.rts.Message.sendToArray(Message.java:1147)
at com.maddox.rts.Message.sendTo(Message.java:1128)
at com.maddox.rts.Message.trySend(Message.java:1115)
at com.maddox.rts.Time.loopMessages(Time.java:252)
at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:100)
at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:131)
at com.maddox.il2.game.Main.exec(Main.java:436)
at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)

Dynamic libraries:
0x00400000 - 0x0049A000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\il2fb.exe
0x7C900000 - 0x7C9B1000 C:\WINDOWS\system32\ntdll.dll
0x7C800000 - 0x7C8FA000 C:\WINDOWS\system32\kernel32.dll
0x7E360000 - 0x7E3F1000 C:\WINDOWS\system32\USER32.dll
0x77F10000 - 0x77F59000 C:\WINDOWS\system32\GDI32.dll
0x77DC0000 - 0x77E6B000 C:\WINDOWS\system32\ADVAPI32.dll
0x77E70000 - 0x77F02000 C:\WINDOWS\system32\RPCRT4.dll
0x77FE0000 - 0x77FF1000 C:\WINDOWS\system32\Secur32.dll
0x76B30000 - 0x76B5E000 C:\WINDOWS\system32\WINMM.dll
0x76370000 - 0x7638D000 C:\WINDOWS\system32\IMM32.dll
0x10000000 - 0x1001E000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\DINPUT.dll
0x72250000 - 0x7227B000 C:\WINDOWS\system32\dinput.dll
0x77C00000 - 0x77C58000 C:\WINDOWS\system32\msvcrt.dll
0x6D420000 - 0x6D4EF000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\hotspot\jvm.dll
0x6D220000 - 0x6D227000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\verify.dll
0x6D250000 - 0x6D266000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\java.dll
0x6D3C0000 - 0x6D3CD000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\zip.dll
0x06C90000 - 0x06CD9000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\wrapper.dll
0x77110000 - 0x7719B000 C:\WINDOWS\system32\OLEAUT32.DLL
0x774D0000 - 0x7760D000 C:\WINDOWS\system32\ole32.dll
0x07BE0000 - 0x07BEA000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\pathfind.dll
0x07BF0000 - 0x0AACA000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\il2_corep4.dll
0x7C340000 - 0x7C396000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\MSVCR71.dll
0x0AAD0000 - 0x0AAF3000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\jgl.dll
0x0B630000 - 0x0B66A000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\il2_usgs2.dll
0x71A80000 - 0x71A97000 C:\WINDOWS\system32\WS2_32.dll
0x71A70000 - 0x71A78000 C:\WINDOWS\system32\WS2HELP.dll
0x0BE80000 - 0x0BEF1000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\mg_snd_sse.dll
0x0CF10000 - 0x0CF49000 C:\WINDOWS\system32\dinput8.dll
0x68E60000 - 0x68E69000 C:\WINDOWS\system32\HID.DLL
0x77910000 - 0x77A05000 C:\WINDOWS\system32\SETUPAPI.DLL
0x76C20000 - 0x76C4E000 C:\WINDOWS\system32\WINTRUST.dll
0x77A70000 - 0x77B06000 C:\WINDOWS\system32\CRYPT32.dll
0x77B10000 - 0x77B22000 C:\WINDOWS\system32\MSASN1.dll
0x76C80000 - 0x76CA8000 C:\WINDOWS\system32\IMAGEHLP.dll
0x6D340000 - 0x6D348000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\net.dll
0x71AA0000 - 0x71AAA000 C:\WINDOWS\system32\WSOCK32.dll
0x71A20000 - 0x71A60000 C:\WINDOWS\System32\mswsock.dll
0x76F10000 - 0x76F37000 C:\WINDOWS\system32\DNSAPI.dll
0x76D50000 - 0x76D69000 C:\WINDOWS\system32\iphlpapi.dll
0x76FA0000 - 0x76FA8000 C:\WINDOWS\System32\winrnr.dll
0x76F50000 - 0x76F7D000 C:\WINDOWS\system32\WLDAP32.dll
0x5F210000 - 0x5F2DC000 C:\WINDOWS\system32\Opengl32.dll
0x61AE0000 - 0x61B01000 C:\WINDOWS\system32\GLU32.dll
0x73710000 - 0x7375B000 C:\WINDOWS\system32\DDRAW.dll
0x73B70000 - 0x73B76000 C:\WINDOWS\system32\DCIMAN32.dll
0x75190000 - 0x751BE000 C:\WINDOWS\system32\msctfime.ime
0x69030000 - 0x6A1BA000 C:\WINDOWS\system32\atioglxx.dll
0x77BF0000 - 0x77BF8000 C:\WINDOWS\system32\VERSION.dll
0x0E320000 - 0x0E353000 C:\WINDOWS\system32\atiadlxx.dll
0x7C9C0000 - 0x7D1DA000 C:\WINDOWS\system32\SHELL32.dll
0x77F60000 - 0x77FD6000 C:\WINDOWS\system32\SHLWAPI.dll
0x78130000 - 0x781CB000 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e6967989\MSVCR80.dll
0x773C0000 - 0x774C3000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll
0x5D5A0000 - 0x5D63A000 C:\WINDOWS\system32\comctl32.dll
0x73EC0000 - 0x73F1C000 C:\WINDOWS\system32\dsound.dll
0x72CD0000 - 0x72CD9000 C:\WINDOWS\system32\wdmaud.drv
0x72CC0000 - 0x72CC8000 C:\WINDOWS\system32\msacm32.drv
0x77BD0000 - 0x77BE5000 C:\WINDOWS\system32\MSACM32.dll
0x77BC0000 - 0x77BC7000 C:\WINDOWS\system32\midimap.dll
0x73E90000 - 0x73E94000 C:\WINDOWS\system32\KsUser.dll
0x76090000 - 0x76198000 G:\Programmer\Ubisoft\IL-2 Sturmovik 1946\bin\awt.dll
0x533F0000 - 0x53416000 C:\WINDOWS\system32\WINSPOOL.DRV
0x71930000 - 0x719D1000 C:\WINDOWS\system32\DBGHELP.dll
0x76BE0000 - 0x76BEB000 C:\WINDOWS\system32\PSAPI.DLL

Local Time = Tue May 27 17:21:50 2014
Elapsed Time = 1944
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 compiled mode)
#
----------------------------------------------------------------------I don't know,  but is it a Graphics driver issue ??????????

Im using 4.09m/2.1.
Thank you for your  attension to this.
Benno

[CWatson]

Benno,
thanks for the input.

The classfile alteration I did was for the mother class that both share. Neither MkV or MkVII's classfile was  touched, so if one works, both should.

[Stainless]

Benno that is a crash in glReadPixels

The game code looks fine.

Is it a repeatable crash?

[Birdman]

Benno, that crash might be due to Java memory limits. Old versions of modded IL-2 can crash like that when they have a lot of planes installed and then get above Java memory limits while taking screenshots. This can be fixed by either removing some planes or using modern IL-2 version selector ( https://www.sas1946.com/main/index.php?topic=16403.0 ) that can increase those memory limits and prevent such crashes.

[Benno]

Hi' Birdman  & Stainless
Thank you very much for your input.  I use C.Watsons  class file fix and that has fixed the issues 
Benno

[Benno]

Hi'
I do use the latest of IL-2Selector .
Benno

[Epervier]

Last version work fine in my UP2 ! 
Thank you very much Cwatson, Gio963TTo, Barnesy12, Stanislao, ...