Print

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

[SAS~Storebror]

Actually with that GPU I would say no AA at all and 8xAF max.
But what tomhighway described - extreme drop at accelerated time, only in BAT, not in "lightweight" modpacks - is exactly what happens when hitting the "Java Wall".
Can we see your il2fb.ini please and would you mind to let us know how much RAM there is in your system?

[tomhighway]

My compute has 8 gig of RAM.

Here's the file you asked for:

Code: [Select]

; Modtype setting. Set the number of different Mod Types here.
[Modtypes]
Types=3
; Mod Type No.1 (Zero-based Index=0).
; Set short Name, Help text, Files folder name and Mods folder name.
[Modtype_00]
Name=Stock Game
Help=Unmodded, untouched 'stock' game version.
Files=none
Mods=none
; Mod Type No.2 (Zero-based Index=1).
[Modtype_01]
Name=SAS MODACT 5.3
Help=SAS MODACT 5.3, mods reside in '#SAS' folder
Files=none
Mods=#SAS
; Mod Type No.3 (Zero-based Index=2).
[Modtype_02]
Name=B.A.T. World at War 1936-1946
Help=World at War 1936-1946, mods reside in '#WAW3' folder
Files=none
Mods=#WAW3
; Startup Settings for the SAS / UltraPack IL-2 1946 Game Launcher
[Settings]
; Mod Type Setting:
;
; 0=No Mods, Stock IL-2 1946 Server
; 1="Classic" Mod Style, i.e. modded files reside in "FILES" and "MODS" folder
; 2=SAS Modact Modded game, i.e. modded files reside in "#SAS" folder
; 3=UltraPack Modded game, i.e. modded files reside in "#UP#" folder
; 4=Dark Blue World Modded game, i.e. modded files reside in "#DBW" folder
; 5=Dark Blue World Modded game, i.e. modded files reside in "#DBW" folder
; default setting: 0
ModType=2
; Ram Size Setting in Megabytes.
; Be careful not to select too big size here.
; Above 512MB is risky.
; Above 1024MB is critical.
; Above 1800MB will most likely cause startup errors.
;
; default setting: 512
RamSize=1024
; Expert Mode Setting
; With Expert Mode enabled, the selector offers more setting options than
; than with default setting
;
; default setting: 0 (Expert Mode disabled)
ExpertMode=0
; Memory Strategy setting
; This setting affects the way memory is being allocated for the Java
; virtual Machine. Balanced means that memory will be allocated in a
; blanced manner for heap, stack and objects.
; Heap only is the "old fashioned" way of binary edited il2fb.exe files
; where only the heap memory size is getting increased while all other
; memory areas remain untouched.
; Conservative is a setting right between Balanced and Heap only.
;
; default setting: 0 (Balanced Mode)
MemoryStrategy=0
; Cached File Lists setting
; When this setting is enabled, IL-2 on startup does not scan the modded files
; folder anymore, but uses a filelist cache file for this folder if it exists.
; The filename for this cache file is "~wrapper.cache".
; Every time when you change something inside your modded files folder, you
; have to wipe this file for the game to recreate it with updated contents.
;
; default setting: 0 (Cached File Lists disabled)
UseCachedFileLists=0
; Multiple Instances setting
; Usually you can run only one single IL-2 instance at a time.
; When you enable this setting, you can run IL-2 multiple times in parallel.
; This is particularly useful for developing and debugging tasks.
;
; default setting: 0 (Multiple Instances disabled)
MultipleInstances=0
; Exit With IL-2 setting
; When enabled, IL-2 selector will quit when you exit the game.
; When disabled, you'll get back to the selector when you exit the game, in
; case you started it through the selector.
;
; default setting: 0 (Exit With IL-2 disabled)
ExitWithIL2=1
SplashScreenMode=1
; The following section holds additional parameters for the JVM,
; one parameter per line. Check Java 2 SE documents for applicable parameters.
DumpMode=0


[SAS~Storebror]

Ramsize 1024 is critical, as indicated by the Selector when choosing it.
Stick to 512 and try again please.


Mike

[tomhighway]

Okay. Flew a couple of missions with the Ramsize at 512. It seems like it may have helped a little, but certainly didn't fix it. If I set the time compression to X8 and bring up the mini map, the fps still drops to 0.  At X4 with the map up it only drops to about 4fps. If I don't use time compression, it still drops to around 30fps sometimes just by bringing the map up. I also noticed that when I turn on the ntrk recorder, I get a freeze frame that lasts about 5 to 7 seconds.

[SAS~Storebror]

