Print

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

[King_Franky]

Hello,

I bought IL2 1946 via Steam with version 4.13.4

Is it possible to install the VP Modpack for this?

Thank you in advance.

[western0221]

Hello.

I bought IL2 1946 via Steam with version 4.13.4

Is it possible to install the VP Modpack for this?

VP Modpack needs version 4.12.2m game.
And Steam provides 4.12.2m game in Beta version install option.

- Execute Steam Launcher; Open .... Library - Game window.
- Mouse Right button click on IL-2 Sturmovik: 1946 to open sub menu window --- Choose Property.
- In Property screen, choose Beta tab and Install Beta version 4_12_2 in Drop-down menu.
- Your game will become the version 4.12.2m after downloading and installing.

- Copy whole game folder of version 4.12.2m into another place from Steam original.
- Steam main game can be recover into 4.13.4m again by the same way of Beta installation.
- Make another copy of 4.12.2m and install VP Modpack on it. (Keep stock 4.12.2m folder)

[King_Franky]

Ah, thank you very much for your quick reply.

I will do so.

[vpmedia]

what mods should be deleted from VP

!!00_0_FXEvolution_v4.12
!CTO_Modact5

are not compatible with SAS engine mod

[blackshark]

Hi VPmedia, I am enjoying your great modpack

I have two questions about it:

a) I installed the Configurable MaxVisualDistance Mod (https://www.sas1946.com/main/index.php/topic,57401.0.html) to increase the distance for objects & effects; may I ask you which are "visual distance" parameters of VPmodpack without that mod ?

b) I see that for effects you use the two FXevolution mod; just to better understand, if I should disable them (with "-") i would have the "stock/default" effects of 4.12 ?

best regards

[vpmedia]

a) Smoke distance is around 3km in the stock game iirc. No clue about the rest to be honest.

b) Do not disable "!!00_0_FXEvolution_v4.12_Independent static smoke and fire".
If you disable the other effects folder I mentioned, you'll have the stock effects back.

[Joe_Vochy]

Hello pilots.

I returned to IL2 1946 after some years and tried to improve it using this nice looking VP Modpack.
However, unfortunately I got some trouble with installation.

IL2 is from Steam.
I changed the version (using Beta testing option) to 4.12.2. Made a copy to other folder. Test of start OK.
I copied the pack into the folder and added lines into the conf.ini. Start failed. Just some short trial visible as a blink of some welcome picture, but then nothing...

Here is the log from initlog.lst

2019-01-14 22:50:57:706 (dinput.dll) : IL-2 Process ID = 00002228
2019-01-14 22:50:57:706 (dinput.dll) : Starting Watchdog at D:\Hry\IL-2 Sturmovik 1946\bin\selector\basefiles\IL-2 Watchdog.exe
2019-01-14 22:50:57:716 (dinput.dll) : Watchdog process started.
2019-01-14 22:50:57:716 (dinput.dll) : JVM Parameters injector activated
2019-01-14 22:50:57:716 (dinput.dll) : Applying JVM Memory Settings from IL-2 Selector...
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Xms444M
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Xmx444M
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Xss4096K
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -XX:PermSize=64M
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -XX:MaxPermSize=64M
2019-01-14 22:50:57:716 (dinput.dll) : Checking duplicate JVM Options...
2019-01-14 22:50:57:716 (dinput.dll) : Checking mandatory JVM Options...
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Djava.class.path=.
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Xincgc
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Xverify:none
2019-01-14 22:50:57:716 (dinput.dll) : Adding JVM Option: -Xcomp
2019-01-14 22:50:57:716 (dinput.dll) : Final JVM Option List:
2019-01-14 22:50:57:716 (dinput.dll) : -Xms444M
2019-01-14 22:50:57:716 (dinput.dll) : -Xmx444M
2019-01-14 22:50:57:716 (dinput.dll) : -Xss4096K
2019-01-14 22:50:57:716 (dinput.dll) : -XX:PermSize=64M
2019-01-14 22:50:57:716 (dinput.dll) : -XX:MaxPermSize=64M
2019-01-14 22:50:57:716 (dinput.dll) : -Djava.class.path=.
2019-01-14 22:50:57:716 (dinput.dll) : -Xincgc
2019-01-14 22:50:57:716 (dinput.dll) : -Xverify:none
2019-01-14 22:50:57:716 (dinput.dll) : -Xcomp
2019-01-14 22:50:57:736   (watchdog) : IL-2 Parent Process Handle = 00000084, ID=00002228
2019-01-14 22:50:57:736   (watchdog) : IL-2 Watchdog started.
2019-01-14 22:50:57:736   (watchdog) : Message Window Created.
2019-01-14 22:50:57:796 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated, injecting JVM Parameters
2019-01-14 22:50:57:796 (dinput.dll) : JVM Parameters injector deactivated

Please, do you have and idea how to solve this problem?

I have also tried to switch the Stock version of IL2 using Selector, but also no success.
After that I copied the patch, but no start again...

Thank you very much.

[vpmedia]

The initlog.lst is not useful, log.lst is the one we need:
https://www.sas1946.com/main/index.php/topic,13457.0.html

[western0221]

I cannot figure out what happened on Joe_Vochy's PC and IL-2 1946 folder,
but his initlog.lst looks il2fb.exe is not executed, log.lst might not be generated.
His trouble might be a previous stage one of it.


