Print

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

[GEORGES44]

Latest results with Mike settings:

Running perfectly:
- BAT EP12 (all modules)
- CUP
- UP 2.01
- 4.13.1 SASModAct6.1

Others versions (see previous post): no joy

[SAS~Storebror]

TFM, CUP, UI 1.2 frankly I don't care.
All of them are outdated, superseded, not developed further on.

VP Modpack I will try when I get the chance to, maybe next week.

Best regards - Mike

[GEORGES44]

Take your time Mike, there is no hurry.

And have a beer on my account

[GEORGES44]

Since I had some time, I made some experiments and I managed to get VPModpack working...and I am still laughing about the way it works

Experiment 1:
- took my IL2 1946 DVD and installed it via wine on /home/user/.wine/drive_c/IL-2 Sturmovik 1946=> it worked OK
- copied my VPModpack install on top of it => NOTHING (even with right click on selector and "open with wine")

Experiment 2:
- tried installing IL2 1946 with Playonlinux => error: install failed
    BUT a virtual disk "VPmodpack" was created in /home/user/.PlayOnLinux/wineprefix/VPmodpack

Experiment3: wild try crossover between Playon linux and wine:
- opened Playonlinux, choose "Configure" and select the virtual drive "VPmodpack" of experiment 2
- select "Divers" and "launch an .exe in this virtual drive"
- choose the Il2 selector.exe of experiment 1 (the one that gave no results)
   ====> AND IT WORKED:
  I could fly a few missions: only bugs so far gunsight on F4, and Blitzkrieg add-on causing a 70% CTD (although it works fine on W10)

Still laughing my ass out: How the same version of wine (only one installed, checked playonlinux uses the system version) can achieve such different outcomes only due to the location?   

Going for a walk to calm myself down; in the meantime, if a guru can find the answer, I'll be quite grateful for the enlightement

[SAS~Storebror]

I finally found time to check this myself and couldn't find any issues in running VP Modpack, installed with "all in one" Patch 1-14 and "New Patch 1" + "New Patch 2" on the same environment like I tested BAT with: Ubuntu 16.04 LTS + Wine 2.0.2.

See video of the test run here:



Best regards - Mike

[SAS~Storebror]

Further information for users who are facing OpenGL issues when trying to run IL-2 1946 on wine (like I just did when I tried to get it to run on latest and greatest Ubuntu 17.04):
If you get an error message like

Code: [Select]

err:wgl:init_opengl Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory
err:wgl:init_opengl OpenGL support is disabled.
Main begin: wglCreateContext failed
com.maddox.opengl.GLContextException: wglCreateContext failedyou are probably running on a 64 Bit OS and therefore need to add 32 Bit support and furthermore need to add OpenGL support to it.
In order to get there, open up a command prompt and enter the following commands:

Code: [Select]

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-dri:i386
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/libGL.so.1
Best regards - Mike

[SAS~Storebror]

*bump*
Tests finished on Ubuntu 17.04 "Zesty" with latest Wine "staging" 2.13 version.

How to uninstall old Wine versions (prerequisite before updating, otherwise you might have conflicting dependency issues):
Open up a terminal Window and enter the following commands:

Code: [Select]

