Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Having display problem and crashing after BAR v. 4.2.3 win7 OS.  (Read 293 times)

0 Members and 1 Guest are viewing this topic.

sixstrings

  • member
  • Offline Offline
  • Posts: 381
Having display problem and crashing after BAR v. 4.2.3 win7 OS.
« on: December 09, 2024, 12:28:30 AM »

Never had this problem before with BAT. Running Win7 OS. BAT Blue Edge will load to 20% then CTD. It changes my pc display settings when loading. Checked config .ini and display settings are correct. Read about other people having problems with win10/11 doing the same thing, but couldn't find anything out about with win7. Here's the log file. Maybe someone could piont me in the right direction ? Thanks for any help.   
Code: [Select]
[list type=decimal]
[li]2024-12-09 00:55:19:935 (dinput.dll) : JVM Parameters injector activated
2024-12-09 00:55:19:935 (dinput.dll) : Applying JVM Memory Settings from IL-2 Selector...
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -Xms888M
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -Xmx888M
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -Xss8192K
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -XX:PermSize=128M
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -XX:MaxPermSize=128M
2024-12-09 00:55:19:935 (dinput.dll) : Checking mandatory JVM Options...
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -Djava.class.path=.
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -Xverify:none
2024-12-09 00:55:19:935 (dinput.dll) : Added JVM Option: -Xcomp
2024-12-09 00:55:19:935 (dinput.dll) : IL-2 Process ID = 00001B54
2024-12-09 00:55:19:935 (dinput.dll) : Starting Watchdog at C:\IL-2 '46\IL-2 Sturmovik'46 BAT\bin\selector\basefiles\IL-2 Watchdog.exe 1 ""
2024-12-09 00:55:19:935 (dinput.dll) : Watchdog process started.
2024-12-09 00:55:19:951 (dinput.dll) : Starting Pipe Logger at C:\IL-2 '46\IL-2 Sturmovik'46 BAT\bin\selector\basefiles\PipeLogger.exe
2024-12-09 00:55:19:951 (dinput.dll) : PipeLogger process started.
2024-12-09 00:55:19:998   (watchdog) : IL-2 Parent Process Handle = 00000110, ID=00001B54
2024-12-09 00:55:19:998   (watchdog) : IL-2 Watchdog started.
2024-12-09 00:55:19:998   (watchdog) : Splash Screen Mode = 1
2024-12-09 00:55:19:998   (watchdog) : Splash Screen Image Path =
2024-12-09 00:55:19:998   (watchdog) : Splash Screen Image Full Path = C:\IL-2 '46\IL-2 Sturmovik'46 BAT
2024-12-09 00:55:19:998   (watchdog) : Message Window Created.
2024-12-09 00:55:19:998 (PipeLogger) : PipeLogger Starting
2024-12-09 00:55:19:998 (PipeLogger) : Reading PipeLogger Settings from C:\IL-2 '46\IL-2 Sturmovik'46 BAT\il2fb.ini
2024-12-09 00:55:19:998 (PipeLogger) : PipeLogger Settings:
2024-12-09 00:55:19:998   (watchdog) : LoadSplashImage.
2024-12-09 00:55:19:998 (PipeLogger) : ShowLogWarnings = false
2024-12-09 00:55:19:998 (PipeLogger) : LogSizeThreshold = 10,000,000 Bytes
2024-12-09 00:55:19:998 (PipeLogger) : ExceptionThreshold = 10 Exceptions
2024-12-09 00:55:19:998 (PipeLogger) : ErrorThreshold = 0 Errors
2024-12-09 00:55:19:998 (PipeLogger) : PipeLogger Process ID: 00001414; Parent (IL-2) Process ID: 00001B54
2024-12-09 00:55:19:998 (PipeLogger) : Listener thread awaiting client connection on \\.\pipe\SAS_PIPE_LOGGER
2024-12-09 00:55:19:998   (watchdog) : Loading Splash Image from "C:\IL-2 '46\IL-2 Sturmovik'46 BAT\bin\selector\basefiles\splash.png", Handle=00C9FFC0,
2024-12-09 00:55:20:107   (watchdog) : Splash Screen Created.
2024-12-09 00:55:20:185 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated
2024-12-09 00:55:20:185 (dinput.dll) : OpenGL Mode detected, checking IL-2 Graphics Extender Availability...
2024-12-09 00:55:20:185 (dinput.dll) : Trying C:\IL-2 '46\IL-2 Sturmovik'46 BAT\il2ge.dll
2024-12-09 00:55:20:185 (dinput.dll) : Trying C:\IL-2 '46\IL-2 Sturmovik'46 BAT\il2ge\lib\il2ge.dll
2024-12-09 00:55:20:185 (dinput.dll) : Trying C:\IL-2 '46\IL-2 Sturmovik'46 BAT\bin\selector\basefiles\il2ge.dll
2024-12-09 00:55:20:185 (dinput.dll) : IL-2 Graphics Extender not available.
2024-12-09 00:55:20:185 (dinput.dll) : Injecting JVM Parameters
2024-12-09 00:55:20:216 (dinput.dll) : Java Virtual Machine Initialization with additional parameters successful!
2024-12-09 00:55:20:216    (wrapper) : ProcessAttach, attached Processes =  1
2024-12-09 00:55:20:216    (wrapper) : Calling GetCommandLineParams()
2024-12-09 00:55:20:216    (wrapper) : Command Line Parameter No. 1 = /f:none
2024-12-09 00:55:20:216    (wrapper) : Command Line Parameter No. 2 = /m:#waw3
2024-12-09 00:55:20:216    (wrapper) : Command Line Parameter No. 3 = /lb:il2fb.exe
2024-12-09 00:55:20:216    (wrapper) : MODS Folder = "#waw3"
2024-12-09 00:55:20:216    (wrapper) : No FILES Folder set.
2024-12-09 00:55:20:216    (wrapper) : Calling LinkIl2fbExe()
2024-12-09 00:55:20:232    (wrapper) : Trying to link back to C:\IL-2 '46\IL-2 Sturmovik'46 BAT\il2fb.exe through LoadLibrary()
2024-12-09 00:55:20:232    (wrapper) : Calling CreateModsFolderList()
2024-12-09 00:55:20:310    (wrapper) : Scanning #waw3 folder took 84 milliseconds.
2024-12-09 00:55:20:310    (wrapper) : Total number of modded files = 17015.
2024-12-09 00:55:20:310    (wrapper) : Calling SortList()
2024-12-09 00:55:20:310    (wrapper) : Sorting modded files list took 3.984 milliseconds.
2024-12-09 00:55:20:310    (wrapper) : Calling RemoveDuplicates()
2024-12-09 00:55:20:310    (wrapper) : Removing 3 Duplicates took 0.057 milliseconds.
2024-12-09 00:55:25:489   (watchdog) : IL-2 Main Window created: "Il2-Sturmovik Forgotten Battles" (MaddoxRtsWndClassW), Handle= 0x006202BE
2024-12-09 00:55:25:489   (watchdog) : Activating IL-2 Main Window (0x006202BE) using SwitchToThisWindow()
2024-12-09 00:55:25:723    (wrapper) : ThreadAttach, attached Threads =  1
2024-12-09 00:55:25:723    (wrapper) : ThreadAttach, attached Threads =  2
2024-12-09 00:55:25:723    (wrapper) : ThreadDetach, attached Threads =  1
2024-12-09 00:55:25:723    (wrapper) : ThreadAttach, attached Threads =  2
2024-12-09 00:55:25:723    (wrapper) : ThreadDetach, attached Threads =  1
2024-12-09 00:55:26:128    (wrapper) : ThreadAttach, attached Threads =  2
2024-12-09 00:55:26:300    (wrapper) : ThreadAttach, attached Threads =  3
2024-12-09 00:55:26:394    (wrapper) : ThreadAttach, attached Threads =  4
2024-12-09 00:55:26:503   (watchdog) : Successfully activated IL-2 Main Window (Handle: 0x006202BE)
2024-12-09 00:55:26:503    (wrapper) : ThreadAttach, attached Threads =  5
2024-12-09 00:55:26:752    (wrapper) : ThreadAttach, attached Threads =  6
2024-12-09 00:55:26:752    (wrapper) : ThreadAttach, attached Threads =  7
2024-12-09 00:55:26:752    (wrapper) : ThreadAttach, attached Threads =  8
2024-12-09 00:55:26:752    (wrapper) : ThreadAttach, attached Threads =  9
2024-12-09 00:55:26:768   
 