When IL2Selector and SASModAct succeed to execute il2fb.exe , initlog.lst has those lines

Code: [Select]

2019-01-14 12:01:21:617   (watchdog) : IL-2 Parent Process Handle = 00000080, ID=00002698
2019-01-14 12:01:21:617   (watchdog) : IL-2 Watchdog started.
2019-01-14 12:01:21:617   (watchdog) : Message Window Created.
2019-01-14 12:01:21:617 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated, injecting JVM Parameters
2019-01-14 12:01:21:648 (dinput.dll) : JVM Parameters injected successfully
2019-01-14 12:01:21:648    (wrapper) : ProcessAttach, attached Processes =  1
2019-01-14 12:01:21:648    (wrapper) : Calling GetCommandLineParams()
2019-01-14 12:01:21:648    (wrapper) : MODS Folder = "#SAS"
2019-01-14 12:01:21:648    (wrapper) : No FILES Folder set.
2019-01-14 12:01:21:648    (wrapper) : Calling LinkIl2fbExe()
2019-01-14 12:01:21:648    (wrapper) : Trying to link back to S:\IL-2 Sturmovik 1946 4.12.2m SASModAct\il2fb.exe through LoadLibrary()
2019-01-14 12:01:21:648    (wrapper) : Calling CreateModsFolderList()
2019-01-14 12:01:21:726   (watchdog) : Splash Screen Created.
2019-01-14 12:01:23:069    (wrapper) : Scanning #SAS folder took 1420 milliseconds.
2019-01-14 12:01:23:069    (wrapper) : Total number of modded files = 117711.
instead of his

Code: [Select]

2019-01-14 22:50:57:736   (watchdog) : IL-2 Parent Process Handle = 00000084, ID=00002228
2019-01-14 22:50:57:736   (watchdog) : IL-2 Watchdog started.
2019-01-14 22:50:57:736   (watchdog) : Message Window Created.
2019-01-14 22:50:57:796 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated, injecting JVM Parameters
2019-01-14 22:50:57:796 (dinput.dll) : JVM Parameters injector deactivated

[Joe_Vochy]

Dear vpmedia, dear western0221, thanks for your effort.

There is no initlog.lst file in the IL2 folder root.

Here is the initlog.lst after start trial with final configuration including the path

2019-01-15 19:56:21:862 (dinput.dll) : IL-2 Process ID = 00001E00
2019-01-15 19:56:21:862 (dinput.dll) : Starting Watchdog at D:\Hry\IL-2 Sturmovik 1946\bin\selector\basefiles\IL-2 Watchdog.exe
2019-01-15 19:56:21:893 (dinput.dll) : Watchdog process started.
2019-01-15 19:56:21:909 (dinput.dll) : JVM Parameters injector activated
2019-01-15 19:56:21:909 (dinput.dll) : Applying JVM Memory Settings from IL-2 Selector...
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Xms444M
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Xmx444M
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Xss4096K
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -XX:PermSize=64M
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -XX:MaxPermSize=64M
2019-01-15 19:56:21:909 (dinput.dll) : Checking duplicate JVM Options...
2019-01-15 19:56:21:909 (dinput.dll) : Checking mandatory JVM Options...
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Djava.class.path=.
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Xincgc
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Xverify:none
2019-01-15 19:56:21:909 (dinput.dll) : Adding JVM Option: -Xcomp
2019-01-15 19:56:21:909 (dinput.dll) : Final JVM Option List:
2019-01-15 19:56:21:909 (dinput.dll) : -Xms444M
2019-01-15 19:56:21:909 (dinput.dll) : -Xmx444M
2019-01-15 19:56:21:909 (dinput.dll) : -Xss4096K
2019-01-15 19:56:21:909 (dinput.dll) : -XX:PermSize=64M
2019-01-15 19:56:21:909 (dinput.dll) : -XX:MaxPermSize=64M
2019-01-15 19:56:21:909 (dinput.dll) : -Djava.class.path=.
2019-01-15 19:56:21:909 (dinput.dll) : -Xincgc
2019-01-15 19:56:21:909 (dinput.dll) : -Xverify:none
2019-01-15 19:56:21:909 (dinput.dll) : -Xcomp
2019-01-15 19:56:21:924   (watchdog) : IL-2 Parent Process Handle = 00000084, ID=00001E00
2019-01-15 19:56:21:924   (watchdog) : IL-2 Watchdog started.
2019-01-15 19:56:21:924   (watchdog) : Message Window Created.
2019-01-15 19:56:21:971 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated, injecting JVM Parameters
2019-01-15 19:56:22:034   (watchdog) : Splash Screen Created.
2019-01-15 19:56:22:034 (dinput.dll) : JVM Parameters injector deactivated

I will try to check also the Windows log and think about some other clues...
Of course, eat stills much appreciated. Thank you.


Joe, Czech RAF Crew

[Joe_Vochy]

Yesterday I checked the log of Windows events & errors, but it seems, there is nothing related to failed start of IL2...
Theoretically - could have the antivirus or firewall have an influence on such type of operation? I use Avast and Comodo. Will try to switch them off for a test.

[Groovy Greensnack]

I have done some thorough checking of at what point in the install this mod will fail to launch and it seems that it's the patch after the conf.ini edits that is causing the failures to launch. I downloaded the two in one patch from google drive linked in the op.