sudo apt-get --purge remove winetricks
sudo apt-get --purge remove wine-stable
sudo apt-get --purge remove wine-devel
sudo apt-get --purge remove wine-staging
sudo apt-get --purge remove wine
sudo apt-get autoremoveNote: Depending on which wine parts and versions you have installed, one or the other command might reply that the regarding package isn't installed. That's normal.
When being asked to remove packages (even if it's lots of them), confirm with "y".

How to install Wine 2.13 "staging":
Open up a terminal Window and enter the following commands:

Code: [Select]

sudo dpkg --add-architecture i386
wget -nc https://dl.winehq.org/wine-builds/Release.key
sudo apt-key add Release.key
sudo apt-add-repository https://dl.winehq.org/wine-builds/ubuntu/
sudo apt-get update
sudo apt-get install --install-recommends winehq-stagingNote: I recommend installing the "staging" branch of wine for running IL-2 1946.

How to install additionally required OpenGL components:
Open up a terminal Window and enter the following commands:

Code: [Select]

sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-dri:i386
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/libGL.so.1
How to add required DLL overrides:
Open up a terminal Window and enter the following command:

Code: [Select]

winecfgSwitch to the "Libraries" tab and add the following library overrides:
"dinput" as "Native, Builtin"; "msvcp71" as "Native" and "msvcr71" as "Native".

I'd furthermore recommend to add your (several) IL-2 installation(s) as separate drive(s) in winecfg so you can find them easily later on the wine command prompt.

How to run IL-2:
Open up a terminal Window and enter the following command:

Code: [Select]

wine cmdThis opens up a windows command prompt.
Change to the drive/path pointing to your IL-2 installation, e.g. in my case VP Modpack was reachable like this:

Code: [Select]

d:
cd IL2
cd CLIENT
cd IL-2 VP ModpackFinally, run IL-2 with the following command:

Code: [Select]

il2fb
Best regards - Mike

[.-083]

Couldn't test too many different versions yet, but Modact 5.3, Modact 6.4 and UP3 + Patch Pack 210 are running fine for me.

Ubuntu 16.04 plain vanilla with all latest patches.
Wine 2.0.2 installed and up to date, straight from winehq.org repo (I've removed the previously installed xenial distro version 1.6.2 of Wine as it gave me nothing but errors).

Most important point for me to convince Wine to run IL-2 was to add the three DLLs:
Under "Libraries", I have configured "dinput" as "Native, Builtin"; msvcp71 as "Native" and msvcr71 as "Native".

Best regards - Mike

Thank you very much! Got it working with these settings

[SAS~Storebror]

Thanks for confirmation .-083.
I've added my test results including these settings and the OpenGL stuff for newer Linux/Wine versions to WineHQ's AppDB on 27th but they're still pending admin checks.

Best regards - Mike

[Heretic]

(Note: This is a massive cleanup from my initial post and subsequent edits!)


Got BAT 3.7.2 and VP Mod (16 parts, 2 patches) up and running on Arch Linux (kernel 5.3.x, WINE 4.18-1, native NVidia drivers version 435.21) after a bit of a struggle.
In case anbody needs some tips to get going:


1. Make sure you've got all WINE-related 32 bit packages installed.


2. All the installers, i.e. GOG's 4.10m installer and those from the later BAT updates worked flawlessly for me.


3. Create a 32bit wineprefix (replace "user" here and in all following commands with your usename; credit to Phoenix)

Code: [Select]

WINEPREFIX="/home/user/.wine_32" WINEARCH=win32 wine wineboot

4. Start winecfg in the new prefix

Code: [Select]

WINEPREFIX="/home/user/.wine_32" WINEARCH=win32 winecfgand add your local drives or at least the one you've installed IL-2 BAT/VP on, then select a virtual desktop with your screen resolution for the "default settings"(!!) entry ("Graphics" tab), then add an il2fb.exe to the list of applications and set its Windows version to "WindowsXP".
Select "Automatically capture mouse" in the "Graphics" tab and add these library overrides:

Code: [Select]

dinput (native, builtin)
dinput8 (native, builtin)
msvcp71 (native)
msvcr71 (native)

5. In a terminal, enter (reminder to change "user" to your username; also change the path to your il2fb.exe)

Code: [Select]

env WINEPREFIX="/home/user/.wine_32" wine start "e:/IL-2 1946 BAT/il2fb.exe"

6. IL-2 with BAT (or VP) should now start and load correctly. You're on the right track if you see the Selector's splash screen before the regular one.



Additional tips:

In case somebody uses a Linux native Opentrack, it has to be launched with

Code: [Select]

env WINEPREFIX="/home/user/.wine_32" /opt/opentrack/bin/opentrackin order to make it recognize the 32bit Wineprefix. (Username and path will of course differ.)
(Build instructions for Arch are here.)

Reshade also works!
https://www.sas1946.com/main/index.php/topic,46936.msg689339.html#msg689339

DCG 3.49 also works.


So far, I'm really happy how this turned out. Thanks for the hard work, SAS Team and VPmedia!

[SAS~Storebror]

So to summarize your issues:
Your Wine / Arch Linux combo insisted on being 64 Bit and you had to convince it to run IL-2 in 32 Bit mode.


Mike

[Heretic]

Basically yes.

To clarify, and what my previous post initially talked about: My 64 bit WINE prefix starts IL-2 with any BAT module just fine (when launched via "WINE start "[path to IL2FB.exe]""), but using the native dinput.dll basically breaks input (for me), making the mouse uncontrollable and only detecting two of four joystick axis (and, to add insult to injury, inverting them).
Switching to the built-in dinput.dll makes IL-2 crash on loading when using any mod/module that is more complex than Dawn Of Flight. However, stock IL-2 and Modact with a few mods do work and input works as advertised.

Luckily, the 32 bit prefix was the golden ticket out of that unsatisfying situation (thanks again to Phoenix for that post in the UP thread!).


I've only spent five hours flying in the sim, but so far, it's stable. Even the two DCG BoB camapaign missions that I've accidentially flown with full squadron density didn't produce any hiccups at 50+ aircraft. Framerates are also what you'd expect (40 - 60 FPS on a Ryzen 3700X with a 1060GTX).

Two drawbacks I've encountered so far is:
1) ...loss of the Umlaut keys in the keyboard assignments and in-session (they do work otherwise) and
2) ...lack of anti-aliasing from the NVidia control panel (doesn't work with WINE), which has to be injected with ReShade, at the cost of a blurry image or an extra sharpening filter on top.

But still, IL-2 seems to be better and more fun than ever thanks to the tremendous amount of work you guys are pouring in day after day! 

Now if you'll excuse me, there's an aircraft with my name on it. Can't decide which one yet and where to fly it, but there's one.