Logged

Epervier

  • 4.09 Guardian Angel !
  • SAS Team
  • member
  • Offline Offline
  • Posts: 9589
  • I'm French and Rebel_409! Nobody is perfect!
    • Some tinkering here
Re: Having display problem and crashing after BAR v. 4.2.3 win7 OS.
« Reply #1 on: December 09, 2024, 02:50:23 AM »

Here's the log file.
It's not the LOG file !
Logged
If your results do not live up to your expectations, tell yourself that the great oak was once an acorn too. - Lao Zi -

JCC

  • member
  • Offline Offline
  • Posts: 26
Re: Having display problem and crashing after BAR v. 4.2.3 win7 OS.
« Reply #2 on: December 09, 2024, 03:48:41 AM »

I updated one of my BAT 4.2.2 Installs to BAT 4.2.3 awhile ago, and as I´ve been using BAT for more than 5-6 years now, I did it like I used to do (and followed the Instructions too), and once I had reloaded all Mods that I use in #WAW3 with JSGME (which are quite a lot) I Started it up.. and it went tit´s up.. -Wtf?!?

I checked the Log, but since I don´t really understand the Log all that well. I firstly thought it was the added huge Single Missions addon that I Installed by using JSGME, but it wasn´t, and I was devastated and had one of those -FUXX!!!! moment. Which was prolly what I needed to clear my mind.
..
Anyways, I started to check the huge Mission addon which I felt could be the culprit, but as I know that the guys who had made it is very skilled, I kinda realized that the only one to blame for this was prolly me.

