Print

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

[Frankiek]

Yep, that's a valid one.
This line is what sparks my interest:

Code: [Select]

Java max RAM = 1380M, Selector Auto Adjusted RAM Size = 1311MBackground: The new Selector doesn't just "guess" the maximum RAM size, it simply tries what works and what doesn't.
It is quite surprising to see that on Win XP, java.exe comes up with a max RAM setting of 1380M, but IL-2 fails to launch (from the same Java folder, just using JVM.dll instead of java.exe, which should make no difference) with even half that size.
Definitely something to dig deeper into...


Mike

I am very surprised that it actually works using max RAM 1380 as with selector 5.1.2 I have to set the memory at 512 (with 768 the system works but is very unstable and with 1024 will crash very quickly)

[SAS~Storebror]

Specs for my main PC and initlog.lst for 512/128.

Something's wrong with your il2fb.ini.
If the settings was 512/128, these lines (like shown in Frankie's log) should come up:

Code: [Select]

(...)
2024-12-19 17:08:08:078 (dinput.dll) : Final JVM Option: -Xmx512M
(...)
2024-12-19 17:08:08:078 (dinput.dll) : Final JVM Option: -XX:MaxPermSize=128M
(...)
In your case they read:

Code: [Select]

(...)
2024-12-19 17:08:08:078 (dinput.dll) : Final JVM Option: -Xmx1057M
(...)
2024-12-19 17:08:08:078 (dinput.dll) : Final JVM Option: -XX:MaxPermSize=528M
(...)...and that's the auto adjusted setting when no explicit 512/128 setting is available in il2fb.ini


Mike

[genXgamer]

Ran through it once more.

Copy and pasted entries at the bottom of the il2fb.ini
Saved file then reopened it to check that it saved.
Opened the Selector and checked the auto adjust box.
Saved settings and pressed start now button.
Game doesn't launch.
Open il2fb.ini and entries are gone.

[Frankiek]

Entering the memory parameters in IL2fb.ini is not sufficient. Open the selector and click on the expert mode box then enter the parameters in the box below finally save and launch.

[Frankiek]

Just to let you know that out of curiosity I have applied the same JVM parameters 512/128 also to the 5.1.2 Selector and I notice a clear improvement in performance.

I checked the initlog and noticed that the  Final JVM Option: -XX:MaxPermSize=128M is the double to the one if I have when launching the selector without this parameter. On the other side the -Xmx increase is from 444M to 512M.

To make this test I have used the two version of the selector on UP2, UP3.4 and Stock 4.09, 4.10.1  and 4.12.2 with same conf.ini and using the BlackDeath track as benchmarck.

The results are very consistent with increased FPS and smoother reproduction of the track. Overall I didn't noticed any significative difference in performance between selector 5.2.2 and 5.1.2 when the memory tweaking is applied.
For what is worth stock 4.09 was the best performer followed by UP3.4

[genXgamer]

Thanks mate!

Java Virtual Machine Initialization with additional parameters successful!

That additional info worked, I now have B.A.T. 4.3 (Windows XP) launching with Auto Adjust selected.
The Selector documentation needs updating, I would never have touched that Additional JVM Parameters box without clear instruction.

Now I need Mike to take a look at the initlog.lst and tell me if everything is working as it should.

EDIT:  There is no need to enter the entries to the il2fb.ini, simply add to Additional JVM Parameters box and it saves to the il2fb.ini.
The initial 700/250 also launches but with Russian Paratroopers error so I'll be sticking with 512/128 for the time being.

Code: [Select]

2024-12-21 09:27:49:390 (dinput.dll) : JVM Parameters injector activated
2024-12-21 09:27:49:437 (dinput.dll) : ReadJvmOptions()
2024-12-21 09:27:49:453 (dinput.dll) : Checking for presence of JVM Option: -xmx
2024-12-21 09:27:49:484 (dinput.dll) : Added JVM Option: -Xmx512M
2024-12-21 09:27:49:500 (dinput.dll) : Adding JVM Option from Ini: -Xmx512M
2024-12-21 09:27:49:531 (dinput.dll) : Checking for presence of JVM Option: -xx:maxpermsize=
2024-12-21 09:27:49:546 (dinput.dll) : Added JVM Option: -XX:MaxPermSize=128M
2024-12-21 09:27:49:578 (dinput.dll) : Adding JVM Option from Ini: -XX:MaxPermSize=128M
2024-12-21 09:27:49:593 (dinput.dll) : IL-2 Process ID = 00000474
2024-12-21 09:27:49:625 (dinput.dll) : Starting Watchdog at H:\B.A.T. 4.3 Clean\bin\selector\basefiles\IL-2 Watchdog.exe 0 ""
2024-12-21 09:27:49:640 (dinput.dll) : Watchdog process started.
2024-12-21 09:27:49:671 (dinput.dll) : Starting Pipe Logger at H:\B.A.T. 4.3 Clean\bin\selector\basefiles\PipeLogger.exe
2024-12-21 09:27:49:703 (dinput.dll) : PipeLogger process started.
2024-12-21 09:27:49:750 (dinput.dll) : Attach SAS_CreateJavaVM = OK
2024-12-21 09:27:49:765   (watchdog) : IL-2 Parent Process Handle = 00000040, ID=00000474
2024-12-21 09:27:49:796 (PipeLogger) : PipeLogger Starting
2024-12-21 09:27:49:796 (dinput.dll) : Attach SAS_SFS_mount = OK
2024-12-21 09:27:49:843 (PipeLogger) : Reading PipeLogger Settings from H:\B.A.T. 4.3 Clean\il2fb.ini
2024-12-21 09:27:49:890 (PipeLogger) : PipeLogger Settings:
2024-12-21 09:27:49:921 (PipeLogger) : ShowLogWarnings = false
2024-12-21 09:27:49:875 (dinput.dll) : AdjustJvmParams: Mod Flag NOT set!
2024-12-21 09:27:49:828   (watchdog) : IL-2 Watchdog started.
2024-12-21 09:27:49:953 (PipeLogger) : LogSizeThreshold = 10,000,000 Bytes
2024-12-21 09:27:50:031 (PipeLogger) : ExceptionThreshold = 10 Exceptions
2024-12-21 09:27:50:046 (PipeLogger) : ErrorThreshold = 0 Errors
2024-12-21 09:27:50:000   (watchdog) : Splash Screen Mode = 0
2024-12-21 09:27:50:078 (PipeLogger) : PipeLogger Process ID: 00000CBC; Parent (IL-2) Process ID: 00000474
2024-12-21 09:27:50:109   (watchdog) : Splash Screen Image Path =
2024-12-21 09:27:50:125 (PipeLogger) : Listener thread awaiting client connection on \\.\pipe\SAS_PIPE_LOGGER
2024-12-21 09:27:50:156 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated
2024-12-21 09:27:50:156   (watchdog) : Splash Screen Image Full Path = H:\B.A.T. 4.3 Clean
2024-12-21 09:27:50:265   (watchdog) : Message Window Created.
2024-12-21 09:27:50:437 (dinput.dll) : Java max RAM = 1670M, Selector Auto Adjusted RAM Size = 1586M
2024-12-21 09:27:50:531 (dinput.dll) : Applying JVM Memory Settings from IL-2 Selector...
2024-12-21 09:27:50:562 (dinput.dll) : Checking for presence of JVM Option: -xms
2024-12-21 09:27:50:578 (dinput.dll) : Added JVM Option: -Xms96M
2024-12-21 09:27:50:609 (dinput.dll) : Checking for presence of JVM Option: -xss
2024-12-21 09:27:50:640 (dinput.dll) : Added JVM Option: -Xss1024K
2024-12-21 09:27:50:656 (dinput.dll) : Checking mandatory JVM Options...
2024-12-21 09:27:50:687 (dinput.dll) : Checking for presence of JVM Option: -djava.class.path=
2024-12-21 09:27:50:703 (dinput.dll) : Added JVM Option: -Djava.class.path=.
2024-12-21 09:27:50:734 (dinput.dll) : Checking for presence of JVM Option: -xverify:none
2024-12-21 09:27:50:765 (dinput.dll) : Added JVM Option: -Xverify:none
2024-12-21 09:27:50:781 (dinput.dll) : Checking for presence of JVM Option: -xcomp
2024-12-21 09:27:50:812 (dinput.dll) : Added JVM Option: -Xcomp
2024-12-21 09:27:50:843 (dinput.dll) : Checking for presence of JVM Option: -xnoclassgc
2024-12-21 09:27:50:859 (dinput.dll) : Added JVM Option: -Xnoclassgc
2024-12-21 09:27:50:890 (dinput.dll) : OpenGL Mode detected, checking IL-2 Graphics Extender Availability...
2024-12-21 09:27:50:906 (dinput.dll) : Trying H:\B.A.T. 4.3 Clean\il2ge.dll
2024-12-21 09:27:50:937 (dinput.dll) : Trying H:\B.A.T. 4.3 Clean\il2ge\lib\il2ge.dll
2024-12-21 09:27:50:953 (dinput.dll) : Trying H:\B.A.T. 4.3 Clean\bin\selector\basefiles\il2ge.dll
2024-12-21 09:27:50:984 (dinput.dll) : IL-2 Graphics Extender not available.
2024-12-21 09:27:51:000 (dinput.dll) : Injecting JVM Parameters
2024-12-21 09:27:51:031 (dinput.dll) : Final JVM Option: -Djava.class.path=.
2024-12-21 09:27:51:046 (dinput.dll) : Final JVM Option: -Xcomp
2024-12-21 09:27:51:078 (dinput.dll) : Final JVM Option: -Xms96M
2024-12-21 09:27:51:109 (dinput.dll) : Final JVM Option: -Xmx512M
2024-12-21 09:27:51:125 (dinput.dll) : Final JVM Option: -Xnoclassgc
2024-12-21 09:27:51:156 (dinput.dll) : Final JVM Option: -Xss1024K
2024-12-21 09:27:51:171 (dinput.dll) : Final JVM Option: -Xverify:none
2024-12-21 09:27:51:203 (dinput.dll) : Final JVM Option: -XX:MaxPermSize=128M
2024-12-21 09:27:51:234 (dinput.dll) : Java Virtual Machine Initialization with additional parameters successful!
2024-12-21 09:27:51:265    (wrapper) : ProcessAttach, attached Processes =  1
2024-12-21 09:27:51:296    (wrapper) : Calling getCommandLineParams()
2024-12-21 09:27:51:312    (wrapper) : MODS Folder = "#WAW3"
2024-12-21 09:27:51:343    (wrapper) : No FILES Folder set
2024-12-21 09:27:51:359    (wrapper) : Calling linkIl2fbExe()
2024-12-21 09:27:51:390    (wrapper) : Trying to link back to H:\B.A.T. 4.3 Clean\il2fb.exe through LoadLibrary()
2024-12-21 09:27:51:406    (wrapper) : Calling createModsFolderList()
2024-12-21 09:27:52:234    (wrapper) : Scanning #WAW3 folder took 801 milliseconds.
2024-12-21 09:27:52:265    (wrapper) : Total number of modded files = 18042.
2024-12-21 09:27:52:281    (wrapper) : Calling sortList()
2024-12-21 09:27:52:312    (wrapper) : Sorting modded files list took 5.140 milliseconds.
2024-12-21 09:27:52:343    (wrapper) : Calling removeDuplicates()
2024-12-21 09:27:52:359    (wrapper) : Removing 3 Duplicates took 0.286 milliseconds.
2024-12-21 09:27:57:265   (watchdog) : IL-2 Main Window created: "Il2-Sturmovik Forgotten Battles" (MaddoxRtsWndClassW), Handle= 0x000C02D8
2024-12-21 09:27:57:296   (watchdog) : Activating IL-2 Main Window (0x000C02D8) using SwitchToThisWindow()
2024-12-21 09:27:57:359    (wrapper) : ThreadAttach, attached Threads =  1
2024-12-21 09:27:57:406    (wrapper) : ThreadAttach, attached Threads =  2
2024-12-21 09:27:57:484    (wrapper) : ThreadAttach, attached Threads =  3
2024-12-21 09:27:57:531    (wrapper) : ThreadAttach, attached Threads =  4
2024-12-21 09:27:57:593    (wrapper) : ThreadAttach, attached Threads =  5
2024-12-21 09:27:57:625    (wrapper) : ThreadAttach, attached Threads =  6
2024-12-21 09:27:57:656    (wrapper) : ThreadAttach, attached Threads =  7
2024-12-21 09:27:57:687    (wrapper) : ThreadAttach, attached Threads =  8
2024-12-21 09:27:58:296   (watchdog) : Successfully activated IL-2 Main Window (Handle: 0x000C02D8)
2024-12-21 09:28:26:828    (wrapper) : ThreadAttach, attached Threads =  9
2024-12-21 09:28:26:859    (wrapper) : ThreadDetach, attached Threads =  8
2024-12-21 09:28:37:593    (wrapper) : ThreadAttach, attached Threads =  9
2024-12-21 09:28:37:625    (wrapper) : ThreadDetach, attached Threads =  8
2024-12-21 09:28:58:671    (wrapper) : ThreadAttach, attached Threads =  9
2024-12-21 09:28:58:703    (wrapper) : ThreadDetach, attached Threads =  8
2024-12-21 09:29:02:375    (wrapper) : ThreadDetach, attached Threads =  7
2024-12-21 09:29:02:406    (wrapper) : ThreadDetach, attached Threads =  6
2024-12-21 09:29:02:421    (wrapper) : ThreadDetach, attached Threads =  5
2024-12-21 09:29:02:734    (wrapper) : ThreadDetach, attached Threads =  4
2024-12-21 09:29:02:765   (watchdog) : IL-2 Main Window destroyed: "Il2-Sturmovik Forgotten Battles" (MaddoxRtsWndClassW), Handle= 0x000C02D8
2024-12-21 09:29:02:765    (wrapper) : ThreadDetach, attached Threads =  3
2024-12-21 09:29:02:828    (wrapper) : ThreadDetach, attached Threads =  2
2024-12-21 09:29:02:843    (wrapper) : ThreadDetach, attached Threads =  1
2024-12-21 09:29:02:796   (watchdog) : IL-2 main window (handle 0x000C02D8) disappeared, checking process status.
2024-12-21 09:29:02:953    (wrapper) : ProcessDetach, attached Processes =  0
2024-12-21 09:29:02:984    (wrapper) : Total files opened = 326406
2024-12-21 09:29:03:015    (wrapper) : Files loaded from SFS archives = 17290
2024-12-21 09:29:03:031    (wrapper) : Files loaded from mod folders  = 11581
2024-12-21 09:29:03:062    (wrapper) :   ~ using 1st level hash match = 11581
2024-12-21 09:29:03:078    (wrapper) :   ~ using 2nd level hash match = 0
2024-12-21 09:29:03:109    (wrapper) : Files not found                = 297535
2024-12-21 09:29:03:203    (wrapper) : Total search time consumed = 20.402 milliseconds (0.020401919261 Seconds)
2024-12-21 09:29:03:234    (wrapper) : Search Time per File = 62.505 nanoseconds (0.000000062505 Seconds)
2024-12-21 09:29:03:265    (wrapper) : Average Search Iterations required per File = 8.0
2024-12-21 09:29:03:281 (dinput.dll) : JVM Parameters injector deactivated
2024-12-21 09:29:03:359 (PipeLogger) : il2fb.exe Termination detected, terminating Pipe Logger.
2024-12-21 09:29:03:390 (PipeLogger) : All Writers Threads finished, exiting.


[Frankiek]

I had the paratrooper error too so maybe we could try with something intermediate like 640/320. I will see at it tomorrow

[vonOben]

I’ve done some testing in WAW on Windows XP playing The Black Death track and done Benchmarks tests with Fraps.
In auto mode IL-2 starts with 640/320 and 672/288, but after the track has ended I get a CTD.
The highest setting without CTD is 640/288.

The frame rate in Auto mode and without on 512MB are similar.

[Frankiek]

I can see that there a few XP diehard still around

I had similar results when comparing performances however the use of the latest versions of the selector really makes a difference including for the stock game. Not only I have an improvement of frame rates between 5-10% (depending on versions) but I also have smoother running and lower frequency of stutters. I suppose that on more powerful PC this is not a great deal but for a 20+ year old rig this is a blessing 

[Whiskey_Sierra_972]

Hi mates!

Can I ask a small off topic question?

There is some advantage to use XP over more recent version like W10 or W11?

[Frankiek]

No not really newer PCs will have a much better performance. But I had this old desktop lying around with the very first versions (Sturmovik, PF, 1946 etc etc) installed. So it was fun to give him a second life after all we all deserve a second chance.  I also have to admit that after years of laptop screens is also good for my aging eyes to look at a decent size display.   

[SAS~Storebror]

the Final JVM Option: -XX:MaxPermSize=128M is the double to the one if I have when launching the selector without this parameter. On the other side the -Xmx increase is from 444M to 512M.

Well you can always use -XX:MaxPermSize=64M to see if that improves anything.

the use of the latest versions of the selector really makes a difference including for the stock game.

Just to precise here:
Are you running the tests within the same game instance, "just" swapping out the selector?
Or are these different game folders you are using?
And if it's really "just" swapping the selector, would you mind illustrating what exactly you are doing to get there?
I'm not trying to be picky, just wanting to understand what you did so I can - with a little luck - reproduce the issue.

Background is: With BAT 4.3 (The new Selector isn't available individually yet) we've not only shipped a new Selector, but applied at least one very significant corresponding change under the hood as well, and honestly the Selector itself is not supposed to have any influence on the game performance, as all it does is to "inject" launch parameters to the Java VM, which is what it always did.
The difference between new and old Selector is: Old had certain static launch parameters, new tries to figure out the best launch parameters automatically. Once you set the new selector to manual memory settings, the behaviour of both is precisely the same.
The remaining difference is that other important change under the hood, which I don't talk about in detail right now as otherwise it will have an influence on your answer to my initial question: What did you do exactly to change from new to old selector and vice versa?


Mike