You seem to have other issues with your game.
I'd recommend a complete reinstall of BAT.
What you describe doesn't make sense for a working BAT installation of good integrity.


Mike

[tomhighway]

I will give that a try.

Not sure when I'll get it done, but I will let you all know how it goes after it happens.

Thanks to you both for your help. I appreciate it.

[tomhighway]

Okay.

I wiped my hard drive and got the new Operating System installed. Got all of my versions of IL-2 1946 up and running.   4.07, 4.12.2, 4.13.4, VPMod, Ypack, all running with no issues.

Did a fresh install of BAT 4.0 RED CORE over a clean, unmodded version of 4.12.2. It ran pretty good. The fps never dropped below 22 even with X8 compression and the map up. The map by itself didn't seem to have much effect on the fps. At X4 or X2 time compression, the fps never dropped below 40, map or no map.  It's playable with those frame rates.
I installed the BAT 4.2 FLASHPOINT, and it's right back where it was before I made any changes to my computer. The map by itself will drop the fps 15 to 20 even at normal time. Without the map, X8 time compression will drop the fps down to 4. As you can imagine, with those frame rates, I get a lot of stutters and freeze frames. The game is unplayable at that point.

So, whatever issues I'm having came after installing 4.2 FLASHPOINT. I didn't bother with installing the BAT 4.2.1 update.

All of this testing was done running a mission I made in the FMB.  It's downloadable for play at Mission4today if you want to look at it to see how it might affect the fps during game play.

https://www.mission4today.com/index.php?name=Downloads3&file=details&id=3137


And by the way, for my Operating System, I went from Linux Mint 19.2 Xfce, to Mint 21.1 Xfce. Both versions ran all the other IL-2 1946 installs without issue.

Any ideas?

[SAS~Storebror]

Memory allocation issue in Wine?
It's guesswork.
BAT is a memory hog and we all know that the dreaded "Java Wall" just got pushed a lot further with BAT 4.0, but it still exists.
There's no other modpack even remotely as big as BAT, that's probably why it happens here and not anywhere else.
BAT 4.0 -> 4.2 adds quite a bunch of mods and might just have crossed the boundary for your version of Wine.
We have no such issues for Windows users so far, and dare I say: No one here is focussed on Wine support.


Mike

[tomhighway]

Howdy,

I've fixed the issue with BAT running properly on my computer. I bought a new computer with Windows 11 on it. The fps still drops considerably if I'm flying with a lot of airplanes in the air, lot's of ground clutter, x8 time compression, and lot's of explosions etc. However, even with all of that going on, and the mini map up, the fps never drops below 10, and I get no stutters or freeze frames. In normal flight mode ,(no time compression), the fps runs between 120 and 168, depending on what's happening at any given moment. I'm pleased with the way it's running now.


I do have another issue, with the controllers. This issue was present on the Linux machine, and it didn't go away with the new Windows box.

The issue is with my Gladiator NXT stick and my Thrustmaster throttle switching device numbers after a reboot/shutdown. I can't just remap the functions because the pitch and roll axis switch to the mini-stick on the throttle, and I lose my "hat" views on the stick also. If I reboot the machine many, many times, the device numbers eventually switch back, but it takes a lot of time and effort to do it. I typically end up deleting the "User" folder and replacing it with the one from my 4.12.2 unmodified install, and deleting the joystick configuration from the conf.ini file. Then I have to boot up the game with just the joystick, map all the buttons on the joystick, and then turn the game off, plug in the throttle/rudder pedals, and reboot the game. Even that doesn't work every time and I end up repeating the whole process many times.

The stick is a VKB Gladiator NXT. The throttle is a Thrustmaster TWCS with Thrustmaster TFRP rudder pedals.

Has anyone else here had this issue? If so, did you get it resolved, and what did you do to fix it?
And should I start a new thread with this issue in a different section of this forum?

Any help would be greatly appreciated.

[SAS~Storebror]

--> https://www.sas1946.com/main/index.php/topic,63136.msg695323.html#msg695323


Mike

[tomhighway]

I seem to be having exact same issue WxTech had.

"Mike,
I tried to run DeviceLister.exe, but a .NET Framework error box pops up:

Could not load file or assembly 'Microsoft.DirectX.DirectInput,
Version=1.0.2902.0 Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
The system cannot find the file specified

I'm following your 'recipe', in sequence, and have not yet got the .ini and .dll to put in the game folder..."

I can get the Application to go ahead and run, but the output box is empty.

I downloaded and put the "dinput8.dll" file in the BAT main folder, but that didn't change anything.

What am I doing wrong?

(edit) I did download and install the .net framework before I ever got the app to run.