So I started to compere the folder structure with my other Installs of the game and saw that I had a new Folder in the new 4.2.3 Install called MODS. So I checked the JSGME.ini and sure enough it pointed toward that MODS folder, which I never had one before. I mean, I never had a folder Installed named MODS before.

My BATMODS folder where all my mods reside was still there, but according to the the 4.2.3 Update´s JSGME.ini file, I could figure out that one should use the newly installed MODS Folder from now on and NOT the BATMODS folder anymore.

Some of my Mods seemed to have gone up in smoke too and it made me a wee bit angry (understatement of the year) In all my years using these awesome BAT-Updates I had never ever experienced nothing but minor problems of which pretty much all was my fault, and I was afraid that I would not be able to fix the problem.
..
Anyways.. I started out by checking the Installations Instructions but there was nothing in it about the newly Installed MODS folder or how to use it. EDIT: That I could find in my upset state then. There is of course Information available about it./JCC
..
A few coups of coffee later my brain was back in working mode again. So I compered a couple of JSGME.ini files with the new one from the 4.2.3 Update, and sure enough you should use the MODS folder with it and NOT the BATMODS folder anymore.
..
The Solution: I moved all my gathered mods that hadn´t gone tit´s up from the BATMODS folder to the new MODS Folder and in the few cases where I believed the mod prolly was damaged, I used JSGME ready backups and added them to my new MODS folder. Once that was done I took a look at the JSGME.ini file again and made sure that it pointed to the MODS folder, as I had edited it in an attempt to make it use the BATMODS folder (which it certainly wouldn´t do.)

While trying that I realized that all I prolly needed to do was to point it to use the MODS Folder and once it did, the file would get sorted "by itself" even though my incorrect attempts to Edit it, because the ones who has written the JSGME proggie is good at what they do.
..
Once done I tried to fire up the Game again and it started and the JSGME.ini file was sorted too! ]hello2[
Now "all" that was left to do was to add all my Mods, it took a while as of 124 Mods I currently have available, 87 of those Mods are now activated by JSGME, and it worked like a charm.
..
Once done I felt very satisfied, but also quite tired and went to bed after a few flight´s.

This might not be your problem mate, but it could be. This Installation is made on a Win7 64 and it works really well now. I should perhaps try to use a good Intel/Nvidia Win11 Laptop which I got from my son-in-law for the game as it is a far better PC, but the BAT 4.2.3 runs remarkably well on my old Win7 64 PC tower, so I dunno if gives any improvement to be honest.
..
EDIT: I was of course working with BAT 4.2.3 Update. -Doh.. ]clown[

Cheers  ]cheers[
/JCC 
 
Logged

Vampire_pilot

  • member
  • Offline Offline
  • Posts: 8630
Re: Having display problem and crashing after BAR v. 4.2.3 win7 OS.
« Reply #3 on: December 09, 2024, 04:56:23 AM »

20% usually is some "incompatible" ini file somewhere.  Your install is botched.
Logged

sixstrings

  • member
  • Offline Offline
  • Posts: 381
Re: Having display problem and crashing after BAR v. 4.2.3 win7 OS.
« Reply #4 on: December 09, 2024, 06:38:09 AM »

So sorry guys. Been having IL-2 BAT "Blue Edge" working for quite a long while till my win10 pc crashed and had to start over in a backup win7 64bit pc, but am currently suffering from Parkinson's Disease and having problems now. Will try installing BAT slower.May not be able to,but will keep trying. God willing,there is hope. Thanks for the help. Did get BAT Red Core v. 4  working though
Logged
Pages: [1]   Go Up
 

Page created in 0.071 seconds with 20 queries.